I don't think the drinkable quality of water should be the prime criteria to tag water sources (or a reason to use amenity=*) A fountain will striclty have the same external and internal design either the water is drinkable or not.
This data should be introduced with a tag drinkable=yes/no or any other values giving information about the drinkable quality of water for humans. I agree with the approach of Althio on man_made. *François Lacombe* fl dot infosreseaux At gmail dot com www.infos-reseaux.com @InfosReseaux <http://www.twitter.com/InfosReseaux> 2015-01-16 15:50 GMT+01:00 althio althio <althio.fo...@gmail.com>: > I didn't follow every bits of the discussion, so sorry for > interrupting. Sorry also if my proposals are out of scope or already > reviewed. Maybe a fresh view can help. > > @Marc amenity=drinking_water // amenity=non_drinking_water > It feels like a good start and compromise. > Either can be associated with a more physical feature that represents > an outlet of a water network. > > A few tagging examples... > > any point with drinking water: > amenity=drinking_water > + [opt] man_made=* > > a well: > man_made=water_well > + [opt] amenity=drinking_water/non_drinking_water > > a tap: > man_made=water_tap > + [opt] amenity=drinking_water/non_drinking_water > > a water point: > man_made=water_tap or man_made=water_point or man_made=water_supply or ... > + [opt] amenity=drinking_water/non_drinking_water > * currently exists amenity=water_point ... I find it a bad tag, this > one I would consider to maybe deprecate and link as a equivalent > amenity=water_point <=> amenity=drinking_water + man_made=[to_be_chosen] > > and it should not implies drinking_water=yes. > > a fountain for cultural / decorational / recreational purposes [often > not suitable for drinking]: > amenity=fountain > (man_made=fountain is maybe more logical... and here 2x amenity can clash) > * if it is drinking water, a workaround would be two features, ideally > a node amenity=drinking_water within an area (however small) > amenity=fountain. Some fountains are also detailed with an area of > natural=water. > > toilets with drinking water > amenity=toilets and amenity=drinking_water as two features (2 nodes or > area+node) > > drinking fountain > amenity=drinking_water > + [opt] man_made=* (man_made=fountain if there is a need?) > > > > Either way, the slightly conflicting tag are > amenity=[non_]drinking_water and drinking_water=yes/no. > They should be linked and treated together in algorithms. > I think amenity=drinking_water is a valuable tag because it is useful > to people. It makes sense to use it alone. > drinking_water=yes alone on a node makes less sense IMO. > > water_point and water_tap should not assume > > _______________________________________________ > Tagging mailing list > Tagging@openstreetmap.org > https://lists.openstreetmap.org/listinfo/tagging >
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
