12.07.2015 Views

Local Street Gazetteer - Health Check - Iahub.net

Local Street Gazetteer - Health Check - Iahub.net

Local Street Gazetteer - Health Check - Iahub.net

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Local</strong> <strong>Street</strong> <strong>Gazetteer</strong><strong>Health</strong> <strong>Check</strong> SpecificationVersion 2.2January 2012


Contents1 Introduction ........................................................................................................ 42 Scope ................................................................................................................. 53 <strong>Health</strong> <strong>Check</strong>s .................................................................................................... 63.1 <strong>Street</strong> Record <strong>Check</strong>s ............................................................................... 73.2 <strong>Street</strong> Descriptor Record <strong>Check</strong>s ........................................................... 103.3 Additional <strong>Street</strong> Interest Record checks ................................................ 143.4 Reinstatement Designation Record checks ............................................ 233.5 Special Designation Record checks ....................................................... 283.6 Height, Width and Weight Record checks .............................................. 313.7 Monthly Comparison ............................................................................... 324 NLPG <strong>Street</strong> Comparison ................................................................................ 345 Statistics ........................................................................................................... 39


Document historyVersion Publication Date Author Comments1.0 June 2007 Nick TurnerNSG Custodian1.1 July 2007 Nick TurnerNSG Custodian1.2 December 2007 Nick TurnerNSG Custodian1.3 November 2009 Abbas LokatNSG Coordinator2.0 April 2011 Abbas LokatNSG Coordinator2.1October 2011Abbas LokatNSG CoordinatorFirst issue.Minor corrections.Minor updates.<strong>Check</strong> EA3 removed.<strong>Check</strong> GA2 divided into three checks GA2-GA4 and subsequent GA checksrenumbered.<strong>Check</strong>s HC7-HC9 and HD4 added.Additional NSG/NLPG comparison checksadded.Update to accommodate DTF 7.1 Includesassignment of new codes and StatisticReport.Minor updates<strong>Check</strong> TP7 split into TP7a and TP7b<strong>Check</strong>s AS7- AS10 removed<strong>Check</strong>s AS12 – AS13 removedAS <strong>Check</strong>s renumbered<strong>Check</strong>s RC12 – RC14 added<strong>Check</strong>s H1 –H12 added<strong>Check</strong> NC1 split into NC1a and NC1b<strong>Check</strong> NC13 addedMinor updates<strong>Check</strong>s AS9, AS13, AS27 removed<strong>Check</strong>s H1, H2, H3, H4, H6, H7, H8, H9,H10, H11 removed<strong>Check</strong>s SD6, SD8 removed<strong>Check</strong>s SR9 removed2.2CopyrightFebruary 2012Abbas LokatNSG CoordinatorMinor Edits<strong>Check</strong>s TP7a, AS10, H5, H12 removedAll Intellectual Property Rights in this document are held by the Improvement andDevelopment Agency. It is a public domain document and may be copied, quoted,published and distributed with attribution freely but not re-sold.If you wish to make any comments on this document, please contactGeoPlace LLPIvybridge House1 Adam <strong>Street</strong>LONDONWC2N 6DDTel 020 7747 3500National <strong>Street</strong> <strong>Gazetteer</strong> and ASD – <strong>Health</strong> <strong>Check</strong> SpecificationV2.1 January 2012Page 3 of 40


1 Introduction<strong>Local</strong> <strong>Street</strong> <strong>Gazetteer</strong> (LSG) submissions to the hub are subject to an array ofcompliance checks, as detailed in the ‘Standard Compliance <strong>Check</strong>’ document.These ensure that the format and content of the data is consistent with thatspecified in the Code of Practice associated with the New Roads and <strong>Street</strong> WorksAct (1991). The submission must pass all of these checks in order for it to bepublished as part of the National <strong>Street</strong> <strong>Gazetteer</strong> (NSG).The objective of the health checks is to improve the quality of the data held withinthe NSG to ensure it is of the highest possible standard, and to provide maximumbenefit to its users within the <strong>Street</strong> Works community. By facilitating the use of theElectronic Transfer of Notices (EToN) system, the benefits of the improvedcoordination of <strong>Street</strong> Works will be passed on to the citizens of the HighwayAuthorities involved.Conforming to the standards outlined in this document will help to ensure theconsistency and integrity of the NSG, resulting in a truly national gazetteer.<strong>Health</strong> <strong>Check</strong>s can only be conducted on data that successfully validates against allof the compliance check specification. It is not possible to conduct health checks ondata that is not loaded into the NSG Hub.Submissions do not need to conform to the <strong>Health</strong> <strong>Check</strong> in order to count as a‘passed’ submission to the hub.National <strong>Street</strong> <strong>Gazetteer</strong> and ASD – <strong>Health</strong> <strong>Check</strong> SpecificationV2.1 January 2012Page 4 of 40


2 ScopeThe scope of this document is to outline the range of ‘<strong>Health</strong> <strong>Check</strong>s’ that the NSGhub will carry out on LSG submissions, and the resulting compiled national dataset.This includes checks to be made on street data files (including <strong>Street</strong>, CrossReference, Elementary <strong>Street</strong> Unit (ESU), ESU Coordinate and <strong>Street</strong> DescriptorRecords) as well as Associated <strong>Street</strong> Data (ASD) files (including Additional <strong>Street</strong>,Reinstatement Designation, Special Designation, Height, Width and Weight andOne Way Exemption records).<strong>Check</strong>s that require attention will be highlighted with aThe corrective action will be highlighted with a Advisory checks will be highlighted with a An additional report will contain a comparison between the streets held within theNational <strong>Street</strong> <strong>Gazetteer</strong> (NSG) and the National Land and Property <strong>Gazetteer</strong>(NLPG). This may identify missing data and/or mismatches that may need to bechanged within one of the gazetteers.Further detail on the record types, terminology and validation checks can beobtained from the ‘DTF 7.1 Compliance <strong>Check</strong> Specification’ document located onthe NSG website in the ‘Documents’ section.National <strong>Street</strong> <strong>Gazetteer</strong> and ASD – <strong>Health</strong> <strong>Check</strong> SpecificationV2.1 January 2012Page 5 of 40


3 <strong>Health</strong> <strong>Check</strong>sThis section outlines the checks that are performed on the NSG data. For eachrecord type there is a table showing the identifier for each check and a briefdescription of the check.In addition to the tables there is a set of notes explaining each check andsuggesting possible resolutions where suitable.Further clarification on the checks and their resolutions can be obtained bycontacting the NSG Helpdesk by email at helpdesk@thensg.org.ukThe LSG Custodian should review each of the records reported by the checks anddecide what action needs to be taken using the explanatory notes as guidance.National <strong>Street</strong> <strong>Gazetteer</strong> and ASD – <strong>Health</strong> <strong>Check</strong> SpecificationV2.1 January 2012Page 6 of 40


