This allows provider classes to have a useable elevation properties class, for example to know
if the provided data is 3D or 2D. This will be useful to compute 3D/2D extent.
Allows all layer types (including vector, mesh and point cloud)
providers to show custom metadata in the layer properties dialog.
Previously this was limited to raster/vector tile and tiled
scene layers only.
Also fix const for a lot of raster providers as a consequence.
Allows returned blocks to overlap by the specified number of pixels.
Useful for algorithms which need to consider neighbouring pixels in
a tiled approach, without tile boundary artefacts.
and auto-set the "represents elevation" flag for these
We do this when:
- the layer contains only one band
- the data type is int or float (not complex, rgb or byte)
- the layer doesn't have an attribute table
- there's something "dem-like" in the layer's name (ie 'elevation',
'dem', 'height', 'srtm')
This should help make the elevation profile tool more user-friendly,
as these layers will be included in the profiles by default
elevation related properties to their layers
And use this to ensure that wms tiles with maptiler terrain
or terrarium terrain interpretation are always included by
default in elevation profile plots.
Most specifically, this ensures that projects containing the
out-of-the-box "Mapzen Global Terrain" layer will be automatically
included in elevation plots.
We were cloning the data provider correctly, but doing this on the
main thread means that the provider has thread affinity with the
main thread -- so we need to ensure it is moved over to the
actual rendering thread prior to the rendering.
Fixes#51200 and more small GUI/UX related glitches:
- locale aware double input (consitent behavior with the vector attr
table and the widgets)
- locale aware double formatting (same logic of the vector fields of type double.
- right-alignment of double fields
- wrong tooltip for last column
