Resilience Atlas
A map-first investigation connecting climate, infrastructure, energy, and neighborhood vulnerability across New York City.
Overview
Climate risks overlap, but the evidence used to understand them often lives in separate datasets, tools, and institutional contexts.
Our team created Resilience Atlas to explore how public climate and infrastructure data could be connected and made easier to investigate across all five boroughs.
- Context
- QCC Green Energy Program · Team investigation
- Year
- 2026
- Role
- Problem framing, analytical structure, product experience, and public presentation
- Boundary
- Public-data research prototype, not a real-time operational tool
The challenge
Flood exposure, extreme heat, infrastructure, neighborhood vulnerability, and service demand interact, but the data describing them is usually reviewed separately.
When those relationships stay fragmented, teams spend more time reconciling information and less time understanding what deserves attention.
Shared exploration
The Progressive Web Application gives the team and its audience one visual environment for exploring locations, comparing risks, and asking more specific questions.
Shared understanding
The Hex dashboard translates the analytical record into a faster stakeholder view while preserving the path back to the underlying evidence.
What we learned
- Climate risk does not arrive one hazard at a time; flood, heat, energy, and vulnerability compound.
- Public datasets can reveal conditions that deserve deeper investigation without supporting definitive asset-level claims.
- The difficult work is connecting evidence across silos so people can see relationships and ask better questions.
Evidence boundary
My contribution
Resilience Atlas was a team effort. I led the integration of the project’s problem framing, analytical structure, product experience, and public presentation.
I translated our research into a map-first application, developed the Hex dashboard, connected the analytical and interface layers, and established the project’s public-data boundaries.