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.

Navigating the UK Open Address Data Controversy: A Step-by-Step Guide
Source: hackaday.com

What You Need

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?

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).

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.

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.

Navigating the UK Open Address Data Controversy: A Step-by-Step Guide
Source: hackaday.com

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.

Tips

By following these steps, you'll gain a solid grasp of the British address data controversy and its significance for open data worldwide.

Recommended

Discover More

10 Reasons Why Docker Hardened Images Are Built the Hard Way (and Why That Matters)5 Key Insights for Starting Django: A Developer's GuideLinux Kernel Team Rushes Out Seven New Stable Releases with Critical Security Patches10 Key Moves in MARA Holdings' Bold Shift from Bitcoin to AI PowerFunded Standards Work: Sovereign Tech Agency Pilot Pays Open Source Maintainers