As a victorian this issue doesn’t apply to me (We can do a u-turn at any intersection unless there is a sign saying no) however in this instance the best approach is to use what we call a Bow Tie intersection. You can read more about this mapping technique here:
Only use this technique at intersections that technically need one such as your examples.
I’ve gone ahead and re-mapped the Merrylands Road intersection as an example. If you need further advice, let me know!
And about how quickly map edits take to process, look at http://status.waze.com/ for INTL tile updates. The UTC time (plus 11 hours for us) is when the map the Waze App uses was last updated. It’s normally updated once a day but recently it’s been all over the place, with no updates for up to 2 weeks in some instances.
The Bow Tie is a good temporary work-around but really Victoria should not be split. It does not meet any of the criteria as you have noticed. It would be a good one for you to un-split. The separation on Cumberland Hwy in the vicinity of its junction with Victoria is even not great enough to be split.
These roads will not show up as split on the client because they are not far enough apart. Hence there is no point splitting them. Also maintenance becomes more than twice as difficult and flagging incidents in the ‘other lane’ does not work on the client.
Hi Brad321,
Thanks for the post. I have un-split some of Victoria, and will continue when time permits. I will be driving the rest of Victoria later this week and will be able to check out the actual no u-turn situations on the intersections. Given the time it has taken so far, I can imagine the mammoth task in keeping all roads updated.
Regards
Ian
I hope, you don’t unsplit roads by just deleting one of the charriageways and making the other dual way…that would kill a lot of data, which is explicitely against the interrests of Waze. :?
Please, if unsplitting roads ALWAYS follow THIS procedure. With this method all data is merged - even housenumbers on both sides (though they have to be realigned).
That’s very important, otherwise it might even kill routing. I just recently helped tracking a foul routing, proposing a detour over a much longer hwy route instead of dollowing a comparable more direct freeway route. The reason was someone unsplitting a tunnel-section of the freeway. Well a 5km freeway segment with an average speed of 0.1 km/h was absolutely unroutable, therefore leading to the stupid detour proposal. So never underestimate the value of proper procedures :mrgreen:
Thanks Caradellino, I actually read that doc! Took a few reads to understand it fully though. The last map update was today, and I have checked the route along the road, and it appears OK through routing on the PC. I drove the route this evening (in fact i drive it every day) and it was OK. I will be heading in the opposite direction tomorrow morning.
These roads here, I believe should remain split. A big bow tie would work, but this intersection can become very busy and there are fairly long turning lanes. At grade connectors would make the intersection more complex, but give the driver enough warning to change lanes and would solve the “No U-turn” issues. Any thoughts? https://www.waze.com/editor/?lon=150.84873&lat=-33.92482&zoom=6&layers=TBFTFFTTTTFTTTTTTTTTTTTTTT&env=row
OK, for Cowpasture / Hoxton intersection I have added 2 diagonal sag rod shaped two way segments to take the right turn traffic whilst setting the turn restrictions to not allow any U-Turns. I’ve also added the slip lanes for good measure. If you can, please give it a test drive when the map tiles update. Cheers!
I hope the thread necromancy is ok, but this seemed the best place to post.
On the Great Western Highway (A44, split road) I noticed three different styles for intersections where the intersecting road has different names on each side of the Highway:
Great Western Highway intersecting with Blacktown Rd and Clunies Ross St (maplink) is done as a bowtie.
Great Western Highway intersecting with Pendle Way and Ettalong Rd (maplink) has a short unnamed section between the junction points on eastbound and westbound parts of the Highway. Does this cause a problem with directions not giving the name of the street to turn into due to the segment being unnamed?
Great Western Highway intersecting with Jones St and Berith Rd (maplink) has two additional named road segments to turn right off the Highway into the corresponding street. Does this solve a directions problem? Does it add unnecessary noise/confusion to the map - it does look a bit odd on the map compared to other.
I only spotted this because I have WME Validator set to highlight unnamed roads hence spotting the second one - found the other two when I was looking for the best way to solve it. My reading of the wiki suggests that 2 and 3 should really be bowties - or is this fixing a non-problem, especially since it needs a level 3+ editor to resolve?
Each style of intersection has its advantages and disadvantages, due to the extra complications of divided roads.
The bowtie helps to stop the issue with u-turns but can cause other issues if not done correctly. If the separation of the roads is large, the intersection can look “wrong” in the app and can cause the wrong prompts to be spoken. Bowtie intersections can create map issues because the left hand turns are too far apart from the intersection of the bowtie.
The name of the next segment will be used for the spoken prompt when navigating so having this unnamed is not a problem.
The named turning lanes are using the names of the road you will be turning into from the highway.
Depending upon the zoom level you have in the app, you generally won’t see them as the width of the highways will almost cover them up. Only issue is, if they are not far enough away from the highway you can get snapped onto them when driving past them.
If all the junction exit and entry angles are done correctly then there will not be any problems with the wrong prompts being said.
There is extra functionality called Big Junctions being tested which will allow more control over intersections.
The Junction Style Guide page has more information regarding how to deal with different kinds of intersections.
If the intersections are not causing any User Reports or Map Issues then they shouldn’t need to be changed.