How much does UK mapping data cost?

UK mapping data pricing looks complicated because it reflects real-world usage. But it needn’t be a headache – the price depends less on ‘maps’ and more on how you’ll use them: internal, published, tiled, downloaded, or served via an API. The same underlying dataset can be priced very differently depending on who needs access, how big the area is, whether you’ll publish externally, and whether you need raw GIS features or simply a basemap for visual context. 

Some OS datasets are available free under the Open Government Licence, but premium datasets such as OS MasterMap remain commercially licensed. We can help you to work out what’s right for your business.

OS data vs third-party suppliers – what’s most cost-effective?

It’s not quite as simple as that. Ordnance Survey (OS) pricing is typically structured around coverage (area / tiles / national); usage rights (internal vs external, distribution rules); number of terminals or users; and term length (often annual contracts for premium datasets).

Third-party suppliers can cost less for specific tasks, or make life a lot easier – our Emapsite team is very happy to help you find out what’s best for your situation. But in general, third party suppliers might bundle licensing guidance, fulfilment, hosting, or workflow tools; offer project-based purchases that avoid overbuying; and can simplify contractor access greatly, as well as multi-team delivery.

Mapping Data per user vs enterprise pricing

A useful rule of thumb, is that pricing works either per user – which is better for small teams and tightly scoped usage – or on an enterprise basis, which is better value once you have multiple teams, wider coverage, or long-running internal use. OS’s own pricing examples show how ‘terminal bands’ can materially change the cost for the same coverage and dataset. Let us know if we can help.

So should it be web map tiles or raw GIS data?

These are very different buying decisions. GIS specialists have the inside track here. Web map tiles / basemaps are visual, and usually best when you need mapping as a background layer in dashboards, portals, or public-facing pages. Raw GIS data – that’s features you can query and analyse – are usually better if you need assets, addresses, networks, topology, attribution, change-only updates, or anything operational. Raw GIS data often carries higher licence value because of its analytical and operational use.  That raw data usually costs more because it enables more. It also carries more compliance considerations – especially around sharing and publication. 

API pricing models - how do they work?

Again, it’s case-specific, but most API pricing falls into one of these patterns:

• • Free tier / included allowance (good for prototypes and low-volume production)
• • Pay as you go (charged by transactions or usage)
• • Subscrption tiers (predictable monthly spend)
• • Enterprise agreements (high volume, multiple services, negotiated terms)

It’s important to get this right, as a highly popular API can ramp up costs significantly – which is great news for business, but does need factoring in from the start. OS’s own Data Hub guidance highlights a ‘free up to £1,000’ monthly allowance for some premium usage, with exclusions for certain APIs.

So how much should you budget for UK Mapping?

These are broad, real-world ranges. Contact us, and we’ll help you work out what your exact cost is likely to be – much depends on dataset, scope, and rights (and if you’re budgeting early, the key is to decide whether you’re buying a basemap, data that you’ll analyse, or an API service):

• • One-off mapping extracts / planning-style outputs: ~£10–£50 per plan (depending on scale, annotation, and workflow)
• • Entry-level national datasets for small teams: hundreds to low thousands per year (per user/terminal products can sit here)
• • Operational ‘core’ datasets used across teams: mid four figures to low five figures per year (common once coverage and user count rise)
• • Enterprise / premium datasets at national scale: five to six figures per year (e.g., corporate/national pricing for high-value layers)

How Emapsite can help

Start with the outcome: basemap, raw data, or API – then write down (1) internal vs external use, and (2) who needs access, including contractors. With those two facts, you can avoid overbuying, pick the right pricing model, and keep compliance simple. If you want, we’ll sanity-check the scope and suggest the cleanest route before you commit budget.

For more information, reach out to our Customer Support team.