For Council TOD staff
Annual Update
This prototype illustrates the steps TOD staff would follow for an annual update.
Step 1
Drop the new Analysis outputs in a folder
Save the Analysis team’s yearly files into
data/incoming/2026/:station_area_metrics_2026.csv: one row per station areastation_areas_2026.geojson: half-mile buffers (only if stations changed)
Step 2
Run one documented script
$ python update_dashboard.py --year 2026The script merges the new year, recalculates corridor and region totals, applies the small-number suppression rule, and writes the files the dashboard reads.
Step 3
Read the automatic validation report
Validation report · 2026 · (mock)
Rows read ............... 83 station areas
Schema check ............ PASS 18 / 18 columns
Missing station IDs ..... WARN 1 (gold-helmo not in file)
Value ranges ............ PASS dpi 0–100, rent burden 0–100%
Suppression (<11 hh) ... 23 cells hidden
Year continuity ......... PASS 2006–2026
Step 4
Preview
Run
python update_dashboard.py --previewto open a local copy. Scrub to 2026 on the map and spot-check two or three station areas.Step 5
Publish
Copy the
dist/folder to the Council’s web host, or publish the updated layers to ArcGIS Online. The previous year stays archived for rollback.
Validate a sample file
Try the same checks the script runs. Use the built-in sample, which has a few deliberate problems, or pick your own CSV (it never leaves your browser).
Show sample file
station_id,corridor_id,year,phase,households,hh_in_lt50,hh_out_lt50,median_income_pct_ami,rent_burden_pct,dpi green-raymond,green,2026,operation,4210,182,205,84.2,47.5,61.3 green-snelling,green,2026,operation,3980,160,214,79.8,49.1,64.0 blue-lake,blue,2026,operation,5120,240,262,72.4,52.3,66.8 gold-sun-ray,gold,2026,operation,3305,9,141,63.0,44.0,52.1 orange-lake,orange,2026,operation,2875,130,151,70.1,46.2,58.9 a-grand,a,2026,opration,3720,120,118,101.5,41.0,49.2 c-plymouth,c,2026,operation,3010,151,170,58.6,104.0,57.7 xx-unknown,d,2026,operation,2600,98,120,66.0,45.0,55.0
No report yet. Run a validation to see results.
Data dictionary
| Field | Type | Description | Example |
|---|---|---|---|
station_id | string | Stable station-area identifier | green-raymond |
corridor_id | string | Transitway or control corridor identifier | green |
year | integer | Data year (2006 or later) | 2026 |
phase | enum | pre-development, planning, construction, operation, control | operation |
households | integer | Total households in the half-mile area | 4210 |
hh_in_lt50 … hh_in_gt120 | integer | Households moving in, by income band | 182 |
hh_out_lt50 … hh_out_gt120 | integer | Households moving out, by income band | 205 |
median_income_pct_ami | number | Median household income as % of AMI | 84.2 |
rent_burden_pct | number | % of renters paying over 30% of income | 47.5 |
dpi | number | Displacement Pressure Index, 0–100 | 61.3 |
Expected file schema
station_area_metrics_<year>.csv
station_id,corridor_id,year,phase,households,
hh_in_lt50,hh_in_50to80,hh_in_80to120,hh_in_gt120,
hh_out_lt50,hh_out_50to80,hh_out_80to120,hh_out_gt120,
median_income_pct_ami,rent_burden_pct,dpi
station_areas_<year>.geojson
FeatureCollection of Polygon features
properties: { station_id, corridor_id, name, buffer_miles: 0.5 }