Page History

Table of Contents

style	circle

Element Description

Spatial Extent-The Track element provides orbit information for data collected via satellite including Cycle, Pass, and Tiles. This allows for file level searches on these orbital parameters. 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

Best Practices

The Track element was designed to support the Surface Water and Ocean Topography , or (SWOT, ) mission managed by NASA's PO.DAAC . However, it will eventually be expanded to other future projects. data center, however, this concept can be applied to any data that can be described using orbital cycles, passes, and tiles. There are three main components to the Track element:

Cycle: A cycle is an integer that represents data from a specific set of satellite orbits. What constitutes a full cycle will vary from mission to mission. Typically, a cycle includes a full set of spatially varied data - a new cycle indicates that the spatial pattern of data collection is being repeated. For example, for the SWOT mission, a cycle is equivalent to 21 days of data made up of 14 full Earth orbits per day. Each of these orbits covers a slightly different spatial extent, and the exact same spatial area is not covered again until the next cycle. The cycle number also inherently includes a temporal component, since each cycle number indicates the passage of time (i.e. data from the 2nd cycle is collected after the 1st cycle, etc.).
Pass: A pass includes data from a half-orbit. Each spatially unique pass should be assigned a unique identifier, and thus, the pass is represented by an integer. Each pass is made up of a number of tiles, which are assigned identifiers based on their unique spatial location. A granule may be comprised of data from a single pass, or multiple passes.
Tiles: A tile is a subset of a pass' spatial extent. A set of consecutive tiles make up a pass. Each spatially unique tile has a unique identifier. The tile element holds the list of tile identifier(s) that exist in the granule, allowing a user to search by tile identifier. What constitutes a tile will vary from mission to mission. For example, for the SWOT mission, a tile is defined as a spatial extent that encompasses either a 64 km x 64 km square to the left or to the right of the ground track, or a rectangle that includes a full scanning swath both to the left and right of the ground track.

Each tile is contained within a pass (half-orbit), which is contained within a cycle. There will only be one instance of a particular pass number and tile identifier in a given cycle, therefore, the combination of tile, pass, and cycle can be used to constrain a data search.

Examples:

Example 1: A granule from cycle 1 containing 2 passes, where each pass includes 12 tiles

A granule from cycle 12, containing 4 passes, where each pass contains 4 tiles

Track:

Cycle: 1

Passes:

Pass: 34

Tiles: ["396", "397", "398", "399", "400", "401", "402", "403", "404", "405", "406", "407"]

Pass: 35

Tiles: ["408", "409", "410", "411", "412, "413", "414", "415", "416", "417", "418", "419"]

Track:

Cycle: 12

Passes:

Pass: 1

Tiles: ["1L", "2R", "3L", "4R"]

Pass: 2

Tiles: ["5L", "6R", "7L", "8R"]

Pass: 3

Tiles: ["9L", "10R", "11L", "12R"]

Pass: 4

Tiles: ["13L", "14R", "15L", "16R"]

Element Specification

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

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 encompass data from a days worth of orbits while a pass will only be a half-orbit.

Examples:

Element Specification

... is required (Cardinality: 0..*)

Model	Element	Type	Constraints	Required?	Cardinality	Notes
UMM-G	SpatialExtent/Track/Cycle	Integer	n/a	Yes, if applicable	1	Track is an optional metadata element. If provided, it is required that cycle, pass information be included.
UMM-G	SpatialExtent/Track/Passes/Pass

String

Integer

N/A

n/a	Yes, if applicable	1..*	A minimum of 1 pass number must be provided.
UMM-G	SpatialExtent/Track/Passes/Tiles	Array composed of Strings	n/a	No	0..*	Listing the tile identifiers within a pass is optional, but highly recommended.

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

title	GCMD Metadata QA/QC

Manual Review
Automated Review

Expand

title	CMR Validation

<>

Expand

title	ARC Metadata QA/QC

ARC Priority Matrix

Not Applicable

Priority Categorization	Justification
Red = High Priority Finding	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. information provided does not align with the granule data. The Track is provided but either Cycle or Pass are missing. Both Cycle and Pass must be provided in the Track element.
Yellow = Medium Priority Finding	Not Applicable
Blue = Low Priority Finding	This element is categorized as low priority when: No Tiles are listed under Pass.
Green = No Findings/Issues	Not Applicable	The element is provided and follows all applicable criteria specified in the best practices section above.

ARC Automated RulesChecks

ARC uses the pyQuARC library for automated metadata checks. Please see the pyQuARC GitHub for more information.

Dialect Mappings

Example Mapping

Expand

title	ECHO 10

ECHO 10

Production Date Time is required for ECHO 10.

Specification

Path

Type

Constraints

Required in ECHO10?

Cardinality

ECHO 10

GranuleLocality/Locality Value

String

N/A

Yes

1

Section

Column

width	50%

ECHO 10

No Format
<LocalityValue>Global</LocalityValue>

Column

width	50%

UMM

No Format"DataGranule": { "Granule Locality" : "Global" }

The Track element does not exist in ECHO 10.

Example Mapping

None, since ECHO 10 doesn't support the Track element.

Expand

title	ISO 19115-2 MENDS

ISO 19115-2 MENDS

The path where Granule Locality is provided in ISO is optional, however, a Granule Locality is required for all CMR granule metadata (Cardinality: 0..1)

Spatial Extent - Track is optional in ISO 19115-2 MENDS.

typegmd:MD_KeywordTypeCode codeList="https://cdn.earthdata.nasa.gov/iso/resources/Codelist/gmxCodelists.xml#MD_KeywordTypeCode" codeListValue="place" = placeMaps to the UMM element "GranuleLocalities"

UMM-G ElementSpecification	Path	Type	Notes
ISO 19115-2 MENDSSpatialExtent/Track	/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:descriptiveKeywordsextent/gmd:MD_KeywordsEX_Extent id="boundingExtent" [=> [=>/gmd:keywordgeographicElement/gco:CharacterString /gmi:MI_Metadatagmd:EX_GeographicDescription id="Track"/gmd:identificationInfogeographicIdentifier/gmd:MD_DataIdentificationIdentifier[==> [==>/gmd:descriptiveKeywordsdescription/gco:CharacterString = Track and [==>/gmd:MD_KeywordscodeSpace/gmd:keywordgco:CharacterString = gov.nasa.esdis.umm.track	String	N/A
SpatialExtent/Track/Cycle	[==>/gmd:	code/	String	gco:CharacterString = "Cycle: {value}"	String	Cycle, Pass and Tiles are all provided in the "gmd:code" field. Cycle and Pass are differentiated by the "Cycle: " and "Passes: " prefixes. List the cycle number after the "Cycle: " prefix.
SpatialExtent/Track/Passes/Pass	[==>/gmd:code/gco:CharacterString = "Passes: [pass1 [tiles 1] pass2 [tiles 2]]"	String	Cycle, Pass and Tiles are all provided in the "gmd:code" field. Cycle and Pass are differentiated by the "Cycle: " and "Passes: " prefixes. Provide the first pass number in square brackets after the "Passes: " prefix. To list a set of Tiles within a Pass, open a second set of square brackets right after the Pass number and list the Tiles as an array. To list a second Pass number, close the second set of square brackets (containing the Tiles from the first pass) and then list the second Pass number. Repeat this pattern as many times as needed to provide all Passes and Tiles contained within the granule.
SpatialExtent/Track/Passes/Tiles	(see above)	String

Example Mapping

Section

Column

width	50%

ISO 19115-2 MENDS

No Format

<gmi:MI_Metadata>
  <gmd:identificationInfo>
    <gmd:MD_DataIdentification>
      <gmd:descriptiveKeywords>
extent>
        <gmd:EX_Extent> id="boundingExtent"
        ...
          <gmd:geographicElement>
            <gmd:EX_GeographicDescription> id="Track"
              <gmd:geographicIdentifier>
                <gmd:MD_Keywords>
Identifier>
                  <gmd:keyword>description>
                    <gco:CharacterString>Granule Localities<:CharacterString>Track</gco:CharacterString>
                  </gmd:description>
                  <gmd:codeSpace>
                    <gco:CharacterString>gov.nasa.esdis.umm.track</gco:CharacterString>
                  </gmd:description>
:codeSpace>
                  <gmd:code>
                    <gco:String>Global<:CharacterString>Cycle:4 Passes:[13["1T", "2T", "3T", "4T"]14["5T", "6T", "7T", "8T"]]</gco:String>CharacterString>
                  </gmd:keyword>code>
                </gmd:MD_Keywords>Identifier>
              </gmd:geographicIdentifier>
            </gmd:EX_GeographicDescription>
          </gmd:descriptiveKeywords>geographicElement>
         ...
        </gmd:MDEX_DataIdentification>Extent>
      </gmd:identificationInfo>extent>
    </gmd:MD_DataIdentification>
  </gmd:identificationInfo>
</gmi:MI_Metadata>

Column

width	50%

UMM

No Format

"DataGranule": {
  "Granule Locality" : "Global"
}"SpatialExtent": {
    ...
      },
      "Track": {
        "Cycle": 4,
        "Passes": [
        {
          "Pass": 13,
          "Tiles": ["1T", "2T", "3T", "4T"]
        }, 
        {
          "Pass": 14,
          "Tiles": ["5T", "6T", "7T", "8T"]
        }
      ]
    }
  },

Expand

title	ISO 19115-2 SMAP

ISO 19115-2 SMAP

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

Specification	Path	Type	Notes
ISO 19115-2 SMAP	N/A	N/A	N/A

Example Mapping

Section

Column

width	50%

ISO 19115-2 SMAP

No Format
N/A

Column

width	50%

UMM

No Format
"DataGranule": { "Granule Locality" : "Global" }

UMM Migration

UMM Version 1.4.0	Translation Direction	UMM Version 1.5.0

Excerpt

hidden	true

Future Mappings

Expand

title	ISO 19115-1

ISO 19115-1

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

Specification	Path	Type	Notes
ISO 19115-1	N/A	N/A	N/A

Example Mapping

Section

Column

width	50%

ISO 19115-1

No Format
N/A

Column

width	50%

UMM

No Format
"DataGranule": { "

Granule Locality

Track" : "

2009-12-14T00:00:00Z

Cycle"
}

History

UMM Versioning

Version	Date	What Changed
1.

5

6.0

01

11/

30

4/2019

No changes were made

for Spatial Extent-Track

for Track during the transition from version 1.

4

5.0 to 1.

5

6.0.

1.

4

5.0

08

01/

01

30/

2018

2019	The Track element was added to the UMM-G schema

No changes were made for Spatial Extent-Track

during the transition from version 1.

3

4.0 to 1.5.0.
1.4.0	08/01/2018	Track was not available in version 1.4.0.

ARC Documentation

Version	Date	What Changed	Author
1.0	04/02/15/2019	Recommendations/priority matrix transferred from internal ARC documentation to wiki space	Camille Woods Jeanne' le Roux

Page tree

Versions Compared

Old Version 3

New Version Current

Key

Element Description

Best Practices

Element Specification

Best Practices

Element Specification

Metadata Validation and QA/QC

Dialect Mappings

ECHO 10

ISO 19115-2 MENDS

ISO 19115-2 SMAP

UMM Migration

Future Mappings

ISO 19115-1

History

UMM Versioning

ARC Documentation