[mkgmap-dev] Really Serious bug when not using --routeFrom Felix Hartmann extremecarver at googlemail.com on Thu May 27 12:25:23 BST 2010
On 27.05.2010 13:12, Johann Gail wrote: > >> Setting the fourth via gmaptool breaks the routing for routable maps >> even though it should be there for setting maps tranparent/opaque is >> some obscure way different from the general transparent/opaque flag >> > Could this be the exactly the NOD flag? > If modifying this flag breaks routing then this IS a strong hint for > influencing routing. Could it be that in this byte one bit is the flag > for the presence (or absence) of the NOD table? If this bit is > set/cleared then it tells the device that there is no NOD table and > therefore no routing is possible. > > Well I don't know how to clear it. Setting it to 0 doesn't help. It seems to only matter whether it is even or uneven. Setting it even breaks routing, while all uneven values work. Therefore I'm more or less sure, this is not the NOD flag. Also this byte is set for non routable garmin maps to even and uneven values, so no, I don't think this has anything to do with it.
- Previous message: [mkgmap-dev] Really Serious bug when not using --route
- Next message: [mkgmap-dev] Really Serious bug when not using --route
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list