Bottom     Previous     Contents

3 Allocation of AtcoCodes for new stops

The introduction of Electronic Bus Service Registration makes it essential that a bus operator preparing a new Registration can be given, in confidence, an AtcoCode to be used for each new stop that may be required. That code will be used to reference the proposed stop in the Registration, and the Registration should give provisional details of name, location etc. Whilst the code for each stop, once allocated, must remain unchanged, the attributes of that stop - including its name and coordinates - will be determined by the NaPTAN data manager for the authority. This process should take account of the operator's suggestions, and the results of any site meetings or otherwise to agree precise location details. Once an AtcoCode is allocated, however, it must appear in the local NaPTAN data EVEN IF the new stop is never created for whatever reason ... in such circumstances, the record will simply be flagged as DELeted.

4 NaPTAN codes

These codes, used for the SMS service, must never be reused. Quality checks on the national database should detect any attempt to reuse a NaPTAN code that has been used previously at a different stop, and will block the upload of this data. Both Kizoom and Thales provide tools to ensure the effective allocation of available and valid codes to individual stops.

5 Permanence of NaPTAN data

Because NaPTAN data is used in a wide variety of databases, some of which are long lasting, it is essential that each NaPTAN record is retained permanently. When a stop ceases to exist, therefore, its record must be flagged as DELeted and an explanation of what has happened should be added in the Notes field. But the record of that stop remains in the local NaPTAN database permanently. Consideration is being given nationally to an arrangement whereby batches of such stops may be archived from the live database after a period of time - but such arrangements have not yet been established.

If a stop is moved temporarily, then NaPTAN makes provision (in the Stop Availability section) to create a record of such temporary changes, specifying when the change takes effect and when it will cease.

If details of a stop need to be changed, for whatever reason, the most important point is that the AtcoCode and the NaptanCode should NOT be changed (unless the stop has moved to a significantly different location). But any other element of the data that is associated with a particular stop can be edited - so you can change a name, coordinates, locality-association, stoptype without changing AtcoCode and NaptanCode. To do otherwise will simply increase the number of DELeted records in your database - making it increasingly difficult to manage.

Next     Top