I'm finding an error querying the CMR for some MODIS-Terra granules. This is the original query:
https://cmr.earthdata.nasa.gov/search/granules.umm_json_v1_6_6?collection_concept_id=C1940475563-POCLOUD&temporal=2025-01-10T00:00:00Z/P1D&page_size=300
It returns an HTTP status of 500, or internal server error. If I modify the time period, I've reduced the troublesome time range to sometime between 2025-01-10 10:30 Z and 10:50 Z.
I presume there is at least one bad granule in this time period that is causing this error?
CMR internal server error
-
schut_satelligence_com
- Posts: 1
- Joined: Thu May 30, 2024 5:42 am America/New_York
Re: CMR internal server error
This is interesting. We recently hit exactly the same issue, but then when searching for Sentinel-1 data on the ASF DAAC.
The time period is different, but the day is the same.
We identified at least 2 time ranges on 2025-01-10 that result in this error (on ASF):
2025-01-10 15:32:42.597656 - 2025-01-10 15:34:48.281250
2025-01-10 17:19:30.703125 - 2025-01-10 17:19:39.492187
We already notified ASF about it, and they are looking into it. But I thought it would be beneficial to also post our experience here, because it rather seems related to the CMR software itself (or the database), then to a specific sensor (or DAAC ___location)?
The time period is different, but the day is the same.
We identified at least 2 time ranges on 2025-01-10 that result in this error (on ASF):
2025-01-10 15:32:42.597656 - 2025-01-10 15:34:48.281250
2025-01-10 17:19:30.703125 - 2025-01-10 17:19:39.492187
We already notified ASF about it, and they are looking into it. But I thought it would be beneficial to also post our experience here, because it rather seems related to the CMR software itself (or the database), then to a specific sensor (or DAAC ___location)?