Skip to content

Decoding of price field partially wrong for VDV tickets #55

Description

@user4223

Price field is decoded from 4 bytes big-endian integer for VDV tickets from 0xDA primary data record. This is working for some tickets due to 0 in the byte before, but when the byte before is != 0, it leads to wrong results for the price.
Solution should be, to decode price from a big-endian 3 byte integer at offset 8.

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions