LuciadFusion Release notes

The WFS server now supports a new SHAPE-ZIP output format for GetFeature and GetFeatureWithLock requests.

This format encodes the requested features as an ESRI Shapefile (.shp, .shx, .dbf, .cpg, .sbn/.sbx and .prj), and combines all of these files into a single application/zip archive. The .shp file and its companion files are named after the requested feature type.

The article Which vector output formats does the WFS service support describes the supported output formats in more detail.

Visualization of an I3S dataset on a Lightspeed map — data: ODU GeoSEA, CC BY 4.0

Added support for the OGC Indexed 3D Scene Layers (I3S) data format. OGC I3S is an open community standard that defines a 3D content delivery format used to rapidly stream and distribute large volumes of 3D GIS data to mobile, web and desktop clients.

For more details, see the OGC I3S entry in the Data Formats documentation section.

The Spring Boot dependencies of LuciadFusion have been upgraded from version 3.5 to version 4.1. This newer version brings numerous new features and fixes. It's advisable to read through the release notes of every version to know what is new, what has changed and what has been deprecated.

• Spring Boot 4.1 Migration Guide
• Spring Boot 4.1 Release Notes
• Spring Boot 4.0 Migration Guide
• Spring Boot 4.0 Release Notes
• Spring Framework 7 Release Notes
• Spring Security 7 migration guide

Check out our LuciadFusion troubleshooting guide for a list of major changes caused by the Spring Boot upgrade.

Check out our deployment requirements section for the minimum supported Jakarta Servlet, Jakarta EE, and Tomcat versions.

• Aerodrome:
  • TLcdDAFIFTAerodromeDataProperties#COORDINATE_PRECISION,
  • TLcdDAFIFTAerodromeDataProperties#MAGNETIC_VARIATION_OF_RECORD.
• ATS Route:
  • TLcdDAFIFTATSRouteSegmentDataProperties#CYCLE_DATE,
  • TLcdDAFIFTATSRouteSegmentDataProperties#ATS_DESIGNATOR.
• Helipad:
  • TLcdDAFIFTHelipadDataProperties#COORDINATE_PRECISION.
• Heliport:
  • TLcdDAFIFTHeliportDataProperties#COORDINATE_PRECISION,
  • TLcdDAFIFTHeliportDataProperties#MAGNETIC_VARIATION_OF_RECORD.
• ILS Components (GlidePath, Localizer, Marker, ILSDME):
  • TLcdDAFIFTGlidePathDataProperties#COORDINATE_PRECISION,
  • TLcdDAFIFTLocalizerDataProperties#COORDINATE_PRECISION,
  • TLcdDAFIFTMarkerDataProperties#COORDINATE_PRECISION,
  • TLcdDAFIFTILSDMEDataProperties#COORDINATE_PRECISION.
• Navaid:
  • TLcdDAFIFTDMEDataProperties#COORDINATE_PRECISION,
  • TLcdDAFIFTNDBDataProperties#COORDINATE_PRECISION,
  • TLcdDAFIFTTACANDataProperties#COORDINATE_PRECISION,
  • TLcdDAFIFTVORDataProperties#COORDINATE_PRECISION.
• Procedure:
  • TLcdDAFIFTProcedureDataProperties#PROCEDURE_DESIGN_CRITERIA,
  • TLcdDAFIFTProcedureDataProperties#PROCEDURE_AMENDMENT_DATE,
  • TLcdDAFIFTProcedureDataProperties#PRIMARY_APPROACH_ROUTE_QUALIFIER,
  • TLcdDAFIFTProcedureDataProperties#SECONDARY_APPROACH_ROUTE_QUALIFIER,
  • TLcdDAFIFTProcedureDataProperties#PRECISION_RNAV_LEVEL_OF_SERVICE_AUTHORIZED,
  • TLcdDAFIFTProcedureDataProperties#PRECISION_RNAV_LEVEL_OF_SERVICE_NAME,
  • TLcdDAFIFTProcedureDataProperties#LNAV_VNAV_RNAV_LEVEL_OF_SERVICE_AUTHORIZED,
  • TLcdDAFIFTProcedureDataProperties#LNAV_VNAV_RNAV_LEVEL_OF_SERVICE_NAME,
  • TLcdDAFIFTProcedureDataProperties#LNAV_RNAV_LEVEL_OF_SERVICE_AUTHORIZED,
  • TLcdDAFIFTProcedureDataProperties#LNAV_RNAV_LEVEL_OF_SERVICE_NAME,
  • TLcdDAFIFTProcedureDataProperties#MAGNETIC_VARIATION.
