Transport Stops specification - ODIQueensland/ocd-standards GitHub Wiki

This page contains stuff related to developing the Transport Stops specification.

It has 4 steps:

1. Research standards

The UK Department of Transport (DtF) has produced a range of standards on this topic, based around the National Public Transport Access Nodes (NaPTAN) database. The database contains detailed data element designs for site accessibility (e.g. ferry terminal, and train or bus station) and stop (bus stop, ferry pier or train platform) accessibility data. DtF also provide an XML Schema design (v2.5) to provide data to NaPTAN, as well as the TransXChange standard for exchanging bus schedules and related data. TransXChange includes the design for the accessibility data elements.
Transport for NSW API Gateway seems to use TransXChange v2.4, and therefore it is unlikely it contains detailed accessibility data beyond a wheelchair accessibility indicator.
Transport for NSW GTFS release notes clarifying their interpretation of some fields.
Public Transport Victoria seem to have defined Stop Facilities accessibility data in their PTV Timetable API which is stating the level of compliance to the DDA.
European Committee for Standardisation (CEN) – CEN/TR 16427:2013 Traveller Information for Visually Impaired People
GTFS stops.txt
See How does Wheelmap.org work? on the Wheelmap.org FAQ.
All public transport services, including associated infrastructure and public transport vehicles, are subject to the:
- Disability (Access to Premises – Buildings) Standards 2010 (Cwlth)
- Disability Standards for Accessible Public Transport 2002.

Commonwealth Games – Gold Coast 2018 Transport Strategic Plan; 3.3 Games Route Network – “GOLDOC is obliged to provide ‘safe, secure, reliable and accessible transport’ for the Games Family”
Queensland Rail Accessibility Action Plan
Translink Disability Action Plan — Improving Access to 2017
As a passenger, I want to plan my journey from A to B in the most accessible way for me, so that I arrive on time.
As a publisher of GTFS data, I want to derive the wheelchair_boarding field in the GTFS stops.txt file from Transport Stops data so that passengers planning their journey can know if a stop is wheelchair accessible and the vehicle can be boarded.
As a publisher of Transport Stops data, I want to contribute my data to other popular apps (e.g. Wheelmap) so that I increase the options for passengers to plan their journey based on wheelchair accessibility.
As an asset owner, I want to demonstrate my compliance with the law so that my performance is transparent and I can be held accountable.
As a ..., I want to ... so that ...
See Improving access to rail information for disabled passengers by the ODI.

Analysis of data using these sources of information about public transport accessibility in Queensland:

Brisbane data includes accessibility attributes
Logan data
Sunshine Coast bus stop data for bus stops with shelter and without shelter. Data includes DDA Compliant attribute (assume DDA is Disability Discrimination Act)
TRANSLink data. (TRANSLink installs some bus stops.)

The GTFS specification for stops allows a wheelchair boarding attribute to be encoded. This field is not present in the TransLink GTFS data.

The specification will be:

contributed to Open Council Standards to encourage use across all Australian Local Councils
defined as a data package and json table schema.

The specification is being drafted and commented on in this Google Sheet.

Transport stops assets owners will publish their stops data to the standard and using identifiers that make it easy to link to the TMR GTFS data.
TMR derives the wheelchair_boarding field in the GTFS stops.txt file from the Transport Stops data files and published an enhanced GTFS file.
- add wheelchair_boarding field to the GTFS stops.txt file
- default all bus, train and ferry values to 0 (or empty): Indicates that there is no accessibility information for the stop
- default all G:Link tram values to 1: Indicates that at least some vehicles at this stop can be boarded by a rider in a wheelchair.
TMR considers if defaults can be set for wheelchair_accessible in GTFS trips.txt
- default all bus and ferry values to 0 (or empty): Indicates that there is no accessibility information for the trip.
- default all G:Link tram values to 1: Indicates that the vehicle being used on this particular trip can accommodate at least one rider in a wheelchair.
- default all train values to 1 based on this web page.
TMR publishes a json table schema and data package for the GTFS public transport data.

Potential functions:

Potential data consumers:

wheelmap.org (The current tagged Wheelmap overlay for Open Street Map with the extended tags for wheelchair access and toilets). The routing attributes have not been implemented into an algorithm for this map version. There were betas for some towns in Germany. Get the app