Documentation menu

Gaussian splats (3D Tiles)

Gaussian splats as one 3D Tiles tileset of GLB tiles with KHR_gaussian_splatting, SPZ-compressed (a tileset.json with its tiles, or a single .3tz archive). The tileset must be in the dataset's coordinate system, or carry it in Esri's ESRI_crs extension as Esri SURE writes it; nothing is reprojected. A folder is packed into one .3tz.

A scene as 3D Gaussian splats (a photogrammetry or scanner capture trained into splats) delivered as a 3D Tiles tileset whose tiles are GLB files with the KHR_gaussian_splatting extension, SPZ-compressed, as Esri SURE exports a "Gaussian splat layer". The tileset is shown as delivered; a folder is first packed into one .3tz archive.

Folder layout#

Either a folder with the tileset in it:

<dataset bucket>/
└── utrecht/                     any name, or none
    ├── tileset.json             the root of the tileset
    ├── 1359_4548/               blocks with external child tilesets, if your exporter writes them
    │   └── entry_relative/s_0_0_0_e_256_128_32.json
    ├── L0/ … L6/                the tiles
    │   └── node_3.glb
    └── …

or one archive:

<dataset bucket>/
└── utrecht.3tz                  a .3tz with tileset.json at its root

The tileset may sit at the top of the bucket or in a folder of any name and depth. Its root file must be called tileset.json; files below it, external child tilesets included, belong to it.

One tileset per dataset. Two tilesets side by side fail the delivery: deliver each as a dataset of its own.

Nothing else in the bucket. .obj and .zip files fail the delivery (documents in Reports/ excepted): deliver OBJ exports as a mesh, and a zipped tileset unzipped or as a .3tz.

Upload with the file manager, rclone or the aws command line. Some upload tools put a / in front of every name (a folder with no name); those files cannot be read, and the delivery fails.

The tileset#

3D Tiles 1.0 and 1.1 are both read, with an explicit tile tree or external child tilesets. Only the root tileset.json and one tile it names are read during indexing; the other tiles are not downloaded.

The tiles must be GLB files (.glb) holding Gaussian splats: their glTF declares KHR_gaussian_splatting and must be compressed with SPZ (KHR_gaussian_splatting_compression_spz_2, or Cesium's older KHR_spz_gaussian_splats_compression; SPZ versions 1 to 3). Uncompressed splats are not shown. A mesh tileset belongs in a mesh dataset, and point clouds (.pnts) in a point cloud dataset; glTF JSON (.gltf), Batched 3D Models (.b3dm), instanced (.i3dm) and composite (.cmpt) tiles are not shown.

A .3tz is the tileset in one ZIP file, with tileset.json at its root (entries stored or deflated). It is read in place, by ranged reads. A delivered folder is packed into one .3tz next to its tileset.json, and the loose files are removed once the archive has been read back; a delivered .3tz is kept as it is.

  • The delivery must be one tileset: one tileset.json (the shallowest one in the bucket; any below it, such as external tilesets per block, belong to it) or one .3tz archive. Two tilesets side by side fail the delivery, and so does a delivery whose root file is named anything else, such as scene.json. A folder is packed into one .3tz, which cannot hold another archive: a .3tz inside the tileset's folder fails too. So does any .obj or .zip outside Reports/: OBJ exports are a mesh, a zipped tileset is not read (unzip it, or deliver it as a .3tz), and a source archive left beside the tileset would be packed into it.
  • The root tileset.json must be a 3D Tiles tileset: JSON with an asset.version and a root tile. In a .3tz it is read from the archive's central directory, so the archive must be a ZIP with tileset.json at its root, stored or deflated. A file whose stored name begins with / (an empty folder name, which some upload tools write) is listed but cannot be read, and fails here too.
  • The root tile must place the tileset in plan: with Esri's ESRI_crs extension, the root's bounding volume and transform in that extension; without it, the root's own. Either must be a box or a sphere (with its transform, if any), and its outline in plan is the dataset's footprint. A region is longitude and latitude on WGS 84 and fails. A tileset whose ESRI_crs names a CRS but gives the root no bounding volume in it fails too.
  • The tileset must lie where the dataset's coordinate reference system is used. Nothing is reprojected. A tileset with Esri's ESRI_crs extension (earth-centred tiles, the tree repeated in a projected CRS, as Esri SURE writes it) must name the dataset's CRS there (wkid, e.g. 28992 for RD New), and its footprint in that CRS is compared with the CRS's registered area of use, with a 5% margin. A tileset without the extension is compared as written: one in earth-centred coordinates or in a local frame lies far outside the area and fails. For a CRS without a registered area of use only the ESRI_crs code is checked.
  • With Esri's ESRI_crs extension, its vcsWkid should name the dataset's vertical coordinate system (5709, NAP height, in an RD New + NAP dataset). Heights are not converted: a tileset exported with ellipsoidal heights is drawn tens of metres too high (about 43 m above NAP in the Netherlands). A missing vcsWkid, or another vertical system, warns. (a warning, not an error)
  • Every tile content the root tileset.json names must be a GLB (.glb) or an external tileset (.json): glTF JSON tiles (.gltf), Batched 3D Models (.b3dm), point clouds (.pnts), instanced models (.i3dm) and composite tiles (.cmpt) fail. The first GLB the root file names is opened, in the folder or inside the .3tz, and must declare KHR_gaussian_splatting (a mesh tileset belongs in a mesh dataset) and SPZ compression (KHR_gaussian_splatting_compression_spz_2, or the older KHR_spz_gaussian_splats_compression): the viewer draws nothing of uncompressed splats. Only the root file is read: content named in external tilesets is not checked.

Coordinate reference system#

Nothing is reprojected. The tileset must be placed in the dataset's coordinate system in one of two ways:

  • With Esri's ESRI_crs extension, as Esri SURE writes it: the tiles in earth-centred coordinates, and the same tree again in a projected CRS in the extension. The extension's wkid must be the dataset's CRS (for the Netherlands, 28992, RD New), and the root's bounding volume there gives the footprint. Its vcsWkid should be the dataset's vertical system (5709, NAP height): heights are not converted, so a tileset exported with ellipsoidal heights is drawn about 43 m too high, and a missing or different vcsWkid is a warning.
  • Without it, the tileset's own coordinates, after its root transform, must be the dataset's CRS, heights included, as for a mesh. In Cesium ion that is a tileset that is not georeferenced.

The root's bounding volume (in ESRI_crs, or its own) must be a box or a sphere. Its outline in plan is the dataset's footprint, and it must lie where the dataset's CRS is used. A tileset in earth-centred coordinates without ESRI_crs lies thousands of kilometres away and fails. See Coordinates.

Ingest parameters#

None.

What you get back#

The tileset as one .3tz archive: a delivered folder is packed into tileset.3tz beside its tileset.json, and a delivered archive is kept. One indexed tileset, in a set named splats, with the footprint of its root bounding volume as the dataset's coverage.

A tileset carries no capture dates. Enter the acquisition period when you submit the delivery, or at checkup; the dataset cannot be accepted without it.

Re-running is safe — see Re-running is safe.

Common failures#

SymptomCause
"no tileset.json or .3tz archive"The root file has another name, such as scene.json
"the delivery holds 2 tilesets"Two tilesets side by side; deliver them as two datasets
"is listed but cannot be read"The files were uploaded with a / in front of their names
"its root bounding volume is a region"The tileset was exported on the globe (WGS 84)
"its ESRI_crs extension places the tileset in EPSG:…"The tileset's ESRI_crs names another CRS than the dataset's
"far outside where EPSG:… is used"The tileset is in earth-centred coordinates without ESRI_crs, or in a local frame
"which a Gaussian splat dataset does not show"The tileset holds .gltf, .b3dm, .pnts, .i3dm or .cmpt tiles
"does not declare KHR_gaussian_splatting"The tiles are a mesh, not splats
"its splats are not SPZ-compressed"The splats were exported without SPZ compression
"sits beside"A .3tz inside the tileset's folder: deliver the tileset once, as a folder or as an archive
"OBJ and .zip files are not read"OBJ exports (a mesh), a zipped tileset, or a source archive left in the bucket
"names no vertical coordinate system" (warning)The ESRI_crs has no vcsWkid: check that the heights are in the dataset's vertical system