The 2021.1 release of LuciadLightspeed brings an update to the support for military grids, additional support for background data, and improved tile processing capabilities.
Military grids complement global reference systems. In specific areas, coordinates can become quite precise and long. To prevent confusion, grid systems that specify areas with a combination of letters and numbers have been created. These grids can be global, or area-specific for battlefield management purposes.
LuciadLightspeed already supported MGRS grids, both for Lightspeed views and GXY views, and offered sample code for CGRS and GARS grids.
With this release, LuciadLightspeed has been extended with API that supports both the CGRS and GARS format, and the visualization of CGRS and GARS grids on Lightspeed views. With the format API, you can convert lon-lat coordinates into the Common Grid Reference System (CGRS) and Global Area Reference System (GARS) notation, and use methods to parse grid coordinate strings into point objects.
The military grid support for LuciadLightspeed has been moved to the “Defense Symbology” option. This means that you now need the Defense Symbology option for both the existing MGRS grid support and the new CGRS and GARS grid support. If you have any questions related to this change, please contact Luciad Product Management via email@example.com.
Operational data becomes more relevant when you show it in context. For that, you need detailed background data. There are various providers of such imagery data, and LuciadLightspeed already offers numerous data connectors that allow you to include background imagery. In addition, the OGC WMS and WMTS connectors ensure that you can also include any background data offered through those services.
With this release, we enriched our set of connectors with a connector for OpenStreetMap data that is offered through OpenStreetMap tile servers. LuciadLightspeed can consume that data directly, and display it in both the GXY view and the Lightspeed view.
A dedicated OpenStreetMap decoder has been added to LuciadLightspeed samples:
You can find more information in the tutorials Visualize OpenStreetMap raster tiles data on a GXY map and Visualize OpenStreetMap raster tiles data on a Lightspeed map.
In this release, the 3D tiles processing engine has been extended with material support and tile geometry compression.
3D tiles is an OGC community standard and popular exchange format for 3D information. A typical example of data that is very suitable to be exchanged in 3D tiles format is 3D city models. Despite the efficiency that comes from the tiled and multi-leveled nature of the data, there are still cases where the amount of data becomes a bottleneck. A solution for that is data compression. Google’s Draco is a popular library for compressing geometry during the encoding of a 3D payload into the glTF format.
LuciadLightspeed’s 3D tiles processing engine has now been extended with the capability to encode meshes as Draco-compressed 3D tiles. The benefit of applying this compression is that the resulting data set is significantly smaller. The conversion time is only slightly higher.
3D data sets have become more and more detailed, and now often have texture information. Visualizing the textures of a data set helps users distinguish between objects, and makes clear what an object represents. In the absence of textures, this is less clear.
There are situations where objects are quite similar in geometry. Factory and building data typically consists of geometrically similar objects, for example. Although those objects may look similar in form, we can still tell them apart through their material properties.
If 3D objects offer information on their material, such as metallic-ness and roughness, the LuciadLightspeed 3D tiles processing engine will now pick it up, and encode it within the tiles. Any compatible client can then offer quite realistic rendering of the data. Note that LuciadRIA supports the rendering of 3D tiles, including material properties.
Because OBJ files typically do not encode a wide variety of materials, support for input data in binary GLTF has been added to the processing engine. The GLTF format can contain more material information.
The Command Line Interface (CLI) Meshup sample now includes Draco compression and material support.
- Line rounding
Line rounding is now supported for polylines and polygons. Lines and areas can be used to mark exact boundaries and areas. Sometimes, it is necessary to indicate an approximate area or boundary on a map. For that purpose, API has been added in LuciadLightspeed 2021.1 to create rounded polylines and polygons, and visualize and edit them.
- Setting up scale ranges
LuciadLightspeed now offers an easy way to set up scale ranges for all layer types, especially raster layers. The tutorial Use scale to change layer visibility has been created to help you get started.
- Java 17
LuciadLightspeed runs on Java 17 in compatibility mode.
- Faster 3D Tiles processing
LuciadLightspeed’s 3D tiles processing engine now uses optimized caching, resulting in faster processing.
LuciadLightspeed’s Lucy framework now offers native Lightspeed visualization support for magnetic north models, NITF data, and Polygon files produced by Jeppesen’s TAAM application.