Page History

Table of Contents

Element Description

Note: this wiki page is a draft/ work in progress

The Spatial Information element stores information about the reference frame or system from which horizontal and vertical spatial domains are measured. The horizontal reference frame includes a 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.

If coordinate system information is provided, then the The Spatial Coverage Type field is required . This field is used to specify whether the for Spatial Information.

Spatial Coverage Type: Denotes the type of spatial coverage of the collection is horizontal, vertical, horizontal and vertical, orbital, or orbital and vertical.

Spatial Coverage Type: Denotes the type of spatial coverage of the collection. While this field is not currently controlled, recommend

. While this field is not currently controlled, recommend providing one of the spatial coverage type enumeration values:

HORIZONTAL

EARTH/GLOBAL, HORIZONTAL, VERTICAL, ORBITAL, HORIZONTAL_VERTICAL, ORBITAL_VERTICAL

, HORIZONTAL_ORBITAL, HORIZONTAL_VERTICAL_ORBITAL, LUNAR

Vertical Horizontal Spatial Information

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

There are 3 2 categories for Horizontal Vertical Coordinate Systems including:

(1) Geodetic ModelAltitude System Definition

Altitude System Definition should be 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"

Element Specification

Providing Spatial Information is optional. Spatial Information can only be provided once (Cardinality: 0..1)

ModelElementTypeConstraintsRequired?CardinalityNotesUMM-CSpatialInformation/SpatialCoverageTypeString

1 - 80 characters

Yes, if applicable1

Highly recommend providing one of the following enumeration values:

HORIZONTAL

VERTICAL

ORBITAL

HORIZONTAL_VERTICAL

ORBITAL_VERTICAL

UMM-CSpatialInformation/VerticalCoordinateSystem/AltitudeSystemDefinition/DatumNameString

1 - 80 characters

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

HectoPascals

Kilometers

Millibars

No0..1UMM-CSpatialInformation/VerticalCoordinateSystem/AltitudeSystemDefinition/ResolutionsNumbern/aNo0..*UMM-CSpatialInformation/VerticalCoordinateSystem/DepthSystemDefinition/DatumNameString1 - 80 charactersNo0..1Recommend providing EPSG vertical datum namesUMM-CSpatialInformation/VerticalCoordinateSystem/DepthSystemDefinition/DistanceUnitsEnumeration

Fathoms

Feet

HectoPascals

Meters

Millibars

No0..1UMM-CSpatialInformation/VerticalCoordinateSystem/DepthSystemDefinition/ResolutionsNumbern/aNo0..*UMM-CSpatialInformation/HorizontalCoordinateSystem/GeodeticModel/HorizontalDatumNameString1 - 80 charactersNo0..1Recommend providing EPSG geodetic datum namesUMM-CSpatialInformation/HorizontalCoordinateSystem/GeodeticModel/EllipsoidNameString1 - 255 charactersNo0..1Recommend providing EPSG ellipsoid namesUMM-CSpatialInformation/HorizontalCoordinateSystem/GeodeticModel/SemiMajorAxisNumbern/aNo0..1UMM-CSpatialInformation/HorizontalCoordinateSystem/GeodeticModel/DenominatorOfFlatteningRatioNumbern/aNo0..1UMM-CSpatialInformation/HorizontalCoordinateSystem/GeographicCoordinateSystem/GeographicCoordinateUnitsEnumeration

Decimal Degrees

Kilometers

Meters

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

Number

n/aNo0..1UMM-CSpatialInformation/HorizontalCoordinateSystem/GeographicCoordinateSystem/LongitudeResolutionNumbern/aNo0..1UMM-CSpatialInformation/HorizontalCoordinateSystem/LocalCoordinateSystem/GeoReferenceInformationString1 - 2048 charactersNo0..1UMM-CSpatialInformation/HorizontalCoordinateSystem/LocalCoordinateSystem/DescriptionString1 - 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).

Lucidchartrich-viewerfalseautofittruenameCopy of Wiki Page Metadata Evaluation Workflow-1939-51df84width1102pages-to-displayid98e5dc28-3252-4209-953f-66f1378e1cf4alignLeftheight299

Please see the expandable sections below for flowchart details.

Expand

title	GCMD Metadata QA/QC

Manual Review

Automated Review

Expand

title	CMR Validation

<>

Expand

title	ARC Metadata QA/QC

ARC Priority Matrix

Priority CategorizationJustification

This element is categorized as highest priority when:

The information provided is not related to the element.
The descriptions are inaccurate for the data set.

Not applicable

This element is categorized as low priority when:

The descriptions includes spelling or grammatical errors.

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

title	DIF 9

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

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.

Element Specification

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


Model	Element	Type	Usable Valid Values	Constraints	Required?	Cardinality	Notes
UMM-C	SpatialInformation/SpatialCoverageType	String	EARTH/GLOBAL, HORIZONTAL, VERTICAL, ORBITAL, HORIZONTAL_VERTICAL, ORBITAL_VERTICAL, HORIZONTAL_ORBITAL, HORIZONTAL_VERTICAL_ORBITAL, LUNAR	1 - 80 characters	Yes, if applicable	1
UMM-C	SpatialInformation/VerticalCoordinateSystem/AltitudeSystemDefinition/DatumName	String	n/a	1 - 80 characters	No	0..1	Recommend providing EPSG vertical datum names
UMM-C	SpatialInformation/VerticalCoordinateSystem/AltitudeSystemDefinition/DistanceUnits	Enumeration	HectoPascals Kilometers Millibars	n/a	No	0..1
UMM-C	SpatialInformation/VerticalCoordinateSystem/AltitudeSystemDefinition/Resolutions	Number	n/a	n/a	No	0..*
UMM-C	SpatialInformation/VerticalCoordinateSystem/DepthSystemDefinition/DatumName	String	n/a	1 - 80 characters	No	0..1	Recommend providing EPSG vertical datum names
UMM-C	SpatialInformation/VerticalCoordinateSystem/DepthSystemDefinition/DistanceUnits	Enumeration	Fathoms Feet HectoPascals Meters Millibars	n/a	No	0..1
UMM-C	SpatialInformation/VerticalCoordinateSystem/DepthSystemDefinition/Resolutions	Number	n/a	n/a	No	0..*

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-viewer	false

autofit	true
name	Copy of Wiki Page Metadata Evaluation Workflow-1939-51df84
width	1102
pages-to-display
id	98e5dc28-3252-4209-953f-66f1378e1cf4
align	Left
height	299

Please see the expandable sections below for flowchart details.

Expand

title	GCMD Metadata QA/QC

Manual Review
- Identify errors, discrepancies or omissions.
- Proof all content for conciseness and readability.

Expand

title	CMR Validation

None

Expand

title	ARC Metadata QA/QC

ARC Priority Matrix

Priority Categorization	Justification
Red = High Priority Finding	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.
Yellow = Medium Priority Finding	Not Applicable
Blue = Low Priority Finding	This element is categorized as low priority when: A recommendation is made to provide any additional information to existing Spatial Information provided in the metadata.
Green = No Findings/Issues	The element is provided and follows all applicable criteria specified in the best practices section above.

ARC Automated Checks

ARC uses the pyQuARC library for automated metadata checks. Please see the pyQuARC GitHub for more information.

Dialect Mappings

Example Mapping

Expand

title	DIF 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 Element	DIF 10 Path	Type	Constraints	Required in DIF 10?	Cardinality	Notes
SpatialInformation/SpatialCoverageType	Spatial_Coverage/Spatial_Info/Spatial_Coverage_Type	Enumeration	Earth/Global, Horizontal, Vertical, Orbit, HorizontalVertical, Orbital_Vertical, Horizontal_Orbital, Horizontal_Vertical_Orbital, Lunar	Yes, if applicable	1	Horizon&Vert has been deprecated, use HorizontalVertical instead
n/a	Data_Resolution/Vertical_Resolution	String		No	0..1
n/a	Data_Resolution/ Vertical_Resolution_Unit	String		No	0..1
n/a	Data_Resolution/Vertical_Resolution_Range	String	KMS controlled	No	0..1	Recommend selecting a value from the GCMD Vertical Data Resolution keywords to populate this field
n/a	Data_Resolution/Temporal_Resolution	String		No	0..1	Note: this field does not map to any other metadata elements and is unique to DIF 10.
n/a	Data_Resolution/Temporal_Resolution_Range	String	KMS controlled	No	0..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 10	Translation Direction	UMM
Earth/Global	↔	EARTH/GLOBAL
Horizontal	↔	HORIZONTAL
HorizontalVertical	↔	HORIZONTAL_VERTICAL
Orbit	↔	ORBITAL
Vertical	↔	VERTICAL
Horizon&Vert	→	HORIZONTAL_VERTICAL
Orbital_Vertical	↔	ORBITAL_VERTICAL
Horizontal_Orbital	↔	HORIZONTAL_ORBITAL
Horizontal_Vertical_Orbital	↔	HORIZONTAL_VERTICAL_ORBITAL
Lunar	↔	LUNAR

Example Mapping

Section

Column

width	50%

DIF 10

