LuciadFusion Release notes

The WCS server now uses a non-persistent cache for tiled GetCoverage requests. This cache makes sure that subsequent tile requests are handled much faster, improving the performance and scalability of the WCS server when using tiled requests. See ALcdOGCWCSCommandDispatcherFactory for more information and configuration options.

This implies that for data that changes dynamically, extra care needs to be taken to make sure caches are invalidated. To this end, the API ILcdCoverageOffering#getUpdateSequence and TLcdDefaultCoverageOffering#setUpdateSequence is introduced to indicate that a WCS coverage has changed. By default, the implementations of these methods (mostly) assume static data/coverages. For WCS servers that serve data that changes over time (for example data updates), these methods should be used correctly. Note that the LuciadFusion Platform already takes care of this. An alternative is to disable the caches.

OGC filters: the changes made for LCD-11278 introduced a performance regression for the evaluation of a filter with nested OR or AND conditions. This performance regression is now avoided, unless you're using an or condition nested inside an and condition (or vice-versa).

The TLcdOGCDistanceBuffer and TLcdOGCBinarySpatialOperator need to transform their shape to match the reference of the shape that is being evaluated. This was not done in the past, causing wrong results of the spatial test.

Seeing as not all shapes can be converted from one reference to another, the documentation of both classes has been updated to clearly document that this transformation is needed when mixing references, and that it is recommended to avoid this case.

We support a limited number of shape transformations out of the box (currently only points and bounds). When the transformation fails, evaluating the filter will now throw a clear exception instead of providing the wrong results.

• a new constructor has been added in TLcdSLDGeometry, accepting a TLcdOGCFunction,
• a new geometry method has been added in the builder of each symbolizer (e.g., TLcdSLDPointSymbolizer), accepting a TLcdOGCFunction.

ILcdEvaluatorFactory: the canBuildEvaluator method could not perform a decent check because it did not receive the same arguments as the buildEvaluator method. This could result in the creation of evaluators which would throw exceptions when used.

This has been fixed by introducing a new default canBuildEvaluator method which has the same arguments as the buildEvaluator method. The old method has been deprecated.

The result of this change is that calling TLcdOGCFilterEvaluator#buildFilter for a filter containing expressions that cannot be evaluated will now throw an IllegalArgumentException in all cases, and never return a filter with undefined behavior at runtime.

The ILcdEvaluatorFactory interface should not be implemented nor used by customers, so this change should not affect your code base.

LuciadLightspeed now comes with a native JavaFX Lightspeed view called TLspFXView. All controller and editing API has been adjusted to work with FX input events. In addition, the following API has been added to kick-start your JavaFX development:

• TLspViewBuilder to create TLspFXViewinstances
• TLcdOverlayPane to easily position nodes in the view's corners or along its edges
• TLspFXScaleIndicator to visually show the scale of your JavaFX view
• TLcdFXIcon is a JavaFX node that displays an ILcdIcon
• TLcdFXEventFilterBuilder to assist with controller chaining
• TLcdBingMapsLogoIcon#asJavaFXImage and TLspBingMapsCopyrightIcon#asJavaFXImage for displaying Bing copyright information
• TLspFXBalloonManager for displaying balloons on your maps.

Refer to the samples.lightspeed.javafx package for samples demonstrating the new FX view.

Note that the LuciadLightspeed API provides numerous Swing UI components. However, only the UI elements explicitly listed above are currently available for JavaFX.

BUFR files containing World Area Forecasting System (WAFS) Significant Weather (SIGWX) data can now be decoded and visualized in Lightspeed and GXY views, and LuciadFusion WMS/WMTS/WFS services.

Example of a BUFR dataset visualized in Lightspeed

For more details, see:

• The BUFR entry in the Data Formats documentation section
• TLcdBUFRModelDecoder to decode BUFR files containing SIGWX data.
• TLspBUFRLayerBuilder to visualize SIGWX models in a Lightspeed view.
• TLcdBUFRGXYLayerFactory to visualize SIGWX models in a GXY view.
• TLcdBUFRStyleSettings to customize the BUFR visualization.

XML files containing data for the MGCP 2.0.1 Portrayal standard can now be decoded and visualized in Lightspeed and GXY views, and LuciadFusion WMS/WMTS services.

Example of a dataset rendered with MGCP styling

For more details, see:

• The MGCP entry in the Data Formats documentation section
• TLcdMGCPModelDecoder to decode XML files containing MGCP data
• TLspMGCPLayerFactory to visualize MGCP models in a Lightspeed view
• TLcdMGCPGXYLayerFactory to visualize MGCP models in a GXY view

Support for the Hexagon PPM Binz data format. For more details, see

• The Binz entry in the Data Formats documentation section
• TLcdBinzModelDecoder to decode Binz data files
• TLcdOGC3DTilesModelEncoder to convert Binz data to OGC 3D Tiles

TLspMagnifierController: this new controller allows users to zoom in on a part of the view, that is then displayed in a square overlay that follows the mouse position.
In the magnifier overlay, world sized objects are scaled while view sized objects have the same size as in the original view.

