Sitescan is currently forcing users into using "correct" coordinate systems. This becomes an issue when we need the flights to be processed with an adjacent coordinate system, by request from the project/client. For example, in Norway the official UTM sones are 32 - 35 although the country spans the UTM sones 31 - 36. This means that data collected for for clients like the state or municipalities on the west coast, is required to be in UTM32 even tough the area technically falls within UTM31. We have a official coordinate system with higher accuracy used in construction (NTM). This has has smaller sones, compared to UTM, and this also becomes an issue when large construction projects are crossing the border of two NTM sones.
When creating a project in Sitescan the user is forced to select the sone that is technically correct. For this we have a workaround by defining the project center further east/west, to be able to select the desired sone.
After recent updates we cannot upload GCP's because they fall outside of coordinate system. When uploading a GCP set that falls outside of the coordinate system definition "Save" button is simply disabled. This means that currently we cannot deliver data from flights processed with GCP's in the official coordinate system used for western parts Norway.
My idea is this:
Display warnings if it seems that the selected coordinate system or uploaded GCP set is incorrect, but do not disable the option to create a project/save GCP's or process the mission because of it.
