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.
The Spatial Coverage Type field is required for Spatial Information. This field is used to specify whether the 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 providing one of the spatial coverage type enumeration values:
HORIZONTALEARTH/GLOBAL, HORIZONTAL, VERTICAL, ORBITAL, HORIZONTAL_VERTICAL, ORBITAL_VERTICAL, HORIZONTAL_ORBITAL, HORIZONTAL_VERTICAL_ORBITAL, LUNAR
Horizontal Vertical 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 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
- 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:
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:
Examples
Example 1:
SpatialCoverageType: "HORIZONTAL_VERTICAL"
HorizontalCoordinateSystem/GeodeticModel/HorizontalDatumName: "World Geodetic System 1984"
HorizontalCoordinateSystem/GeodeticModel/EllipsoidName: "WGS 84"
HorizontalCoordinateSystem/GeodeticModel/SemiMajorAxis: "6378137"
HorizontalCoordinateSystem/GeodeticModel/DenominatorOfFlatteningRatio: "298.257223563"
HorizontalCoordinateSystem/GeographicCoordinateSystem/GeographicCoordinateUnits: "Decimal Degrees"
HorizontalCoordinateSystem/GeographicCoordinateSystem/LatitudeResolution: "0.05"
HorizontalCoordinateSystem/GeographicCoordinateSystem/LongitudeResolution: "0.05"
VerticalCoordinateSystem/AltitudeSystemDefinition/DatumName: "National Geodetic Vertical Datum 1929"
VerticalCoordinateSystem/AltitudeSystemDefinition/DistanceUnits: "Kilometers"
VerticalCoordinateSystem/AltitudeSystemDefinition/Resolutions: "5"
SpatialCoverageType: "HORIZONTAL_VERTICAL"
HorizontalCoordinateSystem/GeodeticModel/HorizontalDatumName: "Easter Island 1967"
HorizontalCoordinateSystem/GeodeticModel/EllipsoidName: "International 1924"
HorizontalCoordinateSystem/GeodeticModel/SemiMajorAxis: "6378388"
HorizontalCoordinateSystem/GeodeticModel/DenominatorOfFlatteningRatio: "297"
HorizontalCoordinateSystem/GeographicCoordinateSystem/GeographicCoordinateUnits: "Decimal Degrees"
HorizontalCoordinateSystem/GeographicCoordinateSystem/LatitudeResolution: "0.01"
HorizontalCoordinateSystem/GeographicCoordinateSystem/LongitudeResolution: "0.01"
VerticalCoordinateSystem/DepthSystemDefinition/DatumName: "Mean Sea Level"
VerticalCoordinateSystem/DepthSystemDefinition/DistanceUnits: "Fathoms"
VerticalCoordinateSystem/DepthSystemDefinition/Resolutions: "1"
Note: There are 2 Spatial Information fields that the CMR supports but are not currently included in the schema. These fields also do not currently map to or from any other metadata dialects. Support for these elements will be provided in the future. These fields are 'Latitude Resolution' and 'Longitude Resolution'.
Examples:
LatitudeResolution: 300 m
LongitudeResolution: 300 m
LatitudeResolution: 34 km
LongitudeResolution: 30 km
Element Specification
Providing Spatial Information is optional. Spatial Information can only be provided once (Cardinality: 0..1)
1 - 80 characters
Highly recommend providing one of the following enumeration values:
HORIZONTAL
VERTICAL
ORBITAL
HORIZONTAL_VERTICAL
ORBITAL_VERTICAL
1 - 80 characters
HectoPascals
Kilometers
Millibars
Fathoms
Feet
HectoPascals
Meters
Millibars
Decimal Degrees
Kilometers
Meters
Number
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).
Please see the expandable sections below for flowchart details.
title | GCMD Metadata QA/QC |
---|
Expand | ||
---|---|---|
| ||
<> |
title | ARC Metadata QA/QC |
---|
This element is categorized as highest priority when:
- Spatial Information is provided but the required 'Spatial Information Type' field is not included.
- An invalid value is provided for 'Distance Units'. 'DistanceUnits' must be selected from an enumeration list.
- An invalid value is provided for 'GeographicCoordinateUnits'. 'GeographicCoordinateUnits' must be selected from an enumeration list.
- The information provided is incorrect for the dataset.
Not applicable
This element is categorized as low priority when:
- A recommendation is made to add the Horizontal Datum Name in the metadata.
- A recommendation is made to provide any additional information to existing Spatial Information provided in the metadata.
ARC Automated Rules
If novalue is provided, return is "np."- 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 | ||
---|---|---|
| ||
DIF 9 (Note: DIF-9 is being phased out and will no longer be supported after 2018) |
- . 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.
- 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.
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 | ||
---|---|---|
| ||
|
Expand | ||
---|---|---|
| ||
None |
Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
ARC Automated Checks ARC uses the pyQuARC library for automated metadata checks. Please see the pyQuARC GitHub for more information. |
Dialect Mappings
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
DIF 10Providing 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.
|
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ECHO 10Providing the Spatial Info element is optional in ECHO 10 (Cardinality: 0..1)
|
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 |
title | 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 field in DIF 10. 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.
Horizontal
HorizontalVertical
Orbit
Vertical
Horizon&Vert
String
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.
Horizontal
HORIZONTAL
Section | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
title | ECHO 10 |
---|
ECHO 10
Providing the Spatial Info element is optional in ECHO 10 (Cardinality: 0..1)
1 - 80 characters
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)
1 - 80 characters
1 - 80 characters
1 - 2048 characters
The means used to encode measurements.
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.1 - 80 characters
1 - 80 characters
1 - 2048 characters
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.1 - 80 characters
1 - 255 characters
1 - 80 characters
Units of measure used for the geodetic latitude and longitude resolution values. E.g. Decimal Degrees or Degrees Minutes Seconds.
For lat, a 2 digit decimal number from 0-90
+ or absence of - for values north of equator; - for all others.
For lon, a 3 digit decimal number from 0-180
+ or absence of - for values west of prime meridian; - for all others.
1 - 2048 characters
1 - 2048 characters
Section | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
title | ISO 19115-2 MENDS |
---|
ISO 19115-2 MENDS
Section | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
title | ISO 19115-2 SMAP |
---|
ISO 19115-2 SMAP
Section | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
UMM Migration
Future Mappings
title | ISO 19115-1 |
---|
ISO 19115-1
Section | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
History
UMM Versioning
Information during the transition from version 1.11.0 to 1.12.0. | |
1.11.0 | 2018-11 |
-28 |
No changes were made for Spatial |
Information during the transition from version 1.10.0 to 1.11.0. | |
1.10.0 | 2018-05 |
-02 |
During the transition from version 1.9.0 to 1.10.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 |