Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Element Description

The Spatial Information element stores information about the reference frame from which horizontal and vertical spatial domains are measured. The horizontal reference frame includes fields for Geodetic Model, Geographic Coordinates, and Local Coordinates. The Vertical reference frame includes fields for altitudes (elevations) and depths.


Best Practices

Providing Spatial Information is optional, but encouraged. This element can be used to provide horizontal and/or vertical coordinate system information. 

The Spatial Coverage Type field is required for Spatial Information. 

  • Spatial Coverage Type: Denotes the type of spatial coverage of the collection. While this field is not currently controlled, recommend providing one of the spatial coverage type enumeration values: HORIZONTAL, VERTICAL, ORBITAL, HORIZONTAL_VERTICAL, ORBITAL_VERTICAL

Horizontal Spatial Information

The following sub-elements can be used to describe Horizontal Coordinate Systems.

There are 3 categories for Horizontal Coordinate Systems including:

(1) Geodetic Model

Geodetic Model is used to describe data that has been georeferenced to a datum, which is a well defined ellipsoidal/spherical representation of the Earth. There are many different standard datums. Knowing which datum the data is encoded in is extremely useful for manipulating the data using GIS software. Sub-elements under Geodetic Model are summarized below:

      • Horizontal Datum Name: The name of the datum the data are encoded in. Also commonly referred to as a geodetic datum. A geodetic datum is a more localized/ specialized version of a simple Ellipsoid model of the Earth (see below). It is recommended that EPSG Datum names be used. 
      • Ellipsoid Name: An elliptical or spherical shape representing the Earth. An Ellipsoid's shape can be defined by a major axis (longer axis) and a minor axis (shorter axis). There are standard names for different Ellipsoids - it is recommended that EPSG Ellipsoid names be used. 
      • Semi Major Axis: The radius of the major axis of the Ellipsoid. The length and units of the Semi Major Axis should be defined in the Ellipsoid standard. 
      • Denominator Of Flattening Ratio: The ratio of the Ellipsoid's major axis to the difference between the major and the minor axis. Also referred to as the Inverse Flattening ratio. The smaller the ratio, the 'flatter' or more oval-like the Ellipsoid's shape will be. The units of the Inverse Flattening ratio are also defined by the Ellipsoid standard. 

(2) Geographic Coordinate System

Data that has been georeferenced to a geodetic datum are provided in latitude and longitude coordinates. The Geographic Coordinate System fields can be used to describe the coordinate system in more detail. Sub-elements under Geographic Coordinate System are summarized below:

      • Geographic Coordinate Units: Units of measure used for the geodetic latitude and longitude resolution values (e.g., decimal degrees or degrees minutes seconds).
      • Latitude Resolution: The minimum difference between two adjacent latitude values in the Geographic Coordinate System, expressed in the Geographic Coordinate Units of measure, expressed as a two-digit decimal number, e.g., 0.01.
      • Longitude Resolution: The minimum difference between two adjacent longitude values in the Geographic Coordinate System, expressed in the Geographic Coordinate Units of measure, expressed as a two-digit decimal number, e.g., 0.01.

(3) Local Coordinate System

Data collected over small or localized areas may be georeferenced to a custom or highly specialized reference system. In order to accurately compare the local data to other data, the local coordinates must be converted to a standard reference system such as one of the EPSG geodetic datums. The Local Coordinate System fields provide information about the local coordinate system. Sub-elements under Local Coordinate System are summarized below:

      • Geo Reference Information: Information on how the local system were registered to a standard reference system (e.g. control points, satellite ephemeral data, and inertial navigation data). In some cases, the user may be responsible for georeferencing the data.
      • Description: A description of the Local Coordinate System and georeference information.

Vertical Spatial Information

The following sub-elements can be used to describe Vertical Coordinate Systems.

There are 2 categories for Vertical Coordinate Systems including:

(1) Altitude System Definition 

Altitude System Definition should be used to describe data with a vertical component that is above-ground. Sub-elements under Altitude System Definition are summarized below:

      • Datum Name: The name of the vertical datum the data is encoded in. Vertical datums define a level reference surface from which vertical measurements are compared. There are many standard vertical datums. If a standard vertical datum is used, it is recommended that the EPSG vertical datum name be provided. 
      • Distance Units: The units in which altitude measurements are recorded. This field is controlled and must be selected from one of the following values: HectoPascals, Kilometers, Millibars
      • Resolutions: The minimum distance possible between two adjacent values, expressed in distance units of measure for the collection.

(2) Depth System Definition

Depth System Definition should be used to describe data with a vertical component that is below-ground. Sub-elements under Depth System Definition are summarized below:

      • Datum Name: The name of the vertical datum the data is encoded in. Vertical datums define a level reference surface from which vertical measurements are compared. There are many standard vertical datums. If a standard vertical datum is used, it is recommended that the EPSG vertical datum name be provided.
      • Distance Units: The units in which depth measurements are recorded. This field is controlled and must be selected from one of the following values: Fathoms, Feet, HectoPascals, Meters, Millibars
      • Resolutions: The minimum distance possible between two adjacent values, expressed in distance units of measure for the collection.

          Examples

Example 1:


Example 2:

SpatialCoverageType"HORIZONTAL_VERTICAL"

   HorizontalCoordinateSystem/GeodeticModel/HorizontalDatumName: "World Geodetic System 1984"

           HorizontalCoordinateSystem/GeodeticModel/EllipsoidName: "WGS 84"

           HorizontalCoordinateSystem/GeodeticModel/SemiMajorAxis: "6378137"

           HorizontalCoordinateSystem/GeodeticModel/DenominatorOfFlatteningRatio: "298.257223563"

           HorizontalCoordinateSystem/GeographicCoordinateSystem/GeographicCoordinateUnits: "Decimal Degrees"

           HorizontalCoordinateSystem/GeographicCoordinateSystem/LatitudeResolution: "0.05"

   HorizontalCoordinateSystem/GeographicCoordinateSystem/LongitudeResolution: "0.05"

   VerticalCoordinateSystem/AltitudeSystemDefinition/DatumName: "National Geodetic Vertical Datum 1929"

   VerticalCoordinateSystem/AltitudeSystemDefinition/DistanceUnits: "Kilometers"

   VerticalCoordinateSystem/AltitudeSystemDefinition/Resolutions: "5"

SpatialCoverageType"HORIZONTAL_VERTICAL"

   HorizontalCoordinateSystem/GeodeticModel/HorizontalDatumName: "Easter Island 1967"

           HorizontalCoordinateSystem/GeodeticModel/EllipsoidName: "International 1924"

           HorizontalCoordinateSystem/GeodeticModel/SemiMajorAxis: "6378388"

           HorizontalCoordinateSystem/GeodeticModel/DenominatorOfFlatteningRatio: "297"

           HorizontalCoordinateSystem/GeographicCoordinateSystem/GeographicCoordinateUnits: "Decimal Degrees"

           HorizontalCoordinateSystem/GeographicCoordinateSystem/LatitudeResolution: "0.01"

   HorizontalCoordinateSystem/GeographicCoordinateSystem/LongitudeResolution: "0.01"

   VerticalCoordinateSystem/DepthSystemDefinition/DatumName: "Mean Sea Level"

   VerticalCoordinateSystem/DepthSystemDefinition/DistanceUnits: "Fathoms"

   VerticalCoordinateSystem/DepthSystemDefinition/Resolutions: "1"


Note: There are 2 Spatial Information fields that the CMR supports but are not currently included in the schema. These fields also do not currently map to or from any other metadata dialects. Support for these elements will be provided in the future. These fields are 'Latitude Resolution' and 'Longitude Resolution'.

  • SpatialInformation/LatitudeResolution: A free text field used to describe the latitude resolution of the data. Units should be included. This field can be used to describe the resolution of projected data, unlike the 'GeographicCoordianteSystem/LatitudeResolution' field which just supports geodetic coordinate systems.
  • SpatialInformation/LongitudeResolution: A free text field used to describe the longitude resolution of the data. Units should be included. This field can be used to describe the resolution of projected data, unlike the 'GeographicCoordianteSystem/LongitudeResolution' field which just supports geodetic coordinate systems.

    Examples:
    LatitudeResolution: 300 m
    LongitudeResolution: 300 m

    LatitudeResolution: 34 km
    LongitudeResolution: 30 km


