Re: [QGIS-Developer] [Qgis-psc] QGIS 2.18 EOL approaching?

[Filipe Dias]

Hi,

After QGIS 2.18 reaches EOL are there any plans to keep it available in a
repository or via flatpak/snap app? I have moved to QGIS 3 but I still have
to maintain QGIS 2.18 projects that are connected to Lizmap. Currently, I
switch back and forth between versions using the official repositories, but
once 2.18 reaches EOL, I'm guessing that will no longer be possible.

Cheers
F

On Fri, Dec 28, 2018 at 7:46 AM Paolo Cavallini 
wrote:

> Hi Nyall, others
>
> On 27/12/18 22:58, Nyall Dawson wrote:
> > On Thu, 27 Dec 2018 at 18:42, Paolo Cavallini 
> wrote:
> >
> >> From another standpoint, we still have 102 Q3 regressions:
> >> https://issues.qgis.org/projects/qgis/issues?query_id=27
> >> From a quick scroll, I suspect at least some of them are not
> >> particularly relevant, but a thorough analysis is needed.
> >
> > Yeah, a quick flick through revealed a very mixed lot -- many sound
> > familiar and likely have already been fixed, some I know are still
> > outstanding, and many waiting feedback for too long and should be just
> > closed.
>
> I think a triaging would be useful here to have a more accurate picture.
> Anyone willing to do it and report back?
> >
> > I guess my question is (if we do delay the 2.x EOL as a result of
> > these) is how many regressions are "acceptable" before EOL? We'll
> > never get this to 0 -- there's been too many "by design" changes to
> > make a zero regression target feasible (See obligatory xkcd ref:
> > https://xkcd.com/1172/).
> >
> >> I'm not sure whether it will be acceptable for our users to release an
> >> LTR with these regression, but this could be a way of putting pressure
> >> on donors to help us fix them.
> >
> > Big +1 to this. If I'm being blunt, I think if a bug is a blocker to
> > an organisation moving to 3.4, it's ultimately going to sit with them
> > to get it fixed (or to sponsor QGIS and support the funded bug hunts).
> > (Or, perhaps, in the case of regressions in features an organisation
> > originally funded -- it's their responsibility to put pressure on the
> > original developer they paid for the feature to fix it and protect it
> > with suitable unit tests -- but that's between them and their original
> > developer).
>
> Agreed. It's a matter of communicating properly to users. We have time
> to write a blog post and circulating it well before EOL.
> Thanks.
>
> --
> 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
___
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 with ubuntgis dependancy broken

[Filipe Dias]

Hi
Is there an estimate of when this issue will be fixed?
Thanks
Cheers
F

On Mon, Nov 27, 2017 at 12:51 PM, Patrick Dunford 
wrote:

> It's a very common issue, you should search this list's archives first
>
> Short answer: these are two different projects and are not guaranteed to
> be in sync all the time. If you need something that is, don't use ubuntugis.
>
> On 28/11/17 00:38, Walter Lorenzetti wrote:
>
> Hi list,
>
> QGIS repository for ubuntugis-unstable is broken, require gdal 2.2.1 but
> ubuntugis updated to 2.2.2.
>
> It is correct or I'm doing a  mistake?
>
> Thanks in advance.
>
> W
>
>
> --
>
> Walter Lorenzetti phD
> email: lorenze...@gis3w.it
> skype: aiki74
> twitter:w_lorenzetti 
> g+:aiki74 
> Tel/Cell: (+39) 347-6597931 <+39%20347%20659%207931>
> Viale Verdi 24 - 51016 Montecatini Terme (PT)
> Nuovi corsi QGIS e GFOSS
> 
>
>
> ___
> QGIS-Developer mailing listqgis-develo...@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 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] Processing throws an error

[Filipe Dias]

Same here with 2.18.4

On Tue, Mar 7, 2017 at 7:46 AM, Paolo Cavallini 
wrote:

> Hi all,
> suddenly Processing on 2.18.4 throws an error when right clicking on any
> of the Molels > Tools:
>
> "/usr/local/src/qgis/QGIS/build_qgis2/output/python/
> plugins/processing/gui/ProcessingToolbox.py",
> line 208, in showPopupMenu
> popupmenu.addSeparator()
> UnboundLocalError: local variable 'popupmenu'
> referenced before
> assignment
>
> All the best.
> --
> Paolo Cavallini - www.faunalia.eu
> QGIS & PostGIS courses: http://www.faunalia.eu/training.html
> https://www.google.com/trends/explore?date=all=IT=qgis,arcgis
> ___
> 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] Processing takes a very long time to close the Options popup

[Filipe Dias]

There's a ticket on this. I am using QGIS 2.18 and the problem persists on
Ubuntu 16.04 at least.

https://hub.qgis.org/issues/15550

On Wed, Oct 26, 2016 at 6:18 PM, Paolo Cavallini 
wrote:

> Il 26/10/2016 19:04, roy roy ha scritto:
>
> > Hi, not shure if this can be related to this issue i found today
> > about SVG symbols Path:
> >
> > http://hub.qgis.org/issues/15759
> >
> > maybe you had hundreds of duplicated path(?)
>
> checked, not
> thanks
>
> --
> Paolo Cavallini - www.faunalia.eu
> QGIS & PostGIS courses: http://www.faunalia.eu/training.html
> https://www.google.com/trends/explore?date=all=IT=qgis,arcgis
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] QEP about Multimap support for QGIS

[Filipe Dias]

Hi,
Really nice feature in my opinion. Out of curiosity: would it be possible
to split Map 1 and Map 2 between two different screens? It would be really
nice to be able to drag Map 2's window to a second screen.
Thanks
Cheers


On Thu, Aug 25, 2016 at 2:36 AM, A Huarte  wrote:

> Hi devs, I have developed an experimental code to support more than one
> map in QGIS. I created a video showing the features implemented (
> https://vimeo.com/179982647 ).
>
> The main features are:
>
>
>- New user option to enable multi map canvas mode.
>- QGIS has one no closeable default map, and 0-N extra dockable maps.
>- Full integration of maps in legend using a new map legend node for
>each map.
>- Print composer supports layouts with different maps.
>- New legend menu option to synchronize the extent of maps.
>- Map tools and plugins work with the current selected map (The
>signals and slots to the map canvas are updated with an automatic mechanism
>of synchronization to minimize the migration of code and to preserve
>behavior).
>
>
> I'm aware that this is a big change in QGIS, and I am sure that this
> capability must be debated by many people (project and developer
> leaders...) before writing any code. Because of that, I have not created
> any QEP entry in the https://github.com/qgis/QGIS-Enhancement-Proposals
> page.
>
> I developed it to learn QGIS core and it will have work to do (plugins and
> tools). But it runs fine, and it was funny :-). If at least, it is useful
> for a day to implement this capability in QGIS or to see the amount of
> changes needed, I am satisfied.
>
>
>
> github:
> https://github.com/qgis/QGIS/compare/master...ahuarte47:
> Feature_MultimapView
>
> video:
> Multi Map Canvas for QGIS
>
>
> [image: image]
>
>
>
>
>
> Multi Map Canvas for QGIS
> Ver en vimeo.com
> Vista previa por Yahoo
>
>
>
>
> Comments are welcome!
>
> Best regards
> Alvaro Huarte - https://github.com/ahuarte47
>
>
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Processing & SAGA 2.2.2

[Filipe Dias]

Would it be possible/reasonable for QGIS repositories to provide the
supported versions of SAGA alongside QGIS? This issue comes up often and it
seems to consume a lot of the Processing developer's time (which seems to
be very limited at the moment).
Cheers

On Thu, Dec 24, 2015 at 7:06 AM, Paolo Cavallini 
wrote:

> Il 24/12/2015 07:46, Victor Olaya ha scritto:
> > I think that changes in Processing to support newer SAGA versions have
> > not been backported to the 2.8.x series, which explains that.
> >
> > However, with SAGA being the less predictable software ever having
> > tons of API breaks in each version...I dont think our LTR should move
> > the supported SAGA version. If 1.8 had support for SAGA 2.1, it should
> > stick to that for all 2.8.x, and actually the installers and bundles
> > should not advance the version and ship that same version of SAGA
> > always. And if not using a bundled version, the user should install
> > the supported version of SAGA, not a more recent one, since that will
> > probably compromise the stability.
>
> Hi Victor,
> thanks for the response. Unfortunately, this holds true only for distros
> where we have complete control over the stack (only Win, I believe). On
> Debian, as in my case, packages get updated all the time, so we really
> have no choice. I acknowledge the issues with saga changes; on the other
> hand, supporting newer versions on more context will help us spotting
> issues and fixing them earlier.
> Of course, the alternative is to fork saga and keep and internal stable
> version. I noticed, however, that currently there seems to be more
> activity than in the past, so forking will be bad:
> http://sourceforge.net/p/saga-gis/code-0/commit_browser
> All the best.
> --
> Paolo Cavallini - www.faunalia.eu
> QGIS & PostGIS courses: http://www.faunalia.eu/training.html
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Meaning of "Canvas Units" in project properties?!?

[Filipe Dias]

Hi,
I agree with Giovanni. Please clarify this issue before release. I got
numerous complaints from users when this happened the last time.
Cheers

On Tue, Oct 20, 2015 at 10:47 AM, Giovanni Manghi  wrote:

> Hi Nyall,
>
>
> > I'm trying to get to the bottom of http://hub.qgis.org/issues/11986
> > (Area calculation is wrong with OTF enabled), but even after reading
> > the source I'm struggling to understand how QGIS is supposed to be
> > handling this. And if a developer who CAN read the source has no idea,
> > how are normal users supposed to understand this? ;)
>
> I guess the right ticket is now this one
>
> http://hub.qgis.org/issues/13209
>
> right? Too bad there was no feedback, does this probably mean that we
> will have again a release with wrong area measures? I have put quite a
> lot of effort in testing this issue, see for example
> http://hub.qgis.org/issues/12057, but now I'm out of time. Shouldn't
> the reference ticket be tagged as blocker (I mean, we should not
> really ship the new release with this issue unresolved...).
>
> cheers!
>
> -- g --
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] [Qgis-user] QGIS Master broken - again

