Okay Gang, maybe you can help me come up with a solution: manually georeferencing an .obj export

A bit of a complicated workflow here: I need to be able to bring the .obj file I export from SketchUp into CloudCompare BUT it needs to be georeferenced so that when I eventually bring the CloudCompare export I generate into ArcGIS Pro it is where it needs to be…

Is your model geo-located in SketchUp? If not you can use the Add Location feature or manually set the Lat/Long in Model Info>Geo-Location.

Yup!

I actually figured out the issue and it wasn’t the workflows in SketchUp but rather CloudCompare: after modeling in SU and exporting as an .obj file, CloudCompare was recognizing the coordinate reference from the SU model. However, the subsampled point cloud I created from the .obj surfaces then didn’t have a global shift which it needed in order to line up with the terrain point cloud once I brough it into ArcGIS Pro.

By copying the global shift of the terrain lidar dataset and assigning it to the .obj subsample point cloud, once I brought it into ArcGIS as an LAS dataset it was right where it needed to be.

Having (4) different pieces of software in my workflows (Reality Capture → SketchUp → CloudCompare → ArcGIS Pro) is exhausting, but it’s also awesome.

1 Like