1. Stop Data

2. Data Overview NPTG NaPTAN Timetables National Public Transport
Gazetteer
List of localities and hierarchy
NaPTAN
NAtional Public Transport Access Nodes
Stop records. Each stop has a locality code from NPTG
Timetables
List of stops and times for each service

3. Data Overview NPTG NaPTAN Timetable (Metrobus 6)
E Gossops Green
E Crawley (W Sussex)
N Southgate (W Sussex)
NaPTAN
4400CY0299 Bus Station Stand I E
4400CY0300 Bus Station Stand J E
4400CY0272 Dower Walk W-bound E
Timetable (Metrobus 6)
4400CY0300 dep 0910
4400CY0272 arr 0921 dep 0921

4. NPTG Editing

5. NPTG Step 1 - Revise Active locality?
Is this a parent, an alternate name, or neither (stand alone name)?
Change
Link to Multimap
New locality based on this one

6. When is a locality not a locality?
NPTG Step 1 - Revise
When is a locality not a locality?

7. When is a locality not a locality? A second example
NPTG Step 1 - Revise
When is a locality not a locality? A second example

8. When is a locality not a locality? Another example
NPTG Step 1 - Revise
When is a locality not a locality? Another example

9. NPTG Step 2a - Relationships
Localities are listed in order of distance from the parent
Select localities which are the children of the selected parent

10. NPTG Step 2b – Other Names
List of “alternate names”
Current assignment
One that is not assigned. NO STOPS!

11. NPTG Step 2b – Other Names
Currently Shoreham-by-Sea
Arranged in distance order as before
Select to change. Only one alternate name

12. NaPTAN Editing Maintained locally Uploaded to National Database
Can be held in timetable systems e.g. Routewise
Can be held in other systems e.g. GIS
Uploaded to National Database
Version 2, XML imports only.

13. NaPTAN Editing Alternative Descriptors Stops StopAreas Alternative
Locality
Information
HailRide
StopsInArea
Area Hierarchy

14. NaPTAN Editing
Edit stops and areas in Transoniq or application that supports NaPTAN v2 XML natively
When editing is complete, submit file to Thales
Submit just the XML file
Use web site

15. Format of STOPS file (1) ATCOCode Easting / Northing
Anything you like so long as it begins with your area prefix
BUT rail station entrances have a special notation
Easting / Northing
To 1m, but occasionally worth moving to avoid problems such as wrong street in GIS

16. Format of STOPS file (2) Common Name
There are rules! You can find them on the DMS.
Succinct
Don’t include locality unless necessary
“Abingdon School” OK as may be more than one school in Abingdon
“Abingdon Woody Park” probably not OK, as “Woody Park” would be sufficient

17. Format of STOPS file (3) Indicator
Standard terms to qualify the common name
Stop, Bay, Stand, Stance
followed by A, N, AN, NA, NN, NNA or ANN e.g. Bay A3
Opp, Opposite, O/S, Outside, Adj, Adjacent, Nr, Near, Behind, Inside
Long-word versions converted to their abbreviated formats.
can all be followed by N, NN, NNN, NA, NNA, or NNNA e.g. “O/S 32”
“No” / “Number” etc are omitted, as is all punctuation e.g. “O/S No. 32” -> “O/S 32”

18. Format of STOPS file (4) New range of indicators allowed Entrance
Main | Side | Front | Back Entrance
North | East | South | West Entrance
Arrivals, Departures In
Can also have N, A, NA and AN extensions e.g. Entrance 1

19. Format of STOPS file (5)
Unusable identifiers will be thrown away and the direction setting will be used
“Dower Walk / next to Woldhurstlea Close” becomes “Dower Walk (Westbound)”

20. Format of STOPS file (6) Street, Cross Street & Landmark NatGazID
The street that the stop is on, the cross street (if any) and the landmark (if any) that locates the stop
Street is important, as we allow searching on street name
NatGazID
Lowest level that applies
We will handle the hierarchy!

21. What MDV do with it Import NPTG Import NaPTAN
Imports can create additional data structures
You can just worry about the important ones
Imports include data quality checks
You need to look at logs and correct errors!

22. MDV Stop Naming
Stop names are created from Common Name, Identifier and NatGazID
Format is Locality, Common Name (Identifier)
We also create links for hierarchy
In the example above, you can refer to the stop being in either Three Bridges or Crawley.

23. MDV Stop Naming
MDV stop concept is at stoparea (DIVA stop) level, with a NaPTAN stop being referred to as a DIVA Platform, or stopping point.
Stopping points need a unique identifier.
A stoparea (DIVA stop) can have a different name from the stops in the stoparea, but DfT (and SELTA) guidance is to avoid doing so unless unavoidable.

24. MDV Grouping
It can be hard work creating and maintaining groups for every pair of stops!
Why worry! Sit back and relax, and let MDV do the work for you…

25. MDV Grouping
If two stops have the same common name, and are in the same locality, and are within 150m of each other, MDV will automatically group them.
They will carry on adding stops into the group as long as no stop is more than 250m from any other stop in the group

26. MDV Grouping Why is this important?
You can walk to a stop at the start of a trip and you can walk from a stop at the end. But interchange mid-trip is only possible within a group.

27. MDV Grouping
Remember the stop model. Each stoparea (DIVA Stop) should ideally have the same common name as the stops within it
DIVA stops which are grouped together are linked by FOOTPATHS

28. Explicit or Implicit Grouping?
Use NaPTAN stopareas:
always for every major interchange node (e.g. bus stations, rail stations)
if you already have stopareas defined in your data
if you want to include stops with different names in the same group (although not recommended)
if you want to include the stoparea in a super-group (interchange possibilities)
if you want to group stops which are more than 250m apart (max 500m)
Otherwise, let MDV do it!

29. Example of Grouping
Explicit grouping
Implicit grouping

30. Footpaths vs Assignment
MDV can link stopareas by FOOTPATH and by ASSIGNMENT
Take example of rail station with bus stops on main road.
Stopareas linked with footpaths, user given walk from bus stops to rail station
Stopareas assigned, user told to go to bus stop and that’s it
Even with assignments, must be footpath AS WELL or journeys through the rail station cannot be made
Assignments can be confusing for user if names are different
SE has turned assignments off

31. Localities. Main shown first, then parents and/or aternates
How to read the DMS
ATCOCodes in group
Identifiers
DIVA Stop Number
Name as it appears on the timetables and journey planner, plus alternates
Group ID
Link to Map
Linked DIVA Stop
F = Footpath
A = Assignemt
Localities. Main shown first, then parents and/or aternates

32. What can we do better? Use the DMS. Check it regularly.
For example, here is a historic example of a really glaring error:
Someone mis-selected the locality!

33. What can we do better?
Here is something else that was a “gross error” example.
Zero coordinates are sloppy, and should be rejected by the import validations now
If you don’t understand the errors, ask!

34. What can we do better Hail and Ride coordinates
Normally, the system will route a bus along the road network from stop to stop
For HAR sections, it ADDITIONALLY uses the START coordinate and the END coordinate for routing
Often these are incorrect, or wrong way round
Leads to incorrect / confusing route maps as system tries to serve points in right order