How rishit-ui/resqtrack works
ResQTrack detects and confirms road incidents from camera video, then alerts the response backend to coordinate responders, scene navigation, nearby facilities, and case tracking. The detector also builds vehicle profiles and renders an operator HUD. The README documents dashboard/responder experiences and the end-to-end response stages. Some modules are represented from the source index or README rather than inspected source; their internal links are omitted where the available evidence does not establish ownership.
Main entry points: app.py Response API · main_before_database_debug.py Video detector · routing_service.py Road routing · hospital_service.py Facility search
Components 21
Detection and evidence
- Video detector
main_before_database_debug.py - Incident reasoning
vision/incident_engine.py - Vehicle profiles
vision/vehicle_profile.py - Motion features
vision/kinematics.py - Detector HUD
vision/overlay.py
Incident response
- Alert sender
vision/alert_client.py - Response API
backend/app.py - Responder dispatch
backend/services/dispatch.py
Routing and facilities
- Geospatial services
backend/services/geo.py - Road routing
backend/services/routing_service.py - Traffic scoring
backend/services/traffic.py - Facility search
backend/services/hospital_service.py
Realtime and records
- Incident database
backend/database.py - Live updates
backend/realtime.py
Temporal analysis
- Temporal detector
temporal_detector.py - Feature engine
temporal_features_engine.py - Model inference
temporal_ml_inference.py - Accident logic
accident_logic.py
Other components
- Traffic camera
- Control room
- Responder app
Connections 23
- Traffic camera → Video detector: provides video
- Video detector → Incident reasoning: evaluates frames
main_before_database_debug.py - Video detector → Vehicle profiles: updates profiles
main_before_database_debug.py - Vehicle profiles → Motion features: uses motion
vision/vehicle_profile.py - Video detector → Detector HUD: renders overlay
main_before_database_debug.py - Incident reasoning → Detector HUD: supplies evidence
vision/overlay.py - Video detector → Alert sender: queues alert
main_before_database_debug.py - Alert sender → Response API: posts incident
vision/alert_client.py - Response API → Responder dispatch: selects responders
backend/app.py - Responder dispatch → Geospatial services: uses location
backend/services/dispatch.py - Response API → Road routing: requests routes
backend/app.py - Road routing → Geospatial services: uses coordinates
backend/services/routing_service.py - Road routing → Traffic scoring: scores alternatives
backend/services/routing_service.py - Response API → Facility search: searches facilities
backend/app.py - Facility search → Geospatial services: uses coordinates
backend/services/hospital_service.py - Facility search → Road routing: ranks by road time
backend/services/hospital_service.py - Response API → Incident database: reads and writes
backend/app.py - Live updates → Incident database: reads records
backend/realtime.py - Response API → Live updates: broadcasts updates
backend/app.py - Control room → Response API: views incidents
- Responder app → Response API: accepts dispatch
- Feature engine → Temporal detector: supplies features
- Temporal detector → Model inference: uses model