[QGIS-Developer] Plugin [1350] Mascaret approval notification.

2018-01-30 Thread noreply
Plugin Mascaret approval by zimbogisgeek. The plugin version "[1350] Mascaret 0.0.6 Experimental" is now approved Link: http://plugins.qgis.org/plugins/Mascaret/ ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info:

Re: [QGIS-Developer] Get rid of Processing scripts in favour of plain alogrithms

2018-01-30 Thread Victor Olaya
I like the idea, but i dont think it will mean less code, specially for defining the parameters and outputs. Why not keeping it for those that want to use it this way? Before removing this (in case it's decided to do so), two things to notice: -- There were algorithms (built-in ones) defined

Re: [QGIS-Developer] update of otb plugin for QGIS

2018-01-30 Thread Tisham Dhar
Hi Rashad, I meant pre-built OTB binaries rather than plugin binaries. I believe QGIS builds on more platforms than OTB does. Regards, Tisham. From: Rashad Kanavath [mailto:mohammedrasha...@gmail.com] Sent: Tuesday, January 30, 2018 7:45 PM To: Tisham Dhar Cc:

Re: [QGIS-Developer] [Qgis-psc] Commit rights for Luigi Pirelli

2018-01-30 Thread Tim Sutton
MacGyver was working on some commits but ran off to find a rusty nail and seven bottlecaps to improvise an antennae for his failing WIFI connection. Thanks Luigi - I have added you on GitHub and on the committers voting group on Loomio (please check your email for the invitation). Regards Tim

Re: [QGIS-Developer] Get rid of Processing scripts in favour of plain alogrithms

2018-01-30 Thread G. Allegri
I know there are much more important priorities in view of the QGIS 3.0 release. I will try to implement the idea of Geoalgorithms served by the script provider and, in case, I'll commit a PR for testing and comments. Giovanni Il 29 gen 2018 16:44, "Anita Graser" ha scritto:

Re: [QGIS-Developer] How are Featured Plugins Chosen?

2018-01-30 Thread Tobias Wendorff
Hi there, Am Di, 30.01.2018, 18:39 schrieb C Hamilton: > I haven't really monitored > them, but when ever I look they seem like they are about the same set. Interesting question. Many websites advertise the number of downloads, which I consider to be total nonsense. Interesting would be a

[QGIS-Developer] How are Featured Plugins Chosen?

2018-01-30 Thread C Hamilton
I am curious about how he so called Featured Plugins are chosen and I know it is very subjective so I apologize if this is a bad question. I think there are some very good choices on that list and then I think there might be some better choices put on. Do these change? I haven't really monitored

Re: [QGIS-Developer] QGIS3 Plugin debugging help

2018-01-30 Thread Chris Crook
(see nabble link for context) i've run this with a debugger. It does indeed identify the location of the crash as in the matplotlib triangulation function, and specifically within qh_initstatistics which is called to construct the convex hull of the points. Which I guess means there is an issue

[QGIS-Developer] plugin causes 2.99 to crash - help?

2018-01-30 Thread Tom Chadwin
Hello all I'm converting qgis2web for QGIS3, and a lot of the work is done. However, the following steps cause QGIS to crash: 1. start qgis2web (Github master) 2. if Leaflet is selected, click "Update preview", otherwise select Leaflet 3. close the plugin dialog This crashes QGIS (latest

[QGIS-Developer] Should I wait to develop processing routines?

2018-01-30 Thread C Hamilton
I have been seeing the chatter about Processing scripts and plugins. I just released one processing function for my Shape Tools plugin. Based on the possibility that the way processing scripts may be changed, should I hold off in developing further processing routines in my plugins or is this only

Re: [QGIS-Developer] WARNING No QgsCoordinateTransformContext context set for transform

2018-01-30 Thread Denis Rouzaud
Hi, The issue is not PyQGIS but rather unfixed call to QgsCoordinateTransform constructors. See https://github.com/qgis/QGIS/pull/5535 and the "future work" part. According to Nyall, some are quite complex to fix and not in the first priority (like map rendering, copy/paste, etc). Cheers, Denis

Re: [QGIS-Developer] WARNING No QgsCoordinateTransformContext context set for transform

2018-01-30 Thread Mathieu Pellerin
Andreas, I've dealt with two sources of such warnings today, one which caused one warning on every canvas redraw (the north arrow decoration), the other caused many warnings upon (re-)drawing the content of the overview panel. One of the few remaining sources of warnings is with the WMS/XYZ

Re: [QGIS-Developer] QGIS 2.99 weekly snapshot 64 bits

2018-01-30 Thread SIGéal
Thank you for the answer. I am in the process of migrating plugins. I'll try OSGeo4W installer. -- Christophe Le 30/01/2018 à 10:53, Jürgen E. Fischer a écrit : Hi Christophe, On Tue, 30. Jan 2018 at 10:22:05 +0100, SIGéal wrote: It seems that QGIS 2.99 weekly snapshot is only available in

Re: [QGIS-Developer] QGIS3 Plugin debugging help

2018-01-30 Thread Tom Chadwin
Hi Chris Have you attached a debugger, and therefore can you get a backtrace? I think that's what you'll need. Tom - Buy Pie Spy: Adventures in British pastry 2010-11 on Amazon -- Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html

[QGIS-Developer] QGIS3 Plugin debugging help

2018-01-30 Thread Chris Crook
Hi All I am looking for suggestions on how to debug a plugin that is crashing QGIS3 I am trying to port the contour plugin to QGIS3. The port is largely done but there is one outstanding issue that causes QGIS to die. The plugin uses the python matplotlib library to do the contouring. It has

Re: [QGIS-Developer] [Qgis-psc] Bringing back a *highly curated* blocker tag on redmine?

2018-01-30 Thread Daan Goedkoop
Hello Jürgen, apparently the open bugs which are regressions and cause data corruption or crashes are only 10 in number at the moment (of which I reported one). I think they are important because they can catch you by surprise in tested and established workflows. New things will probably only be

Re: [QGIS-Developer] [Qgis-psc] Bringing back a *highly curated* blocker tag on redmine?

2018-01-30 Thread Jürgen E . Fischer
Hi Giovanni, On Tue, 30. Jan 2018 at 09:09:52 +, Giovanni Manghi wrote: > * a regression that causes data corruption > * a regression that causes qgis to crash I still don't understand this obsession with regressions ;) Any bug that is severe should block the release. Whether it's a

Re: [QGIS-Developer] [Qgis-psc] Bringing back a *highly curated* blocker tag on redmine?

2018-01-30 Thread Sandro Santilli
On Tue, Jan 30, 2018 at 09:09:52AM +, Giovanni Manghi wrote: > Examples of what, in my opinion, should be a always a real blocker: > > * a regression that causes data corruption (like the one that caused > to compute wrong area in several 2.* releases) > * a regression that causes qgis to

Re: [QGIS-Developer] Changes to processing gdal:translate?

2018-01-30 Thread Tom Chadwin
Thanks again, Nyall. I'm not confident enough to log these on Redmine, as I've not looked into the Processing code before. Tom - Buy Pie Spy: Adventures in British pastry 2010-11 on Amazon -- Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html

Re: [QGIS-Developer] QGIS 2.99 weekly snapshot 64 bits

2018-01-30 Thread Jürgen E . Fischer
Hi Christophe, On Tue, 30. Jan 2018 at 10:22:05 +0100, SIGéal wrote: > It seems that QGIS 2.99 weekly snapshot is only available in 32 bits > version. > Does anyone know why the 64 bits version isn't available anymore ? It currently exceeds NSIS' 2GB limit (GRASS needs py2 - so we have to

[QGIS-Developer] QGIS 2.99 weekly snapshot 64 bits

2018-01-30 Thread SIGéal
Hi, It seems that QGIS 2.99 weekly snapshot is only available in 32 bits version. Does anyone know why the 64 bits version isn't available anymore ? -- Christophe ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info:

Re: [QGIS-Developer] Last call for switching to github issue tracker

2018-01-30 Thread Tim Sutton
Hi Just as a follow up to this thread, I have started a Loomio vote for QGIS Voters to decide if we should move to GitHub issues. https://www.loomio.org/d/cDwCmhsG/proposal-to-shift-bug-issue-tracking-work-to-github-issues-for-qgis-3x- Regards Tim On Thu, Jan 25, 2018 at 4:29 PM, Jorge

Re: [QGIS-Developer] update of otb plugin for QGIS

2018-01-30 Thread Rashad Kanavath
Hell Tisham, Can you explain the part of binaries issue? The documentation of build from source is already there for OTB. The new module which if merged into Modules/Wrappers/QGIS will be like any other otb module. Since there are no external dependencies, this could be enabled by default. So

Re: [QGIS-Developer] [Qgis-psc] Bringing back a *highly curated* blocker tag on redmine?

2018-01-30 Thread Giovanni Manghi
Hi all, > I think that a carefully used BLOCKER tag makes a lot of sense. > > There are some bugs that we should definitely not be part of a release or > this will seriously impact user's trust in QGIS both as a software and as a > community. > > I also suggest that the ones who take care of the

Re: [QGIS-Developer] update of otb plugin for QGIS

2018-01-30 Thread Rashad Kanavath
On Mon, Jan 29, 2018 at 5:36 PM, Paolo Cavallini wrote: > Il 29/01/2018 16:59, Rashad Kanavath ha scritto: > > (x-post to qgis-developer list) > > > > Hello all, > > > > Here is an RFComments for new otb plugin. > > https://gitlab.orfeo-toolbox.org/jmichel/otb/blob/ >

Re: [QGIS-Developer] [Qgis-psc] Commit rights for Luigi Pirelli

2018-01-30 Thread Luigi Pirelli
Hi community, as requested, I read the requirement for new contributors [1] and I accept and agree with accepting it. I read the three referred documents and I accept and agree with them. Will be an honor to be contributor with Chuck Norris [2]. Has also MacGyver commit right? ;) as requested I

Re: [QGIS-Developer] Bringing back a *highly curated* blocker tag on redmine?

2018-01-30 Thread Alessandro Pasotti
On Tue, Jan 30, 2018 at 12:22 AM, Nyall Dawson wrote: > Hi all, > > I'd like to raise the idea of resurrecting the "blocker" tag on > redmine. I understand the reasons behind its original removal, and > fully agree that the new process is working much better. > > BUT... >