[SESSION_127] PersonVehicleCorrelator: Implement Motion-Based Association (Phase 23)
Resolved 💬 2 comments Opened Nov 20, 2025 by ragdm Closed Nov 29, 2025
Feature: Motion-Based Person-Vehicle Association
Component: PersonVehicleCorrelator (/nodes/behavior_nodes/person_vehicle_correlator/)
Severity: 🔴 CRITICAL BLOCKER
Session: SESSION 127 (Definition of Done)
Current Status: Uses only spatial distance, no velocity analysis
Target Phase: Phase 23
Context
Distance-only association misses important behavioral context. A person approaching a vehicle has different significance than one passing by. Motion analysis distinguishes approach/entry from casual proximity.
Requirements
- Track velocity vectors for persons and vehicles
- Detect approach vectors (moving toward vehicle)
- Distinguish entry/exit from passing by
- Calculate approach angle and speed
- Integrate motion into confidence scoring
Impact
Without this feature:
- High false positives (30-40% incorrect associations)
- Cannot distinguish entry from proximity
- Reduced blacklist/investigation accuracy
- Unreliable person-vehicle tracking
Effort Estimate
- Velocity calculation: 1.5 hours
- Motion analysis logic: 2-3 hours
- Testing: 1-1.5 hours
- Total: 4-5 hours
Technical Approach
- 2D velocity estimation (frame-to-frame)
- Dot product for approach detection
- Distance rate-of-change analysis
- Confidence weighting by motion signals
---
Generated by SESSION 127 FASE 2.7
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