[mkgmap-dev] process-exits and Oregon 600
From michael lohr micha.lohr at web.de on Wed Jun 3 17:22:40 BST 2015
Hi Gerd, my 1st assumption was that I set the road_speed too high, and the routing would "jump" overthe 2nd part to the 3rd, 2nd assumption was to use a different line type - changing both things made no difference. Am 03.06.2015 um 17:59 schrieb GerdP: > Hi Michael, > > > michael lohr wrote >> Finally found the reason: my style assigns generic names to unnamed >> roads, so the segments of a motorway_link were named "GENERIC_NAME", >> "EXIT_HINT", "GENERIC_NAME". As soon as a name is present on either the >> 1st or the 3rd segment the Oregon would use this name for routing (btw, >> contrary the my previous posts: the Oregon 450 also behaves like that). >> >> Which brings up this question: why not assign the exit_hint to all 3 >> segments in the first place? > My understanding is that the style should be able to use a different > type (not 0x08 / 0x09) for that small 2nd part, so that Garmin uses > the name of it as a hint. > > Gerd > > > > -- > View this message in context: http://gis.19327.n5.nabble.com/process-exits-and-Oregon-600-tp5845444p5846973.html > Sent from the Mkgmap Development mailing list archive at Nabble.com. > _______________________________________________ > 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/20150603/570d048e/attachment.html>
- Previous message: [mkgmap-dev] process-exits and Oregon 600
- Next message: [mkgmap-dev] process-exits and Oregon 600
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list