Know your fleet.
Track aircraft position, battery and observation freshness. Know when a signal is current—and when it isn’t.
FLEET + TELEMETRYLess noise. More context. Turn aerial awareness into coordinated public-safety response—with a human behind every decision.
Surface signals. Bring the evidence.
Illustrative workflowReview the context. Own the call.
Operator approval first01 / THE PLATFORM
A drone feed alone is only part of the story. Bring aircraft, observed conditions and incident decisions into one shared workspace.
Track aircraft position, battery and observation freshness. Know when a signal is current—and when it isn’t.
FLEET + TELEMETRYLocate anonymous face regions and flag weak video quality. People stay unnamed; operators review the diagnostics.
ANONYMOUS FACE ANALYSISReview monitored zones and map-linked events. Keep location provenance and uncertainty in the picture.
ZONES + GEOSPATIALInspect the evidence, acknowledge an incident and record an action. An alert starts a review, not an automatic response.
REVIEW + AUDITThe current workspace uses simulated crowd observations and fixture zone locations. A separate internal worker supports video-quality checks and baseline person detection. Aerial accuracy and calibrated ground projection still need evaluation.
02 / BUILT FOR WHAT HAPPENS NEXT
Good conditions. Bad signal. A crowded exit.
Explore the decisions behind the dashboard.
OBSERVE / UNDERSTAND
Follow aircraft and zone observations in one view. Normal activity stays visible without turning every movement into an incident.
Weather changesInspect official context and data age. Weather does not equal flight clearance.
Evidence reviewAcknowledge, dismiss or resolve with a decision note and an audit record.
Volunteer checkpointSeparate consent and manual review. No public face search or biometric matching.
Lost connectivityKeep stale inputs visible. Field offline buffering remains planned work.
03 / FROM SIGNAL TO DECISION
Human judgment isn’t a fallback.
It’s the centre of the workflow.
Bring aircraft telemetry and monitored-zone observations into the workspace. Surface freshness and source quality.
Open the incident. Inspect the trigger, threshold, persistence and location provenance before deciding.
Acknowledge, dismiss or resolve. Record the action and reason. Exercise actions do not dispatch real teams.
Review the local audit chain and export the exercise. Accountability stays part of the operation.
04 / NO BLACK BOX ENERGY
Trust starts with saying exactly what a system can do—and what it can’t.
No automatic enforcement. No inference of criminal intent. Every incident calls for operator review.
Aircraft GPS isn’t a person’s location. Imported airspace and fixture zones are labeled. Ground projection needs validated calibration.
IMD, SACHET and Bhuvan adapters need configuration and validation. Other agency services remain disconnected.
The checkpoint records consent and manual review. It stores no face images, templates or biometric scores.
THE PRACTICAL STUFF
The included exercise uses synthetic telemetry. Signed HTTP gateway ingestion is implemented, but your authorized fleet still needs a protocol adapter. There is no aircraft-control feature.
The Feed & face analysis view accepts private video uploads, configured storage API imports, registered recordings and authorized RTSP feeds. It runs anonymous face detection, image-quality checks and optional baseline person detection. The exercise counts remain synthetic. Aerial validation, continuous streaming, tracking and calibrated ground projection remain deployment work.
No. Public face search and watchlist matching are not implemented. A separate volunteer checkpoint supports consent records and manual review only.
Run four exercise conditions, inspect aircraft freshness, edit zone thresholds, review incidents, inspect source adapters, manage volunteer consent, verify the local audit chain and export the exercise.
This is a local hackathon prototype. Agency authorization, verified data, real video evaluation, TLS, production identity and operational acceptance are separate deployment requirements.
Explore the local prototype. Keep the decisions human.