We are having some issues with visually boresighting the R2A laser and camera. Within PCMaster / Painter, you cant zoom in or pan practically past a certain point. This makes it very hard to “get right in there” to align trajectories very precisely. Best guess is 10cm or so.
I am hoping this is not something to do with our GPU but we have run this on a number of machines, each with either integrated GPU or standalone (GeForce RTX 3080) with the same issue.
While we wait patiently for the trajectory to be exported in a recognizable format like SBET (something the developers have promised from day 1), would someone like to have a crack at this and offer their suggested values? Each of the 5 of us in office have all got wildly different values for both the camera and laser boresight. While this is not a serious issue on data that is collected from a short distance, the effects of poor boresighting are dramatically noticeable on longer range measurements.
Here is a link to the data:
The method of “visually” aligning data is not common practice in the photogrammetry world and having more quantifiable methods will take a lot of guesswork out of this.