LuciadCPillar Release notes

Added support for editing PolygonPolygonPolygon instances using the EditorEditorEditor class. This is done using the new PolygonHandlesProviderPolygonHandlesProviderPolygonHandlesProvider class. Editing polygons works out of the box: this new handles provider is used by default by FeatureHandlesProviderFeatureHandlesProviderFeatureHandlesProvider and CompositeGeometryHandlesProviderCompositeGeometryHandlesProviderCompositeGeometryHandlesProvider.

In addition to this functionality, a few utilities where added to modify and handle PolygonPolygonPolygon instances:

• ObservablePolygonUtilObservablePolygonUtilObservablePolygonUtil
• Polygon::replaceExteriorRingPolygon::replaceExteriorRingPolygon::replaceExteriorRing
• Polygon::replaceInteriorRingPolygon::replaceInteriorRingPolygon::replaceInteriorRing
• Polygon::appendInteriorRingPolygon::appendInteriorRingPolygon::appendInteriorRing
• Polygon::removeInteriorRingPolygon::removeInteriorRingPolygon::removeInteriorRing

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

• Implicit tiling (both JSON and binary subtrees, no metadata yet).
• GLB/glTF (using internal, Base64 inlined or external buffers) as payload.
• Supported glTF 2.0 extensions:
  • KHR_texture_transform
  • KHR_mesh_quantization
  • EXT_meshopt_compression
  • EXT_mesh_features

• The MBTiles Developer's Guide.
• The reference documentation of MbTilesModelDecoderMbTilesModelDecoderMbTilesModelDecoder on how to decode MBTiles.

• RasterLayerType::BackgroundRasterLayerType::BackgroundRasterLayerType::Background layers.
• RasterLayerType::InteractiveRasterLayerType::InteractiveRasterLayerType::Interactive layers.

• GdalModelDecoderGdalModelDecoderGdalModelDecoder
• GeoPackageModelDecoderGeoPackageModelDecoderGeoPackageModelDecoder
• WmsModelDecoderWmsModelDecoderWmsModelDecoder
• WmtsModelDecoderWmtsModelDecoderWmtsModelDecoder
• Ogc3DTilesModelDecoderOgc3DTilesModelDecoderOgc3DTilesModelDecoder

• KHR_texture_transform
• KHR_mesh_quantization
• EXT_meshopt_compression

• libcurl: updated to version 8.6.0
• openssl: updated to version 3.1.2
• zlib: updated to version 1.3.1

A couple of methods now use double values instead of integer values:

• Map::resizeMap::resizeMap::resize
• Map::getWidthMap::getWidthMap::getWidth and Map::getHeightMap::getHeightMap::getHeight
• Camera::getWidthCamera::getWidthCamera::getWidth and Camera::getHeightCamera::getHeightCamera::getHeight

This was done to avoid precision loss due to rounding errors. In rare cases, this precision loss could lead to incorrect behavior like:

• map-wide jittering effects
• a (small) black border at the side of the map
• the map content being stretched out very slightly

It is now possible to specify an OcclusionModeOcclusionModeOcclusionMode when painting geometries and (non-label) icons or text. This allows you to (partially) show 3D objects that would otherwise be obscured by other 3D objects. See

• FeatureCanvas::GeometryDrawCommand::occlusionModeFeatureCanvas::GeometryDrawCommand::occlusionModeFeatureCanvas::GeometryDrawCommand::occlusionMode
• FeatureCanvas::IconDrawCommand::occlusionModeFeatureCanvas::IconDrawCommand::occlusionModeFeatureCanvas::IconDrawCommand::occlusionMode
• FeatureCanvas::TextDrawCommand::occlusionModeFeatureCanvas::TextDrawCommand::occlusionModeFeatureCanvas::TextDrawCommand::occlusionMode

The precision of WKT and EPSG references that use an ellipsoidal version of the Lambert azimuthal equal area projection has been improved. This affects the following EPSG codes:

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

The C# WinForms and WPF integration code has been improved to more easily support scenarios where a Map is removed from the application window, and moved to a different component in that same application window. An example of such a scenario is when the WinForms or WPF Map components are used within a docking UI framework.

Before this improvement, this would either cause crashes or the map component would not paint its Map content anymore.

It is now possible to create 3D icons from glTF files in LuciadCPillar by using the FeatureCanvas::drawIcon3DFeatureCanvas::drawIcon3DFeatureCanvas::drawIcon3D method. FeatureCanvas::Icon3DDrawCommandFeatureCanvas::Icon3DDrawCommandFeatureCanvas::Icon3DDrawCommand allows you to set the glTF source file to load as well as other properties such as transformations: scale, rotation, orientation and translation. As well as color modulation, mesh position, query-ability of the mesh and a setting to tell if the mesh contains transparent surfaces.

The camera sample demonstrates how to import a glTF file. This information can also be found in the article Learn how to load and visualize your glTF data.
For information about the limitation of our glTF support in LuciadCPillar please refer to the article Which glTF version is supported and what are the limitations?.

• The raster RasterStyle::Builder::opacityRasterStyle::Builder::opacityRasterStyle::Builder::opacity
• The raster RasterStyle::Builder::brightnessRasterStyle::Builder::brightnessRasterStyle::Builder::brightness
• The raster RasterStyle::Builder::contrastRasterStyle::Builder::contrastRasterStyle::Builder::contrast
• The raster RasterStyle::Builder::modulationColorRasterStyle::Builder::modulationColorRasterStyle::Builder::modulationColor

LuciadCPillar has been upgraded to support .NET standard 2.0. It is now much easier to use the LuciadCPillar C# binary on newer .NET implementations. LuciadCPillar already supported .NET Framework 4.7.2 (or later). It now also supports all .NET Core and .NET versions (5 or later).

Note that building and running the LuciadCPillar C# samples still requires .NET Framework 4.7.2.

• C++: include <luciad/drawing/ImageIcon.h>
• C#: using Luciad.Drawing
• Android: import com.luciad.drawing.ImageIcon

• GDAL: updated to version 3.7.0
• PROJ: updated to version 9.1.1
• json-c: version 0.17, used by GDAL
• libtiff: version 4.5.1, used by GDAL
• nlohmann_json: version 3.11.2, used by PROJ

• The presence of a MapScaleMapScaleMapScale with a small denominator in the layer's IFeaturePainterIFeaturePainterIFeaturePainter implementation or in the layer's FeatureQueryConfigurationFeatureQueryConfigurationFeatureQueryConfiguration
• The presence of a large feature in the layer's IFeatureModelIFeatureModelIFeatureModel
• A model update of this large feature in the layer's IFeatureModelIFeatureModelIFeatureModel
• A camera position that is looking towards the horizon (in 3D), or the additional presence of many small features (>50000) in the layer's IFeatureModelIFeatureModelIFeatureModel, concentrated in a small area.

It is now possible to replace the IFeaturePainterIFeaturePainterIFeaturePainter of a FeatureLayerFeatureLayerFeatureLayer by a new feature painter instance. This allows you to change the styling for all features in the layer.

Note: There is currently the limitation that the detail levels of the new IFeaturePainterIFeaturePainterIFeaturePainter must be the same as those of the previous feature painter.

• Korean Datum 1985
• Macao 1920

Since the 2022.0 release, QQuickMapObject and QQuickMapRenderer didn't allow creating multiple maps anymore. This is now possible again.

When you have copies of these classes, you can fix this issue by copying the new versions of these classes from the LuciadCPillar sample code to your application.

• 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

• PolylineHandlesProvider
• PolylineRingHandlesProvider

• The Map can now correctly visualize non-world covering elevation data sets correctly. In previous versions it clips away all other data outside the extents of the elevation data set. This is not the case anymore: all data outside the elevation data's extent is now painted at elevation 0.
• The map can now visualize multiple elevation data sets at the same time. In previous versions only the top-most elevation layer is used to generate terrain. Now all layers that contain elevation data are used to generate terrain.

• The DTED Developer's Guide.
• The reference documentation of DtedModelDecoderDtedModelDecoderDtedModelDecoder on how to decode DTED.

• HttpClientHttpClientHttpClient
• HttpRequestHttpRequestHttpRequest
• HttpResponseHttpResponseHttpResponse

• Ogc3DTilesModelDecoderOgc3DTilesModelDecoderOgc3DTilesModelDecoder
• HspcModelDecoderHspcModelDecoderHspcModelDecoder
• WmsModelDecoderWmsModelDecoderWmsModelDecoder
• WmtsModelDecoderWmtsModelDecoderWmtsModelDecoder

• AngleAngleAngle
• AzimuthAzimuthAzimuth

