PostcodeType¶
S small user, L large user
NRS data dictionary (extracted; reviewed (AI-assisted review, 2026-10-02, record))
| Dictionary table | Type | Range | Description |
|---|---|---|---|
sspl (SSPL Data Dictionary 2026-2.docx) |
Char(1) | S or L | Small or Large User postcode indicator. |
| Table | Type | Nullable | Category | In the CSV export | SQL Server type |
|---|---|---|---|---|---|
main table (postcode_simd, SSPL) |
string | no | NRS Scottish Statistics Postcode Lookup field | yes | nvarchar(200) |
Provenance in the main table (postcode_simd, SSPL)¶
Where it comes from
| Input | Field | Condition | Reaches the row by |
|---|---|---|---|
SSPL/sspl-2026-2/SingleRecord.csv (pinned, SHA256 a6b23a9abfbd…) |
PostcodeType |
the row itself |
Scope: the row itself.
What was done to it: copied. Copied as text from the NRS Scottish Statistics Postcode Lookup, unchanged. (code: simd_ingest/core/sspl.py: build_latest_index)
How it is checked (what each check tests; whether a build passed it is in that build's manifest.json["checks"])
sspl.schema: the SSPL file's header is exactly the reviewed header, in orderreadback.main.index_columns: the saved file's NRS columns equal the source, re-read
Why: sspl-main-table, sspl-allocation-is-part-of-the-contract, two-nrs-cuts