Page History

Table of Contents

style	circle

Element Description

The Spatial Extent element describes the geographic coverage of the data. For data collections, the spatial extent describes the area of the Earth that the collection covers. For specific files or granules, the spatial extent describes the area covered by that individual file.

The Spatial Extent element may also be used to describe vertical coverage of the data and orbital parameters where appropriate.

The Spatial Extent's coordinate system and resolution is also included under this main element. The horizontal spatial domain includes the geographic coverage of the data plus its coordinate system and the geographic coverage's resolution. This information provides the reference frame from which horizontal and vertical spatial domains are measured. The horizontal reference frame includes fields for Geodetic Model, Horizontal Data Resolution, and Local Coordinates. The geographic coverage's resolution is defined as the smallest horizontal distance between successive elements of data in a dataset. This is synonymous with terms such as ground sample distance, sample spacing and pixel size. It is to be noted that the horizontal data resolution could be different in the two horizontal dimensions. Also, it is different from the spatial resolution of an instrument, which is the minimum distance between points that an instrument can see as distinct.

Best Practices

In the CMR, there is the option to describe the horizontal, vertical, and orbital spatial coverage of a dataset along with its coordinate system and resolution. The type of spatial coverage being described in the metadata is identified via the 'Spatial Coverage Type' metadata element. There are five different controlled vocabulary options for 'Spatial Coverage Type'. These include:

Horizontal
Vertical
Orbital
Horizontal and Vertical
Orbital and Vertical

Each spatial extent type requires different information. The information needed for each type is summarized below:

Horizontal

Horizontal spatial extent refers to data covering the surface of the Earth. For horizontal spatial extent, a coordinate system must be specified with the choice of either a Cartesian or Geodetic coordinate system:

SpatialExtent/HorizontalSpatialDomain/Geometry/CoordinateSystem:

Choice of:

CARTESIAN
GEODETIC

Please see the Coordinate Systems section of the CMR Data Partner User Guide for instructions on how to assign the appropriate coordinate system.

Furthermore, there are four different options for describing horizontal spatial coverage. Only one of these options may be selected, however, the selected option may be repeated as many times as necessary (e.g. you can't provide a bounding rectangle and a point, but you can provide multiple bounding rectangles). The four options are:

(1) Point

- A point location defined by a latitude and longitude coordinate. Multiple points may be provided if necessary.

(2) Bounding Rectangle

- A rectangle defined by a north latitude coordinate, south latitude coordinate, east longitude coordinate, and west longitude coordinate. The north bounding latitude may not exceed 90 degrees, the south bounding coordinate may not be less than -90 degrees, the west bounding coordinate may not be less than -180 degrees, and the east bounding coordinate may not exceed 180 degrees.

(3) GPolygon

- A polygon defined by latitude/longitude point pairs. The more points are provided, the more detailed the polygon will be. Exclusion zones within the polygon can also be identified. Please see the CMR Data Partner User Guide for more details.

(4) Line

- A width-less line defined by latitude/longitude point pairs. Multiple points may be provided to express a complex line. Please see the CMR Data Partner User Guide for more details.

Horizontal Resolution and Coordinate System

The following sub-elements can be used to describe Horizontal Resolution and Coordinate System.

There are 3 categories for Horizontal Resolution and Coordinate System Data Resolution 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) Horizontal Data Resolution

Data that has been georeferenced to a geodetic datum can have resolution information. There are three basic types of spatial coverages: Point Data, Non Gridded Data, and Gridded Data. Depending on which type different set of data is useful to describe the data sets resolution. These are summarized below:

Varies Resolution: The data product's resolution information is varied and not described in the data set's metadata record. For more information the data set's landing pages should be visited.
Point Resolution: The data product's spatial extent is a point and therefore there is no resolution information to describe.
Non Gridded Resolutions: The data product's spatial extent is not gridded and the following set of sub elements apply:
- XDimension: The resolution value on an X axis on a plane - On the Earth this is normally the Longitudinal axis.
- YDimension: The resolution value on a Y axis on a plane - On the Earth this is normally the Latitudinal axis.
- Unit: The unit of measure for the X and Y dimensions. The valid values are controlled and they include: Decimal Degrees, Kilometers, and Meters.
- ViewingAngleType: Describes the sensors angle when the measurements are taken. The valid values are controlled and they include: At Nadir and Scan Extremes.
- ScanDirection: Describes the direction that is scanned by the sensor. The valid values are controlled and they include: Along Track and Cross Track.
Non Gridded Range Resolutions: Resolution ranges are necessary for data that is collected by aircraft and other such vessels. The following set of sub elements apply to describing the data product's resolution:
- MinimumXDimension: The minimum resolution value on an X axis on a plane - On the Earth this is normally the Longitudinal axis.
- MinimumYDimension: The minimum resolution value on a Y axis on a plane - On the Earth this is normally the Latitudinal axis.
- MaximumXDimension: The maximum resolution value on an X axis on a plane - On the Earth this is normally the Longitudinal axis.
- MaximumYDimension: The maximum resolution value on a Y axis on a plane - On the Earth this is normally the Latitudinal axis.
- Unit: The unit of measure for the X and Y dimensions. The valid values are controlled and they include: Decimal Degrees, Kilometers, and Meters.
- ViewingAngleType: Describes the sensors angle when the measurements are taken. The valid values are controlled and they include: At Nadir and Scan Extremes.
- ScanDirection: Describes the direction that is scanned by the sensor. The valid values are controlled and they include: Along Track and Cross Track.
Gridded Resolutions: The data product's spatial extent is gridded and the following set of sub elements apply:
- XDimension: The resolution value on an X axis on a plane - On the Earth this is normally the Longitudinal axis.
- YDimension: The resolution value on a Y axis on a plane - On the Earth this is normally the Latitudinal axis.
- Unit: The unit of measure for the X and Y dimensions. The valid values are controlled and they include: Decimal Degrees, Kilometers, and Meters.
Gridded Range Resolutions: Resolution ranges are necessary for data that is collected by aircraft and other such vessels. The following set of sub elements apply to describing the data product's resolution:
- MinimumXDimension: The minimum resolution value on an X axis on a plane - On the Earth this is normally the Longitudinal axis.
- MinimumYDimension: The minimum resolution value on a Y axis on a plane - On the Earth this is normally the Latitudinal axis.
- MaximumXDimension: The maximum resolution value on an X axis on a plane - On the Earth this is normally the Longitudinal axis.
- MaximumYDimension: The maximum resolution value on a Y axis on a plane - On the Earth this is normally the Latitudinal axis.
- Unit: The unit of measure for the X and Y dimensions. The valid values are controlled and they include: Decimal Degrees, Kilometers, and Meters.
Generic Resolutions: The data product's spatial extent is not known if it is gridded or not. The following set of sub elements apply:
- XDimension: The resolution value on an X axis on a plane - On the Earth this is normally the Longitudinal axis.
- YDimension: The resolution value on a Y axis on a plane - On the Earth this is normally the Latitudinal axis.
- Unit: The unit of measure for the X and Y dimensions. The valid values are controlled and they include: Decimal Degrees, Kilometers, and Meters.

