> For the complete documentation index, see [llms.txt](https://docs.os.uk/os-downloads/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.os.uk/os-downloads/~/changes/AJZwzCsyrD9hiTbOxIbO/addressing-and-location/code-point-open.md).

# Code-Point Open

{% embed url="<https://www.ordnancesurvey.co.uk/products/code-point-open>" %}

An open dataset of all the current postcode units in Great Britain. For each postcode, Code-Point Open provides a positional quality indicator (PQI), country code, NHS area code along with local government county, district, and ward codes.&#x20;

{% hint style="info" %}
**This product is updated quarterly in February, May, August and November.**
{% endhint %}

<figure><img src="https://1897589978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNpJpLP8RROUaWVQo5ea%2Fuploads%2Fdeirn0CBM2uasdfC4MLr%2FCodepoint-Open-5.png?alt=media&amp;token=6611da8c-a25f-49f0-af9c-92994131b577" alt="A representation of Code-Point Open data showing the area surrounding Edinburgh and the Lothians" width="563"><figcaption><p>A representation of Code-Point Open data </p></figcaption></figure>

{% tabs %}
{% tab title="Features" %}

#### **Locate your analysis**

Link any dataset that includes postcode data to the postcode location in a GIS and build up a spatial picture of your data.

#### **Additional attributes**

To give you extra analytical power, Code-Point Open includes NHS authority and administrative unit codes.

#### **Authoritative data**

Code-Point Open provides accurate coverage of the 1.7 million postcodes in Great Britain that is updated quarterly.
{% endtab %}

{% tab title="Use Cases" %}

#### **Link statistical and numeric datasets to your postcode data**&#x20;

Using ONS administrative unit codes and NHS health authority code attributes in each postcode.
{% endtab %}

{% tab title="Summary" %}

* **Access:** Download
* **Data theme:** Administrative and Statistical Units
* **Data structure:** Vector – Points
* **Coverage:** Great Britain
* **Scale:** 1:1 250 to 1:10 000
* **Format:** CSV, GeoPackage
* **Ordering area:** All of Great Britain
* **Publication months:** February, May, August, November
* **OS Data Hub plan:** OS OpenData Plan (FREE), Public Sector Plan, Premium Plan, Energy & Infrastructure Plan
  {% endtab %}

{% tab title="Additional Information" %}

#### **Northern Ireland coverage**

Northern Ireland postcodes aren’t included in Code-Point Open, but they are present in Code-Point.

#### **Code-Point accuracy and resolution**

Code-Point is created by taking the average of the coordinates of all the individual addresses in a postcode (provided we have any of sufficient quality), then snapping to the nearest of those addresses. Code-Point then delivers the coordinates of that address, as representative of the whole postcode, to a resolution of 1metre.

The accuracy of a Code-Point Open record could be expressed as, that the coordinated position will always be within the notional geographical extent of the postcode. The accuracy of each postcode unit coordinate pair is defined by the positional quality indicator (PQI) which provides a quality statement of a Code-Point record.
{% endtab %}
{% endtabs %}

## How to get this product

Access to this OS OpenData product is free through the [OS Data Hub](https://osdatahub.os.uk/downloads/open/CodePointOpen).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.os.uk/os-downloads/~/changes/AJZwzCsyrD9hiTbOxIbO/addressing-and-location/code-point-open.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.