I recently encountered a private road, with a gate at the far end, near Kings Clipstone: https://www.waze.com/en-GB/editor?env=row&lon=-1.09440&lat=53.16912&s=70753559&zoom=10&segments=282599119. The entrance from B6030 is marked as “private road”, etc., but Waze routed me down it. The gate is at the other end, and the road is intended for local traffic (i.e., residents on the road) only.
Nearby is another, https://www.waze.com/en-GB/editor?env=row&lon=-1.08555&lat=53.17405&s=70753559&zoom=5&segments=147945674, which is actually blocked at the entrance from B6030.
Should these be modified in the database?
I’m not a level 3 editor, so I can’t do it. (And I can’t see how anyway.)
(Moved from the Global forum to UK Editor Requests)
Hi there. It looks like quite a mess here! There was only one segment of the B6030 that was locked above level 1 - and I see no reason for that so I’ve downlocked it back to auto(1). That means everything should be editable for you.
I’ll take this one first because it’s easy. The road isn’t paved; it is closed by a gate; it is additionally deliberately blocked off by rocks, metal posts and timber. It can’t be used - delete it.
The Google Street View car has driven into the forest, up to the Sherwood Pines Cafe and Visitor Centre. I would set all of those roads as normal street (or parking lot road for any car parking area). Any private roads that might be used by residents to access properties/locations should be mapped. If a private road is closed by a gate at one end only, then disconnect that end from any other segments.
I see a lot of off-road/4x4 segments. Unless they lead to a destination the public would normally drive to, they can all be deleted. Anyone going off-road is unlikely to be using Waze. And real Waze users might get routed onto them.
Then there is the forest area place itself. For a start, it’s wrongly named “Sherwood Forest”. It looks to me like it should be “Sherwood Pines Forest Park”. Then there’s the navigation point - the crosshair icon in the middle of the place when you select it. This has been left right in the middle of the area by the editor who created it, so Waze will route you onto those pointless off-road segments to get to it! I would suggest moving it to the entrance to the car park. That way, Waze will route users somewhere sensible when they search for “Sherwood Pines Forest Park”.
One other note. I don’t know if you enabled them, but don’t enable any u-turns in Waze. Most junctions in the UK are unsuitable for u-turns (Waze developers think we all have enormous intersections like in the US :lol: ) and the client really doesn’t handle it well. It’s better to allow Waze to route around a series of turns or let the user decide for themselves where to turn around.
You should be able to do all that, so I’ll leave you to it, but feel free to ask for any further advice or help. :mrgreen: