# Resolved Data Issues

This page lists resolved data issues in relation to the OS NGD themes, collections and feature types.

{% hint style="info" %}
Please see the [Current Known Data Issues](https://osdatahub.os.uk/support/status) page for details about current live data issues issues.

Any live interruptions to the availability of OS NGD API – Features and OS NGD API – Tiles will be documented on the [Service Availability Dashboard on the OS Data Hub](https://osdatahub.os.uk/serviceStatus).
{% endhint %}

## Generic OS NGD resolved data issues

No current resolved data issues to note that impact multiple OS NGD themes.

## OS NGD Address Theme resolved data issues

<table data-full-width="true"><thead><tr><th width="240.4000244140625">Data Issue Name</th><th width="495.400146484375">Original Description for Data Issue</th><th width="157.3336181640625">Resolution Date</th><th>Resolution Message</th></tr></thead><tbody><tr><td>Duplicate rows in the Postal Address Related Component</td><td><p>We are aware of an issue with daily Change‑Only Update (COU) supplies, resulting in a small number of duplicated rows in the Postal Address Related Component. </p><p></p><p>This issue only affects customers with orders containing OS NGD Address feature types data schema versions 1.0 or 2.0 who received a daily supply between 11 and 18 February. </p><p></p><p>If you believe you are affected by this issue, please <a href="https://www.ordnancesurvey.co.uk/contact-us/business-government/use-os-data">contact us for assistance</a>.</p></td><td>04/03/2026</td><td>This issue was resolved on 04 March 2026.</td></tr><tr><td>Small numbers of UPRNs appearing across lifecycle feature types in COUs</td><td>We are aware of an issue affecting the OS NGD Address Theme where a small number of Unique Property Reference Numbers (UPRNs; approximately 500 out of 43 million) are appearing in more than one lifecycle feature type (i.e. present in both the Built Address Feature Type and the Pre‑Build Address Feature Type) within Change‑Only Updates (COUs).</td><td>27/02/2026</td><td>This issue was resolved by 27 February 2026. </td></tr></tbody></table>

## OS NGD Administrative and Statistical Units Theme resolved data issues

<table data-full-width="true"><thead><tr><th width="236.5999755859375">Data Issue Name</th><th width="497.5333251953125">Original Description for Data Issue</th><th width="156.666748046875">Resolution Date</th><th>Resolution Message</th></tr></thead><tbody><tr><td>Three missing parishes from the Parish Or Community Feature Type</td><td><p>The Margaret March, Tollard Royal and Marlow Bottom Civil Parish (CP) within the Parish Or Community Feature Type (data schema version 1.0) are missing from the May 2025 release of data.</p><p></p><p>This issue is currently being investigated and we are working to fix it for a future release.</p></td><td>October 2025</td><td>The three missing parishes were restored to the Parish Or Community Feature Type in the October 2025 release of data for the OS Boundaries Collection.</td></tr></tbody></table>

## OS NGD Buildings Theme resolved data issues

No current resolved data issues to note for this theme.

## OS NGD Geographical Names Theme resolved data issues

No current resolved data issues to note for this theme.

## OS NGD Land Theme resolved data issues&#x20;

<table data-full-width="true"><thead><tr><th width="248.666748046875">Data Issue Name</th><th width="494.86669921875">Original Description for Data Issue</th><th width="162.5999755859375">Resolution Date</th><th>Resolution Message</th></tr></thead><tbody><tr><td>Intertidal areas beneath Travelling Cranes and Supported Conveyors not present</td><td>Intertidal areas beneath Travelling Cranes and Supported Conveyors are not currently present and will be added in a future data improvement. This applies to data schema version 3.2 of the Land Feature Type.</td><td>September 2025</td><td>This issue was resolved in September 2025.</td></tr><tr><td>Intertidal areas beneath elevated structures situated over intertidal islands not present</td><td>Intertidal areas beneath elevated structures situated over intertidal islands are not currently present and will be added in a future data improvement. This applies to data schema version 3.2 of the Land Feature Type.</td><td>September 2025</td><td>This issue was resolved in September 2025.</td></tr></tbody></table>

## OS NGD Land Use Theme resolved data issues

No current resolved data issues to note for this theme.

## OS NGD Structures Theme resolved data issues

<table data-full-width="true"><thead><tr><th width="245.4666748046875">Data Issue Name</th><th width="507.5999755859375">Original Description for Data Issue</th><th width="163.666748046875">Resolution Date</th><th>Resolution Message</th></tr></thead><tbody><tr><td>Field Boundary data quality</td><td>At the time of launch of the Field Boundary Feature Type (March 2024; data schema version 1.0), areas of Great Britain were still to be quality checked and will be improved as part of OS’s continuous quality review programme when updated imagery is available. Most of the known data quality errors are either in Moorland areas or where imagery was captured earlier in the year and vegetated features are ‘leaf-off’.<br><br>Data issue identification date: 27/03/2024.</td><td>01/03/2026</td><td>This issue was resolved by 01/03/2026 through improvements made to the automated method used to identify field boundary data. More information is available from the <a href="../../os-ngd-news/os-ngd-improvements#march-2026-improvements-to-the-field-boundary-feature-type">OS NGD Improvements page</a>.</td></tr><tr><td>Some underground Structure features are missing from the Habitat Coverage cross reference table</td><td>Three underground Structure features with an OS Land Cover Tier B attribute of ‘Coniferous Trees’, ‘Non-Coniferous Trees’, ‘Scattered Coniferous Trees’ or ‘Scattered Non-Coniferous Trees’ are missing from the corresponding Habitat Coverage Reference cross reference table. This issue impacts the Land Feature Type.<br><br>Data issue identification date: 15/04/2024.</td><td>03/11/2025</td><td>This issue was resolved on 03/11/2025.</td></tr><tr><td>Duplicate features in the OS NGD Structures and OS NGD Land Themes, and duplicate features in OS NGD Structures and OS NGD Building Themes</td><td><p>Following a recent update, not all features which were due to move themes fully migrated from one OS NGD theme to another. There are 3 595 duplicate features in the below themes:</p><ul><li>3 584 ‘slipway’ features are in both the OS NGD Structures Theme and the OS NGD Land Theme. These features should only be available in the OS NGD Land theme.</li><li>11 ‘Grandstand’ features are in both the OS NGD Structures Theme and the OS NGD Buildings Theme. These features should only be available in the OS NGD Building Part Feature Type.</li></ul><p>The duplicated features have the same ID when represented in the more than one Feature Type.</p></td><td>02/09/2025</td><td>This issue was resolved on 02 September 2025. Customers who take monthly updates will see this fix in the next update on 01 October 2025.</td></tr></tbody></table>

## OS NGD Transport Theme resolved data issues

<table data-full-width="true"><thead><tr><th width="247">Data Issue Name</th><th width="509.066650390625">Original Description for Data Issue</th><th width="165.7998046875">Resolution Date</th><th>Resolution Message</th></tr></thead><tbody><tr><td>Street to Road Link reference table refers to non-existent features</td><td>316 828 records in the Street to Road Link reference table refer to Road Link features which no longer exist. This issue is currently being investigated.</td><td>12/03/2026</td><td>This issue was resolved on 12 March 2026. Customers who take monthly updates will see this fix in the next update on 01 April 2026.</td></tr><tr><td>Street Light features refer to non-existent links</td><td>7 Street Light features refer to a Road Link (data schema versions 2.0, 3.0, 4.0 and 5.0) that does not currently exist. This issue is currently being investigated.</td><td>14/02/2026</td><td>This issue was resolved on 14/02/2026.</td></tr><tr><td>Road Links with unexpected 0 values for pavement width attributes</td><td>187 Road Link features (data schema versions 2.0, 3.0, 4.0 and 5.0) where we would expect their Presence of Pavement Minimum Width M and Presence of Pavement Average Width M attributes to be populated have a value of 0 for these attributes. This issue is currently being investigated.</td><td>12/12/2025</td><td>This issue was resolved on 12/12/2025.</td></tr><tr><td>Road Links with unexpected pavement update dates</td><td>17 Road Link features (data schema versions 2.0, 3.0 and 4.0) with an incorrect Presence of Pavement Update Date attribute date value in the future (2999). The update date should reflect when the attribute was last updated, so it should never be a future date. This issue is currently being investigated.</td><td>05/11/2025</td><td>This issue was resolved on 05 November 2025. Customers who take monthly updates will see this fix in the next update on 01 December 2025.</td></tr></tbody></table>

## OS NGD Water Theme resolved data issues

<table data-full-width="true"><thead><tr><th width="253.4000244140625">Data Issue Name</th><th width="509.0665283203125">Original Description for Data Issue</th><th width="162.2664794921875">Resolution Date</th><th>Resolution Message</th></tr></thead><tbody><tr><td>Incorrect 0m width values for Water Links</td><td>There are 190 Water Link features (data schema version 2.0) that have Width Average, Width Minimum and Width Maximum attribute values of 0m. There are an additional 385 Water Link features (data schema version 2.0) that have a Width Minimum attribute value of 0m.</td><td>28/01/2026</td><td>This issue was resolved on 28 January 2026. Customers who take monthly updates will see this fix in the next update on 01 February 2026.</td></tr><tr><td>Unexpectedly null Level of Detail values for Water Links</td><td>7 Water Link features (data schema version 1.0) incorrectly have a null Level of Detail attribute value. All Water Links should have this value populated. This issue is currently being investigated.</td><td>28/01/2026</td><td>This issue was resolved on 28 January 2026. Customers who take monthly updates will see this fix in the next update on 01 February 2026.</td></tr><tr><td>Unexpectedly null Catchment Name and Catchment ID for Water Links</td><td>Approximately 19 000 Water Link features (data schema version 1.0) incorrectly have a null Catchment Name and Catchment ID. Only links which straddle catchment boundaries or sit entirely outside catchments should have null values in these attributes. </td><td>28/10/2025</td><td>This issue was resolved on 28 October 2025. Customers who take monthly updates will see this fix in the next update on 01 November 2025.</td></tr><tr><td>Water Link features with an End Node attribute value of 'MissingXRef'</td><td>3 667 Water Link features (data schema version 1.0) erroneously have an End Node attribute value of 'MissingXRef'. This may cause problems with validation as the value is not a valid OSID.</td><td>28/10/2025</td><td>This issue was resolved on 28 October 2025. Customers who take monthly updates will see this fix in the next update on 01 November 2025.</td></tr><tr><td>Orphaned Water Nodes</td><td>1 007 Water Node features (data schema version 1.0) are not referenced by any extant Water Link.</td><td>28/10/2025</td><td>This issue was resolved on 28 October 2025. Customers who take monthly updates will see this fix in the next update on 01 November 2025.</td></tr><tr><td>Unexpected Water Link names</td><td>Approximately 4 000 Water Link features (data schema version 1.0) are not being named as expected: Name 1 Text / Name 2 Text attribute populated with the name from the longest (by length) named waterway; Name Secondary 1 Text attribute populated with the name of the next longest named waterway, etc.</td><td>28/10/2025</td><td>This issue was resolved on 28 October 2025. Customers who take monthly updates will see this fix in the next update on 01 November 2025.</td></tr></tbody></table>

## Archived resolved data issues for temporal filtering

Resolved data issues older than six months are included in the tabs below under each OS NGD theme.

{% tabs fullWidth="true" %}
{% tab title="Archived data issues" %}
Snapshots of OS NGD data retrieved through temporal filtering in OS Select+Build may include issues with the data that were present at the time but have since been resolved. The following tabs contain details of resolved data issues more than six months old, arranged by the OS NGD themes they apply to.

For more information on temporal filtering within OS Select+Build, please see the [getting started with temporal filtering page](https://docs.os.uk/osngd/getting-started/downloading-with-os-select+build/getting-started-with-data-packages/getting-started-with-temporal-filtering).
{% endtab %}

{% tab title="Generic OS NGD Issues" %}

<table data-full-width="true"><thead><tr><th width="205">Data Issue Name</th><th width="273">Original Description for Data Issue</th><th width="112.400146484375">Resolution Date</th><th>Resolution Message</th></tr></thead><tbody><tr><td>Interruption to the supply of Daily Updates for OS NGD Building Part (February 2025) and impact on topological data ‘surface’ of OS NGD 'Feature' Collections</td><td><p>We are currently deploying improvements to the Building Height data available on OS NGD Building Part (data schema v1.0 and v2.0) until 24 February 2025. During this period, daily updates to the Building Part Feature Type, such as changes captured by surveyors, will be temporarily paused. These changes will be reflected in the product data after the completion of the improvements.</p><p></p><p>Consequently, users may observe anomalies in the consistency of the topological surface when utilising various OS NGD 'Feature' Collections (such as OS NGD Land Features). These anomalies will manifest as holes or overlaps where the Building Part feature has not been updated concurrently with the surrounding features. This impact will also be visible in OS NGD API – Features and OS NGD API – Tiles.</p><p></p><p>Please note that we advise against using counts from the OS NGD Building Part Feature Type with a temporal filter set between <strong>02 February 2025 and 24 February 2025</strong> as the counts may not be accurate due to the impact on a small number of topographic features.</p></td><td>24/02/2025</td><td><p>The improvements were completed by 24/02/2025 as planned and Daily Updates resumed as normal for impacted feature types.</p><p></p><p>Please note that we advise against using counts from the OS NGD Building Part Feature Type with a temporal filter set between <strong>02 February 2025 and 24 February 2025</strong> as the counts may not be accurate due to the impact of the improvement work on a small number of topographic features.</p></td></tr><tr><td>3D geometry missing in GeoPackage format for some feature types in the OS NGD Transport Network and Water Network Collections</td><td>In the OS NGD Transport Network Collection and OS NGD Water Network Collection, there are multiple feature types that contain 3D geometry. We are aware of an issue where 3D geometry is not being supplied in the GeoPackage format. This issue impacts the following feature types: Connecting Link, Connecting Node, Ferry Link, Ferry Node, Path Link, Path Node, Road Link, Road Node, Water Link and Water Node.<br><br>Customers taking CSV format will not be affected. </td><td>26/11/2024</td><td><p></p><p>This issue was resolved on 26 November 2024. <br><br><strong>To receive updated data:</strong></p><ul><li><strong>Customers who have only ordered once:</strong> Customers will need to re-order to receive the corrected data.</li><li><strong>Monthly Update Customers:</strong> 01 December monthly updates with corrected data will be supplied as normal.</li><li><strong>Annual Update Customers:</strong> 01 January annual updates with corrected data will be supplied as normal.</li></ul></td></tr><tr><td>Topographic features missing from four feature types</td><td><p>From 26 September 2024 to 31 October 2024, an issue affected the following four OS NGD feature types, causing features to be missing from the data:</p><ul><li>OS NGD Building Part Feature Type: ~80 000 features are missing from data schema v2.0 compared to data schema v1.0.</li><li>OS NGD Land Feature Type: ~38 000 features are missing from data schema v3.0 compared to data schema v2.0.</li><li>OS NGD Water and OS NGD Structure Feature Types: ~100 features are missing in total across both feature types from data schema v3.0 compared to data schema v2.0.</li></ul><p>For example, where an affected Building feature should be visible, a blank area will instead be seen, creating a ‘gap’: </p><p></p><p><img src="https://170091638-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0pZjHxkAvY7Mn6TqFBMD%2Fuploads%2FEYRDCLPa7z6eAWSKIRW4%2Fimage.png?alt=media&#x26;token=bbac3324-8e2b-4c2c-a40d-a1f1eb9ac951" alt="Example image showing gaps in the OS NGD Building Part Feature Type data caused by a recent issue."></p></td><td>31/10/2024</td><td><p></p><p>This issue was resolved on 31 October 2024. Any data ordered or provided after this date will include the fixed data.</p><p><br>Please note, we advise against using counts from the four aforementioned affected OS NGD feature type datasets when taking historic snapshots of data between 26 September 2024 and 31 October 2024 as the counts may not be accurate due to the missing topographic features.</p></td></tr></tbody></table>
{% endtab %}

{% tab title="Address Theme" %}

<table data-full-width="true"><thead><tr><th width="182.77777099609375">Data Issue Name</th><th width="254.7779541015625">Original Description for Data Issue </th><th>Data Issue Resolution Date</th><th>Resolution Message</th></tr></thead><tbody><tr><td>Incorrect GSS code values for Barnsley and Sheffield</td><td>The GSS codes for Sheffield and Barnsley have only been updated in OS NGD Address GB Collection features that have received change-only updates (COUs) since 01/04/2025. Features in Sheffield or Barnsley that have not received COU since this date will display the previous (incorrect) GSS code.</td><td>24/06/2025</td><td>We are pleased to inform you that the fix for GSS codes affecting the OS NGD Address GB Collection was made available to customers on Tuesday 24/06/2025.  </td></tr></tbody></table>
{% endtab %}

{% tab title="Land Theme" %}

<table data-full-width="true"><thead><tr><th>Data Issue Name</th><th>Original Description for Data Issue</th><th width="134">Resolution Date</th><th>Resolution Message</th></tr></thead><tbody><tr><td>Site count discrepancies for some Land features</td><td>In a small number of instances, the Containing Site Count attribute presents the wrong value in Land features. This error only impacts 0.7% of Land features, and we expect it to be fixed by early October 2024.</td><td>12/10/2024</td><td>This issue was resolved on 12 October 2024. Any data ordered or provided after this date will include the fixed data.</td></tr></tbody></table>
{% endtab %}

{% tab title="Land Use Theme" %}

<table data-full-width="true"><thead><tr><th width="145.888916015625">Data Issue Name</th><th width="163.11126708984375">Original Description for Data Issue</th><th>Data Issue Resolution Date</th><th>Resolution Message</th><th data-hidden></th></tr></thead><tbody><tr><td>Uppercase and lowercase variations of two description values in Site Feature Type data schema v1.2</td><td>Two <a href="../../data-structure/land-use/land-use-features/site#description">description values</a> in data schema v1.2 of the <a href="../data-structure/land-use/land-use-features/site">Site Feature Type</a> contain duplicates with uppercase and lowercase variations. </td><td>25 September 2024 </td><td><p>Data schema v1.0 of Site was launched incorrectly with two description values that did not align with OS casing standards, and on 25 September 2024 the data and related code list were updated to fix this issue. </p><p></p><p>The two affected values are:</p><ul><li>Education Support Site</li><li>Public Waste Disposal Site</li></ul><p>The OS NGD access services of OS NGD API – Features and OS Select+Build validate against the data schema, meaning both versions of the description values must be retained to facilitate filtering.</p><p></p><p>The lowercase values (i.e. Education Support <strong>site</strong> and Public Waste Disposal <strong>site</strong>) should be used to filter and retrieve historical features (before 25/09/24), while the uppercase values (i.e. Education Support <strong>Site</strong> and Public Waste Disposal <strong>Site</strong>) should be used for records after this date. </p><p></p><p>This issue only affects data schema version 1.2 of Site; data schema v2.0 of Site was launched with the casing standards consistently applied.</p></td><td></td></tr></tbody></table>
{% endtab %}

{% tab title="Transport Theme" %}

<table data-full-width="true"><thead><tr><th width="263">Data Issue Name</th><th width="312">Original Description for Data Issue</th><th width="135.60009765625">Resolution Date</th><th>Resolution Message</th></tr></thead><tbody><tr><td>Duplicate Street Light features</td><td>There are around 84 000 Street Light features that are duplicated in Milton Keynes, Bedford and surrounding areas. This means that in this area, each street Light geometry is replicated twice; however, each geometry will still have its own unique OSID. </td><td>03/04/2025</td><td>This issue was resolved on 03 April 2025. Customers who take monthly updates will see this fix in the next update on 01 May 2025.</td></tr><tr><td>Incorrect Street Light coverage values on Road Links</td><td><p>We are aware of an issue that has caused a small number of incorrect values for Street Light coverage attribution on Road Links. Impacted Road Links will have a Presence Of Street Light Coverage attribute value that does not align with the evidence of street light presence in the Street Light Feature Type. </p><p></p><p>For example, a Road Link that has Street Lights features along it may have a coverage value of 'Fully Unlit' when it does in fact have Street Light features alongside it. </p><p></p><p>This issue affects approximately 0.45% of Road Links. </p></td><td>03/04/2025</td><td>This issue was resolved on 03 April 2025. Customers who take monthly updates will see this fix in the next update on 01 May 2025.</td></tr><tr><td>Incorrect speed values</td><td>Speed data is supplied quarterly from our third-party supplier. We have identified an issue in which OS have not correctly processed this data. This has resulted in possible incorrect values in the Average and Indicative Speed Feature Type.</td><td>25/07/2024</td><td>This issue was resolved on 25 July 2024. Any data ordered or provided after this date will include the fixed data.</td></tr><tr><td>Welsh speed limit changes</td><td>On 17 September 2023, default 20 mph speed limits were introduced across Wales. We are aware that these changes are not yet reflected in the Average and Indicative Speed Feature Type. Speed limit data is supplied by our third-party supplier quarterly. The most recent supply occurred before the Welsh speed limit changes took place and therefore will not be reflected in the OS NGD until the next supply. We expect the updated Welsh speed limits to be in NGD from December 2023.</td><td>13/12/2023</td><td>This issue was resolved on 13 December 2023. Any data ordered or provided after this date will include updated Welsh speed limit data.</td></tr><tr><td>Incorrect speed values</td><td>In the Average and Indicative Speed Feature Type, the indicative speed value for individual Road Links can be inferred by Ordnance Survey. We are aware that in certain instances some of these indicative speed values are incorrect. We are working to resolve this issue and have an approximate implementation date of the start of July 2023. This issue impacts just over 2% (174 000) of the total Road Links in the Average and Indicative Speed Feature Type.</td><td>02/07/2023</td><td>This issue was resolved on 02 July 2023. Any data ordered or provided after this date will include the fixed data.</td></tr></tbody></table>
{% endtab %}
{% endtabs %}