<html><body><br><aside>
---------- Původní e-mail ----------<br>
Od: Jo <winfixit@gmail.com><br>
Komu: Tag discussion, strategy and related tools <tagging@openstreetmap.org><br>
Datum: 28. 3. 2018 18:43:15<br>
Předmět: Re: [Tagging]
Still RFC — Drop stop positions and platforms
</aside><br><blockquote data-email="winfixit@gmail.com"><div dir="ltr">I've tried to accomplish that many years ago already, it failed. The people at the helm of the rendering stack consider the 'old' tags good enough and the new scheme somehow not explicit enough, hence the double tagging.<div></div></div></blockquote><p><br></p><p>I don't like this half way situation :-( And if situation does not change for some time, it does not mean that it can't change at all.<br></p><p> <br></p><blockquote data-email="winfixit@gmail.com"><div dir="ltr"><div><br></div><div>Dropping the tags you call obsolete from the data, is not an option as far as I'm concerned. Part of the reason for mapping bus stops, is to get them rendered on the map. That's not tagging for the renderer, that's merely being practical and adapting to the situation at hand.</div><div></div></div></blockquote><p><br></p><p>I don't like that I'm forced to use these old tags, because it is not render on map and then some user with Maps.Me will come and put OSM note, that bus stop is missing or will create a duplicate node with highway=bus_stop.</p><p><br></p><blockquote data-email="winfixit@gmail.com"><div dir="ltr"><div><br></div><div>Adding public_transport=platform/stop_position is also being practical, as they are treated in certain ways by JOSM, with regard to assignment of roles.</div><div></div></div></blockquote><p><br></p><p>Yes. I like it as well. But it still could be improved. E.g. I'm thinking about tool which - If you create four objects: two nodes on highway and two nodes/ways beside highway and select all of them - will automatically tag them as stop_position and platform and will create corresponding public_transport relation. I have to find a time to develop it.</p><p><br></p><blockquote data-email="winfixit@gmail.com"><div dir="ltr"><div><br></div><div>I stopped worrying about the wasted disk space or processing power several years ago.</div><div></div></div></blockquote><p><br></p><p>I don't worry about disks or processors, but I worry about my time I waste by adding this tag or solving OSM notes about "missing" bus stops.</p><p><br></p><p>Marián</p><p><br></p><blockquote data-email="winfixit@gmail.com"><div dir="ltr"><div><br></div><div>Polyglot<br><div><br></div><div><br></div></div></div><div><br><div>2018-03-28 17:48 GMT+02:00 Marián Kyral <span dir="ltr"><<a href="mailto:mkyral@email.cz">mkyral@email.cz</a>></span>:<br><blockquote style="margin:0 0 0 0.8ex;border-left:1px#ccc solid;padding-left:1ex"><div><br><aside>
---------- Původní e-mail ----------<br>
Od: "Christian Müller" <<a href="mailto:cmue81@gmx.de">cmue81@gmx.de</a>><br>
Komu: <a href="mailto:tagging@openstreetmap.org">tagging@openstreetmap.org</a><br>
Datum: 28. 3. 2018 16:22:41<br>
Předmět: Re: [Tagging]
Still RFC — Drop stop positions and platforms
</aside><br><span><blockquote>> Sent: Wed, 28 Mar 2018 16:53:28 +0300<br>> From: "Ilya Zverev" <<a href="mailto:ilya@zverev.info">ilya@zverev.info</a>><br>> To: <a href="mailto:tagging@openstreetmap.org">tagging@openstreetmap.org</a><br>> Subject: [Tagging] Still RFC — Drop stop positions and platforms<br>><br>> Hi folks,<br>> <br>> A while ago I've made a proposal to deprecate some public_transport=* tags:<br>> <br>> <a href="https://wiki.openstreetmap.org/wiki/Proposed_features/Drop_stop_positions_and_platforms">https://wiki.openstreetmap.<wbr>org/wiki/Proposed_features/<wbr>Drop_stop_positions_and_<wbr>platforms</a><br>> <br><br>In your proposal you complain about subjectively felt things like "history won't go away", but at the same time you are trying to revert a part of history itself - "the public_transport tags are seven years old now". Many people were involved creating those tags, they are well understood and discriminate the features they describe in a thoroughly documented and plausible way.<br><br>Just because a lot of deprecated tags have not vanished in favor of the new ones yet does not mean there is a preference on the deprecated tags. A lot of users and apps have adopted the new public_transport tags. It simply does not make any sense to do a rollback on these for the observation of a sluggish adoption/transition rate.<br><br></blockquote><p><br></p></span><p>I fully agree with this.<br></p><p><br></p><p>I'm still waiting for full support of new public_transport schema on maps (especially on the "transport" layer on <a href="http://osm.org">osm.org</a>) and decommission of the old schema. Still no progress on it.. Instead, we still have to use obsolete tags like highway=bus_stop to see stops on the map. It is mapping for render I think and we should stop doing it, convert old schema objects to new schema (a MapRoulette task?) and use only new schema.<br></p><p><br></p><p>I think the new schema is really good and should be fully implemented. It means have support in editors and renderers.<span><font color="#888888"><br></font></span></p><span><font color="#888888"><p><br></p><p>Marián<br></p><br></font></span></div><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">https://lists.openstreetmap.<wbr>org/listinfo/tagging</a><br>
<br></blockquote></div><br></div>
_______________________________________________<br>Tagging mailing list<br>Tagging@openstreetmap.org<br>https://lists.openstreetmap.org/listinfo/tagging<br></blockquote></body></html>