59291 Commits

Author SHA1 Message Date
Borys Jurgiel
dbdc397fd8 [DB Manager] Fix broken geometry type of GeoPackage based SQL Layers. Fixes #33232 2019-12-16 10:08:44 +10:00
Nyall Dawson
0d84e35839 Update test images 2019-12-15 10:18:47 +10:00
Nyall Dawson
2e3b57a360 [pal] Don't reuse spatial index for two different purposes
This forces many removals/additions to the existing index, which
we can avoid by just using a seperate index in the first place
2019-12-15 10:18:47 +10:00
Nyall Dawson
1929c53bf4 Avoid some unnecessary heap allocations 2019-12-15 10:18:47 +10:00
Nyall Dawson
c23565287a [pal] Only truncate the feature candidate list after we've pruned all hard conflicts
Avoids throwing away potentially good candidates too early
2019-12-15 10:18:47 +10:00
Nyall Dawson
da5cd52162 [pal] Bring back refined upstream version of superliminal rtree index
Turns out this index is MUCH (magnitudes) faster for use in pal. So
grab an updated version of the upstream library and place in external libs,
and use this for indices in pal.

(we should probably investigate whether this is faster for snapping and
other index use too!)
2019-12-15 10:18:47 +10:00
Alessandro Pasotti
7464290ae3
Merge pull request #33379 from elpaso/widget-dependencies-move-to-formatter
Move layerDependencies to formatter
2019-12-14 09:00:08 +01:00
Nyall Dawson
40b198cf90 Correctly skip ProcessingQgisAlgorithmsTestPt1 on azure builds 2019-12-14 08:21:20 +10:00
Nyall Dawson
db2ac240de Add some references hashes seen on azure builds 2019-12-14 08:20:15 +10:00
Alessandro Pasotti
33b1bec927
Merge pull request #33391 from elpaso/bugfix-gh33390-html-form-wodget-crash
Don't crash on QgsHtmlWidgetWrapper
2019-12-13 22:36:01 +01:00
Alexander Bruy
fba3ab99a0
Merge pull request #33368 from alexbruy/processing-updates
Processing updates
2019-12-13 21:59:08 +02:00
Nyall Dawson
cf95f1452e Fix another test under proj6 2019-12-14 05:33:59 +10:00
Nyall Dawson
da92b3fe8d Fix another test under proj 6 2019-12-14 05:33:59 +10:00
Nyall Dawson
526963efb2 Fix a test under proj 6 2019-12-14 05:33:59 +10:00
Nyall Dawson
05eaa65737 Fix transform differences vs proj < 6 when using custom CRS via proj definition
By being more selective about when we force convert to a single crs

Fixes #32928
2019-12-14 05:33:59 +10:00
Nyall Dawson
9be6b333d0 Fix build 2019-12-14 05:33:59 +10:00
Nyall Dawson
51046d98f6 Fix incorrect reverse coordinate transforms are created when using a
PROJ 6+ build and a project has manual coordinate operation pathways
set

Refs #33121
2019-12-14 05:33:59 +10:00
Nyall Dawson
a1ac77877f Add a method to determine if the coordinate operation string returned
by QgsCoordinateTransformContext.calculateCoordinateOperation corresponds
to the reverse of what's actually required.

Gross API, but it's the best we can do until proj has a method to
invert a coordinate operation so that we can return the proper
inverse operation proj string from calculateCoordinateOperation
(without resorting to fragile proj string parsing/mangling)
2019-12-14 05:33:59 +10:00
Nyall Dawson
ef19797997 Add method to retrieve the details of the coordinate operation which is
actually being used by a QgsCoordinateTransform object
2019-12-14 05:33:59 +10:00
Nyall Dawson
82a84ffd0d Don't try to normalize proj coordinate operations constructed directly
from the proj string via the transform context

This isn't possible -- only proj coordinate operations constructed
from a src/dest CRS pair can be normalized, not those constructed
from a proj string.

It was redundant in any case, since we always normalize the available
operations before giving users a choice of them.

So just add some big bold warnings to the dox in case anyone is
manually manipulating and adding custom operations, that these
also MUST be pre-normalized

Refs #33121, conversation in https://github.com/OSGeo/PROJ/issues/1794
2019-12-14 05:33:59 +10:00
Nyall Dawson
8994a4b994 Update test results for proj < 6 2019-12-14 05:32:55 +10:00
Nyall Dawson
8de83c5133 When saving and restoring CRS definitions to XML, save wkt
definition too, and prefer rebuilding the CRS from the WKT
definition whenever it's available