Element Specification

Providing Spatial Information is optional (Cardinality: 0..1)

ModelElementTypeUsable Valid ValuesConstraintsRequired?CardinalityNotes
UMM-CSpatialInformation/SpatialCoverageTypeString

HORIZONTAL

VERTICAL

ORBITAL

HORIZONTAL_VERTICAL

ORBITAL_VERTICAL

1 - 80 characters

Yes, if applicable1


UMM-CSpatialInformation/VerticalCoordinateSystem/AltitudeSystemDefinition/DatumNameStringn/a

1 - 80 characters

No0..1Recommend providing EPSG vertical datum names
UMM-CSpatialInformation/VerticalCoordinateSystem/AltitudeSystemDefinition/DistanceUnitsEnumeration

HectoPascals

Kilometers

Millibars

n/a

No0..1
UMM-CSpatialInformation/VerticalCoordinateSystem/AltitudeSystemDefinition/ResolutionsNumbern/an/aNo0..*
UMM-CSpatialInformation/VerticalCoordinateSystem/DepthSystemDefinition/DatumNameStringn/a1 - 80 charactersNo0..1Recommend providing EPSG vertical datum names
UMM-CSpatialInformation/VerticalCoordinateSystem/DepthSystemDefinition/DistanceUnitsEnumeration

Fathoms

Feet

HectoPascals

Meters

Millibars

n/a


No0..1
UMM-CSpatialInformation/VerticalCoordinateSystem/DepthSystemDefinition/ResolutionsNumbern/an/aNo0..*
UMM-CSpatialInformation/HorizontalCoordinateSystem/GeodeticModel/HorizontalDatumNameStringn/a1 - 80 charactersNo0..1Recommend providing EPSG geodetic datum names
UMM-CSpatialInformation/HorizontalCoordinateSystem/GeodeticModel/EllipsoidNameStringn/a1 - 255 charactersNo0..1Recommend providing EPSG ellipsoid names
UMM-CSpatialInformation/HorizontalCoordinateSystem/GeodeticModel/SemiMajorAxisNumbern/an/aNo0..1
UMM-CSpatialInformation/HorizontalCoordinateSystem/GeodeticModel/DenominatorOfFlatteningRatioNumbern/an/aNo0..1
UMM-CSpatialInformation/HorizontalCoordinateSystem/GeographicCoordinateSystem/GeographicCoordinateUnitsEnumeration

Decimal Degrees

Kilometers

Meters

n/a

No0..1
UMM-CSpatialInformation/HorizontalCoordinateSystem/GeographicCoordinateSystem/LatitudeResolution

Number

n/an/aNo0..1
UMM-CSpatialInformation/HorizontalCoordinateSystem/GeographicCoordinateSystem/LongitudeResolutionNumbern/an/aNo0..1
UMM-CSpatialInformation/HorizontalCoordinateSystem/LocalCoordinateSystem/GeoReferenceInformationStringn/a1 - 2048 charactersNo0..1
UMM-CSpatialInformation/HorizontalCoordinateSystem/LocalCoordinateSystem/DescriptionStringn/a1 - 2048 charactersNo0..1



Metadata Validation and QA/QC

All metadata entering the CMR goes through the below process to ensure metadata quality requirements are met. All records undergo CMR validation before entering the system. The process of QA/QC is slightly different for NASA and non-NASA data providers. Non-NASA providers include interagency and international data providers and are referred to as the International Directory Network (IDN).

Lucidchart
rich-viewerfalse
autofittrue
nameCopy of Wiki Page Metadata Evaluation Workflow-1939-51df84
width1102
pages-to-display
id98e5dc28-3252-4209-953f-66f1378e1cf4
alignLeft
height299

Please see the expandable sections below for flowchart details.


Expand
titleGCMD Metadata QA/QC
  • Manual Review
  • Automated Review


Expand
titleCMR Validation

<>

Expand
titleARC Metadata QA/QC

ARC Priority Matrix

Priority CategorizationJustification

