6.3.8.1
All BLPUs shall have a Logical Status reflecting where the BLPU has reached in its life cycle. GeoHub contains current and historical entries to enable data users to trace changes to land and property details. The table below shows the acceptable LOGICAL_STATUS codes that must be used:
1
Approved
5
Candidate
6
Provisional
7
Rejected external
8
Historical
9
Rejected internal
6.3.8.2
Approved BLPUs (LOGICAL_STATUS = 1) are those which the Authority Address Custodian consider to be the current and complete Record of the Object.
6.3.8.3
Candidate BLPUs (LOGICAL_STATUS = 5) must not be created by the SNN Authority. Candidates are submitted by an external source and the correct LOGICAL_STATUS applied before insertion into the LLPG. See Section 10 and Appendix K.
6.3.8.4
Please refer to the Life Cycle Guidance and Best Practice Document for information on Provisional BLPUs in the SNN / construction stages of development.
6.3.8.5
Historical BLPUs (LOGICAL_STATUS = 8) are used for those Objects which no longer exist as an entity in the real world.
6.3.8.6
Rejected BLPUs (LOGICAL_STATUS = 7 or 9) shall be recorded as follows:
- LOGICAL_STATUS = 7 Records exist when Records received as Candidates are deemed by the Authority Address Custodian to be an inappropriate or an inaccurate representation of a real world Object.
- LOGICAL_STATUS = 9 Records exist when Records from an internal source within the SNN Authority are deemed to be an inappropriate or inaccurate representation of a real world Object.
- Local convention determines whether rejected Records are deleted from LLPGs or retained for auditing purposes.
- For more information on the acceptable use of the BLPU LOGICAL_STATUS Field, see Section 6.4.1.