LuciadLightspeed Release notes

getLegendURL(ALcdWMSLayer, ALcdWMSLayerStyle, TLcdWMSLegendURLParameters) for WMS, and getLegendURL(String, String, TLcdWMTSLegendURLParameters) for WMTS.

These methods allow an encoder to customize the LegendURL advertised in the GetCapabilities response for a given layer and style. An implementation can override the width, the height, or the online resource — for example to advertise a static, externally-hosted legend image instead of a dynamically-generated one — or suppress the LegendURL entirely by returning null.

Both methods are default methods that return the given default parameters unchanged, which preserves the existing behavior for encoders that do not override them.

The ShapeFile decoders (TLcdSHPModelDecoder and TLcdSHPModelDecoder2) now only log number parse warnings once, to avoid log file flooding. An example of such a warning is: Failed to parse '***********' as number: Not a numeric string..

If you enable debug logging for the com.luciad.format.shp package, you will still see the individual warnings for each value that cannot be parsed as a number.

Fixed an issue where min/max altitude values in some tactical graphics labels were fetched from the "Additional Information" modifier instead of from the "Altitude/Depth" modifier.

Affected symbols:

Resolved an issue that could cause hierarchy icon, of military symbols containing a letter icon, to be misaligned. For example, the before and after of the APP-6A "Reconnaissance - Airborne Early Warning (AEW)" (1.X.2.1.1.10) symbol:

APP-6A Reconnaissance - Airborne Early Warning (AEW), before the change.

APP-6A Reconnaissance - Airborne Early Warning (AEW), after the change.

The ShapeFile decoders (TLcdSHPModelDecoder and TLcdSHPModelDecoder2) now only log number parse warnings once, to avoid log file flooding. An example of such a warning is: Failed to parse '***********' as number: Not a numeric string..

If you enable debug logging for the com.luciad.format.shp package, you will still see the individual warnings for each value that cannot be parsed as a number.

1. If an object is being created, the creation process is being canceled, allowing to restart creation immediately after.
2. If an object is not yet being created (e.g. before the first click), the action to trigger after commit is performed, allowing to set the default controller back on the view and terminate the creation process completely.

1. If an object is being created, the creation process is being canceled, allowing to restart creation immediately after.
2. If an object is not yet being created (e.g. before the first click), the action to trigger after commit is performed, allowing to set the default controller back on the view and terminate the creation process completely.

• TLcdEllipsoidUtil#closestPointOnShape
• TLcdEllipsoidRhumblineUtil#closestPointOnShape
• TLcdSphereRhumblineUtil#closestPointOnShape

• TLcyS101FormatAddOn introduces core support to decode S-101 data, visualize it in a GXY view and change the S-101 display settings in the UI.
• TLcyLspS101FormatAddOn extends the core support with visualization support in a Lightspeed view.

Partial support for the APP-6E standard has been added to the TLcyAPP6AAddOn. Since APP-6E is only partially supported, APP-6D remains the default standard. You will need to switch the standard to APP-6E in the addon configuration in order to use the new standard. Read the How to switch between military symbologies in Lucy article for more information.

The supported APP-6E symbol sets are listed in the Supported standards article.

We have added partial support for the military standard APP-6E. This update introduces the ability to create and visualize instances of TLcdEditableAPP6AObject for the APP-6E military standard.

APP-6E support is currently limited to the Cyberspace icon symbols. All supported symbol sets are listed in the supported military standards article.

You can visualize the supported symbols using the Military Symbology "Allsymbols" samples available for both GXY and Lightspeed.

Visualization of an S‑101 dataset in Lucy, delivered via a WMS service from LuciadFusion

Added support for the S-101 maritime data format. S-101 introduces several enhancements over S-57, aimed at improving the usability and functionality of electronic navigational charts in modern ECDIS systems. S-101 data can be visualized in a GXY or Lightspeed view in LuciadLightspeed, or can be served in a WM(T)S service in LuciadFusion.

For more details, see the S-101 related articles in the ECDIS entry in the Data Formats documentation section.

• TLcdGXYLocationListLabelingAlgorithm now supports defining separate shifts for the X and Y axes to move the label from the anchor point of the domain object in both directions with the respective shifts. As a result, new methods have been added to set and get the X and Y shifts separately:
  • setShiftLabelLocationX(int)
  • setShiftLabelLocationY(int)
  • getShiftLabelLocationX()
  • getShiftLabelLocationY()
  In addition, the following methods have been kept for backward compatibility but are now deprecated.
  • setShiftLabelLocation(int)
  • getShiftLabelLocation()
• The TLcdGXYFixedOnPathLabelingAlgorithm is a new labeling algorithm added to support precise label placement along a path using flexible horizontal (LEFT, CENTER, RIGHT) and vertical (ABOVE, CENTER, BELOW) alignment options. The anchor point, defined by a relative path position (0.0–1.0), determines the label’s base location, while alignment and optional offsets adjust its position relative to that point without changing the anchor itself.

• Models: Handling raster data
• GXY Views: Visualizing raster data
• Lightspeed Views: Visualizing raster data

void createModelEncoder(ILcdModel)

void createModelEncoder(ILcdModel, TLcdWFSRequestContext)

This new method signature allows implementations to take into account request parameters via the TLcdWFSRequestContext parameter.

Existing implementations can be updated by simply ignoring the new TLcdWFSRequestContext parameter.

• createWCSCapabilitiesProvider: is now abstract. It does no longer provide support backwards compatibility for the way of working from 2016 or before.
• Removed methods:
  • createCoverageOfferingList
  • createServiceMetaData

• ILcdWCSServiceMetadata: use ILcdWCSCapabilitiesProvider
• ILcdWCSModelEncoder: use ILcdWCSModelEncoderFactory
• ILcdCoverageOfferingList: use ILcdWCSCapabilitiesProvider
• TLcdCoverageOffering: use TLcdDefaultCoverageOffering
• TLcdCoverageOfferingDetail: use TLcdDefaultCoverageOfferingDetail

void encodeGXYView(ILcdGXYView, OutputStream)

String encodeGXYView(ILcdGXYView, OutputStream, ALcdRequestContext)

This new method signature allows implementations to take into account request parameters via the ALcdRequestContext parameter. Furthermore, implementations should now return the content type used by the encoding, allowing to dynamically choose the most appropriate encoding for a given view.

Existing implementations can be updated by simply returning the value of the getContentType() method. The new ALcdRequestContext parameter can be ignored.

• Added support for Revit and Navisworks 2026 files
• Fixes several issues related to reading geometry and metadata