Also there is the new aggregate processing tool that do exactly the same task
than dissolve but with much more powerfull options !
Regards
Dominique
--
Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html
___
QGIS-Developer mai
Hi,
I was also confronted to this weird auto-classification behavior
(https://issues.qgis.org/issues/17102) and it seems it can be tricky to
reproduce.
As I pointed in the issue discussion, it seems to me that classification
should happen only and only if the user explicitly click on the classify
No sadly it only return a QgsAbstractVectorLayerLabeling.
--
Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/
My 2 cents after som testing:
1. I agree with the necessity to consider only the vertices of the selected
feature(s), it's the best way to resolve edition at common boundary. Nyall's
proposed approach seems good to me, otherwise another idea to avoid the
"magic effect": we can just test if the sel
Hi,
Thank you very mutch for this work.
It would be usefull to add an explicit entry for opening non spatial tabular
data like ods, xls or dbf. It's really un-intuitive to add this kind of
datasource by vector dialog and the user needs to control how the first line
will be interpreted (column hea