
Hi Minko, I think you found a bug in GPSMapEdit. I've just verified that mkgmap doesn't write the type 0x02 line into NET or NOD, so I assume that GPSMapEdit shows some defaults when it finds a line with type 0x02. I can reproduce the routing errors on the device: 0x02 as road works, without road it fails or the device crashes after a few seconds. So I think it is not a good idea to use 0x02 without road-class/speed. Gerd
Date: Fri, 9 May 2014 15:47:05 +0200 From: ligfietser@online.nl To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Commit: r3259: remove most checks regarding routable/non-routable types.
Hi Gerd
I have noticed types between 0x30-3f are behaving inconsistent, they are not rendered at all in Mapsource/Basecamp, even with a typ file. Routing seems to work but not very reliable.
After some more tests, I notice other remarkable things:
I search for an address on an unclassified road (type 0x06, road_class=3 road_speed=2) This road also has a bicycle route (routable line without road class/speed):
[0x02 resolution 22 continue] gpsmapedit shows road_class=5 road_speed=3 on this line 0x02 (??) and routing errors happen. It always routes to the tile border and then a straight direct line to the address that I search for.
[0x05 resolution 22 continue] gpsmapedit shows road_class=1 road_speed=3, routing error
[0x06 resolution 22 continue] gpsmapedit shows road_class=0 road_speed=3, routing error
[0x10 resolution 22 continue] gpsmapedit shows road_class=0 road_speed=0, routing error
[0x0a resolution 22 continue] gpsmapedit shows road_class=0 road_speed=1, no routing error
[0x29 resolution 22 continue] gpsmapedit dont show road_class nor road_speed, no routing error
Normally I set on type 0x02 road_class=4 road_speed=3, and then the routing is ok.
Any idea why a default value of road_speed and class is assigned altough I don't specify it? Is there a way how to show/print the routing parameters that mkgmap sets on every line?
okay, got it. So maybe we have to separate the "well known" routable types 0x01 -0x13 , 0x1a, 0x1b, 0x16 from others which are also routable?
Gerd
mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev