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

Compare with Current View Page History

« Previous Version 12 Next »

Element Description

The Input Granules element provides identification of other granule(s) that were used to generate the granule. 


Best Practices

The Input Granules element can be used to identify other granule(s) (i.e. data files) that were used to generate the granule data. For instance, this could be used to specify a granule from a lower level data product that were used to generate the granule. For fusion products, this element can be used list the granules which were fused together to create the resulting granule. Providing Input Granules is optional, but can be leveraged to clearly identify inputs to the file being described (when applicable). It is recommended that the Granule UR, or another unique granule identifier, be used to specify the input granule.    


Examples:

Example 1: A level 2 MODIS granule with UR "MOD09.A2019105.0045.006.2019106025523.hdf" provides atmospherically corrected surface reflectance. The granule was generated by processing the following level 1B input granule:Example 2: A Digital Elevation Model (DEM), a land use/ land cover file, and a land surface temperature file were fused together to create a data file containing all 3 properties:

Input Granule: MOD021KM.A2019105.0045.006.2019105134947.hdf

Input Granule: DEM_feb01_srtm_30m.tif

Input Granule: landsat7_03072019_123456_landclass_30m.tif

Input Granule: landsat7_surfTemp_03072019_123456_30m.tif



Element Specification

The Input Granules element is optional, and may be repeated (Cardinality: 0..*)

ModelElementTypeConstraintsRequired?CardinalityNotes
UMM-GInputGranules/InputGranule

Array composed of:

Strings

1 - 500 characters

No0..*Each array provided should be unique (i.e. the same input granule should not be provided more than once)



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. 


<>

ARC Priority Matrix

Priority CategorizationJustification

This element is categorized as highest priority when:

    • The information provided is incorrect for the granule

Not Applicable


Not Applicable


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

ARC Automated Rules

  • If no value is provided, return is "np."
  • Otherwise, return is "OK."

Dialect Mappings

ECHO 10

The Input Granules element is optional in ECHO 10, and may be repeated (Cardinality: 0..*)

UMM-G ElementECHO 10 PathTypeConstraintsRequired in ECHO10?Cardinality
InputGranules/InputGranuleInputGranules/InputGranuleString

1 - 255 characters

No0..*


Example Mapping

ECHO 10

<InputGranules>  
  <InputGranule>VNP02DNB_NRT.A2019106.1812.001.2019106194334.nc</InputGranule>
</InputGranules>

UMM

InputGranules: {
    InputGranule: "VNP02DNB_NRT.A2019106.1812.001.2019106194334.nc"
},

ISO 19115-2 MENDS

The Input Granule element is optional in ISO-19115-2 (Cardinality: 0..*)

UMM-G ElementISO PathTypeNotes
InputGranule/gmi:MI_Metadata/gmd:dataQualityInfo/gmd:DQ_DataQuality/gmd:lineage/gmd:LI_Lineage/gmd:source [=>
[=>gmi:LE_Source/gmd:description/gco:CharacterString = GranuleInput
[=>/gmi:LE_Source/gmd:sourceCitation/gmd:CI_Citation/gmd:title/gmx:FileName src= {the actual InputGranule Value}
[=>/gmi:LE_Source/gmd:sourceCitation/gmd:CI_Citation/gmd:date gco:nilReason="unknown"

String

The "gmd:date gco:nilReason="unknown" path is present because it is required by ISO, but not needed by the CMR.



Example Mapping

ISO 19115-2 MENDS

<gmi:MI_Metadata>
  <gmd:dataQualityInfo>
    <gmd:DQ_DataQuality>
      <gmd:lineage>
        <gmd:LI_Lineage>
          <gmd:source>
            <gmi:LE_Source>
              <gmd:description>
                <gco:CharacterString>GranuleInput</gco:CharacterString>
              </gmd:description>
              <gmd:sourceCitation>
                <gmd:CI_Citation>
                  <gmd:title>
                    <gmx:FileName src="VNP02DNB_NRT.A2019106.1812.001.2019106194334.nc"/>

                  </gmd:title>
                  <gmd:date gco:nilReason="unknown"/>
                </gmd:CI_Citation>
              </gmd:sourceCitation>
            </gmi:LE_Source>
          </gmd:source>
        </gmd:LI_Lineage>
      </gmd:lineage>
    </gmd:DQ_DataQuality>
  </gmd:dataQualityInfo>
</gmi:MI_Metadata>

UMM

InputGranules: {
    InputGranule: "VNP02DNB_NRT.A2019106.1812.001.2019106194334.nc"
},

ISO 19115-2 SMAP

There is currently no mapping between UMM-G and ISO 19115-2 SMAP for Input Granules.

UMM-G ElementISO PathTypeNotes
InputGranule

N/A

N/A

N/A


Example Mapping

ISO 19115-2 SMAP

N/A

UMM

N/A

UMM Migration

UMM Version 1.4.0Translation DirectionUMM Version 1.5.0




History

UMM Versioning

VersionDateWhat Changed
1.5.001/30/2019No changes were made for Input Granules during the transition from version 1.4.0 to 1.5.0.
1.4.008/01/2018No changes were made for Input Granulesduring the transition from version 1.3.0 to 1.4.0.

ARC Documentation

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