Proposal talk:Drinking water attributes

These are just ideas and questionable places:

• chilled=yes/no if you add this tag then how do you whether this place gives only chilled water or also "normal" water? Also some places might give hot water.
• taste is not verifiable, so do not include this!
  • +1. Subjective tags like that are avoided in OSM --Pieren 12:15, 26 August 2011 (BST)
• repair=working/needs_repair/broken probably a better key would be something like state/condition because repair is currently used to indicate whether facility offers repairs for whatever they deal with (condition is also not good as it is used with roads and its typical values do not suit here). RM87 09:06, 24 August 2011 (GMT)

One more general comment: if you include this into the main page, add a comment saying it is all optional. --Pieren 12:15, 26 August 2011 (BST)

• Consider how this interacts with natural=spring. In some places the difference between a spring and a drinking fountain could be hard to define. Stevage 09:51, 29 August 2011 (BST)
• Also, is it not preferable to make all these attributes proper subtags: drinking_water:dog=yes is a lot clearer than "dog=yes". Stevage 09:51, 29 August 2011 (BST)
  • I agree, that just seems so verbose and cluttery. Should I do it anyway? Brycenesbitt 20:06, 31 August 2011 (BST)
    • Yeah, there are plenty of other tags that work this way (eg, the ski piste stuff). Stevage 05:30, 12 September 2011 (BST)

• I hope we can adapt the proposal to include waterpoints as shown in the picture below. Some tags that have been used by Mapkibera so far, you can find on their wiki. Would be great if we can merge the drinking water bit into this official proposal. Reinier 11:53, 14 September 2011 (EAT)

Images

Typical Urban Drinking Water collection point in Africa

A bubbler with drinking_water:bottle=yes bottle-filling facility

Please prefix, write as drinking_water:*=*

Many of these tags are not very general and should be rewritten in the drinking_water:<subkey>=<value> style. I'd suggest:

• bottle=* → drinking_water:fill_bottle=*. This is pretty specific to drinking water sources, and may have other meanings elsewhere. Better say that it's about being able to fill a bottle too.
• level=* General and already in widespread use. Applies to any object you might find inside a building, no need to specify separately, just move to Useful Combinations and link.
• maintenance=* → General and already in use; but consider disused=* or abandoned=*. Or maybe even better, let's raise maintenance=* as a separate tag write-up (hint: check taginfo for values in common use)
• maintenance:note=* As maintenance=*, but consider using note=*. There are no instances of this in the db at the time of writing.
• image=* General and already in limited use. Applies to any object you might find inside a building, no need to specify separately, just link.
• drinking_water:style=* Looks good; maybe just drinking_water=<style> though if that doesn't conflict with the emergent drinking_water=no. I think the two can coexist, and I like the animal=fish fish=trout trout=rainbow_trout style of tagging notation.
• chilled=* → drinking_water:chilled=* → Since the meaning is not that the thing itself is chilled but that what it provides is chilled, I think this is better. I know. Picky.
• dog=* → drinking_water:dog=* → Because it's not so much that dogs can access it, but that they can drink from it. Parodying myself: drinking_water:fill_dog=*.
• operator=* Perfectly general, not even any need to specify this, just move to Useful Combinations and provide a link.
• taste=* → drinking_water:taste=* definitely. It's both subjective and specific to things that can be tasted (politely).

--achadwick 13:02, 29 November 2011 (UTC)