Spotlight: Emesent SLAM scans now drop into Trimble Connect
Emesent GX1 and Hovermap SLAM data can now flow into Trimble Connect and Business Center. What scan-to-BIM teams should test first.
Autodesk University filled the last two days. The unused story for BIM and VDC teams is on the geospatial side of the same week: Emesent’s mobile SLAM scanners now plug into Trimble Connect and Trimble Business Center.
That is a file-handling change, not a new scanner. GX1 and Hovermap STX already capture. The usual pain is what happens after: export a cloud, convert it, drop it into the CDE, then hope Tekla or the as-built model still sits on the same coordinates. Emesent’s claim, announced 15 September at INTERGEO 2026 and repeated by Geo Week News, is that Aura Cloud can send a dense, georeferenced point cloud straight into Trimble Connect. From there it is available to Business Center and, Emesent says, to Tekla Structures and SketchUp.
What actually changed
The capture devices did not change this week. GX1 is the integrated SLAM and RTK scanner Emesent launched earlier in 2026. Hovermap STX is the unit firms already hang on a drone or walk through a plant room. Both process in Aura Cloud. The new piece is the Trimble handoff: sign in once, approve access, and send the processed cloud into a Connect project you can already open.
Emesent’s product page is more careful on accuracy than the press release. GX1 is listed at 5–10 mm local with unconstrained SLAM, or 15 mm global with RTK or PPK. Hovermap is listed at 5–10 mm unconstrained, or 15–30 mm global, and can be paired with a Trimble GNSS receiver for RTK at the point of capture. Those numbers are vendor figures. They are not a project tolerance until you close them with independent checkpoints.
Tim Lemmon at Trimble, quoted in the announcement, called Connect the gateway into the rest of the Trimble stack. That is the useful sentence. If your firm already lives in Connect, TBC and Tekla, a SLAM cloud that arrives as a Connect object is less work than another E57 sitting in a folder nobody owns.
What a BIM or VDC lead should do
Do not rebuild the survey method because the export step got shorter. The rules in our scan-to-BIM note still hold: say what the cloud is for, set a tolerance, lock a coordinate system, and keep a read-only source.
If you already run Emesent and Trimble, pick one non-sensitive existing-conditions job. Send the cloud through Aura into Connect. Then ask four questions: does the cloud land on project coordinates without a second transform; can TBC extract the features you actually issue; can Tekla see the same cloud the field team captured; and does the permission prompt stay inside projects the firm already controls.
If you are not on that stack, this is not a reason to buy two ecosystems. It is a reason to stop treating “we scanned it” as the deliverable. The deliverable is a cloud that the model, the steel package and the as-built all share.
Start with Emesent’s INTERGEO announcement and the Trimble integration page.
Frequently asked questions
What did Emesent announce?
A workflow integration, announced 15 September 2026 at INTERGEO in Munich. Mobile SLAM data from GX1 and Hovermap STX can move into Trimble Connect and Trimble Business Center after processing in Aura Cloud.
Which scanners are included?
Emesent GX1, the handheld SLAM plus RTK unit, and Hovermap STX, the SLAM LiDAR system used on drones, vehicles or a backpack. Both use the same Aura Cloud processing path.
Does this replace a scan-to-BIM standard?
No. It shortens file handling. You still need a coordinate statement, checkpoints, a modeling scope and a comparison of the finished model back to the cloud.
Who can see the Trimble projects?
Emesent says the first transfer asks you to sign in to Trimble and approve access, and that Aura Cloud can only reach projects you already have permission to open.