LuciadRIA Release notes

• Korean Datum 1985
• Macao 1920

WMTS support is extended to handle Tile Matrix Sets of which the first Tile Matrix has more than 8 columns and 8 rows, only in the case of a WebGL-enabled maps.

RasterTileSetLayer can now display a red hatched rectangle instead of any actual imagery data when zoomed out to a fair distance from the data. More information can be found in the article Why does my imagery layer show a red (hatched) rectangle on a WebGL map?

You can customize the style of the raster outline drawn when zoomed out far from the data. For more information please refer to the article Learn how to visualize and style raster data using a RasterTileSetLayer. and the API documentation of RasterStyle, where you can find the new fillStyle and lineStyle properties.

You can now use complex stroke lines with a width in world units, for example meters. See the ComplexStrokedLineStyle.uom property for details.

You can also scale your icon or text decorations in world size, see the size property on their factory method options.

World-sized complex stroke lines are not supported in a non-WebGL Map.

• A sample's package.json now mentions "type": "module".
• A sample's tsconfig.json now sets "moduleResolution": "nodenext".
• Imports in samples now also contain the file extension (.js or .jsx)

The creation of WMTSTileSetModel now can create a RasterTileSetModel that does not have a quad-tree tile set structure.

Users of a WebGL enabled map are not affected by this change as the rendering supports this type of tile set structures.

Users of a Canvas map are affected as this map only supports raster tile sets that have a quad-tree structure. You need to update the call for the WMTS model creation to restrict use to Tile Matrix Sets that have a quad-tree. You can do this by adding the option useQuadTreeOnly: true in the WMTSTileSetModelCreateOptions when calling the method createFromURL or createFromCapabilities.

The RasterTileSetModel can now represent tile sets that are not a quad-tree. It allows to create tile sets where the bounds on different levels are not exactly the same and for which the number of rows and columns is not a power of two with respect to the top level. The bounds for each level in the tile set must be aligned in the top-left corner.

The constructor options for the following raster models are affected by this change. They now use a new way to express the tile set structure.

• RasterTileSetModelConstructorOptions
• URLTileSetModelConstructorOptions
• WMTSTileSetModelConstructorOptions
• FusionTileSetModelConstructorOptions

To maintain backward compatibility these constructor options have an equivalent with Deprecated in their name, i.e., RasterTileSetModelConstructorDeprecatedOptions for RasterTileSetModelConstructorOptions. When using TypeScript type declarations you may need to update your code to use the deprecated options type.

You can now use world-sized lines for non-draped 3D lines. Before, these were always draped on terrain.

The behavior is now in line with other shape painting: the line will be draped if you explicitly enable draping in your style, or if the line is 2D (Z=0 and depth=0). Otherwise, the line is not draped.

If you have 3D lines with a world size, these were always draped before, so if you want to keep that behavior, specify draped: true in your ShapeStyle.

You can now use complex stroke lines for non-draped 3D lines. Before, these were always draped on terrain.

The behavior is now in line with other shape painting: the line will be draped if you explicitly enable draping in your style, or if the line is 2D (Z=0 and depth=0). Otherwise, the line is not draped.

If you have 3D lines with complex strokes, these were always draped before, so if you want to keep that behavior, specify draped: true in your ShapeStyle.

In addition, the width of draped complex strokes is now much more stable, also when looking at the horizon.

Non-draped pixel-sized 3D lines with complex strokes are oriented towards the viewer. Draped strokes, or world-sizes strokes are never screen-oriented.

Keep in mind that certain deformations of your pattern is expected, particularly when looking along the line.

Example of complex strokes on 3D lines.