Skip to content

simd2009v2_rank

1 = most deprived; identical to the Scottish Government rank

Table Type Nullable Category In the CSV export SQL Server type
history table (postcode_simd_history, SPD) int16 no PHS SIMD, population-weighted yes smallint
main table (postcode_simd, SSPL) int16 no PHS SIMD, population-weighted yes smallint

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
PHS/simd2009v2_23062019.csv (pinned, SHA256 effa76a98982…) SIMD2009V2Rank DataZone2001Code = DataZone

Scope: the row itself.

What was done to it: copied. The SIMD rank as published, 1 most deprived. (code: simd_ingest/core/phs.py: canonicalise_phs)

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

  • source.hash.PHS/simd2009v2_23062019.csv: the pinned file's SHA256 equals the registry's: the bytes are exactly the ones reviewed
  • phs.2009v2.source.schema: the PHS file's header is the declared one
  • phs.2009v2.source.key_unique: each data zone appears once in the PHS file
  • cross.2009v2.same_zones: PHS and the Government publish the same data zones for the edition
  • join.<table>.phs.2009v2.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
  • phs.2009v2.source.rank_dense: the PHS ranks run 1 to the number of zones with no gap
  • cross.2009v2.rank_identical: PHS and the Government publish the same rank for every zone

Why: rank-direction-confirmed, trust-the-sources