A WFS request such as
`SERVICE=WFS&REQUEST=GetFeature&VERSION=1.1.0&SRSNAME=EPSG:4326` does
not invert the axis and return the coordinates in the LON/LAT
order. For example:

<gml:Envelope srsName="EPSG:4326">
  <gml:lowerCorner>2.358 48.865</gml:lowerCorner>
  <gml:upperCorner>2.37 48.876</gml:upperCorner>
</gml:Envelope>

However, the same request without a SRSNAME parameter inverts the axis
and returns the the coordinates in the LAT/LON order:

<gml:Envelope srsName="EPSG:4326">
  <gml:lowerCorner>48.865 2.358</gml:lowerCorner>
  <gml:upperCorner>48.876 2.37</gml:upperCorner>
</gml:Envelope>

With this change, the axis is not inverted if the SRSNAME parameter is
not passed. This way, this is the same behavior as
`SRSNAME=EPSG:4326`.

This is a follow-up of qgis#45270.

This fixes UNC paths not identified as network paths.

By ensuring that a trailing slash for directories is passed
down to the identify function.

Bumps [follow-redirects](https://github.com/follow-redirects/follow-redirects) from 1.15.4 to 1.15.6.
- [Release notes](https://github.com/follow-redirects/follow-redirects/releases)
- [Commits](follow-redirects/follow-redirects@v1.15.4...v1.15.6)

---
updated-dependencies:
- dependency-name: follow-redirects
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>

…attempt-2

Browser: fix slow behavior with network drives on windows

qgswfsgetfeature: Do not invert axis if no SRSNAME is passed

The original version number check was completely random numbers

Attempts to set the input band for the renderer.
Returns TRUE if the band was successfully set, or FALSE if the
band could not be set.

This was implemented in various raster renderer subclasses,
but it was necessary to down cast and then call the individual
methods (which don't have consistent names!).

Instead, add a top level virtual method so that it's easy to
change the input band for the renderers.

…t available

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

Just like the equivalent mode for raster layers, this mode indicates
that a fixed constant z range should be applied to the entire mesh
layer.

Use the processing context's ellipsoid instead of a hardcoded
WGS84 ellipsoid for distance calculations during network
analysis, so that the lengths used will exactly match other
measurement tools used on the same features in the same
project.

… display

These buttons actually check or uncheck visibility of the fields, they do not (de)select them in the dialog

Followup qgis#56891

Transform the "Opacity" value calculated by Data Defined Override expression from [0-100] range to [0-1] range.

layers from browser panel

Fixes qgis#56838

…not present in the XML; ask for confirmation before overriding GUI values