Repository navigation
6.1.0 built from NRS 2026/1 (HEAL-Scot)
Postcode-SIMD reference tables 6.1.0, built from the NRS 2026/1 postcode releases. This is for HEAL-Scot, whose postcodes DataLoch links with SPD and SSPL 2026/1.
This is not the current release. The current release is 6.1.0, built from NRS 2026/2. Use this one only when your data were linked with NRS 2026/1.
What differs from 6.1.0
- The registry pins SPD 2026/1 and SSPL 2026/1, with their SHA256s.
- NRS 2026/1 names the Scottish Parliament fields with
2021, not2026. These are different boundaries, so the fields keep the names NRS publishes. - The schemas have their own names,
postcode_simd_wide_v5_nrs2026_1(history table, 247,261 rows) andpostcode_simd_sspl_v5_nrs2026_1(main table, 229,708 rows). A loaded table can't be mistaken for a 2026/2 one. - A new build check: every data zone of every SIMD edition must have at least one postcode in the history table.
- The build writes to
results_nrs_2026_1/, throughconfig/workflow_nrs_2026_1.yaml.
Checks. The build passed 1,866 checks and the audit passed 1,178. 478 tests passed, plus 457 that read the built tables. The SQL Server import passed 10 of 10. Of the 360 ground-truth postcodes, 359 hold. The other, EH12 9ND, was introduced after 2026/1.
Know before you link. In 2026/1, NRS swapped the A and B parts of AB31 5AS, AB54 7NS, FK14 7JX and KA6 6EY in place. In 2026/2 NRS replaced that with a deletion on 18 February 2026 and new records. So the same postcode on the same date can give a different data zone in the two releases.
No tables are attached. NRS files are cited, not redistributed. To build the tables, download SPD and SSPL 2026/1 from NRS into manual_data/, then run the build with config/workflow_nrs_2026_1.yaml. The build stops if any file differs from its pinned hash.