Re: [Tagging] Deprecation proposal: man_made=drinking_fountain

2022-10-06 Thread Warin
On 6/10/22 10:44, Martin Koppenhoefer wrote: sent from a phone On 5 Oct 2022, at 15:26, Jass Kurn wrote: When it should be, as a suggestion, drinking_water:type=bubbler, or drinking_water:type=bottle_refill. these tags are misleading, you are not describing drinking water, hence it is

Re: [Tagging] Better term for unisex

2022-10-06 Thread martianfreeloader
That's already in use in the same proposal. gender=any - all genders allowed, unknown if there is segregation gender=segregated - all genders allowed, genders segregated gender=unisex - all genders allowed, no gender segregation I was wondering if we can replace gender=unisex by something which

Re: [Tagging] Deprecation proposal: man_made=drinking_fountain

2022-10-06 Thread Warin
On 5/10/22 22:44, Illia Marchenko wrote: Alternative to the sport=soccer is sport=british_football because "football" is context specific, and "American football", "Australian football", "Canadian football", "Gaelic football" exists. In parts of Britain 'football' is rugby ... For some

Re: [Tagging] Deprecation proposal: man_made=drinking_fountain

2022-10-06 Thread Davidoskky via Tagging
I think the above should depreciate amenity=drinking_water as it is more generic. I do like this approach, however it forces people to actually describe several features when entering data in the database rather than just writing "here you can drink". While I might like this, I think this is

Re: [Tagging] Deprecation proposal: man_made=drinking_fountain

2022-10-06 Thread ael via Tagging
On Thu, Oct 06, 2022 at 01:41:21AM +0200, Martin Koppenhoefer wrote: > > > sent from a phone > > > On 5 Oct 2022, at 15:26, Jass Kurn wrote: > > > > The tag amenity=fountain was created to map the entity/object known in > > English as fountains, and is documented in the OSM wiki with several

Re: [Tagging] Deprecation proposal: man_made=drinking_fountain

2022-10-06 Thread Martin Koppenhoefer
sent from a phone > On 6 Oct 2022, at 14:00, Davidoskky via Tagging > wrote: > > I feel that man_made=water_tap is quite useless in this regard and might very > well be substituted for a tap=yes secondary value. these are 2 completely different things, one is a feature and one is a

Re: [Tagging] Deprecation proposal: man_made=drinking_fountain

2022-10-06 Thread Martin Koppenhoefer
sent from a phone > On 6 Oct 2022, at 11:41, ael via Tagging wrote: > > Definitely not a fountain. > > These all in British English. these all fountains in German and Italian, basically any sculpture with water around it or emerging from it is a fountain, particularly if the water is in

Re: [Tagging] Deprecation proposal: man_made=drinking_fountain

2022-10-06 Thread Martin Koppenhoefer
sent from a phone > On 6 Oct 2022, at 14:00, Davidoskky via Tagging > wrote: > > For example a public tap where you can wash clothes, which I guess you could > tag as amenity=fountain, drinking_water=no but that does not differentiate it > from a decorative fountain. >

Re: [Tagging] Better term for unisex

2022-10-06 Thread Zeke Farwell
The proposal currently states: > Meaning of the unisex =yes > is currently unclear: > >- gender neutral facility (as the "unisex" term in English); or >- facility that accessible for men and women, either segregated or not. > > I do not

Re: [Tagging] Deprecation proposal: man_made=drinking_fountain

2022-10-06 Thread ael via Tagging
On Thu, Oct 06, 2022 at 05:56:03PM +0200, Martin Koppenhoefer wrote: > > > sent from a phone > > > On 6 Oct 2022, at 11:41, ael via Tagging wrote: > > > > Definitely not a fountain. > > > > These all in British English. > > > these all fountains in German and Italian, basically any

Re: [Tagging] Deprecation proposal: man_made=drinking_fountain

2022-10-06 Thread Davidoskky via Tagging
these are 2 completely different things, one is a feature and one is a property. both can be used, but typical applications will be different. Yes, I meant that there is no need for such feature since it overlaps with other features and could very well be described as a property of one of

Re: [Tagging] Deprecation proposal: man_made=drinking_fountain

2022-10-06 Thread Graeme Fitzpatrick
On Thu, 6 Oct 2022 at 22:00, Davidoskky via Tagging < tagging@openstreetmap.org> wrote: > > With all these tags, there is still no way to properly describe a place > with a pipe that provides water which is not drinkable and not decorative. > Throwing another one into the mix - taps in camp

[Tagging] A broader tagging perspective (was Deprecation proposal: man_made=drinking_fountain)

2022-10-06 Thread stevea
"Viewing from higher altitudes" here, it should be said that "tagging," tagging improvements, "how we better tag into the future..." all seem to be getting more difficult as OSM grows. One fundamental that just emerged is "no need for such a feature since it overlaps with other features and

Re: [Tagging] Deprecation proposal: man_made=drinking_fountain

2022-10-06 Thread Mateusz Konieczny via Tagging
Oct 7, 2022, 01:05 by tagging@openstreetmap.org: >> these are 2 completely different things, one is a feature and one is a >> property. >> >> both can be used, but typical applications will be different. >> > > Yes, I meant that there is no need for such feature since it overlaps with >

Re: [Tagging] Deprecation proposal: man_made=drinking_fountain

2022-10-06 Thread stevea
Yes, I agree with Mateusz: I would find deprecation of amenity=drinking_water to be highly problematic. It is a very long-established tag. On Oct 6, 2022, at 10:06 PM, Mateusz Konieczny via Tagging wrote: > But I am very dubious about deprecation of amenity=drinking_water, even > if