You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
16-bit words are currently printed in varying formats in the JSON output.
"0xABCD": is used for most PI codes
"ABCD": used whenever multiple 16-bit words are concatenated
43981: used for TMC location codes, Program Item Number, ODA message data, in-house data
Additionally, the newly-supported transparent data channels are printed as 8-bit hex words without 0x.
Instead, one format should be chosen for all 16-bit data.
One downside to the decimal format (3) is that information about the word size is lost. Location codes and PINs are supposed to be numbers so they should be OK. But at least ODA message data and in-house data should probably be formatted as hexadecimal. This would be a schema-breaking change.
The text was updated successfully, but these errors were encountered:
16-bit words are currently printed in varying formats in the JSON output.
"0xABCD"
: is used for most PI codes"ABCD"
: used whenever multiple 16-bit words are concatenated43981
: used for TMC location codes, Program Item Number, ODA message data, in-house dataAdditionally, the newly-supported transparent data channels are printed as 8-bit hex words without
0x
.Instead, one format should be chosen for all 16-bit data.
One downside to the decimal format (3) is that information about the word size is lost. Location codes and PINs are supposed to be numbers so they should be OK. But at least ODA message data and in-house data should probably be formatted as hexadecimal. This would be a schema-breaking change.
The text was updated successfully, but these errors were encountered: