Visible obstruction may retain and mobilize street waste during rainfall.
40% weight · 32.8 pointsWhich drain should your crew inspect before the storm?
DrainGuard turns visible street evidence and changing conditions into explainable inspection priorities—then verifies whether cleanup worked.
A decision has to be made.
- 01Street litter
- 02Blocked storm drain
- 03Rainfall mobilizes waste
- 04Potential transport toward waterways
- 05Environmental concern
DrainGuard intervenes through Detect → Prioritize → Priority Shock → Allocate → Verify → Close.
Photo in. Priority out.
The model runs on the image, then a transparent risk formula combines obstruction, litter, and rainfall. No black-box flood claims.

Choose a photo — analysis starts automatically.
Every point has a visible reason.
Uses 18.0 mm as the current or selected scenario input.
30% weight · 8.4 pointsVisible waste increases potential environmental concern; it does not measure pollution volume.
20% weight · 12.4 pointsHigh proximity concern: mapped water feature about 180 m away.
10% weight · 10.0 pointsRecommended action: Schedule inspection and cleanup within 24 hours.
Environmental decision-support estimate. This helps prioritize inspection using visible blockage, litter evidence, rainfall conditions, and mapped environmental context. It is not a hydrological model or a prediction of pollution volume.
Same drains. Different conditions. Different priorities.
Change the rainfall scenario and watch the existing scoring logic update priority, environmental concern, and the ranked queue. This is scenario exploration for decision support—not a weather forecast or flood prediction.
#1DG-1045th Cross · Koramangala63/100—
Severe visible obstruction remains the strongest priority contributor.
#2DG-098Market Road · Shantinagar55/100—
Visible evidence remains lower than the reports above it.
#3DG-0911st Main · Indiranagar46/100—
Visible evidence remains lower than the reports above it.
#4DG-0878th Block · Jayanagar27/100—
Cleanup already verified; this report remains visible for routine monitoring.
One drain. Three operating conditions.
Scenario exploration for decision support. These are controlled inputs, not a weather forecast or a prediction of flooding or pollution volume.
What changed because we prioritized these drains?
Calculated only from reports added on this device. Demo scenarios are excluded.
Add a location after inspecting a photo, or select Demo preview to see how the dashboard responds.
Demo mode
Select a controlled scenario to update the inspection, scoring, explanation, and map workflow. These examples are not real municipal observations.
What should crews inspect next?
Crews see cleanup priority, environmental concern, evidence status, and the recommended action—not simply the newest report.
Reports, scores, and compressed before/after evidence survive refreshes on this inspection device. Shared multi-user storage requires a connected municipal database.
Dispatch now. Cleanup priority 84/100 · environmental concern 87/100.
Evidence that needs a person.
Low-confidence or non-drain evidence requires a field officer to check the inlet.
If you only have one crew, where should it go?
Transparent capacity allocation—not route optimization. DrainGuard selects the highest-priority dispatchable reports using the current scenario and distributes them across available crews. Human-review cases stay with the review queue.
All open reports fit within today's capacity.
Most systems stop at reporting.
Detection is not the finish line. Verified action is.
Close the loop,
not just the ticket.
After the crew cleans this drain, upload a second photo. The AI compares obstruction and litter with the original evidence before closing the report.
Detection alone does not prove the problem was solved. DrainGuard verifies the cleanup evidence.
Before · 82% blockedAfter photo appears here
AI proposes. Evidence explains.
People decide.
See
A research-backed ResNet-50 classifies blockage locally in the browser. A drain-domain gate rejects uncertain photos; COCO-SSD is used only for visible litter.
Score
Central configuration drives cleanup priority and a separate environmental decision-support estimate. Missing waterway context lowers coverage instead of becoming a fake value.
Allocate
The system ranks inspections and turns limited capacity into a concise, traceable field plan for cleanup teams.
Verify
A normalized scene fingerprint must match the original drain before blockage reduction can close the task. Uncertain pairs go to human review.
92.5% accuracy on unseen cameras.
Balanced blocked-versus-clear audit using the four cameras held out by the source research.
| Actual | Predicted blocked | Predicted clear |
|---|---|---|
| Blocked | 20 TP | 0 FN |
| Clear | 3 FP | 17 TN |
Threshold fixed on 28 images from seven different cameras, then tested once on 40 balanced images from four source-paper test cameras.
95% accuracy interval: 80.1–97.4%Open dataset + research weights ↗Scope: this is a reproducible proxy audit on UK trash-screen imagery, not claimed Bengaluru street-drain accuracy and not flood prediction. Uncertain field images still go to human review.
Workflow logic also stays tested.
| Controlled test group | Cases | Expected behavior | Decision |
|---|---|---|---|
| Blocked drain controls | 3 | Remain open and ranked | 3/3 pass |
| Clear drain controls | 3 | Low obstruction signal | 3/3 pass |
| Same-drain cleaned pairs | 2 | Match scene, then verify reduction | 2/2 pass |
| Unchanged after evidence | 1 | Reject zero-point reduction | 1/1 pass |
| Different-scene after photos | 2 | Reject scene mismatch | 2/2 pass |
| Non-drain input | 1 | Route to human review | 1/1 pass |
Twelve deterministic checks cover ranking, clear evidence, unchanged cleanup, wrong-scene evidence, and non-drain review routing. These verify workflow policy separately from the model audit above.
Why should you trust this recommendation?
Every priority exposes the blockage, litter, rainfall, and context evidence contributing to it.
Unavailable map or weather context lowers coverage instead of becoming a fabricated value.
Low-confidence images, mismatched scenes, and uncertain cleanup evidence route to review.
What the prototype proves—and what it does not.
Executable checks
- ✓ Cleanup-priority weighting and thresholds
- ✓ Environmental-risk weighting and missing-context behavior
- ✓ Rainfall sensitivity across controlled scenarios
- ✓ Before/after scene mismatch detection
- ✓ Human-review routing and cleanup gates
Still requires field validation
- Drain detection and blockage-estimation accuracy
- Environmental-risk calibration
- Real-world precision, recall, and false-positive rates
- Bias across lighting, devices, seasons, and weather
- Coverage and freshness of mapped water features
Passing workflow tests demonstrates deterministic product behavior. It does not establish scientific validity or field-model accuracy.
DrainGuard supports inspection prioritization. It does not predict floods, measure pollution volume, or replace hydrological and engineering assessment. Scores depend on image quality, rainfall inputs, and available map context.
Prototype v0.15 · Field pilot