Fix discrepancy between EUMETSAT and ROM SAF processing to BUFR

[Ian Culverwell]

Harald Anlauf (DWD) writes:

Dear all,

I've restricted the list of addressees to EUMETSAT and ROMSAF 
because this is only a minor technical issue.

There is inconsistent rounding in the last decimal places between 
the encoding at EUMETSAT and at the ROMSAF in different places.  
This applies to current data (as of today, 2016-07-06, 08:36 UTC).

It would be nice if this could be made consistent, and if wrong 
rounding and/or undesired truncation be identified and resolved.

I've attached what our "in-house" BUFR decoding software actually 
"sees" for a Metop-B sounding.

See the attachment for details, and sorry for the special language 
and spelling used in the description of the keys.  ;-)

Harald

The contents of Harald's tar file are attached.

[Ian Culverwell]

gras_metopb_eum-ppf4.txt

[Ian Culverwell]

gras_metopb_romsaf.txt

[Ian Culverwell]

Most of Harald's differences involve the impact parameter, where it is the ROM SAF that is wrong, and which we have already corrected (#470). The other things are mainly georeferencing quantities (undulation, RoC, latitude, seconds, POD). We could probably fix these if desired.

[Ian Culverwell]

radioocc_gras_metopb_eum.bufr

[Ian Culverwell]

radioocc_gras_metopb_dmi.bufr

[Ian Culverwell]

Harald's BUFR files are attached.

[Ian Culverwell]

Deferring to ROPP10.0, and downgrading priority to 'minor' until we have more resources to throw at ROPP development/maintenance.

[Ian Culverwell]

To be done "whenever" (we have the same resources as EUM or DMI to do this sort of thing).