3.1 <strong>Street</strong> Record <strong>Check</strong>sThe following checks are applied to the Type 11 <strong>Street</strong> records.Table 1: <strong>Street</strong> record checksCodeSR1SR2SR3SR4SR5<strong>Check</strong> Description<strong>Street</strong>s in your authority referencing the same coordinates.<strong>Street</strong>s in your authority referencing the same coordinates as a street in a differentauthority.<strong>Street</strong>s referencing the same coordinates in both the start and end coordinate fields.Open USRNs that have also been submitted by another authority.Closed USRNs from another authority range.SR6 Open streets with no open ESU cross-references (i.e streets that are not Level 3).SR7SR8SR10SR11SR12Closed streets with open ESU cross-references.<strong>Street</strong> listed in exception list not present in ****_LG.csv.*<strong>Street</strong>s in the TfL Exception List.<strong>Street</strong>s in the Welsh Agency Trunk Road Exception List.<strong>Street</strong>s in the Highways Agency Exception List.SR1 This displays streets within your authority which have the same startand end coordinates as another street within your authority. A range of actions may be necessary such as correcting thecoordinates, or closing one street if they are duplicates. The custodian shouldreview the records and decide what action is appropriate.SR2 This displays streets within your authority which share coordinateswith another street in a different authority. It may be that you are holding the same street as a neighbouringauthority and it should be decided who should hold the record.SR3 This displays open streets where the start coordinates are the sameas the end coordinates. The record should be updated to reflect the correct coordinates. Forroundabouts and T- junctions etc. generally, the furthest two points should beNational <strong>Street</strong> <strong>Gazetteer</strong> and ASD – <strong>Health</strong> <strong>Check</strong> SpecificationV2.1 January 2012Page 7 of 40


used for the start and end coordinates. Please review the NSG DEC forfurther guidance;SR4 This displays open streets that have been submitted by you andanother highway authority. It may be that you are holding the same street as a neighbouringauthority and it should be decided who should hold the record.SR5 This displays closed streets that have been submitted by you and arefrom the USRN range of another authority This street may have been subject to a boundary change andsubsequently closed by you. You may wish to review this record.SR6 This displays streets which do not have a cross-reference to an ESU. If the relevant ESU exists, but has not yet been associated to thecorrect street the cross-reference should be created. Alternatively, a newESU may need to be digitised.SR7 This displays closed streets which have a Type 2 cross-reference to alive ESU. (A Type 2 cross-reference links a USRN to an ESU.) The ESU should either be closed or if the ESU is going to be linked toanother street then the existing Type 2 cross reference should be removed.SR8***This check will become a compliance check at a later dateThis displays the streets that exist in the current exception list but areno longer submitted in the street (xxxx_LG.csv) file. The list should be reviewed and a new updated list of exceptionstreets should be sent through to the hub.OR The street that has been removed from the LG file needs to bereentered as it has been removed in error.National <strong>Street</strong> <strong>Gazetteer</strong> and ASD – <strong>Health</strong> <strong>Check</strong> SpecificationV2.1 January 2012Page 8 of 40


SR10 list.This displays the streets that have been submitted in the TfL exception This should be used to review the streets that you believe to belong toTfL and to assist you in adding a Type 8 interest record to this street if youhave not already done so. This check only applies to London authoritieswhere TfL are responsible for maintaining the street.SR11 This displays the streets that have been submitted in the WAGexception list. This should be used to review the streets that you believe to belong toone of the Welsh Trunk Road Agents and to assist you in adding a Type 8interest record to this street if you have not already done so. This check onlyapplies to Welsh authorities where WAG Agents are responsible formaintaining the street.SR12 This displays the streets that have been submitted in the HighwaysAgency exception list. This should be used to review the streets that you believe to belong tothe Highways Agency and to assist you in identifying those Trunk Road andMotorway records that you are not responsible for maintaining. This checkonly applies to English authorities where Highways Agency roads exist.National <strong>Street</strong> <strong>Gazetteer</strong> and ASD – <strong>Health</strong> <strong>Check</strong> SpecificationV2.1 January 2012Page 9 of 40


3.2 <strong>Street</strong> Descriptor Record <strong>Check</strong>sThe following checks are applied to the Type 15 <strong>Street</strong> Descriptor records:Table 2: <strong>Street</strong> Descriptor <strong>Check</strong>sCodeSD1SD2SD3SD4SD5SD7SD9<strong>Check</strong> DescriptionOfficially named streets that resemble Type 2 street descriptions.Officially named streets which start with a Type 3 road classification.Type 3 streets which do not appear to start with a street classification number.Type 1 streets with text abbreviations.<strong>Street</strong>s containing double spaces in any of the following fields: name, locality, town,administrative area.<strong>Street</strong>s with an invalid locality.Records appear to be Motorway records, are they following the motorway data entryconvention?SD10 Type 1 and 2 streets that appear to be ‘Motorways’ and may not have a xref to a Type 3<strong>Street</strong>SD11 Type 1 and 2 streets that appear to be ‘A Roads’ and may not have a xref to a Type 3<strong>Street</strong>SD1 This displays Type 1 (Officially Named) streets whose nameresembles a Type 2 <strong>Street</strong> Description. The street Type may need to be changed to a Type 2 (OfficiallyDescribed) street for these records. You may however, have legitimaterecords which are highlighted by this check. If this is the case then treat thecheck as advisorySD2 This displays Type 1 (Officially Named) streets which appear to beginwith a Type 3 road classification. These may need to be changed to Type 2 (Officially Described) orType 3 (Numbered) streets.SD3 This displays Type 3 (Numbered) streets which do not appear to startwith a street classification number. The street Type may need to be changed or the format of the recordrevised.National <strong>Street</strong> <strong>Gazetteer</strong> and ASD – <strong>Health</strong> <strong>Check</strong> SpecificationV2.1 January 2012Page 10 of 40


SD4 This displays Type 1 streets that appear to contain commonabbreviations. For example: ‘St’ for <strong>Street</strong> or ‘Rd’ for Road etc. The full spelling of the words should be used, unless the abbreviationis part of the official street name.You may however, have legitimate records which are highlighted by thischeck. If this is the case then treat the check as advisory.SD5 This displays streets which contain double spaces (‘ ’) in the name,locality, town or county fields. It also displays streets that begin with a spacecharacter. These are difficult to identify visually and can make it difficult forusers to find a particular street within the gazetteer.. The double spaces or spaces at the start of the name should beremoved.SD7 This displays streets which may have invalid text in the locality field.The locality should contain an entry which is locally known and understood,not arbitrary values designed to create uniqueness. If the locality does not fulfil the locality criteria it should be amendedappropriately.SD9 This displays records within your gazetteer which could be interpretedas motorway records. This is to help you review the data to ensure themotorway <strong>net</strong>work within your area is complete and adheres to the publishedconventions.SD10 This displays Type 1 or 2 streets which appear to relate to motorwayrecords but which are not cross-referenced to a Type 3 street with therelevant motorway number. The Type 3 street and relevant cross-references should be created.SD11 This displays Type 1 or 2 streets which appear to relate to an A roadbut which are not cross-referenced to a Type 3 street with the relevant A roadnumber. The Type 3 street and relevant cross-references should be created.National <strong>Street</strong> <strong>Gazetteer</strong> and ASD – <strong>Health</strong> <strong>Check</strong> SpecificationV2.1 January 2012Page 11 of 40


