Page History
Table of Contents | ||
---|---|---|
|
Element Description
Spatial Extent-Track is a recently added element that will be assigned is only available at the granule level only. The first campaign that will use this element will be level. The Track element provides orbit information for data collected via satellite including Cycle, Pass and Tiles. This allows for file level searches by Track information.
Best Practices
The Track element was initially designed to support the Surface Water and Ocean Topography , or (SWOT, ) mission managed by NASA's PO.DAAC . It will then be expanded to other future projects.
Best Practices
In an effort to make searching for data easier, granules will eventually have the ability to be searched by their orbit information using the following terms: cycle, pass, and tiles. A cycle will encompassdata center. The Track element can be used to describe 3 sub-components:
- Cycle: A cycle encompasses data from 1 full day of orbits
- .
- Pass: A pass includes data from a half-orbit.
- Tiles: Here, a tile is defined as a 64 km x 64 km square to the left and right of the ground track
- . A set of consecutive tiles make up a pass.
Examples:
Element Specification
Spatial Extent-Track is required an optional element in the UMM-G (Cardinality: 0..*)
Model | Element | Type | Constraints | Required? | Cardinality | |
---|---|---|---|---|---|---|
UMM-G | SpatialExtent/Track | String | N/A | Yes | 1
Metadata Validation and QA/QC
All metadata entering the CMR goes through the below process to ensure metadata quality requirements are met. All records undergo CMR validation before entering the system. The process of QA/QC is slightly different for NASA and non-NASA data providers. Non-NASA providers include interagency and international data providers and are referred to as the International Directory Network (IDN).
Lucidchart rich-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 | ||
---|---|---|
| ||
<> |
Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
ARC Automated Rules |
Dialect Mappings
Expand | ||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||
ECHO 10Production Date Time is required for ECHO 10.
|
Expand | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||
ISO 19115-2 MENDSSpatial Extent-Track currently does not map to ISO 19115-2 MENDS.
|
Expand | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||
ISO 19115-2 SMAPSpatial Extent-Track currently does not map to ISO 19115-2 SMAP.
|
UMM Migration
UMM Version 1.4.0 | Translation Direction | UMM Version 1.5.0 |
---|---|---|
Future Mappings
Expand | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||
ISO 19115-1Spatial Extent-Track currently does not map to ISO 19115-1.
|
History
UMM Versioning
Version | Date | What Changed |
---|---|---|
1.5.0 | 01/30/2019 | No changes were made for Spatial Extent-Track during the transition from version 1.4.0 to 1.5.0. |
1.4.0 | 08/01/2018 | No changes were made for Spatial Extent-Track during the transition from version 1.3.0 to 1.4.0. |
ARC Documentation
Version | Date | What Changed | Author |
---|---|---|---|
1.0 | 02/15/2019 | Recommendations/priority matrix transferred from internal ARC documentation to wiki space |