<div dir="ltr"><div>Estan requiriendo ideas para mejorar el etiquetado de transporte publico con el esquema version 2... <br></div><div><br></div><div>La conversación está en el hilo de talk-transit. <br></div><div><br></div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature">Abrazos,<br><br>Marco Antonio</div></div><br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">---------- Forwarded message ---------<br>From: <b class="gmail_sendername" dir="auto">Markus</b> <span dir="ltr"><<a href="mailto:selfishseahorse@gmail.com">selfishseahorse@gmail.com</a>></span><br>Date: Fri, 26 Apr 2019 at 15:11<br>Subject: [Talk-transit] Ideas for a simplified public transportation scheme<br>To: Public transport/transit/shared taxi related topics <<a href="mailto:talk-transit@openstreetmap.org">talk-transit@openstreetmap.org</a>><br></div><br><br>Hi all,<br>
<br>
I've added, updated and corrected several dozen public transportation<br>
routes in the past few years using the PTv2 scheme. As is the case<br>
with most route relations, they often break (e.g., because the course<br>
of a road or rails is modified, a new roundabout is built, a stop is<br>
displaced or simply by accident). However, with all the stop_positions<br>
and stop_areas, maintaining these routes and stops is very much<br>
time-consuming.<br>
<br>
There have been several ideas to simplify and improve public<br>
transportation mapping (e.g. [1] or [2]), however they either faced<br>
too much opposition or are inactive. Therefore I've worked out three<br>
different drafts for an improved public transportation scheme and<br>
would like your opinion. After that, i plan to write a full proposal<br>
for the option that got the most support.<br>
<br>
In order to better understand how I came up with the ideas below, I<br>
have first listed the deficiencies of the current public transport<br>
schemes:<br>
<br>
Deficiencies of PTv1:<br>
<br>
* No separate route relation per direction and route variant.<br>
* Platforms at stations cannot be added to route relations, which<br>
prevents a better routing.<br>
* Stops (highway=bus_stop/railway=tram_stop) are often placed on the<br>
road or rail, which is not optimal for routing.<br>
<br>
Deficiencies of PTv2:<br>
<br>
* public_transport=stop_position and public_transport=stop_area make<br>
mapping and maintaining complicated and time-consuming. Besides,<br>
public_transport=stop_position is unnecessary, as it can be calculated<br>
from public_transport=platform (which provide a more exact routing).<br>
* Counter-intuitive public_transport=platform: its meaning depends<br>
on whether used on way/area (where it means a platform) or on node<br>
(where it means a waiting area w/o platform).<br>
* Not possible to add transport mode tags (e.g. bus=yes) on<br>
public_transport=platform because they are also used to set access.<br>
<br>
Now for the possible solutions:<br>
<br>
1. Sticking to PTv1 tags, but with separate route relations per<br>
direction/variant and by placing stops at the point where passengers<br>
wait. A stop with a platform get a railway/highway=platform way/area<br>
and a railway=tram_stop/highway=bus_stop node. (Except at stations, a<br>
stop_area relation is not required because the stop node is placed on<br>
the platform.) -- Advantage: Widely used tags, least retagging<br>
required. Disadvantage: A stop with a platform needs two elements (as<br>
railway/highway=platform + railway=tram_stop/highway=bus_stop can't be<br>
combined).<br>
<br>
2. Sticking to PTv2 tags, but abandoning<br>
public_transport=stop_position and introducing a new transport_mode=*<br>
tag. -- Advantage: Only one element per stop. Disadvantage: The rather<br>
counter-intuitive public_transport=platform remains.<br>
<br>
3. Abolishing public_transport=stop_position and<br>
public_transport=platform and introducing a new public_transport=stop<br>
tag (node/way/area) for the waiting area at stops, which can be<br>
combined with railway/highway=platform if the stop consists of a<br>
platform. Besides, introducing a new transport_mode=* tag. --<br>
Advantage: Only one element per stop, very flexible and clear.<br>
Disadvantage: Much retagging required.<br>
<br>
[1]: <a href="https://wiki.openstreetmap.org/wiki/Proposed_features/Transport_modes_on_platforms_and_stations" rel="noreferrer" target="_blank">https://wiki.openstreetmap.org/wiki/Proposed_features/Transport_modes_on_platforms_and_stations</a><br>
[2]: <a href="https://wiki.openstreetmap.org/wiki/Proposed_features/Refined_Public_Transport" rel="noreferrer" target="_blank">https://wiki.openstreetmap.org/wiki/Proposed_features/Refined_Public_Transport</a><br>
<br>
Thanks in advance for your replies.<br>
<br>
Best regards<br>
<br>
Markus<br>
<br>
_______________________________________________<br>
Talk-transit mailing list<br>
<a href="mailto:Talk-transit@openstreetmap.org" target="_blank">Talk-transit@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/talk-transit" rel="noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/talk-transit</a><br>
</div></div>