Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Element Description

Note: this wiki page is a draft/ work in progress

The Spatial Representation Information element..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

There are eighteen sub-elements that comprise Spatial Representation Information:

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           SpatialCoverageType: Denotes whether the spatial coverage of the collection is horizontal, vertical, horizontal and vertical, orbit, or vertical and orbit.

          VerticalCoordinate System/AltitudeSystemDefinition/DatumName: The identification given to the level surface taken as the surface of reference from which measurements are compared.

  VerticalCoordinateSystem/AltitudeSystemDefinition/DistanceUnits: The units in which altitude measurements are recorded.

  VerticalCoordinateSystem/AltitudeSystemDefinition/EncodingMethod: 

  VerticalCoordinateSystem/AltitudeSystemDefinition/Resolutions: The minimum distance possible between two adjacent values, expressed in distance units of measure for the collection.

  VerticalCoordinateSystem/DepthSystemDefinition/DatumName: The identification given to the level surface taken as the surface of reference from which measurements are compared.

. 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
  VerticalCoordinateSystem/DepthSystemDefinition/DistanceUnits
      • The units in which altitude measurements are recorded.

  VerticalCoordinateSystem/DepthSystemDefinition/EncodingMethod:

  VerticalCoordinateSystem/DepthSystemDefinition/
      • 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.

  HorizontalCoordinateSystem/GeodeticModel/HorizontalDatumName: The identification given to the reference system used for defining the coordinates of points.

  HorizontalCoordinateSystem/GeodeticModel/EllipsoidName: Identification given to established representation of the Earth's shape.

  HorizontalCoordinateSystem/GeodeticModel/SemiMajorAxis: Radius of the equatorial axis of the ellipsoid.

  HorizontalCoordinateSystem/GeodeticModel/DenominatorOfFlatteningRatio: The ratio of the Earth's major axis to the difference between the major and the minor.

  HorizontalCoordinateSystem/GeographicCoordinateSystem/GeographicCoordinateUnits: Units of measure used for the geodetic latitude and longitude resolution values (e.g., decimal degrees).

  HorizontalCoordinateSystem/GeographicCoordinateSystem/LatitudeResolution: The minimum difference between two adjacent latitude values in the Geographic Coordinate System,  expressed in Geographic Coordinate Units of measure, expressed as a two-digit decimal number, e.g., 0.01.

  HorizontalCoordinateSystem/GeographicCoordinateSystem/LongitudeResolution: The minimum difference between two adjacent longitude values in the Geographic Coordinate System, expressed in Geographic Coordinate Units of measure, expressed as a two-digit decimal number, e.g., 0.01.

  HorizontalCoordinateSystem/LocalCoordinateSystem/GeoReferenceInformation: The information provided to register the local system to the Earth (e.g. control points, satellite ephemeral data, and inertial navigation data).

  HorizontalCoordinateSystem/LocalCoordinateSystem/Description: A description of the Local Coordinate System and geo-reference information.

  

          Examples:

           SpatialCoverageType"Horizontal"

           DistanceUnits: "Kilometers"

           GeoReferenceInformation: "Control Points"

           

(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.

Element Specification

Providing Spatial Information is optional (Cardinality: 0..1)

Element Specification

Providing the Spatial Representation Information element is optional (Cardinality: 0..1)

ModelElementTypeConstraintsRequired?CardinalityNotesUMM-CSpatialRepresentationInfo/SpatialCoverageTypeString

1 - 80 characters

Yes1UMM-CSpatialRepresentationInfo/VerticalCoordinateSystem/AltitudeSystemDefinition/DatumNameString








ModelElementTypeUsable Valid ValuesConstraintsRequired?CardinalityNotes
UMM-CSpatialInformation/SpatialCoverageTypeString

EARTH/GLOBAL, HORIZONTAL, VERTICAL, ORBITAL, HORIZONTAL_VERTICAL, ORBITAL_VERTICAL, HORIZONTAL_ORBITAL, HORIZONTAL_VERTICAL_ORBITAL, LUNAR

1 - 80 characters

Yes, if applicable1


UMM-CSpatialInformation/VerticalCoordinateSystem/AltitudeSystemDefinition/DatumNameStringn/a

1 - 80 characters

No0..1Recommend providing EPSG vertical datum names
UMM-CSpatialInformation/VerticalCoordinateSystem/AltitudeSystemDefinition/DistanceUnitsEnumeration

HectoPascals

Kilometers

Millibars

n/a

No0..1
UMM-CSpatialInformation/VerticalCoordinateSystem/AltitudeSystemDefinition/ResolutionsNumbern/an/aNo0..*
UMM-CSpatialInformation/VerticalCoordinateSystem/DepthSystemDefinition/DatumNameStringn/a
1 - 80 charactersNo0..1Recommend providing EPSG vertical datum names
UMM-C
SpatialRepresentationInfo
SpatialInformation/VerticalCoordinateSystem/
AltitudeSystemDefinition
DepthSystemDefinition/DistanceUnitsEnumeration

Fathoms

Feet

HectoPascals

Kilometers

Meters

Millibars

n/a


No0..1
UMM-C
SpatialRepresentationInfo
SpatialInformation/VerticalCoordinateSystem/
AltitudeSystemDefinition
DepthSystemDefinition/
EncodingMethodUMM-CSpatialRepresentationInfo/VerticalCoordinateSystem/AltitudeSystemDefinition/ResolutionsArray
Resolutions
No0..1
Numbern/an/a
No0..*
UMM-CSpatialRepresentationInfo/VerticalCoordinateSystem/DepthSystemDefinition/DatumNameString1 - 80 charactersNo0..1UMM-CSpatialRepresentationInfo/VerticalCoordinateSystem/DepthSystemDefinition/DistanceUnitsEnumeration

Fathoms

Feet

HectoPascals

Meters

Millibars

No0..1UMM-CSpatialRepresentationInfo/VerticalCoordinateSystem/DepthSystemDefinition/EncodingMethodNo0..1UMM-CSpatialRepresentationInfo/VerticalCoordinateSystem/DepthSystemDefinition/ResolutionsArrayNo0..*UMM-CSpatialRepresentationInfo/HorizontalCoordinateSystem/GeodeticModel/HorizontalDatumNameString1 - 80 charactersNo0..1UMM-CSpatialRepresentationInfo/HorizontalCoordinateSystem/GeodeticModel/EllipsoidNameString1 - 255 charactersNo0..1UMM-CSpatialRepresentationInfo/HorizontalCoordinateSystem/GeodeticModel/SemiMajorAxisNumberNo0..1UMM-CSpatialRepresentationInfo/HorizontalCoordinateSystem/GeodeticModel/DenominatorOfFlatteningRatioNumberNo0..1UMM-CSpatialRepresentationInfo/HorizontalCoordinateSystem/GeographicCoordinateSystem/GeographicCoordinateUnitsEnumeration

Decimal Degrees

Kilometers

Meters

No0..1UMM-CSpatialRepresentationInfo/HorizontalCoordinateSystem/GeographicCoordinateSystem/LatitudeResolution

Number

No0..1UMM-CSpatialRepresentationInfo/HorizontalCoordinateSystem/GeographicCoordinateSystem/LongitudeResolutionNumberNo0..1UMM-CSpatialRepresentationInfo/HorizontalCoordinateSystem/LocalCoordinateSystem/GeoReferenceInformationString1 - 2048 charactersNo0..1UMM-CSpatialRepresentationInfo/HorizontalCoordinateSystem/LocalCoordinateSystem/DescriptionString1 - 2048 charactersNo0..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).

Lucidchartrich-viewerfalseautofittruenameCopy of Wiki Page Metadata Evaluation Workflow-1939-51df84width1102pages-to-displayid98e5dc28-3252-4209-953f-66f1378e1cf4alignLeftheight299

Please see the expandable sections below for flowchart details.

