[GRASS-dev] Introduction and GSoC

Pierre Roudier pierre.roudier at gmail.com
Thu Apr 5 17:58:05 EDT 2012


As a user, I would also find the integration of say OTB in GRASS being a
plus - a very general segmentation algorithm like the watershed is provided
by OTB and is a handy tool at times. OTB being based on VTK, maybe you
could make use of some of Soeren's work on the vtk-grass-bridge?

On Apr 4, 2012 4:47 PM, "Eric Momsen" <eric.momsen at gmail.com> wrote:

> On Tue, Apr 3, 2012 at 9:57 AM, Moritz Lennert
> <mlennert at club.worldonline.be> wrote:
> > I personally am a bit weary of increasing dependencies between packages,
> but
> > at the same time, why re-invent the wheel. Integrating the OTB algorithms
> > into GRASS would definitely be a great plus.
> >
> > This said, several FOSS4G programs out there already play the role of
> > integrators (e.g. QGIS, gvSIG) and I'm not sure that GRASS should try to
> go
> > the same direction. Generally, I'd say: let GRASS do really well what it
> > does, and not try to integrate everything.
> >
> This does sound critical to me.  Being "new" to GIS, I have been
> struggling to figure out what the differences (strength/weakness/etc)
> are between GRASS, QGIS, etc.  I started with GRASS and R and haven't
> had time to try out the other programs, so am only comparing based on
> what each website describes.  I haven't found any feature comparison
> table.  So I am interested to hear what everyone has to say about what
> packages should (or should not) be integrated into GRASS vs. what
> packages GRASS is integrated into...but I suspect it is a bigger issue
> than can be answered in a GSoC project. :)
> _______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/grass-dev/attachments/20120406/4f8fbcb4/attachment.html

More information about the grass-dev mailing list