[QGIS-Developer] Plugin [1066] Isogeo approval notification.

Plugin Isogeo approval by zimbogisgeek. The plugin version "[1066] Isogeo 1.6.0-beta2 Experimental" is now approved Link: http://plugins.qgis.org/plugins/isogeo_search_engine/ ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: http

[QGIS-Developer] Plugin [1086] SEC4QGIS approval notification.

Plugin SEC4QGIS approval by zimbogisgeek. The plugin version "[1086] SEC4QGIS 1.0.5" is now approved Link: http://plugins.qgis.org/plugins/SEC4QGIS/ ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman

[QGIS-Developer] Plugin [1246] go2mapillary approval notification.

Plugin go2mapillary approval by zimbogisgeek. The plugin version "[1246] go2mapillary 1.3" is now approved Link: http://plugins.qgis.org/plugins/go2mapillary/ ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.o

[QGIS-Developer] Plugin [1102] AequilibraE approval notification.

Plugin AequilibraE approval by zimbogisgeek. The plugin version "[1102] AequilibraE 0.3.5.9" is now approved Link: http://plugins.qgis.org/plugins/AequilibraE/ ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.

[QGIS-Developer] Plugin [1356] ZoomToBelgium approval notification.

Plugin ZoomToBelgium approval by zimbogisgeek. The plugin version "[1356] ZoomToBelgium 0.1.1 Experimental" is now approved Link: http://plugins.qgis.org/plugins/ZoomToBelgium/ ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: htt

[QGIS-Developer] Flaky tests

Hi, I've had a hard time today with a pull request that changed only some python test code, but failures occuring in totally unrelated tests. I had to restart Travis-CI 5 times before it was green. Had similar issue with another PR The various failures I got : 3 times: 359 - PyQgsFil

Re: [QGIS-Developer] QgsServer and 3d tiles

Hello, On 03/11/2017 21:04, G. Allegri wrote: > What if we had a QgsServer service dedicates to serving 3d tiles for > Cesium or iTowns? > Is anybody working on this? At Oslandia, we work on 3D topics a lot, and 3d tiles in particular. We are implementing 3D Tiles support in iTowns, and several c

Re: [QGIS-Developer] QgsServer and 3d tiles

Hi Vincent, I agree tiled static data can, and should, be served as static content but what I meant was having something like Tilestache, GeoWebCache, MapCache, etc.. They're meant to render and cache on the fly, or preseeding the tileset. My question raised from the fact that QGIS 3D renderer cou

Re: [QGIS-Developer] Flaky tests

I don't know if it's related, but I've had real problems over the last two or three weeks with Travis tests for a Python plugin. Tests which use an external resource (a remote WFS) tend to work in the morning (GMT), but fail in the afternoon. I'm also getting segfaults which I hardly ever get (and

[QGIS-Developer] Convert from mapunits to pixels

Hello all I've never implemented support of any unit other than pixels in my plugin. A particular use case (vector tiles) could really use mapunits. Can someone explain (or point me towards) the method for converting from mapunits to pixels for on-screen rendering? Thanks Tom - Buy Pie Sp

Re: [QGIS-Developer] Flaky tests

PyQgsLocator is failing 50% of the times for me. Recently I've been lucky with the others. On Thu, Nov 9, 2017 at 4:24 PM, Even Rouault wrote: > Hi, > > > > I've had a hard time today with a pull request that changed only some > python test code, but failures occuring in totally unrelated test

Re: [QGIS-Developer] Flaky tests

Hi Even, Yes, despite things settling again I experienced the same/similar issues. I can confirm the issues with the spatialite and the locator test. I am in favor of disabling (parts of) these, since they do more damage than good in their current state. This will be much appreciated To avoid th

[QGIS-Developer] pyqgis ImportError: DLL load failed: ─ίΊ ▐ΪάΊ ϊΫΊάΪⁿ Ίά ίΊΪΎΏώ≤Ϊί▀ ύ ΆάϋΎ±ώ≤Ή▌Ίύ ΈίώΪ

I try I create a pyqgis standalone script in windows 10 but I have some errors first I have read this post and I follow comment of Mr.caiohamamura but I have semi success I think,a

[QGIS-Developer] pyqgis ImportError: DLL load failed: ─ίΊ ▐ΪάΊ ϊΫΊάΪⁿ Ίά ίΊΪΎΏώ≤Ϊί▀ ύ ΆάϋΎ±ώ≤Ή▌Ίύ ΈίώΪ

I try I create a pyqgis standalone script in windows 10 but I have some errors first I have read this post and I follow comment of Mr.caiohamamura but I have semi success I think,a

[QGIS-Developer] Handy methods to Copy/Paste Features via QgisInterface

Hi qgis-devs, what do you think about exposing methods to copy/paste features from/to *given layers* through QgisInterface? Such methods are available in qgisapp.cpp already [1], but plugin devs cannot access them. What is exposed right now are the actionCopyFeatures and actionPasteFeatures, whi

[QGIS-Developer] Python error on start up from GRASS processing

Hi Its great to see the GRASS stuff merged now. However it gives me an error on startup: An error has occurred while executing Python code: TypeError: QgsProcessingAlgorithm.addParameter(): argument 1 has unexpected type 'ParameterRaster' Traceback (most recent call last): File "/Users/tim

Re: [QGIS-Developer] Python error on start up from GRASS processing

On 09-11-17 20:28, Tim Sutton wrote: > Does anyone else get this? > Yep, confirmed here Richard ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists

Re: [QGIS-Developer] Python error on start up from GRASS processing

Le 2017-11-09 20:28, Tim Sutton a écrit : Hi Its great to see the GRASS stuff merged now. However it gives me an error on startup: An error has occurred while executing Python code: TypeError: QgsProcessingAlgorithm.addParameter(): argument 1 has unexpected type 'ParameterRaster' Traceback (m

[QGIS-Developer] Crashes in qgsogrfeatureiterator.cpp:52 on master

Hi all (specifically bugfixing devs) While doing a bunch of mapping tasks yesterday on master (i.e. being a QGIS user, not a developer!) I hit a bunch of frequent crashes on Windows. Nathan's awesome crash report tool identified the issue as occurring at qgsogrfeatureiterator.cpp:52. Looking into

[QGIS-Developer] discuss: What's our development gameplan for 3.0 and above?

Hi all, I started a discussion at https://github.com/qgis/QGIS/pull/5559#issuecomment-342974170 but I'd like greater exposure for this discussion and more feedback, so that together we can determine what our preferred development approach is for 3.0 and up. The question is: Is it our prefer

Re: [QGIS-Developer] Python error on start up from GRASS processing

Hi Thanks Médéric - cleaning out my build dir fixed the issue. Regards Tim > On 09 Nov 2017, at 22:18, Médéric Ribreux wrote: > > Le 2017-11-09 20:28, Tim Sutton a écrit : >> Hi >> Its great to see the GRASS stuff merged now. However it gives me an >> error on startup: >> An error has occurre

Re: [QGIS-Developer] Crashes in qgsogrfeatureiterator.cpp:52 on master

On vendredi 10 novembre 2017 07:24:09 CET Nyall Dawson wrote: > Hi all (specifically bugfixing devs) > > While doing a bunch of mapping tasks yesterday on master (i.e. being a > QGIS user, not a developer!) I hit a bunch of frequent crashes on > Windows. Nathan's awesome crash report tool identifi

Re: [QGIS-Developer] Crashes in qgsogrfeatureiterator.cpp:52 on master

On jeudi 9 novembre 2017 23:07:11 CET Even Rouault wrote: > On vendredi 10 novembre 2017 07:24:09 CET Nyall Dawson wrote: > > Hi all (specifically bugfixing devs) > > > > While doing a bunch of mapping tasks yesterday on master (i.e. being a > > QGIS user, not a developer!) I hit a bunch of freque

Re: [QGIS-Developer] discuss: What's our development gameplan for 3.0 and above?

Having suffered at the hands of the QtWebkit thing, I would strongly agree, though I guess one airways needs to evaluate the health of any dependency - perhaps the are instances where a Qt class is better maintained than the alternatives. Tom - Buy Pie Spy: Adventures in British pastry 201

Re: [QGIS-Developer] Crashes in qgsogrfeatureiterator.cpp:52 on master

On 10 November 2017 at 08:24, Even Rouault wrote: > Digging further this code comes from the dev branch of qt5: > https://github.com/qt/qtbase/blob/dev/src/corelib/thread/qsemaphore.cpp#L414 > > Released branches use a different logic: > https://github.com/qt/qtbase/blob/5.10/src/corelib/thread/q

Re: [QGIS-Developer] Crashes in qgsogrfeatureiterator.cpp:52 on master

On vendredi 10 novembre 2017 08:41:53 CET Nyall Dawson wrote: > On 10 November 2017 at 08:24, Even Rouault wrote: > > Digging further this code comes from the dev branch of qt5: > > https://github.com/qt/qtbase/blob/dev/src/corelib/thread/qsemaphore.cpp#L4 > > 14 > > > > Released branches use a d

Re: [QGIS-Developer] Crashes in qgsogrfeatureiterator.cpp:52 on master

> and this should occur also on any platform running qt 5.9 QT bug filed per https://bugreports.qt.io/browse/QTBUG-64413 -- Spatialys - Geospatial professional services http://www.spatialys.com ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo

Re: [QGIS-Developer] discuss: What's our development gameplan for 3.0 and above?

Hey, Personally, I like using the database wrapper that Qt provide and I don't really see much risk in using it, to be honest. We might get better speeds going to std route which is something to consider but I prefer an easier API over raw speed unless it's massive speed up. Ideally, we really ne

Re: [QGIS-Developer] Crashes in qgsogrfeatureiterator.cpp:52 on master

On 10 November 2017 at 09:02, Even Rouault wrote: >> and this should occur also on any platform running qt 5.9 > > > > QT bug filed per > > https://bugreports.qt.io/browse/QTBUG-64413 Fantastic work... I'm thinking the Qt project should contract you to review their codebase! PR for QGIS at https

Re: [QGIS-Developer] discuss: What's our development gameplan for 3.0 and above?

On 10 November 2017 at 07:29, Nyall Dawson wrote: > Is it our preference to use Qt classes and methods wherever available, > or should we use std algorithms or raw library methods instead? On a related note, I'd encourage any QGIS dev to watch KDAB's "Effective Qt (2017 edition)" presentation:

Re: [QGIS-Developer] discuss: What's our development gameplan for 3.0 and above?

super +1, I follow the same rule. We should add rule for that methods that require pyqt bindings... e.g. any API should use and return QT containers (just to simplify type mapping) Luigi Pirelli ** * Bo

[QGIS-Developer] Maintainer for qgsrasterprojector.cpp

Hi All, I have made a small UI change to add bilinear as a reprojection option when sawing raw rasters to file (particularly with reprojection). I am adding bilinear reprojection code to "qgsrasterprojector.cpp" block method , sampling surrounding row/columns in the source raster in addition to

[QGIS-Developer] Plugin [1341] AGRC Geocoding Toolbox approval notification.

Plugin AGRC Geocoding Toolbox approval by zimbogisgeek. The plugin version "[1341] AGRC Geocoding Toolbox 1.0.0" is now approved Link: http://plugins.qgis.org/plugins/AGRCGeocodingToolbox/ ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org Li

Re: [QGIS-Developer] discuss: What's our development gameplan for 3.0 and above?

Very interesting presentation! Thanks for sharing. One question: how would SIP behave with STL containers if we decide to use them instead of Qt containers? On Fri, Nov 10, 2017 at 12:22 AM, Nyall Dawson wrote: > On 10 November 2017 at 07:29, Nyall Dawson wrote: > > > Is it our preference to u