The new controller is available in all samples with visual inspection tools (e.g. samples.lightspeed.decoder)

• EPSG:2065
• EPSG:5221
• EPSG:5513
• EPSG:5514
• EPSG:8352
• EPSG:8353

The GXY-specific ECDIS sample has been removed. You can open S-57 data using the generic GXY Decoder sample.

If you need the S-52 display settings UI panel in GXY, you can easily plug that in and use the S52GXYLayerFactory to pick up the S-52 display settings instance. For more information, see the tutorial article "How to customize the S-52 visualization".

The S-63-specific sample have been removed. You can open S-63 data using the regular ECDIS Lightspeed sample, or the generic Lightspeed and GXY Decoder samples.

All these samples will automatically pick up the TLcdS63UnifiedModelDecoder to load S-63 data. Place your Cell Permit files (ENC.PMT or PERMIT.TXT) next to the source data, and make sure you are using the Luciad license that has the corresponding User Permit.

• API users are not expected to have overridden getProcessedEvent();
• Other parts of the API and implementation did enforce the use of AWTEvent.

• All views now have label placing enabled by default. If you don't want advanced label placement or decluttering, you can disable it by calling view.setGXYViewLabelPlacer(null).
• All views now use anti-aliasing by default. To disable this, call view.setAntiAliased(false).
• All views no longer use smart panning by default. To revert this, call view.setSmartPan(true).
• All map implementations (e.g. TLcdMapJPanel) now come with sensible minimum and maximum scale ranges. To revert this, call view.setMinScale(0) and view.setMaxScale(Double.MAX_VALUE).

• wms.crsReferences
• wms.epsgReferences
• wms.auto2References
• wms.autoReferences

TLcdAPP6AEchelonNode.getCodeMask and TLcdMS2525bEchelonNode.getCodeMask have been deprecated. These methods are not compatible with the more recent symbology standards which no longer use code masks (MIL-STD 2525d, APP-6C, APP-6D,...). These methods now always return the name of the echelon.

Use TLcdAPP6AEchelonNode.getName() or TLcdMS2525bEchelonNode.getName() to identify an echelon.

Use TLcdAPP6AEchelonNode.applyOn(ILcdEditableAPP6ACoded) or TLcdMS2525bEchelonNode.applyOn(ILcdEditableMS2525bCoded) to apply the echelon to a symbol.

Support was added for the engagement bar graphical amplifier for the MIL-STD-2525c, MIL-STD-2525d and APP-6D standards.

A new text modifier was added which can be used to set the content of the engagement bar. The name of this text modifier can be accessed trough the static properties ILcdAPP6ACoded.sEngagementBar and ILcdMS2525bCoded.sEngagementBar.

Styling options for the engagement bar are configured using the new class TLcdEngagementBarStyle, which can be set and retrieved from ILcdAPP6AStyle and ILcdMS2525bStyle.

Added an option to disable certain painting optimizations in TLcdS52GXYCatalogueLayer.

By default, these optimizations are enabled, and typically reduce the amount of elements to be painted by 30%. The cost of determining which elements to skip is offset by faster subsequent paints because of spatial locality.

In the context of a WMS server however, you have multiple threads/layers handling requests of multiple users, in different areas. In this case, each layer has to build up the visibility information separately and can re-use it a lot less in subsequent requests.

When using tiled WMS or WMTS, requests don't overlap and are typically cached on the client and/or server.

To use this option in WMS or WMTS, plug in your own ILcdGXYLayerFactory:

      @LcdService(service = ILcdWMSGXYLayerFactory.class, priority = LcdService.HIGH_PRIORITY)
      public class MyWMSLayerFactory implements ILcdWMSGXYLayerFactory {
         @Override
         public ILcdGXYLayer createGXYLayer(ILcdModel aModel, ALcdWMSLayer aWMSLayer, String aStyleID, TLcdWMSRequestContext aContext) {
            TLcdS52GXYCatalogueLayer layer = (TLcdS52GXYCatalogueLayer)
            TLcdS52ProductConfiguration.getInstance(ELcdS57ProductType.ENC).createGXYLayerFactory(displaySettings).createGXYLayer(aModel);
            layer.setMultileveledObjectVisibilityCalculations(false);
            return layer;
         }
      }
    

• Air
• Air Missile
• Space
• Space Missile
• Land Unit
• Land Civilian Organization
• Land Equipment
• Land Installation
• Dismounted Individual
• Sea Surface
• Sea Subsurface
• Mine Warfare
• Activities
• Signals Intelligence - Space
• Signals Intelligence - Air
• Signals Intelligence - Land
• Signals Intelligence - Surface
• Signals Intelligence - Subsurface
• Cyberspace - Space
• Cyberspace - Air
• Cyberspace - Land
• Cyberspace - Surface
• Cyberspace - Subsurface

SLD now supports the use of functions inside SLD Geometry and ParameterValue (such as rotation) elements. On top of the existing capability to use property names, this provides additional flexibility to determine the desired value.

• startAngle(propertyName) and endAngle(propertyName): determine respectively the start and end angle of the referred geometry, measured in degrees clockwise from the direction at 12 o'clock.
• startPoint(propertyName) and endPoint(propertyName): determine respectively the start and end point of the referred geometry.

