LuciadFusion Release notes

It is now possible to enable/disable strict segmentation of tactical graphics. Disabling strict segmentation will limit the amount of times information is repeated on a symbol. Strictly speaking, the military standards defines that some symbols need to repeat all information for each segment of 2 consecutive anchor points. This is not very useful in realistic situations.

For example, if you create a "Main Supply Route" that matches an actual route in the real world. It could be constructed out of many thousands of anchor points, forming very small segments. Having to repeat the information thousands of times is not desired as labels will overlap with each other and can cause performance issues when zooming out far enough where you are able to see the whole symbol.

This strict segmentation can be enabled/disabled with the following methods:

• TLcdDefaultAPP6AStyle.setStrictSegmentationEnabled(boolean)
• TLcdDefaultMS2525bStyle.setStrictSegmentationEnabled(boolean)

Fixed an erroneous warning about missing cell update files in case of cell re-issues.

This was just a warning, the actual updates were applied correctly.

Note that all available update files are attempted to be applied, regardless of missing intermediate updates.

It is now possible to configure the icon type of the "Antitank Obstacles, Tetrahedrons, Dragon’s Teeth and Other Similar Obstacles" symbols in APP-6A and APP-6B. These symbols can have different icons depending on their type: "Fixed And Prefabricated", "Movable" or "Movable And Prefabricated". Unfortunately the APP-6A and APP-6B specifications do not indicate how this obstacle type should be encoded in the symbol.

The approach taken here is similar to other products: the obstacle type is encoded in the "Type Of Equipment" text modifier of the symbol. The value should either be one of the following values (casing is not important):

• POINTM: TLcdLonLatMPoint or TLcdXYMPoint
• POINTZM: TLcdLonLatHeightMPoint or TLcdXYZMPoint
• LINESTRINGM: TLcdLonLatMPolyline or TLcdXYMPolyline
• LINESTRINGZM: TLcdLonLatHeightMPolyline or TLcdXYZMPolyline
• POLYGONM: TLcdLonLatMPolygon or TLcdXYMPolygon
• POLYGONZM: TLcdLonLatHeightMPolygon or TLcdXYZMPolygon
• MULTIPOINTM: ILcdShapeList containing TLcdLonLatMPoint or TLcdXYMPoint objects
• MULTIPOINTZM: ILcdShapeList containing TLcdLonLatHeightMPoint or TLcdXYZMPoint objects
• MULTILINESTRINGM: ILcdShapeList containing TLcdLonLatMPolyline or TLcdXYMPolyline objects
• MULTILINESTRINGZM: ILcdShapeList containing TLcdLonLatHeightMPolyline or TLcdXYZMPolyline objects
• MULTIPOLYGONM: ILcdShapeList containing TLcdLonLatMPolygon or TLcdXYMPolygon objects
• MULTIPOLYGONZM: ILcdShapeList containing TLcdLonLatHeightMPolygon or TLcdXYZMPolyline objects

Due to a regression triggered by 2022.0 enhancement LF-2159, WMS GetMap requests with a non-null STYLES parameter but without an SLD could no longer be processed, resulting in a service exception report.

A new property wms.additionalParametersForViewPoolCacheKey has been added to application-fusion.common.yml to specify additional WMS request parameters that need to be taken into account for the view pool cache. This applies when you plug in a custom WMS layer factory that changes the visualization based on additional request parameters beyond the standardized WMS parameters.

• A single invalid object (NaN bounds) will no longer make binz-conversion fail.
• Sweeps no longer have inverted normals when the sweep contour is closed.
• Sweeps no longer have a dark line at the closing point of the sweep contour.
• Planes no longer fail during tesselation when the cause was a faulty normal.

The TLcdGeoJsonModelEncoder will now detect a primary key that has been declared on a supertype of a TLcdDataType. The primary key property is used as id value of the GeoJson feature, and is omitted from the properties list.

      {
        "type" : "Feature",
        "id" : "0001",
        "geometry" : { ... },
        "properties" : {
          "nonPrimaryKeyProperty" : "someValue",
          ...
        }
      }
    

