Until now "map units" in snapping config dialog actually referred to layer units.
From now on, "map units" refer to project's CRS units. Where appropriate, it is
possible to choose "layer units" that refer to layer CRS units.
Projects from older versions of QGIS should be handled seamlessly (tolerances
in layer units will be still handled in layer units, not project units).
In API, QgsTolerance::MapUnits is deprecated as it is unclear to what units
it refers to (should be ProjectUnits, but actually it is LayerUnits)
xmin and ymin are resevered fieldnames in Postgis, so better not
use these field names. Because this makes it impossible to create
a vector grid and transfer it to Postgis
Instead of calculating feature count (which may add extra overhead),
let's directly try to build index for layers. Only when a certain limit
of features is reached (currently 1 million), the indexing is cancelled
and layer is marked as non-indexable.
*Styled Layer Descriptor profile of the Web Map Service* : DescribeLayer
http://www.opengeospatial.org/standards/sld
Defining a user-defined style requires information about the features being
symbolized, or at least their feature/coverage type. Since user-defined styles
can be applied to a named layer, there needs to be a mechanism by which a
client can obtain feature/coverage-type information for a named layer. This is
another example of bridging the gap between the WMS concepts of layers and
styles and WFS/WCS concepts such as feature-type and coverage layer. To allow
this, a WMS may optionally support the DescribeLayer request.
DescribeLayer method has been thought to be a better approach than overloading
the WMS capabilities document even more.
For each named layer, the description should indicate if it is indeed based on
feature data and if so it should indicate the WFS/WCS (by a URL prefix) and
the feature/coverage types. Note that it is perfectly valid for a named layer
not to be describable in this way.
The offline layers were duplicated, now the automatically inserted one is
removed and only the one at the restored place is preserved.
Followup 46490d4
Before only provider fields where created in the local database while it was
attempted to copy every field in the layer (including virtual fields and
joins) introducing a crash.
This commit itself just removes dead code, but the previous commits bring:
- OTF reprojection support
- use can specify exact tolerance (not just non-sense relative value)
- tolerance can be specified either in map units or layer units
- tolerance settings are stored in settings
- simplify multiple features at once (drag a rectangle instead of just clicking)
- support for multi-part features
- statistics about reduction of the number of vertices