An example use case combining these new functions and the possibility to use them inside SLD Geometry and ParameterValue elements is the configuration of an arrow head at the end of a polyline. By using a point symbolizer with a geometry defined by the endPoint of the polyline and a rotation defined by the endAngle of the polyline, an oriented arrow icon can be drawn at the end of the polyline.

LuciadLightspeed now supports the eye-dome lighting (EDL) technique to improve depth perception in point cloud data sets. For more details, see the how-to article on eye-dome lighting.

The functionality of changing the EDL parameters is also available in the Lucy UI.

• Removed the enableFeatureTypeNameCompatabilityMode option, now the default behavior should be similar to the behavior that happened when it existed and was set to true.
• Allow multiple data sources within a product that is included in a WFS service. Feature type names will be a combination of product and data name.
• Fixed an issue with quick service creating a product with a name that contains dashes which are not valid in the resulting WFS XML.
• Fixed an issue with GeoMedia not being able to read the LuciadFusion WFS because the namespace definitions don't match between GetCapabilities and DescribeFeatureType.
• Fixed an issue with ArcGIS not able to read 2.0.0 version of WFS because of not handling "(" separated feature types in DescribeFeatureType.

• Single Fence
• Double Fence
• Double Apron Fence
• Low Wire Fence
• High Wire Fence
• Antitank Ditch - Under Construction
• Antitank Ditch - Complete
• Wire Obstacle - Unspecified

The eye-dome lighting technique will be enabled by default when visualizing point cloud data sets. To disable, a custom TLspPointCloudStyle should be used for 3DTile point clouds, or a custom TLspPlotStyle for LIDAR point clouds.
For more details, see the how-to article on eye-dome lighting.

• Fix for possible IndexOutOfBoundsException when encoding a GeoTIFF with JPEG compression.

• Follow And Assume
• Follow And Support
• Direction Of Attack - Main Attack
• Direction Of Attack - Supporting Attack
• Abatis
• Crossing Site/Water Crossing - Lane
• Crossing Site/Water Crossing - Ferry
• Crossing Site/Water Crossing - Raft Site
• Foxhole, Emplacement or Weapon Site
• Linear Target
• Linear Smoke Target
• Final Protective Fire
• Line Of Contact

• Seize
• Withdraw
• Withdraw Under Pressure
• Relief In Place

• Isolate
• Occupy
• Retain
• Secure

      @Override
      public void handleAWTEvent(AWTEvent aEvent) {
        // delivers drag events to #mouseDragged, wheel events to #mouseWheelMoved, and so on
        com.luciad.gui.TLcdAWTUtil.dispatchAWTEvent(aEvent, this);
      }
    

• Fortified Line
• Bearing Line
• Retirement
• Antitank Wall
• Obstacle Restricted Area
• Main Supply Route
• Alternate Supply Route
• Explosive State of Readiness 1 (Safe)
• Explosive State of Readiness 2 (Armed But Passable)
• Roadblock Complete
• Single Concertina
• Double Strand Concertina
• Triple Strand Concertina

Added support for InlandECDIS (IENC) cells that contain regular ENC data.

While this is not according to the specification, data providers often do this. For example, often IENC cells contain both "achare" objects (part of IENC) and "ACHARE" objects (part of regular ENC).

The IENC object classes and attributes now include those from ENC that were not already part of the IENC spec. Similarly, the IENC visualization rules now include the full S-52 rules as a fallback.

If you have IENC cells or catalogs/multicatalogs with only IENC cells, all this will be picked up automatically.

If you have catalogs or multicatalogs that contain cells of product type IENC as well as regular ENC, you have to manually force IENC. This is because the cells themselves contain this information, and are lazy-loaded.

      // Decode the model
      TLcdS57CatalogueModelDecoder decoder = TLcdS57ProductConfiguration.getInstance(ELcdS57ProductType.IENC).createCatalogueModelDecoder();
      decoder.setLoadingPolicy(SOFT_REFERENCED);
      ILcdModel model = decoder.decode("/path/to/CATALOG.031");
    

ILcdLoggerFactory and its implementations are no longer obfuscated so that they can be picked up by the service loader.

You don't need to do anything when you obfuscate your application and include our luciadlightspeed.pro file in your Proguard configuration, as is recommended.

If you use your own Proguard configuration file which does not include luciadlightspeed.pro, you need to add the following lines:

      -keep interface com.luciad.util.logging.ILcdLoggerFactory
      -keep class * implements com.luciad.util.logging.ILcdLoggerFactory
    

• TLcdGXYPolylineLabelPainter
• TLcdGXYPolygonLabelPainter
• TLcdGXYCompositeLabelPainter

• Constructors that know the default image path have been added to the following classes: TLcdGXYCompassNavigationControl, TLcdGXYZoomNavigationControl, TLspAltitudeExaggerationControl, TLspCompassNavigationControl, TLspPanNavigationControl and TLspZoomNavigationControl.
• TLcdGXYNavigationControlsFactory now has a method (createNavigationControls) which allows you to combine a compass and zoom navigation control into a single component.

