I know this is an old bug thats been around for some time now.
Why are all of these places submerged? Is there anything we can do to fix it?
Frankly its becoming a real annoyance, and its starting to put me off the waze app completely.
Any ideas?
Last I heard it is a locked water layer out of our reach.
Sent from my SM-G920I using Tapatalk
In Oz the are starting to to use islands to fix this problem
https://www.waze.com/forum/viewtopic.php?f=56&p=1313691#p1313691
That’s a good idea around the issue.
I will do a test near me as most of the coast line is out.
Can confirm it works a treat!
We can reclaim the coastline… 
Check the Oz post, I think they may have some problems?
Looks like somebody has tried fixing up around Paekakariki/Paraparaumu (Northern Wellington kapiti Coast), but it does not seem to have had any effect. 
https://www.waze.com/livemap?zoom=15&lat=-40.98045&lon=174.95985
I’ve made more changes (extended)
We have been telling users to report this issue to Waze support when they have reported a UR complaining about the water over land.
This way the more support is notified about the water issue the greater the chance something may be done to rectify the issue they created. 
The information you leave out of your post is how long WazeHQ have known about this problem for?
Have any of these been fixed?
https://www.waze.com/forum/viewtopic.php?f=56&t=124948
Having said that it would be good if you could talk to WazeHQ again about this problem
Kiwidroid: Creating such islands has certainly helped the coastline in Onehunga, Auckland. It worked there, so it should work further south too!
If I’m reading it right, ispyisail loaded that ‘island’ for Paekakariki on the 2nd of April, which won’t be included yet (last map tile update was edits as at “as at March 29, 2016 11:30 UTC” or 00:30 am March 30, NZDT, five days ago now. Check status.waze.com)
(I also cynically wonder if Kiwis are just used to bad data from offshore-based services so don’t bother complaining, which is why we don’t get so many issues reported? After all, even Apple Maps has the same issue in places!)
Just for those that are new
Over the years there are many things that don’t work as expected with Waze
People started creating workaround’s like the one in this thread.
WazeHQ has has discouraged workarounds and I don’t disagree in principle
But this has been a problem for so long now (I think we are into years now) That I just created an Island as I understand people are now doing in OZ.
Just a note, if we create islands, it’s worth not giving them names! (Real islands excepted, of course.) Just looked at an UR of
What I’ve been doing is (a) leaving the name blank, and (b) adding “Temp Landmass Fix” to the description. (Any words in the ‘name’ will be visible on the map in the app!) I figure leaving the Alternate Names blank reduces the changes of polluting the search results, but I suppose we could put text there too?)
(I can’t fix this particular one as it’s outside of my editing area.)
Looks like this has been fixed now (kapiti Coast), thanks guys.
Thanks
If a global champ finds us, deny everything 
Will do! I advise not looking at the live map and editor for San Francisco (on the USA server). You’ll go green with envy over the obviously vastly, vastly higher resolution coastline data there! Heck, unless I’m missing something, their base coastline data only gets rough when it’s mapping the individual jetties within a marina – that’s right, no the marina as a whole, but the individual jetties!
(However, I think the editors here (before me) can be justly proud - it’s gratifiying to note just how little speed limit information is present in San Francisco!). 
BTW, the update request about Murawai is here.
fixed.
When you think about it, the amount of work we have done is crazy
As time goes on we are slowly increasing the resolution.
@SMLol379
While we are speaking of increased resolution you know to avoid creating slipways and dual carriage roads.
When we start mapping it seams like a good idea but over time its makes the map look like rubbish and serves very little navigation value.