3.2.1 Elementary <strong>Street</strong> Unit (ESU) and ESU Coordinate RecordchecksThe following checks are applied to Type 13 Elementary <strong>Street</strong> Unit (ESU) recordsand Type 14 ESU Coordinate records.Table 3: Topology <strong>Check</strong>sCodeTP3TP4TP5TP6TP7bTP9<strong>Check</strong> DescriptionOpen ESUIDs which match an open ESUID in a different authority.Open ESUs in the authority referencing the same coordinates as another open ESU in adifferent authority.Open ESUs referencing the same coordinates in both the start and end coordinate fields.Open ESUs whose start and end points are referenced by multiple ESU IDs.Open ESUs with coordinate points digitised at sub metre level (Count)Closed ESUs with ASD Type 65 (One way street exemption record)TP3 This displays ESUs within your gazetteer which have the same ESUID and version number as another ESU in a different authority. If the ESUs refer to different sections of highway then one of the ESUIDs should be changed to ensure uniqueness.OR If the NSG DEC has been followed then no action is required ininstances where the administrative boundary falls on the centreline of anESU.TP4 This displays ESUs with the same coordinates as an ESU withinanother authority. The custodian should identify whether the ESU falls within theirauthority and if not the ESU_End_Date should be added.OR If the administrative boundary falls on a centerline and either ESU IDscan be used then the authorities should work together to determine whichESU ID to use.National <strong>Street</strong> <strong>Gazetteer</strong> and ASD – <strong>Health</strong> <strong>Check</strong> SpecificationV2.1 January 2012Page 12 of 40


TP5 This displays ESUs where the start point and the end point of the ESUare identical The ESU record should be reviewed and the coordinate pointsamended accordingly.TP6 This displays ESUs where both the start point and end points of theESU are duplicated across one or more ESUs. The ESU records should be reviewed and amended. Where you havelegitimate cases of this the check should be treated as advisory.TP7b This displays ESUs in the Type 14 record where coordinate pointshave been digitised at a sub metre tolerance.This check may uncover issues where the data is being held in the system to2d.p. but not being exported to the NSG at 2 d.p. If this is the case thenappropriate guidance must be sought from the software supplier.TP9 This displays closed ESUs that have associated one way streetexemptions (Type 65) data attached.National <strong>Street</strong> <strong>Gazetteer</strong> and ASD – <strong>Health</strong> <strong>Check</strong> SpecificationV2.1 January 2012Page 13 of 40


3.3 Additional <strong>Street</strong> Interest Record checksThe following checks are applied to the Type 61 Additional <strong>Street</strong> Interest records.WAG = Welsh Assembly GovernmentTfL = Transport for LondonTable 4: Additional <strong>Street</strong> Information <strong>Check</strong>sCode<strong>Check</strong> DescriptionAS1 <strong>Street</strong>s in the authority which do not have a Primary Notice Authority (Interest Type 1).AS2AS3AS4AS5AS6AS7AS8Primary Notice Authority Interest record duplicates TfL Primary Notice Authority record.Missing Type 8 interest record on TfL streets submitted in the exception list.Primary Notice Authority Interest record duplicates WAG Primary Notice Authority record.Missing Type 8 interest record on WAG streets submitted in the exception list.Open <strong>Street</strong>s with ASD 61 (Interest Type 1 - Primary Notice Authority) submitted by WAG.Open <strong>Street</strong>s with ASD 61 (Interest Type 1 - Primary Notice Authority) submitted by TfL.Under Construction streets with ASD 61 and Interest Type 1 (Primary Notice Authority).AS11 <strong>Street</strong>s with interest Type 1 (Primary Notice Authority ) and street adoption code set to 3.AS12AS14AS15AS16AS17AS18<strong>Street</strong>s without an ASD 61 <strong>Street</strong>_Adoption_Code.<strong>Street</strong>s without a full set of Primary Notice Authority records.‘Part Road' ASD 61 with coordinates matching the street start and end coordinates.‘Part Road' ASD 61 with 'Whole Road' in Additional_<strong>Street</strong>_Location_Text field.'Dummy' text in Additional_<strong>Street</strong>_Location_Text field.Closed <strong>Street</strong>s with ASD Type 61 Interest record.AS19 Conflicting Authority whole road Type 1 Interest record with TfL/WAG part road Type 1Interest recordAS20 Conflicting authority part road Type 1 Interest record with TfL/WAG whole road Type 1Interest recordAS21AS22AS23AS24AS25AS26No Type 1 Interest record exists on this street – specific to London and Welsh authorities.<strong>Street</strong> exists in the exception list - Authority Type 1 Interest record duplicates TfL/WAGInterest recordAuthority has submitted a part road Type 1 Interest record - TfL/WAG do not have acorresponding Type 1 Interest.TfL/WAG do not appear to have a corresponding part road Type 8 interest recordNo corresponding Type 1 Interest records exists on this street - the authority has provided apart road Type 8 Interest recordA part road Type 1 Interest record has been submitted by TfL/WAG - the highway authoritydo not have a corresponding Type 1 interestNational <strong>Street</strong> <strong>Gazetteer</strong> and ASD – <strong>Health</strong> <strong>Check</strong> SpecificationV2.1 January 2012Page 14 of 40


Table 4: Additional <strong>Street</strong> Information <strong>Check</strong>sCode<strong>Check</strong> DescriptionAS27AS28A part road Type 1 Interest record has been submitted by the highway authority - acorresponding Type 8 interest record has not.<strong>Street</strong> exists in the Exception list - TfL/WAG have not declared a Type 1 InterestAS1 This displays open Type 1 or 2 streets which do not have acorresponding Type 61 ASD record to indicate who the Primary NoticeAuthority is for the road. Where possible the Highway Authority or the Private <strong>Street</strong> Managershould be identified and the relevant Type 61 Primary Notice Authority(Interest Type 1) record(s) created.AS2 This displays open Type 1 or 2 streets where Type 61 data submittedby you duplicates the data submitted by TfL and both authorities aresubmitting a primary notice recipient record (Interest Type 1) The correct Primary Notice recipient should be identified and anexception created where necessary.You must ensure that the SWA_ORG_REF /DISTRICT_REF_MAINTAINING_DATA is reflective of the authority responsible for theauthority maintaining the data in the street fileThis check only applies to London authorities with TfL roads.AS3 This displays open Type 1 or 2 streets where you have an exceptionfor a TfL road and there is no corresponding Type 8 interest record. For successful coordination of street works it is recommended that youhave an interest in all streets in your authority that are not maintained by you.The procedure on how to handle interest records for TfL maintained roads iscurrently being determined and more information will be made available indue course.This check only applies to London authorities with TfL roads.National <strong>Street</strong> <strong>Gazetteer</strong> and ASD – <strong>Health</strong> <strong>Check</strong> SpecificationV2.1 January 2012Page 15 of 40


AS4 This displays open Type 1 or 2 streets where Type 61 data submittedby you duplicates the data submitted by the WAG agents and both authoritiesare submitting a primary notice recipient record (Interest Type 1) The correct Primary Notice recipient should be identified and anexception created where necessaryYou must ensure that the SWA_ORG_REF /DISTRICT_REF_MAINTAINING_DATA is reflective of the authority responsible for theauthority maintaining the data in the street fileThis check only applies to Welsh Authorities with WAG trunk roads.AS5 This displays open Type 1 or 2 streets where you have an exceptionfor a WAG road and there is no corresponding Type 8 interest record. For successful coordination of street works it is recommended that youhave an interest in all streets in your authority that are not maintained by you.The procedure on how to handle interest records for WAG maintained roadsis currently being determined and more information will be made available indue course.This check only applies to Welsh Authorities with WAG trunk roads.AS6 This displays all of the streets within your gazetteer for which ASDType 61 records with an Interest Type 1 have been submitted by the WelshAssembly Government.This indicates that WAG are responsible for maintaining the physicalhighway. The record(s) should be reviewed periodically to ensure that theownership of each street is correct.AS7 This displays all of the streets within your gazetteer for which ASDType 61 records with an Interest Type 1 have been submitted by Transportfor London (TFL) denoting them as the maintainer of the street.These should be reviewed periodically to ensure that the ownership of eachstreet is agreed by all parties.AS8 This displays all of the streets within your gazetteer for which ASDType 61 records with an Interest Type 1 have been submitted for thosestreets where the street that are declared as under construction.National <strong>Street</strong> <strong>Gazetteer</strong> and ASD – <strong>Health</strong> <strong>Check</strong> SpecificationV2.1 January 2012Page 16 of 40


These streets should be reviewed periodically and the status of thestreet should be updated to open. This check may also facilitate thecoordination of <strong>Street</strong> Works for new connections.AS11 This displays all of the streets within your gazetteer for which there isType 1 Interest record on a street that is neither publicly or prospectivelymaintainable. All the private streets within the authority area should be listedwithin this check. This is complimentary to check AS1.AS12 This displays all streets within your gazetteer for which a streetadoption code has not been entered. Although the street adoption code is an optional field, the completionof this field is useful to determine whether a street is owned by an authority orwhether it is a private street.AS14 This displays streets where a single part road Additional <strong>Street</strong> recordhas been submitted by the Highway authority. The information for the remainder of the street should be added. This check requires loading into a GIS as the health check may pickup legitimate complete records and flag them as incomplete.AS15 This displays Additional <strong>Street</strong> records which are flagged as ‘NotWhole Road’ (Whole Road= 0) but whose start and end coordinates are thesame as the street to which they apply. This appears to be a contradiction. If the record applies to the whole road the ‘Whole road’ flag should beset to 1 appropriately and the coordinates removed. Otherwise the correctcoordinates should be inserted. The exception to this check however is if the record applies to thewhole length of the street (meaning the coordinates are valid) but not thewhole width. Records will not be reported in the <strong>Health</strong> <strong>Check</strong> if the Locationtext field contains the following:‘CARRIAGEWAY’, ‘FOOTWAY’, ‘VERGE’, ‘CYCLEWAY’National <strong>Street</strong> <strong>Gazetteer</strong> and ASD – <strong>Health</strong> <strong>Check</strong> SpecificationV2.1 January 2012Page 17 of 40


AS16 This displays Additional <strong>Street</strong> records which are flagged as ‘NotWhole Road’ (Whole road flag = 0) but have location text which says‘WHOLE ROAD’ or similar. This is a misuse of the record. If the record does apply to the whole road then the location text shouldbe removed and the whole road flag set to ‘Whole Road’.AS17 This displays instances where the same location text appears in a highnumber of Additional <strong>Street</strong> records on different USRNs. This indicates that‘dummy’ text has been used rather than a meaningful textual description.The dummy text in question is reported, alongside a count of the number ofdifferent streets that are affected. The dummy text should be replaced with a more accurate and usefuldescription of the location.AS18 This displays all of the streets within your gazetteer for which there isan additional street record attached to a street that is now closed.AS19 This displays instances where the Interest Record submitted by theauthority states that they are responsible for maintaining the whole road but aconflicting Type 1 Interest record has been submitted on a part road byTfL/WAG The ownership of the street should be clarified. A corresponding partroad Type 1 Interest record should be created by the authority. A Type 8Interest record should also be created so that copy notices are received forthe corresponding TfL/WAG part road.OR If it is determined that TfL/WAG are responsible for maintaining thewhole road then the local authority should replace the Type 1 interest recordwith a Type 8 record and, remove the associated reinstatement/specialdesignation/height, width and weight records. This USRN must be included inthe exception list.National <strong>Street</strong> <strong>Gazetteer</strong> and ASD – <strong>Health</strong> <strong>Check</strong> SpecificationV2.1 January 2012Page 18 of 40


AS20 This displays instances where the Interest Record submitted by theauthority states that they are responsible for maintaining the whole road but aconflicting Type 1 Interest record has been submitted on a whole road byTfL/WAG The ownership of the street should be clarified. If TfL/WAG areresponsible for maintaining the whole road then the existing Type 1 Interestrecord should be removed by the authority and a Type 8 Interest recordshould be created for the whole road to ensure that copy notices arereceived. Reinstatement/Special Designation and Height Width, and Weightrecords should also be removed by the authority and the USRN must beincluded in the exception list.OR If it is determined that street is subject to shared ownership then theauthority must liaise with TfL/WAG and determine the extent of theownership. Type 1 and Type 8 Interest records must be created accordinglyas should Reinstatement/Special Designation and Height Width, and Weightrecords. The USRN must not be included in the exception listAS21 This displays instances where no Type 1Interest Record has beensubmitted by the Authority or TfL/WAG. Neither organisation think they areresponsible for maintaining the street. The ownership of the street should be clarified. Where the authorityowns the street, a Type 1 Interest record should be created by the authorityor by TfL/WAG. Reinstatement/Special Designation and Height Width, andWeight records should be reviewed and created/amended where necessary.OR Where TfL/WAG owns the street, Type 8 Interest records should also becreated by the authority so that copy notices are received on the road and theUSRN must be included in the exception list. Reinstatement/SpecialDesignation and Height Width, and Weight records should be reviewed andremoved where necessary.National <strong>Street</strong> <strong>Gazetteer</strong> and ASD – <strong>Health</strong> <strong>Check</strong> SpecificationV2.1 January 2012Page 19 of 40


AS22 This displays instances where a USRN has been included in theexception list and the authority has submitted an Interest Record that statesthat they are responsible for maintaining the whole road, and a Type 1Interest record has also been submitted on the whole road by TfL/WAG. The ownership of the street should be clarified. If TfL/WAG areresponsible for maintaining the whole road then the existing Type 1 Interestrecord should be removed by the authority and a Type 8 Interest recordshould be created for the whole road to ensure that copy notices arereceived. Reinstatement/Special Designation and Height Width, and Weightrecords should also be removed by the authority. The USRN must beincluded in the exception listOR If it is determined that street is subject to shared ownership then theauthority must liaise with TfL/WAG and determine the extent of theownership. Type 1 and Type 8 Interest records must be created accordinglyas should Reinstatement/Special Designation and Height Width, and Weightrecords. The USRN must be removed from the exception listAS23 This displays instances where the Authority has submitted a part roadType 1 Interest Record but a corresponding part road Interest Type 1 recordmay not have been submitted by TfL/WAG. The ownership of the street should be clarified. If TfL/WAG areresponsible for maintaining part of the road then the authority should liaisewith TFL/WAG to ensure a part road Interest Type 1 record is submitted. Acorresponding Type 8 Interest record should be created for the part road toensure that copy notices are received.OR If the authority is in fact responsible for maintaining the whole road inwhich case the records need to be amended so that a whole road Type 1interest record is submitted. A review of Reinstatement/Special Designationand Height Width, and Weight records should also be undertaken,National <strong>Street</strong> <strong>Gazetteer</strong> and ASD – <strong>Health</strong> <strong>Check</strong> SpecificationV2.1 January 2012Page 20 of 40


AS24 This displays instances where the Authority has submitted a part roadType 1 Interest Record but no corresponding part road Interest Type 8 recordhas been submitted by TfL/WAG for that section. The ownership of the street should be clarified. If TfL/WAG areresponsible for maintaining part of the road then corresponding part roadInterest Type 8 records should also be submitted by TfL/WAG for theHighway Authority section.AS25 This displays instances where a Type 8 Interest Record has beensubmitted by the Authority and a corresponding part road Interest Type 1record has not. The ownership of the street should be clarified and where the authorityowns the street (part or whole), a corresponding Type 1 Interest recordshould be created and submitted by the authority. Reinstatement/SpecialDesignation and Height Width, and Weight records should be reviewed.AS26 This displays instances where a part road Type 1 Interest Record hasbeen submitted by TfL/WAG but a corresponding part road Type 1 InterestRecord has not been submitted by the authority. The ownership of the street should be clarified. Where the authorityowns part of the street a part road Type 1 Interest record should be createdby the authority. A Type 8 Interest record should also be created for thecorresponding part road to ensure that copy notices are received.Reinstatement/Special Designation and Height Width, and Weight recordsshould be reviewedAS28 This displays instances where a USRN has been included in theexception list but TfL/WAG may not have declared a Type 1 interest. The ownership of the street should be clarified. If TfL/WAG areresponsible for maintaining the whole road then a Type 1 Interest recordshould be submitted by TfL/WAGOR If the road is maintained by the authority, in whole or partNational <strong>Street</strong> <strong>Gazetteer</strong> and ASD – <strong>Health</strong> <strong>Check</strong> SpecificationV2.1 January 2012Page 21 of 40


, then the USRN should be removed from the exception list. TheReinstatement/Special Designation and Height Width, and Weight recordsshould also be reviewed.OR If it is determined that street is subject to shared ownership then theauthority must liaise with TfL/WAG and determine the extent of theownership. Type 1 and Type 8 Interest records must be created accordinglyalong with Reinstatement/Special Designation and Height Width, and Weightrecords. The USRN must be removed from the exception listNational <strong>Street</strong> <strong>Gazetteer</strong> and ASD – <strong>Health</strong> <strong>Check</strong> SpecificationV2.1 January 2012Page 22 of 40


3.4 Reinstatement Designation Record checksThe following checks are applied to the Type 62 Reinstatement Designationrecords.Table 5: Reinstatement Designation checksCodeRC1RC2RC3<strong>Check</strong> DescriptionConflicting Reinstatement Designation records. – CarriagewaysConflicting Reinstatement Designation records. – FootwaysConflicting Reinstatement Designation records. – Private <strong>Street</strong>RC4 <strong>Street</strong> Classification Code of 4,6,9 or 10 with Carriageway Reinstatement Types 1,2,3,4,5or 10RC5RC6RC7RC8RC9Part Road Type 62 data with street start and end coordinates.<strong>Street</strong>s without full set of Reinstatement Designation records.Part road Type 62 data with 'Whole Road' textual description in location text field.'Dummy' text in location text field.Reinstatement Designation record duplicates TfL DataRC10 <strong>Street</strong>s in Exception List with ASD 62RC11 Closed <strong>Street</strong>s with ASD Type 62RC12RC13RC14<strong>Street</strong> exists in the Exception list - a Reinstatement record has not been supplied by TfLReinstatement category has been supplied on a whole road that the authority may not beresponsible for maintainingReinstatement category has been supplied on a part road that the authority may not beresponsible for maintainingRC1 This displays instances where there is a Reinstatement Designationrecord defining the ‘Carriageway’ Reinstatement Category for the whole ofthe street, and another record on the same street also defining the‘Carriageway’ Reinstatement Category for that street (part or whole).The two records either agree in which case duplication has occurred or theyconflict in which case the data is not accurate.The Reinstatement Category should be confirmed and the recordschanged to reflect the true situation.National <strong>Street</strong> <strong>Gazetteer</strong> and ASD – <strong>Health</strong> <strong>Check</strong> SpecificationV2.1 January 2012Page 23 of 40


RC2 This displays instances where there is a Reinstatement Designationrecord defining the ‘Footway’ Reinstatement Category for the whole of thestreet and another record on the same street also defining the ‘Footway’Reinstatement Category for that street (part or whole).The two records either agree in which case duplication has occurred or theyconflict in which case the data is not accurate.The Reinstatement Category should be confirmed and the recordschanged to reflect the true situation.RC3 This displays instances where there is a Reinstatement Designationrecord denoting ‘Private <strong>Street</strong> – no designation information held by streetauthority’ for the whole of the street and another record stating aReinstatement Category on the same street (part or whole).This is a duplication and/or contradiction. and the records should bechanged to reflect the true situation.RC4 This displays records where there is a ‘Carriageway’ ReinstatementDesignation and the ‘STREET_CLASSIFICATION_CODE’ is one of thefollowing:4 ‘PEDESTRIAN WAY OR FOOTPATH’6 ‘CYCLE TRACK OR CYCLEWAY’9 ‘RESTRICTED BYWAY’10 ‘BRIDLEWAY’Either the <strong>Street</strong> Classification in the street record should be amendedto reflect the true situationORThe Reinstatement Category in the reinstatement designation recordshould be amended to reflect the true situation.RC5 This displays Reinstatement Designation records which are flagged as‘Not Whole Road’ but whose start and end coordinates are the same as thestreet to which they apply. This appears to be a contradiction.National <strong>Street</strong> <strong>Gazetteer</strong> and ASD – <strong>Health</strong> <strong>Check</strong> SpecificationV2.1 January 2012Page 24 of 40


If the record applies to the whole road the ‘Whole road’ flag should beset appropriately and the coordinates removed. Otherwise the correctcoordinates should be inserted.The exception to this <strong>Health</strong> check is if the record applies to the wholelength of the street (meaning the coordinates are valid) but not the wholewidth. If this is the case the records will not be reported in the <strong>Health</strong> <strong>Check</strong> ifthe location text field contains one of the following values:‘CARRIAGEWAY’, ‘FOOTWAY’, ‘VERGE’, ‘CYCLEWAY’RC6 This displays streets which have a Reinstatement Designation recordrecording the Reinstatement Category of ‘part’ of the road but no informationfor the rest of the road.The information for the remainder of the street should be added.This check requires loading into a GIS as the health check may pick uplegitimate complete records and flag them as incomplete.RC7 This displays Reinstatement Designation records which are flagged asPart Road records but have location text which says ‘WHOLE ROAD’ orsimilar. This is a misuse of the record. If the record does apply to the whole road then the location text shouldbe removed and the whole road flag set to ‘Whole Road’.RC8 This displays instances where the same location text appears in a highnumber of Reinstatement Designation records on different USRNs. Thisindicates that ‘dummy’ text has been used rather than a meaningful textualdescription.In the interest of presenting the information as concisely as possible, thedummy text in question is reported, alongside a count of the number ofdifferent streets that are affected. The dummy text should be replaced with a more accurate and usefuldescription of the location.National <strong>Street</strong> <strong>Gazetteer</strong> and ASD – <strong>Health</strong> <strong>Check</strong> SpecificationV2.1 January 2012Page 25 of 40


