On Tue, Jun 5, 2012 at 8:13 AM, Marco Hugentobler
wrote:
>> A solution
>> would be to port the core SEXTANTE interfaces to c++ and add Python
>> wrappers to PyQGIS
>
> This is a good idea. That way (c++), other plugins could use the core
> sextante functions, e.g. to automatically define process c
Il 05/06/2012 08:13, Marco Hugentobler ha scritto:
> Would it be possible to include the native QGIS algorithms to sextante via
> Python
> bindings of the analysis lib (adding sip files where they are missing)?
>
>> A solution
>> would be to port the core SEXTANTE interfaces to c++ and add Pytho
Hi all
Would it be possible to include the native QGIS algorithms to sextante
via Python bindings of the analysis lib (adding sip files where they are
missing)?
A solution
would be to port the core SEXTANTE interfaces to c++ and add Python
wrappers to PyQGIS
This is a good idea. That way (
Il 01/06/2012 12:56, Nathan Woodrow ha scritto:
> but QGIS is only exposed via Python and C++ so it has to be called
> that way. Most of the other apps it calls are command line based apps
> and hence calling the executable make sense.
see also http://hub.qgis.org/issues/5705
thanks.
--
Paolo Ca
> but it calls directly the executables
but QGIS is only exposed via Python and C++ so it has to be called
that way. Most of the other apps it calls are command line based apps
and hence calling the executable make sense.
- Nathan
On Fri, Jun 1, 2012 at 8:21 PM, Paolo Cavallini wrote:
> Il 01/
Il 01/06/2012 12:20, Martin Dobias ha scritto:
> Yes because SEXTANTE is written in Python :-)
but it calls directly the executables
--
Paolo Cavallini - Faunalia
www.faunalia.eu
Full contact details at www.faunalia.eu/pc
___
Qgis-developer mailing li
On Fri, Jun 1, 2012 at 11:49 AM, Paolo Cavallini wrote:
> Il 01/06/2012 11:43, Martin Dobias ha scritto:
>> The main issue right now with native QGIS algorithms is that they are
>> implemented in c++ (if not counting fTools and GdalTools), so binding
>> them to the python SEXTANTE interfaces would
Il 01/06/2012 11:43, Martin Dobias ha scritto:
> The main issue right now with native QGIS algorithms is that they are
> implemented in c++ (if not counting fTools and GdalTools), so binding
> them to the python SEXTANTE interfaces would be cumbersome. A solution
> would be to port the core SEXTANT
Hi Victor
On Fri, Jun 1, 2012 at 9:19 AM, Victor Olaya wrote:
> It is feasible if QGIS exposes those algorithms and they are
> documented. I tried myself to implement the GPS processes in QGIS, but
> I could not find any docs about them, so I did not know how to call
> them. As loong as there is
It's an excellent idea. It would be great to be able to use those commands
via the Model Builder.
On Fri, Jun 1, 2012 at 8:19 AM, Victor Olaya wrote:
> It is feasible if QGIS exposes those algorithms and they are
> documented. I tried myself to implement the GPS processes in QGIS, but
> I could
It is feasible if QGIS exposes those algorithms and they are
documented. I tried myself to implement the GPS processes in QGIS, but
I could not find any docs about them, so I did not know how to call
them. As loong as there is a way of calling them, they can be wrapped
and included into SEXTANTE
R
Hi all.
Would it be feasible and reasonable to add QGIS as a backed of sextante? This
would
be useful from user point of view, to be able to run the same analyses in all
different ways. See e.g. slope and aspect: now it can be done from QGIS GUI
through
grass, gdal, and native commands, and throu
12 matches
Mail list logo
