The default WMS and WMTS GetLegendGraphic support for layers styled with an SLD did not take into account the color of a polygon symbolizer if it was defined inside a mark.

Bug fixLuciadFusion

LCD-13508

The following WCS server issues have been fixed related to the handling of the optional "Sections" parameter in a GetCapabilities request:

The parameter was not supported for WCS 1.1 POST requests.
The parameter was not validated for WCS 1.0 GET and POST requests.

Dimensions with an axis without a unit.
Dimensions with strings as possible values.

Upgrade considerationLuciadFusion

LCD-13414

Fixed a potential deadlock when modifying the ILcdCollection that is returned by ILspInteractivePaintableLayer#getObjectsWithPaintState, while holding a write lock on that collection. To fix this, ILcdCollection (and by extension ILcdList) now have additional methods that allow specifying an ILcdFireEventMode when performing modifications. By using the ILcdFireEventMode.FIRE_LATER event mode, collection change events are fired after the write lock has been released.

We recommend scanning your codebase for any custom usages of ILspInteractivePaintableLayer#getObjectsWithPaintState and making sure that any modifications to this collection happen within a write lock, while the change events are only fired after that write lock has been released. An example code snippet on how to do this can be found in the ILspInteractivePaintableLayer#getObjectsWithPaintState method javadoc.

ImprovementLuciadFusion

LCD-13396

The implementations of com.luciad.format.dafif.TLcdDAFIFModelDecoder#canDecodeSource and com.luciad.format.coverage.TLcdCoverageModelDecoder#canDecodeSource have been optimized. This also improves crawling performance of data inside LuciadFusion, which is now up to 24% faster.

ImprovementLuciadFusion

LF-2592

LuciadFusion Studio can now correctly parse the model reference and bounds of HSPC datasets that define their reference as a "projection-wkt" property in the hspcInfo.json file.

ImprovementLuciadFusion

LCD-12583

The existing article Using LuciadLightspeed in a Maven repository has been extended with a section about using BOM files.

ImprovementLuciadFusion

LCD-10417

The TLcdGeoPackageModelDecoder and TLcdGeoPackageModelEncoder now have support for the following geometry types:

MULTICURVE

MULTISURFACE

LCD-13474

TLcdEPSGReferenceParser parsed the TOWGS84 rotation incorrectly for some EPSG codes. Coordinate references using the following datums are affected:

IG05/12 Intermediate Datum (EPSG:1144)
World Geodetic System 1984 (G730) (EPSG:1152)
World Geodetic System 1984 (Transit) (EPSG:1166)
CR-SIRGAS (EPSG:1225)
Sistem Referensi Geospasial Indonesia 2013 (EPSG:1293)
International Terrestrial Reference Frame 1992 (EPSG:6651)

Bug fixLuciadFusion

LF-2620

Updated the value of the cache.maxAge properties to 30 days, which corresponds to the value mentioned in the documentation.

The following caching properties have been updated:

fusion.ogctilesservice.cache.maxAge
fusion.panoramics.cache.maxAge
fusion.studio.webapp.cache.maxAge

Bug fixLuciadFusion

LCD-13429, LCD-13432

The WMTS model decoder now skips tile matrix sets with an unknown geographic reference instead of throwing an UnsupportedOperationException.

Bug fixLuciadFusion

LCD-13431

The WMTS model decoder used an incorrect geographic reference when creating a model for a WMTS layer backed by a GoogleCRS84Quad tile matrix set that used a reference with a lat/lon axis order. This prevented the layer from being visualized on the map.

Bug fixLuciadFusion

LCD-13379

TLcdOGC3DTilesModelDecoder: fixed an issue when opening Luciad Point Cloud datasets by passing a file URL.

Bug fixLuciadFusion

New featureLuciadFusion

The Spring Boot dependencies of LuciadFusion have been upgraded from version 2.7 to version 3.2. 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.

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

New featureLuciadFusion

TLcdMBTilesModelDecoder now also supports MBTiles services, next to files. To decode an MBTiles service you need to provide the TileJSON endpoint as source. An MBTiles service can for example be set up with LuciadFusion as of version 2024.0.

New featureLuciadFusion

TLcdGeoTIFFModelDecoder : com.luciad.format.raster.TLcdGeoTIFFModelDecoder.referenceDecoderPriority
TLcdLASModelDecoder : com.luciad.format.las.TLcdLASModelDecoder.referenceDecoderPriority
TLcdE57ModelDecoder : com.luciad.format.e57.TLcdE57ModelDecoder.referenceDecoderPriority

The priority decides whether the model reference decoding is first attempted from the reference information embedded in the data file and then fall back to external reference source files such as WKT (.prj), REF (.ref) and EPSG (*.epsg) in case of an error or vice versa when the other reference decoder priority is selected.

For more information on how to configure the reference decoder priority for supported ILcdModelDecoder implementations, refer to the following article: Setting model reference decoder priority

ImprovementLuciadFusion

LCD-13341

The metadata in the gpkg_data_columns table of a GeoPackage file is now used by TLcdGeoPackageModelDecoder to provide the correct display names in TLcdDataModelDisplayNameProvider#getDisplayName(TLcdDataProperty).

ImprovementLuciadFusion

The included Apache Ant distribution has been upgraded to version 1.10.14. This improves compatibility with Java 21.

ImprovementLuciadFusion

Products with cartesian referenced data can now be added to a WFS service.

ImprovementLuciadFusion

LCD-13289

It is now possible to customize the tile grid reference used by the tiled WMS painters for GXY and Lightspeed views. The tile grid reference can be specified through a newly added constructor in TLcdGXYTiledWMSProxyPainter and TLspTiledWMSProxyPainter. Customizing tile grid references can be useful to align with a server-defined tile grid reference used for caching of requests.

ImprovementLuciadFusion

LuciadLightspeed and LuciadFusion now support Java 21. Refer to the documentation on hardware and software requirements in the prerequisites section for more information.

ImprovementLuciadFusion

LCD-8681, LCD-13260

Introduced TLcdDataProperty#getSourceName, which contains the property name as it was defined in the source data. This may differ from the actual name of the property within the TLcdDataType, because that name can contain only alphanumeric characters and underscores, and may therefore have been sanitized.

When building a data type, the source name of a property can be configured with a setter on the TLcdDataPropertyBuilder. Additionally, TLcdDataType#getProperty now also checks this source name when searching a property that matches a given name.

The default TLcdDataModelDisplayNameProvider has also been adapted to use this source name by default, when retrieving a display name for a property.

Finally, The TLcdGeoJsonModelEncoder now uses these source names by default as well, when encoding data objects to GeoJSON features.

ImprovementLuciadFusion

LF-1958

To ease using HTTP/2 with LuciadFusion, the following improvements have been introduced:

A new article How to use HTTP/2 with LuciadFusion has been introduced.
HTTP/2 is now enabled by default in the LuciadFusion Platform configuration.
In order to enable HTTP/2 with the sample Jetty server shipped with LuciadFusion, we have included the following sample dependencies:

Group ID	Artifact ID ID	Version
org.eclipse.jetty.http2	jetty-http2-common	12.0.7
org.eclipse.jetty.http2	jetty-http2-hpack	12.0.7
org.eclipse.jetty.http2	jetty-http2-server	12.0.7
org.eclipse.jetty	jetty-alpn-conscrypt-server	12.0.7
org.eclipse.jetty	jetty-alpn-server	12.0.7
org.conscrypt	conscrypt-openjdk-uber	2.5.2

ImprovementLuciadFusion

The LuciadFusion Studio REST API endpoint GET /api/data/filter now allows filtering Data resources by data categories and keywords. These properties are also listed by the GET /api/data/queryable-properties endpoint. More information on how you can use the GET /api/data/filter endpoint can be found in the data querying article.

ImprovementLuciadFusion

Bug fixLuciadFusion

LF-2579

The list of privileges required by LuciadFusion when using an Oracle database was updated to include the SELECT ON SYS.DBA_RECYCLEBIN privilege. A warning is shown if this privilege is not granted to the user used by LuciadFusion to connect to the database.

Bug fixLuciadFusion

LCD-12748

Fixed an issue in the TLcdGeoTIFFModelDecoder for the case of data with photometric interpretation RGB with additional sample values. The standard cases RGB(A) worked fine. For the case with additional sample values the ALcdImage band semantics did not include information on the red, green, and blue channels. It would be interpreted as a greyscale image by the image painter. Now the correct band semantics are reported which makes the image painter pick it up and render the file correctly.

Upgrade considerationLuciadFusion

We now enable support for vertical datums by default for a number of model decoders. If your services require preprocessing (such as LTS and OGC 3D Tiles) and you encounter issues with vertical datum application, you may need to preprocess the involved data again to ensure correct application of the vertical datum support. Preprocessing again is only necessary if you have other data with vertical datums and observe inconsistencies. Inconsistencies occur when combining the following data:

Data which is served by an LTS or OGC 3D Tiles service, which has not applied the vertical datum. This usually occurs because the service was created with an older LuciadFusion version (2023.1 or older), which did not enable vertical datum support by default.
Data which is loaded directly into a client application, is served by a service which does not do preprocessing or is served by a new LTS or OGC 3D Tiles service, which has been created in LuciadFusion 2024.0.

More information about enabling support for vertical datums by default is given in the release note for issue LCD-12921.

Upgrade considerationLuciadFusion

LuciadLightspeed and LuciadFusion now increasingly make use of Java's own file and URI handling API to improve reliability, consistency, and portability when handling data sources. This includes, but is not limited to TLcdIOUtil, TLcdInputStreamFactory, and several model decoders. Because of this, the following invalid data source paths may no longer be recognized:

The colon ":" is no longer accepted in Windows file names.
Spaces are no longer accepted in file URI's. They need to be escaped as described in the URI specification.

Make sure to correct these source names before passing them to the API.

Upgrade considerationLuciadFusion

LuciadLightspeed and LuciadFusion no longer support 32-bit JDKs. Previously there was still limited support for Linux.

Upgrade considerationLuciadFusion

The minimum supported glibc (GNU C Library) for Linux has been raised to 2.28. This means that Ubuntu 18 is no longer supported.

Upgrade considerationLuciadFusion

LCD-12921

The default behavior of a number of model decoders has been changed. We now enable support for vertical datums by default for a number of model decoders. The vertical datum support will cause the appropriate geoid height to be applied to data files of the affected formats, if the data advertises a vertical datum. In previous versions, we ignored the vertical datum advertised by data by default.

Using the geoid will result in the use of more accurate elevation values, at the cost of performance when processing the data.

The following data formats are affected by this change:

DEM: TLcdDEMModelDecoder
DMED/DTED: TLcdDMEDModelDecoder, TLcdDTEDModelDecoder, TLcdDTEDDirectoryModelDecoder
ETOPO: TLcdETOPOModelDecoder
GeoTIFF: TLcdGeoTIFFModelDecoder
LAS/LAZ: TLcdLASModelDecoder
SwissDHM: TLcdSwissDHMMatrixModelDecoder

Because the default behavior has changed for these formats, your data may be painted at a different height, which can cause misalignment with your other layers. For example, you may apply the geoid to points in a LAS file, which causes your LAS points to be painted at a different elevation. If you combine this LAS data with an inaccurate terrain layer, there may be overlap between your LAS points and the terrain layer. You should check that your data is still properly aligned with your other layers after upgrading.

The recommended way to fix such alignment issues is to make sure you use an accurate terrain layer and use the same geoid on all your layers with elevation data. You should also verify that all your elevation data advertises the correct vertical datum. Read our article on Detecting and fixing vertical datum issues for more details.

If you have different behavior then before, and you are sure that the old behavior is preferred, you can revert to the old behavior in the following ways:

Disable geoid support for a specific model decoder, by calling the method #setSupportGeoidDatums(boolean)
Disable geoid support for all aforementioned model decoders, by setting the system property com.luciad.geodesy.geoidSupport.LEGACY to true.

Upgrade considerationLuciadFusion

Since the upgrade to Spring Security version 6, Spring Security blocks all requests for which no authorization rule is defined. In order to register authorization rules for services in LuciadFusion, a few changes have been made in the LuciadFusion configuration and the ILfnServiceTypeConfiguration interface, which makes it possible to plug in custom service types in LuciadFusion

The documentation changes consist of 2 new properties: fusion.security.serviceAuthenticationRequired and fusion.security.authenticatedEndpoints

fusion.security.serviceAuthenticationRequired allows you to globally configure if services published in LuciadFusion require authentication or if anonymous access is permitted.
fusion.security.authenticatedEndpoints allows you to override the configuration set by fusion.security.serviceAuthenticationRequired for certain url patterns. This can, for example, be used if you want to allow anonymous access for all services except services of a certain type (wms, wfs, lts, etc)

Additionally we have deprecated the property fusion.accessControl.authenticatedEndpoints. This property used to only have an effect when access control is enabled, it is now replaced by fusion.security.authenticatedEndpoints, which is also active when access control is disabled. If you are using fusion.accessControl.authenticatedEndpoints, this configuration will still be applied, but this property will be removed in a future LuciadFusion release, so we recommend that you replace its usage by fusion.accessControl.authenticatedEndpoints.

We have added the method getEndpointPatterns() to he interface ILfnServiceTypeConfiguration. This method is used to inform the LuciadFusion Security system of which url patterns are handled by the service type implementation.

Please read the following articles for more information:

Upgrade considerationLuciadFusion

Security updates have been applied to the following sample dependencies of the OGC server sample:

Group ID	Artifact ID	Old Version	New Version
org.springframework.boot	spring-boot	2.7.14	3.2.1
org.springframework.boot	spring-boot-starter	2.7.14	3.2.1
org.springframework.boot	spring-boot-autoconfigure	2.7.14	3.2.1
org.springframework.boot	spring-boot-starter-jetty	2.7.8	3.2.1
org.springframework.boot	spring-boot-starter-json	2.7.14	3.2.1
org.springframework.boot	spring-boot-starter-logging	2.7.14	3.2.1
org.springframework.boot	spring-boot-starter-web	2.7.14	3.2.1
org.springframework	spring-aop	5.3.29	6.1.2
org.springframework	spring-beans	5.3.29	6.1.2
org.springframework	spring-context	5.3.29	6.1.2
org.springframework	spring-core	5.3.29	6.1.2
org.springframework	spring-expression	5.3.29	6.1.2
org.springframework	spring-jdbc	5.3.29	6.1.2
org.springframework	spring-tx	5.3.29	6.1.2
org.springframework	spring-web	5.3.29	6.1.2
org.springframework	spring-webmvc	5.3.29	6.1.2
com.zaxxer	HikariCP	4.0.3	5.0.1
org.ow2.asm	asm-commons	9.4	9.6
org.ow2.asm	asm-tree	9.4	9.6
com.fasterxml.jackson.datatype	jackson-datatype-jdk8	2.14.2	2.15.3
com.fasterxml.jackson.datatype	jackson-datatype-jsr310	2.14.2	2.15.3
com.fasterxml.jackson.module	jackson-module-parameter-names	2.14.2	2.15.3
org.apache.tomcat.embed	tomcat-embed-el	9.0.78	10.1.17
org.eclipse.jetty	jetty-client	9.4.50.v20221201	12.0.7
org.eclipse.jetty	jetty-http	9.4.50.v20221201	12.0.7
org.eclipse.jetty	jetty-io	9.4.50.v20221201	12.0.7
org.eclipse.jetty	jetty-plus	9.4.50.v20221201	12.0.7
org.eclipse.jetty	jetty-security	9.4.50.v20221201	12.0.7
org.eclipse.jetty	jetty-server	9.4.50.v20221201	12.0.7
org.eclipse.jetty	jetty-util	9.4.50.v20221201	12.0.7
org.eclipse.jetty	jetty-xml	9.4.50.v20221201	12.0.7
org.slf4j	jul-to-slf4j	1.7.36	2.0.9
org.slf4j	slf4j-api	1.7.36	2.0.9
org.apache.logging.log4j	log4j-api	2.17.2	2.21.1
org.apache.logging.log4j	log4j-to-slf4j	2.17.2	2.21.1
ch.qos.logback	logback-classic	1.2.12	1.4.14
ch.qos.logback	logback-core	1.2.12	1.4.14
org.yaml	snakeyaml	2.0	2.2
jakarta.annotation	jakarta.annotation-api	1.3.5	2.1.1
jakarta.websocket	jakarta.websocket-api	1.1.2	2.1.1

The following dependencies have been added:

Group ID	Artifact ID	Version
org.eclipse.jetty.ee10	jetty-ee10-annotations	12.0.7
org.eclipse.jetty.ee10	jetty-ee10-plus	12.0.7
org.eclipse.jetty.ee10	jetty-ee10-servlet	12.0.7
org.eclipse.jetty.ee10	jetty-ee10-servlets	12.0.7
org.eclipse.jetty.ee10	jetty-ee10-webapp	12.0.7
org.eclipse.jetty.ee10	jetty-ee10-websocket-jakarta-client	12.0.7
org.eclipse.jetty.ee10	jetty-ee10-websocket-jakarta-common	12.0.7
org.eclipse.jetty.ee10	jetty-ee10-websocket-jakarta-server	12.0.7
org.eclipse.jetty.ee10	jetty-ee10-websocket-jetty-server	12.0.7
org.eclipse.jetty.ee10	jetty-ee10-websocket-servlet	12.0.7
org.eclipse.jetty	jetty-alpn-client	12.0.7
org.eclipse.jetty	jetty-jndi	12.0.7
org.eclipse.jetty	jetty-session	12.0.7
jakarta.websocket	jakarta.websocket-client-api	2.1.1

The following dependencies have been removed:

Group ID	Artifact ID	Version
org.eclipse.jetty	jetty-annotations	9.4.50.v20221201
org.eclipse.jetty	jetty-continuation	9.4.50.v20221201
org.eclipse.jetty	jetty-servlet	9.4.50.v20221201
org.eclipse.jetty	jetty-servlets	9.4.50.v20221201
org.eclipse.jetty	jetty-util-ajax	9.4.50.v20221201
org.eclipse.jetty	jetty-webapp	9.4.50.v20221201
org.eclipse.jetty.websocket	websocket-api	9.4.50.v20221201
org.eclipse.jetty.websocket	websocket-client	9.4.50.v20221201
org.eclipse.jetty.websocket	websocket-common	9.4.50.v20221201
org.eclipse.jetty.websocket	websocket-server	9.4.50.v20221201
org.eclipse.jetty.websocket	websocket-servlet	9.4.50.v20221201

Upgrade considerationLuciadFusion

The following dependencies have changed due to the Spring Boot upgrade from version 2.7 to 3.2:

Group ID	Artifact ID	Old Version	New Version
org.springframework.boot	spring-boot	2.7.14	3.2.1
org.springframework.boot	spring-boot-actuator-autoconfigure	2.7.14	3.2.1
org.springframework.boot	spring-boot-actuator	2.7.14	3.2.1
org.springframework.boot	spring-boot-autoconfigure	2.7.14	3.2.1
org.springframework.boot	spring-boot-configuration-processor	2.7.14	3.2.1
org.springframework.boot	spring-boot-starter	2.7.14	3.2.1
org.springframework.boot	spring-boot-starter-actuator	2.7.14	3.2.1
org.springframework.boot	spring-boot-starter-freemarker	2.7.14	3.2.1
org.springframework.boot	spring-boot-starter-jdbc	2.7.14	3.2.1
org.springframework.boot	spring-boot-starter-json	2.7.14	3.2.1
org.springframework.boot	spring-boot-starter-logging	2.7.14	3.2.1
org.springframework.boot	spring-boot-starter-security	2.7.14	3.2.1
org.springframework.boot	spring-boot-starter-validation	2.7.14	3.2.1
org.springframework.boot	spring-boot-starter-web	2.1.14	3.2.1
org.springframework.boot	spring-boot-starter-websocket	2.7.14	3.2.1
org.springframework.ldap	spring-ldap-core	2.4.1	3.0.4
org.springframework.security	spring-security-config	5.8.6	6.2.1
org.springframework.security	spring-security-core	5.8.6	6.2.1
org.springframework.security	spring-security-crypto	5.8.6	6.2.1
org.springframework.security	spring-security-ldap	5.8.6	6.1.2
org.springframework.security	spring-security-oauth2-core	5.8.6	6.1.2
org.springframework.security	spring-security-oauth2-resource-server	5.8.6	6.1.2
org.springframework.security	spring-security-web	5.8.6	6.2.1
org.springframework	spring-aop	5.3.29	6.1.2
org.springframework	spring-beans	5.3.29	6.1.2
org.springframework	spring-context	5.3.29	6.1.2
org.springframework	spring-context-support	5.3.29	6.1.2
org.springframework	spring-core	5.3.29	6.1.2
org.springframework	spring-expression	5.3.29	6.1.2
org.springframework	spring-jdbc	5.3.29	6.1.2
org.springframework	spring-messaging	5.3.29	6.1.2
org.springframework	spring-tx	5.3.29	6.1.2
org.springframework	spring-web	5.3.29	6.1.2
org.springframework	spring-webmvc	5.3.29	6.1.2
org.springframework	spring-websocket	5.3.29	6.1.2
org.webjars	swagger-ui	4.15.5	5.10.3
org.apache.tomcat.embed	tomcat-embed-el	9.0.78	10.1.17
org.yaml	snakeyaml	2.0	2.2
org.hibernate.validator	hibernate-validator	6.2.5.Final	8.0.1.Final
org.apache.logging.log4j	log4j-api	2.17.2	2.21.1
org.apache.logging.log4j	log4j-to-slf4j	2.17.2	2.21.1
org.jboss.logging	jboss-logging	3.4.1.Final	3.4.3.Final
org.slf4j	jcl-over-slf4j	1.7.36	2.0.9
org.slf4j	jul-to-slf4j	1.7.36	2.0.9
org.slf4j	log4j-over-slf4j	1.7.36	2.0.9
org.slf4j	slf4j-api	1.7.36	2.0.9
ch.qos.logback	logback-classic	1.2.12	1.4.14
ch.qos.logback	logback-core	1.2.12	1.4.14
com.zaxxer	HikariCP	4.0.3	5.0.1
io.github.classgraph	classgraph	4.8.149	4.8.108
io.micrometer	micrometer-core	1.9.13	1.12.1
joda-time	joda-time	2.8.1	2.10.10
com.sun.activation	jakarta.activation	1.2.2	2.0.1
jakarta.servlet	jakarta.servlet-api	4.0.4	6.0.0
jakarta.validation	jakarta.validation-api	2.0.2	3.0.2
jakarta.xml.bind	jakarta.xml.bind-api	2.3.3	4.0.0

The following dependencies have been added:

Group ID	Artifact ID	Version
io.micrometer	micrometer-common	1.12.1
io.micrometer	micrometer-jakarta9	1.12.1
io.micrometer	micrometer-observation	1.12.1
io.swagger.core.v3	swagger-annotations-jakarta	2.2.19
io.swagger.core.v3	swagger-core-jakarta	2.2.19
io.swagger.core.v3	swagger-models-jakarta	2.2.19
org.springdoc	springdoc-openapi-starter-common	2.3.0
org.springdoc	springdoc-openapi-starter-webmvc-api	2.3.0
org.springdoc	springdoc-openapi-starter-webmvc-ui	2.3.0
jakarta.transaction	jakarta.transaction-api	6.0.0

The following dependencies have been removed:

Group ID	Artifact ID	Version
commons-lang	commons-lang	2.6
javax.inject	javax.inject	1
io.swagger.core.v3	swagger-annotations	2.2.7
io.swagger.core.v3	swagger-core	2.2.7
io.swagger.core.v3	swagger-models	2.2.7
org.springdoc	springdoc-openapi-common	1.6.14
org.springdoc	springdoc-openapi-security	1.6.14
org.springdoc	springdoc-openapi-ui	1.6.14
org.springdoc	springdoc-openapi-webmvc-core	1.6.14
org.webjars	webjars-locator-core	0.52

LuciadFusion can be used with a Jetty embedded servlet container. The jetty sample dependencies are used in this situation. The following sample dependencies related to Jetty have changed:

org.springframework.boot	spring-boot-starter-jetty	2.7.8	3.2.1
org.ow2.asm	asm-commons	9.4	9.6
org.ow2.asm	asm-tree	9.4	9.6
org.eclipse.jetty	jetty-client	9.4.50.v20221201	12.0.7
org.eclipse.jetty	jetty-http	9.4.50.v20221201	12.0.7
org.eclipse.jetty	jetty-io	9.4.50.v20221201	12.0.7
org.eclipse.jetty	jetty-plus	9.4.50.v20221201	12.0.7
org.eclipse.jetty	jetty-security	9.4.50.v20221201	12.0.7
org.eclipse.jetty	jetty-server	9.4.50.v20221201	12.0.7
org.eclipse.jetty	jetty-util	9.4.50.v20221201	12.0.7
org.eclipse.jetty	jetty-xml	9.4.50.v20221201	12.0.7
jakarta.annotation	jakarta.annotation-api	1.3.5	2.1.1
jakarta.websocket	jakarta.websocket-api	1.1.2	2.1.1

The following sample dependencies related to Jetty have been added:

Group ID	Artifact ID	Version
org.eclipse.jetty.ee10	jetty-ee10-annotations	12.0.7
org.eclipse.jetty.ee10	jetty-ee10-plus	12.0.7
org.eclipse.jetty.ee10	jetty-ee10-servlet	12.0.7
org.eclipse.jetty.ee10	jetty-ee10-servlets	12.0.7
org.eclipse.jetty.ee10	jetty-ee10-webapp	12.0.7
org.eclipse.jetty.ee10	jetty-ee10-websocket-jakarta-client	12.0.7
org.eclipse.jetty.ee10	jetty-ee10-websocket-jakarta-common	12.0.7
org.eclipse.jetty.ee10	jetty-ee10-websocket-jakarta-server	12.0.7
org.eclipse.jetty.ee10	jetty-ee10-websocket-jetty-server	12.0.7
org.eclipse.jetty.ee10	jetty-ee10-websocket-servlet	12.0.7
org.eclipse.jetty	jetty-alpn-client	12.0.7
org.eclipse.jetty	jetty-jndi	12.0.7
org.eclipse.jetty	jetty-session	12.0.7
jakarta.websocket	jakarta.websocket-client-api	2.1.1

The following sample dependencies related to Jetty have been removed:

Group ID	Artifact ID	Version
org.eclipse.jetty	jetty-annotations	9.4.50.v20221201
org.eclipse.jetty	jetty-continuation	9.4.50.v20221201
org.eclipse.jetty	jetty-servlet	9.4.50.v20221201
org.eclipse.jetty	jetty-servlets	9.4.50.v20221201
org.eclipse.jetty	jetty-util-ajax	9.4.50.v20221201
org.eclipse.jetty	jetty-webapp	9.4.50.v20221201
org.eclipse.jetty.websocket	websocket-api	9.4.50.v20221201
org.eclipse.jetty.websocket	websocket-client	9.4.50.v20221201
org.eclipse.jetty.websocket	websocket-common	9.4.50.v20221201
org.eclipse.jetty.websocket	websocket-server	9.4.50.v20221201
org.eclipse.jetty.websocket	websocket-servlet	9.4.50.v20221201

Upgrade considerationLuciadFusion

LCD-13176

TLcdGXYImagePainter, TLcdRasterPainter, TLcdMultilevelRasterPainter, TLcdEarthGXYRasterPainter, TLcdGXYTiledWMSProxyPainter and TLcdWMSProxyGXYPainter now apply brightness and contrast to raster layers with the same algorithm as Lightspeed's TLspRasterStyle. This used to be different but has now been aligned. With the new behavior, the [0, 2] brightness value range covers the entire color brightness range (black to white). The contrast setting offers a modifier on top for further tweaking.

Upgrade considerationLuciadFusion

The keywords for the Style, Product, Data and Service resources are now sets instead of lists, so any duplicate keywords are removed. The LuciadFusion Studio REST API endpoint POST /api/services/{id}/keywords now accepts a set instead of a list of keywords. Any duplicate keywords that are added to the service are ignored.

Upgrade considerationLuciadFusion

The LuciadLightspeed and LuciadFusion APIs now use the Jakarta EE 10 API and Jakarta Servlet 6.0 API, where in previous releases the Java EE 7 API and Java Servlet 3.1 API were used. There are a few breaking changes in the new Jakarta Servlet 6.0 API, the main one being a rename of the javax.servlet package to jakarta.servlet. Any LuciadLightspeed or LuciadFusion API that use classes from this package thus contain a corresponding breaking change. The affected classes are mainly the classes implementing the OGC server standards (WM(T)S, WFS, etc). Any compilation errors you encounter related to this change can typically be resolved by performing a find and replace operation.

Refer to the documentation on hardware and software requirements in the prerequisites section for more information.

Upgrade considerationLuciadFusion

The property isoMetadataXmlContent that is part of the Service resource of the LuciadFusion Studio REST API was marked for deprecation in release 2023.0 and has now been removed. Instead, use LuciadFusion's Studio Catalog Service to get the ISO-19115 metadata of a service.

Upgrade considerationLuciadFusion

LuciadLightspeed and LuciadFusion now require Java 17. Refer to the documentation on hardware and software requirements in the prerequisites section for more information.

Upgrade considerationLuciadFusion

LF-2408

The following dependencies have been updated:

Group ID	Artifact ID	Old Version	New Version
org.apache.commons	commons-configuration2	2.9.0.lcd-11	2.9.0
org.orbisgis	cts	1.4.0	1.7.0
org.geolatte	geolatte-geom	0.13	1.9.1
com.h2database	h2	1.4.195	2.1.214
org.orbisgis	h2gis-api	1.3.1	2.2.0
org.orbisgis	h2gis-utilities	1.3.1	2.2.0
org.orbisgis	h2gis	1.3.1	2.2.0
org.liquibase	liquibase-core	3.6.3	4.8.0

The following dependencies have been added:

Group ID	Artifact ID	Version
org.eclipse.jdt	ecj	3.26.0
org.orbisgis	poly2tri	0.4.0

The following dependencies have been removed:

Group ID	Artifact ID	Version
org.codehaus.mojo	animal-sniffer-annotations	1.14
com.infradna.tool	bridge-method-annotation	1.13
org.javassist	javassist	3.18.2-GA
org.reflections	reflections	0.9.9
org.orbisgis	poly2tri-core	0.1.2
com.vividsolutions	jts-io	1.14.0
com.googlecode.json-simple	json-simple	1.1
jakarta.activation	jakarta.activation-api	1.2.2

Upgrade considerationLuciadFusion

LCD-9539

The following dependencies have been updated:

Group ID	Artifact ID	Old Version	New Version
com.fasterxml.jackson.core	jackson-annotations	2.14.2	2.15.3
com.fasterxml.jackson.core	jackson-core	2.14.2	2.15.3
com.fasterxml.jackson.core	jackson-databind	2.14.2	2.15.3
com.google.protobuf	protobuf-java	3.19.4	3.25.3
com.thetransactioncompany	cors-filter	1.3.2	3.0
com.thetransactioncompany	java-property-utils	1.6	1.17
jakarta.servlet	jakarta.servlet-api	4.0.4	6.0.0
joda-time	joda-time	2.8.1	2.10.10
org.apache.commons	commons-compress	1.22	1.26
org.apache	commons-io	2.6	2.15.1
org.apache.commons	commons-lang3	3.12.0	3.14.0
org.apache.xmlgraphics	batik-xml	1.16	1.17
org.apache.xmlgraphics	batik-util	1.16	1.17
org.apache.xmlgraphics	batik-transcoder	1.16	1.17
org.apache.xmlgraphics	batik-swing	1.16	1.17
org.apache.xmlgraphics	batik-svggen	1.16	1.17
org.apache.xmlgraphics	batik-svg-dom	1.16	1.17
org.apache.xmlgraphics	batik-script	1.16	1.17
org.apache.xmlgraphics	batik-shared-resources	1.16	1.17
org.apache.xmlgraphics	batik-parser	1.16	1.17
org.apache.xmlgraphics	batik-i18n	1.16	1.17
org.apache.xmlgraphics	batik-gvt	1.16	1.17
org.apache.xmlgraphics	batik-gui-util	1.16	1.17
org.apache.xmlgraphics	batik-ext	1.16	1.17
org.apache.xmlgraphics	batik-dom	1.16	1.17
org.apache.xmlgraphics	batik-css	1.16	1.17
org.apache.xmlgraphics	batik-constants	1.16	1.17
org.apache.xmlgraphics	batik-codec	1.16	1.17
org.apache.xmlgraphics	batik-bridge	1.16	1.17
org.apache.xmlgraphics	batik-awt-util	1.16	1.17
org.apache.xmlgraphics	batik-anim	1.16	1.17
org.apache.xmlgraphics	xmlgraphics-commons	2.7	2.9
org.slf4j	slf4j-api	1.7.36	2.0.9
org.postgresql	postgresql	42.5.4	42.7.3
org.checkerframework	checker-qual	3.5.0	3.42.0

The following dependencies have been added:

Group ID	Artifact ID	Version
org.locationtech	jts-core	1.19.0

The following dependencies have been removed:

Group ID	Artifact ID	Version
com.vividsolutions	jts-core	1.14.0

Upgrade considerationLuciadFusion

LF-2408

LuciadFusion 2024.0 and subsequent releases are not compatible with H2 databases created with LuciadFusion 2023.1 and preceding releases. This is because the H2 library has been updated to version 2.1.214. The H2GIS library has been updated to version 2.2.0.

Upgrade considerationLuciadFusion

LCD-9539

The QueryDSL library has been updated to version 5.0.0. Please note that these libraries have been modified from the original QueryDSL libraries to include additional fixes.

Upgrade considerationLuciadFusion

LCD-9539

The JTS library has been updated to version 1.19.0. Please note that this library is not backward compatible. All classes have moved from com.vividsolutions.* to org.locationtech.*.

Upgrade considerationLuciadFusion

LCD-12881

The LWJGL Java binding for the OpenGL and OpenCL APIs has been updated to version 3.3.3. This improves compatibility with Java 19 and higher.

Upgrade considerationLuciadFusion

Oracle versions 11g, 12c and 18c are no longer supported as a database for LuciadFusion Studio. These versions are no longer supported by Oracle, see the Oracle Lifetime Support Policy document. It's advisable to upgrade to a newer version of Oracle database if you are still using any of these versions.

Upgrade considerationLuciadFusion

PostgreSQL versions 9.4, 9.5, 9.6, 10 and 11 are no longer supported as a database for LuciadFusion Studio. These versions are no longer supported by the PostgreSQL Global Development Group, see the PostgreSQL Versioning Policy page. It's advisable to upgrade to a newer version of PostgreSQL if you are still using any of these versions.

Upgrade considerationLuciadFusion

SQL Server version 2012 is no longer supported as a database for LuciadFusion Studio. This version is no longer supported by Microsoft, see the SQL Server 2012 lifecycle page. It's advisable to upgrade to a newer version of SQL Server if you are still using version 2012.

Upgrade considerationLuciadFusion

LCD-10042

TLcdLRDBModelEncoder#SUPPORTED_COVERAGE_TYPES is removed from the API.

Bug fixLuciadFusion

LCD-13356

TLcdSpatiaLiteModelDecoder#decode(Properties) no longer triggers an error with message no such function: spatialite_version.

ImprovementLuciadFusion

LCD-13315

The SLD Lightspeed implementation now supports the rendering of extruded shapes. This capability can be enabled on a polygon symbolizer by configuring the following SLD vendor options:

extrudedShapeMinimum, accepting a literal or property name that specifies the minimum value in meters.
extrudedShapeMaximum, accepting a literal or property name that specifies the maximum value in meters.
extrudedShapeReference, accepting the values of ILspWorldElevationStyle.ElevationMode

Bug fixLuciadFusion

LCD-13361

Fixed an issue where empty tiles were returned by the WMTS server if the WGS84 tile matrix set was used.

Bug fixLuciadFusion

LCD-13362

Corrected the CRS of the GoogleMapsCompatible well-known tile matrix set in the capabilities document returned by the WMTS server: it now includes the minor version (urn:ogc:def:crs:EPSG:6.18.3:3857).

Bug fixLuciadFusion

LCD-12343

TLcdGXYCompositeCurvePainter: fixed a regression caused by LCD-11480 where the editing handles were no longer shown.

Bug fixLuciadFusion

LCD-13368

Bug fixLuciadFusion

TLcdLonLatPointFormat#parseObject now throws a ParseException when parsing only whitespace.

Bug fixLuciadFusion

LCD-13323

The WCS server now supports WCS 1.1.x GetCoverage requests that neither specify a bounding box nor a resolution.

Bug fixLuciadFusion

LCD-13327

TLcdWFSProxyModel could trigger a NullPointerException when retrieving data from a WFS server that did not advertise arithmetic function capabilities.

ImprovementLuciadFusion

LCD-13310

Aligned with the OGC WMS standard, the request URL prefixes listed in the WMS capabilities now always end with a question mark.

ImprovementLuciadFusion

LCD-13288

The maximum resolution of the default tileset used by:

TLcdGXYTiledWMSProxyPainter
TLcdWCSProxy
TLspWMSLayerBuilder with TLspWMSLayerBuilder#paintStrategy(ELcdWMSPaintStrategy aPaintStrategy) set to ELcdWMSPaintStrategy#TILED

LCD-13225

Two issues have been fixed when encoding an SLD style containing a color map to an OGC SE 1.1 style file using TLcdSLDFeatureTypeStyleEncoder:

The alpha component of a color was not preserved during encoding when the SLD style was decoded from an OGC SE 1.1 style file.
The color map was not encoded to the correct color map function: Categorize and Interpolate were incorrectly exchanged.

Bug fixLuciadFusion

LCD-13073

TLcdWMSGXYViewFactory#createGXYView(boolean, int, int, ILcdBounds, ILcdXYWorldReference, Color,
                           aRequestContext)

When the configuration option Keep associated Data and Styles is enabled, the crawl job will retain inaccessible or corrupt data/styles on a re-crawl. This also means that the associated Products will keep this data/styles on a subsequent re-crawl. When the valid data/styles is accessible again at a later time, the user will be able to visualize/access it normally as before when requested via an associated OGC service. When the configuration option Delete associated Data and Styles is enabled, the crawl job will delete the inaccessible or corrupt data/styles from all the associated Products. This behavior/configuration is enabled by default.

New featureLuciadFusion

TLcdMBTilesModelDecoder

now supports vector tiles as well as image tiles. Vector tile data can be visualized in a Lightspeed view by using TLspMBTilesVectorLayerBuilder.

New featureLuciadFusion

Unreferenced BINZ, IFC and OBJ data can now be used in an OGC 3D Tiles service in LuciadFusion. The data will be pre-processed to OGC 3D Tiles when it is published in an OGC 3D Tiles service.

New featureLuciadFusion

LF-2439

LuciadFusion now allows users to pre-process and publish custom elevation formats in a Luciad Tile Service (LTS). Check Registering a model decoder for a custom elevation format as a service to find out how.

New featureLuciadFusion

The role-based access control for data resources in LuciadFusion has been extended to allow the user to provide both scale and spatial ranges for the data rules. You can use the updated LuciadFusion REST API to configure the extended data access rules.

Read the access control in LuciadFusion reference guide for more information.

ImprovementLuciadFusion

The WCS server's GetCoverage handling logic now reuses threads across multiple requests improving the response time depending on the used data and hardware.

ImprovementLuciadFusion

LCD-11110

An ellipsoidal version of TLcdLambertAzimuthalEqualArea has been added: TLcdEllipsoidalLambertAzimuthalEqualArea. This projection use ellipsoidal calculations instead of only spherical calculations.

This also improves the precision of the WKT and EPSG references that use this an ellipsoidal version of this projection. TLcdWKTReferenceParser now makes a distinction between the spherical and the ellipsoidal versions of this projection. The precision of these EPSG codes has now been improved:

3035
3571 to 3576
5633, 5635, 5636, 5638
6931, 6932
9039
9947

ImprovementLuciadFusion

LCD-13074

The WFS server's capability to output features as GeoJSON has been made more robust: features that cannot be encoded to GeoJSON (for example, because of an unsupported geometry type) are now skipped with a warning instead of causing a WFS GetFeature response failure.

ImprovementLuciadFusion

LCD-13067

The TLcdGeoJsonModelDecoder can now decode features with a null geometry. The resulting domain objects are ILcdDataObjects containing the json properties, and also implement ILcdShapeList, but contain no shapes (they are empty shape lists).

Likewise, the TLcdGeoJsonModelEncoder now supports encoding domain objects that don't have a geometry, provided that they implement ILcdDataObject. The resulting json contains the data object's properties and a null geometry.

ImprovementLuciadFusion

Values for enum string properties are no longer case-sensitive in the LuciadFusion REST API.

ImprovementLuciadFusion

LCD-13022, LCD-13016, LCD-8758

The WFS server is now more flexible against accepting a geometry property name in an OGC Filter condition. Next to a fully-qualified geometry property name (with a prefix bound to a namespace, such as gml:geometry), it now also accepts an unqualified property name (such as geometry). Additionally, warnings such as "Error while converting filter" are no longer logged for valid geometry property names.

ImprovementLuciadFusion

LCD-13035

The following classes now correctly implement ILcdGXYPainter#isTouched:

TLcdGXYImageIconPainter

ALcdEarthGXYPainter

TLcdEarthGXYVertexArrayPainter

Complex strokes in a Lightspeed view were not always painted correctly for vertical line segments with points with a large altitude.

Bug fixLuciadFusion

LCD-13079

TLcdOGCFilterEvaluator could not handle a spatial condition with an empty geometry property for domain objects that implemented both ILcdShape and ILcdDataObject and that contained multiple geometry properties.

Bug fixLuciadFusion

LF-2090

LuciadFusion now allows you to use data decoded through the HGTModelDecoder and the TLcdBCIRasterModelDecoder in an LTS service.

Bug fixLuciadFusion

LF-2423

Issues with storing information with unicode characters in LuciadFusion Studio when an SQL Server database is used have been fixed. Crawling files with file names containing unicode characters, or entering metadata information that contained unicode characters would result in the unicode characters being replaced by ?? after storing the information in the database. This has been fixed by changing the type of the columns that store this information from VARCHAR to NVARCHAR.

Note that this reduces the length of a file path that can be crawled or added to LuciadFusion when an SQL Server database is used, as shown in the table below.

SQL Server database version	Max file path length
2012, 2014	450
2016 or later	850

Bug fixLuciadFusion

LF-2436

Resolved an issue that caused a Style resource's updated by user to never be updated.

Bug fixLuciadFusion

LF-2503

Upgrade considerationLuciadFusion

LuciadFusion Studio now enabled Draco mesh compression by default for OGC 3D Tiles services created from OBJ, GLB, IFC or BINZ files. The compression can still be disabled using the drop-down in the user interface while configuring your service.

Upgrade considerationLuciadFusion

The dependency to io.reactivex:rxnetty:0.4.9 has been removed because it is no longer used by LuciadFusion. The following dependencies are no longer included in the LuciadFusion release:

Group ID	Artifact ID	Version
io.reactivex	rxnetty	0.4.9
io.reactivex	rxjava	1.0.10
io.netty	netty-codec-http	4.0.27
io.netty	netty-transport-native-epoll	4.0.27
io.netty	netty-codec	4.0.27
io.netty	netty-handler	4.0.27
io.netty	netty-common	4.0.27
io.netty	netty-buffer	4.0.27
io.netty	netty-transport	4.0.27

Upgrade considerationLuciadFusion

LF-2401

Security updates have been applied to the following dependencies:

Group ID	Artifact ID	Old Version	New Version
org.apache.tomcat.embed	tomcat-embed-el	9.0.71	9.0.78
org.springframework	spring-websocket	5.3.25	5.3.29
org.springframework	spring-webmvc	5.3.25	5.3.29
org.springframework	spring-web	5.3.25	5.3.29
org.springframework	spring-tx	5.3.25	5.3.29
org.springframework	spring-messaging	5.3.25	5.3.29
org.springframework	spring-jdbc	5.3.25	5.3.29
org.springframework	spring-expression	5.3.25	5.3.29
org.springframework	spring-core	5.3.25	5.3.29
org.springframework	spring-context-support	5.3.25	5.3.29
org.springframework	spring-context	5.3.25	5.3.29
org.springframework	spring-beans	5.3.25	5.3.29
org.springframework	spring-aop	5.3.25	5.3.29
org.springframework.boot	spring-boot-starter-websocket	2.7.8	2.7.14
org.springframework.boot	spring-boot-starter-web	2.7.8	2.7.14
org.springframework.boot	spring-boot-starter-validation	2.7.8	2.7.14
org.springframework.boot	spring-boot-starter-security	2.7.8	2.7.14
org.springframework.boot	spring-boot-starter-logging	2.7.8	2.7.14
org.springframework.boot	spring-boot-starter-json	2.7.8	2.7.14
org.springframework.boot	spring-boot-starter-jdbc	2.7.8	2.7.14
org.springframework.boot	spring-boot-autoconfigure	2.7.8	2.7.14
org.springframework.boot	spring-boot-actuator	2.7.8	2.7.14
org.springframework.boot	spring-boot-starter-freemarker	2.7.8	2.7.14
org.springframework.boot	spring-boot-starter-actuator	2.7.8	2.7.14
org.springframework.boot	spring-boot-starter	2.7.8	2.7.14
org.springframework.boot	spring-boot-configuration-processor	2.7.8	2.7.14
org.springframework.boot	spring-boot-actuator-autoconfigure	2.7.8	2.7.14
org.springframework.boot	spring-boot	2.7.8	2.7.14
org.yaml	snakeyaml	1.33	2.0
org.apache.commons	commons-configuration2	2.8.0	2.9.0
ch.qos.logback	logback-core	1.2.11	1.2.12
ch.qos.logback	logback-classic	1.2.11	1.2.12
io.micrometer	micrometer-core	1.9.7	1.9.13
org.springframework.security	spring-security-web	5.8.1	5.8.6
org.springframework.security	spring-security-config	5.8.1	5.8.6
org.springframework.security	spring-security-oauth2-resource-server	5.8.1	5.8.6
org.springframework.security	spring-security-ldap	5.8.1	5.8.6
org.springframework.security	spring-security-core	5.8.1	5.8.6
org.springframework.security	spring-security-crypto	5.8.1	5.8.6
org.springframework.security		5.8.1	5.8.6

The following dependencies have been added:

Group ID	Artifact ID	Version
com.opencsv	opencsv	5.7.1
org.apache.commons	commons-collections4	4.4

Upgrade considerationLuciadFusion

Security updates have been applied to the following dependencies:

Group ID	Artifact ID	Old Version	New Version
com.fasterxml.woodstox	woodstox-core	5.0.3	6.5.1
org.codehaus.woodstox	stax2-api	3.1.4	4.2.1

Security updates have been applied to the following sample dependencies of the OGC server sample:

Group ID	Artifact ID	Old Version	New Version
org.springframework.boot	spring-boot	2.7.8	2.7.14
org.springframework.boot	spring-boot-starter	2.7.8	2.7.14
org.springframework.boot	spring-boot-autoconfigure	2.7.8	2.7.14
org.springframework.boot	spring-boot-starter-json	2.7.8	2.7.14
org.springframework.boot	spring-boot-starter-jetty	2.7.8	2.7.14
org.springframework.boot	spring-boot-starter-logging	2.7.8	2.7.14
org.springframework.boot	spring-boot-starter-web	2.7.8	2.7.14
org.springframework	spring-aop	5.3.25	5.3.29
org.springframework	spring-tx	5.3.25	5.3.29
org.springframework	spring-jdbc	5.3.25	5.3.29
org.springframework	spring-beans	5.3.25	5.3.29
org.springframework	spring-context	5.3.25	5.3.29
org.springframework	spring-core	5.3.25	5.3.29
org.springframework	spring-expression	5.3.25	5.3.29
org.springframework	spring-web	5.3.25	5.3.29
org.springframework	spring-webmvc	5.3.25	5.3.29
org.eclipse.jetty.websocket	javax-websocket-client-impl	9.4.50.v20221201	9.4.51.v20230217
org.eclipse.jetty.websocket	javax-websocket-server-impl	9.4.50.v20221201	9.4.51.v20230217
org.eclipse.jetty	jetty-annotations	9.4.50.v20221201	9.4.51.v20230217
org.eclipse.jetty	jetty-client	9.4.50.v20221201	9.4.51.v20230217
org.eclipse.jetty	jetty-continuation	9.4.50.v20221201	9.4.51.v20230217
org.eclipse.jetty	jetty-http	9.4.50.v20221201	9.4.51.v20230217
org.eclipse.jetty	jetty-io	9.4.50.v20221201	9.4.51.v20230217
org.eclipse.jetty	jetty-plus	9.4.50.v20221201	9.4.51.v20230217
org.eclipse.jetty	jetty-security	9.4.50.v20221201	9.4.51.v20230217
org.eclipse.jetty	jetty-server	9.4.50.v20221201	9.4.51.v20230217
org.eclipse.jetty	jetty-servlet	9.4.50.v20221201	9.4.51.v20230217
org.eclipse.jetty	jetty-servlets	9.4.50.v20221201	9.4.51.v20230217
org.eclipse.jetty	jetty-util	9.4.50.v20221201	9.4.51.v20230217
org.eclipse.jetty	jetty-util-ajax	9.4.50.v20221201	9.4.51.v20230217
org.eclipse.jetty	jetty-webapp	9.4.50.v20221201	9.4.51.v20230217
org.eclipse.jetty	jetty-xml	9.4.50.v20221201	9.4.51.v20230217
org.eclipse.jetty.websocket	websocket-api	9.4.50.v20221201	9.4.51.v20230217
org.eclipse.jetty.websocket	websocket-client	9.4.50.v20221201	9.4.51.v20230217
org.eclipse.jetty.websocket	websocket-common	9.4.50.v20221201	9.4.51.v20230217
org.eclipse.jetty.websocket	websocket-server	9.4.50.v20221201	9.4.51.v20230217
org.eclipse.jetty.websocket	websocket-servlet	9.4.50.v20221201	9.4.51.v20230217
org.apache.tomcat.embed	tomcat-embed-el	9.0.71	9.0.78
org.yaml	snakeyaml	1.33	2.0
ch.qos.logback	logback-core	1.2.11	1.2.12
ch.qos.logback	logback-classic	1.2.11	1.2.12

Upgrade considerationLuciadFusion

TLcdMBTilesModelDecoder has been moved from the SQLite component to a dedicated MBTiles component. It is now contained in the package


                              com.luciad.format.mbtiles

Upgrading users will get a compiler error because of this, which can be resolved by adapting the affected import statements. Furthermore, build configurations may need to be updated to include the new lcd_mbtiles.jar file.

Upgrade considerationLuciadFusion

TLcdMBTilesModelDecoder now requires the Google Protocol Buffer library (protobuf-java-3.19.4.jar) to support files which contain vector tiles.

Upgrade considerationLuciadFusion

The return type of the method TLspScaleBasedStyler.getStylersByScaleRange has been changed from ALspStyler to ILspStyler.

Upgrade considerationLuciadFusion

The JLessC library has been added as a dependency. This library is used to compile LESS files to CSS files.

Group ID	Artifact ID	Version
de.inetsoftware	jlessc	1.10

Upgrade considerationLuciadFusion

The dependency of the jsass library has been removed. This library is no longer maintained. The libsass native library, which jsass is built upon, is deprecated and will no longer be developed further.

Group ID	Artifact ID	Version
io.bit3	jsass	5.7.0

Bug fixLuciadFusion

LCD-12888

The


                              TLcdMBTilesModelDecoder

now interprets the minzoom value stored in the metadata table. As a result tiles are now shown which previously where not.

Bug fixLuciadFusion

LCD-12664

The TLcdLVDBModelDecoder and the TLcdGeoPackageModelDecoder now return null instead of 0 when the NULL value is stored in the database.

Bug fixLuciadFusion

LCD-12861

The


                              TLcdMBTilesModelDecoder

and TLcdGeoPackageModelDecoder no longer create empty directories when trying to open non-existing sources.

Bug fixLuciadFusion

Bug fixLuciadFusion

LCD-12471

Some of the EPSG references parsed by TLcdEPSGReferenceParser had incorrect projection parameters. This affected references where the EPSG database defines parameters in a different unit than meters or degrees:

EPSG:3359
EPSG:22391 and EPSG:22392
EPSG:22780
EPSG:26191 to EPSG:26195
EPSG:26814 and EPSG:26815
EPSG:26819 to EPSG:26822
EPSG:26825 and EPSG:26826
EPSG:26830 to EPSG:26833
EPSG:26836 and EPSG:26837
EPSG:26841 to EPSG:26844
EPSG:30491 and EPSG:30492
EPSG:30791 and EPSG:30792

Group ID	Artifact ID	Old Version	New Version
com.fasterxml.jackson.dataformat	jackson-dataformat-xml	2.9.7	2.14.0
com.fasterxml.jackson.dataformat	jackson-dataformat-cbor	2.9.7	2.14.0
com.fasterxml.jackson.datatype	jackson-datatype-jdk8	2.9.7	2.14.0
com.fasterxml.jackson.datatype	jackson-datatype-jsr310	2.9.7	2.14.0
com.fasterxml.jackson.module	jackson-module-afterburner	2.9.7	2.14.0
com.fasterxml.jackson.module	jackson-module-jaxb-annotations	2.9.7	2.14.0

ImprovementLuciadFusion

LCD-12863

TLcdEPSGReferenceParser now additionally supports the following datums, and coordinate references that make use of it:

Korean Datum 1985
Macao 1920

ImprovementLuciadFusion

LCD-12863

TLcdGeodeticDatum now supports the Molodensky-Badekas 10-parameter transformation. On top of the previous 7 parameters, it is now possible to set 3 additional parameters that define a pivot point. See

TLcdGeodeticDatum#setPivotX
TLcdGeodeticDatum#setPivotY
TLcdGeodeticDatum#setPivotZ

New featureLuciadFusion

The Spring Boot dependencies of LuciadFusion have been upgraded from version 2.1 to version 2.7. 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.

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

New featureLuciadFusion

It is now possible to configure multiple named styles for WMS and WMTS Services. To accomplish this, new endpoints /api/products/{id}/style-sets and /api/products/{id}/data are now part of the REST API. The endpoint /api/products/{id}/styled-data is now deprecated.

You can find more explanation on how to create named styles for WMS and WMTS services within the LuciadFusion REST API Developer Guide webpage.

ImprovementLuciadFusion

LCD-12439

The make_osgi_bundles script now comes with an upgraded BND library and Felix framework, improving compatibility with Java 11 and higher.

ImprovementLuciadFusion

LF-2371

The length of the database column of the pre-process path has been increased to the maximum allowed size. The pre-process path was previously limited to around 255 characters.

ImprovementLuciadFusion

LCD-12864

Support has been added for an OGC strReplace function in TLcdOGCVendorSpecificFunctions that can replace a pattern in a String property. This function can be used when querying a model (see ILcdModel#query), when creating an OGC Filter or when creating an SLD style.

ImprovementLuciadFusion

LCD-11611

Split packages have been eliminated from all lcd_*.jar files. This improves compatibility with JDK 9 and higher.

ImprovementLuciadFusion

The lcd_3dtiles.jar file has been renamed to lcd_tiled3d.jar, so Java can generate an automatic module for it. The name change also applies to the corresponding maven pom file.

ImprovementLuciadFusion

LCD-11985

The vertical view controllers (TLcdVVAltitudeRangeSliderJPanel, TLcdVVStartEndIndexJSlider, and TLcdVVStartEndIndexJSlider) no longer reset when the vertical view's ILcdVVModel fires a change event. Usually those controllers only need to be reset when the view displays an entirely different profile. You can achieve this by maintaining a 1-to-1 mapping between the domain object and the vertical view model, as shown in the sample class FlightSelectionListener. In addition, TLcdVVTerrainModel has a new constructor making it easier to create a fully initialized terrain profile to achieve that 1-to-1 mapping. The other constructors have been deprecated. If you don't have a 1-to-1 mapping, you can unset and set the vertical view's model (i.e. vview.setVVModel(null); vview.setVVModel(model);) whenever you want to reset the controllers.

ImprovementLuciadFusion

It is now possible to perform comparison between two queryable properties using e.g.


                           lfn.type=ic=${aStringPropName}

Upgrade considerationLuciadFusion

The ECWP service of LuciadFusion has been disabled by default to avoid a Studio styling issue on Linux when the customization of the Studio front-end is enabled (= by default in the development profile). To enable ECWP again, you can set the property fusion.ecwp.enabled=true in the config/application-fusion.common.yml file. If you are using Linux, make sure to disable the customization of the Studio front-end in this case by setting the property fusion.studio.webapp.theme.enabled=false.

Upgrade considerationLuciadFusion

The minimum OpenGL version required by ILspView is now 4.2. GPUs or drivers which do not support this version will no longer be able to use the hardware-accelerated Lightspeed view. For more information please contact support.luciad.gsp@hexagon.com.

Upgrade considerationLuciadFusion

LuciadLightspeed no longer supports Oculus devices. For more information please contact support.luciad.gsp@hexagon.com.

Upgrade considerationLuciadFusion

LCD-11985

TLcdAltitudeRangeSliderAdapter has been deprecated. Its functionality is now handled automatically by TLcdVVAltitudeRangeSliderJPanel. You can safely remove it from your code.

Upgrade considerationLuciadFusion

The vmoptions files used by start.jar and the launcher scripts have been simplified and moved to config/vmoptions to avoid split packages. If you want to override the startup parameters of a sample or product, look for a vmoptions file in that directory starting with the relevant package, such as com.luciad.lucy.vmoptions for com.luciad.lucy.TLcyMain.

Upgrade considerationLuciadFusion

The logback version has been upgraded to version 1.2.11 due to the Spring Boot upgrade from version 2.1 to 2.7:

Group ID	Artifact ID	Old Version	New Version
ch.qos.logback	logback-classic	1.2.3	1.2.11

Upgrade considerationLuciadFusion

LCD-12446, LCD-12445

The com.luciad.ogc.filter.model package is no longer split between multiple jars. To achieve this, the following API has been moved:

Class or interface	Old package	New package
ILcdGenericExpression ILcdOGCCondition ILcdOGCExpression ILcdOGCSortBy	com.luciad.ogc.filter.model	com.luciad.ogc.filter
ILcdOGCFeatureIDRetriever	com.luciad.ogc.filter	com.luciad.ogc.filter.evaluator
TLcdOGCFilterCapabilitiesConstants	com.luciad.ogc.filter	N/A

If you encounter any compile errors due to these changes, simply update the relevant import statement. There should be no need for the TLcdOGCFilterCapabilitiesConstants class. If you require some of its constants, you can define these yourself.

Upgrade considerationLuciadFusion

LCD-12445

The com.luciad.geometry package is no longer split between multiple jars. To achieve this, the following API has been moved:

Class or interface	Old package	New package
ILcd2DAdvancedBinaryTopology ILcd2DBinaryTopology ALcd2DBasicBinaryTopology ALcd2DBasicBinaryTopologyMultiShape ELcdGeometryDimension ELcdGeometryRegion ILcd2DLineIntersectionTopology ILcdIntersectionMatrix ILcdIntersectionMatrixPattern	com.luciad.geometry	com.luciad.geometry.topology
TLcdCartesianAdvancedBinaryTopology TLcdCartesianBasicBinaryTopology	com.luciad.geometry.cartesian	com.luciad.geometry.topology.cartesian
ILcd2DEllipsoidalBinaryTopology TLcdEllipsoidalAdvancedBinaryTopology TLcdEllipsoidalBasicBinaryTopology	com.luciad.geometry.ellipsoidal	com.luciad.geometry.topology.ellipsoidal
TLcdSphericalAdvancedBinaryTopology TLcdSphericalBasicBinaryTopology	com.luciad.geometry.spherical	com.luciad.geometry.topology.spherical
ILcdConstructiveGeometry	com.luciad.geometry	com.luciad.geometry.constructive
TLcdCartesianConstructiveGeometry	com.luciad.geometry.cartesian	com.luciad.geometry.constructive.cartesian
TLcdSphericalConstructiveGeometry	com.luciad.geometry.spherical	com.luciad.geometry.constructive.spherical
TLcdEllipsoidalConstructiveGeometry	com.luciad.geometry.ellipsoidal	com.luciad.geometry.constructive.ellipsoidal
TLcdEllipsoidalShapePointEnumerationFactory	com.luciad.geometry.ellipsoidal	N/A
ILcd2DBasicBinaryTopology	com.luciad.geometry	N/A

If you encounter any compile errors due to these changes, just update the relevant import statement. If you were still using ILcd2DBasicBinaryTopology, you can replace it with the identical ILcd2DBinaryTopology interface. If you still have a need for TLcdEllipsoidalShapePointEnumerationFactory, please reach out to support.luciad.gsp@hexagon.com.

Upgrade considerationLuciadFusion

Security updates have been applied to the following dependencies:

Group ID	Artifact ID	Old Version	New Version
org.apache.commons	commons-text	1.6	1.10.0
org.apache.commons	commons-configuration2	2.2.4	2.8.0
commons-beanutils	commons-beanutils	1.9.3	1.9.4

The following dependencies have been added:

Group ID	Artifact ID	Version
org.sharegov	mjson	1.4.1

Upgrade considerationLuciadFusion

The package com.luciad.format.gml, containing legacy support for GML 2, has been removed. Its functionality has been deprecated for more than a decade, with com.luciad.format.gml2.xml.TLcdGML2ModelDecoder and com.luciad.format.gml2.xml.TLcdGML2ModelEncoder in the com.luciad.format.gml2.xml package as direct replacements.

Upgrade considerationLuciadFusion

The utility class TLcdJDOM2OGCFilter which was deprecated since 2017 has been removed. If you are using this class, you can replace it with the following code:


                           ByteArrayOutputStream outputStream = new ByteArrayOutputStream();
                           new XMLOutputter().output(element, outputStream);
                           TLcdOGCFilterDecoder filterDecoder = new TLcdOGCFilterDecoder();
                           filterDecoder.setInputStreamFactory(string -> new ByteArrayInputStream(outputStream.toByteArray()));
                           return (TLcdOGCFilter) filterDecoder.decode("");

Upgrade considerationLuciadFusion

Security updates have been applied to the following dependencies:

Group ID	Artifact ID	Old Version	New Version
com.fasterxml.jackson.core	jackson-databind	2.14.0	2.14.2
com.fasterxml.jackson.core	jackson-core	2.14.0	2.14.2
com.fasterxml.jackson.core	jackson-annotations	2.14.0	2.14.2
org.apache.xmlgraphics	batik-xml	1.11	1.16
org.apache.xmlgraphics	batik-util	1.11	1.16
org.apache.xmlgraphics	batik-transcode	1.11	1.16
org.apache.xmlgraphics	batik-swing	1.11	1.16
org.apache.xmlgraphics	batik-svggen	1.11	1.16
org.apache.xmlgraphics	batik-svg-dom	1.11	1.16
org.apache.xmlgraphics	batik-script	1.11	1.16
org.apache.xmlgraphics	batik-parser	1.11	1.16
org.apache.xmlgraphics	batik-i18n	1.11	1.16
org.apache.xmlgraphics	batik-gvt	1.11	1.16
org.apache.xmlgraphics	batik-gui-util	1.11	1.16
org.apache.xmlgraphics	batik-ext	1.11	1.16
org.apache.xmlgraphics	batik-dom	1.11	1.16
org.apache.xmlgraphics	batik-css	1.11	1.16
org.apache.xmlgraphics	batik-constants	1.11	1.16
org.apache.xmlgraphics	batik-codec	1.11	1.16
org.apache.xmlgraphics	batik-bridge	1.11	1.16
org.apache.xmlgraphics	batik-awt-util	1.11	1.16
org.apache.xmlgraphics	batik-anim	1.11	1.16
org.apache.xmlgraphics	xmlgraphics-commons	2.3	2.7
org.slf4j	slf4j-api	1.7.25	1.7.36
org.postgresql	postgresql	42.3.6	42.5.4
com.github.mreutegg	laszip4j	0.7	0.9
org.jdom	jdom2	2.0.5	2.0.6.1
org.apache.commons	commons-text	1.6	1.10
org.apache.commons	commons-lang3	3.8.1	3.12
org.apache.commons	commons-compress	1.5	1.22

The following dependencies have been removed:

Group ID	Artifact ID	Version
xalan	xalan	2.7.2
xalan	serializer	2.7.2
org.jdom	jdom	1.1.3
javax.servlet	javax.servlet-api	3.1.0

The following dependencies have been added:

Group ID	Artifact ID	Version
jakarta.servlet	jakarta.servlet-api	4.0.4
org.apache.xmlgraphics	batik-shared-resources	1.16

Upgrade considerationLuciadFusion

Security updates have been applied to the following sample dependencies of the OGC server sample:

Group ID	Artifact ID	Old Version	New Version
org.springframework.boot	spring-boot	2.1.2.RELEASE	2.7.8
org.springframework.boot	spring-boot-starter	2.1.2.RELEASE	2.7.8
org.springframework.boot	spring-boot-autoconfigure	2.1.2.RELEASE	2.7.8
org.springframework.boot	spring-boot-starter-json	2.1.2.RELEASE	2.7.8
org.springframework.boot	spring-boot-starter-logging	2.1.2.RELEASE	2.7.8
org.springframework.boot	spring-boot-starter-web	2.1.2.RELEASE	2.7.8
org.springframework	spring-aop	5.1.4.RELEASE	5.3.25
org.springframework	spring-beans	5.1.4.RELEASE	5.3.25
org.springframework	spring-context	5.1.4.RELEASE	5.3.25
org.springframework	spring-core	5.1.4.RELEASE	5.3.25
org.springframework	spring-expression	5.1.4.RELEASE	5.3.25
org.springframework	spring-jdbc	5.1.4.RELEASE	5.3.25
org.springframework	spring-tx	5.1.4.RELEASE	5.3.25
org.springframework	spring-web	5.1.4.RELEASE	5.3.25
org.springframework	spring-webmvc	5.1.4.RELEASE	5.3.25
com.zaxxer	HikariCP	3.2.0	4.0.3
org.ow2.asm	asm	5.0.4	9.4
com.fasterxml.jackson.datatype	jackson-datatype-jdk8	2.9.8	2.14.2
com.fasterxml.jackson.datatype	jackson-datatype-jsr310	2.9.8	2.14.2
com.fasterxml.jackson.module	jackson-module-parameter-names	2.9.8	2.14.2
org.eclipse.jetty.websocket	javax-websocket-client-impl	9.4.3.v20170317	9.4.50.v20221201
org.eclipse.jetty.websocket	javax-websocket-server-impl	9.4.3.v20170317	9.4.50.v20221201
org.eclipse.jetty	jetty-annotations	9.4.3.v20170317	9.4.50.v20221201
org.eclipse.jetty	jetty-client	9.4.3.v20170317	9.4.50.v20221201
org.eclipse.jetty	jetty-continuation	9.4.3.v20170317	9.4.50.v20221201
org.eclipse.jetty	jetty-http	9.4.3.v20170317	9.4.50.v20221201
org.eclipse.jetty	jetty-io	9.4.3.v20170317	9.4.50.v20221201
org.eclipse.jetty	jetty-plus	9.4.3.v20170317	9.4.50.v20221201
org.eclipse.jetty	jetty-security	9.4.3.v20170317	9.4.50.v20221201
org.eclipse.jetty	jetty-server	9.4.3.v20170317	9.4.50.v20221201
org.eclipse.jetty	jetty-servlet	9.4.3.v20170317	9.4.50.v20221201
org.eclipse.jetty	jetty-servlets	9.4.3.v20170317	9.4.50.v20221201
org.eclipse.jetty	jetty-util	9.4.3.v20170317	9.4.50.v20221201
org.eclipse.jetty	jetty-util-ajax	9.4.3.v20170317	9.4.50.v20221201
org.eclipse.jetty	jetty-webapp	9.4.3.v20170317	9.4.50.v20221201
org.eclipse.jetty	jetty-xml	9.4.3.v20170317	9.4.50.v20221201
org.slf4j	jul-to-slf4j	1.7.25	1.7.36
org.slf4j	slf4j-api	1.7.25	1.7.36
org.apache.logging.log4j	log4j-api	2.11.1	2.17.2
org.apache.logging.log4j	log4j-to-slf4j	2.11.1	2.17.2
ch.qos.logback	logback-classic	1.2.3	1.2.11
ch.qos.logback	logback-core	1.2.3	1.2.11
org.yaml	snakeyaml	1.23	1.33
org.eclipse.jetty.websocket	websocket-api	9.4.3.v20170317	9.4.50.v20221201
org.eclipse.jetty.websocket	websocket-client	9.4.3.v20170317	9.4.50.v20221201
org.eclipse.jetty.websocket	websocket-common	9.4.3.v20170317	9.4.50.v20221201
org.eclipse.jetty.websocket	websocket-server	9.4.3.v20170317	9.4.50.v20221201
org.eclipse.jetty.websocket	websocket-servlet	9.4.3.v20170317	9.4.50.v20221201

The following dependencies have been added:

Group ID	Artifact ID	Version
org.springframework.boot	spring-boot-starter-jetty	2.7.8
jakarta.annotation	jakarta.annotation-api	1.3.5
jakarta.websocket	jakarta.websocket-api	1.1.2
org.apache.tomcat.embed	tomcat-embed-el	9.0.71
org.ow2.asm	asm-commons	9.4
org.ow2.asm	asm-tree	9.4

The following dependencies have been removed:

Group ID	Artifact ID	Version
org.eclipse.jetty	jetty-unixsocket	9.4.3.v20170317
org.eclipse.jetty	jetty-schemas	9.4.3.v20170317
org.eclipse.jetty	jetty-rewrite	9.4.3.v20170317
org.eclipse.jetty	jetty-quickstart	9.4.3.v20170317
org.eclipse.jetty	jetty-proxy	9.4.3.v20170317
org.eclipse.jetty	jetty-proxy	9.4.3.v20170317
org.eclipse.jetty	jetty-nosql	9.4.3.v20170317
org.eclipse.jetty	jetty-memcached-sessions	9.4.3.v20170317
org.eclipse.jetty	jetty-jndi	9.4.3.v20170317
org.eclipse.jetty	jetty-jmx	9.4.3.v20170317
org.eclipse.jetty	jetty-jaspi	9.4.3.v20170317
org.eclipse.jetty	jetty-jaas	9.4.3.v20170317
org.eclipse.jetty	jetty-infinispan	9.4.3.v20170317
org.eclipse.jetty	jetty-gcloud-session-manager	9.4.3.v20170317
org.eclipse.jetty	jetty-deploy	9.4.3.v20170317
org.eclipse.jetty	jetty-alpn-server	9.4.3.v20170317
org.eclipse.jetty	jetty-continuation	9.4.3.v20170317
org.eclipse.jetty	jetty-continuation	9.4.3.v20170317
org.eclipse.jetty.cdi	cdi-core	9.4.3.v20170317
org.eclipse.jetty.cdi	cdi-servlet	9.4.3.v20170317
org.eclipse.jetty.cdi	cdi-websocket	9.4.3.v20170317
com.fasterxml.jackson.core	jackson-core	2.9.8
com.fasterxml.jackson.core	jackson-databind	2.9.8
javax.annotation	javax.annotation-api	1.3.2
javax.websocket	javax.websocket-api	1.0

Upgrade considerationLuciadFusion

The following dependencies have changed due to the Spring Boot upgrade from version 2.1 to 2.7:

Group ID	Artifact ID	Old Version	New Version
org.springframework.boot	spring-boot-actuator-autoconfigure	2.1.2.RELEASE	2.7.8
org.springframework.boot	spring-boot-actuator	2.1.2.RELEASE	2.7.8
org.springframework.boot	spring-boot-autoconfigure	2.1.2.RELEASE	2.7.8
org.springframework.boot	spring-boot-configuration-processor	2.1.0.RELEASE	2.7.8
org.springframework.boot	spring-boot-starter-actuator	2.1.2.RELEASE	2.7.8
org.springframework.boot	spring-boot-starter-freemarker	2.1.2.RELEASE	2.7.8
org.springframework.boot	spring-boot-starter-jdbc	2.1.2.RELEASE	2.7.8
org.springframework.boot	spring-boot-starter-json	2.1.2.RELEASE	2.7.8
org.springframework.boot	spring-boot-starter-logging	2.1.2.RELEASE	2.7.8
org.springframework.boot	spring-boot-starter-web	2.1.2.RELEASE	2.7.8
org.springframework.boot	spring-boot-starter-websocket	2.1.0.RELEASE	2.7.8
org.springframework.boot	spring-boot-starter-validation	/	2.7.8
org.springframework.boot	spring-boot-starter	2.1.2.RELEASE	2.7.8
org.springframework.boot	spring-boot	2.1.2.RELEASE	2.7.8
org.springframework.ldap	spring-ldap-core	2.3.4.RELEASE	2.4.1
org.springframework.security	spring-security-config	5.1.1.RELEASE	5.8.1
org.springframework.security	spring-security-core	5.1.1.RELEASE	5.8.1
org.springframework.security	spring-security-ldap	5.1.1.RELEASE	5.8.1
org.springframework.security	spring-security-web	5.1.1.RELEASE	5.8.1
org.springframework	spring-aop	5.1.4.RELEASE	5.3.25
org.springframework	spring-context-support	5.1.4.RELEASE	5.3.25
org.springframework	spring-context	5.1.4.RELEASE	5.3.25
org.springframework	spring-expression	5.1.4.RELEASE	5.3.25
org.springframework	spring-jdbc	5.1.4.RELEASE	5.3.25
org.springframework	spring-messaging	5.1.2.RELEASE	5.3.25
org.springframework	spring-web	5.1.4.RELEASE	5.3.25
org.springframework	spring-webmvc	5.1.4.RELEASE	5.3.25
org.springframework	spring-websocket	5.1.2.RELEASE	5.3.25
org.springframework	spring-beans	5.1.4.RELEASE	5.3.25
org.springframework	spring-core	5.1.4.RELEASE	5.3.25
org.springframework	spring-tx	5.1.4.RELEASE	5.3.25
org.springdoc	springdoc-openapi-common	1.6.9	1.6.14
org.springdoc	springdoc-openapi-security	1.6.9	1.6.14
org.springdoc	springdoc-openapi-ui	1.6.9	1.6.14
org.springdoc	springdoc-openapi-webmvc-core	1.6.9	1.6.14
io.swagger.core.v3	swagger-annotations	2.2.0	2.2.7
io.swagger.core.v3	swagger-core	2.2.0	2.2.7
io.swagger.core.v3	swagger-models	2.2.0	2.2.7
org.webjars	swagger-ui	4.11.1	4.15.5
org.webjars	webjars-locator-core	0.50	0.52
org.apache.tomcat.embed	tomcat-embed-el	/	9.0.71
org.yaml	snakeyaml	1.23	1.33
com.zaxxer	HikariCP	3.2.0	4.0.3
org.hdrhistogram	HdrHistogram	2.1.9	2.1.12
io.github.classgraph	classgraph	4.8.147	4.8.149
com.fasterxml	classmate	1.4.0	1.5.1
org.freemarker	freemarker	2.3.28	2.3.32
org.hibernate.validator	hibernate-validator	6.0.14.Final	6.2.5.Final
org.jboss.logging	jboss-logging	3.3.2.Final	3.4.1.Final
org.slf4j	jul-to-slf4j	1.7.25	1.7.36
org.slf4j	jcl-over-slf4j	1.7.25	1.7.36
org.slf4j	log4j-over-slf4j	1.7.25	1.7.36
org.apache.logging.log4j	log4j-api	2.11.1	2.17.2
org.apache.logging.log4j	log4j-to-slf4j	2.11.1	2.17.2
ch.qos.logback	logback-classic	1.2.3	1.2.11
ch.qos.logback	logback-core	1.2.3	1.2.11
com.fasterxml.jackson.datatype	jackson-datatype-jdk8	2.9.8	2.14.2
com.fasterxml.jackson.datatype	jackson-datatype-jsr310	2.9.8	2.14.2
com.fasterxml.jackson.module	jackson-module-parameter-names	2.9.8	2.14.2
com.fasterxml.jackson.dataformat	jackson-dataformat-yaml	2.9.8	2.14.2
io.micrometer	micrometer-core	1.1.2	1.9.7

The following dependencies have been added:

Group ID	Artifact ID	Version
org.springframework.security	spring-security-crypto	5.8.1
org.springframework.boot	spring-boot-starter-security	2.7.8
jakarta.validation	jakarta.validation-api	2.0.2

The following dependencies have been removed:

Group ID	Artifact ID	Version
com.google.code.gson	gson	2.8.5
com.fasterxml.jackson.dataformat	jackson-dataformat-cbor	2.9.8
com.fasterxml.jackson.dataformat	jackson-dataformat-xml	2.9.8
com.fasterxml.jackson.module	jackson-module-afterburner	2.9.8
com.fasterxml.jackson.module	jackson-module-jaxb-annotations	2.9.8
javax.annotation	javax.annotation-api	1.3.2
org.glassfish.web	javax.el	2.2.4
javax.el	javax.el-api	3.0.0
org.springframework.plugin	spring-plugin-core	1.2.0.RELEASE
org.springframework.plugin	spring-plugin-metadata	1.2.0.RELEASE
javax.validation	validation-api	2.0.1

LuciadFusion can be used with a jetty embedded servlet container. The jetty sample dependencies are used in this situation. The following sample dependencies related to jetty have changed:

org.ow2.asm	asm	5.0.4	9.4
org.eclipse.jetty.websocket	javax-websocket-client-impl	9.4.3.v20170317	9.4.50.v20221201
org.eclipse.jetty.websocket	javax-websocket-server-impl	9.4.3.v20170317	9.4.50.v20221201
org.eclipse.jetty	jetty-annotations	9.4.3.v20170317	9.4.50.v20221201
org.eclipse.jetty	jetty-client	9.4.3.v20170317	9.4.50.v20221201
org.eclipse.jetty	jetty-continuation	9.4.3.v20170317	9.4.50.v20221201
org.eclipse.jetty	jetty-http	9.4.3.v20170317	9.4.50.v20221201
org.eclipse.jetty	jetty-io	9.4.3.v20170317	9.4.50.v20221201
org.eclipse.jetty	jetty-plus	9.4.3.v20170317	9.4.50.v20221201
org.eclipse.jetty	jetty-security	9.4.3.v20170317	9.4.50.v20221201
org.eclipse.jetty	jetty-server	9.4.3.v20170317	9.4.50.v20221201
org.eclipse.jetty	jetty-servlet	9.4.3.v20170317	9.4.50.v20221201
org.eclipse.jetty	jetty-servlets	9.4.3.v20170317	9.4.50.v20221201
org.eclipse.jetty	jetty-util	9.4.3.v20170317	9.4.50.v20221201
org.eclipse.jetty	jetty-util-ajax	9.4.3.v20170317	9.4.50.v20221201
org.eclipse.jetty	jetty-webapp	9.4.3.v20170317	9.4.50.v20221201
org.eclipse.jetty	jetty-xml	9.4.3.v20170317	9.4.50.v20221201
org.slf4j	slf4j-api	1.7.25	1.7.36
org.eclipse.jetty.websocket	websocket-api	9.4.3.v20170317	9.4.50.v20221201
org.eclipse.jetty.websocket	websocket-client	9.4.3.v20170317	9.4.50.v20221201
org.eclipse.jetty.websocket	websocket-common	9.4.3.v20170317	9.4.50.v20221201
org.eclipse.jetty.websocket	websocket-server	9.4.3.v20170317	9.4.50.v20221201
org.eclipse.jetty.websocket	websocket-servlet	9.4.3.v20170317	9.4.50.v20221201

The following sample dependencies related to jetty have been added:

Group ID	Artifact ID	Version
org.springframework.boot	spring-boot-starter-jetty	2.7.8
jakarta.annotation	jakarta.annotation-api	1.3.5
jakarta.websocket	jakarta.websocket-api	1.1.2
org.ow2.asm	asm-commons	9.4
org.ow2.asm	asm-tree	9.4

The following sample dependencies related to jetty have been removed:

Group ID	Artifact ID	Version
org.eclipse.jetty	jetty-unixsocket	9.4.3.v20170317
org.eclipse.jetty	jetty-schemas	9.4.3.v20170317
org.eclipse.jetty	jetty-rewrite	9.4.3.v20170317
org.eclipse.jetty	jetty-quickstart	9.4.3.v20170317
org.eclipse.jetty	jetty-proxy	9.4.3.v20170317
org.eclipse.jetty	jetty-proxy	9.4.3.v20170317
org.eclipse.jetty	jetty-nosql	9.4.3.v20170317
org.eclipse.jetty	jetty-memcached-sessions	9.4.3.v20170317
org.eclipse.jetty	jetty-jndi	9.4.3.v20170317
org.eclipse.jetty	jetty-jmx	9.4.3.v20170317
org.eclipse.jetty	jetty-jaspi	9.4.3.v20170317
org.eclipse.jetty	jetty-jaas	9.4.3.v20170317
org.eclipse.jetty	jetty-infinispan	9.4.3.v20170317
org.eclipse.jetty	jetty-gcloud-session-manager	9.4.3.v20170317
org.eclipse.jetty	jetty-deploy	9.4.3.v20170317
org.eclipse.jetty	jetty-alpn-server	9.4.3.v20170317
org.eclipse.jetty	jetty-continuation	9.4.3.v20170317
org.eclipse.jetty	jetty-continuation	9.4.3.v20170317
org.eclipse.jetty.cdi	cdi-core	9.4.3.v20170317
org.eclipse.jetty.cdi	cdi-servlet	9.4.3.v20170317
org.eclipse.jetty.cdi	cdi-websocket	9.4.3.v20170317
javax.websocket	javax.websocket-api	1.0

Upgrade considerationLuciadFusion

LCD-12684

The following methods have been removed in favor of #getInputStreamFactory and #setInputStreamFactory:

TLcdGeoTIFFModelDecoder#getImageInputStreamFactory
TLcdGeoTIFFModelDecoder#setImageInputStreamFactory
TLcdTABRasterModelDecoder#getImageInputStreamFactory
TLcdTABRasterModelDecoder#setImageInputStreamFactory
TLcdTFWRasterModelDecoder#getImageInputStreamFactory
TLcdTFWRasterModelDecoder#setImageInputStreamFactory
TLcdRasterModelDecoder#getTileInputStreamFactory
TLcdRasterModelDecoder#setTileInputStreamFactory
TLcdDIMAPModelDecoder#getImageInputStreamFactory
TLcdDIMAPModelDecoder#setImageInputStreamFactory

The following jackson dependencies have been upgraded:

Group ID	Artifact ID	Old Version	New Version
com.fasterxml.jackson.dataformat	jackson-dataformat-xml	2.9.8	2.14.0
com.fasterxml.jackson.dataformat	jackson-dataformat-cbor	2.9.8	2.14.0
com.fasterxml.jackson.datatype	jackson-datatype-jdk8	2.9.8	2.14.0
com.fasterxml.jackson.datatype	jackson-datatype-jsr310	2.9.8	2.14.0
com.fasterxml.jackson.module	jackson-module-afterburner	2.9.8	2.14.0
com.fasterxml.jackson.module	jackson-module-jaxb-annotations	2.9.8	2.14.0

Upgrade considerationLuciadFusion

LF-2368

The following OGC server sample dependencies have been upgraded:

Group ID	Artifact ID	Old Version	New Version
com.fasterxml.jackson.core	jackson-core	2.9.8	2.14.0
com.fasterxml.jackson.core	jackson-databind	2.9.8	2.14.0
com.fasterxml.jackson.datatype	jackson-datatype-jdk8	2.9.8	2.14.0
com.fasterxml.jackson.datatype	jackson-datatype-jsr310	2.9.8	2.14.0
com.fasterxml.jackson.module	jackson-module-parameter-names	2.9.8	2.14.0

ImprovementLuciadFusion

LF-2329

The custom properties can be used to store additional metadata information about a Data, or they can be used to store information needed when extending LuciadFusion with custom functionality. An example of the former would be to add custom properties publisherName (string) and publicationYear (number) to store the name of the publisher of the Data and the year it was published. An example of the latter would be to add a spotlight (boolean) property to a Data, and using it to highlight certain Data that should stand out from the rest.

Custom properties can be set and obtained for a specific Data using the LuciadFusion Studio REST API. The PATCH /api/data/{id} endpoint allows users to set the custom properties for a Data. The GET /api/data/{id} endpoint allows users to obtain the custom properties for a Data.

New featureLuciadFusion

LuciadFusion is able to pick up custom properties from a metadata file when crawling or adding Data. This allows users to automatically associate additional metadata information with Data when it gets added to LuciadFusion. For example, if the metadata specifies the name of the publisher of the Data and a year when the Data was published, then this information could be extracted from the metadata and added as custom properties to the Data in LuciadFusion when it is imported.

An implementation of ILfnCustomPropertyDecoder is needed to let LuciadFusion extract custom properties from a TLcdISO19115Metadata decoded by an ILcdMetadataDecoder. To learn more, see this article.

New featureLuciadFusion

LuciadFusion can be configured to allow querying Data based on queryable properties. This allows users to search for Data based on the additional metadata information that is associated with the Data. For example, when using custom properties publisherName (string) and publishYear (number) to store the name of the publisher of the Data and the year it was published, a user can search for all Data published by a specific publisher during a specific year.

An implementation of ILfnCustomPropertyDecoder needs to be provided so that LuciadFusion is aware of the type of the custom properties, as this has an impact on the supported query operations. See the Define the custom properties article for more information.

Querying Data based on queryable properties is done using the LuciadFusion Studio REST API. The GET api/data/queryable-properties endpoint lists all the properties that can be used to query Data. To query Data, use the GET api/data/filter endpoint. For more information on how to query Data and which operations are supported, see this article.

New featureLuciadFusion

LuciadLightspeed now has support for the Canadian Geodetic Vertical Datum of 2013, as well as the associated EPSG references EPSG:6649 to EPSG:6665, EPSG:9711, EPSG:9714 and EPSG:9715.

ImprovementLuciadFusion

LCD-12354

You can now plug in an ILcdWFSClientModelEncoderFactory by adding an @LcdServiceannotation to the implementation. This interface is used by WFS services to encode features. Only the factory with the highest priority is used. By default, a factory with support for GML 2 / 3.1 / 3.2 and GeoJSON is used.

ImprovementLuciadFusion

LF-2294

The metadata of a data can no longer overwrite the id of the data when uploading new metadata, recrawling or refreshing. This ensures that the id of a data always remains the same.

ImprovementLuciadFusion

The LuciadFusion Studio async jobs thread pool is now configurable. the thread pool size can be configured with the following properties:

fusion.studio.configuration.jobs.threadPool.minimumSize
fusion.studio.configuration.jobs.threadPool.maximumSize

These properties are configured in the fusion.common.yml configuration file. Have a look there for more information about these properties.

ImprovementLuciadFusion

PostgreSQL 15 and SQL Server 2022 are now supported as a database for LuciadFusion Studio.

ImprovementLuciadFusion

LCD-12602

A new interface ILcdWMTSGXYLayerFactory has been introduced to create request-based layer factories for a WMTS layer. By adding an @LcdServiceannotation to an implementation, it is automatically picked by at runtime by the LuciadFusion Platform application.

ImprovementLuciadFusion

LCD-12572

The performance of TLcdEllipsoidRhumblineUtil#intersectionGeodesicRhumblineSFCT has improved one to two orders of magnitude for the case where the rhumbline is a meridian or a parallel.

ImprovementLuciadFusion

LF-2138

The default built-in DataSource bean has been marked with @Primary annotation to indicate that this DataSource bean will be given preference when multiple DataSource beans are defined. This essentially ensures that LuciadFusion will work as intended in the presence of multiple user defined DataSource beans.

ImprovementLuciadFusion

Upgrade considerationLuciadFusion

For its new S3 functionalities, LuciadFusion makes the use of some new libraries:

AWS SDK Annotations (version 2.17.168)
AWS SDK Apache-client (version 2.17.168)
AWS SDK Arns (version 2.17.168)
AWS SDK Auth (version 2.17.168)
AWS SDK Aws-core (version 2.17.168)
AWS SDK Aws-query-protocol (version 2.17.168)
AWS SDK Aws-xml-protocol (version 2.17.168)
AWS SDK Http-client-spi (version 2.17.168)
AWS SDK Json-utils (version 2.17.168)
AWS SDK Metrics-spi (version 2.17.168)
AWS SDK Profiles (version 2.17.168)
AWS SDK Protocol-core (version 2.17.168)
AWS SDK Regions (version 2.17.168)
AWS SDK S3 (version 2.17.168)
AWS SDK Sdk-core (version 2.17.168)
AWS SDK Third-party-jackson-core (version 2.17.168)
AWS SDK Utils (version 2.17.168)
Reactivestreams (version 1.0.3)
Eventstream (version 1.0.1)

A few libraries were also updated:

Commons-codec (version 1.11)
Httpcomponents Httpclient (version 4.5.13)
Httpcomponents Httpcore (version 4.4.13)
org.reactivestreams reactive-streams New 1.0.3 MIT)
Slf4j (version 1.7.36)

Upgrade considerationLuciadFusion

LuciadFusion now uses an RSQL library to support querying Data against LuciadFusion's built-in standard and user defined custom properties.As a result, upgrading an older version of LuciadFusion to V2022.1 or later is desired. The following JAR has been added.

rsql-common-<version>.jar

Upgrade considerationLuciadFusion

The following methods have been deprecated:

TLcdGeoTIFFModelDecoder#getImageInputStreamFactory
TLcdGeoTIFFModelDecoder#setImageInputStreamFactory
TLcdTABRasterModelDecoder#getImageInputStreamFactory
TLcdTABRasterModelDecoder#setImageInputStreamFactory
TLcdTFWRasterModelDecoder#getImageInputStreamFactory
TLcdTFWRasterModelDecoder#setImageInputStreamFactory
TLcdRasterModelDecoder#getTileInputStreamFactory
TLcdRasterModelDecoder#setTileInputStreamFactory
TLcdDIMAPModelDecoder#getImageInputStreamFactory
TLcdDIMAPModelDecoder#setImageInputStreamFactory

The getters now simply return the result of their sibling #getInputStreamFactory, while the setters no longer have any effect. Please change any calls to these methods to #getInputStreamFactory or #setInputStreamFactory instead. In the next major release, these methods will be removed entirely.

LCD-12527

In a Lightspeed view, labels that are anchored to an other label were sometimes not displayed.

Bug fixLuciadFusion

EPSG:7404 could be decoded by TLcdEPSGReferenceParser, even though it was not correctly supported. Trying to decode EPSG:7404 now throws a ParseException as expected.

Bug fixLuciadFusion

LCD-12228, LCD-7715

Upgrade considerationLuciadFusion

The TLcdGeoJsonModelEncoder will now detect a primary key that has been declared on a supertype of a TLcdDataType. The primary key property is used as id value of the GeoJson feature, and is omitted from the properties list.

      {
        "type" : "Feature",
        "id" : "0001",
        "geometry" : { ... },
        "properties" : {
          "nonPrimaryKeyProperty" : "someValue",
          ...
        }
      }

New featureLuciadFusion

The TLfnPointCloudPreprocessor now supports Draco compression. You can use this new functionality through the API:


                           builder.pointCloudCompression(ELcdOGC3DTilesMeshCompressionType.DRACO)

LCD-11939

The OGC server sample now integrates with Spring Boot. It takes advantage of Java Servlet 3.0 annotations, which makes it much easier to set up. Additionally, a new article How to use Spring Boot with the OGC Web Server Suite explains how to integrate your own server created with the OGC Web Server Suite in a Spring Boot application.

ImprovementLuciadFusion

You can now easily calculate the area of a complex polygon using the following new methods:

TLcdEllipsoidUtil.geodesicArea(ILcdShape, ILcdEllipsoid)
TLcdSphereUtil.geodesicArea(ILcdShape, double)
TLcdCartesian.area(ILcdShape)

ImprovementLuciadFusion

TLcdGML32Triangle/TLcdGML31Triangle now implement ILcdRing.

ImprovementLuciadFusion

LF-2159

It is now possible to implement request-based SLD rendering customizations for a LuciadFusion product with an SLD style. To accomplish this, a new method has been added to the WMS API: ALcdSLDWMSGXYLayerFactory#createGXYLayer(ILcdModel aModel, ALcdWMSLayer aWMSLayer, TLcdSLDFeatureTypeStyle[] aStyle, TLcdWMSRequestContext aRequestContext) Based on the request stored in the TLcdWMSRequestContext changes can be applied to the TLcdSLDFeatureTypeStyle[] to allow for SLD rendering customizations.

It is now also possible to configure feature type styles on the server side. This is done by plugging in a custom implementation of a ILcdWMSSLDFeatureTypeStyleProvider in the ALcdOGCWMSCommandDispatcherFactory by overriding the method ALcdOGCWMSCommandDispatcherFactory#createSLDFeatureTypeStyleProvider(ServletConfig aServletConfig).

ImprovementLuciadFusion

The following core API classes now implement ILcdCurve:

The following core API classes now implement ILcdRing:

TLcdXYZFloatPolygon

ImprovementLuciadFusion

The WMS client now supports server-side map rotations if you are using non-tiled visualization in GXY views with a projection supported by the WMS server. You can enable this capability with the boolean System property com.luciad.wms.client.serverMapRotation. If you set it to true, map rotations are propagated to the WMS server through the custom GetMap request parameter angle. When used in combination with LuciadFusion or other WMS servers supporting this parameter, it ensures that labels on rotated maps are always upright, and that oriented icons still have their intended orientation.

ImprovementLuciadFusion

The WMS server now supports map rotations: by means of a new custom GetMap request parameter angle, WMS clients can indicate the map rotation in degrees, measured clockwise around the center of the map.

ImprovementLuciadFusion

The user can now register their own ILcdWMTSGetLegendGraphicRequestEncoder or ILcdWMSGetLegendGraphicRequestEncoder using the mechanism of the TLcdServiceLoader. This way it is possible to generate custom legends for GetLegendGraphic requests coming from WMS or WMTS clients.

ImprovementLuciadFusion

LCD-7979, LF-2236

The WMS and WMTS server now support GetLegendGraphic requests. The default response is an icon that depends on the type of model used: elevation, raster or vector.

ImprovementLuciadFusion

It is now possible to configure access constraint and contact information for services of type WMS, WMTS, WFS and WCS directly in LuciadFusion Studio. This information will be included in the service capabilities.

ImprovementLuciadFusion

The WMS client can now parse contact information from the GetCapabilities response. This information gets added to the ALcdWMSServiceMetaData

ImprovementLuciadFusion

It is now possible to configure access constraints and contact information of the service metadata of the WMS server capabilities. This information can be configured using the ALcdWMSServiceMetaData.

ImprovementLuciadFusion

LCD-12187

TLcdGML2ModelEncoder and TLcdGML31ModelEncoder's generated feature collection element is now in the _FeatureCollection substitution group. This improves embedding feature collections into other data models, such as WMTS feature info responses.

ImprovementLuciadFusion

ImprovementLuciadFusion

LCD-11314

The TLcdCSVModelDecoder now creates models that implement ILcdMultiDimensionalModel, when at least one of the columns is specified to contain values of type TLcdCSVDataSource.ColumnType.DATE_TIME. The resulting model contains one time dimension for each column of that type.

ImprovementLuciadFusion

LCD-12039

Introduced a new method named TLspViewNavigationUtil#animatedZoom, which performs an animated zoom to a target map scale on a Lightspeed view.

ImprovementLuciadFusion

LCD-12088

ILspView implementations now fire property change events for the background and paintingOrder properties.

ImprovementLuciadFusion

TLcdJPEG2000ModelDecoder: the decoder can now parse the model reference from embedded GMLJP2 in the file. The decoder supports versions 1.0, 2.0 and 2.1 of the GMLJP2 specification, and will only parse the model reference, other elements will be ignored but are accessible via the TLcdJPEG2000ModelDescriptor.

ImprovementLuciadFusion

LCD-10677

Calling ILcdModel#dispose() on the output of TLcdJPEG2000ModelDecoder now closes the JPEG2000 file.

ImprovementLuciadFusion

LCD-8189

The JPEG2000 model decoder now decodes geo-references using the RPC00B coefficients without requiring a world file. When no geo-reference data is available as GeoTIFF tags the decoder looks for the existence of the optional _rpc.txt which contains the RPC00B coefficients.

ImprovementLuciadFusion

LCD-8903

JPEG2000's native library now requires GLIBC 2.3.4, down from 2.14. This improves compatibility with Red Hat Enterprise Linux 6.

ImprovementLuciadFusion

The TLcdJPEG2000ModelDecoder and TLcdJPIPModelDecoder have been updated to handle monochrome, RGB and multi band images. The number of bands that can be decoded is unlimited with the limitation that each band consists of up to 16 bits. These improvements are only available via the imaging API. Please refer to the class javadoc for more information.

ImprovementLuciadFusion

The TLcdJPEG2000ModelDecoder and TLcdJPIPModelDecoder have been adapted for integration with the new imaging API. They now produce models with domain objects that extend ALcdImage. Please refer to the class javadoc, com.luciad.imaging package javadoc and to the developer's guide for more information.

ImprovementLuciadFusion

LCD-4415

The JPIP model decoder now verifies that the provided source name points to a valid JPIP server in its canDecode method. Previously it would only verify that the source name is a valid URI. You can get the old behavior by calling setQueryServerOnCanDecode(false).

ImprovementLuciadFusion

LCD-4332

The JPEG2000 and JPIP model decoders now document that image components may be scaled. The model descriptors also expose the necessary information to allow computing the original values in the image.

ImprovementLuciadFusion

LCD-4252

The JPEG2000 performance for tiled data has improved.

ImprovementLuciadFusion

Bug fixLuciadFusion

The TLcdCSVModelDecoder now also parses the time component of a date by default, using a SimpleDateFormat with pattern "yyyy-MM-dd HH:mm:ssXXX" for columns of type TLcdCSVDataSource.ColumnType.DATE_TIME. This DateFormat can be modified with TLcdCSVModelDecoder#setDateFormat.

Bug fixLuciadFusion

Bug fixLuciadFusion

LCD-8496

Increased maximum allowed quality of TLcdJPEG2000ModelEncoder from 1.0 to 8.0, to allow encoding of higher-quality JPEG2000 files.

Bug fixLuciadFusion

Fixed an issue in TLcdJPEG2000ModelDecoder where, in some cases, alpha channels were not properly detected.

Bug fixLuciadFusion

LCD-7914

Fixed an issue in TLcdJPIPModelDecoder where RGB data with 16 bits per component could not be decoded.

Bug fixLuciadFusion

LCD-7893

Bug fixLuciadFusion

LMAP-5479, LCD-94

The positioning of JPEG2000 rasters based on JPW files with arbitrary rotations has been corrected. Additionally, sheared rasters now supported.

Bug fixLuciadFusion

The name of the system property controlling the JPEG2000 native decoder pool size has been changed from JPEG2000_POOL_SIZE to jpeg2000.pool.size, in line with the usual naming conventions. The old system property name is still used as a fallback, for backwards compatibility.

Bug fixLuciadFusion

Attempting to load a non-existing file no longer crashes the application.

Bug fixLuciadFusion

LMAP-3932

Loading a corrupted JPEG2000 file no longer crashes the entire application.

Bug fixLuciadFusion

LMAP-3850

TLcdJPEG2000ModelDecoder was allocating large amounts of native memory. On 32 bit platforms this was sometimes exceeding the virtual memory space of the process, leading to a crash. LuciadMap now uses a pool of "connections" to the native JPEG2000 library, limiting the amount of memory used. The size of this pool can modified by setting the JPEG2000_POOL_SIZE system property (the default value is 2).

Bug fixLuciadFusion

The Linux 64-bit version of the libLcdJPEG2000.so depended on an older version of the standard C++ library (libstc++.so.5). The library is now linked against libstdc++.so.6.

Bug fixLuciadFusion

TLcdJPEG2000ModelDecoder now correctly supports JPEG2000 images with color maps.

Upgrade considerationLuciadFusion

Third party libraries used in the samples have been moved to the samples/lib/thirdparty directory.

Upgrade considerationLuciadFusion

The two modules lcd_jpeg2000_decoder and lcd_jpeg2000_encoder have been merged into one module lcd_jpeg2000, which contains the JPEG2000 model decoder and encoder.

Upgrade considerationLuciadFusion

The swaggerV2Url property of the response returned by the /api endpoint has been renamed to apiSpecification.

Upgrade considerationLuciadFusion

The LuciadFusion Studio REST API specification now follows the OpenAPI 3 specification. Previously this followed the Swagger 2 specification. If you are using a tool to automatically generate an API based on the LuciadFusion Studio REST API specification then you now need to make sure it supports the OpenAPI 3 specification. The interactive console and REST API documentation have been updated to use the OpenAPI 3 version of the specification and can be used as before.

To support the upgrade from Swagger 2 to OpenAPI 3, the following dependencies were added to LuciadFusion:

Group ID	Artifact ID	Version
org.springdoc	springdoc-openapi-ui	1.6.9
org.springdoc	springdoc-openapi-common	1.6.9
org.springdoc	springdoc-openapi-webmvc-core	1.6.9
org.springdoc	springdoc-openapi-security	1.6.9
io.swagger.core.v3	swagger-annotations	2.2.0
io.swagger.core.v3	swagger-core	2.2.0
io.swagger.core.v3	swagger-models	2.2.0
io.github.classgraph	classgraph	4.8.147
org.webjars	swagger-ui	4.11.1
org.webjars	webjars-locator-core	0.50
com.fasterxml.jackson.dataformat	jackson-dataformat-yaml	2.9.8

Dependencies related to Springfox and the older version of Swagger have been removed.

Upgrade considerationLuciadFusion

The com.luciad.format.raster package is no longer split between multiple jars. This means that the following classes have been moved to their own sub package:

Class	New Package
`TLcdJPEG2000AssociationBox`	`com.luciad.format.jpeg2000`
`TLcdJPEG2000Box`	`com.luciad.format.jpeg2000`
`TLcdJPEG2000ImageDecoder`	`com.luciad.format.jpeg2000`
`TLcdJPEG2000ModelDecoder`	`com.luciad.format.jpeg2000`
`TLcdJPEG2000ModelDescriptor`	`com.luciad.format.jpeg2000`
`TLcdJPIPModelDecoder`	`com.luciad.format.jpeg2000`
`TLcdJPIPModelDescriptor`	`com.luciad.format.jpeg2000`
`TLcdJPEG2000ModelEncoder`	`com.luciad.format.jpeg2000`
`TLcdBCIRasterModelDecoder`	`com.luciad.format.bci`
`TLcdBCIRasterModelDescriptor`	`com.luciad.format.bci`
`TLcdBCITileDecoder`	`com.luciad.format.bci`
`TLcdDIMAPModelDecoder`	`com.luciad.format.dimap`
`TLcdDIMAPModelDescriptor`	`com.luciad.format.dimap`
`TLcdECWConfiguration`	`com.luciad.format.ecw`
`TLcdECWImageDecoder`	`com.luciad.format.ecw`
`TLcdECWModelDecoder`	`com.luciad.format.ecw`
`TLcdECWModelDescriptor`	`com.luciad.format.ecw`
`TLcdGeoSPOTSubsetDescriptor`	`com.luciad.format.geospot`
`TLcdGeoSPOTSceneDescriptor`	`com.luciad.format.geospot`
`TLcdGeoSPOTRasterDescriptor`	`com.luciad.format.geospot`
`TLcdGeoSPOTRaster`	`com.luciad.format.geospot`
`TLcdGeoSPOTModelDescriptor`	`com.luciad.format.geospot`
`TLcdGeoSPOTModelDecoder`	`com.luciad.format.geospot`
`TLcdMrSIDImageDecoder`	`com.luciad.format.mrsid`
`TLcdMrSIDModelDecoder`	`com.luciad.format.mrsid`
`TLcdMrSIDModelDescriptor`	`com.luciad.format.mrsid`
`TLcdCADRGBoundaryRectangleDescriptor`	`com.luciad.format.cadrg`
`TLcdCADRGDirectoryModelDecoder`	`com.luciad.format.cadrg`
`TLcdCADRGFrameDescriptor`	`com.luciad.format.cadrg`
`TLcdCADRGImageDecoder`	`com.luciad.format.cadrg`
`TLcdCADRGModelDecoder`	`com.luciad.format.cadrg`
`TLcdCADRGModelDescriptor`	`com.luciad.format.cadrg`
`TLcdCADRGMultilevelRasterModelDescriptor`	`com.luciad.format.cadrg`
`TLcdCADRGRaster`	`com.luciad.format.cadrg`
`TLcdCADRGTile`	`com.luciad.format.cadrg`
`TLcdECRGMediaMetadata`	`com.luciad.format.ecrg`
`TLcdECRGModelDecoder`	`com.luciad.format.ecrg`
`TLcdECRGModelDescriptor`	`com.luciad.format.ecrg`
`TLcdECRGMultilevelRasterModelDescriptor`	`com.luciad.format.ecrg`
`TLcdECRGTile`	`com.luciad.format.ecrg`
`ELcdNITFBandRepresentation`	`com.luciad.format.nitf`
`TLcdNITFGXYLayerFactory`	`com.luciad.format.nitf`
`TLcdNITFModelDecoder`	`com.luciad.format.nitf`
`TLcdNITFModelDescriptor`	`com.luciad.format.nitf`
`TLcdNITFTextSegment`	`com.luciad.format.nitf`
`TLcdNITFUncompressedImageDecoder`	`com.luciad.format.nitf`
`TLspNITFLayerFactory`	`com.luciad.format.nitf`
`TLcdSwissDHMMatrixModelDecoder`	`com.luciad.format.swissdhm`
`TLcdSwissDHMMatrixModelDescriptor`	`com.luciad.format.swissdhm`
`TLcdUSRPAccuracyDescriptor`	`com.luciad.format.usrp`
`TLcdUSRPDatasetModelDescriptor`	`com.luciad.format.usrp`
`TLcdUSRPLegend`	`com.luciad.format.usrp`
`TLcdUSRPModelDecoder`	`com.luciad.format.usrp`
`TLcdUSRPModelDescriptor`	`com.luciad.format.usrp`
`TLcdUSRPTile`	`com.luciad.format.usrp`
`TLcdUSRPZoneDescriptor`	`com.luciad.format.usrp`

If you encounter any compile errors due to these changes, simply update the relevant import statement.

Upgrade considerationLuciadFusion

Upgraded the PostgreSQL JDBC driver to version 42.3.6.

Upgrade considerationLuciadFusion

The samples now depend on the HikariCP third-party library. It is used to illustrate how the database model decoders can use a database connection pooling framework.

Upgrade considerationLuciadFusion

The SQLiteJ library has been updated to version 3.36.0.lcd-2 to improve compatibility with Hibernate 5.

Upgrade considerationLuciadFusion

To allow for greater extensibility, the signature of the method

ILcdWMSGetLegendGraphicRequestEncoder#encode(ALcdWMSLayer,ALcdSLDLayer,TLcdSLDStyledLayerDescriptor,String,String,float,int,int,OutputStream,TLcdWMSRequestContext)

has been changed into #encode(TLcdWMSGetLegendGraphicRequestContext,TLcdWMSRequestContext,OutputStream). TLcdWMSGetLegendGraphicRequestContext gives access to the original method arguments and a number of additional arguments.

The change impacts WMS implementations that use an implementation of ILcdWMSGetLegendGraphicRequestEncoder.

Upgrade considerationLuciadFusion

Support for 32-bit Windows will be phased out. Starting with LWJGL, new or upgraded native libraries will no longer include 32-bit versions.

Upgrade considerationLuciadFusion

The JAXB implementation which is used in LuciadFusion has been upgraded to 2.3.6.

Upgrade considerationLuciadFusion

LCD-12054

The LWJGL Java binding for the OpenGL and OpenCL APIs has been updated to version 3.3.1. For Linux, the glibc (GNU C Library) minimum version has been raised to 2.27.

Upgrade considerationLuciadFusion

The third-party library dependencies Apache HttpClient, HttpClient Cache and HttpMime have been updated from version 4.5.6 to 4.5.13. Their dependencies have also been updated accordingly: Apache HttpCore from version 4.4.10 to 4.4.13, Apache Commons Codec from version 1.10 to 1.11.

Upgrade considerationLuciadFusion

LCD-12142

The version of Ehcache was updated from 3.2.0 to 3.10.0 to improve compatibility with Java 17.

Upgrade considerationLuciadFusion

The ILcdPolyline constructor parameter of TLcdSHPPolylineZ now also needs to be an instance of ILcdCurve.

Upgrade considerationLuciadFusion

The createFilteredModel(ILcdModel aSourceModel, TLcdWFSGetFeatureConstraints aConstraints) method of ILcdWFSFilteredModelFactory now imposes new conditions on the elements in the model. Any ILcdPolyline or ILcdPolygon model elements now also need to implement ILcdCurve or ILcdRing, respectively.

Upgrade considerationLuciadFusion

By default, TLspLonLatGridLayerBuilder's layers now generate lines that use the same ILcdGeodeticDatum as the world reference of the view, even when the world reference of the view changes. It always used the WGS 84 datum before this change. It is still possible to use a fixed geodetic datum by using the TLspLonLatGridLayerBuilder#createModel method that takes an ILcdGeodeticDatum as argument.

ImprovementLuciadFusion

LCD-12129

The Maven sample project setup script 'build/maven/setup-sample-project.xml' now uses NodeJS instead of the Nashorn JavaScript engine. This means you now have to install NodeJS before running the setup script.

LCD-12202

TLspShapeLayerBuilder: the outline of a polygon with points on the poles would be clipped on the equator in the Lambert Conformal projection.

Bug fixLuciadFusion

TLcdGXYAsynchronousPaintQueue: after a period of inactivity, the isEmpty method could incorrectly return false.

ImprovementLuciadFusion

LF-2215

Creating a WFS service for an unsupported product name - containing characters other than letters, digits or underscores - led to a broken service. To avoid this, the creation no longer works for unsupported product names and the user gets notified of the reason.

Bug fixLuciadFusion

LCD-12185

TLcdOGC3DTilesModelDecoder: fixed a NullPointerException that could occur when decoding a 3D Tiles dataset containing GLTF without primitives.

Bug fixLuciadFusion

LF-2219

Resolved an issue with the default values of the cache configuration of LuciadFusion Platform services. The cache.enabled and cache.maxAge properties were uninitialized if the properties were missing from the configuration profile. Meaning that caching was disabled by default, while the yml configuration files mentioned caching is enabled by default. The default values have been changed so caching is enabled by default and the maxAge property is set to 30 days by default.

The following caching properties have been affected:

fusion.ogctilesservice.cache.enabled
fusion.ogctilesservice.cache.maxAge
fusion.panoramics.cache.enabled
fusion.panoramics.cache.maxAge
fusion.hspc.cache.enabled
fusion.hspc.cache.maxAge
fusion.studio.webapp.cache.enabled
fusion.studio.webapp.cache.maxAge

Bug fixLuciadFusion

LCD-12169

A few EPSG reference are defined using axes that point west and south, instead of the usual east and north:

EPSG:2065
EPSG:5513
EPSG:8352

The coordinates of these references are now correctly interpreted and transformed.

Bug fixLuciadFusion

LCD-12179

The SLD label painting pipeline incorrectly interpreted XML Label element content encoded on multiple lines as a multiline label. This should only be the case if the newline characters are part of a CDATA XML element, as illustrated in the How to define multiline labels SLD article.

Bug fixLuciadFusion

LCD-12173

The OGC Filter functions startAngle and endAngle incorrectly added a rotation of 90 degrees to the evaluated values. This could led to an incorrect icon rotation when used in combination with an SLD icon symbolizer.

New featureLuciadFusion

LCD-12148

A best effort has been made to add support for version 100 of OSGB for the


                           TLcdOSGBModelDecoder

, including support for

Binary brackets
DrawElementsUInt
Vec2Array
Vec3Array

ImprovementLuciadFusion

Moved some How to articles from the FAQ section to the How to section.

ImprovementLuciadFusion

LCD-12133

Support has been added for a new OGC Filter geometry function TLcdOGCVendorSpecificFunctions#VERTICES, which returns the points of a geometry. An example use case is the usage of the function in an SLD Geometry element to style the individual points of a polyline with an icon.

ImprovementLuciadFusion

LCD-12130

Support has been added for a new OGC Filter geometry function TLcdOGCVendorSpecificFunctions#INTERIOR_POINT, which returns a point that is interior the the geometry in case of a polygon, or sitting on its boundary otherwise. An example use case is the usage of the function in an SLD Geometry element, to style a point that is interior to the geometry with an icon or text symbolizer.

Bug fixLuciadFusion

LCD-12090

New featureLuciadFusion

The OGC3DTiles service now supports Draco mesh compression. It can be used when creating an OGC3DTiles Service for Binz, OSGB or any other mesh data type. It can be activated by choosing Draco from the mesh compression drop down.

New featureLuciadFusion

The TLcdOGC3DTilesModelEncoder now supports Draco mesh compression for mesh models, such as Binz and OSGB mesh data, or even existing OGC 3D Tiles datasets. You can use this new functionality through the API: setMeshCompression(ELcdOGC3DTilesMeshCompressionType). It is also available in LuciadFusion Studio when you create an OGC3DTiles service from the mesh data, and in the MeshUp en BinzConverter CLI samples.

New featureLuciadFusion

The TLcdRoundedPolyline and TLcdRoundedPolygon shapes have been added. These shapes allow you to create a rounded curve based on a set of control points. You can use these shapes to create rounded versions of ILcdPolyline and ILcdPolygon shapes. They can be visualized, created, and edited in ILcdGXYView and ILspView implementations.

The utility class TLcdShapeUtil was added to the API. This class contains utility method to created rounded lines.

TLcdShapeUtil.round(ILcdModelReference, ILcdPolyline, double): Use this method to created a TLcdRoundedPolyline.
TLcdShapeUtil.round(ILcdModelReference, ILcdPolygon, double): Use this method to created a TLcdRoundedPolygon.

TLcdSHPModelDecoder is now able to parse 'Infinity' and '-Infinity' as number properties.

Upgrade considerationLuciadFusion

The Oracle JDBC driver has been upgraded to version 19.12.0.0.

Upgrade considerationLuciadFusion

The SQLite library has been updated to version 3.36.0.

Upgrade considerationLuciadFusion

When a TLspRasterLayer is configured with the incrementalPainting flag set to false and contains multiple rasters, the layer is not updated until all tiles of all rasters are ready. Previously, the layer was updated whenever all tiles of any raster were ready.

Upgrade considerationLuciadFusion

For Java 17 support, the version of spring-ldap-core was updated from 2.3.2.RELEASE to 2.3.4.RELEASE.

Upgrade considerationLuciadFusion

The military grid implementations have moved to the defense symbology component. This results in the following package changes:

Old Class	New Class
com.luciad.text.TLcdMGRSFormat	com.luciad.text.mgrs.TLcdMGRSFormat
com.luciad.text.TLcdGARSPointFormat	com.luciad.text.gars.TLcdGARSFormat
com.luciad.view.map.TLcdMGRS*	com.luciad.view.map.mgrs.TLcdMGRS*
com.luciad.view.lightspeed.painter.grid.TLspMGRS*	com.luciad.view.lightspeed.painter.grid.mgrs.TLspMGRS*

Upgrade considerationLuciadFusion

The new ALspLayer map scale range property can clash with custom subclasses of ALspLayer. Additionally, to make this property work as expected for custom layers, it might be needed to listen to


                              TLspLayerStateEvent.Type#MAP_SCALE_RANGE_CHANGED

events or to override


                              ALspLayer#setMapScaleRange

Bug fixLuciadFusion

LCD-12000

Fixed the UnsupportedOperationException that occurred when querying a TLspLayer that contains view-spaced icons with a TLspIconStyle that uses orientation.

Bug fixLuciadFusion

LCD-11994

TLspRadarVideoLayerBuilder: a NegativeArraySizeException could sometimes occur during visualization of a radar.

ImprovementLuciadFusion

Upgrade considerationLuciadFusion

Bug fixLuciadFusion

LCD-11974

TLspIconStyle: the minimum pixel size was not applied correctly during printing.

Bug fixLuciadFusion

TLspGeorefGridOverlayLabelBuilder/


                           TLspMGRSGridOverlayLabelBuilder

LCD-11902

Solved a problem decoding GML files to a TLcdDataModel with generic enumerated types, such as String or Object.

New featureLuciadFusion

The WMTS service now supports KVP GetFeatureInfo requests. The GetFeatureInfo response is always in GeoJSON format. The GetFeatureInfo operation is listed in the operations metadata of the capabilities and the supported info format is listed for all layers.

New featureLuciadFusion

Support has been added for WMTS GetFeatureInfo requests. The class TLcdWMTSClient has a new method getFeatureInfo to perform the GetFeatureInfo request. This method expects a TLcdWMTSGetFeatureInfoContext parameter, which is a new class that specifies WMTS GetFeatureInfo settings. Additionally, a WMTS model's domain object now implements the new interface ILcdWMTSClientProvider to easily access a TLcdWMTSClient.

New featureLuciadFusion

LuciadLightspeed now has support for the vertical datum Normaal Amsterdams Peil (NAP), as well as the associated EPSG reference EPSG:7415. As a LuciadLightspeed user, this just works for you. You can open, visualize, and use data in this reference or referring to this vertical datum.

New featureLuciadFusion

You can now add custom service types to LuciadFusion. Adding a custom service type allows you to serve geospatial data managed in LuciadFusion Studio using a custom protocol. As a result, you gain access to a vast range of options for getting your data to clients. Custom service types can be used in addition to the built-in service types such as WMS, WFS, OGC 3D Tiles, etc.

Take a look at the com.luciad.fusion.platform.services.configuration package on how to get started with adding a custom service type. The classes in the com.luciad.fusion.platform.repository package contain the repositories necessary to access services, products, data from your custom service endpoint. There is also a detailed tutorial on how to add a custom service type to LuciadFusion.

New featureLuciadFusion

Maven POM files are now provided for LuciadFusion releases. There are Maven POM files available for each product tier (Essential, Advanced, Pro), which depend on all non-optional components of their respective tiers. In addition there are maven POM files for each optional component for each tier.

The product tier POM dependencies are:

Group ID	Artifact ID
com.luciad	luciadfusion_essential
com.luciad	luciadfusion_advanced
com.luciad	luciadfusion_pro

The optional component POM dependencies are:

Group ID	Artifact ID
com.luciad	luciadfusion_database_connectors
com.luciad	luciadfusion_google_earth_enterprise
com.luciad	luciadfusion_graph_and_routing_engine
com.luciad	luciadfusion_terrain_analysis_engine
com.luciad	luciadfusion_weather_environment_standards
com.luciad	luciadfusion_aviation_standards
com.luciad	luciadfusion_infrastructure_standards
com.luciad	luciadfusion_maritime_standards
com.luciad	luciadfusion_defense_standards
com.luciad	luciadfusion_radar_connectors
com.luciad	luciadfusion_s63
com.luciad	luciadfusion_defense_symbology

New featureLuciadFusion

It is now possible to print the contents of a TLspFXView at high resolution. The newly introduced print() method can be used to generate a print-quality image. The sample class samples.lightspeed.javafx.common.printing.PrintPreview demonstrates how to use this method together with the JavaFX printing API. It also implements a preview of the print result and supports multi-page printing. The print preview can be accessed via a new toolbar button which is available in all JavaFX samples.

New featureLuciadFusion

LuciadFusion Studio now includes an HSPC service type. This service can be used to serve Hexagon Smart Point Cloud (HSPC) data.

New featureLuciadFusion

JavaFX UI components that can be used for map navigation and altering the altitude exaggeration of a 3D view have been added to the API.

TLspFXCompassNavigationControl: rotate and pan the map.
TLspFXPanNavigationControl: pan the map.
TLspFXZoomNavigationControl: change the zoom level of the map.
TLspFXAltitudeExaggerationControl: change the altitude exaggeration factor of a 3D view.

ImprovementLuciadFusion

The TLcdRD1918DutchGridReference model reference class has been deprecated, because it uses outdated hardcoded parameters. Where possible, using EPSG or WKT parsing is encouraged, for example:
new TLcdEPSGReferenceParser().parseModelReference("EPSG:28992").

ImprovementLuciadFusion

LCD-11312

TLcdExpressionFactory: a log expression has been added which returns the natural logarithm of its parameter.

ImprovementLuciadFusion

LCD-5200

LuciadLightspeed now has more extensive support for EPSG and WKT encoded references that use a geoid.

ImprovementLuciadFusion

The service resource in the LuciadFusion Studio REST api now has a new property service.endpointUrl. This property contains a url that clients can use to connect to the service.

ImprovementLuciadFusion

LCD-5095, LCD-2134, LCD-6783

LuciadLightspeed now has improved support for working with map scales. The new TLcdMapScale class now allows working with a physical, unitless map scale ratios such as "1:100.000". You can directly set and retrieve them on any ILcdGXYView. For Lightspeed views, you can retrieve the scale from ALspViewXYZWorldTransformation and set it using TLspViewNavigationUtil. TLcdMapScale#createScaleRange is also supported in several places to specify unitless map scale ranges. For more information, refer to the Working with map scales article.

ImprovementLuciadFusion

The layer control UI component used in the JavaFX samples now has the following additional features:

Layers can be moved in the tree with drag and drop or buttons.
A progress indicator now indicates when a layer is busy.
Buttons have been added to toggle selectable, editable and labeled.

The FXLayerControl can be reused in your own application.

ImprovementLuciadFusion

LF-1378

Crawl jobs can now be configured to recrawl all files, even it seems like they haven't changed since the last successful crawl. This can be enabled by setting the crawl job property forceRecrawlFiles to

true

Upgrade considerationLuciadFusion

3D data (point cloud or mesh) can no longer be published in a WMS or WMTS service in LuciadFusion. The 3D data was not visible when published in either WMS or WMTS. Please use an OGC 3D Tiles service to publish 3D data.

Upgrade considerationLuciadFusion

The Maven POM files provided with a LuciadLightspeed release have been renamed to follow the Maven artifactId naming conventions.

If you depend on any Lightspeed component in your project's POM file, they will need to be renamed as follows.

Group ID	Old Artifact ID	New Artifact ID
com.luciad	LuciadLightspeed	luciadlightspeed
com.luciad	Advanced_GIS_Engine	luciadlightspeed_advanced_gis_engine
com.luciad	Advanced_Raster_Connectors	luciadlightspeed_advanced_raster_connectors
com.luciad	Aviation_Standards	luciadlightspeed_aviation_standards
com.luciad	Database_Connectors	luciadlightspeed_database_connectors
com.luciad	Defense_Standards	luciadlightspeed_defense_standards
com.luciad	Defense_Symbology	luciadlightspeed_defense_symbology
com.luciad	Google_Earth_Enterprise	luciadlightspeed_google_earth_enterprise
com.luciad	Graph_and_Routing_Engine	luciadlightspeed_graph_and_routing_engine
com.luciad	Infrastructure_Standards	luciadlightspeed_infrastructure_standards
com.luciad	Maritime_Standards	luciadlightspeed_maritime_standards
com.luciad	Radar_Connectors	luciadlightspeed_radar_connectors
com.luciad	Real_time_Engine	luciadlightspeed_real_time_engine
com.luciad	S_63	luciadlightspeed_s63
com.luciad	Terrain_Analysis_Engine	luciadlightspeed_terrain_analysis_engine
com.luciad	Tiling_Engine	luciadlightspeed_tiling_engine
com.luciad	Weather_Environment_Standards	luciadlightspeed_weather_environment_standards

In addition, POM files are now available for each product tier (Essential, Advanced and Pro). These POM files depend on all non-optional modules available for their respective product tiers.

The new product tier POM files are:

Group ID	Artifact ID
com.luciad	luciadlightspeed_essential
com.luciad	luciadlightspeed_advanced
com.luciad	luciadlightspeed_pro

Upgrade considerationLuciadFusion

Some Spring Boot Cloud dependencies have been upgraded from the Milestone version (2.1.0.M1) to the release version (2.1.0.RELEASE). Because of this change we needed to upgrade some of the transitive dependencies of the Spring Boot Cloud dependencies. Here is an overview of the dependency changes:

Group ID	Artifact ID	Old Version	New Version
org.springframework.cloud	spring-cloud-netflix-archaius	2.1.0.M1	2.1.0.RELEASE
org.springframework.cloud	spring-cloud-starter-netflix-hystrix	2.1.0.M1	2.1.0.RELEASE
org.springframework.cloud	spring-cloud-netflix-eureka-server	2.1.0.M1	2.1.0.RELEASE
org.springframework.cloud	spring-cloud-netflix-zuul	2.1.0.M1	2.1.0.RELEASE
org.springframework.cloud	spring-cloud-starter	2.1.0.M1	2.1.0.RELEASE
org.springframework.cloud	spring-cloud-starter-netflix-zuul	2.1.0.M1	2.1.0.RELEASE
org.springframework.cloud	spring-cloud-netflix-hystrix	N/A	2.1.0.RELEASE
org.springframework.cloud	spring-cloud-context	2.1.0.M1	2.1.0.RELEASE
org.springframework.cloud	spring-cloud-netflix-ribbon	2.1.0.M1	2.1.0.RELEASE
org.springframework.cloud	spring-cloud-commons	2.1.0.M1	2.1.0.RELEASE
org.springframework.cloud	spring-cloud-starter-netflix-ribbon	2.1.0.M1	2.1.0.RELEASE
org.springframework.cloud	spring-cloud-netflix-eureka-client	2.1.0.M1	2.1.0.RELEASE
org.springframework.boot	spring-boot-starter-actuator	2.1.0.RELEASE	2.1.2.RELEASE
org.springframework.boot	spring-boot-actuator-autoconfigure	2.1.0.RELEASE	2.1.2.RELEASE
org.springframework.boot	spring-boot-starter	2.1.0.RELEASE	2.1.2.RELEASE
org.springframework.boot	spring-boot-autoconfigure	2.1.0.RELEASE	2.1.2.RELEASE
org.springframework.boot	spring-boot-starter-web	2.1.0.RELEASE	2.1.2.RELEASE
org.springframework.boot	spring-boot-starter-aop	2.1.0.RELEASE	2.1.2.RELEASE
org.springframework.boot	spring-boot-starter-freemarker	2.1.0.RELEASE	2.1.2.RELEASE
org.springframework.boot	spring-boot-starter-json	2.1.0.RELEASE	2.1.2.RELEASE
org.springframework	spring-boot-starter-jdbc	N/A	2.1.2.RELEASE
org.springframework.boot	spring-boot	2.1.0.RELEASE	2.1.2.RELEASE
org.springframework.boot	spring-boot-actuator	2.1.0.RELEASE	2.1.2.RELEASE
org.springframework.boot	spring-boot-starter-logging	2.1.0.RELEASE	2.1.2.RELEASE
org.springframework	spring-context-support	5.1.2.RELEASE	5.1.4.RELEASE
org.springframework	spring-webmvc	5.1.2.RELEASE	5.1.4.RELEASE
org.springframework	spring-aop	5.1.2.RELEASE	5.1.4.RELEASE
org.springframework	spring-beans	5.1.2.RELEASE	5.1.4.RELEASE
org.springframework	spring-context	5.1.2.RELEASE	5.1.4.RELEASE
org.springframework	spring-core	5.1.2.RELEASE	5.1.4.RELEASE
org.springframework	spring-expression	5.1.2.RELEASE	5.1.4.RELEASE
org.springframework	spring-web	5.1.2.RELEASE	5.1.4.RELEASE
org.springframework	spring-tx	5.1.2.RELEASE	5.1.4.RELEASE
org.springframework	spring-jdbc	5.1.2.RELEASE	5.1.4.RELEASE
org.hibernate.validator	hibernate-validator	6.0.13.Final	6.0.14.Final
com.netflix.eureka	eureka-client	1.9.3	1.9.8
com.netflix.eureka	eureka-core	1.9.3	1.9.8
com.netflix.hystrix	chystrix-core	1.5.12	1.5.18
com.netflix.hystrix	hystrix-javanica	1.5.12	1.5.18
com.netflix.hystrix	hystrix-metrics-event-stream	1.5.12	1.5.18
com.netflix.hystrix	hystrix-serialization	1.5.12	1.5.18
com.netflix.ribbon	ribbon-transport	2.2.5	2.3.0
com.netflix.ribbon	ribbon	2.2.5	2.3.0
com.netflix.ribbon	ribbon-core	2.2.5	2.3.0
com.netflix.ribbon	ribbon-httpclient	2.2.5	2.3.0
com.netflix.ribbon	ribbon-loadbalancer	2.2.5	2.3.0
com.fasterxml.jackson.dataformat	jackson-dataformat-xml	2.9.7	2.9.8
com.fasterxml.jackson.dataformat	jackson-dataformat-cbor	2.9.7	2.9.8
com.fasterxml.jackson.datatype	jackson-dataformat-jsr310	2.9.7	2.9.8
com.fasterxml.jackson.datatype	jackson-dataformat-jdk8	2.9.7	2.9.8
com.fasterxml.jackson.module	jackson-module-jaxb-annotations	2.9.7	2.9.8
com.fasterxml.jackson.module	jackson-module-afterburner	2.9.7	2.9.8
com.fasterxml.jackson.module	jackson-module-parameter-names	2.9.7	2.9.8
io.micrometer	micrometer-core	2.9.7	2.9.8
org.aspectj	aspectjweaver	1.9.1	1.9.2

Upgrade considerationLuciadFusion

Due to changes in the dependencies of LuciadFusion we have upgraded our com.fasterxml dependencies in LuciadLightspeed to ensure we depend on the same version across all products.

Here is an overview of the dependency changes:

Group ID	Artifact ID	Old Version	New Version
com.fasterxml.jackson.core	jackson-core	2.9.7	2.9.8
com.fasterxml.jackson.core	jackson-databind	2.9.7	2.9.8
com.fasterxml.jackson.core	jackson-annotations	2.9.5	2.9.8

Bug fixLuciadFusion

an incorrect prime meridian shift
a prime meridian shift that was applied twice
incorrect projection parameters

ImprovementLuciadFusion

LCD-11769

TLcdEPSGReferenceParser now uses more precise parameters to transform from S-JTSK to WGS 84. This affects to following codes:

EPSG:2065
EPSG:4156
EPSG:4818
EPSG:5221
EPSG:5513
EPSG:5514

Bug fixLuciadFusion

LCD-11777

Fixed a regression caused by SLD enhancement LCD-11733, resulting in the behavior that an SLD PerpendicularOffset was no longer taken into account for basic line styles in a Lightspeed view.

Bug fixLuciadFusion

LCD-11787

ImprovementLuciadFusion

LCD-11706

Improved the visualization of TLcdLonLatBuffer and TLcdLonLatHeightBuffer on GXY views (using TLcdGXYGeoBufferPainter) and 2D Lightspeed views.

Bug fixLuciadFusion

LCD-11725

TLcdMercator and TLcdPseudoMercator: Fixed an issue where points on the date line were transformed incorrectly.

Bug fixLuciadFusion

LCD-11703

TLspLabelPainter and TLspEditController: fix a few small memory leaks. When removing a domain object from a model, that object could sometimes not be garbage collected.

Bug fixLuciadFusion

Fixed an issue that prevented users from creating more than one instance of TLspExternalView.

Bug fixLuciadFusion

Bug fixLuciadFusion

LCD-11549

Fixed an issue that prevented TLcdDataSource objects from being decoded by the


                           TLcdGeoPackageModelDecoder

.

Bug fixLuciadFusion

LCD-11514

TLspIconStyle: when using multiple TLspIconStyles, only one icon was taken into account for selection. Thus, an object could only be selected by one of the icons it was styled with.

Bug fixLuciadFusion

LF-2031

Added missing 'Panorama' category to the possible Product types. Additionally, empty products, which were previously categorized as 'Unknown', will now be categorized as 'Empty'. In existing products, these changes will only be apparent upon an update of their product contents.

Bug fixLuciadFusion

LCD-11534

Fixed an issue related to the previous SLD fix LCD-11421, which caused that the SLD graphic size setting was not always taken into account for world-sized SVG icons.

Bug fixLuciadFusion

LF-2034

Fixed an issue in the LuciadFusion Studio CSW server causing a CSW dc:date query to fail.

Bug fixLuciadFusion

TLcdLonLatGeoBuffer#setJoinStyle changed the end cap style. This has been fixed.

Upgrade considerationLuciadFusion

LF-1964

The http method is now included when http requests to LuciadFusion are logged. Important to note is that the fusion.logback.xml has been updated to use a different logger for requests. Make sure you use the updated logback when upgrading LuciadFusion.

New featureLuciadFusion

The LuciadFusion documentation now contains a dedicated section on creating a configuration with multiple servers in a failover and/or load balancing scenario.

POST /api/data: allows Data to be added directly to Studio.
POST /api/styles: allows Styles to be added directly to Studio.
PUT /api/data/{id}/refresh: allows Data to be updated based on the changes made to the source file(s).
PUT /api/styles/{id}/refresh: allows Styles to be updated based on the changes made to the source file.
DELETE /api/data/{id}: allows Data to be removed from Studio.
DELETE /api/styles/{id}: allows Styles to be removed from Studio.

You can try out these new operations in the API Console, available at /api/console of a running Fusion development server. You can read in more detail about all the operations in the Developer's guide, available at /api/documentation.

Users will notice that adding certain Data directly to LuciadFusion Studio will be much quicker than crawling if the Data consists of many individual files (e.g. OGC 3D Tiles). This is because adding Data directly to LuciadFusion does not require evaluating all individual files.

New featureLuciadFusion

TLcdGeoPackageModelEncoder and TLcdGeoPackageModelDecoder now support the GeoPackage 1.1, 1.2.1, and the 1.3.0 specifications.

New featureLuciadFusion

You can now decode and visualize MBTiles files with image tiles in Lightspeed and GXY views, and LuciadFusion WMS/WMTS services.

For more details, see:

The MBTiles entry in the Data Formats documentation section
The TLcdMBTilesModelDecoder reference documentation

ImprovementLuciadFusion

LCD-8112

Improved the way TLcdGeoJsonModelDecoder automatically constructs a TLcdDataModel. It now detects nested properties objects and creates separate data types for them as well.

ImprovementLuciadFusion

To simplify the sample code, some exotic GXY touch samples have been removed (multi-edit, multi-view, multi-user, gestures).

ImprovementLuciadFusion

TLcdGXYStampLabelPainter: deprecated the setGXYInteractiveLabelProvider method to avoid confusion with the TLcdGXYInteractiveLabelsController.

ImprovementLuciadFusion

LCD-10513

Improved compatibility with JDK 9 and higher by removing illegal reflective access calls from the API and sample code.

ImprovementLuciadFusion

LCD-11207

ILcdGXYController now has a getLayered method to add temporary layers to the view. When the controller is active, the layers are painted and the view's label placer takes those layers into account. The TLcdAdvancedMapRulerController now makes use of this if it's not configured to add a measurement layer to the view.

Upgrade considerationLuciadFusion

All date-time properties used in the LuciadFusion Studio REST API now conform to RFC 3339. This means that a date-time property will now include a time-offset. The time-offset will be based on the time zone of the machine that LuciadFusion Studio runs on. If e.g the creationTime of a product was previously 2020-01-01T00:00:00.000 and LuciadFusion Studio is running on a machine in the CET timezone, then the creationTime returned by the REST API is now 2020-01-01T00:00:00.000+01:00. A creationTime that was previously 2020-08-01T00:00:00.000 will now return


                           2020-08-01T00:00:00.000+02:00

on that same machine.

Upgrade considerationLuciadFusion

LCD-11352

The Jaxen and Batik libraries have been upgraded to version 1.2.0 and 1.11, respectively. This improves compatibility with JDK 11.

Upgrade considerationLuciadFusion

The optional ArcSDE component has been removed from the Tiling Engine module as it has been discontinued by Esri as of ArcGSI 10.3. Consequently, ArcSDE data sources can no longer be preprocessed using Tiling Engine.

Upgrade considerationLuciadFusion

The optional ArcSDE component (com.luciad.format.arcsde) has been removed from the product after being deprecated since the 2016.0 release.

This component provided support for visualize data from an ESRI ArcSDE. However ArcSDE has been discontinued by Esri as of ArcGIS 10.3 in 2015, and you cannot buy it anymore.

As we're not aware of any customers using ArcSDE anymore, we removed it from all our products including LuciadFusion and Lucy. Consult the release notes of those products for more details.

Upgrade considerationLuciadFusion


                           TLcdSHPPolygonZ

.

ImprovementLuciadFusion

LCD-11438

It is now possible to define a lon lat grid using a different geodetic datum than WGS84 in a Lightspeed view. See TLspLonLatGridLayerBuilder#createModel.

Bug fixLuciadFusion

LCD-11452

When adding a grid layer with a non default ALspLayerStyle to a Lightspeed view, it was not painted.

Bug fixLuciadFusion

LCD-11436

Fixed an issue in the OGC 3DTiles encoding where textures would be encoded multiple times, resulting in an unnecessary large size of the result files.

Upgrade considerationLuciadFusion

LCD-11443

When evaluating an OGC filter through the TLcdOGCFilterEvaluator, the ILcdPropertyRetrieverProvider will now cache and re-use the created ILcdPropertyRetriever instances which results in improved performance.

Since the introduction of LCD-11278 the ILcdPropertyRetrieverProvider is queried more often. By introducing caching, there is no performance penalty anymore.

This is achieved by decorating the property retriever provider which is passed in the constructor of the TLcdOGCFilterContext. The result is that the corresponding getter returns an instance which isn't the same as the one which is passed into the constructor.

Upgrade considerationLuciadFusion

ImprovementLuciadFusion

ImprovementLuciadFusion

LCD-11413

TLcdCartesianReference now implements the loadProperties and writePropertiesSFCT methods. This allows this reference to be written to file using TLcdModelReferenceEncoder, and to be read back using


                           TLcdModelReferenceDecoder

ImprovementLuciadFusion

LF-1979

Bug fixLuciadFusion

LCD-11348

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.

Bug fixLuciadFusion

LCD-11350

Fixed an issue where the default style of a data source would not be recognized if the data was crawled before the style.

Bug fixLuciadFusion

TLcdCSVModelDecoder: fixed the incorrect parsing of days in DateTime fields.

ImprovementLuciadFusion

ImprovementLuciadFusion

LF-1947

Upgrade considerationLuciadFusion

LCD-11278

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.

New featureLuciadFusion

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.

ImprovementLuciadFusion

TLcdGXYShapePainter: considerably improved anti-aliased appearance of shapes that are discretized into many small line segments.

ImprovementLuciadFusion

LCD-10079

GXY label placement can now be configured at the layer level. This means you can configure label visualization as well as label placement in your layer factory. Refer to TLcdGXYLayer#setGXYLabelingAlgorithmProvider and its sample code usages for more information.

ImprovementLuciadFusion

Support for the Krovak projection was added, see TLcdKrovak. TLcdWKTReferenceParser and TLcdEPSGReferenceParser have been modified to support this new projection. For the latter, the following EPSG codes that use the Krovak projection are now supported:

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

Bug fixLuciadFusion

LCD-11244

Fixed a potential deadlock when loading BINZ data in a TLspFXView.

Upgrade considerationLuciadFusion

You now need to manually initialize touch support for Swing applications by calling TLcdTouchDevice#getInstance() at application startup. Any touch enabled application that checks the touch device status automatically fulfills this requirement. Additionally, the TLcdAWTEventDispatcher no longer dispatches touch events.

Upgrade considerationLuciadFusion

TLcdTouchEvent#getSource and TLcdAWTEvent#getSource: the return type has been changed from Component to Object. This allows using the Lightspeed touch controllers in a Lightspeed JavaFX view. If you were using those methods in your application, you may need to cast the result to a Component.

Upgrade considerationLuciadFusion

The data category in the model metadata of OBJ models produced by TLcdOBJModelDecoder has been changed from VECTOR to MESH.

Upgrade considerationLuciadFusion

TLspExternalView is now deprecated. Integration of LuciadLightspeed in C++ applications is no longer actively supported as of V2020.0. Please contact your account manager or support.luciad.gsp@hexagon.com to discuss possible alternatives.

Upgrade considerationLuciadFusion

To improve the separation between AWT and JavaFX code paths, the return type of TLspEditHandleResult#getProcessedEvent() was changed from EventObject to AWTEvent. In practice, this change should have no impact on existing applications, since

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

Upgrade considerationLuciadFusion

The GXY view implementations now have the following useful options enabled by default:

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

ImprovementLuciadFusion

The EPSG resources are updated to EPSG database v9.8.6.

ImprovementLuciadFusion

LF-1926

A new REST API call /api/services/types/validate-products is available which allows to check which services can be created for the given products.

ImprovementLuciadFusion

LF-1923

LuciadFusion system administrators can now configure LuciadFusion to use Oracle 19c database for the catalog (see config/application-fusion.development.yml for details).

ImprovementLuciadFusion

LF-1922

Added the ability to modify the set of CRS codes exposed in LuciadFusions' WMS responses. See the following new properties in config/fusion.common.yml for more details.

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

Bug fixLuciadFusion

LCD-11248

ImprovementLuciadFusion

TLcdGXYCompositeController now also works with ILcdAWTEventListener delegates.

ImprovementLuciadFusion

LCD-10958

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.

Additionally, support has been added for 4 new functions in TLcdOGCVendorSpecificFunctions that operate on a geometry defined by a given property name:

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.

ImprovementLuciadFusion

LCD-10559

The ILcdPointList2 interface added no extra methods compared to the


                           ILcdPointList

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.

Bug fixLuciadFusion

LCD-10618, LCD-873, LCD-10797

Fixed a bug where TLcdLonLatEllipse#getBounds could return undersized bounds that would not contain the entire ellipse. Now the bounds calculation is more accurate and consistent with TLcdLonLatArc.

Bug fixLuciadFusion

LCD-10466

TLcdInputStreamFactory: can now create input streams for zipped data, independent of whether the data uses zlib/gzip compatible compression or not.

Bug fixLuciadFusion

The SLD decoder now ignores leading newline and/or leading spaces when decoding a text symbolizer label element.

Bug fixLuciadFusion

LCD-10991

The SLD label rotation implementation for Lightspeed views did not properly take into account a possible label offset introduced by a an SLD label anchor point and/or label displacement property.

Upgrade considerationLuciadFusion

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.

Upgrade considerationLuciadFusion

LCD-10695

The Java version handling in TLcdSystemPropertiesUtil has been improved with a new method isJavaVersion(JavaVersion). Java version check methods below the minimum Java requirement have been removed.

Upgrade considerationLuciadFusion

TLcdOGCFilterFactory: the public constructor has been removed. This class only contains static factory methods and was never designed to be instantiated. To make the intended usage of this class crystal clear, the public constructor has been removed.

Upgrade considerationLuciadFusion

LCD-7667

A new version of the JAI ImageIO library is used.

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

      @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);
      }

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

Bug fixLuciadFusion

The WCS client API now automatically uses sensible settings for TLcdWCSProxy's tiled multilevel raster structure, based on the coverage bounds. This helps to efficiently query WCS raster data and avoids manual configuration of the raster structure settings (tile width, tile height, rows, columns ...).

ImprovementLuciadFusion

TLcdGXYSurfacePainter now supports creation of a surface, provided that it has an exterior ring and no inner rings.

Bug fixLuciadFusion

LF-1790

Removed -XX+UseParNewGC java command line parameter from the Fusion deployment startup scripts, which prevented the server from starting when running Java 11.

Bug fixLuciadFusion

LF-1791

Fixed an issue that prevented data from being added to an existing product in LuciadFusion Studio.

Bug fixLuciadFusion

LCD-10689

When running LuciadLightspeed on a 32-bit JVM, functionality that depends on OpenCL could cause exceptions, e.g. when using an ALcdImageOperator.

Bug fixLuciadFusion

LCD-10701

Improved rendering of SLD icons on HiDPI displays.

Bug fixLuciadFusion

TLcdIconFactory.LINK_DECO_ICON: made the 16x16 icon consistent with the other icon sizes.

Bug fixLuciadFusion

LCD-10688

TLspIconStyle: icons did not adapt correctly when switching between a HiDPI and non-HiDPI screen. As a result icons would appear to large on the non-HiDPI screen or to small when switching to a HiDPI screen.

Bug fixLuciadFusion

LCD-10687

TLcdImageIcon: the icon would not be painted with the correct resolution when switching between a HiDPI and a non-HiDPI display.

Bug fixLuciadFusion

LCD-10686

TLspSLDStyler configured an incorrect labeling algorithm for line and polygon symbolizers. This would result in polygons with labels on the outline of the polygon instead of labels inside the polygon.

Bug fixLuciadFusion

LCD-10730

TLspSelectController was no longer able to select objects with the rectangle selection feature.

ImprovementLuciadFusion

The lightspeed.imageprojection sample has been modified to show a sample video draped onto the terrain instead of a single image icon.

ImprovementLuciadFusion

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.

ImprovementLuciadFusion

LCD-10410

TLcdWFSDataSource.Builder now allows to set a QName as feature type name, next to the existing capability to set a String. This better aligns with the OGC WFS specification, which focuses on the use of qualified names for feature types.

ImprovementLuciadFusion

LCD-3558

Improved the performance of adding and removing (many) layers to a view.

ImprovementLuciadFusion

ILcdPointList now implements all methods of ILcdPointList2. As such, there is no need to use the latter anymore.

ImprovementLuciadFusion

The WFS client model decoder class TLcdWFSModelDecoderDecorator can now be instantiated with a custom ILcdOWSTransport. Example uses cases include the configuration of authentication credentials or request / response interception.

ImprovementLuciadFusion

Visualizing Bing Maps data has been simplified:

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

Adding the Bing Maps logo and copyright information on your view is also simplified:

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

ImprovementLuciadFusion

You no longer have to create and set up a TLcdGXYAsynchronousPaintQueueManager to use asynchronous layer wrappers in an ILcdGXYView.

ImprovementLuciadFusion

Upgrade considerationLuciadFusion

The lib directory now contains a newer version of the httpmime jar (httpmime-4.5.3.jar -> httpmime-4.5.6.jar). The lib directory now contains a newer version of the httpclient-cache jar (httpclient-cache-4.5.3.jar -> httpclient-cache-4.5.6.jar).

Upgrade considerationLuciadFusion

The lib directory now contains a newer version of the QueryDsl jars (querydsl-*-4.1.3.jar -> querydsl-*-4.2.1.lcd-2.jar). The lib directory now contains a newer version of the Liquibase jar (liquibase-core-3.5.3.jar -> liquibase-core-3.6.3.jar).

Upgrade considerationLuciadFusion

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.

Upgrade considerationLuciadFusion

The method TLcdWFSDataSource#getFeatureTypeName() now returns a QName instead of a String, to better reflect the focus of the OGC WFS specification on the use of qualified names for feature type names. Existing implementations can be updated by simply relying on the toString method to convert the QName to a String.

Upgrade considerationLuciadFusion

TLcdIconFactory.DRAW_VARIABLE_BUFFER_ICON has been removed since it was duplicating the TLcdIconFactory.DRAW_VARIABLE_WIDTH_BUFFER_ICON.

Upgrade considerationLuciadFusion

TLcdGXYSelectController2 now only draws a multi-select rectangle when holding down the shift key. This makes it trivial to add pan behavior by appending TLcdGXYNavigateController. To revert the previous behavior, call selectController.setMultiSelectModifierKey(0);.

Upgrade considerationLuciadFusion

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.

Upgrade considerationLuciadFusion

LCD-10486

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.

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

Upgrade considerationLuciadFusion

LCD-9310, LCD-9763

A new version of the JAI ImageIO library is used.

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.

Upgrade considerationLuciadFusion

All public classes that depended on the legacy 3D component were removed from the API.

Upgrade considerationLuciadFusion

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.

Upgrade considerationLuciadFusion

LCD-10581

The return types of some of the methods of the following classes were narrowed from Enumeration to ILcdAutoCloseableEnumeration.

ILcdDatabaseDecoder
ILcdDatabaseDecoder2
TLcdDatabaseModel
TLcdDatabaseReadOnlyModel

TLspShapeLayerBuilder: when culling was disabled and a TLcdModelQueryConfiguration was configured, the objects on the map would not be updated when the view scale changed.

Bug fixLuciadFusion

LCD-9051

The TLcdGeoTIFFModelDecoder could result in certain cases in throwing an IllegalArgumentException. This was the case when

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

ImprovementLuciadFusion

LCD-10201

A number of improvements have been implemented related to the WFS server's interoperability with 3rd party WFS client solutions:

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.

Bug fixLuciadFusion

LF-1685

Fusion Studio now uses a secure WebSocket connection (wss://) between browser and backend, if it is accessed over HTTPS. This avoids issues where the browser would disallow the WebSocket to be established, due to the mixed content security policy.

Bug fixLuciadFusion

The output format encoding in the DescribeFeatureType requests in XML Schema location URLs could contain an unexpected + character.

Bug fixLuciadFusion

LF-1686

Fixed an issue where a crawl job for the uploads directory was not created and therefore the files under that directory weren't recrawled unless the user uploaded new files. This problem occurred when the upload directory was not empty and LuciadFusion Studio started with a fresh database.

Bug fixLuciadFusion

LCD-10378

Fixed issue with TLspFixedInPathLabelLocationProvider, where an incorrect locations was provided for composite curves.

Upgrade considerationLuciadFusion

The Java Expression Language dependency has been upgraded from version 2.2 to 3.0. Consequently, an application server or servlet container with support for EL 3.0 API or higher is now required for deployment of the LuciadFusion Platform, for instance, Tomcat 8 or higher.

ImprovementLuciadFusion

LCD-10414

TLcdServiceLoader: improved compatibility with certain OSGi implementations.

ImprovementLuciadFusion

LCD-10156

The border factor property of raster layers allows you to configure processing some additional data outside of the view. This reduces the popping effect while panning or zooming. TLspRasterLayerBuilder and TLspRasterLayer now allow you to configure to include texture loading in this additional processing. By default, it is not included. Including it increases the memory and cpu usage, but will often give faster updates for small pan and zoom operations.

Bug fixLuciadFusion

Bug fixLuciadFusion

LCD-10388

Fixed an issue when interactively editing geodetic ellipses (TLcdLonLatEllipse) on a Lightspeed view using the regular TLspEllipseEditor. When dragging a handle on one of the axes beyond XYZ, the ellipse was flipped: the major axis reversed and rotated by 180 degrees. This has no visual result on the ellipse, but was unexpected.

Bug fixLuciadFusion

LCD-10406

Fixed a regression related to the decoding of SLD ParameterValue elements, introduced by enhancement LCD-10387.

ImprovementLuciadFusion

LCD-10343

The WFS client can now handle WFS feature types for which the mandatory geographical reference information is missing in the WFS server's capabilities.

ImprovementLuciadFusion

LCD-10387

The SLD label painting pipeline in GXY / Lightspeed views now support the use of multiline labels, by using a CDATA element inside the label content that specifies a new line as follows: <![CDATA[ ]]>

ImprovementLuciadFusion


                           /datastore/path/uploads

already exists" message when this occurred.

Bug fixLuciadFusion

LF-1647

Fixed bug where the name of a style would default to the file path instead of the file name of the sld file.

Bug fixLuciadFusion

LF-1644

Fixed an issue where the preprocessing path changing dialog in the LuciadFusion Studio web front end would show incorrect descriptions.

Bug fixLuciadFusion

TLcdISO8601DateFormat did not correctly handle parsing errors according to the contract defined in java.text.Format. In case of parsing errors:

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

Bug fixLuciadFusion

LCD-10321

ImprovementLuciadFusion

LCD-10047

The OGC Web Client classes TLcdWFSDataSource, TLcdWMSDataSource, TLcdWMTSDataSource and TLcdWCSDataSource have improved support for parameterized URIs:

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.

ImprovementLuciadFusion

Added compatibility for OracleJDK/OpenJDK 11. Warnings might still appear at runtime when using those JDK but can be avoided using the

--add-opens

LCD-10078

An extra constructor has been added to the class TLcdWCSCoverageModelDecoder to allow configuring a custom ILcdOWSHttpTransport instance. This interface is used by the OGC client implementations to perform request / response handling.

ImprovementLuciadFusion

LCD-10054

TLspRasterLayerBuilder and TLspRasterLayer now allow configuring whether the layer should be repainted as soon as a tile is available. If the incremental painting property is set to false, the layer is not updated until all tiles are ready.

ImprovementLuciadFusion

LuciadFusion Studio now supports the localization of the UI text, and allows you to add translations to a new language. Studio determines which language to display based on the language setting in the web browser. if it cannot find a translation match, English is used by default. For more information, please consult the LuciadFusion Platform developer guide.

ImprovementLuciadFusion

The LuciadFusion Studio web front end allows the user to change the name (which is also used as the unique identifier) of a product inside a service. This allows the user to replace a product in a service while keeping the URL to that product intact. For example, when a service serves weather data which gets updated regularly, the user can replace the outdated weather data with fresh data without the need to update the URL used in the client.

ImprovementLuciadFusion

LF-1332

The LuciadFusion Platform developer, deployment and migration guides have been merged into a single guide. The content of the guides has also been restructured.

ImprovementLuciadFusion

LCD-9017

The abstract model implementation ALcdModel has a method setModelDisposer to register a function to be called on ILcdModel#dispose(). This avoids the need to override the method ILcdModel#dispose() when using a model implementation based on ALcdModel.

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.

ImprovementLuciadFusion

LCD-2075

TLcdLayerTree now by default hides its root node. If you don't want this, call TLcdLayerTree#setRootVisible(true).

ImprovementLuciadFusion

LCD-9286

Bug fixLuciadFusion

LCD-10277

Fixed an issue when displaying lines with 3D information from LuciadFusion vector coverages. In some cases, their Z information got lost.

Bug fixLuciadFusion

LCD-10288

TLcdClusteringTransformer: When reused after another transformer was configured on the TLcdTransformingModel, model changes that occurred when it was not in use, were not visualized anymore (e.g. added elements were missing).

Upgrade considerationLuciadFusion

A uniqueness constraint was added to the public id columns of the tables that contain Data and Services in the database (imported_data and geo_service). The REST API uses the public id as the identifier for Data and Services and requires this value to be unique. Ensure that all the public ids of Data and Services are unique before upgrading or it will fail.

Upgrade considerationLuciadFusion

The addition of the REST API requires that the 'pgcrypto' extension need to be enabled when using a PostgreSQL database. This extension allows LuciadFusion to create unique identifiers (of type UUID) for the domain objects that are obtainable through the REST API.

Upgrade considerationLuciadFusion

Added a dependency to the LWJGL library version 3.2.0, used to retrieve window handles.

Upgrade considerationLuciadFusion

The JOGL, JOCL, and GlueGen libraries have been updated to version 2.3.2+3-lcd. This is the same as the official 2.3.2 version of JOGL, with the exception that it contains a fix to prevent a JVM crash when closing an application on the Mac OS X platform when using OpenJDK 11.

Upgrade considerationLuciadFusion

For Java 11 support, Spring Boot and its dependencies have been upgraded. The libraries that have been upgraded are as follows:

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)

The following properties were updated along with these libraries.

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

Upgrade considerationLuciadFusion

To document the JSON REST API and provide an interactive console (see LuciadFusion Studio REST API Developer’s Guide - Interactive API documentation) several Swagger related libraries were added. The Guava library has been updated to the version required by these new libraries. The following libraries have been added:

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

The following libraries were updated:

Guava (version 20.0)

Upgrade considerationLuciadFusion

A new version of the jai_imageio library is used. It no longer depends on classes that are not available in certain Java versions.

Upgrade considerationLuciadFusion

Some API constructs in Luciad's abstract OpenGL binding have been deprecated:

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.

Bug fixLuciadFusion

LCD-10212, LCD-10213, LF-1626

Fixed an issue where the WMTS server could produce:

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

TLcdClusteringTransformer: when using multiple scale denominators to create a scale based cluster transformer with TLcdClusteringTransformer#createScaleDependent, an exception was incorrectly thrown when the denominators were ordered from low to high values. As a result it was not possible to create a scale based cluster with more than one scale denominator.

Bug fixLuciadFusion

LCD-10203


                              TLspPlotLayerBuilder

: Fixed a NullPointerException that could occur when performing a query on a plot layer (e.g. when using the select controller).

Bug fixLuciadFusion

LCD-10161

Fixed an issue where point-to-point snapping could behave erratically for domain objects that do not implement ILcdPoint.

Bug fixLuciadFusion

LCD-10179

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.

ImprovementLuciadFusion

LF-1476

Improved the performance of services with many products.

Bug fixLuciadFusion

LF-1568

Service exception reports returned by the WMTS service are now of content type 'text/xml'. Previously the content type was not in accordance with the OGC WMTS protocol specification.

Bug fixLuciadFusion

LCD-10071

TLcdOGCFilterEvaluator#buildFilter would return ILcdDynamicFilter instances for unsupported TLcdOGCFilter instances. Using the returned dynamic filter would result in runtime exceptions (like


                           NullPointerExpception

Bug fixLuciadFusion

LCD-9952

The GeoTIFF decoder now can handle case of missing ProjectedCSTypeGeoKey within the GeoTIFF tags by handling it as user defined.

Bug fixLuciadFusion

LCD-9955

The GeoTIFF decoder now correctly interprets model references where a user defined geodetic datum is used (GeoTIFF key 2062). The interpretation of the rotation and the scale correction has been fixed.

Upgrade considerationLuciadFusion

LCD-10003

TLcdModelList#setClassTraceOn is now declared static, similar to other classes with that method. If you override this method somewhere in your code, you should make that overriding method static as well.

Upgrade considerationLuciadFusion

LCD-10001

TLcdFeatureIndexedAnd2DBoundsIndexedModel#setTraceOn is no longer declared static. This was a bug, since the method would enable tracing on for every instance of that class, which is not what the javadoc says it does. If you call this method statically somewhere in your code, you should either:

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.

LCD-10004

Bug fixLuciadFusion

LCD-9770

Different geojson features with the exact same geometry are no longer considered 'equal' by their equals method.

ImprovementLuciadFusion

TLspViewNavigationUtil's fit behavior now uses the TLcdModelMetadata bounds, if present. This makes the fit behavior more consistent, regardless of whether or not the model is ILcdBounded.

ImprovementLuciadFusion

LF-1214

The drop-down menu of available data formats in Studio's data table now shows a nice, human-readable name for the GeoPackage and LRDB formats.

ImprovementLuciadFusion

LCD-9816

The XML decoders now accept anyURI values with spaces. Although it is highly discouraged to use spaces in an anyUri, it is not prohibited - see https://www.w3.org/TR/xmlschema-2/#anyURI.

ImprovementLuciadFusion

LCD-6481

TLcdLASModelDecoder#setPerformBoundsAndRangeScan now allows skipping the (limited) data scan during decoding.

ImprovementLuciadFusion

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

ImprovementLuciadFusion

TLcdExpressionFactory can now create expressions for trigonometric, vector and distance operations. A view position attribute, which represents the view coordinates of the object that is evaluated, was also added.

ImprovementLuciadFusion

Three parameterized styles that can be used by the TLspShapePainter (e.g. layers created with TLspShapeLayerBuilder) were added to the

com.luciadview.lightspeed.style

package:

TLspParameterizedIconStyle
TLspParameterizedLineStyle
TLspParameterizedFillStyle

These styles are configured using ILcdExpression, which can be created with the TLcdExpressionFactory. This allows to style objects based on their property values without the need to create a custom ALspStyler and submit multiple styles. Since the evaluation of the expressions of the style is done on the GPU and only one style needs to be used for property based styling, performance will improve compared with a custom ALspStyler.

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.

ImprovementLuciadFusion

The properties in the LAS data model (see TLcdLASModelDescriptor) now disallow null values, because they cannot have absent values. Only the "ExtraBytes" property is nullable, because whether or not extra bytes are present depends on the file content, not the LAS point format.

ImprovementLuciadFusion

TLcdOGCWMSProxyModelDecoder: an extra constructor has been added which allows to specify the ILcdOWSTransport. This can for example be used to connect to a server which requires authentication.

ImprovementLuciadFusion

The LAS model decoder can now decode LASzip (LAZ) 1.0, 1.1, 1.2 and 1.3 files. It depends on the laszip4j third party library for this.

ImprovementLuciadFusion

Studio now includes a file server service. You can use it to let users download geospatial dataset files "as is". To allow downloading a dataset, select it in the data view, press "Create Service" and then choose the "File Server" service type.

ImprovementLuciadFusion

LF-1250

Studio now recognizes and stores the relations between a composite dataset and its children. This considerably improves the crawling performance for composite datasets such as ECDIS catalogs and DTED and CADRG data. In addition, the Studio data view now automatically aggregates composite datasets, hiding all children. This behavior is automatically active for all newly crawled content. You can disable it by deactivating the fusion.studio.configuration.hideDataSeriesChildren configuration property.

ImprovementLuciadFusion

The new TLcdModelMetadata class encapsulates advanced metadata information (including ISO 19115 metadata) about ILcdModel instances. ILcdModelDecoder has a new method decodeModelMetadata to retrieve model information without having to decode the entire model. The information can also be accessed from any ILcdModel. The Luciad model decoders have been enhanced to decode the metadata as efficiently as possible and provide more generic metadata, such as the data category, related files and their mime types.

ImprovementLuciadFusion

LCD-9430

ILcdFeatured and related interfaces have been deprecated in favor of ILcdDataObject and TLcdDataModel.

ImprovementLuciadFusion

LCD-8520

Modulo and integer to float conversion operations are added to the TLcdExpressionFactory.

ImprovementLuciadFusion

LCD-7761

The TLcdCSVModelDecoder can be used to decode CSV files.

LuciadLightspeed now comes with several JavaFX integration samples, which can be found in the package samples/lightspeed/integration/javafx.

ImprovementLuciadFusion

The Natural Earth sample data (see Shp/NaturalEarth) has been updated to version 4.1.

ImprovementLuciadFusion

com.luciad.util.collections: the collections for primitive types were extended with methods to efficiently add an entire array of values without the overhead of boxing the primitive values. See the javadoc for the new addAll methods for more detail.

ImprovementLuciadFusion

LCD-9096

TLcdCRSReferenceParser and TLcdCRSReferenceFormatter now also support the "CRS:83" and "CRS:27" references, and now also have support for ILcdXYWorldReference. TLcdOGCModelReferenceParser and TLcdOGCModelReferenceFormatter now also handle references in the CRS name space.

ImprovementLuciadFusion

LCD-9611

TLcdOGCModelReferenceFormatter now also implements ILcdXYWorldReferenceFormatter.

ImprovementLuciadFusion

LCD-8401

Greatly improved the worst-case performance of TLcdClusteringTransformer. This improvement greatly reduces the clustering time when zooming in on a large (100.000s of points) clustered data set. For a data set with approximately 300.000 points, this can give a 20x performance improvement.

ImprovementLuciadFusion

ILcdSelection now has a new default method getSelectedObjects that exposes the selected objects as a List. In addition, the interface now has a type parameter so you can select more specific collections.

ImprovementLuciadFusion

ILcdModelContainer now has a new default method getModels that exposes the models as a List.

ImprovementLuciadFusion

LCD-9413

TLcdOGCModelReferenceParser now also implements ILcdXYWorldReferenceParser.

ImprovementLuciadFusion

LCD-4144

TLspShapeLayerBuilder: you can now configure whether the created layer should be regarded as a source for snapping points via TLspShapeLayerBuilder#snapTarget.

Bug fixLuciadFusion

Changed TLcdSpatiaLiteModelDescriptor.TYPE_NAME to correspond with the actual type name in the model descriptor instances.

Bug fixLuciadFusion

TLcdEditableModelListDescriptor's constructor taking a type name and display name switched the arguments around.

Bug fixLuciadFusion

Improved trackpad/magic mouse zooming on macOS in GXY and Lightspeed views.

Bug fixLuciadFusion

LCD-9434

Fixed a JRE related performance problem that occurs when using JRE 1.8 update 131 and newer on macOS. It caused low framerates when moving or dragging the mouse.

Upgrade considerationLuciadFusion

Added a dependency on the third party library HPCC Collections for efficient HashMap implementation which is used in PointCloud tile voxelization.

Upgrade considerationLuciadFusion

Due to the introduction of enhancement LCD-4316, the ILcdModelReferenceDecoder and ILcdModelReferenceEncoder instances in a deployed application should no longer be obfuscated. The Proguard configuration file in the release has been adjusted for this. If you use your own Proguard configuration, make sure to update it as well.

Upgrade considerationLuciadFusion

TLcdGeoJsonModelDecoder now ensures that the uid property value of decoded Geojson features is always of type String, as described by the associated data model. Implementations that expected an Integer type in case of a numeric value in the input data should adapt accordingly.

Upgrade considerationLuciadFusion

ILcdOWSTransport a default canPerformRequest method has been added to the interface, allowing users of the transport to first check whether the request can be performed.

Upgrade considerationLuciadFusion

TLspPlotStyle : The alpha value of the modulation color configured on the style is now also taken into account, previously it was ignored. The transparency of the icon is now determined by multiplying the alpha value of the modulation color and the opacity configured on the style. If in your code you use a modulation color which is transparent on your style e.g. TLspPlotStyle.newBuilder().modulationColor(new Color(255,0,0,128)).build(), then you will need to change this to TLspPlotStyle.newBuilder().modulationColor(new Color(255,0,0,255)).build() if the icon needs to remain fully opaque.

Upgrade considerationLuciadFusion

TLcdInputStreamFactory now by default requests compressed content over HTTP, using the "Accept-Encoding" header, for performance. When serving compressed data is not available on the server, it automatically falls back on raw data, unless specified differently. This can be disabled using:

The boolean system property com.luciad.io.TLcdInputStreamFactory.acceptHttpCompressedEncoding
The method TLcdInputStreamFactory#setAcceptCompressedEncoding
The setDefaultRequestProperty("Accept-Encoding", null) method on a specific factory instance

There is no change on the user side, as the TLcdInputStreamFactory automatically unzips the content.

Upgrade considerationLuciadFusion

LCD-9343

ALspDensityStyle: the deprecated protected constructors from ALspDensityStyle and its subclasses have been removed.

Upgrade considerationLuciadFusion

The CSW server component is now included in the OGC server component.

Upgrade considerationLuciadFusion

Removed the protected fNextNumber and fScaleOrigin fields from the GXY view map implementations (for example, TLcdMapJPanel). If you used fNextNumber, you should manage the map count yourself in your map extension class. If you used fScaleOrigin, you can replace it with 450 / (2 * Math.PI * TLcdConstant.EARTH_RADIUS).

Upgrade considerationLuciadFusion

TLcd3DPrimitiveType: this class represents an enumeration, but still had a public constructor. This constructor has been removed as nobody should create new instances of this class.

Upgrade considerationLuciadFusion

TLcdModelDescriptor's protected fields have been removed from the API. You can replace any uses with calls to the respective setter and getter methods.

Upgrade considerationLuciadFusion

Removed the isBackgroundImageCapable methods from the GXY view map implementations (for example, TLcdMapJPanel). You can safely replace any invocation with false.

Upgrade considerationLuciadFusion

LCD-9577

ImprovementLuciadFusion

TLcdOGCFilter: added support to set a TLcdOGCResourceId condition for a single id value, instead of requiring the need to use a TLcdOGCResourceIdOperator condition.

ImprovementLuciadFusion

LF-1274

Improved wording on the close / cancel buttons of dialogs.

ImprovementLuciadFusion

LCD-9219, LCD-9493

TLcdTransformingModelFactory : the bounds of the transformed model are now valid immediately when creating it. This allows you to fit on the layer containing the transformed layer as soon as you created the layer, for instance.

Bug fixLuciadFusion

Bug fixLuciadFusion

Fixed rare threading issue ("Unable to marshal") in TLcdXMLDataObjectEncoderLibrary.

Bug fixLuciadFusion

LF-1433

Fixed rare threading issue ("Unable to marshal") during GML encoding on the WFS server.

Bug fixLuciadFusion

LCD-9808

Fixed an issue with TLspRulerController. When #setKeepMeasurements was set to true, the last created measurement would remain selected during the creation of a new measurement.

Bug fixLuciadFusion

LCD-9761

Fixed handling of layers having a Dimension element without a value for the unitSymbol field. The unitSymbol field is optional. When absent it could cause a NullPointerException.

Bug fixLuciadFusion

LCD-9801


                              TLspPlotLayerBuilder

The default value of the configuration option for the interpretation of the axis-order for EPSG:4326 for WMS 1.3.0 requests is changed to true. This makes the default value compliant with the WMS 1.3.0 specification.

Add the following to your LuciadFusion web.xml file fpr the WMS to disable inversion (making the WMS non-compliant):

      <init-param>
        <param-name>EPSG.4326.latlon</param-name>
        <param-value>false</param-value>
      </init-param>

Bug fixLuciadFusion


                           ILcdModelDecoder

Add the following to your WMS web.xml file to disable inversion (making the WMS non-compliant):

      <init-param>
        <param-name>EPSG.4326.latlon</param-name>
        <param-value>false</param-value>
      </init-param>

Bug fixLuciadFusion

LCD-9681

Bug fixLuciadFusion

LCD-9628

A number of improvements have been implemented related to the server's support for WFS 2.0:

Support has been added for the optional 'RESOURCEID' parameter in a WFS 2.0 GetFeature request. This parameter can be used to query a feature based on its identifier, without the need to specify a feature type.
Support has been added for the WFS 2.0 requests ListStoredQueries and DescribeStoredQueries, along with support for the default, standardized stored query urn:ogc:def:query:OGC-WFS::GetFeatureById. This stored query can be used inside GetFeature requests to query a feature based on its identifier.
The error reporting in case of invalid requests has been improved.
The WFS 2.0 capabilities now include information about constraints and supported conformance classes.

ImprovementLuciadFusion

ELcdBingMapsMapStyle: the enumeration has been extended with values for


                           CANVAS_DARK

, CANVAS_GRAY and CANVAS_LIGHT, allowing you to access those Bing Maps styles. See the Bing Maps blog post for the announcement from Microsoft about those new map types.

ImprovementLuciadFusion

OGC Filter: the handling for spatial operators has been improved:

Some inconsistencies between the BBOX operator and the other spatial operators have been removed.
When the TLcdOGCPropertyName used in the spatial operator to point to the geometry refers to a non-existing property, the geometry will evaluate to null instead of falling back to the domain object itself. This ensures that the spatial operators behave as descriped in the specification in section 7.8.3.4 NULL geometries.

ImprovementLuciadFusion

LF-1279

Added new properties to configure default metadata that will be used when generating any missing required ISO-19115 meta data properties during import jobs

fusion.studio.configuration.defaultMetadata.language: represents the language of the dataset (e.g. en, nl, fr, etc)
fusion.studio.configuration.defaultMetadata.abstractText: is used as a default abstract text
fusion.studio.configuration.defaultMetadata.responsibleParty.role: function performed by the responsible party
fusion.studio.configuration.defaultMetadata.responsibleParty.organisationName: name of the organisation associated with the dataset
fusion.studio.configuration.defaultMetadata.responsibleParty.email: list of emails to communicate with, person(s) and organisations associated with the dataset

ImprovementLuciadFusion

Added new properties to configure default background data and style preview data

fusion.studio.configuration.defaultData.defaultBackgroundData: is used to configure the default background data
fusion.studio.configuration.defaultData.defaultRasterData: is used to configure data for raster style previews
fusion.studio.configuration.defaultData.defaultVectorData: is used to configure data for vector style previews

ImprovementLuciadFusion

TLcdDurationFormat: this new java.text.Format class allows to parse and format durations.

ImprovementLuciadFusion

LF-1314

Improved the "Product contents" UI. It now allows you to set styles on a large number of data items at once.

ImprovementLuciadFusion

LF-1342

The LuciadFusion Platform WFS server now allows to overcome a limitation found in a number of 3rd party WFS clients, such as ArcGIS and Geotools, so that it is now compatible with them. This functionality can be enabled by modifying the fusion.ogc.wfs.enableFeatureTypeNameCompatibilityMode flag in the fusion.common.yml configuration file. This flag, and more information about its behavior can be found in the config/fusion.common.yml file.

ImprovementLuciadFusion

The CSW client is now part of LuciadLightspeed.

ImprovementLuciadFusion

LF-1263, LF-1295

The LuciadFusion Platform Server launcher now shows a clear warning when using a 32-bit version of Java, instead of just terminating the process.

ImprovementLuciadFusion

LF-1343

The LuciadFusion Platform LTS service now also logs the data source title next to the name when an error occurs.

ImprovementLuciadFusion

LF-1333

ImprovementLuciadFusion

LF-1299

The button for removing dataroots is now disabled if it's impossible to remove that dataroot (for example, for the dataroot where uploads are stored).

ImprovementLuciadFusion

LF-1158

The Jobs UI has been redesigned. It has been split into an overview page listing all import jobs, and a detail page showing the properties of a single job.

ImprovementLuciadFusion

TLspShapePainter and TLspShapeLayerBuilder can now be used to create density plots by submitting ALspDensityStyle instances from the used styler. As a result, TLspDensityPainter and TLspDensityLayerBuilder have been deprecated. Consult the class javadoc of TLspShapePainter for more information.

ImprovementLuciadFusion

TLcdBingMapsModelDecoder: improved reliability when working with servers that occasionally return an error.

ImprovementLuciadFusion

The TLcdGeoidGeodeticDatumFactory class now supports the EGM2008 geoid model. See TLcdGeoidGeodeticDatumFactory.EGM2008_GRID_TWO_AND_HALF_MINUTE

ImprovementLuciadFusion

LCD-7540

TLspScaleBasedStylerBuilder can now be used to create a scale dependent ALspStyler. On the builder it's possible to configure scale ranges linked to an ALspStyler. The resulting ALspStyler will automatically switch between styles depending on the scale of the view.

ImprovementLuciadFusion

LF-1123

Bug fixLuciadFusion

LCD-9494

The CADRG decoder now detects and attempts to correct an offsetted subframe mask table, which would otherwise result in decoding errors.

Bug fixLuciadFusion

Fixed a rare ConcurrentModificationException when constructing a new TLcdXMLEntityResolver using the default constructor.

Upgrade considerationLuciadFusion

LCD-9513, LCD-8614

Ensured that TLspEditingStateEvent supports multiple objects in a single event. This allows editing state listeners to be more efficient when editing a large group of objects. This incompatible change removes the TLspEditingStateEvent.getObject() method in favor of a TLspEditingStateEvent.getObjects() method, which returns a list of objects, instead of a single domain objects. If you have code that relies on TLspEditingStateEvent objects, you can easily update your code by iterating over the list of objects returned by TLspEditingStateEvent.getObjects() in a for loop, and handle the event one by one. Note that if you manually used to call ALspEditor.edit() in your code, without using a TLspEditController, you now also have to call ILspInteractivePaintableLayer.editedObjectChanged() explicitly in your own code. The responsibility of calling this method has been moved from the editor to the controller. The default TLspCreateController and TLspEditController have been updated to reflect this, but if you have your own controller (that does not extend from either controllers), then you might have to call ILspInteractivePaintableLayer.editedObjectChanged() directly in your controller.

Upgrade considerationLuciadFusion

The Fusion server now requires the PostGIS extension in order to be used with a PostgreSQL database.

Upgrade considerationLuciadFusion

Upgraded JTS to version 1.14.0 The dependency changed from com.vividsolutions:jts:1.8 to com.vividsolutions:jts-core:1.14.0

Upgrade considerationLuciadFusion

The protected TLfnEngineFactory#createEngineSession method was removed from the API. This method was not designed to be called or overridden.

Upgrade considerationLuciadFusion

LCD-6951

The ArcInfo ASCII Grid format does not include metadata for specifying the coordinate reference system (CRS) of the data. This needs to be specified using an external file (eg .prj or .ref) which is handled by the ILcdModelReferenceDecoder.

The decoder no longer has a default model reference (EGM96) as fall-back when no external geo-reference is found. This makes it visible that important metadata is missing rather than showing the data at a wrong location. The behavior is consistent with other model decoders.

Users that want to get the behavior as before can do this based on the following fragment in their application code. TLcdArcInfoASCIIGridModelDecoder arcInfoASCIIGridModelDecoder = new TLcdArcInfoASCIIGridModelDecoder(); arcInfoASCIIGridModelDecoder.setDefaultModelReference( new TLcdGeodeticReference(new TLcdGeoidGeodeticDatumFactory().createGeodeticDatum(EGM96_GRID_BILINEAR)) );

Upgrade considerationLuciadFusion

The CSW API is now final. The following changes were made since the 2017.0 release:

ALcdCSWRecordDescriptor has been renamed to TLcdCSWRecordType and all subclasses have been replaced by constants.
ILcdCSWQueryHandler is now part of ILcdCSWCapabilitiesProvider.
ILcdCSWQueryHandler#getQueryLanguages has moved to ILcdCSWCapabilitiesProvider#getInputRecordTypes.
ILcdCSWQueryHandler#getOutputRecordTypes has moved to ILcdCSWCapabilitiesProvider#getOutputRecordTypes.
ILcdCSWQueryHandler#getFilterCapabilities has moved to ILcdCSWCapabilitiesProvider#getFilterCapabilities.
ILcdCSWQueryHandler#getQueryLanguages has been removed.
ALcdCSWFilterQueryHandler#executeFilter now passes the original request.
TLcdCSWGetCapabilitiesRequest has been removed.
TLcdCSWCommandDispatcherContext has been removed.
ALcdCSWCommandDispatcherFactory#createQueryHandler has been moved to ILcdCSWCapabilitiesProvider#getQueryHandler
TLcdCSWGetCapabilitiesRequest: removed getVersion and setVersion
TLcdCSWOpenSearchTemplate: removed OutputFormat in favor of TLcdCSWRecordType
TLcdCSWQuery: split up get/setElements into get/setElements and get/setElementNameSet
TLcdCSWElementSetName: renamed get/setValueObject to get/setElementSet
TLcdOpenSearchAtomFeed: removed some property constants, use the getters and setters instead
TLcdCSWServiceException: has been moved to the com.luciad.ogc.csw package
TLcdCSWRecordPropertyRetrieverProvider: now takes a record type as constructor argument
Several client API related classes have been moved out of the com.luciad.ogc.csw.server package

The name of the LcdService annotation the service loader is looking for as it may be obfuscated.
The actual annotations that are available at runtime on the class.

Bug fixLuciadFusion

The TLcdEllipsoid#bufferContour2DOfSegmentSFCT and TLcdEllipsoid#bufferContour2DOf2DPolylineSFCT methods now use geodetic calculations instead of spherical calculations.

Bug fixLuciadFusion

LCD-9088

For some configurations of TLcdObliqueMercator, converting from world to lon-lat could result in points with NaN values.

Bug fixLuciadFusion

LCD-9103

The OGC clients threw an incorrect exception (TLcdOWSUnsupportedVersionException) when a HTML website was accessed that did not represent an OGC web service.

ImprovementLuciadFusion

An new Dublin Core metadata package is now available in com.luciad.format.metadata.dc.model. It provides support for the DCMI's specification for metadata.

ImprovementLuciadFusion

An new ATOM metadata package is now available in com.luciad.format.metadata.atom.model. It provides support for describing metadata using the Atom Syndication Format.

ImprovementLuciadFusion

Added a new, generic cartesian reference that can be used as a model reference or world reference. You can optionally specify a unit of measure (ILcdISO19103UnitOfMeasure) per axis. This reference can be used to specify any non geospatial 2D X/Y plane or 3D X/Y/Z volume.

ImprovementLuciadFusion

The WFS client now supports the new "minBoundsSize" OGC function. When used with servers that support this function (for example LuciadFusion), the function is evaluated by the server, so the client can avoid retrieving small elements.

This function allows to filter out elements which do not have a certain minimum size. A use-case of this function is requesting only the elements which will be visible when painting data on a map at a certain scale, and skip all objects which are too small.

For more information, see TLcdOGCVendorSpecificFunctions.

ImprovementLuciadFusion

LCD-7622

TLcdDataModelDescriptor now uses sensible defaults for model element types and model types if you pass null for the respective arguments:

The TLcdDataModel.getDeclaredTypes() are used as model element types if you pass null.
The TLcdDataModel.getTypes() are used as model types if you pass null.

ImprovementLuciadFusion

TLcdSymbol now has a new symbol type: a filled circle with a double outline.

ImprovementLuciadFusion

Added new parameter to TLcdKML22Parameter called "asynchronousAllowed". This allows you to set whether dynamic models should retrieve their resources synchronously or asynchronously. The default behavior is asynchronous, as before. We recommend setting this parameter to false when working on a server-side application such as WMS. Note that by default, if you are already using a parameters updater object, such as TLcdKML22GXYViewParametersUpdater, TLcdKML22GXYViewParametersUpdater, then this will automatically update this setting based on the preferences of the currently active view.

ImprovementLuciadFusion

Added decoding/encoding support for GML 3.2 coverages (see TLcdGML32AbstractCoverage and subclasses). Note that visualization of or image operations on GML coverages are not supported.

ImprovementLuciadFusion

LCD-3555

TLcdWFSClientModelEncoderFactory now includes GeoJSON in its advertised output formats. This made the previously available sample code to support GeoJSON redundant, so that sample code has been removed (WFSClientModelEncoderFactory).

ImprovementLuciadFusion

LCD-8853

To be able to use an existing OpenGL texture object with ALspTextureObject, it was required to overwrite all the methods of this class. Now it's only required to overwrite ALspTextureObject#getTextureObject to provide the OpenGL texture object ID.

ImprovementLuciadFusion

LCD-8974

A new custom OGC function is introduced: see


                           TLcdOGCVendorSpecificFunctions.GEOMETRY_TYPE_FUNCTION_NAME

For more information, please refer to the javadoc of TLcdModelQueryConfiguration or the LuciadLightspeed Developer's Guide. See also the article How to visualize OpenStreetMap data sets with LuciadLightspeed on the Luciad Developer Platform for an example use case.

ImprovementLuciadFusion

LCD-8678

Several API usability improvements were made for working with OGC filters:

TLcdOGCFilterEvaluator: this class can now evaluate spatial filters as well when the Geometry Additional Component is available on the class path. It is no longer needed to create a TLcdOGCFilterSpatialEvaluator for this. As a consequence, the constructor for TLcdOGCFilterSpatialEvaluator has been deprecated.
Introduction of ILcdOGCFeatureIDRetriever#createDefaultFeatureIDRetriever. TLcdXMLElementPropertyRetrieverProvider is deprecated in favor of this new method.
Extra constructors are added to TLcdOGCFilterContext
The static method TLcdOGCFilterEvaluator#registerDefaultFunction allows to add support for default OGC functions to all evaluators.
TLcdOGCFilterDecoder and TLcdOGCFilterEncoder now offer (static utility) methods to decode/encode from/to a String and or Input/OutputStream.

ImprovementLuciadFusion

Several minor inconsistencies in the different evaluators for OGC filters have been fixed. An example of such an inconsistency is an evaluator which would return true for A == B but false for A >= B.

ImprovementLuciadFusion

LCD-8418, LCD-7697

ALspCameraConstraint can now be used to constrain parameters other than those passed to lookAt() and lookFrom(), such as the field of view or the near and far clipping planes. This improvement also fixes possible drifting of a 3D camera when a constraint is active (reported in LCD-7697).

ImprovementLuciadFusion

XML framework: improved the handling of content in elements of the "any" type.

ImprovementLuciadFusion

LCD-8743

The WFS model TLcdWFSProxyModel now properly takes into account all bounding boxes of a feature type to locate the data. In the past, only one bounding box was considered, which is the most common use case.

ImprovementLuciadFusion

LCD-8968

ILcdModelDecoder now has a method to retrieve all ILcdDataSource instances for a given source path. This method can be used in conjunction with the new API to retrieve a specific ILcdModel custom model decoder that wraps an existing ILcdModelDecoder, we highly recommend delegating these new default interface methods as well.

ImprovementLuciadFusion

LCD-8896

An new ISO metadata package is now available in com.luciad.format.metadata.model.service. It provides support for the ISO 19119 specification for Geographic information Services.

ImprovementLuciadFusion

LCD-8965

All common implementations of ILcdISO19103UnitOfMeasure now implement equals() and hashcode() so that they can be compared more easily. This also makes serialization of units of measure easier to implement.

ImprovementLuciadFusion

In the WCS service, the default implementation of ALcdOGCWCSCommandDispatcherFactory#createModelDecoderFactory returns a TLcdOGCModelDecoderFactory. This factory automatically picks up all the data connectors that are found on the class path. It uses the TLcdServiceLoader to find all the


                           ILcdModelDecoder

Only coverages of types ELfnDataType#IMAGE,ELfnDataType#ELEVATION, and ELfnDataType#RASTER are supported.

The returned models expose their dimensions through the ILcdMultiDimensional interface.

ImprovementLuciadFusion

LCD-3862

There is a default command dispatcher factory available which provides a good starting point for making a Web Map Service with few or no additional programming. The TLcdOGCWMSCommandDispatcherFactory loads most of its functionality using a service loader mechanism. More specifically, implementations of decoders and layer factories are picked up automatically when they are annotated with the appropriate LcdService annotation. The sample command dispatcher factory extends from the default factory and only adds dynamic behavior.

ImprovementLuciadFusion

The display names of several formats have been improved. Also, TLcdModelDescriptor.sourceNameToDisplayName has been added to derive a display name from a source name.

ImprovementLuciadFusion

You can use a new, lazy-loading ESRI Shapefile decoder: TLcdSHPModelDecoder2.

This decoder does lazy loading of elements, based on the client request.

This ensures a low memory footprint if only part of the data is needed at the same time:
- when visualizing a small area
- when a model query filter is used
- when doing processing on the elements one by one
It also ensures fast model creation.

Both changes can be used regardless of whether the condition will eventually be serialized to a 1.1 OGC Filter (for example WFS 1.x, or SLD), or a 2.0 OGC Filter (for example WFS 2.0).
Binary arithmetic operators (Add/Mul/Sub/Div) are no longer supported in the OGC Filter 2.0 standard. You can still create them and evaluate them, but you will get an error when it is serialized to OGC Filter 2.0 XML (for example WFS 2.0).

ImprovementLuciadFusion

ALcdMultiDimensionalModelProvider provides a default implementation of its getModel method that takes dimensional parameters. This adds multidimensional support to WMS if your models implement ILcdMultiDimensionalModel.

ImprovementLuciadFusion

LCD-7978

The new TLcdShapeDataTypes.SHAPE_TYPE is a built-in data type (TLcdDataType) that you can use for properties that are ILcdShape.

ImprovementLuciadFusion

LCD-6917

3D icons are now rendered in two passes when the painting hints on the view are set to NICEST. As a result, 3D icons with transparent textures will no longer contain 'holes'.

ImprovementLuciadFusion

ILcdFilter now extends java.util.function.Predicate<T> and implements test() using a default method that delegates to accept().

ImprovementLuciadFusion

For better interoperability with reverse proxies, the server now uses OnlineResource paths relative to the servlet mapping instead of relative to the servlet container in its capabilities. For backwards compatibility, the behavior towards older clients remains as it was before. This feature requires that both client application (DCM, Lucy, ...) and server are using LuciadFusion V2017.0 or higher. If you're running a LuciadFusion server behind a reverse proxy and want to take advantage of this feature, you should make sure both client and server are up-to-date.

ImprovementLuciadFusion

LCD-8209

The sample package samples.lightspeed.style.textured is removed. The fill style sample in the package samples.lightspeed.style.fillstyle shows how to use a texture with a fill style.

ImprovementLuciadFusion

LCD-8546, LCD-8801

ILcdBounds now has a few new default convenience methods:

getMinX(), getMaxX(), getMinY(), getMaxY(), getMinZ(), getMaxZ(): provide the left/right/lower/upper/bottom/top boundary values. These are derived properties, calculated from the location and width/height/depth. They can be overridden for performance
getCenter(): provides a point that is the center of the bounds.

ImprovementLuciadFusion

ILcdLogger received new methods which accept a Supplier<String> as argument instead of a String, similar to what has been done in the JDK for the


                           java.util.logging.Logger

In some cases, TLcdWFSProxyModelDescriptor#getModelElementTypes() returned too many data types.

Bug fixLuciadFusion

GML encoding: has-a-shapelist domain objects are now correctly encoded to GML 2.

Bug fixLuciadFusion

The default ILcdModelProvider returned by ALcdOGCWMSCommandDispatcherFactory#createModelProvider threw an IllegalArgumentException instead of an IOException when no model decoder can be found for a given source.

Bug fixLuciadFusion

LCD-7277

TLcdSHPModelDecoder: The character set used for String values parsed from the DBF file was incorrect if the DBF file uses one of the ISO-8859 encodings.

Bug fixLuciadFusion

      <ogc:PropertyIsEqualTo>
      <ogc:Function name="my_custom_function">
      <ogc:Literal>foo</ogc:Literal>
      </ogc:Function>
      <ogc:Literal>true</ogc:Literal>
      </ogc:PropertyIsEqualTo>

might be converted to just a TLcdOGCFunction which evaluates to a boolean, instead of being wrapped in a TLcdOGCBinaryComparisonOperator.

Upgrade considerationLuciadFusion

The deprecated classes from the com.luciad.ogc.filter package have been removed, as well as the TLcdOGCBinarySpatialFilterFactory class.

These classes have been deprecated since V6 and were only used in V5 to decode an XML representation of an OGC filter into Java classes. For this, you can use the TLcdOGCFilterDecoder instead.

Upgrade considerationLuciadFusion

TLcdTransformingModelFactory no longer offers a way to specify whether the transformed model should keep a spatial index. It will never do so. This also means returned models will no longer implement ILcd2DBoundsIndexedModel.

Upgrade considerationLuciadFusion

TLcdOGCFilterSpatialEvaluator: the constants of this class have been removed. These constants were ILcdSpatialEvaluatorFunction instances which should not have been used directly. If you want to perform spatial filtering, you either decode an XML representation of a filter into an TLcdOGCFilter, or you use the TLcdOGCBinarySpatialOperator class.

Upgrade considerationLuciadFusion

LCD-3073

The third library dependency on Batik has been updated from version 1.7 to 1.9. Its dependency on Xalan has also been updated from version 2.6.0 to 2.7.2.

Upgrade considerationLuciadFusion

The interface ILcdCoverageFilterFactory has been removed from the API. A compile error will notify you if you were using this interface, which we don't anticipate as it was not used effectively. The new ILcdWCSCapabilitiesProvider offers a more powerful and easier-to-use replacement, should there be a need.

Upgrade considerationLuciadFusion

LCD-7995

TLcdCompositeModelDecoder now throws an exception when no delegate decoder creates a non-null model. Before, it returned null instead. This change has little impact as calling code already had to deal with exceptions. In addition, it is more clear because of the exception message, and is more in line with what to expect from ILcdModelDecoder.decode, as defined by the interface. See javadoc of TLcdCompositeModelDecoder.decode for details.

Upgrade considerationLuciadFusion

LCD-8955

Upgraded woodstox to a newer version. Previously, the XML module had a dependency on woodstox 4.0.9, but this has been upgraded to woodstox 5.0.3 for compatibility reasons.

Upgrade considerationLuciadFusion

TLcdOGCBinaryComparisonOperator: the unsupported class constants MATCH* have been removed from the API. As it was virtually impossible to use them, we don't expect this to affect anyone.

Upgrade considerationLuciadFusion

The following classes related to the MTM format have been deprecated: TLcdMultilevelTiledModelDecoder, TLcdMultilevelTiledModelDescriptor and TLcdMultilevelRegularTiledModelDecoder.

Upgrade considerationLuciadFusion

The caching behavior for ILcdWFSFeatureType on the WFS server has been modified. Previously, caches used the ILcdWFSFeatureType instance itself as key for a cache. This implies that caches didn't work as expected when using different WFS feature type instances that represent the same data.

This instance-based caching mechanism has been replaced by a caching mechanism that uses the following properties as cache key:

ILcdWFSFeatureType#getQName: uniquely identifies the WFS feature type.
ILcdWFSFeatureType#getUpdateSequence: identifies the 'version' of the WFS feature type. I.e. if a property of the feature type changes, its update sequence should change as well.
ILcdOGCModelProvider#getUpdateSequence: identifies the 'version' of the underlying data. I.e. if the data changes, this update sequence should change as well.

Upgrade considerationLuciadFusion

TLcdKML22LookAt and TLcdKML22Camera used to have a method adjustCameraSFCT to modify the settings of an ILcdGLCamera of an ILcdGLView (so not GXY nor Lightspeed views). These methods are no longer available. It is still possible to fit an ILcdGLView on a feature using TLcdKML22GLViewFitAction, as before.

Upgrade considerationLuciadFusion

For reasons of technical software consistency, TLcdCADRGModelDecoder and related API have moved to the NITF component, part of the option Defense Standards. Please contact Luciad support if you have questions on how to get access to this option.

Upgrade considerationLuciadFusion

The LuciadFusion server API (com.luciad.fusion.server.*) has been superseded with the LuciadFusion Platform. Please refer to the Fusion migration guide for more information.

Upgrade considerationLuciadFusion

The WMS server has added caches on two new levels:

The command dispatchers now use a mechanism of view pooling. This changes the call order of methods such as TLcdOGCWMSCommandDispatcher.clearGXYView. If needed, the pool size (ALcdWMSCommandDispatcher.setGXYViewPoolSize) can be set to 0 obtain the old behavior.
It now uses a non-persistent tile cache for tiled (Tiled WMS) GetMap requests. This cache makes sure that subsequent tile requests are handled much faster, improving the performance and scalability of the WMS server when using tiled requests. See ALcdOGCWMSCommandDispatcherFactory for more information (also on how to disable tile caching for example).

This implies that for data that changes dynamically, extra care needs to be taken to make sure caches are invalidated. To this end, the following API was introduced:

ALcdWMSLayer#setUpdateSequence: Used to indicate that a WMS layer has changed. This includes all dependencies such as styles, layer factory implementation, etc...
ILcdModelProvider#getModelUpdateSequence: Used to indicate that the underlying data has changed. This can mean that the model has been changed in-memory, or that the underlying data (file/database/...) has been changed.

By default, the implementations of these methods (mostly) assume static data/layers. For WMS 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.

Upgrade considerationLuciadFusion

The Java Servlet dependency has been upgraded from version 3.0 to 3.1. Consequently, an application server or servlet container with support for Java Servlet 3.1 or higher is now required for deployment of the server - for instance, Tomcat 8 or higher. The impact of this is expected to be low since Java Servlet 3.1 is widely adopted by application server and servlet container products. The servlet container delivered with the Luciad products, Jetty 9, already supports Servlet 3.1.

Upgrade considerationLuciadFusion

The Java Servlet dependency has been upgraded from version 3.0 to 3.1. Consequently, an application server or servlet container with support for Java Servlet 3.1 or higher is now required for deployment of the server - for instance, Tomcat 8 or higher. The impact of this is expected to be low since Java Servlet 3.1 is widely adopted by application server and servlet container products. The servlet container delivered with the Luciad products, Jetty 9, already supports Servlet 3.1

Upgrade considerationLuciadFusion

The isAntiAliased method was added to the ILcdGXYView interface. The view implementations have the corresponding setter. This allows to globally enable anti-aliasing on a view, to achieve smoother rendering results. This can lead to a compile error for custom ILcdGXYView implementations. The compile error can be solved either by delegating to an other view, or by implementing this method when no delegate is available. A basic implementation would be to always return true or false.

Upgrade considerationLuciadFusion

All WCS request handler implementations are no longer part of the public API:

TLcdWCSGetCapabilitiesRequestHandler
TLcdWCSDescribeCoverageRequestHandler
TLcdWCSGetCoverageRequestHandler

Any unlikely usages of these concrete classes can be replaced as follows:

Decoration: in case you were wrapping the request handlers, you can generically wrap them instead, they offered nothing in addition to the ILcdRequestHandler interface.
setCoverageOfferingList and setServiceMetaData calls can be replaced by creating/wrapping the ILcdWCSCapabilitiesProvider in the WCS command dispatcher factory. This is a much more powerful, easier and safer approach to achieve similar results. See also the other release note about ILcdWCSCapabilitiesProvider for more information.

Upgrade considerationLuciadFusion

The ILcdWCSCapabilitiesProvider interface was added. This interface describes the capabilities of a WCS service. Advantages over ILcdCoverageOfferingList are that:

it is easier now to update the coverage offering while the service is running.
it allows to lazily load models to improve the scalability of the server.
it allows to do per-request handling of coverages. This for example allows to filter out coverages for specific users or groups.
it separates the configuration/metadata from the actual use of models.

The models should be accessed through the model provider. To this end, the method createModelProvider was added to the ALcdOGCWCSCommandDispatcherFactory. The default implementation TLcdOGCModelProvider maintains a cache for all decoded models.

The ALcdOGCWCSCommandDispatcherFactory allows you to plug in a ILcdWCSCapabilitiesProvider by overriding the createWCSCapabilitiesProvider method.

The methods createServiceMetaData and createCoverageOfferingList of ALcdOGCWCSCommandDispatcherFactory remain to exist but they will be no longer be abstract. Overwriting the new method to create the capabilities provider createWCSCapabilitiesProvider will be the preferred way of working instead of using the two previously mentioned methods.

In order to make sure this new interface is used in the WCS server, the following change was made:

TLcdWCSCommandDispatcherContext now contains the methods getCapabilitiesProvider() and getModelProvider() instead of the getCoverageOfferingList() and getServiceMetaData() methods. Usages of these methods can be replaced by the corresponding functionality on the ILcdWCSCapabilitiesProvider.

Upgrade considerationLuciadFusion

All WFS request handler implementations are no longer part of the public API:

TLcdWFSDescribeFeatureTypeRequestHandler
TLcdWFSGetCapabilitiesRequestHandler
TLcdWFSGetFeatureRequestHandler
TLcdWFSLockFeatureRequestHandler
TLcdWFSTransactionRequestHandler

Any unlikely usages of these concrete classes can be replaced as follows:

Decoration: in case you were wrapping the request handlers, you can generically wrap them instead, they offered nothing in addition to the ILcdRequestHandler interface.
setFeatureTypeList calls (which had inherent threading issues) can be replaced by creating/wrapping the ILcdWFSCapabilitiesProvider in the WFS command dispatcher factory. This is a much more powerful, easier and safer approach to achieve similar results. See also the other release note about ILcdWFSCapabilitiesProvider for more information.
The TLcdDataModel instances passed to TLcdWFSTransactionRequestHandler can now be configured in the WFS command dispatcher factory. See ALcdOGCWFSCommandDispatcherFactory#createTransactionContentDataModels(). By default, this method, amongst others, returns the AIXM 5.1 data model (if available).

Upgrade considerationLuciadFusion

LCD-4837

The ILcdWFSCapabilitiesProvider interface was added. This interface describes the capabilities of a WFS service. Advantages over ILcdWFSFeatureTypeList are that:

it allows adding/removing data without restarting the server
it allows to lazily load models to improve the scalability of the server
it allows to do per-request handling of feature type. This for example allows to filter out feature types for specific users or groups.

The ALcdOGCWFSCommandDispatcherFactory allows you to plug in a ILcdWFSCapabilitiesProvider by overriding the createWFSCapabilitiesProvider method.

In order to make sure this new interface is used in the WFS server, the following changes were made:

TLcdWFSCommandDispatcherContext now contains a getCapabilitiesProvider() method instead of the getFeatureTypeList(), getServiceProvider() and getServiceMetaData() methods. Usages of these methods can be replaced by the corresponding functionality on the ILcdWFSCapabilitiesProvider.
TLcdWFSRequestContext now contains a getCapabilitiesProvider() method instead of the getAvailableFeatureTypes method. Usages of this method can be replaced by a call to ILcdWFSCapabilitiesProvider#getFeatureTypes. It will also be necessary to handle the TLcdWFSServiceException that is thrown by this method (during a request, this exception should not be caught).
The TLcdWFSFilteredModelFactory constructor now doesn't take any parameters as input anymore.
ALcdOGCWFSCommandDispatcherFactory#createFilteredModelFactory now takes an ILcdWFSCapabilitiesProvider as argument instead of an ILcdWFSFeatureTypeList.

Upgrade considerationLuciadFusion

The interfaces ILcdRequest and ILcdResponse have been extended with additional methods that are useful in the context of conditional get requests. The methods were already available on the concrete implementations for which internally instance of and casting was done to achieve the desired behavior.

This change affects users that have implemented ILcdRequest and ILcdResponse themselves. There is no need to implement these interfaces yourselve though as there are implementations available within the Luciad product.

Upgrade considerationLuciadFusion

The interfaces ILcdRequest and ILcdResponse have been extended with additional methods that are useful in the context of conditional get requests. The methods were already available on the concrete implementations, but are now accessible from the interface without the need for downcasting.

This change affects users that have implemented ILcdRequest and ILcdResponse themselves. There is no need to implement these interfaces yourself though as there are implementations available within the Luciad product.

Upgrade considerationLuciadFusion

TLcdWMTSModelDecoder now returns models with has-an-image domain objects instead of just an image. So the element(s) returned by ILcdModel.elements() no longer extend from ALcdImage, but rather contain a reference to such an ALcdImage. In certain conditions, the returned TLcdWMTSModelDescriptor also implemented ILcdEarthModelDescriptor, this is no longer the case. Because of the has-an-image approach, the WMTS client can now support multidimensional data such as GRIB or NetCDF that varies over time, altitude or other dimensions (see also ILcdMultiDimensionalModel). By applying a dimensional filter (ILcdMultiDimensionalModel.applyDimensionFilter), you can now change one or more values of of a multidimensional data model, and see the underlying image change accordingly. This means the behavior of serving NetCDF and GRIB data through a WMTS is very similar to opening it locally. This change does not affect any typical painting related code, the regular approaches remain to work as expected (e.g. TLcdGXYImagePainter or TLspRasterLayerBuilder). Should direct access to the image data be needed, please refer to ALcdImage.fromDomainObject.

Upgrade considerationLuciadFusion

The interfaces ILcdKVPRequest and ILcdXMLRequest have been merged within their common super-interface ILcdRequest. Consequently, these interfaces have been removed. This change makes the request interface more in line with the well-known Servlet API, and makes it easier to use. It also allows to deal with other content types in the future, and resolves an API dependency on JDom XML parsing. In addition, extra methods are exposed on ILcdRequest to have access to more information such as the attributes and the user principal.

As a consequence the interface ILcdRequestHandler and the abstract class ALcdOGCCommandDispatcher (and their implementations) have been updated accordingly. They now have a single method

void handleRequest(ILcdRequest aRequest, ILcdResponse aResponse) throws TLcdOGCServiceException

which is used for all requests. This further simplifies the request handling, allowing implementations to decide if they want to differentiate on the content type of the request or not.

Code that used to differentiate based on the content type of the request (e.g. instanceof ILcdKVPRequest or ILcdRequestHandler.handleRequest(ILcdKVPRequest ...)) needs to be adapted, the compiler will flag these places. Typical OGC service customizations had no need to do this. The type of request can now be determined using the content type of the request, utility methods TLcdServletUtil#isKVPRequest and TLcdServletUtil#isXMLRequest are available.

Upgrade considerationLuciadFusion

ILcdInitializationConfig now exposes an ILcdServletContext object. This servlet context object contains the configuration for a group of servlets, while ILcdInitializationConfig contains the configuration for a single servlet. This is useful for example to configure a shared cache between servlets. This change normally does not affect anyone as the implementation of this interface is provided by the product.

Upgrade considerationLuciadFusion

Server-side support for coverages of type VECTOR has been superseded with other mechanisms. Please refer to the Fusion migration guide for more information.

This means that it is no longer possible to read existing VECTOR coverages anymore. This also means it is no longer possible to fuse data as VECTOR coverages anymore.

Upgrade considerationLuciadFusion

Support for coverages of type VECTOR has been superseded with other mechanisms. Please refer to the Fusion migration guide for more information.

This means that it is no longer possible to read existing VECTOR coverages anymore. This also means it is no longer possible to fuse data as VECTOR coverages anymore.

Upgrade considerationLuciadFusion

Client-side support for coverages of type VECTOR has been deprecated in favor of other mechanisms for publishing vector data. Please refer to the Fusion migration guide for more information.

This means that LuciadFusion clients remain able to read existing VECTOR coverages. We recommend publishing vector data through the OGC WFS protocol.

In the context of this change, these API changes were done:

The ELfnDataType#VECTOR field has been deprecated.
Classes related to ELfnDataType#VECTOR coverages have been deprecated.

Upgrade considerationLuciadFusion

The PNG encoder implementation TLcdGXYViewPNGEncoder now uses the ObjectPlanet PNG encoder, which is part of an additional 3rd party library. The ObjectPlanet PNG encoder library is a lot faster than the previously used JAI based PNG encoding.

As a result the implementation of TLcdGXYViewPNGEncoder.encodeGXYView declares it can throw an IOException. The interface ILcdGXYViewEncoder.encodeGXYView already declared the IOException on its method. This affects only users using the concrete class TLcdGXYViewPNGEncoder, which is very unlikely.

Upgrade considerationLuciadFusion

LCD-450

The class ALcdWMSProxy no longer implements the interface ILcdDataSource. ILcdDataSource implementations are expected to not contain business logic and they are expected to be modeled such that they can be serialized, which was not achievable for ALcdWMSProxy. The class TLcdWMSDataSource provides a proper ILcdDataSource implementation for a WMS client proxy object.

Upgrade considerationLuciadFusion

The dependency on the Jackson library changed from version 1 to 2. In case you had code written directly to this library, you can keep on using Jackson 1 and 2 together as they have separate namespaces: org.codehaus.jackson and com.fasterxml.jackson respectively. Please refer to the library documentation for more information about this change.

Upgrade considerationLuciadFusion

LCD-8782

Various protected fields in the core point and bounds classes have been made private. They were already clearly documented that they should not be accessed directly.

Changed classes and fields:

TLcdLonLatPoint: fLon, fLat, fSinLon, fSinLat, fCosLon, fCosLat
TLcdLonLatHeightPoint: fLon, fLat, fZ, fSinLon, fSinLat, fCosLon, fCosLat
TLcdLonLatFloatPoint: fLon, fLat
TLcdLonLatBounds: fPoint, fWidth, fHeight
TLcdLonLatHeightBounds: fPoint, fWidth, fHeight, fDepth
TLcdLonLatFloatBounds: fLon, fLat, fWidth, fHeight
TLcdXYPoint: fX, fY
TLcdXYZPoint: fX, fY, fZ
TLcdXYFloatPoint: fX, fY
TLcdXYZFloatPoint: fX, fY, fZ
TLcdXYBounds: fPoint, fWidth, fHeight
TLcdXYZBounds: fPoint, fWidth, fHeight, fDepth
TLcdXYFloatBounds: fX, fY, fWidth, fHeight
TLcdXYZFloatBounds: fPoint, fWidth, fHeight, fDepth

If you access any of these fields, you will now get a compilation error. Each of the fields has an alternative method that you should use.

Upgrade considerationLuciadFusion

LuciadFusion can not support legacy AIXM 5.0 anymore. AIXM 5.0 was introduced in 2007 by FAA and Eurocontrol as an intermediary to validate a new approach. This has lead to the creation of the official AIXM 5.1 standard in 2010, which of course remains supported, together with AIXM 3.3 and 4.x.

Upgrade considerationLuciadFusion

LCD-8698

Proguard's jar-merging capability is no longer supported. Proguard merges .jar files by simply adding all files contained inside multiple jar files in a single jar file, not handling duplicate file names. This creates issues with the contents of the META-INF directories, present in every jar file. Most notably, the contents of the META-INF/services directory must be preserved as of now.

To know if you are affected or not, search your configuration files for the '-outjars' Proguard option. If it specifies a directory name, you are not affected. If it specifies a file name, you are affected. You can solve it by changing the file name into a directory name, and update the remainder of your build script to work with that directory rather than a single file. This avoids using Proguard's jar-merging; it now obfuscates and copies every jar file separately into the output directory. All example build scripts were updated to do so.

Should you not make this change, existing projects will keep on working. When starting to use new 2017.0 functionality, you may experience that not all services (model decoders, layer factories etc.) are found after deploying your application.

Our product code (com.luciad.*) started to make use of TLcdServiceLoader in certain places (identical to java.util.ServiceLoader), such as the default WMS server configuration. Previously, it was only used by sample code (samples.*). This allows for many benefits, now and in future versions, to pick up optional dependencies. For example, the default WMS server may automatically pick up the MrSID data format if you installed it.

These so called 'services' are listed in files in the META-INF/services directory of various jar files. Distinct jar files use the same file names, as prescribed by ServiceLoader. When deploying your application using Proguard, as our example deployment scripts do, care must be taken to disable its jar-merging capability which does not correctly handle those services files (see also https://sourceforge.net/p/proguard/feature-requests/94/). This can be done by specifying the name of a directory instead of a file for the -outjars property. Proguard then no longer attempts to merge the jar files, but instead obfuscates them all individually and places them in the output dir. Should jar-merging still be required, we recommend using an existing technology that supports services files, as most do.

Upgrade considerationLuciadFusion

The ILcdRequest interface has been extended with a few additional methods. It provides access to the current authenticated user, if any authentication is taking place. It also allows to retrieve programmatically set attributes to pass on information. As instances of this interface are created internally, you are normally not affected by this change.

Upgrade considerationLuciadFusion

It is now possible to make ILcdGXYView implementations behave synchronously. This can be enabled or disabled by using the setAsynchronousAllowed method on the ILcdGXYView implementations.

The isAsynchronousAllowed method was added to the ILcdGXYView interface to make sure layers/painters/... can detect if asynchronous behavior is allowed. This can lead to a compile error for custom ILcdGXYView implementations. The compile error can be solved either by delegating to an other view, or by implementing this method when no delegate is available. A basic implementation would be to always return true or false.

The TLcdGXYViewBufferedImage and TLcdGXYViewPlanarImage and their extension now don't allow asynchronous painting/operations by default. The previous behavior can be restored by calling view.setAsynchronousAllowed(true).

Upgrade considerationLuciadFusion

ILspLayer can have now post-processing effects with a TLspLayerStyle. TLspLayerStyle styles a layer as a whole contrary to ILspStyler or ALspStyle that perform the styling per object. TLspLayerStyle can be set and retrieved with the newly added methods ILspLayer#setLayerStyle(TLspLayerStyle) and ILspLayer#getLayerStyle(). For layers built by TLspShapeLayerBuilder, you can also set the layer style with ALspLayerBuilder#layerStyle(TLspLayerStyle). You can now set a TLspLayerStyle on a Lightspeed layer to

change the transparency of the entire layer
perform color conversions on the fly. For instance, you can convert an entire layer to greyscale.
adjust the brightness and the contrast of each pixel.
swap colors on the fly.

Upgrade considerationLuciadFusion

All usages of ILcdDataSourceModelDecoder in the API were removed and replaced by ILcdModelDecoder. This affects the ILfnDataSourceModelDecoderFactory interface and its implementations. Compile errors can be fixed by using ILcdModelDecoder instead.

Upgrade considerationLuciadFusion

ILcdModelDecoder now supports decoding ILcdDataSource objects. More specifically, it now contains the canDecodeSource(ILcdDataSource) and decodeSource(ILcdDataSource) methods with a default implementation that adds support for the TLcdDataSource data source implementation. This means that it is not needed to implement or use ILcdDataSourceModelDecoder anymore, since you can now use ILcdModelDecoder instead.

Custom ILcdModelDecoder instances that override the methods with ILcdDataSource as argument, need to make sure they call the overridden method using super as well. Not doing so breaks the default support for TLcdDataSource.

Upgrade considerationLuciadFusion

Some thread names have been improved to facilitate debugging and profiling. If you were relying on any Luciad thread name (which is not recommended), adjust your code accordingly.

Upgrade considerationLuciadFusion

The fusion engine now doesn't support fusing multivalued data as MULTIVALUED coverages anymore. Support for MULTIVALUED coverages was very limited. You can still fuse multivalued assets as RASTER coverages, which is better supported.

In the context of this change, API changes were done:

The ALfnFormat class now doesn't contain an ILcdEarthMultivaluedProviderFactory anymore. This means that its constructors now don't accept such a parameter anymore. The getter and setter for this property was removed as well.
The ALfnFormat#newMultivaluedFormat methods were removed.
A similar change was done for TLfnFormat.

This also means that MULTIVALUED coverages can not be read anymore by fusion clients. In order to upgrade the tile store, the assets that were used to create these coverages should be refused to a RASTER COVERAGE.

Upgrade considerationLuciadFusion

Support for MULTIVALUED fusion coverages has been removed. This type of coverage was only used for GRIB files, but support for MULTIVALUED GRIB files had many limitations. Note that the fusion engine now supports the fusing of GRIB files to RASTER coverages, which is better supported.

This means that fusion clients will not be able to read existing MULTIVALUED coverages anymore. This can be resolved by re-fusing multivalued assets as RASTER coverages.

In the context of this change, these API changes were made:

The ELfnDataType#MULTIVALUED field was removed.
Several (deprecated) setAssetPart and addAssetPart methods were removed from TLfnRasterAssetMetadata.Builder. You can use the addAssetPart method that doesn't take any parameters instead.
The get/setParameter methods were removed from TLfnRasterCoverageMetadata.Builder. You can use the parameter methods instead.
Fields were removed from TLfnQuery.Property:
- RASTER_ASSET_parameter_name
- RASTER_ASSET_parameter_unit
- RASTER_COVERAGE_parameter_name
- RASTER_COVERAGE_parameter_unit
These were only useful in the context of multivalued assets and coverages.

Upgrade considerationLuciadFusion

The Apache HttpClient library has been updated to version 4.5.2.

Upgrade considerationLuciadFusion

The Fusion engine now uses TLcdNetCDFModelDecoder to fuse GRIB models. GRIB models that are decoded using TLcdNetCDFModelDecoder can now be fused to an IMAGE, as well as to a RASTER coverage. The latter adds out-of-the-box support for dimension filters (for time, elevation or other dimensions) to GRIB coverages when visualizing them. This also means that the Fusion engine now doesn't support models that were decoded using TLcdGRIBModelDecoder anymore.

Upgrade considerationLuciadFusion

Bug fixLuciadFusion

LCD-9055

TLcdScaleFormat used to return and accept Double.NaN. Setting Double.NaN as scale on a view could result in unexpected behavior. This has been fixed by adjusting the format to refuse this value.

Bug fixLuciadFusion

Fixed an issue where, in some cases, displaying point-sampled raster data caused exceptions.

Bug fixLuciadFusion

LF-1098

Windows network paths could be handled incorrectly when creating asset metadata from NetCDF or S57 catalogue data located.

Bug fixLuciadFusion

LCD-8952

Editing in a Lightspeed view no longer invalidates multi-object handles if an unrelated change has occurred in another part of the view. This includes adding and removing of layers, making layers visible and invisible, and changing the editing state of layers that are not being edited.

Bug fixLuciadFusion

LCD-9044

The following methods now also return a non-null result when the TLcdHasGeometryAnnotation was added on a super type of the domain object's data type:

ALcdShape#fromDomainObject
ALcdImage#fromDomainObject
ALcdBounds#fromDomainObject

Bug fixLuciadFusion

BlackLimeLookAndFeel: an indeterminate JProgressBar having its value set to the maximum now shows up. Before, such progress bars being in the indeterminate, finished state remained all black.

Bug fixLuciadFusion

LCD-8890

When the optional material attribute of a geometry element was missing a NullPointerException was thrown. Now a default styling will be applied, when there is no material defined.

Bug fixLuciadFusion

LCD-8906

Some combinations of expand, crop and resize operations resulted in exceptions for some image sizes.

ImprovementLuciadFusion

The WCS server now uses EPSG:4326 as fallback in case the data's native reference does not have an EPSG representation.

ImprovementLuciadFusion

LCD-8904

TLcdEPSGReferenceParser now supports coordinate references based on the China 2000 datum (CGCS2000).

Bug fixLuciadFusion

LCD-8911

ImprovementLuciadFusion

LCD-8797

TLspPinLineStyle.PinEndPosition now also has a CLOSEST_POINT_ON_EDGE position.

ImprovementLuciadFusion

TLspExternalView is a new ILspView implementation which can paint directly into an externally supplied OpenGL context (rather than creating a new context of its own). This is useful in cases where a Lightspeed view should be integrated with a non-Java application and windowing toolkit (e.g. a C++ application using Qt). The article How to integrate LuciadLightspeed in a C++ application on the Luciad Developer Platform provides more detailed information.

ImprovementLuciadFusion

LCD-8787

TLcdAdvancedMapRulerController#setAlwaysCreate allows creating measurements that start from existing measurements. If you don't set the flag, clicking or dragging an existing measurement edits that measurement. The javadoc has more information on how to add snapping behavior to this.

ImprovementLuciadFusion

LCD-8778

The WMS client's XML capabilities decoder now supports capabilities documents that contain style definitions at the end of a layer definition instead of at the standardized position defined by the WMS capabilities XML Schema.

Bug fixLuciadFusion

LCD-8766

Fixed an issue that caused the swipe and porthole controllers to appear jittery when zooming in and out in a 3D view.

Bug fixLuciadFusion

LCD-8805

Bug fixLuciadFusion

LCD-8528

A density layer would not update when there was a change on the filter that was configured on the layer.

Bug fixLuciadFusion

LCD-8516

ImprovementLuciadFusion

LCD-7591

GML encoding: improved the export of models that are not GML feature collections but do contain GML features (e.g. WFS models).

ImprovementLuciadFusion

BlackLimeLookAndFeel: the color of selected toggle buttons is now slightly more prominent.

ImprovementLuciadFusion

LCD-8441

You can now add new points to the beginning or end of ILcd2DEditablePolyline implementations (2D/3D polylines, arrows, buffers etc.) with a CTRL+left click to any location on the view by using TLsp2DPointListEditor. If the clicked point is closer to the first point than the last point of the shape, it will be inserted as the first point, otherwise it will be inserted as the last point.

ImprovementLuciadFusion

LCD-8451

DimensionalFilterManager was setting a model's filter value to the first possible value of the filter when the model is added to a view and if the model is the first model for that filtering dimension in the view. This was preventing you to set a filter value on the model and then display it with the same filtering value via the DimensionalFilterManager. To achieve that, you had to set the same filtering value after displaying the model. Now with this enhancement, the DimensionalFilterManager sets the value of the filter by getting it from the model if the model is the first model of that dimension in the UI.

Bug fixLuciadFusion

LCD-8483

Fix visualization of alpha channel for non 8-bit/component RGBA rasters.

Bug fixLuciadFusion

The ALcdMeasureProvider instances created by a


                           TLcdImageModelMeasureProviderFactory

The WCS client now automatically recognizes the GeoTIFF format 'GeoTIFFFLOAT32'.

ImprovementLuciadFusion

Google Earth Enterprise image repositories can now be used to create a non-tiled repository and serve the imagery through WMS. More information on how to decode Google Earth Enterprise image repositories can be found in the javadoc of TLcdGEEModelDecoder.

ImprovementLuciadFusion

ALspGLResource now has a default implementation for the destroy(ILcdGLDrawable) method. When extensions of this class call super.destroy, error checking is added to make sure no destroyed GL resources are used during painting. If they are, an exception is thrown. This avoids possible VM crashes.

ImprovementLuciadFusion

It is now possible to enable GetFeatureInfo requests for a WMS layer at the client side, even though the capabilities advertise that GetFeatureInfo requests are possible. See

TLcdWMSStyledNamedLayerWrapper#setQueryable(boolean)
TLcdSLDNamedLayer#setQueryable(boolean)

ImprovementLuciadFusion

TLspLayerTreeNode: a new constructor which accepts a model has been added.

ImprovementLuciadFusion

TLspLayerTreeNodeCellRenderer is a new extension of TLcdLayerTreeNodeCellRenderer specific for Lightspeed views. It implements the same behavior already present in TLcdGXYLayerTreeNodeCellRenderer, where layers are grayed out when they are outside their scale range.

ImprovementLuciadFusion

TLcdGXYLayerTreeNode: a new constructor which accepts a model has been added.

ImprovementLuciadFusion

LCD-7903

TLcdGXYRoundedPointListPainter: improved discretization for polygons crossing the boundaries of rectangular projections.

ImprovementLuciadFusion

TLspFusionVectorLayerBuilder will now use GeoSym styling for both bodies and labels when visualizing a VPF coverage. Previously, the GeoSym styling was only used for the body.

ImprovementLuciadFusion

LCD-8171

The TLsp2DPointListEditor no longer consumes mouse-wheel events in its creation handle.

The sample package samples.lightspeed.timeview contains a ready-to-use time slider component which has a Lightspeed view. You can add layers to it with data that has time information.
See TimeSlider javadoc for more details.

ImprovementLuciadFusion

LCD-5122

TLcdResizeableIcon now implements ILcdAnchoredIcon.

ImprovementLuciadFusion

LCD-7855

TLcdStatusEvent now has new factory methods to make it easier to report progress and messages. In addition, messages can now include a severity.

ImprovementLuciadFusion

LCD-2904

TLspViewNavigationUtil can now perform animated center operations.

TLcdOGCPropertyName has received a new convenience constructor that accepts a Java QName.

ImprovementLuciadFusion

LCD-7949, LCD-7306

To improve the event handling of TLcdWFSProxyModel, three existing methods have been reintroduced with an additional argument to specify an event type (ILcdFireEventMode):

setFilter(TLcdOGCFilter, int)
setCachingModel(int, int)
invalidate(int)

This enables users to explicitly trigger an event while invoking these methods, so that any listeners can be notified of changes to the model. A typical use case is to trigger a repaint when calling one of these methods.

ImprovementLuciadFusion

LCD-7959

TLcdWCSProxyModelDescriptor now uses the coverage's label as display name, because it is intended as a human-readable name for the coverage. If not available, the coverage's name is used, similar to the past.

ImprovementLuciadFusion

LCD-7957

TLcdWFSProxyModelDescriptor now uses the feature type's title as display name, because it is intended as a human-readable name for the feature type. If not available, the feature type's name is used, similar to the past.

ImprovementLuciadFusion

TLcdDimensionAxis.TIME_AXIS: a constant has been added representing a time axis, which is convenient when you are creating your own time-dependent models.

ImprovementLuciadFusion

LCD-3204

ALspEditable3DMesh can now contain texture coordinates. This allows you to provide the texture coordinates in a custom TLspShapeDiscretizer by overriding TLspShapeDiscretizer#discretizeSFCT().

ImprovementLuciadFusion

LCD-7611

TLcdWFSProxyModelDescriptor now provides information about the possible data types in the model. This information is accessible through the regular ILcdDataModelDescriptor methods getModelTypes() and getModelElementTypes().

ImprovementLuciadFusion

LCD-7917

The new TLcdGXYRotateController allows you to rotate GXY views.

ImprovementLuciadFusion

LCD-7918

Vendor-specific parameters included in URLs supplied to TLcdWCSClient, TLcdWFSClient, TLcdWMSClient or TLcdWMTSClient are now automatically used in all requests sent to the server. This supports use cases such as services requiring authentication through a proprietary token parameter.

ImprovementLuciadFusion

TLcdGXYShapeListPainter and TLcdGXYSurfacePainter now also implement ILcdGXYPathPainter. This also improves the out-of-the-box labeling support.

ImprovementLuciadFusion

TLcdGXYLabelPainter: a new method (setAntiAliased) has been introduced which allows to enable anti-aliasing. Anti-aliasing has been enabled by default.
The same has been done for the TLcdGXYPolygonLabelPainter, TLcdGXYPolylineLabelPainter, TLcdMapLonLatGridLayer, and TLcdMapGeorefGridLayer.

ImprovementLuciadFusion

LuciadFusion now supports fusion of vector data retrieved from an PostgreSQL PostGIS database.

ImprovementLuciadFusion

Bug fixLuciadFusion

Bug fixLuciadFusion

LCD-8138

Fixed a rare OutOfMemoryError when using an MGRS grid in a 3D Lightspeed view. This exception could occur when moving close to the terrain and tilting the camera.

Bug fixLuciadFusion

LCD-8238

Bug fixLuciadFusion

The WMTS client sometimes still showed error tiles in case of a tile not found (HTTP 404) response.

Bug fixLuciadFusion

LCD-6636

TLspShapeDiscretizer now correctly triangulates ILcdPolygons that are vertical (i.e. exactly perpendicular to the ellipsoid).

Bug fixLuciadFusion

LCD-4290

TLcdSHPModelDecoder: The TLcdDataModel generated for empty SHP files was incorrect. Now a TLcdDataModel is generated based on the properties defined in the DBF file, if available.

Upgrade considerationLuciadFusion

LCD-8198

The overlay panel of Lightspeed views, which typically contains the navigation controls or a scale icon, can now avoid full redraws in a number of scenarios. This makes it behave subtly faster, resulting in somewhat higher frame rates depending on the screen resolution and exact set-up. It may uncover bugs in client code that previously remained unnoticed. Should you experience a partially updating overlay, check out the documentation in ILspAWTView.getOverlayComponent. Most notably, samples classes HaloLabel, TouchInformationPanelController and PreviewerOnMapCustomizerFactory (Lucy) had to be adjusted.

Upgrade considerationLuciadFusion

Packaging for the sqlitej native library has changed. Instead of a single statically linked object, the library now dynamically links to sqlite3. Apart from there now being two native libraries, you should not be affected in any way by this change.

Upgrade considerationLuciadFusion

SpatiaLite has been updated to version 4.3.0. The decoder now also supports databases created with SpatiaLite 4.0.0 and above. Newly created databases will be in the 4.0.0 format and cannot be read by older versions of the decoder. For more information, see https://www.gaia-gis.it/fossil/libspatialite/wiki?name=switching-to-4.0.

Upgrade considerationLuciadFusion

LCD-8048, LCD-8054

TLspFrustum was made immutable to avoid potential concurrency issues. In order to do this, some of the methods were changed:

The computeFromModelViewProjectionMatrix() method was replaced with the factory method createFromModelViewProjectionMatrix().
The computeFromViewRectangle() method was replaced with the factory method createFromViewRectangle().
The return type of the getCorners() method was changed from ArrayList<TLcdXYZPoint> to List<ILcdPoint>. It now also returns an immutable List of points.

Upgrade considerationLuciadFusion

Model references that contain metadata (ILcdExtendedModelReference) are now only considered equal if they have the same axis ordering. This means for example that from now on "urn:ogc:def:crs:OGC:1.3:CRS84" (which is a lon-lat reference), and "urn:ogc:def:crs:EPSG::4326" (which is a lat-lon reference) are now considered different. The references in this example can be parsed using TLcdOGCModelReferenceParser.

Upgrade considerationLuciadFusion

LCD-5225

The vertex array renderer accessible using ILspView.getViewServices().getVertexArrayRenderer() no longer uses the standard gl_Color attribute. If you have written a custom painter that uses this vertex array renderer together with custom shader programs, you need to update your vertex programs to no longer use gl_Color, but use following construct:

      //declare custom attribute and uniforms
      attribute vec4 aLspColor;
      uniform vec4 uLspColor;
      uniform bool uUseAttribute;

      // ...

      void main() {
      // ...
      vec4 colorToUse = uUseAttribute ? aLspColor : uLspColor;
      // ...
      }

Any calls to ILcdGL.glColor4f (or equivalent) should be replaced with setting the uLspColor uniform on the shader. For instance:

      int[] currentProgramRet = new int[1];
      gl.glGetIntegerv(ILcdGL.GL_CURRENT_PROGRAM, currentProgramRet);
      int currentProgram = currentProgramRet[0];
      if (currentProgram > 0) {
      int uLspColor = gl.glGetUniformLocation(currentProgram, "uLspColor");
      if (uLspColor > 0) {
      gl.glUniform4f(uLspColor, fColor[0], fColor[1], fColor[2], fColor[3]);
      }
      }

Upgrade considerationLuciadFusion

It is now possible to pass query context parameters to the ALcdWMSProxy#createImageInputStream and ALcdWMSProxy#createFeatureInfoInputStream method directly. See TLcdWMSGetMapContext and TLcdWMSGetFeatureInfoContext. For GetFeatureInfo requests, this allows to specify which feature info format to use, and which layers should be queried, without the need to modify the ALcdWMSProxy object. This provides a better way to do getFeatureInfo request calls in a thread-safe manner.

The ALcdWMSProxy#createImageInputStream and ALcdWMSProxy#createFeatureInfoInputStream method are abstract, which means that custom implementations of this class will show a compile error. For wrappers, this can easily be resolved by delegating to the wrapped ALcdWMSProxy. For custom implementations, these new methods will need to be implemented. ALcdWMSProxy#createImageInputStream should pose no problems since no extra parameters were introduced. The implementation of the new ALcdWMSProxy#createFeatureInfoInputStream method will need to take the new arguments (i.e. the contents TLcdWMSGetFeatureInfoParameters) into account.

Upgrade considerationLuciadFusion

TLcdGeoJsonModelEncoder and the GML model encoders now format geodetic WGS84 lon-lat references with EPSG as authority as "CRS84" by default. This new behavior can be reverted, see TLcdOGCModelReferenceFormatter#setFormatEPSGLonLatWGS84AsEPSG4326() for more information.

Upgrade considerationLuciadFusion

The lcd_wms_client_earth.jar file was removed. This also means that a Maven artifact was removed. Dependencies on lcd_wms_client_earth.jar should be removed and replaced by a dependency on lcd_wms_client.jar.

Upgrade considerationLuciadFusion

LCD-7986, LCD-5592

ILspTexturedStyle now supports the use of ALsp2DTextureObject. To support this it now has a new getTextureObject method and the textureObject method was added to ILspTexturedStyle.Builder. This new functionality allows to use an OpenGL texture directly with an ILspTexturedStyle.

Upgrade considerationLuciadFusion

LCD-7395

The JOGL, JOCL, and GlueGen libraries have been updated to version 2.3.2+2-lcd. This is the same as the official 2.3.2 version of JOGL, with two exception. The first is a change for the Mac OS X platform that fixes following JOGL issues:

1277: GLCanvas content draws in wrong position when canvas moves after JFrame containing it is setVisible(true) on EDT
1299: warning when using JOGL on Mac OS X El Capitan
1306: Medium-weight tooltips are painted behind the GLCanvas
1307: GLCanvas is always drawn on top when using a JTabbedPane

Fusion is now more robust against WMTS services that use a data format that is not a supported MIME type.

ImprovementLuciadFusion

LCD-8087

LF-925

ImprovementLuciadFusion

LCD-7851

com.sun.media:clibwrapper_jiio
com.sun.media:jai_codec
com.sun.media:jai_imageio
javax.media:jai
javax.media:jai_core
javax.media.jai:mlibwrapper_jai
org.jogamp.jogl:jogl-all-main
org.jogamp.jocl:jocl-main
org.jogamp.gluegen:gluegen-rt-main

ImprovementLuciadFusion

LF-870

Fusion of WMTS: improved the performance when fusing a WMTS layer using a clipping shape.

Bug fixLuciadFusion

The Fusion server sample was initialized with an incorrect classpath, leading to a conflict between Luciad libraries residing in the lib and in the distrib/ogc folder.

Bug fixLuciadFusion

LF-968

Fusion is now more robust against WMTS services that return empty tiles instead of 404 "Tile not found" and WMTS services that advertize much more tile matrices (levels) than they actually have tiles for.

Bug fixLuciadFusion

LF-867

Fixed a bug when fusing a WMTS layer into a coverage with a reduced bounding box, which caused all of the source data to be squashed inside the reduced bounding box rather than being clipped to it.

ImprovementLuciadFusion

LCD-7748

Native libraries are now cached to $XDG_CACHE_HOME on Linux, in accordance with the XDG Base Directory specification. If the variable is not set, $HOME/.cache will be used.

ImprovementLuciadFusion

LCD-7754

The WMTS model decoder now automatically detects empty tiles and empty tile matrix sets.

Detection of empty tiles works around WMTS services that use an empty tile image instead of a 404 when a tile is not found.
Detection of empty tile matrices (levels) works around WMTS services that advertize more tile matrices than they actually have tiles for.

Bug fixLuciadFusion

ImprovementLuciadFusion

LCD-7434

The TLcdGeoJsonModelEncoder can now encode domain objects that are not an ILcdShape, but which do implement ILcdDataObject and the data type has a TLcdHasGeometryAnnotation. The geometry property in this case must be one of the supported shapes.

ImprovementLuciadFusion

LCD-7133

It is now possible to use textured line and fill colors when using TLspComplexStrokedLineStyle. To support this, new lineTexture and fillTexture methods were added to the stroke builders in ALspComplexStroke. This is demonstrated in the lightspeed.style.strokedline sample, in the Airspace layer.

ImprovementLuciadFusion

LCD-7471

It is now possible to customize the angle threshold that is used to determine if strokes are omitted at a corner or wrapped around it. See TLspComplexStrokedLineStyle.Builder#shapeAngleThreshold.

ImprovementLuciadFusion

LCD-7275, LCD-4106

Added ability for TLspCreateController to go to the next step in creation, without explicitly finishing or committing the creation of the shape. This allows you to perform changes to your newly created shape (such as due to a UI event), without interrupting the creation process.

ImprovementLuciadFusion

LF-874

Now each asset of a coverage can have its own input SLD file instead of one SLD file per coverage as before.

ImprovementLuciadFusion

The GL resource cache for Lightspeed views now has better default behavior regarding its maximum size. For most practical purposes, the size no longer needs to be specified. See TLspViewBuilder.glResourceCacheSize for more information.

ImprovementLuciadFusion

TLspViewPaintingHints offers a way to ensure peak performance or quality, taking into account the currently installed GPU.

ImprovementLuciadFusion

LF-871

For interoperability with reverse proxies, the links to the online resources advertized in the capabilities have changed when both server and client are running LuciadFusion V2016.0 or higher. The path of the URI is now relative to the servlet mapping instead of relative to the application server root: by default online resources are now advertized with an empty URI "" instead of "/LuciadFusion/lts". For backwards compatibility, the behavior towards older clients remains as it was before. If you're running a LuciadFusion server behind a reverse proxy and want to take advantage of this feature, you should make sure both client and server are up-to-date.

ImprovementLuciadFusion

LCD-7354

The multidimensional API now includes an interface ILcdMultiDimensionalModel for filtering dimensional data. It is typically implemented by dimensional models such as NetCDF, LuciadFusion raster and NVG models. Even when models implement the interface, implementations may still indicate that particular instances do not support dimensional filtering by returning the empty filter TLcdDimensionFilter.EMPTY_FILTER upon ILcdMultiDimensionalModel.getDimensionFilter().

The new multidimensional API replaces some legacy, format-specific APIs which have been deprecated. Examples of such APIs are get/setDate on ASTERIX and NVG models. A notable difference with these legacy APIs is that the multidimensional models must no longer do any snapping of elements to filters. In case no elements pass a filter, the result must be empty. Snapping can now be applied to any model, using TLcdDimensionFilter#createSnappingFilter.

The following enhancements were also done in this context:

TLcdDimensionInterval.Relation and relationTo have been removed and replaced with TLcdDimensionInterval.overlaps.
TLcdDimensionInterval now documents the use of null as min or max to indicate that it is unbounded at one or both ends. The methods TLcdDimensionInterval.union, overlaps and compareTo know how to deal with unbounded intervals.

ImprovementLuciadFusion

LuciadFusion is extended with a new asset and coverage type RASTER, which allows preservation of all the source data's multi-dimensional and multi-band information. This can be used to fuse NetCDF data whilst preserving the multi-dimensional nature of the source data. This allows clients to treat fused NetCDF data as if it were regular NetCDF data, using the imaging API. Such fusion models only support the imaging API, they no longer support the raster (tile set) API. The new RASTER data type thus replaces the legacy data types IMAGE, ELEVATION and MULTIVALUED.

The tile format for RASTER coverages is "image/tiff". Every possible combination of possible values for every dimension will be stored as a separate page of a multi-page TIFF file.

The RASTER data type can also be used to preserve the multi-band nature of source data.

'Preservation of multi-dimensional and multi-band nature' does not imply 'preservation of source resolution without any resampling'. Even when preserving multi-dimensional and multi-band nature, fusion may yet resample the source data using bilinear interpolation and warping to fit the source raster into the raster defined by the coverage's bounds, layout and tile resolution.

Fusing coverages as RASTER is thus a lot more powerful than fusing coverages as IMAGE, ELEVATION or MULTIVALUED. There could however be reasons to not use RASTER:

When you want to offer the coverage as WMTS, you need to use IMAGE. RASTER coverages do not support WMTS.
Preserving the multi-dimensional samples is overhead if you don't need them. When you're only interested in a single 'default' combination of dimensional values, and you want to save bandwidth, you're probably better off using IMAGE.
RASTER coverages don't have a compact format for elevation. If you want to use the compact format for elevation to preserve bandwidth, you should use ELEVATION.
When you're fusing GRIB data, you'll still have to use MULTIVALUED. GRIB source data cannot be fused as raster, because the source format does not support the imaging API. There is no other good reason to still use MULTIVALUED.

The model structure for a decoded raster coverage is this:

The model has a TLfnRasterTileStoreModelDescriptor, which is also an ILcdImageModelDescriptor.
If the model has multi-dimensional information, it is also an ILcdMultiDimensionalModel.
Even if it doesn't have any multi-dimensional information, the model is still ILcdMultiDimensionalModel, but it has null for filter parameters.
The model adheres to the imaging API. You can get the current image usingALcdImage.fromDomainObject(modelElement).
The ALcdImage instances themselves are immutable, so when you update the dimensional filter, the reference will be updated with a new instance.

ImprovementLuciadFusion

LCD-7345

ALcdWeakSelectionListener, ALcdWeakLayeredListener, and ALcdWeakPropertyChangeListener can now also be used on ILcdLayerTreeNode as hierarchy listeners.

ImprovementLuciadFusion

LCD-7344

The new class TLcdDeleteSelectionAction allows removing selected objects with undo-redo support.

ImprovementLuciadFusion

TLcdIconFactory has been added to the API, which is a class containing factory methods for ILcdIcon instances. This class allows to create icons for a string identifier, and introduces the concept of "themes": depending on the theme, the returned icon for a certain identifier will be different. Consult the class javadoc for more information.
TLcdIconFactory is the preferred way to create icons based on the resources in the release. Therefore we deprecated the TLcdGUIIcon and TLcdShapeIcon classes in favor of the TLcdIconfactory class.

ImprovementLuciadFusion

TLspPortholeController visually compares two layer sets by exposing one set of layers through a porthole in the other set. The porthole is a rectangular region that follows the mouse. You can customize this controller or use it programmatically. The controller is available in the decoder sample.

ImprovementLuciadFusion

LCD-3901

TLcdRangeSlider now supports Nimbus Look and Feel.

ImprovementLuciadFusion

CSVModelDecoder is a customizable model decoder for point data in CSV files, available as sample code.

ImprovementLuciadFusion

LuciadFusion is extended with support for all raster formats that can be decoded using the GDAL decoder.

ImprovementLuciadFusion

LuciadFusion is extended with support for multi-dimensional NetCDF data, which can be fused to a raster or image coverage. The format ID is defined by ALfnFormat.NETCDF_FORMAT_ID.

Fusing NetCDF data to a raster coverage preserves the multi-dimensional and multi-band nature of the source data. The dimensional information of the source data can be accessed using RasterAssetPart.getDimensions() and RasterAssetPart.Builder.dimensions(). You can restrict the dimensional information to a subset of the source data's using TLfnRasterCoverageMetadata.getDimensions() and TLfnRasterCoverageMetadata.Builder.dimensions().

Fusing NetCDF data to an image coverage renders RGB images from the multi-dimensional source data, and requires a dimensional filter of the same sort that you would use when visualizing the multi-dimensional data. You can define a dimensional filter, consisting of a specific combination of a single dimensional value for each dimension, using TLfnRasterCoverageMetadata.getDimensions() and TLfnRasterCoverageMetadata.Builder.dimensions().

ImprovementLuciadFusion

LCD-7266

TLcdGXYAsynchronousLayerWrapper now logs a warning if it wraps an unsupported layer.

ImprovementLuciadFusion

LCD-7264

Improved TLcdGXYCompositeController robustness when a delegate terminates the controller.

ImprovementLuciadFusion

A 3D arc band shape was introduced; ILcd3DArcBand. This shape represents a subvolume of a sphere. It extends from a minimum radius to a maximum radius from the center point. It is further delimited by a start angle and an arc angle in the horizontal plane and a pitch start angle and a pitch arc angle in the vertical plane. It has two implementations; TLcdLonLatHeight3DArcBand and TLcdXYZ3DArcBand. This shape can only be visualized in a Lightspeed view.

ImprovementLuciadFusion

Support was added for cartesian (XY) grid. They can be displayed in

a GXY view using TLcdXYGridLayer. This is demonstrated in the gxy.grid sample.
a Lightspeed view with the new TLspXYGridLayerBuilder. This is demonstrated in the lightspeed.grid sample.

Cartesian grids are useful in combination with grid references, but can also be used for non-georeferenced views.

ImprovementLuciadFusion

LCD-7137

ALcdModel now has support to debug missing or wrong locks. Please refer to its class comment for instructions on how to enable it.

ImprovementLuciadFusion

LCD-7159

TLcdGXYPanController, TLcdGXYSelectController2 and TLcdGXYEditController2 now have a new method: setAWTFilter. This allows specifying the mouse events they should respond to. You can easily create such filters using the new TLcdAWTEventFilterBuilder class. Lightspeed users can also use that class instead of TLspAWTEventFilterBuilder, which has been deprecated.

ImprovementLuciadFusion

The printing samples now show how to add a compass icon to the printout.

ImprovementLuciadFusion

LCD-7659

LCD-6939

Fixed an issue preventing the correct decoding of XML files containing a union of unions.

Bug fixLuciadFusion

Closing the OutputStream object in a custom implementation of ILcdWMSFeatureInfoRequestEncoder or ILcdGXYViewEncoder resulted in a duplication of the result. This bug has been fixed.

Upgrade considerationLuciadFusion

LCD-7444

ArcSDE has been discontinued by Esri as of ArcGIS 10.3.

See these links for more information:

http://downloads2.esri.com/support/TechArticles/W34229_DEPRECATION_PLAN_FOR_ARCGIS_10_4_and_10_3_1__082015.pdf
http://blogs.esri.com/esri/supportcenter/2015/02/11/where-is-the-install-for-arcsde-10-3/

Therefore the ARC_SDE_VECTOR_FORMAT_ID and ARC_SDE_RASTER_FORMAT_ID constants in ALfnFormat have been deprecated.

As an alternative to the ArcSDE connector, LuciadLightspeed offers direct connectors for the spatial database back-ends supported by ArcSDE/ArcGIS: SQL Server, Oracle Spatial, DB2, Informix, PostGIS or SAP Hana.
You can also use any of the OGC services (WMS, WFS, WCS).
Contact Luciad Support for more information on how to obtain and use these connectors.

Upgrade considerationLuciadFusion

To enable WCS request parameter access when customizing request-related operations (data decoding, data encoding), a few API changes have been introduced:

A new class TLcdWCSRequestContext has been introduced to access request context parameters such as the original HTTP request and the requested coverage(s).
The signature of the method ILcdWCSModelEncoderFactory#createModelEncoder(ILcdModel, ILcdOutputStreamFactory, String) has been changed into ILcdWCSModelEncoderFactory#createModelEncoder(ILcdModel, ILcdOutputStreamFactory, String, TLcdWCSRequestContext).
The signature of the methods in ILcdCoverageOfferingList have been changed by means of the introduction of an extra argument of type TLcdWCSRequestContext.
The methods ILcdCoverageOfferingList#getCoverageOffering(int, TLcdWCSRequestContext) and ILcdCoverageOfferingList#getCoverageOffering(String, TLcdWCSRequestContext) can now throw an IOException.

The change will impact WCS implementations that implement ILcdWCSModelEncoderFactory and/or ILcdCoverageOfferingList. Affected implementations can simply update the signature ignore the new TLcdWCSRequestContext parameter.

Upgrade considerationLuciadFusion

The following methods/classes in ALcdProjection were removed:

ALcdProjection.bisectInterval class
findBisectLonIntervals()
findBisectLatIntervals()
bisectLonInterval()
bisectLatInterval()

These were not meant to be used or extended.

Upgrade considerationLuciadFusion

To enable the integration of the Luciad imaging API and its TLcdGXYImagePainter for SLD raster styling in GXY views, the dependency on ILcdRasterPainter has been removed from the API. More specifically:

ILcdSLDRasterPainterConfigurator and its implementation TLcdRasterPainterConfigurator have been removed.
The factory method TLcdSLDSymbolizerPainterFactory#createRasterPainterConfigurator has been removed.
The javadoc of the factory method TLcdSLDSymbolizerPainterFactory#createRasterPainterProvider no longer requires an ILcdRasterPainter as return type. Any painter provider capable of rendering rasters is sufficient.

This only impacts users that manually interacted with ILcd/TLcdRasterPainterConfigurator. If this is the case, raster painter customization should be moved to TLcdSLDSymbolizerPainterFactory#createRasterPainterProvider.

Upgrade considerationLuciadFusion

LCD-7413

The Java Servlet dependency has been upgraded from version 2.5 to 3.0. Consequently, an application server or servlet container with support for Java Servlet 3.0 or higher is now required for deployment of the server - for instance, Tomcat 7 or higher. The impact of this is expected to be low since Java Servlet 3.0 is widely adopted by application server and servlet container products for over 6 years. The servlet container delivered with the Luciad products, Jetty 8, already supports Servlet 3.0

Upgrade considerationLuciadFusion

LF-875

The Java Servlet dependency has been upgraded from version 2.5 to 3.0. Consequently, an application server or servlet container with support for Java Servlet 3.0 or higher is now required for deployment of the server - for instance, Tomcat 7 or higher. The impact of this is expected to be low since Java Servlet 3.0 is widely adopted by application server and servlet container products for over 6 years. The servlet container delivered with LuciadFusion, Jetty 8, already supports Servlet 3.0

Upgrade considerationLuciadFusion

LF-816

Solaris 10+ was dropped from the list of supported platforms for LuciadFusion.

Upgrade considerationLuciadFusion

TLfnTileStoreModelDescriptor no longer implements ILcdEarthModelDescriptor. TLfnRasterTileStoreModelDescriptor no longer implements ILcdImageModelDescriptor, rather the concrete internal implementation classes do, but only when applicable:

ILcdImageModelDescriptor if the model follows the imaging API. This is the case when the coverage type is RASTER.
ILcdEarthModelDescriptor if the model follows the tile set API. This is the case when the coverage type is MULTIVALUED and in some cases also when it is ELEVATION.
Both if the model is a hybrid following both these APIs. This is the case when the coverage type is IMAGE and in in most cases also when it is ELEVATION.

This means that TLfnRasterTileStoreModelDescriptor cannot be assigned to any of the aforementioned interfaces without a cast. Model descriptors of specific models will still implement these interfaces, so you can fix any compile errors by doing a type check on the model descriptor before casting.

Upgrade considerationLuciadFusion

LCD-7352

The names of some classes and methods of the multi-dimensional API have changed. You may need to fix compile errors accordingly.

ILcdDimension replaces ILcdDimensionAxisValues.
TLcdDimension replaces TLcdDimensionAxisValues.
ILcdMultiDimensional.getDimensions() replaces ILcdMultiDimensional.getDimensionAxisValues().
ILcdDimension.getValues() now returns a bounded and sorted List containing no duplicates instead of an impractical unboundedIterable.

Upgrade considerationLuciadFusion

LCD-7055

The signature of the ALspLabelLocationProvider methods was modified to take an ILspLabelingAlgorithm.LabelContext and an ILspView as method parameter instead of a TLspContext. This makes it possible for implementations of ALspLabelLocationProvider to retrieve context information such as the elevation mode, or the previous label location.

Implementations of ALspLabelLocationProvider will now generate a compile error that can be resolved by modifying the signature accordingly. If TLspContext was used, it can now be retrieved using the following line of code:

      TLspContext aContext = aLabelContext.getContext(aLabel.getLayer(), aView);

ImprovementLuciadFusion

LCD-7612

The WMTS client has been made more flexible against WMTS XML capabilities that are not fully compliant against the OGC OWS Common 1.1 XML Schema used by WMTS. More specifically, a correct order of XML elements is now no longer required.

Bug fixLuciadFusion

TLspLayer#query: Using TLspPaintedObjectsQuery with viewBounds null could return more objects than actually painted.

Bug fixLuciadFusion

LCD-7240

Bug fixLuciadFusion

Bug fixLuciadFusion

LCD-7431

The OGC spatial filter now automatically determines the spatial property when the <BBOX> element does not specify a <propertyName> element. The spatial property is determined from the data type:

If the data type has a TLcdHasGeometryAnnotation, the spatial property is defined by it.
If not, it is the property of type ILcdShape.
In case there are multiple such properties, an appropriate exception report is generated. This is consistent with the OGC Filter 1.1.0 specification which states that a <propertyName> element is required when there are multiple spatial properties.

Bug fixLuciadFusion

The WMS client sample class ProxyModelFactory did not properly handle WMS servers that only advertise a single root WMS layer.

Bug fixLuciadFusion

LCD-7423

Fixed potential NullPointerException in the KML styler for lightspeed views that could occur when visualizing placemarks with malformed altitude modes.

Bug fixLuciadFusion

LCD-7321

Fixed issue where networklinks containing "onExpire" refreshmode links would not get loaded correctly unless manually updated.

Bug fixLuciadFusion

LCD-7125

Ensured that the TLspPointSetHandle does not fire unnecessary FINISHED interaction state events when moving or dragging the mouse.

ImprovementLuciadFusion

The sample class WFSFeatureIDRetriever now supports retrieving the id of data objects with a primary key annotation (TLcdPrimaryKeyAnnotation).

ImprovementLuciadFusion

LCD-7428

Made some changes to the WFS client for the sake of interoperability with ArcGIS WFS servers:

Spaces in URLs are now escaped as "%20" instead of '+'. Both are valid according to the URI specification, but ArcGIS server can't handle '+' correctly, at least not when it occurs as value of an outputFormat such as "text/xml;+subtype=gml/3.1.1" (escaped).
Recognition of output formats has been made more lenient towards casing differences: both "subType" and "subtype" are now recognized in outputFormat parameters such as "text/xml; subType=gml/3.1.1".
Recognition of output formats has been made (even) more lenient towards alternative names for formats: "text/xml; subType=gml/3.1.1/profiles/gmlsf/1.0.0/0" is now for example also recognized as GML Simple Features Profile.

Bug fixLuciadFusion

The elapsed time continues after a stop/restart of a job, instead it continues from the last checkpoint, in accordance with the progress itself.
The elapsed time continues after disconnecting and reconnecting the DCM to a remote fusion server.

ImprovementLuciadFusion

LF-814

Fusion now picks up an SLD style file next to the data file by default when building a coverage using any of the concrete subclasses of ALfnCoverageMetadata.Builder. This benefits the following use cases:

The Fusion Engine automatically applies the SLD style when fusing vector as image.
The WMS Fusion Server automatically applies the SLD style when serving coverages with asset sources in Tile Store, including the specific case of non-tiled coverages.
The Fusion Client automatically applies the SLD style when visualizing a vector coverage.
The preview layer in the DCM uses the SLD style, but beware that the map layer (when opening the file as a layer) does not.

LF-774

Security improvements:

The server no longer exposes the stack trace of the internal server error to the client.
The server is now more robust against malicious attempts to escape the confinements of its directories.

ImprovementLuciadFusion

TLcdGXYEditController2 now also displays a preview of the object's labels during translation.

ImprovementLuciadFusion

The interpolation mode set to a TLcdWCSProxy can now be retrieved by invoking getInterpolationMethod().

ImprovementLuciadFusion

LCD-1137

The sample class samples.ogc.server.Main has been updated with a -fromsource mode to easily start the OGC sample services in an IDE, directly from the source code.

ImprovementLuciadFusion

LF-778

The WCS service in the LuciadFusion Data Server now supports version 1.1.0 and 1.1.1 of the OGC WCS protocol, next to the already supported version 1.0.0.

ImprovementLuciadFusion

Slightly improved the rendering of filled shapes crossing the projection boundaries.

ImprovementLuciadFusion

LF-746

The server by default no longer saves its statistics in a fusion.stats file. Saving the statistics can still be enabled in the web.xml if desired.

ImprovementLuciadFusion

The WCS server now supports point-sampling mode. The appropriate sampling mode is not configurable, it is automatically chosen based on the sampling mode of the data being served:

Image data, such as GeoTIFF areal imagery, is typically area-sampled.
Elevation data, such as DTED or GeoTIFF, is typically point-sampled.

When using the default GeoTIFF format, the response to a GetCoverage requests is a GeoTIFF with the appropriate tag set to 'RasterPixelIsPoint' or 'RasterPixelIsArea'.

ImprovementLuciadFusion

The WCS server now supports the "bilinear" interpolation method in addition to "nearest neighbor", and advertises this in the coverage offering. Bilinear interpolation usually yields better results than nearest neighbor interpolation, especially when requesting coverages in a much higher resolution than the native one (oversampling).

ImprovementLuciadFusion

TLcdKML22ModelEncoder is a model encoder to export a KML model into a kml file. Its main purpose is to save models made programmatically. TLcdKML22ModelEncoder has several limitations :

This model encoder doesn't export non KML models into KML files.
This model encoder does not support kmz extension.
This model encoder was not made for round-trips and KML models don't have a reference to this model encoder.
Relative network links will not be modified and this model encoder will not copy their target contents.

ImprovementLuciadFusion

WMS models decoded with TLcdOGCWMSProxyModelDecoder will now by default use image/png and transparency as image exchange format settings, instead of image/jpeg with a background color.

ImprovementLuciadFusion

LCD-1722

Lighting for 3D icons is now also supported in a 2D view.

ImprovementLuciadFusion

TLcdMGRSFormat now provides an enumeration to indicate the precision used to format MGRS or UTM/UPS strings. The following methods have been deprecated in TLcdMGRSFormat:

getNumberOfDigits(), getPrecision() should be used instead.
setNumberOfDigits(int aNumberOfDigits), setPrecision(FormatPrecision aPrecision) should be used instead.

ImprovementLuciadFusion

TLsp3DIconStyle: when using a 3D icon containing textures, the textures will now be compressed. This reduces the amount of memory that is needed on the GPU for showing that 3D icon.

ImprovementLuciadFusion

LCD-6587

Added built-in HTTP Basic Authentication support to TLcdOWSHttpTransport: constructors have been added to supply username and password for authentication at an OGC server.

ImprovementLuciadFusion

KML balloons now support dark Nimbus look and feels in that the balloon background remains white, to be sure text is always readable.

ImprovementLuciadFusion

LuciadFusion now supports point-sampled elevation data. By default, the sampling mode of the assets is preserved in the coverage, but it can be set manually as well. Point-sampled and area-sampled assets can be mixed into either a point-sampled or area-sampled coverage. The interpolation of values from the assets' rasters into the coverage's raster takes care of converting the values from assets that have a different sampling mode than the coverage.

You can inspect the sampling mode of coverage with TLfnRasterCoverageMetadata.getSamplingMode().
A coverage decoded as a LuciadFusion model offers its data as both an ILcdEarthTileSet and an ALcdImageMosaic, so that it integrates with both the tile set API and the imaging API. However, only the imaging API can accurately visualize point-sampled data. Due to the lack of a point-sampled notion in the tile set API, the data will always be interpreted as area-sampled, resulting in inaccuracies such as pixels which are shifted slightly out of place. When working with point-sampled data, it is thus strongly recommended to use the imaging API. The tile set API is only supported for backwards compatibility.
Point-sampled coverages have tile width and height +1 compared to their area-sampled equivalent with the same pixel density (resolution).

ImprovementLuciadFusion

LCD-6420

TLfnTileStoreModelDecoder has been adapted for integration with the imaging API. It produces domain objects that extend ALcdImageMosaic as well as implement ILcdEarthTileSet.

ImprovementLuciadFusion

Collada models referenced in KML files can now be visualized in layers build by TLspKML22LayerBuilder.

Collada is a standard for encoding 3D geometries. It is used as the format for 3D objects in KML. The standard is an official Khronos Standard, supported by major companies such as ATI and NVIDIA. It is also being supported in may 3D modelers and game engines and in Google Earth (through KML). See https://www.khronos.org/collada/ for more information.

Opening a KML file containing Collada 3D objects on a Lightspeed view will show the Collada data. An example use-case is a KML file referring to a set of Collada files representing the buildings of a city.

When opening a KML file containing a Collada model on a GXY view, only the bounds of the Collada model will be shown.

ImprovementLuciadFusion

LuciadLightspeed can now visualize Collada models.

Collada is a standard for encoding 3D geometries. It is used as the format for 3D objects in KML. The standard is an official Khronos Standard, supported by major companies such as ATI and NVIDIA. It is also supported in many 3D modelers and game engines and in Google Earth (through KML). See https://www.khronos.org/collada/ for more information.

The TLsp3DIconStyle class now offers a new method to use a Collada file as icon style. See the TLsp3DIconStyle.Builder#icon(String) method for more information.

This is typically used to style moving objects with for example an airplane, a car or a vessel. The TLsp3DIconStyle class javadoc contains more information on this.

LuciadLightspeed supports Collada data in KML files as well. Consult the KML release notes and KML developer guide for more information.

ImprovementLuciadFusion

LCD-6474

TLcdDTEDDirectoryModelDecoder now attempts to automatically detect the bounds of the available data. You can disable this using TLcdDTEDDirectoryModelDecoder.setAutoDetectBounds(false).

ImprovementLuciadFusion

LCD-6483

The default color scheme for elevation data was enhanced to have less saturated colors that are perceived more equally. The new color scheme is available from TLcdColorModelFactory and TLcdDTEDColorModelFactory.

Should you still need the old color scheme, here is a code snippet to create it:

      TLcdDTEDColorModelFactory factory = new TLcdDTEDColorModelFactory();
      factory.setLevels(new double[]{-16000,-8000, -4000, -2000, -1000, 0, 0.1, 100, 200, 300, 400, 500, 600, 700, 800,
      900, 1000, 1100, 1200, 1300, 1400, 2500, 3500});
      factory.setColors(new Color[]{ new Color(0x000000), new Color(0x0000ff), new Color(0x00c0c0), new Color(0x80c0c0),
      new Color(0xa0e0e0), new Color(0x8c96d2), new Color(0x55793d), new Color(0x679349), new Color(0x75a552), new
      Color(0x84b264), new Color(0xedd283), new Color(0xf7d865), new Color(0xf2cd60), new Color(0xedb54f), new
      Color(0xe7aa50), new Color(0xe59547), new Color(0xe56c35), new Color(0xc88c3d), new Color(0xac8533), new
      Color(0xb48352), new Color(0x9a4e2e), new Color(0x909090), new Color(0xffffff)});
      ColorModel colorModel = factory.createColorModel();

Depending on how you visualize your data, you have to set the color model to a painter or a style. See ILcdRasterPainter.setColorModel or TLspRasterStyle for example.

ImprovementLuciadFusion

LCD-4550

TLcdSymbologyDateFormat now supports custom formats. In addition, TLcdSymbologyDateFormat#parse(String) accepts strings with or without spaces, and strings with or without seconds, regardless of the value of the isWithSeconds property.

ImprovementLuciadFusion

LCD-6471

TLspRasterLayerBuilder by default builds layers whose styler implements ILspCustomizableStyler.

ImprovementLuciadFusion

LCD-4544

Balloons created via ALcdBalloonManager can be closed by pressing ESC key.

ImprovementLuciadFusion

LCD-6344

The following classes and interfaces have been added, facilitating the use of weak listeners. Consult the javadoc of those new classes and interfaces for more information:

Property changes: ILcdPropertyChangeSource and ALcdWeakPropertyChangeListener
Model changes: ALcdWeakModelListener
Change events: ALcdWeakChangeListener
Selection changes: ALcdWeakSelectionListener
Layered changes: ALcdWeakLayeredListener
Status changes: ALcdWeakStatusListener

LF-767

Added a keep-alive mechanism to replication and import/export protocols. Keep-alives kick in after 15s of no connection activity, with an interval of 15s. This prevents the client from timing out in case the operation takes a long time to respond. Old clients will throw upon these keep-alives, so you should upgrade all clients before upgrading your servers. When import/export and replication remain within the keep-alive interval, no keep-alives are used and the protocol remains backwards compatible, but there is no way to guarantee this up front. Affected operations:

Import/export
Replication

Use cases that benefit from the new keep-alive mechanism:

Replication of large coverages with an AOI, where a lot of tiles are skipped, resulting in long periods of connection inactivity.
Scheduling of multiple import/export jobs, where jobs need to wait for others to finish.

Upgrade considerationLuciadFusion

Updated the version of the jai_imageio library. The new version includes fixes a native memory leak when encoding tiffs using the deflate algorithm.

Upgrade considerationLuciadFusion

ILcdOpenFlightNode now extends from ILcd3DMeshNode. Any custom implementations of this interface will have to implement this interface.

Upgrade considerationLuciadFusion

The TLspMesh3DIcon#paint() method has been made final. In case you have overwritten this method, you will get a compile error. The behavior of this method has changed, so that any GL calls made before this method will have no effect on the mesh rendering (e.g. by using a wrapper method).

Upgrade considerationLuciadFusion

LCD-6614

When using SVG based point symbolizers, the width and height of the created SVG icon is now set by width and height of the source SVG file.

Upgrade considerationLuciadFusion

The LuciadFusion API was simplified to allow no more than a single coverage per model. It is no longer possible to decode multiple coverages per model. You may need to adjust your custom code:

Callers of TLfnTileStoreModelDecoder.decode need to be adjusted to match the method signature. Use a single String instead of aString[].
Callers of ALfnTileStoreModel.setCoverageIds need to be adjusted to use setCoverageId instead.
Callers of TLfnTileStoreModelDescriptor.getCoverageMetadatas or TLfnTileStoreDataSource.getCoverageMetadatas need to be adjusted to use getCoverageMetadata instead.
Custom extensions of any of the aforementioned classes need to be adjusted to match the new method signatures. Implementations should be adjusted to work with a single coverage ID instead of multiple ones.

There are almost no practical use cases for allowing multiple coverages per model. In case you need it, you can still do it manually:

Decode all the relevant coverages into their own models.
Get theILcdEarthTileSetCoverages from theILcdEarthTileSets of the separate models, and combine them into a newILcdEarthTileSet. Beware that you can only do this if their coverage structures match.
Put the combined ILcdEarthTileSet into a newILcdModel.

LCD-6614

Bug fixLuciadFusion

TLcdUTMUtil: using -1 as numberOfDigits could result in invalid UTM Strings. Also, trying to parse UTM strings with a negative coordinate now throws an exception as expected.

Bug fixLuciadFusion

LCD-6585

TLcdEPSGReferenceFormatter now throws IllegalArgumentException rather than ClassCastException, when formatting an unknown reference, as stated in the javadoc.

Bug fixLuciadFusion

LCD-6582

Raster layers with type BACKGROUND and ALcdImage domain objects containing elevation data were not rendered correctly.

Bug fixLuciadFusion

LCD-5918

In GXY views, SVG icons which are linked as external graphics from an SLD stylesheet, and which have a width or height specified in a unit of measure that corresponds to a real-world distance such as mm, cm, or in, are now drawn so that those dimensions correspond to actual distances on the map. A practical result is that the icon's size on the screen will change as the scale of the map changes.

Bug fixLuciadFusion

LCD-6577

LCD-4326

Some editors can change their creation behavior to use free-hand drawing. The affected editors are:

TLsp2DPointListEditor
TLspShapeEditor
TLspSurfaceEditor
TLspCompositeCurveEditor
TLspGeoBufferEditor

ImprovementLuciadFusion

LCD-6311

The SQLite additional component no longer depends the public domain ForkJoin jsr166y-20130109.jar, since the ForkJoin framework is now part of Java since 1.7.

ImprovementLuciadFusion

An abstract wrapper class ALfnTileStoreWrapper was added to the API to facilitate the development of custom ALfnTileStore implementations that wrap another instance.

ImprovementLuciadFusion

To allow user data on any resource, the hierarchy of resource classes was now completed to mimic that of their metadata:

ALfnResource (new)
ALfnTheme (new)
ALfnAsset
ALfnCoverage

The user data API is primarily intended for internal use by replication.

The asynchronous APIs of the resources has been further developed to replace ILfnFailureHandler and its extensions with the more user-friendlyILfnCallback. In this respect, a new extension ILfnProgressCallback was added for long-running asynchronous tasks that report intermediate progress.

ImprovementLuciadFusion

TLcdEarthArrowIcon now doesn't paint an icon anymore when the STRENGTH_2D Parametrization is used and both parameters are 0.

ImprovementLuciadFusion

On Windows systems with NVidia GPUs, Lightspeed now automatically disables the "threaded optimization" setting in the NVidia drivers. This setting, when enabled, has been known to cause severe performance problems for LuciadLightspeed. To prevent Lightspeed from modifying the driver settings, set the system property com.luciad.view.opengl.binding.retainNVIDIAThreadedOptimizationsSetting.

ImprovementLuciadFusion

The JSP-based front-end delivered with the Data Server sample has been replaced by a new JavaScript-based front-end that gives access to the various services and example requests. This also removes the JSP dependency from the sample.

ImprovementLuciadFusion

LCD-1097

The JSP-based front-end delivered with the OGC web services sample has been replaced by a new JavaScript-based front-end that gives access to the various services and example requests. This removes the JSP dependency from the sample.

ImprovementLuciadFusion

LCD-1097, LCD-1103

The JSP-based front-end delivered with the OGC web services sample has been replaced by a new JavaScript-based front-end that gives access to the various services and example requests. This removes the JSP dependency from the sample.

ImprovementLuciadFusion

TLcdGXYImageIconPainter was added. This painter makes it possible to paint ALcdImage objects as a regular icon grid, using ILcdParameterizedIcon.

ImprovementLuciadFusion

An implementation of ILcdParameterizedIcon that displays numeric values was added, TLcdNumericParameterizedIcon.

ImprovementLuciadFusion

LCD-6202

Raster layers now also support explicit ordering for the elements in a single layer. You can configure this using TLspRasterStyle's Z-order property.

ImprovementLuciadFusion

LCD-6176

To support transaction requests containing data defined in a custom data format, it is now possible to register one or more data models via the constructor of TLcdWFSTransactionRequestHandler. A typical use case is the set up of an OGC WFS-T, capable of receiving AIXM 5 data.

ImprovementLuciadFusion

LCD-6173

The performance of TLcdAlbersEqualAreaConic was improved. The lonlatheight2worldOnEllipsoidSFCT() and world2LonLatOnEllipsoid() methods are now 20% to 40% faster on average.

ImprovementLuciadFusion

TLcdAdvancedMapRulerController and TLcdMapTouchRulerController now enable anti-aliasing when painting the measurements.

ImprovementLuciadFusion

TLcdAdvancedMapRulerController and TLcdMapTouchRulerController can now paint a halo around measurement lines. See the setHaloEnabled, setHaloThickness and setHaloColor methods.

ImprovementLuciadFusion

LCD-5465

TLspRulerController now has a setDisplayAzimuth(boolean) method that can be used to easily paint an azimuth label for every segment of the measurement. The ruler controller also paints an arrow in the middle of every line segment when the azimuths are displayed.

ImprovementLuciadFusion

LCD-5465

TLcdAdvancedMapRulerController and TLcdMapTouchRulerController now paint an arrow in the middle of every measurement line segment when setDisplayAzimuth(true) is called.

ImprovementLuciadFusion

LCD-6090

The performance of the contains2D and contains3D methods for geodetic and rhumb polygons has been improved.

ImprovementLuciadFusion

LuciadFusion now supports replication of tile stores. Given a target tile store, replication lets you define a source tile store to replicate data from. The main entry point is the classTLfnReplication. Replication allows you to:

Select which coverages or updates to replicate before initiating the actual replication.
Define an area of interest to limit the coverage size on the replica (only for tiled raster coverages). Tiles are filtered such that only those overlapping with the area of interest are replicated.

Replication has some interesting properties:

It is symmetrical, meaning that there is nothing which inherently defines a tile store to be source or target. Any tile store can be used as source or target at any given moment.
It replicates all resources: coverages, assets and themes. Replication operates on both a resource's metadata and data, but the data is only replicated as part of a coverage. This means that, for asset sources in tile store, the asset sources are replicated only if the asset is part of a coverage.
Resources are globally identified across tile stores based on the resource ID, which must be globally unique. Updates are detected based on the global update sequence of a resource, which has the semantics of a 'last modified' timestamp.

ImprovementLuciadFusion

LCD-5977

All ILcdGXYView implementations now support setting a different scale along the X and Y axes. This allows changing the aspect ratio of a view.

ImprovementLuciadFusion

The coverage must be a raster coverage.
The asset must be of a tile set format. A tile set format is a format that creates models with an ILcdTileSet as element. By definition, the tiling structure thus must be power-of-two.
The coverage must have exactly one asset with one asset part. For example a single WMTS layer.
The coverage's tiling structure must match that of the asset.
The coverage's tile format must match the native format class of the tile set.
The native format class

By default, a coverage will be automatically configured to meet these conditions if possible. There are two default tile set formats:

WMTS
Geospatial PDF

You can of course define your own tile set format, in which case you must take the above conditions into account.

ImprovementLuciadFusion

LCD-4125

The WCS proxy object TLcdWCSProxy no longer silenty discards exceptions in case no exception handler is configured.

Bug fixLuciadFusion

TLcdGXYSurfacePainter: previously, when TLcdGXYRoundedPointListPainter was used as a painter for external or internal polygonal surfaces, the first corner was not rounded.

Bug fixLuciadFusion

LCD-4703

Raster layers with layer type interactive now support model and style target changes without flickering in most cases. You can find all details in the documentation of TLspRasterLayerBuilder and TLspRasterLayer.

Bug fixLuciadFusion

LCD-5280

Clarified TLcdLonLatBuffer and TLcdLonLatHeightBuffer width and height properties:

Width is measured from axis to buffer edge, so the buffer has a total width of 2 * the buffer's width property.
Height is measured from the buffer's bottom to top, so the buffer's height property is the sum of the height from the axis to the top and the height from the axis to the bottom.

Bug fixLuciadFusion

LCD-5749

TLcdGXYViewFitAction#fitGXYLayer did not take the isFitToChildren property into account.

Bug fixLuciadFusion

LCD-4984

Calling TLspLabelBoxStyle.Builder#fillColor() or TLspLabelBoxStyle.Builder#frameColor() now enables fill or frames as expected.

Upgrade considerationLuciadFusion

ALfnTileStore now has a putTileStoreMetadata method which must be implemented by all of its extensions. The new method is called by the LuciadFusion framework in the context of replication. Wrapper or composite extensions may delegate this method.

Upgrade considerationLuciadFusion

LCD-5731

It is now possible to specify a content type for the response to a WFS DescribeFeatureType request by implementing the new method getContentType on the interfaceILcdWFSModelSchemaEncoder. In case you have a custom implementation of this interface, you must implement this new method. Typical implementations will return a constant MIME type, for example"text/xml".

Upgrade considerationLuciadFusion

Because of the OGC web service front-end improvement (LCD-1097), there is a change in 3rd party library dependencies for the OGC web service sample. Because this new front-end is now built using JavaScript instead of JSP, the following JSP-related libraries have been removed:

jspapi-2.2.jar
javax.servlet.jsp.jstl-1.2.1.jar
javax.servlet.jsp-2.2.2.jar
jdt-core-3.7.1.jar
el-api-2.2.jar
jstl-api-1.2.jar

Instead, a JavaScript library dependency has been added to support the front-end, namely AngularJS 1.3.10. More specifically, the following AngularJS modules have been added to build/ogc/resources/js:

angular
angular-route
angular-sanitize

Users that relied on the front-end need to update their build process to take the 3rd party library change into account.

Upgrade considerationLuciadFusion

Because of the Data Server sample front-end improvement, there is a change in 3rd party library dependencies for the Data Server sample. Because this new front-end is now built using JavaScript instead of JSP, the following JSP-related libraries have been removed:

jspapi-2.2
javax.servlet.jsp.jstl-1.2.1.jar
javax.servlet.jsp-2.2.2.jar
jdt-core-3.7.1.jar
el-api-2.2.jar
jstl-api-1.2.jar

Instead, a JavaScript library dependency has been added to support the front-end, namely AngularJS 1.3.10. More specifically, the following AngularJS modules have been added to build/fusion/resources/js:

angular
angular-route
angular-sanitize

Users that relied on the front-end need to update their build process to take the 3rd party library change into account.

Upgrade considerationLuciadFusion

LCD-6172

It is now possible to separately define output formats for GetFeature and DescribeFeatureType requests. To this end, the new methods ILcdWFSClientModelEncoderFactory.getSupportedSchemaOutputFormatCount and ILcdWFSClientModelEncoderFactory.getSupportedSchemaOutputFormat have been added, which define the supported output formats for the DescribeFeatureType request. The existing methods ILcdWFSClientModelEncoderFactory.getSupportedOutputFormatCount and ILcdWFSClientModelEncoderFactory.getSupportedOutputFormat now only define the supported output formats for the GetFeature request. Existing, custom implementations of ILcdWFSClientModelEncoderFactory can delegate to the default implementation available in TLcdWFSClientModelEncoderFactory.

Upgrade considerationLuciadFusion

LCD-5174

It is now possible to define supported output formats per feature type. To this end, a new method ILcdWFSFeatureType.getSupportedOutputFormats has been added, which returns the supported output formats as an object of type TLcdWFSOutputFormatList. The default implementation, TLcdWFSFeatureType, has been updated accordingly and has also received a setter for this new property. Existing, custom implementations of ILcdWFSFeatureType can implement the new method by returning null, indicating that the global list of output formats needs to be used; this corresponds to the past behavior.

Upgrade considerationLuciadFusion

The ILcdEarthParameterizedIcon interface was removed, and replaced by ILcdParameterizedIcon. On top of the already existing methods, this new interface also adds an anchorPointSFCT(double[], Point) method. All classes in LuciadLightspeed that previously implemented ILcdEarthParameterizedIcon now implement ILcdParameterizedIcon. This change may cause compile errors in the following cases:

Direct use of the ILcdEarthParameterizedIcon interface. Can be fixed by using ILcdParameterizedIcon instead.
Implementations of ILcdEarthParameterizedIcon that don't extend from ALcdEarthParameterizedIcon will need to implement the anchorPointSFCT method. Wrappers can just delegate to the delegate anchorPointSFCT method. Other classes can use a default implementation, see javadoc of anchorPointSFCT.

Upgrade considerationLuciadFusion

The signature of the user data operations on ALfnCoverage has changed: the result of the operation now uses a WriteResult or ReadResult rather than a Boolean to indicate its outcome. Method signatures need to be updated where necessary:

putUserData: the semantics of true and false have been replaced with Result.Code.PUT and CREATED respectively.
getUserData: the semantics of true and false have been replaced with Result.Code.FOUND and NOT_FOUND respectively.
deleteUserData: the semantics of true and false have been replaced with Result.Code.DELETED and NOT_FOUND respectively.

Upgrade considerationLuciadFusion

TLcdImageFactory was replaced by TLcdImageBuilder, TLcdImageMosaicBuilder, TLcdRasterImageBuilder and TLcdEarthImageBuilder. The factory methods on ALcdBandColorSemantics and ALcdBandMeasurementSemantics were also replaced by TLcdBandColorSemanticsBuilder and TLcdBandMeasurementSemanticsBuilder.

Upgrade considerationLuciadFusion

LCD-4786

The XML framework API in the com.luciad.format.xml and com.format.xml.schema packages has been deprecated in favor of the equivalent API offered by the XML binding framework (see com.luciad.format.xml.bind and com.format.xml.schema.bind).

Upgrade considerationLuciadFusion

The TLspRasterWorldTouchInfo#setColorValue(int, ColorModel) method was removed. The setRasterData(Raster) method should be used instead.

Upgrade considerationLuciadFusion

LCD-3909

It is now possible to define the content type (MIME type) of a custom outputFormat. To this end, the return type of method ILcdWFSClientModelEncoderFactory.createModelEncoder has changed from ILcdModelEncoder to a new type ILcdWFSModelEncoder. You need to update your implementations accordingly:

If the ILcdModelEncoder you used to return is an instance of a class under your control, just implement the new method getContentType.
If the ILcdModelEncoder you used to return is an instance of a class not under your control, you can wrap it using TLcdWFSModelEncoder and give it a content type. Using null as content type is allowed but not recommended: it means that the GetFeature response will not have a content type, which can result in ill-defined behavior on the client.

Upgrade considerationLuciadFusion

LCD-6103

To enable WMS request parameter access in the layer creation, the signature of the method ILcdWMSGXYLayerFactory#createGXYLayer(ILcdModel, ALcdWMSLayer, String) has been changed into #createGXYLayer(ILcdModel, ALcdWMSLayer, String, TLcdWMSRequestContext). TLcdWMSRequestContext gives access to the original request and a number of additional request-related parameters.

The change will impact WMS implementations that use an implementation of ILcdWMSGXYLayerFactory that does not extend from ALcdSLDWMSGXYLayerFactory. Affected implementations can simply update the signature of the createGXYLayer method and ignore the new parameter.

Upgrade considerationLuciadFusion

TLcdCADRGRaster no longer extends TLcdRaster. Instead it extends ALcdImageMosaic. To maintain existing functionality TLcdCADRGRaster now implements ILcdRaster.

Upgrade considerationLuciadFusion

ALcdGXYSmartController's default pan and zoom keyboard shortcuts have been simplified to the arrow keys and +/-, to prevent interference with application-specific keyboard shortcuts.

Upgrade considerationLuciadFusion

The minimum Java version to run LuciadLightspeed is now Java 7.

Upgrade considerationLuciadFusion

LCD-5281

Fixed an issue in TLcdLonLatHeightBuffer.contains3D(): it checked if points were within [0, +height] measured from the axis line, instead of the interval [-height/2, +height/2] around the axis line.

In addition, TLcdLonLatHeightBuffer's bounds used this interpretation, which caused the bounds to be shifted up incorrectly by height/2.

If you use TLcdLonLatHeightBuffer.contains3D or its bounds, please verify that your application can handle this change.

Upgrade considerationLuciadFusion

Bug fixLuciadFusion

LCD-6261

ImprovementLuciadFusion

TLspMesh3DIcon now supports the use of an ILcdInputStreamFactory to load texture images.

ImprovementLuciadFusion

LCD-6235

TLcdEllipsoidCircleUtil was added. This class contains methods for topology calculations with circles on the ellipsoid.

Bug fixLuciadFusion

LCD-6217

Fixed possible exception using the band-select operator on an image backed by data with a BandedSampleModel.

Bug fixLuciadFusion

LCD-6213

you have multiple TLfnFileSystemTileStores using a shared ALfnEnvironment
you use the same coverage IDs in multiple of these Tile Stores

ImprovementLuciadFusion

LCD-5992

LCD-5993

TLcdGeorefUtil now uses truncating to determine the minute square coordinates instead of rounding.

ImprovementLuciadFusion

TLcdImageHeightProvider now checks that the height value is in a valid range, similar to TLcdRasterHeightProvider. The range can be configured using the new constructors or using the keys in ALcdRasterModelHeightProviderFactory when using a TLcdImageHeightProviderFactory. The default range is [-12000,10000].

ImprovementLuciadFusion

Fusion of Geospatial PDF benefits from the upgrade to IcePDF 5.1.1 in its dependencies:

Handling of Geospatial PDF files with a suboptimal internal tiling structure is now more robust. This fixes OutOfMemoryErrors which could happen when fusing some of these files.
Improved rendering of Geospatial PDF input data results in better looking fused coverages.

LuciadLightspeed no longer includes ProGuard. It used to be included to demonstrate various deployment scenarios. Those samples are still available, but you now have to download ProGuard separately from its website. The downloaded proguard.jar should be placed in the build/proguard directory.

Upgrade considerationLuciadFusion

LCD-5946, LCD-4201

To enable WMS request parameter access in the data backend, the signature of the method ILcdModelProvider#getModel(String) and its extension ALcdMultiDimensionalModelProvider#getModel(String) have been changed into #getModel(String, ALcdRequestContext). ALcdRequestContext is a new class giving access to the original request; in the WMS, this class is implemented by TLcdWMSRequestContext, which adds a number of additional request-related parameters.

The change will impact WMS implementations that use a custom implementation of ILcdModelProvider or ALcdMultiDimensionalModelProvider. Affected implementations can simply update the signature of the getModel method and ignore the new parameter.

Upgrade considerationLuciadFusion

LCD-5946

To enable WFS request parameter access in the data backend, the signature of the method ILcdOGCModelProvider#getModel(String) has been changed into ILcdOGCModelProvider#getModel(String, ALcdRequestContext). ALcdRequestContext is a new class giving access to the original request; in the WFS, this class is implemented by TLcdWFSRequestContext, which adds a number of additional request-related parameters.

The change will impact WFS implementations that use a custom implementation of ILcdOGCModelProvider. Affected implementations can simply update the signature of the getModel method and ignore the new parameter.

Upgrade considerationLuciadFusion

LCD-5422

Two constructors have been removed from com.luciad.wms.sld.model.ALcdSLDLayer.

ALcdSLDLayer()
ALcdSLDLayer(String aName, ALcdSLDLayerStyle[] aSLDLayerStyles, TLcdSLDLayerFeatureConstraints aLayerFeatureConstraints)

Bug fixLuciadFusion

LCD-5981

Correctly decode GeoTIFF images that use a geographic coordinate system encoded as a projected coordinate system.

Bug fixLuciadFusion

Bug fixLuciadFusion

LCD-5902

LF-640

The LTS mechanism for conditionally getting tiles based on modification times in ETag/If-None-Match headers was fundamentally flawed. The ETag headers were interpreted on the client as milliseconds, which

is against the ETag principle (it must be used as an opaque value);
broke down in more advanced server scenarios where servlet filters may change the ETag headers (for example GzipFilter in Jetty 8).

LCD-5396

In some cases lon lat grid labels could flip all the time.

Bug fixLuciadFusion

Fixed performance bottleneck in TLspEditController when selecting many (10000+) objects.

ImprovementLuciadFusion

From now on, patch releases of LuciadLightspeed will be binary compatible with their respective Major.Minor version. For instance, version 2014.0.01 will be binary compatible with version 2014.0. It will not necessarily be binary compatible with version 2014.1 or 2015.0.

There may be occasional exceptions. These will be documented in the release notes.

The appendix 'Compatibility of LuciadLightspeed version' in the developer's guide has more information.

Support was added for the SWEN08_RH2000 and SWEN08_RH70 geoid geodetic datums. See TLcdGeoidGeodeticDatumFactory#SWEN08_RH2000 and TLcdGeoidGeodeticDatumFactory#SWEN08_RH70.

ImprovementLuciadFusion

ImprovementLuciadFusion

LCD-4763

Support was added for a new tile format "image/tiff" for elevation and multivalued coverages.

ImprovementLuciadFusion

LCD-3261, LCD-4303, LCD-4603

The navigation controllers now navigate around and toward the object that is touched by the mouse. This allows for convenient navigation around tall or airborne objects, such as air tracks.

ImprovementLuciadFusion

When using a Lightspeed view, the default selection style for text and text labels now uses an orange color with a black halo instead of an orange color with the regular halo color. This improves the legibility of the text in cases where a light regular halo color is used.

ImprovementLuciadFusion

The package com.luciad.imaging introduces a new API to perform various image processing operations on raster data. The package defines a new representation for image data (ALcdImage), which supports multi-band and HDR imagery. It also provides a number of operators, such as band select or convolution, which can be applied to images. In GXY views, images can be visualized using the new TLcdGXYImagePainter. In Lightspeed views, TLspRasterLayerBuilder supports the new image types and the new TLspImageFilterStyle can be used to perform image processing on raster layers in a view. Please refer to the package javadoc and to the developer's guide for more information.

ImprovementLuciadFusion

LCD-4836

An appropriate HTTP status code is now set on the response in case of a service exception report: 4xx for client request errors, 5xx for server errors.

ImprovementLuciadFusion

LuciadFusion now supports fusion of floating point elevation values. There are some limitations:

The input format needs to support floating point elevation values as well. GeoTIFF is currently the only format that supports this.
The new elevation tile format "image/tiff" provides optimal support for floating point values and is the new default. Old clients will not be able to visualize coverages with this new tile format. For backwards compatibility, you need to explicitly set "image/png" as tile format on the coverage.
The old "image/png" tile format also provides limited support for decimal values by scaling them. The drawback is that the precision is unpredictable because the scaling depends on the max./min. values which are different in each tile.
It may be beneficial to use "image/tiff" even if the input format does not support floating point elevation values: fusion interpolates the values, in which case it makes sense to preserve their floating point nature even if the input values themselves are not floating point.
The "image/tiff" tile format can also be used for multivalued data. Even though there is currently no input format that supports floating point multivalued data, it may still be beneficial to use this new tile format to preserve floating point values: fusion interpolates the values, in which case it makes sense to preserve their floating point nature even if the input values themselves are not floating point.

ImprovementLuciadFusion

LCD-5118

The Feature Type Style decoder, TLcdSLDFeatureTypeStyleDecoder, now also supports decoding a Feature Type Style from XML documents that have a Styled Layer Descriptor, Named Layer, User Layer, or User Style as top level element.

ImprovementLuciadFusion

The filtering of vector data during the fusion process can now use SLD. Consult the developer guide, user guide and javadoc of TLfnVectorCoverageMetadata for more information.

ImprovementLuciadFusion

LCD-3578

The creation of a layer for Fusion vector data has been simplified. The classes which are available in the API have been extended to support more use cases by default:

TLfnGXYVectorLayer: used to visualize Fusion vector data in GXY views

When the vector coverage for which the layer is created contains SLD feature type styles, the visualization will automatically use those feature type styles for styling (bodies and labels).
When the vector coverage for which the layer is created contains VPF data, the visualization will automatically use GeoSym styling.
When the vector coverage defines OGC filters, the filters will be respected during the visualization.
The layer contains by default a label painter based on the ILcdDataModel of the coverage.

Consult the javadoc of TLfnGXYVectorLayer for more information.

TLspFusionVectorLayerBuilder: used to visualize Fusion vector data in Lightspeed views

When the vector coverage for which the layer is created contains SLD feature type styles, those feature type styles define the styling which will be used during the visualization.
When the vector coverage for which the layer is created contains VPF data, the visualization will automatically use GeoSym styling.
When the vector coverage defines OGC filters, the filters will be respected during the visualization.
A label styler is added by default.

Consult the javadoc of TLspFusionVectorLayerBuilder for more information.

ImprovementLuciadFusion

LCD-4282

TLcdScaleFormat now parses plain values as "1 : value" (for example, "25,000" is interpreted as "1:25,000"). It also accepts common decadic multiple suffixes (for example "1 : 25K").

ImprovementLuciadFusion

LCD-5047

ALspAWTView now has a getImage() method, analogous to the one that already existed in TLspOffscreenView, to retrieve a screenshot of the view.

ImprovementLuciadFusion

Added support for PNG in TLcdTFWRasterModelDecoder.

ImprovementLuciadFusion

The EPSG resources are updated to EPSG database v8.4. At the same time, a few EPSG code parsing problems were fixed:

Some geocentric references were parsed as geodetic references
The datum transformation parameters were improved

ImprovementLuciadFusion

Fusion now supports S-63, the encrypted low-level data format of ECDIS.

ImprovementLuciadFusion

The LIDAR Developer's Guide
The javadoc of TLcdLASModelDecoder on how to decode .las files
The javadoc of TLspLIDARLayerBuilder on how to visualize such data

ImprovementLuciadFusion

Performance improvements for TLspLabelPainter when querying label information and preparing for painting.

ImprovementLuciadFusion

ILcdExpressions created using TLcdExpressionFactory.attribute() now implement equals() and hashCode().

ImprovementLuciadFusion

TLcdCompositeModelDecoder now implements ILcdDataSourceModelDecoder as well.

ImprovementLuciadFusion

LCD-4152

ImprovementLuciadFusion

LCD-3569

You can now use TLcdLockUtil together with the Java 1.7 try-with-resources idiom. This means that you no longer have to unlock explicitly in a finally block. Example:

      try (TLcdLockUtil.Lock lock = TLcdLockUtil.readLock(model)) {
      Enumeration enumeration = model.elements();
      }

ImprovementLuciadFusion

LCD-3974

TLcdDefaultModelModelTransformation, TLcdDefaultModelXYWorldTransformation and TLcdDefaultModelXYZWorldTransformation now have a convenience constructor that takes the source and destination reference as arguments.

ImprovementLuciadFusion

LCD-244, LCD-4583

TLcdGXYMultiFontLabelPainter now extends from TLcdGXYStampLabelPainter. Because of this, it now supports:

label editing
label halo and pin halo
interactive labels
labels of labels
...

TLspViewXYZWorldTransformation3D.getScale() now returns a value that does not depend on the current reference point (see getReferencePoint()). This fixes a few scale-related issues:

The scale icon showed incorrect values when linking the camera to for example a track
When using level-of-detail based on the scale, the incorrect detail level was chosen in some cases.
The scale was not always updated immediately during navigation.
The shape discretization was too fine-grained in some cases.

Bug fixLuciadFusion

LCD-551

Fixed an issue preventing decoding of non-qualified XML elements.

Bug fixLuciadFusion

TLcdGXYMultiFontLabelPainter now throws a property change event when calling the setConsiderPinForBounds() method.

Bug fixLuciadFusion

LCD-5328

The TLcdSLDFeatureTypeStyle#insertRuleAt now correctly shifts rules towards the back of list of rules instead of replacing the rule at that index. For example, if two rules are inserted at position 0, the one that was added first will now be shifted to position 1. Before, the one added first would be replaced with the one added second.

Bug fixLuciadFusion

Fixed artifacts when painting a text label in combination with a semi-transparent halo color or fill color (TLspLabelBoxStyle.Builder#fillColor).

Bug fixLuciadFusion

addViewInvalidationListener
removeViewInvalidationListener

View invalidation listeners can be used to get notified whenever the view has been invalidated.

Upgrade considerationLuciadFusion

ILfnResourceMetadataResolver: the signature of the method getResourceMetadata has changed.

It now declares to throw IOException and TLfnServiceException.
It returns a generic type argument allowing the user to omit a cast.

These changes make the method signature compatible with the same method on ALfnTileStore, so that ALfnTileStore can now implement ILfnResourceMetadataResolver. Decorator implementations of ILfnResourceMetadataResolver will need to throw on these exceptions. Callers of this method will need to be adjusted to deal with the exceptions. A typical handling will be to ignore or to log the exceptions and treat them the same way as if the call would have returned null.

Upgrade considerationLuciadFusion

The ILspLabelStyler interface was removed. This interface served no purpose, and using it could lead to incorrectly working code. Instead of using ILspLabelStyler, ALspLabelStyler can still be used without changes, or ILspStyler can be used directly by casting the style collector passed in the style() method to ALspLabelStyleCollector. For more information on label styling and examples, see ILspStyler or ALspLabelStyleCollector class doc.

Upgrade considerationLuciadFusion

LCD-4768

To prevent incorrect usage, TLcdModelXYWorldTransformation and TLcdModelXYZWorldTransformation were deprecated and replaced by the TLcdIdentityModelXYWorldTransformation and TLcdIdentityModelXYZWorldTransformation classes.

Upgrade considerationLuciadFusion

The TLcdWMTSLayer.hasCompatibleTileStructure method has been removed. The updated decoder now supports all tile structures. Previously it only supported quad tree tile structures. You can use the new isTileStructureQuadTree method to query if a TLcdWMTSLayer has a quad-tree tile structure. In other words this new method behaves exactly like hasCompatibleTileStructure did in older versions.

Upgrade considerationLuciadFusion

LCD-5089

TLspScaleIndicator: the scale indicator now uses the scale at the center of the projection by default instead of the scale at the center of the map. Consult the javadoc of TLspScaleIndicator#setScaleAtCenterOfMap for more information.

Upgrade considerationLuciadFusion

LCD-5089

TLcdGXYScaleIndicator: the scale indicator now uses the scale at the center of the projection by default instead of the scale at the center of the map. Consult the javadoc of TLcdGXYScaleIndicator#setScaleAtCenterOfMap for more information.

Upgrade considerationLuciadFusion

LCD-5133

The TLcdGXYCompositeViewLabelPlacer#getGroupID(...) method now also takes a view as argument. Code extending from this method can be fixed by adding an ILcdGXYView parameter to the method signature.

Upgrade considerationLuciadFusion

LCD-4200

The capabilities class ALcdWMSCapabilities and its default implementation TLcdWMSCapabilities now implement ILcdCloneable, providing a public clone() method to create a copy of an instance. Additionally, TLcdWMSCapabilities now has a copy constructor that allows to create a new TLcdWMSCapabilities instance based on a given ALcdWMSCapabilities instance.

Custom implementations of ALcdWMSCapabilities or extensions of TLcdWMSCapabilities are recommended to override the clone() method and implement proper behavior for the custom implementation / extension - i.e., take into account potential custom properties or delegate in case of a wrapper implementation.

Upgrade considerationLuciadFusion

TLcdWeakIdentityHashMap no longer extends AbstractMap. This should not affect the use of this class.

Upgrade considerationLuciadFusion

LCD-3634

TLpsFusionVectorLayerBuilder: you can now set any ILspStyler on the builder, without triggering tile loading of the most detailed level.

Prior to this release, you had to make sure that the ILspStyler which was set used a TLspFusionGeometryProvider. If this was forgotten, you would probably trigger the loading of the most detailed tiles, even when visualizing tiles at a less detailed level.

The TLpsFusionVectorLayerBuilder will now automatically ensure that the ILspStyler works with the correct geometries. Consult the class javadoc of TLpsFusionVectorLayerBuilder for more information.

This improvement has two consequences:

The ILspStyler which is returned by the ILspInteractivePaintableLayer#getStyler method of the created layer will no longer be the styler which was set on the builder.
If your ILspStyler uses an ALspStyleTargetProvider, this style target provider will no longer receive the domain objects as it was previously the case. It will receive the geometries specific to a tile instead. Consult the class javadoc of TLpsFusionVectorLayerBuilder for more information.

Upgrade considerationLuciadFusion

Coverages which were fused with asset sources in Tile Store using V2013.1 are incompatible with V2014.0.

The WMS server will fail on non-tiled coverages with an error on the console "Could not create model decoder for asset". WMS clients will not display anything for WMS layers corresponding to such coverages.
The WMS GetFeatureInfo requests will fail with a similar error on non-tiled coverages or coverages with asset sources in Tile Store. WMS clients will not display any feature info for WMS layers corresponding to such coverages.

You'll have to remove and recreate those coverages from their original input data.

Upgrade considerationLuciadFusion

With the introduction of support for non-quadtree tile matrix sets, it is no longer guaranteed that WMTS models (created via TLcdWMTSModelDecoder) contain an ILcdEarthTileSet domain object. If a layer's tile structure is not a quadtree, the created domain object (via TLcdWMTSModelDecoder) is an extension of ALcdMultilevelImageMosaic. In this case you can no longer explicitly cast the domain object to an ILcdEarthTileSet as before. If the tile structure is a quadtree, the created domain object can be casted to both ILcdEarthTileSet and ALcdMultilevelImageMosaic.

Upgrade considerationLuciadFusion

For version 2014.0, all LuciadMap customers with the appropriate maintenance contract are upgraded to LuciadLightspeed LM. This is the same product as LuciadLightspeed, but with the hardware-accelerated components disabled. With LuciadLightspeed LM, you cannot instantiate any ILspView implementation, nor use any functionality that uses such a view.

LuciadMap customers upgrading from LuciadMap 2012 or 2013 to LuciadLightspeed LM can find the release notes that are relevant to them here.

LuciadLightspeed LM is only available for customers who bought LuciadMap in the past.

Upgrade considerationLuciadFusion

The lookup table classes used for color filtering have been migrated to the new image processing API. As a consequence the following classes have been renamed:

com.luciad.view.lightspeed.style.imagefilter.ALspColorLookupTable to com.luciad.imaging.operator.util.ALcdColorLookupTable
com.luciad.view.lightspeed.style.imagefilter.TLspColorLookupTable to com.luciad.imaging.operator.util.TLcdColorLookupTable
com.luciad.view.lightspeed.style.imagefilter.TLspComponentColorLookupTable to com.luciad.imaging.operator.util.TLcdComponentColorLookupTable
com.luciad.view.lightspeed.style.imagefilter.TLspLookupTable to com.luciad.imaging.operator.util.TLcdLookupTable

The TLspColorLookupTableFilterStyle is still available but you are strongly advised to use the more general TLspImageFilterStyle instead. You can easily convert the lookup table style to an equivalent image filter by chaining TLcdColorLookup operators.

Upgrade considerationLuciadFusion

V2013.1 Tile Stores which already contain coverages with asset sources in Tile Store are not compatible with V2014.0. Opening them will succeed, but the asset sources in Tile Store will appear absent. When upgrading a server from V2013.1 to V2014.0, you need to re-fuse those coverages with asset sources in Tile Store. Any lingering files will not be removed from the server.

Upgrade considerationLuciadFusion

AssetParts now always belong to a parent asset metadata, to which they now have a reference. They can no longer be created as stand-alone instances. The constructors of RasterAssetPart and VectorAssetPart have been removed. As a result, users of any of these constructors will get compile errors which can be fixed by using either AssetPart.Builders or one of the methods addAssetPart or setAssetPart on TLfnRasterAssetMetadata.Builder or TLfnVectorAssetMetadata.Builder.

The AssetPart.Builders can be created using the method ALfnAssetMetadata.Builder.newAssetPart(). When the asset metadata is built, its asset parts will have a reference to it.

LCD-5403, LCD-5404, LCD-4933

Bug fixLuciadFusion

Fixed a bug that prevented TLspOffscreenView from doing GL context sharing with an external ILcdGLDrawable.

Bug fixLuciadFusion

LCD-5103

Fixed a bug in the handling of TLsp3DIconStyles with transparency.

Bug fixLuciadFusion

ALcdAnimationManager now uses a daemon thread for its timing logic.

Bug fixLuciadFusion

LCD-5129

The label placement performance was bad when using TLspOnPathLabelingAlgorithm, TLspInPathLabelingAlgorithm or TLspCurvedPathLabelingAlgorithm on a non-culled layer, and when using a world reference with a projection that doesn't cover the entire world.

Bug fixLuciadFusion

LCD-5100

The GeoPackage decoder can now handle empty files and files with empty tables.

Bug fixLuciadFusion

LCD-5123

Cloning of ILcdDataObjects with a property that has collection type MAP failed. This is now resolved.

ImprovementLuciadFusion

LCD-4968

Bug fixLuciadFusion

LCD-5078

LCD-5041

Some EPSG grid references using an oblique Mercator projection (for example EPSG:2056) incorrectly transformed points.

Bug fixLuciadFusion

TLcdWKTReferenceParser could return model references containing an incorrect ellipsoid when the 'inverse flattening' value in the WKT string is 0.

ImprovementLuciadFusion

TLcdISO19115Code now has an additional 'type' property, which is required to support for XML-Java-XML roundtripping of ISO metadata.

Bug fixLuciadFusion

LCD-5013

Polylines were drawn as filled polygons in GeoJson decoder sample.

Bug fixLuciadFusion

LCD-5023

Fixed possible exception when opening a GeoPackage file in a Lightspeed view.

Bug fixLuciadFusion

LCD-5021

Fixed an overflow bug which caused SHP files larger than 1 GiB to be fused incorrectly.

Bug fixLuciadFusion

LCD-5021

Fixed an overflow bug in TLcdSHPTiler so that now SHP files larger than 1 GiB can also be tiled.

Bug fixLuciadFusion

If one ILspController would set another controller on the view in its startInteraction method, its layers would not be correctly unregistered.

Bug fixLuciadFusion

LCD-4480

The XML decoding and encoding in TLcdISO19139MetadataDecoder and TLcdISO19139MetadataEncoder have been improved: full roundtripping from XML to Java and back to XML is now possible without information loss.

ImprovementLuciadFusion

LF-568

Fusion's SHP format now allows setting the character set on the model decoder. To set the character set, one must

ImprovementLuciadFusion

LCD-4842

ImprovementLuciadFusion

GML decoding speed has been considerably improved for certain geodetic models.

ImprovementLuciadFusion

LCD-4745

Decoding a model of a coverage from a Tile Store has now become a lot easier:

Create a TLfnTileStoreModelDecoder instance using the default constructor. It uses default internal resources.
Decode an ALfnTileStore using tileStoreModelDecoder.canDecodeTileStore(sourceName) and decodeTileStore(sourceName).
Get the Tile Store's list of coverage IDs using tileStore.getCoverageIDs().
Decode an ALfnTileStoreModel for any coverage using tileStoreModelDecoder.decode(tileStore, coverageId).

ImprovementLuciadFusion

LCD-4949

LuciadFusion environments created by ALfnEnvironment.newInstance() and ALfnClientEnvironment.newInstance() are now automatically closed in finalize(). This helps to avoid resource leaks. Because there is no guarantee when the finalizer will be called, it is still recommended to close them explicitly.

ImprovementLuciadFusion

LCD-4872

ImprovementLuciadFusion

LCD-4676

For Lightspeed views: Floating GroundOverlays with transparency used to obscure shapes rendered below them. This has now been fixed. This only affects GroundOverlay elements that were not clamped to ground.

ImprovementLuciadFusion

Bug fixLuciadFusion

LCD-4725

Bug fixLuciadFusion

LCD-4681

Fixed out-of-bounds error when a tile set is not completely visible in the view's world reference.

ImprovementLuciadFusion

LCD-4208

TLcdGXYPointListPainter can now be configured to change the winding rule that determines the inside of self-intersecting polygons.

ImprovementLuciadFusion

LCD-4249

ImprovementLuciadFusion

LCD-4296, LCD-4489, LCD-3828, LCD-3825

Several improvements and fixes for the lightspeed.limitnavigation sample:

The constraints used to limit navigation now handle movement along the border of the area of interest much better.
The navigation constraints now handle changing the world reference better.
The navigation constraints now do not use the area of interest constraint if the area lies completely outside the projection bounds.

ImprovementLuciadFusion

LCD-4374

It is now possible to configure an expiry date on a WMS layer (ALcdWMSLayer). This information is used to fill in the "Expires" HTTP header on the response of a GetMap and GetFeatureInfo request.

ImprovementLuciadFusion

TLfnWMSLayerFactory now uses the DTED color model by default for the styling of elevation layers. For the styling of elevation layers, you should by preference pass an ILcdColorModelFactory to its constructor rather than a TLcdColorMap.

ImprovementLuciadFusion

The TLspTouchSelectEditController#selectWhat method now returns a set containing all available paint representations in the view.

ImprovementLuciadFusion

The Fusion WMS server now supports serving S-57 data with pixel-perfect rendering at any scale. This feature will automatically be enabled for coverages that have been fused with asset sources in Tile Store. You can combine this with a tile structure or not, depending on the use case.

Standard tiled coverage: for serving pre-rendered S-57 tiles. Pixel-perfect rendering is limited to a fixed style, a set of discrete scales and a fixed geographic reference. Supported protocols are WMS, WMTS and LTS.
Tiled coverage with asset sources in Tile Store: same as above, plus the flexibility to use client-side WMS styling. Supported protocols are WMS, WMTS and LTS.
Non-tiled coverage (always with asset sources in Tile Store): for serving pixel-perfect S-57 images at any scale, in any geographic reference, with any style. There are no pre-rendered tiles. WMS is the only supported protocol.

ImprovementLuciadFusion

TLcdLayerTree now allows setting the minimum visible row count, which affects its preferred size in a scroll pane. This behavior is especially useful when overlaying a JTree on a map, where you want to prevent unused empty space, but you also want to allow it to grow when needed.

ImprovementLuciadFusion

LCD-2088

S-57 catalogues and cells are supported.
All other formats only supported if the source is a single file. Auxiliary files are lost. Fusion does not fail on these formats, instead it copies only a single asset source.
Only files are supported, not streams in general.

ImprovementLuciadFusion

OGC GeoPackage is now supported.

You can open .gpkg files using TLcdGeoPackageModelDecoder. You can use a shape layer to visualize vector data, or a raster layer to visualize raster data, as demonstrated in the common decoder sample: samples.lightspeed.decoder.MainPanel
You can create .gpkg files using TLcdGeoPackageModelEncoder, as demonstrated in samples.encoder.sqlite.geopackage.Main

See developer's guide or javadoc of com.luciad.format.sqlite.geopackage for more details.

ImprovementLuciadFusion

TLcdRotatingIcon can now be used on the Lightspeed view overlay panel.

ImprovementLuciadFusion

LCD-4155

The TLcdGeoJsonModelDecoder.decode instance method is less restrictive now. Instead of allowing only sources with FeatureCollections, it now allows you to decode sources that contain either a single geometry, a single feature, or an array of features, into an ILcdModel.

ImprovementLuciadFusion

The WMS server now allows the Post method as access point for GetFeatureInfo requests. This is also reflected in the WMS capabilities.

ImprovementLuciadFusion

ImprovementLuciadFusion

LCD-2833

Painting performance when using many different icons (more than 100) has been considerably improved. You can disable this change using the system property -Dcom.luciad.view.lightspeed.painter.TLspShapePainter.iconAtlasSupport=false

LCD-3702

The sample layer factories DatabaseLayerFactory (Lightspeed and GXY views) were removed. You can use UnstyledLayerFactory (Lightspeed) and GXYUnstyledLayerFactory (GXY) instead. They offer the same functionality but are not database-specific.

ImprovementLuciadFusion

LCD-3702

Bug fixLuciadFusion

LF-498

Two bugs were fixed affecting some WMTS layer's tile matrix set limits, if defined.

Tile matrix sets for less detailed levels are always included if there is a more detailed level for which a tile matrix set limit exists, even if the tiles for the less detailed levels are empty. This improves memory consumption on the WMTS client, and avoids potential OutOfMemoryErrors, especially for high-resolution coverages.
Tile matrix set limits can never be about other levels than those defined by the tile matrix set itself.

Bug fixLuciadFusion

LCD-856

The JDBC driver used to connect to SQLite databases has been changed to a custom implementation that is more robust. In particular, it avoids certain rare native crashes that could occur.

Bug fixLuciadFusion

The classes of the samples are now delivered in jar files. These jar files are located in the samples/lib folder of the LuciadMap distribution. This prevents error messages about java.util.ServiceConfigurationErrors. The sample classes used to be delivered as extracted class files in the samples/classes folder.

Bug fixLuciadFusion

LCD-3372, LCD-3649

Added a workaround for a Java 7 bug on Linux where multiple screen setups were not dealt with correctly leading to problems when dragging a Lightspeed view from one screen to another. The workaround is enabled by default. It can be disabled using the system property -Dcom.luciad.view.lightspeed.multipleScreenWorkAroundForLinuxJava7Enabled=false.

Bug fixLuciadFusion

TLcdAWTUtil now has a method invokeAndWait that takes a Callable as an argument. This allows to conveniently return a result computed on the event dispatch thread.

Upgrade considerationLuciadFusion

ALfnServiceContext.getCompositeFormat is a new abstract method on an abstract class. There should be no custom extensions of this class. However, if there are, those will need to implement the new method. It is safe to implement this method to return null.

Upgrade considerationLuciadFusion

LCD-4324

TLcdWMTSModelDescriptor now doesn't implement ILcdEarthModelDescriptor anymore. Models for individual WMTS layers will still have a model descriptor that is both TLcdWMTSModelDescriptor and ILcdEarthModelDescriptor. However, when decoding multiple WMTS layers, the decoded model is a model tree node, with no data in the root node and sub-models for each WMTS layer. Since the root node does not contain any data, it should not have an ILcdEarthModelDescriptor.

Upgrade considerationLuciadFusion

TLspShapePainter now only applies style change events from its own stylers. In particular, style events with the wrong event source will be ignored. This can happen when one styler decorates another styler, and forwards events without adapting the source. If you use a styler decorator, make sure it does not attach external listeners to its delegate directly. Instead, it should intercept the events of the delegate and re-fire the events, as shown here:

        public class StylerDecorator extends ALspStyler {
            private final ILspStyler fDelegate;

            private StylerDecorator( ILspStyler aDelegate ) {
                fDelegate = aDelegate;
                fDelegate.addStyleChangeListener( new ILspStyleChangeListener() {
                    @Override public void styleChanged( TLspStyleChangeEvent aEvent ) {
                        fireStyleChangeEvent( aEvent.getAffectedModel(), aEvent.getAffectedObjects(), aEvent.getAffectedStyles() );
                    }
                } );
            }

            @Override public void style( Collection aObjects, ALspStyleCollector aStyleCollector, TLspContext aContext ) {
                // ...
            }
        }

Upgrade considerationLuciadFusion

Bug fixLuciadFusion

LCD-4363

LCD-4141

TLcdGeoJsonModelEncoder can now encode more shapes.

Empty ILcdShapeLists are now encoded as empty GeometryCollections
The baseShape of an ILcdExtrudedShape will now be encoded to a GeoJson geometry
An ILcdSurface is now encoded as a Polygon (provided all the rings are also an instance of ILcdPointList)
An ILcdRing is now encoded as a Polygon (provided it is also an instance of ILcdPointList)
An ILcdCurve is now encoded as a LineString (provided it is also an instance of ILcdPointList)

Bug fixLuciadFusion

LCD-1517

The Z order property of ALspStyle is now applied globally across different style types, whereas before it was only considered within groups of objects with the same type of style.

ImprovementLuciadFusion

TLcdGeoTIFFModelEncoder will now produce stripped images when the tile width and/or height properties are set to zero.

ImprovementLuciadFusion

LCD-1842

TLspPointToPointSnapper: improved the snapping performance when working with many points.

Bug fixLuciadFusion

LCD-4040

The make_osgi_bundles script now also processes the native libraries necessary for LuciadLightspeed's touch support.

Bug fixLuciadFusion

LCD-4031

Fixed balloon rendering problem for jdk 1.5 that would cause greater-than signs to appear at the side of the balloon.

Bug fixLuciadFusion

LCD-4028

Bug fixLuciadFusion

LF-464

Bug fixLuciadFusion

Bug fixLuciadFusion

LCD-1468

TLcdEarthElevationDataCombiner: did not support tiles with odd tile resolutions.

ImprovementLuciadFusion

The LuciadLightspeed distribution now contains a sample that creates the necessary metadata to integrate LuciadLightspeed into OSGi-based projects. You can get started by running the make_osgi_bundles.bat (on Windows) or make_osgi_bundles.sh (on Unix-like systems) in the build/osgi directory. You can find additional information in the 'Running in OSGi' chapter in LuciadLightspeed's developer's guide.

ImprovementLuciadFusion

ALcdAnimationManager now uses a default update rate of 60 Hz instead of 30 Hz. This is in line with today's monitor refresh rates.

ImprovementLuciadFusion

LCD-3471

The Multi-threaded Data Access chapter in the LuciadLightspeed Developer's Guide has been completely revised.

ImprovementLuciadFusion

The Web Client Suite developer's guide (OGCWebClientSuite_DeveloperGuide.pdf)
The class javadoc of TLcdWMTSModelDecoder and TLcdWMTSClient
The package javadoc of com.luciad.ogc.wmts

Icon painting performance when using TLspShapePainter or TLspShapeLayerBuilder has been improved for the case where many different icons are used.

ImprovementLuciadFusion

When tiles are deleted from a Tile Store, space is now reclaimed. Bear in mind that putting tiles over existing ones does not reclaim space; rather the whole history of the tiles is preserved.

ImprovementLuciadFusion

TLcdGXYViewComponentPrintable was introduced to make it easier to setup multi-page printing and printing of a view layed out in a Swing hierarchy. The printable can also create a preview component (TLcdPrintPreview). This is demonstrated in the printing sample. For more information on printing, refer to the developer's guide Chapter on printing.

ImprovementLuciadFusion

Terminology: a bounding shape has been renamed to a clipping shape. This brings LuciadFusion terminology in line with that of LuciadMap (Earth). This change reflected in the API and the documentation.

The method ALfnAssetMetadata.getBoundingShape() has been deprecated in favor of ALfnAssetMetadata.getClippingShape().
The builder method ALfnAssetMetadata.Builder.setBoundingShape() has been deprecated in favor of ALfnAssetMetadata.Builder.clippingShape().

ImprovementLuciadFusion

All setters on the metadata builders "setSomething(Something aSomething)" have been renamed to "something(Something aSomething)". This brings LuciadFusion conventions in line with those of LuciadLightspeed. The old setters have been deprecated for backwards compatibility, and refer to their new counterparts. Some examples (non-exhaustive list):

ALfnResourceMetadata.Builder.setId(String aId) => ALfnResourceMetadata.Builder.id(String aId)
TLfnVectorCoverageMetadata.Builder.setMaxLevel(int aLevel) => TLfnVectorCoverageMetadata.Builder.maxLevel(int aLevel)

ImprovementLuciadFusion

Fusion of coverages can now also be performed on the server. A system which is both fusion server and tile server is a typical setup. In a more advanced setup, client, fusion server and tile server are all different systems. The client and fusion server both require access to the source data. The data root of the source data may be different on the different machines. You can define path prefixes to make abstraction of system-specific data roots.

Work has been done to centralize all the information about the fusion of a coverage on the tile server. If a fusion server breaks down, another fusion server has all the information it needs to be able to continue the work. Some configuration has been moved from the engine session to the coverage. Line simplification, area simplification, filtering etc. can now be configured on the coverage rather than on the engine session.

ImprovementLuciadFusion

This means ALfnEngineEnvironment.getCheckpointDirectory is not used anymore. Using null to disable checkpoints is still valid, but instead you should set the checkpoint interval to -1 (you can set it with RasterSessionBuilder.setCheckpointInterval or VectorSessionBuilder.setCheckpointInterval).

ImprovementLuciadFusion

LCD-3501

Added support for ILcdAnchoredIcon in TLspIconStyle. Anchored icons will automatically be displaced to their anchor-points. Their center of rotation will also shift to their anchor point.

ImprovementLuciadFusion

TLcdWatermarkPrintable and TLcdCompositePageable were added. TLcdWatermarkPrintable makes it possible to decorate a Printable with a textual watermark. TLcdCompositePageable makes it possible to compose different Pageables.

ImprovementLuciadFusion

LCD-3497

Loading or refreshing groundoverlays now happens more efficiently.

ImprovementLuciadFusion

Several GXY samples have been combined, renamed and restructured. Most notably, there is now a single decoder sample that is able to open all supported formats.

ImprovementLuciadFusion

TLcdIndexColorModel now supports TLcdColorMap instances whose levels do not map directly to raster values by making use of an ILcdRasterValueConverter. This allows retaining the semantics of the color map's levels (e.g. height, temperature).

ImprovementLuciadFusion

TLcdKML22RenderableModel.applyOnInteracts2DBounds now returns screenoverlay elements if it is queried with an undefined bounds. (See ILcdBounds.isDefined)

ImprovementLuciadFusion

LCD-3303, LCD-2373

TLspCreateController now starts its creation on mouse-moved events instead of on the first mouse released event. This allows creation handles to perform visualizations before the first click. As a first use case, TLspPointSetHandle has been updated to show its point while the mouse is hovering over the globe. This allows you to see snapping on your first point while creating objects.

ImprovementLuciadFusion

ILspTaskExecutor now supports executing tasks with a delay. This can for example be used to easily throttle how often a task is run. The delay can be configured on TLspTaskExecutorRunnable.

ImprovementLuciadFusion

The "fusion.engine" GUI sample and "fusion.engine.coveragecropper" CLI sample have been replaced with a comprehensive command-line fusion tool: "fusion.engine". Limitations:

Fusing GRIB data is not supported.

ImprovementLuciadFusion

ImprovementLuciadFusion

LCD-3051

TLspViewBuilder has new methods viewType() and worldReference(), which allow the new views to be pre-configured as 2D or 3D with a given reference. These methods can be used in lieu of a subsequent call to TLspViewTransformationUtil.

ImprovementLuciadFusion

LCD-263

The label painters now try to make use of ILcdCache as much as possible when enabling halo painting. This removes the need to manually clear the painter's cache when the domain object implements ILcdCache.

ImprovementLuciadFusion

ImprovementLuciadFusion

Various samples were changed:

The "streets" sample was moved to the LuciadLightspeed Demo, see samples.lightspeed.demo.application.data.streets
Various label samples were merged into one, see samples.lightspeed.label.placement

ImprovementLuciadFusion

The new classes TLcdGXYViewMeasureProvider and TLspViewMeasureProvider allow retrieving data values for any point in a view, such as the magnetic north declination or weather information. implementations for the relevant models and layers. To see it in action in a sample, simply To see this in action in a sample, simply hover the mouse over any part of the view displaying such information in, for example, the magnetic north sample.

ImprovementLuciadFusion

LCD-2997

Dependencies between labels of non-discrete and discrete labeling algorithms are now supported by default.

ImprovementLuciadFusion

LCD-3333

TLspRasterLayer now supports queries, similar to ILspInteractivePaintableLayer. This allows for example to determine which raster value is painted at a specific pixel in the view.

ImprovementLuciadFusion

LCD-3346

TLspLabelStyler now implements ILspCustomizableStyler.

ImprovementLuciadFusion

LCD-3134

ImprovementLuciadFusion

TLcdGUIIcon has a new icon for routes.

ImprovementLuciadFusion

LCD-677

TLcdEllipsoidRhumblineUtil.closestPointOnRhumbline() was added.

ImprovementLuciadFusion

LCD-3349

Curved path labels (TLcdGXYCurvedPathLabelPainter) now avoid too much curvature, eliminating most self-overlap.

Bug fixLuciadFusion

The equals() and hashCode() methods of TLspViewXYZWorldTransformation2D and TLspViewXYZWorldTransformation3D did not take the entire state of the transformation (such as camera constraints and the installed listeners) into account. Now they use the transformation's identity. To only compare what the transformation shows, use the getIdentifier() method.

Bug fixLuciadFusion

LCD-1596

Fixed a number of compatibility issues with TLspAWTView and JDK 1.7. In particular, the full screen toggle in the Lightspeed samples is now also available when JDK 1.7 is used.

Bug fixLuciadFusion

Fixed an issue in TLspShapePainter where points that were projected out-of-bounds could be painted at (0,0) in 2D. Points that fall outside the projection are now always properly discarded during painting.

Bug fixLuciadFusion

The WFS service in the LuciadFusion Data Server did not correctly handle XML POST requests.

Bug fixLuciadFusion

LCD-3374, LCD-2061, LCD-3202

The view fitting when using TLspViewTransformationUtil or TLspViewNavigationUtil has been improved significantly:

fit accounts for the rotation of the view when fitting in 2D
fit more accurately accounts for terrain elevation and the vertical dimension of 3D objects
more accurate view preservation when switching from 2D to 3D

Bug fixLuciadFusion

LCD-1917

Upgrade considerationLuciadFusion

ILcdGLDrawable has new methods, invokeAndWait() and invokeLater(), which invoke a runnable with the guarantee that the drawable's OpenGL context is current.

Upgrade considerationLuciadFusion

The packaging of LuciadLightspeed has been streamlined:

The javadoc is now packaged in a separate zip file called Javadoc.zip. That way you can avoid downloading and extracting this documentation.
There are now more, but smaller, jar files for LuciadLightspeed. This avoids circular dependencies between jar files that were present in previous versions of LuciadLightspeed. That should make it easier to integrate the jar files in some build tools.
The jar files of third party libraries now contain the version number in their filename. That way you can easily determine the version of a jar file.
The resources of a jar file are no longer packaged in separate jar files. This way it is clearer that these resources are not optional. This also reduces the number of jar files that are included in the release. Only the optional geoid resources remain in a separate jar file.

The prerequisites pages in the Technical notes section was updated to reflect these changes. Please take a look at those for more detailed information.

Upgrade considerationLuciadFusion

Added support for creating a Lightspeed view that is not geographically referenced. The lightspeed.nongeoreferenced sample demonstrates this. To accommodate this the following API has changed:

A model with a reference that does not implement ILcdGeoReference is no longer interpreted as data defined in view coordinates. A null model reference is now used for data in view coordinates. This is demonstrated in the lightspeed.paintinview sample.
ALspStyleTargetProvider.getStyleTargetReference now returns an ILcdModelReference instead of an ILcdGeoReference. For all Luciad ILcdGeoReference implementations you can simply cast the reference to ILcdModelReference.
The default transformations now also support identity transformations between custom references.

Upgrade considerationLuciadFusion

An ILcdOWSRequest now supports REST encoding, if applicable. Implementations must now implement "getRestEncoding", but can return null to indicate that it is not supported.

Upgrade considerationLuciadFusion

The constructor of TLspPaintRepresentationState has been removed. Please use TLspPaintRepresentationState.getInstance instead. This ensures that for every paint representation and paint state combination there is only one unique instance. This is important to ensure correctness when using paint representation state instances as key in an identity hash map for example.

Upgrade considerationLuciadFusion

The ALspInteractiveLabelProvider#dispatchAWTEvent() and ALspInteractiveLabelProvider#convertAWTEvent() methods were removed. Because of this change, the event dispatching mechanism of AWT is used, which solves problems in corner cases. After this change

the removed methods are not called anymore causing a possible behavioral change.
rather than handling all events for all components and subcomponents of an interactive label via a single method, it will be needed to register listeners on the components for which events are required.
some custom event dispatching is no longer possible. For example: dispatching left mouse button events to a sub component, but handling middle mouse button events in the parent component is no longer feasible using the standard AWT event dispatching system. This is something that AWT does not support.

Upgrade considerationLuciadFusion

The interface ILfnFusionHandler was removed from the API because it was not used anywhere. Any existing implementations can safely be removed.

Upgrade considerationLuciadFusion

ILcdEarthParameterizedIcon now gets a double[] parameter in its getWidth() and getHeight() methods. As a result of this change you may get some compile errors. Implementations of ILcdEarthParameterizedIcon can be fixed by adding the double[] parameter to the methods. Implementations can be improved by using the double[] parameter in the implementation. Callers of these methods should pass the parameters to it.

Upgrade considerationLuciadFusion

LF-36

The Java Servlet dependency has been upgraded from version 2.4 to 2.5. Consequently, an application server or servlet container with support for Java Servlet 2.5 or higher is now required for deployment - for instance, Tomcat 6 or higher. The impact of this is expected to be low since Java Servlet 2.5 is widely adopted by application server and servlet container products for over 7 years.

Upgrade considerationLuciadFusion

The Java Servlet dependency has been upgraded from version 2.4 to 2.5. Consequently, an application server or servlet container with support for Java Servlet 2.5 or higher is now required for deployment - for instance, Tomcat 6 or higher. The impact of this is expected to be low since Java Servlet 2.5 is widely adopted by application server and servlet container products for over 7 years.

Upgrade considerationLuciadFusion

LCD-377

TLcdIconSW has been deprecated in favor of TLcdSWIcon.

Upgrade considerationLuciadFusion

LCD-2978

The HTTP authentication libraries (withay-http.jar, withay-util.jar) are no longer needed and have been removed from the release.

Upgrade considerationLuciadFusion

LCD-878

The implementation of TLcdXYBounds and TLcdXYZBounds have changed slightly. The functionality has not been changed, but the internal method call sequence has. These methods do not always call their related 2D methods anymore: contains3D, interacts3D, setTo3DUnion, setTo3DIntersection and setToInclude3DPoint. For example, contains3D does not always invoke contains2D.

Upgrade considerationLuciadFusion

LCD-878

An ILcdBounds instance can now be undefined. This means that the instance does not describe a geographic region. For this, there is a new method on ILcdBounds: isDefined(). Implementations must add this method. Usually, returning true is enough. Extensions of ALcd2DEditableBounds can use setDefined(boolean) to manage the defined status. The behavior of the LuciadLightspeed bounds implementations is mostly the same.

Use ALcdBounds.isDefined(aBounds) as a shorthand to check for null bounds or undefined bounds
Bounds transformations will throw TLcdNoBoundsException if the input bounds is undefined
Composite shapes such as ILcdShapeList, ILcdPointLists, ILcdPolygon, etc. will return undefined bounds if they are empty

When creating new bounds instances using LuciadLightspeed implementations:

default (empty) constructors -> undefined
constructors with values -> defined
copy constructor -> copies defined status
clone* -> copies defined status
equals/hashCode -> take defined status into account

When modifying bounds instances:

move?D, translate?D, setWidth, setHeight, setDepth -> instance becomes defined

When testing with bounds instances:

undefined.contains?D(anything) = false
undefined.interacts?D(anything) = false
defined.contains?D(undefined bounds) = false
defined.interacts?D(undefined bounds) = false
Note: this means that new TLcdLonLatBounds().contains2D(0, 0) now returns false instead of true

Calculating intersections:

Position, width and height are always updated as before
undefined.setTo?DIntersection(anything) -> stays undefined
defined.setTo?DIntersection(undefined bounds) -> becomes undefined
defined.setTo?DIntersection(defined bounds, but disjoint, no overlap) -> becomes undefined

Calculating unions:

undefined.setTo?DUnion(defined bounds) -> becomes defined, equal to given bounds
defined/undefined.setTo?DUnion(undefined bounds) -> no change in bounds or defined status
setToIncludePoint?D -> same as union

Upgrade considerationLuciadFusion

ILspShapeDiscretizer's previously deprecated canDiscretize method has been removed. Instead discretizeSFCT should throw a TLspDiscretizationException if it is not capable to discretize the provided shape. Implementations of ILspShapeDiscretizer can simply remove this method. Callers of canDiscretize should instead check whether above exception is thrown on a discretizeSFCT call.

ImprovementLuciadFusion

LCD-3730

The balloon managers now respect the maximum size of a balloon content panel when determining the initial size.

ImprovementLuciadFusion

LCD-3640

Added support for fitting on an image projection layer.

Bug fixLuciadFusion

LCD-3731

Bug fixLuciadFusion

Lightspeed views did not properly terminate all background threads when they were destroyed.

Bug fixLuciadFusion

LCD-3643

Fixed an issue with Cartesian ruler measurements created at the wrong altitude when the view's altitude exaggeration differs from 1.

Bug fixLuciadFusion

LCD-3642

Bug fixLuciadFusion

LCD-3573

Bug fixLuciadFusion

LCD-3469

TLcdInputStreamFactory would throw a StringIndexOutOfBoundsException when passing a URI of the form file://\\path\to\file\on\server. URI's of such forms are for example encountered when using drag-and-drop

ImprovementLuciadFusion

LCD-3331, LCD-3372

TLspSwingView is a new ILspView implementation which is backed by a lightweight component (unlike TLspAWTView, which is heavyweight). The two views are otherwise fully equivalent. Using a lightweight view, however, can solve some specific integration issues that may occur, e.g. when adding the view to a JInternalFrame or an SWT user interface.

Please read the TLspSwingView class javadoc for important information on the performance of lightweight vs. heavyweight views.

ImprovementLuciadFusion

The WFS property name filtering mechanism was not supported for domain objects that implemented ILcdDataObject, but were not extensions of the class TLcdDataObject. The latter restriction has been removed: any implementation of ILcdDataObject is now supported.

Bug fixLuciadFusion

LCD-3422

Calling TLcdJPLEllipsoidFactory using Ellipse_Sphere did not create a spherical ellipsoid.

Bug fixLuciadFusion

LCD-3420

When editing labels using TLcdGXYOffsetIconPainter, the selected labels were painted at the incorrect location.

ImprovementLuciadFusion

LCD-3116

When zooming in on a region were no detailed imagery is available, imagery with less detail will be displayed instead of the white fallback images.

ImprovementLuciadFusion

Information from the individual S-57 cell files was used to create assets for S-57 catalogues; as a result, the creation of assets for large catalogues could take a significant amount of time. This has been fixed. The fix for LF-358 (see below) was reverted in order to fix this issue.

Bug fixLuciadFusion

LF-377

Logging of the license server has been extended: the license server for each license request now logs which clients are currently using a license. The port at which the request came in is now also logged, allowing to map each incoming request to its corresponding license file.

ImprovementLuciadFusion

LCD-2174

The predefined hatch fill pattern in TLspFillStyle has been improved to provide better visual results.

ImprovementLuciadFusion

LF-283

When creating a raster asset from a raster coverage, the bounding boxes and pixel densities of the individual original asset parts are now taken into account. This has a couple of interesting consequences:

Coverage cropping now also works efficiently for coverages with non-uniform pixel densities.
The pixelDensity argument of the TLfnTileStoreUtil.newCoverageAsAssetMetadataBuilder has become obsolete. This method has now been deprecated in favor of a new method without the pixelDensity parameter. The new method also throws appropriate exceptions when accessing the Tile Store fails. There is no longer any need to compute the pixel density upfront using

TLfnRasterCoverageMetadata.Builder.setTileLayout was added as a convenience method to set both the tile width and height with a single call.

Bug fixLuciadFusion

LCD-2906

Bug fixLuciadFusion

Image projection layers (see TLspImageProjectionLayerBuilder) could throw an IllegalArgumentException when calling getStyler() with a valid paint representation.

Bug fixLuciadFusion

TLspRulerController: geodetic measurements were offset by a small amount. This was introduced in the 2012.1.01 patch release.

Bug fixLuciadFusion

LCD-1480

When building a query, specifying an empty array of property-value pairs now behaves as if not invoked, rather than resulting in a StackOverflowError. The affected methods are TLfnQuery.BasicBuilder.andFilterAnyDoNotEqual() and andFilterAnyEqual().

Bug fixLuciadFusion

LCD-3309

LCD-3045

The GeoTIFF encoder used in the WCS now encodes tiles with an odd resolution or a byte indexed color model more accurately.

ImprovementLuciadFusion

SLD styles (TLcdSLDFeatureTypeStyle) can now be used in a Lightspeed view, through the TLspSLDStyler class. This styler supports the most commonly used features of the standard. Please refer to the developer guide for an overview.

ImprovementLuciadFusion

SLD now supports decoding and encoding of Symbology Encoding 1.1.0 styles. By default, new styles will also be saved as 1.1.0 styles.
The following features from version 1.1.0 are supported:

Inline encoding of binary and svg icons.
New standardized functions such as interpolate, recode, formatDate, categorize,...
Line widths specified in world units.

ImprovementLuciadFusion

In order to optimize visualization of vector data for a specific use case, the ELfnDataDensity property was added to the coverage metadata. It is a hint for the visualization how the visualization should be optimized:

OVERVIEW is the optimal setting for vast otherwise not so detailed data, such as the world's coutries. This is the default.
DETAIL is the optimal setting for detailed data that does not need to be visible far towards the horizon, such as roads or buildings.

ImprovementLuciadFusion

It is now possible to plug in custom implementations of a metadata store, for example a database implementation.

ALfnBinaryMetadataStore provides the abstraction of a metadata store.
Constructors were added to TLfnFileSystemTileStore to allow these implementations to be plugged in.
A method ALfnTileStore.close() was added, which custom implementations may override to clean up held resources, such as database handles. Application code that owns a Tile Store instance should call this method when appropriate.

ImprovementLuciadFusion

Calling getFocusPoint() on a Fusion vector feature no longer triggers the loading of the geometry tiles at the most detailed level.

ImprovementLuciadFusion

Added extra methods to ALspCreateControllerModel that are called whenever object creation is cancelled or finished.

ImprovementLuciadFusion

LCD-2199

An extra fireStyleChangeEvent method has been added to TLspStyleChangeSupport allowing to fire a TLspStyleChangeEvent by passing the event as a parameter to the fireStyleChangeEvent method.

ImprovementLuciadFusion

The vertical view now uses anti-aliasing by default. This can be changed with the setAntiAliasing method in TLcdDefaultVVRenderer, TLcdDefaultVVRendererJ2D and TLcdDefaultVVGridRenderer.

ImprovementLuciadFusion

ImprovementLuciadFusion

LCD-1010

The handling of scale ranges in the GXY painter implementation of SLD has been aligned with how scales are computed for the TLcdGXYScaleIndicator.

ImprovementLuciadFusion

It is now possible to configure the spacing between the grid lines of a lon-lat grid. See com.luciad.view.lightspeed.painter.grid.TLspLonLatGridLayerBuilder.spacingRange() for details.

ImprovementLuciadFusion

MGRS grids can now be displayed in a Lightspeed view using the new TLspMGRSGridLayerBuilder. This is demonstrated in the grid sample.

ImprovementLuciadFusion

Improved bounds transformations from geocentric to geodetic when the geocentric bounds contain a pole.

ImprovementLuciadFusion

New API was added to allow for the quick implementation of an action that works on the currently selected objects: ALcdObjectSelectionAction.

ImprovementLuciadFusion

Introduced TLcdDomainObjectContext in the API. This class is a container for information about a domain object.

ImprovementLuciadFusion

LCD-2566

The SLD decoders now avoid adding default values that are not specified in the XML or as a default value in the SLD schema. This ensures that an SLD can be decoded and encoded without making (small) changes to the data.

ImprovementLuciadFusion

Bug fixLuciadFusion

LCD-1478

The checkboxes for enabling/disabling individual coverages in the fusion.client.proxy3d sample now work correctly.

Bug fixLuciadFusion

LCD-1484

Visualization of fused VMAP2i vector data could result in the GeoSymStyleProvider throwing a NullPointerException. This has now been fixed.

Bug fixLuciadFusion

Bug fixLuciadFusion

LF-356

Complex polygons containing duplicate polygons are unsupported by fusion. However, fusion's behavior was not consistent: sometimes it silently accepted those polygons, and sometimes it failed with the error message "Unsupported polygon: sequence of end points without intermediate begin point". This has now been fixed so that fusion always fails on those polygons with the error message "Complex polygon contains duplicate polygons".

There was a bug in VPF which was a common source of this type of unsupported polygons. This bug has now been fixed as well.

Bug fixLuciadFusion

LF-351

Sometimes, when a polygon fully covers a tile but touches it on the edge, it could happen that the affected tile was missing its parts of the geometry's fill. When visualizing the fused data, this could lead to unexpected "holes", or in the worst case, an IllegalStateException with message "Got N fills". This has now been fixed.

Bug fixLuciadFusion

LCD-2919

TLspRasterLayer: the raster layer ignored the levelSwitchFactor for interactive raster layers with an Earth model.

Bug fixLuciadFusion

LCD-2841

TLspLabelingAlgorithm often reused previous placements, event if they become invalid. In order to fix this for custom ALspLabelLocationProvider implementations, ALspLabelLocationProvider now contains an isValidLocation() method, which can be implemented.

Bug fixLuciadFusion

LCD-684

Some datum transformations from references retrieved with TLcdEPSGReferenceParser were incorrect.

Bug fixLuciadFusion

TLspLabelPainter didn't handle the ALspStampLabelLocation world rotation offset correctly in all cases.

Bug fixLuciadFusion

TLspShapeEditor and TLspShapeListEditor now correctly support recursive shapelists. (i.e. shapelists within shapelists)

Bug fixLuciadFusion

Fix NPE when adding a null styler to TLspLabelPainter.

Bug fixLuciadFusion

LCD-2581

In some cases, lon lat grid labels were missing.

Bug fixLuciadFusion

During creation, TLspLonLatHeightBufferEditor now determines the initial width based on the length of the first segment of the axis.

Bug fixLuciadFusion

LCD-2494

TLcdUTMZonePainter no longer paints scale labels in the UPS zones.

Bug fixLuciadFusion

LCD-2468

The terrain no longer contains gaps. Previously there could be small gaps in the terrain in some world references.

Bug fixLuciadFusion

LCD-120

TLcdUTMZonePainter now respects the label color settings for all labels.

Bug fixLuciadFusion

LCD-2710

Improved the accuracy of TLcdUTMZone#getMaxXYBounds.

Upgrade considerationLuciadFusion

ALspDensityStyle and its descendants no longer implement ILspWorldElevationStyle. The elevation mode property defined in the density styles was redundant, as there is an equivalent setting in TLspDensityLayerBuilder which took precedence. Code that used the elevationMode() method of the density style builders will now result in a compilation error; it should be updated to call the elevationMode() method on TLspDensityLayerBuilder instead.

Upgrade considerationLuciadFusion

The new 'OBJECT_DEPENDENT' ElevationMode is now used as the default for TLspLineStyle, TLspFillStyle, TLspIconStyle and TLspWorldSizedLineStyle. This greatly simplifies the creation of styles and stylers, as this elevation mode will provide the best result in most cases. Customers that use a 3D view and rely on the previous default (ABOVE_ELLIPSOID) may want to update their stylers to explicitly use ABOVE_ELLIPSOID.

Upgrade considerationLuciadFusion

The structure of the jar files has been changed:

lcd_earth_3d.jar has been merged into lcd_3d.jar
lcd_wms_client_tiled.jar has been merged into lcd_wms_client.jar
lcd_beans.jar is no longer present in the release

If you copy the new jar files over your existing ones, you should delete the old jar files mentioned in the list.

Upgrade considerationLuciadFusion

The 'blend overlap' property of TLspLineStyle is now represented by an enumeration that allows setting the mode to 'AUTO'. This new mode is also the new default, so existing applications that required that blendOverlap was set to false, will now have to set it to 'NEVER'. Do note that the new 'AUTO' mode will result in the correct behaviour in most cases.

The default styler for shape layers has also been adapted to use this 'AUTO' mode.

Upgrade considerationLuciadFusion

A new method, isNormalized(), has been added to ILspVertexAttribute. This allows users to describe whether a vertex attribute is normalized, i.e. in the [0, 1] range, or not. This flag is used internally when calling glVertexAttribPointer().

Upgrade considerationLuciadFusion

ILspEditor no longer extends ILcdUndoableSource. As a result, it is no longer possible to attach undoable listeners to editors in general. The functionality has been moved to TLspEditOperationResult. This object now stores an undoable. Like before, each edit operation will create a TLspEditOperationResult. This now has a getUndoable() and a constructor that allows you to supply the result with an undoable.

So how does this affect your editors? The following rules should apply:

If you haven't customized any editors: No change in your code should be required.
If you implemented a simple ALspEditor: Everything should work without change to your code. ALspEditor itself has been modified internally to work with the new undo behavior. This will still propagate correctly to the edit controller.
If you implemented an ALspEditor that delegates to another editor: Make sure that you check the TLspEditOperationResult of your delegate first. If this contains an undoable, you should pass this undoable
If you implemented a fully custom ILspEditor: The same rules apply as the bullet point above. Also, if you generate your own undoables, be sure to create new TLspEditOperationResult objects that contain them, instead of firing the undoable as you would before.

A general rule is that, if you had the following code:

      @Override
      public TLspEditOperationResult edit(...){
        //Do edit
        ILcdUndoable undoable = ...
        fireUndoableEvent(new TLcdUndoableEvent(this, undoable));
        return TLspEditOperationResult.SUCCESS;
      }

You should replace it with:

      @Override
      public TLspEditOperationResult edit(...){
        //Do edit
        ILcdUndoable undoable = ...
        TLspEditOperationResult result = new TLspEditOperationResult(isSuccesful, isInvalid, undoable);
        return result;
      }

Upgrade considerationLuciadFusion

The TLspExtrudedShapeEditor no longer returns true for the canEdit method in case its delegate can edit the shape, for consistency with all the other editors. Now each ALspEditor only accepts shapes it can edit itself. The new recommended way to create an editor that supports both extruded shapes and a specific delegate shape is as follows:

      TLspCompositeEditor compositeEditor = new TLspCompositeEditor();
      compositeEditor.addEditor(new TLspExtrudedShapeEditor(compositeEditor));
      compositeEditor.addEditor(new TLsp2DPointListEditor());

The example above works for when you want an editor that edits both 2D pointlists and extruded 2D pointlists.

Upgrade considerationLuciadFusion

Some methods in ALspStyleCollectorWrapper and ALspLabelStyleCollectorWrapper have been made final. These methods now convert the argument and forward the call to another method of the wrapper class. An example is the 'object' method, which wraps its argument in a Collection and forwards the call to the 'objects' method. Now it is no longer needed to override both the 'object' and 'objects' method, but it is sufficient to override the 'objects' method.

In case you have overridden one of the affected methods, you will get a compile error. Normally, you can just delete that overridden final method. The custom behavior of that method should already be included in the other method, otherwise your extension violated the documentation. So in case you had an extension of ALspStyleCollectorWrapper containing the following code:

      @Override
      public ALspStyleCollectorWrapper object( Object aObject ){
        doSomethingCustom( Collections.singleton( aObject ) );
        return super.object( aObject );
      }
      @Override
      public ALspStyleCollectorWrapper objects( Collection<? extends Object> aObjects ){
        doSomethingCustom( aObjects );
        return super.objects( aObjects );
      }

You can just delete the custom 'object' method.

Upgrade considerationLuciadFusion

The Batik libraries have been upgraded from version 1.5 to 1.7, to solve issues with respect to SVG XML decoding. Users that are relying on SVG support inside the WMS will need to update their build process accordingly. SVG can be used in the WMS as map output format (through TLcdGXYViewSVGEncoder) or inside OGC Symbology Encoding styles (in an SLD-enabled WMS). If SVG is not used, the Batik libraries are not required.

Upgrade considerationLuciadFusion

A third library dependency on Batik 1.7 has been added to support the use of SVG in Symbology Encoding 1.1.0 styles. Existing users of SLD will need to include Batik in their build process if they require support for SVG. If SLD is not used or if SVG support inside these styles is not needed, the Batik libraries are not required.

Upgrade considerationLuciadFusion

The method TLfnLTSRequestDispatcherFactory.createRequestDispatcher now declares a ServletException in its 'throws' clause. Any decorator implementations need to be adapted to propagate this exception in their 'throws' clause. The same goes for any extensions of this class that call super.createRequestDispatcher. Other implementations that used to wrap ServletExceptions into RuntimeExceptions may be simplified by removing the wrapping and throw ServletExceptions directly.

Upgrade considerationLuciadFusion

ILspLabelPainter.getAnchorObject() can now also return ALspStyleTargetProvider instances. These can for example return anchor objects in a different reference than the model reference.

Upgrade considerationLuciadFusion

The signature of the ALspSwingLabelStyler.paintImage(JComponent, Dimension, TLspContext) method was changed to ALspSwingLabelStyler.paintImage(JComponent, Dimension, Object, Object, TLspContext) in order to provide more information about the label for which an image is created.

Upgrade considerationLuciadFusion

ILspLabelPainter.getAnchorObject now throws an TLcdNoBoundsException, to indicate that no anchor object could be found.

Upgrade considerationLuciadFusion

TLspEditingStateEvent now extends from EventObject. Because of this, the constructor was adjusted to include a source argument. Also the TLspEditingSupport constructor now has a source argument.

Upgrade considerationLuciadFusion

TLcdGXYLonLatHeightBufferPainter has been deprecated in favor of TLcdGXYBufferPainter and TLcdGXYGeoBufferPainter.

Bug fixLuciadFusion

Bug fixLuciadFusion

LCD-2894

Some property change events fired by the TLspScaleIndicator had an incorrect property name.

Bug fixLuciadFusion

LCD-2894

Some property change events fired by the TLcdGXYScaleIndicator had an incorrect property name.

Bug fixLuciadFusion

LCD-2890

TLcdGeoTIFFModelEncoder did not correctly respect the configured level count.

Bug fixLuciadFusion

LCD-2877

In certain stereographic projections, TLcdUTMZonePainter's paint method could hang.

Bug fixLuciadFusion

LCD-2867

A number of issues have been fixed regarding import/export of coverages and DigestExceptions.

Several fixes for interactive labels:

In some cases labels were painted twice, or not at all. This fix introduces a new constructor in ALspSwingLabelStyler, with an ALspInteractiveLabelProvider as argument. This constructor should be called when using a TLspInteractiveLabelsController. For an example of how to use these classes, see the lightspeed.labels.interactive sample.
ALspSwingLabelStyler now has an option to invalidate itself when model changes are thrown.
ALspSwingLabelStyler could cause components to be removed from the Swing hierarchy. This fix also fixes view lags caused by ALspSwingLabelStyler, and fixes label flickering.
The paint state wasn't always correctly restored after moving away from an interactive label

A variable geobuffer shape was introduced, ILcdVariableGeoBuffer. This shape represents a corridor around a given (3D) polyline, adding a width and height to the shape that is defined for every polyline point. It has one implementation, TLcdLonLatHeightVariableGeoBuffer. This shape can be painted and edited using TLcdGXYGeoBufferPainter.

ImprovementLuciadFusion

LCD-2606

The ILcdGXYView implementations needlessly changed their autoUpdate property if the model was changed.

Bug fixLuciadFusion

Bug fixLuciadFusion

LCD-2560

Bug fixLuciadFusion

Fixed a possible ArrayIndexOutOfBoundsException in TLcdGXYPolylineLabelPainter.

Bug fixLuciadFusion

LCD-2523

The LTS Tile Store implementations now also guarantees that the message digest has been filled in before calling ILfnGetTileHandler.found(). This facilitates implementations of LTS proxies and gateways.

Bug fixLuciadFusion

LCD-2501

The default exception handler of the Earth painters and elevation provider now handles interrupted exceptions better.

Bug fixLuciadFusion

LCD-2513

The TLcdHaloAlgorithm.CONVOLUTION algorithm did not work correctly for anti-aliased text.

Bug fixLuciadFusion

LCD-2506

Bug fixLuciadFusion

LCD-729

Fixed issue with cloning of some domain objects.

Bug fixLuciadFusion

LCD-2379, LCD-2383

Possible Exceptions when resizing a 3D view, making it smaller than 0 pixels.

Bug fixLuciadFusion

LCD-2255, LCD-2381

TLcdViewXYZWorldTransformation2D could produce NaN values when the width and height are 0. TLcdViewXYZWorldTransformation could return a negative scale for a negative height.

Bug fixLuciadFusion

The TLspViewXYZWorldTransformation3D.isAdjustDepthRange property wasn't always respected

Bug fixLuciadFusion

LCD-2238, LCD-2253

TLcdRulerController: It wasn't possible to insert or remove points from a measurement when in cartesian mode.

Bug fixLuciadFusion

LCD-698

Interactive labels couldn't be moved on some location of the label.
The position of the interactive and regular label was inconsistent.
It was possible that 1 label was painted twice when enabling interactive labels.
The move cursors wasn't properly set when hovering over the interactive label.

Bug fixLuciadFusion

LCD-1562

ImprovementLuciadFusion

A new elevation mode is available for TLspIconStyle: ABOVE_TERRAIN. It means that the icons are placed above the terrain. The elevation of the object is determined by adding the object's elevation to the terrain's elevation. Since icons are normally centered around this elevated point, it can be partially obscured by the terrain, depending on the view angle. To avoid this, you can either set a fixed offset on the TLspIconStyle, or add a TLspViewDisplacementStyle to allow the icon to be moved above the terrain dynamically depending on the view angle.

ImprovementLuciadFusion

A new icon implementation TLcdCGMIcon has been added to the com.luciad.format.cgm package. This class supports the decoding of an icon that originates from a CGM file.

ImprovementLuciadFusion

LCD-1474

An attempt to decode a non-existent file using TLcdETOPOModelDecoder will now throw an appropriate IOException rather than return an invalid model.

ImprovementLuciadFusion

LCD-179

TLcdColorMapCustomizer: the behavior of adding a level has been simplified to be more predictable. The new level is now always added between the selected and the next level.

ImprovementLuciadFusion

TLcdObliqueMercator: transforming from world to lon lat and from lon lat to world has become more consistent. Points that can be transformed in one direction can now always be transformed back.

ImprovementLuciadFusion

It is now possible to import an entire coverage from any Tile Store to any other Tile Store. The previously existing restriction that the source coverage had to be on a local Tile Store is hereby lifted. A new utility class TLfnTileStoreUtil provides additional convenience methods to copy coverages between Tile Stores.

It is now possible to check the integrity of a local coverage. Each tile can have an optional checksum, according to the message digest algorithm specified on the coverage metadata.

TLfnDigestTileStore is a decorator which verifies tile checksums upon access. It defines a handler to receive notifications of corrupt tiles.
ALfnCoverage.getTileCoordinates provides iteration over all tiles in a coverage. It only works for local coverages retrieved through a TLfnFileSystemTileStore, not for remote ones retrieved through a TLfnLTSClient.

Bug fixLuciadFusion

TLcdGXYAsynchronousPaintQueue now respects the auto-update property of the view.

Bug fixLuciadFusion

LCD-1473

Resolved an issue that the labels of buffer, band or polygon objects stayed in place when moving the objects.

Upgrade considerationLuciadFusion

The API of all asynchronous methods on ALfnCoverage and ALfnTileStore has been made consistent. The changes:

All asynchronous methods return a Future which can be used to block for the result or to cancel the operation
All asynchronous methods require an extension of ILfnFailureHandler defining the throwables which may happen during asynchronous operation. This is the equivalent of a 'throws' clause of a synchronous method.
Exceptions are propagated via the asynchronous handler, or via an ExecutionException thrown when blocking for the result using Future.get(). In case of multiple exceptions, it is the first one which is propagated. Either one of these mechanisms can be used, they are equivalent.
ILfnFailureHandler has an addition callback method cancelled(CancellationException) next to interrupted(InterruptedException). The former happens when a Future is cancelled, while the latter happens when a thread was unexpectedly interrupted.

Beware that, even though methods have an asynchronous signature, they may do some of their work synchronously. Even in this case, throwables which are thrown synchronously (most notably RuntimeExceptions and Errors) are still propagated via the Future and asynchronous handler. The idea is that this is an implementation detail which is transparent to the application.

Upgrade considerationLuciadFusion

New API has been introduced to allow more customization of the editing functionality in Lightspeed views. In the context of this, the ILspEditor interface has changed considerably. If you have implemented this interface and would like assistance to upgrade to a newer version of LuciadLightspeed, please contact Luciad support.

Upgrade considerationLuciadFusion

TLspSelectController's default key to enable multi-object selection has been changed to shift instead of ctrl. The default behavior can be modified by overriding TLspSelectController#selectWhat.

Upgrade considerationLuciadFusion

The domain objects in the ruler controller model have changed. They are now ALspRulerMeasurement instead of ILspRulerPolyline. The controller now also allows to override distance and azimuth calculation.

Upgrade considerationLuciadFusion

ILspShapeDiscretizer's canDiscretize method has been deprecated. Instead discretizeSFCT should throw a TLspDiscretizationException if it is not capable to discretize the provided shape.

Upgrade considerationLuciadFusion

ILspTerrainSupport: all terrain query methods now have an additional TLspContext argument. This is necessary to allow the methods to be called from a separate thread. The context in that case would be a snapshot of the view's state which is used for the terrain query, while the view's actual state might be changed by the main thread.

The impact of this change should be minimal, since the methods in question are primarily used internally by painters.

Upgrade considerationLuciadFusion

Camera constraints: replaced ALspCameraConstraint2D and ALspCameraConstraint3D by a generic ALspCameraConstraint class. Also the constrainXxxParameters method was replaced by a more general constrain method. Also removed ConstraintChangeListener interfaces and replaced them with ILcdChangeListener.

Upgrade considerationLuciadFusion

In TLspLookAtTrackingCameraConstraint2D the setMaxScale(double) method was removed. This functionality can be replaced using a separate constraint. For an example of how to do this, see the limitnavigation sample.

Upgrade considerationLuciadFusion

ALspTrackingPointProvider now doesn't pass around an ILspView in most of its methods. A view can be retrieved using ALspTrackingPointProvider.getView(). Also TrackingPointChangeListener was removed, and replaced by ILcdChangeListener.

Upgrade considerationLuciadFusion

ALspViewXYZWorldTransformations are now constructed for a specific view. As a consequence, the registerView(ILspView) and unregisterView(ILspView) methods were removed. TLspViewXYZWorldTransformation2D and TLspViewXYZWorldTransformation3D constructors now have an ILspView as argument.

Upgrade considerationLuciadFusion

The various calls to retrieve bounds and touch information from a layer or painter about objects on the screen has changed. They have been replaced by a single ILspInteractivePaintableLayer.query() method that accepts various query objects and returns the relevant information.

In particular, the following calls have been removed:

ILspInteractivePaintableLayer.queryOnViewBounds
ILspInteractivePaintableLayer.queryTouched
ILspInteractivePaintableLayer.isTouched
TLspLayer.applyOnInteract
ILspPainter.queryOnViewBounds
ILspPainter.queryTouched
ILspPainter.isTouched
ILspPainter.boundsSFCT
ILspLabelPainter.isLabelTouched
ILspLabelPainter.labelBoundsSFCT

Although you can still query painters directly, it is advised to query the layer instead. You can replace the removed calls above with these query() calls on ILspInteractivePaintableLayer:

query(new TLspPaintedObjectsBoundsQuery(REGULAR_BODY, viewBounds, 10))
query(new TLspPaintedObjectsTouchQuery(REGULAR_BODY, viewPoint, 10))
query(new TLspIsTouchedQuery(object, REGULAR_BODY, viewPoint, 10))
query(new TLspPaintedObjectsQuery(REGULAR_BODY, viewBounds))
query(new TLspPaintedObjectsBoundsQuery(REGULAR_BODY, viewBounds, 10)) (same as #1)
query(new TLspPaintedObjectsTouchQuery(REGULAR_BODY, viewPoint, 10)) (same as #2)
query(new TLspIsTouchedQuery(object, REGULAR_BODY, viewPoint, 10)) (same as #3)
query(new TLspBoundsQuery(object, REGULAR_BODY))
query(new TLspIsTouchedQuery(label, viewPoint, 10)) (similar to #3)
query(new TLspBoundsQuery(label)) (similar to #8)

The new query method also uses the ALspBoundsInfo and ALspTouchInfo classes as possible return types, with some minor modifications:

ALspWorldBoundsInfo#isGeometryDraped has been removed as there was no clear use case.
ALspWorldTouchInfo#isGeometryDraped has been replaced with getElevationMode. This allows us to return more information about the position of the touched geometry.

Upgrade considerationLuciadFusion

ALspActionController, TLspClickActionController and TLspKeyActionController constructors don't accept an ILcdFilter for AWT events anymore. Instead, use the setAWTFilter method of ALspController.

Upgrade considerationLuciadFusion

The label location hierarchy was simplified and made more flexible. This has an impact on the location classes and label painter hierarchy.

TLspFreeLabelLocation was removed, use TLspStampLabelLocation as a replacement, which is more powerful.

ILspFreeLocationLabelPainter interface was removed. The API of ILspStampLocationLabelPainter was changed to aid algorithms.

Upgrade considerationLuciadFusion

ILspLabelPlacer is now tied specifically to one view. This means that its placeLabels() method does not accept a view anymore, and that it only contains label locations for objects in one view.

Upgrade considerationLuciadFusion

The API of ALspLabelLocations was simplified. Instead of the various applyOn() methods there is one getLabelLocations() and one getLabelLocation() method.

Related, TLspLabelLocationVisibilityChangedEvent was merged into TLspLabelLocationChangedEvent. Instead of the processChangedLocations() and isLabelLocationChanged() methods, there now is only a simple getChanges() method.

Upgrade considerationLuciadFusion

The ILspPaintGroupsChangeListener interface has been changed to support better control over the event processing. This allows for example to make sure that updates to the body and label of objects are visible at the same time. All ILspPainter's must now also implement this interface.

To convert an implementation of the old interface you can perform all work previously done in the paintGroupsChanged method in the prepareChanges method and invoke the changesReady method on the callback immediately if it is not null.

To convert a painter that previously did not implement ILspPaintGroupsChangeListener you should at least invoke the changesReady method on the callback argument passed in the prepareChanges method if it is not null.

Upgrade considerationLuciadFusion

The method ILcdOGCFilterEvaluator#buildFilter, used to create a filter evaluator for a given OGC Filter, now returns an ILcdDynamicFilter instead of an ILcdFilter. This has been done for optimal interoperability when using these filter evaluators on GXY, GL and LSP layers.

Applications that use this method will not be affected, since ILcdDynamicFilter is an extension of ILcdFilter. The change only affects applications that define a custom implementation of ILcdOGCFilterEvaluator or an extension of its default implementation TLcdOGCFilterEvaluator. If this is the case, the new methods introduced by ILcdDynamicFilter, i.e. addChangeListener and addChangeListener), can be given an empty implementation, since dynamic changes to the filter are not supported.

Upgrade considerationLuciadFusion

TLspGXYLayerAdapter no longer allows to set an ILcdFilter on the inner GXY layer. Only ILcdDynamicFilter instances are allowed. Exceptions will be thrown at runtime when an incorrect filter is set on the inner layer.

To convert an ILcdFilter to an ILcdDynamicFilter you can make use of the TLcdChangeSupport class. This class makes it easy to implement ILcdChangeSource.

Upgrade considerationLuciadFusion

The signature of the methods getTile, putTile and deleteTile on ALfnCoverage has changed:

getTile and putTile now take an additional ByteBuffer parameter which can be used to retrieve/provide a signature for the tile. Existing applications or applications which are not interested in the signature may provide a null argument.
the level, row and column parameters have been replaced by a single TLfnTileCoordinates parameter. A TLfnTileCoordinates instance can easily be created via its getInstance() factory method, given the level, row and column arguments.

Bug fixLuciadFusion

LCD-1462

Input streams created by TLcdGeoTIFFModelDecoder and others are now properly closed. This solves issues with "too many open files" when working with a lot of different models.

Bug fixLuciadFusion

LCD-1455

ParseException in TLcdWKTReferenceParser when trying to decode a model reference with name "RGF-93".

Bug fixLuciadFusion

LCD-1451

Bug fixLuciadFusion

Bug fixLuciadFusion

LMAP-4676, LCD-455

TLcdEarthTileRepositoryPreprocessor: the preprocessor sometimes did not process tiles at the edge of an asset.

Bug fixLuciadFusion

LMAP-6002, LCD-458

TLcdEarthTileRepositoryPreprocessor: the preprocessor did not support assets whose bounds crosses the 180 degree meridian.

Bug fixLuciadFusion

TLcdEarthGLTerrainPainter now works correctly in stereoscopic 3D views.

Bug fixLuciadFusion

Bug fixLuciadFusion

The 'image inputstream factory' property of a TLcdGeoTIFFDecoder no longer needs to be set to an input stream factory that returns instances of the JAI SeekableStream class.

ImprovementLuciadFusion

LMAP-3242

Fixed gap/discontinuity on edges of elevation data assets.

Upgrade considerationLuciadFusion

The fusion engine ALfnEngine is now fully asynchronous. The signature and semantics of its methods have changed to reflect this new paradigm.

A quick way to change existing code is this:

Replace all old occurrences of ALfnEngine.fuse() withALfnEngine.fuse(new MyEmptyFusionHandler()).get(), where MyEmptyFusionHandler has empty implementations for all methods.
Add a catch ExecutionException and get its cause.
Replace old occurrences of ALfnEngine.getProgressNonBlocking() withALfnEngine.getProgress(), which has now become non-blocking.
Reevaluate old occurrences ofALfnEngine.getProgress(). The old behavior was blocking, but the new behavior is non-blocking. In case the blocking behavior is irrelevant for your use case, you can just leave it. In case the blocking behavior is relevant for your use case, for example because you want to wait until the progress has been initialized, replace it with ALfnEngine.getInitialProgress().get() .
The blocking call void fuse() has been replaced with a non-blocking counterpartFuture<?> fuse(ILfnFusionHandler). Instead of receiving the exceptions synchronously, they can now be received either by listening for them on a handler or by inspecting the ExecutionException when blocking for the result withFuture.get().
Replace all old occurrences of ALfnEngine.stop() withFuture.cancel(). This means you need to hold onto the future returned by an earlier call toALfnEngine.fuse(ILfnFusionHandler).

Upgrade considerationLuciadFusion

Luciad's abstract OpenGL binding, which is used by ILcdGLView to provide access to the OpenGL API, is now available directly in LuciadLightspeed. The binding is also used by the new Lightspeed view implementations (ILspView).

Only one concrete OpenGL binding is now shipped with LuciadLightspeed: JOGL version 2.x. Previous implementations, based on GL4Java and older versions of JOGL, are no longer included with the release. Applications that forced the use of a particular binding via the system property "com.luciad.view.opengl.binding.ALcdGLBinding" should now be forced to use the JOGL 2.x binding. Normally, this should not pose any problems, however.

Upgrade considerationLuciadFusion

The class ILfnVectorSessionHandler.FailureContext has been made abstract, its constructor has been removed. Users of the API should never instantiate this class. The methods getLevel(), getRow() and getColumn() have been replaced by getTileCoordinates(); the level, row and column information can still be accessed in the returned TLfnTileCoordinates object.

Upgrade considerationLuciadFusion

The functionality previously offered by the 'Earth' Additional Component is now available directly in LuciadLightspeed. This Additional Component provides support for preprocessing raster and elevation data into a 3D terrain database, as well as painters and other tools to work with such terrain databases.

The functionality is still contained inside a separate jar lcd_earth.jar, but this jar is shipped inside the LuciadLightspeed zip file. The documentation of the Earth component, such as the developer's guide and the release notes, has been integrated into the main documentation.

Upgrade considerationLuciadFusion

LF-182

The Fusion protocol now also supports text geometry. Objects with ILcdText geometry can now be fused to vector coverages, and displayed accordingly in Fusion clients. The vector tile data format used by the Fusion protocol has been updated to allow modelling of text geometry; old clients will no longer be able to read data which has been fused with a new Fusion engine supporting text geometry. New Fusion engines can still fuse to the old tile data format, by setting the appropriate codec version number on the coverage metadata.

Upgrade considerationLuciadFusion

TLfnScaleUtil has moved from package com.luciad.fusion.engine.vector tocom.luciad.fusion.util. Imports must be adjusted where necessary.

The default (compilation) scale denominator for a VectorAssetPart is now-1, for which a new constant TLfnScaleUtil.UNKNOWN_SCALE_DENOMINATOR has been defined. Where appropriate, hard-coded values of 0 should be replaced with references to the new constant.

Upgrade considerationLuciadFusion

The bundled Earth repository "sample_repository" has been renamed to "World".

Upgrade considerationLuciadFusion

The signature of the method ALfnTileStore.query() has been changed compared to LuciadFusion V11.0: it no longer declares to throw InterruptedException. Because it is an asynchronous method, InterruptedExceptions are propagated via the ILfnQueryHandler. This has been the behavior since V10.0, so there is no actual change in behavior.

Upgrade considerationLuciadFusion

ILfnVectorSessionHandler: the interface has been modified to support more general failures. More specifically the featureElementFailed method has been renamed to handleFailure and some of the attributes in the context have become optional.

Upgrade considerationLuciadFusion

ILcdLayerTreeNode now allows configuring the position at which layers are inserted by setting an ILcdInitialLayerIndexProvider on the node. See ILcdLayerTreeNode#addLayer.

Direct implementations of the ILcdLayerTreeNode interface will no longer compile, requiring the implementation of the ILcdInitialLayerIndexProvider getter and setter.
The new methods have been added to TLcdLayerTreeNodeSupport, which is the support class for creating such nodes. If you have created an ILcdLayerTreeNode implementation by delegating to this support class, you can implement these new methods by delegating them to the support class as well.

ImprovementLuciadFusion

LMAP-6016

TLcdGXYCircularArcPainter now has a paintEditingLabels method, making it easier to display extra information while editing circular arcs.

ImprovementLuciadFusion

LMAP-6007

TLcdGXYCirclePainter now supports snapping its outline.

Bug fixLuciadFusion

LMAP-6023

GetFeatureInfo requests where not correctly handled for layers that did not provide non-null painters for each available object in a model. It is however valid for layers to do that, if they want to hide an object in the map.

Bug fixLuciadFusion

TLcdEarthGLTerrainPainter: it was possible that some threads get blocked for a very long time when producing tiles on multiple threads. This situation could only occur when overriding the createAsynchronousTileSet method to create a tile set that uses multiple threads.

Bug fixLuciadFusion

TLcdEarthTileSetElevationProviderAdapter: the bounds was incorrect when the source reference did not equal the reference of the elevation provider.

Bug fixLuciadFusion

LMAP-6009

TLcdEarthHeightProviderFactory: the factory did not always consume some of its required keys. In addition it can now also consume the TLcdRasterModelHeightProviderFactory.KEY_INTERPOLATE_DATA key if it its value is true.

Bug fixLuciadFusion

LF-237

The bounding shape of an asset is now encoded in the same geo reference as the asset (used to default to EPSG:4326).

Bug fixLuciadFusion

LMAP-6003

Fixed an exception that could occur when using line placement with objects that do not have a label text.

Bug fixLuciadFusion

LMAP-5641

Bug fixLuciadFusion

LMAP-5974, LCD-94

Bug fixLuciadFusion

LMAP-5894

Possible ConcurrentModificationException when using TLcdGXYCompositeViewLabelPlacer in combination with asynchronous label placement.

Bug fixLuciadFusion

LMAP-5827

Fixed decoding problem for GroundOverlay elements that contained a Region. The Regions now correctly contain a LatLonAltBox.

Bug fixLuciadFusion

LMAP-5689

Improved overridden clone methods so that the behavior for both clone() and clone(Map) is consistent.

ImprovementLuciadFusion

ImprovementLuciadFusion

Performance improvement for TLcdObliqueMercator.inLonLatBounds() and TLcdSphericalObliqueMercator.inLonLatBounds().

ImprovementLuciadFusion

LMAP-4700

TLcdWFSGetFeatureRequest now has an additional setBoundingBox method to specify a bounding box with a coordinate system other than WGS84.

Bug fixLuciadFusion

LF-252

Resources which are added on the file system can now be deleted as well, after the server has picked them up dynamically.

Bug fixLuciadFusion

LMAP-5499

Some bounds transformations used many more point transformations than needed for some cases. This fix improves the performance in these cases.

Bug fixLuciadFusion

TLcdLonLatBounds and TLcdLonLatFloatBounds now handle some additional numerical rounding problems in their contains2D(double,double) methods.

Bug fixLuciadFusion

LMAP-5769

TLcdOWSHttpTransport will no longer attempt to send GET requests if the ILcdOWSRequest does not support KVP encoding. This avoids unpredictable behavior with WFS-T transaction requests.

Bug fixLuciadFusion

LMAP-5762

TLcdEarthGXYRasterPainter: fixed incorrect rendering when warping partially transparent raster data.

Bug fixLuciadFusion

LMAP-5640, LCD-219

In some cases, TLcdLonLatGridPainter could display erroneous meridian line pieces.

ImprovementLuciadFusion

LF-231

When a format is unavailable because of a missing dependency, an info message is logged rather than a warning. In order to make it unaffected by obfuscation, the message displays the format name rather than the class name of the missing dependency.

ImprovementLuciadFusion

ImprovementLuciadFusion

LF-207

While fusing vector data, complex polygons containing duplicate (sub)polygons now fail with a clear error message.

ImprovementLuciadFusion

LF-198

TLcdGXYIconPainter's boundsSFCT and isTouched methods did not respect the UseOrientation flag. The painter can now also handle ILcdOriented instances that return NaN for the orientation.

Bug fixLuciadFusion

LMAP-5647

Fixed a regression with WFS 1.0 GetFeature XML requests that caused the server to return an exception for valid requests.

Bug fixLuciadFusion

TLcdDataObject.clone() now creates an instance of the own class, rather than an instance of TLcdDataType.getClass().

Bug fixLuciadFusion

TLcdSwissGridReference now properly returns custom names set with setName.

Bug fixLuciadFusion

TLcdGXYEditController2: when a shape was moved, extraneous snap targets could be shown. This has been fixed.

Bug fixLuciadFusion

LMAP-5637

Querying on a specified amount of features without a filter is now more memory efficient. This also reduces the memory need on server initialization.

Bug fixLuciadFusion

POL geometries now invalidate their internal cache when the altitude values are adapted. This means, among other things, that the 3D representation of extruded POL geometries will be updated if the minimum or maximum height is changed.

Bug fixLuciadFusion

LMAP-5525

When transforming large (width > 180 degrees) bounds defined in a geodetic reference to bounds in a geodetic reference with a different datum, it was possible to get an incorrect result.

Bug fixLuciadFusion

LMAP-5436

Labels could disappear when the user zoomed in on a polyline that uses TLcdGXYOnPathLabelingAlgorithm to place its labels.

Bug fixLuciadFusion

LMAP-5519

In the tool tip sample, the tool tip was not cleared from the view when the tool tip controller was disabled, by choosing the pan controller, for example.

Bug fixLuciadFusion

The Fusion Client is extended with support for the new coverage type and the querying and visualization of fused GRIB data.

ImprovementLuciadFusion

LuciadFusion is extended with support for rasterizing vector data into raster coverages. The rasterization relies on a layer factory that should be available for the vector format.

The Fusion Engine provides built-in support for rasterizing the vector data formats Shapefile (SHP), Vector Product Format (VPF), MapInfo (MIF/MAP), GML (Simple Features profile) and ECDIS. Through the API, additional formats can be plugged in.

ImprovementLuciadFusion

LuciadFusion now adds support to fuse and and distribute raster data representing values other than image and elevation. For instance, meteorological raster data defining temperature or wind speed. To support this use case, a new 'multivalued' coverage type is introduced. Additionally, support for the GRIB weather data format (V1, V2, bulletins) is added, as a primary use case for the new coverage type.

The Fusion Engine is extended with support for the new coverage type and the GRIB data format.

ImprovementLuciadFusion

LuciadFusion now adds support to fuse and and distribute raster data representing values other than image and elevation. For instance, meteorological raster data defining temperature or wind speed. To support this use case, a new 'multivalued' coverage type is introduced. Additionally, support for the GRIB weather data format (V1, V2, bulletins) is added, as a primary use case for the new coverage type.

The Data Server is extended with support for the new coverage type and the distribution of fused GRIB data through the Luciad Tile Service (LTS) and OGC Web Map Service (WMS) protocols.

ImprovementLuciadFusion

LuciadFusion is extended with support for vector data, enabling users to use very large vector data sets in applications. By applying tiling and the use of multiple levels of details, LuciadFusion allows to fuse vector data sources into a vector coverage, ready for high performance data streaming, visualization and analysis.

To support the vector data use case, the Fusion Client introduces new API to query and visualize vector coverages.

ImprovementLuciadFusion

New API has been introduced giving users fine-grained control over the OGC Web Map Service provided by the Data Server. The class TLfnWMSRequestDispatcherFactory has been extended with a protected method createWMSCommandDispatcherFactory, allowing users to configure the WMS service. A default implementation TLfnWMSCommandDispatcherFactory is available in the API, which users can extend to customize the published capabilities, request handling and styling.

ImprovementLuciadFusion

LuciadFusion is extended with support for vector data, enabling users to use very large vector data sets in applications. By applying tiling and the use of multiple levels of details, LuciadFusion allows to fuse vector data sources into a vector coverage, ready for high performance data streaming, visualization and analysis.

To support the vector data use case, the Data Server allows users to distribute and use vector data coverages through the Luciad Tile Service (LTS) and OGC Web Map Service (WMS) protocols.

ImprovementLuciadFusion

LuciadFusion is extended with support for vector data, enabling users to use very large vector data sets in applications. By applying tiling and the use of multiple levels of details, LuciadFusion allows to fuse vector data sources into a vector coverage, ready for high performance data streaming, visualization and analysis.

To support the vector data use case, the Fusion Engine introduces new API to fuse vector data. The Fusion Engine factory class, TLfnEngineFactory, has been extended with the capability of creating a vector fusion session, next to a raster fusion session. This makes use of a new package com.luciad.fusion.vector, which contains a number of classes related to vector fusion handling and simplification.

LMAP-1806

TLcdGXYLabelPainter: reduced the number of calls to the #retrieveLabels method.

ImprovementLuciadFusion

A street labeling sample was added. This sample shows how a streets application can be built using a few techniques :

Level of detail painting
Level of detail labels
Dynamic model filtering
Dynamic label priorities

ImprovementLuciadFusion

LMAP-5362

TLcdLockUtil now uses a fair ordering policy when using Java 1.6 and higher. This can be configured by calling TLcdLockUtil#setFairPolicy. Due to Oracle bug #6305337, it is strongly recommended to disable fair ordering when using Java 1.5.

ImprovementLuciadFusion

ImprovementLuciadFusion

The new packages com.luciad.format.gmlcommon.transformation, com.luciad.format.gml2.transformation, com.luciad.format.gml31.transformation and com.luciad.format.gml32.transformation introduce a new API that supports the transformation of a data model from and to GML. This API makes it possible to easily encode and decode a model as (from) GML. The sample samples.transformation.gml shows how this API works in practice.

ImprovementLuciadFusion

The new com.luciad.datamodel.transformation package introduces an API to support data transformations between different data models. Data transformations can be made invertible to support bidirectional conversions from source to target and back.

ImprovementLuciadFusion

The package com.luciad.format.sqlite.spatialite provides decoders and encoders to read and write SQLite SpatiaLite databases.

ImprovementLuciadFusion

LMAP-4561

The performance of TLcdColorMap#retrieveColor has been improved when using many levels (for example 10000 levels and colors).

ImprovementLuciadFusion

TLcdUTM, ILcdCompositeProjection, ILcdZonalPoint and ILcd2DEditableZonalPoint were deprecated in favor of the new TLcdUTMGridSystem. This class makes it possible to easily create TLcdUTMGrid instances which can be used by the transformation framework. Similarly, a new TLcdUPSGridSystem class was added for UPS transformations.

ImprovementLuciadFusion

LMAP-5256

The following methods were added to TLcdSphereRhumblineUtil :

rhumblineDistance()
rhumblineAzimuth2D()
rhumblinePointSFCT()

ImprovementLuciadFusion

LMAP-4058

ImprovementLuciadFusion

LMAP-5183

TLcdGXYHaloLabelPainter now also implements ILcdGXYMultiLabelPainter.

ImprovementLuciadFusion

ALcdShapeList (and all classes extending from it) now implement ILcdCache.

ImprovementLuciadFusion

LMAP-3138

TLcdGeodeticPen now uses the line type property when drawing arcs, making it possible to draw rhumb arcs. This is now used in the ruler controllers.

ImprovementLuciadFusion

LMAP-5161

Improved the behavior of TLcdGeodeticPen#appendLineTo when the previous model position was not visible in the current world reference. This also improves the behavior of TLcdGXYPointListPainter for lines that are only partly visible in the world reference.

ImprovementLuciadFusion

ImprovementLuciadFusion

LMAP-5007

TLcdGXYLabelPainter, TLcdGXYPolylineLabelPainter and TLcdGXYPolygonLabelPainter now allow changing the margin around the labels. Also, TLcdGXYPolylineLabelPainter and TLcdGXYPolygonLabelPainter now allow changing the text alignment.

ImprovementLuciadFusion

TLcdGXYStampLabelPainter, TLcdGXYPolygonStampLabelPainter and TLcdGXYPolylineStampLabelPainter now have a protected method pinPointSFCT to retrieve and customize the point where the pin attaches to the label.

ImprovementLuciadFusion

LMAP-4398

TLcdGXYLabelPainter now draws pins for freely placed labels similarly to the pins of discrete label locations, attaching the pin to the middle of one of the label bounds' edges.

ImprovementLuciadFusion

LMAP-4386

TLcdSphereUtil#closestDistanceToGeodesic() was added. This method makes it possible to calculate the closest distance between a point and either the complete geodetic or a geodetic line segment. This method works very similar to TLcdSphereUtil#closestPointOnGeodesic(), but it is more efficient because it does not need to calculate the closest point.

ImprovementLuciadFusion

LMAP-4410

An IllegalArgumentException was thrown when computing the contour of a TLcdXYPolygon base shape containing 0 points. This has been fixed.

Bug fixLuciadFusion

LMAP-5482

Some layers (TLcdUTMGridLayer, TLcdMapGeorefGridLayer) fired a PropertyChangeEvent with an incorrect property name :

ScaleRange instead of scaleRange
Visible instead of visible
Labeled instead of labeled
Label instead of label

Bug fixLuciadFusion

TLcdGeoTIFFModelEncoder now correctly exports rasters containing buffered tiles containing ARGB pixels.

Bug fixLuciadFusion

LMAP-5496

TLcdDefaultModelXYZWorldTransformation swapped the model and world reference if they both were grid references.

Bug fixLuciadFusion

A bug in the rendering of halos,resulting in incorrect halos when printing maps with partly transparent images with halo, has been fixed.

Bug fixLuciadFusion

LMAP-5468

Bug fixLuciadFusion

The short unit names of TLcdAngleUnit.DEGREE and TLcdAngleUnit.GRADIAN now correspond to the symbols defined in the international standard ISO 31-1.

Bug fixLuciadFusion

LMAP-1387

TLcdGXYMagnifierController's keyboard shortcuts have been fixed.

Upgrade considerationLuciadFusion

AssetPart has been renamed to RasterAssetPart for a better symmetry with VectorAssetPart. Constants in TLfnQuery have been renamed accordingly. References to TLfnQuery#ASSET_location and TLfnQuery#ASSET_boundingBox can be replaced with TLfnQuery#RASTER_ASSET_location and TLfnQuery#RASTER_ASSET_boundingBox respectively. Queries using the properties "lts:AssetPart/lts:Location/@link:href" and "lts:AssetPart/lts:BoundingBox" should be updated to "lts:RasterAssetPart/lts:Location/@link:href" and "lts:RasterAssetPart/lts:BoundingBox" respectively, matching a raster asset part specifically.

Upgrade considerationLuciadFusion

The Luciad Tile Service (LTS) protocol version has been incremented to1.0.1. Both client and server remain fully backwards compatible, there should be no impact on the client applications.

Upgrade considerationLuciadFusion

The Luciad Tile Service (LTS) protocol supported by the LuciadFusion Data Server has been changed compared to LuciadFusion V10.0. The old protocol will no longer be supported, requiring applications that use LuciadMap Fusion Client V11.0 to update the LuciadFusion Data Server to V11.0 accordingly.

Upgrade considerationLuciadFusion

The methods TLfnCompositeFormat.canCreateGXYLayer() and TLfnCompositeFormat.canCreateHeightProvider() have been removed. Instead, use ALfnAssetMetadata.getSupportedCoverageTypes(), and check if the result contains ELfnDataType.IMAGE or ELfnDataType.ELEVATION.

Upgrade considerationLuciadFusion

The signature of the constructor in TLfnTileStoreModelDescriptor has been slightly changed: the URI parameter has been replaced by an ALfnTileStore parameter. A TLfnTileStoreModelDescriptor instance is normally constructed automatically in TLfnTileStoreModelDecoder. Implementations that manually instantiated this class should now supply the ALfnTileStore parameter, which can be retrieved through a TLfnLTSClient (in the case of LuciadFusion Data Server connection) or through a TLfnFileSystemTileStore (in the case of a local file system Tile Store).

Upgrade considerationLuciadFusion

The class TLfnWMSRequestDispatcherFactory previously available in com.luciad.fusion.server has been moved to a newly introduced package com.luciad.fusion.server.wms, which groups classes specific to the support of the OGC Web Map Service protocol. Implementations that relied on this class can simply use the new import location.

Upgrade considerationLuciadFusion

The interfaces and classes ILfnTransport, TLfnRequest and TLfnResponse in com.luciad.fusion.client.transport and the class TLfnHttpAccessPoint in com.luciad.fusion.common.TLfnHttpAccessPoint have been moved to com.luciad.io.transport and renamed to respectively ILcdTransport, TLcdTransportRequest, TLcdTransportResponse and TLcdTransportAccessPoint. Implementations that relied on these interfaces or classes can simply use the new name and import location.

Upgrade considerationLuciadFusion

The TLfnRasterAssetMetadata has been changed to support more complex assets. Concretely the pixel density property has been moved to the RasterAssetParts. This change allows modeling file formats that can contain data at multiple locations and multiple levels of detail (ex. CADRG TOC file and ECDIS catalog file) as a single asset. Modeling these with a single asset is desired because an asset should conceptually be a logical group of data. The method TLfnRasterAssetMetadata#getPixelDensity still exists, but now takes the maximum of the pixel densities of the underlying RasterAssetParts.

Upgrade considerationLuciadFusion

TLfnEngineFactory: the engine factory now uses builder classes instead of builder methods for creating engine sessions. This allows for introducing additional parameters without breaking existing code and is also more convenient for optional parameters in general.

Upgrade considerationLuciadFusion

TLcdLonLatGridPainter can now make use of any ILcdLonLatFormatter instead of a TLcdLonLatFormatter. Users of the getLonLatFormatter method may have to add an extra instanceof operation and cast to make their projects compile again. Code overriding the setLonLatFormatter method will also have to change the argument type.

Upgrade considerationLuciadFusion

A new icon set is now being used in all of LuciadMap, Lucy, and all Industry Specific and Additional Components. The icons can easily be reverted to the old icons by adding lib/legacy/legacy_icons.jar to the classpath, before luciadmap.jar. Because the icons use a more advanced format now (PNG), and because all icons have now been consolidated in the LuciadMap.jar file, the file paths have been changed. If you are using TLcdGUIIcon or TLcdShapeIcon, you will automatically use the new icons. If you use the old icon filenames in your own code, it will be necessary to change them to the new file names. To make this easier, the file lib/legacy/legacy_icons.jar contains a mapping (icon_mapping.csv) from the old icon names to the newly used icon names.

Upgrade considerationLuciadFusion

The constant TLfnClientFactory#TRANSPORT_TYPE_APACHE_HTTP_CLIENT_401 has been renamed to TRANSPORT_TYPE_DEFAULT, to avoid explicit versions of third-party libraries in the API. Implementations that used this constant can simply replace it with the new name.

Upgrade considerationLuciadFusion

The lcd_wxs_common.jar is no longer part of the release. The necessary classes have been included in the luciadmap.jar

Upgrade considerationLuciadFusion

The lcd_wxs_common.jar is no longer part of the release. The necessary classes have been included in the luciadmap.jar.

Upgrade considerationLuciadFusion

LMAP-3087

ILcdGXYContext now has a properties object that can be used to store context information across multiple invocations of a method with an ILcdGXYContext object. TLcdGXYNewController2 will keep its properties for as long as the same object is being edited.
If you are affected by this change, consider extending from TLcdGXYContext or ALcdGXYContextWrapper. Note that implementing ILcdGXYContext from scratch is strongly discouraged.

Upgrade considerationLuciadFusion

A new method was added to the ILcdDataModelDisplayNameProvider interface, allowing to query the display name for a value within a type's domain. This may for example be used to translate coded enumeration values into human-readable names. Existing implementations of this interface may implement the new method by returning aValue.toString(), to keep their current behavior.

Upgrade considerationLuciadFusion

LMAP-5409

An ILcdOWSRequest can now encode lists of values in a KVP request using a Java List. This allows the transport to correctly encode these lists using a "," as a separator between values.

ImprovementLuciadFusion

LMAP-3084

TLcdGXYLayer now allows setting an interact margin to better support model elements of which the visual representation is larger than their model bounds.

Bug fixLuciadFusion

ImprovementLuciadFusion

Bug fixLuciadFusion

LMAP-5293

TLcdSHPModelDecoder could throw NegativeArraySizeExceptions when decoding files that contain empty records. This has now been fixed.

Bug fixLuciadFusion

TLcdEarthGLTerrainPainter: changing the altitude exaggeration factor did not work correctly.

ImprovementLuciadFusion

LMAP-5276

ALcdWMSProxy now implements the ILcdCache interface so all caching can be controlled through that interface.

ImprovementLuciadFusion

LMAP-5274

TLcdGXYMagnifierController now allows setting a filter to control what layers are included in the magnified window.

ImprovementLuciadFusion

TLcdSHPModelDecoder has been made more robust in its handling of records of which the actual length (as written in the record headers in the file) does not match the length defined by the specification of the shape type in question. For instance, a PointZ shape consists of 4 doubles (X, Y, Z, M) according to the specification, but some SHP files do not include the M value. Previously, the SHP decoder would read past the end of the record in such cases, resulting in failures to read subsequent records.

ImprovementLuciadFusion

Bug fixLuciadFusion

LMAP-5273

TLcdMAPModelDecoder and TLcdMIFModelDecoder now properly escape the names of types and properties when creating a TLcdDataModel. Previously, file or property names with spaces (or other characters that are invalid according to TLcdDataType) would result in an exception when decoding the file.

Bug fixLuciadFusion

LMAP-5267

Fixed a bug in the Metadata encoder and decoder that resulted in incorrectly encoded and decoded code list values.

Bug fixLuciadFusion

LMAP-5269

Fixed a bug in TLcdXMLSchemaBasedEncoder and TLcdXMLSchemaBasedDecoder that could result (under certain circumstances) in attributes getting incorrect values in case of restriction types inheriting attributes from multiple types in its inheritance hierarchy.

Bug fixLuciadFusion

LMAP-5269

TLcdXMLSchemaBasedEncoder now always marshals attributes that are required and have a fixed value, even if they didn't receive a value in the domain object.

Bug fixLuciadFusion

LMAP-4827

GML line string, linear ring and line string segment now apply linear interpolation also in geodetic models (this used to be geodesic interpolation). This is in accordance with the GML specification.

Bug fixLuciadFusion

ImprovementLuciadFusion

Exporting a shape that implements both ILcdCompositeCurve and ILcdRing now results in a GML Polygon (iso a GML Curve).

Bug fixLuciadFusion

LMAP-5244

TLcdEllipsoid.geoc2llhSFCT() produced an incorrect result when transforming (0, 0, 0).

Bug fixLuciadFusion

LMAP-5248

TLcdUpsMgrsUtil could produce incorrect MGRS strings for one specific grid square on the southern hemisphere. Also converting strings from this grid square to a lon lat point could produce incorrect results.

Bug fixLuciadFusion

LMAP-5249

Bug fixLuciadFusion

LMAP-5166

Bug fixLuciadFusion

LMAP-5135

ILcdGXYPen's append*LineTo implementations did not append the first point of the line when applied to a path with a polygon break. This caused TLcdGXYRoundedPointListPainter to incorrectly render complex polygons.

Bug fixLuciadFusion

LMAP-5122

TLcdSphereRhumblineUtil.intersectionGeodesicRhumblineSFCT() did not always produce an intersection point when the geodesic line segment is completely located on a pole, reducing it to a point.

ImprovementLuciadFusion

LMAP-5119

TLcdGXYOnPathLabelingAlgorithm: improved label positioning on path corners, and path start and end points.

ImprovementLuciadFusion

LMAP-5117

TLcdGXYLocationListLabelingAlgorithm, TLcdGXYOnPathLabelingAlgorithm and TLcdGXYInPathLabelingAlgorithm now log a warning message when they are used in combination with a label painter that does not implement ILcdGXYLabelPainter2.

ImprovementLuciadFusion

LMAP-5118

TLcdGXYOnPathLabelingAlgorithm now has an ABOVE and BELOW AlignmentMode.

ImprovementLuciadFusion

The performance of computations with geoid vertical datums has been improved significantly.

ImprovementLuciadFusion

LMAP-5113

TLcdDMEDModelDecoder provides a new property includeDMEDLevel to specify whether the DMED thumbnail rasters should be included in the decoded multilevel rasters. The decoder now also removes blank DMED rasters if checkTilesImmediately is set.

ImprovementLuciadFusion

LMAP-5083

TLcdGXYPointListPainter.setAnchorPointLocation() can now be called with the 'INSIDE_POLYGON' constant. When using this option, the painter will try to find an anchor point location inside the polygon. The same option was added to TLcdGXYSurfacePainter. TLcdGXYSurfacePainter.setAnchorPointLocation() can now be called with 'INSIDE_SURFACE' constant.

ImprovementLuciadFusion

LMAP-5107

Upgrade considerationLuciadFusion

LMAP-5094

The getters for properties of type gco:Date_PropertyType were incorrectly defined to have return type String. This has been changed to java.xml.datatype.XMLGregorianCalendar. For the same reason, the type of the value parameter of the according setters was corrected to java.xml.datatype.XMLGregorianCalendar (also used to be String). The affected properties are TLcdISO19115Citation.editionDate, TLcdISO19115Date.date, TLcdISO19115MaintenanceInformation.dateOfNextUpdate and TLcdISO19115Metadata.dateStamp.

ImprovementLuciadFusion

TLcdEllipsoidUtil.geodesicArea() and TLcdEllipsoidUtil.orientation2D() were added.

Bug fixLuciadFusion

LMAP-5066

TLcdEllipsoidUtil#orientation2D() did not always produce correct results for polygons spanning a large latitude range in some rare cases.

Bug fixLuciadFusion

LMAP-5077

When using TLcdGXYLabelPainter, multi-line labels were painted on an incorrect location during editing when the label was placed at the EAST or WEST location.

Bug fixLuciadFusion

LMAP-5075

Fixed potential memory leak in document and image providers that would occur for partially loaded files that are removed from the view.

Bug fixLuciadFusion

ImprovementLuciadFusion

LMAP-4642

The ILcdGeoBuffer implementations now also support ILcdPoint, ILcdPolygon, and ILcdComplexPolygon as base shape. The geobuffer painter/editor has also been updated to support buffers based on ILcdPoint and ILcdPolygon shapes.

ImprovementLuciadFusion

LMAP-4958

Add a parameter with the name wfs.supportedVersions to your web.xml file to enable this feature. You can use comma separated lists of versions such as "1.0.0,1.1.0" as values, or you can use wild cards such as "1.*".

ImprovementLuciadFusion

The ALcdCompassNavigationControl now allows specifying separate tooltips for the upper arrow and the rotation ring. Also the TLcdGXYNavigationControlsFactory has a new factory method allowing you to specify the tooltips to be used by its subcomponents.

ImprovementLuciadFusion

LMAP-4821

TLcdOverlayLayout now clamps all components to be within the available space of the parent, instead of always using the preferred size of the children.

ImprovementLuciadFusion

LMAP-4808

TLcdEarthGLShapeTileSet:

The outline and fill coverages of the tile set no also support ILcdCurve, ILcdRing and ILcdSurface objects.
The tile set now also supports point objects through a new coverage.
The documentation on the supported object types was improved.

TLcdRasterModelDecoder now also supports decoding rasters containing TLcdRenderedImageTile instances (based on Java Advanced Imaging), as an alternative to the default TLcdBufferedTile instances (based on ILcdTileDecoder and ILcdBuffer).

ImprovementLuciadFusion

TLcdRasterModelDecoder and TLcdJAIModelDescriptor now support an isElevation flag. The optional flag is read from the input properties and set on the decoded model descriptor, to specify that the raster data can be interpreted as elevation data.

ImprovementLuciadFusion

LMAP-4740

TLcdAngleUnit now supports angular mils.

ImprovementLuciadFusion

LMAP-4443

A new interface for the creation of a layer-based ILcdHeightProvider has been added: ILcdLayerHeightProviderFactory. This interface is similar to the exiting model-based factory: ILcdModelHeightProviderFactory. The difference is that the new interface creates a height provider from a layer and view instead of a model. A layer-based height provider returns heights that are in sync with the layer and view, with the correct level-of-detail for example. Using it often it is likely that the necessary data is cached.

ImprovementLuciadFusion

The TLcdEarthImageTileDataCodec and TLcdEarthSeparateAlphaImageTileDataCodec now allow configuring the compression quality. Setting a lower compression quality results in smaller data sets at the cost of image quality.

ImprovementLuciadFusion

LMAP-2648

Support has been added to automatically create and assign the paint queues of asynchronously painted layers. ALcdGXYAsynchronousPaintQueueManager allows implementing a completely custom paint queue management strategy. In addition, TLcdGXYAsynchronousPaintQueueManager creates and assign paint queues based on layer painting requirements described in paint hints. Please refer to the developer's guide and asynchronous paint sample for more information on how to use the new paint queue managers.

ImprovementLuciadFusion

LMAP-4684

TLcdBufferedTile now has a property to specify whether its pixel values are signed or not, so the method retrieveValue can return them correctly as integers.

ImprovementLuciadFusion

LMAP-4443

Added a new layer-based height provider factory. Opposed to the existing model-based height provider factory (e.g. TLcdEarthHeightProviderFactory), the new TLcdEarthGXYLayerHeightProviderFactory and TLcdEarthGLLayerHeightProviderFactory always return heights that are in sync with the data being painted in a view. THey also provides better performance as all required tile data is already cached in memory. The earth.opengl.aboveterrain sample demonstrates this new functionality.

ImprovementLuciadFusion

ImprovementLuciadFusion

A composite ILcdGXYLabelPainter implementation was added : TLcdGXYCompositeLabelPainter. This class can be used combine multiple label painters into one. This class specifies two ways to remap the label and sub-label index.

Shift label index : Only the label index is shifted.
Shift sub-label index : All indices of labels and sub-labels from the first label painter stay exactly the same. For all other labels, the sub-label index is shifted.

ImprovementLuciadFusion

All LuciadMap implementations of ILcdGXYLabelPainter now provide support for parent labels. This means that when a label location specifies an other anchor point, its coordinates are specified relative to this anchor point, see TLcdLabelLocation#getAnchorPoint(). When this method returns false, the anchor point is created like it was before. In order to make sure that TLcdLabelLocation#getAnchorPoint() returns the correct anchor point, code that alters the label locations should set the parent bounds by using TLcdLabelLocation#setParentBounds().

ImprovementLuciadFusion

A sample was added to demonstrate the creation and usage of labeling algorithms and labeling algorithm wrappers : labels.createalgorithm. It demonstrates how to create a simple labeling algorithm, how to create a wrapper that rotates the labels, how to create a wrapper that tries more possible placements, and a wrapper that tries to adjust the font size to find a suitable label location.

ImprovementLuciadFusion

TLcdLabelLocation now has a few extra methods :

getAnchorPoint() : When this method returns true, the location of this label is defined relative to this anchor point. When this method returns false, the user of the label location should compute an anchor point.
getParentLabel() : When this method returns a non-null object, the label location depends on the returned label. This means that the location of this label is defined with respect to the parent label. When creating or editing a label, one should always make sure that this dependency is respected, and that the location is defined relative to the parent label (getAnchorPoint()). For this it is also necessary to set the bounds of the parent label (setParentBounds()).
getParentBoundsRectangle(), getParentBoundsRotation(), setParentBounds() : When a TLcdLabelLocation has a parent label, the parent bounds should be set before using it.
isBodyLabel() : When this method returns true, it means that this label is used as a representation of its domain object.

TLcdLabelLocations now has a new constructor which takes an ILcdLabelDependencyProvider as argument. When this constructor is used, a parent label is set on the TLcdLabelLocation when calling TLcdLabelLocations#getLabelLocationSFCT(). So the parent dependencies of a label can be specified using the label dependency provider.

This functionality is demonstrated in the labels.offset sample.

ImprovementLuciadFusion

TLcdUTMGrid and TLcdUPSGrid objects now provide a correct TLcdModelReferenceMetaData.

ImprovementLuciadFusion

The performance of the convolution halo algorithm has been improved for objects with large view bounds.

ImprovementLuciadFusion

LMAP-3214, LMAP-1813, LMAP-2241, LMAP-838, LMAP-2995, LMAP-2970, LMAP-3240, LMAP-3101, LMAP-3348

New API has been added for advanced label placement, based on an ILcdGXYLabelingAlgorithm. Algorithms can be combined and wrapped. TLcdGXYLabelPlacer and TLcdGXYAsynchronousLabelPlacer provide the necessary boiler plate code to place a labeling algorithm's labels synchronously and asynchronously, respectively. For more information, see the com.luciad.view.gxy.labeling package, the developer's guide, and the label samples.

ImprovementLuciadFusion

Extensive support was added throughout LuciadMap for ILcdDataObject. In particular, the following enhancements were made:

The models of all vector formats (SHP, GML, ISO metadata, database format, MAP, MIF, SVG, POL, Magnetic North, MTM) are now data object enabled. This means that the model elements are ILcdDataObject instances and the model's descriptor is aILcdDataModelDescriptor. Most of these formats also allow direct access to their data model through a public TLcd<format>DataTypes class, for example TLcdSHPDataTypes orTLcdSVGDataTypes. Encoders that can export models from other formats to their own format have been enhanced such that they also accept data object enabled models. Since the model descriptors of these formats now implement ILcdDataModelDescriptor, all elements in these models are required to implement ILcdDataObject. Custom domain objects wrapping any of these model elements will need to implement ILcdDataObject as well, if they are contained in a model with a model descriptor of any of these formats.
TLcdGXYDataObjectLabelPainter, TLcdGXYDataObjectPolylineLabelPainter and TLcdGXYDataObjectPolygonLabelPainter support painting of labels for data object enabled models. These label painters can be easily configured using a data object expression language (more information on this can be found in the javadoc ofALcdDataObjectExpressionLanguage)).
The class TLcdDataObjectShapeList is introduced as an implementation of both ILcdShapeList and ILcdDataObject.
A number of new annotations are added to describe additional properties of the data model. The TLcdPrimaryKeyAnnotation can be added to a type (typically in the context of a database) to indicate what its primary key property is. TheTLcdHasAShapeAnnotation, TLcdShapeAnnotation and TLcdShapeListAnnotation can be used to better describe the geometry that is contained within a type.
Various smaller changes are implemented to ensure that a model that is data object enabled is supported at least as much as a model that relies on ILcdFeatured.

Also, all sample code has been updated to use ILcdDataObject (in stead of ILcdFeatured). More information about ILcdDataObject can be found in the LuciadMap Developer's Guide.

ImprovementLuciadFusion

LMAP-3863

The GML model decoder now uses the information contained in TLcdModelReferenceMetaData to determine the dimension (2D vs 3D) and coordinate order (lat-lon vs lon-lat) of a model reference.

ImprovementLuciadFusion

LMAP-3756

TLcdGXYPointListPainter can now also edit ILcdEditableComplexPolygon instances.

ImprovementLuciadFusion

TLcdShapeList now implements the ILcdEditableShapeList interface.

ImprovementLuciadFusion

The new interface ILcdEditableComplexPolygon is added. TLcdComplexPolygon now implements this interface.

ImprovementLuciadFusion

LMAP-4168, LMAP-4057, LMAP-2223

Two new contour finders are added, TLcdPolylineContourFinder and TLcdComplexPolygonContourFinder. The original TLcdContourFinder could find closed contours. TLcdPolylineContourFinder can find both open and closed isolines. TLcdComplexPolygonContourFinder can find areas of height ranges on the terrain as complex polygons, supporting holes and translucent rendering. The new contour finders use ILcdContourBuilder to create shapes from the contour data, with implementations TLcdLonLatPolylineContourBuilder, TLcdXYPolylineContourBuilder, TLcdLonLatComplexPolygonContourBuilder and TLcdXYComplexPolygonContourBuilder. These implementations return the shape as TLcdValuedContour and TLcdIntervalContour instances.

ImprovementLuciadFusion

LMAP-4325

The default custom entity resolver on TLcdXMLSchemaBasedMapping is now allowed to return null for schema's that it can't resolve. The default implementation can now handle such cases. This makes it much easier to set a custom entity resolver because it only needs to handle the schema's that it knows about. TLcdXMLSchemaBasedMapping is now also ILcdInputStreamCapable for this reason. The TLcdXMLDataObjectSchemaHandler now also uses the default entity resolver of the decoder's mapping to resolve extension schema's.

ImprovementLuciadFusion

TLcdXMLSchemaBasedUnmarshallerProvider now allows registration of unmarshallers for a given schema element id and java class. Similar functionality is also added to TLcdXMLSchemaBasedMarshallerProvider.

ImprovementLuciadFusion

The name space URI that is passed as parameter to the TLcdXMLDataModelBuilder when creating a data model from a schema is no longer mandatory. This makes it easier to create a data model for a schema for which only the system id is known (and not the name space URI).

ImprovementLuciadFusion

LMAP-3863

The GML model decoder now uses the information contained in TLcdModelReferenceMetaData to determine the dimension (2D vs 3D) and coordinate order (lat-lon vs lon-lat) of a model reference.

ImprovementLuciadFusion

TLcdGXYMultiPointEditControllerModel#editingCandidates and TLcdGXYEditControllerModel2#editingCandidates now only return a single object when an object's handles has been touched. This makes sure that, when translating an object handle of a multiple selection, the untouched objects are not edited as well.

ImprovementLuciadFusion

Performance monitoring now also supports TLcdGXYViewJPanelLightWeight and TLcdMapJPanelLightWeight.

ImprovementLuciadFusion

Updated MapInfo Interchange File (MIF) in the com.luciad.format.mif package to support the new ILcdDataObject interface. A new class (TLcdMIFDataTypes) can be used to generate data models for this file format. The model elements remain backwards compatible with the ILcdFeatured interface, but it is recommended to use the ILcdDataObject interface for future projects.

ImprovementLuciadFusion

TLcdGeodeticReference, TLcdGeocentricReference, TLcdTopocentricReference and TLcdGridReference, (and implicitly TLcdDHDNGermanGridReference, TLcdLambert1972BelgiumGridReference and TLcdRD1918DutchGridReference) now implement ILcdExtendedModelReference.

ImprovementLuciadFusion

LMAP-4019

The interfaces ILcdInputStreamFactoryCapable and ILcdOutputStreamFactoryCapable have been added, introducing a general way to indicate the capability of respectively configuring an ILcdInputStreamFactory and ILcdOutputStreamFactory. These interfaces are now implemented by all existing classes in LuciadMap that provide this capability, including all implementations of ILcdModelDecoder/ILcdModelEncoder and ILcdGXYLayerDecoder/ILcdGXYLayerEncoder.

ImprovementLuciadFusion

LMAP-3864

The TLcdWKTReferenceParser now takes into account the AXIS tags, which can be used in determining the type and order of the coordinate systems' axes. This information is provided by a new interface called ILcdExtendedModelReference that extends ILcdModelReference and gives access to an object of type TLcdModelReferenceMetaData.

ImprovementLuciadFusion

The interfaces ILcdSphere and ILcdDome have been introduced to represent 3D spheres and half-spheres, respectively. The already existing classes TLcdLonLatHeightSphere and TLcdLonLatHeightDome now implement these interfaces. Furthermore, ILcd3DEditableSphere and ILcd3DEditableDome represent modifiable versions of these two shapes.

ImprovementLuciadFusion

LMAP-3220

The following shapes now implement the ILcdRing or ILcdCurve interfaces:

TLcdLonLatLine and TLcdXYLine
TLcdLonLatEllipse and TLcdXYEllipse
TLcdLonLatFloatPolyline and TLcdXYFloatPolyline
TLcdLonLatFloatPolygon and TLcdXYFloatPolygon

Bug fixLuciadFusion

LMAP-4781

TLcdTarModelListDecoder, TLcdZipModelListDecoder, and TLcdUSRPModelDecoder returned an ILcdModelTreeNode with a null model reference, which could lead to NullPointerExceptions. These decoders have been adjusted.

The default model of the TLcdGXYLayerTreeNode had a null model reference. This has been adjusted as well.

Bug fixLuciadFusion

LMAP-4736

When decoding a GML document that contains feature collections as children of the root feature, the display name of the model descriptor the child feature collections are now derived from the type name of the root feature collection. In older V10 releases, all these feature collections (the root and all its children) used the source name of the decoded document.

Bug fixLuciadFusion

LMAP-4768

The filled part of the FILLED_TRIANGLE and OUTLINED_AREA TLcdSymbols did not stay within the outline.

Bug fixLuciadFusion

LMAP-4754

Exporting a model to GML now properly uses the model reference formatter set on the encoder.

Bug fixLuciadFusion

LMAP-2132

The tool tip sample now uses ILcdGXYPainter.isTouched instead of ILcdShape.contains2D to find out which object needs a tool tip. This makes it also work for points.

Bug fixLuciadFusion

Exporting a model to GML now properly takes the model reference into account when deciding on dimension (2D vs 3D) and coordinate order (lat-lon vs lon-lat).

Bug fixLuciadFusion

LMAP-4169

TLcdContourFinder could not find some contours around certain configurations of values in the grid. This has been fixed.

Bug fixLuciadFusion

LMAP-4331

The GML model encoder can now export data object enabled models (that is models whose elements implement ILcdDataObject and whose model descriptor implements ILcdDataModelDescriptor).

Bug fixLuciadFusion

LMAP-4599

Correct the interpretation of angles (bearing) for arcs in a model reference where the first coordinate axis is north (in such a reference, coordinates are expressed as lat-lon).

Bug fixLuciadFusion

LMAP-4596

TLcdGXYLayer now better respects the layer, painter, and label painter paint modes. Among others, the following issues are fixed:

painters never got the ILcdGXYPainter.DEFAULT flag
label painters never got the ILcdGXYLabelPainter.DEFAULT flag
several inconsistencies regarding the ILcdGXYLayer.HANDLES flag

Bug fixLuciadFusion

LMAP-4103

TLcdXMLSchemaBasedEncoder and TLcdXMLSchemaBasedDecoder now only close OutputStream and Inputstream instances that they create themselves. They used to close also streams that were passed as input parameters.

Bug fixLuciadFusion

When using asynchronous painting and adding a new view (with an ILcdGXYEditableLabelsLayer), it was possible that the ALcdLabelLocations of the wrapped layer were not synchronized correctly initially.

Bug fixLuciadFusion

LMAP-4395

A minor bug was fixed in TLcdGXYLabelPainter's discrete placements. Among others, the halo thickness was not taken into account.

Bug fixLuciadFusion

The intersection2DLSSFCT methods of TLcdEllipsoid compute the intersection point of two geodetic lines accurately on the ellipsoid instead of using a spherical approximation.

Bug fixLuciadFusion

LMAP-4156

The following classes are now thread-safe for read-only access:

This also improves the thread-safety of the ILcdModel objects produced by the following decoders:

Upgrade considerationLuciadFusion

ELcdGML32NilReasonEnumeration and ELcdGML32TimeUnit have been renamed to use a TLcd prefix and are now also regular classes instead of enumerations. These new classes correspond better with the types that are defined in the GML schema, and the API that uses these types is now also clearer.

Existing users of these classes can simply use the new ones: TLcdGML32NilReasonEnumeration and TLcdGML32TimeUnit. A method is also available that allows retrieving a constant based on a String and allows iterating over all known values. The change also applies to the corresponding classes in GML 3.1.

In most cases, this change results in a compilation error. However, this is not the case when the NilReasonEnumeration type is used as part of another union and/or choice. An example of this are for instance the nilReason and envelopeOrNull properties on TLcdGML32BoundedShape. The type of these properties is Object.class because they are a union/choice between TLcdGML32NilReasonEnumeration and another class (URI/Envelope). As such, no compilation errors are generated when a String value would be assigned to these properties. However, exceptions may occur at run-time because the property should not contain a String object.

Upgrade considerationLuciadFusion

The classes TLcdSHPPointM, TLcdSHPPointZ, TLcdSHPPolygonZ and TLcdSHPPolylineZ no longer implement ILcdDataObject. The interface was removed as geometry information for the SHP format is no longer exposed through the ILcdDataObject API. In case applications require access to the values contained in these geometries, the API exposed by the 4 before mentioned classes should be used.

Upgrade considerationLuciadFusion

In XML, a number of providers (TLcdXMLSchemaBasedMarshallerProvider, TLcdXMLSchemaBasedUnmarshallerProvider, TLcdXMLTypeMarshallerProvider, TLcdXMLTypeUnmarshallerProvider, TLcdXMLTypeObjectFactoryProvider, TLcdXMLMarshallerProvider and TLcdXMLUnmarshallerProvider) have a type unsafe API. These providers have public methods that return an object with a type parameter that is only used in the return value. As a result, the Java compiler's type inference allows callers to specify the type. This is incorrect and can lead to type unsafe code (this is code that compiles correctly but yields ClassCastExceptions at run-time). This unsafe API has been changed to use a wild-card type parameter as return type. This change may result in compilation errors. For type-safe code, these compilation errors can be easily fixed by using appropriate type parameters.

Take the example ofILcdXMLUnmarshaller. This class has a method public <U, T extends U> ILcdXMLUnmarshaller<T> getUnmarshaller( QName aName, Class<U> aJavaClass ). This signature of this method is changed to public <U> ILcdXMLUnmarshaller<? extends U> getUnmarshaller( QName aName, Class<U> aJavaClass ). Because of this change, the following code no longer compiles, ILcdXMLUnmarshaller<X> m = provider.getUnmarshaller( ..., X.class ); and should be replaced by ILcdXMLUnmarshaller<? extends X> m = provider.getUnmarshaller( ..., X.class );

Upgrade considerationLuciadFusion

The magnetic north model decoders TLcdWMMModelDecoder and TLcdGRFModelDecoder now create TLcdValuedContour instances that contain ILcdPolyline shapes, instead of ILcdValuedPolygon instances that contain ILcdPolygon shapes. The old behavior can still be reproduced by calling the setCreateValuedPolygons() method (found in both model decoders) with parameter true. The default behavior will have this value set to false.

Upgrade considerationLuciadFusion

The behavior of the default model reference in TLcdDatabaseModelDecoder has been changed. Before, the default model reference was always used when set. Now, the default model reference will only be used when the method createModelReference of the ILcdDatabaseFactory associated with the TLcdDatabaseModelDecoder returns null. The old behavior can be accomplished easily by wrapping the TLcdDatabaseModelDecoder and manually replacing the reference of the decoded model with your model reference of choice (cast to ALcdModel and use setModelReference).

Upgrade considerationLuciadFusion

ILcdPOLGeometry now implements ILcdDataObject. Any custom implementations of this interface will have to implement this interface, using the POL data model found in TLcdPOLDataTypes.

Upgrade considerationLuciadFusion

ILcdDatabaseModelDescriptor now extends ILcdDataModelDescriptor. This change is a part of the upgrade of all vector formats supported by LuciadMap to support ILcdDataObject.

Upgrade considerationLuciadFusion

ILcdGXYEditableLabelsLayer now defines two new applyOnInteract() methods which take a paint mode as argument. One of these methods can be used to query domain objects, the other method can be used to query labels. These methods encapsulate the logic used to decide which objects and labels are painted by the layer. Hence, they take into account the labeled, scaleRange and labelScaleRange properties. For TLcdGXYLayer, the methods also use the selectionLabeled and filter properties for example. So these methods remove the need to do these checks externally, improving the encapsulation of the paint/applyOnInteract behavior of the layer.

To see how these methods can be used to adjust the label painting behavior, see the labels.offset sample. In this sample, a distinction is made between labels representing bodies, and text labels. 'Body labels' are painted together with the bodies, and 'text labels' are painted on top later.

This incompatible change impacts all user implementations of ILcdGXYEditableLabelsLayer. In that case a compile error is triggered. This compile error can be solved by implementing the two methods. For wrappers, the methods can be implemented by delegating to the wrapped ILcdGXYEditableLabelsLayer. For other implementations, ILcdGXYLayer#applyOnInteract() can be reused. However the implementation should take into account all settings that could modify the painting behavior.

Upgrade considerationLuciadFusion

The public constant UNKNOWN_TYPE was moved from TLcdCoreDataTypes to TLcdUnknownDataTypes. The type is now defined also in TLcdUnknownDataTypes.getDataModel() and no longer inTLcdCoreDataTypes.getDataModel().

Upgrade considerationLuciadFusion

TLcdComplexPolygon no longer extends TLcdShapeList or implements ILcdShapeList, since this extension was semantically not sound. Although it was occasionally convenient, it was often causing unexpected behavior, for instance when performing a series of instanceof tests. For backward compatibility, the typical TLcdShapeList methods are still available in TLcdComplexPolygon, but code that used to treat TLcdComplexPolygon as an ILcdShapeList will no longer function properly. Notably:

Assigning a TLcdComplexPolygon to an ILcdShapeList (local variable, argument, or field) will fail at compile-time.
Casting a TLcdComplexPolygon to an ILcdShapeList will fail at run-time (with a ClassCastException).
Performing an instanceof test of a TLcdComplexPolygon with ILcdShapeList will now return false at run-time.

A possible symptom may be that complex polygons are not appearing in a view, because shape list painters and editors no longer work. The simple solution is to use complex polygon painters (like TLcdGXYPointListPainter) instead, which paints polygons correctly (taking into account any holes, unlike the shape list painters).

Another symptom may be that complex polygons are not being encoded in a custom encoder, because they are no longer recognized. The encoder should then be adapted to iterate over the contained polygons instead of over the contained shapes.

Upgrade considerationLuciadFusion

Two new methods were added to the ILcdDataObject interface:

      boolean hasValue( TLcdDataProperty aProperty );

      boolean hasValue( String aPropertyName );

These methods return true if a value is set for the specified property, false otherwise. They allow to test whether a multivalued property has a value, without triggering the creation of the Collection instance holding the values of that property (in case the collection would be empty and getValue() would lazily the collection). Classes that implement ILcdDataObject and do not inherit their ILcdDataObject implementation from a LuciadMap API class will no longer compile and need to be updated. The following code snippet provides a default implementation for these methods that is sufficient for most applications:

      public boolean hasValue(TLcdDataProperty aProperty ) {
      Object value = getValue( aProperty );
      if ( value != null ) {
      TLcdDataProperty.CollectionType collectionType = aProperty.getCollectionType();
      if ( collectionType != null ) {
      switch ( collectionType ) {
      case LIST:
      case SET:
      return ( ( Collection ) value ).size() > 0;
      case MAP:
      return ( ( Map ) value ).size() > 0;
      }
      }
      // Single-valued.
      return true;
      }
      // No value set.
      return false;
      }

      public boolean hasValue( String aPropertyName ) {
      return hasValue(getDataType().getProperty( aPropertyName ));
      }

Only in cases where the data objects contain a large number of multivalued properties of which many are empty, a more optimized implementation that does not delegate to getValue() should be considered.

Upgrade considerationLuciadFusion

ILcdGXYEditableLabelsLayer now defines a new paint mode, PLACED_LABELS, which is used to signal that already placed labels should be painted. This mode is only passed to the layer when an ILcdGXYViewLabelPlacer is set on the view. When not using TLcdGXYLayer or an extension of it and when using an ILcdGXYViewLabelPlacer, the implementation of ILcdGXYLayer#paint() should be adjusted to support the ILcdGXYEditableLabelsLayer#PLACED_LABELS paint mode.

Upgrade considerationLuciadFusion

The return type of the following methods has been changed:

TLcdKML22DocumentProvider.updateDocument: changed from boolean to TLcdKML22Kml
TLcdKML22ImageProvider.updateImage: changed from boolean to Image

A true return value now corresponds to an object being returned, a false return value now corresponds to null being returned.

Upgrade considerationLuciadFusion

The ILcdSVGModelDescriptor interface now implements ILcdDataModelDescriptor. If you have a custom implementation of this interface, you can delegate the work of the new interface methods to the TLcdSVGModelDescriptor class as a workaround. Another option would be to extend from TLcdSVGModelDescriptor directly, which is the recommended alternative.

Upgrade considerationLuciadFusion

LMAP-4574

The ALcdBalloonManager no longer wraps the content generated by its ILcdBalloonContentProvider in a scrollpane. This allows for more flexibility while generating content. If you have any custom balloon content providers and would like to keep the scrollbar functionality, just wrap the content in a JScrollPane before returning it to theALcdBalloonManager:

      public JComponent getContent( ALcdBalloonDescriptor aBalloonDescriptor ) {
      //generate content as before
      JComponent contentPanel = generateContentPanel(aBalloonDescriptor);
      //wrap the result in a scrollpane
      JScrollPane scrollPane = new JScrollPane( contentPanel,
      JScrollPane.VERTICAL_SCROLLBAR_AS_NEEDED,
      JScrollPane.HORIZONTAL_SCROLLBAR_AS_NEEDED );
      return scrollPane;
      }

Upgrade considerationLuciadFusion

LMAP-4584

The property names of the property change events (PropertyChangeEvent#getPropertyName()) fired when calling various setters of TLcdGXYLabelPainter now comply to the specification. As such, the property names can easily be derived from the method names, avoiding any confusion in the future.

Search your code for the below strings in the context of PropertyChangeListener's, and rename them like this:

TLcdGXYLabelPainter#setForeground: "foreGroundColor" -> "foreground"
TLcdGXYLabelPainter#setBackground: "backGroundColor" -> "background"
TLcdGXYLabelPainter#setFrame: "framed" -> "frame"

Upgrade considerationLuciadFusion

TLcdGXYEditableLabelPainter has been deprecated in favor of ILcdGXYLabelEditor. The latter interface has a cleaner separation of concerns, and is independent of the ILcdGXYPainter used for the domain object.

Upgrade considerationLuciadFusion

ILcdMIFShape now extends the ILcdDataObject interface. The interface still extends the ILcdFeatured interface for backwards compatibility, but any custom implementations will have to implement the new interface as well.

Upgrade considerationLuciadFusion

LMAP-4378

TLcdDataTypeBuilder now constrains the names that can be used for properties. Names of properties can only consist of letters, digits and the '_' character. More elaborate property names can be stored in the display name of the property.

Upgrade considerationLuciadFusion

ALcdLabelLocations has been modified to provide better support for the tracking of changes in the painted status of TLcdLabelLocation objects. Two methods were adjusted to have an extra argument denoting a fire event mode : setPainted() and clearAllPainted(). Classes extending ALcdLabelLocations should be adjusted to implement these abstract methods. The implementations of these methods can be facilitated by using TLcdLabelLocationEventSupport.

LMAP-3984

Bug fixLuciadFusion

LMAP-4691

Fixed gap/discontinuity on edges of elevation data assets.

Bug fixLuciadFusion

Bug fixLuciadFusion

TLcdInterpolatedRaster no longer interpolates with the default (unknown) value, thus avoiding artifacts in elevation rasters and weather rasters.

Bug fixLuciadFusion

LMAP-4675

Solved a NPE when using TLcdXMLEncoder (the xml encoder that doesn't rely on XML schema) to encode objects that do not implement ILcdXMLElementInfo.

Bug fixLuciadFusion

LMAP-4672

TLcdMBeanPerformanceLogHandler now escapes its ObjectName values, allowing layers and models with special characters in their name.

Bug fixLuciadFusion

The TLcdEarthTileRepositoryPreprocessor sometimes failed to start if the Oracle XML parser is on the classpath.

Bug fixLuciadFusion

LMAP-4657

TLcdColorMapCustomizer: could fire a change event while the TLcdColorMap was still in an inconsistent state. This could break listeners that relied on that.

Bug fixLuciadFusion

LMAP-4655

In the geometry package topology calculations, if an arc was inside a polygon, the topology check "interacts" returned false. This has been fixed.

Bug fixLuciadFusion

LMAP-4627

ImprovementLuciadFusion

LMAP-4577

Bug fixLuciadFusion

The implementations of ILcdProjection have been corrected to take into account their central meridian when returning their boundary longitudes.

Bug fixLuciadFusion

LMAP-4429

The accuracy of bounds transformations in the standard implementations of ILcdModelXYWorldTransformation has been improved, notably for bounds crossing the edges of the model/world projections.

Bug fixLuciadFusion

LMAP-4504

TLcdGXYViewJPanelLightWeight sometimes did not update its labels correctly.

Bug fixLuciadFusion

Fixed bug that would add null to the end of an image url when it could not be parsed the first time.

Bug fixLuciadFusion

Fixed an issue that could cause a NullPointerException in case of XPath resolution.

Bug fixLuciadFusion

TLcdDatabaseModel now more efficiently commits elements that have been changed and subsequently deleted.

Bug fixLuciadFusion

LMAP-4585

TLcdGXYIconPainter#anchorPointSFCT() did not account for ILcdGXYContext#getDeltaX/Y() while editing.

Bug fixLuciadFusion

TLcdGXYPolygonLabelPainter and TLcdGXYPolylineLabelPainter did not fire property change events for all setters.

Bug fixLuciadFusion

LMAP-4572

TLcdGeoTIFFModelEncoder no longer throws a RasterFormatException when trying to encode a raster model with buffered tiles, with short pixel values that do not represent elevations.

Bug fixLuciadFusion

LMAP-4570

TLcdDTEDModelDecoder and TLcdDTEDDirectoryModelDecoder no longer incorrectly return a geoid datum when when the flags applyGeoidDatums and supportGeoidDatums are both set.

Bug fixLuciadFusion

Simplify customizing the default tile set wrappers such as the asynchronous tile set
Support soft caching of the tiles
Support updating tiles on demand

The 3D terrain painter was also updated to:

Automatically add the necessary tile set wrappers for combining image and elevation tiles into terrain tiles. As a result it is now advised to no longer add these yourself. You should for example use TLcdEarthRepositoryModelDecoder instead of the TLcdEarthTerrainRepositoryModelDecoder.
Support image and elevation tile sets with a different set of tiles (e.g. you no longer need both an image and an elevation tile together). If a tile is missing, a tile at a lower level will be used instead.

ImprovementLuciadFusion

A large number of tile set implementations have been updated to support asynchronous tile operation. For example the TLcdEarthTexturedTerrainTileSet produces the elevation and images tiles, needed for a terrain tile, asynchronously. As a result more requests can be executed concurrently. This is especially important if a tile request involves network communication, which can have a high latency. The threads in the TLcdEarthAsynchronousTileSet now also support producing the delegate tiles asynchronously.

ImprovementLuciadFusion

LuciadFusion is a new software platform for the management, fusion, and storage of large spatial data sets in networked environments. The Fusion Client is the native LuciadMap connection to LuciadFusion for the retrieval of fused data from a central Data Server.

Bug fixLuciadFusion

Fixed an issue that could cause a stack-overflow exception in case a datamodel with a cyclic dependency was configured on a xml encoder or decoder.

Bug fixLuciadFusion

LMAP-4536

Pin halo image cache was not validated often enough, sometimes causing label pins to be painted in the wrong location.

Bug fixLuciadFusion

LMAP-4494

TLcdGeoTIFFModelDecoder now again correctly decodes GeoTIFFs with transparency bitmasks.

Bug fixLuciadFusion

LMAP-4529

TLcdColorMapCustomizer: Enhancement LMAP-4452 could cause the gradient toggle to throw an ArrayIndexOutOfBoundsException.

Bug fixLuciadFusion

LMAP-4534

TLcdGXYIconPainter#anchorPointSFCT() could produce a NullPointerException. This is fixed now.

Bug fixLuciadFusion

Fix an issue that caused incorrect decision on whether or not to expand a choice that contains other choices. This might cause exceptions during encoding and decoding.

Bug fixLuciadFusion

LMAP-4493

TLcdGXYPointListPainter: when paint cache was used and changing the projection a NPE could occur while editing a polygon, and when adding a point to a polygon it could sometimes appear at the wrong edge. This has been fixed.

Bug fixLuciadFusion

LMAP-4183

The samples now also build the GUI on the Event Dispatch thread when started as an applet.

Upgrade considerationLuciadFusion

The ILcdEarthModelDecoderFactory interface was changed to allow configuration of the created model decoders. More specifically an extra java.util.Map parameter was added to its createModelDecoder method.

Previously it was not possible to configure the created model decoder. As a result you could not use a single factory, but instead had to create one for each specific use case. Another drawback was that the creator had to know what configuration was optimal for each use case. By adding an extra configuration parameter, the user of the model decoder can specify what configuration is optimal in his use case. This is similar as the ILcdModelHeightProviderFactory.

As a result of this change you may get some compile errors. In most cases you can fix these by using null or an empty map as the value for the new parameter.

ImprovementLuciadFusion

LMAP-4461

The WFS proxy sample now illustrates how an exception handler can be configured on the TLcdWFSProxyModel to deal with servers that behave erroneously.

ImprovementLuciadFusion

LMAP-4452

TLcdColorMapCustomizer now has API that allows to change its layout, or to modify or remove the actions in the tool bar.

ImprovementLuciadFusion

LMAP-4440

The TLcdXMLSchemaBasedEncoder now allows document-specific schema locations and prefixes to be used (see TLcdXMLSchemaBasedEncoder#getSchemaLocations( ILcdXMLDocumentContext ) and TLcdXMLSchemaBasedEncoder#getNamespacePrefixes( ILcdXMLDocumentContext ) ).

ImprovementLuciadFusion

The (unofficial) EPSG code 900913 used by Google Earth is now supported.

Bug fixLuciadFusion

LMAP-4517

Bug fixLuciadFusion

The getModelElementTypes implementations of the GML model descriptors have been improved to leave out feature collection types.

Bug fixLuciadFusion

LMAP-4453

Fixed bug in the iterator of the set returned by TLcdDataModel#getTypes().

Bug fixLuciadFusion

LMAP-4413

Improved thread-safety for concurrent XML encoding, decoding and XPath resolution.

Bug fixLuciadFusion

Files with recursive MultiGeometry elements are now correctly visualized.

ImprovementLuciadFusion

LMAP-4422

TLcdMapLonLatGridLayer now allows changing its pen.

ImprovementLuciadFusion

Bug fixLuciadFusion

LMAP-4439

Upgrade considerationLuciadFusion

The class TLcdXLinkConstants was removed from the API as there is hardly any use for it.

ImprovementLuciadFusion

The Server's support for GZip content encoding was broken for at least the Jetty servlet container (and possibly others).

Bug fixLuciadFusion

LMAP-4380

TLcdGeoTIFFModelDecoder again correctly interprets binary transparency masks, avoiding a ClassCastException from JAI (bug introduced in 10.0).

Bug fixLuciadFusion

LMAP-4392

TLcdInterpolatingRasterHeightProvider did not account for horizontal wrap-around of the raster.

Upgrade considerationLuciadFusion

LMAP-4352

TLcdGML31MultiLineString and TLcdGML31MultiPolygon no longer implement ILcd2DEditableShape or ILcd3DEditableShape. These interfaces are fairly generic and have no useful meaning on this level of the GML domain model.

ImprovementLuciadFusion

TLcdDTEDModelDecoder now also decodes DTED files that do not have the standard 1 degree by 1 degree size.

Bug fixLuciadFusion

LF-86

Decoding of models during Fusion would fail when the temporary folder was full, without a clear message. Fusion can now handle a situation where the temporary folder is full.

Bug fixLuciadFusion

LMAP-4383

Several GML32, GML31 and GML Model classes that implement ILcdShapelist (for instance the model classes that represent MultiGeometry, MultiCurve, Surface and MultiPoint) now properly update there bounds when one of their elements changes.

Bug fixLuciadFusion

Fixed exception that occurred for certain rotated ScreenOverlay elements in the TLcdKML22GXYPainterProvider.

Bug fixLuciadFusion

TLcdXMLDataModelBuilder now properly allows the creation of datamodels for cases where an XML schema is split over multiple documents (each with the same namespace) and no single schema document exists that imports all other documents.

Bug fixLuciadFusion

Improved the flexibility of the model decoder to allow KMZ files with deflated entries.

Bug fixLuciadFusion

LMAP-4344

The TLcdEarthGXYRasterPainter did not log a warning when the cache size is too small and did not automatically increase its cache size, if this feature is enabled.

Bug fixLuciadFusion

AbstractOverlay elements inside an updating NetworkLink will now force a new query to the server to support updating images.

Bug fixLuciadFusion

Fixed issue with draw orders for ScreenOverlay elements in 2D layers.

Bug fixLuciadFusion

LMAP-4286

Adding or removing one or more elements from a GML model now properly throws model change events.

Bug fixLuciadFusion

Fixed the exception that would arise when a NetworkLink didn't contain its mandatory Link element.

Bug fixLuciadFusion

LMAP-4309

The dateStamp property of TLcdISO19115MetaData can now be properly set (used to throw a NullPointException) using the property setter. This also fixes the same issue for the setters for a number of similar properties on metadata domain objects.

Upgrade considerationLuciadFusion

LMAP-4353

TLcdKML22MultiGeometry no longer implements ILcd3DEditableShape as this interface should never have been there.

ImprovementLuciadFusion

LMAP-4317

Bug fixLuciadFusion

ImprovementLuciadFusion

LMAP-4096

An icons sample was added in samples.gxy.icons.basic. This sample demonstrates the use of icons and the TLcdGXYIconPainter. It shows the use of ILcdAnchoredIcon, rotated icons and icons scaling.

ImprovementLuciadFusion

LMAP-4052

It is now possible to choose an interrupt mode when interrupt painting is enabled for asynchronous painting. The available modes are ALWAYS and NON_OVERLAPPING_PAINTS_ONLY. When using the second mode ongoing paint jobs are only stopped when a new paint job is scheduled and when its contents are completely outside the view. The modes can be set using TLcdGXYAsynchronousPaintQueue.setInterruptMode( InterruptMode aInterruptMode ).

ImprovementLuciadFusion

LMAP-3184

The TLcdEarthGXYRasterPainter has been improved significantly. Some of the improvement and fixes are:

The painting is significantly faster when the raster data must be transformed to a different reference
The tiles at the center of the view are now requested first
The cached tiles can be updated to make changes in the tile set visible
The view no longer becomes blurry when panning
The painter no longer runs out-of-memory due to cached tiles that are outside the view

The WFS server now correctly takes the 'srsName' attribute of incoming queries into account to convert bounding box operators to the coordinate system of the model that is being filtered.

ImprovementLuciadFusion

The WFS server now provides api to convert incoming XPath expressions to the native format that is provided to the WFS. A default implementation exists that relies on the ILcdDataObject interface to support this conversion automatically, assuming that the default WFS client model encoders are used to generate the GML schemas.

ImprovementLuciadFusion

LMAP-3146

Many painters now have a getter and setter for a 'minimum edit delta' property. This property represents the minimum pixel distance the input device (a mouse, for example) must move before editing the shape. A larger value ensures that the object easily snaps back in place, a small value allows fine editing.

ImprovementLuciadFusion

LMAP-3038

TLcdETOPOModelDecoder now also decodes the ETOPO1 product (an elevation raster covering the entire world at 1-minute resolution, distributed by the NOAA's National Geophysical Data Center).

ImprovementLuciadFusion

TLcdISO19103MeasureAnnotation is introduced. This allows data properties to be annotated with an ISO19103 unit of measure.

ImprovementLuciadFusion

The new com.luciad.datamodel package introduces support for the new unified approach taken in LuciadMap for the definition and interaction with domain objects. This approach provides a common API to access all domain objects, independent of their specific domain. In addition, this API makes information about the static structure of the domain objects available. This is the information that typically can be found in UML class diagrams.

This package is designed to be a replacement forILcdFeatured. It is the preferred way to model domain objects as from LuciadMap V10. For backwards compatibility reasons, ILcdFeatured will remain supported. But no new features will be added to it.

The main classes from this package are the following.

ILcdDataObject
TLcdDataModel, TLcdDataType and TLcdDataProperty
ILcdAnnotation

The class com.luciad.model.ILcdDataModelDescriptor was added for models of which the elements implementILcdDataObject. More information about this new API can be found in the developer's guide.

ImprovementLuciadFusion

LMAP-3872

The class TLcdGMLSrsRepository allows application developers to add additional model reference parsers and formatters to deal with custom srsNames that are not recognized by the default implementation.

ImprovementLuciadFusion

New classes are provided for rendering balloons on top of maps: ALcdBalloonManager, TLcdGXYBalloonManager, ILcdBalloonContentProvider. In addition, the 3D optional package provides an equivalent balloon manager implementation for integration with 3D views. Please refer to the developer's guide for more information on the use of balloons.

ImprovementLuciadFusion

LMAP-3925

SLD now also supports 2D painting of extruded shapes. Painting of such shapes is done by painting their base shapes.

ImprovementLuciadFusion

A new package com.luciad.format.metadata has been added. This package is split up in two parts:

The com.luciad.format.metadata.model package and subpackages provide a Java class representation of the ISO Metadata domain model.
The com.luciad.format.metadata.xml package provide an ISO19139 compliant XML decoder, encoder and XML libraries.

This new package now supports the final version of the ISO 19139 Metadata XML encoding standard. The domain model of the new package also supports the new unified domain access (all domain classes implement ILcdDataObject). An encoder for exporting metadata to ISO 19139 compliant XML is also provided. Both the decoder and encoder are now based on the XML Binding framework, allowing easy integration with other XML formats that use metadata.

ImprovementLuciadFusion

LMAP-4001

An ILcdEarthTileSet can now have an uneven amount of rows and columns at level 0. (ex. 1 tile at level 0).

ImprovementLuciadFusion

The TLcdEarthGXYViewTileSet now also supports production of tiles with a different number of horizontal and vertical pixels.

ImprovementLuciadFusion

Support has been added to allow dispatching custom input events to GUI components and, in particular, LuciadMap views and controllers. See TLcdAWTEventDispatcher, TLcdAWTEvent and ILcdAWTEventSource, and/or the developer's guide for more information.

In addition, a new TLcdTouchEvent type has been defined that enables multi-touch user input. Touch events are automatically generated for Windows 7 Touch compatible devices when using Sun's 1.5 and 1.6 JDK implementations, and you can also create and dispatch touch events yourself. The following new controllers work exclusively with touch-based user input:

TLcdGXYTouchEditSelectController
TLcdGXYTouchNewController
TLcdGXYTouchNavigateController
TLcdMapTouchRulerController

Also, several new touch samples have been added to illustrate the use of this new functionality. Please refer to the developer's guide and the samples section for more information on this new functionality.

ImprovementLuciadFusion

The WFS client API now supports creating and sending the following WFS-T requests:

Transaction
LockFeature
GetFeatureWithLock

ImprovementLuciadFusion

The support for locking and transactions has been improved, and is also WFS 1.1.0 and WFS 1.0.0 compliant. These features can be controlled through a parameter in the servlet configuration file. More information can be found in the developer guide.

The transactional improvements rely on the new ILcdDataObject interface that is introduced in LuciadMap V10. Users should ensure that the elements of the models provided to the WFS server implement this interface.

Additional api was added that allows you to customize how locking and transactions are handled. This makes it possible to support any kind of data backend.

ImprovementLuciadFusion

The WFS server implementation is now fully WFS 1.1.0 compliant. This results in some changes:

The result of a GetFeature request is now a wfs:FeatureCollection
The server now performs more strict input checking, invalid input will result in an exception report.
Improved filtering capabilities.

TLcdGXYContext has been extended to allow multiple input points.

ImprovementLuciadFusion

The TLcdEarthGLTerrainPainter now operates better with low JVM heap sizes.

ImprovementLuciadFusion

LMAP-3803, LMAP-3801

The TLcdWKTReferenceFormatter is now able to encode ILcdGridReference objects having a non-zero rotation. This results in a FITTED_CS reference system with an affine mapping that defines a pure rotation. The TLcdWKTReferenceParser has also been updated to correctly reconstruct the original rotated grid reference from the WKT.

ImprovementLuciadFusion

The TLcdEarthGLAboveGroundTileSet tileset also supports putting objects at ground level (e.g. replacing their own altitude by the ground altitude).

ImprovementLuciadFusion

The TLcdGXYArcPainter, TLcdGXYArcBandPainter and TLcdGXYGeoBufferPainter now offer more alternatives for computing the anchor point:

TLcdGXYArcPainter: middle of the arc bounds, middle of the cord, middle of the arc.
TLcdGXYArcBandPainter: middle of the bounds, middle of the arc band.
TLcdGXYGeoBufferPainter: middle of the bounds, middle of the buffer.

ImprovementLuciadFusion

LMAP-3779

The performance of TLcdGXYPointListPainter#isTouched is improved by caching original points in a smarter way.

ImprovementLuciadFusion

TLcd3DEditablePointList now implements ILcdCloneable.

ImprovementLuciadFusion

TLcdPerspectiveProjection now has a getter for the "right" vector of its projection plane (in addition to the "up" vector).

ImprovementLuciadFusion

LMAP-3665

TLcdGeoTIFFModelEncoder and TLcdGeoTIFFModelDecoder now encode and decode a grid reference with a perspective projection using GeoTIFF's 4x4 homogeneous matrix in a geocentric reference.

ImprovementLuciadFusion

LMAP-1213

TLcdGeoTIFFModelDecoder now no longer throws unexpected RuntimeExceptions.

ImprovementLuciadFusion

LMAP-3663

TLcdGeoTIFFModelencoder and TLcdGeoTIFFModelDecoder now support the tag for orthorectification based on Rational Polynomial Coefficients (RPC).

ImprovementLuciadFusion

The method ALcdGXYPen#getHotPointSize used to return the maximum of the width and height of an icon set as HotPointIcon. Now it returns the maximum divided by two. Since this property is used as a sensitivity to evaluate whether or not a the representation of an object is touched by a certain pixel, all handles used to have an sensitive region twice as big as the icon representing the handle. Now the region is exactly as big as the icon. For small icons/handles, this might make it more difficult to select or edit them. However it is now possible to increase the sensitivity for interaction directly by passing it in the ILcdGXYContext (see ILcdGXYContext#getSensitivity). This is for instance used by the select and edit controller models (See TLcdGXYEditControllerModel2#setSensitivity for example).

Bug fixLuciadFusion

LMAP-3988

Bug fixLuciadFusion

LMAP-3797

Upgrade considerationLuciadFusion

TLcdOGCFilter now supports feature ids next to GML object ids. These feature ids are deprecated in the OGC Filter 1.1.0 standard but are required to pass the compliancy tests. The old implementation automatically converted feature ids into gml object ids.

Upgrade considerationLuciadFusion

The clib_jiio_sse2.dll native library has been removed from the release, as it is known to cause stability problems.

Upgrade considerationLuciadFusion

A new library lcd_wxs_server.jar has been added, sharing common code between the WMS, WFS and WCS server implementations. This might require an update to existing application build and obfuscation scripts, to incorporate the new library.

Upgrade considerationLuciadFusion

A new library lcd_wxs_server.jar has been added, sharing common code between the WMS, WFS and WCS server implementations. This might require an update to existing application build and obfuscation scripts, to incorporate the new library.

Upgrade considerationLuciadFusion

A new library lcd_wxs_server.jar has been added, sharing common code between the WMS, WFS and WCS server implementations. This might require an update to existing application build and obfuscation scripts, to incorporate the new library.

Upgrade considerationLuciadFusion

The metadata API that was available in com.luciad.metadata has been replaced with an improved implementation in com.luciad.format.metadata. Related to this change, the old metadata interfaces that were implemented by some OWS domain model classes have been removed from these classes.

The change will have no or very little impact on existing implementations as the affected classes are mostly used internally. Methods that were available on these interfaces can still be found in the OWS domain model.

Upgrade considerationLuciadFusion

The ILcdWFSFeatureType interface has been extended with two methods to indicate that the type supports transactions and/or locking. Most existing implementations will want to return false for these methods, which is also the case for implementations that use the TLcdWFSFeatureType class.

The getModelObjectFactory() method of ILcdWFSFeatureType has been removed. The ILcdDataObject interface is now used to create new instances for specific feature types. This means that servers that wish to support transactions are required to use ILcdDataObject enabled models. Existing transactional WFS implementations should take this into consideration before upgrading.

Upgrade considerationLuciadFusion

The classes TLcdGXYEditController, TLcdGXYSelectController, TLcdGXYSelectControllerModel and TLcdGXYSelectControllerModelSW have been deprecated. Their functionality will remain present as is. It is advised to use their more flexible and powerful alternatives : TLcdGXYEditController2, TLcdGXYSelectController2 and TLcdGXYSelectControllerModel2.

Upgrade considerationLuciadFusion

The ILcdGXYContext interface has been extended with support for multiple input points (to allow for instance touch based editing with more than one finger) and a built-in sensitivity, a tolerance used by painters and editors when interacting with objects. Because this interface might be further extended in the future, it is strongly discouraged to implement it from scratch. Extend TLcdGXYContext for custom implementations or extend ALcdGXYContextWrapper to create a wrapper for a ILcdGXYContext. These classed will always be kept consistent with the interface.

Upgrade considerationLuciadFusion

The getPaintExceptionHandler() method was added to ILcdGXYView to improve the painting exception handling. All our ILcdGXYView implementations now also contain a setPaintExceptionHandler() method. When a painter throws an exception during painting, and it is caught somewhere, it is up to the exception handler returned by the view to handle this exception. This makes it possible for example to log the exception, and continue painting, but it also makes it possible to add fail-fast behavior, i.e. to pass the exception to the outer application.

The addition of the getPaintExceptionHandler() to ILcdGXYView affects all custom implementations of ILcdGXYView. It also affects classes that wrap an ILcdGXYView. In both cases a compile error is generated. In the former case the getPaintExceptionHandler() method needs to be implemented, see example code below, in the latter case the getPaintExceptionHandler() can delegate to the wrapped ILcdGXYView.

      public class CustomGXYView implements ILcdGXYView {

      // Create a default paint exception handler, getPaintExceptionHandler() should never return
      null.
      private ILcdPaintExceptionHandler fPaintExceptionHandler = new
      TLcdLoggingPaintExceptionHandler();

      public ILcdPaintExceptionHandler getPaintExceptionHandler() {
      return fPaintExceptionHandler;
      }

      public void setPaintExceptionHandler( ILcdPaintExceptionHandler aPaintExceptionHandler ) {
      fPaintExceptionHandler = aPaintExceptionHandler;
      }

      // ...
      }

Upgrade considerationLuciadFusion

The ILcdDataObject interface is now used throughout the WFS if it is available, but it is only required for servers that wish to support transactions. It is recommended to use data formats that support ILcdDataObject with the WFS. For backwards compatibility, ILcdFeature objects can also be supported, but this might disable some of the features that are available to ILcdDataObject based types.

The WFS requires that each ILcdWFSFeatureType corresponds with at most one TLcdDataType. This means that if the elements of an ILcdModel returned by an ILcdOGCModelProvider implement ILcdDataObject, the TLcdDataType of these data objects should be the same for all elements.

Upgrade considerationLuciadFusion

The com.luciad.format.xml.bind.schema.featured package has been dropped. The functionality of this package is now provided by the com.luciad.format.xml.bind.schema.dataobject package. More information about this can be found in the LuciadMap developer's guide.

Upgrade considerationLuciadFusion

TLcdXMLSchemaTypeIdentifier and TLcdXMLSchemaElementIdentifier have been extended to properly support the use of global xsd model groups. Elements defined in such groups were previously treated just like local elements. As a result, multiple different type (element) identifiers could point to the same schema type (element).

Upgrade considerationLuciadFusion

The xml binding framework now maps xsd:union types like choices: a single property that can contain values of different types. In previous versions, union types were considered strings and any interpretation was left to the application. Note that TLcdXMLSchemaTypeIdentifier has been extended for this such that anonymous types within a union type can be properly identified.

Upgrade considerationLuciadFusion

The com.luciad.metadata package has been removed and replaced by a new package com.luciad.format.metadata. The domain classes of the new package have been made consistent with the LuciadMap conventions for mapping XML Schema based data onto Java classes. As a consequence, although both domain models describe the same data, the new API for accessing the data in the model differs from the old API: most classes of the old API still exist in the new API, but have been moved to another package and can have slightly different accessor methods. Users that would have used the metadata API in their projects will need to review and upgrade their code.

Upgrade considerationLuciadFusion

Three methods in ALcdGXYNewControllerModel2 (#shouldCommit, #shouldEdit, and #shouldUndo) explicitly relied on MouseEvent information and have been moved to equivalent methods in TLcdGXYNewController2, to allow reusing the model for other input types. Because #shouldCommit uses the previously protected #getCreationStatus, the latter has been made public.

Upgrade considerationLuciadFusion

Three methods in TLcdGXYSelectControllerModel2 (#selectHowMode, #selectByWhatMode, and #applySelection) explicitly relied on MouseEvent information and have been deprecated to allow reusing the model for other input types. #applySelection has been replaced by an equivalent but MouseEvent-independent alternative. The other methods have been moved to equivalent methods in TLcdGXYSelectController2.

Upgrade considerationLuciadFusion

Two methods in TLcdGXYEditControllerModel (#editWho and #editWhatMode) explicitly relied on MouseEvent information and have been deprecated to allow reusing the model for other input types. Instead, these methods have been moved to equivalent methods in TLcdGXYEditController2.

Upgrade considerationLuciadFusion

An extra exception parameter was added to the tileNotAvailable method in the ILcdEarthTileSetCallback interface.

Previously this method only had a String parameter to indicate the reason why the tile is not available. As a result the call back could not easily distinguish the case where a tile was not available because it did not exist or because an error occurred. This also resulted in considerably more difficult debugging if an exception occurred during tile production as its stack trace was not readily available in the tile consumer.

As a result of this change any implementations of the ILcdEarthTileSetCallback interface will need to be updated. In most cases this only requires a small effort:

Delegate to another call back: this is typically the case if the call back is part of an ILcdEarthTileSet implementation that delegates to another tile set such as an implementation of ALcdEarthTileSetWrapper.
Handle the exception: this is typically the case if the call back is part of a tile consumer such as a painter for ILcdEarthTileSets.

Upgrade considerationLuciadFusion

TLcdXMLTypeMarshallerProvider, TLcdXMLTypeUnmarshallerProvider and TLcdXMLTypeObjectFactoryProvider now expose all registered type identifiers for a certain class as a java.util.Set while before it was a java.util.List. In a similar vein, all registered classes for a certain type identifier are now also exposed as a Set while before it was a List. This change was made to improve performance.

Upgrade considerationLuciadFusion

LMAP-3779

The method TLcdGXYPointListPainter#getTouchedSegment(ILcdGXYPen, int, int, boolean, ILcdModelXYWorldTransformation, ILcdGXYViewXYWorldTransformation) was deprecated in favor of TLcdGXYPointListPainter#getTouchedSegment( Graphics, int, ILcdGXYContext ). If you override the old getTouchedSegment method and want the new getTouchedSegment to use its behavior, then override the new getTouchedSegment as well and call the old method as follows:

      int x_origin = aGXYContext.getX() - aGXYContext.getDeltaX();
      int y_origin = aGXYContext.getY() - aGXYContext.getDeltaY();
      return getTouchedSegment( aGXYContext.getGXYPen(), x_origin, y_origin, false,
      aGXYContext.getModelXYWorldTransformation(), aGXYContext.getGXYViewXYWorldTransformation() );

Upgrade considerationLuciadFusion

LMAP-3740, LMAP-3109

The ALcd2DEditableFloatPolypoint and ALcd3DEditableFloatPolypoint no longer use a shared pool of points and are now thread-safe for read-only access. To achieve this goal, the classes require the user to implement two abstract methods called createPoint() and createBounds(), which must create points/bounds of the appropriate type (geodetic or Cartesian).

The change affects all classes extending ALcd2D/3DEditableFloatPolypoint: TLcdLonLatFloatPolypoint, TLcdLonLatFloatPolyline, TLcdLonLatFloatPolygon, TLcdXYFloatPolypoint, TLcdXYFloatPolyline, TLcdXYFloatPolygon, TLcdXYZFloatPolypoint, TLcdXYZFloatPolyline, TLcdXYZFloatPolygon.

Upgrade considerationLuciadFusion

The TLcdGML32Constants, TLcdGML31Constants and TLcdGML2Constants that defined public constants derived from the GML XML schema's have been removed from the API as they are no longer needed. The domain model has no longer a direct dependency on XML.

Upgrade considerationLuciadFusion

The signature of the constructor of the existing model classes that were already available in V9 (TLcdGMLxxAbstractFeature, TLcdGMLxxShapeFactory and TLcdGMLxxModelDescriptor) has changed to incorporate the implementation of ILcdDataObject.

Upgrade considerationLuciadFusion

Bug fixLuciadFusion

Inserting a 3D point in an existing direct position list no longer corrupts the position list. This scenario can occur for instance during editing of airspaces in AIXM5.

Bug fixLuciadFusion

LMAP-4074

TLcdRenderedImage#dispose() now always properly releases the source file. GeoTIFF files would otherwise remain locked under Windows, until garbage collection.

Bug fixLuciadFusion

LMAP-4050

Solved a possible memory leak when using TLcdGXYPolygonStampLabelPainter.

ImprovementLuciadFusion

LMAP-4003

The string "Powered by LuciadMap" has been replaced by "Powered by Luciad" throughout LuciadMap.

ImprovementLuciadFusion

LMAP-3904

A few enhancements were made to the TLcdAdvancedMapRulerController :

TLcdAdvancedMapRulerController now allows multiple measures. This can be enabled using setAllowMultipleMeasurements(). It is possible to start a new measurement starting at a point of an old measurement by setting the edit controller to null, see setGXYEditController().
It is now possible to add the measurement layer to the view in order to keep painting measurements after terminating interaction. This can be enabled using setAddGXYLayerToGXYView().
To give control over the removal of measurements, the measurement layer is exposed using the getGXYLayer() method.
A factory method to create a new TLcdGXYLayer is exposed. This method can be overridden to provide the TLcdAdvancedMapRulerController with a custom TLcdGXYLayer.

LuciadMap now provides USB iButton support for 64-bit Mac OS X.

ImprovementLuciadFusion

LMAP-3663

TLcdGeoTIFFModelencoder and TLcdGeoTIFFModelDecoder now support the NODATA tag for specifying a transparent index in a color map.

Bug fixLuciadFusion

LMAP-3824

The getBounds() method of TLcdLonLatHeightSphere and TLcdLonLatHeightDome were returning 2D bounds instead of 3D bounds. Also, the contains3D methods did not take the z axis into account.

Bug fixLuciadFusion

Properly decode GML documents with coordinates expressed in a mix of reference systems with both lon-lat and inverse lon-lat coordinate orders.

Bug fixLuciadFusion

LMAP-2670

A bug in the rendering of rotated labels with halo's, causing the labels to be partly invisible, has been fixed.

Bug fixLuciadFusion

LMAP-3891

Bug fixLuciadFusion

LMAP-3716

Bug fixLuciadFusion

LMAP-3916

Bug fixLuciadFusion

LMAP-3881

TLcdBILTileDecoder no longer ignores the number of band row bytes when reading tiles without sub-tiling.

Bug fixLuciadFusion

LMAP-3874

TLcdGXYMultiFontLabelPainter could print out stack traces when the object to label was not visible.

Bug fixLuciadFusion

The bounds of TLcdXYArc, TLcdLonLatArc, TLcdXYArcBand no longer include the center point of these shapes (previous change has been reverted).

Bug fixLuciadFusion

LMAP-3860

In the geometry package intersection calculations, in some rare cases it did not find all intersection points between two arcs.

Bug fixLuciadFusion

LMAP-3851

The LuciadMap hardware key now also works on Windows if a different user has installed the .msi 1-Wire drivers.

Bug fixLuciadFusion

LMAP-3828

ImprovementLuciadFusion

TLcdEarthAsynchronousTileSet did not set the priority of the threads it created, resulting in potentially poor performance on single-core machines. Threads are now initialized with minimum priority to ensure that they do not interfere with the event dispatch thread.

Bug fixLuciadFusion

XML schema type identifiers for locally defined attribute types are now correctly represented (i.e. with the attribute name filled in). They used to be presented similar to locally defined element types, (i.e. with the attribute name as an element name).

Bug fixLuciadFusion

LMAP-3834

Bug fixLuciadFusion

LMAP-3798

TLcdBILTileDecoder (used by TLcdBILModelDecoder and TLcdETOPOModelDecoder) now avoids skipping past the end of its input stream, to avoid infinite loops for some input stream implementations.

ImprovementLuciadFusion

Added support for capabilities files which have the MaxScaleDenominator element before the MinScaleDenominator. Although this is not valid according to the WMS specification, it sometimes occurs in practice.

ImprovementLuciadFusion

The bounds of TLcdXYArc, TLcdLonLatArc, TLcdXYArcBand and TLcdLonLatArcBand have been extended to include the center point of these shapes.

Bug fixLuciadFusion

LMAP-3786

Bug fixLuciadFusion

The elevations retrieved from a (multilevel) raster could be incorrect if its reference is WGS84 and its bounds cross the 180 degrees meridian.

Bug fixLuciadFusion

TLcdOWSHttpTransport#sendData did not close the OutputStream of the connection in case of POST requests.

ImprovementLuciadFusion

LMAP-3657

To allow additional configuration on the layer and painter level of a WMS proxy model, two new classes have been introduced: TLcdWMSProxyGXYLayer and TLcdWMSProxyGXYPainter. The existing layer factory, TLcdWMSProxyGXYLayerFactory, now returns layers of type TLcdWMSProxyGXYLayer, configured with a TLcdWMSProxyGXYPainter instance as painter provider.

ImprovementLuciadFusion

LMAP-3755

The TLcdWFSModelDecoderDecorator now supports a boolean flag to turn GML application schema caching on. This is typically used when many small documents need to be decoded from the same WFS server.

ImprovementLuciadFusion

LMAP-3755

A new flag 'useApplicationSchemaCache' has been added to the TLcdGMLModelDecoder. Turning this flag on will ensure that the decoder cache all application schemas it encounters. This reduces memory usage in case many files have to be decoded for the same application scheme.

ImprovementLuciadFusion

TLcdRPCProjection now has getters and setters for its parameters.

ImprovementLuciadFusion

LMAP-3738

TLcdDatabaseModelEncoder now supports automatic periodic commits when exporting a model to a database. This may be useful to avoid overflow of transaction logs.

ImprovementLuciadFusion

Updated the raster sample to use the repository model decoder introduced in 9.1.

ImprovementLuciadFusion

Bug fixLuciadFusion

Fixed race condition in TLcdEarthTileRepository.addTileDataCodec.

Bug fixLuciadFusion

LMAP-3687

TLcdRectifiedProjectiveProjection has been corrected, fixing a mathematical error that was introduced in LuciadMap 9.1.

Bug fixLuciadFusion

LMAP-3732

TLcdGXYFeaturedLabelPainter: Fixed an issue which could cause the feature indices to be reset when using the clone method.

Bug fixLuciadFusion

LMAP-3694

Fixed TLcdXMLDecoder such that it also works with other XML parsers then xerces. This issue manifested it self for instance when starting lucy by showing a dialog box asking for the xsd for XMLSchema when running with java 1.4 (which does not include xerces).

Bug fixLuciadFusion

Bug fixLuciadFusion

Fixed rare bug in TLcdEarthGLTrnTileSet which could cause an infinite wait.

Bug fixLuciadFusion

LMAP-3735

TLcdGXYMultiFontLabelPainter could print out stack traces when the object to label was not visible.

ImprovementLuciadFusion

LMAP-3578

The asset model is now saved with the repository. This allows determining the contents of a repository without testing all its tiles.

ImprovementLuciadFusion

The OGC filter encoder (both the old and the new implementation) now correctly handle filters containing binary operators or binary logic operators with only a single operand. In such cases, only the operand of the binary (logic) operator is encoded resulting in a correct xsd-compliant document.

ImprovementLuciadFusion

LMAP-3612

TLcdPolyconic has been added to the default list of projections of TLcdProjectionCustomEditor.

ImprovementLuciadFusion

TLcdDIMAPModelDecoder now supports setting a custom raster referencer.

ImprovementLuciadFusion

The performance of TLcdGeoTIFFModelEncoder has been improved.

ImprovementLuciadFusion

The elevation data can now be stored instead of the geometry when preprocessing a terrain. This results in a significantly smaller repository at the cost of a small performance penalty when visualizing it in a 3D view. The new classes in the API related to this are: TLcdEarthElevationDataTileDataCodec and TLcdEarthElevationDataCombiner. The TLcdEarthTexturedTerrainTileSet, TLcdEarthTerrainRepositoryModelDecoder and preprocessor sample were also updated to support this improvement.

ImprovementLuciadFusion

LMAP-3568

The warping raster painters can now also avoid opaque borders if the raster has a color map of which the transparent index is not the default raster value.

ImprovementLuciadFusion

LMAP-3477

The TLcdEarthGLTrnTileSet now also contains an image (e.g. texture) and elevation coverage. This allows visualizing a .trn terrain in a 2D view by using an earth GXY painter.

ImprovementLuciadFusion

Updated the ogc.filter.xml sample to use the TLcdOGCFilterEncoder and TLcdOGCFilterDecoder in stead of the old deprecated encoder and decoder.

ImprovementLuciadFusion

LMAP-3491

The TLcdEarthTerrainElevationProvider now also supports Earth models.

ImprovementLuciadFusion

LuciadMap now supports the Rapid Positioning Capability Extension (RPC00B) of the NITF format. The RPC parameters can be used to construct a model reference by using the TLcdRPCModelReferenceDecoder class. The projection used by this reference is called TLcdRPCProjection.

ImprovementLuciadFusion

The EPSG code 3395 is now supported by default.

ImprovementLuciadFusion

The TLcdEarthTerrainRepositoryModelDecoder can now also decode models from a sourcename that is relative to the classpath.

ImprovementLuciadFusion

LMAP-3304

To ease the deployment of the WCS server sample, the release is now delivered with the Jetty web server, a Java-based HTTP server and servlet container. A startup script ogc.server.start in the directory samples starts a Jetty web server on port 8080, predeployed with the WCS server sample available in the directory LuciadMapWCS_X.Y.Z/distrib/.

ImprovementLuciadFusion

LMAP-3304

To ease the deployment of the WFS server sample, the release is now delivered with the Jetty web server, a Java-based HTTP server and servlet container. A startup script ogc.server.start in the directory samples starts a Jetty web server on port 8080, predeployed with the WFS server sample available in the directory LuciadMapWFS_X.Y.Z/distrib/.

ImprovementLuciadFusion

LMAP-3304

To ease the deployment of the WMS server sample, the release is now delivered with the Jetty web server, a Java-based HTTP server and servlet container. A startup script ogc.server.start in the directory samples starts a Jetty web server on port 8080, predeployed with the WMS server sample available in the directory LuciadMapWMS_X.Y.Z/distrib/.

ImprovementLuciadFusion

TLcdInputStreamFactory now avoids unnecessarily opening file descriptors, by only checking the content type for HTTP URLs.

ImprovementLuciadFusion

TLcdLonLatCoord: improved performance of the normalizeLon method.

ImprovementLuciadFusion

LMAP-3322

An option can now be specified in the WMS servlet configuration file (web.xml) to invert the bounding box coordinates in case the request version is 1.3.0 and the reference is EPSG:4326. If these conditions hold, and the option is set, the x coordinates will be interpreted as latitudes and the y coordinates as longitudes.

For WMS version 1.1.1, the order is defined as x=lon, y=lat. In version 1.3.0 it was decided that the order should be consistent with the order defined in the EPSG:4326 reference which is lat/lon. Consequently, some WMS 1.3.0 servers have changed their interpretation of EPSG:4326 coordinates, while others sticked to the old (WMS 1.1.1) interpretation.

Use the configuration option if you want to comply with the WMS 1.3.0 specification. Do note that the EPSG:4326 reference is officially deprecated, so the problem can be circumvented by not supporting this reference.

Add the following to your WMS web.xml file to enable inversion:

      <init-param>
        <param-name>EPSG.4326.latlon</param-name>
        <param-value>true</param-value>
      </init-param>

ImprovementLuciadFusion

LMAP-3322

ALcdWMSProxy: added a getter boolean isInvertXYForEPSG4326() and setter setInvertXYForEPSG4326( boolean aInvertXYForEPSG4326 ). This has to be used by implementations of this class to determine whether the bounding box coordinates for WMS version 1.3.0 and reference EPSG:4326 should be specified as x=lon and y=lat which is the default, or x=lat and y=lon which is inverted.

For WMS version 1.1.1, the order is defined as x=lon, y=lat. In version 1.3.0 it was decided that the order should be consistent with the order defined in the EPSG:4326 reference which is lat/lon. Consequently, some WMS 1.3.0 servers have changed their interpretation of EPSG:4326 coordinates, while others sticked to the old (WMS 1.1.1) interpretation.

ImprovementLuciadFusion

ImprovementLuciadFusion

The DMED and DTED model decoders now support an additional sampling strategy that performs bilinear interpolation across decoded elevation rasters. The strategy is implemented with the help of new classes TLcdInterpolatedRaster and TLcdTruncatedTile, which provide basic support.

ImprovementLuciadFusion

LMAP-3309

A new class TLcdBNGUtil supports formatting and parsing coordinates in the British National Grid notation (for example "HU 396 753")

ImprovementLuciadFusion

LMAP-1783

Throughout LuciadMap, threads no longer inherit the priority of the creating thread but specify it explicitly.

ImprovementLuciadFusion

LMAP-3335

TLcdLayer now filters the selection when a filter has been set to the layer. In addition, the selection is kept up to date if the filter in question implements ILcdChangeSource. This was already implemented for TLcdGXYLayers (see LMAP-2455) and has now been moved from TLcdGXYLayer to the super class TLcdLayer.

ImprovementLuciadFusion

LMAP-3324

The database package now provides shape list implementations of which the identities are determined by their primary features. In concrete terms this means that "equals" and "hashCode" are now implemented based on the primary feature. The caching mechanism has been updated to ensure that it always provides the same object instance for any given database object, in order to minimize any possible confusion about its identity.

ImprovementLuciadFusion

The database package now offers improved caching for queries based on a query window (with TLcdDatabaseModel#applyOnInteract2DBounds). If all objects inside the query window are known to be cached from a previous query, access to the database can be avoided.

ImprovementLuciadFusion

The offset icon sample now allows enabling and disabling the labels of the offset icons.

ImprovementLuciadFusion

LMAP-3289

The ALcdWMSNamedLayer class in the WMS client API has three new methods:

boolean isNoSubsets(): Returns the value of the noSubsets parameter.
int getFixedWidth(): Returns the value of the fixedWidth parameter.
int getFixedHeight(): Returns the value of the fixedHeight parameter.

This allows users of the API to check whether these limitations are set on a layer.

ImprovementLuciadFusion

LMAP-3289

The ALcdWMSLayer class in the WMS server API has three new methods:

boolean isNoSubsets(): Returns the value of the noSubsets parameter.
int getFixedWidth(): Returns the value of the fixedWidth parameter.
int getFixedHeight(): Returns the value of the fixedHeight parameter.

The TLcdWMSLayer class that extends this abstract class also has corresponding setter methods for these parameters. If set, these parameters will also be encoded in the server capabilities, and the server will take them into account when validating an incoming GetMap request.

These parameters can also be set in the capabilities configuration file of the WMS server sample.

ImprovementLuciadFusion

LMAP-3088

The WFS client now has support for requesting a sorted list of features from a WFS server that supports the sortBy element. This can be done by setting a TLcdOGCSortBy on a TLcdWFSGetFeatureRequest.

ImprovementLuciadFusion

LMAP-3088

The WFS server now supports the sortBy parameter in KVP and XML requests. The features returned by the server will be sorted in the requested order. In case a maximum number of features has been set, the sorting will be applied before applying the feature limit.

ImprovementLuciadFusion

LMAP-3286

TLcdGXYIconPainter can now use ILcdOriented objects to rotate icons. In addition, the painter now supports fixed and dynamic icon scaling.

ImprovementLuciadFusion

LMAP-2072

The WMS client API has been extended with new functionality to connect with a WMS service:

A new class TLcdWMSClient has been introduced that facilitates direct communication with a WMS service, by offering functionality to create and send custom requests, and interpreting their result.
Requests are modeled by the existing interface ILcdOWSRequest, of which default implementations exist to represent the existing WMS requests: TLcdWMSGetCapabilitiesRequest, TLcdWMSGetFeatureInfoRequest, TLcdWMSGetMapRequest, TLcdWMSDescribeLayerRequest and TLcdWMSGetLegendGraphicRequest.
The result of a GetCapabilities request is an ALcdOGCWMSCapabilities instance. The result of the other requests is modeled by a TLcdOWSInputStream. This existing class is an extension of InputStream with the addition of a content type property and some metadata.
To allow control over the communication platform used to connect with a service, the interface ILcdOWSTransport can be used. This interface is used by TLcdWMSClient for its communication. A default implementation TLcdOWSHttpTransport exists with support for the HTTP protocol.

The existing API, consisting of a TLcdOGCWMSProxyModelDecoder to create an ALcdWMSProxy object for a given WMS URL, has been adapted to use the new TLcdWMSClient class.

ImprovementLuciadFusion

LMAP-1454

The WMS client now fully supports SLD enabled servers:

GetMap requests can be initialized with an SLD and sent as a KVP or XML request.
Support for DescribeLayer and GetLegendGraphic requests with KVP encoding has been added.

ALcdEarthGLTiledClipmapLevel now correctly handles tile updates that indicate that the tile is no longer available.

Bug fixLuciadFusion

ALcdEarthGLTiledClipmapLevel instances that automatically update tiles upon each paint now ignore tile update callbacks that return the same tile.

Upgrade considerationLuciadFusion

LMAP-3506

The TLcdEarthCompositeImageTileSet now disposes all the tilesets added to it when it is disposed. This behaviour is consistent with the TLcdEarthCompositeTileSet.

Upgrade considerationLuciadFusion

LMAP-3098, LMAP-3258

The unit of measure of ILcdGridReference instances is now taken into account for the z-coordinate as well. Previously, transformations involving an ILcdGridReference assumed that the z-coordinate was expressed in meters. Note that the scale parameter of an ILcdGridReference instance is only applied to the (x,y) grid coordinates as before.

Upgrade considerationLuciadFusion

The model decoder attribute of ILcdEarthAssets is now optional. This allows using the assets to just describe the contents of an ILcdEarthTileSet. To get the old behaviour you can use the TLcdEarthRasterAssetCodec.setModelDecoderOptional method.

Upgrade considerationLuciadFusion

TLcdAWTUtil: now has convenient invoke* methods that first check if they are running on the Event Dispatch thread. The signature of invokeAndWait was changed to no longer throw checked exceptions. This should not cause any issues as the method was documented as "Internal LuciadMap util method". In the very unlikely event that you are affected, it will cause a compiler error. You can then simply replace any calls to TLcdAWTUtil.invokeAndWait with EventQueue.invokeAndWait.

Upgrade considerationLuciadFusion

The lcd_ogc_schema_resources.jar has been split in 3 separate jars: lcd_xml_resources.jar (containing the schemas for XML), lcd_gml3_resources.jar (gml schemas) and lcd_ogc_resources.jar (ogc schemas such as filter and sld). Applications should update their classpath accordingly.

Upgrade considerationLuciadFusion

The TLcdEarthTerrainElevationProvider now throws an exception if a a model that it does not support is added instead of ignoring the model. See TLcdEarthTerrainElevationProvider.isSupportedElevationModel for more details on which models this elevation provider supports.

Upgrade considerationLuciadFusion

ILcdLayerTreeNode: the methods addHierarchySelectionListener and removeHierarchySelectionListener have been added to the interface.

The impact of this change should be minimal. Only nodes which directly implement this interface will result in compile errors. Notice that the support class to create such nodes (TLcdLayerTreeNodeSupport) has been adjusted. Implementations could delegate the call for these extra methods to the support class.

Upgrade considerationLuciadFusion

ILcdView: the autoUpdate property has been moved from ILcdGXYView and ILcdGLView to ILcdView, and methods are added to add or remove a PropertyChangeListener to the view.

The behavior of the standard views has been slightly modified with respect to the autoUpdate property: when switching the property from false to true, a repaint of the view is triggered, which was not the case in earlier versions. Also, all our ILcdView implementations now fire a PropertyChangeEvent when altering the autoUpdate property.

The impact of this change should be minimal. The added methods were actually moved from ILcdGXYView and ILcdGLView, so all existing views implementing these interfaces can remain unchanged. Views implementing ILcdView directly will cause a compile error.

Upgrade considerationLuciadFusion

LMAP-3379

TLcdGXYHaloLabelPainter and TLcdGXYHaloLabelPainter2, and TLcdGXYHaloPainter now allow wrapping ILcdGXYLabelPainterProvider and ILcdGXYPainterProvider instances, respectively. This will cause compilation errors if you used these classes with an ILcdGXYPainter or ILcdGXYLabelPainter instance that also implements ILcdGXYPainterProvider or ILcdGXYLabelPainterProvider. Simply casting your argument to ILcdGXYPainter or ILcdGXYLabelPainter will solve these errors.

ImprovementLuciadFusion

TLcdJULFileHandler automatically creates the directory containing the log files, if it does not exist.

Bug fixLuciadFusion

LMAP-3607

ALcdGXYStampLabelPainter, TLcdGXYHaloPainter, TLcdGXYHaloLabelPainter, TLcdGXYIconPainter, TLcdLonLatGridPainter, TLcdHaloIcon: halo painting now takes into account rendering hints such as anti-aliasing.

Bug fixLuciadFusion

LMAP-3600

The TLcdSVGModelDecoder was not always correctly decoding paths. This has been fixed.

Bug fixLuciadFusion

Bug fixLuciadFusion

The TLcdEarthTileSetElevationProvider now properly checks the input parameters of its setters.

GARSCoordinateFormat did not correctly parse cell rows.

Bug fixLuciadFusion

Bug fixLuciadFusion

TLcdEarthTileSetElevationProvider: improved performance and added some methods to manage the tile cache size.

Bug fixLuciadFusion

LMAP-3453

Performance logging no longer throws an exception when the layer name contains a ':' character.

Bug fixLuciadFusion

TLcdSHPModelEncoder now correctly encodes the Z value of the points when the export3D property is enabled.

Bug fixLuciadFusion

LMAP-3391

TLcdEarthTerrainElevationTileSet: Fixed null native georeference for terrain geometry coverage.

ImprovementLuciadFusion

TLcdWFSProxyModel has become more robust. It can now also handle situations where the WFS server does not include a schema-import in the XML encoding of GetFeature results.

ImprovementLuciadFusion

LMAP-3378

To improve the robustness, the WMS client now adds 'SERVICE=WMS' to all GetMap requests. This is not required by the WMS specification, but some servers do check for it.

Bug fixLuciadFusion

TLcdEarthGLTerrainClipmapLevel: Added support for textures in varying formats.

Bug fixLuciadFusion

TLcdEarthImageCombiner: Added support for combining images opaque and translucent images.

Bug fixLuciadFusion

ALcdEarthTileSetMultilevelRaster: Added support for non-geodetic tileset references.

ImprovementLuciadFusion

LMAP-3212

ImprovementLuciadFusion

TLcdEarthAssetModelCodec: Improved error reporting.

ImprovementLuciadFusion

The EPSG codes database has been upgraded to version 7.1.

ImprovementLuciadFusion

The TLcdMIFModelEncoder now encodes the line style (pen) of TLcdMIFPLine and TLcdMIFRegion model elements.

ImprovementLuciadFusion

LMAP-3305

The TLcdWKTReferenceParser is now able to decode projected systems that use the polyconic projection.

Bug fixLuciadFusion

LMAP-3342

Bug fixLuciadFusion

Added halo enabled, halo color and halo thickness to the *LabelPainterBeanInfo classes. As a result, the TLcdBeanEditAction used on a corresponding label painter shows the halo properties.

Bug fixLuciadFusion

LMAP-3293

TLcdGXYOffsetIconPainter no longer throws NullPointerExceptions when the delegate label painter does not implement ILcdGXYLabelPainter2, as is the case for the MS2525b/APP6a label painters.

Bug fixLuciadFusion

LMAP-3291

The TLcdSphereUtil.polygonContains2D was sometimes returning the wrong results if one of the polygon edges was along the Equator. This has been fixed.

Bug fixLuciadFusion

LMAP-3292

The license server now correctly handles failed UDP communication on Windows 2000.

ImprovementLuciadFusion

TLcdPolyconic provides an implementation of the polyconic projection.

ImprovementLuciadFusion

Improved support for namespace prefixes during encoding. Prefixes set using TLcdXMLSchemaBasedEncoder.registerNamespaceURI now override the default prefixes. Also, the encoder libraries for many formats (GML, AIXM, XLink, ...) have been adapted to have a suitable default namespace prefix. The TLcdXMLFeaturedEncoderLibrary class now supports a new constructor with an additional namespace prefix argument.

Bug fixLuciadFusion

LMAP-3278

Filter encoder and decoder libraries now register proper object factories for all their domain classes. This enables other XML schema based libraries to correctly refer to these classes.

Bug fixLuciadFusion

Bug fixLuciadFusion

LMAP-3269

TLcdRectifiedProjectiveProjection no longer produces mapping artifacts when the distortion is large.

Bug fixLuciadFusion

LMAP-3274

TLcdDMEDTileDecoder now decodes spaces in DMED files as unknown elevations instead of 0 elevations.

ImprovementLuciadFusion

TLcdDatabaseModelDescriptor now has the database URL as source name (instead of null).

Bug fixLuciadFusion

Fixed a NullPointerException when encoding nested binary operators.

ImprovementLuciadFusion

LMAP-3270

Support has been added for SLD external graphics that use the unofficial MIME type image/jpg.

ImprovementLuciadFusion

The transient memory usage during XML decoding has been reduced. The memory footprint of an XML model has also been reduced.

ImprovementLuciadFusion

LMAP-1607

The TLcdUPSMgrsUtil allows the transformation from MGRS UPS coordinates back to geodetic coordinates.

ImprovementLuciadFusion

LMAP-3048

The XML encoding of a GetFeature request generated by TLcdWFSGetFeatureRequest#getXMLEncoding() did not take into account the 'MAXFEATURES' attribute. This is now supported, allowing to set a maximum amount of features when using WFS XML POST requests.

ImprovementLuciadFusion

TLcdWFSProxyModel now uses internally cached XML Schemas for well-known OGC schemas when parsing DescribeFeatureType request results, which results in a better performance.

Bug fixLuciadFusion

LMAP-3271

The TLcdWarpRasterPainter could throw an ArrayIndexOutOfBoundsException under certain circumstances. This has been fixed.

Bug fixLuciadFusion

Incorrect schema locations for the GML 2 and GML 3.2 schemas were corrected.

Bug fixLuciadFusion

Bug fixLuciadFusion

LMAP-3166

Upgrade considerationLuciadFusion

Introduction of the class TLcdXMLMapping for schema-less encoding and decoding. This makes the schema-less interface much more compatible with the schema-based interface. As a result, the method TLcdXMLDecoder#getJavaClassResolver() was removed. Applications that rely on this method should be adapted to use TLcdXMLDecoder#getMapping()#getJavaClassResolver().

ImprovementLuciadFusion

A new interface, ILcdSelfDescribedFeatured, is added to the API. It is an extension of ILcdFeatured that provides direct access to its ILcdFeaturedDescriptor and its features via their name (instead of feature index).

ImprovementLuciadFusion

LMAP-825

TLcdMultivaluedRasterPainter now rotates the multi-valued icon if it implements ILcdOriented.

ImprovementLuciadFusion

TLcdRotatingIcon has been introduced, which is an implementation of ILcdIcon that uses the decorator design pattern to rotate another given ILcdIcon.

ImprovementLuciadFusion

An extra property, with a getter and a setter for it, is added to several ILcdModelDecoders to switch between TLcdModelLists and ILcdModelTreeNodes. The default behavior is left unchanged: by default none of the decoders returns an ILcdModelTreeNode. The decoders with this extra property are:

TLcdTarModelListDecoder
TLcdZipModelListDecoder
TLcdGRIBBulletinModelDecoder
TLcdRaveGeoModelDecoder
TLcdUSRPModelDecoder

ImprovementLuciadFusion

LMAP-2833

TLcdModelList now throws TLcdModelContainerEvents when models are added or removed by implementing ILcdModelContainer.

ImprovementLuciadFusion

ALcdGXYController now supports sending out status events.

ImprovementLuciadFusion

Improved performance of TLcdEarthGXYRasterPainter and TLcdEarthGXYElevationRasterPainter significantly.

ImprovementLuciadFusion

LMAP-2333

ImprovementLuciadFusion

LMAP-2781

ALcdGXYRasterPainter and implementations now support selection and snapping. To support selection, the ALcdGXYRasterPainter#isTouched implementation has been redefined. To support snapping, the ALcdGXYRasterPainter#snaptarget now returns one of the bounds points if they are touched.

ImprovementLuciadFusion

LMAP-3118

TLcdGXYEllipsePainter now allows manipulation of the handles without having to use CTRL.

ImprovementLuciadFusion

LMAP-3117

TLcdGXYIconPainter#getCursor now returns a translation cursor when appropriate.

ImprovementLuciadFusion

TLcdDTEDTileDecoder now supports the additional sampling strategies MINIMUM, MAXIMUM, and AVERAGE.

ImprovementLuciadFusion

ALcdEarthGLPainterBase has a new method setClipCenterMode(), which gives users some control over how the clip center is chosen. Options include the camera eye point and reference point, as well as a new "adaptive" mode in which the clip center is moves in between the eye and reference points in function of the pitch of the camera.

ImprovementLuciadFusion

LMAP-3072

TLcdGeoTIFFModelDecoder and related decoders now support standard Projected Coordinate Systems with explicitly specified units of measure for their coordinates, as used in some non-standard data sets like the 15 cm aerial JPEG2000 images of NY state.

ImprovementLuciadFusion

TLcdGeoTIFFModelEncoder, TLcdGeoTIFFModelDecoder, and related decoders now support grid coordinate systems with more units of measure.

ImprovementLuciadFusion

LuciadMap now offers support for performance monitoring. The following operations can be measured:

Painting time of the 2D and 3D views
Painting time of the 2D and 3D layers
Decoding time of the following formats: SHP, CGM, Database, GML, IGRF, WMM, MIF, POL, BCI, BIL, CADRG Directory, CADRG, DEM, DIMAP, DMED, DTED Directory,DTED, ECW, ETOPO, GeoSPOT, GeoTIFF, JAIRaster, JPEG2000, MrSID, NITF, Raster, SwissDHMMatrix, TAB, TFW, USRP, SVG, DWG, DWG model list, DGN, DGN model list, Oracle GeoRaster, Oracle spatial, Informix Geodetic, PostgreSQL, GDF, GRIB, GRIB Bulletin.

Details about the usage of performance monitoring can be found in the LuciadMap and 3D developer guides.

ImprovementLuciadFusion

LMAP-2525

A new class called TLcdEPSGGeodeticDatumFactory allows to create a geodetic datum based on its WKT name. The datums supported by this class are a subset of the datums from the current EPSG database (v6.18.2).

ImprovementLuciadFusion

The logging class TLcdLog and the associated ILcdLogListener implementations TLcdSystemLog and TLcdOutputFrame have been deprecated. Users are now encouraged to use the TLcdLoggerFactory class and the ILcdLogger interface. Details about the new framework can be found in the "Logging and performance monitoring" appendix of the LuciadMap developer's guide.

ImprovementLuciadFusion

LMAP-2560

TLcdGXYEditController(2): edit controller now only performs snapping when there is a single object to edit. This prevents multiple points to snap to the same location, giving the impression that some points disappeared.

ImprovementLuciadFusion

ILcdGXYView#addGXYLayer(ILcdGXYLayer): the documentation now allows implementations to add layers at indices other than the top most index.

ImprovementLuciadFusion

A new package, com.luciad.util.collections, was introduced. It provides support for collections of primitive types (boolean, byte, char, double, float, int, long, short). Both interfaces and array-based implementations are provided for each of these types.

ImprovementLuciadFusion

LMAP-2945

TLcdGXYStampLabelPainter#setHaloPinColor can now be used to set the halo color for label pins, even when the label itself does not have a halo.

ImprovementLuciadFusion

The new class TLcdGeoidGeodeticDatumFactory can create geodetic datums of which the vertical datums are geoids, for example EGM96, EGM84, NAVD88, NGVD29, and so on.

ImprovementLuciadFusion

A set of new shape interfaces and implementations have been added to com.luciad.shape, to support open and/or closed shapes consisting of a connected combination of lines and arcs.

For this purpose, a new interface ILcdCurve has been added to com.luciad.shape, providing a general representation of a continuous, one-dimensional shape. Examples of curves are lines, arcs, or any connected combination thereof. The following extensions and implementations of this interface are introduced:

ILcdRing: a closed curve (i.e., begin and end point are the same),
ILcdCompositeCurve, TLcdCompositeCurve: a connected sequence of curves,
TLcdLonLatCompositeRing, TLcdXYCompositeRing: a closed, connected sequence of curves,
TLcdLonLatRhumbPolyline: a polyline consisting of rhumbline segments (i.e., constant bearing),
TLcdLonLatRhumbPolygon: a polygon consisting of rhumbline segments (i.e., constant bearing),
ILcdCircularArcByBulge: a circular arc defined by a start point, end point, a bulge direction and a bulge factor,
ILcdCircularArcBy3Points: a circular arc defined by a start point, end point, and a third point on the arc,
ILcdCircularArcByCenterPoint: a circular arc defined by a center point, radius, start angle and arc angle,
ILcdCircleBy3Points: a circle defined by 3 points.

To support the visualization and editing of newly introduced shape types, the following painter/editor implementations have been introduced:

TLcdGXYCompositeCurvePainter: paints and enables visual editing of ILcdCompositeCurve objects,
TLcdGXYCompositeRingPainter: paints and enables visual editing of ILcdCompositeCurve/ILcdRing objects,
TLcdGXYCircularArcPainter: paints and enables visual editing of ILcdCircularArcByBulge, ILcdCircularArcBy3Points and ILcdCircularArcByCenterPoint objects.
TLcdGXYCircleBy3PointsPainter: paints and enables visual editing of ILcdCircleBy3Points objects.

Shapes of type TLcdLonLatRhumbPolyline or TLcdLonLatRhumbPolygon are supported by the existing TLcdGXYPointListPainter class.

To ensure the connectivity between different curves in an ILcdCompositeCurve, the interface ILcdCurveConnector is introduced. By means of an ILcdCurveConnectorProvider, it is used by painter/editor implementations TLcdGXYCompositeCurvePainter and TLcdGXYCompositeRingPainter to ensure connectivity while editing.

All new shapes are illustrated in the "create and edit with mouse" sample.

ImprovementLuciadFusion

LMAP-2639

TLcdInputStreamFactory: now creates buffered input streams.

ImprovementLuciadFusion

A new class TLcdDefaultModelXYWorldTransformation aggregates the existing ILcdModelXYWorldTransformation implementations, and is now used as default transformation class in TLcdGXYLayer. As a result, setting it manually (setModelXYWorldTransfoClass) is no longer required (except when not using the build-in model references).

ImprovementLuciadFusion

ImprovementLuciadFusion

TLcdAdvancedMapRulerController: now has a method setHotPointIcon to change the icon of the handles.

ImprovementLuciadFusion

LMAP-2968

TLcdGXYPanController has a new method setDragViewOnPan. If enabled, the entire view is repainted while dragging. This behavior is activated by default in the LuciadMap samples.

ImprovementLuciadFusion

LMAP-2928

ToolBarSW#addGXYController now adds pan and zoom behavior for the middle mouse button and mouse wheel, respectively. It makes use of two new wrapper classes MouseButtonFilteringController and MouseButtonMappingController.

ImprovementLuciadFusion

LMAP-2786

TLcdMIFModelDecoder was always decoding the features of the shapes as String objects. The types of the features is now more appropriate.

Bug fixLuciadFusion

LMAP-3191

The SHP model decoder was creating a 2D indexed model, even if the model had invalid bounds (for example, if it contained a single point the bounds had 0 width/height). In such a case the decoder now returns a non-indexed model.

Bug fixLuciadFusion

TLcdGXYViewLabelPainter and TLcdGXYLayerLabelPainter would sometimes use the same label location for different sublabels.

Bug fixLuciadFusion

LMAP-2987

TLcdGXYOffsetIconPainter now supports fixed label placement, making it compatible with TLcdGXYLayerLabelPainter and TLcdGXYViewLabelPainter. Also, the offset icon sample is now decluttered by default.

Bug fixLuciadFusion

Bug fixLuciadFusion

LMAP-3140

Upgraded the packaged proguard jar to the latest version to prevent some obfuscation problems with certain versions of JDK 1.6

Bug fixLuciadFusion

LMAP-3135

TLcdDMEDModelDecoder and TLcdDTEDDirectoryModelDecoder with checkTilesImmediately set to true now provide the correct raster pixel densities, even if some lower DTED levels are missing.

Bug fixLuciadFusion

TLcdGXYViewFitAction: now supports fitting on multiple layers.

Bug fixLuciadFusion

LMAP-2455

TLcdGXYLayer now filters the selection when a filter has been set to the layer. In addition, the selection is kept up to date if the filter in question implements ILcdChangeSource.

Bug fixLuciadFusion

TLcdGXYPanController now also pans when the meta or alt keys are pressed.

Bug fixLuciadFusion

LMAP-2828

TLcdTopocentricCoordSysTransfo2 has been deprecated in favour of TLcdTopocentricCoordSysTransformation.

Bug fixLuciadFusion

LMAP-2888

TLcdTFWRasterModelDecoder falls back to ImageIO when decoding via JAI fails.

Upgrade considerationLuciadFusion

The XML binding framework, introduced as beta API in LuciadMap 8.2, has undergone some changes to improve its usability and extensibility. This affects the following packages:

com.luciad.format.xml.bind
com.luciad.format.xml.bind.schema

The following table lists all class renamings which have been done between 8.2 and 9.0:

TLcdXMLUnmarshallerContext	TLcdXMLDecoder
TLcdXMLMarshallerContext	TLcdXMLEncoder
ILcdXMLUnmarshallerLibrary	ILcdXMLDecoderLibrary
ILcdXMLMarshallerLibrary	ILcdXMLEncoderLibrary
TLcdXMLSchemaUnmarshallerContext	TLcdXMLSchemaBasedDecoder
TLcdXMLSchemaMarshallerContext	TLcdXMLSchemaBasedEncoder
ILcdXMLSchemaUnmarshallerLibrary	ILcdXMLSchemaBasedDecoderLibrary
ILcdXMLSchemaMarshallerLibrary	ILcdXMLSchemaBasedEncoderLibrary
ILcdXMLSchemaTypeUnmarshaller	ILcdXMLTypeUnmarshaller
ILcdXMLSchemaTypeMarshaller	ILcdXMLTypeMarshaller
ILcdXMLSchemaDatatypeUnmarshaller	ILcdXMLDatatypeUnmarshaller
ILcdXMLSchemaDatatypeMarshaller	ILcdXMLDatatypeMarshaller
TLcdXMLSchemaTypeUnmarshallerProvider	TLcdXMLTypeUnmarshallerProvider
TLcdXMLSchemaTypeMarshallerProvider	TLcdXMLTypeMarshallerProvider
TLcdXMLSchemaInfo	TLcdXMLSchemaSet

The following additional API changes have been done:

The static newInstance() methods of all unmarshaller and marshaller context classes have been replaced with ordinary constructors in the new decoder and encoder classes.
The unmarshal() and marshal() methods of all unmarshaller and marshaller context classes have been renamed to decode() andencode().
The configureContext() methods of all (un)marshaller library interfaces have been to configureDecoder() andconfigureEncoder().
The Map argument of the (un)marshal and (un)marshalType methods of all (un)marshallers, type (un)marshallers and datatype (un)marshallers has been replaced with a ILcdXMLDocumentContext argument, which offers a richer API for storing and retrieving objects, based on their scope within the XML document.
TLcdXMLSchemaBindingDescriptor is no longer part of the API. Its functionality has been largely moved to the more general TLcdXMLSchemaBasedMapping class.
The ILcdXMLObjectFactory and TLcdXMLTypeObjectFactoryProvider classes have been introduced in the API, in order to separate object instantiation and unmarshalling during theXML decoding process. This allows to plug in custom object factories without having to rewrite unmarshallers.
The ILcdXMLElementInfo interface has been added to the API to allow for XML-Java-XML roundtrips without loss of information. This purpose of this interface is similar to the one provided by JAXBElement: it models an XML element, and allows to store specific XML-related information about the element, which is typically not stored otherwise in the Java representation of the XML data.
All unmarshaller and marshaller interfaces, and their corresponding providers have been generified, with as type parameter the Java class they can unmarshal or marshal.

Upgrade considerationLuciadFusion

LMAP-2833

TLcdModelList now implements ILcdModelContainer:

The addModel(ILcdModel) and addModel(ILcdModel, ILcdFilter) methods now return a boolean indicating whether the collection of models has changed. Classes overriding one of these methods will result in a compile error.
The removeModel(ILcdModel) method now returns a boolean indicating whether a model has been removed from the collection of models and no longer throws a NoSuchElementException when the model was not part of the model list. Classes overriding this method will result in a compile error. Usages of this method which relied on the NoSuchElementException will behave oddly at runtime, since no such error is thrown anymore. The returned boolean can now be used in order to determine whether a model was an element of the model list. It is also no longer necessary to check whether the model is part of the model list before calling the removeModel(ILcdModel) method.
The methods modelCount(), models(), addModelContainerListener(ILcdModelContainerListener) and removeModelContainerListener(ILcdModelContainerListener) have been added.

Upgrade considerationLuciadFusion

LMAP-3116

The interface com.luciad.ogc.wfs.ILcdWFSFeatureType has been extended with a getter and setter to configure a qualified feature name through a javax.xml.namespace.QName object. This might require an update, if a custom implementation of ILcdWFSFeatureType is used.

Upgrade considerationLuciadFusion

All ILcdGXYPainter#isTouched implementations now check whether the paint mode includes ILcdGXYPainter.HANDLES or ILcdGXYPainter.BODY before checking if the handles or bodies are touched, respectively, allowing finer-grained isTouched checks. An example implementation of this behavior can be found in the hippodrome sample painter. If you call these methods, please make sure that the paint mode contains the necessary flags. In particular, please make sure the mode argument contains ILcdGXYPainter.BODY if you need to check if the body was touched.

Upgrade considerationLuciadFusion

The return type of TLcdEarthAssetModelCodec.getDefaultModelReference() has been generalized from TLcdGeodeticReference to ILcdModelReference.

Upgrade considerationLuciadFusion

ILcdGXYEditor's END_CREATION flag is now deprecated. The mode was misused to also include the behavior of ILcdGXYEditor.CREATING, which made it impossible to combine with, for example, double-click behavior. TLcdGXYNewController2 does not use this mode anymore. If necessary, perform the object's final initialization in the new controller model instead.

Upgrade considerationLuciadFusion

The interfaces ILcdTreeLayered, ILcdLayerTreeNode and ILcdModelTreeNode have been introduced, allowing to easily create hierarchical layer and model structures. In relation to that, these changes were made:

A getter and setter for an ILcdIcon are added to the ILcdLayer interface. The impact is minimal as all sub-interfaces (ILcdGXYLayer and ILcdGLLayer) already had these methods. If you are affected by this change, it results in a compile error.
ILcdGXYView now implements ILcdTreeLayered instead of ILcdLayered. This results in one new method (getRootNode). In the unlikely event of implementing an ILcdGXYView directly, please implement the extra method as well, probably by delegating the call to another ILcdGXYView. If you are affected by this change, it results in a compile error.
The following methods in ILcdModelContainer have been renamed to avoid clashing with the methods of ILcdModel. As this interface was not used anywhere, the impact is expected to be minimal. If you are affected by this change, it results in a compile error.
- ```
elements()
```
  to
```
models()
```
- ```
size()
```
  to
```
modelCount()
```
- ```
elementAt(int)
```
  to
```
getModel(int)
```
The addModel method of ILcdModelContainer can now throw IllegalArgumentException for invalid objects.
TLcdLayeredEvent now contains (optional) indices, indicating where the change took place. All LuciadMap code is adapted to provide those indices.

As long as no ILcdLayerTreeNode s are used, nothing changes except the changes mentioned above. When layer nodes are used, extra care must be taken when

Moving a GXYLayer in the GXYView: ILcdGXYView now implements ILcdTreeLayered which affects the behavior of the move operation. The move operation has become a best effort approach. Details of the implications of this change can be found in the developer guide and in the javadoc of the TLcdTreeLayeredSupport#moveLayerAt.
Inserting a layer node in the GXYView: inserting a layer node in the view adds the layer node as a child of the root node, and adds the layer node and all of its children to the view (ILcdGXYView#layers()). Events are generated for every layer that was added to the view.
Requesting all the layers from the GXYView:
calling ILcdGXYView#layers() returns all the layers and layer nodes in the view. When for example copying these layers to another view by looping over the result care must be taken (this is typically done when printing a view). Since the layer nodes are also returned, adding a layer node to the second view will also insert all the child layers to the second view. Those child layers were also returned when calling ILcdGXYView#layers(), hence they would be added twice.

A correct approach for the use-case mentioned above is requesting all the child layers from the root node of the view, and add all those layer(node)s to the second view. Consult the developer guide for a more detailed explanation.
Layer order of the GXYview: the paint order of the layers in the view (ILcdGXYView#layers) is not necessarily related to the layer tree structure (ILcdGXYView#getRootNode). This means that all tasks that directly or indirectly rely on the paint order (for example select controller, ... ) should continue to use the 'flat list' (ILcdGXYView#layers()) and not the hierarchical structure (getRootNode) directly.
Adding a model to an ILcdView: adding a model to an ILcdView by calling ILcdView#addModel will use the layer factory which is set on the view. Depending on whether the layer factory creates ILcdLayerTreeNode 's for TLcdModelList's and/or ILcdModelTreeNode's, the behavior of the addModel method will be slightly different:
1. When a model list is added to the view, and a layer node is created to represent this model list, the model list should not be set as the model of the layer tree node. Hence calling ILcdTreeLayered#layerOf(ILcdModel) with the model list will throw a NoSuchElementException. In case a layer list is created, the model list should be the model of the layer list and calling ILcdTreeLayered#layerOf(ILcdModel) will return the created layer list.
2. When a model list is added to the view, and a layer node is created to represent this model list, the view will be aware of the layer node itself and all of its child layers. These child layers represent the sub-models of the model list. Calling ILcdTreeLayered#layerOf(ILcdModel) with one of the sub-models will return the correct child layer. In case a layer list is created, the view is not aware of the different sub layers. Calling ILcdTreeLayered#layerOf(ILcdModel) with one of the sub-models will throw a NoSuchElementException.
  Notice that the same remark is valid for adding an ILcdLayerTreeNode directly to the view. The view will be aware of the layer tree node and its child layers, which is not the case when a layer list is added to the view.

The recommended way to replace existing ILcdGXYLayerList's to ILcdLayerTreeNode's is to create an empty ILcdLayerTreeNode and add all the layers as child layers to the created layer tree node instead of adding them to a new ILcdGXYLayerList.

However, care must be taken since the behavior of the layer lists and layer nodes is slightly different on some points:

The model: the model of the ILcdGXYLayerList was an ILcdModelList, composed of all the models of the sub-layers. The ILcdLayerTreeNode is a layer itself, with child layers, without any relationship between the model of the node and the models of its children. So the model list should not be used as the model of the layer tree node, as that would cause objects to be painted twice.
All ILcdGXYLayer operations: the standard ILcdGXYLayerList implementation (TLcdGXYLayerList) delegated those operations to all of its sub-layers, where calling these methods on an ILcdLayerTreeNode will not pass the call to its children. So for example the
```
applyOnInteract
```
method will work on the node itself, and not on the child layers which was the case for the layer list. Another example is the
```
getSelectionCount()
```
method. For an TLcdGXYLayerList this returned the sum of the selection counts of all the sub-layers, where for an ILcdLayerTreeNode it just returns the selection count of the node itself. If one wants to retrieve the selection count of all the sub-layers, (s)he must loop over all sub-layers and ask the sub-layers for their selection count. Consult the javadoc of those methods for more detailed information about the differences.
Similarly, listeners added to a node only receive changes about that node itself and not about the child nodes. Some addHierarchy*Listener methods are available that do listen on a node and all its descendants.
The view: with an ILcdGXYLayerList, the view was unaware of the sub-layers and treated the layer list and its sub layers as one big layer. This is no longer the case with an ILcdLayerTreeNode. When such a node is added to the view, all of its child layers are also added and the view knows about those child layers. This happens automatically. For example, it is not necessary to add both the node and all its child layers to the view individually. Adding the node is sufficient. Consult the developer's guide for more information (the section about ILcdTreeLayered).

Upgrade considerationLuciadFusion

The interface ILcdGeodeticDatum has received new methods getHeight, hasNonZeroHeights, equals2D, llh2geocSFCT and geoc2llhSFCT, to integrate the new vertical datum support in an efficient way. This allows using geoids for geodetic datums and ILcdGeoReference instances such as ILcdGridReference. The new vertical datum support is used by all LuciadMap implementations of ILcdModelXYWorldTransformation, ILcdModelXYZWorldTransformation, ILcdModelModelTransformation, and ILcdXYWorldXYWorldTransformation. Classes implementing the old vertical datum support (ILcdVerticalDatum, TLcdNullVerticalDatum, ILcdGeoidReference, TLcdGeoidReference, TLcdGeoid2Grid, and TLcdModelModelGeoid2Grid) have been deprecated.

Upgrade considerationLuciadFusion

LMAP-1047

TLcdLayeredEvent#ALL_REMOVED has now been deprecated in favor of multiple REMOVED events, allowing the listener to be informed of each removed layer. All LuciadMap view implementations no longer use this event type.

Upgrade considerationLuciadFusion

LMAP-2591

TLcdGXYPolygonLabelPainter#paintLabels(String[], ILcdPolygon, ...), TLcdGXYPolygonLabelPainter#labelBoundsSFCT(Graphics, String[], com.luciad.shape.ILcdPolygon, ... ), TLcdGXYPolylineLabelPainter#paintLabels(String[], ILcdPointList, ...) and TLcdGXYPolylineLabelPainter#labelBoundsSFCT(Graphics, String[], com.luciad.shape.ILcdPointList, ... ), have been deprecated. In addition, the paintLabels methods now perform the haloing themselves, being consistent with the paintLabel method. Instead of calling the deprecated methods, set the relevant object on the painter before calling the respective methods without the polygon or point list argument. To customize the labels, the method #retrieveLabels can be overridden.

Upgrade considerationLuciadFusion

LMAP-2892

TLcdGXYNewController now respects the editor's #getCreationClickCount when creating new objects. This means that it is now impossible to create a polyline consisting of a single point, or a polygon consisting of less than 3 points. This behavior can be modified by overriding the #isContinueEdit method.

Upgrade considerationLuciadFusion

LMAP-1998

ILcdGXYEditor: the semantics of #getCreationClickCount have been changed to also express a minimum click count when there is no limit on the number of creation clicks, allowing values lower than -1. The implementations in the following editors have been modified to follow this convention:

TLcdGXYBufferPainter, TLcdGXYGeoBufferPainter, and TLcdGXYLonLatHeightBufferPainter
TLcdGXYPointListPainter

Upgrade considerationLuciadFusion

LMAP-2882

The deprecated library JimiProClasses.jar has been removed. The deprecated class TLcdTIFFImageDecoder, which was using it, is now an extension of TLcdGeoTIFFImageDecoder, which is better and compatible for all practical purposes.

Upgrade considerationLuciadFusion

The following new packages were added to improve support for GML:

com.luciad.format.gml2.model
com.luciad.format.gml2.xml
com.luciad.format.gml31.model
com.luciad.format.gml31.xml
com.luciad.format.gml32.model
com.luciad.format.gml32.xml
com.luciad.format.gmlcommon

These packages provide domain models, decoders and encoders for the GML 2, 3.1 and GML 3.2 formats. Additionally, a generic GML decoder is also provided,

    com.luciad.format.gmlcommon.xml.TLcdGMLModelDecoder

, which is capable of handling all GML formats. These packages are built upon the new XML framework (com.luciad.format.xml.bind). They replace all existing GML packages, which are now deprecated:

com.luciad.format.gml
com.luciad.format.gml3
com.luciad.format.gml3.adapter
com.luciad.format.gml3.factory
com.luciad.format.gml3.model.*
com.luciad.format.gml3.name
com.luciad.format.gml3.reader

Bug fixLuciadFusion

LMAP-3961

TLcdGXYOffsetIconPainter#getLabelCount and #getSubLabelCount would sometimes return incorrect values. This could cause exceptions when, for example, selecting offset icons.

Bug fixLuciadFusion

A bug in the decoding of gml3:LineStringSegment elements containing gml3:DirectPositions was fixed.

Bug fixLuciadFusion

LMAP-3017

TLcdEllipsoidUtil#computeBufferContour2D and TLcdCartesian#computeBufferContour2D did not correctly calculate the buffer contour at very small scales (+- 10m).

ImprovementLuciadFusion

LMAP-3114

Users can now explicitly specify the location of the license file with the java system property "luciadmap.license". For instance:

java -Dluciadmap.license=/home/user/development_license.txt
                           ...

ImprovementLuciadFusion

The TLcdWKTModelReferenceDecoder now accepts multi-line WKTs.

Bug fixLuciadFusion

TLcdGXYPen now correctly draws arcs that are defined in grid references with non-standard scales, rotations, or units of measure.

Bug fixLuciadFusion

LMAP-3053

TLcdSHPModelDecoder and TLcdMIFModelDecoder now properly handle InterruptedIOExceptions.

Bug fixLuciadFusion

LMAP-3111

TLcdGXYIconPainter#isTouched could cause a NullPointerException when #getIcon returned null.

Bug fixLuciadFusion

TLcdGXYStampLabelPainter: the interactive label system now uses the proper mode constants to retrieve label bounds and check whether a label is touched.

ImprovementLuciadFusion

TLcdOWSHttpTransport#configureConnection now sets the connection request property 'Accept-Encoding' to 'gzip, deflate, compress', allowing OGC Web Services to send compressed data.

Bug fixLuciadFusion

LMAP-3065

ALcdGXYPen#drawLineWithArrow did not draw the arrow anymore since enhancement 6690.

Bug fixLuciadFusion

Upgrade considerationLuciadFusion

LMAP-3055

TLcdGXYLayer now always calls the layer label painter for the labels paint mode, even if the layer is not labeled, allowing consistent decluttering that also works for selections. If you implement ILcdGXYLayerLabelPainter, make sure you check your layer's isLabeled() property.

Bug fixLuciadFusion

The ElseFilter did not work properly in all cases after the performance improvements of the SLD painter evaluation (see LMAP-2976).

Bug fixLuciadFusion

LMAP-3031

TLcdGXYBoundsPainter: large bounds were painted incorrectly using a geodetic pen.

Bug fixLuciadFusion

LMAP-3032

TLcdFeaturedShapeList: #hashCode no longer assumes that none of the feature values is null.

Bug fixLuciadFusion

LMAP-3011

Some sample layers did not set a geodetic pen when using a geodetic model.

Bug fixLuciadFusion

LMAP-3009

TLcdGXYLayer could cause a NullPointerException when #getBounds would indirectly call #paint.

ImprovementLuciadFusion

Updated the TLcdEarthTileRepositoryPreprocessor to use multiple threads for improved preprocessing performance. There are also a few new utility TileSet's to support concurrency.

Bug fixLuciadFusion

LMAP-3029

Fixed bad LOD choice in 3D painters when using FOV to zoom.

Bug fixLuciadFusion

LMAP-3024

The class TLcdOWSHttpTransport, used in the OGC client API to communicate with an OGC server, did not support the HTTPS protocol.

Bug fixLuciadFusion

LMAP-3023

Added missing getters for the properties of the TLcdEarthGXYRasterPainter.

ImprovementLuciadFusion

LMAP-2924

Added support for tiles containing images with an alpha channel

Bug fixLuciadFusion

Added support for terrains with non-geodetic model references

ImprovementLuciadFusion

The EPSG codes 3785 and 4055 used by Google Earth and Microsoft Virtual Earth are now supported.

ImprovementLuciadFusion

The list of supported EPSG codes has been updated. Most notably, it now includes codes 3785 and 4055 used by Google Earth and Microsoft Virtual Earth.

ImprovementLuciadFusion

LMAP-2976

ImprovementLuciadFusion

LMAP-2161

The SHP model decoder now decodes features of large integer types (Long or BigInteger), as well as Boolean and Date. The SHP model encoder now encodes the following new feature types: Long, BigInteger, Boolean. Doubles are now encoded as binary. Feature types that are not supported by the DBF format are encoded as Strings.

Bug fixLuciadFusion

Bug fix LMAP-2559 caused ALcdGXYPen to print debugging messages.

Bug fixLuciadFusion

LMAP-1660

In some circumstances, snapping stopped working while creating polylines. This also affected the ruler controller.

Bug fixLuciadFusion

LMAP-2559

The implementation of the clone methods of the pen classes has improved.

Bug fixLuciadFusion

LMAP-2904

ToolBarSW: automatically generating disabled icons for its buttons now also works with a Swing Icon (only worked with ILcdIcon), this fixes a ClassCastException in APP6A and MS2525b samples.

Bug fixLuciadFusion

LMAP-2966

The GeoTIFF model decoder handles more robustly rasters that cross the 180 degrees meridian.

Bug fixLuciadFusion

TLcdEarthTileRepository left a file handle open.

ImprovementLuciadFusion

LMAP-2886

TLcdWFSClient now automatically detects service exception reports coming from an OGC web service, in case the content type is not defined.

ImprovementLuciadFusion

LMAP-2886

TLcdWCSClient now automatically detects service exception reports coming from an OGC web service, in case the content type is not defined.

ImprovementLuciadFusion

LMAP-2413

LMAP-2898

TLcdGXYAsynchronousLayerWrapper used to fire selection events before applying the actual selection changes.

ImprovementLuciadFusion

ILcdGXYEditor capabilities were added. In case of ambiguity, the first available editor is chosen, which works well for simple SLD files where only one symbolizer is available for a given map scale.

ImprovementLuciadFusion

TLcdGXYEditController and TLcdGXYEditController2: the undoables generated by the ILcdGXYEditors no longer need to fire the model change events. The edit controller now takes care of this. This allows for better composition of editors, as the ILcdGXYEditors no longer have to assume that the object they are editing is actually contained in the given model.

ImprovementLuciadFusion

TLcdAltitudeFormat, TLcdDistanceFormat, TLcdSpeedFormat: parsing now accepts values that are entered in another unit as the display unit. If for example the parser is set to km, it also accepts "500m", which is parsed to 0.5km.

ImprovementLuciadFusion

LMAP-2692

The sample-specific controllers of the following samples now have mouse-wheel support:

create and edit with mouse
hippodrome painter
tooltips on the map
magnetic north sample
multigrid samples
projections sample

ImprovementLuciadFusion

The WFS client API has been extended with new functionality to connect with a WFS service:

A new class TLcdWFSClient has been introduced that facilitates direct communication with a WFS service, by offering functionality to create and send custom requests, and interpreting their result.
Requests are modeled by the new interface ILcdOWSRequest, of which three default implementations exist to represent the mandatory WFS requests: TLcdWFSGetCapabilitiesRequest, TLcdWFSDescribeFeatureTypeRequest and TLcdWFSGetFeatureRequest.
The result of a GetCapabilities request is modeled by a TLcdWFSCapabilities object, as before; the result of a DescribeFeatureType and GetFeature request is modeled by TLcdOWSInputStream. This new class is an extension of InputStream with the addition of a content type property and some metadata.
To allow control over the communication platform used to connect with a service, a new interface ILcdOWSTransport has been introduced. This interface is used by TLcdWFSClient for its communication. A default implementation TLcdOWSHttpTransport exists with support for the HTTP protocol.

The existing API that defines the concept of a proxy model now makes use of the newly introduced TLcdWFSClient class: when creating a proxy model through TLcdWFSProxyModelFactory, a TLcdWFSClient can be set to fully configure the mechanism used to communicate with a WFS service.

ImprovementLuciadFusion

The WCS client API has been extended with new functionality to connect with a WCS service:

A new class TLcdWCSClient has been introduced that facilitates direct communication with a WCS service, by offering functionality to create and send custom requests, and interpreting their result.
Requests are modeled by the new interface ILcdOWSRequest, of which three default implementations exist to represent the mandatory WCS requests: TLcdWCSGetCapabilitiesRequest, TLcdWCSDescribeCoverageRequest and TLcdWCSGetCoverageRequest.
The result of a GetCapabilities request is modeled by a TLcdWCSCapabilities object, as before; the result of a DescribeCoverage request is modeled by a TLcdWCSCoverageDescription object and the GetCoverage request by a TLcdOWSInputStream. TLcdOWSInputStream is an extension of InputStream with the addition of a content type property and some metadata.
To allow control over the communication platform used to connect with a service, a new interface ILcdOWSTransport has been introduced. This interface is used by TLcdWCSClient for its communication. A default implementation TLcdOWSHttpTransport exists with support for the HTTP protocol.

The existing API that defines the concept of a proxy model now makes use of the newly introduced TLcdWCSClient class: when creating a proxy model through TLcdWCSProxyModelFactory, a TLcdWCSClient can be set to fully configure the mechanism used to communicate with a WCS service.

ImprovementLuciadFusion

Bug fixLuciadFusion

TLcdMIFModelEncoder and TLcdMIFModelDecoder now properly handle text spanning multiple lines.

Upgrade considerationLuciadFusion

The use of com.luciad.format.xml.TLcdXMLName in the WFS client API has been removed in favor of javax.xml.namespace.QName, which is the Java equivalent of this class. This affects the following classes and methods:

TLcdWFSProxyModelFactory#createProxyModel()
TLcdWFSProxyModelDescriptor#getFeatureTypeName() and constructor
TLcdWFSProxyModel#setGeometryPropertyName() and getGeometryPropertyName()
TLcdWFSFeatureType#setName() and getName()

The methods TLcdWFSFeatureType#setNameSpacePrefix() and getNameSpacePrefix() have been removed, because the prefix information is already contained in the QName object.

Implementations can easily upgrade by replacing 'TLcdXMLName.getInstance("namespace", "localPart")' with 'new QName("namespace", "localPart")', or by invoking TLcdXMLName#asQName on an existing TLcdXMLName instance.

Although QName is only available since JDK 1.5, a backport library ws-commons-java5-1.0.1.jar is provided with LuciadMap to have it also in JDK 1.4.

LMAP-2804

Bug fixLuciadFusion

LMAP-2815

TLcdSelectionSupport now avoids an endless loop when a selection listener calls fireCollectedSelectionChanges().

Bug fixLuciadFusion

TLcdGXYDragRectangleController: XOR-mode painting has been disabled by default, to avoid performance problems with Sun's recent graphics pipeline implementations.

Bug fixLuciadFusion

LMAP-2780

TLcdGXYDragRectangleController: the method to deactivate the XOR mode paint functionality is no longer deprecated. Instead, a new alternative for the XOR mode has been added: halo painting.

Bug fixLuciadFusion

LMAP-2823

TLcdGXYViewJPanelLightWeight would send out view invalidation events on every repaint when in DISABLE_CACHING mode.

Bug fixLuciadFusion

LMAP-2683

TLcdEllipsoid.rhumblinePoint now handles robustly the case when the start point is the South Pole.

Bug fixLuciadFusion

LMAP-2674

Models produced by TLcdMultilevelTiledModelDecoder suffered from a race condition when the same MTM model was used in multiple layers. The issue has been fixed by synchronizing access to the model decoder in TLcdSoft2DBoundsIndexedModel.

Bug fixLuciadFusion

A bug in the encoding of some UCUM units has been fixed.

Bug fixLuciadFusion

LMAP-2808

TLcdGeoTIFFModelEncoder (as updated in LMAP-2772) now again properly closes the output streams that it creates.

ImprovementLuciadFusion

LMAP-2771

TLcdGeoTIFFModelEncoder and TLcdGeoTIFFModelDecoder now provide access to TIFF tags.

ImprovementLuciadFusion

LMAP-2772

Bug fixLuciadFusion

LMAP-2661

TLcdDefaultVVGridRenderer#getOrdinateLabelWidth now returns a label width that completely fits the given altitude ordinates.

Upgrade considerationLuciadFusion

TLcdVVJPanel's getVerticalCursorPosition used to return null when the cursor is not exactly positioned on one of the main profile points. This is no longer the case. Please use getVerticalCursorPercentage() to determine the exact position of the vertical cursor.

Bug fixLuciadFusion

LMAP-2705

TLcdColorMapCustomizer: The "Set all levels" button used to propose the entire interval if only 2 or less levels were present. It now uses the the interval specified by those 2 levels, or the visible interval (getVisibleInterval) if only one level is available.

Bug fixLuciadFusion

LMAP-2721

TLcdGXYStampLabelPainter: used to write fail messages when editing multiple objects amongst which some objects were unlabeled.

ImprovementLuciadFusion

ImprovementLuciadFusion

The vertical view's cursor change event now also contains the main profile index of the point located to the left of the cursor, making it easier to obtain an altitude value for the cursor.

ImprovementLuciadFusion

A new factory class TLcdWMSGXYViewFactory has been introduced, which is used to create and configure views in the WMS to render requested maps. Custom extensions can be integrated in the WMS by overriding the method createWMSGXYViewFactory(ServletConfig) in ALcdOGCWMSCommandDispatcherFactory.

LMAP-2552

Bug fixLuciadFusion

LMAP-2689

TLcdColorMapCustomizer: the color buttons are now also visible in the Motif Look and Feel.

Bug fixLuciadFusion

LMAP-2682

The warping raster painters no longer throw a ClassCastException if a raster does not contain a color model and any of its tiles contain a color model that's not an IndexColorModel.

Bug fixLuciadFusion

TLcdConcurrentBuffer has been fixed to avoid spurious NullPointerExceptions on multi-core processors.

Bug fixLuciadFusion

ALcdGXYSmartController no longer changes the focused window when isRequestFocusOnMouseEntered is true.

Bug fixLuciadFusion

The focus point of a TLcdLonLatPolyline is no longer moved after a move2D, but recalculated when needed. This will only be of influence when the focus point was set to the polyline using setFocusPoint in order to monitor moves of the focus point.

Upgrade considerationLuciadFusion

LMAP-2638

TLcdUndoManager: the wrongly named removeStatusListener method has been deprecated in favor of removeChangeListener. Please use that method to remove your ILcdChangeListener instances.

Upgrade considerationLuciadFusion

TLcdVVAltitudeRangeSliderJPanel: When the bottom (or top) offset property of the vertical view corresponding to the slider is changed, the slider used to interpret this as a new minima (or maxima). Now the bottom (or top) offset property is interpreted as a new range minima (or maxima).

Upgrade considerationLuciadFusion

ILcdGXYAsynchronousLayerWrapper and ILcdGXYAsynchronousPaintQueue have been extended with the methods invokeLaterOnGXYLayerInEDT and invokeLaterInEDT respectively. Wrappers for or extensions of the above interfaces or their implementations should delegate to this method.

Upgrade considerationLuciadFusion

The base class ALcdGXYPen no longer contains the fields and methods to cache world/model references and transformations, since these were used and updated inconsistently, in the end only creating overhead without serving a practical purpose.

Upgrade considerationLuciadFusion

The behavior of some methods of TLcdFeatureIndexedVectorModel and TLcdFeatureIndexedAnd2DboundsIndexedModel has been changed:

If an index was added for which one or more of the feature names did not occur in the featured descriptor, an IndexOutOfBoundsException was thrown, either when the index was added or when the first element was added to the model. No exceptions are thrown anymore; an empty index is created instead.
If retrieveIndex is called for a unique index, this method now returns a Vector containing the unique element that matches the query, instead of returning null.
If retrieveUniqueIndex is called for a non-unique index, an IllegalArgumentException is thrown now, instead of returning null.
If retrieveIndex or retrieveUniqueIndex is called for an index which was not created yet, an IllegalArgumentException is thrown now, instead of returning null.

Upgrade considerationLuciadFusion

Null values are now explicitly forbidden as elements in a model. This was already the case for most model implementations in the com.luciad.model package (except for TLcdVectorModel).

Upgrade considerationLuciadFusion

Some methods of ILcdModel and its implementations now throw better exceptions:

The addModelListener and removeModelListener now throw a NullPointerException if the argument is null. All implementations in the com.luciad.model package have been modified to be compliant with the new specification.
The editing methods of all non-editable models in the com.luciad.model package now throw an UnsupportedOperationException instead of an IllegalArgumentException.
TLcd2DBoundsIndexedModel, TLcd2DRegularTiledBoundsIndexedModel, TLcdSoft2DBoundsIndexedModel and TLcdTiled2DBoundsIndexedModel now always throw a NullPointerException if the applyOnInteract2DBounds method is called with a null function or bounds (this was not the case in previous versions, if the model was empty).

Upgrade considerationLuciadFusion

The specification of addElement, addElements, removeElement and removeElements in ILcdModel has been changed; implementations are no longer required to throw an IllegalArgumentException when an invalid element is added or removed. Instead, these methods now have a precondition (

    canAddElement(aElement)

) which should hold for the element(s) that is being added/removed. It is unspecified by default what happens if one of these methods is called while the precondition does not hold. All implementations of ILcdModel in com.luciad.model no longer call canAddElement or canRemoveElement from within the addElement(s)/removeElement(s) methods. Existing code that relies on the IllegalArgumentException exception being thrown:

      try {
      model.addElement(aElement, ILcdModel.FIRE_NOW);
      }
      catch(IllegalArgumentException e) {
      // Do something.
      }

should be refactored to:

      if (model.canAddElement(aElement)) {
      model.addElement(aElement, ILcdModel.FIRE_NOW);
      }
      else {
      // Do something.
      }

Developers using the add/remove filters, provided by some model implementations, should also make sure that each addElement call is always preceded by a canAddElement call, as these filters are no longer checked in the add/remove methods.

Upgrade considerationLuciadFusion

The GNU regular expressions library gnu-regexp-1.1.4.jar is no longer required by LuciadMap, as its use has been replaced by the regular expressions API available in the JDK (since 1.4). This might require an update to existing build scripts to create a LuciadMap application, as they now no longer need to incorporate this library.

Upgrade considerationLuciadFusion

LMAP-2569, LMAP-2608

A number of issues in the existing buffer domain object TLcdLonLatBuffer and corresponding painter TLcdGXYBufferPainter have been fixed in the new buffer implementation, by the introduction of a new geodetic implementation TLcdLonLatGeoBuffer and a new painter implementation TLcdGXYGeoBufferPainter. The following problems had been identified in the past and are fixed in the new implementation:

LMAP-2569: the fill of a buffer does not match with the contour for wide buffers,
LMAP-2608: a narrow buffer cannot be moved with TLcdGXYBufferPainter,
2446: TLcdLonLatBuffer does not handle degenerate cases,
2782: the line/fill style handling of TLcdGXYBufferPainter is inconsistent,
3682: sharp angles in the axis of a buffer are not handled correctly by TLcdLonLatBuffer and TLcdGXYBufferPainter,
4033: overlapping areas are not handled correctly by TLcdGXYBufferPainter,
4549,5421,5475: TLcdGXYBufferPainter does not allow to move a buffer if it is part of a composite selection but not touched,

To obtain the fixes, an upgrade is needed by replacing the use of TLcdLonLatBuffer and TLcdGXYBufferPainter with TLcdLonLatGeoBuffer and TLcdGXYGeoBufferPainter.

Upgrade considerationLuciadFusion

LMAP-2340

ALcdGXYSmartController#RequestFocusOnMouseEntered is now by default false.

Upgrade considerationLuciadFusion

LMAP-2600

ALcdGXYSmartController's default keyboard shortcuts for left and right panning have been reversed, in order to make them consistent with the panning behavior of the arrow keys.

Upgrade considerationLuciadFusion

LuciadMap now comes with two extra libraries: the JTS Java Topology Suite jts-1.8.jar and an extension lcd_jts_extension.jar. Both libraries are used by the com.luciad.shape.shape2D package (see Technical Notes -> Prerequisites). This might require an update to existing build scripts to create a LuciadMap application, to incorporate the new libraries.

Upgrade considerationLuciadFusion

LMAP-2526

ALcdGXYSmartController: in order to support undo-functionality for the panning and zooming operations resulting from key presses, several undo-related methods have been added to this class:

addUndoableListener
removeUndoableListener
fireUndoableEvent

If you have created a subclass of ALcdGXYSmartController and provided undo-capabilities for this subclass, you need to removed the corresponding methods from your subclass and use the methods mentioned above instead to register and unregister ILcdUndoableListeners and to fire TLcdUndoableEvents.

Bug fixLuciadFusion

LMAP-2680

TLcdColorMapCustomizer: now consumes the key events when stepping through the levels with the arrow keys, to avoid that anybody else can still use these key events.

ImprovementLuciadFusion

LMAP-2636

TLcdGXYSelectControllerModel2: MouseClickedSensitivity is now larger by default, to accommodate for larger icons.

ImprovementLuciadFusion

ImprovementLuciadFusion

The precision of encoding object features of type double using TLcdSHPModelEncoder has been increased to 18 characters (in string representation). Also, the TLcdSHPModelEncoder now supports features of type BigDecimal, with the same limit of 18 characters.

ImprovementLuciadFusion

TLcdCADRGDirectoryModelDecoder has a new boolean property readTableOfContentsFiles to specify whether A.TOC files should be read, whenever they are available.

Bug fixLuciadFusion

LMAP-2635

TLcdCADRGModelDecoder now ignores any erroneous high bits in the section location length field.

Bug fixLuciadFusion

LMAP-2630

TLcdColorMapCustomizer: using setGradientToggleable while the customizer is displayed on screen now properly refreshes the GUI.

Bug fixLuciadFusion

LMAP-2571

Because the WMS Server uses TLcdConcurrentBuffer instead of TLcdBuffer as internal shared buffer since V7, the buffer size configuration is no longer required. The configuration property 'shared.buffer.size.mb' in WEB-INF/classes/settings.cfg is therefore no longer used and has been removed in the sample deployment available in distrib/LuciadMapWMS_x.x.x.

ImprovementLuciadFusion

The WMS Server no longer explicitly depends on the Xerces XML parser, but now uses the package javax.xml.* available in JRE 1.4 and later - the WMS Server requires JRE 1.4 or later, see prerequisites. The sample build script available in build/wms therefore no longer integrate the libraries xercesImpl.jar and xmlParserAPIs.jar in a new build.

ImprovementLuciadFusion

LMAP-2539

The transformation of model bounds to world bounds has been made more efficient.

ImprovementLuciadFusion

TLcdOGCXPath now has an equals and a hashCode implementation.

Bug fixLuciadFusion

LMAP-2547

TLcdGXYOffsetIconPainter: snapping now works for the offset icon painter.

Bug fixLuciadFusion

LMAP-2541

The transformation of model bounds to world bounds now avoids discretisation problems in some corner cases that occur with Cassini and orthographic projections.

Bug fixLuciadFusion

LMAP-2248

TLcdISO19103Measure#convert did not update the supplied ILcdISO19103Measure object if the same unit of measure was given as the source unit of measure.

The advancedLineStyle sample has been reviewed and updated to illustrate three concepts in LuciadMap to render a line:

the painter TLcdGXYRoundedPointListPainter to draw point lists with rounded corners,
the stroke implementation TLcdGXYComplexStroke to draw Shape patterns repetitively along a path,
the painter TLcdGXYHaloPainter to add a halo effect to other ILcdGXYPainter implementations.

ImprovementLuciadFusion

A new painter TLcdGXYRoundedPointListPainter has been added to the API. It is an extension of TLcdGXYPointListPainter that allows to draw an ILcdPointList with rounded corners.

ImprovementLuciadFusion

The API documentation of the following classes has been reviewed and updated:

the interfaces ILcdGXYPainter and ILcdGXYEditor, and their principal implementations,
the interface ILcdGXYView, and its implementations,
ILcdGXYController and ILcdGXYLayer,
all implementations of ILcdModelDecoder in the package com.luciad.format.raster.

setOpaque(false)

and

setCachingMode(TLcdMapJPanelLightWeight.DISABLE_CACHING)

TLcdGXYPointListPainter now has method to check whether the current mouse location is inside the point list as if it were rendered as a polygon. This facilitates modifying the behavior of the isTouched method.

Bug fixLuciadFusion

LMAP-2295

TLcdGXYNewController and TLcdGXYEditController no longer highlight multiple snap targets. This was not very useful as it is only possible to choose one snap target.

ImprovementLuciadFusion

TLcdCompositeIcon now has an implementation for the equals and hashcode methods.

ImprovementLuciadFusion

TLcdGXYPainterFontStyle is a new ILcdGXYPainterStyle that sets a font and a color. It is typically useful for TLcdGXYTextPainter.

ImprovementLuciadFusion

To enable evaluating custom extensions or interpretations of an OGC filter, the following interfaces have been made available:

ILcdGenericExpression: container marker interface for any object that can be evaluated
ILcdEvaluator: evaluates expressions
ILcdEvaluatorFactory: creates evaluators for given generic expressions

And these changes have been applied to the API:

TLcdOGCFilterEvaluator: now has a method to create an evaluator factory that can be overwritten to return custom evaluator factories
ILcdEvaluatorFunction: the signature of the method apply has changed.

ImprovementLuciadFusion

com.luciad.view.map.multilevelgrid is a new package to support multilevel grids. A multilevel grid is a grid that has multiple levels of subdivisions. The classes are:

ILcdMultilevelGrid: models the grid,
TLcdMultilevelGridLayer: an ILcdGXYLayer capable of rendering a multilevel grid on an ILcdGXYView,
ILcdMultilevelGridCoordinate: models an object that covers an element of the grid at any of the levels of the grid,
TLcdMultilevelGridUtil: a utility class to convert locations expressed in the reference on which the grid is based to and from multilevel grid coordinates,
ALcdMultilevelGridCoordinateFormat: parses and formats multilevel grid coordinates,
TLcdMultilevelGridCoordinateModel: takes into account the structure of a multilevel grid to contain multilevel grid coordinates.

Two samples demonstrate how this grid can be used to model and display a CGRS and a GARS grid.

ImprovementLuciadFusion

LuciadMap now supports editable labels that can be freely placed. To this end several interfaces were extended.

These changes mostly affect the com.luciad.view.gxy and com.luciad.view.gxy.controller package. Following interfaces have been extended:

ILcdGXYLabelPainter has been extended by ILcdGXYLabelPainter2. It provides extra methods to influence the label position, and allows for free placement of the labels.
ILcdGXYLayer has been extended by ILcdGXYEditableLabelsLayer. It provides access to the locations of the labels as they were drawn through the getLabelLocations method.

ALcdOGCWMSDimension: represents a dimension definition.
TLcdOGCWMSDimensionExtent: represents a set of values or intervals for a dimension.

To include one or more dimensional parameters in a request, TLcdOGCWMSDimensionWrapper objects must be registered on the active ALcdWMSProxy. A TLcdOGCWMSDimensionWrapper holds a reference to a dimension definition (modeled by ALcdOGCWMSDimension) and the value(s)/interval(s) to be used (modeled by TLcdOGCWMSDimensionExtent). To configure dimensions on a ALcdWMSProxy, the following methods have been introduced:

addDimension(ALcdOGCWMSDimension)
getDimensionCount()
getDimension(int)
removeDimension(int)
clearDimensions()

ImprovementLuciadFusion

Support has been added to handle multi-dimensional data in the WMS server, as defined by Annex C of the OpenGIS OGC 06-042 Web Map Server Implementation Specification.

To define a dimension for a layer, the classes ALcdWMSDimension, TLcdWMSDimension and TLcdWMSDimensionExtent have been introduced. ALcdWMSDimension and TLcdWMSDimension represent a dimensional parameter, while TLcdWMSDimensionExtent is used to model the available values for a dimension. The classes ALcdWMSLayer and TLcdWMSLayer have been extended with methods to configure these elements.

For convenience, the sample XML configuration format to configure the capabilities of a server has been extended with support for dimensions. The decoders for this format, com.luciad.wms.server.config.xml.TLcdWMSCapabilitiesXMLDecoder and samples.wms.server.config.xml.WMSCapabilitiesXMLDecoder, both recognize the XML element 'Dimension' and its contents.

TLcdEPSGReferenceParser now has support for more EPSG codes. It now supports:

references based on a geodetic datum with a meridian shift,
geodetic references of which the name is unknown but for which the transformation parameters to WGS84 are known,
geodetic references for which the names was not recognized, but one of the aliases for the name is.

The complete list of supported coordinate references is available from the API documentation of the TLcdEPSGReferenceParser class. To take advantage of this enhancement the lcd_epsg_resources.jar of this release should be put in the classpath.

ImprovementLuciadFusion

The class com.luciad.wms.client.model.ALcdOGCWMSCapabilities has been extended with three new methods to retrieve extra information about the capabilities of an SLD-enabled Web Map Service:

getDescribeLayerURL(): returns the URL prefix that must be used for DescribeLayer requests.
getGetLegendGraphicURL(): returns the URL prefix that must be used for GetLegendGraphic requests.
getSupportedLegendGraphicFormatCount(): returns the number of supported legend graphic formats by a Web Map Service.
getSupportedLegendGraphicFormat(int): returns the supported legend graphic format at a given index.

TLcdGridReference has a new property name to identify the reference using a textual representation.

Bug fixLuciadFusion

The equals method in TLcdGeodeticDatum now always checks whether the 8 parameters are exactly equal. Previously name equality sufficed to return true.

Upgrade considerationLuciadFusion

Where possible, the cloneAs...() methods in the classes contained in the packages com.luciad.shape.shape2D and com.luciad.shape.shape3D now rely on the clone() method. This will only influence code that (erroneously) assumes a specific type for the returned object, for example, it assumes that TLcdLonLatHeightBounds.cloneAs2DEditableBounds() returns a TLcdLonLatBounds object. The following methods have been updated:

TLcdLonLatBounds.cloneAs2DEditableBounds()
TLcdLonLatFloatBounds.cloneAs2DEditableBounds()
TLcdXYBounds.cloneAs2DEditableBounds()
TLcdXYFloatBounds..cloneAs2DEditableBounds()
TLcdLonLatPoint.cloneAs2DEditablePoint()
TLcdLonLatFloatPoint.cloneAs2DEditablePoint()
TLcdLonLatZonalPoint.cloneAs2DEditablePoint()
TLcdXYPoint.cloneAs2DEditablePoint()
TLcdXYFloatPoint.cloneAs2DEditablePoint()
TLcdLonLatHeightBounds.cloneAs2DEditableBounds()
TLcdLonLatHeightBounds.cloneAs3DEditableBounds()
TLcdXYZBounds.cloneAs2DEditableBounds()
TLcdXYZBounds.cloneAs3DEditableBounds()
TLcdXYZFloatBounds.cloneAs2DEditableBounds()
TLcdXYZFloatBounds.cloneAs3DEditableBounds()
TLcdLonLatHeightPoint.cloneAs2DEditablePoint()
TLcdLonLatHeightPoint.cloneAs3DEditablePoint()
TLcdXYZPoint.cloneAs2DEditablePoint()
TLcdXYZPoint.cloneAs3DEditablePoint()
TLcdXYZFloatPoint.cloneAs2DEditablePoint()
TLcdXYZFloatPoint.cloneAs3DEditablePoint()

Upgrade considerationLuciadFusion

The constructors of TLcdXMLSchema, TLcdXMLSchemaElement, TLcdXMLSchemaType and TLcdXMLSchemaAttribute have changed slightly; all schema elements, types and attributes now keep a reference to their schema, while the schema itself keeps a reference to its schema provider.

Upgrade considerationLuciadFusion

ALcdPoint no longer extends ALcdBounds, instead it extends ALcdShape and implements the interface ILcdBounds. This will only influence code that relies explicitly on ALcdBounds. As ALcdBounds does not expose any methods besides methods defined by ILcdBounds, the ALcdBounds occurrences can be replaced by ILcdBounds.

Upgrade considerationLuciadFusion

Some TLcdXMLName constants in the TLcdXMLSchemaConstants class which were accidentally made public, are removed from the API again.

Upgrade considerationLuciadFusion

ILcdWFSFeatureType has been extended to contain a list of TLcdWFSMetadataURLs. This list was previously only included in TLcdWFSFeatureType, but is now included in the interface as well and must therefore be added to all implementations. The metadata URLs are not mandatory, however, so implementations of the new methods may be empty if they are not needed.

Upgrade considerationLuciadFusion

TLcdAdvancedMapRulerController: the methods get/setGXYEditController and get/setGXYNewController now accept an argument of type ILcdGXYController instead of TLcdGXYEditController and TLcdGXYNewController respectively. This allows to use TLcdGXYEditController2 in combination with the ruler, and in general allows for greater flexibility.

Upgrade considerationLuciadFusion

TLcdGXYLayer now implements ILcdGXYEditableLabelsLayer as well as ILcdGXYLayer. If you used to delegate to a TLcdGXYLayer instance in your own implementation of ILcdGXYLayer, you need to delegate the extra methods defined in ILcdGXYEditableLabelsLayer as well if you want to enable the editable labels functionality.

Upgrade considerationLuciadFusion

The interfaces ILcdRemoteOWSModelDecoder and ILcdRemoteOWSModelProvider have been updated to enable implementations to return an ILcdModel array instead of a single ILcdModel:

ILcdRemoteOWSModelDecoder.decode(): the return type is now ILcdModel[] instead of ILcdModel
ILcdRemoteOWSModelProvider.getModel(): the return type is now ILcdModel[] instead of ILcdModel

This is done to support Styled Layer Descriptors that combine multiple coverages (WCS) or feature types (WFS) into one user-defined layer. Implementations can decode each coverage or feature type into a single ILcdModel. This is especially needed when these coverages or feature types use different model references, since an ILcdModel can only have one model reference.

The abstract class ALcdSLDWMSGXYLayerFactory has been adapted accordingly: the signature of the method

abstract public ILcdGXYLayer createGXYLayer( ILcdModel, TLcdSLDUserLayer, TLcdSLDFeatureTypeStyle[] );

has changed into

abstract public ILcdGXYLayer[] createGXYLayer( ILcdModel[], TLcdSLDUserLayer, TLcdSLDFeatureTypeStyle[] );

to allow implementations to create an ILcdGXYLayer for each decoded ILcdModel that is part of a user-defined layer.

Upgrade considerationLuciadFusion

As stated in the enhancements section, LuciadMap now supports freely placeable labels. In order for your projects to take full advantage of this feature, several guidelines must be followed.

All classes that use any of the methods in ILcdGXYLabelPainter should be made aware that these label painters could also implement ILcdGXYLabelPainter2. If these label painters also implement ILcdGXYLabelPainter2, the Object and the TLcdLabelLocation must be set instead of the Object and the location index.

All classes that paint labels should inform the ALcdLabelLocations which labels have been painted. For instance implementations of ILcdGXYLayer, ILcdGXYLayerLabelPainter and ILcdGXYViewLabelPainter paint labels, and as such have to inform these ALcdLabelLocations.
Please refer to the reference documentation of ILcdGXYEditableLabelsLayer, ILcdGXYLabelPainter2 and ALcdLabelLocations for more detailed information.

If these guidelines are not followed, your application will behave as if there are no editable labels.

Upgrade considerationLuciadFusion

The implementations of ILcdModel have been improved for concurrent access from multiple threads. Their levels of thread-safety are documented in the API documentation. Notably, TLcd2DBoundsIndexedModel now allows concurrent read-only access. The method applyOnInteracts2D is no longer explicitly synchronized, allowing multiple threads to access the model concurrently. This change may be incompatible if any code explicitly or implicitly relies on this synchronization. If so, one can set system properties that are defined in the API documentation to revert to the old behavior. Concurrent read-write access is still only possible with external synchronization. Please consult the developer guide for more details.

Upgrade considerationLuciadFusion

The implementations of ILcdShape - except for all *Float* classes - in com.luciad.shape, com.luciad.shape.shape2D and com.luciad.shape.shape3D have received consistent implementations of the methods clone, equals, hashCode, and toString.

Notably, the method clone now always delegates to the method super.clone, which ensures that a class of the proper type is created, even for extensions. The behavior of clone is kept as much the same as before as possible, especially regarding the choice between a deep clone and shallow clone. The javadoc of the clone method in the updated ILcdShape implementations can be consulted for the exact clone behavior.

The methods equals and hashCode now always compare the classes and the properties of the shapes (like coordinates, radius, height, etc).

As with any class that implements equals and hashcode based on object properties, the implications may catch unsuspecting developers by surprise. A common example is a point that is put in a hash table. If its coordinates are changed after it has been put in the hash table, its identity and, more specifically, its hash code changes. It then becomes impossible to retrieve the point based on its hash code. This usually leads to NullPointerExceptions, as null is returned instead of the object. Another example is points only being equal if their classes are equal. A final example is the confusion caused by extensions of the basic shape implementations that do not properly override the identity methods. Overriding implementations should always delegate to their super versions, adding any necessary code for additional properties. The new implementations in LuciadMap may be incompatible with existing code if the code explicitly or implicitly relies on the previous imperfect implementations.

Upgrade considerationLuciadFusion

The interface ILcdWMSHttpServletRequestFileNameResolver has been removed, due to its limited practical relevance. The two implementations TLcdWMSServiceExceptionDTDDefaultFileNameResolver and TLcdWMSCapabilitiesDTDDefaultFileNameResolver have been removed accordingly.

Four methods in TLcdOGCWMSCommandDispatcher that were used to set or retrieve an instance of ILcdWMSHttpServletRequestFileNameResolver to resolve the WMS 1.1.1 Capabilities DTD or Service Exception DTD have been removed also:

ILcdWMSHttpServletRequestFileNameResolver getWMSCapabilitiesDTDFileNameResolver()
setWMSCapabilitiesDTDFileNameResolver(ILcdWMSHttpServletRequestFileNameResolver)
ILcdWMSHttpServletRequestFileNameResolver getWMSExceptionDTDFileNameResolver()
setWMSExceptionDTDFileNameResolver(ILcdWMSHttpServletRequestFileNameResolver)

Upgrade considerationLuciadFusion

A new class com.luciad.wms.server.TLcdWMSRequestContext has been introduced that holds information about a current request. A number of interfaces in the package com.luciad.wms.server have been adapted to include this class as a parameter in its methods:

ILcdRemoteOWSModelDecoder.canDecode(): replaced HttpServletRequest parameter with TLcdWMSRequestContext parameter
ILcdRemoteOWSModelDecoder.decode(): replaced HttpServletRequest parameter with TLcdWMSRequestContext parameter
ILcdRemoteOWSModelDecoderFactory.createModelDecoder(): replaced HttpServletRequest parameter with TLcdWMSRequestContext parameter
ILcdRemoteOWSModelProvider.getModel(): replaced HttpServletRequest parameter with TLcdWMSRequestContext parameter

Existing implementations just need to update the signature of these methods and can choose whether to use the additional parameter.

iButton USB support has been extended to Mac OS X. The iButton is now supported on the following platforms:

serial adapter: Windows XP/NT/2000, Linux, Solaris
USB adapter: Windows XP/2000, Linux, Mac OS X

ImprovementLuciadFusion

Support has been added for the layer attribute 'opaque'. This is a property defined by the WMS specification that allows to indicate that a layer represents an area-filling coverage. The following changes have been made to support this property:

ALcdWMSLayer has been extended with a method isOpaque() and TLcdWMSLayer has been extended with a method setOpaque(Boolean). The configured value is automatically taken into account while sending the capabilities to the client (see below).
The WMS server configuration decoders, com.luciad.wms.server.config.xml.TLcdWMSCapabilitiesXMLDecoder and samples.wms.server.config.xml.WMSCapabilitiesXMLDecoder, both recognize the XML attribute 'opaque="true|false"' for the XML element 'Layer'.

TLcdOGCWMSProxyModelDecoder.decode(String): uses the GetCapabilities request to retrieve the capabilities of the server.
ALcdWMSProxy.createImageInputStream(int, int, ILcdXYWorldReference, ILcdBounds, Color): uses the GetMap request to retrieve a map.

ImprovementLuciadFusion

To provide better support for dynamic WMS server implementations, a number of enhancements haven been implemented:

A new interface com.luciad.wms.server.ILcdWMSCapabilitiesUpdater has been introduced which can be used to implement an update strategy for the WMS server. This interface contains one method update(HttpServletRequest), which will be invoked for each incoming request. To register an implementation on the WMS, the new factory method createWMSCapabilitiesUpdater(ServletConfig, TLcdOGCWMSCommandDispatcher, ILcdWMSCapabilitiesDecoder) in ALcdOGCWMSCommandDispatcherFactory must be implemented.
A new factory method createModelProvider() has been introduced in ALcdOGCWMSCommandDispatcherFactory, which returns an ILcdModelProvider. In the past, an ILcdModelProvider was created internally and set on the command dispatcher, which made it more difficult to insert a custom ILcdModelProvider implementation.
The WMS server sample has been extended with a sample implementation of ILcdWMSCapabilitiesUpdater.
The implementation of TLcdOGCWMSCommandDispatcher has been improved in the context of a dynamic WMS:
- Extra measures have been taken to prevent any inconsistencies while updating the server at runtime.
- The getWMSCapabilities(HttpServletRequest) will now always return the same ALcdWMSCapabilities object for the same HttpServletRequest object.

The interface ILcdXMLElementAdapter has been extended with extra methods for visiting an XML element; an XML element can now be inspected by passing an ILcdXMLElementVisitor to the adapter, which will call the visitor for each attribute/content/child element of the XML element being visited.
The abstract classes ALcdXMLElementAdapter and ALcdXMLTypedElementAdapter have been removed. They have been replaced by 4 new classes:
- ALcdXMLIndexBasedElementAdapter
- ALcdXMLTypedIndexBasedElementAdapter
- ALcdXMLVisitorBasedElementAdapter
- ALcdXMLTypedVisitorBasedElementAdapter
The first two adapters replace the old adapters; extensions of these classes should override the index-based methods (getXXX(index) and getXXXCount()); the visitXXX() methods of these adapters delegate to the index-based methods. The other two adapters work in the opposite direction: extensions of these classes should override the visitor-based methods, and the index-based methods of these adapters delegate to the visitor-based ones. All existing adapter implementations should rename their super class from ALcdXML(Typed)ElementAdapter to ALcdXML(Typed)IndexBasedElementAdapter. New implementations of ILcdXMLElementAdapter should preferably extend one of the two visitor-based adapter classes, since these are easier to implement, less error-prone and more efficient. All existing adapters, available in the LuciadMap API, have beed adjusted to these changes.
New editable interfaces have been added for name and object stacks, ILcdXMLEditableNameStack and ILcdXMLEditableObjectStack. The default implementations, TLcdXMLNameStack and TLcdXMLObjectStack, have been updated to implement these interfaces.
A default implementation of ILcdXMLDocumentContext, TLcdXMLDocumentContext, has been made available in the API. Interface and implementation have additional startElement() and endElement() methods to control the XML stack depth.
A new Exception class has been introduced, TLcdXMLInterruptedException, which can be used to interrupt a running XML call.
The method signatures of several classes have been harmonized:
- ILcdXMLElementAdapterAdapter.getAdapterForObject
- ILcdXMLElementNameProvider.getElementNameForObject
- ILcdXMLElementAdapter.getName
They now all take as arguments a name and object stack, pointing to the parent XML name/object, and an additional name and object, identifying the XML name/object to be inspected/handled.
The order in which element name provider and element adapter provider are called by the XML encoder has been changed. The element name provider is no longer called directly by the encoder; all XML element names are retrieved now using the ILcdXMLElementAdapter.getName() method, even that of the root object. This implies that element adapter providers should be able to return element adapters for objects, without knowing the exact XML name. The setElementNameProvider() and getElementNameProvider() methods of the TLcdXMLEncoder class have been deprecated.
The ILcdXMLElementNameProvider.getElementNameForObject() method now has an additional TLcdXMLName argument, indicating the XML type to which the returned element name should belong.
XML element adapter libraries have been removed from the API. Composite adapter providers should now be constructed using the new TLcdXMLCompositeElementAdapterProvider class. Basic adapter providers for GML3, SLD, and so on, can be registered with a composite adapter provider, to create one large element adapter provider.

Bug fixLuciadFusion

The UTM grid now takes into account that the zones 31 through 37 are not uniform on the northern hemisphere.

Upgrade considerationLuciadFusion

TLcdUTMZonePainter now only paints one hemisphere of a zone. This is due to the fact that the reference for the northern hemisphere and for the southern hemisphere within a zone are different.

Bug fixLuciadFusion

TLcdXMLEncoder now also escapes attribute values (before, only content was escaped).

ImprovementLuciadFusion

The following methods have been introduced in com.luciad.ogc.sld.xml.TLcdSLDFeatureTypeStyleEncoder10:

setPrefixMap(ILcdPrefixMap), getPrefixMap(): allows to control the mapping between the fully qualified namespaces and their corresponding prefixes in the resulting XML document.
setDefaultNamespace(String), getDefaultNamespace(): allows to set the default namespace in the resulting XML document. This is the namespace for which no prefix will be used.

ImprovementLuciadFusion

The following methods have been introduced in com.luciad.wms.sld.xml.TLcdSLDStyledLayerDescriptorEncoder10:

setPrefixMap(ILcdPrefixMap), getPrefixMap(): allows to control the mapping between the fully qualified namespaces and their corresponding prefixes in the resulting XML document.
setDefaultNamespace(String), getDefaultNamespace(): allows to set the default namespace in the resulting XML document. This is the namespace for which no prefix will be used.

Bug fixLuciadFusion

Several painters no longer supported snapping when creating a new object. These painters now also accept snap targets when the objects they are editing are in an 'initial' state:

TLcdGXYBoundsPainter: when the bounds has width and height 0,
TLcdGXYArcPainter: when the A and B of the ellipse the arc is part of is 0,
TLcdGXYArcBandPainter: when the minimum and maximum radius of the arcband are 0,
TLcdGXYEllipsePainter: when the A and B of the ellipse are 0.

com.luciad.ogc.filter.model: contains the domain model to represent OGC filters and expressions
com.luciad.ogc.filter.model.capabilities: contains the domain model to represent OGC filter capabilities
com.luciad.ogc.filter.xml: contains XML decoding and encoding facilities for OGC filters and filter capabilities. These facilities are built upon the general LuciadMap XML framework.
com.luciad.ogc.filter.xml.capabilities: contains XML decoding and encoding facilities for OGC filter capabilities. These facilities are built upon the general LuciadMap XML framework.
com.luciad.ogc.filter.evaluator: contains the implementation of the OGC Filter Evaluator. The OGC Filter Evaluator allows you to build an ILcdFilter that can be used for accepting or rejecting a given object or to build an ILcdPropertyRetriever than can be used for computing a property of a given object
com.luciad.ogc.filter.spatial: contains the implementation of the OGC Filter Spatial Evaluator that provides the ability to perform advanced spatial filtering

com.luciad.wms.server.ALcdOGCSLDWMSCommandDispatcherFactory: this abstract class is an extension of the regular ALcdOGCWMSCommandDispatcherFactory that adds support for Styled Layer Descriptors. This class must be implemented by the user to create an SLD capable WMS server. The class samples.wms.server.OGCWMSCommandDispatcherFactory in the samples illustrates an example implementation.
com.luciad.wms.server.TLcdOGCSLDWMSCommandDispatcher: this class is an extension of the regular TLcdOGCWMSCommandDispatcher that adds support for Styled Layer Descriptors. This class must be used to handle WMS requests in an SLD capable WMS server. The class ALcdOGCSLDWMSCommandDispatcherFactory automatically registers an object of TLcdOGCSLDWMSCommandDispatcher on the servlet to handle all incoming requests.
com.luciad.wms.server.ALcdSLDWMSGXYLayerFactory: this abstract class is an implementation of ILcdWMSGXYLayerFactory, that is used by the server to create ILcdGXYLayer instances for all ILcdModels, with or without an SLD model. Implementations can be registered on the WMS server by implementing the method ALcdOGCSLDWMSCommandDispatcherFactory.createSLDWMSGXYLayerFactories(). This method replaces the previously used factory method createWMSGXYLayerFactories(), which is now declared final.
com.luciad.wms.server.ILcdRemoteOWSModelDecoder, ILcdRemoteOWSModelDecoderFactory, ILcdRemoteOWSModelProvider: these interfaces are used in the WMS server to decode ILcdModel objects based on remote data (typically located on a remote WFS or WCS server). Through the method ALcdOGCSLDWMSCommandDispatcherFactory.createRemoteOWSModelDecoderFactories(), the user can register one or more ILcdRemoteOWSModelDecoderFactory objects on the WMS server. By default, this method returns null, as this is an optional feature according to the SLD specification..
com.luciad.wms.sld.model: contains the domain model for Styled Layer Descriptors. This domain model builts upon the Feature Type Style domain model that is available in the package com.luciad.ogc.sld.model.
com.luciad.wms.sld.xml: contains an XML decoder and encoder for Styled Layer Descriptors. Both the decoder and encoder respectively built upon the Feature Type Style decoder and encoder that are available in the package com.luciad.ogc.sld.xml.

To inform a client about the SLD support of the WMS server, TLcdOGCSLDWMSCommandDispacher uses the XML capabilities document that is sent to the client after a GetCapabilities request:

for version 1.1.1 and earlier, the XML capabilities document includes the XML element UserDefinedSymbolization, which is defined by the OpenGIS WMS 1.1.1 Capabilities DTD (see http://schemas.opengis.net/wms/1.1.1/WMS_MS_Capabilities.dtd). This element contains some attributes that indicate the SLD support.
for version 1.3.0, the OpenGIS WMS 1.3.0 Capabilities XML Schema does not include an SLD related XML element. Therefore, a custom LuciadMap WMS 1.3.0 Capabilities XML Schema is available (see build/wms/resources/schemas/wms/1.3.0/sld_capabilities_1_3_0.xsd), which extends the OpenGIS WMS 1.3.0 Capabilities Schema (see http://schemas.opengis.net/wms/1.3.0/capabilities_1_3_0.xsd). This extension adds the element UserDefinedSymbolization to the default schema, which was present in the OpenGIS WMS 1.1.1 Capabilities DTD.

ImprovementLuciadFusion

A new package, com.luciad.ogc.sld, was added. It contains an API and implementation for decoding, encoding and representation of OpenGIS SLD Feature Type Styles. The API is based on the OGC 02-070 Styled Layer Descriptor Implementation Specification, version 1.0. This specification allows user-defined symbolization of feature data, by determining which features or layers are rendered with which colors or symbols. The package com.luciad.ogc.sld contains the following subpackages:

com.luciad.ogc.sld.model: contains the domain model to represent Feature Type Styles.
com.luciad.ogc.sld.view.gxy: contains the GXY view representation of the Feature Type Style model applied to ILcdModel objects. The classes in this package enable conversion of a Feature Type Style model/ILcdModel combination into ILcdGXYPainter and ILcdGXYLayer instances which can be used in an ILcdGXYView.
com.luciad.ogc.sld.xml: contains an XML decoder and encoder for Feature Type Styles. The decoder and encoder are built upon the general LuciadMap XML framework.

Upgrade considerationLuciadFusion

ILcdWFSClientModelEncoderFactory:

The method createModelSchemaEncoder() has been added. This method shall return an ILcdWFSModelSchemaEncoder, which is responsible for encoding the result of a DescribeFeatureType request. The class TLcdWFSClientModelEncoderFactory can produce encoders for standard GML application schemas.
Both createModelSchemaEncoder() and createModelEncoder() have an argument of type ILcdWFSRequestContext, which contains context information about the request currently being handled.

Upgrade considerationLuciadFusion

ALcdOGCWFSCommandDispatcherFactory:

The registerFilterFactories() has been removed, as it is no longer applicable. Applications that require customized filtering behaviour may override the createFilteredModelFactory() method to return an extension of the new class TLcdWFSFilteredModelFactory. This class provides a hook similar to registerFilterFactories() to allow filtering customization. Please consult the reference documentation for details.
The class TLcdWFSClientModelEncoderFactory was made available as the default implementation of ILcdWFSClientModelEncoderFactory. This factory supports GML2 and GML3 output formats, and may be extended by applications that wish to add additional output formats. GML output will not be available unless the model encoder factory advertises it.

ImprovementLuciadFusion

TLcdGML3ModelDecoder now supports the gml:ArcByCenterPoint and gml:CircleByCenterPoint elements. TLcdGML3ModelEncoder supports the encoding of ILcdArc and ILcdCircle objects to these GML elements.

ImprovementLuciadFusion

The class com.luciad.wms.client.model.TLcdOGCWMSProxyModelDecoder has been extended with three new methods to control the XML validation and the reference to external entities in a WMS capabilities document.

setValidating(boolean), isValidating(): specifies whether XML validation (DTD and XML Schema) is enabled for the WMS capabilities document provided by a server.
setEntityLocation(String aEntityID, URL aEntityLocation): sets the URL to be used for an entity defined in the WMS capabilities document provided by a server. A typical example of an entity definition in an XML document is a reference to a DTD or XML Schema. By using this method, one can replace such a reference with a reference to a locally stored copy of the DTD or XML Schema. If no locations are specified, the original entity locations defined in the XML document are used.

ImprovementLuciadFusion

The class com.luciad.wms.client.model.ALcdOGCWMSCapabilities has been extended with three new methods to retrieve extra information about the capabilities of a Web Map Service:

getGetFeatureInfoURL(): returns the URL prefix that must be used for GetFeatureInfo requests.
getSupportedFeatureInfoFormatCount(): returns the number of supported feature info formats by a Web Map Service.
getSupportedFeatureInfoFormat(int): returns the supported feature info format at a given index.

ImprovementLuciadFusion

The documentation now contains prerequisites for every Additional Component and Industry Specific Component. The prerequisites contain dependencies on

other LuciadMap specialized packages,
third party jars,
JDK versions,
operating systems.

ImprovementLuciadFusion

      setXYWorldReference( ILcdXYWorldReference aXYWorldReference, boolean aRepaint, boolean
      aAdjusting);

The method with aAdjusting parameter was missing from the interface. It has been added to be consistent with setViewOrigin, setWorldOrigin and setScale.

Upgrade considerationLuciadFusion

ILcd2DEditablePointFactory and ILcd3DEditablePointFactory and their implementations TLcdLonLatPointFactory and TLcdXYPointFactory, and TLcdLonLatHeightPointFactory and TLcdXYZPointFactory, have been removed. The factories were used in TLcd2DEditablePointList/TLcd3DEditablePointList to create new ILcdPoint from coordinates given and could be set with a static method. TLcd2/3DEditablePointList has a protected method create2/3DEditablePoint which by default returns a TLcdXY(Z)Point. This method should be overwritten to simulate setting another ILcd2DEditablePointFactory. In the LuciadMap API this is done in the ALcd2/3DEditablePolyPoint. The extension TLcdLonLatPolypoint (and its extensions TLcdLonLat(Height)Polygon and TLcdLonLat(Height)Polyline) has been adapted to create TLcdLonLat((Height)Point objects on insertion of new points through the coordinates. Since this was the only use of the ILcd2/3DEditablePointFactory in the LuciadMap API, and all extensions of ALcd2/3DEditablePolyPoint have a constructor with an ILcd2/3DEditablePointList parameter, adapting your code consists of constructing the ALcd2DEditablePolyPoint with a TLcd2DEditablePointList that returns the same ILcd2DEditablePoint as your factory would. An example for LonLatPolygons is

      private class MyLonLatPointFactory implements ILcd2DEditablePointFactory {

      public ILcd2DEditablePoint create2DEditablePoint(double aX, double aY) {
      return new MyLonLatPoint( aX, aY );
      }
      }

      TLcd2DEditablePointList.set2DEditablePointFactory(new MyLonLatPointFactory());

      TLcdLonLatPolygon polygon = new TLcdLonLatPolygon();

becomes

      private class MyLonLatPointList extends TLcd2DEditablePointList {

      protected ILcd2DEditablePoint create2DEditablePoint(double aX, double aY) {
      return new MyLonLatPoint( aX, aY );
      }
      }

      TLcdLonLatPolygon polygon = new TLcdLonLatPolygon(new MyLonLatPointList());

This fix alleviates the user of having to set the point factory for the LuciadMap implementations, which could result in the TLcdLonLatPolygon containing TLcdXYPoint objects, for example.

Upgrade considerationLuciadFusion

ILcdGXYView has a missing method added. All properties except XYWorldReference influencing the 'position' of the view (scale, viewOrigin, worldOrigin) could be set using a method with 3 parameters, the property, a boolean indicating whether the view should be repainted and a boolean indicating whether other property changes would follow.

Upgrade considerationLuciadFusion

LuciadMap packaging has changed slightly:

The distribution will now unzip to LuciadMap_X.Y.Z, where X.Y.Z are the major, minor and patch number of the release.
The LuciadMap beans jar, lcd_beans.jar is no longer packaged in a separate zip file. It is now located in the lib directory in LuciadMap zip.
Third party jars no longer have prefixes prepended to designate their use in LuciadMap, for example raster_jai_core.jar is now jai_core.jar. The use of third party jars is now documented in the prerequisites pages of the HTML documentation (Technical Notes -> Prerequisites).

Bug fixLuciadFusion

Some ILcdGXYPainter implementations did not fire property change events consistently when a property was set. This is now adapted for the following properties:

ALcdGXYPainter: displayName,
TLcdGXYArcBandPainter: createCounterClockwise, drawCenterWhenSelected, mode, paintCache
TLcdGXYArcPainter: drawCenter, drawCenterWhenSelected, paintCache, snapIcon,
TLcdGXYAreaShapeListPainter: defaultColor, selectionColor,
TLcdGXYBoundsPainter: paintCache, snapIcon,
TLcdGXYBufferPainter: creationBufferWidth, mode, paintCache, snapIcon
TLcdGXYCirclePainter: displayCenter, displayCenterOnSelection, distanceFormat, editingLabel, editingLabelBackground, editingLabelFilled, editingLabelFont, editingLabelForeground, editingLabelFrame, mode, paintCache, pointFormat, snapIcon
TLcdGXYEllipsePainter: drawCenter, mode, paintCache, snapIcon,
TLcdGXYIconPainter: icon, selectionIcon, snapIcon,
TLcdGXYLonLatHeightBufferPainter: creationBufferWidth, mode, paintCache,
TLcdGXYPointListPainter: fillSelection, mode, moveOnlyOnEdit, paintCache, snapIcon,
TLcdGXYPointShapeListPainter: defaultIcon, selectionIcon,
TLcdGXYPolylineShapeListPainter: defaultColor, paintCache, selectionColor,
TLcdGXYShapeListPainter: editTouchedOnly, shapeGXYPainterProvider, shapeGXYEditorProvider
TLcdGXYTextPainter: creationMode, framed.

ILcdISO19103CodeList: an extendable list of constants.
ILcdISO19103Code: an element of a code list.
ILcdISO19103UnitOfMeasure: a general definition of units for measurements.
ILcdISO19103Measure: a general definition of a measurement.
ILcdISO19103Record: an interface for a dictionary, where values are referred to by String keys.
TLcdISO19103MeasureTypeCode: codes for types of measurement.

com.luciad.format.magneticnorth.TLcdIGRFModelDecoder: com.luciad.format.magneticnorth.TLcdIGRFModelDescriptor
com.luciad.format.magneticnorth.TLcdWMMModelDecoder: com.luciad.format.magneticnorth.TLcdWMMModelDescriptor

com.luciad.util.TLcdLonLatCoord has its precision doubled when parsing a longitude or latitude string.

Upgrade considerationLuciadFusion

com.luciad.view.gxy.painter.TLcdGXYPointListPainter edits the point list by translating the whole point list (translate2D) instead of by moving the list one point at a time (translate2DPoint).

Bug fixLuciadFusion

Some decoders did not close all opened inputstreams:

com.luciad.format.svg.TLcdSVGModelDecoder
com.luciad.reference.TLcdModelReferenceDecoder

srs.epsg.cfg has become crs.epsg.cfg
srs.auto.cfg has become crs.auto.cfg
crs.auto2.cfg has been added for the additional AUTO2 namespace of WMS 1.3.0

com.luciad.shape.shape3D.TLcdXYZPolygon
com.luciad.shape.shape3D.TLcdXYZPolyline
com.luciad.shape.shape3D.TLcdXYZPolypoint

com.luciad.format.shp.TLcdSHPModelReferenceDecoder, TLcdSHPPointZ, TLcdSHPPointM
com.luciad.geometry.cartesian.TLcdXYZRotation.java
com.luciad.projection.ALcd* and TLcd*

support for southern hemisphere UTM references and UPS references on the poles.
improved detection of ASRP versions.
handling of more than 256 colors.

ILcdSVGModelDescriptorFactory creates model descriptors that take into account attributes of the root element of an SVG file.
the name of the root element and the grouping element can be retrieved as properties of the decoder.
the model encoder takes the model into account when writing the file header.

TLcdGXYArcPainter
TLcdGXYBoundsPainter
TLcdGXYBufferPainter
TLcdGXYCirclePainter
TLcdGXYEllipsePainter
TLcdGXYLonLatHeightBufferPainter
TLcdGXYPointListPainter

Bug fixLuciadFusion

com.luciad.format.shp.TLcdSHPModelDecoder splits up numerical feature values, based on their type:

F: Float
B: Double
I : Integer
N : Double/Integer (when the number of decimals is 0, an Integer is returned)

ImprovementLuciadFusion

com.luciad.shape.shape3D contains new com.luciad.shape.ILcdShape implementations to model 3D objects:

TLcdLonLatHeightSphere
TLcdLonLatHeightDome
TLcdLonLatHeightBuffer
TLcdLonLatHeightPolyline
TLcdLonLatHeightPolypoint

ImprovementLuciadFusion

com.luciad.text.TLcdAltitudeFormat has the property userUnit renamed to displayUnit.

ImprovementLuciadFusion

com.luciad.transformation.TLcdGrid2Grid implements the equals method.

ImprovementLuciadFusion

com.luciad.util.ILcdContentDescriptor is deprecated in favor of com.luciad.util.ILcdClassContentDescriptor.

ImprovementLuciadFusion

com.luciad.util.ILcdPointFunction is an interface for a function that can be applied to a point.

ImprovementLuciadFusion

com.luciad.util.TLcdAltitudeUnit has his units renamed:

METRE_UNIT becomes METRE_AMSL
KM_UNIT becomes KM_AMSL
FT_UNIT becomes FEET_AMSL

ImprovementLuciadFusion

com.luciad.view.gxy.ILcdGXYLayerList defines an ordered list of com.luciad.view.gxy.ILcdGXYLayer and implements com.luciad.view.gxy.ILcdGXYLayer. This allows grouping of layers into themes.

ImprovementLuciadFusion

com.luciad.view.gxy.ILcdGXYMultilabelPainter is an interface for label painters which can paint multiple labels per object. Existing label decluttering algorithms takes this new type of label painter into account.

ImprovementLuciadFusion

com.luciad.view.gxy.painter.ArcPainter

can have a null style set
has a snap icon
can have its center always painted
allows snapping to its end points

ImprovementLuciadFusion

com.luciad.view.gxy.painter.TLcdGXYBufferPainter

has a snap icon
allows snapping to its contour

ImprovementLuciadFusion

com.luciad.view.gxy.painter.TLcdGXYCirclePainter

allows snapping to its center
allows snapping of its center to a point
can have its center always/never/on selection painted.
has a snap icon

com.luciad.format.mif.TLcdMAPModelDecoder
com.luciad.format.mif.TLcdMIFModelDecoder
com.luciad.format.shp.TLcdSHPModelDecoder

ImprovementLuciadFusion

com.luciad.text.TLcdAltitudeFormat allows to parse and format altitudes.

ImprovementLuciadFusion

com.luciad.util.TLcdAltitdeUnit defines altitude unit constants.

ImprovementLuciadFusion

com.luciad.format.gml.TLcdGMLModelDecoder throws an IOException when decoding fails instead of returning a null model.

Bug fixLuciadFusion

Line-of-sight calculations take into account that both points should not be over a raster.

ImprovementLuciadFusion

com.luciad.util.ILcdContentDescriptor is an interface that describes the classes a com.luciad.model.ILcdModel contains. Following model descriptors implement this interface:

com.luciad.format.mif.TLcdMIFModelDescriptor
com.luciad.format.shp.TLcdSHPModelDescriptor

TLcdGXYArcBandPainter
TLcdGXYArcPainter
TLcdGXYBufferPainter
TLcdGXYCirclePainter
TLcdGXYEllipsePainter
TLcdGXYPointListPainter
TLcdGXYTextPainter

the interfaces:
- ILcd3DEditablePolygon
- ILcd3DEditablePolyline
- ILcd3DEditablePolypoint
and their implementations:
- TLcdXYZFloatLine
- TLcdXYZFloatPolygon
- TLcdXYZFloatPolyline
- TLcdXYZFloatPolypoint

com.luciad.format.raster.TLcdJAIRasterModelDecoder
com.luciad.format.raster.TLcdTABRasterModelDecoder

ImprovementLuciadFusion

com.luciad.format.raster.TLcdJAIRasterModelDecoder can create a com.luciad.model.ILcdModel based on a java.awt.image.RenderedImage and properties set.

ImprovementLuciadFusion

com.luciad.format.raster.TLcdRenderedImageTile has a method to suggest an index for the color to be made transparent.

ImprovementLuciadFusion

com.luciad.format.raster.TLcdTFWRasterModelDecoder can have a com.luciad.model.ILcdModelReferenceDecoder set.

ImprovementLuciadFusion

A package com.luciad.reference.format has been added. This package contains classes to parse and format reference systems. The following formats for reference systems are available:

AUTO (as defined by openGIS)
European Petroleum Survey Group (EPSG)
Well Known Text format (WKT)
LuciadMap specific format.

ImprovementLuciadFusion

iButton support has been extended to USB ports. The iButton is now supported on the following platforms:

serial adapter: Windows XP/NT/2000, Linux, Solaris
USB adapter: Windows XP/2000, Linux

com.luciad.view.gxy.ILcdGXYView implementations:
- PaintingMode -> paintingMode
- Scale -> scale
- MinScale -> minScale
- MaxScale -> maxScale
- WorldOrigin -> worldOrigin
- ViewOrigin -> viewOrigin
com.luciad.view.gxy.TLcdLayer:
- Visible -> visible
- Filter -> filter
- Selectable -> selectable
- Editable -> editable
- Label -> label
com.luciad.view.gxy.TLcdGXYLayer:
- ModelXYWorldTransfoClass -> modelXYWorldTransfoClass
- Filter -> filter
- Labeled -> labeled
- PaintFromOverlaps -> paintFromOverlaps
- ScaleRange -> scaleRange
- LabelScaleRange -> labelScaleRange
- SelectionLabeled -> selectionLabeled

ImprovementLuciadFusion

com.luciad.shape.ILcdEllipse has been added to the LuciadMap shapes. Two editable implementations are available:

com.luciad.shape.shape2D.TLcdLonLatEllipse
com.luciad.shape.shape2D.TLcdXYEllipse

ILcdPolygon: TLcdLonLatFloatPolygon, TLcdLonLatFloatPolygonCache, TLcdXYFloatPolygon, TLcdXYFloatPolygonCache
ILcdPolyline: TLcdLonLatFloatPolyline, TLcdLonLatFloatPolylineCache, TLcdXYFloatLine, TLcdXYFloatPolyline, TLcdXYFloatPolylineCache
ILcdPolyPoint: TLcdLonLatFloatPolyPoint, TLcdLonLatFloatPolyPointCache, TLcdXYFloatPolyPoint, TLcdXYFloatPolyPointCache

ImprovementLuciadFusion

The interface com.luciad.view.gxy.ILcdGXYPen and its implementations com.luciad.view.gxy.TLcdGXYPen, com.luciad.view.map.TLcdGeodeticPen, com.luciad.view.map.TLcdProjectionPen and com.luciad.view.map.TLcdGridPen have been tuned to improve performance. Two new classes/interfaces have been created for that purpose:

com.luciad.view.gxy.ILcdGeneralPath/TLcdGeneralPath describes a path in world coordinates, including possible line/polygon breaks. The path can be used to cache transformed shapes.
com.luciad.view.gxy.ILcdAWTPath/TLcdAWTPath: describes a path in AWT coordinates, including possible line/polygon breaks. An AWT path can paint itself as a polyline, a polygon, or a filled polygon.

ImprovementLuciadFusion

The properties noOfSubTileColumns/Rows in .rst files have been replaced with the more general properties subTilePixelWidth/Height.

ImprovementLuciadFusion

com.luciad.reference.TLcdProjectionReference has been superseded by com.luciad.reference.TLcdGridReference. To update your code, change TLcdProjectionReference to TLcdGridReference. The TLcdGridReference constructor takes the geodetic datum and the projection in reverse order compared to the TLcdProjectionReference. Following parameters are set to correspond to TLcdProjectionReference by default:

false easting : 0
false northing : 0
scale : 1
unit of measure: 1
rotation : 0 .

LuciadFusion Release notes

2024.0

2024.0.11

ImprovementLuciadFusion

LCD-13562

Bug fixLuciadFusion

LCD-13509

Bug fixLuciadFusion

LF-2644

Bug fixLuciadFusion

LCD-13619

2024.0.10

Bug fixLuciadFusion

LCD-13597

Bug fixLuciadFusion

LCD-13594

Bug fixLuciadFusion

LF-2654

Bug fixLuciadFusion

LCD-13592

2024.0.09

Bug fixLuciadFusion

LCD-10234

Bug fixLuciadFusion

LCD-13575

2024.0.08

ImprovementLuciadFusion

LCD-13516

Bug fixLuciadFusion

LCD-13559, LCD-13560

2024.0.07

ImprovementLuciadFusion

LF-2560

ImprovementLuciadFusion

LF-2560

ImprovementLuciadFusion

LF-2610

ImprovementLuciadFusion

LF-2611

Bug fixLuciadFusion

LCD-13445

Bug fixLuciadFusion

LF-2633

Bug fixLuciadFusion

LCD-13533

2024.0.06

Bug fixLuciadFusion

LCD-13525

2024.0.05

Bug fixLuciadFusion

LCD-13519

Bug fixLuciadFusion

LCD-13508

Bug fixLuciadFusion

LCD-13496

Bug fixLuciadFusion

LCD-13510

2024.0.04

ImprovementLuciadFusion

LCD-13270

ImprovementLuciadFusion

LF-2622

Bug fixLuciadFusion

LF-2626

Bug fixLuciadFusion

LCD-13477

Bug fixLuciadFusion

LCD-13476, LCD-13470

Bug fixLuciadFusion

LCD-13424

Bug fixLuciadFusion

LCD-12862

Bug fixLuciadFusion

LCD-13475

Upgrade considerationLuciadFusion

LCD-13414

2024.0.03

ImprovementLuciadFusion

LCD-13396

ImprovementLuciadFusion