Build an OpenFEMA Administrative Flood Declaration Scorer
Correlate county-level OpenFEMA disaster declarations for inland flooding against croplands and agricultural soil maps. Track historical administrative declaration frequencies to construct targeted soil drainage and crop transition adaptation plans.
What you are building
The core problem, expected build, and operating context for this challenge.
Correlate county-level OpenFEMA disaster declarations for inland flooding against croplands and agricultural soil maps. Track historical administrative declaration frequencies to construct targeted soil drainage and crop transition adaptation plans.
Rural Agricultural Resilience Agent
Fetch OpenFEMA DisasterDeclarationsSummaries data using OData queries filtered for agricultural counties.
Calculate the historical count of administrative flood disaster declarations across specified periods.
Intersect declaration frequency scores with rural crop land cover classifications.
Generate regional adaptation action plans detailing cover cropping and retention pond allocations based on administrative declaration history.
Vue.js dashboard featuring county administrative declaration counts, historical timeframe slider controls, and adaptation plans.
Use OpenFEMA REST endpoints with $filter, $select, and $format=json parameters to retrieve administrative declaration data. Starter examples below are synthetic. They are not downloaded records.
FEMA OpenFEMA Employ OpenFEMA $filter by incidentType and state, utilizing $select for field reduction of administrative records.
crewai, httpx, pandas. CrewAI coordinates specialized agents for administrative data extraction, agronomy analysis, and adaptation plan drafting. Instruction-following LLM capable of multi-agent agricultural planning dialogue focused on administrative historical data.
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 builds OpenFEMA query with URL encoding and logical operators.
Computes administrative declaration event counts accurately from year spans.
Recommends specific soil mitigation measures for counties exceeding historical administrative declaration thresholds.
```json [ { "input": { "county_fips": "19153", "county_name": "Polk County, IA", "crop_type": "Corn/Soy", "declarations": [ { "disasterNumber": 1763, "incidentType": "Flood" }, { "disasterNumber": 1930, "incidentType": "Flood" }, { "disasterNumber": 4421, "incidentType": "Flood" } ] }, "expected_output": { "county_name": "Polk County, IA", "administrative_flood_count": 3, "adaptation_priority": "HIGH", "recommended_interventions": [ "EXPAND_WETLAND_BUFFER_STRIPS", "TRANSITION_DEPRESSIONAL_ACRES_TO_FORAGE" ], "record_type": "simplified synthetic app records, not complete official schema files" } }, { "input": { "county_fips": "19001", "county_name": "Adair County, IA", "crop_type": "Soybeans", "declarations": [] }, "expected_output": { "county_name": "Adair County, IA", "administrative_flood_count": 0, "adaptation_priority": "BASELINE", "recommended_interventions": [ "MAINTAIN_STANDARD_TILLAGE_MANAGEMENT" ], "record_type": "simplified synthetic app records, not complete official schema files" } } ] ```
Outputs are agronomic adaptation suggestions based purely on historical administrative records, not physical hazard recurrence probabilities. Use mock external writes. Require human review before any real deployment.
Participation guide
Outputs are agronomic adaptation suggestions based purely on historical administrative records, not physical hazard recurrence probabilities. Use mock external writes and human review.
How work is evaluated
Correctly builds OpenFEMA query with URL encoding and logical operators. Computes administrative declaration event counts accurately from year spans. Recommends specific soil mitigation measures for counties exceeding historical administrative declaration thresholds.
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
Fetch OpenFEMA DisasterDeclarationsSummaries data using OData queries filtered for agricultural counties. Calculate the historical count of administrative flood disaster declarations across specified periods. Intersect declaration frequency scores with rural crop land cover classifications. Generate regional adaptation action plans detailing cover cropping and retention pond allocations based on administrative declaration history.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Correctness and evidence
Correctly builds OpenFEMA query with URL encoding and logical operators. Computes administrative declaration event counts accurately from year spans. Recommends specific soil mitigation measures for counties exceeding historical administrative declaration thresholds.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Review interface
Vue.js dashboard featuring county administrative declaration counts, historical timeframe slider controls, and adaptation plans.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Safe execution
Outputs are agronomic adaptation suggestions based purely on historical administrative records, not physical hazard recurrence probabilities.
This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.
What you should walk away with
Fetch OpenFEMA DisasterDeclarationsSummaries data using OData queries filtered for agricultural counties.
Calculate the historical count of administrative flood disaster declarations across specified periods.
Intersect declaration frequency scores with rural crop land cover classifications.
Generate regional adaptation action plans detailing cover cropping and retention pond allocations based on administrative declaration history.
Reference links and supporting material
Use OpenFEMA REST endpoints with $filter, $select, and $format=json parameters to retrieve administrative declaration data. Supplied starter examples are synthetic, not source extracts.
Challenge setup
Configuration summary for this challenge.
Challenge input
Input details are not configured.
crewAI
Multi-agent orchestration framework
Evaluated output
No output checks are configured.
- Fetch OpenFEMA DisasterDeclarationsSummaries data using OData queries filtered for agricultural counties. C...
- Correctly builds OpenFEMA query with URL encoding and logical operators. Computes administrative declaratio...
- Vue.js dashboard featuring county administrative declaration counts, historical timeframe slider controls,...
- 2 public reference cases
- 1 configured tool
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
- crewAI · 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.