Page tree

 

 

 

 

Revision 1.2

Earth Science Data and Information Systems (ESDIS) Project, Code 423

 

 

Unified Metadata Model Services (UMM-S)

 


 

 

 

Signature/Approval Page

 

 

 

Prepared by:

 

 

 

 

 

 

 

Name

 

Date

Title/Role

 

 

Organization

 

 

 

 

 

Reviewed by:

 

 

 

 

 

 

 

Name

 

Date

Title/Role

 

 

Organization

 

 

 

 

 

Approved by:

 

 

 

 

 

 

 

Name

 

Date

Title/Role

 

 

Organization

 

 

 

 

 

Concurred by:

 

 

 

 

 

 

 

Name

 

Date

Title/Role

 

 

Organization

 

 

 

[Electronic] Signatures available in B32 Room E148

online at: / https://ops1-cm.ems.eosdis.nasa.gov/cm2/


Preface

This document is under ESDIS Project configuration control. Once this document is approved, ESDIS approved changes are handled in accordance with Class I and Class II change control requirements described in the ESDIS Configuration Management Procedures, and changes to this document shall be made by change bars or by complete revision.

 

Any questions should be addressed to: esdis-esmo-cmo@lists.nasa.gov

ESDIS Configuration Management Office (CMO)
NASA/GSFC

Code 423

Greenbelt, Md. 20771


Abstract

This document describes the Unified Metadata Model for Services (UMM-S) to be used by the NASA Earth Science community and addresses the need for describing services available on data which is managed by repositories contributing their metadata to CMR. This community needs services that transform structured data into a form that is convenient to the end user. Developers, engineers and architects should reference this document and the UMM as a guide while implementing CMR components, CMR clients or services that make use of the CMR or CMR clients.

 

This version of the service model focuses on what is the minimum service metadata needed to support the User Interface/User Experience (UI/UX) leading to an improved user experience. In general, the Unified Metadata Model (UMM) covers both data and services. While the UMM-C (Collection), UMM-G (Granule) and UMM-Var (Variables) consider data, the UMM-S (Service) considers only services.

 

 

Keywords: UMM-S, UMM-Common, UMM-C, UMM-G, UMM-Var, Services, NASA Earthdata Search, Tools, EOSDIS, ESDIS, CMR, GCMD, SERF

Change History Log

Revision

Effective Date

Description of Changes

V0.1.0

February 2015

  • Provisional Release.

V0.1.1

February 2015

  • Added ISO 19115-1

V0.1.2

May 2015

  • Added Normalize to Publication Reference

V0.1.3

July 2015

  • Added Normalize to Publication Reference
  • Updated from June 2015 Earth Science Data and Information System (ESDIS) Standards Office (ESO) review comments.
  • Changed the Parameter Search tag to Search API.
  • Removed Metadata Standard
  • Changed Metadata Dates to Metadata Date
  • Removed Lineage
  • Removed Data Dates

V0.1.4

September 2017

  • Revised for End-to-End Services Design

V1.0.0

December 2017

  • Revised for addition of SERF fields

V1.1.0

April 2018

  • Revised to change cardinality for RelatedURLs, AccessConstraints, and UseConstraints to accommodate SERF record data.

V1.2.0

June 2018

  • Revised to address the ESO UMM-S 10/2017 review comments.

 

 


Table of Contents

1 Introduction

1.1 Purpose

1.2 Scope

1.3 Impact

1.4 Copyright Notice

1.5 Feedback

1.6 Document Conventions

1.7 Related Documentation

1.7.1 Applicable Documents

1.7.2 Reference Documents

2 Services Metadata Conceptual Model

2.1 Use Cases

2.1.1 Collection Search

2.1.2 Operation Request to a Web Service

2.2 UMM-S Metadata Model

2.2.1 Service

2.2.1.1 Name [R]

2.2.1.2 LongName [R]

2.2.1.3 Type [R]

2.2.1.4 Version [R]

2.2.1.5 Description [R]

2.2.1.6 RelatedURLs [R]

2.2.1.7 OperationMetadata

2.2.1.7.1 OperationName

2.2.1.7.2 DistributedComputingPlatform

2.2.1.7.3 OperationDescription

2.2.1.7.4 InvocationName

2.2.1.7.5 ConnectPoint

2.2.1.7.5.1 ResourceName

2.2.1.7.5.2 ResourceLinkage [R]

2.2.1.7.5.3 ResourceDescription

2.2.1.7.6 OperationChainMetadata

2.2.1.7.6.1 OperationChainName [R]

2.2.1.7.6.2 OperationChainDescription

2.2.1.7.7 CoupledResource

2.2.1.7.7.1 ScopedName

2.2.1.7.7.2 DataResourceDOI

2.2.1.7.7.3 DataResource

2.2.1.7.7.4 DataResourceIdentifier [R]

2.2.1.7.7.5 DataResourceType [R]

2.2.1.7.7.6 DataResourceSpatialExtent [R]

2.2.1.7.7.7 DataResourceSpatialExtentType [R]

2.2.1.7.7.8 SpatialResolution [R]

2.2.1.7.7.9 SpatialResolutionUnit [R]

2.2.1.7.7.10 DataResourceTemporalExtent [R]

2.2.1.7.7.11 DataResourceTemporalExtentType [R]

2.2.1.7.7.12 TemporalResolution [R]

2.2.1.7.7.13 TemporalResolutionUnit [R]

2.2.1.7.7.14 RelativePath

2.2.1.7.7.15 CouplingType

2.2.1.7.8 Parameter

2.2.1.7.8.1 ParameterName [R]

2.2.1.7.8.2 ParameterDirection [R]

2.2.1.7.8.3 ParameterDescription [R]

2.2.1.7.8.4 ParameterOptionality [R]

2.2.1.7.8.5 ParameterRepeatability [R]

2.2.1.8 OnlineAccessURLPatternMatch

2.2.1.9 OnlineAccessURLPatternSubstitution

2.2.1.10 ScienceKeywords

2.2.1.11 ServiceKeywords [R]

2.2.1.12 ServiceOrganizations [R]

2.2.1.13 ServiceContacts [R]

2.2.1.13.1 ContactPersons

2.2.1.13.2 ContactGroups

2.2.1.14 Platforms

2.2.1.14.1 Instruments

2.2.1.15 ServiceQuality

2.2.1.16 ServiceCitation [R]

2.2.1.17 AccessConstraints

2.2.1.18 UseConstraints

2.2.1.19 AncillaryKeywords

2.2.2 Options

2.2.2.1 SubsetTypes

2.2.2.2 VariableAggregation

2.2.2.3 SupportedInputProjections

2.2.2.3.1 ProjectionName

2.2.2.3.2 ProjectionLatitudeOfCenter

2.2.2.3.3 ProjectionLongitudeOfCenter

2.2.2.3.4 ProjectionFalseEasting

2.2.2.3.5 ProjectionFalseNorthing

2.2.2.3.6 ProjectionAuthority

2.2.2.3.7 ProjectionUnit

2.2.2.3.8 ProjectionDatumName

2.2.2.4 SupportedOutputProjections

2.2.2.4.1 ProjectionName

2.2.2.4.2 ProjectionLatitudeOfCenter

2.2.2.4.3 ProjectionLongitudeOfCenter

2.2.2.4.4 ProjectionFalseEasting

2.2.2.4.5 ProjectionFalseNorthing

2.2.2.4.6 ProjectionAuthority

2.2.2.4.7 ProjectionUnit

2.2.2.4.8 ProjectionDatumName

2.2.2.5 InterpolationTypes

2.2.2.6 SupportedInputFormats

2.2.2.7 SupportedOutputFormats

2.2.2.8 MaxGranules

Appendix A. Deprecated Elements

Appendix B. Tags Glossary

Appendix C. Abbreviations and Acronyms

List of Figures

Figure 1: UMM Relationships showing key associations

Figure 2: Collection Search Use Case

Figure 3: Collection Search Activity Diagram

Figure 4: Collection Search Sequence Diagram

Figure 5: Operation Request to a Web Service Use Case

Figure 6: Operation Request to a Web Service Activity Diagram

Figure 7: Operation Request to a Web Service Sequence Diagram

Figure 8: Overall Service Model

Figure 9: GeoTIFF file returned in the server response from a GetCoverage request for the AIRS3STD:SurfAirTemp_D_timeAveraged coverage

Figure 10: GeoTIFF file returned in the server response from a GetCoverage request for the 980_14 coverage

Figure 11: PNG file returned in the server response from GetMap request for the /sdat/config/mapfile//1286/1286_1_wms.map map

Figure 12: 32-bit GeoTIFF part of the multipart response from a GetCoverage request for the permafrost_extent coverage

List of Tables

Table 1: Cardinality

Table 2: Applicable Documents

Table 3: Reference Documents

Table 4: Tags Glossary

Table 5: Abbreviations and Acronyms

 

 


 

1           Introduction

EOSDIS generates, archives, and distributes massive amounts of Earth Science data, which in turn are made available to the science community and the public at large. To aid in the search and discovery process, these data must be organized and cataloged, which makes accurate, complete, and consistent metadata a requirement for efficient accessibility.   To improve the quality and consistency among its metadata holdings, EOSDIS has developed a model describing metadata that it archives and maintains. The model represents CMR metadata elements that are useful for discovery​ and maps them to various metadata standards. This unified model, aptly named the Unified Metadata Model (UMM), has been developed as part of the EOSDIS Metadata Architecture Studies (MAS I and II) conducted between 2012 and 2013. The UMM will be used by the Common Metadata Repository (CMR) and will drive search and retrieval of metadata cataloged within that system.

 

This document describes a UMM reference model, referred to as the UMM-S, where 'S' stands for services. The updated UMM-S provides metadata to support the UI/UX-driven approach to End-to-End Services. Specifically, when a user wants to know the   service options for a specific service and   makes selections via the UI, e.g. subsetting, data transformations and the desired output file format. The UMM-S enables the population of the service options which are surfaced in the UI to support these selections. Each service record contains the identification of the service, i.e. name, type, version, description, service options for spatial, temporal, variable subsetting,   other data transformations and reformatting. An important consideration of how the capabilities of the service are captured in UMM-S is to ensure that it can be accessed by both humans, via the UI, and by machines, via the API.

 

Since UMM-S is part of the UMM, there are common elements that are shared across the different UMM models and have already been documented in the UMM-Common document.   When this is the case, this document will provide a description of where the element is located in the UMM-Common.

 

1.1          Purpose

The purpose of   UMM-S is to express a services model applicable to CMR that (1) stores service metadata, and (2) permits user selection of service options for data transformations which are provided by the service (or services) for any given collection. In addition, the UMM-S model is related to the other CMR metadata models, e.g. UMM-Var, which supports the specification of variables which have associated services.

 

Note: the previous service design principally addressed the Service Entry Resource Format (SERF) standard. The SERF version of the service design included tools, software and instances of services, including web services, US and international web portals. NASA’s Earth Observing System Data and Information System (EOSDIS) is evolving to expose data and services using standards-based protocols in order to keep pace with evolving standards in web services, i.e. Open-source Project for a Network Data Access Protocol (OPeNDAP), Web Coverage Services (WCS), Web Mapping Services (WMS). In recent work,   the EED2 team sought to understand how data were being accessed,   for what purpose, and how this could be more simply achieved via services. To develop this idea,   the team has defined a User Interface/User Experience (UI/UX) driven approach to services. The user experience guides what selections and choices a user makes at the UI for typical data transformations, e.g. spatial subsetting, reprojection, reformatting, etc. The user is exclusively concerned about what choices are available for a specific data set and the back-end services take care of any needed processing.  

 

This document provides information to the National Aeronautics and Space Administration (NASA) Earth Science community. Distribution is unlimited.

 

1.2          Scope

This document describes the UMM Service   (UMM-S) model.

 

1.3          Impact

This document outlines a profile intended to be backward compatible with existing NASA Earth Science metadata implementations, including the Global Change Master Directory (GCMD) Service Entry Resource Format (SERF) implementation. It will impact providers from NASA Distributed Active Archive Centers (DAAC[s]), Common Metadata Repository (CMR) client developers, Metadata Maintenance Tool (MMT) developers, metadata catalog developers, and users.

 

1.4          Copyright Notice

The contents of this document are not protected by copyright in the United States and may be used without obtaining permission from NASA.

 

1.5          Feedback

Questions, comments and recommendations on the contents of this document should be directed to support@earthdata.nasa.gov.

 

1.6          Document Conventions

Each section of this document describes an element of the model and includes the following components:

 

  • Element Name: Specifies the element name.
  • Element Specification: Provides the sub-elements, cardinality of the sub-elements, and any other major factors that make up the element.
  • Description: Provides background information on the purpose of the element and its intended use.   Furthermore, any information about the element's current usage, recommendations for usage, or unresolved issues is also documented here.
  • Cardinality: Indicates the expectation of counts for this element, summarized in Table 1.
  • Tags: Provides specific, related categorical values associated with this element, which are defined in Appendix B: Tags Glossary.

 

Table 1 : Cardinality

Value

Description

1

Exactly one of this element is required.

0..N

Optionally, up to and including N number of this element may be present.

0..*

Optionally, any number of this element may be present.

1..*

At least one of this element is required, any number may be present.

1..N

At least one of this element is required, any number up to and including N number of this element may be present.

 

Unified Modeling Language (UML) class diagrams and element lists are provided for each subcomponent of the model. The [R] after an element name indicates that the element is   required.


Some elements are tagged as 'Required (with Option)'. These elements are similar to the xml scheme <choice> element: one of the options is required, but there is a choice as to which option is utilized. For more information about the various tags used throughout this document, refer to Appendix B: Tags Glossary.

 

As described in the Introduction, there is a UMM-Common document that contains elements and their details common to multiple UMM profiles.   While this document will refer to those elements and its details, this document takes precedence.   Any elements and their details described in this document override the details found in the UMM-Common document.   Examples include, but are not limited to a sub element cardinality difference - usually starting from either a 0 or 1, additional sub elements, sub elements that should be excluded, additional analysis or recommendations, etc.

 

1.7          Related Documentation

There is a document that fully describes metadata elements that are used in multiple models. This document, the UMM-Common (https://wiki.earthdata.nasa.gov/display/CMR/CMR+Documents) is documented separately. The Collection model makes multiple references to the UMM-Common throughout.

 

The latest versions of all documents below should be used. The latest ESDIS Project documents can be obtained from URL: https://ops1-cm.ems.eosdis.nasa.gov.   ESDIS documents have a document number starting with either 423 or 505. Other documents are available for reference in the ESDIS project library website at: http://esdisfmp01.gsfc.nasa.gov/esdis_lib/default.php unless indicated otherwise.

 

1.7.1         Applicable Documents

The following documents are referenced within, are directly applicable, or contain policies or other directive matters that are binding upon the content of this document.

 

Table 2 : Applicable Documents

CMR Life Cycle

https://wiki.earthdata.nasa.gov/display/CMR/CMR+Documents

UMM-Common

https://wiki.earthdata.nasa.gov/display/CMR/CMR+Documents

SERF

https://gcmd.nasa.gov/Aboutus/xml/serf/serf.xsd

https://gcmd.nasa.gov/add/serfguide/index.html  

CMR End-To-End Services Study (Task 25) EED2-TP-025

https://wiki.earthdata.nasa.gov/download/attachments/83624411/EED2-TP-025_CMR%20End-To-End%20Services%20Study.pdf?api=v2

 

1.7.2         Reference Documents

The following documents are not binding on the content but referenced herein and, amplify or clarify the information presented in this document.

 

 

Table 3 : Reference Documents

Tags

http://en.wikipedia.org/wiki/Tag_%28metadata%29

Translators

Translators to ISO can be found at https://cdn.earthdata.nasa.gov/iso/resources/transforms/

XPath

XPath is a language for addressing parts of an XML document, designed for use with XSLT.

XLinks

http://en.wikipedia.org/wiki/XLink

MENDS

More information on the Base Metadata Requirements established by the MENDS group: https://wiki.earthdata.nasa.gov/display/NASAISO/NASA+Base+Metadata+Requirements http://www.w3schools.com/schema/el_choice.asp

 

2           Services Metadata Conceptual Model

Any service metadata described by the UMM-S may be associated with other metadata in the UMM,   such as collection (UMM-C) metadata, granule (UMM-G) metadata, and variables (UMM-Var). In addition, as shown in Figure 1, the associations in the UMM support the discovery of services   from a given collection or variable. This model will support the concept of data, represented by metadata contained within the UMM-C, UMM-G, UMM-Var, being discovered, requested, and subsequently transformed via the corresponding service. The other UMM models reside in JAMA in separate projects. The CMR Lifecycle represents how metadata is managed over time   and will govern this model,   all related documentation, and facilitate change. The CMR Lifecycle is documented in a Wiki page located at: https://wiki.earthdata.nasa.gov/display/CMR/CMR+Documents.


Figure 1 shows the UMM-S metadata model at a high-level and specifically depicts the relationship of UMM-S to the other models in the context of the UMM by mapping its relationships with the other key entities: Collection, Granule, and Variable.   These entities are represented in abbreviated forms with only a few key identifiers listed in each class.

 

https://rms.earthdata.nasa.gov/attachment/5992/UMM%20High-Level%20UML%20Diagram%20-%20Page%204%20%281%29.png

Figure 1 : UMM Relationships showing key associations

2.1          Use Cases

This section provides information about use cases identified for the UMM-S. In keeping with the UML methodology, we provide several diagrams that describe different information.   A   use case diagram shows   the actor's interaction with the system. An activity diagram shows the flow of data in terms of the user experience. A sequence diagram shows the sequences of actions within the system   and the key components of the system.

 

2.1.1         Collection Search

As a user of the Earthdata Search Client (EDSC), I can perform a Collection Search and discover the associated variables and service options listing the data transformations from the CMR.

 

Scenario [a]: As a user of the EDSC, I can get a list of collections from the CMR. For each collection, I can determine whether the following logical operators are "true" or "false": "has_variables", "has_transforms" or "has_formats".

Scenario [b]: As a user of the EDSC, I have a collection from the CMR, and I can subsequently make a request to return all the variables and the associated service options. The service options include information about the data transformations, including subset options, re-projections and format conversions.

Scenario [c]: As a user of the EDSC, I can select collection(s) and I can make a request to the CMR which returns all the variables and service options for those collection(s).

 

Outcomes: As an EDSC user, with no knowledge of the service capabilities listed in the CMR, I can perform a collection search and subsequently discover the variables, the service(s) and service options. These will enable the EDSC user to determine whether the collections have variables, transforms, and formats; as well as to gather the details of these and make selections in the UI modals - which are captured in the user's project. These selections can be subsequently used to make a data transformation request from the service, to enable spatial, temporal or variable subsetting, reprojection, or reformatting.

 

Definitions:

 

Variable: A named set of data that contains the values of a measurement. In this context, the variable is described by its name and characteristics. The description includes what was intended to be measured (i.e., the observable property, and how the variable was measured (e.g., measurement technique and the instrument used). Variables may be classified as science variables, quality variables and ancillary variables (or other, when one of these classifications cannot be used). A variable can also be the output of a model.

 

Service: A service has various abilities to transform variables. The service can be remotely accessed via a REST end point, e.g. a web service.

 

Data Transformation (or transform): A data transformation is a specific capability available from a service, e.g. spatial subsetting or reprojection. It is an umbrella term that represents a method for transforming data from one form to another. For example: spatial subsetting might be used on data that exists with a global extent, to subset it to a regional extent. The list of data transformations available is service provider dependent, e.g. at Goddard Earth Sciences Data and Information Services Center (GES DISC), a typical OPeNDAP service provides: spatial subsetting, variable subsetting, and data format conversion. This list of data transformations available is dependent on the service provider.

 

Format: The file format used to store the data on the file system. The data can be transformed to a different format through the use of a service, e.g HDF4 -> GeoTIFF. The native file format and the list of available output file formats will be available from the UMM-S.

 

Note: Within the EDSC UI, there are three modal windows when we arrive to the point of selections of service options in the workflow: the first to list the Variables (which have services), a second for Data Transformations, and a third for formats. In the model, we don't need to separate the formats out into its own class, provided the model can support the UI, in terms of what metadata it needs to "surface".

 

Use Case: See the use case diagram below.

 

https://rms.earthdata.nasa.gov/attachment/5872/Use%20Cases%20-%20UMM-S%20-%20Revised%20Collection%20Search.png

Figure 2 : Collection Search Use Case  

 

User Experience: See the activity diagram below.

https://rms.earthdata.nasa.gov/attachment/6058/UMM-S%20-%20Activity%20Diagrams%20-%20Revised%20Collection%20Search%20-%20Activity%20Diagram.png

Figure 3 : Collection Search Activity Diagram

 

Workflow: See the sequence diagram below.

 

Figure 4 : Collection Search Sequence Diagram

 

2.1.2         Operation Request to a Web Service

Send an Operation Request to a web service. The User receives the Coverage within the multipart XML response from the web service.

 

Scenario [a]: As a user of the EDSC or other CMR client, I can make a request for a GetCapabilities operation by discovering the operations supported by a hosted web service.

Scenario [b]:As a user of the EDSC or other CMR client, I can constrain the request to a desired coverage, spatial extent, temporal extent, projection and format.

Scenario [c]:As a user of the EDSC or other CMR client, I can receive the XML response, containing the coverage in a multipart from the web service.

 

Outcomes: User obtains Coverage from a multipart XML response for subsequent display, or data usage.

 

Use Case: See the use case diagram below.

https://rms.earthdata.nasa.gov/attachment/6055/Use%20Cases%20-%20UMM-S%20-%20Operation%20Metadata%20-%20Use%20Case.png

Figure 5 : Operation Request to a Web Service Use Case

 

User Experience: See the activity diagram below.

https://rms.earthdata.nasa.gov/attachment/6059/UMM-S%20-%20Activity%20Diagrams%20-%20Operation%20Metadata%20-%20Activity%20Diagram%20%281%29.png

Figure 6 : Operation Request to a Web Service Activity Diagram

   

Workflow: See the sequence diagram below.

https://rms.earthdata.nasa.gov/attachment/6060/Sequence%20Diagram%20for%20Operation%20Metadata%20%20-%20Operation%20Request%20to%20a%20Web%20Service%20%281%29.png

Figure 7 : Operation Request to a Web Service Sequence Diagram

 

2.2          UMM-S Metadata Model

The service metadata conceptual model shown in Figure 8 shows the model broken down into three major classes for Services: Service, Options, and OperationMetadata with each class describing a different aspect of the service. There are also some minor classes: RelatedURLs, ScienceKeywords, ServiceKeywords, ServiceOrganizations, ServiceContacts, Platforms and ServiceQuality, which capture other important information about the service. The Collection (UMM-C) and Variable (UMM-Var) models are represented here to highlight these important relationships with the Service class. Each aspect is described in more detail in the subsequent sections of this ​document.

 

https://rms.earthdata.nasa.gov/attachment/6449/UMM-S%20UML%20Diagram%20-%20UMM-S%20w%252FESO%20comments%20addressed%20%285%252F17%29.png

Figure 8 : Overall Service Model

 

The function of the Service class is to enable the service to be specified by its unique service metadata. Each service will be identified in terms of its name, long name, type, version and description. The RelatedURLs class is used to capture important URL(s) related to the service. The RelatedURLs class has attributes which are used to describe the URLs, and it is strongly typed.

 

The function of the Options class is to capture the various data transformations supported by the service.

 

The function of the OperationMetadata class is to capture RESTful service endpoint(s) for the service, the nature of the coupled resource, and specific information about the WMS layer, WFS feature type or WCS coverage. If the service has layers, feature types or coverages, then the identifier, relative path, and any spatial and temporal information may be specified, for each layer, feature type or coverage.

 

Note: Typical WMS layers can be mapped 1:1 with the variables represented in UMM-Var, but the name of the layers sometimes differs from the variable names. This is dependent on choices in naming layers made by the service provider. This is also true of WFS feature types, or WCS coverages. The DataResource class is a generic class which enables the layer, feature or coverage names used as the identifiers to be captured, along with other information about their spatial and temporal extents.

 

2.2.1         Service

The Service class contains basic information about the service itself, its identifying information, and its URL. It contains the elements described below.

 

Service [1..N]

Service /Name [R]

Service /LongName [R]

Service /Type [R]

Service /Version [R]

Service /Description [R]

Service /RelatedURLs [R]

Service /OperationMetadata

Service /OnlineAccessURLPatternMatch

Service /OnlineAccessURLPatternSubstitution

Service /ScienceKeywords

Service /ServiceKeywords [R]

Service /ServiceOrganizations [R]

Service /ServiceContacts [R]

Service /Platforms

Service /ServiceQuality [R]

Service /AccessConstraints

Service /UseConstraints

Service /AncillaryKeywords

 

2.2.1.1        Name [R]

Element Specification

Service/Name (1)

 

Description

The name of the service, software, or tool.

 

Sample Values (service example): "SERVIR".

 

Sample Values (software example): "BYU_slice_response".

 

Sample Values (tool example): "USGS_TOOLS_LATLONG".

 

Sample Values (OPeNDAP example): "AIRS_L3_OPENDAP".

 

Sample Values (Mirador example): "GES_DISC_via_OpenSearch_(Mirador)"

 

Tags

Required

 

2.2.1.2        LongName [R]

Element Specification

Service/LongName (1)

 

Description

The long name of the service, software, or tool. It provides a human readable name for the service.

 

Sample Value (service example: "Mesoamerican Visualization and Monitoring System (SERVIR)".)

 

Sample Value (software example: "SeaWinds 3D Slice Response Software".)

 

Sample Value (tool example: "WRS-2 Path/Row to Latitude/Longitude Converter".)

 

Sample Value (OPeNDAP service example: "OPENDAP (Hyrax) framework for AIRS Level 3 data products".)

 

Sample Value (Mirador service example: "Access the   GES DISC data via OpenSearch (Mirador)".)

 

Tags

Required

 

2.2.1.3        Type [R]

Element Specification

Service/Type (1) <OPeNDAP, THREDDS, ESI, WMS, WFS, WCS, WPS, CSW, NOT PROVIDED>

 

Description

The type of the service, software, or tool.

 

Please note that Type values will come from KMS which is a controlled list.

 

Sample Value: WCS

 

Tags

Required, Controlled Vocabulary

 

2.2.1.4        Version [R]

Element Specification

Service/Version (1)

 

Description

The edition or version of the service, software, or tool. The version should be defined in the form x, y, and z. where 'x.y.z' means 'major.minor.incremental' version numbers. Typically, 'x' and 'y' are numbers (0 through 9) and 'z' is a number (0 through 99).

 

Sample Value: 1.1.1

 

Tags

Required

 

2.2.1.5        Description [R]

Element Specification

Service/Description (1)

 

Description

A brief description of the service, software, or tool. For example, a description might contain information about what is the service, the purpose of the service, and the parameters (or variables) being invoked, and what are the sources of these data.

 

Sample Value (service example): "The SEDAC Hazards Mapper enables users to visualize data and map layers related to Socioeconomic, Infrastructure, Natural Disasters, and Environment and analyze potential impacts and exposure. The web app mashups layers from various sources including SEDAC, NASA LANCE, NASA GIBS, USGS, NOAA, ESRI, and others.

 

Sample Value (software example): "Imaging applications of SeaWinds on QuikSCAT and ADEOS II are facilitated by applying reconstruction and resolution enhancement algorithms to produce high resolution images of the surface normalized radar cross section (sigma-0). Such algorithms require a description of the spatial response functions of the measurements. The pencil-beam design of Seawinds, coupled with the onboard processing."

 

Sample Value (tool example): "The USGS WRS-2 Path/Row to Latitude/Longitude Converter allows users to enter any Landsat path and row to get the nearest scene center latitude and longitude coordinates. You can also enter coordinates in the second section to discover the closest Landsat path and row - daytime (descending) or nighttime (ascending)."

 

Sample Value (OPeNDAP service example): "OPeNDAP (Hyrax) Framework for AIRS L3 data products. This framework facilitates such services as format conversion and selected subsetting (e.g., spatial constraints, parameter/variable)."

 

Tags

Required

 

2.2.1.6        RelatedURLs [R]

Element Specification

Service/RelatedURLs (1..*)

 

Description

This element contains important information about the Uniform Resource Locator (URL) for the service. These include the following required elements: Name, Description and URL. The details are located in the UMM-Common document.

 

RelatedURLs (1..*)

RelatedURLs/URL (1)

RelatedURLs/Description (0..1)

RelatedURLs/URLContentType (1)     <CollectionURL, PublicationURL, DataCenterURL, DistributionURL, DataContactURL, VisualizationURL>

RelatedURLs/Type (1)                                             {Valid values shown below}

RelatedURLs/Subtype (0..1)                         {Valid values shown below}

 

Set Type: select from the following list:

 

  • GET DATA
  • GET SERVICE

 

Set Subtype: select from the following list:

 

  • ACCESS MAP VIEWER
  • ACCESS MOBILE APP
  • ACCESS WEB SERVICE
  • DIF
  • MAP SERVICE
  • NOMADS
  • OPENDAP DATA
  • OPENDAP DATA (DODS)
  • OPENDAP DIRECTORY (DODS)
  • OpenSearch
  • SERF
  • SOFTWARE PACKAGE
  • SSW
  • SUBSETTER
  • THREDDS CATALOG
  • THREDDS DATA
  • THREDDS DIRECTORY
  • TOOL
  • WEB COVERAGE SERVICE (WCS)
  • WEB FEATURE SERVICE (WFS)
  • WEB MAP FOR TIME SERIES
  • WEB MAP SERVICE (WMS)
  • WORKFLOW (SERVICE CHAIN)

 

The following examples show how the above fields should be completed for service, software package and tools examples.

 

Sample Value service example):

RelatedURLs/URL: "https://www.servirglobal.net/default.aspx"

RelatedURLs/Description: "SERVIR-Mesoamerica is regional service that provides a suite of analysis and visualization tools that integrate satellite and other geospatial data"

 

For services, select URLContentType: DistributionURL

 

Set Type: GET SERVICE

 

Set Subtype: ACCESS WEB SERVICE

 

Sample Values (software package example): "SeaWinds 3D Slice Response Software"

RelatedURLs/URL: "http://www.scp.byu.edu/software/slice_response/Xshape_temp.html"

RelatedURLs/Description: "Access the SeaWinds 3D Slice Response software."

 

For software package, select URLContentType:   DistributionURL

 

Set Type: GET SERVICE

 

Set Subtype: SOFTWARE PACKAGE

 

Sample Values (tool example): "USGS_TOOLS_LATLONG"

RelatedURLs/URL: "https://landsat.usgs.gov/wrs-2-pathrow-latitudelongitude-converter"

RelatedURLs/Description: "Access the WRS-2 Path/Row to Latitude/Longitude Converter."

 

For tools, select URLContentType: DistributionURL

 

Set Type: GET SERVICE

 

Set Subtype: TOOL

 

The following example shows how the above fields should be completed for an OPeNDAP service example.

 

If the service type is OPeNDAP, the RelatedURLs/URL field may be populated with the root URL to the OPeNDAP service.

 

Sample Value& (OPeNDAP service example):

 

RelatedURLs/URL: "https://acdisc.gesdisc.eosdis.nasa.gov/opendap/Aqua_AIRS_Level3/contents.html"

RelatedURLs/Description: "OPeNDAP Service for AIRS Level 3 products"

 

For OPeNDAP services, select URLContentType: DistributionURL

 

Set Type: GET SERVICE

 

Set Subtype: OPENDAP DATA

 

Tags

Required

 

2.2.1.7        OperationMetadata

Element Specification

Service/OperationMetadata (0..*)

 

Description

This class describes the signature of the operational metadata provided by the service.

 

Tags

Recommended

 

2.2.1.7.1                 OperationName

Element Specification

Service/OperationMetadata/OperationName (0..*) <GetCapabilities, DescribeCoverage, GetCoverage, GetMap, GetLegendGraphic, GetFeatureInfo,   DescribeFeatureType, GetPropertyValue. GetFeature, GetFeatureWithLock, LockFeature, Transaction, CreateStoredQuery, DropStoredQuery, ListStoredQueries, DescribeStoredQueries>

 

Description

This element contains the name of the operation(s) made possible via this service.

 

Sample Value (Get Capabilities example): "GetCapabilities"

 

Sample Value (Describe Coverage example): "DescribeCoverage"

 

Sample Value (Get Coverage example): "GetCoverage"

 

Tags

Recommended

 

2.2.1.7.2                 DistributedComputingPlatform

Element Specification

Service/OperationMetadata/DistributedComputingPlatform   (0..*) <"XML", "CORBA", "JAVA", "COM", "SQL", "SOAP", "Z3950", "HTTP", "FTP", "WEBSERVICES">

 

Description

This element contains the distributed computing platform (protocol) for the operation(s) made possible via this service.

 

Sample Value (Get Capabilities example): "XML, WEBSERVICES "

 

Sample Value (Describe Coverage example): "XML, WEBSERVICES "

 

Sample Value (Get Coverage example):& "XML, WEBSERVICES "

 

Tags

Recommended

 

2.2.1.7.3                 OperationDescription

Element Specification

Service/OperationMetadata/OperationDescription (0..*)

 

Description

This element contains the description of the operation(s) made possible via this service.

 

Sample Value (Get Capabilities example): "The GetCapabilities operation provides service metadata including information about contact information, coverage identifiers, capabilities, bounding boxes (extent), authorities (projections) and formats."

 

Sample Value (Describe Coverage example): "The DescribeCoverage operation provides service metadata including information about a specific coverage identifier, detailed service capabilities, bounding boxes (extent), authorities (projections), grid axes, labels, time extent and formats."

 

Sample Value (Get Coverage example): "The GetCoverage operation response streams the data for a specific coverage identifier, bound by the specified bounding boxes (extent), selected authority   (projection), grid axis, time extent and format."

 

Tags

Recommended

 

2.2.1.7.4                 InvocationName

Element Specification

Service/OperationMetadata/InvocationName (0..*)

 

Description

This element contains the name of the invocation   of the operation(s) made possible via this service.

 

e.g. Spatial Subsetting

 

Sample Values (GES DISC):

 

"Using the Ozone Monitoring Instrument (OMI) data from NASA Goddard Earth Sciences Data and Information Services Center (GES DISC)"

 

Sample Values (NSIDC):

 

"Atlas of the Cryosphere"

 

Sample Values (ORNL DAAC):

 

"ORNL DAAC WCS Server"

 

Tags

Recommended

 

2.2.1.7.5                 ConnectPoint

Element Specification

Service/OperationMetadata/ConnectPoint (1..*)

 

Description

This element contains the URL of the invocation of the operation(s) made possible via this service.

 

Sample Values (GES DISC):

 

GES DISC WMS: https://disc1.gesdisc.eosdis.nasa.gov/daac-bin/wms_airs?service=WMS&version=1.3.0&request=GetCapabilities

GES DISC WCS: https://acdisc.gesdisc.eosdis.nasa.gov/daac-bin/wcsAIRSL3?service=WCS&version=1.0.0&request=GetCapabilities

 

Sample Values (ORNL DAAC):

 

ORNL DAAC WMS: https://webmap.ornl.gov/ogcbroker/wms?service=WMS&version=1.3.0&request=GetCapabilities
ORNL DAAC WCS: https://webmap.ornl.gov/ogcbroker/wcs?service=WCS&version=1.0.0&request=GetCapabilities

 

Sample Values (NSIDC):

 

Northern Hemisphere: http://nsidc.org/cgi-bin/atlas_north?service=WCS&request=GetCapabilities&version=1.1.1
Southern Hemisphere: http://nsidc.org/cgi-bin/atlas_south?service=WCS&request=GetCapabilities&version=1.1.1

 

Tags

Recommended

 

2.2.1.7.5.1               ResourceName

Element Specification

Service/OperationMetadata/ConnectPoint/ResourceName (0..1)

 

Description

This element contains the name of the resource(s) coupled to this service.

 

Sample Values (GES DISC):

 

"AIRS3STD:TotO3_D" - corresponds to the resource labelled: "Total Column Ozone for Descending Orbit"

 

"AIRS3STD:SurfAirTemp_D_timeAveraged" - corresponds to the resource labelled: ;"Surface air temperature parameter (in Kelvin) from the AIRS Only level 3 daily gridded product at 1 degree resolution"

 

Sample Values (ORNL DAAC):

 

"1000_1" - corresponds to the resource labelled: "Modelled Chlorophyll-a Concentration, June 2002 - December 2003"

 

"1004_27" - corresponds to the resource labelled: "Soil Thermal Capacity with 0 volumetric soil-water fraction at 0-150 cm of Depth"

 

Sample Values (NSIDC):

 

"sea_ice_concentration_01" - corresponds to the resource which represents mean ice concentration percentages for each month over the entire time period 1979-2007, which is generated from passive microwave brightness temperature data derived from Nimbus-7 Scanning Multichannel Microwave Radiometer (SMMR) and Defense Meteorological Satellite Program (DMSP) -F8, -F11 and -F13 Special Sensor Microwave/Imager (SSM/I) radiances at a grid cell size of 25 x 25 km.

 

"seasonal_snow_classification" - corresponds to the resource which represents global seasonal snow classification system, which is based on the physical properties of the snow (depth, density, thermal conductivity, number of layers, degree of wetting, etc.), the world's seasonal snow covers are divided into six classes, plus classes for water and ice fields. Each class is defined by its physical properties, then empirically related to climate using three variables (precipitation, wind, and air temperature). A vegetation proxy was used for wind data: tall vegetation equals low wind, short vegetation equals high wind.

 

Tags

Recommended

 

2.2.1.7.5.2               ResourceLinkage [R]

Element Specification

Service/OperationMetadata/ConnectPoint/ResourceLinkage (1)

 

Description

This element contains the URL of the resource(s) coupled to this service.

 

Sample Values (GES DISC) for a GetCapabilities operation:

 

https://acdisc.gesdisc.eosdis.nasa.gov/daac-bin/wcsAIRSL3?service=WCS&version=1.0.0&request=GetCapabilities

 

Response: Server responds by returning the capabilities in an XML file

 

Sample Values (GES DISC) for a DescribeCoverage operation:

 

https://acdisc.gesdisc.eosdis.nasa.gov/daac-bin/wcsAIRSL3?service=WCS&version=1.0.0&request=DescribeCoverage&coverage=AIRS3STD:SurfAirTemp_D_timeAveraged

 

Response: Server responds by returning the capabilities for the specific coverage in an XML file

 

Sample Values (GES DISC) for a GetCoverage operation:

 

A GeoTIFF of the surface air temperature parameter (in Kelvin) from the AIRS Only level 3 daily gridded product at 1 degree resolution (264 KB):

 

https://acdisc.gesdisc.eosdis.nasa.gov/daac-bin/wcsAIRSL3?service=WCS&

version=1.0.0&

request=GetCoverage&

crs=EPSG:4326&

format=geoTiff&

resx=1.0&

resy=1.0&

bbox=-180,-90,180,90&

time=2007-06-01&

coverage=AIRS3STD:SurfAirTemp_D_timeAveraged

 

Response: Server responds by returning the coverage in a file (AIRS3STD_SurfAirTemp_D_20070601.tif)

 

https://rms.earthdata.nasa.gov/attachment/6200/AIRS3STD_SurfAirTemp_D_20070601.png data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw%3D%3D

Figure 9 : GeoTIFF file returned in the server response from a GetCoverage request for the AIRS3STD:SurfAirTemp_D_timeAveraged coverage  

 

Sample Values (ORNL DAAC) for a GetCapabilities operation:

 

https://webmap.ornl.gov/ogcbroker/wms?service=WMS&version=1.3.0&request=GetCapabilities

https://webmap.ornl.gov/ogcbroker/wcs?service=WCS&version=1.0.0&request=GetCapabilities

 

Response: In each case above the server responds by returning the capabilities in an XML file

 

Sample Values (ORNL DAAC) for a DescribeCoverage operation:

 

https://webmap.ornl.gov/ogcbroker/wcs?service=WCS&version=1.0.0&coverage=980_14&request=DescribeCoverage

 

Response: Server responds by returning the capabilities for the specific coverage   in an XML file

 

Sample Values (ORNL DAAC) for a GetCoverage operation:

 

A 32 bit GeoTIFF for the Weekly Averages of Sea Surface Temperature (1986) (4.4 MB)

 

https://webmap.ornl.gov/ogcbroker/wcs?

service=WCS&

version=1.0.0&

request=GetCoverage&

crs=EPSG:4326&

format=GeoTIFF_FLOAT32&

resx=1.0&

resy=1.0&

bbox=-180,-90,180,90&

coverage=980_14

 

Response: Server response by returning the coverage in a file (mapserv.tiff)

 

https://rms.earthdata.nasa.gov/attachment/6203/mapserv%20%2812%29.png data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw%3D%3D

Figure 10 : GeoTIFF file returned in the server response from a GetCoverage request for the 980_14 coverage

 

Sample Values (ORNL DAAC) for a GetMap operation:

 

A PNG image for the LIDAR-derived Vegetation Canopy Structure, Great Smokey Mountains National Park, 2011 (1986) (249 KB)

 

https://webmap.ornl.gov/cgi-bin/mapserv?

VERSION=1.1.1&

SERVICE=WMS&

STYLES=&

WIDTH=970&

HEIGHT=485&

originator=SDAT&

LAYERS=1286_1_band1&

REQUEST=GetMap&

SRS=EPSG:2264&

BBOX=503414.334,632612.579,819944.274,790877.549&

FORMAT=image/png&

TRANSPARENT=true&

map=/sdat/config/mapfile//1286/1286_1_wms.map

 

Response: Server response by returning the map in a file (mapserv.png)

 

https://rms.earthdata.nasa.gov/attachment/6199/mapserv.png data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw%3D%3D

Figure 11 : PNG file returned in the server response from GetMap request for the /sdat/config/mapfile//1286/1286_1_wms.map map  

 

Sample Values (NSIDC) for a GetCapabilities operation:

 

Northern Hemisphere: http://nsidc.org/cgi-bin/atlas_north?service=WCS&request=GetCapabilities&version=1.1.1

 

Sample Values (NSIDC) for a GetCoverage operation:

 

A 32-bit GeoTIFF of permafrost extent of the Greenland ice sheet at 5-km resolution (791 KB):

 

http://nsidc.org/cgi-bin/atlas_north?
service=WCS&
version=1.1.1&
request=GetCoverage&
crs=EPSG:32661&
format=GeoTIFFFloat32&
resx=5000&
resy =5000&
bbox=-500000,-500000,1800000,1700000&
coverage=permafrost_extent

 

XML Response:

 

--wcs
Content-Type: text/xml
Content-ID: wcs.xml

<?xml version="1.0" encoding="UTF-8"?>
<Coverages
      xmlns="http://www.opengis.net/wcs/1.1"
      xmlns:ows="http://www.opengis.net/ows"
      xmlns:xlink="http://www.w3.org/1999/xlink"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xsi:schemaLocation="http://www.opengis.net/ows/1.1 ../owsCoverages.xsd">
  <Coverage>
    <Reference xlink:href="cid:coverage/out.tif"/>
  </Coverage>
</Coverages>
--wcs
Content-Type: image/tiff
Content-Description: coverage data
Content-Transfer-Encoding: binary
Content-ID: coverage/out.tif
Content-Disposition: INLINE

*******************  

******************* } represents the GeoTIFF part of the multipart response

