Skip to content

simd2004_employment_domain_vigintile

Scottish Government SIMD 2004 employment domain vigintile, unweighted, 1 = most deprived; copied exactly as published on statistics.gov.scot, never derived; the publisher places some tied zones in adjacent bands

What the employment domain measures (indicators in the Scottish Government's SIMD 2020v2 glossary; earlier editions' indicators differ in detail):

  • Percentage of working age people who are employment deprived (EmpRate, percentage; SIMD 2020v2 glossary: a 2020v2 example, not verified for this edition)
  • Number of working age people who are employment deprived (EmpNumDep, count; SIMD 2020v2 glossary: a 2020v2 example, not verified for this edition)
Table Type Nullable Category In the CSV export SQL Server type
history table (postcode_simd_history, SPD) int8 no Scottish Government published domain band yes tinyint
main table (postcode_simd, SSPL) int8 no Scottish Government published domain band 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
statistics.gov.scot/simd_historical_2004_2012.csv (pinned, SHA256 d9745d9d7763…) Value SIMD Domain = Employment, Measurement = Vigintile, DateCode = 2004 DataZone2001Code = FeatureCode
data.gov.uk/SG_SIMD_2004/SG_SIMD_2004.dbf (pinned, SHA256 8a17b1aa0df6…) emprank the rank the published rank must equal, or differ from as declared DataZone2001Code = datazone

Scope: the row itself.

What was done to it: copied (gated). The Scottish Government's published band, copied, never derived; admitted only where the published rank is the shapefile's, a half the dataset rounds up allowed. (code: simd_ingest/core/govscot.py: read_published_bands)

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

  • source.hash.statistics.gov.scot/simd_historical_2004_2012.csv: the pinned file's SHA256 equals the registry's: the bytes are exactly the ones reviewed
  • govscot.2004.bands.years: the band file holds exactly the years the registry declares for it
  • govscot.2004.bands.employment.zones: every zone of the edition is published once for the domain
  • govscot.2004.bands.employment.ranks_agree: every published rank equals the shapefile rank, or differs only in a declared way
  • join.<table>.gov.2004.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.2004.bands.employment.vigintile.whole: every published band is a whole number
  • govscot.2004.bands.employment.vigintile.range: every published band is within its range
  • govscot.2004.bands.employment.vigintile.monotone: the published band never falls as the published rank rises (a split tie is allowed)
  • join.<table>.simd2004_employment_domain_vigintile.range: every joined band is within its range

Why: simd-domain-bands, bands-are-looked-up