[Filipe Dias]

Ok, thanks. I will wait for the next build.

I am not a programmer, therefore I can't figure out which commit fixes
which bug. This message doesn't mean anything to me:

debian packaging update (take II on fixing #13310)

In cases such as these I would suggest adding a note to the commit message
saying such as: Fixes QGIS Master build. That way end users who are not
programmers can check the log and be warned.

Thanks for fixing this so quickly

Cheers

On Fri, Oct 2, 2015 at 9:21 AM, Jürgen E.  wrote:

> Hi,
>
> On Fri, 02. Oct 2015 at 10:16:25 +0200, DelazJ wrote:
> > Filipe, you should report your bug to qgis-developer@lists.osgeo.org or
> at
> > the qgis issues hub.
>
> Or follow the commit log - [1] probably already fixes this - nightlies
> still
> building...
>
>
> Jürgen
>
>
> [1]
> https://github.com/qgis/QGIS/commit/e263e9ecbffa87af7f000b7530a93eca5b0a0935
>
> --
> Jürgen E. Fischer   norBIT GmbH Tel.
> +49-4931-918175-31
> Dipl.-Inf. (FH) Rheinstraße 13  Fax.
> +49-4931-918175-50
> Software Engineer   D-26506 Norden
> http://www.norbit.de
> QGIS release manager (PSC)  GermanyIRC: jef on FreeNode
>
> ___
> Qgis-user mailing list
> qgis-u...@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-user
>
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] [Qgis-user] QGIS Master broken - again

[Filipe Dias]

Hi
Thanks, it works.
Cheers

On Fri, Oct 2, 2015 at 9:45 AM, Jürgen E. <j...@norbit.de> wrote:

> Hi Filipe,
>
> On Fri, 02. Oct 2015 at 09:34:59 +0100, Filipe Dias wrote:
> > In cases such as these I would suggest adding a note to the commit
> message
> > saying such as: Fixes QGIS Master build. That way end users who are not
> > programmers can check the log and be warned.
>
> The master build itself was fine.  It was just a missing dependency in the
> debian packaging - so manually installing python-qt4-sql also helps.
>
>
> Jürgen
>
> --
> Jürgen E. Fischer   norBIT GmbH Tel.
> +49-4931-918175-31
> Dipl.-Inf. (FH) Rheinstraße 13  Fax.
> +49-4931-918175-50
> Software Engineer   D-26506 Norden
> http://www.norbit.de
> QGIS release manager (PSC)  GermanyIRC: jef on FreeNode
>
> ___
> Qgis-user mailing list
> qgis-u...@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-user
>
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] SSL error on QGIS startup

[Filipe Dias]

+1 for getting rid of the the warning
- 1 for getting rid of the news tab

On Fri, Oct 2, 2015 at 8:53 AM, Paolo Cavallini 
wrote:

> Il 02/10/2015 09:49, Richard Duivenvoorde ha scritto:
>
> > I'm in favour of removing Google lib dependencies, especially if they
> > give certificate errors :-)
> >
> > But I did like the news-tab though, and was hoping to attract more
> > people to read (and write!) about QGIS.
>
> +1, thanks.
>
> --
> Paolo Cavallini - www.faunalia.eu
> QGIS & PostGIS courses: http://www.faunalia.eu/training.html
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Processing regression: OGR algs cannot be used in models

[Filipe Dias]

Hi,

Despite the lack of financial investment QGIS-Processing is, in my opinion,
the best tool for GIS analysis in the market (including paid software).
However there are a few problems (like the one mentioned above) that can
discourage new users and ruin user experience.

I think some paid development time would certainly help QGIS- processing a
lot. For instance QGIS-Processing multi-threaded support seems to be
finished or close but still hasn't been merged into master (I assume
because no developer had the time to review it).

If the sponsors are not interested in financing Processing, then
crowdfunding would be a nice alternative. I would certainly be willing to
contribute.

Cheer

On Sun, Sep 20, 2015 at 11:28 AM, Anita Graser  wrote:

> Hi,
>
> ​I'd like to draw some attention to a really nasty OGR issue/regression
> which makes it impossible to use OGR algos in models:
> http://hub.qgis.org/issues/13174
>
> In general, this is kind of a follow upon of the thread "GRASS missing
> from Processing?" where Paolo summarized:
>
> On Fri, Sep 18, 2015 at 12:31 PM, Paolo Cavallini 
> wrote:
>
>> The main point here is very few people invest in it, so
>> stabilization and innovation is slower than we would like.
>>
>
> ​I assume most of the paid development is currently not aimed towards
> geoprocessing. Paying users so far seem quite focused on cartographic
> abilities and data management but much less on spatial analysis.
>
> ​What would it take to get a Processing testing framework up and running
> as discussed in https://hub.qgis.org/issues/5807?
>
> There's been success with crowd-funding initiatives in the past. Is there
> any dev who would want to focus on this?
>
> Best wishes,
> Anita
>
>
>
>
>
>
>
> ​
>
>
>
>
>
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] GRASS missing from Processing?

[Filipe Dias]

Hi
Has a new Processing version been release? It's not showing in the plugin
manager.
Cheers

On Sun, Sep 20, 2015 at 6:43 PM, Paolo Cavallini 
wrote:

> Il 18/09/2015 11:46, Paolo Cavallini ha scritto:
>
> > yes, little bit more than zipping code from master and uploading it.
> > I think Victor can do it, or I can as well, with a little help.
>
> new version released, all well.
> Thanks!
>
> --
> Paolo Cavallini - www.faunalia.eu
> QGIS & PostGIS courses: http://www.faunalia.eu/training.html
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] GRASS missing from Processing?

[Filipe Dias]

Hi

This is indeed annoying. I'm using GRASS 7 directly as a result.

As Paolo mentioned recently, Processing doesn't seem to be extremely
popular amongst QGIS users and it is understaffed at the moment.

Cheers

On Fri, Sep 18, 2015 at 10:19 AM, Bernd Vogelgesang <
bernd.vogelges...@gmx.de> wrote:

> Am 18.09.2015, 09:30 Uhr, schrieb Paolo Cavallini :
>
> Il 18/09/2015 08:58, Paolo Cavallini ha scritto:
>>
>> I'm referring to this:
>>> https://lists.osgeo.org/pipermail/qgis-developer/2015-August/038772.html
>>> If I inderstand it correctly, a commit and a new package is much needed.
>>>
>>
>> I confirm once more that the simple fix in:
>>
>> https://github.com/qgis/QGIS/commit/2a14ffd281d0a0e99a0a899622a29ca0efdb0852
>> works. Could please someone release a new Processing package?
>> It's pretty important, as GRASS is broken without it.
>> Thanks.
>>
>
> I was already wondering why nothing happened for such a long time.
> https://hub.qgis.org/issues/13072 is closed.
> My GRASS (on QGIS 2.8.3) was only working cause I fiddled around for hours
> and then downloaded processing 2.9.3 manually and refused to update it to
> 2.10.1. Since then, no new processing plugin was shipped.
> I wonder how many people have no GRASS support for months now, don't they
> dare or are there only so few Linux users who try to use LTR but always
> compile latest versions?
>
> Cheers
> Bernd
>
> --
> Bernd Vogelgesang
> Siedlerstraße 2
> 91083 Baiersdorf/Igelsdorf
> Tel: 09133-825374
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Failing tests consider blockers

[Filipe Dias]

Hi

About regressions, I agree with the current guidelines. From the user's
perspective, regressions are extremely annoying. It is very frustrating to
be used to a tool that suddenly stops working in a new version. Depeding on
the severity of the regression, it can even discourage the adoption of a
new version.

Cheers

On Mon, May 25, 2015 at 8:03 AM, Tim Sutton t...@kartoza.com wrote:

 Hi


 On 19 May 2015, at 10:58, Jürgen E. Fischer j...@norbit.de wrote:

 Hi Paolo,

 On Mon, 18. May 2015 at 22:52:04 +0200, Paolo Cavallini wrote:

 Following a suggestion from Juergen, I'm again here to suggest to use
 for our bugs the Debian system:
 https://www.debian.org/Bugs/Developer#severities
 To me it seems the most simple and reasonable system. Of course we will
 need minor adaptation to definitions, but I think we'll easily agree on
 that.


 Yes, I'd also prefer that scheme.  I also don't see regressions as extra
 serious - if there is a regression it's severity should still be evaluated
 as
 for all other bugs and it should not automatically get the highest
 available
 severity.


 +1 from me to amend our scheme following Jürgen’s guidelines.

 Regards

 Tim



 Jürgen

 --
 Jürgen E. Fischer   norBIT GmbH Tel. +49-4931-918175-31
 Dipl.-Inf. (FH) Rheinstraße 13  Fax. +49-4931-918175-50
 Software Engineer   D-26506 Norden
 http://www.norbit.de
 QGIS release manager (PSC)  GermanyIRC: jef on
 FreeNode
 ___
 Qgis-developer mailing list
 Qgis-developer@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/qgis-developer


 —




 Tim Sutton

 Visit http://kartoza.com to find out about open source:

 * Desktop GIS programming services
 * Geospatial web development
 * GIS Training
 * Consulting Services

 Skype: timlinux Irc: timlinux on #qgis at freenode.net
 Tim is a member of the QGIS Project Steering Committee

 Kartoza is a merger between Linfiniti and Afrispatial


 ___
 Qgis-developer mailing list
 Qgis-developer@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/qgis-developer

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Processing and ftools (Proposal for hackfest)

