|
How should the the turn restrictions for this junction be represented in the OSM data?
Also, some follow up questions:
Thanks! |
|
|
The tagging of the routing through any junction requires that " one ways" and junction "nodes" each have the correct restrictions. Once you have done all of them you will have to wait for the routing engines to use that data. This is my question when i struggled with a pair of simpler junctions 
|
Looking at the present tagging of your junction it may not need any additional turn restrictions as the one ways seem to do the job. The jpeg shows the results that one router gives. Does this agree with the road signs? 2
Both OSRM and MapQuest allow traffic from A to D, from C to B, and U-turns from A to A and C to C. None of these are allowed according to the road signs..
(18 Aug '15, 23:08)
michaelt
I think i understand now. I'll see if i can get to grips with iD's functions
(19 Aug '15, 06:23)
andy mackey
Initial tries suggest some new turn lanes may be needed, and turn restrictions at each individual node where necessary.
(19 Aug '15, 06:27)
andy mackey
I did not add any turn lanes. I found that iD as very good turn restriction editing facilities. I have mapped some or all of them, You can inspect or change them of course. We can now wait and see if they work correctly when the routers get to use the updated info.
(19 Aug '15, 06:50)
andy mackey
I have added some turn restrictions to your junction with iD. The tool to do this is neatly implemented in the iD editor. We will have to wait and see if they work, but I suspect that you are correct in your question that some restrictions might not be easy to map.
(19 Aug '15, 07:15)
andy mackey
|
|
I was so impressed with iD's turn restriction implementation that I thought i would share them. It works like this. Start iD. Click on the junction node, click on the "in Way" and then "out ways" show red or green indicator, to change a red or a green one just click on it to toggle or swap over, Excellent. well done iD Guys. |
