Build a Disaster Declaration Administrative Frequency Auditor
Correlate municipal asset portfolios against OpenFEMA disaster declarations to measure regional declaration frequency. Quantify historical administrative disaster frequencies to guide municipal infrastructure adaptation grant planning and funding applications.
What you are building
The core problem, expected build, and operating context for this challenge.
Correlate municipal asset portfolios against OpenFEMA disaster declarations to measure regional declaration frequency. Quantify historical administrative disaster frequencies to guide municipal infrastructure adaptation grant planning and funding applications.
Municipal Adaptation Planner
Filter OpenFEMA DisasterDeclarationsSummaries by state, county, and incidentType 'Flood'.
Ingest municipal facility locations and match to county FIPS codes.
Calculate historical administrative declaration frequencies and mean intervals between declarations.
Produce a capital improvement grant prioritization list based on administrative declaration frequency.
Streamlit application displaying county administrative disaster timelines, declaration metrics, and facility grant priority tables.
Query OpenFEMA API endpoint /v2/DisasterDeclarationsSummaries with $filter or download historical CSV extract using $allrecords=true. Starter examples below are synthetic. They are not downloaded records.
FEMA OpenFEMA Queries OpenFEMA DisasterDeclarationsSummaries using $filter parameters state, incidentType, and declarationDate specified in OpenFEMA docs.
mastra-ai, requests, pandas. Mastra AI provides deterministic workflow orchestration and schema validation for API aggregation pipelines. Local or hosted LLM to generate narrative adaptation grant summaries based on historical administrative declaration counts.
Submit runnable source, pinned dependencies, setup commands, a working interface, example outputs, and a recorded end-to-end demo. Include tests and an action log.
Correctly formats OData query parameters including ISO-8601 timestamps.
Aggregates flood declarations per county over specified multi-decade windows.
Ranks public assets by county administrative disaster declaration counts for grant planning.
```json [ { "input": { "_record_type": "simplified synthetic app record", "county_fips": "12086", "state": "FL", "declarations": [ { "disasterNumber": 4001, "incidentType": "Flood", "declarationDate": "2015-01-01T00:00:00.000Z" }, { "disasterNumber": 4200, "incidentType": "Flood", "declarationDate": "2020-01-01T00:00:00.000Z" } ], "asset_count": 12 }, "expected_output": { "county_fips": "12086", "flood_declaration_count": 2, "mean_declaration_interval_years": 5, "grant_priority_level": "MODERATE_FREQUENCY" } }, { "input": { "_record_type": "simplified synthetic app record", "county_fips": "12001", "state": "FL", "declarations": [], "asset_count": 3 }, "expected_output": { "county_fips": "12001", "flood_declaration_count": 0, "mean_declaration_interval_years": null, "grant_priority_level": "LOW_FREQUENCY" } } ] ```
Does not calculate physical flood risk or provide engineering guarantees; outputs strictly reflect administrative grant declaration history for funding evaluation. Use mock external writes. Require human review before any real deployment.
Participation guide
Does not calculate physical flood risk or provide engineering guarantees; outputs strictly reflect administrative grant declaration history for funding evaluation. Use mock external writes and human review.
How work is evaluated
Correctly formats OData query parameters including ISO-8601 timestamps. Aggregates flood declarations per county over specified multi-decade windows. Ranks public assets by county administrative disaster declaration counts for grant planning.
Runnable source, pinned dependencies, setup commands, working interface, example outputs, recorded demo, tests, and action logs.
Challenge datasets
Public datasets, plus the private datasets you have access to.
How submissions are scored
These dimensions define what the evaluator checks and which criteria separate a passable run from a strong one.
Complete workflow
Filter OpenFEMA DisasterDeclarationsSummaries by state, county, and incidentType 'Flood'. Ingest municipal facility locations and match to county FIPS codes. Calculate historical administrative declaration frequencies and mean intervals between declarations. Produce a capital improvement grant prioritization list based on administrative declaration frequency.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Correctness and evidence
Correctly formats OData query parameters including ISO-8601 timestamps. Aggregates flood declarations per county over specified multi-decade windows. Ranks public assets by county administrative disaster declaration counts for grant planning.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Review interface
Streamlit application displaying county administrative disaster timelines, declaration metrics, and facility grant priority tables.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Safe execution
Does not calculate physical flood risk or provide engineering guarantees; outputs strictly reflect administrative grant declaration history for funding evaluation.
This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.
What you should walk away with
Filter OpenFEMA DisasterDeclarationsSummaries by state, county, and incidentType 'Flood'.
Ingest municipal facility locations and match to county FIPS codes.
Calculate historical administrative declaration frequencies and mean intervals between declarations.
Produce a capital improvement grant prioritization list based on administrative declaration frequency.
Reference links and supporting material
Query OpenFEMA API endpoint /v2/DisasterDeclarationsSummaries with $filter or download historical CSV extract using $allrecords=true. Supplied starter examples are synthetic, not source extracts.
Challenge setup
Configuration summary for this challenge.
Challenge input
Input details are not configured.
Mastra AI
TypeScript agent framework.
Evaluated output
No output checks are configured.
- Filter OpenFEMA DisasterDeclarationsSummaries by state, county, and incidentType 'Flood'. Ingest municipal...
- Correctly formats OData query parameters including ISO-8601 timestamps. Aggregates flood declarations per c...
- Streamlit application displaying county administrative disaster timelines, declaration metrics, and facilit...
- 2 public reference cases
- 2 configured tools
Summary shows the first task, up to three tools, and up to three evidence items. Open the technical recipe to view all configured items.
View technical recipe
Configured tools
- Mastra AI · Optional
- Mastra AI · Optional
Evaluation contract
- Complete workflow · Weight 40
- Correctness and evidence · Weight 30
- Review interface · Weight 20
- Safe execution · Weight 10
Reference cases
- 2 public reference cases
Workflow tasks
No workflow tasks are configured.
Recipe freeze marker
No recipe freeze time is recorded.