Versions Compared

Key

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

...

The UERRA data sample format

  • Only the agreed parameters should be included (all which will be produced) and only on the defined levels, with the defined frequency etc.
  • If the data is already in GRIB2 format it is should be encoded as UERRA test data (productionStatusOfProcessedData=9)
  • Each sample dataset should be split by for given day only by 
    • forecasting system type(deterministic/ensemble)
    • forecast type (analysis/forecast)
    and
    • vertical level (pl/ml/hl/sfc/soil)
    • model run(00/06/12/18UTC)
  • Regarding vertical level type for each model run on given day. Please follow exactly the defined groups of parameters etc as defined in the UERRA parameters page.
  • Only the agreed parameters should be included (all which will be produced) and only on the defined levels, with the defined frequency etc.
  • If the data is already in GRIB2 format it is should be encoded as UERRA test data (productionStatusOfProcessedData=9)Follow this naming convention of the sample files:
    <SYTEM TYPE>.<FORECAST TYPE>.<LEVEL TYPE>.<YYYYMMDDRR>.<GRIB ENCODING>
    where
    • SYTEM TYPE = det/ens for deterministic or ensemble system
    • FORECAST TYPE = an/fc
    • LEVEL TYPE = ml/pl/hl/sl/sl for model/pressure/height/surface or soil levels
    • GRIB ENCODING = grib1/grib2 depending on GRIB edition used
    e.g. det.an.sl.1962010106.grib  for surface level analysis parameters (all steps) from deterministic system run on 1.1.1962, 6h.

Conversion/archiving progress report pages

...