On 12/10/2014 08:18 AM, Noel Hidalgo wrote:
> When my girlfriend broke her foot, she found it quite
> frustrating that she couldn't plan for stations that
> had escalators, let alone know which ones were broken.
My thinking is that this is an accessibility issue and
should be part of the alerts for a trip, quite apart from
an escalator/elevator status API. In GTFS-Realtime terms
that would be a "service alert" and in SIRI it would be a
"situation."
The spec for service alerts in GTFS-Realtime includes an
`effect` field, perhaps the MODIFIED_SERVICE enum, though
perhaps an accessibility enum should be added:
https://developers.google.com/transit/gtfs-realtime/service-alerts
The `effect` field is unused in the Subway's GTFS-Realtime
feed, and similarly, whereas SIRI's `Situation` element
contains a `Severity` setting, I've gotten "undefined"
when I've queried BusTime for it.
There's an older convention that separates "alerts" from
"advisories," and they can be entirely different systems
(some agencies have separate third parties running them!).
I've been in exactly the situation as you, my girlfriend
was on crutches, except we were shuttling between NYC and
the Bay Area at the time.
Bay Area Rapid Transit is fastidious about ADA compliance,
and there are constant announcement and countdown clock
displays about elevators out of service. However, these
are "advisories" and don't show up in their GTFS-Realtime
alerts feed. There's room for improvement on both coasts.
<_Jym_>