Elevator required vs non-required trip times in Open Trip Planner

[skiverk]

We have open trip planner set up in Philly:

http://opentrips.phl.io/otp-leaflet-client/

It allows the exclusion of certain routes in trip requests. Can we send it stations with no access via elevators and compare that trip time to one that doesn't require elevator access?

We should also be able to display the two trips so site visitors can see the issues faced by wheel-chaired individuals.

[flibbertigibbet]

Looking at the SEPTA GTFS data, there's no wheelchair accessibility defined for the rail stops, and most of the bus/subway/trolley stops do not have accessibility set in the wheelchair_boarding column. This probably explains why most trips with wheelchair=true return only walking directions and not transit.

Here are two stops that are marked in the GTFS stops.txt as accessible:
61,Frankford Transportation Center - MFL,40.023427,-75.077185,,,1,1
82,Olney Transportation Center - BSL,40.039066,-75.144737,,,1,1

An alternate approach may be to query by banning routes or trips (defined by route + stops). OpenTripPlanner API docs here.

[skiverk]

Great catch! I'll ping Septa's Mike Zaleski to see if there's an easy fix for them to push.

[mikezphilly]

For Regional Rail, we've been using this as a work-around wheelchair_boarding station https://github.com/septadev/SEPTA-iOS/blob/master/gtfs/Rail_ADA.csv (until we can get the data source populated).

The GTFS bus has them for MFL, BSL, NHSL I believe, but for bus wheelchair boarding is based on the vehicle not the bus stop. I'm not sure about trolleys, though I am pretty sure that although some stations are accessible, they vehicles are not.

[skiverk]

I've submitted a comment to Septa's customer service through their online form per Mike Zileski:

https://twitter.com/mikezphilly/status/491966897249058817

The ticket number is 671836.

[skiverk]

@flibbertigibbet, would Open Trip planner be able to route wheelchair accessible transit routes if, for all Septa transit stops in stops.txt, they had a 0 or 1 populated in the wheelchair_boarding field instead of just having it empty? Do you have any thoughts on how I could rig a trip planner install to properly return an accessible transit trip by manipulating the data and feeding it into my own Open Trip Planner setup?

What do you think is a long term fix for the issue? Did Septa not include data it should have? Is this really an Open Trip Planner problem?

[flibbertigibbet]

As described in the GTFS docs I linked to above, 0 and null both mean
accessibility is unknown, 1 means the stop is accessible, and 2 means it is
not. No, it's not an OTP issue, it's a data issue. From Mike's reply,
they are aware of the issue. For buses, there may be no good solution, as
accessibility depends on the vehicle and not the stop.

For the time being I would suggest banning routes or trips, and to
incorporate the data Mike linked to above.
On Jul 26, 2014 5:14 PM, "Jim Smiley" notifications@github.com wrote:

@flibbertigibbet https://github.com/flibbertigibbet, would Open Trip
planner be able to route wheelchair accessible transit routes if, for all
Septa transit stops in stops.txt, they had a 0 or 1 populated in the
wheelchair_boarding field instead of just having it empty? Do you have any
thoughts on how I could rig a trip planner install to properly return an
accessible transit trip by manipulating the data and feeding it into my own
Open Trip Planner setup?

What do you think is a long term fix for the issue? Did Septa not include
data it should have? Is this really an Open Trip Planner problem?

—
Reply to this email directly or view it on GitHub
#2 (comment)
.

[mikezphilly]

We just posted a list of stops and whether or not they have curb cuts. Not exactly the data that's needed, but it may be useful. It's all in a tab delimited text file at: https://github.com/septadev/CurbCuts/blob/master/curbcuts.txt

[flibbertigibbet]

Thanks @mikezphilly !