[Filipe Dias]

Hi

I think it would be nice to be able to access some tools from the Menu.
Maybe allow users to select which tools or groups of tools can be opened
from the Menu?

A few years ago ArcGIS moved all geoprocessing tools to the Toolbox and a
lot of users complained. They ended up creating a Menu called
geoprocessing that had the most commonly used algorithms: intersection,
clip etc.

Also, many ftools algorithms are terribly slow (e.g. dissolve),
particularly when compared to the equivalent tools based on ogr2ogr, that
Giovanni Manghi added to Processing a few months ago. It may worth
considering the possibility of deleting some ftools algorithm in favor of
the ogr2ogr based algorithms.

Cheers

On Wed, May 6, 2015 at 1:07 PM, Régis Haubourg 
regis.haubo...@eau-adour-garonne.fr wrote:

 Hi,
 + 1 for centralizing alg's in one place. From a UI point of view, what
 about
 discussing some kind of shortcuts in menu, allowing to open directly
 processing algorithms?
 Users do love the graphic icon in ftools that help understanding what
 geometric operator will be triggered. Even more, an assistant would be
 perfect, even if it's only a shortcut to processing tools.
 We have user here that use menu a lot, and that would have diffulties to
 understand having a vector menu without geo processing entries. same for
 raster.
 Cheers
 Régis



 --
 View this message in context:
 http://osgeo-org.1560.x6.nabble.com/Processing-and-ftools-Proposal-for-hackfest-tp5204324p5204401.html
 Sent from the Quantum GIS - Developer mailing list archive at Nabble.com.
 ___
 Qgis-developer mailing list
 Qgis-developer@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/qgis-developer
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Print composer font pickers are broken

[Filipe Dias]

Hi,
Has a decision been made on this subject? Will 2.8 be released with this
bug? Or will skip to 2.8.1 with this bug fixed?

Cheers
F.

On Sat, Feb 21, 2015 at 11:30 PM, Anita Graser anitagra...@gmx.at wrote:

 Thanks Tim!

 On Sat, Feb 21, 2015 at 10:51 PM, Tim Sutton t...@kartoza.com wrote:

 Confirmed here on Linux last night too and mentioned on IRC. IMHO this is
  a blocker / reason for immediate patch and 2.8.1.


 ​​+1 since this issue makes print map production impossible :(

 Best wishes,
 Anita






 Regards

 Tim

 On Sat, Feb 21, 2015 at 7:31 PM, Anita Graser anitagra...@gmx.at wrote:

 Hi,

 Please see https://hub.qgis.org/issues/12233:
 Font pickers in print composer don't accept user input - fonts cannot be
 changed. Tested with 2.8 and master from OSGeo4W on Win7 and Win8.

 Best wishes,
 Anita

 ___
 Qgis-developer mailing list
 Qgis-developer@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/qgis-developer




 --

 --
 Tim Sutton
 Visit http://kartoza.com to find out about open source:
  * Desktop GIS programming services
  * Geospatial web development
 * GIS Training
 * Consulting Services
 Skype: timlinux Irc: timlinux on #qgis at freenode.net
 Tim is a member of the QGIS Project Steering Committee

 ---
 Kartoza is a merger between Linfiniti and Afrispatial



 ___
 Qgis-developer mailing list
 Qgis-developer@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/qgis-developer

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Print composer font pickers are broken

[Filipe Dias]

In that case:

+1 to 2.8.1 . Too bad no one noticed it before release. I made a bunch of
maps a few days ago and missed it...

Cheers

On Sun, Feb 22, 2015 at 8:17 PM, Pedro Venâncio pedrongvenan...@gmail.com
wrote:

 Filipe,

 2.8 has been realeased already.

 +1 to 2.8.1. But maybe it is better to wait a few more days to see if any
 more serious errors appears, and then release 2.8.1.


 Best regards,
 Pedro

 ___
 Qgis-developer mailing list
 Qgis-developer@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/qgis-developer

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Print composer font pickers are broken

[Filipe Dias]

It is indeed a very serious.

I know that packaging takes a lot of time and effort, but I wonder if it
wouldn't be better to cancel 2.8 and jump to 2.8.1. since the bug was
already fixed.

This was obviously very unfortunate, but I fear that many people will be
extremely annoyed to find this problem in a new release.

If 2.8.1 is not feasible right away, I would suggest a big warning about
this.

Cheers


On Sun, Feb 22, 2015 at 9:02 PM, Anita Graser anitagra...@gmx.at wrote:


 On Sun, Feb 22, 2015 at 9:17 PM, Pedro Venâncio pedrongvenan...@gmail.com
  wrote:

 Filipe,

 2.8 has been realeased already.


 ​I think the release hasn't officially been announced yet though.​

 +1 to 2.8.1. But maybe it is better to wait a few more days to see if any
 more serious errors appears, and then release 2.8.1.


 ​On the other hand we know there's a serious issue - so we would at least
 have to warn users that this one feature is broken in 2.8.0 ...


 Best wishes,
 Anita

 ​








 Best regards,
 Pedro

 ___
 Qgis-developer mailing list
 Qgis-developer@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/qgis-developer



 ___
 Qgis-developer mailing list
 Qgis-developer@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/qgis-developer

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] New Processing modeller issue

[Filipe Dias]

Hi
This problem was there in the previous version. It's kind of annoying but
if you give it a jiggle, either by zooming in or out or moving the scroll
bars they should reappear.

In my experience, its gets worse as you add more actions.


On Thu, Jul 3, 2014 at 6:43 AM, Paolo Cavallini cavall...@faunalia.it
wrote:

 Hi all.
 The new modeller seems to have a minor issue: when zooming in, when items
 get close
 to the window border, the lines connecting the blocks disappear.
 Does anyone confirm? Should I open a ticket?
 All the best.
 --
 Paolo Cavallini - www.faunalia.eu
 Corsi QGIS e PostGIS: http://www.faunalia.eu/training.html
 ___
 Qgis-developer mailing list
 Qgis-developer@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/qgis-developer

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Qgis-Processing (former Sextante) has two bug trackers

[Filipe Dias]

Great, thanks Alex.

I see a minor issue: users who are not aware of the Processing tracker will
probably open tickets in the main tracker with the general category
Processing/Sextante and won't be able to specify which is the affected
backend (the Processing bug tracker has a subcategory for each backend:
SAGA GIS, GRASS GIS etc).

A possible workaround would be to replace the category Processing/Sextante
with Processing/SAGA GIS, Processing/R, Processing GRASS GIS etc.

Thanks
Regards


