5.1.1
This section provides background, data entry conventions and guidance as to how each Street Record should be maintained in the LLPG to comply with the implementation of this document. For a diagram showing how LLPGs and LSGs interact, see Appendix G.
5.1.2
The SNN Officer for each SNN Authority administrative area is responsible for the allocation and approval of Street Names as described in Section 4.
5.1.3
The Authority Address Custodian is responsible for ensuring the Street Records are entered accurately into the LLPG and must work closely with the Authority Street Custodian to ensure that the Street Records match and are consistent.
5.1.4
The Authority Street Custodian is responsible for ensuring that all Street Records are entered accurately into the LSG and must work closely with the Authority Address Custodian to ensure that the Street Records match and are consistent. The Authority Street Custodian is responsible for the Street Data attributes as shown in the table at Section 5.3.3.
5.1.5
Sometimes a Street in the LSG is represented as a PAON in the LLPG, for example if a block of flats has an adopted access road of the same name. In the LSG this name is recorded as a Street but in the LLPG the name is recorded as the PAON of the block of flats and addressed to the main road off which the access road leads (This is the Approved Preferred LPI). To ensure the LSG and the LLPG match, add a type 1 or a type 2 Street for the access road and create an Alternative LPI associated with the access road.
5.1.6
For guidance on a legacy case when a terrace is represented as a PAON in the LLPG and as a Street in the LSG, see Section 11.9.2.9.
5.1.7
The SNN Officer, Authority Address Custodian and the Authority Street Custodian must be conversant with the data entry conventions and guidance described in the current version of the DEC-NSG.
5.1.8
For the purposes of LLPG Records, a Street must be either one of the DEC-NSG: type 1, 2, 3 or 4 Street or DEC-Addresses: type 9 Street, entered within the Associated Street Gazetteer (ASG) in the LLPG.
5.1.9
A type 3 (Numbered) Street defines the entirety of a numbered route, for example A24, B3350. It is the responsibility of the Authority Street Custodian to create and maintain type 3 Streets. A separate range of USRNs is allocated to the Authority Street Custodian for this purpose. Any type 3 Street that has been created by the Authority Street Custodian should be included in the ASG and the Authority Address Custodian will need to liaise with the Authority Street Custodian accordingly, especially between District and County contacts.
5.1.10
Within the ASG some or all lengths of the type 3 Street will relate to either a type 1 or type 2 Street (please note for the ASG, DTF7.3.3.1 has no type 12 Street Cross Reference (XRef) Record for type 3 or 4 Streets).
5.1.11
If a linear feature representing a river, canal, waterway or railway is needed in the LLPG, this must be entered into the ASG as a type 9 Street, as described within this DEC-Addresses implementation.
5.1.12
If the feature has a tow path, then the tow path must be entered as a type 1 or type 2 Street, and a type 9 Street must not be used for the feature.