Hi Gerd,
change the code help me and it works.
Thx
lasemax
--
Sent from: http://gis.19327.n8.nabble.com/Mkgmap-Development-f5324443.html
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Well all the problems about problematic arcs so far came up from a
combination of two things:
a) my style creates two additional ways (bit different
road_class/road_speed based on input) if the following is met: route
relation hiking, bicycle or mtb | ( mtb:scale>0 & mtb:scale<5) |
Hi Henning,
Henning Scholland wrote
> Hi Gerd, I just was thinking about if one road is leaving the roundabout
> at two angles it may count on the Garmin as two roads and will lead to
> 'exit on 3rd exit' instead of 'exit on 2nd exit' for example.
>
> But I haven't gave it a try yet.
>
ah,
Hi Gerd, I just was thinking about if one road is leaving the roundabout at two
angles it may count on the Garmin as two roads and will lead to 'exit on 3rd
exit' instead of 'exit on 2nd exit' for example.
But I haven't gave it a try yet.
Henning
Sent from BlueMail
On 23 Mar 2018, 09:07,
Hi Henning,
Do you think that the patch causes problems? I'd be very surprised. Why do you
think that? Do you have an example where this happens?
The patch only changes the heading values, the expected effect is that the
angles shown in the routing instructions differ by maybe 5° degrees.
Maybe
