[Qgis-developer] Re: Creating a Python plugin for OSSIM-QGIS
Peter Borissow
peter.borissow at yahoo.com
Sun Apr 22 11:33:45 EDT 2012
Makes sense. I guess the only doubt I have has to do with rendering the output from SEXTANTE. SEXTANTE would be used to construct an OSSIM image chain but for performance reasons, we'd want to pipe the output directly to the OSSIM image renderer without having to write out an intermediary file. Hopefully that will all be handled transparently bu the OSSIM image provider.
________________________________
From: Victor Olaya <volayaf at gmail.com>
To: Peter Borissow <peter.borissow at yahoo.com>
Cc: "qgis-developer at lists.osgeo.org" <qgis-developer at lists.osgeo.org>; Vipul Raheja <vipul.rahejaug08 at students.iiit.ac.in>; ossim users <ossim-developer at lists.sourceforge.net>
Sent: Sunday, April 22, 2012 10:59 AM
Subject: Re: [Qgis-developer] Re: Creating a Python plugin for OSSIM-QGIS
Right. That's the point, SEXTANTE handles the graphical stuff and the
integration in QGIS. The only thing the developer has to do to create
a SEXTANTE algorithm is to write the algorithm itself, the processing
part
Regards
El día 22 de abril de 2012 15:28, Peter Borissow
<peter.borissow at yahoo.com> escribió:
>
>> I think it makes more sense to have just ONE visual tool, that can
>> incororate ANY algorithm, and then plug all the algorithms into that
>> tool, whether they come from OSSIM, OTB, or whatever. That is, at
>> least, the idea behind SEXTANTE :-)
>
> Sure, no objections here.
>
> In that case, Vipul would simply develop python bindings for individual
> OSSIM algorithms (e.g. pan sharpening, orthorecitification, histogram
> matching, etc) and expose them in SEXTANTE. SETANTE would provide a visual
> front end to create processing chains. Correct?
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/qgis-developer/attachments/20120422/272ff23e/attachment-0001.html
More information about the Qgis-developer
mailing list