Michael,
There are probably different numbers in the agency's computers
somewhere, but if so, they're not exposed to the public. In fact, even
the A/B names are something I added below.
This is what they really look like:
↑PPP↕PPP↓
↑P|P↕P|P↓
↑P|P↕P|P↓
↑P|P↕P|P↓
↑PPP↕PPP↓
↑P|P↕P|P↓
↑P|P↕P|P↓
↑P|P↕P|P↓
↑PPP↕PPP↓
On each side of the walls ("|"), there is a sign listing places where a
train stopping there might go, but it's up to you to (a) wander around
until you find a platform listing your destination and (b) get on the
right train based on the signs in its windows.
If you're on the wrong side of the platform (first case below) when your
train arrives, you just walk around the wall, but if you're on the wrong
platform entirely (second case below), there's not enough time to change
to the correct one before it departs. OTOH, telling people they have to
change platforms when they don't need to (first case) may also cause
them to miss their train.
This is not how I'd design things if I were in charge, but I have to map
this mess as it actually is, not how I wish it were.
S
On 2016-11-13 19:57, Michael Tsang wrote:
> I always separate those platforms into connected halves (sharing same nodes)
> because they have different refs:
>
> ↑12↕34↓
>
> Are your platforms really called A and B with tracks on both sides in your
> case? For example, if the timetable tells you to board at platform B and
> there is a train on both tracks, which do you board?
>
> Michael
>
> Sent from Outlook.com
>
> -------------------------
>
> FROM: Stephen Sprunk <[email protected]>
> SENT: 01 November 2016 02:37
> TO: [email protected]; Public transport/transit/shared taxi related topics
> CC: Tag discussion, strategy and related tools
> SUBJECT: Re: [Talk-transit] [Tagging] Bus routes forward/backward
>
> Polyglot,
>
> Just noting the platform may sometimes not be specific enough, however, which
> I suspect is why stop_positions exist.
>
> Keep in mind that platforms may serve multiple tracks. For instance, there
> are a few stations here configured like this:
>
> ↓A↕B↑
>
> The "regular" trains (which run the full line, every N minutes) stop on the
> outside tracks while the "peak" or "express" trains (which run part of the
> line, but only certain hours) stop on the middle track. Telling someone to
> take the next train from a given platform could easily send them in the wrong
> direction.
>
> Other, similar-looking stations are set up like this:
>
> ↓A↑B↑
>
> All the trains on the left track are going to downtown, but the trains on the
> middle and right track are going to different suburbs; telling someone to
> take the next train from a given platform could easily send them to the wrong
> place and also loses cross-platform transfers from the left track to middle
> track, which might result in a missed train if someone (especially with
> limited mobility) had to take the stairs/elevator twice to get from platform
> A to B.
>
> Also, short trains may stop in different places along the platform--including
> multiple trains stopping there at the same time at peak hours, while others
> take the entire platform.
>
> So, by not marking the stop_position, one loses valuable information and
> disserves users.
>
> _______________________________________________
> Talk-transit mailing list
> [email protected]
> https://lists.openstreetmap.org/listinfo/talk-transit
--
Stephen Sprunk "Those people who think they know everything
CCIE #3723 are a great annoyance to those of us who do."
K5SSS --Isaac Asimov_______________________________________________
Talk-transit mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/talk-transit
