No planner-style optimism
The public pages keep departures fixed, transfers capped, and uncertainty visible. The point is comparability, not exhaustive trip search.
Copenhagen mobility resilience
One public surface for atlas, operations, benchmark, and research review.
This site packages the project as a coherent product rather than a pile of research artifacts. Use the atlas to inspect spatial resilience, the operations page to review risk-informed intervention choices, the benchmark to compare routing assumptions, and the research review to understand structural fragility and reliability evidence.
How to read the site
- Start with the atlas if you want to see where the network remains useful under constrained transfer budgets.
- Use the operations page when you need a concrete recommendation for where limited support interventions should go first.
- Use the benchmark page when you need schedule, snapshot, and robust assumptions on the same candidate slice.
- Open the research review when you need the structural and operational evidence behind the public-facing story.
Mobility resilience atlas
Inspect catchments, municipality ranking, and reachable campuses, hospitals, and job hubs under fixed departure slices.
Open atlas Applied AIOperations planner
Review a risk-informed intervention plan that allocates a fixed budget across vulnerable catchments.
Open operations view Operational comparisonBenchmark dashboard
Compare schedule-only, realtime-snapshot, and robust assumptions on a single decision-facing benchmark slice.
Open benchmark Research reviewResults dashboard
Trace the line from graph structure and failure sensitivity to line reliability, risk modeling, and route trade-offs.
Open research reviewFrom risk signal to action
The operations page converts predicted missed-connection exposure into a concrete intervention shortlist under a fixed budget.
Cheap to publish, easy to audit
Static pages and precomputed bundles keep the product reproducible and easy to inspect without turning it into a heavy application stack.
Useful for both demos and scrutiny
The visual layer is intentionally polished, but every page is still anchored to explicit assumptions, generated artifacts, and inspectable inputs.