Saw a UR from someone complaining that because Waze doesn’t use Coto de Caza Bld, that it adds 4 miles to the planned trip. While taking a look at it I saw the following:
A) I found some level 1 edits that were preventing routing through it. Otherwise the main road through is currently set as Primary Street.
B) Maybe it should be restricted (private road).
If you are not familiar with Coto de Caza, it isn’t actually a city. It is a gated community of over 10,000 people. You aren’t allowed in the gates if you aren’t a resident or have business inside.
What say ye? Change from Primary Road to Private Road, or leave it be?
Well, I’m going to go ahead and set segments at the entrance and exit as private unless someone argues against me on this. I see no reason to make the entire giant complex private.
I agree with the strategy of “private” and not “parking lot”. I’ve seen several auto generated map problems where Waze routes through a parking lot where any possible advantage is minuscule at best, so a private road at the entrance seems the only option.
Hmm…that’s disturbing. I believe the Waze routing engine was supposed to levy a heavy penalty for parking lot roads, greatly reducing the probability of being routed over them. Private roads, however, do not have as heavy of a penalty. Anyone with a better understanding how Waze handles weighting of the different road types know?
Here’s what I have seen: An editor, preferring to do “shortcuts” through Parking Lots because that’s what he/she usually does, will sometimes turn off directional arrows such that the Parking Lot is the only way to get from Point A to B. So, when they use Waze, it always uses their “preferred route” even though it screws everyone else over. Extremely annoying and hard to spot/identify.
That should be a hard and fast rule violation with consequences… but I digress. Here’s a location I’ve seen multiple times get flagged automatically by Waze because drivers stay on the road heading NE on Walnut to turn left on Newport even though Waze routed them through the parking lot:
There’s clearly no distance advantage. Maybe someone had monkeyed with the arrows and they got changed before I checked it out. However, now I see that someone has put a red arrow on the left turn into the parking lot from the NB Walnut. My guess is that they did it to prevent the parking lot route, however, that left turn is legal. I’m not sure if I should correct the arrow to see if Waze starts the parking lot route again.
It seems to me that Waze should never route through a parking lot unless the destination is in the parking lot.
Allow the turn arrow. Next time someone gets routed through there contact Waze via Nanorep. Send them a permalink and a screen shot of the problem. Don’t close the UR.
Or PM it to me and I’ll contact them.
It should not be routing through that parking lot, but we have to provide real examples to Waze to get them to check out the problem.
Last time this happened someone closed the UR before Waze looked at it, so they couldn’t do anything.
Similarly, I’ve seen these popping up where Waze is routing people through alleys marked as Parking Lot Roads. Even though it’s an alley and not an actual parking lot, would you advise the same Nanorep report protocol?
Looks like what you wanted me to see has been closed by someone.
Is it a UR about being routed over a parking lot road?
Or is it a MP about being routed over a parking lot road? Specifically the “Most users didn’t follow…” error?
If the latter, the Champs have said this is due to Waze using ancient data to generate those automated MP’s, and they should just be marked as solved.