<div dir="ltr"><div dir="ltr"><br></div><div dir="ltr" class="gmail_attr">On Mon, 26 Aug 2019 at 08:53, Paul Allen <<a href="mailto:pla16021@gmail.com">pla16021@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr">On Sun, 25 Aug 2019 at 23:35, Graeme Fitzpatrick <<a href="mailto:graemefitz1@gmail.com" target="_blank">graemefitz1@gmail.com</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><br></div><div class="gmail_quote"><div>A bit messy, but how about </div><div><div>amenity=parking_space + access=vehicle_charging_only</div></div></div></div></blockquote><div><br></div><div>Big problem right there: you're expanding on the access tag. Some on this list will</div><div>take great exception to that. Some editors will take even greater exception to it as</div><div>they populate drop-downs from the wiki, so when you map a road the access drop-down</div><div>will include yes, no, private, vehicle_charging_only. Which is why the parking_space</div><div>proposal invented access:<role>. And even that is pushing things, a little.<br></div></div></div></blockquote><div><br></div><div>Yes, you're quite right there - I hadn't thought that side of access= through</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div>car_charging=yes/no</div><div>truck_charging=yes/no</div><div>hgv_charging=yes/no</div></div></div></blockquote><div><br></div><div>And this will re-open hostilities in a different argument about the undesirability of having all</div><div>those different binary tags instead of charging=car|truck|hgv. Or was it the other way</div><div>around that was undesirable? I forget now.<br></div></div></div></blockquote><div><br></div><div>I "think" it was charging=car|truck|hgv arrangement that wasn't liked because of semi-colons, but you're right - it could be the other way round!</div><div><br></div><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 26 Aug 2019 at 21:56, Paul Allen <<a href="mailto:pla16021@gmail.com">pla16021@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr">On Mon, 26 Aug 2019 at 01:37, Warin <<a href="mailto:61sundowner@gmail.com" target="_blank">61sundowner@gmail.com</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<div class="gmail-m_-3752157282695535127gmail-m_2216998371087620327moz-cite-prefix">amenity=charging _space? Says what it
is. <br></div></div></blockquote><div><br></div><div>First problem is that goes against the design of amenity=parking_space. Somebody</div><div>will then decide to have amenity=disabled_parking_space rather than use the</div><div>appropriate subtag with amenity=parking_space.</div></div></div></blockquote><div><br></div><div>& then, in a few years as electric vehicles become more popular, you'll have disabled, charging bays! (Which started as a joke but is actually quite correct - charging bike racks, perhaps?)</div><div><br></div><div>Thanks<div><br></div><div>Graeme</div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
</blockquote></div></div>