I'm trying to make a point cloud and have had great success getting the detail and resolution I want, but I'm having a bear of a time getting it to scale things properly.
I'm using Context Capture to build the cloud and then Pointools to view:
In Context Capture:I have 4 control points viewable in 90%+ of the photos which I've anchored as such, used their coordinates in my coordinate system, and chosen the right projection system so the square should be georeferenced. This coordinate system is all US survey feet. all the way through the process I see I've selected the right spatial reference system and the coordinates and the bounds for my point cloud are right in my 'spatial framework' tab of my reconstruction of the block.
In Pointools: If I take that completed .pod or .las (I've tried both) into pointools it assumes all the numbers are in meters. That means if I measure a coordinate or distance within the cloud and ignore the unit type, its right. I've even overwritten the "default" spatial reference system in the las and manually chosen the ESPG number of the one I want, it still shows up as if its all really in meters.
I don't know if A)contrary to all the evidence CC is showing me, that CC is building these too big
or B)Pointools is rigidly forcing metric onto my data and I am missing the setting to make it stop.
Any help or advice would be greatly appreciated.
Craig,
We've noticed the exact same thing. We use Aeropoint GCP's and also transfer the .POD file into PointTools. We have gotten into the habit of collecting all data in metric to avoid this scaling problem. Our drone is set to meters in DJI Go 4 and Pix4d Capture and we download the GCP data in meters despite the USft stated in the EPSG name of the local state plane coordinate system. Once all that is processed in meters, it imports into PointTools just fine.
We have recently noticed an issue when examining the Splat after Aerotriangulation and a 3MX Mesh viewing in ContextCapture Viewer. ContextCapture appears to be scaling the view which is stated in the Quality Report. That same data exported into PointTools does not have this scaled error and correctly confirms control measurements.