Skip to main content
Challenge

Build a County Disaster Declaration Adaptation Prioritizer

Aggregate county-level disaster declaration counts from OpenFEMA to prioritize regional adaptation grant proposals. Rank counties by administrative exposure to historical flood and severe storm events.

Data ScienceHosted by Vera
Challenge brief

What you are building

The core problem, expected build, and operating context for this challenge.

Aggregate county-level disaster declaration counts from OpenFEMA to prioritize regional adaptation grant proposals. Rank counties by administrative exposure to historical flood and severe storm events.

Regional Resilience Grant Coordinator

Query the OpenFEMA API for county-level disaster declaration records spanning the past two decades.

Group administrative records by disaster incident type to identify dominant hazard categories per county.

Ingest county demographic housing metrics to weight the base disaster frequency.

Rank county-level adaptation intervention priorities and generate draft grant allocation worksheets for human review.

Dashboard table with sortable county ranks, hazard tallies, and exportable CSV reports.

Query OpenFEMA endpoint v2/DisasterDeclarationsSummaries via REST API; test using bundled offline mock JSON responses. Starter examples below are synthetic. They are not downloaded records.

FEMA OpenFEMA Constructs OpenFEMA $filter queries with logical operators like ge on declarationDate and $select for specific fields.

agno, requests, pandas. Agno lightweight agents orchestrate data retrieval, statistical ranking, and narrative grant proposal drafting. Local or hosted LLM with fast structured function calling capabilities.

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 filters declarations by start date using OpenFEMA date formatting.

Ranks counties deterministically by historical incident frequency.

Produces a prioritized adaptation report with justification notes for human review.

```json [ { "input": { "county_id": "COUNTY-701", "county_fema_counts": { "Flood": 6, "Severe Storm": 8 }, "residential_units": 120000 }, "expected_output": { "county_id": "COUNTY-701", "total_incidents": 14, "priority_level": "TIER_1", "recommended_grant": "FLOOD_MITIGATION_ASSISTANCE", "record_type": "Simplified synthetic app record" } }, { "input": { "county_id": "COUNTY-702", "county_fema_counts": { "Flood": 0, "Severe Storm": 1 }, "residential_units": 45000 }, "expected_output": { "county_id": "COUNTY-702", "total_incidents": 1, "priority_level": "TIER_3", "recommended_grant": "STANDARD_PREPAREDNESS", "record_type": "Simplified synthetic app record" } } ] ```

Produces planning prioritization scores for human review; carries no statutory authority over actual federal grant distribution. Use mock external writes. Require human review before any real deployment.

Rules

Participation guide

Produces planning prioritization scores for human review; carries no statutory authority over actual federal grant distribution. Use mock external writes and human review.

Delivery guide

How work is evaluated

Evaluation

Correctly filters declarations by start date using OpenFEMA date formatting. Ranks counties deterministically by historical incident frequency. Produces a prioritized adaptation report with justification notes for human review.

Submission format

Runnable source, pinned dependencies, setup commands, working interface, example outputs, recorded demo, tests, and action logs.

Datasets

Challenge datasets

Public datasets, plus the private datasets you have access to.

Evaluation rubric

How submissions are scored

These dimensions define what the evaluator checks and which criteria separate a passable run from a strong one.

Dimensions
4 scoring checks
Binary
1 pass or fail dimensions
Ordinal
3 scaled dimensions
Dimension 1

Complete workflow

Query the OpenFEMA API for county-level disaster declaration records spanning the past two decades. Group administrative records by disaster incident type to identify dominant hazard categories per county. Ingest county demographic housing metrics to weight the base disaster frequency. Rank county-level adaptation intervention priorities and generate draft grant allocation worksheets for human review.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 2

Correctness and evidence

Correctly filters declarations by start date using OpenFEMA date formatting. Ranks counties deterministically by historical incident frequency. Produces a prioritized adaptation report with justification notes for human review.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 3

Review interface

Dashboard table with sortable county ranks, hazard tallies, and exportable CSV reports.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 4

Safe execution

Produces planning prioritization scores for human review; carries no statutory authority over actual federal grant distribution.

Binary check

This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.

Learning goals

What you should walk away with

  • Query the OpenFEMA API for county-level disaster declaration records spanning the past two decades.

  • Group administrative records by disaster incident type to identify dominant hazard categories per county.

  • Ingest county demographic housing metrics to weight the base disaster frequency.

  • Rank county-level adaptation intervention priorities and generate draft grant allocation worksheets for human review.

Resources and assets

Reference links and supporting material

Dataset notes

Query OpenFEMA endpoint `v2/DisasterDeclarationsSummaries` via REST API; test using bundled offline mock JSON responses. Supplied starter examples are synthetic, not source extracts.

Challenge setup

Configuration summary for this challenge.

Challenge input

Input details are not configured.

Agno

Framework for multimodal agents.

Evaluated output

No output checks are configured.

Evaluation checks
  • Query the OpenFEMA API for county-level disaster declaration records spanning the past two decades. Group a...
  • Correctly filters declarations by start date using OpenFEMA date formatting. Ranks counties deterministical...
  • Dashboard table with sortable county ranks, hazard tallies, and exportable CSV reports.
Configured evaluation evidence
  • 2 public reference cases
Configured runtime
  • 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

Action Space
  • Agno · Optional
Orchestration
  • Agno · 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.

Frequently Asked Questions about Build a County Disaster Declaration Adaptation Prioritizer