<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
W dniu 29.03.2018 o 09:43, Johnparis pisze:<br>
<blockquote type="cite"
cite="mid:CAEVvu1Prsq216nHsRVnTKY9iJKr55JKnSRmeF9VEeMp=o0P0Dg@mail.gmail.com">
<div dir="ltr">
<div>I have spent some time reading </div>
<div><a
href="https://github.com/gravitystorm/openstreetmap-carto/issues/435"
moz-do-not-send="true">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"
moz-do-not-send="true">https://github.com/gravitystorm/openstreetmap-carto/issues/331</a><br>
</div>
</div>
</blockquote>
<br>
Great! I will try to do it too, but thanks for the summary anyway.<br>
<br>
<blockquote type="cite"
cite="mid:CAEVvu1Prsq216nHsRVnTKY9iJKr55JKnSRmeF9VEeMp=o0P0Dg@mail.gmail.com">
<div dir="ltr">
<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. </div>
</div>
</blockquote>
<br>
I don't think that platform should always have an icon. It might be
clear from the context if it's a train, tram or ferry, for example.
Icons for buses however make sense for me, because there is no trail
visible on a default map to spot them.<br>
<br>
<blockquote type="cite"
cite="mid:CAEVvu1Prsq216nHsRVnTKY9iJKr55JKnSRmeF9VEeMp=o0P0Dg@mail.gmail.com">
<div dir="ltr">
<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>
</div>
</div>
</blockquote>
<br>
I don't want to render stop position on default map. It worked great
for a half-automated bus routing updates in Warsaw (we were able to
catch up with the changes and the positions were accurate, without
expensive guessing), so I wouldn't like to get rid of them, but I
think this is not what people are looking for on the map.<br>
<br>
I also hope that this will make the schema transition reality. When
I started using Tag History tool I was surprised to find that some
transitions went smooth without proper change in our rendering (like
emergency phones - full transition half a year before visual change,
IIRC), but some more substantial things like landuse->landcover
or platforms need some support from the rendering department to
happen in my opinion.<br>
<br>
<blockquote type="cite"
cite="mid:CAEVvu1Prsq216nHsRVnTKY9iJKr55JKnSRmeF9VEeMp=o0P0Dg@mail.gmail.com">
<div dir="ltr">
<div><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. <br>
</span></div>
</div>
</blockquote>
<br>
Yes, that's me. We are looking for coders (of all the types of
features, including simple cleaning), because at the moment it's our
scarcest resource - on the other hand the ideas are cheap, because
we have a lot of them...<br>
<br>
<pre class="moz-signature" cols="72">--
"My method is uncertain/ It's a mess but it's working" [F. Apple]</pre>
</body>
</html>