I still hope to be able to change private to public… some places are changed to private by users, and currently I can only delete it…
I’ve run into this. Bunch of weird random bugs cropping up with places.
I can confirm this in the US - the first part anwyay. I created a new road “Foobar Ln” about a block away from where I am right now. Waited for the tiles to update, refreshed my map cache, the road shows up in the map display but it is not searchable. I am going to add a house number to it and see if that makes it searchable after the next tile update.
Needs to be in google maps to be searchable
Yes there is no problem, but when you look at the map at a very high level, accept a photo as “other” but it should be public. Now you have to find where it was on the map, select it and switch to private. The problem is to find it when you are not on a close zoom.
Zoom on it ( I hold shift a drag the mouse over it on chrome) before saving while the update pin is still there.
Sent using Tapatalk for Android 4.4.2
This doesn’t appear to be true either.
So I’m not sure if it was adding House Numbers or just waiting an extra day, but my new fake road is now searchable in the app. I may do some additional testing later this week.
To recap: I created a fake street about a block from where I am, ‘Foobar Ln’, and connected it to a real street. This street does not exist in Google Maps. After the tile update, the road showed up in the app on the map, but you could not search for it.
I added two fake house numbers to the road, and after the next tile update, you can now search for “Foobar Ln” and it will come up.
Later this week, I will try creating a fake street and waiting two tile update cycles to see if it becomes searchable in the app (without creating any house numbers).
I always zoom in on a place update before approving it if I’m going to need to take a closer look. I particularly do this with new places to check for duplicates or if I’ll need to reposition it afterwards (which is common.)
So I asked WazeHQ. They gave me the list . . . but asked that I not make it public. I’m not sure what to do at this point.
Say you magically found a link that has that list online and claim you’re one of the victims of the Fappening (Blame iCloud). 
I just verified that a new subdivision that I mapped and added addresses to is fully searchable from the client.
https://www.waze.com/editor/?env=usa&lon=-117.56436&lat=33.95873&layers=1605&zoom=6
Everything in that “field” whether with or without a house number is searchable.
Well it’s their property so you should respect their wishes, but at some point the Waze community is going to grow weary of wasting hundreds of hours reverse engineering their work on this and other topics (turn instructions, routing calculation). Needless to say, we will document our findings in the wiki, so it only seems to serve to delay the inevitable and consume valuable volunteer resources spinning wheels rather than fixing issues, researching maps, or moderating dirty places pictures. Knowledge should be a zero-sum game, to the extent it doesn’t compromise the ability to maintain profitability and remain competitive
I totally agree. I did expressly ask for a list I could share with the editing corp, but received a list that can’t be shared. I don’t understand the reasoning for restricting the information here. From a personal perspective, I wish I hadn’t asked as I also feel that I can’t participate in the wasting of the hours of reverse engineering on this topic after having seen the list.
It is as if the Waze team expressly wishes to drive editors away. Especially CBenson. This information can be extracted via a tedious reverse-engineering process. So it is not actually a secret. Providing it would bring efficiency and joy to editors, and so improve the experience for the entire community. Even a “we decline to provide this because it is changing by the hour; we expect some stability by …” Or even “it is automagically generated and we expect it to change constantly – similar to how the cities layer is generated”
But “here’s a list we expect you’ll find useful only please don’t put it to use unless, you know, you intend to adjust the names/categories of the entire world of places all by your lonesome”. That just sounds like “Thanks for offering us the opportunity to frustrate you so badly you are tempted to give up in disgust”
The Hotels category turned to Hostels issue still not fixed here in Malaysia. There are just too many and not easy to track to change manually.
REQuest Waze to fix them all.
Globally, I wonder how many “hostels” are actually properly mapped? I would think if we changed every “Hostel” to “Hotel” that the data cleanup would be much less.
Has anyone else found?
- Cannot define a keyboard shortcut
- Shift+click+drag to create a zoom-in box often leaves the zoom controller in the previous zoom level/state
The first one has been noticed by many, myself included in the toolbox thread. It was confirmed there to be a native wme issue. I was under the impression it was reported already. If it’s not already on the list, needs to be.
The second I haven’t looked.
Sent using Tapatalk for Android 4.4.2
I will get it added.
It was mentioned here by MapSir in the Scandinavian Countries forum that the issue is fixed. Well maybe at least for Norway.