CMIP7 Data Request: v1.2.2.4 now available

This is the latest version of the Data Request.

On this Page

We are pleased to release v1.2.2.4 of the CMIP7 Data Request.

The key components of the Data Request that you can access from today are:

If you would like more information about the new structure of the Data Request for CMIP7, or some background information about how the Data Request was developed, you can find this at the bottom of this page.

This release would not have been possible without the immense amount of work contributed by the Thematic Author Teams, the Data Request Task Team, and the Controlled Vocabularies Task Team.

The Data Request content

The CMIP7 Data Request specifies data requirements for CMIP7 experiments with a list of variables, with associated metadata, and mappings between scientific opportunities, groups of variables and groups of experiments. In earlier versions of the Data Request, the list of experiments was limited to the CMIP7 Assessment Fast Track. The latest version of the CMIP7 Data Request for the Assessment Fast Track (v1.2.2.4) includes some additional experiments outside of the Fast Track.

The Data Request contains a subset of the variables which were requested in CMIP6, alongside a suite of new and modified variables. We have outlined some of the updates users can expect from both the CMIP6 Data Request and earlier version of the CMIP7 Request.

CMIP7 MIP/CMOR tables

The CMIP7 MIP tables (also known as CMOR tables) have been generated using the CMIP7 data request content and are available for modelling centres to start testing.

Providing feedback

We would like to thank the numerous thematic author team members, MIP contacts, and modelling centre representatives who have provided feedback on the Data Request at any point during the process.

Despite the incredible amount of work and review the Data Request has undergone, there will inevitably be mistakes remaining in the request. If you have spotted an error or problem in the Data Request, please create an issue in our Harmonised Public Consultation GitHub, where we will do our best to respond to and address your issue.

What has changed since the last version?

A website view of the Data Request, along with easy-to-read information on what has changed between each Data Request release is available here. This shows users both what has changed with the request (i.e. which variables are requested from which Opportunities/Experiment Groups) and what has changed in the definitions of variables.

We would like to thank Martin Schupfner (DKRZ) for setting up those webpage views.

Content notes

New content notes for v1.2.2.4

Changes to variables

New C4MIP variables atmos.fco2all.tavg-u-hxy-u.mon.glb and land.netAtmosLandCO2Flux.tavg-u-hxy-lnd.mon.glb (Amon.fco2all, Emon.netAtmosLandCO2Flux) were introduced, both requested only for emission-driven coupled carbon climate model runs.
land.tas.tavg-h2m-hxy-u.1hr.[glb,30S-90s] (E1hr.tas, E1hr.tasSouth30) were replaced with atmos.tas.tavg-h2m-hxy-u.1hr.[glb,30S-90S] (AERhr.tas, AERhr.tasSouth30) because they are equivalent except for their primary realm, and this duplication was confusing and also produces a DRS conflict since the dir path doesn’t contain the realm.
The olevel dimension (ocean model levels) was removed from the three global average variables Omon.bigthetaoga, Omon.thetaoga, Omon.soga since it had been erroneously included. This changes their CMIP7 names to (respectively) ocean.bigthetao.tavg-u-hm-sea.mon.glb, ocean.thetao.tavg-u-hm-sea.mon.glb, ocean.so.tavg-u-hm-sea.mon.glb.
CF standard name of ocean.sfacrossline.tavg-u-ht-sea.mon.glb (Omon.sfacrossline) was corrected to ocean_salt_mass_transport_across_line.
The frequency of o3ref_tclm-al-hxy-u was corrected from fx to mon since it is a monthly climatological annual cycle.
The cell methods of land.rsus.tavg-u-hxy-lnd.mon.glb (Emon.rsus) was corrected from “area: mean where land” to “area: time: mean where land” (i.e., time averaging should have been indicated in the cell methods, as it already is in the dimensions and branding suffix).
Processing note of some variables was amended to clarify that global versions of variables that have been requested regionally can be published if that is data producer’s preference. E.g., if a variable is requested at 30S-90S and data producers prefer to produce the global version, that’s perfectly fine.

Changes to coordinates

Description of the site dimension was changed without changing its meaning (the format of the previous description caused a CMOR error).
The positive attribute for the osurf coordinate was set to blank since it doesn’t have an associated direction.

Changes to Opportunities and Experiments

Experiments list for CORDEX DR Opportunities were corrected.
piControl was added to the Dynamical Downscaling Opportunity (and updating text) based on ISIMIP request (confirmed by CORDEX).
Typos in experiment length were corrected to make the DR experiments table consistent with the CMIP7 CVs.
abrupt-0p5CO2 experiment ID was updated to abrupt-0p5xCO2 to match CMIP7 CVs.