Due to changes in how the GeoJson encoder handles primary keys of objects, the GeoJson output of the BinzConverter will now have the FeatureID encoded as the id member of the features, instead of having it as a property.

      {
        "type" : "Feature",
        "id" : 0,
        "geometry" : { ... },
        "properties" : { ... }
      }
    

When reading GeoJson files from Binz datasets, you can use this snippet to get the primary key property for both new and old GeoJson files:

      ILcdModel model = new TLcdGeoJsonModelDecoder().decode("path\\to\\features.geojson");
      TLcdDataType dt = ((ILcdDataObject) model.elements().nextElement()).getDataType(); // assuming the model has at least one element
      TLcdPrimaryKeyAnnotation annotation = dt.getAnnotation(TLcdPrimaryKeyAnnotation.class);
      TLcdDataProperty property = annotation != null ? annotation.getProperty() : dt.getProperty("FeatureID");
    

The samples.fusion.pointcloud.PointCloudPreprocessorTool also supports Draco compression. It can be activated through a "--compression=draco" program argument.

Added support for the IFC data format. The IFC format is an open international standard for Building Information Model (BIM) data covering entities such as buildings or facilities.

For more details, see the IFC entry in the Data Formats documentation section

LuciadRIA showing a sample IFC file

When creating a WFS service for a product consisting of multiple data sources, the corresponding WFS feature types now each have as title a combination of the product title and the data source title. Before, only the product title was used, which made it difficult to differentiate between the WFS feature types in client applications.

• TLcdEllipsoidUtil.geodesicArea(ILcdShape, ILcdEllipsoid)
• TLcdSphereUtil.geodesicArea(ILcdShape, double)
• TLcdCartesian.area(ILcdShape)

It is now possible to implement request-based SLD rendering customizations for a LuciadFusion product with an SLD style. To accomplish this, a new method has been added to the WMS API: ALcdSLDWMSGXYLayerFactory#createGXYLayer(ILcdModel aModel, ALcdWMSLayer aWMSLayer, TLcdSLDFeatureTypeStyle[] aStyle, TLcdWMSRequestContext aRequestContext) Based on the request stored in the TLcdWMSRequestContext changes can be applied to the TLcdSLDFeatureTypeStyle[] to allow for SLD rendering customizations.

It is now also possible to configure feature type styles on the server side. This is done by plugging in a custom implementation of a ILcdWMSSLDFeatureTypeStyleProvider in the ALcdOGCWMSCommandDispatcherFactory by overriding the method ALcdOGCWMSCommandDispatcherFactory#createSLDFeatureTypeStyleProvider(ServletConfig aServletConfig).

• TLcdSHPPolylineZ
• TLcdXYZFloatLine
• TLcdXYZFloatPolygon
• TLcdXYZFloatPolyline

• TLcdXYZFloatPolygon

The WMTS server now supports HTTP GET operation using RESTful encodings.

The WMTS server now supports the following additional Well Known Scale Sets: EPSG:3395, EPSG:4326, EPSG:5041 and EPSG:5042.

The WMTS and WMS services now support image/gif as output format.

• TLcdAISPolyline
• TLcdProcedureTrajectory

• TLcdAISPolygon
• ALcdDiscretizedGeoPath

• ILcdAirspace
• ILcdHelipad
• ILcdParachuteJumpArea

The forced color style is now also applied to tactical graphic symbols instead of only to icon symbols. The forced color can be inspected/edited with the following methods:

• ILcdMS2525bStyle.setForcedColor
• ILcdMS2525bStyle.getForcedColor
• ILcdAPP6AStyle.setForcedColor
• ILcdAPP6AStyle.getForcedColor

It is now possible to override the default line style of the outer frame of an icon. To support this, the following methods are added to the interfaces ILcdMS2525bStyle and ILcdAPP6AStyle:

• ILcdMS2525bStyle.setForcedFrameLineStyle
• ILcdMS2525bStyle.getForcedFrameLineStyle
• ILcdAPP6AStyle.setForcedFrameLineStyle
• ILcdAPP6AStyle.getForcedFrameLineStyle

These new methods are implemented by the existing API classes TLcdDefaultMS2525bStyle and TLcdDefaultAPP6AStyle.

• TLcdArcInfoASCIIGridModelDecoder
• TLcdBILModelDecoder
• TLcdBinzModelDecoder
• TLcdCGMModelDecoder
• TLcdDGNModelDecoder
• TLcdDWGModelDecoder
• TLcdEarthRepositoryModelDecoder
• TLcdECWModelDecoder
• TLcdGDALModelDecoder
• TLcdGeoTIFFModelDecoder
• TLcdGMLModelDecoder
• TLcdLASModelDecoder
• TLcdMrSIDModelDecoder
• TLcdNITFModelDecoder
• TLcdOBJModelDecoder
• TLcdOSGBModelDecoder
• TLcdPegasusModelDecoder
• TLcdTFWRasterModelDecoder

• TLcdArcInfoASCIIGridModelDecoder
• TLcdBILModelDecoder
• TLcdBinzModelDecoder
• TLcdCGMModelDecoder
• TLcdCSVModelDecoder
• TLcdDGNModelDecoder
• TLcdDWGModelDecoder
• TLcdGeoTIFFModelDecoder
• TLcdLASModelDecoder
• TLcdNITFModelDecoder
• TLcdOBJModelDecoder
• TLcdOpenFlightModelDecoder
• TLcdOSGBModelDecoder
• TLcdPegasusModelDecoder
• TLcdSHPModelDecoder
• TLcdTFWRasterModelDecoder

• When decoding a REP file, the model metadata contains the BIL, HDR and RSC files as supporting sources.
• When decoding a DSC file, the model metadata contains every referenced REP subset as data series, each containing their respective BIL, HDR and RSC as supporting sources.

The LuciadFusion Studio REST API specification now follows the OpenAPI 3 specification. Previously this followed the Swagger 2 specification. If you are using a tool to automatically generate an API based on the LuciadFusion Studio REST API specification then you now need to make sure it supports the OpenAPI 3 specification. The interactive console and REST API documentation have been updated to use the OpenAPI 3 version of the specification and can be used as before.

To support the upgrade from Swagger 2 to OpenAPI 3, the following dependencies were added to LuciadFusion:

Dependencies related to Springfox and the older version of Swagger have been removed.

The com.luciad.format.raster package is no longer split between multiple jars. This means that the following classes have been moved to their own sub package:

If you encounter any compile errors due to these changes, simply update the relevant import statement.

• ALcdAISGeometryFactory#createPolyline()
• ALcdAISGeometryFactory#createPolyline(ILcd3DEditablePointList aPointList)

• ALcdAISGeometryFactory#createPolygon()
• ALcdAISGeometryFactory#createPolygon(ILcd3DEditablePointList aPointList)

• TLcdEditableMS2525bUnit: This class has been deprecated in favor of the more general TLcdEditableMS2525bObject. Existing code depending on this class can be updated by using the TLcdEditableMS2525bObject.
• TLcdMS2525bShapeGXYNewController: This controller has been made deprecated in favor of TLcdGXYNewController2. Existing code depending on this class can be updated by using TLcdGXYNewController2 that is initialized with an implementation of ALcdMS2525bGXYNewControllerModel. This is illustrated in the symbology samples.
• TLcdAPP6AShapeGXYNewController: This controller has been made deprecated in favor of TLcdGXYNewController2. Existing code depending on this class can be updated by using TLcdGXYNewController2 that is initialized with an implementation of ALcdAPP6AGXYNewControllerModel. This is illustrated in the symbology samples.

The paint representations used for the direction of movement arrows have been removed from the API.

• TLspMS2525bLayerBuilder.ARROW_PAINT_REPRESENTATION
• TLspAPP6ALayerBuilder.ARROW_PAINT_REPRESENTATION

The direction of movement arrows are now painted in the TLspPaintRepresentation.BODY paint representation.

If you had a custom TLspPaintingOrder handling the ARROW_PAINT_REPRESENTATION, you can replace it with a default TLspPaintingOrder.