An optional new switch to the console bufr_decoder that allows for delimitation of the output message such as [-delimiter ]
ex. bufr_decoder ... .... -delimiter ^
The resulting output using a delimiter would look as follows:
...
...
Section 4
length : 139
Section 5
length : 4
Subset 1 : 30 descriptors
311001
301051
001006^VALUE=" "^CCITT IA5^AIRCRAFT FLIGHT NUMBER
002061^VALUE=0^CODE TABLE^AIRCRAFT NAVIGATIONAL SYSTEM
...
the ordering of the descriptor, value, unit, description is not important.
Currently the output of bufr_decoder is only good for visual appeal but proves difficult for parsing.
001204 IDENTIFICATIF DE STATION, OBSERV. HORAIRE CCITT IA5 XFA
001019 LONG STATION OR SITE NAME CCITT IA5 FANNY ISLAND
060001 TABLE ID (SENSOR ARRAY IDENTIFIER) NUMERIC 160
006002 LONGITUDE (COARSE ACCURACY) DEGREE -125.98
Writing a direct C intermediary program that uses a chosen delimiter using the libec api is the way we get around this but it is one extra piece of dependency to C as opposed to one single run using bufr_decoder.
Moved from https://blueprints.launchpad.net/libecbufr/+spec/delimiter-to-console-decoder
Delimiter Switch to Console Decoder
Registered by Martin Petras on 2010-11-16
An optional new switch to the console bufr_decoder that allows for delimitation of the output message such as [-delimiter]
ex. bufr_decoder ... .... -delimiter ^
The resulting output using a delimiter would look as follows: ... ...
Section 4
length : 139
Section 5
length : 4
Subset 1 : 30 descriptors
311001
301051
001006^VALUE=" "^CCITT IA5^AIRCRAFT FLIGHT NUMBER 002061^VALUE=0^CODE TABLE^AIRCRAFT NAVIGATIONAL SYSTEM ...
the ordering of the descriptor, value, unit, description is not important.
Currently the output of bufr_decoder is only good for visual appeal but proves difficult for parsing. 001204 IDENTIFICATIF DE STATION, OBSERV. HORAIRE CCITT IA5 XFA 001019 LONG STATION OR SITE NAME CCITT IA5 FANNY ISLAND 060001 TABLE ID (SENSOR ARRAY IDENTIFIER) NUMERIC 160 006002 LONGITUDE (COARSE ACCURACY) DEGREE -125.98
Writing a direct C intermediary program that uses a chosen delimiter using the libec api is the way we get around this but it is one extra piece of dependency to C as opposed to one single run using bufr_decoder.
Blueprint information
Status: Not started
Approver: None
Priority: Undefined
Drafter: None
Direction: Needs approval
Assignee: None
Definition: New
Series goal: None
Implementation: Unknown
Milestone target: None
Started by
Completed by