RC9 There can only be one Reinstatement Designation on each section ofroad (excluding Footways). Where TfL/WAG is responsible for the whole/partroad then the Authority should not submit Reinstatement Designations onthat section of road. The Highways Authority should confirm if the street is maintained byTfL/WAG.In the instance that the Highway Authority is not maintained by TfL/WAGthen a Reinstatement Designation record should not be submitted by theauthority.Where the Highway Authority is responsible for maintaining the road thenTfL/WAG must be contacted and a solution agreed. This check is only applicable to London and Welsh authoritiesrespectivelyRC10 This displays instances where an Authority has submitted anexception in the Exceptions List for Highways Agency, TfL or WAG Roads,yet is still submitting a Reinstatement record on part of the road/whole road. Ownership of the road must be clarified. Only the responsible Authorityfor physically maintaining the street can submit Reinstatement Categories ona road. Reinstatement records should be split at the relevant points wheretwo authorities are responsible for reinstatements.RC11 This displays all of the streets within your gazetteer for which there is aReinstatement Designation record attached to a street that is now closed.RC12 This displays instances where an Authority has submitted anexception in the Exceptions List for TfL or WAG Roads, but TfL or WAG havenot submitted a Reinstatement record. Ownership of the road must be clarified. If the road is owned by theAuthority then the USRN must be removed from the exception list.OR The authority should liaise with TfL/WAG who must provide areinstatement record. Reinstatement records should be split at the relevantpoints where two authorities are responsible for reinstatements.National <strong>Street</strong> <strong>Gazetteer</strong> and ASD – <strong>Health</strong> <strong>Check</strong> SpecificationV2.1 January 2012Page 26 of 40


RC13 This displays instances where an Authority has submitted a wholeroad reinstatement record on a road but where an Interest Record with a Type 1Interest (Primary Notice Recipient) has not been submitted by the Authority for thisstreet. Ownership of the road must be clarified. If the Authority is the primarynotice recipient for the whole street then a Type 1 Interest record must becreated.OR If the Authority is not the primary noticing authority for the street, theReinstatement record should be removed and an exception submitted.Reinstatement records should be split at the relevant points where twoauthorities are responsible for reinstatements.RC14 This displays instances where an Authority has submitted a part roadreinstatement record on a road but where an Interest Record with a Type 1Interest (Primary Notice Recipient) has not been submitted by the Authorityfor this street. Ownership of the road must be clarified. If the Authority is the primarynotice recipient for part of the street then a part road Type 1 Interest recordmust be createdOR If the Authority is not the primary noticing authority for the street, theReinstatement record should be removed and an exception submitted.Reinstatement records should be split at the relevant points where twoauthorities are responsible for reinstatements.National <strong>Street</strong> <strong>Gazetteer</strong> and ASD – <strong>Health</strong> <strong>Check</strong> SpecificationV2.1 January 2012Page 27 of 40


3.5 Special Designation Record checksThe following checks are applied to the Type 63 Special Designation records.Table 6: Special Designation checksCode <strong>Check</strong> DescriptionSPD1 Special Designations that have endedSPD2 Special Designations that have not yet startedSPD3 'Not Whole Road' ASD 63 with street start and end coordinates.SPD4 'Not Whole Road' ASD 63 with ‘Whole Road’ in location.SPD5 ‘Dummy’ text in location text field.SPD6 Special Designations that should apply ‘Everyday’.SPD7 <strong>Street</strong>s with Code 5 (Section 58 no longer used) special designationsSPD8 Closed <strong>Street</strong>s with ASD Type 63SPD1 This displays special designations records in your gazetteer datawhere the special designation is no longer applicable. You may wish toreview these records and determine whether the designation requiresremoving or amending.SPD2 This displays special designations records in your gazetteer datawhere the special designation relates to a future activity. These records mayrequire a review to ensure that the data is correct and accurately reflects thedates shown.SPD3 This displays Special Designation records which are flagged as ‘NotWhole Road’ but whose start and end coordinates are the same as the streetto which they apply. This appears to be a contradiction. If the record applies to the whole road the ‘Whole road’ flag should beset appropriately and the coordinates removed. Otherwise the correctcoordinates should be inserted. However, it is possible that the record applies to the whole length ofthe street (meaning the coordinates are valid) but not the whole width. If thisis the case the records will not be reported in the <strong>Health</strong> <strong>Check</strong> if the locationtext field contains one of the following values:‘CARRIAGEWAY’, ‘FOOTWAY’, ‘VERGE’, ‘CYCLEWAY’National <strong>Street</strong> <strong>Gazetteer</strong> and ASD – <strong>Health</strong> <strong>Check</strong> SpecificationV2.1 January 2012Page 28 of 40


SPD4 This displays Special Designation records which are flagged as ‘NotWhole Road’ but have location text which says ‘WHOLE ROAD’ or similar.This is a misuse of the record. If the record does apply to the whole road then the location text shouldbe removed and the whole road flag set to ‘Whole Road’.SPD5 This displays instances where the same location text appears in a highnumber of Special Designation records on different USRNs. This indicatesthat ‘dummy’ text has been used rather than a meaningful textual description.In the interest of presenting the information as concisely as possible, thedummy text in question is reported, alongside a count of the number ofdifferent streets that are affected. The dummy text should be replaced with a more accurate and usefuldescription of the location.SPD6 This displays Special Designation records which should have aPeriodicity of ‘Everyday’ but do not in this case. For example you wouldexpect a designation of ‘Special Surfaces’ to apply all the time, notperiodically. The designations in question are:Table 7: ‘Everyday’ Special Designation TypesCode STREET_SPECIAL_DESIG_TEXT3 Special Engineering Difficulty6 Proposed special engineering difficulty8 Level crossing safety zone9 Environmentally sensitive areas10 Structures (not Special Engineering Difficulty)11 Special surfaces12 Pipelines13 Priority lanes14 Special Construction needs If appropriate, the Periodicity should be changed to ‘Everyday’.National <strong>Street</strong> <strong>Gazetteer</strong> and ASD – <strong>Health</strong> <strong>Check</strong> SpecificationV2.1 January 2012Page 29 of 40


SPD7 This displays those special designations with a Special DesignationCode 5. Code 5 is no longer used, it was previously used to transfer section58 information.At this time, this is provided for information only. This may change as a resultof the ongoing review of the NSG DEC and current EToN mechanism oftransferring Section 58 informationSPD8 This displays all of the streets within your gazetteer for which there is aSpecial Designation record attached to a street that is now closed.National <strong>Street</strong> <strong>Gazetteer</strong> and ASD – <strong>Health</strong> <strong>Check</strong> SpecificationV2.1 January 2012Page 30 of 40


