3.6.1
Each LLPG is a constituent part of GeoHub, built around the following concept that:
- Each Basic Land and Property Unit (BLPU) represents a real world Object within the Participating Authority administrative area and has a Unique Property Reference Number (UPRN).
- Each BLPU and its associated Land and Property Identifier (LPIs), is referenced to a Street using a Unique Street Reference Number (USRN).
- Each USRN must be contained within GeoHub.
3.6.2
An entity diagram which describes the basic elements that make up the data components of a DCA Address Update is available in Appendix I.
3.6.3
Each Authority Address Custodian must take Address Change Intelligence (ACI) from the SNN processes of the official SNN Officer. ACI can also be taken from other functions within the SNN Authority, for example, Building Control, Development Control and Land Charges. The BLPU Classification code for each applicable Addressable Object is listed in Appendix C.
3.6.4
The following rules apply to the Classification of real world Addressable Objects.
3.6.4.1 If an Addressable Object is Mandatory and is sent to the Authority Address Custodian as a Candidate (see Section 10), it must be created and maintained in GeoHub and therefore must be included in a DCA Address Update.
3.6.4.2 If an Addressable Object is Optional and is sent to the Authority Address Custodian as a Candidate (see Section 10.1.4), it should be created, maintained and delivered within the DCA Address Update. It will also be accepted into GeoHub if it is included in a DCA Address Update.
3.6.5
Appendix C contains the following:
- A table that shows the Classification of applicable Addressable Objects. See Appendix C Section 1.
- An alphabetical list of applicable Addressable Objects and their Classification codes. See Appendix C Section 2.
- A list of inserted BLPU Classification codes. See Appendix C Section 3.
- A list of retired BLPU Classification codes. See Appendix C, Section 4.
- A list of Objects which must not be submitted in an Authority Address Update. See Appendix C, Section 5.
3.6.6
If an Object is neither referred to in the Classifications table at Appendix C Section 1, nor on the excluded items list at Appendix C Section 5, it is possible that it is not within scope. The Authority Address Custodian should email [email protected] to ask whether the proposed real world object is within scope, and, if so, which Classification code should be used.
3.6.7
If a proposed real world Object is not currently within scope, the same email address can be used to ask for the DCA-DECTWG to consider inclusion as an Addressable Object at the next DEC-Addresses review. In the meantime, such Objects may be held locally but must not be submitted in a DCA Address Update.