Add description of the EUMETSAT to bufr mapping to the ROPP documentation

[Ian Culverwell]

Axel von Engeln (EUM) writes:

Hi Ian,

one more issue I just thought of, can you add a story/remind me 
later to eventually take our description of the EUMETSAT to bufr 
mapping also into your ROPP documentation? I have the table already 
in LaTeX, so should be straight forward to implement it on your 
side (mostly copy/paste). We are just waiting for a more formal 
document delivery in September, but then you could start to 
integrate it to fully document the eum2ropp tool.

Cheers,

      Axel

No problem - Sec 2.6.7 of the ROPP IO User Guide looks like the best place.

[Ian Culverwell]

BUFR_netCDF_Mapping.tex

[Ian Culverwell]

Axel's suggested file attached. He says:

Hi Ian,

this is actually the eum2bufr mapping used for our new 
netCDF4 data, it does though have some L1/L5 
information in it since it was also written for EPS-SG. 
But you can remove that if you want, or just keep it in 
to make it more generic.

It is probably best if you can use the table mostly 
unmodified, in order to make updates that we will 
provide in the future easier to accommodate into the 
ROPP doc.

Fairy nuff.

[Ian Culverwell]

B_BUFR_netCDF_Mapping.tex

[Ian Culverwell]

Checked with AvE. Latest version attached.

[Ian Culverwell]

Chris Marquardt sent me the attached latex file 11_bufr.tex and, very usefully, EUMETSAT RO level 1 product format specification. His comments:

The tables are mostly fine; we changed the source of 
the closed/open loop data only bit to the variable 
/quality/ol_data_used (Stig suggested, and rightly so, 
that he doesn't care much about what's available in 
theory, but rather about what has been used); and in 
our official format specification (attached), we 
changed the wording in a few remarks in the second 
table.

I had already picked up the change /quality/ol_data_available to /quality/ol_data_used.

In fact I only spotted one inconsistency between the document and the ROPP source code (contained within ropp_io/ropp/ropp_io_read_ncdf_get.f90): the document says octets 21&22 are defined by /data/transmitter/satellite_prn, but in fact they use the /data/transmitter/satellite/satellite_prn netCDF attribute.

The ROPP IO User Guide has been updated with these changes (and the above typo) at r5139. Closing the ticket as fixed.

[Ian Culverwell]

Radio Occultation Level 1 Product Format Specification.pdf

[Ian Culverwell]

11_bufr.tex