Tempo feed entries missing "updated" field

[earthengine_urs]

When querying for TEMPO V4 products via the JSON API, we noticed that the "updated" field is not among those returned in each feed entry, such as

"feed": {
"updated": "2026-06-04T12:21:34.712Z",
"id": "https://cmr.earthdata.nasa.gov:443/search/granules.json?online_only=true&collection_concept_id[]=C3685896149-LARC_CLOUD&page_size=1&page_num=1&sort_key=-revision_date",
"title": "ECHO granule metadata",
"entry": [
{
"producer_granule_id": "TEMPO_CLDO4_L3_V04_20250912T160435Z_S007.nc",
"time_start": "2025-09-12T16:04:35.000Z",
"dataset_id": "TEMPO gridded cloud fraction and pressure (O2-O2 dimer) Version V04 (PROVISIONAL)",
"data_center": "LARC_CLOUD",
"title": "TEMPO_CLDO4_L3_V04_20250912T160435Z_S007.nc",
"coordinate_system": "CARTESIAN",
"day_night_flag": "UNSPECIFIED",
"time_end": "2025-09-12T17:04:16.000Z",
"id": "G4206479863-LARC_CLOUD",
"original_format": "UMM_JSON",
"granule_size": "0",
"browse_flag": true,

We see this for concept IDs C3685896708-LARC_CLOUD, C3685897141-LARC_CLOUD, C3685896625-LARC_CLOUD, C3685896402-LARC_CLOUD, and C3685896149-LARC_CLOUD.

We've not run into entries without "updated" before so maybe this is normal, and we can issue the more expensive UMM JSON queries for the true revision dates as a backup. But we first wanted to check if this omission is expected/intentional.

[ASDC - ghayescrepps]

Thank you for reaching out with your question. Or team has been investigating.
In the CMR API response, there is a “feed:{ “updated” “field (as shown in your screenshot), which is the date/time the API search was executed and should be returned; this field is not related to the granule metadata.
https://cmr.earthdata.nasa.gov/search/site/docs/search/api.html#general-request-details:~:text=representing%20a%20feed%20of

If you did not receive the “updated” field, was the rest of the results seem correct? It may have occurred during a system outage and the query was not fulfilled properly. Could you please share your query return that does not include the “updated” field (and the general date/time of your query, if known) so we can investigate further?

[earthengine_urs]

Thanks for the response. The granule contents all look reasonable, with the start and end times correlating with the filename, and the download URL is correct. Here's a full response of the same query that I just (3:31 PM EDT on 2026/6/5) ran, showing that "feed.entry[0].updated" is not present:

Code: Select all

{
  "feed": {
    "updated": "2026-06-05T19:31:10.641Z",
    "id": "https://cmr.earthdata.nasa.gov:443/search/granules.json?online_only=true&collection_concept_id%5B%5D=C3685896149-LARC_CLOUD&page_size=1&page_num=1&sort_key=-revision_date",
    "title": "ECHO granule metadata",
    "entry": [
      {
        "producer_granule_id": "TEMPO_CLDO4_L3_V04_20250914T170352Z_S008.nc",
        "time_start": "2025-09-14T17:03:52.000Z",
        "dataset_id": "TEMPO gridded cloud fraction and pressure (O2-O2 dimer) Version V04 (PROVISIONAL)",
        "data_center": "LARC_CLOUD",
        "title": "TEMPO_CLDO4_L3_V04_20250914T170352Z_S008.nc",
        "coordinate_system": "CARTESIAN",
        "day_night_flag": "UNSPECIFIED",
        "time_end": "2025-09-14T18:03:33.000Z",
        "id": "G4207728939-LARC_CLOUD",
        "original_format": "UMM_JSON",
        "granule_size": "0",
        "browse_flag": true,
        "polygons": [
          [
            "57.42 -163.98 57.14 -163.18 56.7 -162.68 55.8 -157.92 54.48 -152.96 53.2 -149.24 51.96 -146.26 50.3 -142.92 48.5 -139.9 46.3 -136.82 43.86 -133.98 41.06 -131.28 38.24 -129.02 35.06 -126.9 31.88 -125.14 28.62 -123.64 25.26 -122.36 21.58 -121.22 17.54 -120.24 17.36 -112.06 17.2 -97.66 17.22 -82.34 17.46 -65.16 21.44 -64.28 25.36 -63.2 28.98 -61.98 32.56 -60.52 35.94 -58.86 39.04 -57.04 42.04 -54.94 44.64 -52.78 47.58 -49.84 50.22 -46.60001 52.72 -42.8 54.7 -39.06 56.44 -34.98 58.02 -30.26001 59.16 -25.84 60.28 -20.14 60.98 -20.14 61.52 -20.32001 61.5 -20.54001 62.22 -20.58 62.12 -21.22 62.94 -21.24001 62.88 -21.68001 63.74 -21.7 63.56 -22.90001 63.7 -23.02 63.68 -23.26001 62.28 -33.02 60.78 -44.28001 59.84 -52.72 59.18 -59.32 58.7 -64.60001 58.06 -74.46 57.76 -82.06001 57.64 -88.4 57.68 -97.18 57.9 -104.36 58.36 -112.84 58.98 -120.92 60 -131.32 60.56 -135.76 60.58 -136.34 60.94 -138.84 60.9 -139.02 61.06 -139.78 61.04 -140.02 61.3 -141.7 61.26 -141.86 61.38 -142.3 62.02 -147.42 63.62 -158.5 63.74 -159.74 63.48 -159.76 63.54 -160.28 63.16 -160.3 63.24 -160.8 61.9 -160.82 61.9 -160.94 61.8 -160.96 61.84 -161.3 61.74 -161.32 61.82 -161.86 60.86 -161.88 60.9 -162.18 59.8 -162.34 59.82 -162.56 59.66 -162.58 59.72 -163.04 58.88 -163.14 58.9 -163.34 58.68 -163.36 58.74 -163.78 58.16 -163.8 58.18 -163.98 57.42 -163.98"
          ]
        ],
        "collection_concept_id": "C3685896149-LARC_CLOUD",
        "online_access_flag": true,
        "links": [
          {
            "rel": "http://esipfed.org/ns/fedsearch/1.1/browse#",
            "title": "Download thumb-TEMPO_CLDO4_L3_V04_20250914T170352Z_S008.nc.png",
            "hreflang": "en-US",
            "href": "https://data.asdc.earthdata.nasa.gov/asdc-prod-public/TEMPO/TEMPO_CLDO4_L3_V04/2025.09.14/thumb-TEMPO_CLDO4_L3_V04_20250914T170352Z_S008.nc.png"
          },
          {
            "rel": "http://esipfed.org/ns/fedsearch/1.1/browse#",
            "title": "This link provides direct download access via S3 to the granule",
            "hreflang": "en-US",
            "href": "s3://asdc-prod-public/TEMPO/TEMPO_CLDO4_L3_V04/2025.09.14/thumb-TEMPO_CLDO4_L3_V04_20250914T170352Z_S008.nc.png"
          },
          {
            "rel": "http://esipfed.org/ns/fedsearch/1.1/data#",
            "title": "Download TEMPO_CLDO4_L3_V04_20250914T170352Z_S008.nc",
            "hreflang": "en-US",
            "href": "https://data.asdc.earthdata.nasa.gov/asdc-prod-protected/TEMPO/TEMPO_CLDO4_L3_V04/2025.09.14/TEMPO_CLDO4_L3_V04_20250914T170352Z_S008.nc"
          },
          {
            "rel": "http://esipfed.org/ns/fedsearch/1.1/s3#",
            "title": "This link provides direct download access via S3 to the granule",
            "hreflang": "en-US",
            "href": "s3://asdc-prod-protected/TEMPO/TEMPO_CLDO4_L3_V04/2025.09.14/TEMPO_CLDO4_L3_V04_20250914T170352Z_S008.nc"
          },
          {
            "rel": "http://esipfed.org/ns/fedsearch/1.1/metadata#",
            "title": "api endpoint to retrieve temporary credentials valid for same-region direct s3 access",
            "hreflang": "en-US",
            "href": "https://data.asdc.earthdata.nasa.gov/s3credentials"
          },
          {
            "rel": "http://esipfed.org/ns/fedsearch/1.1/service#",
            "title": "OPeNDAP request URL",
            "hreflang": "en-US",
            "href": "https://opendap.earthdata.nasa.gov/collections/C3685896149-LARC_CLOUD/granules/TEMPO_CLDO4_L3_V04_20250914T170352Z_S008.nc"
          },
          {
            "inherited": true,
            "rel": "http://esipfed.org/ns/fedsearch/1.1/metadata#",
            "hreflang": "en-US",
            "href": "https://tempo.si.edu"
          },
          {
            "inherited": true,
            "rel": "http://esipfed.org/ns/fedsearch/1.1/metadata#",
            "hreflang": "en-US",
            "href": "https://doi.org/10.5067/IS-40e/TEMPO/CLDO4_L3.004"
          },
          {
            "inherited": true,
            "rel": "http://esipfed.org/ns/fedsearch/1.1/documentation#",
            "hreflang": "en-US",
            "href": "https://asdc.larc.nasa.gov/citing-data"
          },
          {
            "inherited": true,
            "rel": "http://esipfed.org/ns/fedsearch/1.1/data#",
            "hreflang": "en-US",
            "href": "https://search.earthdata.nasa.gov/search/granules?p=C3685896149-LARC_CLOUD"
          },
          {
            "inherited": true,
            "rel": "http://esipfed.org/ns/fedsearch/1.1/documentation#",
            "hreflang": "en-US",
            "href": "https://asdc.larc.nasa.gov/documents/tempo/guide/TEMPO_Level-2-3_trace_gas_clouds_user_guide_V2.1.pdf"
          },
          {
            "inherited": true,
            "rel": "http://esipfed.org/ns/fedsearch/1.1/metadata#",
            "hreflang": "en-US",
            "href": "https://www.earthdata.nasa.gov/data/instruments/tempo"
          }
        ]
      }
    ]
  }
}

[ASDC - ghayescrepps]

Thank you for the example. We have been discussing this topic with the CMR team and have some additional information to provide:

The "feed.entry updated" field represents the “date/time of the last update to the associated metadata” and is pulled from the granule metadata “ProviderDates” field. However, the "ProviderDates" field must contain at least one date with associated tag of Create, Insert, Update, or Delete, with only one Date/Tag pair being required. If a data provider includes an “Update” tag pair, then this date will be used in the "feed.entry updated" field. However, if there is no “Update” tag (e.g., only a “Create” date is provided), then nothing is returned in the "feed.entry updated" field.

Therefore, I do not think that the feed.entry updated field is a reliable field to assume will always be present. Depending on your script set up, there may be a different field that would be a better choice.

Example:
"ProviderDates": [
{
"Date": "2022-09-06T14:20:20.791Z",
"Type": "Insert"
},
{
"Date": "2022-09-06T14:20:20.791Z",
"Type": "Update"
}
],

[earthengine_urs]

It doesn't look like there are any metadata timestamps in the JSON result, just the start and end time of the observation. So I think our only option is to use the more expensive UMM JSON endpoint to list the granules.