• FeatureStateFeatureStateFeatureState
• PriorityPriorityPriority
• GeoPackageTableMetadataGeoPackageTableMetadataGeoPackageTableMetadata
• LayerLayerLayer
• FeatureLayerFeatureLayerFeatureLayer
• TileSet3DLayerTileSet3DLayerTileSet3DLayer
• MouseCursorMouseCursorMouseCursor
• KeyCodeKeyCodeKeyCode
• MouseButtonMouseButtonMouseButton
• ModifierKeysModifierKeysModifierKeys
• MapScaleMapScaleMapScale

• FeatureCanvas::IconDrawCommand::iconFeatureCanvas::IconDrawCommand::iconFeatureCanvas::IconDrawCommand::icon
• FeatureCanvas::LabelDrawCommand::iconFeatureCanvas::LabelDrawCommand::iconFeatureCanvas::LabelDrawCommand::icon
• FillStyle::Builder::iconFillStyle::Builder::iconFillStyle::Builder::icon

• FeatureCanvas::IconDrawCommand::scaleFeatureCanvas::IconDrawCommand::scaleFeatureCanvas::IconDrawCommand::scale
• FeatureCanvas::IconDrawCommand::sizeFeatureCanvas::IconDrawCommand::sizeFeatureCanvas::IconDrawCommand::size
• FeatureCanvas::TextDrawCommand::scaleFeatureCanvas::TextDrawCommand::scaleFeatureCanvas::TextDrawCommand::scale

• LineStyle::Builder::inMetersLineStyle::Builder::inMetersLineStyle::Builder::inMeters
• FeatureCanvas::IconDrawCommand::inMetersFeatureCanvas::IconDrawCommand::inMetersFeatureCanvas::IconDrawCommand::inMeters
• FeatureCanvas::TextDrawCommand::inMetersFeatureCanvas::TextDrawCommand::inMetersFeatureCanvas::TextDrawCommand::inMeters

LuciadCPillar for Android allows you to develop GPU accelerated geospatial situational awareness applications targeted to run on Android mobile devices. LuciadCPillar for Android is an SDK that supports both Kotlin and Java development. It is feature equivalent with LuciadCPillar for desktop.

To get started, consult the product documentation and select the Android profile at the top right of the page. The product documentation includes installation guides, a Java API reference and a set of ready-to-run kotlin samples that can be installed on your mobile device from Android studio.

You can now enable GPU texture compression on TileSet3DLayerTileSet3DLayerTileSet3DLayer for OGC 3D Tiles mesh data. This can greatly reduce the amount of GPU memory needed, improve performance and stability.

Enable when displaying meshes with large textures, such as reality capture reconstructions. By default, texture compression is enabled.
Disable when displaying meshes with lookup textures, such as CAD models.

If your environment does not support GPU texture compression, setting the flag has no effect.

• Data starts appearing on the screen up to 10 times faster right after adding a vector layer or after zooming in to a different detail level.
• Data loading throughput is up to 2 times larger.
• Data appears and disappears up to 5-10 times faster while navigating.
• The map's frame rate is higher while vector data is loaded. Navigation now remains smooth at all times during loading.

• EPSG:6988
• EPSG:6989
• EPSG:6990
• EPSG:6991

• libcurl: updated to version 7.86.0
• openssl: updated to version 1.1.1s
• zlib: updated to version 1.2.13

• GDAL: updated to version 3.4.3
• PROJ: updated to version 9.0.1
• SQLite3: updated to version 3.38.5
• nlohmann_json: version 3.10.5, used by PROJ
• libgeotiff: version 1.7.1, used by GDAL
• json-c: version 0.15, used by GDAL

• The updated articles regarding Interacting with the Map.
• The LuciadCPillar Qt integration Guide.

• The OGC 3D Tiles Developer's Guide.
• The HSPC Developer's Guide.
• The reference documentation of Ogc3DTilesModelDecoderOgc3DTilesModelDecoderOgc3DTilesModelDecoder on how to decode OGC 3D Tiles.
• The reference documentation of HspcModelDecoderHspcModelDecoderHspcModelDecoder on how to decode HSPC (Hexagon Smart Point Cloud) files.

The CPillar map now supports high DPI rendering. This means that fonts, icons and other map elements are automatically resized in proportion to the display scale configured in the operating system. This also means that map scale calculations use the configured DPI to get a correct interpretation.

