Data Formats:
OGC 3D Tiles
The OGC 3D Tiles protocol is designed
for streaming and rendering massive 3D geospatial content such as
Photogrammetry, 3D Buildings, BIM/CAD, Instanced Features, and Point Clouds from a server to a client.
It defines a hierarchical data structure and a set of tile formats which deliver renderable content.
In LuciadLightspeed, we support 3D tiles that contain a payload with:
- Point cloud data (the
PNTS format)
- Reality meshes (the
B3DM or Batched 3D Model format)
The OGC 3D Tiles format describes the structure of a 3D tile hierarchy. It consists of:
-
A metadata format that describes the 3D scene.
It is encoded as JSON, and is typically named
tileset.json.
It can link to other tileset.json files or data files.
-
The data files containing the tiles.
Each tile contains a payload.
In LuciadLightspeed, the payload consists of either a point cloud in PNTS or a textured 3D mesh in a Batched
3D Model (B3DM).
For the encoding of the mesh data itself, the OGC 3D Tiles specification uses glTF.
For more information about glTF, see
https://www.khronos.org/gltf/.
Each tile in a tileset can also contain metadata such as:
- A bounding volume.
- The geometric error, which represents the visual error incurred by displaying a parent tile instead
of its (more detailed) children.
- A list of child tiles.
Basics
How-to guides
Frequently asked questions
Main classes