Re: [Tagging] Is it man_made=water_tap?
Water "tap" implies at least some (even if crude) control of the flow. I don't know where the rest of it goes, but if you are "tapping" water (at a drinking fountain, a sink, as a plumber...), you strongly imply, if not guarantee, that you allow some control over the flow of it. To call it a water "tap" automatically (in my mind, understanding, life-long experience...) means "valve" (somehow, somewhere, and if there isn't one, and you are a plumber, perhaps it is Job 1 to install a valve). ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Is it man_made=water_tap?
I expanded https://wiki.openstreetmap.org/wiki/Tag:man_made%3Dwater_tap
based on discussion here and what I researched while implementing
https://github.com/streetcomplete/StreetComplete/pull/4423
("How is drinking water provided here?")
Feel free to improve that wiki page (and others) if I put something
incorrect there and to expand it if needed.
Sep 28, 2022, 00:29 by graemefi...@gmail.com:
> I would say that regardless of how it's operated - turn handle, push button,
> lever, foot pedal, auto sensor etc - that if water comes out, it's a tap!
>
> Thanks
>
> Graeme
>
>
> On Tue, 27 Sept 2022 at 23:20, Mateusz Konieczny via Tagging <>
> tagging@openstreetmap.org> > wrote:
>
>>
>>
>>
>> Sep 27, 2022, 14:58 by >> dieterdre...@gmail.com>> :
>>
>>>
>>>
>>> sent from a phone
>>>
On 27 Sep 2022, at 14:52, Georg < georg2...@nurfuerspam.de > wrote:
IMHO yes.
>>>
>>>
>>> I agree, although I wouldn’t see it necessary to characterize the feature
>>>
>> I see value in mapping whether given amenity=drinking_water
>> is a proper tap or just providing miserable jet of water making
>> impossible to fill water bottle.
>>
>> Also, I noticed that many bare amenity=drinking_water are in
>> various ways quite likely to be problematic
>> (misplaced, used for water taps without drinkable water or
>> inaccessible to public and soon)
>> ___
>> Tagging mailing list
>> >> Tagging@openstreetmap.org
>> >> https://lists.openstreetmap.org/listinfo/tagging
>>
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
[Tagging] Can we assume surface=cobblestone:flattened to be an exact duplicate of surface=sett?
So far I assumed that surface=cobblestone:flattened is an exact duplicate of surface=sett but looking at https://lists.openstreetmap.org/pipermail/tagging/2018-January/thread.html#34931 https://wiki.openstreetmap.org/wiki/Template:Map_Features:surface https://wiki.openstreetmap.org/w/index.php?title=Tag:surface%3Dcobblestone:flattened=edit=1 it seems to not be actually true. I am asking as - I want to document also this surface value - I am considering treating it as a missing data in StreetComplete (and ask user to provide surface info, like for missing surface value) - Right now in the upcoming surface edit mode it is treated as surface=sett synonym - maybe it should be changed and be treated as missing surface info So how it should be treated? Like surface=cobblestone where it can be surface=sett or surface=unhewn_cobblestone so ideally it would be retagged with more specific values? ( https://wiki.openstreetmap.org/wiki/Tag:surface%3Dcobblestone ) ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Feature Proposal - RFC - Bench: replace seats by capacity
This person's opinion: I very much like capacity with amenity=bench, especially when it is "significantly greater than two or three," though I also see great merit in saying capacity=1 to emphasize "single-seat only" in some cases where that might be or is unusual, or even usual! Y'know, this could go in many directions from here, too, like "children-sized" or "extra-large sized" (there are such humans on this planet). But I'm getting ahead of myself. Good for us; sweet blend, bench + capacity. Tag. Tag accurately! Even succinctly, as we can here. If it grows to more than two tags, it does. What's nice is "we get to pick which (two, three...) tags." More than one tag can and certainly is/are true about a particular (node, way, relation) in our map. Cleverly, "we choose which." Nice map we have here. ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Feature Proposal - RFC - Bench: replace seats by capacity
I have stopped tagging seats, because most benches do not have seats. Capacity is ok with me, I will start using that, but still I don't think I will tag that very often, unless it's a huge bench for 20 (I have seen one!) or a very small one for 1 person. I don't mind if others tag seats or estimate the capacity different, as long as they don't remove my capacity tag. Peter Elderson Op do 29 sep. 2022 om 14:10 schreef martianfreeloader < martianfreeloa...@posteo.net>: > Facing heavy objections and no support, I have come to the conclusion > that my proposal is not considered useful by the community. > > I thus decided to retract it. > > ___ > Tagging mailing list > Tagging@openstreetmap.org > https://lists.openstreetmap.org/listinfo/tagging > ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Feature Proposal - RFC - Bench: replace seats by capacity
Most times, I don't map the number of seats, because I don't have a number of 3-4 friends with me when I'm mapping to test the bench, so I can't tell how many people can sit on it. They installed a few 1-seater "benches" in my locality during lockdown, I added it then. But I agree that it might make it easier to simplify from seats to capacity. Anne On 29/09/2022 17:26, martianfreeloader wrote: I personally find it more consistent to reduce the number of synonymous keys across all objects. But yes, I am considering two groups of mutually exclusive proposals to settle this issue. Something along these lines: - ISSUE 1 Should the capacity of a bench be tagged on all benches or only on those which have clear seat separation? This is independent of issue 2. Proposal 1A) Only on benches with have clear seat separation. Proposal 1B) On all benches. Question to be resolved: Can a thing that has individual seats be considered a bench at all? --- ISSUE 2: Which key should be used to tag the capacity of a bench? This is independent of issue 1. Proposal 2A) Use seats=* on all benches. Proposal 2B) Use capacity=* on all benches. Proposal 2C) [Only if 1B is approved] Use seats=* on benches with clear seat separation and capacity=* otherwise. --- This is just a sketch, let's see if I have time to spell this it out in the next days. On 29/09/2022 17:19, Martin Koppenhoefer wrote: sent from a phone On 29 Sep 2022, at 14:10, martianfreeloader wrote: Facing heavy objections and no support, I have come to the conclusion that my proposal is not considered useful by the community. I thus decided to retract it. as you are interested in consistency, have you considered proposing the opposite, retagging of the 1000 capacity on benches to seats? Cheers Martin ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Feature Proposal - RFC - Bench: replace seats by capacity
I personally find it more consistent to reduce the number of synonymous keys across all objects. But yes, I am considering two groups of mutually exclusive proposals to settle this issue. Something along these lines: - ISSUE 1 Should the capacity of a bench be tagged on all benches or only on those which have clear seat separation? This is independent of issue 2. Proposal 1A) Only on benches with have clear seat separation. Proposal 1B) On all benches. Question to be resolved: Can a thing that has individual seats be considered a bench at all? --- ISSUE 2: Which key should be used to tag the capacity of a bench? This is independent of issue 1. Proposal 2A) Use seats=* on all benches. Proposal 2B) Use capacity=* on all benches. Proposal 2C) [Only if 1B is approved] Use seats=* on benches with clear seat separation and capacity=* otherwise. --- This is just a sketch, let's see if I have time to spell this it out in the next days. On 29/09/2022 17:19, Martin Koppenhoefer wrote: sent from a phone On 29 Sep 2022, at 14:10, martianfreeloader wrote: Facing heavy objections and no support, I have come to the conclusion that my proposal is not considered useful by the community. I thus decided to retract it. as you are interested in consistency, have you considered proposing the opposite, retagging of the 1000 capacity on benches to seats? Cheers Martin ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Feature Proposal - RFC - Bench: replace seats by capacity
sent from a phone > On 29 Sep 2022, at 14:10, martianfreeloader > wrote: > > Facing heavy objections and no support, I have come to the conclusion that my > proposal is not considered useful by the community. > > I thus decided to retract it. as you are interested in consistency, have you considered proposing the opposite, retagging of the 1000 capacity on benches to seats? Cheers Martin ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Feature Proposal - RFC - Mobile apps
Hi, I have added a few comments in the wiki. Davide On 29/09/22 10:18, Martin Fischer wrote: Hey everybody, I just drafted a proposal to formalize app:* which is currently used in Sweden to link Android & iOS apps of pharmacies. My proposal also addresses the inconsistency between the currently in use app:apple, app:google, payment:app:android and payment:app:ios. https://wiki.openstreetmap.org/wiki/Proposal:Mobile_apps Please discuss this proposal on its Wiki Talk page. Best, Martin ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Feature Proposal - RFC - Bench: replace seats by capacity
Facing heavy objections and no support, I have come to the conclusion that my proposal is not considered useful by the community. I thus decided to retract it. ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
[Tagging] Feature Proposal - RFC - Clothing
Clothing policy of the facility (old proposal, but renewed). https://wiki.openstreetmap.org/w/index.php?title=Proposed_features/Clothing Please discuss this proposal on its Wiki Talk page. ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
[Tagging] Feature Proposal - RFC - Bench: replace seats by capacity
I propose to stop using seats=* on benches. Instead, capacity=* should be used. For details, see the proposal: https://wiki.openstreetmap.org/wiki/Proposed_features/Bench:_replace_seats_by_capacity Please discuss this proposal on its Wiki Talk page. ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Is it man_made=water_tap?
On 29/9/22 18:03, Martin Koppenhoefer wrote: sent from a phone On 29 Sep 2022, at 09:43, Warin <61sundow...@gmail.com> wrote: particularly to distinguish different drinking fountain types <#> Am Mi., 28. Sept. 2022 um 10:45 Uhr schrieb Warin <61sundow...@gmail.com>: I would not use the tag man_made=water_tap for these. Why not use https://wiki.openstreetmap.org/wiki/Key:fountain You will note the different tags - some relate to the 'style' of the structure others relate to the water delivery eg mist, bottle_refill .. thus the tag is used for anything. The word 'type' in the description is the probable source of this confusion. We introduced the fountain tag particularly to distinguish different drinking fountain types I think you mean "different drinking fountain apperance"? no, I mean types And what do you mean by 'drinking fountain types'? Read the bottom first... possibly "different drinking fountain water flow"? that could be a different tag , on the other hand it could still be seen as kind of the same property. Err no. They are different properties - visual appearance vs water flow. it is about fountain typologies according to the system that fountain proposes (arguably it is not complete or finished). “bottle refill” which you mentioned as outlier, as far as I understand it, is used for specific machines built to refill water bottles (or glasses), not for any kind of fountain where you can refill a bottle (sometimes it is not geometrically possible/convenient to do it, eg bubblers). Also “mist” can be seen as a type of fountain, as is splash pad. It is true that sometimes the kind of water flow is implied, but this is not the criterion in general Present on the fountain page; Styles? nasone 'style' Literally meaning "large nose" toret 'style' The water is running out of an iron cast bull's head. roman_wolf 'style' water is running out of an iron cast wolf's head and for easier drinking there is a hole on the top where the water ejects when you cap the lower hole. wallace 'style' green cast iron Possibly these could have designer=wallace?, material=cast_iron and colour=green Material? stone_block - 'material' .. so use the key material? Water delivery? nozzle mist bubbler splash_pad ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
[Tagging] Feature Proposal - RFC - Mobile apps
Hey everybody, I just drafted a proposal to formalize app:* which is currently used in Sweden to link Android & iOS apps of pharmacies. My proposal also addresses the inconsistency between the currently in use app:apple, app:google, payment:app:android and payment:app:ios. https://wiki.openstreetmap.org/wiki/Proposal:Mobile_apps Please discuss this proposal on its Wiki Talk page. Best, Martin ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Is it man_made=water_tap?
sent from a phone > On 29 Sep 2022, at 09:43, Warin <61sundow...@gmail.com> wrote: > >> particularly to distinguish different drinking fountain types >> >> I think you mean "different drinking fountain apperance"? >> > > I think you mean "different drinking fountain apperance"? > no, I mean types > possibly "different drinking fountain water flow"? > that could be a different tag > >> , on the other hand it could still be seen as kind of the same property. > > Err no. They are different properties - visual appearance vs water flow. > it is about fountain typologies according to the system that fountain proposes (arguably it is not complete or finished). “bottle refill” which you mentioned as outlier, as far as I understand it, is used for specific machines built to refill water bottles (or glasses), not for any kind of fountain where you can refill a bottle (sometimes it is not geometrically possible/convenient to do it, eg bubblers). Also “mist” can be seen as a type of fountain, as is splash pad. It is true that sometimes the kind of water flow is implied, but this is not the criterion in general Cheers Martin ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Is it man_made=water_tap?
On 28/9/22 21:26, Martin Koppenhoefer wrote: Am Mi., 28. Sept. 2022 um 10:45 Uhr schrieb Warin <61sundow...@gmail.com>: I would not use the tag man_made=water_tap for these. Why not use https://wiki.openstreetmap.org/wiki/Key:fountain You will note the different tags - some relate to the 'style' of the structure others relate to the water delivery eg mist, bottle_refill .. thus the tag is used for anything. The word 'type' in the description is the probable source of this confusion. We introduced the fountain tag particularly to distinguish different drinking fountain types I think you mean "different drinking fountain apperance"? around here. You are right that somebody has "hijacked" the key and uses it with values like "mist", and "bottle_refill", which seem to be describing something slightly different possibly "different drinking fountain water flow"? , on the other hand it could still be seen as kind of the same property. Err no. They are different properties - visual appearance vs water flow. ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
