-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Visualize / exaggerate the single pixel at the bottom of the detection box used for zones #3911
Comments
Yeah that's probably a good idea to be a reminder. I also have a PR up that adds configuration to make it the top center, left center, right center, or bottom center |
Even more important to visualize it then.. Sounds like a nice option to have. Is a center of object also possible? It would be useful for heavily overhead views. |
I agree. It would likely be more accurate considering that bounding boxes don't always perfectly align with objects. |
This would be far less precise and almost impossible to use for cameras mounted at a front door. It started this way and it was almost useless. |
For me the easiest solution to understand from the end user's point of view would be to be able to use the center point of the entire area surrounded by the bounding box (not a point on the bounding box). |
Describe what you are trying to accomplish and why in non technical terms
The documentation states that zones are determined only by a single pixel at the bottom of the object. I suggest adding a dot/square/crosshair at the bottom of every detection bounding box to help call this out.
Describe the solution you'd like
I suggest adding a dot/square/crosshair at the bottom of every detection bounding box to help show how a zone detection was made.
I personally keep forgetting that the zone needs to basically be at the FEET of the object to work and at various camera angles this creates some interesting problems where I wish zone detection was based on the box clipping the object instead of a single pixel.
The text was updated successfully, but these errors were encountered: