A new mention "did not drink during coding" has been recently added to QGIS PR template.
I understand that this has to be considered as a joke. Events like codesprint sometimes include good beer, and I guess this new mention was a kind of private joke with regard to a specific situation.
Offering beer or alcoholic beverage _alongside_ tea, coffee, juices and other alcohol-free beverages is no particular problem.
Meanwhile, I really think we should avoid this kind of reference. IT in general and OpenSource in particular, especially during events, often promote a drinking culture. This is wrong on many aspects. Some cultures ( mainly non-occidental) totally reject alcohol consumption, and we should be respectful for it.
Having a mention referring to alcohol in our PR template is really contradictory to our goal of inclusion and diversity. We should stay vigilant not to propagate a drinking culture which is opposite to our core values. We want to facilitate onboarding to the project, and a PR is one of the important steps converting users to contributors. We should keep it inclusive.
GDAL/OGR has two geojson related drivers now: GeoJSON and
GeoJSONSeq, see https://www.gdal.org/drv_geojsonseq.html
This commit makes it possible to open GeoJSONSeq (geojsonl and
geojsons and json) files as protocols/streams. And write them
as *.json.
These algorithms calculate the boolean OR or AND for a set of input
rasters. For AND, if all of the input rasters have a non-zero value
for a pixel, that pixel will be set to 1 in the output raster, otherwise
it will be set to 0. For OR, if ANY of the input rasters have a non-zero
value for a pixel, that pixel will be set to 1 in the output raster,
else 0.
A reference layer parameter specifies an existing raster layer to use
as a reference when creating the output raster. The output raster will
have the same extent, CRS, and pixel dimensions as this layer
By default, a nodata pixel in ANY of the input layers will result in
a nodata pixel in the output raster. If the 'Treat nodata values
as false' option is checked, then nodata inputs will be treated the
same as a 0 input value.
Makes for much simpler raster boolean logic calculation without
the complexity of using the raster calculator (and that's not
always possible to do anyway, e.g. when ANY of the input rasters
has a nodata pixel). It's also scalable dynamic to any number of
input rasters (unlike raster calc), so is more flexible when
used within models.
The problem was introduced in PR #8828 when fixing issue #20963
This fix immediately deletes terrain entity on generator change
and informs other code about that + identify map tool is now aware
of the fact that terrain entity may be temporarily null.
When a PostGIS table does not have CRS specified (srid == 0) then
it was not possible to correctly load it from browser (but it worked
from DB manager). The problem was that browser item used negative
srid in layer URI, messing up everything.
Also fixed the display of srid in tooltip (it says "unknown" rather
than showing -2147483648)