• MIL-STD-2525 B/C/D
  • 'Reinforced or Detached' got renamed to 'Reinforced or Reduced'
• APP-6 C/D
  • 'Special Headquarters' got renamed to 'Named Headquarters'

TLspTouchNavigateController now extends ALspConfinedTouchController. This fixes a bug where calling startInteraction or terminateInteraction would call those same methods multiple times on the rest of the controller chain.

This could cause problems in any of the appended controllers. For example, when a TLspKeyActionController was appended to it, it would trigger a NullPointerException.

Improved the rendering of both GXY and Lightspeed views on High DPI screens. Accordingly, TLcdImageIcon now supports multiple versions of an icon for different resolutions and uses the proper one according to the DPI scale of the screen.

Note:In most Linux distributions, Java does not pick up the operating system's configured scale factor. You can use the -Dsun.java2d.uiScale VM parameter to manually set the scale factor.

Please refer to the articles Support high-resolution displays on a GXY map and Support high-resolution displays on a Lightspeed map for more information.

• The model decoder is now annotated with the LcdService annotation.
• Introduction of TLcdBingMapsGXYLayerFactory and TLspBingMapsLayerFactory. Both classes are also annotated as LcdService

• Introduced TLcdBingMapsCopyrightIcon#asComponent method allowing to convert the copyright icon in a component which can be added to a Swing UI
• Introduced the TLcdBingMapsLogoIcon class (including a similar asComponent method), making it easy to add the Bing Maps icon to a Swing UI

Lightspeed views now support high DPI rendering. This means that fonts, icons and other map elements will be automatically resized in proportion to the DPI scale factor configured in the operating system. Due to the way high DPI support is implemented in Swing, however, applications that use a Lightspeed view now essentially have an additional coordinate system to deal with, which we refer to as "toolkit coordinates". In most scenarios this is merely an implementation detail. Applications may need to be adjusted to work correctly with DPI scaling if they

• use the methods in ALspViewXYZWorldTransformation to transform between UI coordinates and geographic coordinates;
• contain custom implementations of ILspController.

Please refer to the javadoc of ALspViewXYZWorldTransformation for more information on toolkit coordinates and DPI scaling.

• ILcdDatabaseDecoder
• ILcdDatabaseDecoder2
• TLcdDatabaseModel
• TLcdDatabaseReadOnlyModel

ALspDensityStyle.Builder and subclasses: the public constructors have been removed. Creating your own density style (builder) instances was never supported. Removing the constructors makes this clear.

If you called the public constructor of TLspDensity...Style.Builder, use the TLspDensity...Style#newBuilder method instead.

ILcdGXYPen and ILcdAWTPath now support double coordinates to improve precision in HiDPI views. Hereafter methods accepting integer coordinates accept double coordinates.

In the unlikely event that you have a custom ILcdGXYPen or ILcdAWTPath implementation, you may have to modify it to use double coordinates as well, or alternatively convert the double coordinates to integers.

The following classses inherit ALcdGXYPen, and they were updated accordingly to be able to use double coordinates.

• TLcdGeodeticPen
• TLcdGridPen
• TLcdProjectionPen
• TLcdGXYPen

Accordingly, the type of the protected field ALcdGXYPen#fLastAWTPoint has been changed to TLcdXYPoint and the field has been renamed as fLastViewPoint.

• Support for decoding TIFF files using floating point predictor 3 (TIFF Technical Note 3) has been added.
• It improves on memory usage needed for reading the image metadata for large (Big)TIFF files when decoding the model.

LuciadLightspeed now uses LWJGL as its Java binding for the OpenGL and OpenCL APIs (instead of the JogAmp libraries used by previous versions). This means that the following JAR files are no longer part of the release:

• gluegen-rt-<version>.jar
• gluegen-rt-<version>-natives-<platform>.jar
• jocl-<version>.jar
• jocl-<version>-natives-<platform>.jar
• jogl-all-<version>.jar
• jogl-all-<version>-natives-<platform>.jar

The following JARs have been added to replace the above:

• lwjgl-<version>.jar
• lwjgl-<version>-natives-<platform>.jar
• lwjgl-jawt-<version>.jar
• lwjgl-opencl-<version>.jar
• lwjgl-opengl-<version>.jar
• lwjgl-opengl-<version>-natives-<platform>.jar

Users upgrading from LuciadLightspeed V2018.x or earlier to V2019.0 may need to adapt their IDE settings or build scripts to reflect these changes.

Additionally, the migration to LWJGL has also brought with it some changes to how Lightspeed views deal with NIO buffers. The most visible result of these changes is that some data which was previously stored in native memory, will now be stored on the heap. As a result, upgrading an application from an older version of LuciadLightspeed to V2019.0 or newer may result in the application using less native memory and more heap memory. This may require some adjustment of JVM parameters, especially for applications that were tuned to run within tight memory constraints.

Finally, some of the API surrounding ALcdGLBinding has been changed incompatibly:

• ILcdGLBuffer et al. have been removed. All API methods that used this interface now accept only java.nio.Buffer and/or primitive arrays. Applications that used these API methods will have to be updated accordingly. Note that the new class TLcdGLNIOBufferFactory should be used to allocate buffers that are intended to be passed to OpenGL calls.
• The interface ILcdGL has been streamlined and now contains only the OpenGL core and compatibility profile API (i.e. no OpenGL extensions). It has, however, been updated to cover all OpenGL versions up to and including OpenGL 4.6. Applications that contain custom OpenGL code and use certain OpenGL extensions, can access these extensions by calling LWJGL directly. This is safe and easy to do since LWJGL exposes the OpenGL API entry points as static methods.
• ILcdGL has also been stripped of method overloads that take a primitive array followed by an array offset parameter. Applications that use these methods should use an NIO buffer instead, positioned to the appropriate offset.
• The methods makeCurrent(), canMakeCurrent() and release(), which were previously deprecated, have now been removed from ILcdGLDrawable. To execute code that requires an active OpenGL context, use the drawable's invokeLater() or invokeAndWait() methods instead.
• The previously deprecated displayChanged() method has been removed from ILcdGLEventListener. The method was never called by any implementation of ILcdGLDrawable.

• the decoder was configured to create multiple levels automatically for files having only a single level of detail
• the data had 4 samples/pixel

