On the live map we have an intersection of Otto and Cusak St
Above that is Bristol St
If you route from the RH end of Bristol St TO Cusak St just to the left of where it joins to Otto, the route will go down Bristol, and left into Cusak. A bit of a long way round.
If you route from the RH end of Bristol St TO Cusak St just to the right of where it joins to Otto, the route will go down Bristol, and left into Bettina and then onto Cusak. The way one would expect it.
The same happens with a reverse route.
Does anyone have an idea what is wrong with the intersection? The turns looked OK.
I’m suspecting it’s calculating on how many nodes it has to calculate. To the right of Otto is only 6 nodes to GZ, whereas if you have it to the left of Otto, it would have to navigate 7 nodes to GZ, hence the longer way because that would only mean 6?
To test that theory, I’ve purposely added in 2 nodes on the left side of Cusak St and will wait for the INTL sync, then test. See if that affects routing to make it go to the right?
I’ve had a look at the road turns and and segment ranking, and all looks ok, so I’m only suspecting the nodes.
-following added-
I did find a problem with the Pittwater Rd heading to the NW where it doubled back on itself. I also noticed sections of Pittwater Rd (where it splits) do not have City Names on them as the No-City box is ticked. Should they?
There’s some horrible complexity there that could be fixed up entirely with some two way segments rather than multiple one way segments.
With a couple of intersections in Brisbane that have been broken when attempting to split roads (just around the intersection), I’ve fixed by putting back to a two way segment. Less chance of routing anomalies and missing turns.
Yes, there is, but I am going to have a good think about the most efficient way to go and their consequences before I even attempt it. (and when I get some time!!)
The largest consequence is the risk of breaking turn restrictions that were previously working.
The 2nd largest consequence is the risk of losing historical traffic data.
I have seen both on numerous occasions here in Brisbane the past 2 months, unfortunately I can only fix up one of those.
If/when you decide to attempt fixing them up, make sure you read the Wiki section on un-splitting roads first. After you fix them up, ask us to check them, that’s why we’re here.
If it is done with roads rather than roundabout segments, your best bet is to delete the roundabout and re-create it from scratch. I am not aware of any tools that can use road segments to redraw roundabouts.
Unfortunately this does lose some traffic data but it’s better to have proper instructions in this case I think.
I do not believe there is any way to do it other than deleting the roads and inserting a proper roundabout. Unsplit Restwell Rd while you are there and that makes it a “simple roundabout”. If you delete the split sections and stretch the remainder up to Cowpasture you will maintain the average speed data.