This element is categorized as highest priority when:

  • Spatial Information is provided but the required 'Spatial Information Type' field is not included.
  • An invalid value is provided for 'Distance Units'. 'DistanceUnits' must be selected from an enumeration list.
  • An invalid value is provided for 'GeographicCoordinateUnits'. 'GeographicCoordinateUnits' must be selected from an enumeration list.
  • The information provided is incorrect for the dataset.

Not applicable


This element is categorized as low priority when:

  • A recommendation is made to add the Horizontal Datum Name in the metadata.
  • A recommendation is made to provide any additional information to existing Spatial Information provided in the metadata.

The element is provided and follows all applicable criteria specified in the best practices section above.

ARC Automated Rules

  • If novalue is provided, return is "np."
  • Otherwise, return is "OK."
  • Rules for "Spatial Coverage Type" sub-element in DIF10:
    • If no value is provided the return is "np".
    • If a value is provided but it's not in the schema, then, the return is: "Invalid value for Spatial_Coverage_Type: [<Provided Value>]. Spatial_Coverage_Type should be chosen from the following options: (Values will be provided here)"
    • If a value is correct the return is "OK"

Dialect Mappings

Expand
titleDIF 9

DIF 9 (Note: DIF-9 is being phased out and will no longer be supported after 2018)

Expand
titleDIF 10

DIF 10

Providing Spatial_Info is optional in DIF 10 (Cardinality: 0..1).

Note: There are no Vertical Coordinate System fields in DIF 10 - vertical information can be provided in the Vertical_Spatial_Info element. For details on Vertical_Spatial_Info please see the Spatial Extent wiki page.

DIF 10 also supports an element called Data_Resolution which does not currently map to the UMM, however, there are plans to support it in the future.

UMM-C ElementDIF 10 PathTypeConstraintsRequired in DIF 10?CardinalityNotes
SpatialInformation/SpatialCoverageType
Spatial_Coverage/Spatial_Info/Spatial_Coverage_TypeEnumeration

Horizontal

HorizontalVertical

Orbit

Vertical

Horizon&amp;Vert

Yes, if applicable1
SpatialInformation/HorizontalCoordinateSystem/GeodeticModel/HorizontalDatumName
Spatial_Coverage/Spatial_Info/Horizontal_Coordinate_System/Geodetic_Model/Horizontal_DatumNameString
No0..1Recommend providing EPSG geodetic datum names
SpatialInformation/HorizontalCoordinateSystem/GeodeticModel/EllipsoidName
Spatial_Coverage/Spatial_Info/Horizontal_Coordinate_System/Geodetic_Model/Ellipsoid_NameString
No0..1Recommend providing EPSG ellipsoid names
SpatialInformation/HorizontalCoordinateSystem/GeodeticModel/SemiMajorAxis
Spatial_Coverage/Spatial_Info/Horizontal_Coordinate_System/Geodetic_Model/Semi_Major_AxisDecimal
No0..1
SpatialInformation/HorizontalCoordinateSystem/GeodeticModel/DenominatorOfFlatteningRatio
Spatial_Coverage/Spatial_Info/Horizontal_Coordinate_System/Geodetic_Model/Denominator_Of_Flattening_RatioDecimal
No0..1
SpatialInformation/HorizontalCoordinateSystem/GeographicCoordinateSystem/GeographicCoordinateUnits
Spatial_Coverage/Spatial_Info/Horizontal_Coordinate_System/Geographic_Coordinate_System/GeographicCoordinateUnitsString
No0..1
SpatialInformation/HorizontalCoordinateSystem/GeographicCoordinateSystem/LatitudeResolution
Spatial_Coverage/Spatial_Info/Horizontal_Coordinate_System/Geographic_Coordinate_System/LatitudeResolutionDecimal
No0..1
SpatialInformation/HorizontalCoordinateSystem/GeographicCoordinateSystem/LongitudeResolution
Spatial_Coverage/Spatial_Info/Horizontal_Coordinate_System/Geographic_Coordinate_System/LongitudeResolutionDecimal
No0..1
SpatialInformation/HorizontalCoordinateSystem/LocalCoordinateSystem/GeoReferenceInformation
Spatial_Coverage/Spatial_Info/Horizontal_Coordinate_System/Local_Coordinate_System/GeoReference_InformationString
No0..1
SpatialInformation/HorizontalCoordinateSystem/LocalCoordinateSystem/Description
Spatial_Coverage/Spatial_Info/Horizontal_Coordinate_System/Local_Coordinate_System/DescriptionString
No0..1
Will be supported in the futureData_Resolution/Latitude_ResolutionString
No0..1
Will be supported in the future
Data_Resolution/Longitude_Resolution

