📤 Change Requests via NLPG Hub (Data Receiving Authorities)
Candidate changes submitted by Data Receiving Authorities (e.g., Emergency Services) are processed by the national hub.
Validation: Checked against BS 7666 standards by the NLPG Custodian.
Approval: Forwarded to the LLPG Custodian for approval or rejection.
Distribution: Approved changes are returned to NLPG customers through updates sent back to the hub.
Workflow in NGz:
Candidate records are first validated, then stored in a temporary table.
Exported to the hub in DTF 7.3 format via:
File → Export → Change-Only Update File
Once created, validated candidates cannot be removed.
Approved changes return to Data Receiving Authorities in a Change Only Update (COU) file, which can be imported using:
File → Import → Change-Only Update File
🏢 Changes from Data Owners (Custodians)
District/Unitary Authorities manage the LLPG directly.
Sources of change intelligence include:
Internal departments and third-party systems
Candidate requests via the NLPG hub
Processing Steps in NGz:
Import and validate candidates received from the hub.
Approve or reject candidates, then resubmit approved ones to the hub.
Enter new records based on locally gathered intelligence.
Tools:
Candidate → Process Candidates: Approve or reject candidate requests.
File → Export → Change-Only Update File: Export approved changes as part of the COU process.
📂 Local-Only Data
Authorities may hold data in the local gazetteer that:
Is not intended for submission to the hub, or
Does not comply with national standards but is useful internally.
This is called Local Only Data (LOD) and is available only to the data owning authority.
🆔 Property Identifiers
Only the Custodian can issue an official UPRN (Unique Property Reference Number).
When the custodian creates a new property, NGz automatically attaches a UPRN.
If a Data Receiver submits a candidate to the hub:
The hub forwards it without a UPRN.
The Custodian attaches a UPRN during validation.
The updated record (with UPRN) is returned to the Data Receiver.
Local Only Records (LORs) are assigned IDs from a different numbering range.
🚦 Street Identifiers and SNN Coordination
Close coordination is required between:
SNN function (Street Naming and Numbering)
AAC (LLPG Custodian)
ASC (LSG Custodian)
Key points:
The SNN authority provides official street names and numbers.
The AAC manages BLPU, LPI, and LLPG street data.
The ASC manages street gazetteer content, including Level 3 geometry.
In some cases, the SNN authority may allocate a USRN early in the street lifecycle.
🛣️ Street Gazetteer Data
Only the Custodian can issue an official USRN (Unique Street Reference Number).
Requirements:
All publicly maintained highways, prospective highways, and private roads must be recorded in the National Street Gazetteer (NSG).
Street Types in the NSG include:
Motorways
Classified principal streets (trunk and numbered)
Publicly maintained unclassified streets
Prospective publicly maintained streets
Known private streets
Cycleways, footpaths, subways, and maintained or metalled paths
Street Gazetteer Information includes:
Street name and location
Street geometry
Additional Street Data (ASD):
Ownership details
Reinstatement categories
Protected streets
Traffic-sensitive designations
Engineering difficulty zones
Level crossing safety areas
Environmentally sensitive areas
Special surface or construction needs
Priority lanes
Height, weight, width, and direction restrictions
Comments
0 comments
Article is closed for comments.