// RETAIL & SITE SELECTION

Catchment, drive-time and location data for multi-site retail and expansion teams.

A new store is a catchment, a drive-time and a competitor set, not a pin on a web map. We license Points of Interest, Highways, AddressBase, postcode polygons and boundaries so location teams can model catchments and expansion on GB-accurate geometry.

  • OS Points of Interest for competitor and amenity density
  • Highways Network and Code-Point for drive-time and catchment
  • AddressBase and Boundary-Line for demand, reporting and site context

// WHO THIS IS FOR

Location planning, property and network strategy.

In-house location teams and the consultancies that support them buy the same layers. The difference is usually whether the extract can leave the building.

In-house location teams

Retail, leisure, grocery, QSR and multi-site operators.

You already know the brand’s analogue set. What you need is a lawful POI file, a road network for drive-times, and addressing or postcode geography for demand. National coverage is normal; a region is enough for a trial.

  • POI for competitors, complementary uses and amenities
  • Highways Network for drive-time and access
  • Code-Point polygons for demand and media catchments
  • AddressBase when the model is household- or premise-level
Location consultancies

Agencies modelling networks for more than one client.

A studio licence has to say whether Client A’s extract can seed Client B’s model. We would rather write that down than discover a national POI file living on a shared drive.

  • Named-client or studio-wide terms
  • The same POI and Highways stack across briefs
  • Boundary-Line for the reporting geography the client’s board uses
  • Optional hosted viewer for a property-committee pack

// USE CASES

Site-selection work that needs more than a web map.

If the recommendation will be defended in a property committee, the catchment should sit on licensed OS geometry.

Competitor and analogue density

POI classified to the analogue set you actually use, not a scrape that disappears when a terms-of-use change lands.

Drive-time catchments

Highways Network for 5, 10 and 15-minute catchments that respect the road graph, not Euclidean buffers around a pin.

Demand and media geography

Code-Point polygons and Boundary-Line for the units a media or insight team already reports on.

Premise-level targeting

AddressBase when the model needs households, workplaces or a UPRN rather than a postcode unit.

Access and servicing

MasterMap and Highways for the last 50 metres — servicing, parking and whether the unit is actually on the pitch.

Network optimisation

National POI plus your own estate file for closures, relocations and cannibalisation, on identifiers that survive a refresh.

// HOW IT'S DELIVERED

National files for the model. A clip for the committee pack.

1. National analytics files

POI, Highways, Code-Point and addressing into the location-planning warehouse or GIS you already run.

Best for: in-house location and insight teams.

2. API for a product or portal

If franchisees or agents see a catchment tool, that is a product surface with attribution and rate limits, not an internal shapefile.

Best for: franchise and broker-facing tools.

3. Site pack

MasterMap, Highways and a drive-time snapshot for a named unit or a shortlist, sometimes as a hosted viewer for investment committee.

Best for: a live acquisition or lease.

// LICENSING, EXPLAINED

Internal models versus tools that leave the building.

Closed location-planning GIS

A national or regional file for named analysts and environments is the simple case. Group companies and overseas parents need to be listed if they can open the warehouse.

Franchisee or public catchment tools

If someone outside the core team sees OS mapping or a derived catchment, that display is in the licence. We will not treat a franchise portal as “internal GIS”.

// FAQ

Questions from location-planning and property teams.

Can we use Google POIs instead?

You can, until the terms, the completeness or the audit trail fail. OS Points of Interest is a licensed, classified GB file you can put in a warehouse and still have next year.

Do drive-times include traffic?

The Highways Network is the graph and the restrictions. Live or typical-speed traffic is a separate feed. We can join them; we do not sell congestion as an OS product.

Is AddressBase required for catchments?

Not if Code-Point polygons and POI already answer the question. Add AddressBase when the model is household-level, delivery-based, or needs a UPRN for the unit itself.

Can a retained consultancy keep our national POI file?

Only under terms that name that consultancy and whether the file can be reused for other clients. Otherwise they should hold their own studio licence.

Do you cover footfall?

No. We license location geometry and POI. Mobility and card-spend feeds stay with those vendors; OS is the frame they should sit on.

Can we publish a store-locator map on the brand site?

Yes as a scoped public display with OS attribution. That is a different use from the internal location GIS.

Official Ordnance Survey Licensed Partner

// REQUEST A QUOTE

Tell us whether this is a national model or a live shortlist.

Share the analogue set, the operating territory, and whether franchisees or a committee will see the map. We will come back with datasets, delivery and indicative pricing under NDA within one UK working day.

  • Reply within one UK working day
  • Senior partner team - no SDR gauntlet
  • Indicative pricing under NDA