Page info | ||||||
---|---|---|---|---|---|---|
|
Note |
---|
Please be aware that some of the content of this page is only relevant for the current CDS system. We welcome your contribution with reporting any errors you may encounter while using CDS-beta so that it may be documented below for the benefit of all users. |
Info | ||||
---|---|---|---|---|
| ||||
|
...
Easy Heading Macro | ||
---|---|---|
|
Hide content |
---|
Major modification in progress for this article - please DO NOT UPDATE THIS PAGE or your edits will get overwritten when the new modified article will be published. Please edit the working copy of this page in the |
Introduction
In a small number of cases, users may experience some issues when requesting data from the CDS API. The most common issues are documented in the "Troubleshooting" section below.
Info |
---|
Please note that CDS API requests are only shown on the CDS "Your Requests" web page while they are running. Once they have completed, they are removed from the list. |
However, as a first step we strongly advise that if you experience any of these issues you first:
...
Please note that a given Error Message can be triggered by an number of reasons. The most common Error Messages are shown below:
Error Message |
connection error |
an internal error occurred processing your request |
no data is available within your requested subset |
the request you have submitted is not valid |
Client has not agreed to the required terms and conditions. |
Invalid 'method': cds.catalogue.retrieve |
Invalid 'method': cds |
Examples of some of the reasons (and solutions) for these errors are given below.
...
- Reduce size: request the data in smaller sections (less than 10GB),
- Reduce size: request individual variables in 1 per request
- Convert locally: request the data in GRIB format and convert the data to netCDF on your local system.
...
Request Failed: Request cancelled by system admin
...
Solution: Create a valid request on the ADS/CDS dataset web form and click "Show API request". Read the relevant documentation.
Request Failed: MARS Connection ("MARS Tunnel") Issue
Symptom: The CDS API request fails as the connection to the MARS archive has issues.
Code Block |
---|
raise exception(call, proc.returncode, output)\nhome.cds.cdsservices.services.mars_constrained.__init__.py.mars.exceptions.MarsException: Suspected MARS tunnel problem\n'}. |
Diagnosis: Some ADS/CDS datasets are stored in the MARS archives. Sometimes the connection between the ADS/CDS and these archives has issues, resulting in failed requests.
Solution: Check for announcements on the Copernicus User Support forum, and the ADS/CDS home pages. Retry you requests after some time later, as the issue may have been resolved.
Data not available: Invalid request for ADS/CDS requests
...
Solution: Use the ADS/CDS dataset web form to check that your requests are valid i.e. that you are using the correct dates, variable names etc.
Info | ||
---|---|---|
| ||
This document has been produced in the context of the Copernicus Climate Change Service (C3S). The activities leading to these results have been contracted by the European Centre for Medium-Range Weather Forecasts, operator of C3S on behalf of the European Union (Delegation agreementAgreement signed on 11/11/2014 and Contribution Agreement signed on 22/07/2021). All information in this document is provided "as is" and no guarantee or warranty is given that the information is fit for any particular purpose. The users thereof use the information at their sole risk and liability. For the avoidance of all doubt , the European Commission and the European Centre for Medium - Range Weather Forecasts have no liability in respect of this document, which is merely representing the author's view. |