*******************

...

--wcs--

 

The GeoTIFF part of the multipart response looks like this:

 

https://rms.earthdata.nasa.gov/attachment/6201/cryosphere_atlas_north152423754617048.png data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw%3D%3D

Figure 12 : 32-bit GeoTIFF part of the multipart response from a GetCoverage request for the permafrost_extent coverage

 

Note: A multipart response can be viewed in most browsers (i.e. Firefox, Chrome, Safari). A programmatic client (i.e. one written in python or java) would require a function to separate the components of the multipart response into their respective parts.

 

In the above GetCoverage example, the REST endpoint root URL would be the metadata entry for the ConnectPoint/ResourceLinkage field.

 

The remaining KVPs (crs, format, resx, resy, bbox, coverage) would be added by the client, which together specify the exact service request. The choices of values (and ranges of values) for each of these KVPs can be determined from the corresponding GetCapabilities response (listed above).

 

Tags

Recommended

 

2.2.1.7.5.3               ResourceDescription

Element Specification

Service/OperationMetadata/ConnectPoint/ResourceDescription (0..1)

 

Description

This element contains the description of the resource(s)   coupled to this ;service.

 

Sample Values (GES DISC):

"Total Column Ozone for Descending Orbit"

 

Sample Values (ORNL DAAC):

"Modelled Chlorophyll-a Concentration, June 2002 - December 2003"

 

Sample Values (NSIDC):

"Mean ice concentration percentages for each month over the entire time period 1979-2007, which is generated from passive microwave brightness temperature data derived from Nimbus-7 Scanning Multichannel Microwave Radiometer (SMMR) and Defense Meteorological Satellite Program (DMSP) -F8, -F11 and -F13 Special Sensor Microwave/Imager (SSM/I) radiances at a grid cell size of 25 x 25 km"

 

Tags

Recommended

 

2.2.1.7.6                 OperationChainMetadata

Element Specification

Service/OperationMetadata/OperationName (0..*)

 

Description

This element contains the name of the chained operation(s) made possible via this service.

 

Examples of chained operations:

       
Subset/Regrid/Format convert            
Subsetting by variable/time/region            

 

This list of valid chained operations is sourced from the Data Transformation Working Group.

 

Tags

Recommended

 

2.2.1.7.6.1               OperationChainName [R]

Element Specification

Service/OperationMetadata/OperationChainMetadata/OperationChainName (1) <Spatial Subsetting, Temporal Subsetting, Variable Subsetting, Reprojection, Regridding, Format Conversion, Variable Aggregation>

 

Description

This element contains the name of the operation chain made possible via this service.

 

Sample Value (GES DISC):

 

To express the operation chain: Subset/Regrid/Format convert, use the following keywords separated by the "|" delimiter:

 

"Spatial Subsetting |

Regredding |

Format Conversion"

 

Tags

Required

 

2.2.1.7.6.2               OperationChainDescription

Element Specification

Service/OperationMetadata/OperationChainMetadata/OperationChainDescription (0..1)

 

Description

This element contains the description of the operation chain made possible via this service.

 

Sample Value:

 

To describe the operation chain: Subset/Regrid/Format convert more fully, e.g.,

 

"Spatial Subsetting, then Regridding (from Native 1km x 1 km to 10km x 10km grid), then Format conversion (from hdf4 to geotiff)".

 

Tags

Recommended

 

2.2.1.7.7                 CoupledResource

Element Specification

Service/OperationMetadata/CoupledResource (0..*)

Service/OperationMetadata/CoupledResource/ScopedName (0..*)

Service/OperationMetadata/CoupledResource/DataResourceDOI (0..*)

Service/OperationMetadata/CoupledResource/DataResource (0..*)

Service/OperationMetadata/CoupledResource/CouplingType (0..*)

 

Description

This element contains important information about the resource(s) coupled to this service.

 

Tags

Recommended

 

2.2.1.7.7.1               ScopedName

Element Specification

Service/OperationMetadata/CoupledResource/ScopedName (0..1)

 

Description

This element contains the name of the resource(s) coupled to this service.

 

Sample Value (GES DISC):

 

"WCS Service for AIRS3STD: AIRS/Aqua L3 Daily Standard Physical Retrieval (AIRS-only) 1 degree x 1 degree V006"

 

Tags

Recommended

 

2.2.1.7.7.2               DataResourceDOI

Element Specification

Service/OperationMetadata/CoupledResource/DataResourceDOI (0..*)

 

Description

This element contains the DOI for   the resource(s) coupled to this service.

 

Sample Value (GES DISC):

 

doi:10.5067/Aqua/AIRS/DATA303

 

Tags

Recommended

 

2.2.1.7.7.3               DataResource

Element Specification

Service/OperationMetadata/CoupledResource/DataResource (0..*)

 

Description

This element contains the data identification and scope for the resource(s) coupled to this service.

 

The DataResource class describes the layers, feature types or coverages available from the service. It contains the elements described below.

 

DataResource/ [0..1]

DataResource/DataResourceIdentifier [R]

DataResource/DataResourceType [R] <WMS_LAYER, WFS_FEATURE_TYPE, WCS_COVERAGE>

DataResource/DataResourceSpatialExtent [R]

DataResource/DataResourceSpatialExtentType [R] <SPATIAL_POINT, SPATIAL_LINE_STRING, BOUNDING_BOX, GENERAL_GRID, SPATIAL_POLYGON>

DataResource/DataResourceSpatialExtent/Uuid [R]

DataResource/SpatialResolution [R]

DataResource/SpatialResolutionUnit [R]

DataResource/DataResourceTemporalExtent [R]

DataResource/DataResourceTemporalExtent/DataResourceTimePoints [R]

DataResource/DataResourceTemporalExtent/DataResourceTimePoints/Time [R]

DataResource/DataResourceTemporalExtent/DataResourceTimePoints/Value [R]

DataResource/DataResourceTemporalExtent/DataResourceTimePoints/Description

DataResource/TemporalResolution [R]

DataResource/TemporalResolutionUnit [R]

DataResource/RelativePath

 

CHOICE OF:

 

DataResource/DataResourceTemporalExtent/SpatialPoints

DataResource/DataResourceTemporalExtent/SpatialPoint/Coordinates

 

OR

 

DataResource/DataResourceTemporalExtent/SpatialLineStrings

DataResource/DataResourceTemporalExtent/SpatialLineString/Coordinates

 

OR

 

DataResource/DataResourceTemporalExtent/SpatialBoundingBox

DataResource/DataResourceTemporalExtent/CRSIdentifier [R]

DataResource/DataResourceTemporalExtent/SpatialBoundingBox/WestBoundingCoordinate [R]

DataResource/DataResourceTemporalExtent/SpatialBoundingBox/SouthBoundingCoordinate [R]

DataResource/DataResourceTemporalExtent/SpatialBoundingBox/EastBoundingCoordinate [R]

DataResource/DataResourceTemporalExtent/SpatialBoundingBox/NorthBoundingCoordinate [R]

 

OR

 

DataResource/SpatialExtent/GeneralGrid

DataResource/SpatialExtent/GeneralGrid/CRSIdentifier [R]

DataResource/SpatialExtent/GeneralGrid/Axes

DataResource/SpatialExtent/GeneralGrid/Axis/GridLabel

DataResource/SpatialExtent/GeneralGrid/Axis/GridResolution

DataResource/SpatialExtent/GeneralGrid/Axis/UOM

DataResource/SpatialExtent/GeneralGrid/Axis/Extent

DataResource/SpatialExtent/GeneralGrid/Axis/Extent/Label [R]

DataResource/SpatialExtent/GeneralGrid/Axis/Extent/Minimum [R]

DataResource/SpatialExtent/GeneralGrid/Axis/Extent/Maximum

DataResource/SpatialExtent/GeneralGrid/Axis/Extent/Resolution

DataResource/SpatialExtent/GeneralGrid/Axis/Extent/UOMLabel

 

OR

 

DataResource/DataResourceTemporalExtent/SpatialPolygons

DataResource/DataResourceTemporalExtent/SpatialPolygons/Coordinates

 

Note: the DataResource/SpatialExtent/GeneralGrid class is based on the metadata cited in the following reference:

 

Coverage Implementation Schema 1.1 standard http://docs.opengeospatial.org/is/09-146r6/09-146r6.html

 

Support for Coordinate Reference Systems:

 

The European Petroleum Survey Group (EPSG) codes are numeric codes associated with coordinate system definitions. For example, EPSG:4326 is geographic WGS84, and EPSG:32611 is UTM zone 11.

 

