[mkgmap-dev] Error in TreReader? Are our limits too small?From Gerd Petermann GPetermann_muenchen at hotmail.com on Fri Jan 28 10:14:15 GMT 2022
Hi programmers! Our code in TreFileReader differs from that in GPXSee treFile.cpp. Our code only reads 24 bits into field lastRgnOffset, but GPXSee reads up to 28 bits as offset. We assume 1 byte for the flags and 3 bytes for the offset. GPXSee assumes 4 bits for the flags and 28 bit for the offset. Since our flags field has values > 0x10 I think the code in GPXSee looks better. Not sure what that means. Maybe we can write larger tiles? Is MapSplitter.MAX_RGN_OFFSET_SIZE related to this? Gerd -------------- next part -------------- A non-text attachment was scrubbed... Name: TreReader.patch Type: application/octet-stream Size: 2348 bytes Desc: TreReader.patch URL: <https://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20220128/10c2f5a7/attachment.obj>
- Previous message: [mkgmap-dev] Commit r4882: improve comment reg. MAX_DIVISION_SIZE
- Next message: [mkgmap-dev] Error in TreReader? Are our limits too small?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list