On Wed, Mar 26, 2014 at 9:31 AM, Alexander Bruy alexander.b...@gmail.comwrote:

 Hi all,

 thanks to Alex, now Processing/SEXTANTE bugtracker is
 a subproject of QGIS. All Processing tickets should be visible
 inside main QGIS tracker, but for submitting issue one should
 use Processing tracker.

 Please test. If this solution will not work fine for us we can always
 restore previous state.

 2014-03-25 17:08 GMT+02:00 Alexander Bruy alexander.b...@gmail.com:
  +1 from me to make Processing/SEXTANTE subproject if
  this keep all tickets categories and allow to see Processing
  bugs among QGIS ones
 
  2014-03-24 21:32 GMT+02:00 Alex Mandel tech_...@wildintellect.com:
  As a sub-project, it would show up in queries of the main QGIS ticket
  system, but at the same time be able to have it's own internal
 categories.
 
  This to me seems the best compromise. It's really a big plugin with a
  myriad of backends. That complexity is what makes it a little different
  from the others mentioned. The others mentioned could be sub-projects of
  the main QGIS too. In reality all of them are core plugins, but they are
  still plugins. None of them are required to make QGIS work (boot). Hence
  they each have their own category. The challenge here is
  Processing/Sextante(I always call it by both since I do the the
  possibility of Processing stuff that isn't sextante) needs it's own
  categories/sub-categories.
 
  Also it's really easy for use to try moving it to be a subproject and
  then reassess (Takes about 30 seconds to move it). If it's still not
  right then we can talk about how to move tickets.
 
  Thanks,
  Alex
 
  On 03/24/2014 12:05 PM, Filipe Dias wrote:
  Hi
  I think Processing tickets should be in the main bug tracker, since
 GDAL
  tools, fTools and Grass plugin tickets are also there.
 
  Also, Qgis-Processing is a really big (and great) feature, that
 interests a
  lot of users, so it makes sense to keep its tickets in the main
 tracker.
 
  Regards
  F.
 
 
  On Mon, Mar 24, 2014 at 6:02 PM, Alex Mandel 
 tech_...@wildintellect.comwrote:
 
  On 03/24/2014 05:10 AM, Filipe Dias wrote:
  Hi
 
  QGIS-Processing (former Sextante) has open tickets on two
 bugtrackers:
 
  - the plugin bug tracker, built when it was a plugin, but with a lot
 of
  active tickets - http://hub.qgis.org/projects/sextante/activity
 
  - the main bug tracker with a few open tickets -
  http://hub.qgis.org/projects/quantum-gis/issues
 
  I understand those two can't be merged in one go, because the
  plugin-bugtracker has categories (QGIS-Processing SAGA GIS,
  QGIS-Processing
  GRASS GIS etc) that don't fit in the main bug tracker. But this
 should be
  solved ASAP, because the current situation is quite confusing
 
  Regards
  F.
 
 
 
  I'm of the opinion that the tracker should continue to be the Plugin
  tracker, not the main QGIS tracker. So I'd propse moving any
  Sextante/Processing tickets from the main or linking them into the
  Plugin tracker.
 
  To me it's still a plugin, just a core plugin but big enough that it's
  really a subproject. If we wanted to move the Plugin tracker as a
  sub-project of QGIS that would also make sense.
 
  Also Processing bugs aside from Processing not loading aren't
  showstoppers for release.
 
  Thanks,
  Alex
 
 
 
 
  ___
  Qgis-developer mailing list
  Qgis-developer@lists.osgeo.org
  http://lists.osgeo.org/mailman/listinfo/qgis-developer
 
 
  ___
  Qgis-developer mailing list
  Qgis-developer@lists.osgeo.org
  http://lists.osgeo.org/mailman/listinfo/qgis-developer
 
 
 
  --
  Alexander Bruy



 --
 Alexander Bruy
 ___
 Qgis-developer mailing list
 Qgis-developer@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/qgis-developer

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

[Qgis-developer] Qgis-Processing (former Sextante) has two bug trackers

[Filipe Dias]

Hi

QGIS-Processing (former Sextante) has open tickets on two bugtrackers:

- the plugin bug tracker, built when it was a plugin, but with a lot of
active tickets - http://hub.qgis.org/projects/sextante/activity

- the main bug tracker with a few open tickets -
http://hub.qgis.org/projects/quantum-gis/issues

I understand those two can't be merged in one go, because the
plugin-bugtracker has categories (QGIS-Processing SAGA GIS, QGIS-Processing
GRASS GIS etc) that don't fit in the main bug tracker. But this should be
solved ASAP, because the current situation is quite confusing

Regards
F.
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Qgis-Processing (former Sextante) has two bug trackers

[Filipe Dias]

Hi
I think Processing tickets should be in the main bug tracker, since GDAL
tools, fTools and Grass plugin tickets are also there.

Also, Qgis-Processing is a really big (and great) feature, that interests a
lot of users, so it makes sense to keep its tickets in the main tracker.

Regards
F.


On Mon, Mar 24, 2014 at 6:02 PM, Alex Mandel tech_...@wildintellect.comwrote:

 On 03/24/2014 05:10 AM, Filipe Dias wrote:
  Hi
 
  QGIS-Processing (former Sextante) has open tickets on two bugtrackers:
 
  - the plugin bug tracker, built when it was a plugin, but with a lot of
  active tickets - http://hub.qgis.org/projects/sextante/activity
 
  - the main bug tracker with a few open tickets -
  http://hub.qgis.org/projects/quantum-gis/issues
 
  I understand those two can't be merged in one go, because the
  plugin-bugtracker has categories (QGIS-Processing SAGA GIS,
 QGIS-Processing
  GRASS GIS etc) that don't fit in the main bug tracker. But this should be
  solved ASAP, because the current situation is quite confusing
 
  Regards
  F.
 
 

 I'm of the opinion that the tracker should continue to be the Plugin
 tracker, not the main QGIS tracker. So I'd propse moving any
 Sextante/Processing tickets from the main or linking them into the
 Plugin tracker.

 To me it's still a plugin, just a core plugin but big enough that it's
 really a subproject. If we wanted to move the Plugin tracker as a
 sub-project of QGIS that would also make sense.

 Also Processing bugs aside from Processing not loading aren't
 showstoppers for release.

 Thanks,
 Alex

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Post-release period of portable commits only?

[Filipe Dias]

How about making a formal announcement (mailing list, website, wiki etc)
telling the users that QGIS version 2.X is in feature freeze and therefore
is sufficiently stable to be tested by end users? This may increase the
number of testers.

As an end user that uses QGIS for production, this is the only time I work
with QGIS Master.


On Mon, Feb 24, 2014 at 2:17 PM, Jonathan Moules 
jonathanmou...@warwickshire.gov.uk wrote:



  Why not?  We're talking about a feature freezed period!?  The nightly
 build
 is a snapshot what what will get release.  Where do you see a difference?


 I think it's a perception thing.
 Nightly build in my mind always means bleeding edge may or may not
 work, use at own risk. I'm aware that doesn't always mean *it will
 crash your computer, burn down your house, and spend your life savings on
 questionable drugs*, but it's certainly not what I see as a synonym for
 stable either.

 Every time I see a nightly, it always comes with a big scary caveat (QGIS
 does too - http://www.qgis.org/en/site/forusers/alldownloads.html ). This
 trains users not to use them. Taking one of the nightlies and re-branding
 it to something more amicable would get more folks to test it. Just copy
 and paste it and rename the file. :-)

 Cheers,
 Jonathan




  Very few average user will install a nightly development build, but you
 get
  an higher chance of getting a broader number of people (that interacts
 with
  QGIS in different ways) to test out your product before it's released.

 Why should it matter if we call it weekly snapshot, nightly build or
 prerelease?   It's the same thing, just the tag is different.  And
 installation is essential as easy as installing the stable release.


  It also helps channel what your describing as noise (i.e. users running
  into problems) into a better managed call for people to test and report.
  The noise will happen no matter what. But it might make some sense to
  trigger some of that noise (valid bugs and invalid RTFM cases)
 _before_
  you release your final version via a pre-release social media and news
 site
  try this pre-release build :)

  It's really more a matter of presentation to the users than of actual
 work.

 Exactly.  And that's what I meant with noise: tada, there's a new weekly
 snapshot/prerelease/nightly build - not users running into problems.
  Because
 I see that as the only significant difference to what we already have.


 Jürgen

 --
 Jürgen E. Fischer norBIT GmbH   Tel.
 +49-4931-918175-31
 Dipl.-Inf. (FH)   Rheinstraße 13Fax.
 +49-4931-918175-50
 Software Engineer D-26506 Norden
 http://www.norbit.de
 QGIS PSC member (RM)  Germany  IRC: jef on
 FreeNode

 --
 norBIT Gesellschaft fuer Unternehmensberatung und Informationssysteme mbH
 Rheinstrasse 13, 26506 Norden
 GF: Jelto Buurman, HR: Amtsgericht Emden, HRB 5502

 ___
 Qgis-developer mailing list
 Qgis-developer@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/qgis-developer



 This transmission is intended for the named addressee(s) only and may
 contain sensitive or protectively marked material up to RESTRICTED and
 should be handled accordingly. Unless you are the named addressee (or
 authorised to receive it for the addressee) you may not copy or use it, or
 disclose it to anyone else. If you have received this transmission in error
 please notify the sender immediately. All email traffic sent to or from us,
 including without limitation all GCSX traffic, may be subject to recording
 and/or monitoring in accordance with relevant legislation.
 ___
 Qgis-developer mailing list
 Qgis-developer@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/qgis-developer

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Priority for bugfixing

[Filipe Dias]

Hi
Don't forget about QGIS Processing, that has a separate bugtracker (
http://hub.qgis.org/projects/sextante/issues) and a few blockers. My
personal priority list is:

1- #6299 - Sextante outputs do not have the same Encoding as the inputs -
http://hub.qgis.org/issues/6299

2 - #8264 - error when trying to load a layer that wasn't actually
created - http://hub.qgis.org/issues/8264

3 - #8772 - Deactivating a module in Modeler has no effect after the save
and close of the model - http://hub.qgis.org/issues/8772

4 - #8919 - R scripts: not possible to export .csv -
http://hub.qgis.org/issues/8919


Best regards
F.



On Wed, Feb 5, 2014 at 8:02 AM, Paolo Cavallini cavall...@faunalia.itwrote:

 Hi all.
 Juergen and Martin will do one week of bugfixing, in order to have a
 better release.
 They are best palced to decide their own priorities. I suggest to have a
 look to
 blockers first, then high; IMHO, blockers should be either solved (if they
 are really
 blocking) or downgraded. Releasing with real blockers should be a very
 last resort
 option.
 All the best, and thanks.
 --
 Paolo Cavallini - www.faunalia.eu
 Corsi QGIS e PostGIS: http://www.faunalia.eu/training.html
 ___
 Qgis-developer mailing list
 Qgis-developer@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/qgis-developer

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Why does Processing not provide GDAL Rasterize?

[Filipe Dias]

Hi, it was added to Qgis Master sometime ago. If you want to use QGIS 2.0.1
you can upgrade Processing from the plugin installer and get the code from
October 29th.


On Mon, Nov 18, 2013 at 5:17 PM, Anita Graser anitagra...@gmx.at wrote:

 Hi,

 Is it possible to add support for GDAL Rasterize to Processing? I see
 Polygonize but not Rasterize.

 Best wishes,
 Anita
 ___
 Qgis-developer mailing list
 Qgis-developer@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/qgis-developer

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Processing: more integration and upgrade

[Filipe Dias]

Thank you very much. I does work. I had thought about that but was afraid
it could ruin my installation. I wish I knew that before!


On Tue, Oct 15, 2013 at 7:38 AM, Alexander Bruy alexander.b...@gmail.comwrote:

 Hi Filipe,

 2013/10/14 Filipe Dias filipesd...@gmail.com:
  +1 Personally I would prefer to have daily versions. It is highly
 motivating
  for users and testers to report a bug and to have Processing fixed and
  available in the next day. I would not mind to have to use an external
  software to get the most recent code (e.g. Tortois svn or equivalent).

 You can grab Processing code from GitHub and just copy it to your
 QGIS installation. It should work.

 Packaging needed for peoples, that don't know about git and github, but
 want to test (or in most cases simply use) latest Processing.

 --
 Alexander Bruy

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Processing: more integration and upgrade

[Filipe Dias]

 Opinions on the best way to do this are welcome

+1 Personally I would prefer to have daily versions. It is highly
motivating for users and testers to report a bug and to have Processing
fixed and available in the next day. I would not mind to have to use an
external software to get the most recent code (e.g. Tortois svn or
equivalent).


On Mon, Oct 14, 2013 at 6:10 PM, Paolo Cavallini cavall...@faunalia.itwrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Il 14/10/2013 19:06, Victor Olaya ha scritto:

  I plan to integrate that into the training manual, probably along this
  week (I'm glad that you like the Processing tutorial... :-) )

 fine, obviously +1 for me - ready to give feedback from out in the wild

 BTW, people in Gibraltar at a conference were rather astonished by QGIS in
 general,
 and Processing in particular.

  Opinions on the best way to do this are welcome

 +1 for me. I'd suggest to have the usual Debian strategy: publish in
 experimental,
 and if no bad bugs are reported for, say, 2 weeks, move that version to
 stable.

 Thanks.
 - --
 Paolo Cavallini - Faunalia
 www.faunalia.eu
 Full contact details at www.faunalia.eu/pc
 Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.15 (GNU/Linux)
 Comment: Using GnuPG with Icedove - http://www.enigmail.net/

 iEYEARECAAYFAlJcJZ4ACgkQ/NedwLUzIr4PpACdFcqY/wuoU9X1CxYINyG2imbb
 9hYAnjeaP6X215PZ4etmhJNU9kJuMbNf
 =ak8W
 -END PGP SIGNATURE-
 ___
 Qgis-developer mailing list
 Qgis-developer@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/qgis-developer

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Processing Python Error on Startup

[Filipe Dias]

I agree too. Processing is massive and to fully test it is going to take
while.

Also, considering the interest of the community and the number of new
features that are added or requested in the bug tracker/GIS Stackexchange
every day, I think scheduling frequent releases is the best way to keep
Processing evolving and maturing.

As always, I would like to thank Victor Olaya for bringing
Sextante/Processing to QGIS. It has greatly improved my GIS work and made
it a lot more enjoyable. I think sometime ago Camilo Polymeris said
something like the more into Sextante, the more I like it. I feel the
same way about using it.

Regards


On Sun, Oct 6, 2013 at 8:30 PM, Pedro Venâncio pedrongvenan...@yahoo.comwrote:

 Hi,

 I also think the best option is to provide updates of Processing in the
 plugin repo. Processing is still evolving and much bugfixing has been done
 and is done regularly. In my opinion, these fixes must be backported more
 regularly than the QGIS releases.


 Best regards,
 Pedro





 - Original Message -

 I have discussed with Tim the idea of releasing new versions of
 Processing periodically, tagged as experimental, to the plugin repo.
 Alex has prepared a script that packages and uploads the Processing
 code, and that can be used to automate that, but we haven't done
 anything yet regarding that. What do people think of this idea?

 If a new QGIS release is made, the master version cntains quite a few
 bug fixes for Processing.

 Cheers
 Victor

 2013/10/6 Paolo Cavallini cavall...@faunalia.it:
  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA1
 
  Il 06/10/2013 21:07, Victor Olaya ha scritto:
  That is already fixed in master
 
  Hi all.
  What are the plans for this?Are we going to backport and release a
  fixed version?
  This question concerns a few other fixed bugs, I believe.
  All the best.
 
  - --
  Paolo Cavallini - Faunalia
  www.faunalia.eu
  Full contact details at www.faunalia.eu/pc
  Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario
  -BEGIN PGP SIGNATURE-
  Version: GnuPG v1.4.14 (GNU/Linux)
  Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
 
  iEYEARECAAYFAlJRtcgACgkQ/NedwLUzIr6lHQCfZI8bj/ZW0bqNKvDDoZo32N7E
  JcwAn0mvz/QeZl3zEWs0Ke6GbwSQZcnf
  =I60/
  -END PGP SIGNATURE-
  ___
  Qgis-developer mailing list
  Qgis-developer@lists.osgeo.org
  http://lists.osgeo.org/mailman/listinfo/qgis-developer
 ___
 Qgis-developer mailing list
 Qgis-developer@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/qgis-developer

 ___
 Qgis-developer mailing list
 Qgis-developer@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/qgis-developer

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Qgis-developer Digest, Vol 95, Issue 94

[Filipe Dias]

I agree with Giovanni. QGIS 2.0 introduced a huge amount of new features
and it is not reasonable to expect the first version that comes out is
without major issues. For example in the weeks before the release there
were a number of problems with the nightly builds which prevented many
users from testing the new features.

As an end user I'd rather have more consolidated version of QGIS 2.0 (which
is, by any standards, awesome and way superior to ArcGIS and other freen
and commercial softwares) than see the project rushing to 2.1 without
addressing the issues have and will continue surfacing in the next weeks.

Regards



On Thu, Sep 26, 2013 at 6:17 PM, Giovanni Manghi 
giovanni.man...@faunalia.pt wrote:

  Maybe I missed the memo, but there is now a 2.0.2 release designation for
  tagging issues in the hub.qgis.org tracker. Is there some timeline
  concerning a 2.0.2 release? If so, where?
 
  I have been scheduling my work sessions around the expectation of a 2.1
  release and have not anticipated a sooner one. Likewise, do we currently
  have any timeline goals for a 2.1 release?


 I don't know if there is really a 2.0.2 release programmed, what I
 know is that there are couple of nasty regressions (like the field
 calculator that gives wrong results with otfr on, that have been
 noticed just before the 2.0 release) that would certainly deserve a
 2.0.2 release.

 just my opinion.

 cheers

 -- G --
 ___
 Qgis-developer mailing list
 Qgis-developer@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/qgis-developer

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] roadmap to 2.0

[Filipe Dias]

Hi, and these from Sextante too:
http://hub.qgis.org/projects/sextante/issues


On Fri, Aug 23, 2013 at 4:42 PM, Paolo Cavallini cavall...@faunalia.itwrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Hi all.
 While searching for the announcement of the roadmap to 2.0 release, I
 noticed that we
 have a number of annouuncements, wiki pages, etc, scattered over the net.
 It would be better to update or remove most of them, and point to a single
 documents,
 possibly the original post:
 http://lists.osgeo.org/pipermail/qgis-user/2013-August/023482.html
 or some rewriting of it. Opinions? And, anyway, Sunday is supposed to be
 the Point of
 no return (we still have 8 blockers[0] and 49 high relevance tickets[1]):
 are we
 going to meet and discuss about this?
 All the best.

 [0] http://hub.qgis.org/projects/quantum-gis/issues?query_id=23
 [1]

 http://hub.qgis.org/projects/quantum-gis/issues?priority_id=5set_filter=1status_id=osubproject_id=!*
 - --
 Paolo Cavallini - Faunalia
 www.faunalia.eu
 Full contact details at www.faunalia.eu/pc
 Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.14 (GNU/Linux)
 Comment: Using GnuPG with Icedove - http://www.enigmail.net/

 iEYEARECAAYFAlIXgvYACgkQ/NedwLUzIr5dSgCbB79h1+H5YXd3Fzi6+Kf48UZo
 PwkAnj5hM6tsXDlwzs1tOZvpzxS4Tbq/
 =NGsR
 -END PGP SIGNATURE-
 ___
 Qgis-developer mailing list
 Qgis-developer@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/qgis-developer

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] roadmap to 2.0

[Filipe Dias]

Given the short amount of available time, I'd like to single out this bug:

http://hub.qgis.org/issues/6299

which causes the outputs to have a different encoding from the input. This
can potentially mess up analysis conducted with .shp with non-ascii
characters.

I believe Victor Olaya wont be able to fix this in time. so if there's
anyone else wiling and able to fix it it would be most appreciated
(particularly who speak languages who require special characters).


On Fri, Aug 23, 2013 at 5:01 PM, Paolo Cavallini cavall...@faunalia.itwrote:

 Filipe Dias filipesd...@gmail.com ha scritto:

 Hi, and these from Sextante too:
 http://hub.qgis.org/projects/sextante/issues


 On Fri, Aug 23, 2013 at 4:42 PM, Paolo Cavallini 
 cavall...@faunalia.itwrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Hi all.
 While searching for the announcement of the roadmap to 2.0 release, I
 noticed that we
 have a number of annouuncements, wiki pages, etc, scattered over the net.
 It would be better to update or remove most of them, and point to a
 single documents,
 possibly the original post:
 http://lists.osgeo.org/pipermail/qgis-user/2013-August/023482.html
 or some rewriting of it. Opinions? And, anyway, Sunday is supposed to be
 the Point of
 no return (we still have 8 blockers[0] and 49 high relevance
 tickets[1]): are we
 going to meet and discuss about this?
 All the best.

 [0] http://hub.qgis.org/projects/quantum-gis/issues?query_id=23
 [1]

 http://hub.qgis.org/projects/quantum-gis/issues?priority_id=5set_filter=1status_id=osubproject_id=!*
 - --
 Paolo Cavallini - Faunalia
 www.faunalia.eu
 Full contact details at www.faunalia.eu/pc
 Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.14 (GNU/Linux)
 Comment: Using GnuPG with Icedove - http://www.enigmail.net/

 iEYEARECAAYFAlIXgvYACgkQ/NedwLUzIr5dSgCbB79h1+H5YXd3Fzi6+Kf48UZo
 PwkAnj5hM6tsXDlwzs1tOZvpzxS4Tbq/
 =NGsR
 -END PGP SIGNATURE-
 ___
 Qgis-developer mailing list
 Qgis-developer@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/qgis-developer



 Right, these should be migrated now.
 --
 http://faunalia.it/pc
 Sent from mobile, sorry for being short

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Renaming SEXTANTE

[Filipe Dias]

Hi,
Many people refer to Vector and Raster tools as Ftools and GDAL.
Sextante, in my opinion, is not different, so I dont see why we should
change anything. The Sextante menu is called Analysis which makes sense.
And Sextante toolbox seems to be a good name, as well as Sextante Modeler.

Additionally, Sextante is a recognizable name for gvsig and Arcgis users.
Considering that we can expect that a lot more users are going to start
using QGIS after 2.0 is released, it would make sense the keep the Sextante
naming

Best regards
F.