No Format
<Spatial_Coverage> <Spatial_Info> <Spatial_Coverage_Type>Horizontal</Spatial_Coverage_Type> </Spatial_Info> </Spatial_Coverage> ------------------------------------------------------------

Expand

title	DIF 10

DIF 10

Providing the Spatial_Coverage element is optional in DIF 10 (Cardinality: 0..1). DIF 10 also supports an element called Data_Resolution which cross-walks to Spatial Representation information when being converted from DIF 10 to the UMM. Providing the Data_Resolution element is optional (Cardinality: 0..*).

Specification

Path

Type

Constraints

Required in DIF 10?

Cardinality

Notes

DIF 10

Spatial_Coverage/Spatial_Info/Spatial_Coverage_Type

Enumeration

Yes

1

DIF 10

Spatial_Coverage/Spatial_Info/Horizontal_Coordinate_System/Geodetic_Model/Horizontal_DatumName

String

No

0..1

DIF 10

Spatial_Coverage/Spatial_Info/Horizontal_Coordinate_System/Geodetic_Model/Ellipsoid_Name

String

No

0..1

DIF 10

Spatial_Coverage/Spatial_Info/Horizontal_Coordinate_System/Geodetic_Model/Semi_Major_Axis

Decimal

No

0..1

DIF 10

Spatial_Coverage/Spatial_Info/Horizontal_Coordinate_System/Geodetic_Model/Denominator_Of_Flattening_Ratio

Decimal

No

0..1

DIF 10

Spatial_Coverage/Spatial_Info/Horizontal_Coordinate_System/Geographic_Coordinate_System/GeographicCoordinateUnits

String

No

0..1

DIF 10

Spatial_Coverage/Spatial_Info/Horizontal_Coordinate_System/Geographic_Coordinate_System/LatitudeResolution

Decimal

No

0..1

DIF 10

Spatial_Coverage/Spatial_Info/Horizontal_Coordinate_System/Geographic_Coordinate_System/LongitudeResolution

Decimal

No

0..1

DIF 10

Spatial_Coverage/Spatial_Info/Horizontal_Coordinate_System/Local_Coordinate_System/GeoReference_Information

String

No

0..1

DIF 10

Spatial_Coverage/Spatial_Info/Horizontal_Coordinate_System/Local_Coordinate_System/Description

String

No

0..1

DIF 10

Data_Resolution/Latitude_Resolution

String

No

0..1

DIF 10

Data_Resolution/Longitude_Resolution

String

No

0..1

DIF 10

Data_Resolution/Horizontal_Resolution_Range

String

No

0..1

DIF 10

Data_Resolution/Vertical_Resolution

String

No

0..1

DIF 10

Data_Resolution/ Vertical_Resolution_Unit

String

No

0..1

DIF 10

Data_Resolution/Vertical_Resolution_Range

String

No

0..1

DIF 10

Data_Resolution/ Temporal_Resolution

String

No

0..1

DIF 10

Data_Resolution/ Temporal_Resolution_Range

String

No

0..1

Section

Column

width	50%

DIF 10

No Format

<Spatial_Coverage> 
	<Spatial_Info>
		<Spatial_Coverage_Type></Spatial_Coverage_Type>
		<Horizontal_Coordinate_System>
			<Geodetic_Model>
				<Horizontal_DatumName></Horizontal_DatumName>
				<Ellipsoid_Name></Ellipsoid_Name>
				<Semi_Major_Axis></Semi_Major_Axis>
				<Denominator_Of_Flattening_Ratio></Denominator_Of_Flattening_Ratio>
			</Geodetic_Model>
			<Geographic_Coordinate_System>
				<GeographicCoordinateUnits></GeographicCoordinateUnits>
				<LatitudeResolution></LatitudeResolution>
				<LongitudeResolution></LongitudeResolution>
        	</Geographic_Coordinate_System>
			<Local_Coordiante_System>
				<Description></Description>
				<GeoReferenceInformation></GeoReferenceInformation>
			</Local_Coordiante_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> Twice per day; day and night; Orbital repeat cycle 16 days <---------------
<Data_Resolution>
  <Temporal_Resolution>Hourly - < Daily</Temporal_Resolution>
</Data_Resolution>

Column

width	50%

UMM

No Format
ADD EXAMPLE "SpatialInformation": [ { "SpatialCoverageType": "HORIZONTAL", } ]

Expand

title	ECHO 10

ECHO 10

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

UMM-C Element	ECHO 10

Specification

Path	Type	Constraints	Required in ECHO10?	Cardinality	Note

ECHO 101ECHO 10SpatialInfo/VerticalCoordinateSystem/AltitudeSystemDefinition/DatumNameString

1 - 80 characters

