On a 3D WebGLMap, you can load and viusalize elevation data. It will be visible as terrain. Other raster data will be draped on that terrain.

elevation data

Elevation data is only visible on a 3D WebGLMap. On a 2D map, the elevation data layer has no visualization.

You can make only one elevation layer visible on a map. To add multiple elevation data sources, you can combine those sources up front when you prepare your elevation coverage on the server.

Using LuciadFusion elevation data

Elevation data can be added from elevation coverage on a LuciadFusion Tile Service (LTS). Adding a model and layer for an elevation coverage is identical to adding a LuciadFusion image coverage:

  1. Create a FusionTileSetModel for the coverage.

  2. Use a RasterTileSetLayer as layer.

This is illustrated in the Visualize LuciadFusion coverages tutorial.

Using elevation data from a custom data source

You can also connect to a custom non-LuciadFusion service that serves elevation data. The data on the service must comply with a number of requirements, however:

Data structure

The elevation data must be served as a multi-leveled dataset, with a quad-tree structure. There are no restrictions for the number of columns and rows at the first level of the dataset, but each subsequent level must have 4 times as many tiles as the preceding level. The levels should appear at a regular interval. That is the case for a quad-tree dataset.

Data format

The elevation tiles must be available in the TIFF format, as single-channel 32-bit IEEE floating point numbers, or as single-channel 16-bit signed integers. Each value in the TIFF file will be interpreted as meters above the EGM96 geoid.

To create a custom elevation layer, create a RasterTileSetModel and set the dataType parameter to RasterDataType.ELEVATION.