I’m Level 1 editor, and I’m trying to add private drives in my block. One needs to be connected to the Hilda Ave, which has Lock 5, so I can’t change turning arrows. Please unlock.
Cheers,
Eugene
Hi Eugene,
That block is locked due to the turn restrictions just north of that and I don’t want to unlock the street to Level 1 for risk of that being damaged.
If you can tell me what you’d like the turn restrictions to be, I’m happy to set them for you.
Also, please ensure you “name” the street – at least as “no name”. It will make it a white street (rather than the thin red line) and allow it to be routable.
Thanks,
Also, this: https://www.waze.com/editor/?lon=-79.42765&lat=43.79515&zoom=6&layers=BFTFFTTTTFTTFTTTTTFTTTTFTT&segments=73438666 is an improper use of a roundabout.
Please see: http://www.waze.com/wiki/index.php?title=Junction_Style_Guide#Dead_Ends
Thanks!
Hi doctorkb,
I have created a private road between Hilda and Tangreen to have an access to both streets. My condo is the tower closer to Tangreen, and I’m going to set my ‘home’ point right at the entrance. I’m assuming the ‘private’ road will never get routed through. I see it red but can’t add a name, shall I change it to ‘parking’ road?
Where it touches Hilda and Green Bush intersection, all the turns in all directions (except U-turns) are possible. Please make them all green.
The roundabout at the end of Tangreen - I’ve removed it and marked a dead end with U-turn, will that work? Because when I exit my private road to Tangreen, I turn RIGHT, then make a U-turn in the end.
Thanks,
Eugene
Good work!
I’ve enabled all turns there for you.
To name the streets, click the “Edit” button next to “Unnamed Street”.
Ensure you put the correct city in (likely the same as those around it), then check the “none” box next to the street name. Click Apply, then save your changes.
If your end point is on the private road, Waze will indeed route you there… it just tries its best to avoid private and parking lot roads except when they’re necessary to get you to the destination. Also, if it’s routable, it will route you along it to get to a destination other than home. This might be beneficial given the multiple exits from the private road.
In my view it is better to set this as a parking lot. If there is a gate that limits access I’ll set it to private road.
Waze use parking lot and private roads in similar way and only route to and from them if they are the first or last set of segments in your route, so if you set it to parking lot and set your home there, it will work for you when you navigate to and from this location.
Cheers,
Hagay.
Hagay: My feeling on this is different… and perhaps needs to change, but I’ll present my argument:
a private road is a place where you have no business being, unless you have been invited by the property owner or his/her representative. This is regardless of whether it is gated or not – but rather, if being there means you’re trespassing, whether you’re being a nuisance or not. This would mean condominium complexes, private golf course access roads, and gated communities.
A parking lot road, on the other hand, is used to get to somewhere where nearly everyone is invited to be, by mere fact of the place – e.g. shopping mall, public swimming pool, etc. – and the only way you’re going to get charged with trespassing is if you’re being a nuisance.
It doesn’t really matter, as both are function the same in the routing algorithm.
The gated part is from the Wiki page - http://www.waze.com/wiki/index.php/Map_Editing_-_select_map_editor?title=Road_Type
If you follow the instruction on the guide, it should be parking lot, unless it is gated.
It’s somehow confusing sometime the way Waze set out road types.
Cheers,
Hagay.
that says “may have gated or other controlled access points” 
The other point is that private roads should only be used when the destination requires it. In theory, a parking lot road could be used as a shortcut if traffic is REALLY REALLY bad.
Also, this is apparently what North American editors should be referencing (per the top of the wiki page you cited):
http://www.waze.com/wiki/index.php/Road_Types_(USA)#Private_Road
n.b.:
The penalty Waze will add for routing on both Private Roads and Parking Lots is so extensive that it is unlikely that Waze routing algorithm will suggest using them as a cut through.
As both function in the same way, it isn’t really matter.
If you feel that Private Road is more appropriate I will not argue.
In many cases the condo connecting roads also have visitor parking along them.
My point is that since they are both function the same, Waze should really make one set of segment type that include both.
Cheers,
Hagay.
It seems they function the same… I’m not sure that the penalty is identical for both (nor would Waze ever tell us – that’s a trade secret, I imagine).
Functionally, they’re similar… but I think we need to call a spade, a spade. Regardless of whether there is visitor parking, it’s still by invitation by the owner or his agent (condo occupant). If you’re just wanting to park somewhere, you shouldn’t be there.
Thanks guys, I really appreciate your help.
It’s working, routing me to my garage entrance from both ways, exciting!
Also thanks to Nickolka who made final touches yesterday.