The DataResource/SpatialExtent/GeneralGrid/CRSIdentifier field uses the ESPG numeric code.

 

Note: a full list of ESPGs is available here: http://www.geotoolkit.org/modules/referencing/supported-codes.html

 

Tags

Recommended

 

2.2.1.7.7.4               DataResourceIdentifier [R]

Element Specification

DataResource/DataResourceIdentifier (1)

 

Description

The identifier of the layer, feature type or coverage available from the service.

 

Sample Values: "sea_ice_concentration_01" or "seasonal_snow_classification" or "AIRS3STD:TotO3_D" or "AIRS3STD:SurfAirTemp_D_timeAveraged".

 

Tags

Required

 

2.2.1.7.7.5               DataResourceType [R]

Element Specification

DataResource/DataResourceType(1) <Map, Variable, Granule, Collection, Virtual>

 

Description

The resource type of the layer, feature type or coverage available from the service.

 

Sample Values: "Variable".

 

Tags

Required

 

2.2.1.7.7.6               DataResourceSpatialExtent [R]

Element Specification

DataResource/DataResourceSpatialExtent (1)

 

Description

The spatial extent of the layer, feature type or coverage available from the service. These are coordinate pairs which describe either the point, line string, boundingbox, general grid, or polygon representing the spatial extent.

 

Sample Values (SpatialPoint example):

 

DataResource/DataResourceSpatialExtentDataResourceSpatailExtentType: “SPATIAL_POINT”

DataResource/DataResourceSpatialExtent/SpatialPoints

DataResource/DataResourceSpatialExtent/SpatialPoint/Coordinates

DataResource/DataResourceSpatialExtent/SpatialPoint/Coordinates/Latitude: "34.32"

DataResource/DataResourceSpatialExtent/SpatialPoint/Coordinates/Longitude:   "-167.63"

 

OR (SpatialLineString example)

 

DataResource/DataResourceSpatialExtent/DataResourceSpatialExtentType: "SPATIAL_LINE_STRING"

DataResource/DataResourceSpatialExtent/SpatialLineStrings

DataResource/DataResourceSpatialExtent/SpatialLineStrings/StartPoint

DataResource/DataResourceSpatialExtent/SpatialLineStrings/StartPoint/Coordinates

DataResource/DataResourceSpatialExtent/SpatialLineStrings/StartPoint/Coordinates/Latitude: "23.04"

DataResource/DataResourceSpatialExtent/SpatialLineStrings/StartPoint/Coordinates/Longitude: "78.32"

DataResource/DataResourceSpatialExtent/SpatialLineStrings/EndPoint/Coordinates

DataResource/DataResourceSpatialExtent/SpatialLineStrings/EndPoint/Coordinates/Latitude: 26.75"

DataResource/DataResourceSpatialExtent/SpatialLineStrings/EndPoint/Coordinates/Longitude: "78.12"

 

OR (SpatialBoundingBox example)

 

DataResource/DataResourceSpatialExtent/DataResourceSpatialExtentType: "BOUNDING_BOX"

DataResource/DataResourceSpatialExtent/SpatialBoundingBox

DataResource/DataResourceSpatialExtent/SpatialBoundingBox/BBox

DataResource/DataResourceSpatialExtent/SpatialBoundingBox/BBox/WestBoundingCoordinate: "-180.0"

DataResource/DataResourceSpatialExtent/SpatialBoundingBox/BBox/SouthBoundingCoordinate: "-90.0"

DataResource/DataResourceSpatialExtent/SpatialBoundingBox/BBox/EastBoundingCoordinate: "180.0"

DataResource/DataResourceSpatialExtent/SpatialBoundingBox/BBox/NorthBoundingCoordinate: "90.0"

 

OR (General Grid example)

DataResource/DataResourceSpatialExtent/DataResourceSpatialExtentType: "GENERAL_GRID"

 

Simple case: AIRX3STD, SPL3SMP L3 Gridded
Global WCS coverage representing a grid of points

 

Case 1: WCS Coverage per Granule:
Only a single time per coverage so only two axes:

 

DataResource/DataResourceTemporalExtent/DataResourceTimePoints

DataResource/DataResourceTemporalExtent/DataResourceTimePoints/Time:   (%YEAR%%MONTH%%DAY)  

DataResource/DataResourceTemporalExtent/DataResourceTimePoints/Value:   (2001-01-01)  

DataResource/TemporalResolution: 1

DataResource/TemporalResolutionUnit: day

 

DataResource /SpatialExtent/GeneralGrid/Axis/Extent/Label: " AIRX3STD L3 Gridded"

DataResource /SpatialExtent/GeneralGrid/Axis/Extent/Minimum/ Latitude: ("-90.0")

DataResource /SpatialExtent/GeneralGrid/Axis/Extent/UOMLabel: ("degrees_north")
DataResource /SpatialExtent/GeneralGrid/Axis/Extent/Minimum/ Longitude ("-180.0")

DataResource /SpatialExtent/GeneralGrid/Axis/Extent/UOMLabel: ("degrees_east")

DataResource /SpatialExtent/GeneralGrid/Axis/Extent/Maximum/ Latitude: ("90.0")

DataResource /SpatialExtent/GeneralGrid/Axis/Extent/UOMLabel: ("degrees_north")
DataResource /SpatialExtent/GeneralGrid/Axis/Extent/Maximum/ Longitude   ("180.0")

DataResource /SpatialExtent/GeneralGrid/Axis/Extent/UOMLabel: ("degrees_east")


Case 2: WCS Coverage for Collection

Here the collection spans   a time range:

 

DataResource/DataResourceTemporalExtent/DataResourceTimePoints

DataResource/DataResourceTemporalExtent/DataResourceTimePoints/Time:   (%YEAR%%MONTH%%DAY)  

DataResource/DataResourceTemporalExtent/DataResourceTimePoints/Value:   (2001-01-01)  

DataResource/TemporalResolution: 1

DataResource/TemporalResolutionUnit: day

DataResource/DataResourceTemporalExtent/CoverageTimePoints/Time:   (%YEAR%%MONTH%%DAY)  

DataResource/DataResourceTemporalExtent/CoverageTimePoints/Value:   (current)  

DataResource/DataResourceTemporalExtent/CoverageTimePoints/Description:   (ongoing)  


DataResource/SpatialExtent/GeneralGrid/Axes:

 

DataResource /SpatialExtent/GeneralGrid/Axis/Extent/Label: " AIRX3STD L3 Gridded"

DataResource /SpatialExtent/GeneralGrid/Axis/Extent/Minimum/ Latitude: ("-90.0")

DataResource /SpatialExtent/GeneralGrid/Axis/Extent/UOMLabel: ("degrees_north")
DataResource /SpatialExtent/GeneralGrid/Axis/Extent/Minimum/ Longitude   ("-180.0")

DataResource /SpatialExtent/GeneralGrid/Axis/Extent/UOMLabel: ("degrees_east")

DataResource /SpatialExtent/GeneralGrid/Axis/Extent/Maximum/ Latitude: ("90.0")

DataResource /SpatialExtent/GeneralGrid/Axis/Extent/UOMLabel: ("degrees_north")
DataResource /SpatialExtent/GeneralGrid/Axis/Extent/Maximum/ Longitude   ("180.0")

DataResource /SpatialExtent/GeneralGrid/Axis/Extent/UOMLabel: ("degrees_east")

 

DataResource/SpatialResolution: 10

DataResource/SpatialResolutionUnit: KM

 

OR (SpatialPolygon example)

 

Case 1: WCS Coverage for Granule (swath)

Note: Spatial extent covers an enclosed region described by a series of coordinates. In order to close the polygon, always repeat the first point last.

 

DataResource/DataResourceSpatialExtentType: "SPATIAL_POLYGON"

DataResource/DataResourceSpatialExtent/SpatialPolygons

DataResource/DataResourceSpatialExtent/SpatialPolygons/Coordinates/Latitude: "36.92"

DataResource/DataResourceSpatialExtent/SpatialPolygons/Coordinates/Longitude:   "-120.72"

 

DataResource/DataResourceSpatialExtent/SpatialPolygons/Coordinates/Latitude:   "37.74"

DataResource/DataResourceSpatialExtent/SpatialPolygons/Coordinates/Longitude:   "-121.84"

 

DataResource/DataResourceSpatialExtent/SpatialPolygons/Coordinates/Latitude:   "41.84"

DataResource/DataResourceSpatialExtent/SpatialPolygons/Coordinates/Longitude:   "-123.84"

 

DataResource/DataResourceSpatialExtent/SpatialPolygons/Coordinates/Latitude:   "35.83"

DataResource/DataResourceSpatialExtent/SpatialPolygons/Coordinates/Longitude:   "-120.92"

 

DataResource/DataResourceSpatialExtent/SpatialPolygons/Coordinates/Latitude:   "36.92"

DataResource/DataResourceSpatialExtent/SpatialPolygons/Coordinates/Longitude:   "-120.72"

 

Tags

Required

 

2.2.1.7.7.7               DataResourceSpatialExtentType [R]

Element Specification

DataResource/ DataResource SpatialExtent/ DataResource SpatialExtentType (1) <"SPATIAL_POINT", "SPATIAL_LINE_STRING", "BOUNDING_BOX", "GENERAL_GRID", "SPATIAL_POLYGON">

 

Description

The type of the spatial extent of the layer, feature type   or coverage available from the service.

 

Sample Values: " SPATIAL_POINT ".

 

Tags

Required

 

2.2.1.7.7.8               SpatialResolution [R]

Element Specification

DataResource/SpatialResolution(1)

 

Description

The spatial resolution of the layer, feature type or coverage available from the service.

 

Sample Values: "10".

 

Tags

Required

 

2.2.1.7.7.9               SpatialResolutionUnit [R]

Element Specification

DataResource/SpatialResolutionUnit(1) <Meters, KM, Degrees_North, Degrees_East>

 

Description

The unit of the spatial resolution of the layer, feature type or coverage available from the service.

 

Sample Values: "KM".

 

The list will be managed as a KMS-managed list.

 

Tags

Required

 

2.2.1.7.7.10           DataResourceTemporalExtent [R]

Element Specification

DataResource/DataResourceTemporalExtentType (1)

DataResource/DataResourceTemporalExtent (1)

 

Description

The temporal extent of the layer, feature type or coverage available from the service.

 

Sample Values:

 

DataResource/DataResourceTemporalExtentType: "TIME_STAMP"

DataResource/DataResourceTemporalExtent/TimePoints

DataResource/DataResourceTemporalExtent/TimePoints/Time: "%H:%M:%S"

DataResource/DataResourceTemporalExtent/TimePoints/Value "12:20:01"

DataResource/DataResourceTemporalExtent/TimePoints/Description "Time stamp of the layer"

 

OR

 

DataResource/DataResourceTemporalExtentType: "TIME_RANGE"

DataResource/DataResourceTemporalExtent/TimePoints

DataResource/DataResourceTemporalExtent/TimePoints/Time: "%H:%M:%S"

DataResource/DataResourceTemporalExtent/TimePoints/Value "12:20:01"

DataResource/DataResourceTemporalExtent/TimePoints/Description "First time stamp of the layer"

DataResource/DataResourceTemporalExtent/TimePoints/Time: "%H:%M:%S"

DataResource/DataResourceTemporalExtent/TimePoints/Value "current"

DataResource/DataResourceTemporalExtent/TimePoints/Description "ongoing"

 

Tags

Required

 

2.2.1.7.7.11           DataResourceTemporalExtentType [R]

Element Specification

DataResource/DataResource TemporalExtent/ DataResource Temporal ExtentType (1) <"TIME_STAMP", "TIME_SERIES", "TIME_AVERAGE", "TIME_RANGE">

 

Description

The type of the temporal extent of the layer, feature type or coverage available from the service.

 

Sample Values: " TIME_STAMP ".

 

Tags

Required

 

2.2.1.7.7.12           TemporalResolution [R]

Element Specification

DataResource/TemporalResolution (1)

 

Description

The temporal resolution of the layer, feature type or coverage available from the service.

 

Sample Values: "1".

 

Tags

Required

 

2.2.1.7.7.13           TemporalResolutionUnit [R]

Element Specification

DataResource/TemporalResolutionUnit (1) <DAY, WEEK, MONTH, YEAR>

Description

The unit of the temporal resolution of the layer, feature type or coverage available from the service.

 

Sample Values: "DAY".

 

The list will be managed as a KMS-managed list.

 

Tags

Required

 

2.2.1.7.7.14           RelativePath

Element Specification

DataResource/RelativePath (0..*)

 

Description

Path relative to the root URL for the layer, feature type or coverage service.

 

Format: "%year%/%month%"

 

Sample Values: "2002/01"

 

Note: Some layers are specified as a path relative to the root service endpoint. This field serves to capture this information. The client would simply join the two strings contained in the RelatedURL/URL and DataResource/RelativePath fields to get the fully qualified path to the layer. For example: https://mydaac.nasa.gov/wms_airsL3/2002/01".

 

Tags

Recommended

 

2.2.1.7.7.15           CouplingType

Element Specification

