<div dir="ltr"><div>I have spent some time reading  </div><div><a href="https://github.com/gravitystorm/openstreetmap-carto/issues/435">https://github.com/gravitystorm/openstreetmap-carto/issues/435</a><br></div><div>and</div><div><a href="https://github.com/gravitystorm/openstreetmap-carto/issues/331">https://github.com/gravitystorm/openstreetmap-carto/issues/331</a><br></div><div><br></div><div>It seems that one major issue was that, given a simple public_transport=platform situation, which icon should be used to render it? In many cases there isn't a {mode}=yes tag. My contribution to solving that issue is attached -- a generic transit icon which I hereby put into the public domain. I think this icon should be used (a) when there is no indicator of the transport mode, or (b) when there are multiple modes, as in </div><div><a href="https://www.openstreetmap.org/way/66332939">https://www.openstreetmap.org/way/66332939</a> </div><br>As I understand it, valid relevant mode tags are:<div>train=yes<br></div><div>light_rail=yes</div><div>tram=yes</div><div>subway=yes</div><div>monorail=yes</div><div>bus=yes</div><div>trolleybus=yes</div><div>ferry=yes</div><div>aerialway=yes</div><div><br></div><div>... and in hindsight, wouldn't it have been nice to have a "platform:" namespace for these? Very difficult to track these, especially if/when a new mode arrives (self-driving vehicles, anyone?). </div><div><br></div><div>(As a side note, one issue raised in another thread was that "bus=yes" does double duty as an overriding tag in combination with for "access=no" on highways. This isn't an issue for the vast majority of platforms, as they are nodes not ways, but still... I'd prefer that the access overriding tags have an "access:" namespace anyhow: "access:bus=yes", "access:psv=yes", etc.)</div><div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial"><br></div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial">Another major issue with rendering public_transport=platform tags was a limitation in the database schema, which appears to have been lifted with the (relatively recent) addition of hstore. (Though the issue, apparently, was the ability to render based on the mode tags -- which could have been solved with a generic transit icon.) </div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial"><br></div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial">A third concern was double-rendering. If both a highway=bus_stop node and a public_transport=platform node exist, won't mappers want to remove the duplicate? I would hope so! Alternatively, if a stop area is mapped with both <span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">public_transport=platform and <span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">public_transport=stop_position, won't that make the map messy? That, it seems to me, is a valid consideration. It was proposed to NOT render <span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">public_transport=stop_position in all cases, which frankly I agree with when the node is on a highway (not clear to me when it's on a railway, as I don't have experience there).</span></span></span></div><br style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial"><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">The last issue, raised by kocio-pl, who I assume is Daniel Koć of this thread, is that someone needs to write the code. </span><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial"><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"></span></span></span></div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial"><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br></span></span></span></div><br class="gmail-Apple-interchange-newline"></div><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Mar 29, 2018 at 3:56 AM, Daniel Koć <span dir="ltr"><<a href="mailto:daniel@koć.pl" target="_blank">daniel@koć.pl</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">W dniu 28.03.2018 o 18:42, Jo pisze:<br>
<span class="gmail-">> I've tried to accomplish that many years ago already, it failed. The<br>
> people at the helm of the rendering stack consider the 'old' tags good<br>
> enough and the new scheme somehow not explicit enough, hence the<br>
> double tagging.<br>
<br>
</span>I'm not sure who do you mean, but I certainly want to make it render on<br>
osm-carto. It wasn't possible before we have hstore few months ago<br>
(v4.0.0+) and I had to learn coding with this feature enabled, but now<br>
it's much closer to being reality - I need just some time probably, but<br>
any help is welcome. Related issue:<br>
<br>
<a href="https://github.com/gravitystorm/openstreetmap-carto/issues/435" rel="noreferrer" target="_blank">https://github.com/<wbr>gravitystorm/openstreetmap-<wbr>carto/issues/435</a><br>
<span class="gmail-"><br>
> Dropping the tags you call obsolete from the data, is not an option as<br>
> far as I'm concerned. Part of the reason for mapping bus stops, is to<br>
> get them rendered on the map. That's not tagging for the renderer,<br>
> that's merely being practical and adapting to the situation at hand.<br>
<br>
</span>Tagging for rendering is confusing slogan. There's nothing wrong in the<br>
literal sense, the problem is with faking data just to show something on<br>
the map. Double tagging is a problem too, but transition is always<br>
troublesome process.<br>
<span class="gmail-HOEnZb"><font color="#888888"><br>
--<br>
"My method is uncertain/ It's a mess but it's working" [F. Apple]<br>
</font></span><div class="gmail-HOEnZb"><div class="gmail-h5"><br>
<br>
<br>
______________________________<wbr>_________________<br>
Tagging mailing list<br>
<a href="mailto:Tagging@openstreetmap.org">Tagging@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/tagging" rel="noreferrer" target="_blank">https://lists.openstreetmap.<wbr>org/listinfo/tagging</a><br>
</div></div></blockquote></div><br></div></div>