1 / 48

Advanced NaPTAN Issues

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

ena
Télécharger la présentation

Advanced NaPTAN Issues

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Advanced NaPTAN Issues

  2. 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

  3. 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

  4. ITO & NaPTAN Viewer • Both systems are available to those needing to use and manage NaPTAN data • ITO system • Mapping and Analysis tool • Maps NaPTANs, Localities etc. • Provides a series of warnings where data appears to be inconsistent • NaPTAN Viewer • Mapping system • Displays details of NaPTANs, Localities etc.

  5. AN EXAMPLE OF AN ITO Regional Summary

  6. ITO provides a summary count of warnings about possible NaPTAN errors

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

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

  9. 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

  10. Locality OSGR NaPTANs in Locality

  11. 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

  12. 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

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

  14. 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

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

  16. 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

  17. 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

  18. An obvious pair of stops with different names.

  19. 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

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

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

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

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

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

  25. Stop Naming • Preferred format of stop name in EBSR is • Locality, 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 as • Locality, CommonName, Indicator, StreetName, (SMS Code)

  26. Example of Simple Stop Names in EBSR Indicator & CommonName Locality Name

  27. Complex Stop Names in EBSR Indicator & CommonName Locality Name

  28. 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 localities • Localities across rivers • “Spikes” in locality shapes • Overlapping localities • Other anomalies

  29. 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

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

  31. Example of a Locality crossing a river.

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

  33. Stop with an incorrect OSGR?

  34. 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

  35. Display of DEL NaPTANs

  36. Archived Stops no Longer Shown on NaPTAN Viewer

  37. Display of DEL NaPTANs

  38. Archived Stops no Longer Shown on NaPTAN Viewer

  39. 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)

  40. Display of Bearings on NaPTANs

  41. Bearing appears to be incorrect and needs to be reviewed

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

  43. Well-defined Hail & Ride Sections

  44. Flexible Service Zones

More Related