Location Keywords

Element Description

The Location Keywords element contains keywords that characterize the study area/region where data was collected. This allows users to narrow their searches to areas that suit their geographic interest. The Location Keywords are chosen from a controlled keyword hierarchy maintained in the Keyword Management System (KMS). A list of valid Location Keywords can be found here: https://gcmdservices.gsfc.nasa.gov/static/kms/locations/locations.csv ?

Best Practices

Location Keywords identify areas where data collection occurred, and are provided in a hierarchical structure. The keywords can be chosen to classify broad study areas/regions or very specific places. However, it is suggested that location keywords are as specific as possible to aid in data discovery. Providing a Location Keyword is optional. If provided, the top level of the Location Keyword hierarchy must be provided (at a minimum). If a specific location keyword is not already included in the KMS, a request to have it added can be made through the GCMD Keywords Community Forum.

Examples:

LocationKeywords/Category: "CONTINENT"

LocationKeywords/Topic: "NORTH AMERICA"

LocationKeywords/Subregion1: "UNITED STATES"

LocationKeywords/Subregion2: "ALABAMA"

LocationKeywords/DetailedLocation: "THE UNIVERSITY OF ALABAMA IN HUNTSVILLE"

LocationKeywords/Category: "CONTINENT"

LocationKeywords/Topic: "NORTH AMERICA"

LocationKeywords/Subregion1: "CANADA"

LocationKeywords/Subregion2: "ONTARIO"

LocationKeywords/Category: "GEOGRAPHIC REGION"

LocationKeywords/Topic: "TROPICS"

Element Specification

Providing a Location Keyword is optional. Multiple Location Keywords may be provided, if necessary (Cardinality: 0..*).

Model	Element	Type	Usable Valid Values	Constraints	Required?	Cardinality	Notes
UMM-C	LocationKeywords/Category	String	Location Category Keywords	KMS controlled	Yes, if applicable	1	If a Location Keyword is included in the metadata (it's optional), then a Category keyword must be provided at a minimum.
UMM-C	LocationKeywords/Type	String	Location Type Keywords	KMS controlled	No	0..1
UMM-C	LocationKeywords/Subregion1	String	Location Subregion1 Keywords	KMS controlled	No	0..1
UMM-C	LocationKeywords/Subregion2	String	Location Subregion2 Keywords	KMS controlled	No	0..1
UMM-C	LocationKeywords/Subregion3	String	Location Subregion3 Keywords	KMS controlled	No	0..1
UMM-C	LocationKeywords/DetailedLocation	String	n/a	1 - 80 characters (Uncontrolled/Free-Text)	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).

Please see the expandable sections below for flowchart details.

GCMD Metadata QA/QC

Manual Review
- Identify errors, discrepancies or omissions.
- Verify that all pertinent keywords have been applied.
- Verify that existing facets and other controlled keyword values are consistent and suitable for the data.
Automated Review
- Check that the field has been populated.
- Check that the field is populated with a valid value from KMS.
- Check that the field value is not a duplicate.
- Check that the 'Detailed_Variable' field length is not greater than 80 characters.

ARC Metadata QA/QC

ARC Priority Matrix

Priority Categorization	Justification
	This element is categorized as highest priority when: The location keyword does not align with the KMS. The location keyword does not exist in KMS. A keyword(s) is missing from the hierarchy. A keyword(s) is placed in the incorrect position of the hierarchy (e.g. a Subregion 2 keyword is placed in the Subregion 1 field). The location keyword is not appropriate for the dataset.
	This element is categorized as medium priority when: A recommendation is made to add to an existing keyword in the metadata (i.e. to extend a keyword hierarchy down to a more detailed keyword).
	This element is categorized as low priority when: A recommendation is made to add a relevant location keyword to the metadata.
	The element is provided and follows all applicable criteria specified in the best practices section above.

ARC Automated Checks

CMR Validation

<>

Dialect Mappings

DIF 9

DIF 9 ^{(Note: DIF-9 is being phased out and will no longer be supported after 2018)}

DIF 10

Providing a Location is optional. Multiple Locations may be provided, if necessary (Cardinality: 0..*).

