Public Transport Information Coordination GroupIssue Proforma

Reference number / PTIC-086 v0.1
Submitter/Owner / Name:Jonathan Shewell-Cooper
Organisation:Atos (on behalf of DfT)
Email address:
Title/Short description / Incorporatestop level accessibility to NaPTANv2
Issue description / To add accessible journey planning to Transport Direct (and Spectator Journey Planner before that) use has been made of two different levels of stop data. In London TfL maintains “level three path aware” accessibility data in their DIVA database for its stops; whereas for the rest of Great Britain this is largely not available so a capability level two, “stop level accessibility”, dataset was created.
The level three data while being documented in the NaPTANv3 proto-standard is not yet available as a national dataset.
To define the level two data used in Transport Direct, two approaches have been taken:
  1. For National stops – It is assumed that they are not suitable for wheelchairs and there is no assistance available unless it is defined in the IF136 “Transport Direct Accessible Network (TDAN) Stops” dataset. IF136 data defines, for a National Stop, if the stop is suitable for wheelchairs and if there is passenger assistance available at the stop. It also defines the days of the week and times of day the assistance service is available.
  2. For Local stops – it is assumed that if a wheelchair accessible service calls at the stop then it is suitable for wheelchairs. Where this is not the case the NaPTAN for the stop is recorded in the IF157 “Stops not suitable” dataset. This data set will be extended to indicate that if a stop is not suitable for all wheelchair journeys is it suitable for just high floor services or just low floor services. This will better represent the difference between these types of service.
In addition to this if a station is accessible for wheelchairs but has some entrances that do not have accessible routes from the entrance to all platforms then the NaPTAN for that entrance is recorded in the IF157 “Stops not suitable" dataset. This ensures that, for journey planers that use entrances, the entrance is not used in journey plans for wheelchairs.
Both IF157 and IF136 datasets have been supplied to all current Traveline suppliers.
Until NaPTANv3 is a fully populated data set then the accessibility data created by Transport Direct could be incorporated into the NaPTANv2 data set.
In the short term this can be achieved by making IF136 & IF157 available alongside NaPTANv2 data, providing operators and local authorities a method of verifying their contents. The data sets are currently maintained by the DfT’s Manual Data Service
The next step is to incorporate the data from them into the NaPTANv2 schema.
Other features of stops that impact the accessibility of the stop for passengers could include - RNIB Wayfinding React scheme, Public Address, Help Points, Departure screens. This could also be captured as Level 2 data.
Issue manifestation / Level 2 stop availability data is not available as part of the NaPTAN dataset so users of NaPTAN data are unable to incorporate this measure of stop accessibility into their systems.
Issue severity / This is an issue of moderate severity.
Priority code / TBD
Response options / A description of possible responses to resolve the issue, together with an overview of the impact of each
If there is an obvious or preferred response, this should be stated
Add StopAccessibility properties to the NaPTAN StopPoint element. This would be an optional child element that could be used to collect accessibility data.
Outline below - See NaPTAN 2.5 User guide for further details
Response actor / DfT propose to undertake a technical study to investigate how the level 2 data created for Transport Direct can be added to the NaPTAN v2 standard.
Respondent code / TBD
Issue progress / Mar 2013: Issue submitted to PTIC and circulated to PTIC members for comment. To be discussed at PTIC meeting on 13/04/2013.
Status code / [ALLOCATED BY PTIC SECRETARY]

NaPTAN Stop Accessibility

TheStopAccessibility allows the accessibility properties for a stop to be described. These may include

  • Classification of the stop with an overall assessment for accessibility assessment and a basic classification of its accessibility for Wheel chairs, , step free use , lift free use, etc.
  • The type of assistance needed to use the stop and the DayTypes and Timebandswhen it is available. Note that accessibility depends on the type of vehicle as well as the stop. For rail services this will typically be a fixed property of the stop. For bus services it may vary according to the vehicle type. A default indication can be given as to whether most services at the stop are accessible or not:
  • Information about the Operator through which booking is done. .
  • Detailed quantitative values on accessibility such as gap to platform may be captured, as well as a summary classification for end user system