Version 0.1.0
The first tracked release brings the existing analysis and verification pages into one navigable review surface. It packages approved or explicitly declared snapshots for presentation; it does not change indicator methods or calculate new results.
| Page | What it says | Data in this release | Visualisation / interaction |
|---|---|---|---|
| Overview | Explains how the analysis surfaces fit together and where to go for each question. | No indicator-data change | Added Page guide, question routing, shared interaction rules, and this release tracker. |
| Parcel explorer | Compares eight supplied normalized indicators for Singapore and Tokyo parcels. | Packaged The two supplied parcel datasets are harmonized for browser use; source values and methods are unchanged. | Added Linked distributions, point/density relationship view, district ranking, and correlation matrix. |
| Subzone explorer | Reviews progress on Singapore's indicators on official URA subzones, with Punggol Digital District as the focal boundary and H3 as optional detail. | Packaged Verified cell and subzone evaluation of one review bundle plus explicitly declared sandbox fields; declared spatial supports decide what is mapped; no promotion occurs here. | Updated Subzone-first map frame with H3 drill-down and city context, PDD subzone context, ranked comparison, subzone bivariate view, and subzone correlation matrix. |
| Indicator verification Local only | Shows what has actually been verified, for which indicator and city, and what remains unresolved. | Updated Adds annual Sentinel-2 scene provenance and catalog reconciliation for Universal Greenspace NDVI alongside existing evidence. | Added Registry readiness matrix, raw-versus-analysed maps, and indicator-specific evidence panels. |
| Built-form verification | Reviews achieved GPR and building-footprint compactness across Singapore, Tokyo, and Vienna. | Packaged Existing approved GPR and recalculated compactness outputs; readiness gaps remain visible. | Added Three-city maps and resolution, threshold, boundary-support, and spatial-pattern diagnostics. |
- Record snapshot refreshes and city or indicator coverage changes here.
- Document new or revised visualisations page by page.
- Extend coverage only after method, data-readiness, and validation review.
H3 framework
Which tab answers which question
Rules the explorer tabs share
The explorer pages follow the same interaction contract, so a control learned on one page behaves the same way on the others. On the subzone explorer the analysed population is the set of official subzones; H3 cells appear only as optional detail inside one selected subzone.
The two verification tabs are review surfaces rather than filtering surfaces: they present fixed, pre-validated evidence panels, and the built-form tab adds a city selector.
Where the data comes from
src/data/parcel/snapshot.json.py from the two supplied parcel CSVs, harmonized into one browser payload.src/data/snapshot.zip.py, which runs the canonical cell and subzone evaluation preflight on one verified review bundle, joins the declared sandbox outputs, and records each metric's declared spatial supports.src/data/built-form.zip.py from existing sandbox outputs. It validates and packages; it does not recalculate.Snapshots are cached under src/.observablehq/cache/. The cache, dist/, and node_modules/ are generated and are not versioned. The parcel CSVs are not versioned in this repository; the loader looks for them under REGENCITY_PARCEL_DATA_DIR, then data/parcel_study/, then the sibling Regen_Parcel_Study/ directory. Method definitions, indicator specifications, and evaluation eligibility all remain upstream in the pipeline repository — see observable-framework/README.md for the publication boundary in full.