... quite a few mis-alignments. ...
The image service uses and rpdef file to define camera interior orientation, and the image exterior orientation parameters are in a dbf that reference the rpdef file. ....
You should combine GCP & TP with RPC to refine this model, at least, a few of TP (Tie Points) for your case.
... to run the IMU data through Applanix POSPac MMS after the flight, generate an external orientation file, and use that as input to the orthorectification process. We have not been using tie points or gcp.
Is there a way to specify tie points in ArcMap?
The "nad83_with_subset_of_images" image shows how the change (switching to a nad83 datum in the EO) affected the subset (about 10) images. The "nad83_with_all_images" image shows how the change did not have the same effect on the complete dataset. It is slightly different than before I switched to NAD83, but it isn't helping as much as it did with the smaller subset of images. Does that mean anything?
I'm also seeing that in ArcMap, when I zoom in more, the alignment gets better. It seems to change the images it is selecting. I don't see similar behavior in the deployed service (as a WMS), so I'm not sure what that means.
Indeed, �??Direct Georeferencing�?? products look easy and simple to many end users; but, many practices show that it is intensive cooperation and detail-oriented mission�?