Advanced NaPTAN Issues

Why are NaPTAN & NPTG Important for EBSR?

Information from NaPTAN & NPTG is vital for the identification of stops in EBSR & TXC

It is important to make sure that both are accurate before EBSR is introduced

Locations, names, correct links to localities etc. are all important to downstream systems

NaPTAN data is being used in ways and by systems that were never envisaged when they were originally created

It is important to get consistency

NaPTANs & Locality Data Both NaPTAN & Locality data underpin travel

information and EBSR systems EBSR is based on NaPTANs

Route is defined using NaPTANs Data needs to be accurate and consistent NaPTANs & Localities often needs clarification during

the process of conversion from paper to EBSR

Links between NaPTANs and Localities are important for correct positioning of stops, stop names, accurate trip planning (esp. by car) etc.

ITO and NaPTAN Viewer tools have been developed to help manage this data

ITO & NaPTAN Viewer Both systems are available to those

needing to use and manage NaPTAN data ITO system

Mapping and Analysis toolMaps NaPTANs, Localities etc.Provides a series of warnings where data

appears to be inconsistent NaPTAN Viewer

Mapping system Displays details of NaPTANs, Localities etc.

AN EXAMPLE OF AN ITO REGIONAL SUMMARY

ITO provides a summary count of warnings about possible NaPTAN errors

The TRENDS page summarises weekly changes in the numbers of current warnings

The “Per Area” summary provides a count of the number of current warnings in individual areas

Some Examples

Localities with Geocode outside It is important to get localities correctly geo-coded Could impact on EBSR, but will impact on road journey

planning that uses the NPTG Gazetteer

Locality OSGR

NaPTANs in Locality

The NaPTAN Viewer shows in red the stops linked to a locality. This example illustrates that either the locality has a wrong OSGR, or the stops have been linked to the wrong locality

Some Examples

Localities with Geocode outside It is important to get localities correctly geo-coded Could impact on EBSR, but will impact on road journey

planning that uses the NPTG Gazetteer

Locality Shape May indicate that stops are linked to the wrong Locality

Elongated locality shape suggests a possible error in linking of NaPTANs to Localities

The NaPTAN Viewer shows in red the stops linked to a locality. This example suggests that some stops have been linked to the wrong locality

Elongated locality shape suggests a possible error in linking of NaPTANs to Localities

The NaPTAN Viewer shows in red the stops linked to a locality. This example suggests that some stops in Kelso have been linked to the wrong locality

Some Examples

Localities with Geocode outside It is important to get localities correctly geo-coded Could impact on EBSR, but will impact on road journey

planning that uses the NPTG Gazetteer

Locality Shape May indicate that stops are linked to the wrong Locality

Pairs of stops with different names NaPTAN guidance expects stops pairs to normally have

same common name

An obvious pair of stops with different names.

Some Examples

Localities with Geocode outside It is important to get localities correctly geo-coded Could impact on EBSR, but will impact on road journey

planning that uses the NPTG Gazetteer

Locality Shape May indicate that stops are linked to the wrong Locality

Pairs of stops with different names NaPTAN guidance expects stops pairs to normally have same

common name

Stops outside of area boundary This will cause problems with EBSR as it will confuse

operators and interfere with EBSR function checking which LAs should receive copy of registration

TEST 1Indicates NaPTANs linked to a Locality that belongs to a different LA area from the one “owning” them

TEST 2Indicates NaPTANs physically located outside of the LA area “owning” them

Use the “Filter by Authority” funciton in the NaPTAN Viewer to display stops belonging to one Authority. Displays stops outside of Authority Boundary

Two stop prefixed “hal”.One prefixed “mer”.Indicate stops located outside of owning area

The “Filter by Authority” function in the NaPTAN Viewer displays stops outside of Authority Boundary

Stop Naming

Preferred format of stop name in EBSR isLocality, CommonName, Indicator

This combination should provide a unique name for a bus stop

In information systems such as Transport Direct the preferred format contains more detail and appears asLocality, CommonName, Indicator,

StreetName, (SMS Code)

Example of Simple Stop Names in EBSR

Locality NameIndicator & CommonName

Complex Stop Names in EBSRLocality NameIndicator & CommonName

Locality Checks The ITO Viewer shows the extent of

localities Draws a border around NaPTANs associated

with each locality

This can be useful in identifying problems in the association of NaPTANs with localitiesLocalities across rivers“Spikes” in locality shapesOverlapping localitiesOther anomalies

This elongated locality (Roadhead) shows 3 groups of NaPTANs. One in middle and one at both the top and the bottom of Locality shape. The stops are located close to other localities and they may need to be associated with different localities

Examples of overlapping localities – review the allocation of NaPTANs to localities

Example of a Locality crossing a river.

Instances of “Stops in Water” need to be checked in case a stop has an incorrect OSGR.

Stop with an incorrect OSGR?

Archiving NaPTANs

This new facility allows NaPTANs that have been in DEL state for more than 3 years to be archived from the system The data is retained in the system but is not included in

downloads Removes “clutter” from NaPTAN Avoids risk of errors with EBSR Simplifies viewing on NaPTAN Viewer If they are causing real problems, NaPTANs that do not meet

the 3 year rule can be archived on application to TD

Display of DEL NaPTANs

Archived Stops no Longer Shown on NaPTAN Viewer

Display of DEL NaPTANs

Archived Stops no Longer Shown on NaPTAN Viewer

New ITO Functions and Tests

View Stop Areas Shows & Checks Bearings for Stop Points Show Hail & Ride Sections Show Flexible Zones

Tests for Hail & Ride Sections More than 1 km in length Valid start, end and intermediate points

Tests for Stops within 4 metres of each other (2 metres for BCS point)

Display of Bearings on NaPTANs

Bearing appears to be incorrect and needs to be reviewed

Hail & Ride Sections not clearly defined. Unclear as to which roads are served

Well-defined Hail & Ride Sections

Flexible Service Zones