LuciadRIA Release notes

Added support OGC 3DTiles 1.0 I3DM (Instanced 3D Model, .i3dm files) and CMPT (Composite, .cmpt files) tile payloads.

The support is not complete, and notably has the following limitations:

• Orientation of instances can be wrong depending on the input data.
• East-north-up orientation is not applied.
• Only composite tiles containing i3dm and b3dm data are supported, not pnts.
• Selection of instances is not possible.

The AxisConfiguration now supports labeling sub-tick in addition to main tick. This feature includes the following enhancements:

• Draw labels on axis sub-tick. Previously, only main tick were labeled. Now, both main and sub-tick can be labeled together.
• Style the sub-tick differently. You can now specify two TextStyle values - one for main tick labels and another for sub-tick labels.
• Dynamically change the number of sub-tick. The number of sub-tick can now change at runtime if a callback function is provided instead of a number.

HSPC attribute mapping is now decoded and can be accessed through the HSPCTilesModelDescriptor.

The AxisConfiguration for axes in a 2D cartesian map now supports styling and labeling sub-ticks in addition to main ticks. This feature includes these enhancements:

• Draw labels on axis sub-ticks. Previously, you could only label main ticks. Now, you can label both main ticks and sub-ticks.
• Style the sub-ticks differently. You can now specify two TextStyle values - one for main tick labels and another one for sub-tick labels.
• Dynamically change the number of sub-ticks. The number of sub-ticks can now change at runtime if you provide a callback function instead of a number.

It is now possible to connect to Azure Maps and use its data in your LuciadRIA application. A new class @luciad/ria/model/tileset/AzureMapsTileSetModel allows you to create a model for the desired Azure Maps data, which can you can then add to a LuciadRIA map using a RasterTileSetLayer. More information can be found in the new Visualize Azure Maps data article.

Please note that Azure Maps is introduced by Microsoft as the successor of Bing Maps. Only enterprise account customers can continue using Bing Maps for Enterprise services until June 30th, 2028. Free (Basic) account customers can no longer use Bing Maps and need to switch to Azure Maps.

• Property Textures are now supported.
• More than one Property Texture per object is also supported.
• Property Textures that use floating point values stored in PNG textures are also supported.

• the identifier set as "unknown"
• a Point representing the point location in the map's reference frame as Feature.Shape
• all the properties defined for this point
• an extra property called pointLocation, indicating the point's location as it appears in the original data

• ReferenceOptions.mercatorLatitudeExtentMin
• ReferenceOptions.mercatorLatitudeExtentMax
• ReferenceOptions.pseudoMercatorLatitudeExtentMin
• ReferenceOptions.pseudoMercatorLatitudeExtentMax

Improved the type definitions and documentation of the HSPCTilesModelDescriptor properties using a new HSPCModelPropertyDescription type.

urn:ogc:def:crs:WKT::LOCAL_CS%5B%22Generic+Cartesian+3D%22%2CLOCAL_DATUM%5B%22Unknown%22%2C0%5D%2CUNIT%5B%22m%22%2C1.0%5D%2CAXIS%5B%22x%22%2CEAST%5D%2CAXIS%5B%22y%22%2CNORTH%5D%2CAXIS%5B%22z%22%2CUP%5D%5D

You can now create an OrientedBox based on a Bounds object with ShapeFactory.createOrientedBoxFromBounds(bounds).

You can also transform a box using any coordinate transformation with OrientedBox.transformOrientedBox(box, transformation), which will return a new box in the output reference of the transformation.

Note that oriented boxes can only represent cartesian, topocentric, geocentric and projected grid coordinates properly, but not geodetic. The edges of a geodetic box are not geodesic lines and don't follow earth curvature, so for larger geodetic boxes, contains checks and transformations can produce inaccurate results. On small scales, geodetic boxes can still be used and transformed with good accuracy.

You can now create a combined transformation using TransformationFactory.createChainedTransformation(transformation1, transformation2). It will do the two subsequent transformations in one go.