public final class Ogc3DTilesModelDecoder extends Object
ITileSet3DModel
implementation that can read OGC 3D Tiles data.
See Ogc3DTilesModelDecoder#decode
for more details.
Modifier and Type | Class and Description |
---|---|
static class |
Ogc3DTilesModelDecoder.Options
Options for decoding OGC 3D Tiles data. |
Modifier and Type | Method and Description |
---|---|
static ITileSet3DModel |
decode(String source)
An OGC 3D Tiles model connects to a 3D tile service to retrieve tiles for a
TileSet3DLayer . |
static ITileSet3DModel |
decode(String source,
Ogc3DTilesModelDecoder.Options options)
An OGC 3D Tiles model connects to a 3D tile service to retrieve tiles for a
TileSet3DLayer . |
@NotNull public static ITileSet3DModel decode(@NotNull String source) throws IOException
TileSet3DLayer
.source
- the OGC 3D tiles endpoint url or the path to the entry point fileIOException
- when decoding the OGC 3D Tiles data fails.decode(const std#string&, const Options&)
@NotNull public static ITileSet3DModel decode(@NotNull String source, @NotNull Ogc3DTilesModelDecoder.Options options) throws IOException
TileSet3DLayer
.
File | Entry point | Description |
---|---|---|
tileset.json/root.json | x | File containing the root tile metadata as well as links to the sub-tiles/content. |
*.json | Files containing sub-tile metadata as well as links to its sub-tiles/content. | |
*.b3dm | File containing Batched 3D Model data. See the B3DM documentation for more information about this file. | |
*.pnts | File containing batched Point Cloud data. See the PNTS documentation for more information about this file. |
tileset.json
file entry point, with full metadata support, including property values and ranges.
tileset.json
.
tileset.json
is not supported directly, but can be achieved using expressions, based on StyleExpressionFactory
.
style expressions
that make use of attributes
. An attribute represents additional metadata for each of the points in the point cloud. Typical attributes are intensity, color, height, etc...
When attributes are available, they can be discovered by manually inspecting the top-level tileset.json
or root.json file
. That file can contain a section called "properties". It's a list of attribute names, with (optionally) range indications.
This is an example of the attributes that you can find in this file:
"properties" : { "Intensity" : { "minimum" : 0.0, "maximum" : 65535.0 }, "Classification" : { "minimum" : 2.0, "maximum" : 4.0 }, "ReturnNumber" : { "minimum" : 1.0, "maximum" : 7.0 }, "Height" : { "minimum" : 29.02975082397461, "maximum" : 116.85025024414062 } }Additional properties can be discovered by manually inspecting the data itself. More concretely, b3dm files contain a header section that describe these properties. This is an example of the attributes that you can find in a b3dm file:
{ "fid": { "componentType": "INT", "type": "SCALAR", "byteOffset": 0 }, "height" : { "componentType" : "FLOAT", "type" : "SCALAR", "byteOffset" : 24 } }
source
- the OGC 3D tiles endpoint url or the path to the entry point fileoptions
- options for decoding OGC 3D Tiles data, for example an optional custom loader implementation to fetch the OGC 3D Tiles resources.IOException
- when decoding the OGC 3D Tiles data fails.