Build a Disaster Declaration County Portfolio Tracker
Cross-reference municipal commercial building inventories against historical OpenFEMA disaster declarations to track portfolio inclusion in county-level disaster events. Generate administrative asset dossiers highlighting declared hazard history.
What you are building
Cross-reference municipal commercial building inventories against historical OpenFEMA disaster declarations to track portfolio inclusion in county-level disaster events. Generate administrative asset dossiers highlighting declared hazard history.
Municipal Climate Resilience Officer
Fetch county disaster history using OpenFEMA DisasterDeclarationsSummaries endpoint filters.
Ingest municipal commercial asset locations and map to corresponding county administrative boundaries.
Tally historical county-level flood declarations during the lifespan of each asset.
Synthesize structured portfolio inclusion profiles and export administrative review dossiers.
CLI tool that ingests asset CSVs and outputs a Markdown administrative dossier.
Download public DisasterDeclarationsSummaries from OpenFEMA API endpoint https://www.fema.gov/api/open/v2/DisasterDeclarationsSummaries with $filter=state eq 'VA' and local synthetic municipal asset county mappings. Starter examples below are synthetic. They are not downloaded records.
FEMA OpenFEMA Queries the OpenFEMA API endpoint v2/DisasterDeclarationsSummaries using $filter with state and incidentType parameters.
pydantic-ai, requests, pandas. Pydantic AI enforces type-safe parsing of FEMA records and structured administrative portfolio exports. Fast hosted model or local small model with reliable structured JSON output support.
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.
Filters OpenFEMA records for matching state, county, and disaster type correctly.
Calculates county declaration inclusion count strictly from matched historical records.
Outputs valid structured JSON containing asset identifier and county declaration tally.
```json [ { "input": { "county": "Fairfax (County)", "state": "VA", "asset_id": "COMM-001", "fema_records": [ { "disasterNumber": 4042, "incidentType": "Flood", "designatedArea": "Fairfax (County)" } ] }, "expected_output": { "asset_id": "COMM-001", "county_exposure_count": 1, "record_type": "simplified synthetic app record" } }, { "input": { "county": "UnknownCounty", "state": "VA", "asset_id": "COMM-002", "fema_records": [] }, "expected_output": { "asset_id": "COMM-002", "county_exposure_count": 0, "record_type": "simplified synthetic app record" } } ] ```
Simulates administrative hazard inclusion scores; produces no real property underwriting or legally binding coverage assessments. Use mock external writes. Require human review before any real deployment.
Rules
Simulates administrative hazard inclusion scores; produces no real property underwriting or legally binding coverage assessments. Use mock external writes and human review.
How work is evaluated
Filters OpenFEMA records for matching state, county, and disaster type correctly. Calculates county declaration inclusion count strictly from matched historical records. Outputs valid structured JSON containing asset identifier and county declaration tally.
Runnable source, pinned dependencies, setup commands, working interface, example outputs, recorded demo, tests, and action logs.
Datasets
Public datasets, plus the private datasets you have access to.
How submissions are scored
Complete workflow
Fetch county disaster history using OpenFEMA DisasterDeclarationsSummaries endpoint filters. Ingest municipal commercial asset locations and map to corresponding county administrative boundaries. Tally historical county-level flood declarations during the lifespan of each asset. Synthesize structured portfolio inclusion profiles and export administrative review dossiers.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Correctness and evidence
Filters OpenFEMA records for matching state, county, and disaster type correctly. Calculates county declaration inclusion count strictly from matched historical records. Outputs valid structured JSON containing asset identifier and county declaration tally.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Review interface
CLI tool that ingests asset CSVs and outputs a Markdown administrative dossier.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Safe execution
Simulates administrative hazard inclusion scores; produces no real property underwriting or legally binding coverage assessments.
This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.
Learning goals
Fetch county disaster history using OpenFEMA DisasterDeclarationsSummaries endpoint filters.
Ingest municipal commercial asset locations and map to corresponding county administrative boundaries.
Tally historical county-level flood declarations during the lifespan of each asset.
Synthesize structured portfolio inclusion profiles and export administrative review dossiers.
Resources
Download public DisasterDeclarationsSummaries from OpenFEMA API endpoint `https://www.fema.gov/api/open/v2/DisasterDeclarationsSummaries` with `$filter=state eq 'VA'` and local synthetic municipal asset county mappings. Supplied starter examples are synthetic, not source extracts.
Challenge setup
Challenge input
Input details are not configured.
Pydantic AI
Typed Python agent framework.
Evaluated output
No output checks are configured.
- Fetch county disaster history using OpenFEMA DisasterDeclarationsSummaries endpoint filters. Ingest municip...
- Filters OpenFEMA records for matching state, county, and disaster type correctly. Calculates county declara...
- CLI tool that ingests asset CSVs and outputs a Markdown administrative dossier.
- 2 public reference cases
- 2 configured tools
Shows the first task, up to three tools, and up to three evidence items.
View technical recipe
Configured tools
- Pydantic AI · Optional
- Pydantic 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.