I see you added way/684682335 with the name Elkhorn Ridge a few months ago. Looking at the old and current USGS maps it looks like the name Elkhorn Ridge is only used for the southeastern portion. Do you have a source that confirms if htis name can also be applied from the section to the northwest? I’ve cut this off into 2 new ways: 884504461 and 884504460, where there are physical differences in the ridges. Please add back the name if you have a good source for it.

So in this area you are mapping the individual dunes as natural=ridge + landform=dune_system? But I though the dune_system tag was for areas. Would it make more sense to add a qualifier to natural=ridge, like natural=ridge + ridge=dune? Or alternately you could use natural=dune to map individual dunes. See natural=dune
If hte issue is rendering, we could certainly propose something for natural=dune at http://github.com/gravitystorm/openstreetmap-carto once the tagging is clarified.

egmont,

What does landform=dune_system ean to you when you add it in these areas? I notice it is always combined with natural=ridge or natural=sand.

Re: "That was the reason we started removing the smaller estuaries from the coastline, so edits to them would show up on the map in a timely fashion”

I’m sorry that the coastline updating process is often broken. It’s unfortunate that managing the coastline polygons is complex and can often be stopped by mistakes around the world.

However, that is not a good reason for incorrectly mapping parts of the sea as natural=water, the tag for lakes and rivers. Pamlico sound is a coastal lagoon with salinity only a little lower than that of the open ocean: according to Wikipedia it’s 20 ppm instead of the 35 ppm of the open Atlantic. This is higher salinity than the Black Sea or the Baltic sea, which are clearly part of the sea. Pamlico sound has large passageways to the open ocean and is strongly influenced by tides and ocean water flow in from the open sea.

It is comperable to Galveston Bay which also has barrier islands, and is mapped with natural=coastline appropriately. Pamlico Sound is also comperable to the coastal waters of the northern Netherlands and NW Germany, which are mapped as being outside of the coastline (see openstreetmap.de where different colors clearly show the distinction - I’ve also worked on showing this on openstreetmap.org but the PR hasn’t been accepted yet).
- Joseph Eisenberg

I disagree with mapping the entirety of Chesapeak Bay as natural=water. This bay is part of the marine environment. It is not a river or lake or even a coastal lagoon, but rather a shallow bay with an open connection to the high seas. Many of the channels along its edges are not true rivers, but rather tidal channels which are created and influenced by the bi-directional flow of water from the tides. The water is less salty than the open ocean, but that is also true of many marginal seas, including ones like Puget Sound, the Baltic Sea (which has quite low salinity) and Delaware Bay just northeast.

It is possible to map the bay as a natural=bay relation instead. If the local community really wants to map this as natural=water instead ofa. natural=bay, I suppose that’s not too harmful, as long as the ways at the edges are returned to tagged with natural=coastline like before.

Also see the discussion about this issue on the Tagging list, where there is clear support for mapping bays with natural=coastline.

I believe Indian River bay should be included in the area outside of the natural=coastline, though it’s also fine to tag it as a natural=water area too, it is a marginal part of the sea with tides and partially salty water.

Désolée, j'écris en anglais parce que je ne connais pas le français, et je pensais avoir reconnu votre nom d'utilisateur comme quelqu'un qui pouvait communiquer en anglais, mais peut-être étais-je confus.

Je suis heureux d'ajouter une traduction automatique

Je conviens qu’il est parfaitement judicieux de marquer une partie plate de cette zone comme zone humide = tidal_flat, et la partie la plus proche de la terre comme natural = beach. Et la région en Belgique a l'air bien.

Ma seule préoccupation est ici: relation/7397679#map=18/51.08910/2.54444 - où la plage et le tidal_flat se chevauchent partiellement. Était-ce intentionnel?

Sorry, I write in English because I don’t know French, and I thought I recognized your user name as someone who can communicate in English, but perhaps I was confused.

I am happy to add an automated translation (below)

I agree that it’s perfectly sensible to tag flat part of this area as a wetland=tidal_flat, and the part nearest the land as natural=beach.

My only concern is here: relation/7397679#map=18/51.08910/2.54444 - where the beach and tidal_flat are partially overlapping. Was that intentional?

51114u9, veo que usted ha empleado el “tag” landuse=industrial + industrial=fish_farm para unos areas de aquacultura in el lago de Titicaca, di mana hay criadero peces. Pero hay otro tag mas común para aquacultura: landuse=aquaculture - vease osm.wiki/ES:Tag:landuse%3Daquaculture

51114u9, veo que usted ha empleado el “tag” landuse=industrial + industrial=fish_farm para unos areas de aquacultura in el lago de Titicaca, di mana hay criadero peces. Pero hay otro tag mas común para aquacultura: landuse=aquaculture - vease osm.wiki/ES:Tag:landuse%3Daquaculture

Verdy_p, in this changeset you created relation/7397679 which is a wetland=tidal_flat, but this partially overlaps with the area of relation/10626833 - Plage de Bray-Dunes which is a natural=beach area.

I would argue that an area can be either a beach or a tidal flat, but not both.

(See https://github.com/gravitystorm/openstreetmap-carto/issues/3840#issuecomment-720113273)

I would recommend creating small areas formed with closed ways, rather than the huge multipolygons with over 1000 members (e.g. relation/11634595) - these huge relations will be hard to maintain and easy to break. Also, the woodland does not continue across roads, so it would be better to cut out the areas along roads which do not have trees. This alone would cut the areas into smaller, manageble pieces, and often it won’t be necessary to create a multipolygon instead of just using a closed way.

Seaside83,
I see you tagged way/800570757 (McGaugh Slough) as a tidal channel. Is Clear Lake tidal? I thought only seas and Great Lakes have tides. A tidal channel is "A natural intertidal waterway in mangroves, salt marshes and tidal flats with water flow in the direction of the tide” - does the water flow in this slough reverse direction twice a day?

I notice that you have used the tag waterway=tidal_channel for the narrow waterways separating several of these islands, but you also added the tag tidal=no. Usually all tidal_channel features are found in the intertidal zone, between the low and high tide line, often in areas with mud flats, salt marsh, or mangroves (in the tropics). Are these tidal channels, or perhaps are they very narrow straits which are not tidal? Or is the tidal=no tag incorrect?

"The tag tidal=yes indicates that an element is in the tidal range.” tidal=*

waterway=tidal_channel "Use waterway=tidal_channel for a natural tidal waterway within the coastal marine environment with bi-directional flow of salty water which depends on the tides. Such channels form along protected coasts with limited wave action and a gradual slope, usually within tidal mud flats, salt marshes or mangroves."

way/856751817 is tagged waterway=tidal_channel, but this looks incorrect. A tidal channel is a natural waterway next to the ocean, usually in a salt marsh or mud flat or mangroves.

I notice that you used the tag waterway=tidal_channel for short parts of this canal, which is otherwise tagged waterway=canal (correctly). Why did that happen? way/731159356
and
way/731159354
and
way/731144646
etc.
- Joseph Eisenberg

Hi Pragya Pant! Thanks for helping out with OpenStreetMap. I’m a volunteer mapper from the USA, and I noticed that you might have made a mistake on a few streams or rivers in this area. For example, way/853617622 and the ones next to it are tagged waterway=tidal_channel but that’s not right, because a tidal channel is only found next to the ocean. Try waterway=stream or waterway=river instead.
(Also see way/854112713)

नमस्ते प्रज्ञा पंत! OpenStreetMap को साथ मद्दत को लागी धन्यवाद। म संयुक्त राज्य अमेरिकाबाट एक स्वयंसेवक म्यापर हुँ, र मैले थाहा पाएँ कि तपाईले यस क्षेत्रमा केही स्ट्रिमहरू र नदिहरूमा गल्ती गरेको हुनसक्दछ। उदाहरण को लागी, way/853617622 र यसको छेउमा ट्याग गरीएको जलमार्ग = ज्वार_चैनल तर यो सहि छैन, किनकि ज्वार च्यानल मात्र समुद्रको छेउमा फेला पर्दछ। सट्टामा जलमार्ग = स्ट्रिम वा जलमार्ग = नदी प्रयास गर्नुहोस्।
(साथै way/854112713 हेर्नुहोस्)

Hi Pragya Pant! Thanks for helping out with OpenStreetMap. I’m a volunteer mapper from the USA, and I noticed that you might have made a mistake on a few streams or rivers in this area. For example, way/853617622 and the ones next to it are tagged waterway=tidal_channel but that’s not right, because a tidal channel is only found next to the ocean. Try waterway=stream or waterway=river instead.
(Also see way/854112713)

नमस्ते प्रज्ञा पंत! OpenStreetMap को साथ मद्दत को लागी धन्यवाद। म संयुक्त राज्य अमेरिकाबाट एक स्वयंसेवक म्यापर हुँ, र मैले थाहा पाएँ कि तपाईले यस क्षेत्रमा केही स्ट्रिमहरू र नदिहरूमा गल्ती गरेको हुनसक्दछ। उदाहरण को लागी, way/853617622 र यसको छेउमा ट्याग गरीएको जलमार्ग = ज्वार_चैनल तर यो सहि छैन, किनकि ज्वार च्यानल मात्र समुद्रको छेउमा फेला पर्दछ। सट्टामा जलमार्ग = स्ट्रिम वा जलमार्ग = नदी प्रयास गर्नुहोस्।
(साथै way/854112713 हेर्नुहोस्)

way/821856011 and way/821856014 and
way/821856010 and way/821856001
- these ways are tagged as "waterway=tidal_channel” but they should be waterway=river or waterway=stream. A tidal channel is only found by the sea.

这些方式被标记为“ waterway = tidal_channel”，但它们应该是waterway = river或waterway = stream。

way/813021923
and other ways in this region with waterway=tidal_channel are incorrect, they are probably streams

way/810368030 and other ways in this region with waterway=tidal_channel are incorrect, they are probably streams