LuciadRIA Release notes

Symbology Encoding (SLD): added the possibility to use a Luciad specific extension of the WellKnownName of a Mark icon.

It was already possible to use a custom function to fetch the WellKnownName of a Mark in your SLD file. Now you can use such a custom function to return a WellKnownName that starts with a prefix LuciadIconProvider://. When encountering such a WellKnownName, the SLD engine will call upon the IconProvider to fetch the icon, giving you full control of the actual icon. The advantage of this new functionality is that you can create all sorts of feature-dependent icons.

More information and details for a specific use-case can be found in "LuciadIconProvider://XXX" mark

• It is now possible to configure the symbol frame color to be used for icon symbols. This color can be configured using MilSymStyle.symbolFrameColor. The default value is #000000 (black). This custom frame color is ignored in some specific cases where the frame color indicates the affiliation of the symbol.
• It is now possible to configure the alternate fill color for partially filled icon symbols. This color can be configured using MilSymStyle.alternateFillColor. The default value is rgba(0,0,0,0) (transparent).

Military Symbol icon styling options.

You can now create cartesian references from WKT using ReferenceProvider.parseWellKnownText, using the LOCAL_CS WKT tag.

The WKT for a cartesian reference should have a name, local datum, unit and 2 or 3 axes. Here is an example:
LOCAL_CS["MyCartesian",LOCAL_DATUM["Unknown",0],UNIT["m",1.0],AXIS["x",EAST],AXIS["y",NORTH],AXIS["z",UP]]

It is now possible to do transformations (via TransformationFactory.createTransformation) between a 2D and 3D cartesian reference, if the 2D axes are compatible. In that case, only a 2D transformation is done, and the z value is left untouched.

As a consequence, you can now load 2D cartesian data on a 3D cartesian map, and vice-versa.

Note that you can make such references using ReferenceProvider.createCartesianReference, or using the short-hand LUCIAD:XY and LUCIAD:XYZ identifiers in ReferenceProvider.getReference.

The minScale and maxScale properties on Layer are now applied also on maps with a cartesian reference.

If your cartesian map has non-uniform X/Y axes, the minScale and maxScale properties are ignored since they are ambiguous. For example, if your map has an X axis with length unit in meters, and a Y axis with a temperature unit in degrees Celsius, a single scale of 1:100 has no meaning.

You can now use world-sized styling on cartesian maps, as long as the unit of measure is compatible with the X and Y axis of the map reference.

In addition, if world-sized styling is not supported, a warning will be logged and a fall-back width is used, instead of failing to paint entirely.

You can now use WFSFeatureStore with WFS services that contain data in a local cartesian reference.

In that case, the WFS reference should be a LOCAL_CS WKT, and the the store will have a CartesianReference. You can then use this store directly on a cartesian map, for example one with LUCIAD:XY as map reference.

Spatial loading of FeatureLayers on a map with a 3D cartesian reference failed, this is now resolved.

Note that spatial queries are 2D, so the query bounds will be projected on the Z=0 plane.

• TransformationChanged at any change of Tileset3DLayer.transformation
• MeshStyleChanged at any change of Tileset3DLayer.meshStyle
• PointCloudStyleChanged at any change of Tileset3DLayer.pointCloudStyle
• OutlineStyleChanged at any change of Tileset3DLayer.outlineStyle
• SelectedOutlineStyleChanged at any change of Tileset3DLayer.selectedOutlineStyle
• OcclusionStyleChanged at any change of Tileset3DLayer.occlusionStyle
• SelectedOcclusionStyleChanged at any change of Tileset3DLayer.selectedOcclusionStyle
• QualityFactorChanged at any change of Tileset3DLayer.qualityFactor
• PerformanceHintsChanged at any change of Tileset3DLayer.performanceHints

Statistics for HSPC are now available from the HSPCTilesModelDescriptor.properties. These properties are only defined if the pointcloud contains statistics.

WebGLMap now supports display scaling. This allows for sharp and crisp map rendering on high resolution (hiDPI) displays.

More information can be found in the Display scaling (hiDPI) in LuciadRIA guide.

Symbology Encoding (SLD): added support for the vendor option 'inclusion'.

You can now use the vendor option 'inclusion' in your SLD style files to differentiate between styling for legend entries and styling for regular maps. You can provide a `painterType` when creating a Symbology Encoding painter, to indicate which styles should be used.

More information can be found in SLD legend, vendor option 'inclusion' - Usage and examples

A Legend tool was added to the LuciadRIA Toolbox. See toolbox/ria/legend/README.md for more information. Basic usage is illustrated in both the LuciadRIA Symbology Encoding sample and the LuciadRIA Smart Data Loading sample.

You can now set the reference of WebGLMap after the map has been created, instead of only at construction time. Please refer to WebGLMap.reference for more information and restrictions.

All samples that can be run in multiple references now have a new button in the top left that allows users to change the reference of the map, without having to recreate the map. The Dual map sample now also sets the references on the maps, instead of recreating them.

Added support for the BezierCurve geometry. You can now create, visualize, and edit both quadratic and cubic Bézier curves. For more details on how to create these shapes, please refer to ShapeFactory.createQuadraticBezierCurve or ShapeFactory.createCubicBezierCurve.

The Create and Edit sample allows you to interactively create and edit these shapes.

LuciadRIA now supports RESTful encoding for WMTS GetCapabilities and GetTile requests.

When fetching the capabilities document, you can set the preferred WMTSRequestEncoding by using WTMSCapabilitiesFromURLOptions#preferredRequestEncoding.

When creating a WMTSTileSetModel from a URL or from a capabilities document, you can set the preferred WMTSRequestEncoding by using WMTSTileSetModelCreateOptions#preferredRequestEncoding. When creating the WMTSTileSetModel directly, you can set the required WMTSRequestEncoding by using WMTSTileSetModelConstructorOptions#requestEncoding.

• GPU instancing with the EXT_mesh_gpu_instancing extension
• Allow associating metadata with vertices or texels with the EXT_structural_metadata extension.
• Loading of point clouds from GLB files

Improved the tessellation (polygon fill) of non-planar polygons. In some cases, these polygons would not be filled properly.

The improvement applies to both FeatureLayer.performanceHints settings: PREFER_QUALITY or PREFER_PERFORMANCE.

Note that polygons are still expected to be mostly planar and not self-intersecting. If not, it's possible certain parts are not filled properly.

Fixed an issue with shape visualization where the latitude element of geodetic points was outside the valid range of [-90, 90] degrees.

Now, when creating a Point, Polyline, or Polygon, the latitude element of geodetic points is automatically clamped to the valid range of [-90, 90] degrees, establishing accuracy from the start.