LuciadFusion Release notes

The utility class TLcdShapeUtil was added to the API. This class contains utility method to created rounded lines.

• TLcdShapeUtil.round(ILcdModelReference, ILcdPolyline, double): Use this method to created a rounded version of a ILcdPolyline
• TLcdShapeUtil.round(ILcdModelReference, ILcdPolygon, double): Use this method to created a rounded version of a ILcdPolygon

Example usage of these methods can be found in the complex strokes Lightspeed sample. This sample has been adjusted so rounded lines used in the Cartography layer. The lines are rounded using a custom ALspStyleTargetProvider which provides rounded lines for every ILcdPolyline or ILcdPolygon in the model. This ALspStyleTargetProvider is located in samples.lightspeed.style.strokedline.LayerFactory.RoundedLineStyleTargetProvider.

Resolved a caching issue which caused the .binz input files to remain open after decoding them with the TLcdBinzModelDecoder. This resulted in a number of issues when manipulating the files.
For example:

• The .binz file could no longer be removed form disk.
• When replacing an existing .binz file with a new version, this could result in IOExceptions being thrown when decoding the new version of the .binz file.

• the placement is now dynamic within a WM(T)S server environment, making sure that each generated map or tile shows the label of the visible curved paths (such as streets or rivers); this avoids that labels disappear when zooming in.
• the vendor option repeat=valueInPixels is now supported to repeat labels along a curved path, taking into account the specified pixel value to be used between subsequent labels; repeating labels can be useful to improve the label readability for long curved paths.

• Category 30: By default, the Calculated Track Altitude field is used. This can be changed to the Calculated Track Flight Level field by setting the System property com.luciad.format.asterix.cat30.useCalculatedTrackFlightLevel to true.
• Category 62: By default, the Calculated Track Geometric Altitude field is used. This can be changed to the Calculated Track Barometric Altitude field by setting the System property com.luciad.format.asterix.cat62.useCalculatedTrackBarometricAltitude to true.

You can now re-throw cell warnings in your error handler (ILcdS57InvalidCellExceptionHandler#handleCellWarnings), which will make sure the cell is not loaded.

If you disable TLcdS57UnifiedModelDecoder#ignoreInvalidCells, decoding the entire catalog will fail if you re-throw warnings or errors.

By default, the warnings are logged and not re-thrown, so the cell is still loaded.

The S-57 and S-63 decoders now issue a warning when we detect that certain updates are missing. This can happen for example when you have cell GB5X01SW.000 and update file GB5X01SW.002, but not the intermediate update file GB5X01SW.001.

You can inspect the warning either through TLcdS57ModelDescriptor#getWarnings or by registering an error handler on your decoder and implementing ILcdS57InvalidCellExceptionHandler#handleCellWarnings.

If you want to fail the decoding of the particular cell, you can propagate the warning by re-throwing it in ILcdS57InvalidCellExceptionHandler#handleCellWarnings.

You can now add custom service types to LuciadFusion. Adding a custom service type allows you to serve geospatial data managed in LuciadFusion Studio using a custom protocol. As a result, you gain access to a vast range of options for getting your data to clients. Custom service types can be used in addition to the built-in service types such as WMS, WFS, OGC 3D Tiles, etc.

Take a look at the com.luciad.fusion.platform.services.configuration package on how to get started with adding a custom service type. The classes in the com.luciad.fusion.platform.repository package contain the repositories necessary to access services, products, data from your custom service endpoint. There is also a detailed tutorial on how to add a custom service type to LuciadFusion.

Maven POM files are now provided for LuciadFusion releases. There are Maven POM files available for each product tier (Essential, Advanced, Pro), which depend on all non-optional components of their respective tiers. In addition there are maven POM files for each optional component for each tier.

The product tier POM dependencies are:

The optional component POM dependencies are:

• TLspFXCompassNavigationControl: rotate and pan the map.
• TLspFXPanNavigationControl: pan the map.
• TLspFXZoomNavigationControl: change the zoom level of the map.
• TLspFXAltitudeExaggerationControl: change the altitude exaggeration factor of a 3D view.

• Layers can be moved in the tree with drag and drop or buttons.
• A progress indicator now indicates when a layer is busy.
• Buttons have been added to toggle selectable, editable and labeled.

• This fixes the interpretation of GeoTIFF images with exactly 4 bands. The 4^th band was always interpreted as alpha channel.

Microsoft ended its support for Windows 7 and Windows Server 2008. In line with that decision, we now support LuciadLightspeed development and deployment on Windows platforms starting from versions Windows 8.1 and Windows Server 2012.

Microsoft ended its support for Windows 7 and Windows Server 2008. In line with that decision, we now support LuciadFusion development and deployment on Windows platforms starting from versions Windows 8.1 and Windows Server 2012.

The Maven POM files provided with a LuciadLightspeed release have been renamed to follow the Maven artifactId naming conventions.

If you depend on any Lightspeed component in your project's POM file, they will need to be renamed as follows.

In addition, POM files are now available for each product tier (Essential, Advanced and Pro). These POM files depend on all non-optional modules available for their respective product tiers.

The new product tier POM files are:

Due to changes in the dependencies of LuciadFusion we have upgraded our com.fasterxml dependencies in LuciadLightspeed to ensure we depend on the same version across all products.

Here is an overview of the dependency changes: