Hi all,
Could somebody please give me the answer on how I should classify ‘For Access Only’ roads e.g. roads that residents use to get to their homes.
If correctly classified, it should then stop any potential for Waze to route around these types of roads.
I have checked the UK editing manual and done a few searches, but of course ‘access’ and ‘only’ brings lots of non-helpful results.
Cheers.
Hi.
These should be set to “Other Drivable Roads” -> “private roads” - That way waze will only route down that road if the stop is on that road.
Wolfsbanee2k.
Thanks for the info. I have updated some local roads now.
Funnily enough, I was looking for the same (or similar) thing today. I’m not sure what the effect would be of doing what you suggest in my case though. I’ll try to explain…
Two roads at opposite ends of a housing estate are marked as “access only” in an attempt to prevent people using the estate roads as a rat run. There are other roads onto the estate but they take a somewhat longer route so are less desirable for a rat run. What will happen to people who live on the estate trying to route out of it? Would they get routed on the long routes only?
What I think I really need is the road to be “access only” coming into the estate and a normal street for leaving. At the moment for my journey Waze is happily routing me through the estate as the most efficient path, so I ignore it, but strangers to the area might well follow it.
What is the best way of handling this?
You can split the road into 2 one-way segments at the entrance exit - like a tiny bit of dual carriageway. Disable the u-turns, then set the segment going into the estate as private and the segment coming out as “normal”.
However, whilst that will help residents routing out of the estate, it won’t help them routing in - they’ll still be taken “the long way round”.
If you care to share a permalink for the estate, I can have a look at the situation.
Sure thing, the link is as follows
I have highlighted the rat run. Here the 2 roads in question into the estate are, from node A, Cross Rd, and from node B, Beane Rd. [Cross Rd has an additional restriction of “No Right Turn” from Bengeo St into Cross Road, Mon - Fri 7:30am - 8:30am]
You’re in luck - at least as far as a simple solution goes. 
As far as I can see, every entrance to the estate is marked access only: Beane Rd, Cross Rd, and The Avenue are the only entrances into that entire section of roads. So you can just change all three to “Private Road”.
That way, Waze shouldn’t route anyone through the estate but round it. If someone is routing into or out of the estate, all routes have the same penalty (1 section of private road) so there will be no nett effect on routing.
It’s still possible that, under certain circumstances, Waze may decide that the penalty for routing through the estate is still lower than routing around it for, say, a very short route or when traffic is bad. If you do get through routes after making the entrances private, you could make all roads in the estate private to increase the through-routing penalty.
Don’t forget to set a time restriction for that right turn, though - otherwise someone routing into the estate will still be annoyed.
Thanks for your help. Ah yes, I’d forgotten that The Avenue is also for access only :roll:
There is one other route out of there via a one way street (Tower St) that leads onto Bengeo St. I think it is advisable to make that private as well so as to give it equal weighting as for the other exits, yes?
And the pupil has become the master. :lol:
Good catch - I hadn’t thought of that. :oops:
Thanks There’s always more to learn though 
Since this is becoming a masterclass, I thought I’d throw in another private estate where the problem is one exit is for residents only and one is available for everyone. Since we can’t distinguish residents and non-residents what would be the best solution?
Fitzroy Park in North London (much procrastination from me on this one!)
As you say, without the ability for the app to know whether or not the user is a resident, there’s no way to provide accurate routing in all cases. As a partial solution though, if only the resident-only exit were marked as private, leaving the rest of the estate marked as public roads, then it’d allow correct routing into and out of the estate for everyone without turning the estate into a valid through route option.
Whilst this would inconvenience any residents who are both Waze users and require the use of satnav to find their way into or out of the estate, any resident Wazers with the slightest hint of clue about them should be able to figure out that the route Waze has offered isn’t the best and use the resident-only exit anyway.
Yes, it does, unfortunately, seem to be the only solution.
My take on it:
As I recall, all the roads except the “public” entrance are currently disconnected. The non-public entrances have manual gates you have to get out & open. The public gate is automatic. So . . .
Connect each of the disconnected roads to the public road network by a very short segment of private road - you want to stop routing into the estate, but you also don’t want anyone to route onto one of the private segments. The rest of the estate, including the entrance is normal streets.
That should prevent routing through the estate because of private roads.
Anyone routing into or out of the estate will be routed by the “public” entrance.
As said above, this will not accommodate residents (who obviously know the road situation anyway), but will accommodate visitors (who won’t).
If the public entrance is only open to the public at certain times of day, then again you have to choose between breaking routing for residents out-of-hours, or allowing non-residents to try & enter the estate out-of-hours. I can’t imagine you aren’t allowed visitors if you live there, so I would tend towards not implementing a time-based restriction.
Why bother? Leaving them disconnected will have exactly the same effect.
Now, if you had a longer Private segment (avoiding any addressable properties) then Waze would be able to find a new route while the driver was opening the barrier, rather than waiting for them to get past it.
2p.
To avoid the generation of map problems. Minor problem, I know, but it looks wrong to me having them all disconnected.
My concern is that, if someone searches for an address and Google (or Waze) returns a point on the private segment, the driver may then be routed directly to that segment via the residents-only gate. The less chance there is of “hitting” the private segment, the more chance that drivers will be routed via the public entrance.