You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The CDS plugin populates any request that contains a field year with months and days if either don't exist in the request.
This conflicts with the CDS selection limit rules which are based on the number of selections made in the request, for example it is impossible to download data from this catalogue entry: https://cds.climate.copernicus.eu/cdsapp#!/dataset/satellite-albedo?tab=form
This is because there is no day field in the form, so the ek-cds plugin populates it with a list of values 1 to 31. which breaks the selection limits for this dataset, which is 20.
The questions are:
Why are we doing this, are we really adding value by making it possible to submit a partial request and assume we know the rest of the story?
If we do choose to do this, then can we be more methodical about it? e.g. only provide values when we know they are relevant.
What happened?
The CDS plugin populates any request that contains a field
year
withmonths
anddays
if either don't exist in the request.This conflicts with the CDS selection limit rules which are based on the number of selections made in the request, for example it is impossible to download data from this catalogue entry:
https://cds.climate.copernicus.eu/cdsapp#!/dataset/satellite-albedo?tab=form
This is because there is no day field in the form, so the ek-cds plugin populates it with a list of values 1 to 31. which breaks the selection limits for this dataset, which is 20.
The questions are:
What are the steps to reproduce the bug?
ek_alb = ek.data.from_source(
"cds",
'satellite-albedo',
{
'variable': 'albb_bh',
'satellite': 'noaa_7',
'sensor': 'avhrr',
'product_version': 'v2',
'horizontal_resolution': '4km',
'year': '1983',
'month': '01',
'nominal_day': '10',
'format': 'zip',
},
)
Version
latest
Platform (OS and architecture)
MacOS + Linux
Relevant log output
Accompanying data
No response
Organisation
No response
The text was updated successfully, but these errors were encountered: