1. EM NaPTAN data
22 November 2008
Nottingham

4. Importance of updating
Importance of updating NaPTAN frequently
immediately when something changes
at least every month EVEN IF NO CHANGES
Upload on or before Wednesdays for next week’s regional build
Upload is ready for download two working days later
Ito has it one working day after that
NaPTAN viewer upload is fortnightly – see site for dates (last was 19 November)

5. Error 14
A NaPTAN stop has been included in the definition of two Groups, so neither is accepted.
Simple problem – in this case the referenced stop should not be included in 260GCC18303

6. Error 18 NPTG identifier is not in current NPTG data
Two errors – 6 error reports
Newbigg ought to be Westwoodside E ?
Ferriby Sluice ought to be South Ferriby E

7. Error 20
Common name for stop should not include information about bays - this should be in identifier field.
Position!
Naming!

8. Error 20 Position – coordinates clearly are wrong
Naming – one currently shows as
Uppingham, Stop 4 (outside) [and stops 1, 2, 3]
“Stop 4” should be the indicator
What should be the “CommonName”?

9. Error 21
There is a reference to a Group within the GroupsinGroup file that is not listed in the Groups definition file.

10. Error 22
The stop is more than, currently, 10km from the centre of the locality it has been attached to.
109km and 170km from Nottingham!
339GST15 has coordinates of , – northing is wrong!
339GCL60 has coordinates of , – easting is wrong!

11. Error 23
Distance too large, maximum distance between DIVA-stops more than 500m
Error appears to have been corrected in past few days

12. Error 26 NaPTAN Coordinate outside LTA region
Would appear to be an error in the boundary information – MDV has been asked to check

13. Error 29 NPTG-ID not valid within the LTA area
Ito also shows locality shape issue
Locality for this stop should be E Braunstone

14. Error 31 StopArea ID not found in stopareas.csv
227G is marked as DEL in stopareas, but has three stops in stopsinarea
Etc.

15. Error 36 Coordinate outside LTA region for NaPTAN-Group
Example appears to have been removed from Lincs data very recently? (and coordinate was in middle of a field)

16. Error 41
Stoparea contains elements which are not all associated with the same NPTG locality.
The primary locality for all stoppoints in a stoparea must be the same – but alternative localities can be used in addition where relevant

17. Error 43 There are two Groups in NaPTAN which have the same name.
“Oakham Rail Station” is a reserved name for national rail stations … local bus stoparea needs to be “Oakham Railway Station”
MDV has been alerted to a legacy issue here with station stoparea names not coming from NaPTAN – this will be corrected

18. Error 43
13419 is Newhall Wellwood Road, as is – can’t have two stopareas with same name
14150 has already been renamed very recently – fixed!

19. Further comment on example
13149 group – stoparea name does not match commonnames of stoppoints
Wellwood Road (opp) and Wellwood Road (adj) don’t make sense for stops on Wellwood Road

20. Error 44 Group changed, new name exists already
Both pairs are the result of there being three “West Bridgford” localities – reduce these to just one!
stoparea names not yet matching stoppoint names – also unhelpful
Stop indicator for Fox Road (o/s) should be Fox Road (opp)

21. Error 50
Distance between two stops within a DIVA stop is more than 250m
(either an error in the creation of an automatic group, or from the black stops list of stops which are not being updated automatically).
Cause in these cases – too many stops with the same commonname (such as Tennyson Road)

22. Error 55
The distance between a child group and a parent group is more than the prescribed limit.
These two look like incomplete stoparea – may need two GPBS areas with a super-area to link them
error report indicates coordinate error for stoparea, as clear in Ito map

23. Error 77 Similar identifiers in one DIVA-stop
Identifier “YYY” is created by mdv import when there is nothing else to work with
See next slide

24. Indicator must not be in the CommonName
Bay 1 etc is in landmark – not appropriate
Outside/inside is in the Indicator field – it should contain Bay 1 etc
Haymarket H1 likewise should be Haymarket as commonname – and Stop H1 as indicator

25. Even with the locality in front, where are these stops?
Assume that these should have the name of a bus station, or a road name or an area name as the commonname
Once again the Stand reference is in Landmark – it should be in Indicator

26. Error 81
Coordinate outside GB region for HAR (or other coordinate problem with HAR record)
Self-explanatory error message – entry and exit points are identical

27. Error 82
The coordinates of one end of the HAR section and the DIVA stop to which it is attached is too great. Generally HAR sections should be no more than 500m long in urban, and 2km long in rural areas.
Each case needs examining – if rural and <1km OK, if <2km consider splitting

28. Error 83
The distance between the two ends of the HAR section is too great.
Generally HAR sections should be no more than 500m long in urban, and 2km long in rural areas.
Example is clearly wrong – 154Km! Coordinates of exit point are wrong

29. Error 84
The NAPTAN-stops have the same common name but they cannot be grouped to one DIVA-stop because of the distance.
Typically stops have the same name but shouldn’t
Looks as if some of these examples have already been corrected recently
Indicators are inappropriate on some of these stops