All,

NaPTAN v2 will be deployed next Wednesday, 25th January 2006.

The changeover will be made on that day, so please note that there will be no NaPTAN submissions carried out on Wednesday 25th January. Data received here on Tuesday 24th January will be held and submitted on Thursday 26th.

Also on Wednesday 25th, the Journeyweb website will not be available for data downloads, or for uploads either directly or via ftp. The on-line gazetteer editing facility will also not be available on that day.

Calls and emails to the Helpdesk will not be affected.

From Thursday 26th January, submissions and on-line facilities will be resumed.

From 26th January 2006, NaPTAN data may then be submitted either in v1 format (as now) or in the new v2 format.

Data downloads can then be obtained in either the current v1, or the new v2 format.

 

Those authorities that are not yet in a position to submit or use V2 format data will not be affected by these changes immediately, since the current V1 format will be maintained until the end of 2006. The Department for Transport is currently providing all authorities with new software that will enable them to maintain NaPTAN records in V2 format .

 

Please be aware that some data modification may be performed when V1 submissions are imported into the National Database to conform to the V2 rules. These are detailed in the tables below:

 

Table 1: V1 Import Data Modifications

No.

Description

Action at V1 Import

Applies to Import Type

1

Restricted characters in name fields -  Characters from table 3-2 of V2 Schema Guide not allowed in any "name" fields for Stops and Groups

Invalid characters replaced with value from lookup table (see table 2 below) - warnings in import log when replaced.

XML and CSV

2

Street has NULL value - current V1 states these are mandatory

Set to TBA - warnings in import log when done.

XML

3

Invalid value for BusRegistrationStatus - For BCT stops, valid values for BusRegistrationStatus are PPT, TIP, PTP, OTH. For BCS or BCQ stops, valid values are NULL or PPT, TIP, PTP or OTH

If no value supplied, default of OTH will be used. Warnings in import log when done.

XML

4

Invalid value for BusStopType - For BCT stops, valid values for BusStopType are MKD, HAR, CUS, (FLX in V2)

If no value supplied, default of MKD will be used. Warnings in import log when done.

XML

5

HAR stops without HailAndRideSection

Dummy HailAndRideSection created. Warnings in import log when done.

XML and CSV

6

Easting and Northing with negative values in Stops and Groups

Set to 0. Warnings in import log when done.

XML and CSV

7

Invalid BCT Direction - There are some BCT stops with direction of NA

Set to N. Warnings in import log when done.

XML

8

Groups with more than one Parent Group

Group rejected

XML and CSV

 

 

Table 2: V1 Import Stop Name restricted character replacements

Character

Name

Why character is reserved.

Replacement Character

,

Comma

Used as separator for qualifier

.

[

Left Square Bracket

Used to format output

(

]

Right Square Bracket

Used to format output

)

{

Left Brace

Used to format output

(

}

Right Brace

Used to format output

)

^

Caret

Inappropriate

-

=

Equals

Inappropriate

-

@

at

Inappropriate

at

:

colon

May be used to format output

-

;

semicolon

May be used to format output

-

#

hash

Input expression

-

$

Dollar

Input expression

-

£

Pound

Inappropriate

-

?

Question mark

Inappropriate

-

%

Percent

Input expression

-

 

These replacements are performed on the following fields:

Stop->CommonName

Stop->Street

Stop>Identifier

Stop->Landmark

Stop->Town

Stop->Suburb

AlternativeDescriptors->Name

Group->Name

 

 

Please contact us if you have any queries or concerns about this.

Regards,
Jean

Jean Crowley
JourneyWeb Data Manager
Thales Services Division