2026.0

New featureLucy (LuciadLightspeed)

The new TLcyS101FormatAddOn and TLcyLspS101FormatAddOn add-ons provide support for the S-101 hydrographic format:
  • 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.
Both add-ons also provide workspace support, enabling users to store GXY and Lightspeed layers with S-101 data in a Lucy workspace, together with the currently used S-101 display settings. See the reference documentation of TLcdS101ModelDecoder for more information about the supported S-101 files.

New featureLucy (LuciadLightspeed)

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.

New featureDefense Symbology

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.

New featureMaritime Standards

Visualization of an S‑101 dataset in Lucy, delivered via a WMS service from LuciadFusion
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 WMS service in LuciadFusion.

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

ImprovementLuciadLightspeed

LCD-13812
The GeoJSON encoder's supporting class TLcdFeatureMetaDataProvider has a new method getPropertyName(ILcdDataObject, String): by overriding it, you can customize the property name to be used when an object's property is being encoded.

ImprovementLuciadLightspeed

LCD-14072
To ease identifying issues with spatial OGC Filter conditions, the filter evaluation logic now logs an info message if it does not have access to the Advanced GIS Engine component. Without this component, only bounding box spatial filter conditions are supported. The component is only included with the Advanced and Pro product tiers of LuciadLightspeed and LuciadFusion.

ImprovementLuciadLightspeed

LCD-14018
A new sample decoder samples.format.osm.OpenStreetMapXMLExportModelDecoder illustrates how to decode vector data defined in the OpenStreetMap XML export format. For more information about the supported OpenStreetMap data sources in general, see the Data Formats: OpenStreetMap articles.

ImprovementLuciadLightspeed

  • 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.

ImprovementLuciadLightspeed

Added API for GML 3.2/3.1 coordinate systems, which completes the ISO19115 metadata coordinate system API. This causes some ISO metadata methods to accept stricter arguments than before. For example, TLcdISO19115VerticalExtent#setVerticalCRS's argument type has changed from the generic TLcdGML32Definition to the more useful TLcdGML32AbstractCRS.
No mapping is provided to/from Luciad's coordinate system API.

ImprovementLucy (LuciadLightspeed)

The ASDI format for streaming air traffic data has fallen out of use in recent years, in favor of more recent air traffic management systems. Therefore, the Lucy add-ons related to ASDI have been deprecated.

ImprovementLuciadLightspeed

LCD-14080
The sample in samples.gxy.contour now has improved contour accuracy for point-sampled elevation data.

ImprovementOGC Server

LCD-13812
The TLcdWFSClientModelEncoderFactory class has a new protected method createFeatureMetaDataProvider(ILcdOGCFeatureIDRetriever, TLcdWFSRequestContext). This method creates a TLcdFeatureMetaDataProvider, which is used to retrieve feature-specific information during the encoding of a WFS feature response to GeoJSON. You can override the method to customize the GeoJSON encoding of each feature, such as changing the name of a property.

ImprovementInfrastructure Standards

LCD-11332
The TLcd3DTilesProcessorBuilder can now apply a geometrical transformation on input data. The transformation should be passed as an affine transformation matrix using the preTransformFactory API method. This can be used to fix shifts, rotations and scale of the data. When using the MeshUp sample, you can read the transformation matrix from a .matrix file next to the data. The common use case of rotating a Y-up OBJ data set to Z-up has also been added to the MeshUp sample.

ImprovementInfrastructure Standards

LCD-14002
When decoding Revit features using the TLcdRevitModelDecoder, each feature will now include a UniqueID property that links the feature back to the Revit model.
For more information, refer to the "model elements" section of the TLcdRevitModelDecoder class javadoc.

ImprovementInfrastructure Standards

LF-2802
The TLcd3DTilesProcessorBuilder now allows to specify the location of temporary cache files that are created during processing. This can be useful if the default temporary files location is not desirable for the 3D Tiles Processor to write to.

ImprovementInfrastructure Standards

LCD-14006
Fixed a bug where the TLcdNWDModelDecoder caused a JVM crash for certain input datasets. For this change, the myVRDatakitConverter library was upgraded to version 2025.10.80067.

ImprovementRadar Connectors

The ASDI format for streaming air traffic data has fallen out of use in recent years, in favor of more recent air traffic management systems. Therefore, the ASDI model decoder and related classes in com.luciad.format.asdi have been deprecated.

Bug fixLuciadLightspeed

LF-2833
Decoded KML models now have TLcdModelMetadata that identifies the data category as TLcdModelMetadata.DataCategory.VECTOR. This improves the integration of KML data in LuciadFusion: next to the publication of KML data in a WMS service, it is now also possible to preview the data.

Bug fixLuciadLightspeed

LCD-13860
TLcdWKTReferenceFormatter now uses the BASEGEODCRS keyword when formatting topocentric references to make it spec compliant.

Bug fixLuciadLightspeed

LCD-14081
Database encoders and decoders for all supported databases (DB2, Informix, SQL Server, Oracle, and PostgreSQL) previously assumed that Java properties files containing the configuration for accessing spatial data were encoded using ISO‑8859‑1. They now assume that these properties files are encoded in UTF‑8, allowing property names and values to include accent marks and other special characters.

Bug fixOGC Server

LCD-14093
Fixed requesting coverage data as JPEG2000 or JPEG when the source data has transparency. These encoders do not support transparent images. The transparency is removed before encoding the data.

Bug fixAviation Standards

LCD-14073
The AIXM 5.1 decoder now supports route segments of which the start and end points are defined by a link to other AIXM 5.1 features.

Upgrade considerationLucy (LuciadLightspeed)

TLcyJPIPDecoderAddOn and TLcyLspJPIPFormatAddOn have been deprecated (along with TLcdJPIPModelDecoder itself, see separate release note for more information). Consequently, these addons are no longer loaded by default, and workspaces that contain JPIP layers will no longer restore these layers when loaded. If needed, you can insert the addons back into config/lucy/addons_data.xml to re-enable the JPIP functionality.

Upgrade considerationLuciadLightspeed

TLcdJPIPModelDecoder has been deprecated. JPIP is not widely adopted, and we recommend the use of LuciadFusion with WM(T)S or ECWP as an alternative to serve large amounts of imagery to clients.

Upgrade considerationLuciadLightspeed

The WCS Client module no longer provides access using the ILcdRaster, ILcdMultilevelRaster API. Classes, interfaces, and methods related to the raster API have been removed.
The WCS Client module now only provides access using the imaging API.
You can find more information on using the imaging API at the following sections:

Upgrade considerationLuciadLightspeed

The following dependencies have been updated:
Group ID Artifact ID Old Version New Version
com.luciad.thirdparty libmyvrdatakitconverter-native 2025.03.77665 2025.10.79469
com.luciad.native sqlitej 3.36.0 3.49.1
org.locationtech.jts jts-core 1.19.0 1.20.0
org.lwjgl lwjgl 3.3.3 3.4.0
org.lwjgl lwjgl-jawt 3.3.3 3.4.0
org.lwjgl lwjgl-meshoptimizer 3.3.3 3.4.0
org.lwjgl lwjgl-opencl 3.3.3 3.4.0
org.lwjgl lwjgl-opengl 3.3.3 3.4.0

The following dependencies have been removed:
Group ID Artifact ID Version
commons-logging commons-logging 1.2
com.sun.xsom xsom 20110809
relaxngDatatype relaxngDatatype 20020414
The following dependencies have been added:
Group ID Artifact ID Version
org.glassfish.jaxb xsom 4.0.6
com.sun.xml.bind.external relaxng-datatype 4.0.6

Upgrade considerationOGC Server

The ILcdWFSServerModelEncoderFactory interface used by WFS-T services to create a model encoder capable of storing feature type changes (additions, removals, updates) in the data back-end has changed. The existing method

void createModelEncoder(ILcdModel)

has changed to

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.

Upgrade considerationOGC Server

Classes/interfaces/methods that were marked as deprecated for more than 8 years have been removed from the OGC WCS Server module API.
Changes for class com.luciad.ogc.wcs.ALcdOGCWCSCommandDispatcherFactory:
  • 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

Removed classes:

Upgrade considerationOGC Server

The ILcdGXYViewEncoder interface used by WM(T)S services to encode a view to a format requested by a client has changed. The existing method

void encodeGXYView(ILcdGXYView, OutputStream)

has changed to

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.

Upgrade considerationInfrastructure Standards

The .llh model reference file format has been deprecated. This was a Luciad-only file format used to provide a topocentric reference for 3D data. However, support for this file format was inconsistent across our products. We recommend to switch to the standard WKT reference format which works consistently on all models. You can find more information on how to do this our How to add a topocentric (LLH) reference to a 3D model article.

Upgrade considerationInfrastructure Standards

The myVRDatakitConverter library has been upgraded to version master.78725. It is used by the TLcdRevitModelDecoder and the TLcdNWDModelDecoder. This upgrade brings the following new features and enhancements:
  • Added support for Revit and Navisworks 2026 files
  • Fixes several issues related to reading geometry and metadata