When integrating the CPillar map in a UI framework the DPI and the display scale must be configured on the Map::RendererMap::RendererMap::Renderer. You can read more on this in the article on support for high DPI displays. The article on integration within Qt provides details on how this is done for the Qt UI toolkit.

The API allows to provide icons for multiple resolutions such that the CPillar map can use the best applicable for your screen setup. For this purpose, the IIconIIconIIcon class was modified to allow painting an icon in different resolutions.

• How to provide authentication credentials.
• How to configure a proxy server.

IInputEventIInputEventIInputEvents and in particular, gesture recognition, have been refactored. See the updated articles regarding interacting with the Map through a controller and integration within Qt for more information.

• Mouse input events related types are now declared in the luciad/input/mouse/MouseEvents.h header.
• The GestureRecognizer class has been replaced by dedicated MouseGestureRecognizerMouseGestureRecognizerMouseGestureRecognizer and TouchGestureRecognizerTouchGestureRecognizerTouchGestureRecognizer classes, which handle mouse based and touch based gestures, respectively.
• The MouseGestureRecognizerMouseGestureRecognizerMouseGestureRecognizer can be included through the luciad/input/mouse/MouseGestureRecognizer.h header.
• The TouchGestureRecognizerTouchGestureRecognizerTouchGestureRecognizer can be included through the luciad/input/touch/TouchGestureRecognizer.h header.

• FeatureChangeFeatureChangeFeatureChange
• WmtsLayerWmtsLayerWmtsLayer
• WmtsBoundingBoxWmtsBoundingBoxWmtsBoundingBox
• GeoPackageTableMetadataGeoPackageTableMetadataGeoPackageTableMetadata

• Well Known Text (WKT) reference
• WMS capabilities
• GeoTIFF

• EPSG:2065
• EPSG:5513
• EPSG:8352

• Above constraint: to keep the camera above the terrain in 3D
• Pitch constraint: to limit the camera tilt in 3D
• Bounds constraint: to keep the camera inside a defined bounds in 2D
• Scale constraint: to prevent the camera from zooming in or out too far in 2D

• directly pass a horizontalAlignment to the FeatureCanvas::LabelDrawCommand::textFeatureCanvas::LabelDrawCommand::textFeatureCanvas::LabelDrawCommand::text method that accepts a vector of strings
• use the FeatureCanvas::LabelDrawCommand::textFeatureCanvas::LabelDrawCommand::textFeatureCanvas::LabelDrawCommand::text method that accepts a TextBlockTextBlockTextBlock.

• add labels that are attached a point
• add labels that use the same orientation as the line they are attached to
• add labels inside an area

• labels are decluttered to avoid overlap
• labels are always painted above all the other content on the map
• a pin can be drawn to show where the label is attached to its feature

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

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

• The to parameter for a MapNavigator::ZoomActionMapNavigator::ZoomActionMapNavigator::ZoomAction must be in the map reference or an exception is thrown.
• The from parameter for a MapNavigator::PanActionMapNavigator::PanActionMapNavigator::PanAction must be in the map reference or an exception is thrown.
• The center parameter for a MapNavigator::RotateActionMapNavigator::RotateActionMapNavigator::RotateAction must be in the map reference or an exception is thrown.

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

• FeatureCanvasFeatureCanvasFeatureCanvas and its draw command classes
• RasterLayerRasterLayerRasterLayer
• EditSettingsEditSettingsEditSettings
• PointEditHandlePointEditHandlePointEditHandle
• TranslateEditHandleTranslateEditHandleTranslateEditHandle

• Map navigation
• Selection

• FeatureStateManager::Change::createFeatureStateManager::Change::createFeatureStateManager::Change::create
• IFeatureModelObserver::createIFeatureModelObserver::createIFeatureModelObserver::create
• IFeatureQueryCallback::createIFeatureQueryCallback::createIFeatureQueryCallback::create
• IInvalidationCallback::createIInvalidationCallback::createIInvalidationCallback::create
• ILayerObserver::createILayerObserver::createILayerObserver::create
• IMapQueryFeaturesCallback::createIMapQueryFeaturesCallback::createIMapQueryFeaturesCallback::create
• IPointCallback::create

• Top Most feature (unless draped)
• Layer order
• Feature Z order
• Unspecified Order

• Layer order
• Feature Z order
• Unspecified Order