Share
There are considerable financial and service provision benefits for local authorities who have a high number of linkages between their Local Land and Property Gazetteer (LLPG) and other council systems:
Introduction and context
There are considerable financial and service provision benefits for local authorities who have a high number of linkages between their Local Land and Property Gazetteer (LLPG) and other council systems:
• reduce duplication by maintaining one central database of addresses rather than information dispersed across the council in separate, isolated silos
• enhanced intelligence about address changes throughout the local authority area, particularly through linkages with CRM: waste collection, Council Tax, non-domestic rates, Planning, Electoral Registration, Environmental Health and other key service areas
• data will be constantly tested and used on the ground validating quality and enhancing trust in the data
• provides a source for councils to access ‘out of area’ information which is important for various service areas enabled through linkages to the AddressBase range of products
• focuses the Custodian as the central source of address intelligence within the authority
This briefing includes considerations that officers within local authorities might like to consider when exploring linking the LLPG with other council systems.
Considerations
1. Don’t reinvent the wheel. Has another authority already linked systems – is there guidance already available? You can either contact GeoPlace; or your Regional Chair for advice; or ask a question on the Knowledge Hub or check the case studies on the GeoPlace website
2. Where will the link be held? Will the unique reference be in both systems or just one? E.g. does the Council Tax system hold the UPRN; or does the LLPG hold Cross Reference to the UARN/BA_REF or both?
3. How will updates be made and in what format? Supply of UPRNs to the department; Data Transfer Format import of cross references?
4. What will be the frequency of updates? Live database link or daily update from LLPG for example. Weekly or monthly may be sufficient for some systems.
5. Is there an existing lookup between the datasets e.g. Council Tax lookup tables held at GeoPlace?
6. If no lookup exists, initial address data matching is required. There are different options such as purchasing data matching software; asking GeoPlace to do it under the DCA service contract or creating routines internally to undertake a manual match
7. How to maintain the links as an ongoing process – who will be responsible? Custodian or Owner of Linked dataset? This may be dependent on where the link is held.
