3D layer displays 3D models on map by using latitude and longitude coordinates. Users may choose from our library of 3D models, or provide a custom model via a link to a glTF file.
If custom 3D model is not provided, Studio will create 3D ducks on map as a sample model.
The following sections reiterate the 3D models documentation, which details 3D model properties and settings.
The 3D model can be configured to best represent your use case.
Core settings for the 3D layer.
|Must be 3D to display the 3D layer.
|The dataset to use for the 3D layer.
|Specify a latitude and longitude column. Optionally, include an altitude field.
|An optional 3D model displayed for each moving object. Select from our library of 3D models or select Custom, then point to a link containing a .glb or .glTF file.
|Apply a color of your choice or apply the trail's color to the 3D model.
|Size is scaled by a factor of 2^x where x is the slider value.
|Set the model's roll (rotation on the X-axis) via numerical input or with the slider.
|Set the model's pitch (rotation on the Y-axis) via numerical input or with the slider.
|Set the model's yaw (rotation on the Z-axis) via numerical input or with the slider.
To use your own 3D model, you can provide a link to a glTF file with either a .gltf (JSON/ASCII) or .glb (binary) extension.
If you need to render many models on the map, please consider the number of polygons of your model. A model that is too detailed (containing a high number of polygons) may result in significant slowdowns of your visualization.
Note: Cross Origin Resource Sharing (CORS) must be enabled on the remote server hosting the 3D model. This allows Studio to retrieve the 3D model for your visualization.
For details on how to programmatically specify layer properties, refer to the Layer Configuration specification.
Updated about 1 month ago