Skip to content

Settlement2020Code

NRS data dictionary (extracted; reviewed (AI-assisted review, 2026-10-02, record))

Dictionary table Type Range Description
spd small user (spd-indexdatadictionary-2026-2.docx) Char(9) S20001538 to S20002051 A code that identifies a 2020 Settlement.
spd large user (spd-indexdatadictionary-2026-2.docx) Char(9) S20001538 to S20002051 A code that identifies a 2020 Settlement.
Table Type Nullable Category In the CSV export SQL Server type
history table (postcode_simd_history, SPD) string no NRS Scottish Postcode Directory field yes nvarchar(200)

Provenance in the history table (postcode_simd_history, SPD)

Where it comes from

Input Field Condition Reaches the row by
SPD/spd_postcodeindex_cut_26_2_csv/SmallUser.csv (pinned, SHA256 fc82f1091ac1…) Settlement2020Code records of the small-user file the row itself
SPD/spd_postcodeindex_cut_26_2_csv/LargeUser.csv (pinned, SHA256 dcb060cbce01…) Settlement2020Code records of the large-user file the row itself

Scope: the row itself.

What was done to it: copied. Copied as text from the NRS Scottish Postcode Directory, unchanged; the two files are stacked. (code: simd_ingest/core/spd.py: read_index_file, union_index)

How it is checked (what each check tests; whether a build passed it is in that build's manifest.json["checks"])

  • spd.small_user.schema: the SPD file's header is exactly the reviewed header, in order
  • spd.large_user.schema: the SPD file's header is exactly the reviewed header, in order
  • spd.columns: the two SPD files together carry the expected columns
  • readback.history.index_columns: the saved file's NRS columns equal the source, re-read

Why: spd-cut-edition, single-combined-output, record-key