Expand
titleGCMD Metadata QA/QC
  • Manual Review
  • Automated Review
    Expand
    titleCMR Validation

    <>

    Expand
    titleARC Metadata QA/QC

    ARC Priority Matrix

    Priority CategorizationJustification

    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.
    The element is provided and follows all applicable criteria specified in the best practices section above.

    ARC Automated Rules

    If novalue is provided, return is "np."
  • Otherwise, return is "OK."
  • Dialect Mappings

    Expand
    titleDIF 9

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




    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-viewerfalse
    autofittrue
    nameCopy of Wiki Page Metadata Evaluation Workflow-1939-51df84
    width1102
    pages-to-display
    id98e5dc28-3252-4209-953f-66f1378e1cf4
    alignLeft
    height299

    Please see the expandable sections below for flowchart details.


    Expand
    titleGCMD Metadata QA/QC
    • Manual Review
      • Identify errors, discrepancies or omissions.
      • Proof all content for conciseness and readability.
    Expand
    titleCMR Validation

    None

    Expand
    titleARC Metadata QA/QC

    ARC Priority Matrix

    Priority CategorizationJustification

    Red = High Priority Finding

    This element is categorized as highest priority when:

    • Spatial Information is provided but the required 'Spatial Information Type' field is not included.
    • An invalid value is provided for 'Distance Units' ('DistanceUnits' must be selected from an enumeration list).
    • An invalid value is provided for 'GeographicCoordinateUnits' ('GeographicCoordinateUnits' must be selected from an enumeration list).
    • The information provided is incorrect for the dataset.

    Yellow = Medium Priority Finding

    Not Applicable

    Blue = Low Priority Finding

    This element is categorized as low priority when:

    • A recommendation is made to provide any additional information to existing Spatial Information provided in the metadata.

    Green = No Findings/Issues

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

    ARC Automated Checks

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

    Dialect Mappings

    Expand
    titleDIF 10

    DIF 10

    Providing 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.

    UMM-C ElementDIF 10 PathTypeConstraintsRequired in DIF 10?CardinalityNotes
    SpatialInformation/SpatialCoverageType
    Spatial_Coverage/Spatial_Info/Spatial_Coverage_TypeEnumeration

    Earth/Global, Horizontal, Vertical, Orbit, HorizontalVertical, Orbital_Vertical, Horizontal_Orbital, Horizontal_Vertical_Orbital, Lunar

    Yes, if applicable1Horizon&amp;Vert has been deprecated, use HorizontalVertical instead
    n/aData_Resolution/Vertical_ResolutionString


    No0..1
    n/aData_Resolution/ Vertical_Resolution_UnitString
    No0..1
    n/aData_Resolution/Vertical_Resolution_RangeStringKMS controlledNo0..1Recommend selecting a value from the GCMD Vertical Data Resolution keywords to populate this field
    n/aData_Resolution/Temporal_ResolutionString
    No0..1Note: this field does not map to any other metadata elements and is unique to DIF 10.
    n/aData_Resolution/Temporal_Resolution_Range StringKMS controlledNo0..1

    Recommend selecting a value from the GCMD Vertical Data Resolution keywords to populate this field

    Note: this field does not map to any other metadata elements and is unique to DIF 10.


    Enumeration Mapping

    DIF 10Translation DirectionUMM

    Earth/Global

    EARTH/GLOBAL

    Horizontal

    HORIZONTAL

    HorizontalVerticalHORIZONTAL_VERTICAL
    OrbitORBITAL
    VerticalVERTICAL
    Horizon&amp;VertHORIZONTAL_VERTICAL
    Orbital_VerticalORBITAL_VERTICAL
    Horizontal_OrbitalHORIZONTAL_ORBITAL
    Horizontal_Vertical_OrbitalHORIZONTAL_VERTICAL_ORBITAL
    LunarLUNAR


    Example Mapping

    Section
    Column
    width50%

    DIF 10

    No Format
    <Spatial_Coverage> 
      <Spatial_Info>
        <Spatial_Coverage_Type>Horizontal</Spatial_Coverage_Type>
      </Spatial_Info>
    </Spatial_Coverage>
    ----------------------------------------------------------------------------------------------------------------------------
    <Data_Resolution>
      <Temporal_Resolution>Hourly - < Daily</Temporal_Resolution>
    </Data_Resolution>
    Column
    width50%

    UMM

    No Format
    "SpatialInformation": [
      {
        "SpatialCoverageType": "HORIZONTAL",
      }
    ]	
    Expand
    titleECHO 10

    ECHO 10

    Providing the Spatial Info element is optional in ECHO 10 (Cardinality: 0..1)

    UMM-C ElementECHO 10 PathTypeConstraintsRequired in ECHO10?CardinalityNote
    SpatialInformation/SpatialCoverageTypeSpatialInfo/SpatialCoverageTypeString

    1 - 80 characters

    Yes, if applicable1

    This attribute denotes whether the collection's spatial coverage requires horizontal, vertical, or both in the spatial domain and coordinate system definitions. This field is not controlled in ECHO 10, however, it is recommended that one of the UMM SpatialCoverageType enumeration values be provided in order to reduce translation errors (HORIZONTAL, VERTICAL, ORBITAL, HORIZONTAL_VERTICAL, ORBITAL_VERTICAL)

    SpatialInformation/VerticalCoordinateSystem/AltitudeSystemDefinition/DatumName
    SpatialInfo/VerticalCoordinateSystem/AltitudeSystemDefinition/DatumNameString

    1 - 80 characters

    No0..1Recommend providing EPSG vertical datum names
    SpatialInformation/VerticalCoordinateSystem/AltitudeSystemDefinition/DistanceUnits
    SpatialInfo/VerticalCoordinateSystem/AltitudeSystemDefinition/DistanceUnitsString

    1 - 80 characters

    No0..1
    SpatialInformation/VerticalCoordinateSystem/AltitudeSystemDefinition/EncodingMethod
    SpatialInfo/VerticalCoordinateSystem/AltitudeSystemDefinition/EncodingMethodString

    1 - 2048 characters

    No0..1

    The means used to encode measurements.

    SpatialInformation/VerticalCoordinateSystem/AltitudeSystemDefinition/Resolutions
    SpatialInfo/VerticalCoordinateSystem/AltitudeSystemDefinition/Resolutions/ResolutionDecimaln/aNo0..*

    This entity stores the minimum distance possible between two adjacent values, expressed in the distance units of measure for collection.

    A list of vertical resolutions may be provided here.
    SpatialInformation/VerticalCoordinateSystem/DepthSystemDefinition/DatumName
    SpatialInfo/VerticalCoordinateSystem/DepthSystemDefinition/DatumNameString

    1 - 80 characters

    No0..1Recommend providing EPSG vertical datum names
    SpatialInformation/VerticalCoordinateSystem/DepthSystemDefinition/DistanceUnits
    SpatialInfo/VerticalCoordinateSystem/DepthSystemDefinition/DistanceUnitsString

    1 - 80 characters

    No0..1
    SpatialInformation/VerticalCoordinateSystem/DepthSystemDefinition/EncodingMethod
    SpatialInfo/VerticalCoordinateSystem/DepthSystemDefinition/EncodingMethodString

    1 - 2048 characters

    No0..1The means used to encode measurements.
    SpatialInformation/VerticalCoordinateSystem/DepthSystemDefinition/Resolutions
    SpatialInfo/VerticalCoordinateSystem/DepthSystemDefinition/Resolutions/ResolutionDecimaln/aNo0..*

    This entity stores the minimum distance possible between two adjacent values, expressed in the distance units of measure for collection.

    A list of vertical resolutions may be provided here.


    Example Mapping

    Section
    Column
    width50%

    ECHO 10

    No Format
    <SpatialInfo>
      <SpatialCoverageType>HORIZONTAL_VERTICAL</SpatialCoverageType>
      <VerticalCoordinateSystem> 
        <AltitudeSystemDefinition> 
          <DatumName>North American Vertical Datum 1988</DatumName>
          <DistanceUnits>Kilometers</DistanceUnits>
          <Resolutions>
    	    <Resolution>10</Resolution>
          </Resolutions>
        </AltitudeSystemDefinition>
      </VerticalCoordinateSystem>
    </SpatialInfo>
    Column
    width50%

    UMM

    No Format
    "SpatialInformation": {
      "SpatialCoverageType": "HORIZONTAL_VERTICAL",
      "VerticalCoordinateSystem": {
        "AltitudeSystemDefinition": [
          {
            "DatumName": "North American Vertical Datum 1988",
            "DistanceUnits": "Kilometers",
            "Resolutions": "10"
          }
        ]
      }
    }

    UMM Migration

    N/A

    History

    UMM Versioning

    VersionDateWhat Changed
    1.18.02024-03-18Updated Spatial Coverage Type enumeration list for 1.18.0
    1.15.52020-12-03No changes were made for Spatial Information during the transition from version 1.15.4 to 1.15.5
    1.15.42020-09-18No changes were made for Spatial Information during the transition from version 1.15.3 to 1.15.4
    1.15.32020-07-01No changes were made for Spatial Information during the transition from version 1.15.2 to 1.15.3
    1.15.22020-05-20No changes were made for Spatial Information during the transition from version 1.15.1 to 1.15.2
    1.15.12020-03-25No changes were made for Spatial Information during the transition from version 1.15.0 to 1.15.1
    1.15.02020-02-26No changes were made for Spatial Information during the transition from version 1.14.0 to 1.15.0
    1.14.02019-10-21The Horizontal Coordinate System element and all supporting elements were either removed or renamed and moved to the SpatialExtent element.
    1.13.02019-04-11No changes were made for Spatial Information during the transition from version 1.12.0 to 1.13.0
    1.12.02019-01-22No changes were made for Spatial Information during the transition from version 1.11.0 to 1.12.0.
    1.11.02018-11-28No changes were made for Spatial Information during the transition from version 1.10.0 to 1.11.0.
    1.10.02018-05-02

    During the transition from version 1.9.0 to 1.10.0:

    • The sub element 'GeographicCoordinateUnits' was added and enumerated
    • The sub element 'EncodingMethod' was removed from both 'AltitudeSystemDefinitionType' and 'DepthSystemDefinitionType'
    • 'VerticalSystemDefinitionType' was replaced with both 'AltitudeSystemDefinitionType' and 'DepthSystemDefinitionType'
    • Free text strings were changed to enumeration for the following sub elements within 'AltitudeSystemDefinitionType' and 'DepthSystemDefinitionType': 'AltitudeDistanceUnitsEnum' and 'DepthSystemDefinitionType.'
    Expand
    titleDIF 10
    DIF 10

    Providing the Reference element is optional (Cardinality: 0..*)

    SpecificationPathTypeConstraintsRequired in DIF 10?CardinalityNotesDIF 10Reference/CitationStringNo0..1DIF 10Reference/AuthorStringNo0..1DIF 10Reference/Publication_DateStringNo0..1DIF 10Reference/TitleStringNo0..1DIF 10Reference/SeriesStringNo0..1DIF 10Reference/EditionStringNo0..1DIF 10Reference/VolumeStringNo0..1DIF 10Reference/IssueStringNo0..1DIF 10Reference/Report_NumberStringNo0..1DIF 10Reference/Publication_PlaceStringNo0..1DIF 10Reference/PublisherStringNo0..1DIF 10Reference/PagesStringNo0..1DIF 10Reference/ISBN

    String

    Yes1DIF 10Reference/Persistent_Identifier/IdentifierStringYes1DIF 10Reference/Persistent_Identifier/TypeEnumeration

    DOI

    ARK

    Yes1Refer to DOI to view description of sub-element paths within Persistent_IdentifierDIF 10Reference/Online_ResourceanyURINo0..1DIF 10Reference/Other_Reference_DetailsStringNo0..1Example Mapping
    Section
    Column
    width50%

    DIF 10

    No Format
    <Reference>
    	<Publication_Date>1996-01-01</Publication_Date>
    	<Series>Monthly Weather Review</Series>
    	<Title>Data assimilation using incremental analysis updates</Title>
    	<Pages>1256-1271</Pages>
    	<Issue>124</Issue>
    </Reference>
    <Reference>
    	<Publication_Date>2005-01-01</Publication_Date>
    	<Series>Technical Report Series on Global Modeling and Data Assimilation</Series>
    	<Title>Documentation and Validation of the Goddard Earth Observing System (GEOS) Data Assimilation System - Version 4</Title>
    	<Edition>104606</Edition>
    	<Volume>26</Volume>
    	<Author>Bloom, S., A. da Silva, D. Dee, M. Bosilovich, J.-D. Chern, S. Pawson, S. Schubert, M. Sienkiewicz, I. Stajner, W.-W. Tan, M.-L. Wu</Author>
    </Reference>
    <Reference>
    	<Publication_Date>2005-01-01</Publication_Date>
    	<Series>International Journal of High Performance Computing Applications</Series>
    	<Title>Design and implementation of components in the Earth System Modeling Framework</Title>
    	<Persistent_Identifier>
    	    <Type>DOI</Type>
    	    <Identifier>10.1177/1094342005056120</Identifier>
    	</Persistent_Identifier>
    	<Pages>341-350</Pages>
    	<Volume>19</Volume>
    	<Author>Collins, N., G. Theurich, C. DeLuca, M. Suarez, A. Trayanov, V. Balaji, P. Li, W. Yang, C. Hill, and A. da Silva</Author>
    </Reference>
    
    
    Column
    width50%

    UMM

    No Format
    PublicationReferences: [
        {
            PublicationDate: "1996-01-01T00:00:00.000Z",
            Series: "Monthly Weather Review",
            Title: "Data assimilation using incremental analysis updates",
            Pages: "1256-1271",
            Author: "Bloom, S., L. Takacs, A. DaSilva, and D. Ledvina",
            Issue: "124"
        },
        {
            PublicationDate: "2005-01-01T00:00:00.000Z",
            Series: "Technical Report Series on Global Modeling and Data Assimilation",
            Title: "Documentation and Validation of the Goddard Earth Observing System (GEOS) Data Assimilation System - Version 4",
            Edition: "104606",
            Volume: "26",
            Author: "Bloom, S., A. da Silva, D. Dee, M. Bosilovich, J.-D. Chern, S. Pawson, S. Schubert, M. Sienkiewicz, I. Stajner, W.-W. Tan, M.-L. Wu"
        },
        {
            PublicationDate: "2005-01-01T00:00:00.000Z",
            Series: "International Journal of High Performance Computing Applications",
            Title: "Design and implementation of components in the Earth System Modeling Framework",
            DOI: {
              DOI: "10.1177/1094342005056120"
            },
            Pages: "341-350",
            Volume: "19",
            Author: "Collins, N., G. Theurich, C. DeLuca, M. Suarez, A. Trayanov, V. Balaji, P. Li, W. Yang, C. Hill, and A. da Silva"
        },
    ]
    Expand
    titleECHO 10

    ECHO 10

    Publication Reference does not map to ECHO 10.

    SpecificationPathTypeConstraintsRequired in ECHO10?CardinalityNoteECHO 10N/AN/A

    N/A

    N/AN/APublication Reference does not map to ECHO10.Example Mapping
    Section
    Column
    width50%

    ECHO 10

    No Format
    N/A  
    Column
    width50%

    UMM

    No Format
    PublicationReferences: [
        {
            PublicationDate: "1996-01-01T00:00:00.000Z",
            Series: "Monthly Weather Review",
            Title: "Data assimilation using incremental analysis updates",
            Pages: "1256-1271",
            Author: "Bloom, S., L. Takacs, A. DaSilva, and D. Ledvina",
            Issue: "124"
        },
        {
            PublicationDate: "2005-01-01T00:00:00.000Z",
            Series: "Technical Report Series on Global Modeling and Data Assimilation",
            Title: "Documentation and Validation of the Goddard Earth Observing System (GEOS) Data Assimilation System - Version 4",
            Edition: "104606",
            Volume: "26",
            Author: "Bloom, S., A. da Silva, D. Dee, M. Bosilovich, J.-D. Chern, S. Pawson, S. Schubert, M. Sienkiewicz, I. Stajner, W.-W. Tan, M.-L. Wu"
        },
        {
            PublicationDate: "2005-01-01T00:00:00.000Z",
            Series: "International Journal of High Performance Computing Applications",
            Title: "Design and implementation of components in the Earth System Modeling Framework",
            DOI: {
              DOI: "10.1177/1094342005056120"
            },
            Pages: "341-350",
            Volume: "19",
            Author: "Collins, N., G. Theurich, C. DeLuca, M. Suarez, A. Trayanov, V. Balaji, P. Li, W. Yang, C. Hill, and A. da Silva"
        },
    ]
    Expand
    titleISO 19115-2 MENDS

    ISO 19115-2 MENDS

    Providing the Publication Reference element is not required (Cardinality: 0..*)

    SpecificationPathTypeNotesISO 19115-2 MENDS/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:aggregateDataSetName/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:individualName or  gmd:/organisationName with
    /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"

    ISO 19115-2 MENDS/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:aggregateDataSetName/gmd:CI_Citation/gmd:titleStringMaps to the UMM element "PublicationReference/Title"ISO 19115-2 MENDS/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:aggregateDataSetName/gmd:CI_Citation/gmd:series/gmd:CI_Series/gmd:nameStringMaps to the UMM element "PublicationReference/Series"ISO 19115-2 MENDS/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:aggregateDataSetName/gmd:CI_Citation/gmd:editionStringMaps to the UMM element "PublicationReference/Edition"ISO 19115-2 MENDS/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:aggregateDataSetName/gmd:CI_Citation/gmd:ISBNStringMaps to the UMM element "PublicationReference/ISBN"ISO 19115-2 MENDS/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:aggregateDataSetName/gmd:CI_Citation/gmd:identifier/gmd:MD_Identifier/gmd:authority/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:organisationName or gmd:individualNameStringMaps to the UMM element "PublicationReference/DOI/Authority"ISO 19115-2 MENDS/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:aggregateDataSetName/gmd:CI_Citation/gmd:identifier/gmd:MD_Identifier/gmd:code/gco:CharacterString
    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.doiStringMaps to the UMM element "PublicationReference/DOI/DOI"ISO 19115-2 MENDS/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:aggregateDataSetName/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:onlineResource/gmd:CI_OnlineResource/gmd:linkage/gmd:URLStringMaps to the UMM element "PublicationReference/OnlineResource/Linkage"ISO 19115-2 MENDS/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:aggregateDataSetName/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:onlineResource/gmd:CI_OnlineResource/gmd:protocol/gco:CharacterStringStringMaps to the UMM element "PublicationReference/OnlineResource/Protocol"ISO 19115-2 MENDS/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:aggregateDataSetName/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:onlineResource/gmd:CI_OnlineResource/gmd:applicationProfile/gco:CharacterStringStringMaps to the UMM element "PublicationReference/OnlineResource/AplicationProfile"ISO 19115-2 MENDS/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:aggregateDataSetName/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:onlineResource/gmd:CI_OnlineResource/gmd:name/gco:CharacterStringStringMaps to the UMM element "PublicationReference/OnlineResource/Name"ISO 19115-2 MENDS/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:aggregateDataSetName/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:onlineResource/gmd:CI_OnlineResource/gmd:description/gco:CharacterString="Description:" and "PublicationReference:"StringMaps to the UMM element "PublicationReference/OnlineResource/Description"ISO 19115-2 MENDS/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:aggregateDataSetName/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:onlineResource/gmd:CI_OnlineResource/gmd:function/gmd:CI_OnLineFunctionCode codeList="codeListLocation#CI_OnLineFunctionCode" codeListValue="" StringMaps to the UMM element "PublicationReference/OnlineResource/Function"Example Mapping
    Section
    Column
    width50%

    ISO 19115-2 MENDS

    No Format
    ADD EXAMPLE
    
    
    Column
    width50%

    UMM

    No Format
    PublicationReferences: [
        {
            PublicationDate: "1996-01-01T00:00:00.000Z",
            Series: "Monthly Weather Review",
            Title: "Data assimilation using incremental analysis updates",
            Pages: "1256-1271",
            Author: "Bloom, S., L. Takacs, A. DaSilva, and D. Ledvina",
            Issue: "124"
        },
        {
            PublicationDate: "2005-01-01T00:00:00.000Z",
            Series: "Technical Report Series on Global Modeling and Data Assimilation",
            Title: "Documentation and Validation of the Goddard Earth Observing System (GEOS) Data Assimilation System - Version 4",
            Edition: "104606",
            Volume: "26",
            Author: "Bloom, S., A. da Silva, D. Dee, M. Bosilovich, J.-D. Chern, S. Pawson, S. Schubert, M. Sienkiewicz, I. Stajner, W.-W. Tan, M.-L. Wu"
        },
        {
            PublicationDate: "2005-01-01T00:00:00.000Z",
            Series: "International Journal of High Performance Computing Applications",
            Title: "Design and implementation of components in the Earth System Modeling Framework",
            DOI: {
              DOI: "10.1177/1094342005056120"
            },
            Pages: "341-350",
            Volume: "19",
            Author: "Collins, N., G. Theurich, C. DeLuca, M. Suarez, A. Trayanov, V. Balaji, P. Li, W. Yang, C. Hill, and A. da Silva"
        },
    ]
    Expand
    titleISO 19115-2 SMAP

    ISO 19115-2 SMAP

    Providing the Publication Reference element is not required (Cardinality: 0..*)

    SpecificationPathTypeNotesISO 19115-2 SMAP/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:individualName or  gmd:/organisationName
    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"

    ISO 19115-2 SMAP/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:aggregateDataSetName/gmd:CI_Citation/gmd:titleStringMaps to the UMM element "PublicationReference/Title"ISO 19115-2 SMAP/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:aggregateDataSetName/gmd:CI_Citation/gmd:series/gmd:CI_Series/gmd:nameStringMaps to the UMM element "PublicationReference/Series"ISO 19115-2 SMAP/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:aggregateDataSetName/gmd:CI_Citation/gmd:editionStringMaps to the UMM element "PublicationReference/Edition"ISO 19115-2 SMAP/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:aggregateDataSetName/gmd:CI_Citation/gmd:ISBNStringMaps to the UMM element "PublicationReference/ISBN"ISO 19115-2 SMAP/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:authority/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:organisationName or gmd:individualNameStringMaps to the UMM element "PublicationReference/DOI/Authority"ISO 19115-2 SMAP/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:code/gco:CharacterString
    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.doiStringMaps to the UMM element "PublicationReference/DOI/DOI"ISO 19115-2 SMAP/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:contactInfo/gmd:onlineResource/gmd:CI_OnlineResource/gmd:linkage/gmd:URLStringMaps to the UMM element "PublicationReference/OnlineResource/Linkage"ISO 19115-2 SMAP/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:contactInfo/gmd:onlineResource/gmd:CI_OnlineResource/gmd:protocol/gco:CharacterStringStringMaps to the UMM element "PublicationReference/OnlineResource/Protocol"ISO 19115-2 SMAP/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:contactInfo/gmd:onlineResource/gmd:CI_OnlineResource/gmd:applicationProfile/gco:CharacterStringStringMaps to the UMM element "PublicationReference/OnlineResource/AplicationProfile"ISO 19115-2 SMAP/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:contactInfo/gmd:onlineResource/gmd:CI_OnlineResource/gmd:name/gco:CharacterStringStringMaps to the UMM element "PublicationReference/OnlineResource/Name"ISO 19115-2 SMAP/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:contactInfo/gmd:onlineResource/gmd:CI_OnlineResource/gmd:description/gco:CharacterStringStringMaps to the UMM element "PublicationReference/OnlineResource/Description"ISO 19115-2 SMAP/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:contactInfo/gmd:onlineResource/gmd:CI_OnlineResource/gmd:function/gmd:CI_OnLineFunctionCode codeList="codeListLocation#CI_OnLineFunctionCode" codeListValue="" StringMaps to the UMM element "PublicationReference/OnlineResource/Function"Example Mapping
    Section
    Column
    width50%

    ISO 19115-2 SMAP

    No Format
    ADD EXAMPLE
    Column
    width50%

    UMM

    No Format
    PublicationReferences: [
        {
            PublicationDate: "1996-01-01T00:00:00.000Z",
            Series: "Monthly Weather Review",
            Title: "Data assimilation using incremental analysis updates",
            Pages: "1256-1271",
            Author: "Bloom, S., L. Takacs, A. DaSilva, and D. Ledvina",
            Issue: "124"
        },
        {
            PublicationDate: "2005-01-01T00:00:00.000Z",
            Series: "Technical Report Series on Global Modeling and Data Assimilation",
            Title: "Documentation and Validation of the Goddard Earth Observing System (GEOS) Data Assimilation System - Version 4",
            Edition: "104606",
            Volume: "26",
            Author: "Bloom, S., A. da Silva, D. Dee, M. Bosilovich, J.-D. Chern, S. Pawson, S. Schubert, M. Sienkiewicz, I. Stajner, W.-W. Tan, M.-L. Wu"
        },
        {
            PublicationDate: "2005-01-01T00:00:00.000Z",
            Series: "International Journal of High Performance Computing Applications",
            Title: "Design and implementation of components in the Earth System Modeling Framework",
            DOI: {
              DOI: "10.1177/1094342005056120"
            },
            Pages: "341-350",
            Volume: "19",
            Author: "Collins, N., G. Theurich, C. DeLuca, M. Suarez, A. Trayanov, V. Balaji, P. Li, W. Yang, C. Hill, and A. da Silva"
        },
    ]

    UMM Migration

    UMM Version 1.9.0Translation DirectionUMM Version 1.10.0

    Future Mappings

    Expand
    titleISO 19115-1

    ISO 19115-1

    Providing the Publication Reference element is not required (Cardinality: 0..*)

    SpecificationPathTypeNotesISO 19115-1/mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:citation/cit:CI_Citation/cit:citedResponsibleParty/cit:CI_Responsibility/cit:party/
    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=authorStringMaps to the UMM element "PublicationReference/Authors"ISO 19115-1/mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:citation/cit:CI_Citation/cit:titleStringMaps to the UMM element "PublicationReference/Title"ISO 19115-1/mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:citation/cit:CI_Citation/cit:series/cit:CI_Series/cit:nameStringMaps to the UMM element "PublicationReference/Series"ISO 19115-1/mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:citation/cit:CI_Citation/cit:editionStringMaps to the UMM element "PublicationReference/Edition"ISO 19115-1/mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:citation/cit:CI_Citation/cit:ISBNStringMaps to the UMM element "PublicationReference/ISBN"ISO 19115-1/mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:citation/cit:CI_Citation/cit:citedResponsibleParty/cit:CI_Responsibility/cit:party/
    cit:CI_Individual/cit:name or cit:CI_Organization/cit:nameStringMaps to the UMM element "PublicationReference/DOI/Authority"ISO 19115-1/mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:citation/cit:CI_Citation/cit:identifier/mcc:MD_Identifier/mcc:code/gco:CharacterString
    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.doiStringMaps to the UMM element "PublicationReference/DOI/DOI"
    Example Mapping
    Section
    Column
    width50%

    ISO 19115-1

    No Format
    ADD EXAMPLE
    Column
    width50%

    UMM

    No Format
    PublicationReferences: [
        {
            PublicationDate: "1996-01-01T00:00:00.000Z",
            Series: "Monthly Weather Review",
            Title: "Data assimilation using incremental analysis updates",
            Pages: "1256-1271",
            Author: "Bloom, S., L. Takacs, A. DaSilva, and D. Ledvina",
            Issue: "124"
        },
        {
            PublicationDate: "2005-01-01T00:00:00.000Z",
            Series: "Technical Report Series on Global Modeling and Data Assimilation",
            Title: "Documentation and Validation of the Goddard Earth Observing System (GEOS) Data Assimilation System - Version 4",
            Edition: "104606",
            Volume: "26",
            Author: "Bloom, S., A. da Silva, D. Dee, M. Bosilovich, J.-D. Chern, S. Pawson, S. Schubert, M. Sienkiewicz, I. Stajner, W.-W. Tan, M.-L. Wu"
        },
        {
            PublicationDate: "2005-01-01T00:00:00.000Z",
            Series: "International Journal of High Performance Computing Applications",
            Title: "Design and implementation of components in the Earth System Modeling Framework",
            DOI: {
              DOI: "10.1177/1094342005056120"
            },
            Pages: "341-350",
            Volume: "19",
            Author: "Collins, N., G. Theurich, C. DeLuca, M. Suarez, A. Trayanov, V. Balaji, P. Li, W. Yang, C. Hill, and A. da Silva"
        },
    ]

    History

    UMM Versioning

    VersionDateWhat Changed1.10.05/2/2018

    No changes were made for Collection Data Type during the transition from version 1.9.0 to 1.10.0

    1.9.0

    ARC Documentation

    VersionDateWhat ChangedAuthor
    1.011/16/182019-02-15Recommendations/priority matrix transferred from internal ARC documentation to wiki space