Service/OperationMetadata/CoupledResource/Resource/CouplingType (1) <"LOOSE", "MIXED", "TIGHT">

 

Description

This element contains the coupling type for   the resource(s) coupled to this service.

 

Sample Value: "LOOSE" - this is where a variety of data sources (which are not specified precisely) are used to generate the resource.

 

Sample Value: "MIXED" - this is where a combination of data sources is used to generate the resource.

 

Sample Value: "TIGHT" - this is where a single well-cited data source is used to generate the resource.

 

Tags

Recommended

 

2.2.1.7.8                 Parameter

Element Specification

Service/OperationMetadata/Parameter (0..*)

Service/OperationMetadata/Parameter/ParameterName (1)

Service/OperationMetadata/Parameter/ParameterDirection (1)

Service/OperationMetadata/Parameter/ParameterDescription (0..1)

Service/OperationMetadata/Parameter/ParameterOptionality (1)

Service/OperationMetadata/Parameter/ParameterRepeatability (1)

 

Description

This element contains important information about the parameter associated with the resource(s) coupled to this service. This element is used where there are one or more parameters listed with a service. The parameters listed here may share the same name as variables, and stored elsewhere in UMM, however many service providers choose alternate names for their parameters, so this class accommodates both these cases.

 

2.2.1.7.8.1               ParameterName [R]

Element Specification

Service/OperationMetadata/Parameter/ParameterName (1)

 

Description

This element contains the name of the parameter associated with the resource(s) coupled to this service. If there is a varable-service association, this field identifies the parameter (variable) name sourced for the service.

 

Sample Value: "O3_ppbv"

 

Tags

Required

 

2.2.1.7.8.2               ParameterDirection [R]

Element Specification

Service/OperationMetadata/Parameter/ParameterDirection (1) <"IN", "OUT", "IN/OUT">

 

Description

This element contains the direction of the parameter associated with the resource(s) coupled to this service.

 

Sample Value: "OUT"

 

Tags

Required

 

2.2.1.7.8.3               ParameterDescription [R]

Element Specification

Service/OperationMetadata/Parameter/ParameterDescription (1)

 

Description

This element contains the description of the parameter associated with the resource(s) coupled to this service.

 

Sample Value: "ozone mixing ratio reported in parts per billion by volume"

 

Tags

Required

 

2.2.1.7.8.4               ParameterOptionality [R]

Element Specification

Service/OperationMetadata/Parameter/ParameterOptionality (1) <"TRUE", "FALSE">

 

Description

This element contains the optionality of the parameter associated with the resource(s) coupled to this service.

 

Sample Value: "TRUE"

 

Tags

Required

 

2.2.1.7.8.5               ParameterRepeatability [R]

Element Specification

Service/OperationMetadata/Parameter/ParameterRepeatability (1) <"TRUE", "FALSE">

 

Description

This element contains the repeatability of the parameter associated with the resource(s) coupled to this service.

 

Sample Value: "TRUE"

 

Tags

Required

 

2.2.1.8        OnlineAccessURLPatternMatch

Element Specification

Service/OnlineAccessURLPatternMatch (0..1)

 

Description

A field needed for pattern matching in OPeNDAP services. This field is a placeholder to support ongoing development of the OUS component within CMR.

 

Sample Value: /data/s4pa/

 

Tags

Recommended

 

2.2.1.9        OnlineAccessURLPatternSubstitution

Element Specification

Service/OnlineAccessURLPatternSubstitution (0..1)

 

Description

A field needed for pattern substitution in OPeNDAP services. This field is a placeholder to support ongoing development of the OUS component within CMR.

 

Sample Value: /opendap/

 

Tags

Recommended

 

2.2.1.10    ScienceKeywords

Element Specification

Service/ScienceKeywords (1)

Service/ScienceKeywords/Category (1)
Service/ScienceKeywords/Topic (1)
Service/ScienceKeywords/Term (1)
Service/ScienceKeywords/VariableLevel1 (0..1)
Service/ScienceKeywords/VariableLevel2 (0..1)
Service/ScienceKeywords/VariableLevel3 (0..1)
Service/ScienceKeywords/DetailedVariable (0..1)

 

Description

Allows for the specification of Earth Science keywords that are representative of the service, software, or tool being described. The controlled vocabulary for Science Keywords is maintained in the Keyword Management System (KMS).

 

Sample Value: "EARTH SCIENCE > SOLID EARTH > TECTONICS > EARTHQUAKES > EARTHQUAKE OCCURRENCES"

 

Tags

Recommended

 

2.2.1.11    ServiceKeywords [R]

Element Specification

Service/ServiceKeywords (1)

Service/ServiceKeywords/ServiceCategory (1)
Service/ServiceKeywords/ServiceTopic (1)
Service/ServiceKeywords/ServiceTerm (1)
Service/ServiceKeywords/ServiceSpecificName (0..1)

 

Description

Allows for the specification of Earth Science Service keywords that are representative of the service, software, or tool being described. The controlled vocabulary for Service Keywords is maintained in the Keyword Management System (KMS).

 

Sample Value: "ServiceCategory: Earth Science Services, ServiceTopic: Data Management/Data Handling, ServiceTerm: Data Search and Retrieval".

 

Tags

Required

 

2.2.1.12    ServiceOrganizations [R]

Element Specification

Service/ServiceOrganizations (1..*)

Service/ServiceOrganizations/Roles (1..*) <SERVICE PROVIDER, DEVELOPER, PUBLISHER, AUTHOR, ORIGINATOR>

Service/ServiceOrganizations/ShortName (1)

Service/ServiceOrganizations/LongName (0..1)

Service/ServiceOrganizations/ContactInformation (0..1)

Service/ServiceOrganizations/ContactInformation/RelatedURL (0..*)

Service/ServiceOrganizations/ContactInformation/ServiceHours (0..1)

Service/ServiceOrganizations/ContactInformation/ContactInstructions (0..1)

Service/ServiceOrganizations/ContactInformation/ContactMechanism (0..*)

Service/ServiceOrganizations/ContactInformation/ContactMechanism/Type (1) <Direct Line, Email, Facebook, Fax, Mobile, Modem, Primary, TDD/TTY Phone, Telephone, Twitter, U.S. toll free, Other>

Service/ServiceOrganizations/ContactInformation/ContactMechanism/Value (1)

Service/ServiceOrganizations/ContactInformation/Address (0..*)

Service/ServiceOrganizations/ContactInformation/Address/StreetAddresses (0..*)

Service/ServiceOrganizations/ContactInformation/Address/City (0..1)

Service/ServiceOrganizations/ContactInformation/Address/StateProvince (0..1)

Service/ServiceOrganizations/ContactInformation/Address/PostalCode (0..1)

Service/ServiceOrganizations/ContactInformation/Address/Country (0..1)

 

CHOICE OF:

 

Service/ServiceOrganizations/ContactPersons (0..*)

Service/ServiceOrganizations/ContactPersons/Roles (1..*) <SERVICE PROVIDER CONTACT,, TECHNICAL CONTACT, SCIENCE CONTACT, INVESTIGATOR, SOFTWARE AUTHOR, TOOL AUTHOR, USER SERVICES, SCIENCE SOFTWARE DEVELOPMENT>

Service/ServiceOrganizations/ContactPersons/NonServiceOrganizationAffiliation (0..1)

Service/ServiceOrganizations/ContactPersons/FirstName (0..1)

Service/ServiceOrganizations/ContactPersons/MiddleName (0..1)

Service/ServiceOrganizations/ContactPersons/LastName (1)

Service/ServiceOrganizations/ContactPersons/ContactInformation (0..1)

Service/ServiceOrganizations/ContactPersons/ContactInformation/RelatedURL (0..*)

Service/ServiceOrganizations/ContactPersons/ContactInformation/ServiceHours (0..1)

Service/ServiceOrganizations/ContactPersons/ContactInformation/ContactInstructions (0..1)

Service/ServiceOrganizations/ContactPersons/ContactInformation/ContactMechanism (0..*)

Service/ServiceOrganizations/ContactPersons/ContactInformation/ContactMechanism/Type (1) <Direct Line, Email, Facebook, Fax, Mobile, Modem, Primary, TDD/TTY Phone, Telephone, Twitter, U.S. toll free, Other>

Service/ServiceOrganizations/ContactPersons/ContactInformation/ContactMechanism/Value (1)

Service/ServiceOrganizations/ContactPersons/ContactInformation/Address (0..*)

Service/ServiceOrganizations/ContactPersons/ContactInformation/Address/StreetAddresses (0..*)

Service/ServiceOrganizations/ContactPersons/ContactInformation/Address/City (0..1)

Service/ServiceOrganizations/ContactPersons/ContactInformation/Address/StateProvince (0..1)

Service/ServiceOrganizations/ContactPersons/ContactInformation/Address/PostalCode (0..1)

Service/ServiceOrganizations/ContactPersons/ContactInformation/Address/Country (0..1)

 

OR

 

Service/ServiceOrganizations/ContactGroups (0..*)

Service/ServiceOrganizations/ContactGroups/Roles (1..*) <SERVICE PROVIDER CONTACT, TECHNICAL CONTACT, SCIENCE CONTACT, INVESTIGATOR, SOFTWARE AUTHOR, TOOL AUTHOR, USER SERVICES, SCIENCE SOFTWARE DEVELOPMENT>

Service/ServiceOrganizations/ContactGroups/NonServiceOrganizationAffiliation (0..1)

Service/ServiceOrganizations/ContactGroups/GroupName (1)

Service/ServiceOrganizations/ContactGroups/ContactInformation (0..1)

Service/ServiceOrganizations/ContactGroups/ContactInformation/RelatedURL (0..*)

Service/ServiceOrganizations/ContactGroups/ContactInformation/ServiceHours (0..1)

Service/ServiceOrganizations/ContactGroups/ContactInformation/ContactInstructions (0..1)

Service/ServiceOrganizations/ContactGroups/ContactInformation/ContactMechanism (0..*)

Service/ServiceOrganizations/ContactGroups/ContactInformation/ContactMechanism/Type (1) <Direct Line, Email, Facebook, Fax, Mobile, Modem, Primary, TDD/TTY Phone, Telephone, Twitter, U.S. toll free, Other>

Service/ServiceOrganizations/ContactGroups/ContactInformation/ContactMechanism/Value (1)

Service/ServiceOrganizations/ContactGroups/ContactInformation/Address (0..*)

Service/ServiceOrganizations/ContactGroups/ContactInformation/Address/StreetAddresses (0..*)

Service/ServiceOrganizations/ContactGroups/ContactInformation/Address/City (0..1)

Service/ServiceOrganizations/ContactGroups/ContactInformation/Address/StateProvince (0..1)

Service/ServiceOrganizations/ContactGroups/ContactInformation/Address/PostalCode (0..1)

Service/ServiceOrganizations/ContactGroups/ContactInformation/Address/Country (0..1)

 

Description

The service provider, or organization, or institution responsible for developing, archiving, and/or distributing the service, software, or tool.

 

Please note that ShortName and LongName values come from KMS which is a controlled list.

 

Sample Value: "Role: SERVICE PROVIDER, ShortName: SEDAC, LongName: Socioeconomic Data and Applications Center".

 

Tags

Required, Controlled Vocabulary

 

2.2.1.13    ServiceContacts [R]

Element Specification

Service/ServiceContacts (1)

 

Description

The ServiceContacts is the point of contact for more information about the service, software, or tool.

 

ServiceContacts is a parent element to the ContactPerson and the ContactGroup elements. Its purpose is to hold shared elements that its children will use. The ServiceContacts element must exist with at least 1 of its children; it cannot exist on its own.

 

The ContactPerson and the ContactGroup elements are described in detail in their respective sub-sections.

 

Sample Value:

ContactGroup/Roles: TECHNICAL CONTACT

ContactGroup/GroupName: SEDAC USER SERVICES

ContactGroup/ContactInformation/ContactMechanism/Type: Email

ContactGroup/ContactInformation/ContactMechanism/Value: ciesin.info@ciesin.columbia.edu

ContactGroup/ContactInformation/ContactMechanism/Type: DirectLine

ContactGroup/ContactInformation/ContactMechanism/Value: +1 845-365-8920

ContactGroup/ContactInformation/ContactMechanism/Type: Fax

ContactGroup/ContactInformation/ContactMechanism/Value: +1 845-365-8922

ContactGroup/ContactInformation/Address/StreetAddresses: 61 Route 9W. P.O. Box 1000 Palisades

ContactGroup/ContactInformation/ContactMechanism/Address/StateProvince: NY

ContactGroup/ContactInformation/ContactMechanism/Address/PostalCode:10964

ContactGroup/ContactInformation/ContactMechanism/Address/Country: USA

 

Tags

Required

 

2.2.1.13.1             ContactPersons

Element Specification:

ContactPersons (0..*)

ContactPersons/Roles (1..*) <Service Provider Contact, Technical Contact, Science Contact, Investigator, Metadata Author>

ContactPersons/NonDataCenterAffiliation (0..1)

ContactPersons/FirstName (0..1)

ContactPersons/MiddleName (0..1)

