Automatically translate GCP coordinates to ensure no weird rounding error artifacts when rectifying

name: "Feature Request Template"
about: "For feature requests. Please search for existing issues first. Also see CONTRIBUTING."

Feature Request

Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I have an issue when [...]

If a user collects GCP in UTM or StatePlane, the X, Y coordinates are often orders of magnitude larger than the Z coordinate. This causes weird rounding-related errors in the orthorectification process. See #123 (closed) for example. Currently, users must perform this step manually before importing their GCP tables.

Describe the solution you'd like A clear and concise description of what you want to happen. Add any considered drawbacks.

It would be beneficial if IVyTools could automatically translate the X,Y inputs for these surveys to prevent rectification errors. IVy should compute the required translation and save it, so the user can load the GCP table without worrying about the translation. Make it transparent to them, and handle this in the backend.

1. Display the X,Y in their native units in the Points Table
2. Translate by some automatically determined [X, Y] vector, save this
3. The Camera/Homography matrix would be computed on the translated numbers.

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

Currently, users must manually fix this issue before importing their GCP tables.

Teachability, Documentation, Adoption, Migration Strategy If you can, explain how users will be able to use this and possibly write out a version in the docs or SOPs. Maybe a screenshot or design?

We can add a blurb about this in the SOPs

Tagging @mgyves for awareness