[mkgmap-dev] highway=track with no road_class and road_speed set breaks routing ## was ## "No roads near target" bug in Schwabmünchen
From Minko ligfietser at online.nl on Sat Apr 6 21:38:23 BST 2013
> franco_bez wrote > > dropping the road_class and road_speed values, the routing is broken > yes, only ways with road_class or road_speed are added as roads. This > may be true. > But why does this break the routing on other roads ? > In the route in Question there is not a single "track" to be routed > on, it's all on "normal" roads. > > Removing the road_class and road_speed from the tracks should just > affect the tracks, shouldn't it ? No, I have experienced that routing breaks on every road that Garmin defines as a routable line (0x01-0x13; 0x1a,0x1b) and that does not have a road_class and road_speed in the style file. Solution when you dont want to make such road not routable: use another non routable line type (for instance an extended line type). Problem is that it will not be searchable anymore (which makes sense, since it is not routable, you can't route to this road)
- Previous message: [mkgmap-dev] highway=track with no road_class and road_speed set breaks routing ## was ## "No roads near target" bug in Schwabmünchen
- Next message: [mkgmap-dev] highway=track with no road_class and road_speed set breaks routing ## was ## "No roads near target" bug in Schwabmünchen
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list