What you need to know about MindCloud Studio and Software Workflows

General
1

Hey community!

We’ve talked a lot in this forum about the Pocket 2 hardware specs, tracking performance, and on-site RTK accuracy, but we haven’t given enough spotlight to the software powering it behind the scenes!

Whether you’re processing locally or in the cloud, MindCloud Studio and MindCloudX.AI unlock a ton of downstream versatility that goes far beyond basic point cloud rendering:

  • In-App Mobile Control (MindCloud Go): Before heading back to the office, field crews can preview live scans via Wi-Fi, toggle between Elevation, Intensity, and True Color views, and even export early 2D/3D .dxf files directly on site.

  • Direct CAD & Simulation Exports: Beyond standard .las and .e57 point clouds, MindCloud Studio supports exports to .ply, .obj, and .usd (Universal Scene Description). This allows spatial datasets to feed directly into NVIDIA Omniverse or Unreal Engine for 3D simulation and autonomous robotics training.

  • AI-Driven Denoising & Classification: Uploading raw datasets to MindCloudX.AI automates registration, noise removal, and white-model generation without consuming high-end local GPU power.

  • Geoid & Grid Corrections: Recent updates to MindCloud Studio added dedicated interfaces for RTK optimization, supporting custom geoid models and horizontal/vertical grid correction files for strict surveying tolerances.

Hardware is only half the battle-having an open software ecosystem that connects directly to CAD, BIM, and simulation engines makes the real difference in project turnaround times.

2 Likes
2

I was pleased to see there was support for geoid shift calcs, but it doesn’t seem to be working in my version. I work in ftUS and it is spot on in NAD83(2011) however, I still have to calculate an average displacement for my jobs post processing to get close to NAVD88(GEOID18).

Also, when measuring in Section View the results come back way off. The results are suspiciously close to the meter/feet conversion factor (3.3x). For instance, I may get 78 feet for a 2-lane road that is only 24 feet. The power poles may report 165 and should be 50. I am sure this is something the software engineers can work out, but maybe they need it brought to their attention. At least it seems relatively simple to me compared to what the program can do.

Over all, I am pleased with the results and look forward to using the Pocket 2 for most all of my topographic surveys in the future. Also, looking forward to the next software update. Ty.