• 25110101: Boundary - Lateral
• 25110102: Boundary - Forward
• 25110103: Boundary - Rear
• 25110200: Light Line
• 25110300: Engineer Work Line
• 25120100: Area Of Operations
• 25120200: Named Area Of Interest
• 25120300: Target Area Of Interest
• 25120400: Airfield Zone
• 25120500: Base Camp
• 25120600: Guerrilla Base
• 25140100: Forward Line Of Troops
• 25140300: Phase Line
• 25140400: Forward Edge Of The Battle Area
• 25140900: Limit Of Advance
• 25141000: Line Of Departure
• 25141100: Line Of Departure / Line Of Contact
• 25141500: Holding Line (HL)
• 25150200: Assembly Area (AA)
• 25150501: Action Area - Joint Tactical Action Area (JTAA)
• 25150502: Action Area - Submarine Action Area (SAA)
• 25150503: Action Area - Submarine-Generated Action Area (SGAA)
• 25150700: Extraction Zone (EZ)
• 25150800: Landing Zone (LZ)
• 25151000: Fortified Area
• 25151200: Battle Position
• 25151203: Battle Position - Strong Point
• 25151205: Battle Position - Retain
• 25151300: Engagement Area (EA)
• 25151403: Axis Of Advance - Main Attack
• 25151404: Axis Of Advance - Supporting Attack
• 25151600: Attack Position
• 25151700: Objective Area
• 25151800: Encirclement
• 25170100: Air Corridor
• 25170101: Air Corridor - Air Corridor With Multiple Segments
• 25170200: Low-Level Transit Route
• 25170300: Temporary Minimum-Risk Route
• 25170400: Safe Lane
• 25170500: Standard Use Army Aircraft Flight Route (SAAFR)
• 25170600: Transit Corridors
• 25170700: Special Corridor
• 25170800: Base Defence Zone
• 25170900: High-Density Airspace Control Zone
• 25171000: Restricted Operations Zone (ROZ)
• 25171100: Air-to-Air Restricted Operations Zone (AARROZ)
• 25171200: Unmanned Aircraft Restricted Operations Zone (UA-ROZ)
• 25171300: Weapon Engagement Zone
• 25171400: Fighter Engagement Zone (FEZ)
• 25171500: Joint Engagement Zone (JEZ)
• 25171600: Missile Engagement Zone (MEZ)
• 25171700: Low (Altitude) Missile Engagement Zone (LOMEZ)
• 25171800: High (Altitude) Missile Engagement Zone (HIMEZ)
• 25171900: Short Range Air Defence Engagement Zone (SHORADEZ)
• 25172000: Weapons Free Zone
• 25190100: Identification, Friend-or-Foe (IFF) Off Line
• 25190200: Identification, Friend-or-Foe (IFF) On Line
• 25240101: Airspace Coordination Area (ACA) - Irregular
• 25240102: Airspace Coordination Area (ACA) - Rectangular
• 25240103: Airspace Coordination Area (ACA) - Circular
• 25240201: Free Fire Area (FFA) - Irregular
• 25240202: Free Fire Area (FFA) - Rectangular
• 25240203: Free Fire Area (FFA) - Circular
• 25240301: No Fire Area (NFA) - Irregular
• 25240302: No Fire Area (NFA) - Rectangular
• 25240303: No Fire Area (NFA) - Circular
• 25240401: Restricted Fire Area (RFA) - Irregular
• 25240402: Restricted Fire Area (RFA) - Rectangular
• 25240403: Restricted Fire Area (RFA) - Circular
• 25240601: Point Targets - Point or Single Target
• 25240602: Point Targets - Nuclear Target
• 25240603: Point Targets - Target-Recorded (Aegis Only)
• 25240701: Linear Targets - Linear Target
• 25240702: Linear Targets - Linear Smoke Target
• 25240703: Linear Targets - Final Protective Fire (FPF)
• 25240801: Area Targets - Area Target
• 25240802: Area Targets - Rectangular Target
• 25240803: Area Targets - Circular Target
• 25240804: Area Targets - Rectangular Target - Single Target (Aegis Only)
• 25240805: Area Targets - Series or Group Of Targets
• 25240806: Area Targets - Smoke
• 25240808: Area Targets - Bomb Area
• 25241001: Fire Support Area - Irregular
• 25241002: Fire Support Area - Rectangular
• 25241003: Fire Support Area - Circular
• 25241101: Artillery Target Intelligence Zone (ATI) - Irregular
• 25241102: Artillery Target Intelligence Zone (ATI) - Rectangular
• 25241103: Artillery Target Intelligence Zone (ATI) - Circular
• 25241201: Call for Fire Zone (CFFZ) - Irregular
• 25241202: Call for Fire Zone (CFFZ) - Rectangular
• 25241203: Call for Fire Zone (CFFZ) - Circular
• 25241401: Critical Friendly Zone (CFZ) - Irregular
• 25241402: Critical Friendly Zone (CFZ) - Rectangular
• 25241403: Critical Friendly Zone (CFZ) - Circular
• 25241601: Sensor Zone - Irregular
• 25241602: Sensor Zone - Rectangular
• 25241603: Sensor Zone - Circular
• 25241801: Target Value Area - Irregular
• 25241802: Target Value Area - Rectangular
• 25241803: Target Value Area - Circular
• 25242100: Weapon/Sensor Range Fan, Circular
• 25242200: Weapon/Sensor Range Fan, Sector
• 25260100: Fire Support Coordination Line (FSCL)
• 25270100: Obstacle Belt
• 25270200: Obstacle Zone
• 25270400: Obstacle Restricted Zone
• 25270504: Obstacle Effects - Turn
• 25270800: Mined Area
• 25270900: Decoy Mined Area
• 25270901: Decoy Mined Area - Fenced
• 25271000: Unexploded Explosive Ordnance (UXO) Area
• 25271100: Bridge or Gap
• 25271201: Roadblocks, Craters, and Blown Bridges - Planned
• 25271202: Roadblocks, Craters, and Blown Bridges - Explosives, State Of Readiness 1 (Safe)
• 25271203: Roadblocks, Craters, and Blown Bridges - Explosives, State Of Readiness 2 (Armed But Passable)
• 25271204: Roadblocks, Craters, and Blown Bridges - Roadblock Complete (Executed)
• 25271400: Bridge
• 25271700: Biological Contaminated Area
• 25271701: Biological Contaminated Area - Toxic Industrial Material
• 25271800: Chemical Contaminated Area
• 25271801: Chemical Contaminated Area - Toxic Industrial Material
• 25271900: Nuclear Contaminated Area
• 25272000: Radiological Contaminated Area
• 25272001: Radiological Contaminated Area - Toxic Industrial Material
• 25272100: Minimum Safe Distance Zone
• 25272200: Radiation Dose Rate Contour Line
• 25290100: Obstacle Line
• 25290900: Fortified Line
• 25300100: Intelligence Coordination Line
• 25310100: Detainee Holding Area
• 25310200: Enemy Prisoner Of War Holding Area
• 25310300: Forward Arming and Refuelling Point (FARP)
• 25310400: Refugee Holding Area
• 25310500: Regimental Support Area
• 25310600: Brigade Support Area (BSA)
• 25310700: Division Support Area
• 25330100: Moving Convoy
• 25330200: Halted Convoy
• 25330300: Main Supply Route (MSR)
• 25330301: Main Supply Route (MSR) - One Way Traffic
• 25330302: Main Supply Route (MSR) - Two Way Traffic
• 25330303: Main Supply Route (MSR) - Alternating Traffic
• 25330400: Alternate Supply Route (ASR)
• 25330401: Alternate Supply Route (ASR) - One Way Traffic
• 25330402: Alternate Supply Route (ASR) - Two Way Traffic
• 25330403: Alternate Supply Route (ASR) - Alternating Traffic
• 25340600: Counter Attack
• 25340800: Delay
• 25341100: Fix
• 25341300: Follow and Support
• 25341500: Isolate
• 25341700: Occupy
• 25342000: Retire/Retirement
• 25342100: Secure
• 25342201: Security - Cover
• 25342202: Security - Guard
• 25342203: Security - Screen
• 25342300: Seize
• 25342400: Withdraw

• Labels no longer disappear when the rectangular target gets too small
• Space between two words in a label has been reduced
• Hostility indication labels (ENY) are no longer painted for the Rectangular Target symbol
• Label text is always painted upright and no longer follows the slope of the axis line of the rectangle

• 2.X.3.1.1.1 - Belt
• 2.X.3.1.1.2 - Line
• 2.X.3.1.1.3 - Zone
• 2.X.3.1.1.4 - Obstacle Free Area

• 2.X.3.1.1.1 - Belt
• 2.X.3.1.1.2 - Line
• 2.X.3.1.1.3 - Zone
• 2.X.3.1.1.4 - Obstacle Free Area

