More sofisticated GUI to check and review the results

[zsiki]

Functions:

• step forward and backward among images
• delete false match
• add manual match
• rerun the automatic match find for an image or for all images
• alter gcp_find parameters (ArUco)
• select image to display
• add image to image set
• remove image from image set

GUI in tkinter or Qt5 or integration into https://github.com/uav4geo/GCPEditorPro

[APOS80]

I think a GUI would be pretty easy to make. But first I need to try this piece of code.

[zsiki]

Any contribution is welcome!

[ZohaibDurrani]

Hello, I am using aruco marker (Dict 4x4), the printed size of a marker is 2.5x2.5 feet to detect in the images taken from Phantom RTK. Altitude is 70 meters. but couldn't detect the markers. what i am doing wrong here ? Is printed marker size is short ? because when I cropped the image into certain size it detects the marker but not detecting in the actual image size and in height.

[zsiki]

I suppose the size is OK (76 x 76 cm). The proposed size of your marker is 46 x 46 cm (see http://www.agt.bme.hu/on_line/gsd_calc/gsd_calc.html, Phantom 4 RTK, 70 m). May be the --minrate parameters should be tuned. For example if the larger size of your image is 5472 pixels and the minrate is 0.03 (default value) than the minimal perimeter of the marker should be on the image 5472 * 0.03 = 164 pixels and so the size ~12 x 12 pixels. If you send me a sample image I can try to help you more.

[ZohaibDurrani]

Here is an image taken from 70m height.

[ZohaibDurrani]

This image is taken from 80m.

[ZohaibDurrani]

110 meter.

[zsiki]

I made a quick calculation for the image from 70 metres: The 4x4 ArUco marker is ~33x37 pixels on the image, the perimeter = ~138 pixels. The width of the image is 5472, so the --minrate parameter is 138 / 5472 = ~ 0.02. The white blocks of the marker are burnt in so I set --ignor parameter to 0.2 (20% percent).

./gcp_find.py --minrate 0.02 --ignore 0.2 Zohaib/160233726-f40e31b5-7639-4171-a53c-f81e018f28cc.JPG
3993 1846 160233726-f40e31b5-7639-4171-a53c-f81e018f28cc.JPG 4
Finished in 0.6204730359999999 seconds

[zsiki]

Another problem I realized on your 160233926-2cf2bfb9-1a2d-40da-b77e-2da72b440122.JPG image is that, the marker is not separated. At top left and top right corner there are some gray pixels close to the black area of the marker. If I edit the image and change those pixel to white, the marker is recognized. You should use larger outer white border or put a larger white paper below the marker. A last image made from 110 m is burnt in so much, that it cant be recognized. Have you read about gray/black markers in the readme?

[ZohaibDurrani]

I have tried the suggestions you have given. It worked on 70m height. Moreover, the suggestions and information you have provided is a vital info for me. Thank You so much. I also have taken the image from 100m height. If you would like to I will also share that image with you.

On Tue, Mar 29, 2022, 9:50 PM Zoltan Siki @.***> wrote:

Another problem I realized on your 160233926-2cf2bfb9-1a2d-40da-b77e-2da72b440122.JPG image is that, the marker is not separated. At top left and top right corner there are some gray pixels close to the black area of the marker. If I edit the image and change those pixel to white, the marker is recognized. You should use larger outer white border or put a larger white paper below the marker. A last image made from 110 m is burnt in so much, that it cant be recognized. Have you read about gray/black markers in the readme?

— Reply to this email directly, view it on GitHub https://github.com/zsiki/Find-GCP/issues/2#issuecomment-1082122173, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATAYISIUOZFNNI5H3KBYO43VCMYFXANCNFSM43P22TEQ . You are receiving this because you commented.Message ID: @.***>

[ZohaibDurrani]

Now I get the point. Thank You for your time and support. Thank You very much.

On Wed, Mar 30, 2022 at 6:43 PM Zohaib Durrani @.***> wrote:

I have tried the suggestions you have given. It worked on 70m height. Moreover, the suggestions and information you have provided is a vital info for me. Thank You so much. I also have taken the image from 100m height. If you would like to I will also share that image with you.

On Tue, Mar 29, 2022, 9:50 PM Zoltan Siki @.***> wrote:

Another problem I realized on your 160233926-2cf2bfb9-1a2d-40da-b77e-2da72b440122.JPG image is that, the marker is not separated. At top left and top right corner there are some gray pixels close to the black area of the marker. If I edit the image and change those pixel to white, the marker is recognized. You should use larger outer white border or put a larger white paper below the marker. A last image made from 110 m is burnt in so much, that it cant be recognized. Have you read about gray/black markers in the readme?

— Reply to this email directly, view it on GitHub https://github.com/zsiki/Find-GCP/issues/2#issuecomment-1082122173, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATAYISIUOZFNNI5H3KBYO43VCMYFXANCNFSM43P22TEQ . You are receiving this because you commented.Message ID: @.***>

[ZohaibDurrani]

Hello, Faced an issues and some errors in exif_pos.py, like "GPSInfo" is not extracting the info, I thought that it was a PIL version conflicts than I also tried other version but faced same issues, But now I made some little changes and fixed those errors.

[zsiki]

Please open an other issue and give me more information with sample images if possible.or send me a pull request with your modification.