About this atlas

Why this exists

Northern Virginia's jurisdictions plan for floods, heat, and storms with data scattered across a dozen federal portals. This atlas puts the region's hazard, vulnerability, and demographic record on one map, so a planner, an emergency manager, or a resident can answer a concrete question in minutes: where does water go, who gets hottest, what has storm damage cost, and who has the least capacity to cope.

Click any census tract and the atlas returns one combined readout: social vulnerability, the demographic flags that matter in an emergency, and the tract's hazard exposure. That cross-layer view, not any single dataset, is the point.

What each layer is for

Flooding

FEMA flood zones. Check any parcel or corridor against the regulatory floodplain before you zone it, buy it, or build on it.
Sea level rise scenarios. See which shoreline blocks stop draining as the tidal Potomac rises, and set setbacks and outfall designs before the water arrives.
Projected inland flood exposure. Compare how often each tract will see two-inch rain days by mid-century, and size culverts and detention where the increase is steepest.

Extreme heat

Observed urban heat. Find the Arlington blocks that ran hottest on a July afternoon, and target tree canopy and cooling centers block by block.
Projected extreme heat days. Overlay projected days at or above 95 °F on the SVI to find neighborhoods that are both hot and vulnerable, and put cooling investment there first.
Impervious surface. Spot the tracts where pavement drives both heat and runoff, and write redevelopment standards that pay down both risks at once.

Severe weather

Historical storm events. Filter 77 years of tornado, hail, wind, and flood reports by type and decade to brief responders on what actually hits each corridor.
Storm damage intensity. Rank jurisdictions by inflation-adjusted storm losses to argue mitigation budgets with evidence instead of anecdotes.

People and vulnerability

Social Vulnerability Index. Layer any hazard over the SVI to see who has the least capacity to prepare and recover, then aim outreach there first.
Demographic exposure. Switch the lens to seniors, young children, poverty, or car-free households, and plan evacuation and shelter capacity around the people who actually live there.

Data sources and credits

Every layer comes from a federal public-domain source or an attribution-only open source, snapshotted into this atlas's own files. Nothing here hot-links a government server at view time.

DatasetPublisherUsed forLicense / credit
National Flood Hazard Layer (snapshot)FEMAFlood zone layer, tract SFHA sharesU.S. Government work. Credit: FEMA. Loudoun County polygons come from the county's published regulatory floodplain service (major/minor floodplain), used because FEMA's export service would not deliver Loudoun; credit Loudoun County GIS.
Sea Level Rise viewer vectors, VA Northern regionNOAA Office for Coastal Management, Digital Coast+1/+2/+3 ft inundation scenariosU.S. Government work. Credit: NOAA OCM.
CMRA Screening Data (tract summaries)Interagency (resilience.climate.gov / USGCRP)Projected heat days, 2-inch rain daysU.S. Government work. Credit: CMRA.
Urban Heat Watch, Arlington VA, July 15 2021NOAA NIHHIS + CAPA Strategies (VFIC cohort)Observed heat traverse pointsPublic campaign data. Credit: NIHHIS / CAPA Strategies. Arlington is the NoVA locality with a campaign; Fairfax and Alexandria have none to date.
Storm Events Database, 1950–2026NOAA NCEIEvent points, damage choropleth, loss modelU.S. Government work. Credit: NOAA NCEI.
Social Vulnerability Index 2022CDC / ATSDRSVI layer, readout, equity weightingPublic domain. Credit: CDC/ATSDR.
TIGER/Line cartographic boundaries 2024U.S. Census BureauTracts, county, place outlinesPublic domain. Credit: U.S. Census Bureau.
ACS 5-year estimates 2018–2022U.S. Census BureauDemographic layer, exposure modelPublic domain. Credit: U.S. Census Bureau.
NLCD 2021 impervious surfaceUSGS / MRLCImpervious layerPublic domain. Credit: USGS/MRLC.
GlobalMLBuildingFootprints (2026-07-24 release)Microsoft (Bing Maps)Building footprints layer, 2D and 3D views, ML height estimatesCDLA Permissive 2.0. Credit: Microsoft GlobalMLBuildingFootprints. Heights are model estimates from imagery, not survey data.
Protomaps basemap (build 2026-07-23)Protomaps, from OpenStreetMapBasemap ("Streets")Open style; data ODbL. © OpenStreetMap contributors.
World Imagery tile service (view-time)EsriOptional "Satellite" basemapTiles © Esri — Source: Esri, Maxar, Earthstar Geographics, and the GIS User Community. Streamed at view time, not snapshotted; the only layer that needs the network.
CPI-U (CPIAUCSL)U.S. BLS via FREDInflation adjustment of storm damagesPublic data. Credit: BLS / FRED.

Excluded by license: Virginia's statewide Fathom flood model (state sublicense only), First Street / Risk Factor (proprietary), Esri-hosted basemaps, and Google Maps data.

Methodology & assumptions (mitigation analytics)

The analytics panel and the companion workbook (analytics/loss_model.xlsx) price mitigation with public, citable methods. Every number they show is illustrative, built for ranking places and hazards, not for appraising a specific project.

Storm Events undercounts small losses and geocodes damage to the reporting jurisdiction, so treat jurisdiction totals as floors. Commission a project-level FEMA BCA before committing funds.

Geographic scope

The beta covers the Northern Virginia Regional Commission core: Arlington, Fairfax, Loudoun, and Prince William counties, the cities of Alexandria, Fairfax, Falls Church, Manassas, and Manassas Park, and the incorporated towns within those counties. The pipeline clips to a single list of FIPS codes in config.py; edit that list and re-run to cover more of Virginia.

Basemap data © OpenStreetMap contributors.