HI,
I would greatly appreciate it if you could help with this data proper processing settings, as it works fine in Trimble TBC and Pix4D photogrammetry processing engines, but not in a Reality capture. We would like to use Reality capture but so far can’t get the result as good as those two mentioned above.
Data captured with DJI M3E drone, RTK enabled and worked fine (code 50 in .MRK file, fix solution, cors station is near). Around 1000 photos were taken. 5 GCP, 15 CPS to check the module accuracy. GCPs and CPs surveyed with survey grade GNSS. Flight performed at 50 or 60m (don’t remember correctly). Aim is to get a point cloud with a precision of ~5cm, to any point, not only near GCPS.
Data processed without (!) GCPs, to see what result RC gives with only image exif location (RTK data) available. So the photo’s prior pose is set to position and orientation. As there is no geoid correction available in RC, then Ellipsoidal heights and wgs-84 were used for processing. After alignment was done and CP were imported, I noticed that CPs are below sparse point cloud! After further processing and comparing to CP, I can clearly see that the created mesh and ortho is around 3m higher than CPs! Both in ellipsoidal heights.
So the questions arise -
-
is this some settings fault?
-
Lens distortion model could cause this issue? What else?
-
What can be done to be able to use both image location data (RTK precision) and GCPs?
GCPs aren’t used, as it gives inacurate data between GCPs (distance up to 50-100m) (tested it in other RC file). Around GCPs results are ok, but between them data isn’t as accurate. Of course I can disable photos exif location data, but then what’s the point of RTK drone? Purely relying on GCPs doesn’t give the accuracy we are aiming for, as it’s for construction needs.
Further some screenshots and settings used. Shame that new users can post only one attachment per post, as I have more