(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.

A Description sub element is included in the ResolutionAndCoordinateSystem element that allows a CMR data provider to explain to a user the data products horizontal coordinate system and resolution.

Providing the horizontal coverage's resolution and coordinate system data is optional, but encouraged and is used to provide horizontal and/or vertical coordinate system information.

Vertical

Vertical spatial domain can be used to describe the coverage of data with a vertical component. The type of vertical coverage being described in the metadata is identified via the 'Vertical Spatial Domain/Type' metadata element. There are five different controlled vocabulary options for 'Vertical Spatial Domain/Type' in UMM-Common. These include:

SpatialExtent/VerticalSpatialDomain/Type:

Choice of:

Atmosphere Layer
Maximum Altitude
Minimum Altitude
Maximum Depth
Minimum Depth

Once a Type is selected, an accompanying value in the SpatialExtent/VerticalSpatialDomain/Value field must also be provided. For example, if "Maximum Altitude" was selected as the Type, the corresponding Value could be "50 KM."

Orbital

When data is collected via a satellite, the Orbit Parameters metadata elements may be used to describe the spatial coverage. Please see the CMR Data Partner User Guide for additional details on how Orbit Parameters are used by the backtrack search algorithm for conducting spatial searches. Orbit Parameters includes the following sub-elements:

Swath Width: The width of the strip of the Earth's surface from which geospatial data are collected by a satellite, in kilometers. Only a number should be provided since the unit of kilometers is implied. If providing orbit parameters, Swath Width is required.

Period: The time it takes a satellite to complete one complete orbit around the Earth, in decimal minutes. Only a number should be provided since the unit of decimal minutes is implied. If providing orbit parameters, Period is required.

Inclination Angle: The angle between the equatorial plane of the Earth and the orbital plane of a satellite, in degrees. Only a number should be provided since the unit of degrees is implied. If providing orbit parameters, Inclination Angle is required.

Number of Orbits: "Indicates the number of orbits."

Start Circular Latitude: "The latitude start of the orbit relative to the equator. This is used by the backtrack search algorithm to treat the orbit as if it starts from the specified latitude. This is optional and will default to 0 if not specified."

Furthermore, the Granule Spatial Representation element is a required element. This element identifies how the spatial extent is expressed in the granule metadata associated with a collection. The spatial representation used in the collection metadata can be different than what is used in the granule metadata. Granule Spatial Representation is a controlled vocabulary field in the UMM-Common schema and includes the following options:

CARTESIAN
GEODETIC
ORBIT
NO_SPATIAL

The granule spatial representation selected at the collection level must be utilized by the granules. Please see the Collection & Granule Spatial Relationships section of the CMR Data Partner User Guide for additional details.

The spatial extent of the granules should always fall within the spatial extent specified in the collection level metadata (and vice versa). It is the responsibility of the metadata author to ensure that collection-granule spatial relationships are compatible.

Element Specification

Model	Element	Type	Usable Valid Values	Constraints	Required?	Cardinality
UMM-C	SpatialExtent/SpatialCoverageType	Enumeration	HORIZONTAL VERTICAL ORBITAL HORIZONTAL_VERTICAL ORBITAL_VERTICAL	n/a	No	0..1
UMM-C	SpatialExtent/HorizontalSpatialDomain/ ZoneIdentifier	String	n/a	1 - 80 characters	No	0..1
UMM-C	SpatialExtent/HorizontalSpatialDomain/ Geometry/CoordinateSystem	Enumeration	CARTESIAN GEODETIC	n/a	Yes	1
UMM-C	SpatialExtent/ GranuleSpatialRepresentation	Enumeration	CARTESIAN GEODETIC ORBIT NO_SPATIAL	n/a	Yes	1

Choice of one of the following for Horizontal Spatial Domain/ Geometry:

(1) Point

If Point is selected, the cardinality is 1..*

Model

Element

Type

Constraints

Required?

Cardinality

Notes

UMM-C

SpatialExtent/HorizontalSpatialDomain/

Geometry/Point/Longitude

Number

-180 to 180

Yes, if applicable

1

Number in degrees

UMM-C

SpatialExtent/HorizontalSpatialDomain/

Geometry/Point/Latitude

Number

-90 to 90

Yes, if applicable

1

Number in degrees

(2) Bounding Rectangle

If BoundingRectangle is selected, the cardinality is 1..*

Model	Element	Type	Constraints	Required?	Cardinality	Notes
UMM-C	SpatialExtent/HorizontalSpatialDomain/Geometry/ BoundingRectangles/WestBoundingCoordinate	Number	-180 to 180	Yes, if applicable	1	Number in degrees
UMM-C	SpatialExtent/HorizontalSpatialDomain/Geometry/ BoundingRectangles/NorthBoundingCoordinate	Number	-90 to 90	Yes, if applicable	1	Number in degrees
UMM-C	SpatialExtent/HorizontalSpatialDomain/Geometry/ BoundingRectangles/EastBoundingCoordinate	Number	-180 to 180	Yes, if applicable	1	Number in degrees
UMM-C	SpatialExtent/HorizontalSpatialDomain/Geometry/ BoundingRectangles/SouthBoundingCoordinate	Number	-90 to 90	Yes, if applicable	1	Number in degrees

(3) GPolygon

If GPolygon is selected, the cardinality is 1..*

Model	Element	Type	Constraints	Required?	Cardinality	Notes
UMM-C	SpatialExtent/HorizontalSpatialDomain/Geometry/ GPolygon/Boundary/Points/Longitude	Number	-180 to 180	Yes, if applicable	4..*	Number in degrees. A minimum of 4 GPolygon bounding points must be provided.
UMM-C	SpatialExtent/HorizontalSpatialDomain/Geometry/ GPolygon/Boundary/Points/Latitude	Number	-90 to 90	Yes, if applicable	4..*	Number in degrees. A minimum of 4 GPolygon bounding points must be provided.
UMM-C	SpatialExtent/HorizontalSpatialDomain/Geometry/ GPolygon/ExclusiveZone/Boundaries/Points/Longitude	Number	-180 to 180	No	0..*	Number in degrees. A minimum of 4 GPolygon exclusion zone bounding points must be provided, if applicable (providing an exclusion zone is optional).
UMM-C	SpatialExtent/HorizontalSpatialDomain/Geometry/ GPolygon/ExclusiveZone/Boundaries/Points/Latitude	Number	-90 to 90	No	0..*	Number in degrees. A minimum of 4 GPolygon exclusion zone bounding points must be provided, if applicable (providing an exclusion zone is optional).

(4) Line

If Line is selected, the cardinality is 1..*

Model

Element

Type

Constraints

Required?

Cardinality

Notes

UMM-C

SpatialExtent/HorizontalSpatialDomain/

Geometry/Lines/Points/Longitude

Number

-180 to 180

Yes, if applicable

2..*

Number in degrees. A minimum of 2 points must be provided to create a line.

UMM-C

SpatialExtent/HorizontalSpatialDomain/

Geometry/Lines/Points/Latitude

Number

-90 to 90

Yes, if applicable

2..*

Number in degrees. A minimum of 2 points must be provided to create a line.

ResolutionAndCoordinateSystem

Point, Non Gridded, Non Gridded Range, Gridded, Gridded Range, VariesYes

Model	Element	Type	Usable Valid Values	Constraints	Required?	Cardinality	Notes
UMM-C	SpatialExtent/HorizontalSpatialDomain/ ResolutionAndCoordinateSystem/Description	String	n/a	1-2048 characters	No	0..1
UMM-C	SpatialExtent/HorizontalSpatialDomain/ ResolutionAndCoordinateSystem/GeodeticModel/ HorizontalDatumName	String	n/a	1 - 80 characters	No	0..1	Recommend providing EPSG geodetic datum names
UMM-C	SpatialExtent/HorizontalSpatialDomain/ ResolutionAndCoordinateSystem/GeodeticModel/ EllipsoidName	String	n/a	1 - 255 characters	No	0..1	Recommend providing EPSG ellipsoid names
UMM-C	SpatialExtent/HorizontalSpatialDomain/ ResolutionAndCoordinateSystem/GeodeticModel/ SemiMajorAxis	Number	n/a	n/a	No	0..1
UMM-C	SpatialExtent/HorizontalSpatialDomain/ ResolutionAndCoordinateSystem/GeodeticModel/ DenominatorOfFlatteningRatio	Number	n/a	n/a	No	0..1
UMM-C	SpatialExtent/HorizontalSpatialDomain/ ResolutionAndCoordinateSystem/HorizontalDataResolution/ HorizontalResolutionProcessingLevelEnum	Enumeration	VariesResolution	Enumeration	Varies	n/a	No	0..1
UMM-C	SpatialExtent/HorizontalSpatialDomain/ ResolutionAndCoordinateSystem/HorizontalDataResolution/ PointResolution	Enumeration	Point	n/a	No	0..1
UMM-C	SpatialExtent/HorizontalSpatialDomain/ ResolutionAndCoordinateSystem/HorizontalDataResolution/ NonGriddedResolutions GriddedResolutions GenericResolutions	Object	n/a	n/a	No	0..1
UMM-C	SpatialExtent/HorizontalSpatialDomain/ ResolutionAndCoordinateSystem/HorizontalDataResolution/ NonGriddedRangeResolutions GriddedRangeResolutions	Object	n/a	n/a	No	0..1
UMM-C	SpatialExtent/HorizontalSpatialDomain/ ResolutionAndCoordinateSystem/HorizontalDataResolutionsHorizontalDataResolution/ NonGriddedResolutions GriddedResolutions GenericResolutions/XDimension	Number	n/a	n/a	one of XDimension or YDimension is required	0..1	This is used when Horizontal Resolution Processing Level Enum is either for Non Gridded, Gridded, or Not providedGeneric Resolutions.
UMM-C	SpatialExtent/HorizontalSpatialDomain/ ResolutionAndCoordinateSystem/HorizontalDataResolutionsHorizontalDataResolution/ NonGriddedRangeResolutions GriddedRangeResolutions/MinimumXDimension	Number	n/a	n/a	one of MinimumXDimension and MaximumXDimension or MinimumYDimension and MaximumYDimension is required	0..1	This is used when Horizontal Resolution Processing Level Enum is either Non for Non Gridded Range, or Gridded Range.
UMM-C	SpatialExtent/HorizontalSpatialDomain/ ResolutionAndCoordinateSystem/HorizontalDataResolutionsHorizontalDataResolution/ NonGriddedRangeResolutions GriddedRangeResolutions/MaximumXDimension	Number	n/a	n/a	one of MinimumXDimension and MaximumXDimension or MinimumYDimension and MaximumYDimension is required	0..1	This is used when Horizontal Resolution Processing Level Enum is either Non for Non Gridded Range, or Gridded Range.
UMM-C	SpatialExtent/HorizontalSpatialDomain/ ResolutionAndCoordinateSystem/HorizontalDataResolutionsHorizontalDataResolution/ NonGriddedResolutions GriddedResolutions GenericResolutions/YDimension	Number	n/a	n/a	one of XDimension or YDimension is required	0..1	This is used when Horizontal Resolution Processing Level Enum is either for Non Gridded, Gridded, or Not providedGeneric Resolutions.
UMM-C	SpatialExtent/HorizontalSpatialDomain/ ResolutionAndCoordinateSystem/HorizontalDataResolutionsHorizontalDataResolution/ NonGriddedRangeResolutions GriddedRangeResolutions/MinimumYDimension	Number	n/a	n/a	one of MinimumXDimension and MaximumXDimension or MinimumYDimension and MaximumYDimension is required	0..1	This is used when Horizontal Resolution Processing Level Enum is either Non for Non Gridded Range, or Gridded Range.
UMM-C	SpatialExtent/HorizontalSpatialDomain/ ResolutionAndCoordinateSystem/HorizontalDataResolutionsHorizontalDataResolution/ NonGriddedRangeResolutions GriddedRangeResolutions/MaximumYDimension	Number	n/a	n/a	one of MinimumXDimension and MaximumXDimension or MinimumYDimension and MaximumYDimension is required	0..1	This is used when Horizontal Resolution Processing Level Enum is either Non for Non Gridded Range, or Gridded Range.
UMM-C	SpatialExtent/HorizontalSpatialDomain/ ResolutionAndCoordinateSystem/HorizontalDataResolutions/HorizontalDataResolution/ NonGriddedResolutions GriddedResolutions GenericResolutions NonGriddedRangeResolutions GriddedRangeResolutions/Unit	Enumeration	Decimal Degrees Kilometers Meters Statute Miles Nautical Miles Not provided	n/a	Yes	1	This is used when Horizontal Resolution Processing Level Enum is either for Non Gridded, Non Gridded Range, Gridded, Gridded Range, or Not provided.Generic Resolutions
UMM-C	SpatialExtent/HorizontalSpatialDomain/ ResolutionAndCoordinateSystem/HorizontalDataResolutionsHorizontalDataResolution/ NonGriddedResolutions NonGriddedRangeResolutions/ViewingAngleType	Enumeration	At Nadir Scan Extremes	n/a	No	0..1	This is used when Horizontal Resolution Processing Level Enum is either Non for Non Gridded, or Non Gridded Range.
UMM-C	SpatialExtent/HorizontalSpatialDomain/ ResolutionAndCoordinateSystem/HorizontalDataResolutionsHorizontalDataResolution/ NonGriddedResolutions NonGriddedRangeResolutions/ScanDirection	Enumeration	Along Track Cross Track	n/a	No	0..1	This is used when Horizontal Resolution Processing Level Enum is either Non for Non Gridded, or Non Gridded Range.
UMM-C	SpatialExtent/HorizontalSpatialDomain/ ResolutionAndCoordinateSystem/LocalCoordinateSystem/ GeoReferenceInformation	String	n/a	1 - 2048 characters	No	0..1
UMM-C	SpatialExtent/HorizontalSpatialDomain/ ResolutionAndCoordinateSystem/LocalCoordinateSystem/ Description	String	n/a	1 - 2048 characters	No	0..1

Vertical Spatial Domain:

Providing a Vertical Spatial Domain is optional (Cardinality 0..*)

Model

Element

Type

Usable Valid Values

Constraints

Required?

Cardinality

Notes

UMM-C

SpatialExtent/

VerticalSpatialDomain/Type

Enumeration

Atmosphere Layer

Maximum Altitude

Maximum Depth

Minimum Altitude

Minimum Depth

n/a

Yes, if applicable

1

Provide multiple iterations of the vertical spatial domain elements to define an upper and a lower vertical boundary (e.g. a minimum altitude and a maximum altitude).

UMM-C

SpatialExtent/

VerticalSpatialDomain/Value

String

n/a

1 - 80 characters

Yes, if applicable

1

Both Type and Value are required. Use the Value field to describe the number and unit of the Type provided in the previous field (e.g. 50 KM, 208 meters)

Orbit Parameters:

Providing Orbit Parameters is optional (Cardinality 0..*)

Model	Element	Type	Constraints	Required?	Cardinality	Notes
UMM-C	SpatialExtent/OrbitParameters/SwathWidth	Number	n/a	Yes, if applicable	1	In kilometers.
UMM-C	SpatialExtent/OrbitParameters/Period	Number	n/a	Yes, if applicable	1	In decimal minutes.
UMM-C	SpatialExtent/OrbitParameters/InclinationAngle	Number	-90 to 90	Yes, if applicable	1	In degrees.
UMM-C	SpatialExtent/OrbitParameters/NumberOfOrbits	Number	n/a	Yes, if applicable	1
UMM-C	SpatialExtent/OrbitParameters/StartCircularLatitude	Number	-90 to 90	No	0..1	In degrees.

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	true
autofit	true
name	Copy of Wiki Page Metadata Evaluation Workflow-1939-672ea43a
width	1102
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.
Automated Review
- Check that the field has been populated.
- Check that the field value is valid.
- Check that the field values matches the enumeration values.
- Check that the spatial coverage ranges are correct.
- Check that the field length is not greater than 255 characters (Ellipsoid_Name).
- Check that the field length is not greater than 80 characters (Horizontal_Datum_Name).
- Check that the field length is not greater than 80 characters (Geographic_Coordinate_Units).
- Check that the field length is not greater than 2,048 characters (Local_Coordinate_System/Description).
- Check that the field length is not greater than 2,048 characters (Local_Coordinate_System/GeoReference_Information).
- Check that the field length is not greater than 255 characters (Horizontal_Coordinate_System/Planar_Coordinate_System/Grid_Coordinate_System_Name).
- Check that the field length is not greater than 2,048 characters (Horizontal_Coordinate_System/Planar_Coordinate_System/Local_Planar_Coordinate_System/GeoReference_Information).
- Check that the field length is not greater than 2,048 characters (Horizontal_Coordinate_System/Planar_Coordinate_System/LocalPlanar_Coordinate_System/Description).
- Check that the field length is not greater than 80 characters (Horizontal_Coordinate_System/Planar_Coordinate_System/Map_Projection/Map_Projection_Name).
- Check that the field length is not greater than 255 characters (Horizontal_Coordinate_System/Planar_Coordinate_System/Map_Projection/Map_Projection_Pointer).
- Check that the field length is not greater than 80 characters (Horizontal_Coordinate_System/Planar_Coordinate_System/Planar_Coordinate_Information).
- Check that the field length is not greater than 20 characters (Planar_Coordinate_System/Planar_Coordinate_Information/Distance_And_Bearing_Representation/Bearing_Reference_Direction).
- Check that the field length is not greater than 2,048 characters (Planar_Coordinate_System/Planar_Coordinate_Information/Distance_And_Bearing_Representation/Bearing_Reference_Meridian).
- Check that the field length is not greater than 255 characters (Planar_Coordinate_System/Planar_Coordinate_Information/Distance_And_Bearing_Representation/Bearing_Units).
- Check that the field length is not greater than 80 characters (Planar_Coordinate_System/Planar_Coordinate_Information/Encoding_Method).
- Check that the field length is not greater than 80 characters (Horizontal_Coordinate_System/Planar_Coordinate_System/Planar_Coordinate_System_Id).
- Check that the field length is not greater than 80 characters (TwoD_Coordinate_System/TwoDCoordinateSystem/TwoD_Coordinate_System_Name).
- Check that the field length is not greater than 80 characters Check that the field length is not greater than 80 characters (Vertical_Coordinate_System/Altitude_System_Definition/Datum_Name).
- Check that the field length is not greater than 80 characters (Vertical_Coordinate_System/Altitude_System_Definition/Distance_Units).
- Check that the field length is not greater than 2,048 characters (Vertical_Coordinate_System/Altitude_System_Definition/Encoding_Method).
- Check that the field length is not greater than 80 characters (Vertical_Coordinate_System/Altitude_System_Definition/Resolutions).
- Check that the field length is not greater than 80 characters (Vertical_Coordinate_System/Depth_System_Definition).
- Check that the field length is not greater than 80 characters (Vertical_Coordinate_System/Depth_System_Definition/Datum_Name).
- Check that the field length is not greater than 80 characters (Vertical_Coordinate_System/Depth_System_Definition/Distance_Units).
- Check that the field length is not greater than 2,048 characters (Vertical_Coordinate_System/Depth_System_Definition/Encoding_Method).
- Check that the field length is not greater than 80 characters (Vertical_Coordinate_System/DepthSystemDefinition/Resolution).
- Check that the field length is not greater than 80 characters (Vertical_Spatial_Info/VerticalSpatialInfo/Type).
- Check that the field length is not greater than 80 characters (Vertical_Spatial_Info/VerticalSpatialInfo/Value).
- Check that the field length is not greater than 80 characters (Zone_Identifier).

Expand

title	CMR Validation

This element is required and must exist.
General validation rules for cartesian coordinates
- Any single spatial area may not cross the International Date Line or Poles.
- Two vertices will be connected with a straight line.
General validation rules for geodetic coordinates
- The implemented Geodetic model uses the great circle distance to connect two vertices for constructing a polygon area or line. If there is not enough density (that is, the number of points) for a set of vertices, then the line or the polygon area might be misinterpreted or the metadata might be considered invalid.
- Any single spatial area may cross the International Date Line and/or Poles
- Any single spatial area may not cover more than one half of the earth.
General collection level rules
- Each collection may specify only one coordinate system for its spatial coverage.
- Each collection‘s coordinate system is independent of all other collections.
- Each collection‘s coordinate system is independent of its granule spatial representation — i.e., a collection‘s spatial extent may be expressed in the Cartesian geometry, but have all of it‘s granules specify their spatial extents in the Geodetic geometry.
- A collection specifies its granules‘ spatial representation, which cannot be overridden by a granule. This element is called GranuleSpatialRepresentation.
- A collection with an orbital granule spatial representation must specify exact orbit parameters in order to facilitate granule discovery via spatial constraints.
- Ingest for a metadata record will fail if any spatial metadata input is invalid with respect to the associate rules of the utilized coordinate system.
- For any granules that are ingested for the collection, the granules spatial extent must exist within the collection's spatial extent.
The sub element GranuleSpatialRepresentation is required and so it must exist and must be filled in with one of the following enumerations: CARTESIAN, GEODETIC, ORBIT, or NO_SPATIAL. If the collection has granules associated with it the GranuleSpatialRepresentation cannot be changed.If SpatialCoverageType exists, it must be populated with one of the following enumerations: HORIZONTAL, VERTICAL, ORBITAL, HORIZONTAL_VERTICAL, ORBITAL_VERTICAL
Under HorizontalSpatialDomain
- the geometry sub element must exist
- if populated, the zone identifier must have at least 1 character and no more than 80 characters in length
- In geometry
  - The coordinate system sub element must exist and be populated with one of the following enumerations: CARTESIAN or GEODETIC.
  - At least one of the geometry types (points, bounding rectangles, gpolygons, or lines) must exist.
  - For Point and Bounding Rectangle types all sub elements are required.
  - For GPolygon types
    - The Boundary sub element must exist and at least 4 points must be present in the boundary
      - A polygon‘s vertices must be stored in order of vertex connection.
      - Provide the vertices in clockwise order. (If using ISO 19115-2 MENDS, the expected order is counter-clockwise and the CMR will convert the order to clockwise as it translates the record to UMM).
      - No consecutive vertices may have the same latitude and longitude, that is, no repeating points.
      - Polygonal lines may not cross each other within the polygon.
      - The first point and last point must be the same.
      - No polygon should cover more than half the Earth in the Geodetic coordinate system.
    - If the ExclusiveZone is used the Boundary sub element must exist.
  - For Lines
    - At least 2 Points must exist
    - A line may not have consecutive vertices with the same latitude and longitude (duplicate points).
    - A line must be less than one half the circumference of the Earth in the Geodetic coordinate system.
Under VerticalSpatialDomain
- All sub elements must exist
- The type sub element must be populated with the following enumeration values: Atmosphere Layer, Maximum Altitude, Maximum Depth, Minimum Altitude, Minimum Depth.
If the OrbitParameters sub element exists all of its sub elements except for the StartCircularLatitude sub element must exist.

Expand

title	ARC Metadata QA/QC

ARC Priority Matrix

Priority Categorization	Justification
	This element is categorized as highest priority when: The element is not included at all. The element is included but is empty.
	This element is categorized as medium priority when:
	Not applicable
	The element is provided, a correct valid value is used, and the valid value matches the status of the dataset.

ARC Automated Checks

Coordinate System
- If no value is provided, return is: "This is a required element. Geometry/Coordinate_System should be chosen from the following options: <schema listed here>."
- If the provided value does not conform to the schema, return is: "Invalid value for Geometry/Coordinate_System. Geometry/Coordinate_System should be chosen from the following options: <schema listed here>."
- Otherwise, return is "OK."
Vertical
- If no value is provided, return is: "np."
- If the provided value does not conform to the schema, return is: "Invalid value for Vertical Spatial Type: <provided value>. Recommend providing a valid value from the following list: <schema listed here>."
- Otherwise, return is "OK."
Orbital
- If no value is provided, return is: "np."
- Otherwise, return is "OK."

Dialect Mappings

Expand

title	DIF 10

DIF 10

UMM-C Element	DIF 10 Path	Type	Usable Valid Values	Constraints	Required in DIF 10?	Cardinality
SpatialExtent/ SpatialCoverageType	Spatial_Coverage/Spatial_Coverage_Type	Enumeration	HORIZONTAL VERTICAL ORBITAL HORIZONTAL_VERTICAL ORBITAL_VERTICAL	n/a	No	0..1
SpatialExtent/ GranuleSpatialRepresentation	Spatial_Coverage/Granule_Spatial_Representation	Enumeration	CARTESIAN GEODETIC ORBIT NO_SPATIAL	n/a	Yes	1
SpatialExtent/ HorizontalSpatialDomain/ZoneIdentifier	Spatial_Coverage/Zone_Identifier	String	n/a	1 - 80 characters	No	0..1
SpatialExtent/HorizontalSpatialDomain/ Geometry/CoordinateSystem	Spatial_Coverage/Geometry/Coordinate_System	Enumeration	CARTESIAN GEODETIC	n/a	Yes	1

Choice of one of the following for Spatial_Coverage/ Geometry:

(1) Bounding Rectangle

If Bounding_Rectangle is selected, the cardinality is 1..*

UMM-C Element	DIF 10 Path	Type	Constraints	Required in DIF 10?	Cardinality	Notes
	Spatial_Coverage/Geometry/Bounding_Rectangle/ Center_Point/Point/Point_Longitude	Number	-180 to 180	No	1	Number in degrees Does not map to UMM-C
	Spatial_Coverage/Geometry/Bounding_Rectangle/ Center_Point/Point/Point_Latitude	Number	-90 to 90	No	1	Number in degrees Does not map to UMM-C
SpatialExtent/HorizontalSpatialDomain/ Geometry/BoundingRectangles/ SouthBoundingCoordinate	Spatial_Coverage/Geometry/Bounding_Rectangle/ Southernmost_Latitude	Number	-180 to 180	Yes, if applicable	1	Number in degrees
SpatialExtent/HorizontalSpatialDomain/ Geometry/BoundingRectangles/ NorthBoundingCoordinate	Spatial_Coverage/Geometry/Bounding_Rectangle/ Northernmost_Latitude	Number	-90 to 90	Yes, if applicable	1	Number in degrees
SpatialExtent/HorizontalSpatialDomain/ Geometry/BoundingRectangles/ WestBoundingCoordinate	Spatial_Coverage/Geometry/Bounding_Rectangle/ Westernmost_Longitude	Number	-180 to 180	Yes, if applicable	1	Number in degrees
SpatialExtent/HorizontalSpatialDomain/ Geometry/BoundingRectangles/ EastBoundingCoordinate	Spatial_Coverage/Geometry/Bounding_Rectangle/ Easternmost_Longitude	Number	-180 to 180	Yes, if applicable	1	Number in degrees
	Spatial_Coverage/Geometry/Bounding_Rectangle/ Minimum_Altitude	Number		No
	Spatial_Coverage/Geometry/Bounding_Rectangle/ Maximum_Altitude	Number		No
	Spatial_Coverage/Geometry/Bounding_Rectangle/ Altitude_Unit	String		No
	Spatial_Coverage/Geometry/Bounding_Rectangle/ Minimum_Depth	Number		No
	Spatial_Coverage/Geometry/Bounding_Rectangle/ Maximum_Depth	Number		No
	Spatial_Coverage/Geometry/Bounding_Rectangle/ Depth_Unit	String		No

(2) Point

If Point is selected, the cardinality is 1..*

UMM-C Element

DIF 10 Path

Type

Constraints

Required in DIF 10?

Cardinality

Notes

SpatialExtent/HorizontalSpatialDomain/

Geometry/Point/Longitude

Spatial_Coverage/Geometry/Point/Point_Longitude

Number

-180 to 180

Yes, if applicable

1

Number in degrees

SpatialExtent/HorizontalSpatialDomain/

Geometry/Point/Latitude

Spatial_Coverage/Geometry/Point/Point_Latitude

Number

-90 to 90

Yes, if applicable

1

Number in degrees

(3) Line

If Line is selected, the cardinality is 1..*

UMM-C Element	DIF 10 Path	Type	Constraints	Required in DIF 10?	Cardinality	Notes
SpatialExtent/HorizontalSpatialDomain/ Geometry/Lines/Points/Longitude	Spatial_Coverage/Geometry/Line/ Point/Point_Longitude	Number	-180 to 180	Yes, if applicable	2..*	Number in degrees. A minimum of 2 points must be provided to create a line.
SpatialExtent/HorizontalSpatialDomain/ Geometry/Lines/Points/Latitude	Spatial_Coverage/Geometry/Line/ Point/Point_Latitude	Number	-90 to 90	Yes, if applicable	2..*	Number in degrees. A minimum of 2 points must be provided to create a line.
	Spatial_Coverage/Geometry/Line/ Center_Point/Point_Latitude	Number	-90 to 90	No	1	Number in degrees Does not map to UMM-C
	Spatial_Coverage/Geometry/Line/ Center_Point/Point_Longitude	Number	-180 to 180	No	1	Number in degrees Does not map to UMM-C

(4) Polygon

If Polygon is selected, the cardinality is 1..*

UMM-C Element	DIF 10 Path	Type	Constraints	Required in DIF 10?	Cardinality	Notes
SpatialExtent/HorizontalSpatialDomain/ Geometry/GPolygon/Boundary/Points/ Longitude	Spatial_Coverage/Geometry/Polygon/ Boundary/Point/Point_Longitude	Number	-180 to 180	Yes, if applicable	2..*	Number in degrees. A minimum of 2 points must be provided to create a line.
SpatialExtent/HorizontalSpatialDomain/ Geometry/GPolygon/Boundary/Points/ Latitude	Spatial_Coverage/Geometry/Polygon/ Boundary/Point/Point_Latitude	Number	-90 to 90	Yes, if applicable	2..*	Number in degrees. A minimum of 2 points must be provided to create a line.
SpatialExtent/HorizontalSpatialDomain/ Geometry/GPolygon/ExclusiveZone/ Boundaries/Points/Longitude	Spatial_Coverage/Geometry/Polygon/ Exclusion_Zone/Boundary/Point/Point_Longitude	Number	-180 to 180	No	1	Number in degrees
SpatialExtent/HorizontalSpatialDomain/ Geometry/GPolygon/ExclusiveZone/ Boundaries/Points/Latitude	Spatial_Coverage/Geometry/Polygon /Exclusion_Zone/Boundary/Point/Point_Latitude	Number	-90 to 90	No	1	Number in degrees
	Spatial_Coverage/Geometry/Polygon/ Center_Point/Point/Point_Longitude	Number	-180 to 180	No	1	Number in degrees Does not map to UMM-C
	Spatial_Coverage/Geometry/Polygon/ Center_Point/Point/Point_Latitude	Number	-90 to 90	No	1	Number in degrees Does not map to UMM-C

Resolution And Coordinate System:

UMM-C Element	DIF 10 Path	Type	Constraints	Required in DIF 10?	Cardinality	Notes
n/a	Spatial_Coverage/Spatial_Info/Spatial_Coverage_Type	Enumeration	Horizontal HorizontalVertical Orbit Vertical Horizon&Vert	Yes, if applicable	1	This element should be the same as Spatial_Coverage/Spatial_Coverage_Type and therefore is redundant. It is no longer translated.
SpatialExtent/HorizontalSpatialDomain/ ResolutionAndCoordinateSystem/Description	n/a
SpatialExtent/HorizontalSpatialDomain/ResolutionAndCoordinateSystem/ /GeodeticModel/HorizontalDatumName	Spatial_Coverage/Spatial_Info/Horizontal_Coordinate_System/Geodetic_Model/Horizontal_DatumName	String		No	0..1	Recommend providing EPSG geodetic datum names
SpatialExtent/HorizontalSpatialDomain/ResolutionAndCoordinateSystem/ GeodeticModel/EllipsoidName	Spatial_Coverage/Spatial_Info/Horizontal_Coordinate_System/Geodetic_Model/Ellipsoid_Name	String		No	0..1	Recommend providing EPSG ellipsoid names
SpatialExtent/HorizontalSpatialDomain/ResolutionAndCoordinateSystem /GeodeticModel/SemiMajorAxis	Spatial_Coverage/Spatial_Info/Horizontal_Coordinate_System/Geodetic_Model/Semi_Major_Axis	Decimal		No	0..1
SpatialExtent/HorizontalSpatialDomain/ResolutionAndCoordinateSystem/ GeodeticModel/DenominatorOfFlatteningRatio	Spatial_Coverage/Spatial_Info/Horizontal_Coordinate_System/Geodetic_Model/Denominator_Of_Flattening_Ratio	Decimal		No	0..1
SpatialExtent/HorizontalSpatialDomain/ResolutionAndCoordinateSystem/ HorizontalDataResolution/HorizontalResolutionProcessingLevelEnum = Not providedGenericResolutions	n/a
SpatialExtent/HorizontalSpatialDomain/ResolutionAndCoordinateSystem/ HorizontalDataResolution/GenericResolution/XDimension	Spatial_Coverage/Spatial_Info/Horizontal_Coordinate_System/Geographic_Coordinate_System/LongitudeResolution	Decimal		No	0..1	If this exists then translate this element otherwise use Data_Resolution/Longitude_Resolution located in the next cell below.
	Data_Resolution/Longitude_Resolution	String		No	0..1	If Geographic_Coordinate_System/LongitudeResolution doesn't exist then translate this element.
SpatialExtent/HorizontalSpatialDomain/ResolutionAndCoordinateSystem/ HorizontalDataResolution/GenericResolution/YDimension	Spatial_Coverage/Spatial_Info/Horizontal_Coordinate_System/Geographic_Coordinate_System/LatitudeResolution	Decimal		No	0..1	If this exists then translate this element otherwise use Data_Resolution/Latitude_Resolution located in the next cell below.
	Data_Resolution/Latitude_Resolution	String		No	0..1	If Geographic_Coordinate_System/LatitudeResolution doesn't exist then translate this element.
SpatialExtent/HorizontalSpatialDomain/ResolutionAndCoordinateSystem/ HorizontalDataResolution/GenericResolution/Unit	Spatial_Coverage/Spatial_Info/Horizontal_Coordinate_System/Geographic_Coordinate_System/GeographicCoordinateUnits	String		No	0..1
SpatialExtent/HorizontalSpatialDomain/ResolutionAndCoordinateSystem/ LocalCoordinateSystem/GeoReferenceInformation	Spatial_Coverage/Spatial_Info/Horizontal_Coordinate_System/Local_Coordinate_System/GeoReference_Information	String		No	0..1
SpatialExtent/HorizontalSpatialDomain/ResolutionAndCoordinateSystem/ LocalCoordinateSystem/Description	Spatial_Coverage/Spatial_Info/Horizontal_Coordinate_System/Local_Coordinate_System/Description	String		No	0..1
n/a	Data_Resolution/Horizontal_Resolution_Range	String	KMS controlled	No	0..1	Recommend selecting a value from the GCMD Horizontal Data Resolution keywords to populate this field. The CMR will use its own values to categorically create facet ranges. The GCMD values will be updated afterward. Therefore this field cannot be used by the CMR and will not be translated.
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.

Orbit Parameters:

Providing Orbit_Parameters is optional (Cardinality 0..*)

UMM-C Element	DIF 10 Path	Type	Constraints	Required in DIF 10?	Cardinality	Notes
SpatialExtent/OrbitParameters/SwathWidth	Spatial_Coverage/Orbit_Parameters/Swath_Width	Number	n/a	Yes, if applicable	1	In kilometers.
SpatialExtent/OrbitParameters/Period	Spatial_Coverage/Orbit_Parameters/Period	Number	n/a	Yes, if applicable	1	In decimal minutes.
SpatialExtent/OrbitParameters/InclinationAngle	Spatial_Coverage/Orbit_Parameters/Inclination_Angle	Number	-90 to 90	No	1	In degrees.
SpatialExtent/OrbitParameters/NumberOfOrbits	Spatial_Coverage/Orbit_Parameters/Number_of_Orbits	Number	n/a	No	1
SpatialExtent/OrbitParameters/StartCircularLatitude	Spatial_Coverage/Orbit_Parameters/Start_Circular_Latitude	Number	-90 to 90	No	0..1	In degrees.

Vertical Spatial Info:

Providing a Vertical_Spatial_Info is optional (Cardinality 0..*)

UMM-C Element

DIF 10 Path

Type

Usable Valid Values

Constraints

Required in DIF 10?

Cardinality

Notes

SpatialExtent/

VerticalSpatialDomain/Type

Spatial_Coverage/

Vertical_Spatial_Info/Type

Enumeration

Atmosphere Layer

Maximum Altitude

Maximum Depth

Minimum Altitude

Minimum Depth

n/a

Yes, if applicable

1

Provide multiple iterations of the vertical spatial domain elements to define an upper and a lower vertical boundary (e.g. a minimum altitude and a maximum altitude).

SpatialExtent/

VerticalSpatialDomain/Value

Spatial_Coverage/

Vertical_Spatial_Info/Value

String

n/a

1 - 80 characters

Yes, if applicable

1

Example Mapping

Section

Column

width	50%

DIF 10

No Format

<Spatial_Coverage>
  <Spatial_Coverage_Type>Horizontal</Spatial_Coverage_Type>
  <Granule_Spatial_Representation>CARTESIAN</Granule_Spatial_Representation>
  <Zone_Identifier>1</Zone_Identifier>
  <Geometry>
    <Coordinate_System>CARTESIAN</Coordinate_System>
    <Polygon>
      <Boundary>
        <Point>
          <Point_Longitude>-10</Point_Longitude>
          <Point_Latitude>10</Point_Latitude>
        </Point>
        <Point>
          <Point_Longitude>10</Point_Longitude>
          <Point_Latitude>10</Point_Latitude>
        </Point>
        <Point>
          <Point_Longitude>10</Point_Longitude>
          <Point_Latitude>-10</Point_Latitude>
        </Point>
        <Point>
          <Point_Longitude>-10</Point_Longitude>
          <Point_Latitude>-10</Point_Latitude>
        </Point>
      </Boundary>
      <Exclusive_Zone>
        <Boundary>
          <Point>
            <Point_Longitude>-5</Point_Longitude>
            <Point_Latitude>-1</Point_Latitude>
          </Point>
          <Point>
            <Point_Longitude>-1</Point_Longitude>
            <Point_Latitude>-1</Point_Latitude>
           </Point>
           <Point>
             <Point_Longitude>-1</Point_Longitude>
             <Point_Latitude>-5</Point_Latitude>
           </Point>
           <Point>
             <Point_Longitude>-5</Point_Longitude>
             <Point_Latitude>-5</Point_Latitude>
           </Point>
        </Boundary>
        <Boundary>
          <Point>
            <Point_Longitude>0</Point_Longitude>
            <Point_Latitude>5</Point_Latitude>
          </Point>
          <Point>
            <Point_Longitude>5</Point_Longitude>
            <Point_Latitude>5</Point_Latitude>
          </Point>
          <Point>
            <Point_Longitude>5</Point_Longitude>
            <Point_Latitude>0</Point_Latitude>
          </Point>
          <Point>
            <Point_Longitude>0</Point_Longitude>
            <Point_Latitude>0</Point_Latitude>
          </Point>
        </Boundary>
      </Exclusive_Zone>
    </Polygon>
    <Bounding_Rectangle>
      <Southernmost_Latitude>80.1</Southernmost_Latitude>
      <Northernmost_Latitude>90.0</Northernmost_Latitude>
      <Westernmost_Longitude>-180.0</Westernmost_Longitude>
      <Easternmost_Longitude>-170.3</Easternmost_Longitude>
    </Bounding_Rectangle>
    <Line>
      <Point>
        <Point_Longitude>-50</Point_Longitude>
        <Point_Latitude>-50</Point_Latitude>
      </Point>
      <Point>
        <Point_Longitude>-40</Point_Longitude>
        <Point_Latitude>-40</Point_Latitude>
      </Point>
    </Line>
    <Line>
      <Point>
        <Point_Longitude>50</Point_Longitude>
        <Point_Latitude>50</Point_Latitude>
      </Point>
      <Point>
        <Point_Longitude>40</Point_Longitude>
        <Point_Latitude>40</Point_Latitude>
      </Point>
    </Line>
    <Point>
      <Point_Longitude>-70</Point_Longitude>
      <Point_Latitude>-70</Point_Latitude>
    </Point>
    <Point>
      <Point_Longitude>-65</Point_Longitude>
      <Point_Latitude>-65</Point_Latitude>
    </Point>
  </Geometry>
  <Orbit_Parameters>
    <Swath_Width>22</Swath_Width>
    <Period>1</Period>
    <Inclination_Angle>4</Inclination_Angle>
    <Number_Of_Orbits>1</Number_Of_Orbits>
    <Start_Circular_Latitude>1</Start_Circular_Latitude>
  </Orbit_Parameters>
  <Vertical_Spatial_Info>
    <Type>Maximum_Altitude</Type>
    <Value>100</Value>
  </Vertical_Spatial_Info>
  <Vertical_Spatial_Info>
    <Type>Minimum_Altitude</Type>
    <Value>1</Value>
  </Vertical_Spatial_Info>
  ...
  <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

width	50%

No Format

"SpatialExtent": {
  "SpatialCoverageType": "HORIZONTAL",
    "HorizontalSpatialDomain": {
      "ZoneIdentifier" : "1",
      "Geometry": {
        "CoordinateSystem": "CARTESIAN",
        "Points": [{
          "Longitude":-70, 
          "Latitude":-70
         }, {
          "Longitude":-65, 
          "Latitude":-65
         }],
        "BoundingRectangles": [{
          "WestBoundingCoordinate": -180.0, 
          "NorthBoundingCoordinate": 90.0, 
          "EastBoundingCoordinate": -170.3, 
          "SouthBoundingCoordinate": 80.1
        }],
        "GPolygons": [{
          "Boundary" : {
            "Points": [{
              "Longitude":-10, 
              "Latitude":-10
            }, {
              "Longitude":10, 
              "Latitude":-10
            }, {
              "Longitude":10, 
              "Latitude":10
            }, {
              "Longitude":-10, 
              "Latitude":10
            }, {
              "Longitude":-10, 
              "Latitude":-10
            }]
          },
          "ExclusiveZone": {
            "Boundaries": [{
              "Points": [{
                "Longitude":-5, 
                "Latitude":-5
              }, {
                "Longitude":-1, 
                "Latitude":-5
              }, {
                "Longitude":-1, 
                "Latitude":-1
              }, {
                "Longitude":-5, 
                "Latitude":-1
              }, {
                "Longitude":-5, 
                "Latitude":-5
              }]
            }, {
              "Points": [{
                "Longitude":0, 
                "Latitude":0
              }, {
                "Longitude":5, 
                "Latitude":0
              }, {
                "Longitude":5, 
                "Latitude":5
              }, {
                "Longitude":0, 
                "Latitude":5
              }, {
                "Longitude":0, 
                "Latitude":0
              }]
            }]
          }
        }],
        "Lines": [{
          "Points": [{
            "Longitude":-50, 
            "Latitude":-50
          }, {
            "Longitude":-40, 
            "Latitude":-40
          }]
        }, {
          "Points": [{
            "Longitude":50, 
            "Latitude":50
          }, {
            "Longitude":40, 
            "Latitude":40
          }]
        }]
      },
      "ResolutionAndCoordinateSystem": {
        "Description": "A description of the horizontal spatial resolution for end user consumption."
        "GeodeticDatum": {
          "HorizontalDatumName": "North American Datum 1983",
          "EllipsoidName": "GRS 1980",
          "SemiMajorAxis": "6378137",
          "DenominatorOfFlatteningRatio": "298.257222101"
        },        
        "HorizontalDataResolutionsHorizontalDataResolution": [{
          "HorizontalResolutionProcessingLevelEnumGenericResolutions": [{
 "Non Gridded",
          "XDimension": 0.5, 
            "YDimension": 0.5,
            "Unit": "Decimal Degrees"
          }]
        }
      }
    },
    "VerticalSpatialDomains": [{
      "Type": "Maximum Altitude", 
      "Value": "100"
    }, {
      "Type": "Minimum Altitude",
      "Value": "1"
    }
  ],
  "OrbitParameters": {
    "SwathWidth": 22,
    "Period": 1,
    "InclinationAngle": 4,
    "NumberOfOrbits": 1,
    "StartCircularLatitude": 1},
    "GranuleSpatialRepresentation": "CARTESIAN"
  },
  "GranuleSpatialRepresentation": "CARTESIAN"
},

Expand

title	ECHO 10

ECHO 10

UMM-C Element	ECHO 10 Path	Type	Usable Valid Values	Constraints	Required in ECHO10?	Cardinality
SpatialExtent/ SpatialCoverageType	Spatial/SpatialCoverageType	Enumeration	HORIZONTAL VERTICAL ORBITAL HORIZONTAL_VERTICAL ORBITAL_VERTICAL	n/a	No	0..1
SpatialExtent/ HorizontalSpatialDomain/ZoneIdentifier	Spatial/HorizontalSpatialDomain/ZoneIdentifier	String	n/a	1 - 80 characters	No	0..1
SpatialExtent/HorizontalSpatialDomain/ Geometry/CoordinateSystem	Spatial/HorizontalSpatialDomain/Geometry/ CoordinateSystem	Enumeration	CARTESIAN GEODETIC	n/a	Yes	1
SpatialExtent/ GranuleSpatialRepresentation	Spatial/GranuleSpatialRepresentation	Enumeration	CARTESIAN GEODETIC ORBIT NO_SPATIAL	n/a	Yes	1

Choice of one of the following for Horizontal Spatial Domain/ Geometry:

(1) Point

If Point is selected, the cardinality is 1..*

UMM-C Element

ECHO 10 Path

Type

Constraints

Required in ECHO10?

Cardinality

Notes

SpatialExtent/HorizontalSpatialDomain/

Geometry/Point/Longitude

SpatialExtent/HorizontalSpatialDomain/Geometry/Point/Longitude

Number

-180 to 180

Yes, if applicable

1

Number in degrees

SpatialExtent/HorizontalSpatialDomain/

Geometry/Point/Latitude

SpatialExtent/HorizontalSpatialDomain/Geometry/Point/Latitude

Number

-90 to 90

Yes, if applicable

1

Number in degrees

(2) Bounding Rectangle

If BoundingRectangle is selected, the cardinality is 1..*

UMM-C Element	ECHO 10 Path	Type	Constraints	Required in ECHO10?	Cardinality	Notes
SpatialExtent/HorizontalSpatialDomain/ Geometry/BoundingRectangles/ WestBoundingCoordinate	SpatialExtent/HorizontalSpatialDomain/ Geometry/BoundingRectangles/ WestBoundingCoordinate	Number	-180 to 180	Yes, if applicable	1	Number in degrees
SpatialExtent/HorizontalSpatialDomain/ Geometry/BoundingRectangles/ NorthBoundingCoordinate	SpatialExtent/HorizontalSpatialDomain/ Geometry/BoundingRectangles/ NorthBoundingCoordinate	Number	-90 to 90	Yes, if applicable	1	Number in degrees
SpatialExtent/HorizontalSpatialDomain/ Geometry/BoundingRectangles/ EastBoundingCoordinate	SpatialExtent/HorizontalSpatialDomain/ Geometry/BoundingRectangles/ EastBoundingCoordinate	Number	-180 to 180	Yes, if applicable	1	Number in degrees
SpatialExtent/HorizontalSpatialDomain/ Geometry/BoundingRectangles/ SouthBoundingCoordinate	SpatialExtent/HorizontalSpatialDomain/ Geometry/BoundingRectangles/ SouthBoundingCoordinate	Number	-90 to 90	Yes, if applicable	1	Number in degrees
	SpatialExtent/HorizontalSpatialDomain/ Geometry/BoundingRectangles/ CenterPoint/PointLongitude	Number	-180 to 180	Yes, if applicable	CenterPoint 0..1	Number in degrees Does not map to UMM-C
	SpatialExtent/HorizontalSpatialDomain/ Geometry/BoundingRectangles/ CenterPoint/PointLatitude	Number	-90 to 90	Yes, if applicable	CenterPoint 0..1	Number in degrees Does not map to UMM-C

(3) Line

If Line is selected, the cardinality is 2..* since at least 2 points must be provided to create a Line.

UMM-C Element	ECHO 10 Path	Type	Constraints	Required in ECHO10?	Cardinality	Notes
SpatialExtent/HorizontalSpatialDomain/ Geometry/Lines/Points/Longitude	SpatialExtent/HorizontalSpatialDomain/ Geometry/Line/Point/PointLongitude	Number	-180 to 180	Yes, if applicable	1	Number in degrees
SpatialExtent/HorizontalSpatialDomain/ Geometry/Lines/Points/Latitude	SpatialExtent/HorizontalSpatialDomain/ Geometry/Line/Point/PointLatitude	Number	-90 to 90	Yes, if applicable	1	Number in degrees
	SpatialExtent/HorizontalSpatialDomain/ Geometry/Line/CenterPoint/PointLongitude	Number	-180 to 180	Yes, if applicable	CenterPoint 0..1	Number in degrees Does not map to UMM-C
	SpatialExtent/HorizontalSpatialDomain/ Geometry/Line/CenterPoint/PointLatitude	Number	-90 to 90	Yes, if applicable	CenterPoint 0..1	Number in degrees Does not map to UMM-C

(4) GPolygon

If GPolygon is selected, the cardinality is 1..*

UMM-C Element	ECHO 10 Path	Type	Constraints	Required in ECHO10?	Cardinality	Notes
SpatialExtent/HorizontalSpatialDomain/ Geometry/GPolygon/Boundary/Points/Longitude	Spatial/ Horizontal Spatial Domain/ Geometry/ GPolygon/ Boundary/Point/ Point Longitude	Number	-180 to 180	Yes, if applicable	4..*	Number in degrees. A minimum of 4 GPolygon bounding points must be provided to create a polygon.
SpatialExtent/HorizontalSpatialDomain/ Geometry/GPolygon/Boundary/Points/Latitude	Spatial/ Horizontal Spatial Domain/ Geometry/ GPolygon/ Boundary/ Point/ Point Latitude	Number	-90 to 90	Yes, if applicable	4..*	Number in degrees. A minimum of 4 GPolygon bounding points must be provided to create a polygon.
SpatialExtent/HorizontalSpatialDomain/Geometry/ GPolygon/ExclusiveZone/Boundaries/Points/Longitude	Spatial/ Horizontal Spatial Domain/ Geometry/GPolygon/Exclusive Zone/ Boundary/Point/Point Latitude	Number	-180 to 180	No	0..*	Number in degrees. A minimum of 4 GPolygon exclusion zone bounding points must be provided, if applicable (providing an exclusion zone is optional), to create a polygon.
SpatialExtent/HorizontalSpatialDomain/Geometry /GPolygon/ExclusiveZone/Boundaries/Points/Latitude	Spatial/ Horizontal Spatial Domain/ Geometry/ GPolygon/ Exclusive Zone/ Boundary/ Point/ Point Latitude	Number	-90 to 90	No	0..*	Number in degrees. A minimum of 4 GPolygon exclusion zone bounding points must be provided, if applicable (providing an exclusion zone is optional), to create a polygon.
	Spatial/ Horizontal Spatial Domain/ Geometry/ GPolygon/ Center Point/ Point/ Point Longitude	Number	-180 to 180	Yes, if applicable	CenterPoint 0..1	Number in degrees Does not map to UMM-C
	Spatial/ Horizontal Spatial Domain/ Geometry/ GPolygon/ Center Point/ Point/ Point Latitude	Number	-90 to 90	Yes, if applicable	CenterPoint 0..1	Number in degrees Does not map to UMM-C

Resolution And Coordinate System:

UMM-C Element	ECHO 10 Path	Type	Constraints	Required in ECHO10?	Cardinality	Note
n/a	SpatialInfo/SpatialCoverageType	String	1 - 80 characters	Yes, if applicable	1	This attribute should be the same as Spatial/SpatialCoverageType and is therefore redundant. It is no longer translated.
SpatialExtent/HorizontalSpatialDomain/Description	n/a
SpatialExtent/HorizontalSpatialDomain/ResolutionAndCoordinateSystem/ /GeodeticModel/HorizontalDatumName	SpatialInfo/HorizontalCoordinateSystem/GeodeticModel/HorizontalDatumName	String	1 - 80 characters	No	0..1	Recommend providing EPSG geodetic datum names
SpatialExtent/HorizontalSpatialDomain/ResolutionAndCoordinateSystem/ GeodeticModel/EllipsoidName	SpatialInfo/HorizontalCoordinateSystem/GeodeticModel/EllipsoidName	String	1 - 255 characters	No	0..1	Recommend providing EPSG ellipsoid names
SpatialExtent/HorizontalSpatialDomain/ResolutionAndCoordinateSystem /GeodeticModel/SemiMajorAxis	SpatialInfo/HorizontalCoordinateSystem/GeodeticModel/SemiMajorAxis	Decimal	n/a	No	0..1
SpatialExtent/HorizontalSpatialDomain/ResolutionAndCoordinateSystem/ GeodeticModel/DenominatorOfFlatteningRatio	SpatialInfo/HorizontalCoordinateSystem/GeodeticModel/DenominatorOfFlatteningRatio	Decimal	n/a	No	0..1
SpatialExtent/HorizontalSpatialDomain/ResolutionAndCoordinateSystem/ HorizontalDataResolution/HorizontalResolutionProcessingLevelEnum = Not providedGenericResolution
SpatialExtent/HorizontalSpatialDomain/ResolutionAndCoordinateSystem/ HorizontalDataResolution/GenericResolution/XDimension	SpatialInfo/HorizontalCoordinateSystem/GeographicCoordinateSystem/LongitudeResolution	Decimal	n/a	No	0..1	For lon, a 3 digit decimal number from 0-180 + or absence of - for values west of prime meridian; - for all others.
SpatialExtent/HorizontalSpatialDomain/ResolutionAndCoordinateSystem/ HorizontalDataResolution/GenericResolution/YDimension	SpatialInfo/HorizontalCoordinateSystem/GeographicCoordinateSystem/LatitudeResolution	Decimal	n/a	No	0..1	For lat, a 2 digit decimal number from 0-90 + or absence of - for values north of equator; - for all others.
SpatialExtent/HorizontalSpatialDomain/ResolutionAndCoordinateSystem/ HorizontalDataResolution/GenericResolution/Unit	SpatialInfo/HorizontalCoordinateSystem/GeographicCoordinateSystem/GeographicCoordinateUnits	String	1 - 80 characters	No	0..1	Units of measure used for the geodetic latitude and longitude resolution values. E.g. Decimal Degrees or Degrees Minutes Seconds.
SpatialExtent/HorizontalSpatialDomain/ResolutionAndCoordinateSystem/ LocalCoordinateSystem/Description	SpatialInfo/HorizontalCoordinateSystem/LocalCoordinateSystem/Description	String	1 - 2048 characters	No	0..1
SpatialExtent/HorizontalSpatialDomain/ResolutionAndCoordinateSystem/ LocalCoordinateSystem/GeoReferenceInformation	SpatialInfo/HorizontalCoordinateSystem/LocalCoordinateSystem/GeoReferenceInformation	String	1 - 2048 characters	No	0..1

Vertical Spatial Domain:

Providing a Vertical Spatial Domain is optional (Cardinality 0..*)

UMM-C Element

ECHO 10 Path

Type

Usable Valid Values

Constraints

Required in ECHO10?

Cardinality

Notes

SpatialExtent/

VerticalSpatialDomain/Type

Spatial/VerticalSpatialDomain/Type

Enumeration

Atmosphere Layer

Maximum Altitude

Maximum Depth

Minimum Altitude

Minimum Depth

n/a

Yes, if applicable

1

Provide multiple iterations of the vertical spatial domain elements to define an upper and a lower vertical boundary (e.g. a minimum altitude and a maximum altitude).

SpatialExtent/

VerticalSpatialDomain/Value

Spatial/VerticalSpatialDomain/Value

String

n/a

1 - 80 characters

Yes, if applicable

1

Both Type and Value are required. Use the Value field to describe the number and unit of the Type provided in the previous field (e.g. 50 KM, 208 meters)

Orbit Parameters:

Providing Orbit Parameters is optional (Cardinality 0..*)

UMM-C Element	ECHO 10 Path	Type	Constraints	Required in ECHO10?	Cardinality	Notes
SpatialExtent/OrbitParameters/SwathWidth	Spatial/OrbitParameters/SwathWidth	Number	n/a	Yes, if applicable	1	In kilometers
SpatialExtent/OrbitParameters/Period	Spatial/OrbitParameters/Period	Number	n/a	Yes, if applicable	1	In decimal minutes
SpatialExtent/OrbitParameters/InclinationAngle	Spatial/OrbitParameters/InclinationAngle	Number	-90 to 90	Yes, if applicable	1	In degrees
SpatialExtent/OrbitParameters/NumberOfOrbits	Spatial/OrbitParameters/NumberOfOrbits	Number	n/a	Yes, if applicable	1
SpatialExtent/OrbitParameters/StartCircularLatitude	Spatial/OrbitParameters/StartCircularLatitude	Number	-90 to 90	No	0..1	In degrees

Example Mapping

Section

Column

width	50%

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>
<Spatial>
  <SpatialCoverageType>HORIZONTAL</SpatialCoverageType>
  <HorizontalSpatialDomain>
    <ZoneIdentifier>1</ZoneIdentifier>
    <Geometry>
      <CoordinateSystem>CARTESIAN</CoordinateSystem>
      <Point>
        <PointLongitude>-70</PointLongitude>
        <PointLatitude>-70</PointLatitude>
      </Point>
      <Point>
        <PointLongitude>-65</PointLongitude>
        <PointLatitude>-65</PointLatitude>
      </Point>
      <BoundingRectangle>
        <WestBoundingCoordinate>-180.0</WestBoundingCoordinate>
        <NorthBoundingCoordinate>90.0</NorthBoundingCoordinate>
        <EastBoundingCoordinate>-170.3</EastBoundingCoordinate>
        <SouthBoundingCoordinate>80.1</SouthBoundingCoordinate>
      </BoundingRectangle>
      <GPolygon>
        <Boundary>
          <Point>
            <PointLongitude>-10</PointLongitude>
            <PointLatitude>10</PointLatitude>
          </Point>
          <Point>
            <PointLongitude>10</PointLongitude>
            <PointLatitude>10</PointLatitude>
          </Point>
          <Point>
            <PointLongitude>10</PointLongitude>
            <PointLatitude>-10</PointLatitude>
          </Point>
          <Point>
            <PointLongitude>-10</PointLongitude>
            <PointLatitude>-10</PointLatitude>
          </Point>
        </Boundary>
        <ExclusiveZone>
          <Boundary>
            <Point>
              <PointLongitude>-5</PointLongitude>
              <PointLatitude>-1</PointLatitude>
            </Point>
            <Point>
              <PointLongitude>-1</PointLongitude>
              <PointLatitude>-1</PointLatitude>
            </Point>
            <Point>
              <PointLongitude>-1</PointLongitude>
              <PointLatitude>-5</PointLatitude>
            </Point>
            <Point>
              <PointLongitude>-5</PointLongitude>
              <PointLatitude>-5</PointLatitude>
            </Point>
          </Boundary>
          <Boundary>
            <Point>
              <PointLongitude>0</PointLongitude>
              <PointLatitude>5</PointLatitude>
            </Point>
            <Point>
              <PointLongitude>5</PointLongitude>
              <PointLatitude>5</PointLatitude>
            </Point>
            <Point>
              <PointLongitude>5</PointLongitude>
              <PointLatitude>0</PointLatitude>
            </Point>
            <Point>
              <PointLongitude>0</PointLongitude>
              <PointLatitude>0</PointLatitude>
            </Point>
          </Boundary>
        </ExclusiveZone>
      </GPolygon>
      <Line>
        <Point>
          <PointLongitude>-50</PointLongitude>
          <PointLatitude>-50</PointLatitude>
        </Point>
        <Point>
          <PointLongitude>-40</PointLongitude>
          <PointLatitude>-40</PointLatitude>
        </Point>
      </Line>
      <Line>
        <Point>
          <PointLongitude>50</PointLongitude>
          <PointLatitude>50</PointLatitude>
        </Point>
        <Point>
          <PointLongitude>40</PointLongitude>
          <PointLatitude>40</PointLatitude>
        </Point>
      </Line>
    </Geometry>
  </HorizontalSpatialDomain>
  <VerticalSpatialDomain>
    <Type>Maximum Altitude</Type>
    <Value>100</Value>
  </VerticalSpatialDomain>
  <VerticalSpatialDomain>
    <Type>Minimum Altitude</Type>
    <Value>1</Value>
  </VerticalSpatialDomain>
  <OrbitParameters>
    <SwathWidth>22</SwathWidth>
    <Period>1</Period>
    <InclinationAngle>4</InclinationAngle>
    <NumberOfOrbits>1</NumberOfOrbits>
    <StartCircularLatitude>1</StartCircularLatitude>
  </OrbitParameters>
  <GranuleSpatialRepresentation>CARTESIAN</GranuleSpatialRepresentation>
</Spatial>

Column

width	50%

UMM

No Format

"SpatialExtent": {
  "SpatialCoverageType": "HORIZONTAL",
    "HorizontalSpatialDomain": {
      "ZoneIdentifier" : "1",
      "Geometry": {
        "CoordinateSystem": "CARTESIAN",
        "Points": [{
          "Longitude":-70, 
          "Latitude":-70
         }, {
          "Longitude":-65, 
          "Latitude":-65
         }],
        "BoundingRectangles": [{
          "WestBoundingCoordinate": -180.0, 
          "NorthBoundingCoordinate": 90.0, 
          "EastBoundingCoordinate": -170.3, 
          "SouthBoundingCoordinate": 80.1
        }],
        "GPolygons": [{
          "Boundary" : {
            "Points": [{
              "Longitude":-10, 
              "Latitude":-10
            }, {
              "Longitude":10, 
              "Latitude":-10
            }, {
              "Longitude":10, 
              "Latitude":10
            }, {
              "Longitude":-10, 
              "Latitude":10
            }, {
              "Longitude":-10, 
              "Latitude":-10
            }]
          },
          "ExclusiveZone": {
            "Boundaries": [{
              "Points": [{
                "Longitude":-5, 
                "Latitude":-5
              }, {
                "Longitude":-1, 
                "Latitude":-5
              }, {
                "Longitude":-1, 
                "Latitude":-1
              }, {
                "Longitude":-5, 
                "Latitude":-1
              }, {
                "Longitude":-5, 
                "Latitude":-5
              }]
            }, {
              "Points": [{
                "Longitude":0, 
                "Latitude":0
              }, {
                "Longitude":5, 
                "Latitude":0
              }, {
                "Longitude":5, 
                "Latitude":5
              }, {
                "Longitude":0, 
                "Latitude":5
              }, {
                "Longitude":0, 
                "Latitude":0
              }]
            }]
          }
        }],
        "Lines": [{
          "Points": [{
            "Longitude":-50, 
            "Latitude":-50
          }, {
            "Longitude":-40, 
            "Latitude":-40
          }]
        }, {
          "Points": [{
            "Longitude":50, 
            "Latitude":50
          }, {
            "Longitude":40, 
            "Latitude":40
          }]
        }]
      },
      "ResolutionAndCoordinateSystem": {
        "GeodeticDatum": {
          "HorizontalDatumName": "North American Datum 1983",
          "EllipsoidName": "GRS 1980",
          "SemiMajorAxis": "6378137",
          "DenominatorOfFlatteningRatio": "298.257222101"
        },        
        "HorizontalDataResolutionsHorizontalDataResolution": [{
          "HorizontalResolutionProcessingLevelEnumGenericResolution": [{
 "Non Gridded",
          "XDimension": 0.5,
            "YDimension": 0.5,
            "Unit": "Decimal Degrees"
          }]
        }
      }
    },
    "VerticalSpatialDomains": [{
      "Type": "Maximum Altitude", 
      "Value": "100"
    }, {
      "Type": "Minimum Altitude",
      "Value": "1"
    }
  ],
  "OrbitParameters": {
    "SwathWidth": 22,
    "Period": 1,
    "InclinationAngle": 4,
    "NumberOfOrbits": 1,
    "StartCircularLatitude": 1},
    "GranuleSpatialRepresentation": "CARTESIAN"
  },
  "GranuleSpatialRepresentation": "CARTESIAN"
},

Expand

title	ISO 19115-2 MENDS

ISO 19115-2 MENDS

UMM-C element	ISO 19115-2 MENDS Path	Type
SpatialExtent/SpatialCoverageType	Make sure the gmd:extent is a different extent then TilingInformationSystem /gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent id="boundingExtent"/gmd:description/gco:CharacterString SpatialCoverageType=	String
SpatialExtent/ HorizontalSpatialDomain/ZoneIdentifier	/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent id="boundingExtent"/gmd:geographicElement/gmd:EX_GeographicDescription id="ZoneIdentifier"/gmd:geographicIdentifier/gmd:MD_Identifier/gmd:code/gco:CharacterString	String
	/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent id="boundingExtent"/gmd:geographicElement/gmd:EX_GeographicDescription id="ZoneIdentifier"/gmd:geographicIdentifier/gmd:MD_Identifier/gmd:codeSpace/gco:CharacterString = gov.nasa.esdis.umm.zoneidentifier	String
	/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent id="boundingExtent"/gmd:geographicElement/gmd:EX_GeographicDescription id="ZoneIdentifier"/gmd:geographicIdentifier/gmd:MD_Identifier/gmd:description/gco:CharacterString = ZoneIdentifier	String
SpatialExtent/HorizontalSpatialDomain/ Geometry/CoordinateSystem	/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent id="boundingExtent" /gmd:description/gco:CharacterString CoordinateSystem=	String
SpatialExtent/ GranuleSpatialRepresentation	/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent id="boundingExtent"/gmd:description/gco:CharacterString SpatialGranuleSpatialRepresentation= (CMR read only) If the above path does not exist then look here: /gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent id="boundingExtent" /gmd:geographicElement/gmd:EX_GeographicDescription id="GranuleSpatialRepresentation"/gmd:geographicIdentifier/gmd:MD_Identifier/gmd:code/gco:CharacterString	String

Choice of one of the following for Horizontal Spatial Domain/ Geometry:

(1) Point

If Point is selected, the cardinality is 1..*

UMM-C Element

ISO 19115-2 MENDS Path

Type

Notes

SpatialExtent/HorizontalSpatialDomain/

Geometry/Point/Longitude

/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent id="boundingExtent"/gmd:geographicElement/gmd:EX_BoundingPolygon/gmd:polygon/gml:Point/

gml:pos srsName="http://www.opengis.net/def/crs/EPSG/4326" srsDimension="2">Latitude + " " + Longitude

Decimals as strings

Latitude first then longitude for every point. No commas just spaces. ex: -10 -10

SpatialExtent/HorizontalSpatialDomain/

Geometry/Point/Latitude

(2) Bounding Rectangle

If BoundingRectangle is selected, the cardinality is 1..*

UMM-C Element	ISO 19115-2 MENDS Path	Type
SpatialExtent/HorizontalSpatialDomain/ Geometry/BoundingRectangles/ WestBoundingCoordinate	/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent id="boundingExtent"/gmd:geographicElement/gmd:EX_GeographicBoundingBox/gmd:westBoundLongitude/gco:Decimal	Decimal
SpatialExtent/HorizontalSpatialDomain/ Geometry/BoundingRectangles/ NorthBoundingCoordinate	/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent id="boundingExtent"/gmd:geographicElement/gmd:EX_GeographicBoundingBox/gmd:northBoundLongitude/gco:Decimal	Decimal
SpatialExtent/HorizontalSpatialDomain/ Geometry/BoundingRectangles/ EastBoundingCoordinate	/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent id="boundingExtent"/gmd:geographicElement/gmd:EX_GeographicBoundingBox/gmd:eastBoundLongitude/gco:Decimal	Decimal
SpatialExtent/HorizontalSpatialDomain/ Geometry/BoundingRectangles/ SouthBoundingCoordinate	/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent id="boundingExtent"/gmd:geographicElement/gmd:EX_GeographicBoundingBox/gmd:southBoundLongitude/gco:Decimal	Decimal

(3) Line

If Line is selected, the cardinality is 2..* since at least 2 points must be provided to create a Line.

UMM-C Element

ISO 19115-2 MENDS Path

Type

Notes

SpatialExtent/HorizontalSpatialDomain/

Geometry/Lines/Points/Longitude

/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/

gmd:EX_Extent id="boundingExtent"/gmd:geographicElement/gmd:EX_BoundingPolygon/

gmd:polygon/gml:LineString/gml:posList srsName="http://www.opengis.net/def/crs/EPSG/4326" srsDimension="2">

Decimals as strings

Latitude first then longitude for every point. No commas just spaces. The following example has 2 lines: -10 -10 -10 10 10 10 10 -10

SpatialExtent/HorizontalSpatialDomain/

Geometry/Lines/Points/Latitude

(4) GPolygon

If GPolygon is selected, the cardinality is 1..*

UMM-C Element	ISO 19115-2 MENDS Path	Type	Notes
SpatialExtent/HorizontalSpatialDomain/ Geometry/GPolygon/Boundary/ Points/Longitude	/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/ gmd:EX_Extent id="boundingExtent"/gmd:geographicElement/gmd:EX_BoundingPolygon /gmd:polygon/gml:Polygon srsName="http://www.opengis.net/def/crs/EPSG/9825" /gml:exterior/gml:LinearRing/gml:posList	Decimals as Strings	Latitude first then longitude for every point. No commas just spaces. ex: -10 -10 -10 10 10 10 10 -10 -10 -10
SpatialExtent/HorizontalSpatialDomain/ Geometry/GPolygon/Boundary /Points/Latitude		Decimals as Strings
SpatialExtent/HorizontalSpatialDomain/Geometry/ GPolygon/ExclusiveZone/Boundaries/ Points/Longitude	/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/ gmd:EX_Extent id="boundingExtent"/gmd:geographicElement/gmd:EX_BoundingPolygon/ gmd:polygon/gml:Polygon srsName="http://www.opengis.net/def/crs/EPSG/9825"/ gml:interior/gml:LinearRing/gml:posList	Decimals as Strings	Latitude first then longitude for every point. No commas just spaces. ex: -5 -5 -5 5 5 5 5 -5 -5 -5
SpatialExtent/HorizontalSpatialDomain/Geometry /GPolygon/ExclusiveZone/Boundaries/ Points/Latitude		Decimals as Strings

Resolution And Coordinate System:

UMM-C Element

ISO 19115-2 MENDS Path

Type

SpatialExtent/HorizontalSpatialDomain/Description

[=> /gmd:geographicElement/gmd:EX_GeographicDescription id="horizontalresolutionandcoordinatesystem_description"/gmd:geographicIdentifier/gmd:MD_Identifier/gmd:code/gco:CharacterString = Description: description
with
[=>/gmd:geographicElement/gmd:EX_GeographicDescription/gmd:geographicIdentifier/gmd:MD_Identifier/gmd:codeSpace/gco:CharacterString = gov.nasa.esdis.umm.horizontalresolutionandcoordinatesystem_description
and
[=>/gmd:geographicElement/gmd:EX_GeographicDescription/gmd:geographicIdentifier/gmd:MD_Identifier/gmd:description/gco:CharacterString = HorizontalResolutionAndCoordinateSystem_Description

String