Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Page info
infoTypeModified date
prefixLast modified on
typeFlat

Note
iconfalse
titleCDS-Beta QUICK GUIDE
  • Create a new CDS-Beta account and accept CDS-Beta Terms & Conditions at https://cds-beta.climate.copernicus.eu/
  • Accept the licences of the product you are interested in (go to the Download form of the product of interest).
  • For API access:
  • Update API credentials and end point (eg. in your .cdsapirc file) as shown, after logging on here (Note that new .cdsapirc file should only contain a URL and a key field - there is NO UID field anymore)
  • Upgrade your CDS API (i.e pip install --upgrade cdsapi). Please make sure you are using a supported version of Python i.e. 3.8 and above
  • New API is designed to be backward compatible which means that once your .cdsapirc is updated and your CDS API package upgraded, your API


    Warning

    From September 26, 2024, the legacy CDS and legacy ADS are decommissioned and no longer accessible.

    CDS-Beta and ADS-Beta have officially become the new CDS and the new ADS.

    Please refer to our announcements for further details:

    Note
    iconfalse
    titleCDS QUICK GUIDE for CDS legacy users who had not yet created an account on CDS-Beta


    • Create an account on new CDS and accept CDS-Beta Terms & Conditions at https://cds.climate.copernicus.eu/
    • Accept the licences of the product you are interested in (go to the Download form of the product of interest).
    • For API access:
      • Update API credentials and end point (eg. in your .cdsapirc file) as shown, after logging on here (Note that new .cdsapirc file should only contain a URL and a key field - there is NO UID field anymore)
      • Upgrade your CDS API (i.e pip install --upgrade cdsapi). Please make sure you are using a supported version of Python i.e. 3.8 and above
      • New API is designed to be backward compatible which means that once your .cdsapirc is updated and your CDS API package upgraded, your API script may run successfully immediately, downloading data from new CDS
    -Beta
      • . There are a few datasets however for which API syntax may have changed - please check the warning on the catalogue page of the affected datasets (e.g. E-OBS). 
      • Run a small API test request. 
    Note
    iconfalse
    titleADS QUICK GUIDE for ADS legacy users who had not yet created an account on ADS-Beta


    • Create an account on new ADS

    More details available (e.g. CDS Toolbox and Good-to-know sections below)

    Hide content

    Split this section in 2 blocks to have QUICK CDS-Beta on one side and QUICK ADS-Beta on the other

    Create a new ADS-Beta account
    -beta
    • .atmosphere.copernicus.eu/
    • Accept the licences of the product you are interested in (go to the Download form of the product of interest).
    • For API access:
      • Update API credentials and end point (eg. in your .cdsapirc file) as shown, after logging
    on
      • on here (Note that new .cdsapirc file should only contain a URL and a key field - there is NO UID field anymore)
      • Upgrade your CDS API (i.
    e
      • pip install --upgrade cdsapi). Please make sure you are using a supported version of Python i.e. 3.8 and above.
     
      • New API is designed to be backward compatible which means that once your .cdsapirc is updated and your CDS API package upgraded, your API script may run successfully immediately, downloading data from ADS-Beta.
      
      •  
      • Run a small API test request. 
    More details available (e.g. Good-to-know sections below)


    Table of Contents
    maxLevel3

    Introduction 

    hide


    A new Climate Data Store (CDS) and a new Atmosphere Data Store (ADS) powered by a new state-of-the-art infrastructure, referred to as the Common Data Store (CDS) Engine are now open!

    CDS: https://cds

    -beta

    .climate.copernicus.eu/

    and

             and         ADS: https://

    ads-beta.atmosphere

    atmosphere.copernicus.eu/

    All layers of the CDS an ADS infrastructure are being modernised: the front-end web interface, the back-end software engine and the underlying cloud infrastructure hosting the service and core data repositories. The modernisation of the Climate Data Store is a journey on which we embarked for the users and with the users. Without your support and your collaboration, this transition would simply not be achievable. We thank you all again for your patience during this significant modernisation of our Data Stores and eagerly await for your constructive feedback via our Support Portal!

    Please watch our User Forum for further announcements!

    A new Climate Data Store (CDS) powered by a new state-of-the-art infrastructure, referred to as the Common Data Store (CDS) Engine is now open!

    https://cds-beta.climate.copernicus.eu/

    All layers of the CDS an ADS infrastructure are being modernised: the front-end web interface, the back-end software engine and the underlying cloud infrastructure hosting the service and core data repositories. The modernisation of the Climate Data Store is a journey on which we embarked for the users and with the users. Without your support and your collaboration, this transition would simply not be achievable. We thank you all again for your patience during this significant modernisation of our Data Stores and eagerly await for your constructive feedback via our Support Portal!

    A new Atmosphere Data Store (ADS) will also soon be launched. Watch our User Forum for further announcements!

    What does this mean in practice to current CDS and ADS users?

    User account:

    ECMWF Single Sign-On (SSO) has been extended to all its platforms including the new CDS and ADS. SSO allows users to have access to multiple applications by signing in with only one account. It also has other important features in regard to simple management, security, ease of use, and seamlessness.

    All users of the new CDS and new ADS will need an ECMWF account. If you already have one, great. If you do not yet have an ECMWF account, please register with ECMWF to get one.

    As a consequence of the single sign-on implementation, your current CDS or ADS login credentials will not work on the new CDS or ADS, regardless of whether you are currently using the CDS or ADS interactively (e.g. over the web interface) or programmatically (using the API service). A new UserID (ECMWF) and API key will be needed.

    Warning

    Your ECMWF account will only allow you to login to the new CDS/ADS, not onto the current CDS/ADS.

    You cannot use your ECMWF account to log in onto the current CDS or current ADS. SSO does not apply to current CDS nor current ADS.

    Your existing CDS account will only work in the current CDS, not in CDS-Beta. You need an ECMWF account to start using CDS-Beta.

    Hide content

    Your ECMWF account will only allow you to login to the new CDS/ADS, not onto the current CDS/ADS.

    You cannot use your ECMWF account to log in onto the current CDS or current ADS. SSO does not apply to current CDS nor current ADS.

    Your existing CDS account will only work in the current CDS, not in CDS-Beta. You need an ECMWF account to start using CDS-Beta.

    Your existing ADS account will only work in the current ADS, not in ADS-Beta. You need an ECMWF account to start using ADS-Beta.

    CDS/ADS Catalogue - data download over web interface: 

    • Before downloading any data from the new CDS or ADS, users will have to accept dataset licences on the new system. Users' profiles including licensing information are not being transferred. In practical terms, this means for example that if you are downloading ERA5 data (web or API) from the current CDS, you will need to login to the new CDS and accept the terms and conditions for ERA5 on the dataset Download form (i.e. Licence to use Copernicus Products). You can check whether you have accepted the dataset licence under Your Profile on CDS-Beta (see Dataset Licences section below the Terms & Conditions)


    What does this mean in practice to legacy CDS and ADS users?

    User account:

    ECMWF Single Sign-On (SSO) has been extended to all its platforms including the new CDS and ADS. SSO allows users to have access to multiple applications by signing in with only one account. It also has other important features in regard to simple management, security, ease of use, and seamlessness.

    All users of the new CDS and new ADS will need an ECMWF account. If you already have one, great. If you do not yet have an ECMWF account, please register with ECMWF to get one.

    As a consequence of the single sign-on implementation, your legacy CDS or ADS login credentials will not work on the new CDS or ADS, regardless of whether you are currently using the CDS or ADS interactively (e.g. over the web interface) or programmatically (using the API service). A new UserID (ECMWF) and API key will be needed.

    Warning

    Your ECMWF account will only allow you to login to the new CDS/ADS, not onto the current CDS/ADS.

    You cannot use your ECMWF account to log in onto the current CDS or current ADS. SSO does not apply to current CDS nor current ADS.

    Your existing CDS account will only work in the current CDS, not in CDS-Beta. You need an ECMWF account to start using CDS-Beta.

    Your existing ADS account will only work in the current ADS, not in ADS-Beta. You need an ECMWF account to start using ADS-Beta.



    CDS/ADS Catalogue - data download over web interface: 

    • Before downloading any data from the new CDS or ADS, users will have to accept dataset licences on the new system. Users' profiles including licensing information are not being transferred. In practical terms, this means for example that if you are downloading ERA5 data (web or API) from the current CDS, you will need to login to the new CDS and accept the terms and conditions for ERA5 on the dataset Download form (i.e. Licence to use Copernicus Products). Similarly for ADS users, if you are downloading EAC4 data (web or API) from the current ADS, you will need to login to the new ADS and accept the terms and conditions for EAC4 (i.e. Licence to use Copernicus Products).
    • You can check whether you have accepted the dataset licence under Your Profile on the New CDS or Your Profile on the new ADS (see Dataset Licences section below the Terms & Conditions).


    API Service - programmatic way of downloading data from all Data Stores (new CDS/new ADS): 

    • A new version of the cdsapi package has been released for programmatically retrieving data from both the new CDS and the new ADS. API users need to upgrade their CDS API (i.e pip install --upgrade cdsapi). Note that the new version of the cdsapi package works on both the current and new CDS/ADS. 
    • Check you are using a supported version of Python i.e. 3.8 and above
    • Login to the new CDS or the new ADS interface using your ECMWF account and follow the instructions online. Make sure you also accept the Terms and Conditions of the datasets you wish to download (this is the dataset licence in addition to the Terms & Conditions for using CDS/ADS - see CDS/ADS Catalogue section above).
    • Before submitting your API request, you will need to update your .cdsapirc file as follows:
      • To retrieve data from new CDS: copy & paste the content of the first black box displayed on the CDS API page (you must be logged in!). Note that new .cdsapirc file should only contain a URL and a key field - there is NO UID field anymore)
      • To retrieve data from new ADS: copy & paste the content of the first black box displayed on the ADS API page (you must be logged in!). Note that new .cdsapirc file should only contain a URL and a key field - there is NO UID field anymore)
    • While the new API is designed to be backward compatible on both new CDS and new ADSwe strongly recommend you use the "Show API request code" tool on the dataset Download Form on new CDS or new ADS to check you are using the correct syntax for your API request. CDS API syntax is changed and some keys or parameter names may have also changed for some new CDS datasets (e.g. E-OBS).



    Legacy CDS Toolbox, Viewers and Applications:

    The Legacy CDS Toolbox has been discontinued from 26 September 2024 and is not migrated to the new CDS. ECMWF Support will not be able to help with supporting users migrating their CDS Toolbox workflows on to another programming language/software. 

    As a consequence of the CDS Toolbox being discontinued, the Viewer tool for the following datasets in the legacy CDS have also been discontinued. 

    Expand
    • Lake water levels from 1992 to present derived from satellite observations
    • Aerosol properties gridded data from 1995 to present derived from satellite observations
    • Ice sheet surface elevation change rate for Greenland and Antarctica from 1992 to present derived from satellite observations
    • Carbon dioxide data from 2002 to present derived from satellite observations
    • Methane data from 2002 to present derived from satellite observations
    • Surface radiation budget from 1979 to present derived from satellite observations
    • Tropospheric humidity profiles averaged monthly and zonally from 2006 to present derived from satellite observations
    • Sea ice edge and type daily gridded data from 1978 to present derived from satellite observations

    New tool packages will be made available to provide software tools for weather and climate workflows that simplify data access, analysis, visualisation and much more. Please watch the user forum for announcements on this topic in the next coming months.

    All Climate Data Store Applications have been retired. The new CDS will have some better performing applications including the Copernicus Interactive Climate Atlas and Climate Pulse. More applications will be published including new versions of some applications in the legacy CDS e.g. ERA5 explorer, Global temperature trend monitor...


    Hide content
    literalfalse

    Quality of Service (QoS) Rules on CDS-beta

    IP address range for new CDS and new ADS

    CDS and ADS Download servers are all still under the same IP range. 

    136.156.136.0/21

    136.156.128.0/21


    Feedback and reporting bugs/issues:

    Please send your feedback and/or report any issue/bug you may have encountered while using the new CDS and ADS by raising an enquiry ticket through our dedicated  Support Portal (ECMWF login required).


    Good to know

    • Some observation datasets are immediately available to download from the new CDS while technical issues with these particular datasets are being addressed.
    • Expand
      • In situ total column ozone and ozone soundings from 1924 to present from the World Ozone and Ultraviolet Radiation Data Centre
      • In situ observations of meteorological variables from the Integrated Global Radiosounding Archive and the Radiosounding Harmonization dataset from 1978 onward
    • Some unsupported datasets in legacy CDS have been deprecated in the new CDS. 
    • Expand
      • Arctic route availability and cost projection derived from climate projections of ice concentration and thickness
      • Ship performance along standard shipping routes derived from reanalysis and seasonal forecasts

      • Water level change indicators for the European coast from 1977 to 2100 derived from climate projections
      • Performance indicators for offshore wind farms in Europe from 1977 to 2100 derived from climate projections
      • Flood risk indicators for European cities from 1989 to 2018

      • Climate suitability indicators for tourism from 1970 to 2100 over Europe derived from climate projections

      • Climate variables for cities in Europe from 2008 to 2017

      • Sea level daily gridded data from satellite observations for the Mediterranean Sea from 1993 to 2020 
      • Sea level daily gridded data from satellite observations for the Black Sea from 1993 to 2020 
    Hide content
    • Before downloading any data from the new CDS or ADS, users will have to accept dataset licences on the new system. Users' profiles including licensing information are not being transferred. In practical terms, this means for example that if you are downloading ERA5 data (web or API) from the current CDS, you will need to login to the new CDS and accept the terms and conditions for ERA5 on the dataset Download form (i.e. Licence to use Copernicus Products). Similarly for ADS users, if you are downloading EAC4 (check if available from ADS-beta!!!) data (web or API) from the current ADS, you will need to login to the new ADS and accept the terms and conditions for EAC4 (i.e. Licence to use Copernicus Products).
    • You can check whether you have accepted the dataset licence under Your Profile on CDS-Beta or Your Profile on ADS-Beta (see Dataset Licences section below the Terms & Conditions).
    • NOT TO BE ADDED YET: when current CDS shuts down, url of cds-beta will become cds again. Bookmarks will need to be updated but for the .cdsapirc file, users won't need to update the URL in a hurry as both cds-beta and cds urls will continue to work for a little longer (to give users time to switch url again). In due time, we will ask users to update the URL in their .cdsapirc until a date is fixed when cds-beta dns is closed.

    API Service - programmatic way of downloading data from all Data Stores (CDS-Beta/ADS-Beta): 

    • A new version of the cdsapi package has been released. API users need to upgrade their CDS API (i.e pip install --upgrade cdsapi). Note that the new version of the cdsapi package works on both the current and new CDS. 
    • Check you are using a supported version of Python i.e. 3.8 and above
    • Login to the CDS-beta interface using your ECMWF account and follow the instructions online. Make sure you also accept the Terms and Conditions of the datasets you wish to download (this is the dataset licence in addition to the Terms & Conditions for using CDS-Beta - see CDS/ADS Catalogue section above).
    • Before submitting your API request, you will need to update your .cdsapirc file as shown in the first black box displayed on the CDS-Beta API page (you must be logged in!). Note that new .cdsapirc file should only contain a URL and a key field - there is NO UID field anymore)
    • While the new API is designed to be backward compatible, we strongly recommend you use the "Show API request code" tool on the dataset Download Form on CDS-beta to check you are using the correct syntax for your API request. CDS API syntax is changed and some keys or parameter names may have also changed for some datasets (e.g. E-OBS).
    Hide content
    • A new version of the cdsapi package has been released for programmatically retrieving data from both CDS-Beta and ADS-Beta. API users need to upgrade their CDS API (i.e pip install --upgrade cdsapi). Note that the new version of the cdsapi package works on both the current and new CDS/ADS. 
    • Check you are using a supported version of Python i.e. 3.8 and above
    • Login to the CDS-beta or ADS-Beta interface using your ECMWF account and follow the instructions online. Make sure you also accept the Terms and Conditions of the datasets you wish to download (this is the dataset licence in addition to the Terms & Conditions for using CDS-Beta/ADS-Beta - see CDS/ADS Catalogue section above).
    • Before submitting your API request, you will need to update your .cdsapirc file as follows:
      • To retrieve data from CDS-Beta: copy & paste the content of the first black box displayed on the CDS-Beta API page (you must be logged in!). Note that new .cdsapirc file should only contain a URL and a key field - there is NO UID field anymore)
      • To retrieve data from ADS-Beta: copy & paste the content of the first black box displayed on the ADS-Beta API page (you must be logged in!). Note that new .cdsapirc file should only contain a URL and a key field - there is NO UID field anymore)
    • While the new API is designed to be backward compatible on both CDS-Beta and ADS-Betawe strongly recommend you use the "Show API request code" tool on the dataset Download Form on CDS-beta or ADS-Beta to check you are using the correct syntax for your API request. CDS API syntax is changed and some keys or parameter names may have also changed for some CDS-Beta datasets (e.g. E-OBS).

    CDS Toolbox, Viewers and Applications:

    The CDS Toolbox will be discontinued and is not migrated to the new CDS. Support will continue to be provided to CDS Toolbox users until the CDS Toolbox is shutdown in September 2024. ECMWF Support will however not be able to help with supporting users migrating their CDS Toolbox workflows on to another programming language/software. 

    As a consequence of the CDS Toolbox being discontinued, the Viewer tool for the following datasets in the CDS will also be discontinued. 

    Expand

    New tool packages will be made available to provide software tools for weather and climate workflows that simplify data access, analysis, visualisation and much more. Please watch the user forum for announcements on this topic in the next coming months.

    All Climate Data Store Applications will also be retired and no longer available when the current Climate Data Store is shutdown in September 2024.

    CDS-Beta will have some better performing applications including the Copernicus Interactive Climate Atlas and Climate Pulse. More applications will be published including new versions of some applications in the legacy CDS e.g. ERA5 explorer, Global temperature trend monitor...
    Hide content
    literalfalse

    Quality of Service (QoS) Rules on CDS-beta

    IP address range for CDS-beta

    CDS Download servers are all still under the same IP range. 

    In the CDS-Beta, IP address ranges are: 

    136.156.136.0/21

    136.156.128.0/21

    Feedback and reporting bugs/issues:

    Please send your feedback and/or report any issue/bug you may have encountered while using the new CDS and ADS by raising an enquiry ticket through our dedicated  Support Portal (ECMWF login required) - make sure you select "Yes" to the question Is this request related to CDS-beta/ADS-beta/CEMS-EW-beta? on the Support Portal request form - this will help the Support team with triaging enquiries more efficiently.

    Good to know

    • A new GRIB to NetCDF convertor has been implemented in both CDS-Beta and ADS-Beta. Further details to be provided soon.
    • For the time being, DOIs of datasets in CDS-Beta will point to the same datasets in current CDS until current CDS is shutdown in September 2024.
    • The current CDS and ADS will be completely shutdown in September 2024. Please migrate to using the new CDS/ADS by September 3rd, 2024. Should users still have API scripts pointing to the retired CDS and ADS systems, these will systematically break and no support will be provided.
    Hide contentThe current CDS and ADS will be completely shutdown in September 2024. Please migrate to using the new CDS/ADS by September 16th, 2024. Should users still have API scripts pointing to the retired CDS and ADS systems, these will systematically break and no support will be provided.



    This document has been produced in the context of the Copernicus Atmosphere Monitoring Service (CAMS) and 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 CAMS and C3S on behalf of the European Union (Delegation Agreement 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.


    Content by Label
    showLabelsfalse
    max5
    spacesCKB
    showSpacefalse
    sortmodified
    reversetrue
    typepage
    cqllabel in ("ecmwf","login","download","cams","c3s") and type = "page" and space = "CKB"
    labelslogin ecmwf