Re: [mkgmap-dev] Patch: use all 4 bytes of POIGlobalFlags in LBL Header

2022-02-12 Thread Gerd Petermann
HI Ticker, I think new Garmin maps have a lot more bits set, but GPXSee doesn't even read the basic 8 bits, so I can leave the code as is for now. Gerd Von: mkgmap-dev im Auftrag von Ticker Berkin Gesendet: Samstag, 12. Februar 2022 17:54 An: Developm

Re: [mkgmap-dev] Patch: use all 4 bytes of POIGlobalFlags in LBL Header

2022-02-12 Thread Ticker Berkin
Hi Gerd An interpretation of the comment is that POIGlobalFlags data is 16 bits, and, if bit 9 is set, the next byte is the number of extra word of POI information immediately following. The data then continues with 2 bytes unknown, POITypeIndex Position/Size/ItemSize... As mkgmap always writes z

Re: [mkgmap-dev] Patch: use all 4 bytes of POIGlobalFlags in LBL Header

2022-02-12 Thread Gerd Petermann
Hi Ticker, I don't understand. The number of bytes doesn't change, the patch just places more information in the flags field instead of ignoring them. I am not aware of any code in mkgmap that reads or fills those bits,yet. Gerd Von: mkgmap-dev im Auftra

Re: [mkgmap-dev] Patch: use all 4 bytes of POIGlobalFlags in LBL Header

2022-02-12 Thread Ticker Berkin
Hi Gerd Reading it more carefully, probably the basic flag set is 16 bits, with 0x0100 indicating more bytes to read/write Ticker On Sat, 2022-02-12 at 12:36 +, Ticker Berkin wrote: > Hi Gerd > > Although the comment might have inaccuracies and be ambiguous, it > contains useful informatio

Re: [mkgmap-dev] Patch: use all 4 bytes of POIGlobalFlags in LBL Header

2022-02-12 Thread Ticker Berkin
Hi Gerd Although the comment might have inaccuracies and be ambiguous, it contains useful information about how the extra flags for POI might be represented, which could be different from just reading 4 bytes. One way of interpret it is if (first byte & 0x80), then read/write extra bytes; the 3