Re: [QGIS-Developer] [Qgis-psc] 2019 Grant Final reports: Rendering optimisation and labeling work
On Tue, 3 Dec 2019 at 22:27, Régis Haubourg wrote: > > Hi, > Nyall, this is awesome work! Thanks a lot for this. > > I checked the daily performance tests for QGIS server available at > http://test.qgis.org/perf_test/graffiti/aggregate/aggregate.html and couldn't > see clear influence. > Do you have ideas of tests we could add to this framework? If you're checking nightly releases, you'd need to track back a couple of months to before the work began in order to compare (since the changes have been drip fed in over a couple of months). Or alternatively you could compare against a 3.6 build (since many of the optimisations were backported to 3.4 and 3.8/3.10). Nyall > > Cheers > Régis > > > Le mar. 3 déc. 2019 à 08:43, Anita Graser a écrit : >> >> Thank you for the detailed report and the excellent work, Nyall! >> I'm looking forward to testing it by upgrading some projects to the new >> labeling. >> >> Anita >> ___ >> QGIS-Developer mailing list >> QGIS-Developer@lists.osgeo.org >> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer >> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
[QGIS-Developer] Plugin [1902] Azure Maps approval notification.
Plugin Azure Maps approval by pcav. The plugin version "[1902] Azure Maps 0.1 Experimental" is now approved Link: http://plugins.qgis.org/plugins/QGISPlugin/ ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
[QGIS-Developer] Plugin [1856] ESTIMAP Recreation approval notification.
Plugin ESTIMAP Recreation approval by pcav. The plugin version "[1856] ESTIMAP Recreation 1.4 Experimental" is now approved Link: http://plugins.qgis.org/plugins/natcapes_qgis-master/ ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
[QGIS-Developer] Plugin [565] Zoom to Paste approval notification.
Plugin Zoom to Paste approval by pcav. The plugin version "[565] Zoom to Paste 3.0.2" is now approved Link: http://plugins.qgis.org/plugins/zoomtopaste/ ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] BWTA2017 grid support in QGIS >= 3.10
@Even Rounault: thanks for this info. Then I guess we'll see the BWTA2017 support in 3.10.3 in the mid of january... keeping fingers crossed :-) Am Di., 3. Dez. 2019 um 15:06 Uhr schrieb Even Rouault < even.roua...@spatialys.com>: > > @Jürgen Fischer: is there a change that you could "cherry-pick" the > > corresponding pull requests and patch them into the existing PROJ release > > used by osgeo4w for the upcoming pointrelease? > > Just wants to note that a PROJ 6.3.0 release, with the > accompanying proj-datumgrid- backages, is scheduled for the beginning > of > January. > > Even > > > -- > Spatialys - Geospatial professional services > http://www.spatialys.com > ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] BWTA2017 grid support in QGIS >= 3.10
> @Jürgen Fischer: is there a change that you could "cherry-pick" the > corresponding pull requests and patch them into the existing PROJ release > used by osgeo4w for the upcoming pointrelease? Just wants to note that a PROJ 6.3.0 release, with the accompanying proj-datumgrid- backages, is scheduled for the beginning of January. Even -- Spatialys - Geospatial professional services http://www.spatialys.com ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
[QGIS-Developer] BWTA2017 grid support in QGIS >= 3.10
Hello QGIS-devs, in QGIS2 and QGIS-3 versions with proj<6 there was a support for the BWTA2017.gsb-gridfile which is needed in the state Baden-Württemberg ( https://en.wikipedia.org/wiki/Baden-W%C3%BCrttemberg ) in southwest germany to transform between the former official crs EPSG31467 and the new one EPSG25832: https://github.com/qgis/QGIS/pull/6980 For some time there was an issue about including the BWTA in the proj-datumgrid. https://github.com/OSGeo/proj-datumgrid/issues/22 The main reason why QGIS 3.10/proj6 cannot use the BWTA2017.gsb is that it is not referenced in the EPSG registry so far but I will get in contact with the LGL (www.lgl-bw.de) to ask them if they can make a changerequest on http://www.epsg.org/EPSGDataset/Makechangerequest.aspx For the meantime there are two pull requests which have been merged today: https://github.com/OSGeo/proj-datumgrid/pull/65 and https://github.com/OSGeo/PROJ/pull/1759 ( Even Rouault:"...As EPSG has no entry for it, we create a grid_transformation, as well as a dedicated area of use based on the extent of the grid, under the PROJ authority. With the hope to be able to remove it once EPSG has an entry...") @Jürgen Fischer: is there a change that you could "cherry-pick" the corresponding pull requests and patch them into the existing PROJ release used by osgeo4w for the upcoming pointrelease? regards, Thomas ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] QGIS & PROJ 6 & SAGA
вт, 3 груд. 2019 о 14:07 Giovanni Manghi пише: > Said that if the "official" way to support SAGA would be a plugin it > would be much easier to implement and distribute/update such changes. If I recall correctly this was discussed a lot in the mailing lists before 3.0 release and most developers involved into Processing support was agains keeping SAGA and adding any new providers while some community members were pushing hard to keep them. Final decision at the Madeira meeting was to keep SAGA and include OTB with one of the arguments that this way it will be easier for community to maintain them. Now we have SAGA in core and at least 2 plugins for SAGA and very little (I'd even say zero) community involvement in any of them. Do we really want to restart this discussion? I don't think that two involved parties have changed their mind. Also it is probably too early as no breaking changes can be made before 4.0 and even if we make a decision now it anyway very likely will be revised again before release as it happened last time. -- Alexander Bruy ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] [Qgis-psc] 2019 Grant Final reports: Rendering optimisation and labeling work
Hi, Nyall, this is awesome work! Thanks a lot for this. I checked the daily performance tests for QGIS server available at http://test.qgis.org/perf_test/graffiti/aggregate/aggregate.html and couldn't see clear influence. Do you have ideas of tests we could add to this framework? Cheers Régis Le mar. 3 déc. 2019 à 08:43, Anita Graser a écrit : > Thank you for the detailed report and the excellent work, Nyall! > I'm looking forward to testing it by upgrading some projects to the new > labeling. > > Anita > ___ > QGIS-Developer mailing list > QGIS-Developer@lists.osgeo.org > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] QGIS & PROJ 6 & SAGA
Hi, > Not to forget, that SAGA GIS evolves very fast. There are several new, > modern algorithms from version to version in the codebase. Normally, > these new algorithms work as expected out of the box (within SAGA GIS). > If not, the small core team find a solution within hours, at least > within a few days. yes of course, but this has proven to be very hard for us to keep this pace within QGIS, especially when in SAGA fundamental modules like io_gdal change parameters names without keeping retro-compability with previous releases. Also modules change name frequently from one release to another (as also their parameters). This is the main reason we decided to stop trying support every latest release and so stick with the LTR one. Said that if the "official" way to support SAGA would be a plugin it would be much easier to implement and distribute/update such changes. cheers -- G -- ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
[QGIS-Developer] QgsRendererPropertiesDialog crashes external python application
I have an external windows standalone python application that uses pyqgis.
When I display a QgsRendererPropertiesDialog, python crashes when the user
clicks on any color button (screenshot: http://psr.me/1903oq2). The problem
seems to be in displaying the color dialog. In previous QGis versions I
could avoid this problem by using:
settings = QgsSettings()
settings.setValue('qgis/native_color_dialogs', True)
QGis then used another color dialog that did not crash my application.
However, since I updated to QGis 3.8.3 (OSGEO4W) this option no longer
works. Apparently this option has been removed.
I also noticed that QGis uses a color dialog different from the one that
appears in my application. How can I configure my application (from pyqgis)
to use the same dialog?
I wrote a very small PyQt5 application (below, at the end) that reproduces
the problem. Any thoughts on how to fix this?
Operating system: Windows 10 Home
Python version: 3.7.0 (OSGEO4W)
QGis version: 3.8.3 (OSGEO4W)
Thanks,
Marcelo Metello
from qgis.core import QgsVectorLayer, QgsStyle
from qgis.gui import QgsRendererPropertiesDialog
from PyQt5 import QtCore, QtWidgets
def editStyle():
layer = QgsVectorLayer('LineString?field=level:integer',
'contour_lines', 'memory')
dialog = QtWidgets.QDialog()
layout = QtWidgets.QVBoxLayout(dialog)
# Add symbology panel
symbPanel = QgsRendererPropertiesDialog(layer, QgsStyle.defaultStyle(),
True)
layout.addWidget(symbPanel)
# Add Ok Cancel button box
buttonBox = QtWidgets.QDialogButtonBox(QtWidgets.QDialogButtonBox.Ok |
QtWidgets.QDialogButtonBox.Cancel, QtCore.Qt.Horizontal, dialog)
buttonBox.button(QtWidgets.QDialogButtonBox.Ok).setText('Ok')
buttonBox.button(QtWidgets.QDialogButtonBox.Cancel).setText('Cancel')
buttonBox.accepted.connect(dialog.accept)
buttonBox.rejected.connect(dialog.reject)
layout.addWidget(buttonBox)
dialog.setLayout(layout)
dialog.adjustSize()
if (dialog.exec_() == QtWidgets.QDialog.Accepted):
symbPanel.apply()
# Create simple application with only one button
app = QtWidgets.QApplication([])
window = QtWidgets.QWidget()
layout = QtWidgets.QVBoxLayout()
editBtn = QtWidgets.QPushButton('Edit Style')
editBtn.clicked.connect(editStyle)
layout.addWidget(editBtn)
window.setLayout(layout)
window.show()
app.exec_()
app.exit()
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
[QGIS-Developer] Problems in running OTB
Hi all, OTB algs apparently do not work on QGIS 3.10 out of the box: * if a raster output is not explicitly selected I get an error: “.raster.out.tif” files are not supported as outputs for this algorithm * if a vector output is not explicitly selected (with filename.ext) I get another error: 2019-12-03 12:30:43 (FATAL) Segmentation: itk::ERROR: No OGR driver known to OTB to create and handle a DataSource named . If confirmed I can open two tickets. Additionally (but this must be done by OTB itself, nothing to do with QGIS): ERROR 1: TopologyException: Input geom 1 is invalid: Ring Self-intersection at or near point 1651438.0098749998 4818821.1863940004 at 1651438.0098749998 4818821.1863940004 Cheers. -- Paolo Cavallini - www.faunalia.eu QGIS.ORG Chair: http://planet.qgis.org/planet/user/28/tag/qgis%20board/ ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] shp file from /tmp file are seen as memory-layers?
On Tue, Dec 3, 2019 at 10:58 AM Richard Duivenvoorde wrote: > On 03/12/2019 09.50, Nyall Dawson wrote: > >> Is this by design? Or is it a bug because there is 'tmp' in the path? > >> I tested also to put it in ~/tmp but then it is OK... > > > By design -- it was added because many of the processing providers > > which rely on 3rd party utilities (e.g. grass, saga) put temporary > > outputs there, and users weren't getting any warnings that these are > > just temporary. Basically the warning which previously showed only for > > memory layers has been extended to include anything inside the > > operating system's temporary folder (i.e. /tmp, but not ~/tmp on > > Linux). > > Ah, thanks Nyall. I understand the reasoning, and agree... > > Though it does not feel as perfect yet: > > The memory tooltip of this layer says: > "Temporary Layer Only. Contents will be discarded after closing QGIS" > But compared to a real memory layer, it is still there if you reopen the > project (or quit/open QGIS). > So it seems we mix two concepts? > > Thinking out loud here, I know this will all cost time/energy, so I > understand if this is ignored... > > What about leaving out the 'memory' icon, and only warn users IF they > have layers in temporary places? And instead of: > "This project includes one or more temporary layers. These layers are > not permanently saved and their contents will be lost. Are you sure you > want to proceed?" > Something like: > "This project includes one or more layers which are saved in temporary > directories". If you want to keep that data, please save or copy the > data to non-temporary dirs" ? > > Or as bonus: maybe thing of some icon for these processing output > layers: maybe the little 'gear'-icon we use for processing? > In the case of a processing output I will then see the little gear icons > (AND get the warning). > In my usecase I will only get the warning (and I will ignore it :-) ) > > As said: I understand there are probably more important things to do, > just wanted to think about it a little... > > Regards, > > Richard Duivenvoorde > > Hi Richard, I agree with you that in-memory layer and file-based layers stored in temporary folders are two different things and we should try to not mix the concepts. >From a UX perspective they both deserve a warning/icon that reminds the user that they will be eventually lost if not action is taken, we just need to make sure that the user understands the difference. I'd open a question dialog in both cases when the layers are unloaded but I would choose a (slightly?) different icon to mark the memory and tmp layers and certainly a different tooltip message. Cheers -- Alessandro Pasotti w3: www.itopen.it ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] shp file from /tmp file are seen as memory-layers?
On 03/12/2019 09.50, Nyall Dawson wrote: >> Is this by design? Or is it a bug because there is 'tmp' in the path? >> I tested also to put it in ~/tmp but then it is OK... > By design -- it was added because many of the processing providers > which rely on 3rd party utilities (e.g. grass, saga) put temporary > outputs there, and users weren't getting any warnings that these are > just temporary. Basically the warning which previously showed only for > memory layers has been extended to include anything inside the > operating system's temporary folder (i.e. /tmp, but not ~/tmp on > Linux). Ah, thanks Nyall. I understand the reasoning, and agree... Though it does not feel as perfect yet: The memory tooltip of this layer says: "Temporary Layer Only. Contents will be discarded after closing QGIS" But compared to a real memory layer, it is still there if you reopen the project (or quit/open QGIS). So it seems we mix two concepts? Thinking out loud here, I know this will all cost time/energy, so I understand if this is ignored... What about leaving out the 'memory' icon, and only warn users IF they have layers in temporary places? And instead of: "This project includes one or more temporary layers. These layers are not permanently saved and their contents will be lost. Are you sure you want to proceed?" Something like: "This project includes one or more layers which are saved in temporary directories". If you want to keep that data, please save or copy the data to non-temporary dirs" ? Or as bonus: maybe thing of some icon for these processing output layers: maybe the little 'gear'-icon we use for processing? In the case of a processing output I will then see the little gear icons (AND get the warning). In my usecase I will only get the warning (and I will ignore it :-) ) As said: I understand there are probably more important things to do, just wanted to think about it a little... Regards, Richard Duivenvoorde ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] shp file from /tmp file are seen as memory-layers?
On Tue, 3 Dec 2019 at 18:43, Richard Duivenvoorde wrote: > > Hi, > > Wanting to test something temporarily, I copy an (arbitrary) shp file to > my /tmp dir (on Linux). > > I open the shp file (via the Data Source Manager) and browse/open the > shp in the /tmp dir. > > The shp opens fine, BUT in the layermanager I see the little 'memory' > icon, as if this is a memory layer?? > > Also: if I try to close the project (after or before saving it), I get > the warning "This project includes one or more temporary layers. These > layers are not permanently saved and their contents will be lost. Are > you sure you want to proceed?" > > Strangely, if I reopen a saved project, the shp (as memory layer) is > opened fine. > > BUT... these are not really temporary layers.. these are real shapes > (well, in my /tmp dir, but... as long as I do not restart they are there > and should work... I think). > > Is this by design? Or is it a bug because there is 'tmp' in the path? > I tested also to put it in ~/tmp but then it is OK... By design -- it was added because many of the processing providers which rely on 3rd party utilities (e.g. grass, saga) put temporary outputs there, and users weren't getting any warnings that these are just temporary. Basically the warning which previously showed only for memory layers has been extended to include anything inside the operating system's temporary folder (i.e. /tmp, but not ~/tmp on Linux). Nyall > > Regards, > > Richard Duivenvoorde > ___ > QGIS-Developer mailing list > QGIS-Developer@lists.osgeo.org > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
