L3 Colchester (Essex) Butt Road Car Park

Map Editors Community United Kingdom UK Editor Requests
1

New to this, so hoping I get this right! :wink:

My level: 1

https://www.waze.com/en-GB/editor/?env=row&lon=0.89326&lat=51.88449&zoom=8&mode=0&mapProblemFilter=0&mapUpdateRequestFilter=0&venueFilter=2&segments=299294883,299294878,299294879,299294880,299294882,299294876

The road layout of this car park is now about 3 years out of date (see https://www.google.co.uk/maps/@51.8845233,0.8942588,107m/data=!3m1!1e3 for the new layout) and would overlap roads for the new housing estate next door

(Also, Waze doesn’t seem to recognise this as a car park when it searches for car parks nearby - no idea why?)

Many thanks!

2

Hi there, and welcome to the forums! :mrgreen:

I’ve unlocked the car park segments so you can edit them - we often lock car park roads when they’re done because a favourite past-time for new editors is adding every single lane, which doesn’t work! :lol:

Have a go at it, bearing in mind the following points:

  • Phone GPS accuracy isn’t good enough to pin down your exact location. If you map every lane of a car park, the chances are Waze won’t “snap” you to the right segment and the directions will be quite useless.
    If a car park is large, map the segments around the perimeter and perhaps a couple of “main” routes through it. If it’s small, a single segment may be the best choice.
  • Move the navigation point for the car park place to just inside the entrance. This means Waze will guide users into the entrance and then “shut up”, allowing you to concentrate on finding a parking place
  • Use the SHIFT-Z shortcut to show all red arrows - to check you have enabled all the turns. Please note there is a bug in the editor at the moment. Use SHIFT-Z to see all the red arrows, but turn it off again before changing any turn restrictions
    Give me a shout here when you’re done, or if you need any help. :mrgreen:
3

Hi, and thanks for the welcome! :mrgreen:

I’ve given it a go based on your guidance - wasn’t entirely sure how much is “too much” when it came to segments so I have put all the roads of this small car park on - mainly because it’s mostly one-way and the previous version was mapped fully. Hope it’s not too much! :shock:

Moved the navigation point too, so hopefully that’ll help. Let me know what you think!

(P.S. as it’s such a big change, I deleted the old segments and replaced them: https://www.waze.com/en-GB/editor/?env=row&lon=0.89382&lat=51.88439&zoom=8&mode=0&mapProblemFilter=0&mapUpdateRequestFilter=0&venueFilter=2&segments=327269829,327269835,327269833,327269834 - hope that’s okay!)

Thanks! :smiley:

4

All looks good! :mrgreen:

I’ve made a couple of changes, but these concern a problem with Waze routing that you wouldn’t have known about. The routing servers pass routes to the app as a list of junction nodes. If, for a pair of junction nodes, there are are 2 segments directly connecting the nodes, the client can get confused: it may show a route that uses one of the segments whilst giving directions that use the other! The upshot of this is that any loop of segments must be made of at least 3 segments. I’ve accomplished this by adding a couple of extra junction nodes to the 2 loops.

I’ve locked the segments to 3, to demonstrate that they are deliberate despite not matching the aerial images, and to prevent anyone messing about with them. :slight_smile: