aprilrobotics / apriltag-imgs Goto Github PK

I saw a recent commit which corrected png files as they had black/white bits reversed. I think the provided postscript files still generate tags with black/white bits reversed.

The postscript files from commit 8314470 have the correct order of bits for tag generation.

Our team was trying to print the tags, for which the images were too small. I'm not aware of a quicker way to scale the images up rather than writing a numpy script. Having SVG or larger images would be really helpful for printing a lot of tags more efficiently.

Of course if there is a better solution, I would be interested to hear it as I've not worked with tagging before.

Save someone from the hassle of converting a PS to PDF and offer a printable set of the tag36h11 fiducials for download.
AprilTag-tag36h11.pdf

Repo apriltag is licensed under BSD-2-Clause. Does this also apply to the repo apriltag-imgs—or CC kind attribution eventually?

Dear developers.

I am working on a drone-related application, which requires some tags with a long detection range. Therefore, I would like to seek advice from you on how to generate suitable tags with a recursive style. I would appreciate it if you could provide some pre-generated ones.

Best regards~

I am working on the new iteration of realt-time ant tracking system that was originally build using artoolkit, and the apriltag2. It would be nice for us in the future to upgrade to apriltag3.

However the version 3 has dropped the support for artoolkit family. Even if we try at the moment to move to tag36h11 and tag36h10 families for the future, it would be nice for us to still be able to use if possible the artoolkit tags.

Is there any technical difficulties to add support to import the previous tag36artoolkit family back in Apriltag3 ? I noticed that a few new field appeared in the apriltag_family_t structure.
What would be the good new value for those fields.

Also does the opaque void* impl pointer changed for version 2 to version 3 ?

I can contribute to do this port as it is required for my project. Maybe the best place for such a port would be in its own aprilttag-img-legacy repo, to indicate that this is a clearly depreceated feature.