Geospatial Metadata session 8:30 EPA’s Metadata Workgroup –Matt Leopard, OEI 9:00 Data and Metadata publishing– John Bocchino New Jersey DEP 10:00 ESRI Metadata Tools– Jeff Donze 10:45 Break 11:00 Tools for Creating Metadata –Eugenia Naranjo, R2 / Tom Giffen, R1 11:45 Metadata Architecture Wendy Blake-Coleman, OEI
How Does the Profile Affect Existing FGDC Standards? The EPA Profile affects the minimum FGDC requirements by requiring the use of some additional FGDC metadata elements that are not required by minimum standards. It will also affect the application of the minimum FGDC requirements by defining usage for certain tags that are currently implemented as free text entries. The EPA profile is NOT currently proposing to affect the minimum CSDGM by creating new elements. Every tag included in the EPA profile is defined within the CSDGM. The EPA profile will enhance the use of some of these existing tags by providing restrictions on their values, and/or by requiring their use. The EPA will rely on guidance provided by the FGDC for elements not explicitly defined within the profile.
Profile Development Approach • 1. Adhere to Agency and Federal Standards • Base profile on FGDC standards • Use Agency policies to apply usage to standard elements • Align with other Agency standards development activities • 2. Use Existing Examples as Guidelines • Review existing usage by EPA geospatial data developers • Review existing examples by external data developers • 3. Use Guidance Provided by Others • State agencies • Other topic area experts
Metadata Business Rules Considerations Metadata Life-cycle Planning • Creating • Updating • Reviewing • Stewardship Contributions to public repositories (GOS and NSDI) • All EPA geospatial data sets • ‘Non-sensitive’ data sets Creating Consistent Documentation for Common or ‘Priority’ Data Themes • Develop templates to provide consistency for similar data sets across regions Online linkage for public data sets? • Regional status with respect to FGDC/ISO compliancy? • What will the level of effort be once the profile is implemented. • What type of assistance should be provided to authors: metadata editors, guidance, documentation, support?
NJDEP Data and MetadataPublishing Procedures New Jersey Department of Environmental Protection (NJDEP) Bureau of GIS John Bocchino, NJDEP Data/Metadata Manager EPA GIS Work Group Spring 2005 Meeting Atlanta, Georgia
NJDEP Data and Metadata History Data Distribution Value of Metadata Metadata Training Data Administration and Metadata Creation Data and Metadata Submittal Process How Data/Metadata is Cataloged: Internally by NJDEP On Internet Clearinghouse (NJGIN) Security NJDEP handles Data/Metadata Security Issues through: ArcCatalog NJGIN Outline
NJDEP Data Sharing (Mid-1990’s) CD ROM GIS data downloads page (non-FGDC compliant metadata) The ENDEX Clearinghouse Concept NJ Office of GIS Statewide GIS Coordination NJGIN (New Jersey Geographic Information Network) NJDEP Data Sharing (Present) GIS data downloads page (FGDC compliant metadata) NJGIN/Geospatial One-Stop ArcIMS Application Metadata are key for internal/external cataloging NJDEP Data & Metadata History
Before ArcGIS, other metadata tools utilized NJMetaLite for public distribution (free) SMMS for personal metadata management (cost) ArcCatalog: Data Administration and Metadata Creation Experienced GIS specialists trained first in metadata creation Rolled metadata training into 3 day beginners ArcGIS course Online Tutorial NJGIN Clearinghouse usage How to find other data sources through metadata NJDEP Metadata Template and Profile Personal Templates (contains generic information) Checklist of FGDC fields used by NJDEP. Metadata Training
Data & Metadata Submittal Process • Data Creators must create FGDC compliant metadata • Required for review and to ensure FGDC/NJGIN compliancy • Required for administrative cataloging of data on network • Required for any data to be published on Internet. • During review, security questions are asked: • New data? • Internet Peer Review Council (IPRC) must be notified. • Does new data contain any sensitive information? • Update of existing published data? • Does update contain any new fields that may contain sensitive information? • Yes - IPRC needs to be notified. • No- Approved for quick publication.
Data & Metadata Submittal ProcessData and Metadata Administration/Tracking Procedures • File Name/Date Received • Number of files • Data Creator Name • Run MP • Review • Spell Check • Export • Create images • Create zips • Save Data/Metadata on Network • Import Data/Metadata into SDE* • Publish Data/Metadata to GIS Downloads Page • Publish Metadata to NJGIN • Date Complete/Notes • Alert GIS Users • Demo of GIS Downloads Page
A Metadata Clearinghouse plus: A searchable news archive An interactive directory of registered users An interactive calendar of events A browsable list of current NJGIN publishers and metadata Distributed network of geospatial data nodes whose information can be accessed centrally, while being managed locally. Ability to directly control posting and administration of metadata through ArcCatalog Data & Metadata Submittal ProcessNew Jersey Geographic Information Network (NJGIN)
Publishing Metadata in ArcCatalog Drag and Drop Demo of NJGIN
Most DEP data for public distribution Document security classification in FGDC metadata fields Security addressed by NJGIN metadata services through ArcCatalog DEP Public Publish (anyone) DEP Publish (needs login and password) Can address “data” security concerns in selected Internet mapping applications Security Concerns
Public Data readable by anyone Secure Data available to state and other government workers as needed for official purposes Classified Data of a sensitive nature, available only to designated employees, supercedes above categories Personal Personally-identifiable information about individuals, protected by federal or state law, spercedes other categories Above used in Section 1 and Section 7 of CSDGM. Data and Metadata can have different Security Classifications; for example a Secure data set may have Public metadata. NJGIN Security Classification Entries
Provides concise descriptions of data sets Protects DEP investment in data Makes it known that the data exists Link directly to on-line data Reduces the risk of duplication Aids data transfer Included in zip Import, then modify for updates or other data formats Promotes proper data management Allows for protection of data sets Writing metadata does not require 'open access' to data In Summary: Metadata are Key
Geospatial One-Stop Portal Project&The Portal Toolkit EPA GIS Workgroup Spring Meeting2005 Jeff Donze & Chris AlbertESRI
GeoSpatial One-Stop • Primary Use • Discovery and access to geospatial resources (data, applications, web sites) • Primary Goal • Reduce redundant investments and facilitate cost sharing
Team Members • ESRI – Spatial • Google – Search Engine • IBM – Portal Framework / Collaboration Tools • Safe Software – Interoperability & Standards • Image Matters – Interoperability & Standards • Northrop Grumman – Interoperability & Standards • SNVC – Security, Certification & Accreditation • Dataline – Portlets • UC San Diego Supercomputer Center – Usability/Portlets/ Transliteration
What We Learned from the PrototypeFive Important Insights • Usability • Improve user experience • Support multiple audiences • Performance • Achieve sub-second responses • Interoperability • Support evolving standards (Portals, OGC, etc.) • Support data download • Functionality • Channels worked – “two clicks to content” • Marketplace community • Newtechnologies…
Examples: My Yahoo, My MSN, My EBay Portal Technology JSR - 168 IT interoperability standard What’s New Search Engine- Google Spatial Toolkits Communities Marketplace Portlet building blocks What this Means for GOS … GIS Centric Web Standard Specialized Search Google-like Uniform View Personalized
FTP Data Servers The Concept … Users Users Users Connect and Use Download and use Search Catalog and Find GIS Portal Geospatial Resources Publish GIS data and services Document in catalog GIS Data GIS Data GIS Data
Metadata fuels the GIS Portal Catalog Data Models Models Metadata Data Sets Maps Metadata documents describe content and relationships
Gazetteer Category Data Index Map Building GIS portals Search & Navigation View Spatial Users Categories Thesaurus Supporting Data Sets Metadata Publishers Partners
Interoperable Architecture JSR-168 IBM WebSphere Portal WMS Single Sign-on and Personalization WFS/GML Apps FGDC Map Viewer Publish Search WCS ArcIMS ISO WMC Other JSR-168 Portlets Open LS Gazetteer Catalog Service GIS Portal Toolkit Metadata Harvester CS-W CS-W Z39.50 Z39.50 Google http WAF / XML ESRI-Google Spatial Extender Natural Language Search OAI OAI-PMH Google Search Appliance ArcIMS Open LS Gazetteer Metadata Catalog ArcSDE / RDBMS COTS & Standards Based ( Programmatic Connection )
Demonstration Performance Usability Functionality Interoperability
Accessing Open Geospatial Consortium compliant web services Catherine Harness RTP Eugenia Naranjo Region 2 GIS Workgroup meeting, Atlanta
What is the Open Geospatial Consortium (OGC)? It is a non-profit, international, voluntary consensus standards organization that is leading the development of standards for geospatial and location based services.
Why access OGC Compliant Web Services? • Enables seamless integration of a variety of online geoprocessing and location services • Allows communication using technologies such as XML and Http • Provides vendor-neutral interoperable framework for web-based discovery, access, integration, and analysis of online geodata sources
What is a Capability File? It is an XML file that contains service level metadata, which is a description of the service’s information content and acceptable request parameters.
Why is a Capability File Important?: • Required component of an OGC web service. • Makes it possible for other applications to communicate with the OGC web server. Discover Search Publish Discover Service Web Applications requester OGC Web Services provider Consume Service description (xml capability file)