Overview

Paolo Patruno Davide Cesari Enrico Zini
There is a newer version of this page. You can find it here.

wreport library and software overview

Definitions

  • low level d/encoding
  • physically-based data model: unique, high-level, physically-based data model (lon, lat, time, level, parameter, etc.)

Provided by wreport

  • C++ Library for encoding-decoding BUFR and CREX messages at low level
  • It includes a simple command line BUFR dumper
  • It has a minimal dependency on external libraries
  • It cannot convert BUFR between different templates
  • It can use tables in standard XML format as distributed by WMO (easy maintenance)

Core library features

  • BUFR table loading and querying.
  • An abstraction for BUFR variables, storing values with the correct number of significant digits (no artifacts introduced by floats or doubles), and with access to metadata (description, measurement unit, significant digits...) for each variable.
  • Unit conversion, transparent unit conversion when working with variables, conversion functions between related code tables.
  • Variables can be annotated using other variables, to store values that reference other values, such as quality control statistics or substituted values.
  • Script to download and acquire the latest BUFR and CREX tables from WMO.

BUFR decoder features

The decoder supports BUFR editions 2, 3 and 4, both uncompressed and compressed.

C operators supported are:

  • 1 change data width
  • 2 change data scale
  • 4 add associated field, limited to 32 bits of associated fields and to associated field significances 1, 2, and 6.
  • 5 character data
  • 6 local descriptor with explicit length
  • 8 override length of character data
  • 22 quality information matched via data present bitmap
  • 23 substituted values matched via data present bitmap
  • 24 first order statistical values matched via data present bitmap

BUFR encoder features

All features supported by the decoder are supported by the encoder, and tested via decode/reencode/decode runs.

The encoder however does not yet support compression of multisubset data sections.

CREX decoder features

The decoder supports CREX edition 1.

B, R and D opcodes are supported. Some C modifiers may be supported, but are untested due to lack of real-world samples.

CREX encoder features

All features supported by the decoder are supported by the encoder, and tested via decode/reencode/decode runs.

Command line tools

wrep: a tool to print the contents of BUFR and CREX messages.

Provided by DB-All.e

It can import observations from various sources into a unique, high-level, physically-based data model (lon, lat, time, level, parameter, etc.) and export them back

  • It uses Wreport library for BUFR and CREX encoding-decoding
  • It has a GUI for quickly navigating into observation datasets
  • It depends on other external libraries
  • It import data from other formats, such as Binary COSMO AOF (ro) and Text with predefined csv structure (rw)
  • It understand BUFR with different templates (e.g. those from MARS at ECMWF)
  • using command line tools can convert from those formats and write BUFR in WMO/GTS template

  • It has a Fortran interface

  • dbatbl: a query tool for BUFR tables

  • dbamsg: a tool to manipulate BFUR and CREX messages.
    • prints the contents of messages.
    • selects messages from a file.
    • convert to and from CSV, either raw messages or their physical interpretation.
    • convert data across different formats and/or message templates.
    • finds differences between message contents.
    • AOF messages can also be processed by most dbamsg functions, but they cannot be written.
  • dbadb
  • fortran API
  • python bindings
  • GNU R
  • provami

Provided by bufr2netcdf

  • ...
    BUFR preprocessor for observation COSMO data ingest.
    It's a tools for decoding BUFR reports and creating input files for COSMO model assimilation.

  • COSMO model requires observations in netcdf format (AOF is considered obsolete)

  • The COSMO netcdf format is the translation of a BUFR structure in netcdf, difficult to write directly from user applications and not following any standard specification
  • The physical interpretation of the data is done into the COSMO model (>14K lines)
  • The natural source of observed data for COSMO model should be BUFR following a predefined template (e.g. WMO reports)
  • This conversion is an almost literal translation of a BUFR into a netcdf data structure
MongoDB Logo MongoDB