Talk:Tag:waterway=sluice gate

valve=gate

I find different issues with this value, it doesn't sound appropriate for waterway=* key as it's not a proper waterway and it duplicates valve=gate.
We'd better finding a solution to document screens, gates and locks in a consistent way instead of overloading waterway=* key that should be freed from anything else than a proper waterway. Fanfouer (talk) 17:00, 27 October 2021 (UTC)

Waterway=dam and waterway=weir have the same problem, and the solution needs to be clear on how it links to them. I think the solution involves defining a high level subkey, i.e. in the direction of the suggested waterway=flow_control, though not convinced that's the right tag. A sluice gate really isn't a valve either, so I don't consider this a duplicate though they could both fit under a different key. JoeG (talk) 20:37, 27 October 2021 (UTC)

waterway=* is full of values which aren't waterways, dams and weirs are examples. Several proposals may be needed to improve them with years of work. Nevertheless here, waterway=sluice_gate hasn't been discussed so much, rises in usage since beginning of 2021 and make things worse regarding waterway=*. I'm not sure about waterway=flow_control neither, we need to think what are the control features we want to address beside sluice gates. Note that Proposed_features/Outlets_proposal will address such gates like this small one. Fanfouer (talk) 10:07, 28 October 2021 (UTC)

How to map?

Could someone knowledgeable add a How to map section? I'm unsure as how to use this tag correctly on nodes, lines, areas. In this, I seem to be in company with josm, which complains if a waterway=sluice_gate in mapped as a way that is not connected to other waterways. -- Martianfreeloader (talk) 15:14, 11 August 2023 (UTC)