• 25260100 - Fire Support Coordination Line (FSCL)
• 25260200 - Coordinated Fire Line (CFL)
• 25290100 - Obstacle Line
• 25270300 - Obstacle Free Zone

• 2.X.2.2.1.1.2 - Line
• 2.X.2.2.1.1.3 - Zone
• 2.X.2.2.1.9 - Obstacle Free Area

• 2.X.2.2.1.1.2 - Line
• 2.X.2.2.1.1.3 - Zone
• 2.X.2.2.1.9 - Obstacle Free Area

• 25260100 - Obstacle Belt
• 25260200 - Obstacle Zone
• 25270100 - Obstacle Line
• 25260300 - Obstacle Free Zone

• For GML 3.1 / 3.2 responses, linear GML elements are used by default. This makes sure that ILcdPolyline and ILcdPolygon instances are respectively encoded to LineString and LinearRing elements, regardless of their interpolation. Previously, GeodesicString elements were used for a geodesic interpolation.
• The sample WFS server now uses qualified feature type names by default. Additionally, these feature type names are reused as XML element names in the GML output data.

• MIL-STD-2525 B: 2.X.4.3.1.1 - Rectangular Target
• MIL-STD-2525 C: 2.X.4.3.1.1 - Rectangular Target
• MIL-STD-2525 D: 100025000024080200001 - Rectangular Target
• APP6-C: 10002500002306000000 - Rectangular Target

TLcdWMMMagneticNorthMap#setIgnoreModelLifeSpan and TLcdWMMMagneticNorthMap#setInputStreamFactory can now be called even before the data files have been set.

Additionally, improved the error output for methods that cannot be called before the data files have been set.

• parseObject(String) now throws a ParseException instead of an IllegalArgumentException.
• parseObject(String, ParsePosition) now returns null instead of throwing an IllegalArgumentException.

Fixed an issue with loading S-63 cell permits concurrently for multiple S-63 datasets, causing errors and missing cells.

In case where a single S-63 model decoder was used for multiple S-63 models, they share cell permit files. When displaying these models, these cell permit files were decoded concurrently, depending on timing. However, certain aspects of the IHO S-63 permit file decoding were not thread-safe, causing errors, that caused some permits to be skipped.

The end result was that some cell were not displayed. This is now resolved.

• TLcdWFSDataSource.Builder.uri: now supports the use of the parameters 'data', 'typename' and 'typenames' to automatically set the desired feature type name.
• TLcdWMSDataSource.Builder.uri: now supports the use of the parameters 'data', and 'layers' to automatically set the desired layer(s); additionally, the parameters 'styles' and 'format' can be used to respectively set the layer style(s) and desired format.
• TLcdWMTSDataSource.Builder.uri: now supports the use of the parameter 'data' to automatically set the desired layer, similar to the existing supported parameter 'layer'.
• TLcdWCSDataSource.Builder.uri: now supports the use of the parameters 'data' and 'coverage' to automatically set the desired coverage name.

Added TLfnPointCloudPreprocessor to the Fusion API. This API lets you preprocess point cloud file such as LAS, LAZ or E57 so they can efficiently be served in LuciadFusion Studio. LuciadFusion Studio automatically preprocesses any point cloud file that is served as OGC 3D Tiles. The difference is that this preprocessor lets you perform the preprocessing as part of a separate process. The output can be served directly with LuciadFusion Studio without further processing requirements.

The TLfnPointCloudPreprocessor has a command-line sample that you can find in samples.fusion.pointcloud.PointCloudPreprocessorTool.

The GeoTIFF model decoder registers such a function to the model such that file descriptors are closed on disposal of the model. There is no need anymore to do this yourself for GeoTIFF.

Partial support for the military standard APP-6D has been added. It is now possible to create and visualize TLcdEditableAPP6AObject instances using the APP-6D 20-digit SIDC codes. TLcdAPP6ANode also exposes the new domain hierarchy.

The supported symbol sets are:

• 00: Unknown
• 01: Air
• 02: Air Missile
• 05: Space
• 10: Land Unit
• 11: Land Civilian Organization
• 15: Land Equipment
• 20: Land Installation
• 27: Dismounted Individual
• 30: Sea Surface
• 35: Sea Subsurface
• 36: Mine Warfare
• 37: Activities

Improved the rendering of T-shaped and U-shaped military symbols in the APP-6 / MIL-STD 2525 standards.

The updated symbol set are:

• Block
• Breach
• Bypass
• Canalize
• Clear
• Contain
• Penetrate
• Bypass Easy
• Bypass Difficult
• Bypass Impossible

Affected symbols

APP6-C

Affected symbols

APP6-A / APP6-B

Affected symbols

MIL-STD-2525 B / MIL-STD-2525 C

