Releases
v0.33.0
0.33.0 (2023-4-6)
editor
added: Editing of 3D LineString geometry is now automatically enforced in 2D only when using 2D styling.
added: The CrossingDetector utility now supports 3D line geometry and automatically switches between 2D and 3D modes based on the style used.
fixed: The crossing tester utility detects too many crossings when used with 3d line geometry.
fixed: Trigger pointerleave events for hovered features currently in submit process can fail
display
improved: Improved rendering of intersecting 3D Icon-styles with transparency
improved: The rendering of lines in 3D space has been improved
added: New ModelStyles have been introduced that allow features to be displayed as 3D models including lighting support.
added: Point and line styles can now be configured whether to scale their size based on the altitude. See: scaleByAltitude
added: Altitude is now taken into account when projecting a geographic coordinate in pixels.
fixed: Pointer events for 3d lines are now triggered correctly in intermediate zoom levels.
fixed: Using range based line styling can, in rare cases, lead to a crash.
fixed: Line ranges can be ignored if the start/end of the range is exactly on a line coordinate.
fixed: If longitude exceeds 180 degrees, an incorrect tile may be displayed.
fixed: Heavy workload/layer-setup may cause collision detection to crash
fixed: Searching for rendered features at a specific pixel will fail if the layers are not explicitly passed
core
fixed: Using custom margin was ignored when set via TileLayer constructor
You can’t perform that action at this time.