On Fri, Aug 9, 2013 at 6:53 PM, Victor Olaya vola...@gmail.com wrote:

 Hi

 After much thinking and considering some suggestions, I think it would
 be a good idea to remove the SEXTANTE branding, and just have
 everything with a more descriptive name, such as geoanalysis,
 processing, or something like that. In the long-term, that will help
 to integrate the analysis framework into QGIS,and help users locate
 it.

 It shouldn't be more difficult than just replacing string ocurrences,
 but before doing such a big (and potentially troublesome) change, I
 would like to hear the opinion you guys have about this (is it a good
 idea? what name should we use instead of sextante for packages and
 modules? any good refactoring tool that you recommend?,etc)

 I am going to be out of office next week, so I might not read my email
 everyday, but it would be great to hear what you think about it. Once
 I am back, I will proceed to change it,

 I discussed it briefly with Tim and Paolo, who agreed on this, so I
 assumme this is not incompatible with the API freeze and the release
 plan that we have, but if anyone thinks this shouldn't be done now,
 please say it. I personally think that it would be good to have it in
 2.0, so all analysis stuff is called analysis (or whatever) and not
 with a name that (although I like and feel very identified with it)
 for most people doesn't make much sense...

 Thanks in advance.

 Victor
 ___
 Qgis-developer mailing list
 Qgis-developer@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/qgis-developer

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] very slow Spatialite DB creation on master

[Filipe Dias]

I can confirm that issue with those settings.

On Sun, Jul 21, 2013 at 5:08 PM, Giovanni Manghi 
giovanni.man...@faunalia.pt wrote:

 Hi all,

 on qgis master (ubuntu nightly + ubuntugis) I have noticed that when
 creating a new SL db (from the browser or from new sl layer dialog)
 it takes many minutes to do so, so long that at first I was thinking
 that the program had freezed. I can't see the same on master/windows.

 Someone else sees this issue?

 Should I file a ticket?


 cheers


 -- Giovanni --
 ___
 Qgis-developer mailing list
 Qgis-developer@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/qgis-developer

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] web sites offline?

[Filipe Dias]

I can't open them either.

On Sun, Jul 21, 2013 at 8:26 PM, Daniel daniel...@gmail.com wrote:

 I can't access qgis.org and hub.qgis.org

 Anybody can confirm?

 --
 Daniel Vaz

 ___
 Qgis-developer mailing list
 Qgis-developer@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/qgis-developer


___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Various on sextante

[Filipe Dias]

If ypou hadn't pointed it out, I would never find it. Aside from the new
icon, maybe you could add a small popup explaining what it does.

On Fri, Jul 19, 2013 at 9:01 AM, Victor Olaya vola...@gmail.com wrote:

 
  attached.

 The button is there. I am sending you the screenshot back, with my
 mouse pointer (in white) pointing at it :-)

 The manual already contains a picture with that, I added it yesterday.
 Any idea for a better icon for the button?

 I understand this solution would be far easier for many, but I think
 using a system
 which is different from the rest of documentation is suboptimal.

 Can we start just using git, as with the other docs? People can even
 edit the rst files on the on-line editor in github, which is not a bad
 solution...

 ___
 Qgis-developer mailing list
 Qgis-developer@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/qgis-developer


___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

[Qgis-developer] R-Sextante scripts: ideas?

[Filipe Dias]

Hi all,

QGIS 2.0 seems to be coming along well and according to what I've read on
these lists it will be released soon.

As you know, it is possible use R tools in QGIS via Sextante. There are
some example scripts already but I think there should be more.

A few months ago I made a few very simple tools but I'm now planning to
work on some more complex stuff to include in QGIS 2.0. R itself can be
used as GIS, which means there are plenty of tools to analyze GIS data. So
I would like to ask everyone for ideas for new new algorithms. Here's an
example:

http://www.r-bloggers.com/getting-raster-histogram-in-qgis-using-sextante-and-r/?utm_source=feedburnerutm_medium=feedutm_campaign=Feed%3A+RBloggers+%28R+bloggers%29


If anyone has any suggestions, please share them. If you already have some
R code prepared, all the better.

Thanks

Regards
Filipe
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] SEXTANTE: R output?

[Filipe Dias]

I agree with Paolo.

On Fri, Jul 12, 2013 at 12:01 PM, Paolo Cavallini cavall...@faunalia.itwrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Il 12/07/2013 12:56, Victor Olaya ha scritto:

  What do you think of this?

 - -1
 I strongly prefer to install needed R libs at the system level, not in
 user path.
 At very least, sextante should warne the user and ask for confirmation
 before
 installing R libs. In that case, I would skip that and go to the system,
 installing
 all what is needed.
 All the best.

 - --
 Paolo Cavallini - Faunalia
 www.faunalia.eu
 Full contact details at www.faunalia.eu/pc
 Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.12 (GNU/Linux)
 Comment: Using GnuPG with Icedove - http://www.enigmail.net/

 iEYEARECAAYFAlHf4iQACgkQ/NedwLUzIr61fwCggdZBfupQAG8PfbTBN+ah93OT
 0coAn31tob5LUhwKi2MkBflGcGNa5If4
 =fjkZ
 -END PGP SIGNATURE-
 ___
 Qgis-developer mailing list
 Qgis-developer@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/qgis-developer

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] SEXTANTE: R output?

[Filipe Dias]

This is weird. Before i upgraded to R 3.0 it worked, but now it doesnt.
Even more weird is that on Paolo's system it works and on mine doesnt.

Donovan Cameron shared some insights on the bug report. Perhaps he can help
you understand better whats going on.

Regards



On Thu, Jul 11, 2013 at 5:10 PM, Paolo Cavallini cavall...@faunalia.itwrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Il 11/07/2013 17:37, Victor Olaya ha scritto:
  mmm, SEXTANTE doesn't have to find them...it's R that uses them.
  Someone mentioned in the past a problem with packages paths...but my
  knowledge of R is limited, so I don't know what I can do... :-(

 ok, once installed rgdal and raster it works.
 thanks.
 - --
 Paolo Cavallini - Faunalia
 www.faunalia.eu
 Full contact details at www.faunalia.eu/pc
 Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.12 (GNU/Linux)
 Comment: Using GnuPG with Icedove - http://www.enigmail.net/

 iEYEARECAAYFAlHe2Q0ACgkQ/NedwLUzIr7nyACePLOgsNGvrOaMy5gX7BxOePZz
 bs4AniHSJEBkTQO9nF6H5u+gaRaVOtEQ
 =rWZ6
 -END PGP SIGNATURE-

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] SEXTANTE: R output?

[Filipe Dias]

Its working now.

My R version is 3.0.1 and Sextante was working with R 3.0.0 packages which
apparently caused this problem.

I went to ~/qgs2/sextante and deleted the folder rlibs which forced
Sextante to reinstall its packages.

So the problem was that I upgraded R after running R-Sextante for the first
time.

I dont expect users to regularly update R but there should a warning or a
way to Sextante upgrade its core packages.

Thanks for the help



On Thu, Jul 11, 2013 at 5:55 PM, Paolo Cavallini cavall...@faunalia.itwrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Il 11/07/2013 18:50, Filipe Dias ha scritto:
  This is weird. Before i upgraded to R 3.0 it worked, but now it doesnt.
 Even more
  weird is that on Paolo's system it works and on mine doesnt.

 probably you have to recompile your libs. update.packages() is your friend
 here.
 So the message should be Install or update your packages.
 All the best.
 - --
 Paolo Cavallini - Faunalia
 www.faunalia.eu
 Full contact details at www.faunalia.eu/pc
 Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.12 (GNU/Linux)
 Comment: Using GnuPG with Icedove - http://www.enigmail.net/

 iEYEARECAAYFAlHe42kACgkQ/NedwLUzIr6nngCcCD5GLXVlY63JbWi2wQshQOJF
 ED8An1KQBpM4GgUMnq2roYqKVU1uyyg0
 =Yi6q
 -END PGP SIGNATURE-

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] SEXTANTE: R output?

[Filipe Dias]

Hi,
What's your R version?
http://hub.qgis.org/issues/8012



On Wed, Jul 10, 2013 at 10:26 AM, Paolo Cavallini cavall...@faunalia.itwrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Hi all.
 On current master, example R scripts apparently run without issues, but no
 output is
 shown in the Results window. The resulting html is of the type:

 font face=courier
 h2 R Output/h2
 /font

 or

 img
 src=/tmp/sextante/rrasterhistogram18a1cdc6d0734098bc728452ee90d3a6.html.png/

 but the png is not there.
 Any suggestion?
 All the best.
 - --
 Paolo Cavallini - Faunalia
 www.faunalia.eu
 Full contact details at www.faunalia.eu/pc
 Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.12 (GNU/Linux)
 Comment: Using GnuPG with Icedove - http://www.enigmail.net/

 iEYEARECAAYFAlHdKMEACgkQ/NedwLUzIr7wjwCbBSZveJkEDRFsXLiWsA+ZvXIc
 etcAn0VRyo/H5oY1J3ceFMf+hgl9MTn0
 =CfWk
 -END PGP SIGNATURE-
 ___
 Qgis-developer mailing list
 Qgis-developer@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/qgis-developer

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] SEXTANTE: R output?

[Filipe Dias]

I believe Victor Olaya is looking into it.

On Wed, Jul 10, 2013 at 10:33 AM, Paolo Cavallini cavall...@faunalia.itwrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Il 10/07/2013 11:28, Filipe Dias ha scritto:

  What's your R version?
  http://hub.qgis.org/issues/8012

 oh, you're right:

 $ aptitude show r-base
 Pacchetto: r-base
 Nuovo: s￬
 Stato: non installato
 Versione: 3.0.1-3

 sorry I forgot. Any hope to have it fixed?
 All the best.
 - --
 Paolo Cavallini - Faunalia
 www.faunalia.eu
 Full contact details at www.faunalia.eu/pc
 Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.12 (GNU/Linux)
 Comment: Using GnuPG with Icedove - http://www.enigmail.net/

 iEYEARECAAYFAlHdKlgACgkQ/NedwLUzIr5rVACgs8T7ngInUgjyCLxQVI/UTA7h
 y4cAoJutFEk5EBoFPnqWL/uNN6o8SLla
 =yGDR
 -END PGP SIGNATURE-

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] SEXTANTE: R output?

[Filipe Dias]

According to the release notes R  3.0 should be faster than previous
versions with big data so I guess it would make sense to make it the
target version. However, most R users tend to wait a while to update. Would
it be to difficult to support both R3.0 and R  3 ?


On Wed, Jul 10, 2013 at 10:43 AM, Paolo Cavallini cavall...@faunalia.itwrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Il 10/07/2013 11:39, Victor Olaya ha scritto:
  Yes, Filipe reported that and I hope I can fix it soon. I didn't have
  much time these last days, but let's see if I can work on it later
  today. Sorry for that

 thanks

  p.s. One question: Is R 3.0 now more common than 2.x among R users?
  Should we make 3.0 the target version in SEXTANTE?

 At least on Debian, yes:
 http://packages.debian.org/search?keywords=r-basesearchon=names

 All the best.
 - --
 Paolo Cavallini - Faunalia
 www.faunalia.eu
 Full contact details at www.faunalia.eu/pc
 Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.12 (GNU/Linux)
 Comment: Using GnuPG with Icedove - http://www.enigmail.net/

 iEYEARECAAYFAlHdLNoACgkQ/NedwLUzIr4bBwCfX9MLuiOhmLcsIplQMBpLNwqo
 PSwAnjkmGv/eLmuwKCHhLHAuzTZqGtXw
 =cyHN
 -END PGP SIGNATURE-

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] manageR update for 2.0

[Filipe Dias]

Using R via Sextante is also a good alternative. Shapefiles and Rasters are
exported into R and it's possible to apply all sorts of R tools to them.
There are a few good examples already in the algorithms tree.


On Fri, Jun 7, 2013 at 11:27 AM, Giovanni Manghi 
giovanni.man...@faunalia.pt wrote:

  I also miss it. AFAIK there are additional problems in Windows,
  because of rpy2, right?

 just checked and I confirm that there are no Windows binaries for rpy2
 and recent versions of python/R.
 ___
 Qgis-developer mailing list
 Qgis-developer@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/qgis-developer

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] QGIS 2.0 and beyond

[Filipe Dias]

I agree with Giovanni. As an end user I'd rather wait a few more months
than get an imcomplete version of QGIS 2.0.


On Tue, May 28, 2013 at 4:37 PM, Giovanni Manghi 
giovanni.man...@faunalia.pt wrote:

 Hi,

  Undoubtedly we will have to release with blockers

 please no :)
 It would be a huge blow to QGIS reputation as there are actually
 blockers that make QGIS really unusable for any real life job.

 cheers!

 -- Giovanni --
 ___
 Qgis-developer mailing list
 Qgis-developer@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/qgis-developer

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] External calls to SEXTANTE?

[Filipe Dias]

Hi, you are working on InVest right? If so, have you considered making
InVest inside Sextante Toolbox? In CC I'm copying Victor Olaya, who is
the main developer of Sextante so he can help with that.

As a QGIS user it's very exciting for me to know that you are working on
bringing Invest into QGIS.

Regards
Filipe Dias


On Tue, May 28, 2013 at 7:43 PM, Martin Lacayo mlac...@stanford.edu wrote:

 Hello,

 I would like to make external calls to SEXTANTE with a Python script
 or via the command line. I'm interested in using all the
 geoalgorithms, but in particular I am interested in the GRASS
 geoalgorithms, and specifically in r.viewshed at this moment. Is this
 possible?

 I found this post which seems very close to answering the question:


 http://gis.stackexchange.com/questions/28701/how-to-run-sextante-algorithms-outside-of-qgis-python-console/60725#60725

 However when I try calling sextante.runalg I get an error seemingly
 related the fact that the code is not being run inside the QGIS Python
 console (qgis.utils.iface is None).

 Our FOSS software (naturalcapitalproject.org) is developed on Linux
 but packaged for Windows. Any suggestions or advice? We are hoping to
 reduce our development time and eliminate duplicated efforts.

 Thank you,
 Martin
 ___
 Qgis-developer mailing list
 Qgis-developer@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/qgis-developer

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Updating core plugins

[Filipe Dias]

I think decoupling the release of a new Sextante version from the release
of a new QGIS release is very important. QGIS Master always has bugs that
preclude the users from correctly testing Sextante.

When Sextante was first released as a plugin, all users had to do was to
checkout the svn repository to get the latest code. It was during this
period that there was the highest number of people testing Sextante. Now,
there are only a few.


On Sun, Apr 21, 2013 at 10:24 PM, Victor Olaya vola...@gmail.com wrote:

 Hi all

 Having SEXTANTE as a core plugin in QGIS is really great, but I am
 worried about how that will affect users when 2.0 is released. My two
 main concerns are:

 - People currently using SEXTANTE as a non-core plugin will have 2
 versions of SEXTANTE installed when they install 2.0. This is likely
 to cause strange behaviour, and, as some users have reported on the
 mailing list, it seems that the non-core plugin (in this case, the
 older version), will override the other one. Not a nice thing... The
 solution is to manually uninstall it, but that is going to cause a lot
 of confusion...

 - I have a few features that will not be ready for 2.0, but I would
 like to release them later, just releasing a new versino of SEXTATE
 independently. However, I think that core plugins cannot be updated.
 Installing the new one separately will cause two version to be
 installed...

 Any ideas on that? I see that the easiest solution would be to have
 something in the plugin manager that, in case of having two versions
 of a plugin, would use just the most recent one.

 Thanks in advance!
 Victor
 ___
 Qgis-developer mailing list
 Qgis-developer@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/qgis-developer

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] fTools and GdalTools: sextante vs original plugins

[Filipe Dias]

I agree with allowing the user to define some Menu entries. As an end user
I'd rather have all Analytical tools in one place, but this would allow
people to not loose their habit of calling some more commonly used tools
(I agree with Paolo, a poll with be good) from the Menu.

Sextante is more stable in the areas where there more users. This can only
be solved if more people step in for testing or when the full testing suite
is completed. In any case, Sextante is the single most powerfull GIS
analysis tool out there, including proprietary software. It's a huge
undertaking and it is being carried by very few people. I wish there were
more people contributing to the code and testing it.


On Wed, Apr 17, 2013 at 8:49 AM, Victor Olaya vola...@gmail.com wrote:

 I like the idea of allowing menu entries to be defined from SEXTANTE
 algorithms, as a shortcut to them. If we agree on that, I could start
 working on it.

 Thanks everyone for you ideas!

 Cheers
 Victor

 2013/4/17 Bernhard Ströbl bernhard.stro...@jena.de:
  Hi all,
 
  for a course I am about to give tomorrow I played a bit with SEXTANTE,
  although I am going to teach geoprocessing with fTools (we are using QGIS
  1.8). It was my first go with SEXTANTE and I was about to show what it
 will
  offer in the future. Therefore I built a small model with three input
 layers
  a buffer and two overlay operations. I did not succeed in running the
 model
  so I tried in current master.
  As it currently is SEXTANTE is not operable for me (or I am doing it
 wrong):
  First message is Layers do not all use the same CRS although they
  definitely do and the same EPSG-code is noted in square brackets behind
 each
  layer name!? Second I get an Error executing algorithm... it seems as
  SEXTANTE cannot use PostGIS layers as input (when I save them as shape
 files
  the model runs perfectly), this is a big limitation as my institution
 stores
  almost everything in PostGIS. (SEXTANTE should not offer PostGIS layers
 to
  choose as input layers then).
 
  Well, this was a very disappointing experience because additionally QGIS
 was
  frozen two or three times opening or closing the model. I do not want to
  complain, all I want is to ask for keeping fTools as they are until
 SEXTANTE
  can _really_ replace them in all aspects. Then we should remove the
 vector
  menue completely because I agree that finding the tool you are looking
 for
  is a lot easier in SEXTANTE.
 
  my 2 cents
 
  Bernhard
 
  Am 17.04.2013 07:42, schrieb Anita Graser:
 
  On Wed, Apr 17, 2013 at 3:19 AM, Mathieu Pellerin nirvn.a...@gmail.com
  mailto:nirvn.a...@gmail.com wrote:
 
  There might be a way to make most people happy here.
 
  I find the vector menu a nice ui shortcut for useful functions. If
  sextante relevant functions are at par (or better), couldn't the
  vector menu items stay, which would please many, and when clicked
  triggers sextante's function dialogue? Victor? Same thing could
  happen with vector menu too. Sextante's analysis toolbar is super
  useful but might be a throwback for some if vector / raster menu
  functions disappear.
 
  On human resource (coders and testers) and maintenance angles,
  keeping to mechanism to do same thing is an obvious waste.
 
  I see. So you'd suggest to keep only Sextante code (where duplicates
  exist!) but provide shortcuts from the menu? I'd +1 that.
  I've been testing a variety of functions in the menus and in Sextante
  over the last days and there are always some broken ones. Neither
  package is without major bugs today.
  We need to get it together for 2.0 and that's easier if we can focus on
  one.
 
  Best wishes,
  Anita
 
 
 
  __ Information from ESET Mail Security, version of virus
 signature
  database 8235 (20130416) __
 
  The message was checked by ESET Mail Security.
  http://www.eset.com
 
 
 
  ___
  Qgis-developer mailing list
  Qgis-developer@lists.osgeo.org
  http://lists.osgeo.org/mailman/listinfo/qgis-developer
 ___
 Qgis-developer mailing list
 Qgis-developer@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/qgis-developer

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] fTools and GdalTools: sextante vs original plugins