Content notes from previous releases

AerChemMIP variables on height2m

Prior to v1.2.2.2, a number of AerChemMIP variables were on the vertical coordinate ‘lowerModelLayer’. It was later decided that these variables are more suitably defined with the vertical coordinate ‘height2m’. This coordinate was updated from v1.2.2.2 onwards; however, the long name and descriptions were not updated. These have now been fixed and are consistent with the technical definition.

Coordinate changes

Similarly there has been a lot of discussion around the best way to define variables on the ocean surface. To resolve this, a new coordinate has been created and replaces the use of ‘depth0m’ in releases prior to v1.2.2.3. The new coordinate, ‘osurf’, has now been created and attached to 46 ocean biogeochemistry variables.

Additionally, height2m coordinate has been added to LImon.tasIs, E1hr.tas, E1hr.tasSouth30.

Cell measure name updates

We have changed the cell measures ‘::MODEL’ and ‘::OPT’ back to ‘–MODEL’ and ‘–OPT’, as they were in CMIP6. This is due to CMOR understanding the ‘–‘ versions, while CMOR will produce an error for the ‘::’ versions.

Cell measures

Cell measures will not be variable attributes in the CMOR tables, which will be based on branded variables that are grouped by modelling realm (branded variables do not specify a variable’s grid). Grid information, along with frequency and region, is specified by the data request for each requested variable. This grid information includes the cell_measures, and modelling groups can choose to specify the cell measures in their output netcdf files (but it will not propagate automatically into the files from the CMOR tables).

New variables for v1.2.2

The total number of variables in the v1.2.2 was slightly higher than in v1.2.1. This is due to a slight change in structure in preparation for the Variable Register the CVs Task Team is preparing. This now requires each variable in the Data Request to have its region specified. There were approximately 130 variables which were requested both globally and for the region south of 30 degrees. These variables now appear in the request separately.

If modellers are already providing the global version of these regional variables, there is no requirement to also produce the regional version.

Additionally, there were 6 variables identified as duplicates of each other. These duplicates have been removed.

CMIP7 Compound Names and Branded variable names

A new way of uniquely identifying variables has been proposed for CMIP7 onwards. This is known as ‘branded variable names’. The “branded variable” name is constructed from two components described below: a root name associated with the standard name defining the property, and a branding suffix, which indicates how the property should be sampled spatially and temporally. The branding suffix is composed from four components, referencing the variable’s temporal sampling, vertical sampling, horizontal sampling and area type.

A full documentation of the branding algorithm will be submitted as a paper soon. In the meantime, the WIP have compiled some guidance here.

The branding variable algorithm development has been led by Karl Taylor (PCMDI/LLNL) and was adopted by the WIP in a formal decision on 14th January 2025.

Sea-ice variables on atmosphere and ocean grids

There are a small number of ocean variables requested on either the atmospheric grid (i.e. the cell methods are areacella) or both the ocean and atmospheric grid (i.e. there are two versions of the variable, one with cell methods areacella and one with areacello). The Oceans and Sea-ice Theme have confirmed this is an intentional decision, required to compute boundary fluxes.

Experiments outside of the CMIP7 Assessment Fast Track

A small number of experiments outside the CMIP7 Assessment Fast Track have been added to allow users to request data on the Fast Track timeline. These include experiments from TipMIP, FireMIP, and HighResMIP2, among others.

Changes in CMIP6 variables

While most of the variables from CMIP6 remain unchanged, there are a few which have been edited. We have automatically flagged the variables which might have had one of the following fields edited since CMIP6.

Table/physical parameter (i.e. has the variable’s compound name changed)
Cell methods
Cell measures
Dimensions
Units
Positive direction

The updates to these fields have mostly been made to fix errors in CMIP6 variables, to add extra detail in metadata, and sometimes to adjust variable definitions or sampling. Variables with changes have been flagged in the ‘Flag – variable change since CMIP6’ field. Where a variable is flagged, we recommend comparing to the CMIP6 CMOR tables to clarify the differences; however, you will find some information in the Processing Note which will guide you towards the differences.

Making pressure levels more uniform

To make the Data Request easier to implement, the Atmospheric Author Team have proposed to move all daily and monthly data requested on the CMIP6 pressure levels plev8 and plev7h onto 19 pressure levels (plev19 from CMIP6). This was implemented from v1.0.

Sub-daily data requested from the downscaling and emulator communities are still requested on a smaller number of pressure levels, due to the potential data volume bloat a move to 19 levels could cause. Data on plev3, plev7c, and plev27 remain unchanged.

Accessing the Data Request

The Online Database

The full Data Request can be explored online at https://bit.ly/CMIP7-DReq-v1_2_2_4.

Many users will not have used Airtable, or navigated through the CMIP Data Request database before. While it may seem complex at first, Airtable is an extremely powerful tool which makes viewing complex data structures much more simple when you know how to use it. Therefore we encourage users to take some time getting used to the platform in order to make navigation easier for yourself in the future.

We have created some guides to help you navigate and use the CMIP7 Data Request database. Access the Airtable guides at https://bit.ly/CMIP7-DReq-guidance.

Access the CMIP7 Data Request Airtable

Access the Airtable guides

The GitHub Software Package

The Data Request Task Team’s Technical Implementation Subgroup (DR-TISG) worked to create Python code to allow users to interact with the CMIP7 Data Request. It will provide an API and scripts that can produce lists of the variables requested for each CMIP7 experiment, information about the requested variables, and in general will support different ways of querying and utilising the information in the data request.

Access the CMIP7 Data Request Software repo

Flat list of the variables

The new structure of the Data Request is centred around Opportunities, which allows for important description of, and justification for, inclusion of output variables in the Data Request. Additionally, the database structure of the Data Request allows for improved consistency of technical metadata across the many variables in CMIP. However, we appreciate that many Data Request users find a flat list of the variables useful. This flat list is available in two ways:

In the Variables tab of the online Airtable database. This can be exported to CSV format by clicking the MASTER button, then selecting ‘Export to CSV’.
In the GitHub, a JSON export of variable metadata from the Airtable database will be available shortly via the GitHub Software repo. There are two files: in one file variables are indexed by CMIP6-era compound name (e.g., “Amon.tas”) and in the other by CMIP7-era compound name (e.g., “atmos.tas.tavg-h2m-hxy-u.mon.GLB”). The actual metadata for each variable (dimensions, standard name, etc) is identical between the two files.

The new CMIP7 Data Request structure and more background information

The Data Request Task Team have developed an activity that works with community representatives to devise a controlled list of high priority variables that facilitate the majority of user needs. They proposed the following structure of the next Data Request to the CMIP Panel and WCRP-ESMO Infrastructure Panel (WIP). The Panel and WIP both approved the structure.

The Data Request includes variable definitions and the mapping of variables against the justification for the request expressed in terms of the opportunities that the data will generate. This will take the form of a controlled list of high priority variables that serve both the majority of user needs and create a harmonised set of data requests which balance scientific demand for data against modelling centre and infrastructure capacity.

The new CMIP7 Data Request Structure, showing how Experiment Groups and Variable Groups are linked to Opportunities.

The thematic author teams process

Five thematic author teams have been set up to develop the controlled list of high priority variables through through an IPO-supported and Data Request Task Team coordinated paper writing process.

An open call was conducted for authors and reviewers for the thematic papers:

Impacts & adaptation (call closed on 30 November)
Ocean & sea-ice (call closed on 01 March 2024)
Atmosphere (call closed on 08 March 2024)
Earth system (call closed on 08 March 2024)
Land & land-ice (call closed on 08 March 2024)

Appointed authors can be viewed here. The Author teams will be running open meetings and other engagement initiatives with modelling centres during this process.

Variable selection

Author teams as well as the wider CMIP community have been asked to define:

What data is requested, including CF metadata,
Why it is needed and why it is a priority,
Who will make use of it
How it will be used.

Alongside discussing individual variables, the following have been asked to define:

Experiment groups: non-exclusive grouping of experiments (e.g. ‘Fast Track’, ‘DECK’, ‘Scenarios’ etc.)
Variable groups: non-exclusive grouping of variables (e.g. monthly time slices of the baseline variables).
Opportunities: intended use-case/justification for one or multiple variable groups. Opportunities are also linked to relevant experiment groups.

Creating opportunities

Identifying opportunities helps to provide a structure to map variables against requirements. Each opportunity description conveys why this combination of variables and experiments is important and how variables and experiments contribute to impact.

Each opportunity includes:

A high-level description of the science and/or societal use and impact
A time slice to specify a block of years for which data is needed.
Experiments and variables that link to the opportunity. Some experiments and variables will be linked to more than one opportunity.

v1.0 launch event

The Data Request Task Team held a virtual launch event following the Data Request v1.0 release. The event was aimed at MIPs and Modelling Centres, though anyone from the CMIP Community was invited to register.

View the slides and recordings for the launch event here.

v1.2 launch event

The Data Request Task Team held a second virtual launch event following the Data Request v1.2 release. The event was aimed at MIPs and Modelling Centres, though anyone from the CMIP Community was invited to register.

During the session, the Task Team presented an overview of the request, including descriptions of the changes in structure since CMIP6, an overview of the information and tools available to you, and an introduction to the CMIP7 Data Request software package.