|
Hi andy mackey, there is one point on this road with a lot of turnrestrictions with the effect that you cannot go anywhere (?) It maybe an error : https://www.openstreetmap.org/changeset/94956680 restriction=no_straight_on User eteb3 changeset 94956680 Turn restrictions at London Rock quarry turn nr Warmington ; add bldg; add operator at quarry I'm in The Netherlands and not familiar with the situation The solution is to delete this relation, Imo hth Gys I'm also suspicious of the same tagging, but wasn't sure late last night, thanks Gys de Jongh
(30 Aug '21, 08:52)
andy mackey
HELP please we are not sure :-)
(30 Aug '21, 17:27)
andy mackey
1
eteb3 has deleted 3 turn restrictions a few hours back. Now it looks good to me.
(30 Aug '21, 21:59)
TZorn
Thanks etab3
(31 Aug '21, 08:48)
andy mackey
|
NOTICE: help.openstreetmap.org is no longer in use from 1st March 2024. Please use the OpenStreetMap Community Forum
Follow this question
By Email:Once you sign in you will be able to subscribe for any updates here
By RSS:Markdown Basics
- *italic* or _italic_
- **bold** or __bold__
- link:[text](http://url.com/ "title")
- image?
- numbered list: 1. Foo 2. Bar
- to add a line break simply add two spaces to where you would like the new line to be.
- basic HTML tags are also supported
Question tags:
question asked: 29 Aug '21, 23:26
question was seen: 1,292 times
last updated: 06 Sep '21, 10:25
Related questions
NOTICE: help.openstreetmap.org is no longer in use from 1st March 2024. Please use the OpenStreetMap Community Forum
full route https://www.openstreetmap.org/directions?engine=fossgis_osrm_car&route=52.5192%2C-0.4000%3B52.5186%2C-0.4012#map=14/52.5205/-0.3967
OSRM router now working as expected. and Graphopper just now.
GraphHopper Does not work East to West 03/09/2021 a hadn't tested the routing in both directions, sorry.
That must be a glitch or bug in GraphHopper. There is now really nothing left that could prevent routing. Maybe GraphHopper is wrongly evaluating the no u-turn restriction.
How can we find and replicate that error some where else on the OSM. And then report it to GraphHopper?
Graphhopper routes correctly now both ways. Something must have lagged in the data processing.
I tested GraphHopper was working as expected early on 04/09/21, it was,and their algorithm had needed time to calculate both directions i guess. I shows how smart routing engine programmers need to be. Incidentally I travelled this road later that day as a passenger, The turn restrictions are solid white lines and a hatched virtual island at the node in question, I didn't see any other signage, which it doesn't need of course. On my PC later, running Potlatch, I could just about see the virtual traffic island on Bing.