One corridor, four ways to see it.
A single "here's the route" map would have been a missed opportunity. Instead the corridor is split into four map systems, each placed where it does the most good — orient a first-time visitor, walk them through the stakes, help a landowner check their own address, and document the living systems in the path. All four share one rendering engine and one set of data files; only the framing changes.
The overview map
Homepage · orient & alarmHigh on the homepage, full-bleed, interactive — not a button. In one glance you see the proposed corridor laid over the karst and trout-stream layers, so the argument lands before anyone reads a word. Two calls to action lead deeper: walk the full corridor, or check your own land.
A lazy-loaded <iframe> holding a standalone MapLibre page, reused verbatim from the same map component that appears on other pages. Layers load as static GeoJSON from the site root; the basemap is CARTO Positron with no key. Because it's an iframe, the heavy WebGL map never blocks the homepage's first paint.
The corridor storyscroll
Dedicated page · walk the stakes"Walk the line." The map pins to the screen and, as you scroll, flies segment by segment down the corridor while narrative cards name a real place, a sourced impact, and who it affects. It turns 140 abstract miles into a guided tour — the immersive counter-argument to the developer's tidy line.
An IntersectionObserver watches the narrative cards; as each scrolls into the middle band of the viewport it fires map.flyTo() to that segment's center and zoom. No scroll library, no framework — a few dozen lines of vanilla JavaScript over the MapLibre instance. The scroll narrative doubles as the accessible text fallback for anyone the WebGL map doesn't reach.
The address-search explore tool
Landowners page · make it personalA landowner's first question is "is my land near this?" This tool answers it: type a town or address, the map flies there and drops a pin, and toggle chips let you switch route configurations and impact layers on and off. It's the conversion engine — the moment a worried neighbor becomes an engaged one.
Geocoding runs entirely client-side against OpenStreetMap's free Nominatim service — nothing the visitor types is ever sent to us or stored. That's a deliberate privacy and legal-lane choice: the only path that captures data is the separate landowner-support form. Honest framing is baked into the UI: "approximate, proposed route — for orientation only."
The living-systems map
Resource page · document the pathThe corridor doesn't just cross land — it crosses a flyway. This map layers thousands of research-grade bird observations as a heat surface, public birding hotspots, a federal bumble-bee zone, and mussel-rich watersheds, with a dropdown to isolate a single species. It's the ecological record, built to hand to regulators.
Bird points are binned to a ~2 km grid — counts only, no precise coordinates — so sensitive species (a threatened warbler, say) can never be located by someone with bad intent. A match expression recolors route layers by voltage config; the species dropdown swaps the density source between an all-birds layer and a per-species one. Currently in final integration, published to a preview URL.