Maintained geographic data.
One engine. Multiple surfaces.
Geographic query engine with source-backed datasets and versioned packs.
Choose a surface.
The mode ladder is simple: start in Explore when you need orientation, move to Ops when the question is about what is happening now and over the last few days, move to Research when you want a bounded corpus and a longer analytical thread, and use Agents when you want the same pack layer in code.
Open the map
Ask a question, inspect the map, and follow the datasets behind the answer.
Open Explore › OpsWatch live signals
Watch live collectors, current snapshots, and recent-history reports over the same maintained data layer.
Open Ops › ResearchBuild a corpus
Load a bounded corpus, keep the work, and ask cross-domain questions across released data history.
Open Research › AgentsConnect an agent
Call the same dataset layer through a hosted MCP server and HTTP API.
Read the docs ›From real queries
The clearest hot zones sit in the more urbanized eastern and central portions of Fairfax County, while the western side stays cooler where vegetation cover is stronger and development density is lower. Heat patterns are shaped by several land-cover and built-environment factors, not a single driver.
Immediate shock (2004–2005): electricity access dropped 4.2 points, industrial CO2 intensity collapsed 76%, unemployment jumped 2.6 points, industrial production growth halved. National-level recovery was largely complete within two to three years.
Open-core engine. Maintained pack layer.
The engine and schemas are open source. What you pay for is the maintained path: processed datasets, source-backed releases, versioned packs, freshness, packaging, and support. That maintained layer keeps every surface aligned on one published truth.