[Qgis-developer] fTools and GdalTools: sextante vs original plugins
antoniolocandro at hotmail.com
Wed Apr 17 06:17:23 PDT 2013
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 tabletFilipe Dias <filipesdias at 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 <volayaf at 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!
2013/4/17 Bernhard Ströbl <bernhard.stroebl at 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
> Am 17.04.2013 07:42, schrieb Anita Graser:
>> On Wed, Apr 17, 2013 at 3:19 AM, Mathieu Pellerin <nirvn.asia at gmail.com
>> <mailto:nirvn.asia at 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
>> Best wishes,
> __________ Information from ESET Mail Security, version of virus signature
> database 8235 (20130416) __________
> The message was checked by ESET Mail Security.
> Qgis-developer mailing list
> Qgis-developer at lists.osgeo.org
Qgis-developer mailing list
Qgis-developer at lists.osgeo.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Qgis-developer