Closed dcesari closed 2 years ago
I added the test case to the library. With a bit more tracing I see that the BUFR declares 7 bits of associated field, with associated field significance 8.
Associated field significance values are defined in B31021. Value 8 is described as:
0 = Not suspected
1 = Suspected
2 = Reserved
3 = Information not required
I assumed that this implies that the value is never described in more than 4 bits, but perhaps the decoder needs to be changed to consider all bits set to one as missing value, whatever the number of bits is going to be.
With that change, the BUFR decodes correctly, and the rest of the test suite does not break. It is anybody's guess why the generation of that BUFR chose to add 7 bits per value for something that can only go from 0 to 3, but I'm happy to be liberal in what I accept
Thanks, great! I noticed it's an aircraft report on New Delhi airport, so I do not really know who to ask.
@brancomat can we have a new release with this fix?
v3.35 released now
This issue vaguely reminds #48: the attached aircraft report qinfo_overflow.bufr.gz fails with
the only clue is given by
wrep -t
which ends withdoes it mean that 33002 has been resized to 7 bits and the missing value (127) is not recognized?