• Spring Boot (version 2.1.0.RELEASE)
• Spring Core (version 5.1.2.RELEASE)
• Spring AOP (version 5.1.2.RELEASE)
• Spring Beans (version 5.1.2.RELEASE)
• Spring Expression (version 5.1.2.RELEASE)
• Spring Context (version 5.1.2.RELEASE)
• Spring JDBC (version 5.1.2.RELEASE)
• Spring Security LDAP (version 5.1.1.RELEASE)
• Spring Boot Starter (version 2.1.0.RELEASE)
• Spring Boot Starter Actuator (version 2.1.0.RELEASE)
• Spring Boot Starter Security (version 2.1.0.RELEASE)
• Spring Boot Starter Web (version 2.1.0.RELEASE)
• Spring Boot Starter Websocket (version 2.1.0.RELEASE)
• Spring Boot Configuration Processor (version 2.1.0.RELEASE)
• Spring Cloud Eureka (version 2.1.0.M1)
• HikariCP (version 3.2.0)
• Jackson (version 2.9.7)
• Gson 2.8.7
• JAXB Api (version 2.3.1)
• JAXB Implementation (version 2.3.0.1)
• Javax Annotation API (version 1.3.2)

• server.context-path property has been changed to server.servlet.context-path.
• server.session.timeout property has been changed to server.servlet.session.timeout.
• management.context-path has been renamed as management.server.servlet.context-path, therefore the properties which use it have been adjusted accordingly. endpointPattern of fusion.actuators.security.authenticatedEndpoints has been changed.
• Property 'management.security.enabled' is deprecated, there is no longer a separate security auto-configuration for the Actuators. For more information please refer Spring Boot 2.0 Migration Guide - Actuator Security
• Property 'security.basic.enabled' is deprecated, the security auto-configuration is no longer customizable.
• management.endpoints.web.exposure.include has been added to determine which actuator endpoints will be exposed. For more information about the Actuator configuration, please refer to:
  • the production template,
  • Spring Boot 2.0 Migration Guide - Actuator Migration

• ILcdGLBufferFactory and ILcdGLBuffer should be replaced by the equivalent java.nio.Buffer constructs.
• The makeCurrent(), canMakeCurrent() and release() methods of ILcdGLDrawable are prone to improper use. Code that requires an active OpenGL context outside of a regular repaint cycle should instead be scheduled using the invokeLater() or invokeAndWait() method of the drawable.
• ILcdGLEventListener#displayChanged() is never called by any current implementations of ILcdGLDrawable. The init() method serves essentially the same purpose and should be used instead.

• Spring-plugin (version 1.2.0.RELEASE)
• Swagger-Core (version 1.5.20)
• SpringFox (version 2.9.2)

• Guava (version 20.0)

• inverted-color images for jpeg output.
• non-transparent images for png output with requested transparency for the map background.

The ECDIS decoders and visualization now support InlandECDIS (IENC).

You can simply use TLcdS57UnifiedModelDecoder to decode an IENC CATALOG.031 or.000 cell file. The product type will be ELcdS57ProductType.IENC.

The decoder supports IENC versions 2.0, 2.1, 2.2, 2.3 and 2.4. The visualization will use the display rules from IENC 2.4.

To visualize the data in a Lightspeed view, use TLspS52LayerBuilder.

To visualize the data in a GXY view, use TLcdS52GXYLayerFactory.

You can configure your ship's beam and air draft on the S-52 display settings (see TLcdS52DisplaySettings). These settings affect the visualization of the safety of fixed bridges.

If necessary, you can also use TLcdS57ProductConfiguration and TLcdS52ProductConfiguration with product type IENC to have more fine-grained control over the decoding and/or visualization, as described in Chapter 12 of the Maritime Standards Developer's Guide.

The TLfnRasterCoverageMetadata now allows to define an area of interest (bounding box), which is used to clip the data within the raster coverage. This does not affect the coverage tile set structure which is determined by the bounding box.

Note that the version number of the tile store format has been updated for this.

• Callsign
• IFPSFlightId and all its subproperties
• FlightCategory and all its subproperties
• TypeOfAircraft
• WakeTurbulenceCategory
• DepartureAirport
• DestinationAirport

• replace it with a call to TLcdFeatureIndexedAnd2DBoundsIndexedModel#setClassTraceOn, which results in the same behaviour as before, or
• call the method on a specific instance of the class.

• ApronElement: If there is an associated Apron, the value of TLcdAIXM51ApronTimeSlice.APRON_NAME_PROPERTY of Apron is used as name of the ApronElement.
• RunwayElement: If there is an associated Runway, the value of TLcdAIXM51RunwayTimeSlice.NAME_PROPERTY of Runway is used as name of the RunwayElement.
• TaxiwayElement: If there is an associated Taxiway, the value of TLcdAIXM51TaxiwayTimeSlice.NAME_PROPERTY of Taxiway is used as name of the TaxiwayElement.

• The 3D Tiles Developer's Guide
• The javadoc of TLcdOGC3DTilesModelDecoder on how to decode OGC 3D Tiles
• The javadoc of TLcdOSGBModelDecoder on how to decode OSGB files
• The javadoc of TLsp3DTileLayerBuilder on how to visualize such data

• TLspParameterizedIconStyle
• TLspParameterizedLineStyle
• TLspParameterizedFillStyle

The sample package samples.lightspeed.style.expressions contains a sample demonstrating how the parameterized styles can be used.

These styles can be used for dynamic and static data sets. However, for large static point data sets, it is recommended to use TLspPlotLayerBuilder.