Closed jpolton closed 8 months ago
Picking this one up.
The URL we generate is https://nrt.cmems-du.eu/thredds/dodsC/global-analysis-forecast-phy-001-024.dds
, which (when authenticated) gives us a 200 OK but an otherwise empty response. Interestingly, if I add some nonsense to that URL (i.e. https://nrt.cmems-du.eu/thredds/dodsC/this-is-probably-not-a-real-dataset.dds
) I get the exact same response with a 200 OK. This would likely indicate either an issue with the URL (the asset location/name may have changed) or an issue on Copernicus' end.
@jpolton Do you have a time-frame for when this issue first appeared?
Taking a look at https://data.marine.copernicus.eu/product/GLOBAL_ANALYSISFORECAST_PHY_001_024/services, global-analysis-forecast-phy-001-024
is nowhere to be seen.
If I take the first listed dataset (cmems_mod_glo_phy-cur_anfc_0.083deg_PT6H-i
) and pass that into our client, I get the dataset back as expected.
@jpolton I suppose then the question is which dataset you want to offer as an example? Would it be worth asking Copernicus if they can provide permalinks to CMEMS datasets?
In the meantime, I'll see if we can't catch this error in future and produce a friendlier error message.
Functionality to retrieve COPERNICUS data from OPeNDAP servers is not working as advertised in the COAsT: COPERNICUS docs (though maybe now moved and/or hidden)
I am not sure if the problem is to do with the plumbing their side or our side, or possibly even with the product names changing. I tried a few things but to no avail.