Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE REQUEST] Export events information to Redis #19

Open
LdDl opened this issue Feb 18, 2024 · 1 comment
Open

[FEATURE REQUEST] Export events information to Redis #19

LdDl opened this issue Feb 18, 2024 · 1 comment
Assignees
Labels
delayed enhancement New feature or request question Further information is requested

Comments

@LdDl
Copy link
Owner

LdDl commented Feb 18, 2024

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)?

@LdDl LdDl added the enhancement New feature or request label Feb 18, 2024
@LdDl LdDl self-assigned this Feb 18, 2024
@LdDl LdDl added the question Further information is requested label Feb 18, 2024
@LdDl LdDl changed the title [FEATURE REQUEST] Export events to Redis [FEATURE REQUEST] Export events information to Redis Feb 18, 2024
@LdDl
Copy link
Owner Author

LdDl commented Apr 13, 2024

There is Redis drama.
No matter what I think it is need to be implemented anyways, but after #16 (since we can met breaking changes)

@LdDl LdDl added the delayed label Apr 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
delayed enhancement New feature or request question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant