Hi all, I think I found the flag that has to be set to avoid the crash: The 1st bit at offset 0x3F in TRE must be 1, not 0. The wiki says about the meaning of this one byte field: Flags: 0: detailed map, 1: transparent map, 2: show street before street number, 3: show zip before city, 4-7: ?? When bit 0 is set routing is cancelled (wilpin) Any hints where this flag might cause trouble? Gerd
Hi Gerd, wow, I'm impressed! In my notes I have bit 0 described as "basemap". I don't know where I have found this info or how credible it is. -- Best regards, Andrzej
Hi Gerd
I think I found the flag that has to be set to avoid the crash:
The 1st bit at offset 0x3F in TRE must be 1, not 0.
I've just looked at various maps. It seems that bit is always set in detail maps from Garmin and also cgpsmapper created maps regardless of whether it contains a DEM or not. It is usually not set in a garmin basemap even when it does contain a DEM. Seems that cgpsmapper maps sets it in basemaps too, or at least later versions did. ..Steve
The wiki says about the meaning of this one byte field: Flags: 0: detailed map, 1: transparent map, 2: show street before street number, 3: show zip before city, 4-7: ?? When bit 0 is set routing is cancelled (wilpin)
Any hints where this flag might cause trouble?
Gerd _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Steve, okay, so maybe we should set the bit for all maps which are not overview maps? In r4116 it is set for all maps with DEM, but I see no need to set it for the overview map. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Steve Ratcliffe <steve@parabola.me.uk> Gesendet: Mittwoch, 14. Februar 2018 18:32:08 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] Heureka! Hi Gerd
I think I found the flag that has to be set to avoid the crash:
The 1st bit at offset 0x3F in TRE must be 1, not 0.
I've just looked at various maps. It seems that bit is always set in detail maps from Garmin and also cgpsmapper created maps regardless of whether it contains a DEM or not. It is usually not set in a garmin basemap even when it does contain a DEM. Seems that cgpsmapper maps sets it in basemaps too, or at least later versions did. ..Steve
The wiki says about the meaning of this one byte field: Flags: 0: detailed map, 1: transparent map, 2: show street before street number, 3: show zip before city, 4-7: ?? When bit 0 is set routing is cancelled (wilpin)
Any hints where this flag might cause trouble?
Gerd _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
participants (4)
-
Andrzej Popowski -
Gerd Petermann -
Gerd Petermann
-
Steve Ratcliffe