Strongest Now
Disaster Coverage Leads
Earthquakes, storm tracks, tsunamis, volcanoes, tornadoes, and wildfires currently tell the clearest story for the public app and maintained-pack model.
Docs / Source Map
A coverage map of the
source families in play.
This page is the public-facing counterpart to the internal audits. It shows the major source families, what they cover, where the strongest maintained paths currently exist, and where the gaps still are.
How to read this
This is not meant to be a raw dump of every internal file or experimental input. It is a readable map of the source families DaedalMap currently works with, with emphasis on practical coverage, time range, and operational maturity.
Supporting Context
Demographic And Economic Layers
Population, census, FX, and country-level economic layers make the map more than a hazard viewer. They are part of the actual analytical value of the system.
Still Uneven
Freshness And Readiness Gaps
Not every family is equally current or equally release-ready. This page is supposed to make that visible instead of hiding it.
| Source Family | Primary Source | Coverage | Time Range | Live Source | Status | Notes |
|---|---|---|---|---|---|---|
| Earthquakes | USGS + NOAA NGDC | Global | 2150 BC to 2026 | Deployed | Strong | Live collector path is operational and this is one of the strongest maintained disaster packages. |
| Hurricanes / Storm Tracks | IBTrACS / NOAA | Global | 1842 to 2026 | Deployed | Strong | Track-oriented storm package with broad historical coverage and a clear path into hosted and local use. |
| Tsunamis | NOAA NGDC Tsunami Database | Global | 2000 BC to 2025 | Found / partial live path | Strong | Historical event coverage is strong and live collection exists, though freshness still matters. |
| Volcanoes | Smithsonian Global Volcanism Program | Global | Holocene to 2025 | Batch-first | Strong | One of the clearest long-history hazard packages in the system. |
| Wildfires | Global Fire Atlas + regional fire agencies | Global plus regional depth | 2002 to 2024 | Mixed regional paths | Strong but still maturing | Wildfires are progression-oriented and benefit from separate regional support such as USA and Canada fire data. |
| Tornadoes | NOAA Storm Events | Primarily USA | 1950 to 2025 | Batch-first | Good | Operationally useful with strong historical depth, but still more batch-driven than continuously live. |
| Floods | Dartmouth Flood Observatory | Global | 1985 to 2019 | Found, not fully deployed | Needs freshness work | Important coverage exists, but this is one of the clearest gaps between historical package quality and current freshness. |
| Landslides | NASA Global Landslide Catalog + merged sources | Global | 1760 to 2025 | Batch only | Not release-ready | Included in the program map, but still too sparse and uneven to be treated as a mature public disaster family. |
| Demographics | WorldPop + national statistics agencies | USA, EUR, AUS, global extensions | Varies by source | Mixed | Growing | Regional depth exists today, with broader pack-based demographic expansion still in progress. |
| Economic and development | Our World in Data + IMF + UN SDG | Global country-level | Long historical spans, source-dependent | Batch-first | Strong | Includes global financial, SDG, climate-economy, and factbook-style country packages. |
| Climate and weather | Open-Meteo + maintained weather feeds | Global | Live plus historical slices | Deployed | Operational | Weather is one of the clearest live-data paths in the runtime today. |
What people can infer from this
DaedalMap is already useful when the question is geographic, cross-domain, and source-aware. It is not trying to pretend every family is equally deep. The stronger the maintained coverage, the more confidently the system can answer.
What this page does not show
Internal helper sources, raw merge inputs, converter-only artifacts, and incomplete technical support layers are intentionally not treated here as public top-level source families.
Why this matters
People need a way to see what the system already covers without reading internal audit notes or reverse-engineering the repo layout. The public source map is where that story should live.