LuciadCPillar Release notes

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