You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently only aggregated statistics could be exported to Redis.
I'd like to see a optional export of detection events in such form:
{
"event_id": some unique ID (e.g. UUID v4),
"event_time": UnixTimestamp or RFC3339 o ISO8601
"class_id": ID of class (or may be label? Need to investigate common needs)
"bbox": bounding box corresponding to real image size
"speed": estimated speed
"control_zone": ID of control zone or just rectangle or all zone parameters?
"virtual_line": Parameters of virtual line (#16)?
"track": Set of points corresponding to real image coordinates before image resizing (same as bbox)
"timestamps": UnixTimestamps correspondings to set of points in track
}
Additional context
Before implementation need to deeply consider event data.
Should we just register only crossing zone events (so filter any random detection) or any object detection (probably overkill)?
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently only aggregated statistics could be exported to Redis.
I'd like to see a optional export of detection events in such form:
Additional context
Before implementation need to deeply consider event data.
Should we just register only crossing zone events (so filter any random detection) or any object detection (probably overkill)?
The text was updated successfully, but these errors were encountered: