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: Export Detection Coordinates #727

Open
I-AM-EXFOLIATING opened this issue Jan 16, 2025 · 0 comments
Open

Feature: Export Detection Coordinates #727

I-AM-EXFOLIATING opened this issue Jan 16, 2025 · 0 comments

Comments

@I-AM-EXFOLIATING
Copy link

It would be useful for integration with other tools, and for diagnostic purposes, to export the image coordinates of detections to a text file.

My use-case is exporting AprilTag centers for a non-kalibr calibration tool which does not support AprilTags directly, but can consume a text file containing the detection information.

I initially tried doing this with the apriltags_demo from https://people.csail.mit.edu/kaess/apriltags/ however I found that the AprilTag detector in kalibr is exceptionally robust compared to the "official" detector which did not seem to like my Aprilgrid generated by kalibr (I suspect the small black squares on the corners confuse the outline detection). Is there some special sauce in kalibr's implementation?

If this feature is implemented, the exported data must contain the timestamp for the originating frame (seconds + nanoseconds) and the coordinates of the detections (center of tags in the case of AprilGrids).
I've tried to hack this in myself to test if the feature could be viable, but ran into issues of both timestamp and detection coordinates being available in the same scope, so it would require some refactoring.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant