Luciad Developer Platform

Bug fixOGC Server

LCD-13592

The WFS server returned duplicate identifiers for GetFeature requests with a property name filter in case the source data did not have an explicit identifier (such as SHP files).

ImprovementOGC Server

LCD-13516

Bug fixOGC Server

LCD-13423

The WFS server could not handle property name filters for property names that were renamed during the encoding to GML. Such a rename can occur when a property name in the original data starts with a character that is not allowed as first character in an XML element - for example, a number.

New featureOGC Server

The WCS server in the OGC Web Server Suite now supports WCS version 2.0.1.

ImprovementOGC Server

LCD-13326

The WMS Server now supports a vendor-specific FILTER parameter that operates like the WFS GetFeature FILTER parameter for both GetMap and GetFeatureInfo requests.

ImprovementOGC Server

LCD-9574

The tray icon of the OGC server sample now has an additional entry to open the landing page.

Upgrade considerationOGC Server

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

Bug fixOGC Server

LCD-13073

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

was no longer called during the creation of a TLcdGXYViewBufferedImage. Extensions of TLcdWMSGXYViewFactory overriding this method to change the configuration of TLcdGXYViewBufferedImage where no longer applied because of this.

Bug fixOGC Server

LCD-13144

Fixed WCS coverage generation to better take into account the appropriate level of detail from a source data set with multiple level of details. Before the coverage generation would use less detailed information when encountering values representing a NODATA value. This could result in using inappropriate values when generating coverages having a more detailed level of detail.

ImprovementOGC Server

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

ImprovementOGC Server

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.

ImprovementOGC Server

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.

ImprovementOGC Server

LCD-12995

The priority of the ILcdGXYViewEncoder is now used to determine the order of the supported image formats advertised in the capabilities of the WMS Server.

Bug fixOGC Server

LCD-13160

Upgrade considerationOGC Server

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 considerationOGC Server

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

ImprovementOGC Server

The WMS and WMTS server now support GetFeatureInfo requests with text/html or text/xml as output format. When setting the output format to text/xml, the generated XML is based on the WMTS GetFeatureInfo XSD, which can be found here.

ImprovementOGC Server

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

ImprovementOGC Server

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.

ImprovementOGC Server

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.

Upgrade considerationOGC Server

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 considerationOGC Server

LCD-12142

Bug fixOGC Server

LCD-11827

A GML application schema returned by the WFS server for a DescribeFeatureType request no longer includes a GML FeatureCollection element and type, because WFS uses its own FeatureCollection.

Upgrade considerationOGC Server

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.

Bug fixOGC Server

ImprovementOGC Server

ImprovementOGC Server

LCD-10442

Improved the message in the WMS service exception report for the case when the parameter for the coordinate reference system is missing for operations like GetMap and GetFeatureInfo. In case of WMS 1.3.0 the parameter CRS is required and for WMS 1.1.x the parameter SRS is required.

ImprovementOGC Server

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 fixOGC Server

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

Bug fixOGC Server

LCD-10404

Fixed an issue where the WMTS server tried to write data to an already closed response. This issue occured when the client closed the connection while the server was still working on it.

Bug fixOGC Server

The WMS server's command dispatcher TLcdOGCSLDWMSCommandDispatcher did not always include the request context parameter when invoking the createGXYLayer method on the configured layer factory of type ALcdSLDWMSGXYLayerFactory.

Bug fixOGC Server

LCD-10305

The resolution logic introduced by LCD-9859 could cause the return of RGBA images for elevation coverages, leading to possible data interpretation issues in WCS clients.

ImprovementOGC Server

LCD-10187

The WFS server is now flexible against the casing used in the output format parameter in GetFeature requests.

Bug fixOGC Server

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.

Bug fixOGC Server

LCD-9780

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 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 fixOGC Server

LF-1471

When starting the ogc.server sample from the LuciadFusion release, no slf4j binding could be found, resulting in reduced logging.

Bug fixOGC Server

LCD-9616

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

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.

ImprovementOGC Server

LCD-9408

A WMS GetFeatureInfo encoder for the text/plain mime-type has been added. It replaces the encoder that was part of the samples and provides more information about the selected objects. For more details on the encoder have a look at the documentation of TLcdWMSTextPlainGetFeatureInfoEncoder.

Upgrade considerationOGC Server

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

ImprovementOGC Server

A new server and client API for OGC Catalogue Services (CSW) has been introduced.
For more information, see:

The OGC CSW Catalog Server developer's guide (CSW_DeveloperGuide.pdf)
The class javadoc of TLcdCSWServlet and TLcdCSWClient
The package javadoc of com.luciad.ogc.csw

ImprovementOGC Server

In the WFS service, the default implementation of ALcdOGCWFSCommandDispatcherFactory#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 ILcdModelDecoders of the formats that are installed.

ImprovementOGC Server

LCD-6715

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

Upgrade considerationOGC Server

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 considerationOGC Server

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 considerationOGC Server

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 considerationOGC Server

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 considerationOGC Server

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 considerationOGC Server

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 considerationOGC Server

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 considerationOGC Server

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 considerationOGC Server

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 considerationOGC Server

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 considerationOGC Server

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.

LCD-6799

A set of security improvements have been implemented:

Removed the dependency on the legacy JGenerator 2.2 library,
Improved the sanitization of response content to be more robust against CRLF injections and cross-site scripting attempts.

ImprovementOGC Server

LCD-5929

The OGC WMS web service previously available in build/wms (containing the build script) and distrib/ogc/LuciadLightspeedWMS_x.x.x (containing a pre-built / ready-to-deploy service) has now been integrated in a combined OGC web service sample, consisting of a WMS, WFS and WCS; the folder build/ogc contains the build script and the folder distrib/ogc/LuciadLightspeedOGC_x.x.x contains a pre-built and ready-to-deploy service. To run the pre-built service, you can still use the script ogc.server.start (.bat/.sh) available in the samples folder, which will deploy the service in a Jetty servlet container.

ImprovementOGC Server

LCD-5929

The OGC WFS web service previously available in build/wfs (containing the build script) and distrib/ogc/LuciadLightspeedWFS_x.x.x (containing a pre-built / ready-to-deploy service) has now been integrated in a combined OGC web service sample, consisting of a WMS, WFS and WCS; the folder build/ogc contains the build script and the folder distrib/ogc/LuciadLightspeedOGC_x.x.x contains a pre-built and ready-to-deploy service. To run the pre-built service, you can still use the script ogc.server.start (.bat/.sh) available in the samples folder, which will deploy the service in a Jetty servlet container.

Bug fixOGC Server

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 considerationOGC Server

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 considerationOGC Server

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

LCD-7506

ImprovementOGC Server

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

ImprovementOGC Server

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

Bug fixOGC Server

LCD-6640

The WCS server now respects caching headers also for XML requests.

Bug fixOGC Server

LCD-6615

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 considerationOGC Server

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 considerationOGC Server

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 considerationOGC Server

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 considerationOGC Server

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 considerationOGC Server

Upgrade considerationOGC Server

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 considerationOGC Server

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.

Bug fixOGC Server

LCD-5384

Fixed a bug in the deploy_wcs script so that it now correctly includes the license.

ImprovementOGC Server

LCD-5169

ImprovementOGC Server

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.

ImprovementOGC Server

Upgrade considerationOGC Server

Bug fixOGC Server

The WCS server could not cope with some GetCoverage requests that specified a longitude/latitude outside the coverage bounds.

Bug fixOGC Server

LCD-3060

The WMS scale denominators (optionally configurable on WMS layers) are not correctly taken into account in case of the geodetic reference EPSG:4326 / CRS:84.

Bug fixOGC Server

The WCS server could not cope with GetCoverage requests that specified longitude/latitude request that crossed the date line.

Bug fixOGC Server

TLcdOWSDomain#getValues() did always return an empty array. This class is used inside OWS (WFS, WCS, WMS) capabilities to model domain metadata.

Bug fixOGC Server

LCD-2541

The WMS XML schema's have been updated. The new versions now refer to the official W3C XLink schema, instead of the OGC variant that was used before.

Bug fixOGC Server

LCD-2541

The WFS XML schema's have been updated. The new versions now refer to the official W3C XLink schema, instead of the OGC variant that was used before.

Bug fixOGC Server

LCD-2541

The WCS XML schema's have been updated. The new versions now refer to the official W3C XLink schema, instead of the OGC variant that was used before.

ImprovementOGC Server

LCD-2610

It is now possible to avoid loading the EPSG, AUTO and/or AUTO2 reference codes in the WMS capabilities by leaving out their configuration parameters in the web.xml file.

ImprovementOGC Server

XML Schema's are now better cached. This improves the performance of processing XPaths.

ImprovementOGC Server

The WFS server no longer accesses the elements() method to generate its schema's, if a data model is available.

Bug fixOGC Server

LCD-2425

ImprovementOGC Server

The WFS server now supports additional GML output formats to export data using the GML simple features profile. This allows servers to either export as simple features by default, or otherwise to expose the additional output formats so they are available to clients.

Upgrade considerationOGC Server

The lcd_wxs_common.jar is no longer part of the release. The necessary classes have been included in the luciadmap.jar

Upgrade considerationOGC Server

The lcd_wxs_common.jar is no longer part of the release. The necessary classes have been included in the luciadmap.jar.

Bug fixOGC Server

LMAP-2414

The WMS GIF encoder, TLcdGXYViewGIFEncoder, now properly supports images that have more than 256 colors in combination with transparency, regardless of the JDK version.

Bug fixOGC Server

LMAP-3741

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.*".

ImprovementOGC Server

The (unofficial) EPSG code 900913 used by Google Earth is now supported.

Bug fixOGC Server

LMAP-4439

Fixed an issue that could cause decoding of transaction requests to fail when the request contains a schemalocation for a type defined by the WFS. We now ignore these schemalocations and use the schemas that are linked to the data.

ImprovementOGC Server

By default support special versions of EPSG codes and some specific srs names like CRS84.

ImprovementOGC Server

LMAP-4312

Improved handling of certain bad filters, this will now result in a WFS service exception.

ImprovementOGC Server

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.

Upgrade considerationOGC Server

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 considerationOGC Server

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 considerationOGC Server

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 considerationOGC Server

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 considerationOGC Server

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 considerationOGC Server

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.

Bug fixOGC Server

LMAP-3960

The INTERSECT constant of the TLcdOGCSpatialFilterCapabilities evaluator had the incorrect value "Intersect" where it should have been "Intersects". As a result, encoding capabilities containing such a spatial filter capability resulted in an invalid xml document.

ImprovementOGC Server

The JGenerator library used by TLcdGXYViewSWFEncoder to generate maps in the SWF (Flash) format has been upgraded from version 1.3.1 to version 2.2.

ImprovementOGC Server

The EPSG code 3395 is now supported by default.

ImprovementOGC Server

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

ImprovementOGC Server

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

ImprovementOGC Server

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

ImprovementOGC Server

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>

ImprovementOGC Server

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.

Bug fixOGC Server

LMAP-2845

The XML Schema response to a WFS 1.1.0 DescribeFeatureType request now refers to the GML 3.1.1 XML schemas instead of to the GML 2.1.2 XML schemas.

Upgrade considerationOGC Server

The interface com.luciad.ogc.common.ILcdKVPRequest, used by the WFS and WCS server to represent a key-value pair request, has been extended with a new method getParameterNames(). It returns a list of all the parameters that are specified in the request. Although unlikely, this change requires an update if there are custom implementations of this interface.

Upgrade considerationOGC Server

LMAP-2723

To allow a WFS Server implementation to serve data without geometry, the WFS Server API no longer enforces the use of ILcd2DBoundsIndexedModel when decoding models. The API is now compatible with regular ILcdModel implementations, so that implementations like TLcdVectorModel can be used that do not require objects to have a geometric extent.

To be able to support this, the return type of the following methods is now ILcdModel instead of ILcd2DBoundsIndexedModel:

ILcdOGCModelProvider#getModel,
ILcdWFSFilteredModelFactory#createFilteredModel,
TLcdWFSFilteredModelFactory#createFilteredModel.

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.

