📋 Overview
Each BLPU (Basic Land and Property Unit) must have at least one LPI (Land and Property Identifier).
After creating the first LPI, additional LPIs can be added via the LPIs Tab → Add LPI button.
The same details are required for the first LPI and for any additional LPIs.
Some of the information is brought across from the BLPU entry or generated automatically.
🗂️ LPI Fields
🔑 UPRN (Mandatory)
Unique Property Reference Number for the property, land, or structure.
Identifies fixed-location entities with uniform occupation, ownership, or function.
🛣️ USRN (Auto-generated)
Unique Street Reference Number of the assigned street.
🏷️ Street Name (Auto-generated)
The street name the property is assigned to.
🏙️ Street Town (Auto-generated)
Pulled from the Street Tab for the assigned street.
🌐 Local Only (Optional)
Checkbox to flag an LPI as Local-Only.
Prevents updates being pushed to the Hub.
⚖️ Priority (Not Used)
Not applicable for NLPG.
🔄 Alternate
See Logical Status.
📮 Post Code & Post Town (Conditional)
Post Town = nearest major settlement used by Royal Mail.
May differ from Street Town.
If Street Town = Post Town, the name is not repeated.
💡 Tip: Always check the Postal Address Format window to confirm address details.
If Postally Addressable = Yes: fill these fields.
If No: leave blank, otherwise Hub warnings occur.
🏠 PAON (Primary Addressable Object Name) (Mandatory)
Records the name/number of a property.
Up to five fields:
Property number
Number suffix (e.g., letter)
Second number (for multi-unit buildings)
Second suffix
Property name
At least one PAON field must be completed for every LPI.
🏢 SAON (Secondary Addressable Object Name) (Optional)
Works like PAON but typically represents parent/child relationships.
📌 Example:
PAON = “Cygnet House”
SAON = “9th Floor”
Other offices in the building could then use their own floor numbers.
📨 Postal Address Format (Read-only)
Displays the formatted address as a mailing label.
Auto-updates whenever address details change.
✉️ Postally Addressable (Mandatory)
Select Yes if LPI is postal.
Large organisations may have dedicated postcodes.
✅ Official Flag (Optional)
Indicates whether the LPI is an official address.
Requested: postcode request sent to Royal Mail.
Confirmed: postcode confirmed by Royal Mail.
📶 Level (Optional)
Indicates the vertical level (e.g., Ground floor, 1st floor).
👨👩👧 Child LPI (Optional)
Checkbox enables parent/child relationship assignment.
Parent list contains records with PAON but no SAON.
Selecting a parent auto-fills Parent UPRN.
📌 See: Parent/Child Relationships
📜 LPI History (Read-only)
Scroll arrows allow browsing previous versions.
📝 Notes (Optional)
Non-BS7666 field for storing additional property notes.
🔢 Version No (Auto-generated)
Increments with each significant change.
🔎 Logical Status
See Logical Status rules (same as BLPU).
📅 Start Date (Mandatory)
Date the property first existed in the real world.
Must be entered manually.
📅 Entry Date (System-controlled)
For new properties: set to current date automatically.
For imported properties: pulled from source data.
📅 End Date (Auto-generated)
Populated automatically if the property is historical or rejected.
📅 Last Update Date (Auto-generated)
Updates to the current date whenever edits are made.
✅ Click Save when all fields are complete.
⚙️ SDTF "Level" Additions
Populated LPI Level combo box with likely values:
-1, 0, 0.5, 1, 1.5, 2(others can be entered manually)Validation: Street BLPU, BLPU Class = Land or Property Shell → LPI Level not allowed
LPI Level mandatory if Start Date = 01/01/2017 or later
Numeric validation enforced for LPI Level (N2.1 format).
⚙️ Set LPI Defaults
New LPIs are created with the following defaults. These can be overridden in the NLPG.INI file.
[LPI Record Default]
LOGICAL_STATUS=1
POSTALLY_ADDRESSABLE=Y
OFFICIAL_FLAG=Y⚠️ Important: Ensure defaults are compatible with BLPU Logical Status and BLPU State. Otherwise, validations will fail.
Comments
0 comments
Article is closed for comments.