Friday, November 4, 2011

ISO19115 to REST – You can’t go there with metadata

It took me awhile to figure out that it's not easy to author geospatial metadata that will show up in your ArcGIS Server REST catalog for a map service.

The Excel table “Geospatial Metadata Authoring for ArcGIS Server REST and ArcGIS Online Display Throughput”  is a plumbing diagram.  It shows the information flow (and barriers) from ISO19115 metadata authoring in ArcGIS Desktop to display in the ArcGIS Server REST catalog and ArcGIS Online.

I wanted to understand how to author metadata so that it shows up in the ArcGIS Server REST directory and in map descriptions at ArcGIS Online.  And to find opportunities to author metadata once and use it in many places.  I used the ArcGIS desktop metadata editor (ISO19115 NAP format) to author metadata for two map layers (feature classes) and one map document (.mxd).  I published the map service then examined the REST directory.

In the table, metadata input columns are on the left:

§  The ISO19115 NAP metadata fields required by San Mateo County GIS
§  ArcMap Map Document (.mxd), Group Layer, and Layer Properties fields
§  ArcGIS Server Manager configuration fields
§  ArcGIS Online Map Details fields

Web outputs are on the right:

§  ArcGIS Server REST Directory
§  ArcGIS Online Web Map Details page

I was surprised to find that:

  •  For Layers in an ArcMap Document, no text from any field in the metadata editor appears in the ArcGIS Server REST directory for the resulting map service.
  • These REST directory fields are populated from these Layer Properties fields in ArcMap (not the metadata editor):
    • Description  (Description in mxd)
    • Copyright Text (Credits in mxd)
Tags added in the ArcMap Document Properties page appear as "Tags for Searching" in the metadata editor.

Confused yet?  If you want to document your map service, you need a metadata roadmap.

1 comment:

  1. Good post. A real shame they block ExportMetadata_conversion on server (from a geoproc) as it works beautifully when local. Albeit for viewing only.