Junction Flow
local simulation · 800px · 12 fps target
Opening session…
In
0
crossings in
Out
0
crossings out
Net
0
in − out
Unique IDs
0
confirmed tracks
Flow
0/min
rolling 60s
Utilisation
0%
loop time vs frame budget
Crossings per second
Directional counts at the line, bucketed by wall clock
Load
Concurrent tracked objects against achieved frame rate
Zones
Occupancy, dwell time and capacity alerts
No zones configured.
By class
Unique IDs seen, and how they crossed
Waiting for the first confirmed track…
Event log
Newest first
- Nothing yet. Crossings, zone activity and capacity alerts land here.
How this streams
One socket, two message types
Each frame is a JSON envelope (tracks, counts, zones, events, metrics) immediately followed by the matching JPEG as a binary message. Boxes are drawn here on a canvas, so the video stays clean, the payload stays small, and the line and zones remain draggable.
- frames seen
- 0
- raw detections
- 0
- viewers
- 1
- uptime
- —
api: https://kestrel-api-a0rv.onrender.com