NaPTAN

Overview

  1. What is NaPTAN For?
  2. How are NaPTAN stop points identified?
  3. How can NaPTAN stop points be described?
  4. What is the NaPTAN database?
  5. What is the NaPTAN XML schema?
  6. What is the NaPTAN CSV format?
  7. What is the NaPTAN UML Model?
  8. How do I obtain NaPTAN data?
  9. How do I upload NaPTAN data?

What is NaPTAN for?

NaPTAN provides a unique identifier for every point of access to public transport in the UK, together with meaningful text descriptions of the stop point and its location. This enables both computerised transport systems and the general public to find and reference the stop unambiguously. Stops can be related to topographic regions via the National Public Transport Gazetteer.

NaPTAN consists of the following elements

  1. A standard for identifying and naming access points to public transport
  2. A database of all the access points in the UK
  3. An XML Schema for exchanging stop data as XML documents describing the content. All or part of the database may be exchanged in this format
  4. An exchange format for exchanging stop data as csv files

Underpinning NaPTAN & NPTG are UML Models

The NaPTAN Identifier System

NaPTAN identifiers are a systematic way of identifying of all UK points of access to public transport or 'Stop points'). (Stop Point is the TransModel term). In the UK NaPTAN Stop points are submitted by PTEs to a central service which consolidates the stop data and distributes them back to users. Certain sets of stop point data such as airports and ferry ports are provided nationally.

  • Every UK rail station, bus and coach terminus, airport, ferry terminal, bus stop, tram stop, and taxi rank is allocated a unique NaPTAN Identifier
  • For large interchanges & termini, NaPTAN points identify the entrances from the public thoroughfare - one identifier is distinguished as the main entrance
  • For each stop there are two associated NaPTAN identifiers, each unique within the UK
    1. A 12 character system identifier (the AtcoCode).
    2. A short (7 or 8 digit) version suitable for plating on stops and other public facing systems (the NaPtanCode). This number has been designed to be suitable for use in SMS and other delivery channels requiring direct reference to a stop identifier by the general public. It can be keyed easily on a mobile keypad

NaPTAN Stop Point Descriptors

NaPTAN stop points have a number of text descriptor elements associated with them: not just a name, but also Landmarks, Streets and distinguishing identifiers. These elements can be combined in different ways to provide presentations of names useful for many different contexts, for example on maps, stop finders, timetables etc.

  • Stop Points may have a Common Name, Short name, Landmark, Street, identifier, etc.
  • Stop points may also have alternative names, for example for aliases for  different national languages
  • Stop Names may have a qualifier to distinguish them from other stops with the same name

The NaPTAN Database

The National Public Transport Access Node database holds a current copy of all UK stops. Stops are submitted by PTEs to a central authority which consolidates the stops and distributes them back to users.

The NaPTAN database is maintained centrally under contract to the Department of Transport.


The NaPTAN XML Schema

NaPTAN data is described by a NaPTAN XML Schema. This can be used to describe NaPTAN data when exchanging it between systems as XML documents.


The NaPTAN CSV Exchange Format

NaPTAN data can be exchanged in Comma Separated Variable (CSV) format. The structure of this format is described in full by the NaPTAN documentation.


The NPTG & NaPTAN UML Models

The NPTG & NaPTAN data conforms to a family of consistent, interlocking data models. The models are described in the NPTG & NaPTAN Schema Guide in UML notation


NPTG Model

The NPTG model is made up of NPTG localities. of different types. Each NPTG localities belongs to an NPTG administrative area. NPTG administrative areas are grouped into traveline regions.


Page last updated: 2013.03.23