• Runway:
  • TLcdDAFIFTRunwayDataProperties#COORDINATE_PRECISION,
  • TLcdDAFIFTRunwayDirectionDataProperties#TAKEOFF_RUN_AVAILABLE,
  • TLcdDAFIFTRunwayDirectionDataProperties#TAKEOFF_RUN_AVAILABLE_UNIT,
  • TLcdDAFIFTRunwayDirectionDataProperties#ACCELERATE_STOP_DISTANCE_AVAILABLE,
  • TLcdDAFIFTRunwayDirectionDataProperties#ACCELERATE_STOP_DISTANCE_AVAILABLE_UNIT.
• Waypoint:
  • TLcdDAFIFTWayPointDataProperties#COORDINATE_PRECISION.

Additionally, a new runway surface type AM2 has been added to TLcdRunwaySurfaceType, representing a surface type consisting of metal planking.

We have added full support for the military standard 'APP-6 NATO Joint Military Symbology, Edition E Version 2, October 2025'.

The symbols of the Cyberspace symbol set, which we added previous minor release, LuciadLightspeed 2026.0, have been upgraded from APP-6E E Version 1 to APP-6E Version 2.

You can visualize the APP-6E symbols using the Military Symbology samples available for both GXY and Lightspeed. In a Lightspeed view, you can create a layer for these symbols with TLspAPP6ALayerBuilder. In a GXY view, you can paint them by setting a TLcdAPP6AGXYPainterProvider on your TLcdGXYLayer.

APP-6E - Fictional Scenario.

On NVidia GPUs, TLspViewBuilder now takes the GPU's video memory size into account when computing the default size of the OpenGL resource cache (#glResourceCacheSize()). This significantly improves the Lightspeed view's ability to load large datasets. In previous versions, the default cache size was usually overly conservative for modern GPUs with 8+ GB of memory.

The change reduces the need for users to manually adjust the cache size to alleviate performance issues. It only takes effect if the application does not explicitly set the cache size itself (either via the API or via the corresponding system property). On non-NVidia GPUs, the behavior is unchanged compared to previous LuciadLightspeed versions.

You can now define the scale range of WMS data through an SLD style without having to provide SLD-based styling. If the SLD style consists of a single FeatureTypeStyle with a single Rule that has no symbolizers, the WMS server automatically applies the default styling for the underlying data while still honoring the scale range defined in the SLD.

This is particularly useful for data formats that provide their own dedicated styling, such as AIXM, DGN and DWG. You can now restrict such layers to a specific scale range using SLD, without having to recreate their styling through SLD symbolizers. The configured scale range is taken into account during rendering and is advertised in the WMS GetCapabilities document so that clients are aware of it upfront.

The article How to restrict a WMS layer to a scale range without changing its styling describes this feature, and its limitations, in more detail.

You can now configure the maximum expiry time for WFS-T feature locks with the wfs.maxLockExpiry servlet configuration parameter. The value is expressed in seconds and applies to locks created or refreshed by LockFeature and GetFeatureWithLock requests.

If a client requests an expiry value that exceeds this limit, the request is rejected with an InvalidParameterValue service exception report. The configured limit is also advertised as a maxExpiry constraint on the LockFeature and GetFeatureWithLock operations in the WFS GetCapabilities response, so that clients can find out about it up front.

• setFirstArgument(Object)/getFirstArgument()
• setSecondArgument(Object)/getSecondArgument()

• setPropertyName(TLcdOGCPropertyName)/getPropertyName()
• setShape(ILcdShape)/getShape()

• Improved concurrency: downloading and decoding of tile payloads now happen on separate threads; larger thread pool for local data.
• Throttling of GPU data transfers for freshly downloaded tiles, to reduce frame drops during navigation.
• Improved prioritization of tile downloads based on camera position, and cancellation of downloads that become obsolete due to camera movement.
• Texture compression to reduce GPU memory usage and CPU-to-GPU data transfer volumes.
• Evaluation of the geometric error property is now DPI-aware.
• LPC point cloud layers no longer ignore the quality factor configured on the layer builder.
• Authentication can now be configured by annotating an ILcdPasswordProvider with @LcdService. It is no longer necessary to install a custom ILcdInputStreamFactory on the model decoder for this.
• Support for HTTP/2 if supported by the server; automatic fallback to HTTP/1.1 otherwise.

• TLcdDefaultModelModelTransformation
• TLcdDefaultModelXYWorldTransformation
• TLcdDefaultModelXYZWorldTransformation
• TLcdGeoReference2GeoReference

• TLcdDAFIFTProcedureDataProperties#EMERGENCY_SAFE_ALTITUDE,
• TLcdDAFIFTProcedureDataProperties#LATEST_REVISION_DATE,
• TLcdDAFIFTProcedureDataProperties#AMENDMENT_NUMBER,
• TLcdDAFIFTProcedureDataProperties#OFFICE_OF_PRIMARY_RESPONSIBILITY,
• TLcdDAFIFTProcedureDataProperties#HOST_COUNTRY_AUTHORITY,
• TLcdDAFIFTProcedureDataProperties#ALTERNATE_TAKEOFF_MINIMUMS,
• TLcdDAFIFTProcedureDataProperties#TRANSITION_ALTITUDE,
• TLcdDAFIFTProcedureDataProperties#TRANSITION_LEVEL.

Fixed an issue where feature locks were not always released after a successful WFS-T Transaction request with a releaseAction of SOME. As a result, subsequent LockFeature requests for the same features could fail until the locks expired.

The issue affected Update operations that modify geometry on data whose domain objects extend from ILcdShape, such as SHP data. It could also cause the UpdateResults section of the Transaction response to report generated identifiers instead of the identifiers of the updated features. Both issues have been resolved.

Fixed an issue where a GetFeature request for data with an ILcdPolypoint geometry (for example, decoded from a Shapefile using the MultiPoint shape type) failed with an error when requested in the GeoJSON output format, instead of returning the requested features.

Set the com.luciad.fusion.wms.server.errorResponseOnPaintException system property to false to restore the previous behavior.

Because a Data item is now decoded while a request is being rendered, a Data item that cannot be decoded only affects the requests that need it: such a request fails with an HTTP 500 Internal Server Error, while requests whose map extent does not cover that Data item are served normally.

Set the fusion.ogc.wms.lazyInitializationEnabled configuration property to false to restore the previous behavior.

• The LuciadLightspeed image processing framework uses a shared cache to store input, intermediate or processed data required by the imaging engine. The default size of this cache has been increased from 64 MB to 128 MB. This cache size can be configured by setting the system property com.luciad.imaging.maxCacheSize to a value in megabytes, e.g. -Dcom.luciad.imaging.maxCacheSize=64 to limit the cache size to 64 MB. Note that the cache should be large enough to fit at least all data that is being painted.
• The OpenCL imaging engine requires memory on the OpenCL device, typically a GPU, for its operation. It also uses a cache and its default size has been increased from 32 MB to 48 MB. This cache size can be configured by setting the system property com.luciad.imaging.engine.opencl.maxCLCacheSize to a value in megabytes, e.g. -Dcom.luciad.imaging.engine.opencl.maxCLCacheSize=32 to limit the cache size to 32 MB.
• The default size of the tile cache used by a height provider to read data from an image has been increased from 10 MB to 16 MB. This cache size can be configured when creating the height provider using the new cache size property on TLcdImageModelHeightProviderFactory or when creating a TLcdImageHeightProvider directly with the new builder. The maximal number of entries that can be stored in this cache has also been increased. You can configure it similarly to the cache size.

The hostile text modifier now accepts only two values: ENY (the default) and null.

You can use the modifier to disable the ENY indicator: setting it to null removes the annotation from both the icon label and the stroke decoration of tactical graphics. Previously, symbols with a hostile affiliation were always annotated with ENY, regardless of the modifier value.

The change affects all supported military symbology standards.

A number of control measure Line symbols in APP-6D and MIL-STD 2525D no longer display the generic PL ("phase line") label. Previously these symbols were labeled twice: once with PL followed by the first uniqueDesignation modifier, and once with the abbreviation specific to the symbol followed by the second uniqueDesignation modifier. They are now labeled only with their own abbreviation, followed by the first uniqueDesignation modifier.

The change affects the following symbols. All of them belong to symbol set 25 (Control Measure); the symbol code is given for each symbol.

• APP-6D
  • Light Line: 110200
  • Final Coordination Line:140700
  • Limit Of Advance: 140900
  • Line Of Departure: 141100
  • Line Of Contact: 140200
  • Probable Line Of Deployment: 141200
  • Bridgehead Line (BL): 141400
  • Holding Line: 141500
  • Release Line: 141600
• MIL-STD-2525D
  • Light Line: 110200
  • Final Coordination Line: 140700
  • Limit Of Advance: 140900
  • Line Of Departure / Line Of Contact: 141100
  • Line Of Contact: 140200
  • Probable Line Of Deployment: 141200
  • Bridgehead Line (BL): 141400
  • Holding Line (HL): 141500
  • Release Line: 141600

• LuaJIT 2.1.0-beta3 to 2.1.1785606157,
• OpenSSL 3.4.5 to 3.5.8,
• zlib 1.3.1 to 1.3.2,
• libzip 1.5.1 to 1.11.4,
• bzip2 has been removed.