Versions Compared

Old Version 15

changes.mady.by.user Eduardo Penabad

Saved on

compared with

New Version 16

changes.mady.by.user Eduardo Penabad

Saved on

Key

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

...

Surface Fields (not defined at a height level)

  attributes 
name
(CMIP5)		dimensionsstandard_namelong_name
(CMIP5)		unitscoordinatescell_methodsgrid_mappingNOTES
 time,lat,lonair_pressure_at_sea_level Pa "time: point"

C3S: required 
CF: recommended
latitude_longitude 
 time,lat,loncloud_area_fraction 1 "time: point"

C3S: required 
CF: recommended
latitude_longitude 
 time,lat,lonsoil_temperature K "time: point"

C3S: required 
CF: recommended
latitude_longitude 
 time,lat,lonsea_surface_temperature K "time: point"

C3S: required 
CF: recommended
latitude_longitude 
 time,lat,lonsea_ice_temperature K "time: point"

C3S: required 
CF: recommended
latitude_longitude 
 time,lat,lonsea_ice_area_fraction 1 "time: point"

C3S: required 
CF: recommended
latitude_longitude 
 time,depth,lat,lonmass_content_of_water_in_soil_layer kg m-2 "time: point"

C3S: required 
CF: recommended
latitude_longitude 
 time,lat,lonlwe_thickness_of_surface_snow_amount m "time: point"

C3S: required 
CF: recommended
latitude_longitude 
 time,lat,lonsnow_density kg m-3 "time: point"

C3S: required 
CF: recommended
latitude_longitude 
 time,lat,lonlwe_thickness_of_stratiform_precipitation_amount m "time: sum"

C3S: required 
CF: recommended
latitude_longitude 
 time,lat,lonlwe_thickness_of_convective_precipitation_amount m "time: sum"

C3S: required 
CF: recommended
latitude_longitude 
 time,lat,lonlwe_thickness_of_precipitation_amount m "time: sum"

C3S: required 
CF: recommended
latitude_longitude 
 time,lat,lonlwe_thickness_of_snowfall_amount m "time: sum"

C3S: required 
CF: recommended
latitude_longitude 
 time,lat,lonintegral_of_surface_downward_sensible_heat_of_flux_wrt_time W s m-2 "time: sum"

C3S: required 
CF: recommended
latitude_longitude 
 time,lat,lonintegral_of_surface_downward_latent_heat_of_flux_wrt_time W s m-2 "time: sum"

C3S: required 
CF: recommended
latitude_longitude 
 time,lat,lonintegral_of_surface_downwelling_shortwave_flux_in_air_wrt_time W s m-2 "time: sum"

C3S: required 
CF: recommended
latitude_longitude 
 time,lat,lonintegral_of_surface_net_downward_shortwave_flux_wrt_time W s m-2 "time: sum"

C3S: required 
CF: recommended
latitude_longitude 
 time,lat,lonintegral_of_surface_net_downward_longwave_flux_wrt_time W s m-2 "time: sum"

C3S: required 
CF: recommended
latitude_longitude 
 time,lat,lonintegral_of_toa_net_downward_shortwave_flux_wrt_time W s m-2 "time: sum"

C3S: required 
CF: recommended
latitude_longitude 
 time,lat,lonintegral_of_toa_net_downward_longwave_flux_wrt_time W s m-2 "time: sum"

C3S: required 
CF: recommended
latitude_longitude 
 time,lat,lonintegral_of_toa_incoming_shortwave_flux_wrt_time W s m-2 "time: sum"

C3S: required 
CF: recommended
latitude_longitude 
 time,lat,lonintegral_of_surface_downward_eastward_stress_wrt_time Pa s "time: sum"

C3S: required 
CF: recommended
latitude_longitude 
 time,lat,lonintegral_of_surface_downward_northward_stress_wrt_time Pa s "time: sum"

C3S: required 
CF: recommended
latitude_longitude 
 time,lat,lonlwe_thickness_of_watert_evaporation_amount m "time: sum"

C3S: required 
CF: recommended
latitude_longitude 
 time,lat,lonrunoff_amount kg m-2 "time: sum"

C3S: required 
CF: recommended
latitude_longitude 
 time,lat,lonsurface_runoff_amount kg m-2 "time: sum"

C3S: required 
CF: recommended
latitude_longitude 
 time,lat,lonsubsurface_runoff_amount kg m-2 "time: sum"

C3S: required 
CF: recommended
latitude_longitude 

Pressure Level Fields

  attributes 
name
(CMIP5)		dimensionsstandard_namelong_name
(CMIP5)		unitscoordinatescell_methodsgrid_mappingNOTES
 time,plev,lat,lon
air_pressure_at_sea_level
geopotential 
Pa
m2 s-2 "time: point"

C3S: required 
CF: recommended
latitude_longitude 
 

Additional Questions to be addressed

...

Francisco Doblas-Reyes NetCDF4? With or without compression?
Kevin Marsh netCDF4 classic model (with deflate =6 suggested by Pierre-Antoine)

...

Kevin Marsh Pierre-Antoine Bretonniere proposed  follow SPECS convention

...

Kevin Marsh Pierre-Antoine Bretonniere suggested 4GB recommended maximum size

...

Kevin Marsh recommend 4GB Max Size for data files

...

Kevin Marsh DOI likely to be assigned at dataset level

...

Kevin Marsh DOI likely to be assigned at dataset level

...

Kevin Marsh  Antonio S. Cofino Gonzalez suggested follow cmip5 short names

...

Kevin Marsh follow cmip5 short names

...

Coordinate short names to be specified?

...

Kevin Marsh Antonio S. Cofino Gonzalez suggested  follow cmip5 coordinate short names

...

Kevin Marsh follow cmip5 coordinate short names

...

Kevin Marsh yes, but not in the initial convention release

...

Kevin Marsh Not considered in initial release

...

Kevin Marsh Antonio S. Cofino Gonzalez agreed 1 degree grid specified with valid max/min, but actual grid points not specified

...

Kevin Marsh 1 degree grid specified with valid max/min, but actual grid points not specified

...

Kevin Marsh These will be added by C3S, rather than data provider

...

Kevin Marsh These will be added by C3S

...

Kevin Marsh requested via standard name mailing list. Note that this process can take some considerable time.

...

Kevin Marsh requested via standard name mailing list

time,plev,lat,lonair_temperature K "time: point"

C3S: required 
CF: recommended
latitude_longitude 
 time,plev,lat,lonspecific_humidity 1 "time: point"

C3S: required 
CF: recommended
latitude_longitude 
 time,plev,lat,lonatmosphere_relative_vorticity s-1 "time: point"

C3S: required 
CF: recommended
latitude_longitude 
 time,plev,lat,londivergence_of_wind s-1 "time: point"

C3S: required 
CF: recommended
latitude_longitude 
 time,plev,lat,lonx_wind m s-1 "time: point"

C3S: required 
CF: recommended
latitude_longitude 
 time,plev,lat,lony_wind m s-1 "time: point"

C3S: required 
CF: recommended
latitude_longitude

 

Discussion about time coordinates

NOTE: The SPECS approach (2 1D time coordinates) has been chosen for the "providers" convention

 

The encoding of multiple time coordinates requires particular consideration. An explicit example of the structure is given below.

Example of encoding data with multiple time axis informations

  
double forecast_reference_time(forecast_reference_time) ;
       forecast_reference_time:bounds = "forecast_reference_time_bnds" ;
       forecast_reference_time:units = "hours since 1970-01-01 00:00:00" ;
       forecast_reference_time:standard_name = "forecast_reference_time" ;
       forecast_reference_time:calendar = "gregorian" ;
double leadtime(leadtime) ;
       leadtime:bounds = "leadtime_bnds" ;
       leadtime:units = "hours" ; 
       leadtime:standard_name = "forecast_period" ;
       leadtime:calendar = "gregorian" ;
double time(forecast_reference_time,leadtime) ;
       time:axis = "T" ;
       time:bounds = "time_bnds" ;
       time:units = "hours since 1970-01-01 00:00:00" ; 
       time:standard_name = "time" ;
float temp(forecast_reference_time,leadtime,pressure,latitude,longitude);
      temp:units = "K";
      temp:standard_name = "air_temperature";
      temp:coordinates = "time";

Francisco Doblas-Reyes I interpret this as the time coordinates being a hypercube, where there could be missing data; this won't be consistent with the CMIP files; I still find this confusing unless a discussion about what to do with the missing data is undertaken.

Eduardo Penabad: Wouldn't that be solved by clarifying that different variables within the same file could potentially have different time coordinates/dimensions?

Francisco Doblas-Reyes Not sure. If to simplify you assume one variable only and this variable has in one file data for two start dates, one with three forecast time steps and another one with only two, the time dimensions will be forecast_reference_time=2, leadtime=3, but one of the values of temp() will have missing values, unless I haven't understood the model.

...