You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Element Description

Track is a recently added element that is only available at the granule 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 (SWOT) mission managed by NASA's PO.DAAC data center. The Track element can be used to describe 3 sub-components:

  1. Cycle: A cycle encompasses data from 1 full day of orbits.
  2. Pass: A pass includes data from a half-orbit.
  3. 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

Track is an optional element in the UMM-G (Cardinality: 0..*)

ModelElementTypeConstraintsRequired?Cardinality
UMM-GSpatialExtent/TrackString

N/A

Yes



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.


  • Manual Review
  • Automated Review

<>

ARC Priority Matrix

Priority CategorizationJustification

This element is categorized as highest priority when:

  • The Spatial Extent-Track is not provided.
  • The Spatial Extent-Track does not comply with the ISO 8601 Standard.

Not Applicable


Not Applicable


The element is provided and follows all applicable criteria specified in the best practices section above.

ARC Automated Rules

Dialect Mappings

ECHO 10

Production Date Time is required for ECHO 10.

SpecificationPathTypeConstraintsRequired in ECHO10?Cardinality
ECHO 10SpatialExtent/TrackString

N/A

Yes1


Example Mapping

ECHO 10

<Track>Pass</Track>

UMM

"DataGranule": {
  "Track" : "Cycle"
}

ISO 19115-2 MENDS

Spatial Extent-Track currently does not map to ISO 19115-2 MENDS.

SpecificationPathTypeNotes
ISO 19115-2 MENDS

N/A

String

N/A


Example Mapping

ISO 19115-2 MENDS

N/A
 

UMM

"DataGranule": {
  "Track" : "Cycle"
}

ISO 19115-2 SMAP

Spatial Extent-Track currently does not map to ISO 19115-2 SMAP.

SpecificationPathTypeNotes
ISO 19115-2 SMAP

N/A

N/A

N/A


Example Mapping

ISO 19115-2 SMAP

N/A

UMM

"DataGranule": {
  "Track" : "Cycle"
}

UMM Migration

UMM Version 1.4.0Translation DirectionUMM Version 1.5.0



Future Mappings

ISO 19115-1

Spatial Extent-Track currently does not map to ISO 19115-1.

SpecificationPathTypeNotes
ISO 19115-1

N/A

N/A

N/A


Example Mapping

ISO 19115-1

N/A

UMM

"DataGranule": {
  "Track" : "Cycle"
}

History

UMM Versioning

VersionDateWhat Changed
1.5.001/30/2019No changes were made for Spatial Extent-Track during the transition from version 1.4.0 to 1.5.0.
1.4.008/01/2018No changes were made for Spatial Extent-Track during the transition from version 1.3.0 to 1.4.0.

ARC Documentation

VersionDateWhat ChangedAuthor
1.002/15/2019Recommendations/priority matrix transferred from internal ARC documentation to wiki space
  • No labels