Hi
I am satisfied that it is a cache issue. The ways have not been edited
for 3 days and bicycle (graphhopper) which was doing the little zig
zag yesterday is now routing correctly.
I think just wait and let the data catch up.
Tony
Ben, thanks for the suggestions - I'll give them a go.
Ian
The intersection in question is quite new, so I am not surprised that
there are
cache issues as you guys have identified. Each routing engine will ingest
new
OSM data on its own schedule.
One thing that I noticed with the spurious "at the fork, turn right onto
Albany
Hwy" instructions in the original OSMR link
<https://www.openstreetmap.org/directions?engine=fossgis_osrm_car&rout
e=-34.9226%2C117.7915%3B-34.9670%2C117.8239#map=16/-
34.9652/117.8223>,
is the lack of `_link` roads. I would expect the on- and off-ramps to be
tagged
as `highway=trunk_link`. I suspect the routing engines are expecting the
same,
and therefore seeing the Menang Dr slip road
<https://www.openstreetmap.org/way/1077469017> as a legitimate fork in
the highway.
The latest incorrect directions with "turn sharp left" are probably the
result of
missing turn restriction relations
<https://wiki.openstreetmap.org/wiki/Relation:restriction>. I would expect
some "no_u_turn" restrictions where slip roads join the two-way hwy way.
For example, https://www.openstreetmap.org/way/1077469012. Some
routing engines will infer this from the angle of the ways, but not all of
them.
Cheers,
Ben
_______________________________________________
Talk-au mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/talk-au
_____________________________________________________
This mail has been virus scanned by Australia On Line
see http://www.australiaonline.net.au/mailscanning
_______________________________________________
Talk-au mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/talk-au
