Skip to end of metadata
Go to start of metadata

The aim of this checklist is to provide a brief overview of the core requirements for LANCE Near Real-Time (NRT) elements. This checklist should not be used instead of the full LANCE Requirements document and relevant appendices. 

For full details please refer to the LANCE Requirements document: 423-RQMT-002 and relevant appendices, which are available from   The core document captures the system requirements for LANCE; variations from the core element are contained in the appendices.

  • Appendix A   LANCE MODIS / VIIRS Requirements.
  • Appendix B   LANCE AIRS Requirements
  • Appendix C   LANCE MLS Requirements
  • Appendix D   LANCE Ozone Requirements
  • Appendix E   LANCE AMSR-2 Requirements
  • Appendix F   LANCE MISR Requirements 
  • Appendix G   LANCE VIIRS Land Requirements
  • Appendix H   LANCE OMPS Requirements
  • Appendix I    LANCE MOPITT Requirements
  • Appendix J    LANCE VIIRS Atmosphere Requirements
  • Appendix K   LANCE LIS (ISS) 

In the LANCE Requirements document, the requirements are broken down in to the following categories:

  • System Requirements
  • Ingest Requirements
  • Data Processing Requirements
  • Data Distribution Requirements
  • User Services and Support Requirements
  • Algorithm and Product Validation Requirements

In addition the LANCE element will help develop an Appendix specific to each LANCE element with specific requirements and/or exceptions to the core requirements. This Appendix should be modeled after the current LANCE provider appendices (e.g. 423-RQMT-002_D_OMI Requirements) available from

A. Summary of key requirements

A.1. As appropriate, provide L0, L1 and L2 data products within 3 hours of observation (L3 products will vary).

A.2. Short Name should have the _NRT suffix e.g. AIRIBRAD_NRT.005

A.3. Provide HTTPS interfaces for data distribution.

A.4. Implement redundant processing and distribution servers to ensure operational availability.

A.5. Register metadata in CMR. Please see Onboarding Process for a new CMR provider

  • Ensure metadata provided to CMR includes a “CollectionDataType” of “NEAR_REAL_TIME” to identify/discover NRT collections.

A.6. Provide full-resolution browse imagery to GIBS.

A.7. Participate in the LANCE Element telecons and User Working Group meetings.

A.8. Create Digital Object Identifiers (DOI) for NRT products. (more information on the DOI process)

B. System requirements

Servers, software and hardware should:

B.1. Be capable of ingesting data at the rate provided by data provider[1].

B.2. Process and distribute data to users within 3 hours of observation.

B.3. Implement redundancy to ensure a goal of 100% operational availability.

[1] Existing data providers are: EOSDIS Data and Operations System (EDOS) for AIRS, MLS, MISR, MODIS, OMI, OMPS and VIIRS, and the Japan Aerospace Exploration Agency (JAXA) for AMSR2. Data for LIS is downloaded from the International Space Station (ISS)

C. Data Distribution

C.1 Provide basic data subscription services to all users.

  • Existing LANCE providers do this on a request basis.

C.2  Maintain a minimum of a 7-day rolling archive and a maximum of 14 days.  Deviations to this will be reflected in respective Appendices.

C.3 Integrate with EOSDIS Earthdata Login (formally known as URS) and restrict data access to users with a valid Earthdata login account.

D. Metrics and Metadata Requirements

D.1 Provide metrics to ESDIS Metric System (EMS) for Ingest, Archive and Distribution as described in the ICD between EMS and the Data Providers[1]. See onboarding notes from EMS.

D.2 Short name should have the _NRT suffix e.g. AIRIBRAD_NRT.005

D.3 Create Digital Object Identifiers (DOIs) for collection level products[2]

D.4 Register data granules in CMR within an average of 15 minutes after products are available for download from Element.

D.5 The following metadata elements are required: 

◦      CollectionDataType - this should be set to “NEAR_REAL_TIME” to identify/discover NRT collections e.g. <CollectionDataType>NEAR_REAL_TIME</CollectionDataType> 

◦      Metadata Standard Name

◦      Metadata Standard Version

◦      Science Keywords

◦      Temporal Extent Information

◦      Spatial Extent Information

◦      Platform

◦      Instrument

◦      Campaign[3]

Note: Metadata Standard Name and Metadata Standard Version have recently been added to the ECHO 10 xml schema. The latest ECHO10 schema can be found at:

[1] Document number 423-47-01 -

[2] The LANCE UWG recommended DOIs be created for LANCE data. DOI wiki:

[3] Example for campaign entry: <Campaign><ShortName>LANCE</ShortName><LongName>Land, Atmosphere Near real-time Capability for EOS</LongName></Campaign>

E. LANCE User Services and Support Requirements

E.1  Provide web content and links to data, FAQs Help, Algorithm Theoretical Basis Document (ATBD) or equivalent, User Guide and System status for the Earthdata LANCE website.

E.2  Utilize the ESDIS (Kayako) User Support Tool (UST) to provide user services and direct users to DAACs or other user service teams as appropriate for user questions.

E.3  Inform users of planned down time and gaps in NRT data. Most LANCE elements do this via a NASA mailing lists (see Support and Mailing lists under the FAQs. See for more information.

E.4 Notify users of any quality issues that arise unexpectedly due to events such as data gaps, anomalies, processing failures, instrument or spacecraft events and/or issues that they are aware of. 

E.5 Nominate a point of contact to participate in bi-weekly LANCE telecons.

E.6  Provide updates for and participate in LANCE UWG meetings, which are held twice a year.

F. LANCE Algorithm and Product Validation

F.1  Coordinate with the Science Team to make available LANCE products using the latest algorithms.

F.2  Provide products from both existing and new / latest algorithms (for the period specified in the LANCE Element Appendix) to give users sufficient time to transition to the latest algorithms. Provide information on the differences between the algorithms on the Earthdata LANCE website.

F.3  Work with the science team to compare NRT products to standard products and identify and document the differences.

F.4  Provide information on quality differences between NRT and standard science data products and provide descriptions of the differences on

G. GIBS Imagery Requirements

G.1  Develop and baseline the GIBS Imagery as outlined in the ICD between the GIBS and Imagery Providers (423-ICD-009 obtained from

G.2 Provide full-resolution daily composite and/or granule-based visualizations of science data parameters.

G.3 Provide imagery products to GIBS within 45 minutes, on a best effort basis, after products are available for download from Element.

G.4 Provide imagery products to GIBS after metadata has been registered with ECHO/CMR.

Key Points of Contact

LANCE Manager - Karen Michael

LANCE Operations Manager  - Diane Davies

DOIs – Lalit Wanchoo

Earthdata content  - Minnie Wong

CMR - Dana Shum

GIBS - Matt Cechini

URS 4 implementation - Peter Smith

  • No labels