Closed
Conversation
This introduces a new option for specifying how raster layers have associated elevation. It permits a fixed elevation range to be set for the layer. It can be used when the layer has a single fixed elevation, or a range (slice) of elevation values. Users can set the lower and upper elevation range for the layer, and whether the lower or upper limits are inclusive or exclusive. When enabled, the layer will only be visible in elevation filtered 2d maps when the layer's range is included in the map's z range.
Allows forcing the widget to have a specific fixed range width, so that interactions with the lower or upper slider automatically force the other slider to move to keep a constant width
This ensures that the labels don't overlap when the selected range is narrow
This adds a new option to the configure menu for the elevation controller, for setting a fixed elevation slice width. It can be used when a specific elevation range width is desired, or when the range should always be zero width.
In this mode, each band in the raster can have a fixed elevation range associated with it. This is designed for data sources which expose elevation related data in bands, eg netcdf files, such as a raster with temperate data at different ocean depths.
This is exposed as a user editable table of raster bands with lower and upper values. Users can either populate the lower and upper values manually, or use an expression to auto fill all band values based on a qgis expression. The expression based fill allows for users to design expressions which extract useful information from band names, eg extracting the depth value from a "Band 001: depth=-5500 (meters)" style band name.
And selectively expose some of QgsRasterRendererRegistry to python
has a multi-band renderer set
When 'canRead' property for a published WFS layer was set to False from an access control filter plugin the whole /collections reques was returning a 404 insted of returning the list of published layers (minus the filtered ones).
…rmissions Server/OAPIF: fix unreported issue with access control layer permissions
[qml] Add a couple of Q_INVOKABLE in QgsProject and QgsVectorLayer to ease layer and feature fetching + editing
Note that not all fonts available from Google fonts are present on the github repo for some reason, eg Open Sans Condensed is not. Fixes qgis#57070
Instead of "", ensure the actual filename (or tab title, for unsaved scripts) is shown in exceptions
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.