National Street Gazetteer - Iahub.net

1 BackgroundThe NSG provides the nationally definitive dataset for street references (USRN’s) linked tothe names and extents of streets associated with them in England and Wales. TheAdditional Street Data (ASD) is not a nationally definitive dataset, rather it is an abstract ofdata collated from other sources. Many of these sources are legally definitive (e.g. TrafficRegulation Orders (TROs), Public Rights of Way (PROW) definitive maps, s36 HighwayAgency (HA) List of Streets and the ASD designations should not be considered to be alegal substitute for them.Integrity between Local and National gazetteers is maintained by the use of full update files.The NSG implementation of BS 7666:2006 also includes a number of supplementary itemsto support the service delivery requirements and use of street data within central and localgovernment.The new version of the data transfer format for Local Street Gazetteers will be known asDTF7.1. The version of the data transfer format prior to this will be known as NSG CSV.From the 6 th April 2009 versions in both DTF 7.1 and NSG CSV will be made available fordownload from the NSG website.From the 1 st April 2010, only DTF 7.1 will be made available.This document covers the following: BS7666:2006 and DTF 7.1 DTF 7.1 overview of changes NSG Download mechanism NSG Publication datesAdditional information can be found on the NSG website(http://www.thensg.org.uk/iansg/link.htm?id=2008) relating to the DTF 7.1 specification, DataEntry Conventions and the mechanism for handling data for the new Unitary organisations:DTF 7.1 SpecificationDTF 7.1 Data Entry Conventions documentEDG documentFor information on the New Roads and Streetworks Act (NRSWA) and the ElectronicTransfer of Notices (EToN) Technical Specification please visit the following website:http://www.dft.gov.uk/pgr/roads/network/local/streetworks/cop/pdfelectronictransnotices.pdfUtility and Statutory Undertaker DocumentVersion 1April 2009Page 4

2 BS7666:2006 and DTF 7.1A summary of changes to the data transfer format to accommodate the changes toBS7666:2006 and the implementation of new ASD records are shown in the table below:Data Affected due to transformation of data from DTF 7.1 to NSG CSVRecord TypeType 11 (Street Record)Data affectedStreet descriptor, locality, town, administrative area and allAlias street information removed.Type 13 (ESU Record)Type 15 (Street Descriptor)Direction of travel flag - one way street informationNew record type created to incorporate street descriptor,locality,town, administrative area and language flag insupport of dual language for Welsh AuthoritiesType 21 (Additional Street Data) Renamed to Type 61Type 22 (Street Reinstatement) Renamed to Type 62Type 23 (Special Designation) Renamed to Type 63Type 64 (Height, Width and WeightRestriction)Type 65 (One Way StreetExemptions)New record type created to incorporate Height Width andWeight RestrictionsNew Record type to show exceptions for One Way streetrecordsMore information on the DTF 7.1 specification can be found in the Resources section of theNSG website (http://www.thensg.org.uk/iansg/link.htm?id=2008) in the document titled„National Street Gazetteer DTF 7.1 Specification‟.Information relating to the Data Transfer format for each record type and the mechanism fordata delivery is included within this document.Utility and Statutory Undertaker DocumentVersion 1April 2009Page 5

3 DTF 7.1 Translation to NSG CSVAs defined in the letter distributed by LGIH on Dec 23 2008 1 and the EToN 5.01 TechnicalSpecification, NSG CSV data will also be made available for download at the hub from 6 thApril 2009. From 1 st April 2010 only the DTF 7.1 format will be available for download fromthe NSG hub.What does this mean for utilities and statutory undertakers?Each local highway authority will submit data in the DTF 7.1 format from 1 st April 2009 andthis will be transformed into NSG CSV data and published on the NSG website. Thefollowing record types will be specifically affected due to the translation of data:Data Affected due to transformation of data from DTF 7.1 to NSG CSVRecord Type Data affectedType 11 USRN version number will always be set to 1All Alias street fields will be completed for Welsh AuthoritiesType 12 Cross reference version ID will always be set to 1USRN version number will always be set to 1Type 13 ESU Version number will always be set to 1Type 14 ESU Version number will always be set to 1Type 21Type 22Type 23Data not affectedData not affectedData not affected1 ‘LGIH EToN 5.01 Implementation Letter‟ located on the NSG website:http://www.thensg.org.uk/iansg/link.htm?id=2008Utility and Statutory Undertaker DocumentVersion 1April 2009Page 6

4 Downloading NSG DataA change has been made to the download mechanism on the NSG hub to accommodate theNSG CSV option offered to utilities and statutory undertakers. This can be accessed byfollowing these steps:Step 1: Log inLog into the NSG website (http://www.thensg.org.uk/iansg/link.htm?id=9) using your existingusername and password. Once you login, navigate to the ‘Download’ link.Step 2: Agree to licensing agreementClick ‘Accept’ on the licensing agreement provided that you meet the conditions of use andare downloading data on behalf of your employer as indicated on this page.Step 3: DownloadYou will then be presented with the following screen:Utility and Statutory Undertaker DocumentVersion 1April 2009Page 7

Clicking on the ‘CSV Data’ tab will allow you to download the translated NSG CSV data inthe way you do currently and each file is a self extracting zip file.Alternatively, the ‘7.1 Data’ tab will allow you to download DTF 7.1 data.Note: Record Type 64, Record Type 65 and Direction of Travel information is notavailable in the transformed NSG CSV data.5 NSG Publication TimetableThe NSG will be published on the following dates. Any changes to these publication dateswill result in notification emails and news articles published on the NSG website.5.1.1 NSGPublication TimetableNSG Edition Publication Date DTF 7.1 NSG CSVMarch 2009 06/04/2009April 2009 06/05/2009May 2009 02/06/2009June 2009 02/07/2009July 2009 04/08/2009August 2009 02/09/2009September 2009 02/10/2009October 2009 03/11/2009November 2009 02/12/2009December 2009 05/01/2010January 2010 02/02/2010February 2010 02/03/2010March 2010 02/04/2010Utility and Statutory Undertaker DocumentVersion 1April 2009Page 8

6 Appendix 1 – NSG CSV format specification.The following section details the structure of each record type as prescribed by theDepartment of Transport (DfT) Technical Specification for the Transfer of ElectronicNotifications (EToN v.5.0).Header Record (Type 10)Trailer Record (Type 99)Street Record (Type 11)Street Cross-reference Record (Type 12)Elementary Street Unit (ESU) Record (Type 13)ESU Cross-reference Record (Type 14)Additional Street Data Record (Type 21)Reinstatement Designation Record (Type 22)Special Designation Record (Type 23)6.1 Header Record (Type 10)The Header Record must be the first record in every volume. The structure and format ofdata is shown in Table 6.1.1.In the following table Type I = Integer, Date = Date, S = String6.1.1 Header RecordFieldDescriptionType /MaxLengthValueRangeStatusRECORD_IDENTIFIERSWA_ORG_NAME_TEXTIdentifies the record as aheader recordName of the organisationproviding the data.I 2 10 ManS 40SWA_ORG_REF User organisation DfT code. I 4 1-4 ManPROCESS_DATEVOLUME_NUMERProcess date. The date whenthe NSG CSV transfer set wascreated.The Volume SequenceNumberDate 1998-04-01to presentdateManManI 2 1 ManAn example of a Type 10 Record is as follows:10, “HIGHWAY AUTHORITY”, 1234, 2008-08-08,1Utility and Statutory Undertaker DocumentVersion 1April 2009Page 9

6.3.1 Street Record (Type 11)Field Description Type Value StatusSTREET_DESCRIPTORName, description or streetS 100ManNumberLOCALITY_NAME Locality name S 35 OptTOWN_NAME Town name S 30 ManADMINISTRATIVE_AREA Highway authority name S 30 ManALIAS_STREET_DESCRIPTORName, description or streetS 100Optnumber alias for the streetALIAS_LOCALITY_NAMELocality name alias for theS 35OptStreetALIAS_TOWN_NAMETown name alias for theS 30OptStreetALIAS_COUNTY_NAMECounty name alias for theS 30OptStreetSWA_ORG_REF_NAMINGThe DfT code of the StreetNaming Authority, or the LHAif a numbered streetI 4DfT CaptureCodeManSTREET_VERSION_NUMBERA sequential numberindicating the version of therecord.I 4 1-9999 ManSTREET_ENTRY_DATEThe date on which the recordwas entered or a new versioncreated.D1990-01-01 toPresent day +1 yearManSTREET_CLOSURE_DATEThe date on which the recordwas closed or a new versionreplaced the record.D1990-01-01 toPresent day +1 yearOptSTREET_START_XThe X (easting) co-ordinate ofthe start point of the street.I 7 80000 –656100ManSTREET_START_Y The Y (northing) co-ordinate I 7 5000 – ManUtility and Statutory Undertaker DocumentVersion 1April 2009Page 11

6.3.1 Street Record (Type 11)Field Description Type Value Statusof the start point of the street. 657700STREET_END_XThe X (easting) co-ordinate ofthe end point of the street.I 7 80000 –656100ManSTREET_END_YThe Y (northing) co-ordinateof the end point of the street.I 7 5000 –657700ManSTREET_TOLERANCEThe tolerance of the start andend co-ordinates (in metres)I 3 0-999 ManAn example of a Type 11 Record is as follows:11,12345678,1,“STREET”,“”,“TOWN”,“AUTHORITY”,,,,,1234,1,2006-06-06,,123456,234567,345678,456789Table 6.3.2 shows the valid values for RECORD_TYPE.6.3.2 StreetRecord TypesTypeRECORD_TYPE1 Designated Street Name2 Street Description3 Street Number4 Unofficial Street NameUtility and Statutory Undertaker DocumentVersion 1April 2009Page 12

6.4 Cross Reference Records (Type 12 Records)This section details the structure of a street cross-reference record followed by an examplerecord. The structure of the Type 12 Record is shown in Table 6.4.1In the following table Type I = Integer6.4.1 Street Cross-ReferenceRecord (Type 12)Field Description Type Value StatusRECORD_IDENTIFIERXREF_TYPEUSRNUSRN_VERSION_NUMBERXREF_IDXREF_VERSION_NUMBERIdentifies this record asSTREET_XREF record.Identifies the type of recordthat is being crossreferenced.Unique street referencenumberA sequential numberindicating the version ofthe street for which thecross reference appliesCross references to otherrepresentations of thestreetA sequential numberindicating the version ofthe street that is beingcross-referenced.An example of a Type 12 Record is as follows:I 2 12 ManI 1 1 or 2 ManI 8 ManI 4 1-9999 ManI 14A valid USRN(XREF_TYPE= 1) or anESUID(XREF_TYPE= 2)ManI 4 1-9999 Man12,2,12345678,1,123456234567,16.5 Elementary Street Unit (ESU) Records (Type 13 Records)ESU records are compulsory for Level 2 and 3 Street Gazetteers. However, there may besome Level 1 Streets in a Level 2 or 3 Gazetteer for which there are no ESU records.This section details the structure of an elementary street unit record followed by an examplerecord. The structure of the Type 13 Record is shown in Table 6.5.1In the following table Type I = Integer, D = Date6.5.1 ESU Record (Type 13)Utility and Statutory Undertaker DocumentVersion 1April 2009Page 13

Field Description Type Value StatusRECORD_IDENTIFIERIdentifies this record as an ElementaryStreet Unit (ESU) record.I 2 13 ManESUIDMid-point British National GridCoordinate of the ESU. A uniqueidentifier for the ESU.I 14ManESU_VERSION_NUMBERESU_ENTRY_DATEA sequential number indicating theversion of record.The date on which the record wasentered or a new version created.I 4 1-9999 ManD1990-01-01to presentdate + 1yearManESU_CLOSURE_DATEThe date on which the record wasclosed or a new version createdD 1990-01-01to presentdate + 1yearConNUM_COORDThe total number of coordinate pairsthat define the streets geometry. Thisnumber includes the start and endcoordinates held in the ESU record andany additional ESU_COORDS recordsI 5 2 - 99999 ManESU_START_XThe X (eastings) co-ordinate of the startpoint of the ESU. Co-ordinates aredefined in metres.I 7 80000-656100ManESU_START_YThe Y (northings) co-ordinate of thestart point of the ESU. Co-ordinates aredefined in metres.I 7 5000-657700ManESU_END_XThe X (eastings) co-ordinate of the endpoint of the ESU. Co-ordinates aredefined in metres.I 7 80000-656100ManESU_END_YThe Y (northings) co-ordinate of the endpoint of the ESU. Co-ordinates aredefined in metres.I 7 5000-657700ManESU_TOLERANCEThe tolerance of the start and end coordinates.Tolerance is defined inmetres.I 3 0-999 ManAn example of a Type 13 Record is as follows:13,12345678765432,1,2008-08-08,123456,234567,345678,456789,10Utility and Statutory Undertaker DocumentVersion 1April 2009Page 14

6.6 Elementary Street Unit Coordinate Records (Type 14 Records)This section details the structure of an elementary street unit cross-reference record followedby an example record and then a list of the compliance checks undertaken when asubmission is made.The structure of the Type 14 Record is shown in Table 6.6.1In the following table Type I = Integer6.6.1 ESU Coordinate Record (Type14)Field Description Type Value StatusRECORD_IDENTIFIERIdentifies this record as anESU_COORDS record.I 2 14 ManESUID The Unique ESU Identifier I 14 ManESU_VERSION_NUMBERCOORD_NUMESU_X_COORDESU_Y_COORDA sequential number indicatingthe version of the ESU whichthe co-ordinates refer to.Sequential counter of the coordinatesfor an ESU. Starts at2. Indicator as to the order ofthe co-ordinates for an ESU.The X (eastings) co-ordinate ofan intermediate point on theESU. Co-ordinates are definedin metres.The Y (northings) co-ordinate ofan intermediate point on theESU. Co-ordinates are definedin metres.I 4 1-9999 ManI 5 2-9999 ManI 7I 780000 -6561005000 - 657700ManManAn example of a Type 14 Record is as follows:14,12345678765432,3,1234567,23456786.7 Additional Street Data (ASD Type 21 Records)This section details the structure of the additional street data record followed by an example.Utility and Statutory Undertaker DocumentVersion 1April 2009Page 15

The Additional Street record is used to supply additional street attribute data for the NSG.This information is only supplied for Type 1 and Type 2 Streets (i.e. designated street namesand street descriptions).There should be at least one ADDITIONAL_STREET (TYPE 21) record for every STREET(Type 11) record owned by the Highway Authority. However, additional street data shouldnot be submitted by a local authority for Highways Agency trunk/motorway records, WelshAssembly Group trunk roads or Transport for London streets.The structure of the Type 21 Record is shown in Table 6.7.1In the following table Type I = Integer, S = String6.7.1 Additional Street Data Record(Type 21)Field Description Type Value StatusRECORD_IDENTIFIERIdentifies this record asADDITIONAL_STREET record.I 2 21 ManUSRN I 8 ManADDITIONAL_STREET_SEQUENCE_NUMBERSWA_ORG_REF_AUTHORITYWHOLE_STREETADDITIONAL_STREET_LOCATION_TEXTDISTRICT_REF_AUTHORITYSWA_ORG_REF_MAINTAINING_DATADISTRICT_REF_MAINTAINING_DATASTREET_ADOPTION_CODESWA_ORG_TYPESTART_XSequential number for each street eachadditional street information recordCode for the authority that has interest inthe streetFlag to indicate whether additional streetinformation applies to the whole streetDescription of the parts of the streetwhere the record is applicable.The code for the Operational Districtwithin the authorityA code for the organisation responsiblefor maintaining the data on the streetThe code for the Operational Districtwithin the maintaining authorityresponsible for maintaining the street dataStreet Adoption Status (Road status) asdefined within the DfT Data CaptureCodesThe code indicates the nature of theinterest of that the organisation has on thestreet. Defined within the DfT CapturecodesThe X (eastings) co-ordinate of the startpoint. For part road designations onlyI 3 ManI 4I 1S120See DfTCode0 – PartialStreet1 – WholeStreetManManConI 3 1 – 999 ManI 4See DfTCodeOptI 3 1 - 999 OptI 2 Table 6.7.2 OptI 1 Table 6.7.3 ManI 780000 -656100START_Y The Y (northings) co-ordinate of the start I 7 5000 - ConConUtility and Statutory Undertaker DocumentVersion 1April 2009Page 16

6.7.1 Additional Street Data Record(Type 21)Field Description Type Value StatusEND_Xpoint. For part road designations only 657700The X (eastings) co-ordinate of the endpoint. For part road designations onlyI 780000 -656100ConEND_YThe Y (northings) co-ordinate of the endpoint. For part road designations onlyI 75000 -657700ConTable 6.7.2 shows the valid values for STREET_ADOPTION_CODE:6.7.2 StreetAdoption Status (Road Status Codes)Code STREET_ADOPTION_TEXT (ROAD_STATUS_TEXT)1 Publicly maintainable2 Prospectively maintainable3 Neither 1 or 2Table 6.7.3 shows the valid values for INTEREST TYPE:6.7.3 SWAOrganisation Interest TypeCode INTEREST_TYPE Description1 Street authority The Highway Authority for the street.8 All notices9 Restrictions or licencesUsed when an organisation has aninterest in a Street or part street but is notthe highway authority and wishes toreceive all NRSWA notices.Used when an organisation hasan interest in a street or part street butonly wishes to receive details of restrictionnotices or proposed street works licences.Examples of Type 21 Records are as follows:Example 1:21,12345678,1,1234,1,,1,1234,1,1,1,,,,It states that the street is a public street (for its entire length), and SWA 1234 wish to receivea notice as the relevant Highway Authority.Example 2:Utility and Statutory Undertaker DocumentVersion 1April 2009Page 17

Table 6.8.2 Reinstatement Type Categories shows the valid values forSTREET_REINSTATEMENT_TYPE_CODE:6.8.2 ReinstatementType CategoriesCodeSTREET_REINSTATEMENT_TYPE_TEXT1 Carriageway type 1 (10 to 30 MSA)2 Carriageway type 2 (2.5 to 10 MSA)3 Carriageway type 3 (0.5 to 2.5 MSA)4 Carriageway type 4 (up to 0.5 MSA)5 Carriageway type 0 (30 to 125 MSA)6 High Duty Footway7 High Amenity Footway8 Other Footways9 Private Street – No designation information held by street authority10 Carriageway type 6 (over 125 MSA)An example of a Type 22 Record is as follows:22,12345678,1,1,0,“TEXT HERE”,132456,234567,345678,456789Utility and Statutory Undertaker DocumentVersion 1April 2009Page 19

7 Appendix 2 – Process for new Unitary organisations.Additional information on the process for the 9 new unitary organisations in table 7.1.1 canbe found on the NSG Website (http://www.thensg.org.uk/iansg/link.htm?id=2008) in thefollowing documents:EDG Guidelines for Changes to Unitary CodesLGIH letter indicating DTF 7.1 processesThe following table indicates the new organisation name and street works authority(SWA_ORG_REF) reference for the new unitary organisations:7.1.1 NewUnitary OrganisationsUnitary Code Name0235 Bedford Council0240 Central Bedfordshire Council0660 Cheshire East Council0665 Cheshire West and Chester Council0840 Cornwall Council1355 Durham Council2935 Northumberland Council3245 Shropshire Council3940 Wiltshire CouncilUtility and Statutory Undertaker DocumentVersion 1April 2009Page 23