Skip to main content
Warning This document has not been updated for a while now. It may be out of date.
Last updated: 6 Oct 2022

Incorrect postcode data

We get our postcode data from Locations API, which uses OS Places API (Ordnance Survey) under the hood. Locations API postcodes keep themselves up to date automatically and should never be more than about a week out of date.

In case the data is incorrect, a first step would be checking the Locations API result with the OS Places API result.

gds govuk connect --environment integration app-console locations-api
# The OS Places API response
token_manager =
response = HTTParty.get(
    query: { postcode: "E18QS", output_srs: "WGS84", "dataset": "DPA,LPI" },
    headers: { "Authorization": "Bearer #{token_manager.access_token}" },

# The information we currently have in Locations API
Postcode.find_by(postcode: "E18QS").results

If the results are not the same (especially the Local Custodian Code), then either the user happens to have looked up the postcode in the exact week where it has been updated by OS Places API but we haven’t updated our cache yet, or - more likely - our mechanism for self-updating postcodes has broken, and requires further investigation.

This is how you can manually force Locations API to update its cache for a given postcode:

token_manager ="E18QS")

# check if the record was updated
Postcode.find_by(postcode: "E18QS").updated_at