UPRN-keyed OS data for portals, valuation tools and property due-diligence platforms.
Prop-tech products stall when the map is a raster screenshot and the address is a string. We license AddressBase, building footprints, points of interest and imagery as APIs or files so listings, AVMs and feasibility tools sit on the same UPRN and building polygon the rest of the UK market uses.
AddressBase Plus or Premium keyed on UPRN, not free-text search
NGD Buildings for footprints, height context and use class
API delivery for SaaS products that cannot wait on a shapefile drop
// WHO THIS IS FOR
Portals, valuers and development-feasibility tools.
The product question is almost always “can we query this per listing, per title or per site without taking a national file drop every six weeks”.
Portals and consumer apps
Listings, search and sold-price products.
You need a lawful basemap, a UPRN, and enough building and amenity context to power a listing page. AddressBase Plus plus NGD Buildings plus POI covers most consumer products. Premium is for systems that must know historic and alternative addresses.
UPRN lookup and parent-child building relationships
Building polygons for map pins that sit on the footprint
POI amenities for “what is nearby” without scraping Google
API or vector tiles rather than a desktop GIS extract
Valuation, credit and due diligence
AVMs, lender tooling and site-feasibility products.
Underwriting and feasibility need stable identifiers, height and land context, and sometimes imagery for desk review. This is closer to a system of record than a map widget, so Premium addressing and MasterMap or NGD land features show up more often.
AddressBase Premium for historic and provisional UPRNs
NGD Buildings height and use-class context for AVMs
Imagery for desk-based site validation
National coverage with per-query or per-seat commercial terms
// USE CASES
Property products that cannot run on a screenshot.
If the feature needs a UPRN, a building polygon or a lawful map in a customer-facing app, it belongs on a licensed OS route.
Listing and search pages
Put the pin on the building, not the postcode centroid, and show surrounding context without an unlicensed raster.
Automated valuation
Join sold prices and attributes to a UPRN and a building footprint, with height and use class where the model needs them.
Title and due-diligence packs
Desk review against current topography and imagery before a valuer or solicitor visits. This is not a Land Registry title plan substitute.
Development feasibility
Site area, neighbouring buildings, access and land cover for early-stage appraisals that later become a planning map pack.
Occupier and amenities scoring
OS Points of Interest for schools, transport, groceries and services inside a catchment, instead of an unsupported places scrape.
Internal underwriting GIS
A national file drop into the warehouse for credit, insurance-adjacent or portfolio tools that already run a GIS stack.
// THE OS DATA UNDERNEATH
The OS stack most prop-tech products actually need.
Start with addressing and buildings. Add POI, imagery or MasterMap only when the product feature requires them.
UPRN lookup, building polygons and tiles behind your product. This is the usual route for a SaaS portal that cannot run a six-week file load.
Best for: listings, search and consumer apps.
2. National or regional files
GeoPackage or CSV drops of AddressBase and buildings into the valuation or credit warehouse you already operate.
Best for: AVMs, lenders and internal GIS.
3. Custom property build
A joined UPRN–building–POI extract, a hosted due-diligence viewer, or a planning-map generation API if the product later sells maps.
Best for: platforms adding a mapping workflow.
// LICENSING, EXPLAINED
End-user terms for a product that redisplays OS data.
Customer-facing apps
If your users see OS mapping or addressing, the partner licence has to cover that display, including rate limits, attribution and any derived lookup you cache. We scope this as a product licence, not a single-site planning map.
Internal valuation stacks
File delivery into a closed warehouse is simpler. The usual controls are seat counts, environment copies and whether a group company or white-label client can see the same extract.
// FAQ
Questions from property product and data teams.
Is AddressBase Plus enough for a listings site?
Usually yes. Move to Premium when you need historic, alternative or provisional UPRNs — typical for lenders, credit and systems of record, not for a pin on a listing page.
Can we cache UPRN lookups?
Yes, inside the licence we write. Caching is normal; publishing an unlicensed copy of AddressBase is not. We will set retention and refresh rules in the contract.
Do we still need MasterMap if we have NGD Buildings?
Not for a building-footprint pin. You need MasterMap or a planning-map product when the user has to see fences, access, roads and the red-line context of a site.
Can this power a “create a planning map” feature in our app?
Yes, as a separate product workflow — that is closer to our planning-map generation than to a raw data licence. Tell us if the user downloads a council-ready PDF.
What attribution do we have to show?
OS partner attribution on every map view that contains licensed data, plus any AddressBase acknowledgements the product surface requires. We give you the wording with the licence.
Do you cover Northern Ireland?
OS data here is Great Britain. Northern Ireland uses a separate mapping provider, so we will not pretend a GB extract will cover Belfast listings.
// REQUEST A QUOTE
Tell us the product surface and the identifier you hang data on.
Share whether this is a listing page, an AVM, or a due-diligence tool, and whether you need an API or a national file. We will come back with datasets, delivery and indicative pricing under NDA.