String


No0..1


n/aData_Resolution/Horizontal_Resolution_RangeStringKMS controlledNo0..1Recommend selecting a value from the GCMD Horizontal Data Resolution keywords to populate this field.
n/aData_Resolution/Vertical_ResolutionString


No0..1
n/aData_Resolution/ Vertical_Resolution_UnitString
No0..1
n/aData_Resolution/Vertical_Resolution_RangeStringKMS controlledNo0..1Recommend selecting a value from the GCMD Vertical Data Resolution keywords to populate this field
n/aData_Resolution/Temporal_ResolutionString
No0..1Note: this field does not map to any other metadata elements and is unique to DIF 10.
n/aData_Resolution/Temporal_Resolution_Range StringKMS controlledNo0..1

Recommend selecting a value from the GCMD Vertical Data Resolution keywords to populate this field

Note: this field does not map to any other metadata elements and is unique to DIF 10.


Enumeration Mapping

DIF 10Translation DirectionUMM

Horizontal

HORIZONTAL

HorizontalVerticalHORIZONTAL_VERTICAL
OrbitORBITAL
VerticalVERTICAL
Horizon&amp;Vert

ORBITAL_VERTICAL


Example Mapping

Section
Column
width50%

DIF 10

No Format
<Spatial_Coverage> 
  <Spatial_Info>
    <Spatial_Coverage_Type>Horizontal</Spatial_Coverage_Type>
    <Horizontal_Coordinate_System>
      <Geodetic_Model>
		<Horizontal_DatumName>North American Datum 1983</Horizontal_DatumName>
        <Ellipsoid_Name>GRS 1980</Ellipsoid_Name>
        <Semi_Major_Axis>6378137</Semi_Major_Axis>
        <Denominator_Of_Flattening_Ratio>298.257222101</Denominator_Of_Flattening_Ratio>
      </Geodetic_Model>
      <Geographic_Coordinate_System>
		<GeographicCoordinateUnits>Decimal Degrees</GeographicCoordinateUnits>
		<LatitudeResolution>0.5</LatitudeResolution>
		<LongitudeResolution>0.5</LongitudeResolution>
      </Geographic_Coordinate_System>
    </Horizontal_Coordinate_System>	
  </Spatial_Info>
</Spatial_Coverage>
----------------------------------------------------------------------------------------------------------------------------
<Data_Resolution>
  <Latitude_Resolution>50 km</Latitude_Resolution>
  <Longitude_Resolution>50 km</Longitude_Resolution>
  <Horizontal_Resolution_Range>50 km - < 100 km or approximately .5 degree - < 1 degree</Horizontal_Resolution_Range>
  <Temporal_Resolution>Hourly - < Daily</Temporal_Resolution>
</Data_Resolution>
Column
width50%

UMM

No Format
"SpatialInformation": [
  {
    "SpatialCoverageType": "HORIZONTAL",
    "HorizontalCoordinateSystem": {
      "GeodeticDatum": [
        {
          "HorizontalDatumName": "North American Datum 1983",
          "EllipsoidName": "GRS 1980", 
          "SemiMajorAxis": "6378137",
          "DenominatorOfFlatteningRatio": "298.257222101"
        }
      ],
      "GeographicCoordinateSystem": [
        {
          "GeographicCoordinateUnits": "DecimalDegrees",
          "LatitudeResolution": "0.5",
          "LongitudeResolution": "0.5"
        }
      ]
    }
  }
]	



Expand
titleECHO 10

ECHO 10

Providing the Spatial Info element is optional in ECHO 10 (Cardinality: 0..1)

UMM-C ElementECHO 10 PathTypeConstraintsRequired in ECHO10?CardinalityNote
SpatialInformation/SpatialCoverageTypeSpatialInfo/SpatialCoverageTypeString

1 - 80 characters

Yes, if applicable1

This attribute denotes whether the collection's spatial coverage requires horizontal, vertical, or both in the spatial domain and coordinate system definitions. This field is not controlled in ECHO 10, however, it is recommended that one of the UMM SpatialCoverageType enumeration values be provided in order to reduce translation errors (HORIZONTAL, VERTICAL, ORBITAL, HORIZONTAL_VERTICAL, ORBITAL_VERTICAL)

SpatialInformation/VerticalCoordinateSystem/AltitudeSystemDefinition/DatumName
SpatialInfo/VerticalCoordinateSystem/AltitudeSystemDefinition/DatumNameString

1 - 80 characters

No0..1Recommend providing EPSG vertical datum names
SpatialInformation/VerticalCoordinateSystem/AltitudeSystemDefinition/DistanceUnits
SpatialInfo/VerticalCoordinateSystem/AltitudeSystemDefinition/DistanceUnitsString

1 - 80 characters

No0..1
SpatialInformation/VerticalCoordinateSystem/AltitudeSystemDefinition/EncodingMethod
SpatialInfo/VerticalCoordinateSystem/AltitudeSystemDefinition/EncodingMethodString

1 - 2048 characters

No0..1

The means used to encode measurements.

SpatialInformation/VerticalCoordinateSystem/AltitudeSystemDefinition/Resolutions
SpatialInfo/VerticalCoordinateSystem/AltitudeSystemDefinition/Resolutions/ResolutionDecimaln/aNo0..*

This entity stores the minimum distance possible between two adjacent values, expressed in the distance units of measure for collection.

A list of vertical resolutions may be provided here.
SpatialInformation/VerticalCoordinateSystem/DepthSystemDefinition/DatumName
SpatialInfo/VerticalCoordinateSystem/DepthSystemDefinition/DatumNameString

1 - 80 characters

No0..1Recommend providing EPSG vertical datum names
SpatialInformation/VerticalCoordinateSystem/DepthSystemDefinition/DistanceUnits
SpatialInfo/VerticalCoordinateSystem/DepthSystemDefinition/DistanceUnitsString

1 - 80 characters

No0..1
SpatialInformation/VerticalCoordinateSystem/DepthSystemDefinition/EncodingMethod
SpatialInfo/VerticalCoordinateSystem/DepthSystemDefinition/EncodingMethodString

1 - 2048 characters

No0..1The means used to encode measurements.
SpatialInformation/VerticalCoordinateSystem/DepthSystemDefinition/Resolutions
SpatialInfo/VerticalCoordinateSystem/DepthSystemDefinition/Resolutions/ResolutionDecimaln/aNo0..*

This entity stores the minimum distance possible between two adjacent values, expressed in the distance units of measure for collection.

A list of vertical resolutions may be provided here.
SpatialInformation/HorizontalCoordinateSystem/GeodeticModel/HorizontalDatumName
SpatialInfo/HorizontalCoordinateSystem/GeodeticModel/HorizontalDatumNameString

1 - 80 characters

No0..1Recommend providing EPSG geodetic datum names
SpatialInformation/HorizontalCoordinateSystem/GeodeticModel/EllipsoidName
SpatialInfo/HorizontalCoordinateSystem/GeodeticModel/EllipsoidNameString

1 - 255 characters

No0..1Recommend providing EPSG ellipsoid names
SpatialInformation/HorizontalCoordinateSystem/GeodeticModel/SemiMajorAxis
SpatialInfo/HorizontalCoordinateSystem/GeodeticModel/SemiMajorAxisDecimaln/aNo0..1
SpatialInformation/HorizontalCoordinateSystem/GeodeticModel/DenominatorOfFlatteningRatio
SpatialInfo/HorizontalCoordinateSystem/GeodeticModel/DenominatorOfFlatteningRatioDecimaln/aNo0..1
SpatialInformation/HorizontalCoordinateSystem/GeographicCoordinateSystem/GeographicCoordinateUnits
SpatialInfo/HorizontalCoordinateSystem/GeographicCoordinateSystem/GeographicCoordinateUnitsString

1 - 80 characters

No0..1

Units of measure used for the geodetic latitude and longitude resolution values. E.g. Decimal Degrees or Degrees Minutes Seconds.

SpatialInformation/HorizontalCoordinateSystem/GeographicCoordinateSystem/LatitudeResolution
SpatialInfo/HorizontalCoordinateSystem/GeographicCoordinateSystem/LatitudeResolutionDecimaln/aNo0..1

For lat, a 2 digit decimal number from 0-90

+ or absence of - for values north of equator; - for all others.

SpatialInformation/HorizontalCoordinateSystem/GeographicCoordinateSystem/LongitudeResolution
SpatialInfo/HorizontalCoordinateSystem/GeographicCoordinateSystem/LongitudeResolutionDecimaln/aNo0..1

For lon, a 3 digit decimal number from 0-180

+ or absence of - for values west of prime meridian; - for all others.

SpatialInformation/HorizontalCoordinateSystem/LocalCoordinateSystem/Description
SpatialInfo/HorizontalCoordinateSystem/LocalCoordinateSystem/DescriptionString

1 - 2048 characters

No0..1
SpatialInformation/HorizontalCoordinateSystem/LocalCoordinateSystem/GeoReferenceInformation
SpatialInfo/HorizontalCoordinateSystem/LocalCoordinateSystem/GeoReferenceInformationString

1 - 2048 characters

No0..1


Example Mapping

Section
Column
width50%

ECHO 10

No Format
<SpatialInfo>
  <SpatialCoverageType>HORIZONTAL_VERTICAL</SpatialCoverageType>
  <HorizontalCoordinateSystem>
    <GeodeticModel>
      <HorizontalDatumName>North American Datum 1983</HorizontalDatumName> 
      <EllipsoidName>GRS 1980</EllipsoidName>
      <SemiMajorAxis>6378137</SemiMajorAxis>
      <DenominatorOfFlatteningRatio>298.257222101</DenominatorOfFlatteningRatio>
    </GeodeticModel>
    <GeographicCoordinateSystem>
      <GeographicCoordinateUnits>Decimal Degrees</GeographicCoordinateUnits>
      <LatitudeResolution>0.5</LatitudeResolution>
      <LongitudeResolution>0.5</LongitudeResolution>
    </GeographicCoordinateSystem>
  </HorizontalCoordinateSystem>
  <VerticalCoordinateSystem> 
    <AltitudeSystemDefinition> 
      <DatumName>North American Vertical Datum 1988</DatumName>
      <DistanceUnits>Kilometers</DistanceUnits>
      <Resolutions>
	    <Resolution>10</Resolution>
      </Resolutions>
    </AltitudeSystemDefinition>
  </VerticalCoordinateSystem>
</SpatialInfo>
Column
width50%

UMM

No Format
"SpatialInformation": {
  "SpatialCoverageType": "HORIZONTAL_VERTICAL",
  "HorizontalCoordinateSystem": {
    "GeodeticDatum": [
      {
        "HorizontalDatumName": "North American Datum 1983",
        "EllipsoidName": "GRS 1980", 
        "SemiMajorAxis": "6378137",
        "DenominatorOfFlatteningRatio": "298.257222101"
      }
    ],
    "GeographicCoordinateSystem": [
      {
        "GeographicCoordinateUnits": "DecimalDegrees",
        "LatitudeResolution": "0.5",
        "LongitudeResolution": "0.5"
      }
    ],
  "VerticalCoordinateSystem": {
    "AltitudeSystemDefinition": [
      {
        "DatumName": "North American Vertical Datum 1988",
        "DistanceUnits": "Kilometers",
        "Resolutions": "10"
      }
    ]
  }
}
Expand
titleISO 19115-2 MENDS

ISO 19115-2 MENDS

SpecificationPathTypeNotes
ISO 19115-2 MENDSN/AN/AN/A


Example Mapping

Section
Column
width50%

ISO 19115-2 MENDS

No Format
N/A

Column
width50%

UMM

No Format
"SpatialInformation": {
  "SpatialCoverageType": "HORIZONTAL_VERTICAL",
  "HorizontalCoordinateSystem": {
    "GeodeticDatum": [
      {
        "HorizontalDatumName": "North American Datum 1983",
        "EllipsoidName": "GRS 1980", 
        "SemiMajorAxis": "6378137",
        "DenominatorOfFlatteningRatio": "298.257222101"
      }
    ],
    "GeographicCoordinateSystem": [
      {
        "GeographicCoordinateUnits": "DecimalDegrees",
        "LatitudeResolution": "0.5",
        "LongitudeResolution": "0.5"
      }
    ],
  "VerticalCoordinateSystem": {

    "AltitudeSystemDefinition": [
      {
        "DatumName": "North American Vertical Datum 1988",
        "DistanceUnits": "Kilometers",
        "Resolutions": "10"
      }
    ]
  }
}
Expand
titleISO 19115-2 SMAP

ISO 19115-2 SMAP

SpecificationPathTypeNotes
ISO 19115-2 SMAPN/AN/AN/A


Example Mapping

Section
Column
width50%

ISO 19115-2 SMAP

No Format
N/A
Column
width50%

UMM

No Format
"SpatialInformation": {
  "SpatialCoverageType": "HORIZONTAL_VERTICAL",
  "HorizontalCoordinateSystem": {
    "GeodeticDatum": [
      {
        "HorizontalDatumName": "North American Datum 1983",
        "EllipsoidName": "GRS 1980", 
        "SemiMajorAxis": "6378137",
        "DenominatorOfFlatteningRatio": "298.257222101"
      }
    ],
    "GeographicCoordinateSystem": [
      {
        "GeographicCoordinateUnits": "DecimalDegrees",
        "LatitudeResolution": "0.5",
        "LongitudeResolution": "0.5"
      }
    ],
  "VerticalCoordinateSystem": {

    "AltitudeSystemDefinition": [
      {
        "DatumName": "North American Vertical Datum 1988",
        "DistanceUnits": "Kilometers",
        "Resolutions": "10"
      }
    ]
  }
}

UMM Migration

UMM Version 1.9.0Translation DirectionUMM Version 1.10.0



Future Mappings

Expand
titleISO 19115-1

ISO 19115-1

SpecificationPathTypeNotes
ISO 19115-1N/AN/AN/A


Example Mapping

Section
Column
width50%

ISO 19115-1

No Format
N/A
Column
width50%

UMM

No Format
"SpatialInformation": {
  "SpatialCoverageType": "HORIZONTAL_VERTICAL",
  "HorizontalCoordinateSystem": {
    "GeodeticDatum": [
      {
        "HorizontalDatumName": "North American Datum 1983",
        "EllipsoidName": "GRS 1980", 
        "SemiMajorAxis": "6378137",
        "DenominatorOfFlatteningRatio": "298.257222101"
      }
    ],
    "GeographicCoordinateSystem": [
      {
        "GeographicCoordinateUnits": "DecimalDegrees",
        "LatitudeResolution": "0.5",
        "LongitudeResolution": "0.5"
      }
    ],
  "VerticalCoordinateSystem": {

    "AltitudeSystemDefinition": [
      {
        "DatumName": "North American Vertical Datum 1988",
        "DistanceUnits": "Kilometers",
        "Resolutions": "10"
      }
    ]
  }
}

History

UMM Versioning

VersionDateWhat Changed
1.12.001/22/2019No changes were made for Spatial Representation Information during the transition from version 1.11.0 to 1.12.0.
1.11.011/28/2018No changes were made for Spatial Representation Information during the transition from version 1.10.0 to 1.11.0.
1.10.005/02/2018

During the transition from version 1.9.0 to 1.10.0:

  • The sub element 'GeographicCoordinateUnits' was added and enumerated
  • The sub element 'EncodingMethod' was removed from both 'AltitudeSystemDefinitionType' and 'DepthSystemDefinitionType'
  • 'VerticalSystemDefinitionType' was replaced with both 'AltitudeSystemDefinitionType' and 'DepthSystemDefinitionType'
  • Free text strings were changed to enumeration for the following sub elements within 'AltitudeSystemDefinitionType' and 'DepthSystemDefinitionType': 'AltitudeDistanceUnitsEnum' and 'DepthSystemDefinitionType.'
1.9.0

ARC Documentation

VersionDateWhat ChangedAuthor
1.002/15/19Recommendations/priority matrix transferred from internal ARC documentation to wiki space