U-Turn is allowed in this link. Uturn is allowed on Airway Blvd north of the gas station. ALSO-- Incorrect road designations as “Major Highways” needs to be updated. These are primary streets.
Permalink:
https://www.waze.com/editor/?lon=-121.81837&lat=37.70341&zoom=6&layers=901&env=usa&segments=69559635
I have taken a look at the UR which concerns this, and the following is written with the intent to answer your post, as well as the conversation in that UR. I don’t know if you are possibly the reporter there, so this goes out to all involved, and may not seem to be in direct reply to this forum post:
Individual two-way segments CAN have U-turns enabled at either end. There IS a turn restriction button in the Waze Map Editor for this. BUT, there is currently no functionality in the app for a U-turn prompt to be given to the driver en route.
The general consensus in the editing community is that we should wait until Waze officially supports U-turns in the app before we enable them at the ends of two-way segments.
What would happen now, if Waze tried to route a U-turn at NB Airway Blvd and Canyons Pkwy would be a suggested route on screen which appears to just end at Canyons Pkwy (because it doubles back over itself, and looks like one line). There is NO turn prompt at all. What you WOULD see at the top of the screen would be the NEXT turn prompt.
So if, for example, you were heading north on Airway, and needed to make a U to double back and get on the ramp for the 580 W, you would be seeing the turn prompt to Stay to the Right at 580 W while you were still headed north and approaching Canyons Pkwy. This can be terribly confusing to a driver who is not familiar with an area, and it generates far more trouble reports than the inconvenience of Waze routing the long way around a block, instead of the U-turn.
We have been asking Waze to give us full U-turn functionality for a long time, and they have told us that it’s coming someday. Until then, the policy is to leave U-turns disabled at the ends of two-way segments under most conditions.
Now, there IS a way to make a Waze prompt for a U-turn where a road is split. IF a road is split into two one-way halves, you can enable the turn(s) where those segments meet the intersection, and depending upon how you configure the intersection, the app will either tell you to turn left once or twice, and you can actually see the U-turn path on screen.
Where there are good reasons for a major boulevard to be split into two one-way halves, we do this, but only under certain conditions defined in the Waze editing wiki.
Both roads approaching this intersection do have center medians, but they do not otherwise qualify to be split. I would say that we need to wait until Waze supports U-turns in the app before we act on this issue, as frustrating as that wait might be.
Ok, now to the issue of road type. The US Waze Champs have been discussing a nationwide standardization of our road type usage for yeas, and as of April this year decided to implement Functional Classification, as defined by Federal standards (FHWA) and state departments of transportation:
https://wiki.waze.com/wiki/Road_types/USA
https://www.waze.com/forum/viewtopic.php?f=129&t=89435
https://www.waze.com/forum/viewtopic.php?f=251&t=90107&start=10#p763711
Please understand that the NAMES of the road types in the map editor are no longer representative, necessarily, of the physical characteristics of the road. Major and Minor highway types are now used for roads which the departments of transportation (CalTrans/Dot in California) have determined to be Principal and Minor Arterials, respectively. This means that you may well see a road set as a “Highway” type, when it is in fact just a city street which has a functional connection between one place and another. There is room for argument as to whether one particular street has been classified properly by CalTrans, but that should be taken up on a case by case basis with a local Champ (kentsmith9), Area Manager, or Regional Coordinator (Jemay) if you do not have the sufficient rank to change it yourself.
Here is a link to the Functional Classification grid map from California DOT which covers this particular area. You can see in it that these streets have been correctly classified according to CalTrans. If they do not, in your opinion, meet those qualifications, please take this up with kentsmith9 or Jemay, who could best make the call to re-classify them.
http://www.dot.ca.gov/hq/tsip/hseb/crs_map/06l32.pdf