Checklist for buying mapping data in the UK

If it’s not your field of expertise, then a mapping data purchase may look daunting. Here is a practical buying checklist that keeps costs, compliance, and delivery aligned from day one: 

• • Define your use case: What’s the job: visual context, analysis, routing, asset management, customer-facing service, regulatory reporting, or something else?
  
  
• • Internal vs public-facing: Will the mapping stay internal, or be seen outside the organisation in any form: web, portal, PDF, print, app, or contractor delivery?
  
  
• • API vs hosted vs raw data: Do you need an API service, a hosted layer, or downloadable GIS data you can store and analyse? Choose the model that matches your tech stack and governance.
  
  
• • User numbers and access model: How many users need access, and what counts as a user: staff, temps, partners, contractors? Be explicit.
  
  
• • Data refresh requirements: How current does it need to be - and how will updates be delivered and applied? Decide whether you need regular refresh, change-only updates, or “good enough for this project”.
  
  
• • Exit strategy: If you stop paying, what happens? Can you retain historic outputs? Do you need to delete local copies? How will you replace the layer without breaking dependent systems?
  
  
• • Attribution obligations: Where will the attribution appear - on web maps, dashboards, printed reports, PDFs, slides, or screenshots? Build it into templates and UI early.
  
  
• • Indemnity and liability: What warranties are offered, what liability caps apply, and who carries the risk if mapping is wrong or misused? Align this with procurement and any regulatory exposure.

Buying mapping data goes smoothly when you treat it like any other business input: define the outcome, define who will touch it, and define what ‘done’ looks like. Problems start when ‘just a basemap’ becomes a public-facing service, when supplier access is improvised, or when nobody has written down what the organisation is actually entitled to do with the data.

How Emapsite can help

Write a one-page brief using the checklist above: intended use, audience, delivery model, user access, refresh, and exit. That makes it easy to compare suppliers, keeps licence and attribution obligations visible, and prevents a successful pilot turning into an unplanned compliance issue later.

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