Navigating the UK Open Address Data Controversy: A Step-by-Step Guide
Introduction
The clash between open data enthusiasts and traditional mapping authorities is a recurring theme in the digital age. A recent example involves the UK's Ordnance Survey (OS) and a project led by data advocate Owen Boswarva. Boswarva compiled address data released by English local councils under the Open Government Licence (OGL) to create a national open source address database. The OS responded with a legal threat, claiming the data belongs to them, not the public. This guide walks you through the key aspects of this controversy, helping you understand the licensing landscape, the legal arguments, and what it means for open data in the UK and beyond.

What You Need
- Basic understanding of open source licenses (especially the Open Government Licence v3.0)
- Familiarity with UK local government structure (county councils and their datasets)
- Access to the Ordnance Survey's public statements on address data
- Owen Boswarva's blog analysis (for detailed legal arguments)
- A web browser to explore OpenStreetMap and OS data portals
- Patience – legal disputes take time to resolve
Step-by-Step Guide
Step 1: Understand the Open Government Licence (OGL)
The UK government releases many datasets under the Open Government Licence (OGL), which allows anyone to copy, publish, distribute, and adapt the information, as long as they attribute the source and comply with any specific restrictions. Local councils, as part of their auditing of council taxes, publish address data under this licence. The key question is: does the OGL cover the addresses themselves, or only the council's compilation of them?
- Visit the National Archives OGL page to read the full terms.
- Note that OGL is compatible with Creative Commons Attribution 4.0.
- Understand that the OS claims underlying intellectual property rights in the data structure.
Step 2: Recognize the Ordnance Survey's Role
The Ordnance Survey is the UK's national mapping agency, historically a major revenue source from licensing geospatial data. With the rise of OpenStreetMap (OSM) – a free, editable map of the world built by volunteers – the OS lost significant income. Now, they see a similar threat from open address data. The OS argues that council address datasets incorporate their own proprietary information, such as grid references and unique property identifiers (UPRN).
- Explore the OS's own open data products (like OS OpenData) to see what they already release freely.
- Compare OS data with what councils publish – note the overlap and differences.
- Understand that the OS has a vested interest in asserting copyright over any derived data.
Step 3: Learn from Owen Boswarva's Project
Owen Boswarva, a data enthusiast, began collating address datasets from English county councils that had been released under OGL. His goal: a unified, open, national address database. He describes the process as simply aggregating publicly available information – much like someone walking down a street and writing down house numbers. That analogy echoes how OpenStreetMap was built.
- Read Boswarva's blog posts detailing his methodology and the legal threats he received.
- Note that he hasn't published the combined database due to the OS's legal challenge.
- Consider the Streisand effect – by trying to suppress the data, the OS has drawn more attention to the issue.
Step 4: Analyze the Legal Arguments
The core dispute: Are councils allowed to release address data under OGL when the Ordnance Survey claims it owns the underlying data structure? The OS argues that even if councils collected the data, they did so using OS tools and references, so the resulting dataset is derivative of OS intellectual property. Supporters of open data counter that factual information (addresses and locations) cannot be copyrighted, only original expressions of it.

- Review the Infopaq and Football Dataco cases in EU/UK copyright law for precedents on data originality.
- Understand that the OS's position could chill local government open data initiatives.
- Follow updates from the UK's Information Commissioner's Office on data licensing disputes.
Step 5: Consider the Broader Implications for Open Data
Whatever the outcome, this case sets a precedent for how open data licences interact with existing proprietary databases. If the OS wins, it may make local councils wary of releasing data that could be claimed by third parties. If Boswarva prevails, it encourages more grassroots compilation of public data. The situation is a microcosm of the tension between public access and commercial interests in data.
- Think about how similar conflicts could arise in other countries (e.g., US addresses vs. private companies).
- Consider contributing to OpenStreetMap as an alternative – it's built by volunteers without reliance on official datasets.
- Watch for court rulings or out-of-court settlements that might clarify the boundaries of the OGL.
Tips
- Stay informed: Follow Hackaday and organizations like the Open Data Institute for updates on this story.
- Respect the Streisand effect: When powerful entities try to suppress data, the resulting publicity often spreads the information further. Use this principle to advocate for transparency.
- Document your sources: If you compile public data yourself, keep careful records of where each piece came from and under what licence – it protects you legally.
- Engage with the community: Join forums like OpenStreetMap UK to discuss best practices for collecting address data without infringing on existing claims.
- Support legal funds: Consider donating to organizations like the Open Rights Group that may take up such cases.
- Remember the human element: Behind the data, there are real people trying to build a more open future – both Owen Boswarva and the Ordnance Survey employees are acting on their principles.
By following these steps, you'll gain a solid grasp of the British address data controversy and its significance for open data worldwide.
Related Articles
- Global Age Assurance Push Risks Crippling Open Source Innovation, Developers Warn
- Complete Guide to Pokémon Go's Lechonk Community Day
- Securing Access to Life-Saving Drugs: A Practical Guide Based on Colombia's Compulsory Licensing Victory
- Open-Source OS for Humanoid Robots Sparks Debate Over Safety and Control
- What’s New in Python 3.13.10? Your Questions Answered
- AI Breakthrough: Diffusion Models Now Generating Coherent Videos
- Meta Breaks Free from WebRTC 'Forking Trap' with Dual-Stack Architecture for 50+ Use Cases
- How to Escape the WebRTC Forking Trap: A Step-by-Step Guide to Continuous Upstream Integration