Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handling requests for exceeding number of items #46

Closed
JaroCamphuijsen opened this issue Jul 16, 2019 · 3 comments
Closed

Handling requests for exceeding number of items #46

JaroCamphuijsen opened this issue Jul 16, 2019 · 3 comments
Labels
enhancement New feature or request

Comments

@JaroCamphuijsen
Copy link
Collaborator

Implement a check on number of items to be downloaded, before sending the request and potentially split the request in multiple smaller requests, or give user a message.


Example:
Upon sending a reasonable request:
era5cli hourly --variable u_component_of_wind --startyear 2008 --ensemble --statistics

cds raises the following exception:
Exception: the request you have submitted is not valid. Request too large. Requesting 975024 items, limit is 120000.

@JaroCamphuijsen JaroCamphuijsen added the enhancement New feature or request label Jul 16, 2019
@JaroCamphuijsen JaroCamphuijsen changed the title Handling exceeding number of items requests Handling requests with exceeding number of items Jul 16, 2019
@JaroCamphuijsen JaroCamphuijsen changed the title Handling requests with exceeding number of items Handling requests for exceeding number of items Jul 16, 2019
@SarahAldt
Copy link
Contributor

@BSchilperoort
Copy link
Member

@SarahAlidoost it seems like we should also split up requests by month for ensemble downloads, just like we are planning to do for era5land data. That would allow us to resolve this issue.

Related to #133

@BSchilperoort
Copy link
Member

Fixed in #139

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants