LuciadRIA was released in 2012 with a 2D map based on a HTML5 Canvas. In 2016, a 2D/3D map was introduced that takes advantage of the hardware acceleration available in most browsers.
Moving forward, our focus solely lies with the hardware-accelerated RIAMap. It offers all the capabilities of a non-hardware-accelerated Map, and brings much more to the table.
This document explains how we are phasing out the non-hardware-accelerated map, and how you can easily modify your application
to use the RIAMap.
Phasing out the non-hardware-accelerated Map
The non-hardware-accelerated Map was deprecated with LuciadRIA 2024.0.
The 2025.0 release was the last release supporting it. In LuciadRIA 2026.0, we removed the non-hardware-accelerated Map.
All maps are now hardware-accelerated.
Switching to RIAMap in your application
You can switch to RIAMap by changing the constructor call of your Map.
-
If you’re using LuciadRIA 2026.0 or later, replace:
import {Map} from "@luciad/ria/view/Map.js"; const map = new Map(domNode, options);with:
import {RIAMap} from "@luciad/ria/view/RIAMap.js"; const map = new RIAMap(domNode, options); -
If you’re using LuciadRIA 2025.0 or earlier, replace the usage of
Mapwith:import {WebGLMap} from "@luciad/ria/view/WebGLMap.js"; const map = new WebGLMap(domNode, options);
The RIAMap API is a superset of the Map API, so no further changes are necessary.
See LuciadRIA benefits for the features available to you when you use RIAMap.
You can find the WebGPU system requirements here.
|
We plan to keep the |
Upgrade considerations
For completeness, we list the upgrade considerations:
-
If you’re making heavy use of complex stroking (
ComplexStrokedLineStyle) or tactical graphics in your application, it might take longer for those strokes to appear on the map the first time. This happens because every stroke results in a new shader being compiled. To remedy it, you can implement the tips outlined in the Boosting tactical graphics performance on a RIAMap article. -
GoogleLayeris no longer part of the API as of LuciadRIA 2026.0. Instead, you can use Google Maps, HERE Maps, Bing Maps, OpenStreetMap, or any other background layer. Also consider showing Google 3D Tiles as an alternative. -
It’s recommended to use a
RasterImageLayeron a 2DRIAMaponly. On a 3D map, the visualization may appear to have a low resolution. Consider replacing usages ofRasterImageLayerandRasterImageModelwith aRasterTileSetLayerandRasterTileSetModel. For example, replaceWMSImageModelwithWMSTileSetModel.
Aside from the items listed above, RIAMap supports everything that a Map could do, and more.
If you have any questions or feedback, please contact the Luciad Product Management team at product.management.gsp@hexagon.com.