|
Hello, We are using our OSRM instance for routing applications and since our last update on 1st Feb we have ran into a routing problem. We have observed a problem on one of our route which were correct before between A20 Archcliffe Road (51.11420, 1.30183) going east 300meters approx to A20 Archcliffe Road (51.1146, 1.3043) over a roundabout. This route now goes all round A20 west via B2011 and A256 giving a total route of 12kms. Please see the link below: Using Mapzen the routing works correctly as plotted below: I have tried to correct this problem on the OpenStreetMap editor by removing a barrier tag which was at the start of this roundabout which looked like a possible cause. But it hasn’t worked and routing is still incorrect for OSRM. Also, when trying to fix this problem found another. Generate a straight route from a junction exit on A20 roundabout B2011 (51.10479, 1.24031) to exit of B2011 to A20 (51.10479, 1.24031) and the OSRM routing fails. The route is blocked at the exit of B2011 round about. So the route generated is very long via Folkestone Road, A256 and back on A20 on other side of the carriage way. Please see the link below: If I select the Mapzen routing for the same the correct route is displayed as plotted below: Can someone please be able to help with this routing problem as these routes are very crucial for our systems. Thank you.
showing 5 of 12
show 7 more comments
|
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: 13 Feb '16, 21:40
question was seen: 1,665 times
last updated: 14 Feb '16, 22:03
Related questions
NOTICE: help.openstreetmap.org is no longer in use from 1st March 2024. Please use the OpenStreetMap Community Forum
Have you already tried contacting the OSRM developer(s) via IRC, mailing list, twitter or GitHub?
Yes I have now raised my issues with OSRM developers via IRC, twitter and GitHub. Thanks.
the barrier edit was this one https://www.openstreetmap.org/node/479461452/history , right?
barrier=trseems indeeed strange to me. If it caused a problem - I do not know. In any case, keep in mind that OSRM needs time to update to the new data.Do you have more questions or can we close this question here? It would be nice if you could link the github issues here.
Yes this was the edit. The barrier=tr was added a month ago. I guess this can be closed here as I have raised this issue with OSRM links mentioned above.
Btw do you know approximately how long does it takes for OSRM to update?
No, sorry, I do not know (guess: one day up to a month). Please just ask it as a new question entry here if you cannot find it in the old questions.
It would be nice if you could provide links to the other places where you raised this issue. The GitHub issue is here: https://github.com/Project-OSRM/osrm-backend/issues/1977
Thanks for copying this link here. That's the main place where I have raised this issue. On twitter I have just posted the tweet with this link.
Just checked the OSRM and seems like the changes on this route are now updated and it is now working correctly. Thank you all for looking into this matter.
OSRM will avoid any barrier which it doesn't understand, so was behaving correctly. I have no idea what barrier=tr was meant to be,
I wrote a message (asking what barrier=tr should mean) to the relevant user on 14 February 2016 at 00:59 but did not get a reply yet.
I check on the OSRM but barrier has no value of tr. Mauls a month ago. Not sure though why this barrier field was applied if tr was an invalid value. But surely removing it seems to fixed it. A new highway=traffic_signal tag was added which applies the speed restrictions, doubt that would have made any difference.
@Kushagra OSM has a quite unrestricted tagging approach. If you think that you do not want to stick to established tag keys/values then you can use any tags you like, hence
barrier=tris not wrong per so ... but it may be not that useful (in fact I guess it is a typing accident).