[Filipe Dias]

Get Qgis Master, randomly (or deliberately) choose tools that you know how
to use and run them. If they don't work as expected, report a bug:

http://hub.qgis.org/projects/sextante/issues

When I have enough time, I do my regular work using Qgis Master and report
the bugs that I find.



On Wed, Apr 17, 2013 at 2:17 PM, antoniolocandro 
antoniolocan...@hotmail.com wrote:

 Well since I can't code I can help with the testing, just point me where
 to start and I will try Sextante




 Sent from Samsung tablet

 Filipe Dias filipesd...@gmail.com wrote:
 I agree with allowing the user to define some Menu entries. As an end user
 I'd rather have all Analytical tools in one place, but this would allow
 people to not loose their habit of calling some more commonly used tools
 (I agree with Paolo, a poll with be good) from the Menu.

 Sextante is more stable in the areas where there more users. This can only
 be solved if more people step in for testing or when the full testing suite
 is completed. In any case, Sextante is the single most powerfull GIS
 analysis tool out there, including proprietary software. It's a huge
 undertaking and it is being carried by very few people. I wish there were
 more people contributing to the code and testing it.


 On Wed, Apr 17, 2013 at 8:49 AM, Victor Olaya vola...@gmail.com wrote:

 I like the idea of allowing menu entries to be defined from SEXTANTE
 algorithms, as a shortcut to them. If we agree on that, I could start
 working on it.

 Thanks everyone for you ideas!

 Cheers
 Victor

 2013/4/17 Bernhard Ströbl bernhard.stro...@jena.de:
  Hi all,
 
  for a course I am about to give tomorrow I played a bit with SEXTANTE,
  although I am going to teach geoprocessing with fTools (we are using
 QGIS
  1.8). It was my first go with SEXTANTE and I was about to show what it
 will
  offer in the future. Therefore I built a small model with three input
 layers
  a buffer and two overlay operations. I did not succeed in running the
 model
  so I tried in current master.
  As it currently is SEXTANTE is not operable for me (or I am doing it
 wrong):
  First message is Layers do not all use the same CRS although they
  definitely do and the same EPSG-code is noted in square brackets behind
 each
  layer name!? Second I get an Error executing algorithm... it seems as
  SEXTANTE cannot use PostGIS layers as input (when I save them as shape
 files
  the model runs perfectly), this is a big limitation as my institution
 stores
  almost everything in PostGIS. (SEXTANTE should not offer PostGIS layers
 to
  choose as input layers then).
 
  Well, this was a very disappointing experience because additionally
 QGIS was
  frozen two or three times opening or closing the model. I do not want to
  complain, all I want is to ask for keeping fTools as they are until
 SEXTANTE
  can _really_ replace them in all aspects. Then we should remove the
 vector
  menue completely because I agree that finding the tool you are looking
 for
  is a lot easier in SEXTANTE.
 
  my 2 cents
 
  Bernhard
 
  Am 17.04.2013 07:42, schrieb Anita Graser:
 
  On Wed, Apr 17, 2013 at 3:19 AM, Mathieu Pellerin 
 nirvn.a...@gmail.com
  mailto:nirvn.a...@gmail.com wrote:
 
  There might be a way to make most people happy here.
 
  I find the vector menu a nice ui shortcut for useful functions. If
  sextante relevant functions are at par (or better), couldn't the
  vector menu items stay, which would please many, and when clicked
  triggers sextante's function dialogue? Victor? Same thing could
  happen with vector menu too. Sextante's analysis toolbar is super
  useful but might be a throwback for some if vector / raster menu
  functions disappear.
 
  On human resource (coders and testers) and maintenance angles,
  keeping to mechanism to do same thing is an obvious waste.
 
  I see. So you'd suggest to keep only Sextante code (where duplicates
  exist!) but provide shortcuts from the menu? I'd +1 that.
  I've been testing a variety of functions in the menus and in Sextante
  over the last days and there are always some broken ones. Neither
  package is without major bugs today.
  We need to get it together for 2.0 and that's easier if we can focus on
  one.
 
  Best wishes,
  Anita
 
 
 
  __ Information from ESET Mail Security, version of virus
 signature
  database 8235 (20130416) __
 
  The message was checked by ESET Mail Security.
  http://www.eset.com
 
 
 
  ___
  Qgis-developer mailing list
  Qgis-developer@lists.osgeo.org
  http://lists.osgeo.org/mailman/listinfo/qgis-developer
 ___
 Qgis-developer mailing list
 Qgis-developer@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/qgis-developer



___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] fTools and GdalTools: sextante vs original plugins

[Filipe Dias]

I agree. Sextante makes finding the appropriate tools a lot easier,
specially when the user is doing GIS analysis for a long time.

In ArcGIS 9.1 or 9.2 ESRI removed the Analysis tools from Menu and put them
all on ArcToolbox. A lot of users complained and they ended up creating a
Geoprocessing menu with Intersection, Union etc. Perhaps something similar
could be done in QGIS.




On Tue, Apr 16, 2013 at 5:34 PM, Anita Graser anitagra...@gmx.at wrote:

 Hi,

 I know this thread has been silent for a while but I think it's important
 to
 bring it up once more.
 I'm currently trying to develop some materials and wondering if they should
 cover ftools/GDAL or Sextante mainly. Currently, it sounds like it is
 certain that Sextante will be around in future versions while the future of
 ftools/GDAL tools is less certain.

 I don't care much about ftools. I don't like having to create new
 Shapefiles
 every time I run an algorithm. I never managed to remember which tool is in
 which submenu.

 In case of GDAL tools, I see the advantage of being able to copy the GDAL
 code.

 In Sextante, it's easy to find the tools by name and the results can be
 temporal layers. So I strongly disagree with previous arguments that
 Sextante is not valuable from a user perspective.

 Even if we don't reach a consensus whether both menus and toolbox should be
 around permanently, could someone please confirm what will be the situation
 in 2.0? Are there any plans to remove anything for the release? Have any
 decisions been made for after 2.0 yet?

 Thanks and best wishes,
 Anita



 --
 View this message in context:
 http://osgeo-org.1560.x6.nabble.com/fTools-and-GdalTools-sextante-vs-original-plugins-tp5041430p5047360.html
 Sent from the Quantum GIS - Developer mailing list archive at Nabble.com.
 ___
 Qgis-developer mailing list
 Qgis-developer@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/qgis-developer

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Adding a project as a reference

[Filipe Dias]

Hi,
Not sure if its related and/or relevant for this issue, but Sextante has
also been affected by std::bad_alloc error:

http://hub.qgis.org/issues/6228

Best regards


On Tue, Nov 27, 2012 at 8:55 AM, Marco Hugentobler 
marco.hugentob...@sourcepole.ch wrote:

 std::bad_alloc
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

[Qgis-developer] Sextante broken on Master

[Filipe Dias]

Hi, Sextante is currently broken. Upon opening QGIS this shows up.

Tested on Ubuntu 12.04

Regards



Couldn't load plugin sextante due an error when calling its classFactory()
method

Traceback (most recent call last):
  File /usr/lib/python2.7/dist-packages/qgis/utils.py, line 188, in
startPlugin
plugins[packageName] = package.classFactory(iface)
  File /usr/share/qgis/python/plugins/sextante/__init__.py, line 45, in
classFactory
from sextante.SextantePlugin import SextantePlugin
  File /usr/lib/python2.7/dist-packages/qgis/utils.py, line 384, in
_import
mod = _builtin_import(name, globals, locals, fromlist, level)
  File /usr/share/qgis/python/plugins/sextante/SextantePlugin.py, line
34, in
from sextante.core.Sextante import Sextante
  File /usr/lib/python2.7/dist-packages/qgis/utils.py, line 384, in
_import
mod = _builtin_import(name, globals, locals, fromlist, level)
  File /usr/share/qgis/python/plugins/sextante/core/Sextante.py, line 19,
in
from sextante.servertools.GeoServerToolsAlgorithmProvider import
GeoServerToolsAlgorithmProvider
  File /usr/lib/python2.7/dist-packages/qgis/utils.py, line 384, in
_import
mod = _builtin_import(name, globals, locals, fromlist, level)
ImportError: No module named servertools.GeoServerToolsAlgorithmProvider

Python version:
2.7.3 (default, Aug  1 2012, 05:25:23)
[GCC 4.6.3]


QGIS version:
1.9.0-Master Master, exported

Python path: ['/usr/share/qgis/python', '/home/fd/.qgis//python',
'/home/fd/.qgis//python/plugins', '/usr/share/qgis/python/plugins',
'/usr/lib/python2.7', '/usr/lib/python2.7/plat-linux2',
'/usr/lib/python2.7/lib-tk', '/usr/lib/python2.7/lib-old',
'/usr/lib/python2.7/lib-dynload', '/usr/local/lib/python2.7/dist-packages',
'/usr/lib/python2.7/dist-packages', '/usr/lib/python2.7/dist-packages/PIL',
'/usr/lib/python2.7/dist-packages/gst-0.10',
'/usr/lib/python2.7/dist-packages/gtk-2.0', '/usr/lib/pymodules/python2.7',
'/usr/lib/python2.7/dist-packages/ubuntu-sso-client',
'/usr/lib/python2.7/dist-packages/ubuntuone-client',
'/usr/lib/python2.7/dist-packages/ubuntuone-control-panel',
'/usr/lib/python2.7/dist-packages/ubuntuone-couch',
'/usr/lib/python2.7/dist-packages/ubuntuone-installer',
'/usr/lib/python2.7/dist-packages/ubuntuone-storage-protocol',
'/usr/lib/python2.7/dist-packages/wx-2.8-gtk2-unicode',
'/usr/share/qgis/python/plugins/fTools/tools']
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer