Thanks for all the help/information on previous projects - the input has been very useful.
I seem to have hit a bit of a snag with a current project I am working on. We conducted an aerial mapping survey flight (control used with the point cloud projected in an arbitrary/project specific coordinate system) as well as manual flight operations for capturing the roofing system - copper roof (both aged and new areas). The data sets were captured using 2 different drones - mapping flight was captured at 100M AGL using an Intel Falcoin 8+ (Sony Alpha A7r) and the manual flight ops for the roof using a DJI Mavic 2 Pro at a consistent distance between 2-8M away from the roofing systems.
The data sets were processed separately through Stage 1 and the proper process for merging projects was done. When the data was merged and GCP accuracy was verified with checkpoints I ran the project through stage 2 for Point cloud generation. When completed the density of the points for the copper roof was lackluster at best - large areas with gaps. I know reflective surfaces have issues with processing but was hoping that the topo data would supplement the areas that may have required more overlap. However it appears to have done the opposite. I am wondering if there is something that I missed in terms of Advanced processing options or camera model options that I may have missed?
Roof Data - No Merge
Roof Data Merged with Topo
I decided to process just the roofing system on its own to see whether or not I would have better results with the point density and was surprised to see how much better the single data set was as compared to the merge. I am hoping that I do not have to recapture/re-deploy the areas and work with the single data set. Looking forward to some input. Cheers