id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
231	EUMETSAT BUFR decode problem	Dave Offiler	Dave Offiler	"Axel has built the ECMWF library and built ROPP_prototype against it, but notes a problem:
{{{
thanks, got it to work with the ECMWF bufr library now. 
I can do ropp2bufr with a netCDF file, and also go back to bufr with bufr2ropp. 
BUT: I cannot work with bufr2ropp on our bufr files generated here with our bufrizer. 
The following comes up:

-----------------------------------

$ bufr2ropp gras_20110601_121741_metopa_23950_eps_t_thn.l1_bufr -o ropp.nc

 --------------------------------------------------------
                      ROPP BUFR Decoder
                     14:15UT 01-Jun-2011
 --------------------------------------------------------

INFO (from bufr2ropp):  Reading gras_20110601_121741_metopa_23950_eps_t_thn.l1_bufr
                   ECMWF

      BUFR DECODING SOFTWARE VERSION -  7.2
            1 APRIL  2007.



 Your path for bufr tables is :
 /homespace/engeln/linux/.virtualenvs/ROPP5//data/bufr/
BUFR TABLES TO BE LOADED  B0000000000000013000.TXT,D0000000000000013000.TXT

ERROR (from ConvertBUFRtoROPP):  Wrong vertical signficance, not surface: **********

ERROR (from ConvertBUFRtoROPP):  Wrong vertical signficance, not surface: **********

ERROR (from ConvertBUFRtoROPP):  Wrong vertical signficance, not surface: **********
INFO (from bufr2ropp):       3 new profiles saved in total

-------------------------------

Now Simon tells me we just set this field to missing since we don't have any level 2 data, 
but ROPP seems to expect something in this entry. 
I assume that is a problem then on the ROPP implementation? 
I also attached the bufr file. 
}}}

This is caused by ''ropp2bufr'' hard-coding zero for this element, while EUMETSAT encode 'missing', and ''bufr2ropp'' check only for zero being valid. For EUM-BUFR, 'missing' is interpreted as an invalid value (and overflowing the allowed fields width)

The solution is to skip both the Level 2c data conversion and the error message is vertical significance is 'missing'."	defect	closed	normal	5.0	ropp_io	4.1	fixed	BUFR, EUMESAT, Vertical significance