GeoHub NI - Datasets - LPS Pointer
LPS Pointer
Geometry Type |
Access |
|---|---|
Point |
NIMA |
Description of Data
Pointer is the address database for Northern Ireland created and maintained by Ordnance Survey of Northern Ireland (OSNI), with input from Local Councils, the Land and Property Services (LPS) and Royal Mail (RM). This is now the common standard address for every property in Northern Ireland.
It is important to note that Pointer is a dataset for addressable buildings in Northern Ireland.
Each building has a UNIQUE_BUILDING_ID, which uniquely identifies a Primary Addressable Object (PAO). A PAO is defined as the ‘physical footprint’, i.e. the building shell.
Each property has a Unique Property Reference Number (UPRN). The UPRN represents the Secondary Addressable Object (SAO) e.g. a residence or business within a building.
Pointer has been allocated a set of UPRNs from the national hub, which are allocated to all addresses within the dataset. This will ensure consistency of UPRNs across Northern Ireland and Great Britain.
Pointer will be the key to accessing property related data held by multiple organisations from a single point.
Each building will be assigned a geographic position (X_COR and Y_COR) and a postal address.
Metadata
Metadata Field Name |
Attribute |
|---|---|
| Title | LPS_Pointer |
| Alternative Title | Address, Postal Address |
| Originator | Land and Property Services |
| Abstract | Pointer is a comprehensive and standardised address database, which holds address information for every property in Northern Ireland. Products can either be supplied as the full dataset file or by Local Government District. This is updated monthly. |
| Topic Category | Location |
| Subject | Addresses |
| Dataset Language | English UK |
| Data Collection Start Date | 1 January 2003 |
| Data Collection End Date | |
| Dataset Reference Date | 1 January 2007 |
| Frequency of Update | Continual |
| Date of update of metadata | 1 January 2007 |
| Spatial reference system | Irish National Grid |
| North bounding coordinate | 55.3257 |
| South bounding coordinate | 54.0114 |
| East bounding coordinate | -5.3796 |
| West bounding coordinate | -8.1806 |
| Extent | Northern Ireland |
| Access constraint | License |
| Use constraints | License, Copyright |
| Spatial resolution | 0.4m |
| Data format | CSV, GML |
| Vertical extent information | N/A |
| Additional information source | http://www.osni.gov.uk |
| Browse graphic |
|
| Lineage | |
| Distributor - Contact title | Digital Supply |
| Distributor - Name | Land and Property Services |
| Distributor - Postal address | Colby House, Stranmillis Court, Malone Lower Belfast BT9 5BJ |
| Distributor - Telephone number | 028 90255739 |
| Distributor - Facsimilie number | 028 90255735 |
| Distributor - Email | digital.supply@osni.gov.uk |
| Distributor - Web address | http://www.osni.gov.uk |
| Metadata standard name | UK Gemini |
| Metadata standard version | Version 2.0 |
Attributes
| Attribute | Description |
|---|---|
| ORGANISATION_NAME | The trading or business name of an organisation within an addressable property. This field is populated with data supplied by Royal Mail where applicable. Use of this field incurs a Royal Mail licence fee. |
| SUB_BUILDING_NAME | The name or number of a flat, apartment or unit within an entire building identifying a Secondary Addressable Object (SAO). This name or number should be prefixed by the following ‘UNIT’, ‘FLAT’, ‘APARTMENT’ etc Population of this field is mandatory where:
Population of this field is optional in all other cases The use of SUB_BUILDING_NAME applies to flats, apartments, blocks, floors, maisonettes, suites or units located within a building. |
| BUILDING_NAME | A name given to a building – the physical structure to which the address belongs. Population of this field is optional. Not all historical records, which have a BUILDING_NAME, will have a building number. All new records, which contain a BUILDING_NAME, will have a building number. When an organisation vacates a building, the BUILDING_NAME may remain. |
| BUILDING_NUMBER | A number associated with a building. The BUILDING_NUMBER will appear as entered by the Local Council. Previously not all Councils allocated a building number for properties in rural areas. A Building Number may be singular, for example, 1, 11, 111 or a number range, for example, 1-11 or 1A-2A (without spacing). Building Numbers with letter suffixes are valid, for example 1A. Building Numbers must always be held as a numeric format ie 72A not Seventy-Two A. |
| PRIMARY_THORFARE | The name of the thoroughfare on which the building is located or the main access point on which it is located. Population of this field is mandatory. The spelling and punctuation of thoroughfare names are supplied by the Local Councils. Thoroughfare descriptors, for example, road and street are not abbreviated – they are always shown in full. It should be noted that one Local Council (Fermanagh) does not name thoroughfares in rural areas. |
| ALT_THORFARE_NAME1 | A locally known alternative or an official thoroughfare name in another language. In Northern Ireland only Irish or Ulster-Scots languages are used by the Street Naming Authorities. These names are only adopted into Pointer once approved by the Local Council. Population of this field is optional. An ALT_THORFARE_NAME1 will only be permitted for use where a PRIMARY_THORFARE also exists for a building. |
| SECONDARY_THORFARE | This field is used to better identify an address; it will be the main road off which the PRIMARY_THORFARE is located. Population of this field is at the discretion of the Local Council. |
| LOCALITY | A locality is a named area, which does not necessarily fit into the definition of a town. A primary locality is typically a suburb of a city or town. A locality can also be an industrial estate, business centre, business park or hospital complex. The LOCALITY field is related to the TOWN field; at least one of these fields must be populated |
| TOWNLAND | The name of the townland within which the building is located. Population of this field is mandatory. The system generates Townland details for new and changed address records, using OSNI Largescale townland boundary dataset. Townland names are not unique either within a County or Administrative area. The scale of the county boundary dataset is 1:2,500. This represents a change from earlier datasets that were based on 1:50,000 scale. |
| TOWN | The name of a settlement, within which the building is located. Population of this field is at the discretion of the Local Council The TOWN field is related to the LOCALITY field; at least one of these fields must be populated |
| COUNTY | The name of the County, as defined by OSNI, within which the PAO is located. Population of this field is mandatory. The system generates County details for new and changed records, using the OSNI largescale county boundary dataset. The scale of the county boundary dataset is 1:2,500. This represents a change from earlier datasets that were based on 1:50,000 scale. There are currently 6 geographic county boundaries in Northern Ireland:
|
| POSTCODE | A set of characters identifying a group of postal delivery points, defined by Royal Mail, to facilitate the sorting and delivery of mail. Population of this field is not mandatory as an address is created by Local Councils, however all addresses will receive a POSTCODE as part of its lifecycle. Use of this field incurs a Royal Mail licence fee. |
| BLPU | Basic Land and Property Unit. This field still has not been finalised. |
| UNIQUE_BUILDING_ID | A 12-digit non-intelligent sequential number, which uniquely identifies a Primary Addressable Object (PAO). A PAO is defined as the ‘physical footprint’, i.e. the building shell. Population of this field is mandatory. This number will be permanently associated with the PAO i.e. throughout the POINTER Address Lifecycle. A UNIQUE_BUILDING_ID will be assigned either upon its creation in Pointer or upon creation within a Local Council’s database. A UNIQUE_BUILDING_ID can relate to one or many UPRNs but it will have only one Building Name and/or Building Number. If a building is sub-divided into a number of separate units that are new PAOs, the UNIQUE_BUILDING_ID for the original building will be archived and new UNIQUE_BUILDING_IDs will be assigned. If a building is sub-divided into a number of separate units that are new SAOs, the UNIQUE_BUILDING_ID for the building will remain the same and new UPRNs will be assigned. If a number of UNIQUE_BUILDING_IDs are subsumed into a single PAO, then the UNIQUE_BUILDING_ID for the original buildings will be archived and a new UNIQUE_BUILDING_ID will be assigned. If an existing building is demolished and new property/ies are built on the site, each new building will be assigned a new UNIQUE_BUILDING_ID and the previous UNIQUE_BUILDING_ID will be archived. |
| UPRN | Unique Property Reference Number. A 12-digit non-intelligent sequential number, which uniquely identifies a Secondary Addressable Object (SAO). An SAO covers such items as units, flats, or organisations within a building. Population of this field is mandatory. This number will be permanently associated with the SAO i.e. throughout its lifecycle. For where an SAO has been duplicated by different organisations, this will be matched to an existing UPRN. The system generates this attribute automatically. |
| USRN | Unique Street Reference Number. Up to a 10-digit number that will uniquely identify each Primary Thoroughfare in Pointer. Population of this field is mandatory. (See Appendix VII) Uniquely identifies each street (where there is more than one street with the same name). |
| LOCAL_COUNCIL | The name of the administrative area (Local Council) in which the building exists. Population of this field is mandatory. The system will generate Local Council details for new and changed records, using the OSNI largescale ward boundary dataset. The scale of the Local Council boundary dataset is 1:2,500. |
| X_COR | Each building is geo-referenced using co-ordinates on the Irish Grid. Before the building has been surveyed the address will be given a temporary X_COR by the creator of the address. When OSNI survey the building the permanent co-ordinate is collected. The value is held at 1 metre accuracy. Population of this field is mandatory |
| Y_COR | Each building is geo-referenced using co-ordinates on the Irish Grid. Before the building has been surveyed the address will be given a temporary Y_COR by the creator of the address. When OSNI survey the building the permanent co-ordinate is collected. The value is held at 1 metre accuracy. Population of this field is mandatory |
TEMP_COORDS |
Indication as to whether the X_COR and Y_COR are permanent (i.e. assigned during an OSNI survey) or temporary. When an address is created by a Local Council this field will be populated with a ‘Y’. When it is made permanent, by an OSNI surveyor, it will have a ‘NULL’ value. Population of this field is optional. Can only be ‘Y’ or ‘NULL’ values. TEMP_COORDS status will be overwritten once the property has been surveyed. |
| BUILDING_STATUS | The current physical status of the building. Population of this field is mandatory. Permitted PAO Status values are: None, Under Construction, Built, Derelict and Demolished This field reflects changes to the Building_Status. |
| ADDRESS_STATUS | The current logical status of the address. Permitted ADDRESS_STATUS values are: (See diagram above)
Historical and Rejected addresses should be excluded from mail shots |
| CLASSIFICATION | The current use of the building, derived from the LPS classification. Population of this field is mandatory. Permitted CLASSIFICATION values are:
When the building use of an addressable object changes, the CLASSIFICATION field will be updated from the LPS Valuation List to reflect this change. |
| CREATION_DATE | The date when an address is first entered into the system by the Local Council. This field will only be populated for records created after the Pointer application went live in 2005. |
| COMMENCEMENT_DATE | This is the date when construction on the property has begun. This field will be populated for records created after the release of the new Pointer Product and when Local Council informs Pointer of the fact. This indicates when the BUILDING_STATUS changes from ‘NONE’ to ‘UNDER CONSTRUCTION’ |
| ARCHIVED_DATE | This is the date when the address is deemed to be no longer in use. This indicates when the ADDRESS_STATUS becomes ‘HISTORICAL’ |
| ACTION | This field is only populated in the update product to denote the nature of a change. Permitted ACTION values are:
This field will be blank in the full product. |


