...
Full documentation of the templates, and other doding coding issues, is at https://community.wmo.int/activity-areas/wis/wis-manuals
...
These are sometimes written with spaces, eg. 3 09 057.
There should be no need to provide reports in multiple templates: if 309057 is provided then it is better to stop sending 309052.
It is important that there should be one report containing all data from the ascent, although there can be earlier partial reports (particularly up to 100 hPa) for timeliness reasons.
Usually these BUFR reports are produced by the software from the radiosonde manufacturers. (Attempts to convert alphanumeric TEMP reports to BUFR are very problematic, and do not provide the higher resolution that WMO GBON will require shorthlyshortly.)
Ideally there should be an overlap of 2-6 months between good quality BUFR made available over the GTS and the withdrawal of TAC reports - with notification of these changes via https://community.wmo.int/news/operational-newsletter .
...
ECMWF provides a BUFR validator which can be used to check the content of BUFR messages.
It also provides EcCodes ecCodes including a customised program for reading/printing BUFR radiosonde reports (bufr_read_tempf, available in Python or Fortran - EcCodes ecCodes needs setting up first).
Example output is provided below. There is an option to print all levels or just standard levels.
...