Hi ligfietser,
in fact the OFM lite style was the reason that I tried to find a better
solution.
I noticed some strange routing results for this roundabout:
https://www.openstreetmap.org/way/8325782
coming from north (e.g. node 76474542 going south (to node 1601722162).
with setting "OFM racing bike". With other bike types routing looks good.
The style creates several lines for the roundabout (not sure about the order),
two are routable:
0x5 with road_class=1 road_speed=3 toll=no
0xc with road_class=1 road_speed=1 toll=yes
0x10007
0x10105
I think the at least the rule
junction=roundabout {set access=no}
doesn't work as you expect.
Gerd
________________________________________
Von: mkgmap-dev <[email protected]> im Auftrag von lig
fietser <[email protected]>
Gesendet: Sonntag, 12. Februar 2017 12:59:31
An: [email protected]
Betreff: Re: [mkgmap-dev] roundabouts
Gerd,
I have used such approach for my bicycle maps and received quite a few negative
reports with two routable lines on top of each other, especially near and at
roundabouts. A lot of devices will crash (completely shut down) so I'd not
recommend this. In Lambertus' generic new we use an invisible 0x0c line in the
typ file and after the roundabout rules the junctions are made unroutable so we
don't have two routable lines on top of each other.
https://github.com/ligfietser/mkgmap-style-sheets/blob/master/styles/generic%20new/lines
________________________________
Van: mkgmap-dev <[email protected]> namens Gerd Petermann
<[email protected]>
Verzonden: zondag 12 februari 2017 03:39:45
Aan: [email protected]
Onderwerp: [mkgmap-dev] roundabouts
Hi all,
the default style contains these rules for roundabouts:
# Roundabouts
junction=roundabout & (highway=trunk | highway=trunk_link) [0x0c road_class=3
road_speed=2 resolution 18]
junction=roundabout & (highway=primary | highway=primary_link) [0x0c
road_class=3 road_speed=2 resolution 19]
junction=roundabout & (highway=secondary | highway=secondary_link) [0x0c
road_class=2 road_speed=2 resolution 20]
junction=roundabout & (highway=tertiary | highway=tertiary_link) [0x0c
road_class=1 road_speed=1 resolution 21]
junction=roundabout & highway=unclassified [0x0c road_class=1 road_speed=1
resolution 21]
junction=roundabout & highway=* [0x0c road_class=0 road_speed=1 resolution 22]
The wanted effect is that the Garmin device/software produces hints like "enter
roundabout" or "Take the 2nd right onto" ...
The disadvantage is that the roundabout is not rendered.
I replaced all the above rules by
junction=roundabout & highway=* [0x0c road_class=0 road_speed=0 resolution 24
continue]
I tried this with car + bicycle routing and it seems to give the expected
results (routing hints and rendered roads).
Also the --check-roundabouts option doesn't complain.
Alternative might be to keep the distinction of road types for better time
estimation, important point is that
"resoltion 24 continue "
is used.
Comments?
Gerd
_______________________________________________
mkgmap-dev mailing list
[email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
[email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