No0..1ECHO 10SpatialInfo/VerticalCoordinateSystem/AltitudeSystemDefinition/DistanceUnitsString

1 - 80 characters

No0..1ECHO 10

SpatialInformation/SpatialCoverageType

SpatialInfo/SpatialCoverageType

String

1 - 80 characters

Yes

, if applicable	1	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/

EncodingMethod

DatumName

String

1 - 80 characters

No

0..1

ECHO 10SpatialInfo

Recommend providing EPSG vertical datum names

SpatialInformation/VerticalCoordinateSystem/AltitudeSystemDefinition/

Resolutions/ResolutionDecimalNo0..*ECHO 10

DistanceUnits

SpatialInfo/VerticalCoordinateSystem/

DepthSystemDefinition

AltitudeSystemDefinition/

DatumName

DistanceUnits

String

1 - 80 characters

No

0..1

ECHO 10


SpatialInformation/VerticalCoordinateSystem/AltitudeSystemDefinition/EncodingMethod	SpatialInfo/VerticalCoordinateSystem/

DepthSystemDefinition

AltitudeSystemDefinition/

DistanceUnits

EncodingMethod

String

1 -

80

2048 characters

No

0

..1ECHO 10

..1	The means used to encode measurements.
SpatialInformation/VerticalCoordinateSystem/AltitudeSystemDefinition/Resolutions	SpatialInfo/VerticalCoordinateSystem/AltitudeSystemDefinition/

DepthSystemDefinition

Resolutions/

EncodingMethod

Resolution

String1 - 2048 characters

Decimal

n/a

No

0..

.1

*	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

ECHO 10SpatialInfo

/VerticalCoordinateSystem/DepthSystemDefinition/

Resolutions/ResolutionDecimalNo0..*ECHO 10

DatumName

SpatialInfo/

HorizontalCoordinateSystem

VerticalCoordinateSystem/

GeodeticModel

DepthSystemDefinition/

HorizontalDatumName

DatumName

String

1 - 80 characters

No

0..1

ECHO 10

	Recommend providing EPSG vertical datum names
SpatialInformation/VerticalCoordinateSystem/DepthSystemDefinition/DistanceUnits	SpatialInfo/

HorizontalCoordinateSystem

VerticalCoordinateSystem/

GeodeticModel

DepthSystemDefinition/

EllipsoidName

DistanceUnits

String

1 -

255

80 characters

No

0..1

ECHO 10


SpatialInformation/VerticalCoordinateSystem/DepthSystemDefinition/EncodingMethod	SpatialInfo/

HorizontalCoordinateSystem

VerticalCoordinateSystem/

GeodeticModel

DepthSystemDefinition/

SemiMajorAxis

EncodingMethod

String

1 - 2048 characters

Decimal

No

0..1

ECHO 10

The means used to encode measurements.
SpatialInformation/VerticalCoordinateSystem/DepthSystemDefinition/Resolutions	SpatialInfo/VerticalCoordinateSystem/

HorizontalCoordinateSystem

DepthSystemDefinition/

GeodeticModel

Resolutions/

DenominatorOfFlatteningRatio

Resolution

Decimal

n/a

No

0..*

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

.1ECHO 10SpatialInfo/HorizontalCoordinateSystem/GeographicCoordinateSystem/GeographicCoordinateUnitsString

1 - 80 characters

No0..1ECHO 10SpatialInfo/HorizontalCoordinateSystem/GeographicCoordinateSystem/LatitudeResolutionDecimalNo0..1ECHO 10SpatialInfo/HorizontalCoordinateSystem/GeographicCoordinateSystem/LongitudeResolutionDecimalNo0..1ECHO 10SpatialInfo/HorizontalCoordinateSystem/LocalCoordinateSystem/DescriptionString

1 - 2048 characters

No0..1ECHO 10SpatialInfo/HorizontalCoordinateSystem/LocalCoordinateSystem/GeoReferenceInformationString

1 - 2048 characters

No0..1

Example Mapping

A list of vertical resolutions may be provided here.

Example Mapping

Section

Section

Column

width	50%

ECHO 10

No Format

<SpatialInfo>
  <SpatialCoverageType>HORIZONTAL_VERTICAL</SpatialCoverageType>
  <VerticalCoordinateSystem> 
    <AltitudeSystemDefinition> 
      <DatumName>North American Vertical Datum 1988</DatumName>
      <DistanceUnits>Kilometers</DistanceUnits>
      <Resolutions>
	    <Resolution>10</Resolution>
      </Resolutions>
    </AltitudeSystemDefinition>
  </VerticalCoordinateSystem>
</SpatialInfo>

Column

width	50%

ECHO 10UMM

No Format

<Spatial Info>
	<Spatial Coverage Type></Spatial Coverage Type>
	<Vertical Coordinate System> 
		<Altitude System Definition> 
			<Datum Name></Datum Name>
			<Distance Units></Distance Units>
			<Encoding Method></Encoding Method>
			<Resolutions>
				<Resolution></Resolution>
			</Resolutions>
		</Altitude System Definition> 
		<Depth System Definition>
			<Datum Name></Datum Name>
			<Distance Units></Distance Units>
			<Encoding Method></Encoding Method>
			<Resolutions>
				<Resolution></Resolution>
			</Resolutions>
		</Depth System Definition>
	</Vertical Coordinate System>

Column

width	50%

UMM

No Format
ADD EXAMPLE

Expand

title	ISO 19115-2 MENDS

ISO 19115-2 MENDS

SpecificationPathTypeNotesISO 19115-2 MENDSN/AN/AN/AExample Mapping

Section

Column

width	50%

ISO 19115-2 MENDS

No Format
N/A

Column

width	50%

UMM

No Format
N/A

Expand

title	ISO 19115-2 SMAP

ISO 19115-2 SMAP

SpecificationPathTypeNotesISO 19115-2 SMAPN/AN/AN/AExample Mapping

Section

Column

width	50%

ISO 19115-2 SMAP

No Format
N/A

Column

width	50%

UMM

No Format
N/A

UMM Migration

UMM Version 1.9.0Translation DirectionUMM Version 1.10.0

Future Mappings

Expand

title	ISO 19115-1

ISO 19115-1

SpecificationPathTypeNotesISO 19115-1N/AN/AN/AExample Mapping

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

UMM Migration

N/A

History

UMM Versioning

Version	Date	What Changed
1.18.0	2024-03-18	Updated Spatial Coverage Type enumeration list for 1.18.0
1.15.5	2020-12-03	No changes were made for Spatial Information during the transition from version 1.15.4 to 1.15.5
1.15.4	2020-09-18	No changes were made for Spatial Information during the transition from version 1.15.3 to 1.15.4
1.15.3	2020-07-01	No changes were made for Spatial Information during the transition from version 1.15.2 to 1.15.3
1.15.2	2020-05-20	No changes were made for Spatial Information during the transition from version 1.15.1 to 1.15.2
1.15.1	2020-03-25	No changes were made for Spatial Information during the transition from version 1.15.0 to 1.15.1
1.15.0	2020-02-26	No changes were made for Spatial Information during the transition from version 1.14.0 to 1.15.0
1.14.0	2019-10-21	The Horizontal Coordinate System element and all supporting elements were either removed or renamed and moved to the SpatialExtent element.
1.13.0	2019-04-11	No changes were made for Spatial Information during the transition from version 1.12.0 to 1.13.0
1.12.0	2019-01-22	No changes were made for Spatial

Section

Column

width	50%

ISO 19115-1

No Format
N/A

Column

width	50%

UMM

No Format
N/A

History

UMM Versioning

VersionDateWhat Changed1.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.0	2018-11

/

-28

/2018

No changes were made for Spatial

Representation

Information during the transition from version 1.10.0 to 1.11.0.
1.10.0	2018-05

/

-02

/2018

During the transition from version 1.9.0 to 1.10.0

, the

:

The sub element 'GeographicCoordinateUnits' was added and enumerated

, the

The sub element 'EncodingMethod' was removed from both 'AltitudeSystemDefinitionType' and 'DepthSystemDefinitionType'

, and

'VerticalSystemDefinitionType' was replaced with both 'AltitudeSystemDefinitionType' and 'DepthSystemDefinitionType

.

'
Free text strings were

also

changed to enumeration for the following sub elements within 'AltitudeSystemDefinitionType' and 'DepthSystemDefinitionType': 'AltitudeDistanceUnitsEnum' and 'DepthSystemDefinitionType.'

1.9.0

ARC Documentation

Version	Date	What Changed	Author
1.011/16/18	2019-02-15	Recommendations/priority matrix transferred from internal ARC documentation to wiki space	Jeanne' le Roux Ingrid Garcia-Solera

Page tree

Versions Compared

Old Version 38

New Version Current

Key

Element Description

Best Practices

Element Specification

Metadata Validation and QA/QC

Dialect Mappings

Element Specification

Metadata Validation and QA/QC

Dialect Mappings

DIF 10

ECHO 10

ISO 19115-2 MENDS

UMM Migration

Future Mappings

ISO 19115-1

UMM Migration

History

UMM Versioning

History

UMM Versioning

ARC Documentation