<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:PMingLiU;
panose-1:2 2 5 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"\@PMingLiU";
panose-1:2 2 5 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-AU link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From my reading of the wiki (I wasn’t involved when PTv2 was designed), the situation as envisioned in PTv2 would be that you have only one node, way, or area with public_transport=platform. So the existing highway=bus_stop and highway=platform (in cases where both are present) are merged into a single public_transport=platform (on the way or area that currently is the highway=platform, and the highway=bus_stop goes away completely).<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>But this requires proper rendering support. That is, the way or area should be rendered like highway=platform was, AND it should render an icon in the middle of the way like highway=bus_stop did. Because public_transport=platform replaces both of these.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>Trying to see and implement public_transport=platform only as a 1:1 replacement for existing highway=platform and/or railway=platform is going to make the situation worse, not better.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><div style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif'> Jo <winfixit@gmail.com> <br><b>Sent:</b> Thursday, 21 June 2018 01:45<br><b>To:</b> Tag discussion, strategy and related tools <tagging@openstreetmap.org><br><b>Subject:</b> Re: [Tagging] public_transport=platform rendering on osm-carto<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>Actually I have started to remove public_transport=platform from WAYS with highway=platform and railway=platform. As far as I am concerned public_transport=platform goes on NODES next to the ways in combination with highway=bus_stop or railway=tram_stop.<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Removing those tags from ways comes from the objection of some people that there would be both a way and a platform with the public_transport=platform tag.<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>In other words, the rendering of *=platform on WAYS is just fine as it is.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Polyglot<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>Op wo 20 jun. 2018 om 17:02 schreef Daniel Koć <<a href="mailto:daniel@ko%C4%87.pl">daniel@koć.pl</a>>:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm'><p class=MsoNormal>W dniu 19.06.2018 o 17:40, <a href="mailto:osm.tagging@thorsten.engler.id.au" target="_blank">osm.tagging@thorsten.engler.id.au</a> pisze:<br>> But I do not think that it is reasonable to add rendering for it, and at the same moment drop rendering for highway=platform, railway=platform, highway=bus_stop, railway=tram_stop and everything else that public_transport=platform is meant to replace.<br>><br>> This absolutely needs to be a two step process. Add rendering for public_transport=platform first, then let people work on migrating existing data. At some point in the future it might then become possible to drop rendering for existing tags.<br><br>I want to make just one step now - replace *=platform with<br>public_transport=platform. Next steps might be very different and i<br>don't see them clearly now. It might even need PTv3 - I don't know, so I<br>won't touch it.<br><br>We could of course migrate by adding new type and removing old ones<br>after some time and I would do it. However on osm-carto we have a strong<br>opposition to rendering multiple similar tags (fear of fragmentation),<br>so I prefer to start with announcing the planned change and then make<br>the switch in rendering. It's just a different way of migration and if<br>it won't create (unnecessary in this case) tension and makes the whole<br>thing more probable to happen, I vote for it.<br><br>-- <br>"My method is uncertain/ It's a mess but it's working" [F. Apple]<br><br><br><br>_______________________________________________<br>Tagging mailing list<br><a href="mailto:Tagging@openstreetmap.org" target="_blank">Tagging@openstreetmap.org</a><br><a href="https://lists.openstreetmap.org/listinfo/tagging" target="_blank">https://lists.openstreetmap.org/listinfo/tagging</a><o:p></o:p></p></blockquote></div></div></div></body></html>