XGRIDS Pro Guide™ / Module 9: LCC Studio

9.7 Export Formats and Sharing

Choosing the delivery format for the downstream tool, setting the conditions that have to be locked at reconstruction time, running the export, and publishing a shareable web link.

Save Your Edits Before You Export

Export writes from the saved model, not from what is on your screen. If you edit a model and export without saving first, the export contains the original, unedited model, and the work is gone. Lock in this order before you export anything.

  1. Set a clean checkpoint. In the Model Editor, Save writes to an empty folder, so the source stays intact and your saved edits become a separate copy. In the Scene Editor, use File then Save As before major edits.
  2. Make your edits in the Model Editor's Edit Mode for point-level cropping and color grading, or the Scene Editor for scene cleanup, viewpoints, and annotations.
  3. Commit them. In the Model Editor, click Save, or accept the save prompt when you leave Edit Mode. Choose Save, never Discard. In the Scene Editor, use File then Save.
  4. Verify once. Reopen the saved model and confirm the edits are there. Do this the first time on any workstation, so you never have to trust it blindly again.

Do not export straight out of an editing session and assume the edits came with it. The full editing and save mechanics are on 9.10 Model Editor Tools and 9.9 Scene Editor Tools. When in doubt, verify the saved model before you send a deliverable.

Choose the Format for the Job

The format decides which software can open the model, how large the file is, and how it renders. Pick it from what the recipient will do with the model, not from a default. One format, 3D Tiles, carries conditions that must be set during reconstruction, so read Section 3 before you process the scan rather than after.

FormatBest forNotes
LCC2The default for XGRIDS ecosystem delivery and further editingSmaller, smoother, and faster than LCC, and the native editable format of the Model Editor. Loads directly in mainstream 3DGS platforms such as SuperSplat and Arrival.Space.
LCCCompatibility with older LCC tools and workflowsLegacy proprietary format, 70 to 90% smaller than PLY. Integrates with the XGRIDS Unity and Unreal toolkits. Convert to LCC2 for current work.
PLYThird-party 3DGS viewers, broadest open-source compatibilityUniversal point format, 5 to 10 times larger than LCC. Export at selectable precision. Works with the Unreal and Unity 3DGS plugins.
USDNVIDIA Omniverse and Isaac Sim, with ray-traced renderingThe route into simulation and synthetic-data workflows. 3DGRUT toolchain, Omniverse Kit 110.0 or higher, Isaac Sim 5.0 or higher. Does not render in Blender, Maya, Houdini, or Cinema 4D.
3D TilesWebGIS and digital-twin platforms such as Cesium and ArcGISOGC 3D Tiles 1.1. Two versions are offered at export. Conditions in Section 3.
Mesh (OBJ / PLY)Polygon mesh for DCC software and game enginesTriangulated mesh derived from the Gaussian model. Geometry only, no texture. Exports alongside LCC.

LCC2 is the editable format. The Model Editor works in LCC2, and opening a legacy LCC or a PLY file upgrades it automatically on import. If you plan to edit, crop, or color grade after reconstruction, deliver and archive in LCC2. See 9.10 Model Editor Tools.

The full export set requires the Premium edition. The free edition covers Single Model reconstruction, local viewing, and publishing. Export to LCC, LCC2, PLY, USD, and 3D Tiles is a Premium feature, alongside Map Fusion, Aerial-Ground Fusion, Aerial Reconstruction, HD Enhancement, and Spatial Recognition. Confirm the edition on the workstation before you quote a format as a deliverable.

Conditions You Set at Reconstruction Time

3D Tiles cannot be produced from just any finished model. Its two conditions are set while the scan reconstructs, not at export. Verify both before you click Start, because the only fix afterward is to reprocess, and one of them cannot be fixed at all without returning to the site.

  • Absolute coordinates. The scan must carry RTK or control point data. A model processed without georeferencing has no real-world coordinates and cannot export to 3D Tiles. Georeferencing cannot be added after the scan, so this is a field decision, not a workstation one.
  • 4 million Gaussian points or fewer. Models above this count cannot export as 3D Tiles. If WebGIS delivery is a firm requirement, set Maximum Gaussian Points at or below 4 million during reconstruction.

Confirm WebGIS delivery before the site visit, not after processing. Both conditions are cheap to meet up front and expensive to miss. A finished model that was never georeferenced is a re-scan, not a re-export.

Export Procedures

Select the completed model card in My Models, click the ... button in the upper-right corner of the card, and choose Export. Pick the format in the dialog and confirm. LCC2 and 3D Tiles each offer an additional choice inside that dialog.

Export LCC2

  1. Open Export from the model card and select LCC2 in the File Format dropdown.
  2. Choose the compression format. SOG gives the smallest file, an 8 to 26 times reduction, and is the default for the LCC ecosystem. SPZ gives about a 10 times reduction and is compatible with the Niantic and Scaniverse ecosystem. A single LCC2 file uses one compression format; the two are never mixed.
  3. Check additional options as needed. Include Mesh adds collision data. Spatial Recognition results are included only if that feature was enabled during reconstruction.
  4. Choose the save location and confirm.

Export 3D Tiles

  1. Open Export from the model card and select 3D Tiles.
  2. Select the version. The current version uses SPZ v2 compression for smaller files and cleaner rendering, and needs a recent Cesium build. The legacy version targets older Cesium deployments. The dialog states the requirement for each and shows a prompt if you select the legacy option, so match the choice to the version of Cesium your client actually runs and confirm it against that prompt.
  3. Choose the save location and confirm. The output directory contains a tileset.json entry file and several .glb tile files. Deploy the whole directory to Cesium to load it.

Ask the client which Cesium version they run before you export. The wrong version choice loads as an error on their side, not yours, and you will not see it during your own check. Get the number in writing with the rest of the delivery spec.

Convert between formats

LCC Studio includes a Converter for batch format work. It converts between 3DGS formats, including batch conversion to LCC2, and outputs to the third-party ecosystem formats 3D Tiles and USD. Use it when a finished library needs to move to a new delivery format in bulk rather than one model at a time.

Upgrading a single legacy LCC model. Right-click the model in My Models and choose Convert to LCC2. This is a one-way upgrade and cannot be rolled back, though legacy LCC files still open and view normally. After conversion, all later operations use the new format.

Creator Data

After reconstruction completes, LCC Studio gives you access to the underlying capture assets alongside the finished model. This is available at no additional cost and covers data captured with the L2 Pro, K2, and PortalCam.

Creator Data is what downstream simulation, photogrammetry, and machine learning pipelines need, and it is not something the finished 3DGS model alone can supply. If you are delivering into NVIDIA Omniverse or Isaac Sim, training a model, or handing a dataset to a research or robotics team, this is the payload they will ask for.

AssetWhat it gives the recipient
Original imagesThe unmodified capture frames, straight off the device.
Undistorted imagesThe same frames with lens distortion removed, which is what most photogrammetry and training pipelines expect as input.
Invalid masksSupplied for both the original and undistorted image sets, marking regions to exclude from processing.
Camera intrinsic and extrinsic parametersSupplied for both image sets. Defines where each frame sits in space and how the lens projects, which is what makes the images usable for reconstruction elsewhere.
Device posesThe scanner trajectory through the capture.
Optimized laser point cloudThe processed LiDAR geometry underlying the model.

Scope this into the contract before you deliver it. Creator Data is a substantially richer dataset than a viewable model, and it carries different licensing weight, particularly where the recipient intends to train on it or redistribute derivatives. Agree the scope and the license in writing rather than including it as a courtesy attachment.

Publish and Share a Web Link

Publishing uploads the model to XGRIDS cloud hosting and returns a link that opens in any modern browser with no install. It is the fastest way to put a finished model in front of a client, and it does not replace local export, since the model is still retained locally.

Access control

OptionBehavior
Password-Free SharingAnyone with the link can open the model, no password.
Encrypted SharingPassword-protected. Set a custom password or use a system-generated one.
  1. Open File, then Publish, or use the quick-publish button on the model card in My Models.
  2. Choose Password-Free or Encrypted and add a description with context such as address, project name, and scan date.
  3. Click Create to generate the link, then Share to copy the link and password.

To open a published model yourself, use View Online from the model card menu. Reopen Publish Management from the same menu for secondary changes: edit the URL suffix, switch between Password-Free and Encrypted, change the password, update the description, or list and delist the link without deleting the local file.

Confirm data-handling requirements before publishing. Web publishing needs an internet connection and an active XGRIDS account, and it places the model on cloud hosting. For clients with data-sensitivity requirements, deliver by local export in LCC2 or PLY instead of a hosted link.

©2026 Alpine Reality Capture LLC  •  XGRIDS Pro Guide™  •  Site Disclaimer