mirror of
https://github.com/opencv/opencv.git
synced 2026-07-25 21:33:04 +04:00
d9038ad00d
[OpenCV 5] Fix apriltag corners order and update the doc #28823 I have updated documentation for the AprilTag dictionaries. Corresponding issues: - https://github.com/opencv/opencv-python/issues/1195 - https://stackoverflow.com/questions/79044142/why-is-the-order-of-the-incoming-corners-different-between-apriltag-and-aruco-ma This is a breaking change and is targeted only for OpenCV 5. --- I have updated the ArUco doc with more information about fiducial markers detection. I have tried to add some recommendations, best practices: - `DICT_ARUCO_MIP_36h12` should be the recommended family, [see](https://stackoverflow.com/a/51511558) - link to download pregenerated markers for `MIP_36h12` is [here](https://sourceforge.net/projects/aruco/files/. I have not found some other official links for the other ArUco family, but since `MIP_36h12` should be used, I guess it is fined. - recommendation to have a white border when printing the marker ### Pull Request Readiness Checklist See details at https://github.com/opencv/opencv/wiki/How_to_contribute#making-a-good-pull-request - [x] I agree to contribute to the project under Apache 2 License. - [x] To the best of my knowledge, the proposed patch is not based on a code under GPL or another license that is incompatible with OpenCV - [x] The PR is proposed to the proper branch - [x] There is a reference to the original bug report and related work - [ ] There is accuracy test, performance test and test data in opencv_extra repository, if applicable Patch to opencv_extra has the same branch name. - [x] The feature is well documented and sample code can be built with the project CMake