OpenStreetMap
Map of turn restrictions
ߊ߬ ߟߊߦߟߍ߬ߣߍ߲߬ ߦߋ߫ Zartbitter ߓߟߏ߫ 29 January 2013 ߦߋ߫ English ߟߋ߬ ߘߐ߫ ߟߊ߬ߞߎ߬ߘߦߊ߬ߟߌ߬ ߞߐߟߕߊ 20 June 2017 ߘߐ߫Attention, new Link: https://ahorn.lima-city.de/tr/ (map.comlu.com is down)
This map visualizes turn restrictions and indicates errors and warnings. It is intended to guide you in increasing OpenStreetMap’s routing quality. The map isn’t perfect but it is stable enough for the most of us ;)
There are problems in Internet Explorer prohibiting the loading of restriction data for some browser versions. I checked IE 9 and IE 10, they work for me. Firefox, Chrome, Safari work fine.
Turn restrictions are fetched from Overpass-API, which is updated every few minutes.
Have fun!
Some links:
Wiki, turn restrictions: osm.wiki/Relation:restriction
Wiki, Overpass-API: osm.wiki/Overpass_API
Overpass-API: http://overpass-api.de/
Discussion
ߡߙߌߣߊ߲ ߞߊ߬ ߝߘߊ߫ seav ߟߊ߫ 30 January 2013 at 00:13 ߘߐ߫
This is very useful! Thanks for creating this map. :-)
ߡߙߌߣߊ߲ ߞߊ߬ ߝߘߊ߫ evgenykatyshev ߟߊ߫ 30 January 2013 at 10:44 ߘߐ߫
Thanks. Usefull and user-friendly.
Some feedbacks here: http://shtosm.ru/2013/01/29/1/
ߡߙߌߣߊ߲ ߞߊ߬ ߝߘߊ߫ AlexTheTux ߟߊ߫ 30 January 2013 at 11:52 ߘߐ߫
Dear Zartbitter,
Why the following restriction you count as incorrect?
restriction:agricultural=no_left_turn restriction:hgv=no_left_turn type=restriction
Error: — relation with more than 1 restriction tag
Should I bifurcate it to two separate restriction? (I think it would be redundant.)
Thanks.
ߡߙߌߣߊ߲ ߞߊ߬ ߝߘߊ߫ Zartbitter ߟߊ߫ 30 January 2013 at 12:09 ߘߐ߫
@ AlexTheTux Yes, the map counts restrictions with more than one tag named restriction or restriction:* as an error. I think you’re right, I’ll change the rating to warning if there are multiple restiction tags. Just wait until tomorrow.
Can you tell me the relation id for testing, please?
ߡߙߌߣߊ߲ ߞߊ߬ ߝߘߊ߫ AlexTheTux ߟߊ߫ 30 January 2013 at 13:44 ߘߐ߫
Here it is: osm.org/browse/relation/2709321
ߡߙߌߣߊ߲ ߞߊ߬ ߝߘߊ߫ Zartbitter ߟߊ߫ 30 January 2013 at 14:11 ߘߐ߫
@AlexTheTux: I’ll fix this tonight. Multiple restriction tags will be rated as an error only if the values are different (e.g. restriction:hgv=no_left_turn and restriction:psv=no_u_turn). Thanks for your input!
ߡߙߌߣߊ߲ ߞߊ߬ ߝߘߊ߫ Gregory Williams ߟߊ߫ 1 February 2013 at 22:29 ߘߐ߫
Thanks for the excellent tool. It’s helped me spot and fix several broken turn restrictions near to me that have been accidentally broken by subsequent edits.
I wonder whether it might be possible to allow it to be used on one zoom level further out than at present if you’re only looking for errors and warnings? Hopefully errors and warnings only constitute a relatively small portion of the data.
ߡߙߌߣߊ߲ ߞߊ߬ ߝߘߊ߫ Zartbitter ߟߊ߫ 2 February 2013 at 09:41 ߘߐ߫
@Gregory Williams: Thank you!
Now there’s a gear wheel on the bottom right. It opens a small preferences dialog where you can set the minimal zoom level from 10 to 15 (default is 14). But this preference settings aren’t stored. After reloading the page the default values are used again.
Another change: Permalink now uses overlay settings. E.g. if you deactivate turn restrictions without errors/warnings the permalink reloads the page with the overlays activated/deactivated as they where.
ߡߙߌߣߊ߲ ߞߊ߬ ߝߘߊ߫ Zartbitter ߟߊ߫ 2 February 2013 at 09:49 ߘߐ߫
Sorry. a typo: minimal zoom level can be set to values 12 to 15.
ߡߙߌߣߊ߲ ߞߊ߬ ߝߘߊ߫ SatGarcia ߟߊ߫ 8 February 2013 at 05:00 ߘߐ߫
This seems like a very nice tool. It helped me find a couple broken turn restrictions. However, it seems to list many “errors” that I can’t interpret. For example, this relation is said to have the error, “to not properly connected to via.” The node labeled “via” is clearly part of the “to” way so I don’t know what this is getting at. Thoughts?
ߡߙߌߣߊ߲ ߞߊ߬ ߝߘߊ߫ Zartbitter ߟߊ߫ 8 February 2013 at 11:16 ߘߐ߫
@sat
yes, the “via” node is part of the “to” way, but the “via” node has to be the first or last node of the “to” way. Otherwise it is not clear what direction is meant - “to” can be 2 directions if the “via” node is somewhere in the way (from “via” to the first node of the “to” way or from “via” to the last node of the “to” way).
Best is to split the “to” way at the “via” node. You’ll get 2 ways, only one (the right one, of course g) should be the “to” way in the restriction.
ߡߙߌߣߊ߲ ߞߊ߬ ߝߘߊ߫ Aidas Kasparas ߟߊ߫ 23 September 2013 at 10:29 ߘߐ߫
Hi! Wonderful tool! It helped to fix about 10 problems in restrictions. But sometimes restrictions with problems (either warnings or errors) are off-screen, sometimes hidden under multiple restrictions circuit. Therefore, it would be helpful, if message “n warnings/errors” would be a link and it would expand to a list of restrictions with problems when clicked. This way it would be much easier to hunt problems.
ߡߙߌߣߊ߲ ߞߊ߬ ߝߘߊ߫ Mateusz Konieczny ߟߊ߫ 19 May 2015 at 05:35 ߘߐ߫
Very interesting map, though there is situation where it gives a false positive:
there is a way that is oneway (oneway=yes) but not for bicycle (oneway:bicycle=no)
turning left into this way is forbidden, also for bicycles
This tool claims that relation has a problem ““to” member 242368428 forbids to enter oneway in wrong direction”
See osm.org/relation/3835134 http://map.comlu.com/?zoom=19&lat=50.061017&lon=19.944498&layer=Grayscale&overlays=TTT
ߡߙߌߣߊ߲ ߞߊ߬ ߝߘߊ߫ Zartbitter ߟߊ߫ 25 May 2015 at 08:05 ߘߐ߫
@Mateusz Konieczny:
Your turn restriction is true for cars, too. And for cars the error message is correct.
BTW, the turn restriction is checked without using an artificial intelligence to recognize every access condition. If there’s a limitation to only one kind of vehicle, this is not supportet by this map, yet.
ߡߙߌߣߊ߲ ߞߊ߬ ߝߘߊ߫ Sovxx ߟߊ߫ 20 November 2016 at 13:01 ߘߐ߫
Great tool !! Thanks