|
Please could more experienced users help a newbie sort out a problematic roundabout. I'm trying to avoid this: http://www.cyclestreets.net/journey/1293354/ On some wesbites that I know use OSM, the route would have me going even further (6km!) to complete what is in reality 200 m around the roundabout. This problem existed before I ever started editing OSM, but it prompted me to have a go. I've tried a number of things, but none make any difference. (N.B. the return works fine: http://www.cyclestreets.net/journey/1293457/ ) Thanks |
|
The B4091 outgoing wasn't connected to the roundabout. Should be fixed now, but will probably take some time before it is changed on the site you are using. To check for this kind of error the OSMI routing perspective is the tool of choice: http://tools.geofabrik.de/osmi/?view=routing&lon=-3.62842&lat=53.92634&zoom=6 Simon Thx Simon. I checked this 10s of times (as my edit record will show), as it was the most obvious problem. How can you tell if the ways are REALLY connected?
(04 Nov '11, 16:20)
slogfester
I was just going to add that to my answer. Currently the best method is to use the OSMI routing perspective. For the roundabout in question: http://tools.geofabrik.de/osmi/?view=routing&lon=-2.07767&lat=52.38287&zoom=18&opacity=0.69 Note: the error will not show as soon as GeoFabrik have updated their data. PS: I had a look at the roundabout and found the connection looked funny, but OSMI is more reliable :-)
(04 Nov '11, 16:27)
SimonPoole ♦
Wow! What a tool (the OSMI routing perspective thingy, that is!). There are so many junctions that have given me strife over the years. I'll be at them like a rabid cartographer :)
(04 Nov '11, 16:42)
slogfester
|
