// INSURANCE & RISK
Perils models are only as good as the location they hang on. We license AddressBase, terrain, water network, buildings and imagery so UK insurers, MGAs and analytics firms can underwrite, accumulate and stress a risk at a UPRN rather than a postcode sector.
// WHO THIS IS FOR
A personal-lines underwriting API does not need the same cut as a national CAT warehouse. Both still need a UPRN that survives mid-term adjustments.
Hang every policy on a UPRN, then join flood, slope, building and occupancy context. AddressBase Premium is the usual addressing layer because historic and alternative addresses appear on claims and mid-term changes.
National files, stable identifiers, and licence terms that allow derived peril scores. We will write ML-training and derivative use into the contract when that is the product.
// USE CASES
A terrace house and the shop underneath it can share a postcode and not share a flood or subsidence outcome. That is why this sector buys UPRNs.
Resolve the customer’s address to a UPRN before the peril score runs, including flats, annexes and non-postal locations.
Terrain plus Water Network as the geometric skeleton around your flood model or a third-party peril feed.
DTM derivatives and building context for ground-movement screens — still a model input, not a site investigation.
Stable UPRNs and building polygons so a postcode-sector accumulation does not double-count a block of flats.
Imagery and MasterMap for a first look at access, outbuildings and neighbouring structures before a loss adjuster visits.
Points of Interest and building use class for SME quoting where the trade on the ground matters as much as the address.
// THE OS DATA UNDERNEATH
Addressing first. Terrain and water next. Buildings, imagery and POI according to the product, not as a default bundle.
Full UPRN lifecycle — the addressing layer for policies, claims and historic matches.
National 5m DTM for flood, slope and CAT models that run at country scale.
1m surfaces when a high-value or commercial risk needs site-level geometry.
Connected hydrology with flow direction for flood-model skeletons.
Footprints, height and use class for occupancy, accumulation and sum-insured models.
Classified trades and amenities for SME occupancy and nearby-hazard context.
// HOW IT'S DELIVERED
UPRN resolution and selected peril-context layers behind the underwriting journey. Rate limits and caching rules go in the contract.
Best for: personal lines and SME digital quote.
AddressBase, buildings, terrain and water into the CAT or pricing warehouse on the OS refresh cadence.
Best for: pricing, accumulation and reinsurance.
If you sell a flood or subsidence score built on OS geometry, we scope derivative and ML-training use explicitly rather than leaving it implied.
Best for: peril vendors and analytics firms.
// LICENSING, EXPLAINED
Internal underwriting and accumulation is a standard commercial licence. The usual controls are territory, environments and whether a managing agent or TPA can hold the same extract.
A derived peril product is a different use. We will write training, output and redistribution rules into the partner terms so the model you sell does not sit in a grey area.
// FAQ
Claims, mid-term changes and historic policies hit alternative, provisional and retired UPRNs. Plus is enough for a clean current gazetteer. Premium is the system-of-record layer.
No. We license OS geometry — terrain, water network, buildings, addresses — that your flood model or a third-party peril feed sits on.
Yes when the contract says so. Tell us it is an ML or derived-score use at enquiry, not after the model is in production.
For some CAT views, yes. For quoting a single dwelling, no — a UPRN and a building polygon change the answer on terraces, flats and split commercial/residential buildings.
If we name that use. A hosted viewer for claims is a common add-on; emailing them an unlicensed GeoPackage is not.
OS data in this catalogue is Great Britain. NI needs a separate mapping source; we will not silently pad a GB extract.
// REQUEST A QUOTE
Share the product (personal lines, commercial, reinsurance, peril vendor), the identifier you hang a policy on, and whether you need an API or national files. We reply under NDA within one UK working day.
Prefer email? Write to data@planningmapsuk.co.uk.
