Displacement Dashboard annual update guide

This guide is for TOD Office staff. One person can complete the annual refresh in about an hour. No vendor involvement is needed and no software subscription beyond the Council's ArcGIS Online organization is required.

Receive the analysis outputs

The Analysis Team delivers the four CSV files below, aggregated and de-identified, one row per station area per year.

Drop them into the inputs folder

Replace the files in data/inputs. Keep the file names and column names unchanged.

Run the update

Run python data/update.py. The script validates the files, aggregates corridors and the region, and rebuilds the published data.

Publish and check

Publish the refreshed layers to ArcGIS Online (or copy the web folder to the Council web server), then run the checklist below.

Input files and their columns

File	One row per	Required columns
`station_flows.csv`	station area and year	station_id, corridor_id, year, phase, households, in_total, out_total, in_low, out_low, in_middle, out_middle, in_high, out_high, in and out by race and ethnicity group, displacement_index
`base_mobility.csv`	year, dimension and group	year, dimension (Income or Race or ethnicity), group, move_rate
`project_phases.csv`	corridor and year	corridor_id, year, phase (Pre-development, Planning, Construction, Operation)
`corridors.geojson`, `stations.geojson`, `control_corridors.geojson`	feature	id, name, mode, status; station features also carry corridor and seq. Only change these when a corridor or station is added.

What the update script checks before it publishes

Every required column is present and every year from the first to the last is covered with no gaps.
Every station_id in the flows file exists in stations.geojson, and every corridor_id in the phases file exists in the corridor files.
Moves in and out are whole numbers, households are positive, and the displacement index is within the expected range.
The script stops with a plain-language message if a check fails; nothing is published until the file is corrected.

Post-publish checklist

Open the dashboard and move the year slider to the new year: the region cards and the map colors change. Pass when the newest year shows values.
Click one corridor and one station area: the charts extend to the new year and the takeaway sentence names the new year where relevant.
Open the Data table view and confirm the corridor count matches the corridor files.
Open the one-pager: the headline figures and the peak year update automatically.
Run the accessibility quick check (keyboard tab through the filters, screen reader on the data table) if the layout changed.

Production hosting on ArcGIS Online

In production the same CSV and GeoJSON files are the sources for hosted feature layers in the Council's ArcGIS Online organization. The annual refresh overwrites those layers from the files (ArcGIS Online "Update data" or a short ArcGIS Python API script that the Council owns), and the Experience Builder application, the Dashboards widgets and the StoryMap read from them with no rebuild. The Council owns every item, group and script; contractor access is removed at handoff.

Displacement Dashboard: annual update guide

Input files and their columns

What the update script checks before it publishes

Post-publish checklist

Production hosting on ArcGIS Online