The source name property of a layer (see getSourceName() in ALcdWMSLayer), is too limited to be used for a layer with one or more dimensions, since the corresponding data source depends not only on the layer name but also on the dimensional parameters supplied by the client. To be able to map an ALcdWMSLayer with one or more dimensional parameters on a data source, the abstract class ALcdMultiDimensionalModelProvider has been introduced. Users must implement this class and register it by overriding the method createModelProvider(ILcdModelDecoderFactory[]) in ALcdOGCWMSCommandDispatcherFactory, to support multi-dimensional layers.

ImprovementOGC Server

The domain model for the WMS capabilities has been extended to include support for the elements MetadataURL, DataURL and FeatureListURL that can be defined for a layer, and for the elements LegendURL, StylesheetURL and StyleURL that can be defined for a layer style. To model these elements, a new class TLcdWMSURL has been introduced. The classes ALcdWMSLayer, TLcdWMSLayer, ALcdWMSLayerStyle and TLcdWMSLayerStyle have been extended with methods to configure these elements. For consistency, the already supported element AuthorityURL for a layer can now also be modeled using TLcdWMSURL in ALcdWMSLayer and TLcdWMSLayer.

ImprovementOGC Server

A new interface ILcdWMSOnlineResourceResolver has been introduced, which is used to dynamically resolve the paths to online resources. A default implementation is registered by default, but custom implementations can be used by overriding the method createWMSOnlineResourceResolver(ServletConfig) in ALcdOGCWMSCommandDispatcherFactory.

ImprovementOGC Server

Two new methods have added to ALcdWMSLayer, which make it possible to retrieve the parent layer:

setParentWMSLayer(ALcdWMSLayer): a protected method that can be called to register the parent layer. The default implementation TLcdWMSLayer automatically invokes this method on the child layer when addChildWMSLayer(ALcdWMSLayer) or removeChildWMSLayer(ALcdWMSLayer) is called.
getParentWMSLayer(): a public method, allowing to retrieve the currently registered parent layer.

This functionality is particularly useful to retrieve the layer styles registered on parent layers, because the WMS specification defines that a layer inherits the styles of its parent.

ImprovementOGC Server

Support has been added for two new requests: GetLegendGraphic and DescribeLayer. The GetLegendGraphic request provides a general mechanism for acquiring legend symbols. The DescribeLayer request allows a client to obtain feature/coverage-type information for a named layer, which can be used to construct user-defined styles. Both requests are defined by the OpenGIS OGC 02-070 Styled Layer Descriptor Implementation Specification, and are considered optional for an SLD-enabled WMS.

To provide support for these requests in a WMS implementation, the factory methods createWMSGetLegendGraphicEncoders(ServletConfig) and createWMSDescribeLayerEncoders(ServletConfig) in ALcdOGCSLDWMSCommandDispatcherFactory must be implemented. These methods should return respectively one or more ILcdWMSGetLegendGraphicRequestEncoder and ILcdWMSDescribeLayerRequestEncoder objects, which are responsible for sending a response to the client. Next, the available legend graphic and describe layer formats must be listed in the ALcdWMSCapabilities object created by the ILcdWMSCapabilitiesDecoder in ALcdOGCSLDWMSCommandDispatcherFactory.

Because the OpenGIS OGC 02-070 Styled Layer Descriptor Implementation Specification defines a default XML format for DescribeLayer responses, an implementation of ILcdWMSGetLegendGraphicRequestEncoder, ALcdWMSDescribeLayerRequestEncoder, is also available. This abstract class implements the methods defined in ILcdWMSGetLegendGraphicRequestEncoder, and adds some extra abstract methods that are needed to construct a correct DescribeLayer response. Encoders that want to use the default XML format should extend from this abstract class.

Bug fixOGC Server

An issue has been solved in the view management performed by com.luciad.wms.server.TLcdOGCWMSCommandDispatcher, which potentially could lead to a deadlock when handling GetMap/GetFeatureInfo requests, especially on high-loaded servers. When established, some incoming requests would never be handled, and ultimately, the server would stop responding to GetMap/GetFeatureInfo requests.

Upgrade considerationOGC Server

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 considerationOGC Server

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 considerationOGC Server

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 considerationOGC Server

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.

Bug fixOGC Server

The WFS now properly sets the content type (mime type) of its responses.

ImprovementOGC Server

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.

Bug fixOGC Server

The GML model and schema encoders used by the WFS now properly respect the feature type name specified in ILcdWFSFeatureType.

ImprovementOGC Server

The WMS server developer guide has been extended with extra information about offering support for GetFeatureInfo requests. It now also includes an example of a ILcdWMSFeatureInfoRequestEncoder implementation.

ImprovementOGC Server

LMAP-1440

An interface ILcdWFSServiceMetaData has been introduced in the WFS package. By creating an ILcdWFSServiceMetaData in the command dispatcher factory, WFS users can customize the <Service> section of the WFS capabilities document.

ImprovementOGC Server

The WCS server now performs proper escaping of all user-specifiable values that appear in the GetCapabilities and DescribeCoverage responses.

ImprovementOGC Server

The WFS now performs proper escaping of all user-specifiable values that appear in the GetCapabilities response.

ImprovementOGC Server

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.

ImprovementOGC Server

A new sample is available, samples.wms.client.sld.MainApplet, that illustrates the use of an SLD-enabled WMS server at the client side.

ImprovementOGC Server

The SLD-enabled WMS server now supports GetMap requests that use HTTP XML POST instead of HTTP GET. These type of requests are described in the OGC 02-017r1 Web Map Service Implementation Specification, Part 2: XML for Requests using HTTP POST. Note: servers that use the regular ALcdOGCWMSCommandDispatcherFactory and TLcdOGCWMSCommandDispatcher do not support these types of requests, since SLD support is required to handle them.

ImprovementOGC Server

The WMS server now contains support for OpenGIS Styled Layer Descriptors (SLD), as defined in the OGC 02-070 Styled Layer Descriptor Implementation Specification version 1.0. The following classes and packages are added:

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.

ImprovementOGC Server

The WFS has been extended to support most of the WFS 1.1 specification:

GetFeature requests support the "resultType" parameter, allowing clients to retrieve the number of features matched by a request without having to retrieve the actual corresponding features.
Features can be retrieved in both GML2 and GML3 formats.
The OGC Filter 1.1 specification is supported.

Upgrade considerationOGC Server

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 considerationOGC Server

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.

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

LuciadLightspeed Release notes

2024.0

2024.0.10

Bug fixOGC Server

LCD-13592

2024.0.08

ImprovementOGC Server

LCD-13516

2024.0.06

Bug fixOGC Server

LCD-13525

2024.0.05

Bug fixOGC Server

LCD-13508

Bug fixOGC Server

LCD-13510

2024.0.04

Bug fixOGC Server

LCD-13475

2024.0.03

ImprovementOGC Server

LCD-13447

Bug fixOGC Server

LCD-13434

Bug fixOGC Server

LCD-13423

2024.0

New featureOGC Server

ImprovementOGC Server

LCD-13326

ImprovementOGC Server

LCD-9574

Upgrade considerationOGC Server

2023.1

2023.1.15

Bug fixOGC Server

LCD-13361

Bug fixOGC Server

LCD-13362

2023.1.13

Bug fixOGC Server

LCD-13323

2023.1.11

ImprovementOGC Server

LCD-13310

Bug fixOGC Server

LCD-13314

Bug fixOGC Server

LCD-13313

2023.1.06

Bug fixOGC Server

LCD-13253

2023.1.04

Bug fixOGC Server

LCD-13215

2023.1.02

Bug fixOGC Server

LCD-13073

2023.1.01

Bug fixOGC Server

LCD-13144

2023.1

ImprovementOGC Server

ImprovementOGC Server

LCD-13074

ImprovementOGC Server

LCD-13022, LCD-13016, LCD-8758

ImprovementOGC Server

LCD-12995

Bug fixOGC Server

LCD-13160

2023.0

2023.0.12

Bug fixOGC Server

2023.0.11

Bug fixOGC Server

LCD-13085

Bug fixOGC Server

LCD-13108

2023.0.07