LuciadRIA Release notes

LuciadRIA now contains a sample that illustrates how to handle IFC datasets. The geometry is loaded as OGC 3D Tiles, the metadata information is loaded via a GeoJSON dataset. The sample shows how to combine geometry and metadata into a single application.

Screenshot of the IFC sample application.

LuciadRIA now supports draping of 2D raster and vector data on OGC 3D Tiles data. You can use the new DrapeTarget enumeration on objects such as a ShapeStyle, IconStyle and RasterStyle to indicate whether the data needs to be draped on 3D Tiles and/or on terrain. You can also choose which 3D Tiles layers need to be taken into account for draping by means of a new isDrapeTarget flag on TileSet3DLayer. The use of this API is demonstrated in the "OGC 3D Tiles" sample, which has been extended with a walking tour draped on top of the Marseille 3D tiles mesh data. For more information, see the Draping on 3D Tiles article.

An area of interest that is draped on an OGC 3D Tiles layer with a city model.

• For point symbolizers:
  • The use of SVG images through the icon provider.
  • The use of UOM-aware stroke widths for marks.
• For line symbolizers:
  • The use of line joins (mitre, round or bevel) and line caps (butt, round or square) in strokes.
  • The combination of a stroke with a graphic stroke (dash-array, graphic rotation).
  • The use of displacement and anchor points for the graphics in a graphic stroke.
  • The use of perpendicular offset without gaps or overlaps at the line joins.
  • The use of UOM-aware graphic fill for strokes.
• For polygon symbolizers:
  • The use of the same improved stroke support as for line symbolizers.
  • The use of UOM-aware graphic fills.
  • The use of UOM-aware displacement.
  • The use of UOM-aware perpendicular offset.

For a complete overview of the supported SLD styling capabilities, see the SLD styling - Supported versions and capabilities article.

A park area from the OGC Symbology Encoding sample, combining several of the line and polygon styling improvements. A first polygon symbolizer uses a black fill with a displacement to apply a shadow effect. A second polygon symbolizer defines the park area’s fill and outer stroke, which is a combination of a dashed stroke and an icon with a shifted anchor point. A third polygon symbolizer with a negative perpendicular offset is used to draw the smaller green area on top.

• SelectController
• ContextMenuController
• PanController
• RotateController
• ZoomController
• HoverController

You can now add bloom to shapes. Bloom is a glow effect that you can use to make shapes appear very bright, and draw focus to them.

Airspaces in the Trajectory sample with Bloom enabled (left) and bloom disabled (right).

For more information, see BloomStyle and BloomEffect. You can also read the "Bloom effect" section in Configuring WebGL Map effects.

      // Let TS compiler know that feature's shape is a point and its properties can contain the population field.
      interface CityProperties { name: string; population?: number};
      const cityFeature = new Feature<Point, CityProperties>(point, { name: 'Leuven'});
      // Let TS compiler know that the store can accept features with a polyline or a polygon shape and any properties.
      const store = new MemoryStore<Feature<Polyline | Polygon, FeatureProperties>>(data: [polylineFeature]);
    

• libcurl: updated to version 7.86.0
• openssl: updated to version 1.1.1s
• zlib: updated to version 1.2.13