Page History
Table of Contents |
---|
Element Description
Note: this wiki page is a draft/ work in progress
The Spatial Representation Information element...
Best Practices
There are Twenty-one sub-elements that comprise Collection Citation:
Title: The title of the publication in the bibliographic citation.
Publisher: The publisher of the publication.
DOI: The Digital Object Identifier (DOI) of the publication.
DOI Authority: The DOI organization that is responsible for creating the DOI is described in the Authority element.
Author: The author of the publication.
PublicationDate: The date of the publication.
Series: The name of the series of the publication.
Edition: The edition of the publication.
Volume: The publication volume number.
Issue: The issue of the publication.
ReportNumber: The report number of the publication.
PublicationPlace: The publication place of the publication.
Pages: The publication pages that are relevant.
ISBN: The ISBN of the publication.
OtherReferenceDetails: Additional free-text reference information about the publication.
OnlineResource/Linkage: The URL of the website related to the online resource.
OnlineResource/Protocol: The protocol of the linkage for the online resource, such as https, svn, ftp, etc.
OnlineResource/ApplicationProfile: The application profile holds the name of the application that can service the data. For example if the URL points to a word document, then the applicationProfile is MS-Word.
OnlineResource/Name: The name of the online resource.
OnlineResource/Description: The description of the online resource.
OnlineResource/Function: The function of the online resource. In ISO where this class originated the valid values are: download, information, offlineAccess, order, and search.
Examples:
PublicationDate: "1996-01-01T00:00:00.000Z",Series: "Monthly Weather Review",
Title: "Data assimilation using incremental analysis updates"
Edition: "104606"
DOI: "10.1177/1094342005056120"
Pages: "1256-1271"
Author: "Bloom, S., L. Takacs, A. DaSilva, and D. Ledvina",
Issue: "124"
Volume: "19"
Element Specification
Providing the Publication Reference element is optional (Cardinality: 0..*)
1 - 1024 characters
1 - 1030 characters
1 - 1024 characters
1 - 1024 characters
1 - 80 characters
1 - 80 characters
1 - 80 characters
1 - 1024 characters
1 - 1024 characters
1 - 80 characters
1 - 13 characters
1 - 1024 characters
1 - 80 characters
1 - 1024 characters
1 - 80 characters
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.
title | GCMD Metadata QA/QC |
---|
Expand | ||
---|---|---|
| ||
<> |
title | ARC Metadata QA/QC |
---|
This element is categorized as highest priority when:
- The information provided is not related to the element.
- The descriptions are inaccurate for the data set.
- The "Reference/Online_Resource" URL can not be accessed.
This element is categorized as medium priority when:
- The description is missing.
- The "Reference/Publication_Date" does not comply with the appropriate format.
This element is categorized as low priority when:
- The Reference descriptions includes spelling or grammatical errors.
ARC Automated Rules
If novalue is provided, return is "np."Dialect Mappings
Expand | ||
---|---|---|
| ||
DIF 9 (Note: DIF-9 is being phased out and will no longer be supported after 2018) |
Information element stores information about the reference frame from which horizontal and vertical spatial domains are measured. The horizontal reference frame includes fields for Geodetic Model, Geographic Coordinates, and Local Coordinates. The Vertical reference frame includes fields for altitudes (elevations) and depths.
Best Practices
Providing Spatial Information is optional, but encouraged. This element can be used to provide horizontal and/or vertical coordinate system information.
The Spatial Coverage Type field is required for Spatial Information.
Spatial Coverage Type: Denotes the type of spatial coverage of the collection. While this field is not currently controlled, recommend providing one of the spatial coverage type enumeration values: EARTH/GLOBAL, HORIZONTAL, VERTICAL, ORBITAL, HORIZONTAL_VERTICAL, ORBITAL_VERTICAL, HORIZONTAL_ORBITAL, HORIZONTAL_VERTICAL_ORBITAL, LUNAR
Vertical Spatial Information
The following sub-elements can be used to describe Vertical Coordinate Systems.
There are 2 categories for Vertical Coordinate Systems including:
(1) Altitude System Definition
Altitude System Definition should be used to describe data with a vertical component that is above-ground. Sub-elements under Altitude System Definition are summarized below:
- Datum Name: The name of the vertical datum the data is encoded in. Vertical datums define a level reference surface from which vertical measurements are compared. There are many standard vertical datums. If a standard vertical datum is used, it is recommended that the EPSG vertical datum name be provided.
- Distance Units: The units in which altitude measurements are recorded. This field is controlled and must be selected from one of the following values: HectoPascals, Kilometers, Millibars
- Resolutions: The minimum distance possible between two adjacent values, expressed in distance units of measure for the collection.
(2) Depth System Definition
Depth System Definition should be used to describe data with a vertical component that is below-ground. Sub-elements under Depth System Definition are summarized below:
- Datum Name: The name of the vertical datum the data is encoded in. Vertical datums define a level reference surface from which vertical measurements are compared. There are many standard vertical datums. If a standard vertical datum is used, it is recommended that the EPSG vertical datum name be provided.
- Distance Units: The units in which depth measurements are recorded. This field is controlled and must be selected from one of the following values: Fathoms, Feet, HectoPascals, Meters, Millibars
- Resolutions: The minimum distance possible between two adjacent values, expressed in distance units of measure for the collection.
- Datum Name: The name of the vertical datum the data is encoded in. Vertical datums define a level reference surface from which vertical measurements are compared. There are many standard vertical datums. If a standard vertical datum is used, it is recommended that the EPSG vertical datum name be provided.
Element Specification
Providing Spatial Information is optional (Cardinality: 0..1)
Model | Element | Type | Usable Valid Values | Constraints | Required? | Cardinality | Notes |
---|---|---|---|---|---|---|---|
UMM-C | SpatialInformation/SpatialCoverageType | String | EARTH/GLOBAL, HORIZONTAL, VERTICAL, ORBITAL, HORIZONTAL_VERTICAL, ORBITAL_VERTICAL, HORIZONTAL_ORBITAL, HORIZONTAL_VERTICAL_ORBITAL, LUNAR | 1 - 80 characters | Yes, if applicable | 1 | |
UMM-C | SpatialInformation/VerticalCoordinateSystem/AltitudeSystemDefinition/DatumName | String | n/a | 1 - 80 characters | No | 0..1 | Recommend providing EPSG vertical datum names |
UMM-C | SpatialInformation/VerticalCoordinateSystem/AltitudeSystemDefinition/DistanceUnits | Enumeration | HectoPascals Kilometers Millibars | n/a | No | 0..1 | |
UMM-C | SpatialInformation/VerticalCoordinateSystem/AltitudeSystemDefinition/Resolutions | Number | n/a | n/a | No | 0..* | |
UMM-C | SpatialInformation/VerticalCoordinateSystem/DepthSystemDefinition/DatumName | String | n/a | 1 - 80 characters | No | 0..1 | Recommend providing EPSG vertical datum names |
UMM-C | SpatialInformation/VerticalCoordinateSystem/DepthSystemDefinition/DistanceUnits | Enumeration | Fathoms Feet HectoPascals Meters Millibars | n/a | No | 0..1 | |
UMM-C | SpatialInformation/VerticalCoordinateSystem/DepthSystemDefinition/Resolutions | Number | n/a | n/a | No | 0..* |
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 | ||
---|---|---|
| ||
None |
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 10Providing Spatial_Info is optional in DIF 10 (Cardinality: 0..1). Note: There are no Vertical Coordinate System fields in DIF 10 - vertical information can be provided in the Vertical_Spatial_Info element. For details on Vertical_Spatial_Info please see the Spatial Extent wiki page. DIF 10 also supports an element called Data_Resolution which does not currently map to the UMM, however, there are plans to support it in the future.
|
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ECHO 10Providing the Spatial Info element is optional in ECHO 10 (Cardinality: 0..1)
|
UMM Migration
N/A
History
UMM Versioning
Version | Date | What Changed |
---|---|---|
1.18.0 | 2024-03-18 | Updated Spatial Coverage Type enumeration list for 1.18.0 |
1.15.5 | 2020-12-03 | No changes were made for Spatial Information during the transition from version 1.15.4 to 1.15.5 |
1.15.4 | 2020-09-18 | No changes were made for Spatial Information during the transition from version 1.15.3 to 1.15.4 |
1.15.3 | 2020-07-01 | No changes were made for Spatial Information during the transition from version 1.15.2 to 1.15.3 |
1.15.2 | 2020-05-20 | No changes were made for Spatial Information during the transition from version 1.15.1 to 1.15.2 |
1.15.1 | 2020-03-25 | No changes were made for Spatial Information during the transition from version 1.15.0 to 1.15.1 |
1.15.0 | 2020-02-26 | No changes were made for Spatial Information during the transition from version 1.14.0 to 1.15.0 |
1.14.0 | 2019-10-21 | The Horizontal Coordinate System element and all supporting elements were either removed or renamed and moved to the SpatialExtent element. |
1.13.0 | 2019-04-11 | No changes were made for Spatial Information during the transition from version 1.12.0 to 1.13.0 |
1.12.0 | 2019-01-22 | No changes were made for Spatial Information during the transition from version 1.11.0 to 1.12.0. |
1.11.0 | 2018-11-28 | No changes were made for Spatial Information during the transition from version 1.10.0 to 1.11.0. |
1.10.0 | 2018-05-02 | During the transition from version 1.9.0 to 1.10.0:
|
title | DIF 10 |
---|
Providing the Reference element is optional (Cardinality: 0..*)
String
DOI
ARK
Section | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
title | ECHO 10 |
---|
ECHO 10
Publication Reference does not map to ECHO 10.
N/A
Section | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
title | ISO 19115-2 MENDS |
---|
ISO 19115-2 MENDS
Providing the Publication Reference element is not required (Cardinality: 0..*)
/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:aggregateDataSetName/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:role/CI_RoleCode=author
String
Maps to the UMM element "PublicationReference/Authors"
where
/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:aggregateDataSetName/gmd:CI_Citation/gmd:identifier/gmd:MD_Identifier/gmd:description/gco:CharacterString = DOI
and
/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:aggregateDataSetName/gmd:CI_Citation/gmd:identifier/gmd:MD_Identifier/gmd:codeSpace/gco:CharacterString = gov.nasa.esdis.umm.doi
Section | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
title | ISO 19115-2 SMAP |
---|
ISO 19115-2 SMAP
Providing the Publication Reference element is not required (Cardinality: 0..*)
with
/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:aggregateDataSetName/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:role/CI_RoleCode=author
String
Maps to the UMM element "PublicationReference/Authors"
where
/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:aggregateDataSetName/gmd:CI_Citation/gmd:identifier/gmd:MD_Identifier/gmd:description/gco:CharacterString = DOI
and
/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:aggregateDataSetName/gmd:CI_Citation/gmd:identifier/gmd:MD_Identifier/gmd:codeSpace/gco:CharacterString = gov.nasa.esdis.umm.doi
Section | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
UMM Migration
Future Mappings
title | ISO 19115-1 |
---|
ISO 19115-1
Providing the Publication Reference element is not required (Cardinality: 0..*)
cit:CI_Individual/cit:name or cit:CI_Organization/cit:name
with
/mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:citation/cit:CI_Citation/cit:citedResponsibleParty/cit:CI_Responsibility/cit:role/cit:CI_RoleCode=author
cit:CI_Individual/cit:name or cit:CI_Organization/cit:name
where
/mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:citation/cit:CI_Citation/cit:identifier/mcc:MD_Identifier/mcc:description/gco:CharacterString = DOI
and
/mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:citation/cit:CI_Citation/cit:identifier/mcc:MD_Identifier/mcc:codeSpace = gov.nasa.esdis.umm.doi
Section | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
History
UMM Versioning
No changes were made for Collection Data Type during the transition from version 1.9.0 to 1.10.0
ARC Documentation
Version | Date | What Changed | Author |
---|---|---|---|
1.011/16/18 | 2019-02-15 | Recommendations/priority matrix transferred from internal ARC documentation to wiki space |