ContactPersons/LastName (1)

ContactPersons/ContactInformation (0..1)

ContactPersons/ContactInformation/RelatedURL (0..*)

ContactPersons/ContactInformation/ServiceHours (0..1)

ContactPersons/ContactInformation/ContactInstructions (0..1)

ContactPersons/ContactInformation/ContactMechanism (0..*)

ContactPersons/ContactInformation/ContactMechanism/Type (1) <Direct Line, Email, Facebook, Fax, Mobile, Modem, Primary, TDD/TTY Phone, Telephone, Twitter, U.S. toll free, Other>

ContactPersons/ContactInformation/ContactMechanism/Value (1)

ContactPersons/ContactInformation/Address (0..*)

ContactPersons/ContactInformation/Address/StreetAddresses (0..*)

ContactPersons/ContactInformation/Address/City (0..1)

ContactPersons/ContactInformation/Address/StateProvince (0..1)

ContactPersons/ContactInformation/Address/PostalCode (0..1)

ContactPersons/ContactInformation/Address/Country (0..1)

 

Description:

This element includes metadata telling a service user whom they may contact to get information about that service, and how they may contact that person. There may be zero to many contact persons. There may be both a contact person or persons and a contact group or groups for a given service.

 

Tags

Recommended

 

2.2.1.13.2             ContactGroups

Element Specification:

ContactGroups (0..*)

ContactGroups/Roles (1..*) <TECHNICAL CONTACT, User Services, Science Software Development>

ContactGroups/NonDataCenterAffiliation (0..1)

ContactGroups/GroupName (1)

ContactGroups/ContactInformation (0..1)

ContactGroups/ContactInformation/RelatedURL (0..*)

ContactGroups/ContactInformation/ServiceHours (0..1)

ContactGroups/ContactInformation/ContactInstructions (0..1)

ContactGroups/ContactInformation/ContactMechanism (0..*)

ContactGroups/ContactInformation/ContactMechanism/Type (1) <Direct Line, Email, Facebook, Fax, Mobile, Modem, Primary, TDD/TTY Phone, Telephone, Twitter, U.S. toll free, Other>

ContactGroups/ContactInformation/ContactMechanism/Value (1)

ContactGroups/ContactInformation/Address (0..*)

ContactGroups/ContactInformation/Address/StreetAddresses (0..*)

ContactGroups/ContactInformation/Address/City (0..1)

ContactGroups/ContactInformation/Address/StateProvince (0..1)

ContactGroups/ContactInformation/Address/PostalCode (0..1)

ContactGroups/ContactInformation/Address/Country (0..1)

 

Description:

This element includes metadata telling a service user which group   they may contact to get information about that service, including how they may contact that group. There may be zero to many contact groups.

There may be both a contact person or persons and a contact group or groups for a given service.

 

Tags

Recommended

 

2.2.1.14    Platforms

Element Specification

Service/Platforms (0..*)
Service/Platforms/ShortName (1)
Service/Platforms/LongName (0..1)
Service/Platforms/Instruments (1..*) {See Instruments for full specification}

 

Description

Associates the satellite/platform that is supported by the service, software, or tool.

 

Please note that ShortName and LongName values come from KMS which is a controlled list.

 

Sample Value:

 

ShortName: AQUA

LongName: Earth Observing System, AQUA

 

Tags

Recommended, Controlled Vocabulary

 

2.2.1.14.1             Instruments

Element Specification

Service/Platforms/Instruments (0..*)
Service/Platforms/Instruments/ShortName (1)
Service/Platforms/Instruments/LongName (0..1)

 

Description

Associates the instrument/sensor that is supported by the service, software, or tool.

 

Please note that ShortName and LongName values come from KMS which is a controlled list.

 

Sample Value:

 

ShortName: MODIS

LongName: Moderate-Resolution Imaging Spectroradiometer

 

Tags

Recommended, Controlled Vocabulary

 

2.2.1.15    ServiceQuality

Element Specification

Service/ServiceQuality (0..1)

Service/ServiceQuality/QualityFlag (1) <"Available", "Unavailable", "Reviewed", "Not Reviewed", "Other">

Service/ServiceQuality/Traceability (0..1)

Service/ServiceQuality/Lineage (0..1)

 

Description

Information about the quality of the service, software, or tool, or any quality assurance procedures followed in development.

 

Sample Value:

Service/ServiceQuality/QualityFlag: "Reviewed"

Service/ServiceQuality/Traceability: "Ticket#1234: Errors have been reported in ServiceMetadata."

Service/ServiceQuality/Lineage: "The software has been reviewed for quality and errors have been found".

 

Tags

Recommended

 

2.2.1.16    ServiceCitation [R]

Element Specification

Service/ServiceCitation (1)

 

Description

Information about citing the service resources.

 

Sample Value: "Mesoamerican Visualization and Monitoring System (SERVIR) is provided by the National Space Science and Technology Center at MSFC, NASA.".

 

Tags

Required

 

2.2.1.17    AccessConstraints

Element Specification

Service/AccessConstraints (0..1)

 

Description

Information about any constraints for accessing the service, software, or tool.

 

Sample Value: "Registration is required to access this service".

 

Tags

Recommended

 

2.2.1.18    UseConstraints

Element Specification

Service/UseConstraints (0..1)

 

Description

Information on how the item (service, software, or tool) may or may not be used after access is granted. This includes any special restrictions, legal prerequisites, terms and conditions, and/or limitations on using the item. Providers may request acknowledgement of the item from users and claim no responsibility for quality and completeness. Use Constraints describes how the item may be used once access has been granted, and is distinct from Access Constraints, which refers to any constraints in accessing the item.

 

Sample Value: "Please credit U.S. Geological Survey as the Service Provider".

 

Tags

Recommended

 

2.2.1.19    AncillaryKeywords

Element Specification

Service/AncillaryKeywords (0..1)

 

Description

Words or phrases to further describe the service, software, or tool.

 

Sample Value: "Hierarchical Data Format, Document Type Definition, Web Map Service".

 

Tags

Recommended

 

2.2.2         Options

The Options class contains information about the service options available. It contains the elements described below.

 

Options/ [0..N]

Options/SubsetTypes

Options/VariableAggregation

Options/SupportedProjections

Options/SupportedProjections/ProjectionName

Options/SupportedProjections/ProjectionEPSGCode

Options/SupportedProjections/ProjectionDatum

Options/InterpolationTypes

Options/SupportedFormats

Options/MaxGranules

 

This element is used to identify the list of supported data transformations. The term "data transformations" is a general term to describe a variety of ways data can be transformed by the service. These include:

 

Subsetting by geographic region
Subsetting by time
Subsetting by variable
Reformatting
Regridding
Variable Aggregration

 

This list of valid data transformations has been sourced from the Data Transformations Working Group.

 

2.2.2.1        SubsetTypes

Element Specification

Options/SubsetTypes (0..*) <SPATIAL, TEMPORAL, VARIABLE>

 

Description

This element is used to identify the list of supported subsetting requests.

 

These include:

 

Subsetting by geographic region
Subsetting by time
Subsetting by variable

 

Sample Value: "SPATIAL"

 

Tags

Recommended

 

2.2.2.2        VariableAggregation

Element Specification

Options/VariableAggregation (0..*) <AVG, COUNT, SUM, MIN, MAX, VAR, ANOMOLY>

 

Description

This element is used to identify the list of supported methods of variable aggregation.

 

These include:

ave - Calculate average value(s).

count - Calculate overall number of data points.

sum - Calculate sum of all data points.

min - Calculate minimum value(s).

max - Calculate maximum value(s).

var - Calculate variance across value(s).

anomaly - Calculate anomaly across value(s).

 

The list above was taken from the MERRA Analytic Services (MAS) example: https://cds.nccs.nasa.gov/wp-content/test/MASOverview.html

 

MAS enables MapReduce analytics over NASA’s Modern-Era Retrospective Analysis for Research and Applications (MERRA) data collection.

 

In this service, a typical average operation can be achieved by sending the following web service request:

 

Example Web Service Request:

 

http://skyportal.sci.gsfc.nasa.gov/cds/mas/order.php?job_name=avg_T_instM_3d_ana_Np&collection=instM_3d_ana_Np&operation=avg&service_request=GetVariableByCollection_Operation_TimeRange_SpatialExtent_VerticalExtent&variable_list=T&start_date=201101&end_date=201102&min_lon=-125&min_lat=24&max_lon=-66&max_lat=50&start_level=13&end_level=13&overwrite

 

This would result in the following XML response:


Example Web Service XML Response:

 

        <Response>
            <sessionId>37734A627B5E7E74AAB8374586D3D018</sessionId>
            <sessionStatus>Received</sessionStatus>
            <sessionStatusDetail>Map Reduce job submitted at Tue Dec 10 16:29:57 EST 2013</sessionStatusDetail>
        </Response>

 

Tags

Recommended

 

2.2.2.3        SupportedInputProjections

Element Specification

Options/SupportedInputProjections (0..*)

Options/SupportedInputProjections/ProjectionName (0..1)

Options/SupportedInputProjections/ProjectionLatitudeOfCenter (0..1)

Options/SupportedInputProjections/ProjectionLongitudeOfCenter (0..1)

Options/SupportedInputProjections/ProjectionFalseEasting (0..1)

Options/SupportedInputProjections/ProjectionFalseNorthing (0..1)

Options/SupportedInputProjections/ProjectionAuthority (0..1)

Options/SupportedInputProjections/ProjectionUnit (0..1)

Options/SupportedInputProjections/ProjectionDatumName (0..1)

 

Description

This element is used to identify the list of supported input projection types.

 

These include:

 

Geographic
Mercator      
Space Oblique Mercator      
Universal Transverse Mercator      
Military Grid Reference System      
MODIS Sinusoidal      
Sinusoidal      
Lambert Equal Area      
NSIDC EASE Grid North and South (Lambert EA)      
NSIDC EASE Grid Global      
EASE Grid 2.0 N. Polar      
EASE Grid 2.0 Global      
Plate Carree      
Polar Stereographic      
WELD Albers Equal Area      
Canadian Albers Equal Area Conic      
Lambert Conformal Conic    

 

This list of projection names has been sourced from the Data Transformation Working Group.

 

Additionally, the following projection names have been cited from individual legacy services at the DAACs:

 

State Plane Coordinates

Albers Equal   Area Conic

Transverse Mercator

Lambert Azimuthal Equal Area

UTM Northern Hemisphere

UTM Southern Hemisphere

Cylindrical

Orthographic

 

Depending on the area and the geographic coordinate system used by a projection a datum must be specified. This may be done using the ProjectionDatum field.

 

The projection may also be expressed using the EPSG code. This is sourced from the EPSG Geodetic Parameter Registry: http://epsg-registry.org. For example, an EPSG code (Authority) of "4326" corresponds to "WGS84, GeodeticCRS (geographic 2D), over an area of the entire world.

 

Sample Value: Options/SupportedInputProjections/ProjectionName: "Geographic"

Sample Value: Options/SupportedInputProjections/ProjectionLatitudeOfCenter: "0"

Sample Value: Options/SupportedInputProjections/ProjectionLongitudeOfCenter: "0"

Sample Value: Options/SupportedInputProjections/ProjectionFalseEasting: "0"

Sample Value: Options/SupportedInputProjections/ProjectionFalseNorthing: "0"

Sample Value: Options/SupportedInputProjections/ProjectionAuthority: "4326"

Sample Value: Options/SupportedInputProjections/ProjectionUnit: "Meters"

Sample Value: Options/SupportedInputProjections/ProjectionDatum: "World Geodetic System (WGS) 1984"

 

Tags

Recommended

 

2.2.2.3.1                 ProjectionName

Element Specification

Options/SupportedInputProjections/ProjectionName (0..1) <Geographic, Mercator, Space Oblique Mercator, Universal Transverse Mercator, Military Grid Reference, MODIS Sinusoidal System, Sinusoidal, Lambert Equal Area, NSIDC EASE Grid North and South (Lambert EA), NSIDC EASE Grid Global, EASE Grid 2.0 N. Polar, Plate Carree, Polar Stereographic, WELD Albers Equal Area, Canadian Albers Equal Area Conic, Lambert Conformal Conic, State Plane Coordinates, Albers Equal Area Conic, Transverse Mercator, Lambert Azimuthal Equal Area, UTM Northern Hemisphere, UTM Southern Hemisphere, Cylindrical>

 

Description

This element is used to identify the list of supported input projection types.

 

Sample Value: "Geographic"

 

Tags

Recommended

 

2.2.2.3.2                 ProjectionLatitudeOfCenter

Element Specification

Options/SupportedOutputProjections/ProjectionLatitudeOfCenter (0..1)

 

Description

This element is used to identify the origin of the x-coordinates at the center of the projection.

 

Sample Value: "0"

 

Tags

Recommended

 

2.2.2.3.3                 ProjectionLongitudeOfCenter

Element Specification

Options/SupportedOutputProjections/ProjectionLongitudeOfCenter (0..1)

 

Description

This element is used to identify the origin of the y-coordinates at the center of the projection.

 

Sample Value: "0"

 

Tags

Recommended

 

2.2.2.3.4                 ProjectionFalseEasting

Element Specification

Options/SupportedOutputProjections/ProjectionFalseEasting (0..1)

 

Description

This element is used to identify the linear value applied to the origin of the y-coordinates. False easting and northing values are usually applied to ensure that all the x and y values are positive.

 

Sample Value: "0"

 

Tags

Recommended

 

2.2.2.3.5                 ProjectionFalseNorthing

Element Specification

Options/SupportedOutputProjections/ProjectionFalseNorthing (0..1)

 

Description

This element is used to identify the linear value applied to the origin of the x-coordinates. False easting and northing values are usually applied to ensure that all the x and y values are positive.

 

Sample Value: "0"

 

Tags

Recommended

 

2.2.2.3.6                 ProjectionAuthority

Element Specification

Options/SupportedInputProjections/ProjectionAuthority (0..1) <"4326", "3395", "9807", "2000.63", "2163", "3408", "3410", "6931", "6933", "3411", "9822", "9822", "54003", "54008", "54009", "900913">

 

Description

This element is used to identify the authority, expressed as the EPSG code, for the list of supported input projection types.

 

Sample Value: "4326"

 

Tags

Recommended

 

2.2.2.3.7                 ProjectionUnit

Element Specification

Options/SupportedInputProjections/ProjectionUnit (0..1) <"Meters", "Degrees">

 

Description

This element is used to identify the projection unit of measurement.

 

Sample Value: "Meters"

 

Tags

Recommended

 

2.2.2.3.8                 ProjectionDatumName

Element Specification

Options/SupportedInputProjections/ProjectionDatumName (0..1) <"North American Datum (NAD) 1927", "North American Datum (NAD) 1983", "World Geodetic System (WGS) 1984">

 

Description

This element is used to identify the datum names.

 

Sample Value: "World Geodetic System (WGS) 1984"

 

Tags

Recommended

 

2.2.2.4        SupportedOutputProjections

Element Specification

Options/SupportedOutputProjections (0..*)

Options/SupportedOutputProjections/ProjectionName (0..1)

Options/SupportedOutputProjections/ProjectionLatitudeOfCenter (0..1)

Options/SupportedOutputProjections/ProjectionLongitudeOfCenter (0..1)

Options/SupportedOutputProjections/ProjectionFalseEasting (0..1)

Options/SupportedOutputProjections/ProjectionFalseNorthing (0..1)

Options/SupportedOutputProjections/ProjectionAuthority (0..1)

Options/SupportedOutputProjections/ProjectionUnit (0..1)

Options/SupportedOutputProjections/ProjectionDatumName (0..1)

 

Description

This element is used to identify the list of supported output projection types.

 

These include:

Geographic
Mercator      
Space Oblique Mercator      
Universal Transverse Mercator      
Military Grid Reference System      
MODIS Sinusoidal      
Sinusoidal      
Lambert Equal Area      
NSIDC EASE Grid North and South (Lambert EA)      
NSIDC EASE Grid Global      
EASE Grid 2.0 N. Polar      
EASE Grid 2.0 Global      
Plate Carree      
Polar Stereographic      
WELD Albers Equal Area      
Canadian Albers Equal Area Conic      
Lambert Conformal Conic    

 

This list of projection names has been sourced from the Data Transformation Working Group.

 

Additionally, the following projection names have been cited from individual legacy services at the DAACs:

 

State Plane Coordinates

Albers Equal   Area Conic

Transverse Mercator

Lambert Azimuthal Equal Area

UTM Northern Hemisphere

UTM Southern Hemisphere

Cylindrical

Orthographic

 

Depending on the area and the geographic coordinate system used by a   projection a datum must be specified. This may be done using the ProjectionDatum field.

 

The projection may also be expressed using the EPSG code. This is sourced from the EPSG Geodetic Parameter Registry: http://epsg-registry.org. For example, an EPSG code of "4326" corresponds to "WGS84, GeodeticCRS (geographic 2D), over an area of the entire world.

 

Sample Value: Options/SupportedOutputProjections/ProjectionName: "Albers Equal Area"

Sample Value: Options/SupportedOutputProjections/ProjectionLatitudeOfCenter: "0"

Sample Value: Options/SupportedOutputProjections/ProjectionLongitudeOfCenter: "0"

Sample Value: Options/SupportedOutputProjections/ProjectionFalseEasting: "0"

Sample Value: Options/SupportedOutputProjections/ProjectionFalseNorthing: "0"

Sample Value: Options/SupportedOutputProjections/ProjectionAuthority: "9822"

Sample Value: Options/SupportedOutputProjections/ProjectionUnit: "Meters"

Sample Value: Options/SupportedOutputProjections/ProjectionDatum: "World Geodetic System (WGS) 1984"

 

Tags

Recommended

 

2.2.2.4.1                 ProjectionName

Element Specification

Options/SupportedOutputProjections/ProjectionName (0..1) <Geographic, Mercator, Space Oblique Mercator, Universal Transverse Mercator, Military Grid Reference, MODIS Sinusoidal System, Sinusoidal, Lambert Equal Area, NSIDC EASE Grid North and South (Lambert EA), NSIDC EASE Grid Global, EASE Grid 2.0 N. Polar, Plate Carree, Polar Stereographic, WELD Albers Equal Area, Canadian Albers Equal Area Conic, Lambert Conformal Conic, State Plane Coordinates, Albers Equal Area Conic, Transverse Mercator, Lambert Azimuthal Equal Area, UTM Northern Hemisphere, UTM Southern Hemisphere, Cylindrical>

 

Description

This element is used to identify the list of supported output projection types.

 

Sample Value: "Sinusoidal"

 

Tags

Recommended

 

2.2.2.4.2                 ProjectionLatitudeOfCenter

Element Specification

Options/SupportedOutputProjections/ProjectionLatitudeOfCenter (0..1)

 

Description

This element is used to identify the origin of the x-coordinates at the center of the projection.

 

Sample Value: "0"

 

Tags

Recommended

 

2.2.2.4.3                 ProjectionLongitudeOfCenter

Element Specification

Options/SupportedOutputProjections/ProjectionLongitudeOfCenter (0..1)

 

Description

This element is used to identify the origin of the y-coordinates at the center of the projection.

 

Sample Value: "0"

 

Tags

Recommended

 

2.2.2.4.4                 ProjectionFalseEasting

Element Specification

Options/SupportedOutputProjections/ProjectionFalseEasting (0..1)

 

Description

This element is used to identify the linear value applied to the origin of the y-coordinates. False easting and northing values are usually applied to ensure that all the x and y values are positive.

 

Sample Value: "0"

 

Tags

Recommended

 

2.2.2.4.5                 ProjectionFalseNorthing

Element Specification

Options/SupportedOutputProjections/ProjectionFalseNorthing (0..1)

 

Description

This element is used to identify the linear value applied to the origin of the x-coordinates. False easting and northing values are usually applied to ensure that all the x and y values are positive.

 

Sample Value: "0"

 

Tags

Recommended

 

2.2.2.4.6                 ProjectionAuthority

Element Specification

Options/SupportedOutputProjections/ProjectionAuthority (0..1) <"4326", "3395", "9807", "2000.63", "2163", "3408", "3410", "6931", "6933", "3411", "9822", "9822", "54003", "54008", "54009", "900913">

 

Description

This element is used to identify the authority, expressed as the EPSG code, for the list of supported output projection types.

 

Sample Value: "4326"

 

Tags

Recommended

 

2.2.2.4.7                 ProjectionUnit

Element Specification

Options/SupportedOutputProjections/ProjectionUnit (0..1) <"Meters", "Degrees">

 

Description

This element is used to identify the projection unit of measurement.

 

Sample Value: "Meters"

 

Tags

Recommended

 

2.2.2.4.8                 ProjectionDatumName

Element Specification

Options/SupportedOutputProjections/ProjectionDatumName (0..1) <"North American Datum (NAD) 1927", "North American Datum (NAD) 1983", "World Geodetic System (WGS) 1984">

 

Description

This element is used to identify the datum names.

 

Sample Value: "North American Datum (NAD) 1983"

 

Tags

Recommended

 

2.2.2.5        InterpolationTypes

Element Specification

Options/InterpolationTypes (0..*) <Nearest Neighbor, Cubic Convolution, Distance-weighted average resampling, Bilinear Interpolation>

 

Description

This element is used to identify the list of supported interpolation types. This is the method of interpolation used by the service during a regridding operation.

 

Sample Value: "Bilinear Interpolation, Nearest Neighbor, Cubic Convolution"

 

Tags

Recommended

 

2.2.2.6        SupportedInputFormats

Element Specification

Options/SupportedInputFormats (0..*) <HDF4, HDF5, HDF-EOS, HDF-EOS2, NETCDF-3, NETCDF-4, GEOTIFF, GEOTIFFINT16, GEOTIFFFLOAT32, XML, ASCII, BINARY, ICARTT, PNG, JPEG, GIF, TIFF, XLSX, JSON, CSV, KML>

 

Description

The project element describes the list of input format names supported by the service.

 

These include:


hdf4
hdf5
hdfeos
netcdf3
netcdf4
geotiff
xml
ascii
icartt
xlsx
json
csv

 

This list of valid formats has been taken from the Data Transformation Working Group.

 

Additionally, the following formats have been cited from individual legacy services at the DAACs:

 

hdfeos2

binary

geotiffint16

geotifffloat32

png

jpeg

gif

tiff

 

Sample Value: "HDF4"

 

Tags

Recommended

 

2.2.2.7        SupportedOutputFormats

Element Specification

Options/SupportedOutputFormats (0..*) <HDF4, HDF5, HDF-EOS, HDF-EOS2, NETCDF-3, NETCDF-4, GEOTIFF, GEOTIFFINT16, GEOTIFFFLOAT32, XML, ASCII, BINARY, ICARTT, PNG, JPEG, GIF, TIFF, XLSX, JSON, CSV, KML>

 

Description

The project element describes the list of output format names supported by the service.

 

These include:


hdf4
hdf5
hdfeos
netcdf3
netcdf4
geotiff
xml
ascii
icartt
xlsx
json
csv

 

This list of valid formats has been taken from the Data Transformation Working Group.

 

Additionally, the following formats have been cited from individual legacy services at the DAACs:

 

hdfeos2

binary

geotiffint16

geotifffloat32

png

jpeg

gif

tiff

 

Sample Value: "HDF5"

 

Tags

Recommended

 

2.2.2.8        MaxGranules

Element Specification

Options/MaxGranules (0..1)

 

Description

This field indicates the maximum number of granules which this service can download with one request.

 

Sample Value: 32676

 

Tags

Recommended


Appendix A.                Deprecated Elements

With the revisions needed for the End-to-End Services, UI/UX driven approach to services, the following elements were removed:

 

Metadata Language

Metadata Standard

Metadata Dates

Lineage

Entry ID

Entry Title

Abstract

Purpose

Service Language

Data Dates

Responsibility

Party

Quality

Metadata Association

ISO Topic Category

Additional Attributes

Distribution

Project

 

These deprecated elements apply to the UMM-S model only. Elements which have these names have not been removed from the UMM-C model.


Appendix B.                 Tags Glossary

Table 4 : Tags Glossary

Tag Name

Description

Required

This element is required.

Controlled Vocabulary

This element will have a vocabulary that will be used to validate the value. This will most likely be done via a vocabulary management service.

Recommended

This element is recommended.

 


Appendix C.                Abbreviations and Acronyms

Table 5 : Abbreviations and Acronyms

ACL

Access Control List

API

Application Programming Interface

CMR

Common Metadata Repository

CSV

Comma-Separated Values

DAAC

Distributed Active Archive Center

DOI

Digital Object Identifier

ECHO

Earth Observing System (EOS) Clearing House

EOS

Earth Observing System

EOSDIS

Earth Observing System Data and Information System

ESDIS

Earth Science Data and Information System

ESO

Earth Science Office

GCMD

Global Change Master Directory

ISO

International Organization for Standardization

KMS

Keyword Management System

MAS

Metadata Architecture Studies

MENDS

Metadata Evolution for NASA Data Systems

MMT

Metadata Management Tool

MVP

Minimum Viable Product

NASA

National Aeronautics and Space Administration

NOAA

National Oceanic and Atmospheric Administration

OPeNDAP

Open-source Project for a Network   Data Access Protocol

SERF

Service Entry Resource Format

UI

User Interface

UML

Unified Modeling Language

UMM

Unified Metadata Model

UMM-C

Unified Metadata Model - Collections

UMM-Common

Unified Metadata Model - Common Elements

UMM-G

Unified Metadata Model - Granules

UMM-M

Unified Metadata Model - Metadata

UMM-S

Unified Metadata Model - Services

UMM-Var

Unified Metadata Model - Variables

UMM-Vis

Unified Metadata Model - Visualization

URI

Uniform Resource Identifier

URL

Uniform Resource Locator

URS

User Registration System

UX

User Experience

WCS

Open Geospatial Consortium Web Coverage Service

WMS

Open Geospatial Consortium Web Mapping Service

XML

Extensible Markup Language

XPath

XML Path Language