The C3S NetCDF encoding standards are used for the CERISE analysis data.
Here only the differences from the C3S encoding standards are described.
File Naming Conventions
Output Filename Conventions
- <forecast_type> as it is defined in the controlled vocabulary of the global attributes (analysis type is added);
- <start_date_identifier> is a string "SYYYYMM" that describes the year and the month of the analysis data;
An example of the above convention is:
lfpw_cerise-SystemName-v20210101_analysis_S202303_atmos_12hr_pressure_ta_r01i00p00.nc
File Structure
- Each netCDF4 file contains all the valid times within a single calendar month from a single variable and ensemble member.
Global attributes
In the following table, only the differences from the C3S encoding standards are presented
Attribute Name | Value |
---|---|
forecast_type | "analysis" |
forecast_reference_time | Not present |
Time Coordinates
The table below describes the requirements for the time coordinates.
Type | Coordinate Name | Dimension Names | Long name |
---|---|---|---|
double | reftime | Not present in analysis data | |
double | leadtime | Not present in analysis data | |
double | time | time | "Valid time" |
Data Variables
As described in Annex I (data variables) of the C3S encoding standards.
In the analysis variables, "leadtime" dimension is replaced with "time" dimension.