NaPTAN V2.4 Changes 2010 and Relaxed SMS Rules 2011

On 8th December 2010 our systems were updated to accommodate V2.4 changes to NaPTAN and NPTG and be able to accept NaPTAN V2.4 submissions in addition to existing versions. This mostly affects NapTAN submissions, but also affects NPTG viewing and editing.

The format of the downloadable NaPTAN files is unchanged; NPTG XML files have changed slightly. See below for details.

On 9th June 2011 our systems were again updated, to further relax the SMS rules. Specifically any LA may now opt to use alphabetic or numeric SMS codes subject to still being nationally unique. This must be done by notifying the Thales helpdesk and agreeing a timetable for the change.

NaPTAN Upload

The Thales service previously accommodated NaPTAN V2.2, V2.1 and V1 and NPTG V2.1 and V1.

Users now also have the additional option of submitting XML files in NaPTAN V2.4 format.

Submitted XML NaPTAN V2.4 files are validated against the NaPTAN V2.4 schema. However the import and export of the data will be based on the V2.1 or V2.2 schemas and thus any V2.4-specific data will be ignored. The exception to this is the two additional longnames for stop types BCT and BCE. The NaPTAN schema used is NaPTAN V2.4b v52 dated 19 October 2010.

Many of the former rules on SMS codes ("NaptanCode") are no longer applied; the remaining rules are detailed below.

SMS Rules Applied

The set of rules (from 9th June) is:

  • LAs must submit SMS codes in a predefined format: either alphabetic or numeric. An LA can change the predefined format; this must be done by notifying the Thales helpdesk and agreeing a timetable for the change.
  • Numeric SMS codes can contain any digit, i.e. 0-9 inclusive.
  • SMS codes must have the defined prefix (either alpha or numeric) for that particular area.
  • SMS codes must be between 5 and 9 characters (letters or numbers) in length, including the prefix.
  • SMS codes must be unique; i.e. no two stops can have identical SMS codes.
  • An SMS code must also be nationally unique when comparing it's numeric equivelent on a mobile phone keypad.  For example the numeric equivalent of a, b & c is '2'.  So an SMS Code of adgmpmt is equivalent to 2346768.

SMS codes supplied in NaPTAN V2.1 or NaPTAN V2.2 format must also comply with these SMS rules. Other former rules no longer apply.

NaPTAN Download

NaPTAN downloads continue in the current formats. Download in NaPTAN V2.4 format is not provided.

NPTG Viewing, Editing and Download

NPTG locality WGS84 longitude & latitude are now calculated and displayed.

Longitude and latitude values are now included in the downloadable NPTG XML files. They are not included in the CSV files.