Proj strings are lossy, so prefer WKT
2019-12-14 05:32:55 +10:00
Peter Petrik
6e2ef1544f push MDAL 0.4.93 RC1 for 3.12 release with fixed bug in reading of reference time 2019-12-14 05:31:53 +10:00
Alessandro Pasotti
0f70637e36 Don't crash on QgsHtmlWidgetWrapper
Fixes #33390
2019-12-13 17:46:02 +01:00
Matthias Kuhn
c2cde01cc8
Merge pull request #33378 from havatv/patch-4
Fix the label of the output parameter of the TPI algorithm
2019-12-13 15:39:33 +01:00
Alessandro Pasotti
a368e4483e Add tests for field formatter dependencies 2019-12-13 13:49:37 +01:00
Alessandro Pasotti
a977343944 Test for relationreference field formatter deps 2019-12-13 13:36:06 +01:00
Peter Petrik
229245ce65 fix building on macos due to missing include of spatialite 2019-12-13 12:56:07 +01:00
Alexander Bruy
ddb93602ef address comments 2019-12-13 13:41:27 +02:00
Matthias Kuhn
6d7c8c2dd3
Merge pull request #33369 from rouault/fix_qgsdxfexport_compilation_error
Fix compilation error in qgsdxfexport.cpp
2019-12-13 12:28:22 +01:00
Alessandro Pasotti
4ad62aa6ff Move layerDependencies to formatter
... from the widget
2019-12-13 11:54:25 +01:00
Håvard Tveite
512eb4d2b8
Fix the label of the output parameter of the TPI algorithm 2019-12-13 11:09:45 +01:00
Even Rouault
2c652040cd
Fix compilation error in qgsdxfexport.cpp
I'm not sure which of QT 5.9.0 or gcc 5.5.0 is not happy, but with both
of them, I get:
```
/opt/qt59/include/QtCore/qflags.h: In instantiation of ‘QFlags<T>& QFlags<T>::setFlag(Enum, bool) [with Enum = QgsDxfExport::DxfPolylineFlag]’:
/home/even/qgis/QGIS/src/core/dxf/qgsdxfexport.cpp:1102:68:   required from here
/opt/qt59/include/QtCore/qflags.h:153:46: error: no match for ‘operator~’ (operand type is ‘QgsDxfExport::DxfPolylineFlag’)
         return on ? (*this |= f) : (*this &= ~f);
```
2019-12-13 10:33:14 +01:00
Alexander Bruy
d167bab49a [processing] optimize random extract algorithm 2019-12-12 19:17:53 +02:00
Alexander Bruy
19596a8f4b [processing] make pole of inaccessibility feature-based 2019-12-12 16:53:11 +02:00
Alexander Bruy
8bc571c51b [processing] make extract vertices feature-based 2019-12-12 16:04:28 +02:00
Alexander Bruy
61032f0eaf [processing] make extract specific vertices feature-based 2019-12-12 15:40:46 +02:00
Sandro Santilli
d20dd06334 Do not convert boolean NULL to false 2019-12-12 14:18:55 +01:00
Sandro Santilli
ae130d84d6 Add test for handling NULL values in PostgreSQL connector
See https://github.com/qgis/QGIS/pull/33225#issuecomment-564446756
2019-12-12 14:18:55 +01:00
Peter Petrik
6febf38e10 [mesh] support active flag capability of MDAL. mesh layers for datasets that does not support active flags should not take less memory and load faster 2019-12-12 08:37:55 +01:00
Peter Petrik
4988468e26 update to MDAL 0.4.92, second beta release for QGIS 3.12. it speeds up and optimize memory usage by allowing QGIS to check if driver/dataset uses active flag or not 2019-12-12 08:37:55 +01:00
Peter Petrik
a9826bbd97 replace averaging widget with something nicer 2019-12-12 08:37:55 +01:00
Alexander Bruy
0219d0019e
Merge pull request #33290 from alexbruy/port-algorithms
[processing] port some algorithms to C++
2019-12-12 08:21:57 +02:00
Nyall Dawson
66fefdc668 Fix warning 2019-12-12 14:44:50 +10:00
Nyall Dawson
bc41f145e1 Fix infinite recursion on proj < 6 builds 2019-12-12 14:44:50 +10:00
Nyall Dawson
b6e46325d3 Fix travis build 2019-12-12 14:44:50 +10:00
Nyall Dawson
de109b67d2 Fix deadlock 2019-12-12 14:44:50 +10:00
Nyall Dawson
187b8f3325 When saving a user crs, if a WKT representation of the CRS is available,
then store and save that

Proj string representations of CRSes are lossy, so we should always prefer
WKT when it's available
2019-12-12 14:44:50 +10:00
Nyall Dawson
4e4cd313bd Add a WKT column to tbl_srs
proj string definitions of CRSes are lossy, so we need to gradually
transition to WKT definitions instead
2019-12-12 14:44:50 +10:00
Nyall Dawson
3d4b5fb09a Don't flag CRSes created from a WKT which doesn't correspond to any
known authorities as invalid

If proj is happy to accept the WKT string, then it's valid
2019-12-12 14:44:50 +10:00