An OGC 3D Tiles service can serve OGC 3D Tiles data directly.
You can add other 3D data formats to an OGC 3D Tiles service, but those are pre-processed to the OGC 3D Tiles format before you can serve them.
If you want to serve 3D mesh or point cloud formats, you can activate Draco compression for the pre-processing of these formats. In the case of 3D mesh data, for instance, Draco mesh compression techniques reduce the size of the GLTF part in each B3DM file. For more information about Draco, see https://google.github.io/draco/. |
Because an OGC 3D Tiles service can only serve one root tileset, a service can only contain 1 product.
3D Data format | Type | Notes |
---|---|---|
Autodesk Revit |
CAD |
Converted into 3D mesh format and pre-processed before serving. Draco mesh compression is possible. |
Binz |
CAD |
Converted into 3D mesh format and pre-processed before serving. Draco mesh compression is possible. |
E57 |
Point cloud |
Pre-processed before serving. Draco point cloud compression is possible. |
GLB |
3D mesh |
Pre-processed before serving. Draco mesh compression is possible. |
IFC |
CAD |
Converted into 3D mesh format and pre-processed before serving. Draco mesh compression is possible. |
LAS |
Point cloud |
Pre-processed before serving. Draco point cloud compression is possible. |
LAZ |
Point cloud |
Pre-processed before serving. Draco point cloud compression is possible. |
OBJ |
3D mesh |
Pre-processed before serving. Draco mesh compression is possible. |
OGC 3D Tiles 1.0 |
3D Tiles |
Served directly. |
OGC 3D Tiles 1.1 |
3D Tiles |
Served directly. |
OSGB |
3D mesh |
Pre-processed before serving. Draco mesh compression possible. |