Drinkable water group

Please do not create a new group. We already have a "Drinking Water" group, and all of that should be displayed. This includes wells with `drinking_water=yes`.

Unfortunately, water points, fountains and the like are often incorrectly tagged with "drinking_water=yes", even though the water is definitely not fit for drinking. This often applies to taps in cemeteries, which are only used for watering. But it also applies to decorative fountains. I’ve often come across ones that explicitly stated “not drinking water”, yet were still tagged with “yes”.

So you can’t rely on it anyway. Trash in, trash out...

If you notice this, you should change it in OSM immediately.

I've never had a problem with cemetery water LOL

So my point is not to solve or improve OSM tagging. It is a realy interesting point, but not a locusmap topic.
The goal of this topic is to have a solution to display tagged "amenity=fountain" + "drinking_water=yes" with lopoint.

as suggest by freischneider, using already existing "Drinking Water" groupe can be a solution. but I let people frome locus map propose us the best solution

So my point is not to solve or improve OSM tagging. That is a really interesting topic, but it is not a Locus Map topic.

The goal here is simply to find a way to display with LoPoints objects tagged:

amenity=fountain + drinking_water=yes

As suggested by freischneider, reusing the existing Drinking Water group could be one possible solution.

For example, this group could include:

amenity=drinking_water OR drinking_water=yes

The second condition would also catch other useful OSM objects where potable water is available, for example:

• natural=spring + drinking_water=yes
• man_made=water_tap + drinking_water=yes
• man_made=water_well + drinking_water=yes
• amenity=fountain + drinking_water=yes
• amenity=toilets + drinking_water=yes
• tourism=wilderness_hut + drinking_water=yes

But I leave it to the Locus Map team to decide what the best implementation would be. My main goal is simply to be able to display all known potable water points without having to display every fountain, including decorative ones.

Hi all,

I have extended (developed) configuration for "drinking water". There is no separate category. "Drinking water" is a place where one finds clean water to drink. However, places where one naturally expects drinking water are not included, even though tagged with key="drinking_water" value="yes", such as alpine huts, camp sites. This is a bit tricky, as there is clearly a big difference between small camp site at a trail and huge camp sites near busy coastline. No easy way to judge. Also: drinking_water=yes means what it says. (We trust it). The configuration was under-developed indeed.

I used an AI tool to sum-up configuration file as it is now:

Summary: drinking_water category:

This category matches OSM features representing a drinking water source. It has disused_blocks enabled, meaning disused:-prefixed variants of these tags are also recognized as no-longer-active drinking water points.

Standalone primary tags (no additional tag required):

Three tag combinations are sufficient on their own, with no supporting tags needed (logic: NA):

- amenity=drinking_water

- amenity=water_point

- waterway=water_point

Water infrastructure needing explicit confirmation:

man_made=water_tap and man_made=water_well only count as drinking water if paired with at least one (logic: ANY) of: amenity=drinking_water or drinking_water=yes. This makes sense since taps and wells aren't inherently potable — the extra tag confirms the water is safe to drink.

Amenities that may incidentally offer drinking water:

amenity=toilets, amenity=shelter, and amenity=fountain are not drinking-water features by default, but are included in this category when tagged with drinking_water=yes (logic: ANY, single possible additional here) — i.e., a toilet block, shelter, or fountain that also happens to provide potable water.

Natural/outdoor features needing confirmation:

tourism=wilderness_hut and natural=spring follow the same pattern as the water taps/wells above: either amenity=drinking_water or drinking_water=yes (logic: ANY) must also be present to qualify — a hut or spring isn't assumed drinkable unless explicitly tagged so.

Changes will be online soon, offline with new generation. Thanks for raising this issue, I basically did what Florian suggested.

Thanks, this is a great improvement!

My only concern is the use of a whitelist. There may always be other OSM objects that can legitimately have "drinking_water=yes", for example an old "amenity=lavoir".

Would it be more robust to accept "drinking_water=yes" by default, and use a blacklist only for feature types where this would be misleading?

Best regards