accessibility: agencies, what data do you have on hand?

[Joe Hughes]

This is a follow-on to our previous discussion on wheelchair
accessibility:
http://groups.google.com/group/gtfs-changes/browse_thread/thread/f98f8fa7c4cc8430

I wanted to ask some of the agency folks who were interested in
supporting accessibility extensions in GTFS: what accessibility-
related information do you already have in your databases above and
beyond whether a given routes and stops can be boarded/alighted in a
wheelchair? If you have other information that you consider to be of
high enough quality that you'd be willing to publish it today, could
you describe it for this group?

Thanks,
Joe Hughes
Google

[Kevin O'Malley]

Our current feed already has it in the stops.txt. All of our vehicles are ada, so it's not necessary to be in the trips.txt file (the other place it could exist for agencies that have mixed fleets).

I do not have it now, but something could be added to transfers.txt, to denote the possibility that a transfer could be accessible, even if the stops themselves are not. (Albeit rare and probably only effects the older rail systems)

And I would propose it for my proposed entrances.txt file, too.

Kevin

[Martin Akerman]

Hi Group,

We're working on a capital improvement scoring system for an agency in Florida.
The point of the system is to identify stops that are most deserving
of upgrades in a system.
One of the scores we measure is ADA compliance. We used Easter Seals
as a guideline for some of our development.

Here is a pretty robust guideline for Accessibility and Safety from
Easter Seals some of you may find useful.

http://projectaction.easterseals.com/site/PageServer?pagename=ESPA_BusStopToolkit

-Martin
CUTR

> --
>
> You received this message because you are subscribed to the Google Groups "Google Transit Feed Spec Changes" group.
> To post to this group, send email to gtfs-c...@googlegroups.com.
> To unsubscribe from this group, send email to gtfs-changes...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/gtfs-changes?hl=en.
>
>
>

[David Turner]

I'm not part of a transit agency, but I maintain the only public GTFS
feed of New York City Transit's buses (100% accessible) and subways (all
trains accessible; many stops not).

I have not yet gathered accessibility data for the subway stops or
transfers, but it is likely that I will do so shortly, when the patch is
merged into my GTFS library:

http://groups.google.com/group/opentripplanner-dev/browse_thread/thread/a29e46728156d85a

[Oren Vandersteen]

We manage accessibility at a stop level and a trip level as we have a
mixed fleet. I am happy to add this to our gtfs feed if it would be
helpful.

On Dec 9, 2:31 am, Joe Hughes <joe.hughes.c...@gmail.com> wrote:
> This is a follow-on to our previous discussion on wheelchair

> accessibility:http://groups.google.com/group/gtfs-changes/browse_thread/thread/f98f...

[Joe Hughes]

Thanks for all the responses so far. To clarify, I'm interested in
any accessibility information that you are already maintaining
internally at your agency, *beyond* basic "wheelchair riders can board/
alight at this stop" information (since the latter already has an
existing proposal).

Thanks,
Joe Hughes
Google

On Dec 8, 10:31 am, Joe Hughes <joe.hughes.c...@gmail.com> wrote:
> This is a follow-on to our previous discussion on wheelchair

> accessibility:http://groups.google.com/group/gtfs-changes/browse_thread/thread/f98f...

[Devin Braun]

We keep the following information for accessibility by stop in
addition to an overall yes/no for accessibility: if there are curb
cuts or ramps nearby for access to the bus stop, if the bus stop is on
a steep slope, what type of material the sidewalk is made of, what
condition the sidewalk is in, how wide the sidewalk is, whether the
stop has light at night, and whether or not there's a shelter or
bench.

Devin Braun
San Diego MTS

> > Google- Hide quoted text -
>
> - Show quoted text -

[tompw]

[Cross-posting this at the Stop Amenities information discussion]
One example worth lookin at is the UK's National Rail website. They
have a large amount of detailed information on each railway station.
See http://www.nationalrail.co.uk/stations/bth/details.html or
http://www.nationalrail.co.uk/stations/bhm/details.html for examples.
The website's just been revamped, so there are some bugs present. That
should give you a fairly large list of what attributes would be
needed.
Hope this is useful.
Tom W

[Joe Hughes]

Hi Tom,

Thanks for the information. On both of those example pages, when I
click on the "Accessibility and mobility access" sections, no content
is shown. Can you clarify what accessibility information you wanted
the group to take a look at?

Thanks,
Joe Hughes
Google

On Dec 31, 6:47 am, tompw <to...@hotmail.com> wrote:
> [Cross-posting this at the Stop Amenities information discussion]
> One example worth lookin at is the UK's National Rail website. They
> have a large amount of detailed information on each railway station.

> Seehttp://www.nationalrail.co.uk/stations/bth/details.htmlorhttp://www.nationalrail.co.uk/stations/bhm/details.htmlfor examples.

[tompw]

I was hopeing it would be fixed by now... though I've just found
another way to show the information at
http://www.nationalrail.co.uk/stations/sjp/BHM/stationAccessibility.xhtml
or http://www.nationalrail.co.uk/stations/sjp/BTH/stationAccessibility.xhtml
. Also, http://www.nationalrail.co.uk/stations/sjp/BHM/plan.html and
http://www.nationalrail.co.uk/stations/sjp/BTH/plan.html provide a
whole new level of detail.

Accessability information includes:
* Availability of staff for assistance
* Accessible car parking (or not)
* Ticket office opening horus
* Accessability of ticket office (induction loops, low counters, level
acces)
* Acessability of toilets (whether present, if key needed, automatic/
manual doors)
* Places/platforms with level access (such as via elevators)
* Presence of stair cases, esculators
* Elevator information (whether big enough for wheelchair user place
companion, braille on buttons, audible announcements, accessible
emergency alarm)

I'm stopping there... I'm not sure how much information should be
provided, because each piece of information will be useful to someone.

Tom W