a layer is loaded which has no CRS
This is the new default behavior. It effectively defers the choice of CRS
from layer loading time to a later time which is convenient for users. E.g.
it no longer asks for CRS choice 100x when loading 100 files into QGIS at once.
(Effectively an application crash/hang... no one will sit through these 100 dialogs!)
The new behavior means there's no prompt (by default!) when loading these layers,
and instead the layers will be shown in the layer tree with an "unknown CRS"
indicator icon. They'll also be un-referenced, with coordinates from the layer
treated as purely numerically, non-earth values. I.e. the same behavior
as all layers get when a project is set to have no CRS.
The user can then resolve these in their own time, and by using convenient
shortcuts like highlighting multiple layers at once and then setting the CRS
for all these in a single action.
Fixes#19762, #27634, #24815 (and probably others)
A reminder for me (from geoserver docs)
The WMS 1.3.0 specification mandates that the axis ordering for geographic coordinate systems defined in the EPSG database be latitude/longitude, or y/x. This is contrary to the fact that most spatial data is usually in longitude/latitude, or x/y. This requires that the coordinate order in the BBOX parameter be reversed for SRS values which are geographic coordinate systems.
Fix some OPENAPI validation issues.
Swagger is happy now, except for the MAP=/...
in the query string: no query string parameters
are allowed in the endpoint, but we can
fix this in the web server configuration.
bookmarks to/from map layers
These algorithms allow users to create a bunch of new bookmarks
corresponding to the features from a layer, or export bookmark
extents to a new polygon layer.
Updated data:
- countries(poly): Admin 0 level boundaries
- states_provinces(poly): Admin 1 level boudnaries
Updated styling:
- disputed_borders(line): Disputed Admin 0 level borders.
New styling to make these borders stand out less.
Attribute tables of all layers contain the name and identification codes fields.
The geometries of of countries and states_provinces has both been processed
from the same source data (NE admin level 1 borders);
Geometries vere generalized and attribute tables were cleaned in order to reduce size.
For the countries layer, attribute table fields have been joined in from the original
admin level 0 dataset.
Data source: Natural Earth 1:10m generalization level, admin level 0 and level 1 datasets
(version 4.1.0)
- countries(poly): Admin 0 level boundaries: Now Correct topology, higher level of detail
- states_provinces(poly): Admin 1 level boudnaries of the top 15 largest countries by area:
Russia, Antarctica, Canada, United States, China, Brazil,
Australia, India, Argentina, Kazakhstan,
Dem. Republic Of Congo, Algeria, Greenland, Mexico, Saudi Arabia
- disputed_borders(line): Disputed Admin 0 level borders
Attribute tables of all layers contain the name and identification codes fields.
Source: Natural Earth 1:10m generalization level - version 4.1.0 datasets.
an array of points
Allows creation of lines from variable numbers of points, and
from sequences from aggregates/dynamically generated sequences
Fixes#31268
Collects a set of geometries into a multi-part geometry object.
Geometry parts can either be specified as seperate arguments to the
function, or (more flexibly), as an array of geometry parts.
This allows geometries to be generated using iterator based approaches,
such as transforming an array generated using generate_series, e.g:
collect_geometries(
array_foreach(
generate_series( 0, 330, 30),
project($geometry, .2, radians(@element))
)
)
Gives a nice radial effect of points surrounding the central feature
point when used as a MultiPoint geometry generator
It's too dangerous to reuse the existing one, as it breaks the
ability to run multiple versions of qgis (i.e. proj < 6 and proj >= 6)
on the same machine
Fixes#30569
Returns a map containing all attributes from a feature, with field
names as map keys. We've got featureful, robust support for working
with maps in expressions now, so this allows rapid conversion
of all feature attributes to a map to use with these handy
functions.
