NeverDigitised¶
small-user only
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(1) | Y or Null | Indicates whether a postcode boundary has been digitised. Royal Mail introduced a mix of small and large user postcodes prior to the 2007 Election. These postcodes were introduced for use in postal votes. As they were planned for an ‘administrative’ use, we could not digitise the small user postcodes as they had no distinctive geographical position. |
| Table | Type | Nullable | Category | In the CSV export | SQL Server type |
|---|---|---|---|---|---|
history table (postcode_simd_history, SPD) |
string | yes | 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…) |
NeverDigitised |
records of the small-user file; only the small-user file has it, so it is null for the other's records | 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 orderspd.large_user.schema: the SPD file's header is exactly the reviewed header, in orderspd.columns: the two SPD files together carry the expected columnsreadback.history.index_columns: the saved file's NRS columns equal the source, re-read