Element Description
The Spatial Extent element describes the geographic extent or coverage of data provided in a file or in a data collection.
Best Practices
In the CMR, the spatial extent of data may be specified as a horizontal spatial domain, a vertical spatial domain, or an orbital spatial domain. The type of spatial domain 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' in UMM-Common. These include:
- Horizontal
- Vertical
- Orbital
- Horizontal and Vertical
- Orbital and Vertical
Each spatial domain requires different information. These are summarized below:
Horizontal
Horizontal spatial extent refers to the surface area of the Earth covered by data. For horizontal spatial extent, coverage must be specified as either Cartesian or Geodetic via the Coordinate System element:
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 expressing 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 both 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 as expressed with 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 that -90 degrees, the west bounding coordinate may not be smaller 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.
Vertical
Vertical spatial extent can be used to describe 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, it is required to provide an accompanying value in the SpatialExtent/VerticalSpatialDomain/Value field. For example, the Type selected could be "Maximum Altitude" and the corresponding Value could be "50 KM".
Orbital
When data is systematically collected via satellite, there is the option to describe the spatial coverage of the data by specifying the orbital characteristics of the satellite platform. The Orbital spatial domain includes the following sub-elements:
Swath Width: R
Period: R
Inclination Angle: R
Number of Orbits: R
Start Circular Latitude:
Examples:
Element Specification
Model | Element | Type | Usable Valid Values | Required? | Cardinality |
---|---|---|---|---|---|
UMM-C | CollectionProgress | Enumeration | PLANNED ACTIVE COMPLETE NOT APPLICABLE | Yes | 1 |
Value needed for translations:
The following value is needed by the CMR to translate older non UMM compliant records to and from the UMM and other supported specifications where non required elements are considered required but no valid is given. This is needed partly because the CMR still allows a non UMM compliant record to be ingested with warnings.
NOT PROVIDED - It is necessary for this value to exist so that the CMR can translate older non UMM compliant records into the latest UMM specification where CollectionProgress is required. This value should not be used by metadata providers.
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.
Dialect Mappings
UMM Migration
UMM Version 1.9.0 | Translation Direction | UMM Version 1.10.0 |
---|---|---|
PLANNED | ↔ | PLANNED |
IN WORK | ↔ | ACTIVE |
COMPLETE | ↔ | COMPLETE |
NOT APPLICABLE | ↔ | NOT APPLICABLE |
NOT PROVIDED | ↔ | NOT PROVIDED |
Any other value | → | NOT PROVIDED |
Future Mappings
History
UMM Versioning
Version | Date | What Changed |
---|---|---|
1.10.0 | Changes would be tracked here | |
1.9.0 |
ARC Documentation
Version | Date | What Changed | Author |
---|---|---|---|
1.0 | 2/19/18 | Recommendations/priority matrix transferred from internal ARC documentation to wiki space |