Turn NavVis point clouds and panoramic imagery into georeferenced, ready-to-share geodata in GEORIZON, without a licence per user.
Let us be straight about this, because it is the first thing a CLX owner will check. Processing is not where we compete on the CLX. NavVis gives the device a flat rate entitlement, so unlimited cloud processing without heavy local hardware, and direct export to E57, LAS and Recap straight out of IVION. For a firm that scans a building, exports the point cloud and hands it to a modeller, that covers the job. Two things it does not cover. It is tied to a valid subscription: NavVis states in its own licence documentation that with an expired System Software subscription you can still scan, but IVION Processing will not run and data can only be processed while the subscription is valid. And an export is a file, not an environment. E57 and LAS are archive formats, not something you open in a browser with a colleague on the phone.
That is the gap we fill. A CLX dataset published in GEORIZON opens in any browser, on any operating system, with no installation and no seat licence. The number of people looking at it does not change what you pay, which matters because IVION Core caps registered users at 80. Alongside the viewer you get the formats that E57 and LAS are not: COPC and 3D Tiles for streaming on the web, LAZ for the archive, JPG for the panoramas, and an API and WMTS connection so the data lands in your own GIS instead of next to it. Standardised metadata travels with it, so in five years you still know what you are looking at and how it was recorded.
NavVis positions the CLX with processed data accurate to roughly 8 mm and point clouds processed at resolutions down to 5 mm, and you can record control points during the scan to improve the absolute fit. That gets you a well controlled local result. The step after that is ours: transforming to RD New and NAP, fitting against your own control network, and checking the residuals so the scan lines up with the rest of your data rather than only with itself. For Dutch work that is the difference between a point cloud that looks right and one that a NEN 2580 area measurement or a NEN 2767 condition assessment can lean on.
The CLX is built to be a second or third device rather than the only one. The moment it sits beside a VLX, a mobile mapping vehicle or a drone, you have data from several systems that must end up in one picture. In IVION the CLX data lives on its own. We are device independent by design: CLX, VLX, MLX, Leica, Trimble, RIEGL, XGRIDS, Z+F and mobile mapping all run through the same workflow and land in the same viewer, in the same coordinate system, measurable across the boundary between indoor and outdoor. Note also that VLX and MLX still require processing units estimated up front, so the flat rate on the CLX does not extend to the rest of your fleet.
