[mkgmap-dev] Commit: r3259: remove most checks regarding routable/non-routable types.
From Gerd Petermann gpetermann_muenchen at hotmail.com on Sun May 11 07:54:11 BST 2014
Hi Minko, If I got that right, we should 1) warn when the style file lines uses types 0x02 - 0x09 without road class/speed if -check-styles is used 2) warn if a line is added multiple times, once with type between 0x01 and 0x3f and road class/speed, once with type 0x02 - 0x09 and without road class/speed. I've implemented that with r3267. Gerd > Date: Fri, 9 May 2014 15:47:05 +0200 > From: ligfietser at online.nl > To: mkgmap-dev at 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 at lists.mkgmap.org.uk > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20140511/ba986ea7/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: non-routable-type-v1.patch Type: application/octet-stream Size: 6118 bytes Desc: not available URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20140511/ba986ea7/attachment.obj>
- Previous message: [mkgmap-dev] Commit: r3259: remove most checks regarding routable/non-routable types.
- Next message: [mkgmap-dev] Commit: r3259: remove most checks regarding routable/non-routable types.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list