I think a bench is one seat with a given capacity. Therefore, it's prudent to map it and tag capacity=*, rather than seats=*.
Wish you a mappy end of month. On Fri, Sep 30, 2022, 5:09 AM <tagging-requ...@openstreetmap.org> wrote: > Send Tagging mailing list submissions to > tagging@openstreetmap.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.openstreetmap.org/listinfo/tagging > or, via email, send a message with subject or body 'help' to > tagging-requ...@openstreetmap.org > > You can reach the person managing the list at > tagging-ow...@openstreetmap.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Tagging digest..." > > > Today's Topics: > > 1. Re: Feature Proposal - RFC - Bench: replace seats by capacity > (martianfreeloader) > 2. Re: Feature Proposal - RFC - Mobile apps (Davidoskky) > 3. Re: Feature Proposal - RFC - Bench: replace seats by capacity > (Martin Koppenhoefer) > 4. Re: Feature Proposal - RFC - Bench: replace seats by capacity > (martianfreeloader) > 5. Re: Feature Proposal - RFC - Bench: replace seats by capacity > (Anne-Karoline Distel) > 6. Re: Feature Proposal - RFC - Bench: replace seats by capacity > (Peter Elderson) > 7. Re: Feature Proposal - RFC - Bench: replace seats by capacity > (stevea) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 29 Sep 2022 11:58:35 +0000 > From: martianfreeloader <martianfreeloa...@posteo.net> > To: tagging@openstreetmap.org > Subject: Re: [Tagging] Feature Proposal - RFC - Bench: replace seats > by capacity > Message-ID: <c29a78f8-315c-4dba-e4af-e4371d96f...@posteo.net> > Content-Type: text/plain; charset=UTF-8; format=flowed > > 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. > > > > ------------------------------ > > Message: 2 > Date: Thu, 29 Sep 2022 14:10:25 +0200 > From: Davidoskky <davidos...@yahoo.it> > To: tagging@openstreetmap.org > Subject: Re: [Tagging] Feature Proposal - RFC - Mobile apps > Message-ID: <693129da-c6e8-cb0b-5e3d-8992db7b3...@yahoo.it> > Content-Type: text/plain; charset=UTF-8; format=flowed > > 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 > > > > ------------------------------ > > Message: 3 > Date: Thu, 29 Sep 2022 17:19:51 +0200 > From: Martin Koppenhoefer <dieterdre...@gmail.com> > To: "Tag discussion, strategy and related tools" > <tagging@openstreetmap.org> > Subject: Re: [Tagging] Feature Proposal - RFC - Bench: replace seats > by capacity > Message-ID: <01e0cfda-c88f-4032-9e81-cbfc7936e...@gmail.com> > Content-Type: text/plain; charset=us-ascii > > > > sent from a phone > > > On 29 Sep 2022, at 14:10, martianfreeloader < > martianfreeloa...@posteo.net> 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 > > > ------------------------------ > > Message: 4 > Date: Thu, 29 Sep 2022 16:26:59 +0000 > From: martianfreeloader <martianfreeloa...@posteo.net> > To: tagging@openstreetmap.org > Subject: Re: [Tagging] Feature Proposal - RFC - Bench: replace seats > by capacity > Message-ID: <fb7fc43d-7b96-f137-3bb8-d5bfb26e4...@posteo.net> > Content-Type: text/plain; charset=UTF-8; format=flowed > > 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 < > martianfreeloa...@posteo.net> 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 > > > > ------------------------------ > > Message: 5 > Date: Thu, 29 Sep 2022 18:11:15 +0100 > From: Anne-Karoline Distel <annekadis...@web.de> > To: tagging@openstreetmap.org > Subject: Re: [Tagging] Feature Proposal - RFC - Bench: replace seats > by capacity > Message-ID: <548d2caf-9889-ad61-a06a-8f7245adb...@web.de> > Content-Type: text/plain; charset=UTF-8; format=flowed > > 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 > >>> <martianfreeloa...@posteo.net> 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 > > > > ------------------------------ > > Message: 6 > Date: Thu, 29 Sep 2022 19:41:09 +0200 > From: Peter Elderson <pelder...@gmail.com> > To: "Tag discussion, strategy and related tools" > <tagging@openstreetmap.org> > Subject: Re: [Tagging] Feature Proposal - RFC - Bench: replace seats > by capacity > Message-ID: > <CAKf= > p+uhrmawgocb7+oahrnoubq2jlainzc9b39oei2-kbc...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > 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 > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://lists.openstreetmap.org/pipermail/tagging/attachments/20220929/a96750b4/attachment-0001.htm > > > > ------------------------------ > > Message: 7 > Date: Thu, 29 Sep 2022 19:06:42 -0700 > From: stevea <stevea...@softworkers.com> > To: "Tag discussion, strategy and related tools" > <tagging@openstreetmap.org> > Subject: Re: [Tagging] Feature Proposal - RFC - Bench: replace seats > by capacity > Message-ID: <a14a5da1-fd76-415d-8e5f-6ad7a0735...@softworkers.com> > Content-Type: text/plain; charset=us-ascii > > 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. > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Tagging mailing list > Tagging@openstreetmap.org > https://lists.openstreetmap.org/listinfo/tagging > > > ------------------------------ > > End of Tagging Digest, Vol 156, Issue 68 > **************************************** >
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
