<html>
<head>
<style style="display:none;" type="text/css"><!-- P {margin-top:0;margin-bottom:0;} --></style>
<meta name="viewport" content="width=device-width">
<meta http-equiv="Content-Type" content="text/vnd.ui.insecure+html;charset=utf-8">
</head>
<body dir="ltr" style="overflow-wrap:break-word; word-break: break-word;"><div class="mail_android_message" style="line-height: 1; padding: 0.5em">Thanks, but I don't think our medieval pavement adheres to European industrial standards. Also, benches along hiking trails etc. I should just being a measuring tape with me, I suppose.<br/><br/>--<br/>Sent from my Android phone with <a href="http://WEB.DE">WEB.DE</a> Mail. Please excuse my brevity.</div><div class="mail_android_quote" style="line-height: 1; padding: 0.3em"><html><body>On 30/09/2022, 11:02 St Niklaas <st.niklaas@live.nl> wrote:</body></html><blockquote class="gmail_quote" style="margin: 0.8ex 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div id="signature_bookmark"></div>
<div id="appendonsend"></div>
<div class="elementToProof" style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<p class="MsoNormal" style="margin:0cm 0cm 10pt;font-size:11pt;font-family:"Calibri", sans-serif;margin-bottom:0cm"> <span class="ContentPasted0" style="font-size:12.0pt;mso-ascii-font-family:Calibri;mso-fareast-font-family:"Times New Roman";mso-hansi-font-family:Calibri;mso-bidi-font-family:Calibri;color:black;mso-ansi-language:EN-CA;mso-fareast-language:NL">Hi Anne, </span></p>
<p class="MsoNormal" style="margin:0cm 0cm 10pt;font-size:11pt;font-family:"Calibri", sans-serif;margin-bottom:0cm"> <span style="font-size:12.0pt;mso-ascii-font-family:Calibri;mso-fareast-font-family:"Times New Roman";mso-hansi-font-family:Calibri;mso-bidi-font-family:Calibri;color:black;mso-ansi-language:EN-CA;mso-fareast-language:NL"> </span></p>
<p class="MsoNormal" style="margin:0cm 0cm 10pt;font-size:11pt;font-family:"Calibri", sans-serif;margin-bottom:0cm"> <span class="ContentPasted0" style="font-size:12.0pt;mso-ascii-font-family:Calibri;mso-fareast-font-family:"Times New Roman";mso-hansi-font-family:Calibri;mso-bidi-font-family:Calibri;color:black;mso-ansi-language:EN-CA;mso-fareast-language:NL">By lack of friends use your elbows they wont mind. </span></p>
<p class="MsoNormal" style="margin:0cm 0cm 10pt;font-size:11pt;font-family:"Calibri", sans-serif;margin-bottom:0cm"> <span class="ContentPasted0" style="font-size:12.0pt;mso-ascii-font-family:Calibri;mso-fareast-font-family:"Times New Roman";mso-hansi-font-family:Calibri;mso-bidi-font-family:Calibri;color:black;mso-ansi-language:EN-CA;mso-fareast-language:NL">A seat with friends is 0.50 m closely of cosey. With a 'normal' format of strangers its about 0.60 the length of the top of your stretch fingers up to the backside of your elbow. But an estimated guess would do as well or the size of the pavement could be helpful as well.</span></p>
<p class="MsoNormal" style="margin:0cm 0cm 10pt;font-size:11pt;font-family:"Calibri", sans-serif;margin-bottom:0cm"> <span class="ContentPasted0" style="font-size:12.0pt;mso-ascii-font-family:Calibri;mso-fareast-font-family:"Times New Roman";mso-hansi-font-family:Calibri;mso-bidi-font-family:Calibri;color:black;mso-fareast-language:NL">A tile is 0.30 x 0.30 or 0.40 x 0.60 regular size and a kerbstone is 1.00 length. Take you’re pick. </span></p>
<p class="MsoNormal" style="margin:0cm 0cm 10pt;font-size:11pt;font-family:"Calibri", sans-serif;margin-bottom:0cm"> <span style="font-size:12.0pt;mso-ascii-font-family:Calibri;mso-fareast-font-family:"Times New Roman";mso-hansi-font-family:Calibri;mso-bidi-font-family:Calibri;color:black;mso-fareast-language:NL"> </span></p>
<p class="MsoNormal" style="margin:0cm 0cm 10pt;font-size:11pt;font-family:"Calibri", sans-serif;margin-bottom:0cm"> <span class="ContentPasted0" style="font-size:12.0pt;mso-ascii-font-family:Calibri;mso-fareast-font-family:"Times New Roman";mso-hansi-font-family:Calibri;mso-bidi-font-family:Calibri;color:black;mso-fareast-language:NL">Greetz </span></p>
<br>
</div>
<hr style="display:inline-block; width:98%">
<div dir="ltr" id="divRplyFwdMsg">
<font color="#000000" face="Calibri, sans-serif" style="font-size:11pt"><b>Van:</b> tagging-request@openstreetmap.org <tagging-request@openstreetmap.org><br> <b>Verzonden:</b> vrijdag 30 september 2022 04:07<br> <b>Aan:</b> tagging@openstreetmap.org <tagging@openstreetmap.org><br> <b>Onderwerp:</b> Tagging Digest, Vol 156, Issue 68</font>
<div>
</div>
</div>
<div class="BodyFragment">
<font size="2"><span style="font-size:11pt">
<div class="PlainText">
Send Tagging mailing list submissions to
<br> tagging@openstreetmap.org
<br>
<br> To subscribe or unsubscribe via the World Wide Web, visit
<br> <a href="https://lists.openstreetmap.org/listinfo/tagging"> https://lists.openstreetmap.org/listinfo/tagging</a>
<br> or, via email, send a message with subject or body 'help' to
<br> tagging-request@openstreetmap.org
<br>
<br> You can reach the person managing the list at
<br> tagging-owner@openstreetmap.org
<br>
<br> When replying, please edit your Subject line so it is more specific
<br> than "Re: Contents of Tagging digest..."
<br>
<br>
<br> Today's Topics:
<br>
<br> 1. Re: Feature Proposal - RFC - Bench: replace seats by capacity
<br> (martianfreeloader)
<br> 2. Re: Feature Proposal - RFC - Mobile apps (Davidoskky)
<br> 3. Re: Feature Proposal - RFC - Bench: replace seats by capacity
<br> (Martin Koppenhoefer)
<br> 4. Re: Feature Proposal - RFC - Bench: replace seats by capacity
<br> (martianfreeloader)
<br> 5. Re: Feature Proposal - RFC - Bench: replace seats by capacity
<br> (Anne-Karoline Distel)
<br> 6. Re: Feature Proposal - RFC - Bench: replace seats by capacity
<br> (Peter Elderson)
<br> 7. Re: Feature Proposal - RFC - Bench: replace seats by capacity
<br> (stevea)
<br>
<br>
<br> ----------------------------------------------------------------------
<br>
<br> Message: 1
<br> Date: Thu, 29 Sep 2022 11:58:35 +0000
<br> From: martianfreeloader <martianfreeloader@posteo.net>
<br> To: tagging@openstreetmap.org
<br> Subject: Re: [Tagging] Feature Proposal - RFC - Bench: replace seats
<br> by capacity
<br> Message-ID: <c29a78f8-315c-4dba-e4af-e4371d96fe68@posteo.net>
<br> Content-Type: text/plain; charset=UTF-8; format=flowed
<br>
<br> Facing heavy objections and no support, I have come to the conclusion
<br> that my proposal is not considered useful by the community.
<br>
<br> I thus decided to retract it.
<br>
<br>
<br>
<br> ------------------------------
<br>
<br> Message: 2
<br> Date: Thu, 29 Sep 2022 14:10:25 +0200
<br> From: Davidoskky <davidoskky@yahoo.it>
<br> To: tagging@openstreetmap.org
<br> Subject: Re: [Tagging] Feature Proposal - RFC - Mobile apps
<br> Message-ID: <693129da-c6e8-cb0b-5e3d-8992db7b3f6c@yahoo.it>
<br> Content-Type: text/plain; charset=UTF-8; format=flowed
<br>
<br> Hi,
<br>
<br> I have added a few comments in the wiki.
<br>
<br>
<br> Davide
<br>
<br> On 29/09/22 10:18, Martin Fischer wrote:
<br> > Hey everybody,
<br> >
<br> > I just drafted a proposal to formalize app:* which is currently used
<br> > in Sweden to link Android & iOS apps of pharmacies.
<br> > My proposal also addresses the inconsistency between the currently in
<br> > use app:apple, app:google, payment:app:android and payment:app:ios.
<br> >
<br> > <a href="https://wiki.openstreetmap.org/wiki/Proposal:Mobile_apps"> https://wiki.openstreetmap.org/wiki/Proposal:Mobile_apps</a>
<br> >
<br> > Please discuss this proposal on its Wiki Talk page.
<br> >
<br> > Best,
<br> > Martin
<br> >
<br> > _______________________________________________
<br> > Tagging mailing list
<br> > Tagging@openstreetmap.org
<br> > <a href="https://lists.openstreetmap.org/listinfo/tagging"> https://lists.openstreetmap.org/listinfo/tagging</a>
<br>
<br>
<br>
<br> ------------------------------
<br>
<br> Message: 3
<br> Date: Thu, 29 Sep 2022 17:19:51 +0200
<br> From: Martin Koppenhoefer <dieterdreist@gmail.com>
<br> To: "Tag discussion, strategy and related tools"
<br> <tagging@openstreetmap.org>
<br> Subject: Re: [Tagging] Feature Proposal - RFC - Bench: replace seats
<br> by capacity
<br> Message-ID: <01E0CFDA-C88F-4032-9E81-CBFC7936EA6B@gmail.com>
<br> Content-Type: text/plain; charset=us-ascii
<br>
<br>
<br>
<br> sent from a phone
<br>
<br> > On 29 Sep 2022, at 14:10, martianfreeloader <martianfreeloader@posteo.net> wrote:
<br> >
<br> > Facing heavy objections and no support, I have come to the conclusion that my proposal is not considered useful by the community.
<br> >
<br> > I thus decided to retract it.
<br>
<br>
<br> as you are interested in consistency, have you considered proposing the opposite, retagging of the 1000 capacity on benches to seats?
<br>
<br> Cheers Martin
<br>
<br>
<br> ------------------------------
<br>
<br> Message: 4
<br> Date: Thu, 29 Sep 2022 16:26:59 +0000
<br> From: martianfreeloader <martianfreeloader@posteo.net>
<br> To: tagging@openstreetmap.org
<br> Subject: Re: [Tagging] Feature Proposal - RFC - Bench: replace seats
<br> by capacity
<br> Message-ID: <fb7fc43d-7b96-f137-3bb8-d5bfb26e4ff8@posteo.net>
<br> Content-Type: text/plain; charset=UTF-8; format=flowed
<br>
<br> I personally find it more consistent to reduce the number of synonymous
<br> keys across all objects.
<br>
<br> But yes, I am considering two groups of mutually exclusive proposals to
<br> settle this issue. Something along these lines:
<br>
<br> -----
<br> ISSUE 1
<br> Should the capacity of a bench be tagged on all benches or only on those
<br> which have clear seat separation? This is independent of issue 2.
<br>
<br> Proposal 1A) Only on benches with have clear seat separation.
<br>
<br> Proposal 1B) On all benches.
<br>
<br> Question to be resolved:
<br> Can a thing that has individual seats be considered a bench at all?
<br>
<br> -------
<br>
<br> ISSUE 2:
<br> Which key should be used to tag the capacity of a bench? This is
<br> independent of issue 1.
<br>
<br> Proposal 2A) Use seats=* on all benches.
<br>
<br> Proposal 2B) Use capacity=* on all benches.
<br>
<br> Proposal 2C) [Only if 1B is approved] Use seats=* on benches with clear
<br> seat separation and capacity=* otherwise.
<br> -------
<br>
<br> This is just a sketch, let's see if I have time to spell this it out in
<br> the next days.
<br>
<br>
<br>
<br>
<br> On 29/09/2022 17:19, Martin Koppenhoefer wrote:
<br> >
<br> >
<br> > sent from a phone
<br> >
<br> >> On 29 Sep 2022, at 14:10, martianfreeloader <martianfreeloader@posteo.net> wrote:
<br> >>
<br> >> Facing heavy objections and no support, I have come to the conclusion that my proposal is not considered useful by the community.
<br> >>
<br> >> I thus decided to retract it.
<br> >
<br> >
<br> > as you are interested in consistency, have you considered proposing the opposite, retagging of the 1000 capacity on benches to seats?
<br> >
<br> > Cheers Martin
<br> > _______________________________________________
<br> > Tagging mailing list
<br> > Tagging@openstreetmap.org
<br> > <a href="https://lists.openstreetmap.org/listinfo/tagging"> https://lists.openstreetmap.org/listinfo/tagging</a>
<br>
<br>
<br>
<br> ------------------------------
<br>
<br> Message: 5
<br> Date: Thu, 29 Sep 2022 18:11:15 +0100
<br> From: Anne-Karoline Distel <annekadistel@web.de>
<br> To: tagging@openstreetmap.org
<br> Subject: Re: [Tagging] Feature Proposal - RFC - Bench: replace seats
<br> by capacity
<br> Message-ID: <548d2caf-9889-ad61-a06a-8f7245adb61e@web.de>
<br> Content-Type: text/plain; charset=UTF-8; format=flowed
<br>
<br> Most times, I don't map the number of seats, because I don't have a
<br> number of 3-4 friends with me when I'm mapping to test the bench, so I
<br> can't tell how many people can sit on it. They installed a few 1-seater
<br> "benches" in my locality during lockdown, I added it then. But I agree
<br> that it might make it easier to simplify from seats to capacity.
<br>
<br> Anne
<br>
<br> On 29/09/2022 17:26, martianfreeloader wrote:
<br> > I personally find it more consistent to reduce the number of
<br> > synonymous keys across all objects.
<br> >
<br> > But yes, I am considering two groups of mutually exclusive proposals
<br> > to settle this issue. Something along these lines:
<br> >
<br> > -----
<br> > ISSUE 1
<br> > Should the capacity of a bench be tagged on all benches or only on
<br> > those which have clear seat separation? This is independent of issue 2.
<br> >
<br> > Proposal 1A) Only on benches with have clear seat separation.
<br> >
<br> > Proposal 1B) On all benches.
<br> >
<br> > Question to be resolved:
<br> > Can a thing that has individual seats be considered a bench at all?
<br> >
<br> > -------
<br> >
<br> > ISSUE 2:
<br> > Which key should be used to tag the capacity of a bench? This is
<br> > independent of issue 1.
<br> >
<br> > Proposal 2A) Use seats=* on all benches.
<br> >
<br> > Proposal 2B) Use capacity=* on all benches.
<br> >
<br> > Proposal 2C) [Only if 1B is approved] Use seats=* on benches with
<br> > clear seat separation and capacity=* otherwise.
<br> > -------
<br> >
<br> > This is just a sketch, let's see if I have time to spell this it out
<br> > in the next days.
<br> >
<br> >
<br> >
<br> >
<br> > On 29/09/2022 17:19, Martin Koppenhoefer wrote:
<br> >>
<br> >>
<br> >> sent from a phone
<br> >>
<br> >>> On 29 Sep 2022, at 14:10, martianfreeloader
<br> >>> <martianfreeloader@posteo.net> wrote:
<br> >>>
<br> >>> Facing heavy objections and no support, I have come to the
<br> >>> conclusion that my proposal is not considered useful by the community.
<br> >>>
<br> >>> I thus decided to retract it.
<br> >>
<br> >>
<br> >> as you are interested in consistency, have you considered proposing
<br> >> the opposite, retagging of the 1000 capacity on benches to seats?
<br> >>
<br> >> Cheers Martin
<br> >> _______________________________________________
<br> >> Tagging mailing list
<br> >> Tagging@openstreetmap.org
<br> >> <a href="https://lists.openstreetmap.org/listinfo/tagging"> https://lists.openstreetmap.org/listinfo/tagging</a>
<br> >
<br> > _______________________________________________
<br> > Tagging mailing list
<br> > Tagging@openstreetmap.org
<br> > <a href="https://lists.openstreetmap.org/listinfo/tagging"> https://lists.openstreetmap.org/listinfo/tagging</a>
<br>
<br>
<br>
<br> ------------------------------
<br>
<br> Message: 6
<br> Date: Thu, 29 Sep 2022 19:41:09 +0200
<br> From: Peter Elderson <pelderson@gmail.com>
<br> To: "Tag discussion, strategy and related tools"
<br> <tagging@openstreetmap.org>
<br> Subject: Re: [Tagging] Feature Proposal - RFC - Bench: replace seats
<br> by capacity
<br> Message-ID:
<br> <CAKf=P+uhrmaWGOcb7+OAhrnoUBq2JLaiNzC9B39oei2-KbcHmA@mail.gmail.com>
<br> Content-Type: text/plain; charset="utf-8"
<br>
<br> I have stopped tagging seats, because most benches do not have seats.
<br> Capacity is ok with me, I will start using that, but still I don't think I
<br> will tag that very often, unless it's a huge bench for 20 (I have seen
<br> one!) or a very small one for 1 person. I don't mind if others tag seats or
<br> estimate the capacity different, as long as they don't remove my capacity
<br> tag.
<br>
<br> Peter Elderson
<br>
<br>
<br> Op do 29 sep. 2022 om 14:10 schreef martianfreeloader <
<br> martianfreeloader@posteo.net>:
<br>
<br> > Facing heavy objections and no support, I have come to the conclusion
<br> > that my proposal is not considered useful by the community.
<br> >
<br> > I thus decided to retract it.
<br> >
<br> > _______________________________________________
<br> > Tagging mailing list
<br> > Tagging@openstreetmap.org
<br> > <a href="https://lists.openstreetmap.org/listinfo/tagging"> https://lists.openstreetmap.org/listinfo/tagging</a>
<br> >
<br> -------------- next part --------------
<br> An HTML attachment was scrubbed...
<br> URL: <<a href="http://lists.openstreetmap.org/pipermail/tagging/attachments/20220929/a96750b4/attachment-0001.htm">http://lists.openstreetmap.org/pipermail/tagging/attachments/20220929/a96750b4/attachment-0001.htm</a>>
<br>
<br> ------------------------------
<br>
<br> Message: 7
<br> Date: Thu, 29 Sep 2022 19:06:42 -0700
<br> From: stevea <steveaOSM@softworkers.com>
<br> To: "Tag discussion, strategy and related tools"
<br> <tagging@openstreetmap.org>
<br> Subject: Re: [Tagging] Feature Proposal - RFC - Bench: replace seats
<br> by capacity
<br> Message-ID: <A14A5DA1-FD76-415D-8E5F-6AD7A073548C@softworkers.com>
<br> Content-Type: text/plain; charset=us-ascii
<br>
<br> 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!
<br>
<br> 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.
<br>
<br> 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."
<br>
<br> Nice map we have here.
<br>
<br>
<br> ------------------------------
<br>
<br> Subject: Digest Footer
<br>
<br> _______________________________________________
<br> Tagging mailing list
<br> Tagging@openstreetmap.org
<br> <a href="https://lists.openstreetmap.org/listinfo/tagging">https://lists.openstreetmap.org/listinfo/tagging</a>
<br>
<br>
<br> ------------------------------
<br>
<br> End of Tagging Digest, Vol 156, Issue 68
<br> ****************************************
<br>
</div> </span></font>
</div> _______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
</blockquote></div></body>
</html>