Batch geocoding
Match sets of records to locations where suitable source data and rules are available.
- Batch geocoding
- Address matching
- UPRN matching
- Data cleansing
- GIS analysis
- Reporting geography
From records to places
Geocoding helps connect business records to addresses, coordinates, UPRNs, properties, streets, GIS layers and reporting geography. That connection can be useful during migration, service integration, reporting and spatial analysis.
The quality of a geocoding result depends on the input data, available address sources, matching rules and review process.
What geocoding can support
Address matching
Compare input addresses against configured address or gazetteer sources.
UPRN matching
Connect records to UPRNs where the data supports reliable matching.
Data migration preparation
Prepare legacy records for migration by adding location context and reviewing unmatched records.
GIS analysis
Use matched records in mapping, spatial queries and service planning.
Reporting geography
Connect records to areas, boundaries or other reporting geographies where configured.
Data cleansing
Identify incomplete, inconsistent, duplicated or ambiguous address records.
Service-area datasets
Support customer or service-area datasets where the data is appropriate for matching.
Data Integration
Use geocoding alongside DataPump or integration workflows where configured.
Data quality and matching
Matching quality depends on input data, address sources, matching rules and the review process. Unmatched or ambiguous records may need manual review before they are used operationally.
Configured rules, parsing and pattern matching can help in some projects, but they should be tested against the authority's data and agreed acceptance criteria.
Coverage and data sources
Coverage, data sources and licensing depend on the project, customer area, available datasets and agreed service model. Current licensing and data-source availability should be confirmed before relying on any specific dataset or coverage assumption.
Addressing Services
Use address and gazetteer data across GIS, case-management, public portal and reporting workflows.
Gazetteer Management
Connect geocoding work with LLPG, LSG and addressing workflows.
Data Integration
Use geocoding as part of migration, integration and data preparation.
Data Services
Plan geocoding within wider spatial data services.
Example use cases
Migrating legacy records
Add location context before records move into a new GIS, case-management or reporting environment.
Matching customer records to UPRNs
Improve the ability to connect records across services where reliable matching is possible.
Preparing service data for GIS
Make address-based records usable in maps, spatial queries and operational review.
Supporting emergency planning datasets
Prepare appropriate datasets for spatial review where the data, permissions and service model allow.
Improving reporting geographies
Connect records to boundaries, service areas or other reporting geography where configured.
Discuss geocoding and address matching
Talk to StatMap about geocoding, address matching, UPRN linking, data migration and spatial reporting requirements.