Page History
Table of Contents | ||
---|---|---|
|
Element Description
The archive Archive and distribution information main element allows data providers to provide users information of what is available for downloading when they initially looking at a collection. The end users get elements provide information about a format other than its original for data immediately available for download. This includes information such as the average downloadable file size, data format, mime type, checksum, etc., and an estimate of the collections collection's entire downloadable file size, etc.
Best Practices
Instrument keywords are important for the discovery of data. All relevant instruments should be listed for each dataset, and each instrument listed should be provided under its associated platform. It is preferred that more specific instrument keyword terms be chosen from the KMS when available. For example, if data were collected from the AMSR-E instrument, it is preferred that "AMSR-E" be listed as the instrument as opposed to the more generic "RADIOMETERS" keyword. If a particular instrument keyword is missing from the KMS, it is possible to put in a request to have it added. The KMS is managed by the Global Change Master Directory (GCMD) and new keyword requests may be made through the GCMD Keywords Community Forum.
The Instruments/Technique field is optional. It can be used to further describe the technique utilized by the instrument for data collection. For example, the technique for a laser altimeter instrument on board a satellite could read "Measures the distance of the satellite from the Earth's surface by taking a precise measurement of the time it takes a transmitted laser pulse to hit the ground and then return to the instrument."
The Instruments/NumberOfInstruments field is optional. It can be used to indicate the number of instruments (i.e. sensors) used on the instrument while acquiring data. For example, the Terra satellite carries the ASTER instrument. The ASTER instrument is made up of 3 instrument subsystems (VNIR, SWIR, and TIR). In this example, the Instruments/NumberOfInstruments field would read "3".
The Instruments/OperationalModes field is optional and may be repeated. This field can be used to specify the mode(s) in which an instrument collects data. For example, the Sentinel-1 satellite collects data in four different modes. If a collection were to contain data acquired in all four modes, the OperationalModes field could be repeated four times and read "Stripmap (SM)", "Interferomic Wide swath (IW)", "Extra-Wide swath (EW)", "Wave (WV)"
Examples (ShortName > LongName):
SMMR > Scanning Multichannel Microwave Radiometer
OLI > Operational Land Imager
UAVSAR > Uninhabited Aerial Vehicle Synthetic Aperture Radar
LIS > Lightning Imaging Sensor
XPOL > NOAA/ETL X-band Polarimetric Doppler Radar
There are multiple sub-elements that comprise Archive and Distribution Information for Collections:
Format: Defines a single format for an archival artifact (e.g., binary, jpeg, HDF5, HDF-EOS5, GeoTIFF). The format must be selected from the GCMD Granule Data Format vocabulary list in order to adhere to the UMM-C schema. This ensures consistent use of data formats across the CMR.
Format Type: Allows the provider to define if the archival artifact's format is in its native format or another supported format.
Format Description: Allows the data provider to provide added information about the provided Format.
Average File Size: An approximate average of the size of the the archivable item, which gives users an idea of the magnitude of each archivable file.
Average File Size Unit: Unit of measure for the average file size (e.g., KB, MB, TB).
Total Collection File Size: An approximate total size of the archivable items, which gives users an idea of the magnitude of all the archivable files combined.
Total Collection File Size Unit: Unit of measure for the total collection file size (e.g., KB, MB, TB).
Total Collection File Size Begin Date: The date that data collection began for the collection, which should be in the following format: yyyy-MM-ddTHH:mm:ssZ
Description: Enables the provider to provide more information about the archivable item.
Media: Defines how the distributable material can be obtained by an end user (e.g., Online Archive, CD-ROM, hard drives, etc.).
Fees: Provide the price an end user will need to pay in order to obtain the distributable material.
Each of these elements are available under 'FileArchiveInformation' and 'FileDistributionInformation'. FileArchiveInformation describes the data in its archived format. FileDistributionInformation describes the data as distributed by a data provider. It can be the original format in which the data are archived, or it can be used to specify when the data is distributed in a format other than its original format. FileDistributionInformation is the preferred location for providing the data format since this should specify the format data are being distributed in to the end user.
Examples:
Format: "HDF-EOS5"
Format Type: "Native"
Format Description: "This is an EOSDIS specific format, and it is also available in ASCII."
Average File Size: "250"
Average File Size Unit: "KB"
Total Collection File Size: "25"
Total Collect File Size Unit: "GB"
Total Collection File Size Begin Date: "2018-04-01T00:00:00Z"
Element Specification
Cardinality of Archive and Distribution Information:
Element Specification
Instrument is an optional metadata element, however, it is strongly recommended that it be provided when possible. Multiple Instruments may be listed if necessary (Cardinality: 0..*).
Providing instrument characteristics is optional. An unlimited amount of instrument characteristics may be specified for a particular instrument (Cardinality: 0..*). If instrument characteristics are provided, all 5 sub-fields (Name, Description, DataType, Unit, Value) are required.
Model | Element |
---|
Type | Usable Valid Values | Constraints | Required? | Cardinality | Notes |
---|---|---|---|---|---|
UMM- |
C |
ArchiveAndDistributionInformation/ |
FileArchiveInformation/ |
Format | String |
GCMD Granule Data Format vocabulary list | 1 - 80 characters | Yes | 1 | The format must be selected from the GCMD Granule Data Format vocabulary list. |
UMM-C | ArchiveAndDistributionInformation/ FileArchiveInformation/FormatType | String | Native Supported | n/a |
No | 0..1 | ||
UMM- |
C |
ArchiveAndDistributionInformation/ |
FileArchiveInformation/ |
FormatDescription | String |
1 - |
80 characters | No | 0..1 | |
UMM- |
C |
ArchiveAndDistributionInformation/ |
FileArchiveInformation/ |
AverageFileSize |
Decimal | Yes, if TotalCollectionFileSizeBeginDate is used. | 0..1 | |||
UMM- |
C |
ArchiveAndDistributionInformation/ |
FileArchiveInformation/ |
AverageFileSizeUnit | String | KB |
MB GB TB PB NA | n/a |
Yes, if |
AverageFileSize is used. | 0..1 |
UMM- |
C |
ArchiveAndDistributionInformation/ |
FileArchiveInformation/ |
TotalCollectionFileSize |
Decimal |
No | 0..1 | Either use TotalCollectionFileSize or TotalCollectiopnFileSizeBeginDate | ||
UMM-C | ArchiveAndDistributionInformation/ FileArchiveInformation/ TotalCollectionFileSizeUnit | Enumeration | KB MB GB TB PB NA |
STRING
FLOAT
INT
BOOLEAN
DATE
TIME
DATETIME
DATE_STRING
TIME_STRING
DATETIME_STRINGn/a | Yes, if |
TotalCollectionFileSize is used | 0..1 | ||||||
UMM-C | ArchiveAndDistributionInformation/ FileArchiveInformation/ TotalCollectionFileSizeBeginDate | Date | No | 0..1 | Either use TotalCollectionFileSize or TotalCollectiopnFileSizeBeginDate | ||
UMM-C | ArchiveAndDistributionInformation/ FileArchiveInformation/ Description |
String | n/a | 1 - |
1024 characters |
No | 0..1 |
UMM- |
C |
ArchiveAndDistributionInformation/ |
FileDistributionInformation/Format | String |
GCMD Granule Data Format vocabulary list | 1 - 80 characters | Yes |
1 |
The format must be selected from the GCMD Granule Data Format vocabulary list. Recommend providing the data format in this element since this should specify the format data are being distributed in to the end user. |
UMM- |
C |
ArchiveAndDistributionInformation/ |
FileDistributionInformation/ |
FormatType | String |
Native Supported | No | 0..1 | |||
UMM-C | ArchiveAndDistributionInformation/ FileDistributionInformation/ FormatDescription | String |
1 - |
80 characters | No | 0.. |
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.
UNDEFINED - DIF 10 records found to be missing instruments by software will be automatically assigned a value of "Not Provided". It should then be confirmed whether an instrument can be assigned or whether "Not Applicable" should be provided. The value "Not Provided" 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.
Expand | ||
---|---|---|
| ||
|
Expand | ||
---|---|---|
| ||
|
title | ARC Metadata QA/QC |
---|
This element is categorized as highest priority when:
- The element is not included at all.
- The instrument short name tags are provided in the metadata but are left empty.
- The instrument keyword does not align with the KMS.
- The instrument keyword does not exist in KMS.
- A keyword(s) is placed in the incorrect position of the hierarchy (e.g. the instrument short name is placed in the long name field).
- Keywords from two different KMS hierarchies are listed in the same hierarchy in the metadata (i.e. hierarchies cannot be mixed and matched)
- Not all relevant instruments are listed.
- An incorrect instrument is listed.
- An instrument is listed under the incorrect platform.
- A recommendation is made to replace a valid instrument with a more specific/appropriate instrument keyword.
- Please see the Characteristics wiki page for high priority issues related to the Characteristics sub-elements.
This element is categorized as medium priority when:
- A recommendation is made to add an instrument long name when a long name exists in the KMS.
- Instruments are provided in an inconsistent manner across related datasets.
- Please see the Characteristics wiki page for medium priority issues related to the Characteristics sub-elements.
This element is categorized as low priority when:
- The instrument long name tags are provided in the metadata but are left empty.
- Please see the Characteristics wiki page for low priority issues related to the Characteristics sub-elements.
ARC Automated Checks
Instrument Short NameIf novalue is provided, return is: "This is a required field. Recommend providing at least one Instrument Short Name relevent to this data set. Instrument Short Name is GCMD controlled and should be selected from the following list: https://gcmdservices.gsfc.nasa.gov/static/kms/instruments/instruments.csv?ed_wiki_keywords_page"If no value is provided, return is: "Recommend providing at least one Instrument Long name relevent to this data set. Instrument Long Name is GCMD controlled and should be selected from the following list: https://gcmdservices.gsfc.nasa.gov/static/kms/instruments/instruments.csv?ed_wiki_keywords_page"
- If the provided value is in the incorrect hierarchy position, return is: "<provided value> is in the incorrect position of the project keyword hierarchy."
- If the provided value does not conform to GCMD, return is: "<provided value> does not conform to GCMD."
Dialect Mappings
Expand | ||
---|---|---|
| ||
DIF 9 (Note: DIF-9 is being phased out and will no longer be supported after 2018) |
1 | |||||||
UMM-C | ArchiveAndDistributionInformation/ FileDistributionInformation/ Media | String | n/a | 1 - 80 characters | No | 0..1 | |
UMM-C | ArchiveAndDistributionInformation/ FileDistributionInformation/ AverageFileSize | Decimal | n/a | n/a | Yes, if TotalCollectionFileSizeBeginDate is used. | 0..1 | |
UMM-C | ArchiveAndDistributionInformation/ FileDistributionInformation/ AverageFileSizeUnit | Enumeration | KB MB GB TB PB NA | Yes, if AverageFileSize is used. | 0..1 | ||
UMM-C | ArchiveAndDistributionInformation/ FileDistributionInformation/ TotalCollectionFileSize | Decimal | n/a | No | 0..1 | Either use TotalCollectionFileSize or TotalCollectiopnFileSizeBeginDate | |
UMM-C | ArchiveAndDistributionInformation/ FileDistributionInformation/ TotalCollectionFileSizeUnit | Enumeration | KB MB GB TB PB NA | n/a | Yes, if TotalCollectionFileSize is used | 0..1 | |
UMM-C | ArchiveAndDistributionInformation/ FileDistributionInformation/ TotalCollectionFileSizeBeginDate | Date | No | 0..1 | Either use TotalCollectionFileSize or TotalCollectiopnFileSizeBeginDate | ||
UMM-C | ArchiveAndDistributionInformation/ FileDistributionInformation/ Description | String | n/a | 1 - 1024 characters | No | 0..1 | |
UMM-C | Fees | String | n/a | 1 - 255 characters | No | 0..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 | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Please see the expandable sections below for flowchart details.
Expand | ||
---|---|---|
| ||
|
Expand | ||
---|---|---|
| ||
|
Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
ARC Automated Checks ARC uses the pyQuARC library for automated metadata checks. Please see the pyQuARC GitHub for more information. |
Dialect Mappings
Expand | ||
---|---|---|
| ||
DIF 9 (Note: DIF-9 is being phased out and will no longer be supported after 2018) |
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
DIF 10All of the sub-elements are optional in DIF 10.
|
Expand | ||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||
ECHO 10Only 2 UMM-C Archive and Distribution Information sub-elements map to ECHO 10, Data Format and Fees, and neither element is required.
|
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISO 19115-2 MENDSArchive and Distribution Information is an optional metadata element in ISO 19115-2 MENDS.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
UMM-C Element | Path | Type | Usable Valid Values | Constraints | Required in DIF 10? | Cardinality | Notes | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Platforms/Instruments/ShortName | /DIF/Platform/Instrument/Short_Name | String | Instrument Short_Name Keywords | KMS controlled | Yes | 1 | For each instrument provided, a short name is required. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Platforms/Instruments/LongName | /DIF/Platform/Instrument/Long_Name | String | Instrument Long_Name Keywords | KMS controlled | No | 0..1 | It is highly recommended that a long name be provided if one is available in KMS. | Platforms/Instruments/Technique | /DIF/Platform/Instrument/Technique | String | 1 - 2048 characters | No | 0..1 | Platforms/Instruments/NumberOfInstruments | /DIF/Platform/Instrument/NumberOfSensors | Integer | n/a | No | 0..1 | Platforms/Instruments/Characteristics/Name | /DIF/Platform/Instrument/Characteristics/Name | String | 1 - 80 characters | Yes, if applicable | 1 | Only required if a characteristic is provided.Providing characteristics is optional. | Platforms/Instruments/Characteristics/Description | /DIF/Platform/Instrument/Characteristics/Description | String | 1 - 2048 characters | Yes, if applicable | 1 | Only required if a characteristic is provided.Providing characteristics is optional. | Platforms/Instruments/Characteristics/DataType | /DIF/Platform/Instrument/Characteristics/DataType | String | 1 - 80 characters | Yes, if applicable | 1 | Only required if a characteristic is provided.Providing characteristics is optional. | Platforms/Instruments/Characteristics/Unit | /DIF/Platform/Instrument/Characteristics/Unit | String | 1 - 20 characters | Yes, if applicable | 1 | Only required if a characteristic is provided.Providing characteristics is optional. | Platforms/Instruments/Characteristics/Value | /DIF/Platform/Instrument/Characteristics/Value | String | 1 - 80 characters | Yes, if applicable | 1 | Only required if a characteristic is provided.Providing characteristics is optional. | Platforms/Instruments/OperationalModes | /DIF/Platform/Instrument/OperationalMode | String | 1 - 20 characters | No | 0..* | Example Mapping
Section | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
title | ECHO 10 |
---|
ECHO 10
Instrument is an optional metadata element, however, it is strongly recommended that it be provided when possible. Multiple Instruments may be listed if necessary (Cardinality: 0..*).
Providing instrument characteristics is optional. An unlimited amount of instrument characteristics may be specified for a particular instrument (Cardinality: 0..*). If instrument characteristics are provided, all 5 sub-fields (Name, Description, DataType, Unit, Value) are required.
KMS controlled
KMS controlled
Example Mapping
Section | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
title | ISO 19115-2 MENDS |
---|
ISO 19115-2 MENDS
Instrument is an optional metadata element, however, it is strongly recommended that it be provided when possible. Multiple Instruments may be listed if necessary (Cardinality: 0..*).
Providing instrument characteristics is optional. An unlimited amount of instrument characteristics may be specified for a particular instrument (Cardinality: 0..*). If instrument characteristics are provided, all 5 sub-fields (Name, Description, DataType, Unit, Value) are required.
/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:instrument/eos:EOS_Instrument id="<insert unique instrument ID here>"/ gmi:identifier/gmd:MD_Identifier/gmd:code/gco:CharacterString
with
/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:instrument/eos:EOS_Instrument/ gmi:identifier/gmd:MD_Identifier/gmd:codeSpace/gco:CharacterString = gov.nasa.esdis.umm.instrumentshortname
Corresponds to the UMM field Platforms/Instruments/ShortName. A list of valid instrument short names can be found in the KMS under the 'Short_Name' column. For each instrument listed the short name is required by CMR. The short name value goes in the gmd:code field.
The value of " gov.nasa.esdis.umm.instrumentshortname" should be provided in gmd:CodeSpace field so that CMR can properly parse out the instrument short name.
An ID should be provided directly after "eos:EOS_Instrument" in the ISO x-path. This ID corresponds to the instrument and is used to link the instrument information to the associated platform. The ID should be unique within the metadata record.
/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:instrument/eos:EOS_Instrument/ gmi:identifier/gmd:MD_Identifier/gmd:description/gco:CharacterString
Corresponds to the UMM field Platforms/Instruments/Characteristics/DataType.
ISO codelist values (class, codelist, enumeration, codelistElement, abstractClass, aggregateClass, specifiedClass, datatypeClass, interfaceClass, unionClass, metaClass, typeClass, characterString, integer, association)
UMM enum (STRING, FLOAT, INT BOOLEAN, DATE, TIME, DATETIME, DATE_STRING, TIME_STRING, DATETIME_STRING)
/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:instrument/eos:EOS_Instrument/ eos:otherProperty/gco:Record/eos:AdditionalAttributes/eos:AdditionalAttribute/eos:reference/eos:EOS_AdditionalAttributeDescription/ eos:name/gco:CharacterString="OperationalMode"
and
/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:instrument/eos:EOS_Instrument/ eos:otherProperty/gco:Record/eos:AdditionalAttributes/eos:AdditionalAttribute/eos:value/gco:CharacterString
Section | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
title | ISO 19115-2 SMAP |
---|
ISO 19115-2 SMAP
Instrument is an optional metadata element, however, it is strongly recommended that it be provided when possible. Multiple Instruments may be listed if necessary (Cardinality: 0..*).
Providing instrument characteristics is optional. An unlimited amount of instrument characteristics may be specified for a particular instrument (Cardinality: 0..*). If instrument characteristics are provided, all 5 sub-fields (Name, Description, DataType, Unit, Value) are required.
/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:instrument/eos:EOS_Instrument id="<insert unique instrument ID here>"/ gmi:identifier/gmd:MD_Identifier/gmd:code/gco:CharacterString
with
/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:instrument/eos:EOS_Instrument/ gmi:identifier/gmd:MD_Identifier/gmd:codeSpace/gco:CharacterString = gov.nasa.esdis.umm.instrumentshortname
Corresponds to the UMM field Platforms/Instruments/ShortName. A list of valid instrument short names can be found in the KMS under the 'Short_Name' column. For each instrument listed the short name is required by CMR. The short name value goes in the gmd:code field.
The value of " gov.nasa.esdis.umm.instrumentshortname" should be provided in gmd:CodeSpace field so that CMR can properly parse out the instrument short name.
An ID should be provided directly after "eos:EOS_Instrument" in the ISO x-path. This ID corresponds to the instrument and is used to link the instrument information to the associated platform. The ID should be unique within the metadata record.
/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:instrument/eos:EOS_Instrument/ gmi:identifier/gmd:MD_Identifier/gmd:description/gco:CharacterString
Corresponds to the UMM field Platforms/Instruments/Characteristics/DataType.
ISO codelist values (class, codelist, enumeration, codelistElement, abstractClass, aggregateClass, specifiedClass, datatypeClass, interfaceClass, unionClass, metaClass, typeClass, characterString, integer, association)
UMM enum (STRING, FLOAT, INT BOOLEAN, DATE, TIME, DATETIME, DATE_STRING, TIME_STRING, DATETIME_STRING)
/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:instrument/eos:EOS_Instrument/ eos:otherProperty/gco:Record/eos:AdditionalAttributes/eos:AdditionalAttribute/eos:reference/eos:EOS_AdditionalAttributeDescription/ eos:name/gco:CharacterString="OperationalMode"
and
/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:instrument/eos:EOS_Instrument/ eos:otherProperty/gco:Record/eos:AdditionalAttributes/eos:AdditionalAttribute/eos:value/gco:CharacterString
Section | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
UMM Migration
None
|
Expand | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||
ISO 19115-2 SMAPArchive and Distribution Information does not currently map to ISO 19115-2 SMAP.
|
UMM Migration
None
Excerpt | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Future Mappings
|
History
UMM Versioning
Version | Date | What Changed |
---|---|---|
1.15.5 | 12/3/2020 | The description of the format elements now includes text about the controlled vocabulary for this field coming from KMS. |
1.15.4 | 9/18/2020 | No changes were made for Archive and Distribution Information during the transition from version 1.15.3 to 1.15.4 |
1.15.3 | 7/1/2020 | FormatDescription was added to FileArchive and FileDistribution Information types to version 1.15.3 |
1.15.2 | 5/20/2020 | No changes were made for Archive and Distribution Information during the transition from version 1.15.1 to 1.15.2 |
1.15.1 | 3/25/2020 | No changes were made for Archive and Distribution Information during the transition from version 1.15.0 to 1.15.1 |
1.15.0 | 2/26/2020 | No changes were made for Archive and Distribution Information during the transition from version 1.14.0 to 1.15.0 |
1.14.0 | 10/21/2019 | No changes were made for Archive and Distribution Information during the transition from version 1.13.0 to 1.14.0 |
1.13.0 | 04/11/2019 |
Future Mappings
title | ISO 19115-1 |
---|
ISO 19115-1
Instrument is an optional metadata element, however, it is strongly recommended that it be provided when possible. Multiple Instruments may be listed if necessary (Cardinality: 0..*).
Providing instrument characteristics is optional. An unlimited amount of instrument characteristics may be specified for a particular instrument (Cardinality: 0..*). If instrument characteristics are provided, all 5 sub-fields (Name, Description, DataType, Unit, Value) are required.
/mdb:MD_Metadata/mdb:acquisitionInformation/mac:MI_AcquisitionInformation/mac:instrument/mac:MI_Instrument id="<insert unique instrument ID here>"/mac:identifier/mcc:MD_Identifier/mcc:code/gco:CharacterString
with
/mdb:MD_Metadata/mdb:acquisitionInformation/mac:MI_AcquisitionInformation/mac:instrument/mac:MI_Instrument id="<insert unique instrument ID here>"/mac:identifier/mcc:MD_Identifier/mcc:codeSpace/gco:CharacterString = gov.nasa.esdis.umm.instrumentshortname
Corresponds to the UMM field Platforms/Instruments/ShortName. A list of valid instrument short names can be found in the KMS under the 'Short_Name' column. For each instrument listed the short name is required by CMR. The short name value goes in the gmd:code field.
The value of " gov.nasa.esdis.umm.instrumentshortname" should be provided in gmd:CodeSpace field so that CMR can properly parse out the instrument short name.
An ID should be provided directly after "eos:EOS_Instrument" in the ISO x-path. This ID corresponds to the instrument and is used to link the instrument information to the associated platform. The ID should be unique within the metadata record.
/mdb:MD_Metadata/mdb:acquisitionInformation/mac:MI_AcquisitionInformation/mac:instrument/mac:MI_Instrument id="<insert unique instrument ID here>"/mac:identifier/mcc:MD_Identifier/mcc:description/gco:CharacterString
Corresponds to the UMM field Platforms/Instruments/Characteristics/DataType.
ISO codelist values (class, codelist, enumeration, codelistElement, abstractClass, aggregateClass, specifiedClass, datatypeClass, interfaceClass, unionClass, metaClass, typeClass, characterString, integer, association)
UMM enum (STRING, FLOAT, INT BOOLEAN, DATE, TIME, DATETIME, DATE_STRING, TIME_STRING, DATETIME_STRING)
/mdb:MD_Metadata/mdb:acquisitionInformation/mac:MI_AcquisitionInformation/mac:instrument/mac:MI_Instrument id="<insert unique instrument ID here> "/mac:otherProperty/gco:Record/eos:AdditionalAttributes/eos:AdditionalAttribute/eos:reference/eos:EOS_AdditionalAttributeDescription/ eos:name/gco:CharacterString="OperationalMode"
and
/mdb:MD_Metadata/mdb:acquisitionInformation/mac:MI_AcquisitionInformation/mac:instrument/mac:MI_Instrument id="<insert unique instrument ID here> "/mac:otherProperty/gco:Record/eos:AdditionalAttributes/eos:AdditionalAttribute/eos:value/gco:CharacterString
Example Mapping
Section | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
History
UMM Versioning
Version | Date | What Changed |
---|---|---|
1.13.0 | Future | This element was added to the UMM-C specification. |
ARC Documentation
Version | Date | What Changed | Author |
---|---|---|---|
1.0 | 505/16/18 | Recommendations/priority matrix transferred from internal ARC documentation to wiki space | |
1.1 | 04/12/21 | Moved "The data format provided is correct, however, it does not exactly match its entry in the GCMD Granule Data Format vocabulary list." from blue to red. GCMD keywords are now the authoritative controlled vocabulary source for data formats. | Jeanne' le Roux |