3.6 Height, Width and Weight Record checksThese checks are applied to the Type 64 Height, Width and Weight recordsTable 8: Height Width and Weight record checksCode <strong>Check</strong> DescriptionHW1 'Not Whole Road' ASD 64 with street start and end coordinates.HW2 'Not Whole Road' ASD 64 with ‘Whole Road’ in location.HW3 ‘Dummy’ text in location text field.HW4 Closed <strong>Street</strong>s with ASD Type 64HW1 This displays Height, Width and Weight records which are flagged as‘Not Whole Road’ but whose start and end coordinates are the same as thestreet to which they apply. This appears to be a contradiction. If the record applies to the whole road the ‘Whole road’ flag should beset appropriately and the coordinates removed. Otherwise the correctcoordinates should be inserted.HW2 This displays Height, Width and Weight records which are flagged as‘Not Whole Road’ but have location text which says ‘WHOLE ROAD’ orsimilar. This is a misuse of the record. If the record does apply to the whole road then the location text shouldbe removed and the whole road flag set to ‘Whole Road’.HW3 This displays instances where the same location text appears in a highnumber of Height, Width and Weight records on different USRNs. Thisindicates that ‘dummy’ text has been used rather than a meaningful textualdescription.In the interest of presenting the information as concisely as possible, thedummy text in question is reported, alongside a count of the number ofdifferent streets that are affected. The dummy text should be replaced with a more accurate and usefuldescription of the location.HW4 This displays all of the streets within your gazetteer for which there is aHeight, Width and Weight record attached to a street that is now closedNational <strong>Street</strong> <strong>Gazetteer</strong> and ASD – <strong>Health</strong> <strong>Check</strong> SpecificationV2.1 January 2012Page 31 of 40


3.7 Monthly ComparisonThis report will compare certain elements of the submission that has just been madeand the data that is currently contained in the NSG Hub – i.e. the previoussuccessful submissionTable 10: Monthly Comparison reportCodeMC1MC2MC3MC4MC5MC6<strong>Check</strong> DescriptionNew <strong>Street</strong>s added since the last successful submission.Records changed to Closed <strong>Street</strong> since the last successful submission.<strong>Street</strong>s that have not been included since the last successful submission.Open <strong>Street</strong>s that have been submitted with a different street descriptor since the lastsuccessful submission.Closed <strong>Street</strong>s that have been submitted with a different street descriptor since the lastsuccessful submission.Open <strong>Street</strong>s with different co-ordinate information since last successful submission,MC1 This displays streets that have been newly added to the LSG data andsubmitted to the NSG Hub. These may be newly created streets or streetsthat have not yet required submission to the hub due to internal organisationdecisions.MC2 This displays streets that have been closed and submitted to the NSGHub since the last successful submission. These records may require a review.MC3 This displays streets that have not been submitted to the NSG Hubsince the last successful submission. It may be that the street has beenremoved as it is erroneous These records may require a review.National <strong>Street</strong> <strong>Gazetteer</strong> and ASD – <strong>Health</strong> <strong>Check</strong> SpecificationV2.1 January 2012Page 32 of 40


MC4 This displays open streets that have had some part of the streetdescriptor information, i.e. street description, locality or town information,changed since the last submission. These records may require a reviewMC5 This displays closed streets that have had some part of the streetdescriptor information, i.e. street description, locality or town information,changed since the last submission. These records may require a reviewMC6 This displays open streets that have had some part of the streetcoordinate information (i.e. start_x, start_y, end_x, end_y) changed since thelast submission. These records may require a reviewNational <strong>Street</strong> <strong>Gazetteer</strong> and ASD – <strong>Health</strong> <strong>Check</strong> SpecificationV2.1 January 2012Page 33 of 40


4 NLPG <strong>Street</strong> ComparisonThis report contains a comparison of the street records held within the National<strong>Street</strong> <strong>Gazetteer</strong> (NSG) and the National Land and Property <strong>Gazetteer</strong> (NLPG).BS7666:2006, the addressing standard for both the NSG and NLPG, states that allstreets including motorways, trunk roads, classified roads, named/unnamed roadsshould be included within the gazetteers. In order to achieve the aim of 100%completeness in both gazetteers any street that exists in one dataset should be inboth.Not only should a given street be included in both gazetteers, it should be recordedwith the same Unique <strong>Street</strong> Reference Number (USRN). This will provide adefinitive register of streets within an area and facilitate interoperability betweenorganisations and departments.The street name recorded for Type 1 (Officially Named) streets should be theOfficial <strong>Street</strong> Name, as designated by the relevant <strong>Street</strong> naming and NumberingAuthority. Hence this should be the same in both gazetteers. Where this is not thecase the correct name should be identified and the gazetteers amended asrequired.Whilst no individual body has the authority to create Type 2 ‘Official <strong>Street</strong>Descriptions’, every attempt should be made to ensure that they are consistentbetween the two gazetteers.In the interest of positional accuracy, if the coordinates of a given street do notmatch within the NSG and NLPG they should be reviewed and if the difference isnot within a reasonable tolerance then more accurate coordinates should beinserted.Where the record is present in both the NSG and the NLPG but with differences,both the NSG and NLPG records will be displayed. Each will be on a separate lineand will begin with either ‘NSG’ or ‘NLPG’ to indicate the source of the record. Thiswill allow the two records to be compared easily.For the checks which report records that are missing from one of the gazetteers, therecords are displayed in the corresponding DTF 7.1 format.National <strong>Street</strong> <strong>Gazetteer</strong> and ASD – <strong>Health</strong> <strong>Check</strong> SpecificationV2.1 January 2012Page 34 of 40


These comparisons are applied to the latest data within the NSG and NLPG Hubs:Table 11: NLPG Comparison <strong>Check</strong>sCodeNC1aNC1bNC2NC3NC4NC5NC6aNC6bNC7aNC7bNC7cNC8NC9NC10NC11NC12NC13<strong>Check</strong> DescriptionNSG street record does not match NLPG hub record on coordinates where the X and Ycoordinates for the start and end points have been reversed/swappedNSG street record does not match NLPG hub record on coordinates where the X and Ycoordinates for the start and end points have not been reversed/swappedNSG street record does not match NLPG record on street name.NSG street record does not match NLPG record on street state where enteredNSG street record does not match NLPG record on street classification where enteredNSG street record does not match NLPG record on street surface where enteredOpen Type 1 and 2 NLPG street records that do not exist in the NSGOpen Type 3 and 4 NLPG street records that do not exist in the NSGOpen Type 1 NSG street records that do not exist in the NLPG.Open Type 2 NSG street records that do not exist in the NLPG.Open Type 3 and 4 NSG street records that do not exist in the NLPG.Different USRN with same street, locality, town, and authority code.Open Type 9 NLPG streetsClosed Type 9 NLPG streetsUSRNs which are closed in the NLPG and open in the NSGUSRNs which are closed in the NSG and open in the NLPGUSRNs held in the NSG with a different street type to USRNs in the NLPGNC1 This displays records where the same USRN exists in both the NSGand the NLPG but the associated records have different coordinates.NC1a relates to start and end points that have been swapped in the NLPGand NSGNC1b relates to start and end points that do not match These should be reviewed and if the custodian finds that the USRNsrelate to different streets, or they relate to the same street but the coordinatesdiffer by more than a reasonable margin then one of the records should bechanged.NC2 This displays records where the USRN exists in both datasets but thestreet name of the records is different.National <strong>Street</strong> <strong>Gazetteer</strong> and ASD – <strong>Health</strong> <strong>Check</strong> SpecificationV2.1 January 2012Page 35 of 40


If this is due to minor spelling differences then the definitive streetname should be verified from the <strong>Street</strong> naming and Numbering record andthe relevant record(s) amended accordingly.OR If the USRNs are referring to different streets then the HighwayAuthority and <strong>Street</strong> Naming and Numbering authority should discuss how toresynchronise the two datasets.GeoPlace is available to advise on this process if required.NC3 This displays records where the USRN exists in both datasets but thestreet state in both the NLPG and the NSG street record is different where ithas been entered The state of the street should be amended to reflect the correct state.It is generally accepted that the Highway Authority is the definitive source ofthis information.NC4 This displays records where the USRN exists in both datasets but thestreet classification where it has been entered in both the NLPG and the NSGstreet record is different. The street classification of the street should be amended to reflect thecorrect classification. It is generally accepted that the Highway Authority isthe definitive source of this information.NC5 This displays records where the USRN exists in both datasets but thestreet surface in both the NLPG and the NSG street record is different whereit has been entered The street surface of the street should be amended to reflect thecorrect street surface. It is generally accepted that the Highway Authority isthe definitive source of this information.NC6 This displays streets where the USRN exists in the NLPG but not inthe NSG.NC6a displays Open Type 1 and 2 streets that are not in the NSGNC6b displays Open Type 3 and 4 streets that are not in the NSGNational <strong>Street</strong> <strong>Gazetteer</strong> and ASD – <strong>Health</strong> <strong>Check</strong> SpecificationV2.1 January 2012Page 36 of 40


To ensure complete coverage and synchronicity in both datasets therelevant records should be added to the LSG taking care to ensure that thesame USRN is used and street names (and other details where possible) areidentical in bothNC7 This displays streets where the USRN exists in the NSG but not in theNLPG.NC7a displays Open Type 1 streets that are not in the NLPGNC7b displays Open Type 2 streets that are not in the NLPGNC7c displays Open Type 3 and 4 streets that are not in the NLPG To ensure complete coverage and synchronicity in both datasets therelevant records should be added to the LLPG taking care to ensure that thesame USRN is used and street names (and other details where possible) areidentical in both.NC8 This displays instances where the same unique street descriptor(street name, locality, town and authority code) appear in both datasets buton different USRNs. This is a sign that the gazetteers have diverged. This should be resolved by discussion between the LSG and LLPGcustodians and GeoPlace if desired.NC9 This displays instances where the NLPG contains an open Type 9street. Type 9 streets are not used in the NSG. They are only used in theNLPG to accommodate unusual addressing situations. They typicallyencompass examples such as rivers, waterways and railways.You may wish to review these records and provide guidance to the LLPGCustodian where the Type 9 street is a potential duplicate of an existing Type1, 2, or 4 street record.NC10 This displays instances where the NLPG contains a closed Type 9street. Type 9 streets are not used in the NSG. They are only used in theNLPG to accommodate unusual addressing situations. They typicallyencompass examples such as rivers, waterways and railways.You may wish to review these records and provide guidance to the LLPGCustodian where the Type 9 street is a potential duplicate of an existing Type1, 2, or 4 street record.National <strong>Street</strong> <strong>Gazetteer</strong> and ASD – <strong>Health</strong> <strong>Check</strong> SpecificationV2.1 January 2012Page 37 of 40


NC11 This displays USRNs which are closed in the NLPG and live in theNSG. The correct status of the street should be identified and the record(s)amended accordingly.NC12 This displays USRNs which are closed in the NSG and live in theNLPG. The correct status of the street should be identified and the record(s)amended accordingly.NC13 This displays USRNs in the NSG which are of a different street type(Designated <strong>Street</strong> Name (1), <strong>Street</strong> Description (2), <strong>Street</strong> Number (3),Unofficial <strong>Street</strong> Name(4)) to those held in the NLPG. The street type should be identified and the appropriate NLPG or NSGrecord(s) amended accordingly.National <strong>Street</strong> <strong>Gazetteer</strong> and ASD – <strong>Health</strong> <strong>Check</strong> SpecificationV2.1 January 2012Page 38 of 40


5 StatisticsIn order to demonstrate the size and scope of the gazetteer a number of statisticshave been provided. These are provide for information but may promptconsideration of how the extent of the gazetteer can be increased. For example, alow number of Type 2 streets may indicate that streets which do not have officialnames, or footpaths and Public rights of Way are not recorded in the gazetteer.Highlighting this may prompt an exercise to capture them. The custodian shouldreview the scope of the gazetteer and decide if this can be extended.The statistics that will be displayed are shown below.Table 12: LSG Submission statisticsCodeTN1TN2TN3TN4TN5TN6TN7TN8TN9TN10TN11TN12TN13TN14TN15<strong>Check</strong> DescriptionTotal number of <strong>Street</strong> RecordsTotal number of open <strong>Street</strong> RecordsTotal number of closed <strong>Street</strong> RecordsTotal number of TYPE 1 <strong>Street</strong> RecordsTotal number of TYPE 2 <strong>Street</strong> RecordsTotal number of TYPE 3 <strong>Street</strong> RecordsTotal number of TYPE 4 <strong>Street</strong> RecordsTotal number of Open <strong>Street</strong> Records with <strong>Street</strong> Classification TypeTotal number of Open <strong>Street</strong> Records with <strong>Street</strong> Surface TypeTotal number of Open <strong>Street</strong> Records with <strong>Street</strong> StateTotal number of Cross Reference recordsTotal number of ’<strong>Street</strong>’ (Type 1) Cross Reference recordsTotal number of ‘ESU’ (Type 2) Cross Reference RecordsTotal number of ESU recordsTotal number of open ESU recordsTN16 Total number of ESU records with Direction of travel information (Codes 1,2 & 3)TN17TN18TN19Total number of ESU Coordinate recordsTotal number of ESU Coordinate records on open ESUsTotal number of Additional <strong>Street</strong> (ASD 61) recordsTN20 Number of ASD 61 records for each <strong>Street</strong> Adoption ( 1,2 or 3)TN21TN22TN23Number of ASD 61 records for each SWA Organisation Interest TypeTotal number of Reinstatement Designation (ASD 62) recordsNumber of ASD 62 records for each Reinstatement Category CodeNational <strong>Street</strong> <strong>Gazetteer</strong> and ASD – <strong>Health</strong> <strong>Check</strong> SpecificationV2.1 January 2012Page 39 of 40


Table 12: LSG Submission statisticsCode <strong>Check</strong> DescriptionTN24 Total number of Special Designation (ASD 63) recordsTN25 Number of ASD 63 records for each Special DesignationTN26 Number of ASD 63 records for each Special Designation PeriodicallyTN27 Total number of ASD 64 records (Height, Weight, Width)TN28 Total number of ASD 65 records (One Way exemptions)It is important that all streets within your gazetteer are recorded. Particular careshould be taken to ensure that all Type 3 (numbered) streets are present (along withthe cross-references to the relevant Type 1 or 2 street). Whilst ASD records andETON notices are not held against Type 3 streets they are vital in helping users ofthe data to easily identify the correct street.Special Designation Records are extremely valuable and must be submitted with allgazetteers. If the record counts indicate that they are not then every effort should bemade to create and submit these records.Particular attention should also be paid to statistic that shows how many SpecialDesignation records of each Type there are. By considering which Specialdesignations are not currently held within your ASD you may identify designationsthat would be of value to your organisation to hold. This is a good starting point ifyou are in the process of evaluating a program of works to deliver a complete set ofdesignation recordsNational <strong>Street</strong> <strong>Gazetteer</strong> and ASD – <strong>Health</strong> <strong>Check</strong> SpecificationV2.1 January 2012Page 40 of 40

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!