Menu

GeoGateway Address

GeoPlace Services Site

GeoGateway Streets

LA Data Linking Dashboard

GeoPlace

Knowledge Hub

Status updates

Street Naming and Numbering

Integration knowledge base
Close Search

Today

Yesterday

Older

Live
Introduction

5.3.1.1

Apply the following rules to the date Fields in the type 11 Street and type 13 ESU Records:

  • RECORD_ENTRY_DATE
    • The date that the Record is recorded into the LSG. This is not always the same as the STREET_START_DATE because of latency in Record entry, for example, the Street exists in the real world, or the Street does not exist in the real world.

 

  • LAST_UPDATE_DATE
    • The date on which any attribute of the Record was changed. This is the date that any alteration is made to the type 11 Record or the type 15 Record. It is possible that more than one alteration is made between submission periods. A date prior to the date the DCA Street Update transfer file is present at GeoPlace must be the date of the last change.

 

  • STREET_START_DATE
    • The date on which the Street starts to exist in the real world. This can be a date before the RECORD_ENTRY_DATE, because of latency in data entry. This can also be after the RECORD_ENTRY_DATE because sometimes Street Data is required for operational use before they exist on the ground. This date is the first date that the Street was known to be in use. If a date is required for a highway which existed before the Highway Act 1835, a start date of 1835-08-01 must be used. This date corresponds to the date in Section 36(a) of the Highways Act 1980 which is carried forward from the Highway Act 1835.

 

  • STREET_END_DATE
    • The date on which the Street ceased to exist in the real world or is replaced by one or more new USRNs. This is also the Record’s end date.

5.3.1.2

To establish an agreed closure date, the Authority Address Custodian and the Authority Street Custodian must liaise with each other. The information supplied by the Authority Street Custodian should be given priority.

5.3.1.3

Each Street must be allocated a USRN and be maintained in accordance with the principles set out in Appendix F.

5.3.1.4

Appendix B contains a list of:

  • Each LHA in England and Wales.
  • Each DCA Participating Authority.
  • The USRN range prefixes.

5.3.1.5

Each Street recorded in an LSG must have a USRN within the range allocated to the SNN Authority for that administrative area. The three exceptions to this rule are:

  • If the LHA is different from the SNN Authority, then a separate USRN range is allocated for type 3 Street Data.
  • If Streets are exchanged between authorities due to administrative boundary changes, the Streets must be removed from the previous DCA Participating Authority LSG and transferred to the new DCA Participating Authority LSG. The original USRN must be kept. This process must be done in consultation with GeoPlace.
  • If a Motorway is added to the LSG, the USRN must be allocated by the Authority Street Custodian.

5.3.1.6

If a Street which is designated a PRoW is added to the LSG as a type 1 or type 2 Street, then the USRN is allocated by the Authority Street Custodian using the range allocated to the SNN Authority.

5.3.1.7

If a type 3 Street is required by SNN Authorities which are a District Council, USRNs are allocated in the following ways:

  • The SNN Authority obtains them from the Authority Street Custodian at the County Council from their type 3 Street range. This helps to ensure synchronicity between the Associated Street Gazetteer (ASG) used in the LLPG and the LSG.
  • The Authority Address Custodian allocates them if both of the following are in place:
    • An agreed service level agreement or local working arrangement between all the District Councils within a County Council administrative area, whereby the Authority Address Custodian is informed of the County Council type 3 Street USRN range which must be used.
    • A robust process to ensure information is exchanged effectively.

5.3.1.8

Street name changes to a Street must not result in a new USRN. All Street name changes, such as a change to SNN legislation, from a type 1 to a type 2 Street or a spelling correction must be recorded as an amendment to the existing USRN.

5.3.1.9

If a Street Name is officially changed, and the former Street Name continues to be used locally, it can be recorded as a type 4 Street in the LSG or ASG.

5.3.1.10

Historical Streets must not be recorded as a matter of course and must only be created as type 4 Streets if there is a need to keep a local reference when a Street Name changes (during a transition period).

5.3.1.11

All type 4 Streets must be open whilst they are active and locally known by that name.

5.3.1.12

Type 4 Streets must be reviewed and when it is deemed that the Street is no longer known by, or referred to colloquially by that name, it must be closed.

5.3.1.13

Street data is transferred as type 11 Street Data, as defined in the DTF current version. For details of the current version see, Related Documents (page 12).

5.3.1.14

SNN Authorities are responsible for creating and maintaining type 1 Street Names and type 2 Street Descriptions, except for:

  • Motorways; and
  • Streets which have a PRoW designation and are not also type 1 Streets.

LHAs are responsible for creating and maintaining type 3 Street Data, type 2 Street Data for Motorways, and type 2 Street Data which have a PRoW designation and are not also type 1 Streets.

5.3.1.15

A type 3 or a type 4 Street must be cross-referenced to either a type 1 or a type 2 Street.

5.3.1.16

This enables the aggregation of sections of road to be identified, for example if “High Street”, “Main Street” and “Church Street” are all part of the numbered Street the “A11”.

5.3.1.17

Only type 1 Streets or type 2 Streets are used for the referencing of Basic Land and Property (BLPU) points in an LLPG and for notification of street works.

5.3.1.18

In a level 3 gazetteer, this cross-referencing is inferred from relationships through ESU cross-references.

TAGS: