2026.0
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

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.
ImprovementLuciadFusion
LCD-13812
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.
ImprovementLuciadFusion
LCD-13812
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.
ImprovementLuciadFusion
LCD-14072
ImprovementLuciadFusion
ImprovementLuciadFusion
ImprovementLuciadFusion
LCD-14018
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.
ImprovementLuciadFusion
TLcdGXYLocationListLabelingAlgorithmnow 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()
setShiftLabelLocation(int)getShiftLabelLocation()
-
The
TLcdGXYFixedOnPathLabelingAlgorithmis 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.
ImprovementLuciadFusion
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.
ImprovementLuciadFusion
ImprovementLuciadFusion
image/jpgpng,
which lets the service automatically choose between image/jpeg and
image/png. When used in WMS GetMap or WMTS
GetTile requests, the most appropriate format is used based on the requested map data:
- If the map doesn't contain transparent pixels, the
image/jpegformat is used, ensuring a fast encoding time and small payload. - If the map contains transparent pixels, the
image/pngformat is used.
ImprovementLuciadFusion
LF-2802
fusion.ogctilesservice.preprocessorTempPath. Previously, this config option applied only to
point cloud preprocessing.
ImprovementLuciadFusion
LCD-13994, LCD-12072
ImprovementLuciadFusion
LF-2668
- The specification now uses reusable enums.
- The names of the operations have been standardized and are now all unique.
- The security on each operation is now defined.
- The required property is now correctly set on the response schemas
ImprovementLuciadFusion
LCD-14080
samples.gxy.contour now has improved contour accuracy for
point-sampled elevation data.
ImprovementInfrastructure Standards
LCD-11332
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
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
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
TLcdNWDModelDecoder caused a JVM crash for certain input datasets.
For this change, the myVRDatakitConverter library was upgraded to version 2025.10.80067.
ImprovementRadar Connectors
com.luciad.format.asdi have been deprecated.
Bug fixLuciadFusion
LF-2833
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 fixLuciadFusion
LCD-13860
TLcdWKTReferenceFormatter now uses the BASEGEODCRS keyword when formatting topocentric
references to make it spec compliant.
Bug fixLuciadFusion
LCD-14093
Bug fixLuciadFusion
LF-2835
DescribeCoverage requests
to return an incomplete result.
Bug fixLuciadFusion
LCD-14081
Bug fixAviation Standards
LCD-14073
Upgrade considerationLuciadFusion
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)
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 considerationLuciadFusion
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:
createCoverageOfferingListcreateServiceMetaData
Removed classes:
ILcdWCSServiceMetadata: useILcdWCSCapabilitiesProviderILcdWCSModelEncoder: useILcdWCSModelEncoderFactoryILcdCoverageOfferingList: useILcdWCSCapabilitiesProviderTLcdCoverageOffering: useTLcdDefaultCoverageOfferingTLcdCoverageOfferingDetail: useTLcdDefaultCoverageOfferingDetail
Upgrade considerationLuciadFusion
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 considerationLuciadFusion
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 considerationLuciadFusion
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)
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 considerationLuciadFusion
LF-2802
fusion.ogctilesservice.preprocessorTempPath has changed from
${java.io.tmpdir}/pointCloudPreprocessor to ${java.io.tmpdir}/ogctilesPreprocessor,
because the property is now also used for mesh preprocessing.
Upgrade considerationLuciadFusion
| Group ID | Artifact ID | Version |
|---|---|---|
| com.google.errorprone | error_prone_annotations | 2.41.0 |
| com.google.flatbuffers | flatbuffers-java | 23.3.3 |
| com.google.guava | failureaccess | 1.0.3 |
| com.google.j2objc | j2objc-annotations | 3.1 |
| net.sf.geographiclib | GeographicLib-Java | 2.0 |
| org.wololo | flatgeobuf | 3.26.2 |
| Group ID | Artifact ID | Old Version | New Version |
|---|---|---|---|
| com.google.code.findbugs | jsr305 | 3.0.1 | 3.0.2 |
| com.google.guava | guava | 20.0 | 33.5.0-jre |
| com.h2database | h2 | 2.1.214 | 2.3.232 |
| org.apache.lucene | lucene-analyzers-common | 6.4.0 | 6.6.6 |
| org.apache.lucene | lucene-core | 6.4.0 | 6.6.6 |
| org.apache.lucene | lucene-queries | 6.4.0 | 6.6.6 |
| org.apache.lucene | lucene-queryparser | 6.4.0 | 6.6.6 |
| org.apache.lucene | lucene-sandbox | 6.4.0 | 6.6.6 |
| org.apache.lucene | lucene-spatial | 6.4.0 | 6.6.6 |
| org.apache.lucene | lucene-suggest | 6.4.0 | 6.6.6 |
| org.orbisgis | cts | 1.7.0 | 1.7.1 |
| org.orbisgis | h2gis | 2.2.0 | 2.2.3 |
| org.orbisgis | h2gis-api | 2.2.0 | 2.2.3 |
| org.orbisgis | h2gis-utilities | 2.2.0 | 2.2.3 |
| org.orbisgis | poly2tri | 0.4.0 | 0.7.0 |
Upgrade considerationLuciadFusion
| 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 |
| Group ID | Artifact ID | Version |
|---|---|---|
| org.glassfish.jaxb | xsom | 4.0.6 |
| com.sun.xml.bind.external | relaxng-datatype | 4.0.6 |
Upgrade considerationData Connectivity Manager
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 in the Data Connectivity Manager, and workspaces that
contain JPIP layers will no longer restore these layers when loaded. If needed, you can insert the addons back into
config/manager/addons_data.xml and config/manager/addons_lsp.xml,
respectively, to re-enable the JPIP functionality.
Upgrade considerationInfrastructure Standards
Upgrade considerationInfrastructure Standards
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