I found a shop in the sea, 50 km off the coast. It’s being addressed.
However, seeing as 71% of the planet is water, I think it would be naïve to not expect errors like this to happen from time to time. And have happened many times before - Null Island and all that.
However, how does one de-bug the sea? Noting that that there will be valid communications, energy, military, fishing, scientific and other objects in the sea. However, if it is a shop, factory, mountain peak or outdoor electrical substation, then it should be looked at critically.
PS Once, my brother drove his car onto a beach. His GPS unit loudly announced “You are now in the water”.
I’d suspect the first pass would be to do an overpass query for (say) any amenity or shop that is not inside a international (country) boundary (relation? admin_level=2), for an optional boundary box. Haven’t ever done this (or anything like) so cant figure how without lots of reading!
mkgmap, the tool for creating OSM based maps for Garmin navigation devices takes sea/land boundaries as an input. Perhaps that would help with a warning!
Back in 2018, during a drought, we were camping at a dam. While there, we drove along the track more or less following the shoreline #1, till we got up close to the wall #2. No issue with that, but OSMAnd told us that the track was at #3, & the view of the wall was from #4!
If you have a (multi)polygon that describes the “sea” area (parts of oceans, etc. as GeoJSON or WKT), you can use it as the --area (-a) argument of a GOL query:
gol map world [shop],[amenity],[tourism] -a ocean.geojson -e
This displays all elements tagged shop, amenity or tourism that lie (at least partially) inside the ocean area (Click them to edit/delete in iD).
Under the sea Under the sea Darling it’s better Down where it’s wetter Take it from me Up on the shore they work all day Out in the sun they slave away While we’re devotin’ Full time to floatin’ Under the sea
It’s being addressed.
Under the sea
