Creating NaPTAN

Creating and Updating NaPTAN

Data can be prepared either in a comma separated variable (CSV) format files or in XML probably as part of a data entry application. Suppliers of systems to manage the entry of data in XML format are:

(please notify any other products)

All suppliers are asked to include in their software additional data checks over and above those checked for in the NaPTAN schema. The latest checks are listed in version 1a.

Keyboard Characters

Avoid using , [ ] { } ^ = @ : ; # $ £ ? % see an Explanation about Non-permitted characters

Deleting records

If a bus stop is no longer in use the Record Status should be changed from ACT to DEL and the Last Changed date updated. The record should then remain in the NaPTAN feed so that historic data, for instance used for accessibility planning, will always know where the stop was. Other fields should be left intact.

Some systems move the DEL records to an archive or allow them to be hidden so that they are out of the way of current processing and cannot be used in error. On the NapTAN viewer DEL records are marked by an X symbol

NaPTAN2 has some facilities for putting a bus stop temporarily out of use.

If a bus stop has been deleted it can be made active again by changing the Record Status from DEL to ACT.

A stop with Record Status PEN is one that has not be submitted by the local authority in more recent uploads and has been restored from previous records. All stops like this need to be attended to by the local authority and made part of their regular submission, probably with Record Status DEL.

Adding records

A bus stop may need to be created in the data before it has gone through the full local authority consultation process. This is a bit controversial but will be necessary to make electronic bus registration work.

A bus operator or local authority contracting department may request a new stop. It is best to provisionally agree as precise coordinates as possible and allocate an ATCO Number in the local authority's numbering scheme. NaPTAN2 has some facilities for putting a bus stop temporarily out of use and it may be possible to use this to ensure that the bus stop does not display on maps while the consultation process to locate the stop proceeds.

ATCO Numbers are composed of three parts:

local authority PATS number which is a three digit code.
the fourth digit which is always zero (or G for a StopArea)
up to 8 digits which are unique with the authority area.

It is not necessary, and best not, to pad the number out with zeros to make it up to the maximum 12 digits in length. Keep it short.

Use Notes

The NaPTAN record format includes a notes field. It will help others using your NaPTAN records if you include a brief note of why a stop has been inserted, deleted or a correction made.

Dating of Records

Some systems look at the dating of records and only import those that have changed. Whatever change you make remember to update the date the record was created or modified.

Custom and Practice or Hail and Ride

Most Bus Stop Type BCT records have the Bus Stop Type as MKD referring to a marked stop. If there is no marked stop then the CUS or HAR records can be used.

CUS - use this for a point where buses are known to set down and/or pick up passengers. It may be that there is a marked bus stop on the other side of the road.
HAR - use this for a section of road where buses will stop for passengers anywhere it is safe to do so. If there bus service goes in each direction HAR stops will need to be set on each side of the road. Locate them about half way along the section of road. For each HAR stop that is marked a corresponding entry must be placed in the HailRide.csv file that gives the coordinates for the start and end of the section of road. Don't make the length of road too long as the departure time advised to passengers would become inaccurate.

Naming of stops

In NaPTAN1 great attention was paid to the correction plotting of the position of the stop but it was accepted that existing database names could be used to populate the various fields. This has led to many different naming conventions and it is an objective of NaPTAN2 that the names will be held in a more structured way. This is Stage 2 of the process of migrating to NaPTAN2 and no date has yet been set for completion of this work. In some authorities the naming convention is so tied up with other systems that it may be difficult to achieve this.

Locality Name, formerly called NatGazLocality is a good place to start. There is a bit of an art to choosing the right locality. Usually you will choose the nearest one. However the road network and local geography may indicate that you choose the next nearest. However you should always avoid leap frogging a locality as this will cause confusion. You may need to set up a new locality Name.

The LocalityCentre flag (set to Y or N) can be used to denote whether the stop, perhaps with one or more others, should be regarded as the centre of the locality.

Short Common Name This is a new field in NaPTAN2 but is good for concentrates the mind. How short is a length that you determine locally dependant on your infrastructure. However some ticketing systems look for a name of no more than 15 characters. This can include abbreviations and it may be appropriate to include the locality name or part of it.

Common Name Having got the Short Common Name and Locality you can identify a Common Name which should still short but not as constrained as the Short Common Name. It should also be suitable to be presented as Locality+Common Name so should not normally include the Locality name. Very mundane names such as Cross Roads, or letter box are ok because they can be associated with the Locality Name.

The advice is to try and avoid street names, especially the names of long streets. (Here the advice comes into conflict with naming conventions that have deliberately chosen street names because they change less frequently than landmarks). If a street name is to be used it should preferably be that of a cross street or a short street that the bus stops are located on.

Indicator formerly called Identifier, is used to describe the stop more precisely in relation to the Common Name. It should be kept as short as possible. It can be used in some the following ways:

opp, o/s, adj can be used on their own to explain the relationship to the Common Name.
opp, o/s, adj or towards can be used with another name to support the Common Name. Eg opp Post Office
Bay, Stop, Plat, Stance etc number can be used. Eg Stop A, (see also Bus Stations)

Direction (Bearing)

All points with BCT Stop Type should have a direction N NE E SE S SW W NW. For other stop types the direction is NA.

The direction should be the orientation of the road at the bus stop itself whatever the general direction of the bus service. So if a bus is generally moving in a northerly direction it may due to corners in the road network pass a stop with direction code S.

Bus Stations

A stand in a bus station will have Stop Type BCS, Bus Stop Type MKD and direction NA. It may be associated with Stop Type records BCE for Bus/Coach station entrances.

In NaPTAN2 there is a new Stop Type BCQ which where stand allocation may be variable. It may be particularly useful for coding bus arrivals. The exact location of this should probably be near the vehicle entrance to the bus station and possibly separate BCQ stops for each vehicle entrance. The exact use of BCQ stops is being considered at the moment and more advice will follow.

Uploading revised data

See guidance on how to upload the revised data to Thales so that it is available for others to download.

Check when you last updated your NaPTAN data.