Specification	Path	Type	Usable Valid Values	Constraints	Required in DIF 10?	Cardinality	Notes
DIF 10	/DIF/Location/Location_Category	String	Location Category Keywords	KMS controlled	Yes, if applicable	1	If a Location is included in the metadata (it's optional), then a Location_Category must be provided at a minimum.
DIF 10	/DIF/Location/Location_Type	String	Location Type Keywords	KMS controlled	No	0..1
DIF 10	/DIF/Location/Location_Subregion1	String	Location Subregion1 Keywords	KMS controlled	No	0..1
DIF 10	/DIFLocation/Location_Subregion2	String	Location Subregion2 Keywords	KMS controlled	No	0..1
DIF 10	/DIF/Location/Location_Subregion3	String	Location Subregion3 Keywords	KMS controlled	No	0..1
DIF 10	/DIF/Location/Detailed_Location	String	n/a	1 - 80 characters (Uncontrolled/Free-Text)	No	0..1

Example Mapping

DIF 10

<Location>
  <Location_Category>CONTINENT</Location_Category>
  <Location_Type>NORTH AMERICA</Location_Type>
  <Location_Subregion1>UNITED STATES</Location_Subregion1>
  <Location_Subregion2>ALBAMA</Location_Subregion2>
  <Detailed_Location>THE UNIVERSITY OF ALABAMA IN HUNTSVILLE</Detailed_Location>
</Location>
<Location>
  <Location_Category>CONTINENT</Location_Category>
  <Location_Type>NORTH AMERICA</Location_Type>
  <Location_Subregion1>CANADA</Location_Subregion1>
  <Location_Subregion2>ONTARIO</Location_Subregion2>
</Location>

UMM

LocationKeywords: [
  {
    Category: "CONTINENT",
    Type: "NORTH AMERICA",
    Subregion1: "UNITED STATES",
    Subregion2: "ALABAMA",
    DetailedLocation: "THE UNIVERSITY OF ALABAMA IN HUNTSVILLE"
  },
  {
    Category: "CONTINENT",
    Type: "NORTH AMERICA",
    Subregion1: "CANADA",
    Subregion2: "ONTARIO"
  }
],

ECHO 10

Providing a Spatial Keyword is optional. Multiple Spatial Keywords may be provided, if necessary (Cardinality: 0..*).

Specification	Path	Type	Usable Valid Values	Constraints	Required in ECHO10?	Cardinality	Notes
ECHO 10	/Collection/SpatialKeywords/Keyword	String	Any GCMD Location Keyword	KMS controlled	No	0..*	ECHO 10 only has 1 field for spatial keywords. Therefore, a keyword from any position in the GCMD location keyword hierarchy can be provided in this field. If a value is provided that is not in the keyword list, then XXXX ← need to figure out how this would map

Example Mapping

ECHO 10

<SpatialKeywords>
  <Keyword>THE UNIVERSITY OF ALABAMA IN HUNTSVILLE</Keyword> 
  <Keyword>ONTARIO</Keyword>
</SpatialKeywords>

UMM

ScienceKeywords: [
  {
    DetailedLocation: "THE UNIVERSITY OF ALABAMA IN HUNTSVILLE"
  },
  {
    Category: "CONTINENT",
    Type: "NORTH AMERICA",
    Subregion1: "CANADA",
    Subregion2: "ONTARIO"
  }
],
* not sure if this mapping is correct since 'University of Alabama in Huntsville' is not a GCMD keyword

ISO 19115-2 MENDS

Providing a Location Keyword is optional. Multiple Location Keywords may be provided, if necessary (Cardinality: 0..*).

Specification

Path

Type

Notes

ISO 19115-2 MENDS

/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:descriptiveKeywords/gmd:MD_Keywords/ gmd:keyword/gco:CharacterString (list each value of the keyword hierarchy delimited by > )

String

KMS controlled. This is where the entire keyword hierarchy should be listed. Each keyword in the hierarchy must be separated by ">". If any keyword is missing and there exists a keyword later in the hierarchy (such as DetailedLocation), use NONE to fill in the values in-between. The CMR will not translate the NONE values as they are only used to place each keyword in its correct space in the hierarchy.

/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:descriptiveKeywords/gmd:MD_Keywords/ gmd:type/MD_KeywordTypeCode

codeList="https://cdn.earthdata.nasa.gov/iso/resources/Codelist/gmxCodelists.xml#MD_KeywordTypeCode" codeListValue="place"

Codelist

codeList=https://cdn.earthdata.nasa.gov/iso/resources/Codelist/gmxCodelists.xml #MD_KeywordTypeCode

Select the value "place" from the codelist. This codelist value does not directly map to a UMM element; choosing "place" indicates to CMR that the provided value should be mapped to 'Location Keywords'.

Example Mapping

ISO 19115-2 MENDS

<gmi:MI_Metadata>
  <gmd:identificationInfo>
    <gmd:MD_DataIdentification>
      <gmd:descriptiveKeywords>
        <gmd:MD_Keywords>
          <gmd:keyword>
            <gco:CharacterString>CONTINENT&gt;NORTH AMERICA&gt;UNITED STATES&gt;ALABAMA&gt;NONE&gt;THE UNIVERSITY OF ALABAMA IN HUNTSVILLE</CharacterString>
          </gmd:keyword>
          <gmd:keyword>
            <gco:CharacterString>CONTINENT&gt;NORTH AMERICA&gt;CANADA&gt;ONTARIO</CharacterString>
          </gmd:keyword>
          <gmd:type>
            <gmd:MD_KeywordTypeCode codeList="https://cdn.earthdata.nasa.gov/iso/resources/Codelist/gmxCodelists.xml#MD_KeywordTypeCode" codeListValue="place">place</gmd:MD_KeywordTypeCode>
          </gmd:type>
        </gmd:MD_Keywords> 
      </gmd:descriptiveKeywords>
    </gmd:MD_DataIdentification>
  </gmd:identificationInfo>
</gmi:MI_Metadata>

UMM

LocationKeywords: [
  {
    Category: "CONTINENT",
    Type: "NORTH AMERICA",
    Subregion1: "UNITED STATES",
    Subregion2: "ALABAMA"
    DetailedLocation: "THE UNIVERSITY OF ALABAMA IN HUNTSVILLE"
  },
  {
    Category: "CONTINENT",
    Type: "NORTH AMERICA",
    Subregion1: "CANADA",
    Subregion2: "ONTARIO"
  }
],

ISO 19115-2 SMAP

Providing a Location Keyword is optional. Multiple Location Keywords may be provided, if necessary (Cardinality: 0..*).

Specification

Path

Type

Notes

ISO 19115-2 SMAP

/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:descriptiveKeywords/ gmd:MD_Keywords/gmd:keyword/gco:CharacterString (list each value of the keyword hierarchy delimited by > )

String

KMS controlled. This is where the entire keyword hierarchy should be listed. Each keyword in the hierarchy must be separated by ">". If any keyword is missing and there exists a keyword later in the hierarchy (such as DetailedLocation), use NONE to fill in the values in-between. The CMR will not translate the NONE values as they are only used to place each keyword in its correct space in the hierarchy.

ISO 19115-2 SMAP

/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:descriptiveKeywords/ gmd:MD_Keywords/gmd:type/MD_KeywordTypeCode

codeList="https://cdn.earthdata.nasa.gov/iso/resources/Codelist/gmxCodelists.xml#MD_KeywordTypeCode" codeListValue="place"

Codelist

codeList=https://cdn.earthdata.nasa.gov/iso/resources/Codelist/gmxCodelists.xml #MD_KeywordTypeCode

Select the value "place" from the codelist. This codelist value does not directly map to a UMM element; choosing "place" indicates to CMR that the provided value should be mapped to 'Location Keywords'.

Example Mapping

ISO 19115-2 SMAP

<gmd:DS_Series>
<gmd:seriesMetadata>
<gmi:MI_Metadata>
  <gmd:identificationInfo>
    <gmd:MD_DataIdentification>
      <gmd:descriptiveKeywords>
        <gmd:MD_Keywords>
          <gmd:keyword>
            <gco:CharacterString>CONTINENT&gt;NORTH AMERICA&gt;UNITED STATES&gt;ALABAMA&gt;NONE&gt;THE UNIVERSITY OF ALABAMA IN HUNTSVILLE</CharacterString>
          </gmd:keyword>
          <gmd:keyword>
            <gco:CharacterString>CONTINENT&gt;NORTH AMERICA&gt;CANADA&gt;ONTARIO</CharacterString>
          </gmd:keyword>
          <gmd:type>
            <gmd:MD_KeywordTypeCode codeList="https://cdn.earthdata.nasa.gov/iso/resources/Codelist/gmxCodelists.xml#MD_KeywordTypeCode" codeListValue="place">place</gmd:MD_KeywordTypeCode>
          </gmd:type>
        </gmd:MD_Keywords> 
      </gmd:descriptiveKeywords>
    </gmd:MD_DataIdentification>
  </gmd:identificationInfo>
</gmi:MI_Metadata>
</gmd:seriesMetadata>
</gmd:DS_Series>

UMM

LocationKeywords: [
  {
    Category: "CONTINENT",
    Type: "NORTH AMERICA",
    Subregion1: "UNITED STATES",
    Subregion2: "ALABAMA"
    DetailedLocation: "THE UNIVERSITY OF ALABAMA IN HUNTSVILLE"
  },
  {
    Category: "CONTINENT",
    Type: "NORTH AMERICA",
    Subregion1: "CANADA",
    Subregion2: "ONTARIO"
  }
],

UMM Migration

None

Future Mappings

ISO 19115-1

Providing a Location Keyword is optional. Multiple Location Keywords may be provided, if necessary (Cardinality: 0..*).

Specification

Path

Type

Notes

ISO 19115-1

/mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:descriptiveKeywords/mri:MD_Keywords/ mri:keyword/gco:CharacterString

(list each value of the keyword hierarchy delimited by > )

String

KMS controlled. This is where the entire keyword hierarchy should be listed. Each keyword in the hierarchy must be separated by ">". If any keyword is missing and there exists a keyword later in the hierarchy (such as DetailedLocation), use NONE to fill in the values in-between. The CMR will not translate the NONE values as they are only used to place each keyword in its correct space in the hierarchy.

ISO 19115-1

/mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:descriptiveKeywords/mri:MD_Keywords/ mri:type/mri:MD_KeywordTypeCode

codeList="https://cdn.earthdata.nasa.gov/iso/resources/Codelist/gmxCodelists.xml#MD_KeywordTypeCode" codeListValue="place"

Codelist

codeList=https://cdn.earthdata.nasa.gov/iso/resources/Codelist/gmxCodelists.xml #MD_KeywordTypeCode

Select the value "place" from the codelist. This codelist value does not directly map to a UMM element; choosing "place" indicates to CMR that the provided value should be mapped to 'Location Keywords'.

ISO 19115-1

<mdb:MD_Metadata>
  <mdb:identificationInfo>
    <mri:MD_DataIdentification>
      <mri:descriptiveKeywords>
        <mri:MD_Keywords>
          <mri:keyword>
            <gco:CharacterString>CONTINENT&gt;NORTH AMERICA&gt;UNITED STATES&gt;ALABAMA&gt;NONE&gt;THE UNIVERSITY OF ALABAMA IN HUNTSVILLE</CharacterString>
          </mri:keyword>
          <mri:keyword>
            <gco:CharacterString>CONTINENT&gt;NORTH AMERICA&gt;CANADA&gt;ONTARIO</CharacterString>
          </mri:keyword>
          <mri:type>
            <mri:MD_KeywordTypeCode codeList="https://cdn.earthdata.nasa.gov/iso/resources/Codelist/gmxCodelists.xml#MD_KeywordTypeCode" codeListValue="place">place</gmd:MD_KeywordTypeCode>
          </mri:type>
        </mri:MD_Keywords>
      </mri:descriptiveKeywords>
    </mri:MD_DataIdentification>
  </mdb:identificationInfo>
</mdb:MD_Metadata>

UMM

LocationKeywords: [
  {
    Category: "CONTINENT",
    Type: "NORTH AMERICA",
    Subregion1: "UNITED STATES",
    Subregion2: "ALABAMA"
    DetailedLocation: "THE UNIVERSITY OF ALABAMA IN HUNTSVILLE"
  },
  {
    Category: "CONTINENT",
    Type: "NORTH AMERICA",
    Subregion1: "CANADA",
    Subregion2: "ONTARIO"
  }
],

History

UMM Versioning

Version	Date	What Changed
1.12.0	01/22/2019	No changes were made for Location Keywords during the transition from version 1.11.0 to 1.12.0.
1.11.0	11/28/2018	No changes were made for Location Keywords during the transition from version 1.10.0 to 1.11.0.
1.10.0	05/02/2018	No changes were made for Location Keywords during the transition from version 1.9.0 to 1.10.0.
1.9.0

ARC Documentation

Version	Date	What Changed	Author
1.0	2/1/18	Recommendations/priority matrix transferred from internal ARC documentation to wiki space	Jeanne' le Roux

Page tree

Location Keywords

Element Description

Best Practices

Element Specification

Metadata Validation and QA/QC

DIF 10

ECHO 10

ISO 19115-2 MENDS

ISO 19115-2 SMAP

UMM Migration

ISO 19115-1

History

UMM Versioning

ARC Documentation