esip & geospatial one-stop (gos) registering esip products and services with geospatial one-stop

ESIP & Geospatial One-Stop (GOS)

Registering ESIP Products and Services with Geospatial One-Stop

Objective – Answer Questions?

Why should ESIP members publish their metadata holdings to the GOS?

How do ESIP members publish their metadata holdings to GOS?

What is GOS?

Geodata.gov is a portal to our Nation’s digital geographic data.

Managed by the Department of the Interior and sponsored by the President’s Initiative for E-Government.

The portal is a catalog of geospatial information containing metadata records (information about the data) and corresponding links to live map, feature, and catalog services, downloadable data sets, images, clearinghouses, map files, and more.

What is GOS (cont)?

Metadata Repository Tools for uploading and harvesting metadata. Tools for metadata management and administration. Search Interface Map Viewer Communities Marketplace

GOS and Standards

Metadata FGDC & ISO (NA Profile in future)

OGC WMS, WFS, WCS

Harvesting Protocols CS-W, Z39.50, OAI, WAF, ArcIMS

Catolog Search CS-W, Z39.50, OAI, GOOGLE HTP

Portlet JSR-168

ESIP Community

How do ESIP members publish their metadata holdings to GOS?

Step 1: Prepare metadata for GOS ingest. Step 2: Register as a publisher. Step 3: Select a publishing method.

GOS metadata creation tool Upload Metadata - Manual Harvest Metadata – Automated

Step 4: Configure harvesting. Step 5: Review harvesting results.

Step 1: Prepare metadata for GOS Ingest?

Ensure Validation Include required elements

Optimize search with conditional elements Free Text Spatial Temporal Data Type Data Theme Publisher

Optimize references to external resources with online links Map Services Map File Data Documentation

Required Validation Elements

Identify Info

Required Validation Elements (cont)

Contact Info

Required Validation Elements (cont)

Dates

Required Validation Elements (cont)

Spatial Domain

Sample XML Metadata Record with FGDC Essential Elements

Sample XML Metadata Record with FGDC Essential Elements (cont)

Valuable Conditional Elements

Defined in Metadata or Generated by GOS XSLT

Resource description (content type)

Valuable Conditional Elements (cont)

Theme Keywords (data category) /metadata/idinfo/keywords/theme/themekey /metadata/dataIdInfo/tpCat/TopicCatCd

Valuable Conditional Elements (cont)

Online Links – reference external content Detected in multiple elements Used by GOS XSLT to define content type

Step 2: Register as a Publisher

Step 3: Select Publishing Method

GOS Publishing Methods Create Metadata Tool Upload Metadata Tool Harvest Metadata

Create Metadata Tool

Form based metadata creation Ensures Validation One record at a time

Upload Metadata

Form for manual uploading of metadata One record at a time

Harvesting

Automated, scheduled process for collecting new and updated FGDC metadata from external catalogs for publishing to GOS.

Synchronizes GOS repository with publishers metadata catalog.

Five protocol options available for harvesting.

Preferred publishing method for large metadata catalogs.

Step 4: Configure Harvesting

Protocols Z39.50 ArcIMS WAF OAI-PMH CS-W

Harvest / Publish Process

Harvesting Protocol Pros-Cons

Protocol Pro ConZ39.50 Open interoperable

standard clearinghouse connection supports GSDI and GEOSS. Queries, security and ISite SW support.

SW Requires some resources to setup and administer. Must set up on port other than 80. Must use new version of ISite to assign unique ID to records.

ArcIMS Simplifies publishing if in an Arc environment - good persistent unique ID supports traceability. SW allows use of other protocols. AXL Code is xml based.

Exposes your collection to other ESRI collection. Proprietary interface connects easily with GOS but not natively to other NSDI/GSDI nodes. (GOS make the whole collection available through the other protocols). May need to edit some fields. Code provided by one vendor.

WAF Easy to set up with little administration

(Note - different access controls – Active Directory based)

Unique ID management is tied to the location of the system as opposed to a persistent ID from the metadata. ID changes if folder moves to a different machine.

Harvesting Protocol Pros-Cons

Protocol Pro Con

CS-W Interoperable OGC Spec Still new. Many flavors or profiles (EBRim, FGDC, ISO etc). Currently appears to only support getting a subset of the metadata and not the full record back.

OAI-PMH Library community supported.

Very few users at this time in GOS. Limited experience with it.

Step 5: Review harvest results

Harvest Report

Harvest Report

Harvest Report

Indentify metadata records that fail validation.

How does GOS benefit ESIP?

Provides a repository for ESIP metadata. Provides a forum for showcasing ESIP

products and services to the broader geospatial community.

Provides a gateway for GOS users to access the EIE portal.

Top 10 reasons ESIP members should publish their data holding to GOS?

1. Organizational exposure via the ESIP community. 2. Map Viewer for displaying map services (OGC & ArcIMS).3. Option to view map services in Google Earth.4. Robust search tools for finding metadata (spatial, temporal,

text based searching).5. Google search enabled metadata.6. Marketplace for finding & sharing geospatial resources.7. Easy to use publishing, harvesting, and metadata management

Tools. 8. FGDC & ISO friendly ingest.9. The GOS repository will eventually be harvested by the EIE.10. It will make Dick happy!

References

Publishing Metadata to the Geospatial One-Stop Operational Portal- ESRI White Paper

Creating and Publishing Metadata in Support of Geospatial One-Stop and the NSDI