Please double check with your country manager and/or regional coordinator as that is part of the new Parking Lot Area Feature / Roll out.
Exactly why I haven’t touched it, instead highlighted it in the UK forum to encourage some direction from the UK managers.
From the little I’ve teased out of others it is my understanding Waze are pushing to have every car park mapped even if it attached to a single business.
There are also new car park points for car park areas.
And also multiple car parks, with random names, where only 1 exists.
I am joining this a bit late, but have only just noticed a sprinkling of little blue dots over the map. :o
Waze has changed parking to a “area only” type some while ago, resulting in a batch of MP’s highlighting the remaining “point” ones.
Then (in my area) on 18 August put in point type markers for every carpark it can find, those already in place, those not yet done and several that are not even parking areas. It has also stuck some of these points on some private car parks such as supermarkets.
Has anyone seen any guidance on what is happening and what we are meant to do with all of this?
I am currently up to page 32 of a 34 page thread in the Global Champs forum about the new Parking Project. It’s heavy going :lol: and has probably cost me the chance to take the kids out for the day. 
As usual, the whole thing starts with Waze saying “I have a great idea” but not providing enough information or considering the consequences. It then proceeds to a long discussion where plenty of GCs ask sensible questions which don’t get answered; Waze answer other questions and tell us what’s changing, whilst introducing things that lack support in editor/client; GCs ask pointless questions because they didn’t understand what Waze said; and the interminable background noise of “why aren’t you finishing off tunnels/junction boxes etc”.
I’ll be honest and say I lost track of it all long ago and am now catching up. If it seems that we don’t have any guidance for you yet - it’s because we don’t. There are still important questions to be answered by Waze and several countries are still holding back on full guidelines to their communities until these issues are clarified. Some of these issues were brought up at the UK meetup.
When I get to the end of the GC topic, I’ll post back here and try & give a better idea of where things currently stand. We (the UK Admins) also need to try & come up with some concrete guidance - which won’t be helped by the fact that 2 of us are currently on holiday and another is about to go. :mrgreen:
Well, I caught up on the GC thread - and it still keeps growing! Since I’m selfishly on holiday and acting like it, the guideline writing is going slowly, so I thought I’d better at least post back here to give you an idea of the issues.
Areas vs points. This is simple enough. The parking functionality that is coming to Waze needs the client to decide when you have entered a parking area. If it’s a point, that simply can’t be done. So there’s no question, they all need to be areas.
Customer parking attribute on other places. We have asked repeatedly that Waze address the question of how this attribute will be used. No sensible answers.
Multiple entry points for car parks. This is absolutely going to be needed for larger car parks, particularly places like retail parks or shopping centres. Waze have this in the works, but no ETA.
Linking car parks to other places. This will be coming but, again, no ETA. They initially referred to it as “nested places”, but I suspect it will be something similar to linking Waze places to Google results. So if you have, say 8 businesses built around a common parking area, you will be able to link each place to that car park.
Cost. We have the options of free/low/moderate/expensive. Apart from the difference between free & paid, these are plainly stupid. For the first UK Meetup at the Strand Hotel in London, the cheapest overnight parking & found was £35 - and I considered that very cheap for central London. For any small town in the UK, that would be considered “extortionate”. The difference between low/moderate/expensive would have to be locally determined; can only be done with considerable research into all the other parking prices nearby; and would still be entirely subjective - leading to many complaints from users who might not agree with our choice. I have personally asked that low/moderate/expensive be removed.
Another issue with cost is the multitude of different pricing schemes. Free for the first x minutes. Discount rate for whole 24 hours. We are asking Waze about this but not getting many answers. I thought the new car park type had a cost field when I looked a couple of days ago - I can’t see it now. :?
Private/public. I can’t remember the exact terms because this setting also seems to have disappeared. But there were questions about how this will work. Whilst private car parks will need to be mapped to support the app functionality, it will be a disaster if the current app version directs users to private car parks because the full functionality hasn’t been added to the app.
I’ll try to come up with some temporary guidelines shortly, so we can at least deal with all the MPs being generated before the noobs get to them. :lol:
Thanks for the informative reply (as usual 
).
One issue you have not included, and I have had a few issues with, is for carparks with multiple entrances and exits, Waze can be prone to route through these on occasion. I have “fixed” the couple that have been a problem by disconnecting the parking lot roads running through.
Entrances and exits close together are not a problem, but if there are several, on different side of the carpark, exiting onto different roads and the area is often busy, a few naughty wazers taking the shortcut through the car park makes Waze think the route is open for business.
'Nuff said? 
This absolutely should not happen, under any circumstances. Waze should not route through or onto PLRs unless the destination is on those PLRs. This is achieved by having a large penalty against routing off a segment of PLR onto a normal driveable segment. This should not be affected, even by several hundred Wazers taking such a shortcut.
If you can provide any such examples please do so (in a separate thread), as it would indicate a potentially serious problem with the routing engine.
So if Car Parks should now be mapped as areas why is the WazeParking1 bot adding them as points :evil:
Station Road Car Park, Liphook
which is duplicating the area places already on the map :evil: :evil:
I’m guessing this is so they can then flag them all as Map Problems for us to deal with.
Now the project project is open to all to discuss:
https://www.waze.com/forum/viewtopic.php?f=1714&t=202535
Well at less for GC and LC :mrgreen:
I see the Waze fairy has been showering us with new blue dots again.
Today in the south east there must be several hundred new “car park as points” issues that Waze have decided to drop in. At least half of these already exist as properly drawn car parks, but there are quite a few new ones in there. I have also found quite a few train station car parks, a few retail estates and a few other “not for general public” car parks. This is going to take a while to clear up. :?
Even (almost) all of the ones we so lovingly created as area places as part of the car park map raid… Bad enough we’re being swamped with mostly useless SLURs, now we’re being spammed by a bloody Wazebot spewing garbage all over the map for the MP generation code to get its teeth stuck into. And I just LOVE the irony of the bot having to create new point places just so that these MPs can be raised, rather than simply relying on the MP generator going out to find any existing point places that hadn’t already been converted to areas. Well done Waze devs, give yourselves a really big pat on the back for yet another excellent idea perfectly executed.
:roll: :roll: :roll: :roll:
Waze HQ, listen very carefully, for I shall say this only once…
STOP THROWING HALF-ARSED IDEAS OUT INTO THE WILD WITHOUT PROPERLY THINKING THROUGH THE CONSEQUENCES, AND STOP FUCKING AROUND WITH THE MAP DATA IN WAYS THAT WOULD GET ANY NORMAL EDITOR BANNED, IF NOT FOR ETERNITY, THEN FOR A FAIRLY LENGTHY COOLING OFF PERIOD AT LEAST.
:evil: :evil: :evil: :evil:
You want our help. You NEED our help. So work WITH us, learn from the ideas and techniques that the editing community have spent countless hours honing and finessing, and take off your giant ego hats and accept that, despite your frequent protestations to the contrary, your devs really don’t know nearly as much about what map editing actually involves as they think they do.
Right, now I’ve got that off my chest, what shall I do with my editing time tonight? Clear off a bunch more SLURs suggesting each section of the M25 has at least 3 different limits or that some quiet back streets are actually a grand prix circuit in disguise, start nuking all of these new PLIAPs and associated point places, or, ooh, I dunno, actually try and keep on top of all the real problems and reports that we struggle to deal with at the best of times???
I can see lots of these Map Problems near me and would like to resolve them if that’s an appropriate thing to do? An example is https://www.waze.com/editor/?env=row&lon=-2.36562&lat=51.38349&layers=4069&zoom=7&mode=0&update_requestsFilter=true&mapProblemFilter=0&mapUpdateRequestFilter=0&venueFilter=0&venues=234357250.-1951198190.10216284&mapProblem=2%2F3279667 where the existing Parking Lot area looks fine. If that’s the case, should I delete the point and mark it as resolved?
Thanks
Guidelines for how to deal with the epidemic of new car parks and map problems have been posted here. :mrgreen:
I will link to them from the various UK topics discussing car parks and from the UK Wiki.
A note on “why were the car parks imported as points?”. It’s only surmise, but I’m very confident with it. The import comes from an organisation called ParkMe and I have no doubt that their database simply contains point locations. Even if they had geometry areas, they might not be compatible with Waze, or too complex, or too simple.
I think the import as points and the subsequent generation of MPs is actually reasonable. The points wait for an editor to “fix” them properly. The MP draws attention to something that needs looking at. This is little different to how we did petrol stations a few years back. Every petrol station was imported as a small, standard size rectangle. Timbones then generated a UR for every imported petrol station. We fixed each place and marked the UR as solved. That all worked very well - the only difference is the far larger number of car parks than petrol stations.
Remember these are MPs, not URs. No user is waiting for a reply and the only urgency on dealing with them is so that experienced editors get them right before inexperience editors who haven’t seen the guidelines get them wrong.
Which is already happening unfortunately.
If you notice any issues with the imported car parks, please submit them to Waze via this form.
kthxbai
By “issues” do you just mean things wrong with the imported data independent of anything already in Waze (e.g. wrong location, car park name etc.), or can we also report instances where the apparent lack of any data pre-filtering has caused new point places to be generated right next to existing area places, even though there might not be anything wrong with the data used to generate those new points?
Just submit everything that annoys you until you feel better 