The 3D tiles category is experimental.
The 3D Tiles category defines a generalized representation of hierarchical geospatial data structures.
The 3D Tiles category is can represent the
Tileset Traversal Support
To start loading tiles once a top-level tileset file is loaded, the application can instantiate the
Tileset3D class and start calling
Since 3D tiled data sets tend to be very big, the key idea is to only load the tiles actually needed to show a view from the current camera position.
Tileset3D allows callbacks (
onTileUnload) to be registered that notify the app when the set of tiles available for rendering has changed. This is important because tile loads complete asynchronously, after the
tileset3D.update(...) call has returned.
To help applications process the
position data in the tiles, 3D Tiles category loaders are expected to provide matrices are provided to enable tiles to be used in both fixed frame or cartographic (long/lat-relative, east-north-up / ENU) coordinate systems:
Position units in both cases are in meters.
For cartographic coordinates, tiles come with a prechosen cartographic origin and precalculated model matrix. This cartographic origin is "arbitrary" (chosen based on the tiles bounding volume center). A different origin can be chosen and a transform can be calculated, e.g. using the math.gl