simd2012_uw_scotland_vigintile

Scottish Government unweighted vigintile; 1 = most deprived

Table	Type	Nullable	Category	In the CSV export	SQL Server type
history table (postcode_simd_history, SPD)	int8	no	Scottish Government SIMD	yes	tinyint
main table (postcode_simd, SSPL)	int8	no	Scottish Government SIMD	yes	tinyint

Provenance (the same in both tables)

Each table runs its own copy of the table-level checks, named .history. and .main..

Where it comes from

Input	Field	Condition	Reaches the row by
data.gov.uk/SG_SIMD_2012/SG_SIMD_2012.dbf (pinned, SHA256 4dc58c30c7d0…)	vigintile		DataZone2001Code = datazone

Scope: the row itself.

What was done to it: copied. The Scottish Government's unweighted band, copied as published, 1 most deprived. (code: simd_ingest/core/govscot.py: read_gov_edition)

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

• source.hash.data.gov.uk/SG_SIMD_2012/SG_SIMD_2012.dbf: the pinned file's SHA256 equals the registry's: the bytes are exactly the ones reviewed
• govscot.2012.columns_present: every declared shapefile column is in the file
• govscot.2012.key_unique: each data zone appears once in the shapefile table
• join.<table>.gov.2012.every_record_matched: every record found its data zone in the edition: no empty cell
• readback.<table>.attached_values: every attached value in the saved file is looked up again from the sources and equal
• govscot.2012.uw_scotland_vigintile.range: every unweighted band is within its range
• govscot.2012.uw_scotland_vigintile.monotone: the unweighted band never falls as the rank rises
• join.<table>.simd2012_uw_scotland_vigintile.range: every joined band is within its range

Why: government-bands-from-shapefile-tables, bands-are-looked-up, band-column-names-state-weighting