Build a Wildfire Claim Evidence Footprint Reconciler
Correlate commercial property loss claims against historical OpenFEMA fire declarations and STAC post-fire imagery footprints. Verify spatial inclusion within administrative zones and image bounds for human investigators.
What you are building
The core problem, expected build, and operating context for this challenge.
Correlate commercial property loss claims against historical OpenFEMA fire declarations and STAC post-fire imagery footprints. Verify spatial inclusion within administrative zones and image bounds for human investigators.
Property Claim Investigation Specialist
Ingest property claim intake forms with policyholder coordinates and dates.
Verify county disaster declaration status using OpenFEMA DisasterDeclarationsSummaries.
Retrieve corresponding post-event STAC catalog satellite Items intersecting the physical address.
Formulate a structured claim evidence reconciliation report detailing administrative and image footprint matches.
Multi-panel review workbench displaying claim details, FEMA county administrative records, and STAC satellite bounding box previews.
Query OpenFEMA API for fire declarations using $filter=incidentType eq 'Fire' and use mock STAC catalog GeoJSON footprint bounds. Starter examples below are synthetic. They are not downloaded records.
FEMA OpenFEMA Extracts disaster declaration dates and designated county areas from OpenFEMA DisasterDeclarationsSummaries to cross-verify claims against administrative zones.
langgraph, requests, pystac. LangGraph orchestrates a multi-step verification graph, routing claim checks between OpenFEMA administrative queries and STAC spatial footprint lookups. Hosted reasoning model capable of coordinating multi-step graph execution and evaluating spatial point-in-polygon logic.
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.
Checks claim incident date against FEMA declaration start and end dates.
Confirms the claim asset coordinate falls within the declared FEMA administrative county.
Validates that the asset coordinate is within the bounding box of the retrieved STAC post-fire imagery.
```json [ { "input": { "claim_id": "CLM-PROP-401", "incident_date": "2023-08-10", "asset_coords": [ -156.6825, 20.8783 ], "county": "Maui", "fema_declaration": { "incidentBeginDate": "2023-08-08", "incidentEndDate": "2023-08-15", "designatedArea": "Maui (County)" }, "stac_bbox": [ -156.7, 20.8, -156.6, 20.9 ], "note": "Simplified synthetic app record" }, "expected_output": { "claim_id": "CLM-PROP-401", "temporal_match": true, "admin_spatial_match": true, "image_footprint_match": true, "reconciliation_status": "VERIFIED_MATCH", "note": "Simplified synthetic app record" } }, { "input": { "claim_id": "CLM-PROP-402", "incident_date": "2023-09-20", "asset_coords": [ -156.2, 20.7 ], "county": "Maui", "fema_declaration": { "incidentBeginDate": "2023-08-08", "incidentEndDate": "2023-08-15", "designatedArea": "Maui (County)" }, "stac_bbox": [ -156.7, 20.8, -156.6, 20.9 ], "note": "Simplified synthetic app record" }, "expected_output": { "claim_id": "CLM-PROP-402", "temporal_match": false, "admin_spatial_match": true, "image_footprint_match": false, "reconciliation_status": "REQUIRES_REVIEW", "note": "Simplified synthetic app record" } } ] ```
Compiles preliminary event correlation evidence; leaves all insurance coverage and payout decisions to certified human claims adjusters. Use mock external writes. Require human review before any real deployment.
Participation guide
Compiles preliminary event correlation evidence; leaves all insurance coverage and payout decisions to certified human claims adjusters. Use mock external writes and human review.
How work is evaluated
Checks claim incident date against FEMA declaration start and end dates. Confirms the claim asset coordinate falls within the declared FEMA administrative county. Validates that the asset coordinate is within the bounding box of the retrieved STAC post-fire imagery.
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
Ingest property claim intake forms with policyholder coordinates and dates. Verify county disaster declaration status using OpenFEMA DisasterDeclarationsSummaries. Retrieve corresponding post-event STAC catalog satellite Items intersecting the physical address. Formulate a structured claim evidence reconciliation report detailing administrative and image footprint matches.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Correctness and evidence
Checks claim incident date against FEMA declaration start and end dates. Confirms the claim asset coordinate falls within the declared FEMA administrative county. Validates that the asset coordinate is within the bounding box of the retrieved STAC post-fire imagery.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Review interface
Multi-panel review workbench displaying claim details, FEMA county administrative records, and STAC satellite bounding box previews.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Safe execution
Compiles preliminary event correlation evidence; leaves all insurance coverage and payout decisions to certified human claims adjusters.
This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.
What you should walk away with
Ingest property claim intake forms with policyholder coordinates and dates.
Verify county disaster declaration status using OpenFEMA DisasterDeclarationsSummaries.
Retrieve corresponding post-event STAC catalog satellite Items intersecting the physical address.
Formulate a structured claim evidence reconciliation report detailing administrative and image footprint matches.
Reference links and supporting material
Query OpenFEMA API for fire declarations using `$filter=incidentType eq 'Fire'` and use mock STAC catalog GeoJSON footprint bounds. Supplied starter examples are synthetic, not source extracts.
Challenge setup
Configuration summary for this challenge.
Challenge input
Input details are not configured.
LangGraph
Runtime for stateful agent workflows.
Evaluated output
No output checks are configured.
- Ingest property claim intake forms with policyholder coordinates and dates. Verify county disaster declarat...
- Checks claim incident date against FEMA declaration start and end dates. Confirms the claim asset coordinat...
- Multi-panel review workbench displaying claim details, FEMA county administrative records, and STAC satelli...
- 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
- LangGraph · Optional
- LangGraph · 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.