For a large number of datasets (mostly from Mercator Ocean), the provided filename starts with a portion of a query string:
eg: &service=SST_GLO_SST_L4_REP_OBSERVATIONS_010_011-TDS...
In this case, the file name should be retrieved from the Location header of the redirect response.
In the example above, the file name is METOFFICE-GLO-SST-L4-REP-OBS-SST_1638355890887.nc
This mechanism is reusable for other cases, but it is not always safe - namely not for Cryosat or other ESA datasets.
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
Germano Guerrini seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it.
For a large number of datasets (mostly from Mercator Ocean), the provided filename starts with a portion of a query string: eg: &service=SST_GLO_SST_L4_REP_OBSERVATIONS_010_011-TDS...
In this case, the file name should be retrieved from the
Location
header of the redirect response. In the example above, the file name is METOFFICE-GLO-SST-L4-REP-OBS-SST_1638355890887.nc This mechanism is reusable for other cases, but it is not always safe - namely not for Cryosat or other ESA datasets.