Versions Compared

Key

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

...

Does not fail when the message has wrong length

...

Version.

...

Input file offset in bytes. Processing of the input file will start from "offset".

bufr_dump examples

  1. To dump BUFR messages into a flat JSON format.

    Code Block
    > bufr_dump -jf ../data/bufr/aaen_55.bufr
    


  2. To dump BUFR messages into a structured JSON format. Note: This is the default if you omit the -j option

    Code Block
    > bufr_dump -js ../data/bufr/aaen_55.bufr
    


  3. To dump a Fortran program with instructions to create (encode) the input message.

    Code Block
    > bufr_dump -Efortran ../data/bufr/aaen_55.bufr > encode.aaen_55.f90
    
    Now compile and run 'encode.aaen_55.f90'. This will create a new BUFR file called 'outfile.bufr'. Check this is the the same as the input.
    Code Block
    > bufr_compare ../data/bufr/aaen_55.bufr outfile.bufr
    


  4. To dump a Python program with instructions to decode the input message.

    Code Block
    > bufr_dump -Dpython ../data/bufr/aaen_55.bufr > decode.aaen_55.py
    
    Examine the generated Python script 'decode.aaen_55.py'. You will see how to access each of the BUFR keys


  5. To dump in a WMO documentation style with hexadecimal octet values (-H).

    Code Block
    > bufr_dump -OH ../data/bufr/syno_1.bufr
    


  6. To add key type information (-t).

    Code Block
    > bufr_dump -OtH ../data/bufr/syno_1.bufr