In my maps with GCPs, it always seems the drone altitudes and computed point cloud is way different that the measures GCP data. As a result the GCPs are not “near” any of the images so it is not possible to mark the GCP’s on images. Your support pages provide a solution - basically override all of the image EXIF altitudes to fudge the values to about the GCP altitude plus flight height. I have tried this and it has worked, but it is big waste of time as it requires completely rerunning step 1.
There would seem to be a very simply alternative solution - allow matching GCPs using only X, Y data, then then reoptimize to fix the point cloud altitudes.
Another fix would be to allow me to apply a fixed offset to all computed points to allow GCP marking.