LuciadCPillar allows you to add elevation data to the map. Elevation data usually expresses the height Above Mean Sea Level (AMSL) of the terrain. This article explains how you can load and visualize elevation data.
See the related DTED article for more information.
For the best visualization performance in LuciadCPillar, we recommend that you use tiled elevation data.
See the related GeoPackage article for more information on how to decode GeoPackage data.
See the related GeoTIFF article for more information on how to decode GeoTIFF data.
You can create a custom raster model that contains elevation data. See related article for more information on how to create a custom raster model.
In 3D, the map picks up all elevation datasets that you add to it, and uses them to generate terrain: it deforms the surface of the globe according to that elevation data. During this process, LuciadCPillar takes the layer visibility and order into account:
It doesn’t include data from invisible layers in the terrain
It generates the terrain from the layers in reverse order: layers that you added at a higher index in the layer list take precedence over layers with a lower index.
If the model has multiple levels with a different level of detail, LuciadCPillar uses less or more detailed data depending on how close the camera is to the terrain. If no data is available at a location, LuciadCPillar generates terrain at elevation 0.
In 2D, the map doesn’t visualize the elevation data.
Other products, such as LuciadLightspeed, sometimes visualize elevation data in 2D using a color map. LuciadCPillar currently doesn’t support this.