090°Données ouvertes
Jeux de données ouverts, entièrement documentés — interrogeables ici, et lisibles par n’importe quel LLM.
Les titres et les descriptions proviennent des sources de données, en anglais.
1 jeux de données
FEMA county disaster exposure (agent-curated)
Monthly county-level disaster-exposure intelligence from the keyless FEMA OpenFEMA DisasterDeclarationsSummaries v2 API (one row per designated area, no gazetteer needed — each area row carries its county FIPS). Trailing 60 complete calendar months, one row per (month, county_fips): distinct declaration counts by type (DR/EM/FM) and by assistance program (IA/PA/HM/IH), the shared 9-family incident taxonomy, the month's dominant family, max incident duration, look-ahead-free trailing-12-month recurrence features, and a documented 0-100 exposure_score (40% declaration-type weight + 20% program profile + 15% log-scaled duration + 25% recurrence) with within-month exposure_rank (1 = most exposed), exposure_tier e1..e4 quartiles, and a disaster_watch_flag. Finer-grained companion to the declaration-level dataset (same source, same taxonomy). Caveats: the score is a triage heuristic, not a damage estimate (the endpoint carries no obligation/cost figures); statewide ('000') designations are excluded from the county panel; per-area incident-type codes are not mapped; window edges carry shorter trailing lookbacks; tribal designations without county FIPS are excluded. Agent-curated: collection = keyless OpenFEMA API paged sweep; transformation = county resolution with fail-loud FIPS/identity gates + shared incident taxonomy + date arithmetic + recurrence features + documented scoring. FEMA records are U.S. federal government work under use-restricted terms (statistical research/reporting only) — commercial_use = unclear. Sample use: join exposure_score on (month_start, county_fips) to territory/order tables to model disaster-driven demand disruption and churn risk.
Une fois l’allocation gratuite du jour épuisée, les fonctions d’IA peuvent passer par votre propre compte fournisseur.
Conservée uniquement dans cet onglet (effacée à sa fermeture) et envoyée avec chaque requête d’IA. Nos serveurs l’utilisent pour cette requête et ne la stockent ni ne la journalisent jamais.