<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>
<div>Mapping public transport in detail was in part started to aid impaired people and people with diminished mobility. The stop_position is an attempt to tell for large/long platforms at which subarea of the platform you can expect a public service vehicle to have an entrance (regardless of its length, that may change with time of day or when the schedule of the company is overhauled).</div>
<div> </div>
<div>The platform itself will not give you any clues which position to route a user to so that him/her readjusting position on that platform is minimal once the vehicle arrived and is ready for boarding.</div>
<div> </div>
<div>If the platform exists, mapping it is more important than the stop_position, but the latter gives additional info _especially_ for lengthy or large platforms.</div>
<div> </div>
<div>-----</div>
<div> </div>
<div>There have been complaints about added pseudo-platforms in the data. This situation stems from the fact, that platforms are missing on ground (for lack of money, political decisions or because the halt is seen as a temporary one). _Nevertheless_, public transport users _do_ and _have_ to use parts of the area around the PT-pole as a platform. In this case the tag is not used to map a built structure, but how the space is effectively used on ground. If this is a problem, because the tag should ideally discrimnate built structure features, then either</div>
<div> </div>
<div>a) find a new tag for wild platforms</div>
<div>b) allow the platform tag on nodes and use a single node only where a built platform structure does not exist</div>
<div> </div>
<div>may be an solution.</div>
<div> </div>
<div> </div>
<div>Greetings</div>
<div>cmuelle8</div>
<div>
<div name="quote" style="margin:10px 5px 5px 10px; padding: 10px 0 10px 10px; border-left:2px solid #C3D9E5; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div style="margin:0 0 10px 0;"><b>Gesendet:</b> Donnerstag, 29. März 2018 um 13:36 Uhr<br/>
<b>Von:</b> Jo <winfixit@gmail.com><br/>
<b>An:</b> "Tag discussion, strategy and related tools" <tagging@openstreetmap.org><br/>
<b>Betreff:</b> Re: [Tagging] Still RFC — Drop stop positions and platforms</div>
<div name="quoted-content">
<div>That's what I would like to see happen. Last year I created a wiki page about it (with screenshots):
<div> </div>
<div><a href="https://wiki.openstreetmap.org/wiki/JOSM/Plugins/PT_Assistant/Mapping_Public_Transport_with_JOSM#Downloading_data" target="_blank">https://wiki.openstreetmap.org/wiki/JOSM/Plugins/PT_Assistant/Mapping_Public_Transport_with_JOSM#Downloading_data</a></div>
<div> </div>
<div>Polyglot</div>
</div>
<div class="gmail_extra">
<div class="gmail_quote">2018-03-29 13:09 GMT+02:00 Selfish Seahorse <span><<a href="mailto:selfishseahorse@gmail.com" onclick="parent.window.location.href='selfishseahorse@gmail.com'; return false;" target="_blank">selfishseahorse@gmail.com</a>></span>:
<blockquote class="gmail_quote" style="margin: 0 0 0 0.8ex;border-left: 1.0px rgb(204,204,204) solid;padding-left: 1.0ex;"><span>> Otherwise, public_transport=stop_position could be abandoned, which would make PTv2 tagging a lot easier and more time-efficient.</span></blockquote>
</div>
</div>
</div>
</div>
</div>
</div></div></body></html>