This repository has been archived by the owner on Aug 9, 2021. It is now read-only.
Access to the descriptor id #10
Comments
|
From fabien.m...@gmail.com on March 04, 2013 10:04:44 of course, it's not a defect but an enhancement request ! |
mraspaud
pushed a commit
that referenced
this issue
Dec 12, 2014
1. Added a convenience property 'num_subsets' to the _BUFRFile.BUFRFile class to indicate the number of subsets in the BUFR message (same as the length of the data array for a single _BUFRFile.BUFRFileEntry) 2. For version 0.2-5, fixed the bug that only the data for the first subset was filled in (the rest was 0) (ticket #9 and #14) 3. Added a 'descriptor' property to _BUFRFile.BUFRFileEntry that contains the descriptor ID (ticket #10) 4. Added a 'cdata' property to _BUFRFile.BUFRFileEntry that contains the character data for entries with unit 'CCITTIA5' (ticket #11). For other entries it is set to None. Currently the code assumes that the character data is limited to 80 chars. For larger data the data is cut off at 80 (..or the code may fail..) but I have not yet bumped into that problem.
# for free
to subscribe to this conversation on GitHub.
Already have an account?
#.
From fabien.m...@gmail.com on March 04, 2013 18:59:50
We are reviewing your python wrapper at Meteo-France.
For the moment, we are very happy with the result. Great job !
But...
There are two missing features (in our use cases).
The first and the most important one is :
"access to the descriptor id from the python API"
(for some of our internal BUFR, the descriptor name is not enough, we want also the descriptor code)
I'm going to open another issue for the second missing feature.
Original issue: http://code.google.com/p/python-bufr/issues/detail?id=10
The text was updated successfully, but these errors were encountered: