Venezuela + Colombia Earthquake Response

The same discipline the Humanitarian OpenStreetMap Team is using right now on its own live Venezuela earthquake mapping project (not affiliated with this hackathon). Coordinate systems, damage-zone geometry, and the cartographic mistakes that look fine in a demo and mislead a responder in the field.

Ground the sector-assignment and matching logic in how multi-agency search actually works under real field conditions, not how it looks on a whiteboard.

The matching and dispatch logic mirrors real last-mile relief distribution. Unrealistic assumptions show up fast to someone who’s done this.

ATC-20-informed structural triage is a proposed contribution, not a capability in the current starter. Structural engineers can define safe scope, warnings, escalation, and the boundary between software guidance and an authorized evaluation.

Including amateur radio operators. The offline-first, low-bandwidth design needs someone who’s actually run communications on a degraded network.

The outbreak-alerting logic borrows from real syndromic-surveillance practice. A public-health background catches false alerts before they reach a clinic, or a missed real one.

Real beneficiary-fraud patterns look different from what a synthetic dataset assumes. This is exactly your domain.

Pressure-test the claim-triage and scam-link heuristics against real disinformation patterns, not textbook ones.

Matching and consent logic needs real case-management practice behind it — not assumptions about how family tracing “should” work.

The published open track did not prescribe one discipline; relevant expertise depended on the proposed idea.

Build adaptable data pipelines and document their interfaces so organizations can evaluate and integrate components without starting over.

The published plan identified translation and review of safety language, technical terms, and low-connectivity flows as important work across its supported languages.

These are operational tools, not marketing sites: usability under stress, low bandwidth, and accessibility matter more than polish.

Help a track’s data model speak the standards real humanitarian information systems already use, instead of reinventing conventions that exist.

Review licenses, privacy boundaries, threat models, and implementation guidance so organizations can adopt the open tools responsibly.

Place names, institutions, languages, access constraints, and community priorities must be reviewed locally before a prototype can be considered for real use.