Forum

For an accurate and timely response, it would be a good idea to start a new thread with proper subject line! The most efficient method is to search and order AOD data using LAADS "Find Data" interface at: https://ladsweb.modaps.eosdis.nasa.gov/search/order/1/MYD04_L2--61 You can use LAADS ...

"I realize that achieving consistency across thousands of datasets is hard." --True!

Good point! However, a change in data is reflected by the change in last part of the granule id (the production date, e.g., "2018059034713" in MYD03.A2010123.2315.061.2018059034713.hdf) and the change in the "updated" field shows updates in metadata.

Glad that you found the solution and the issue is resolved.

Yes, CMR records for all LAADS data products have been updated starting August 1, 2024. The update is due to changing data access URL from on-premise to Cloud, see announcement at:
https://ladsweb.modaps.eosdis.nasa.gov/cloud/

There is a typo in the data link in the wget command on our website. In the wget command on the page it shows two forward slashes "//" at the end of the URL where there should be only one, see: https://ladsweb.modaps.eosdis.nasa.gov/alerts-and-issues/148498 The command will work if you rem...

There are no negative CTT values for either of the files you mentioned (see attached).
Both offset and scale factor are correct as provided.

see:
For stored value = 14840
CTT_actual =0.01*(14840-(-15000)) = 298.4

For stored value = 14960
CTT_actual =0.01*(14960-(-15000)) = 299.6

See over here:
https://ladsweb.modaps.eosdis.nasa.gov/missions-and-measurements/products/VNP46A4#product-information

No, there is no delay in syncing Earthdata token to the LAADS server. If your Earthdata token is not expired (it expires every 90 days, so check expiration date of your token on Generate Token page) you should not get 401 error. Try using the wget command-line utility by running the command below us...