[GRASS-dev] [GRASS GIS] #3142: Implementing SLIC image segmentation

GRASS GIS trac at osgeo.org
Tue Dec 6 10:04:14 PST 2016


#3142: Implementing SLIC image segmentation
---------------------------+-------------------------------------
  Reporter:  SCrommelinck  |      Owner:  grass-dev@…
      Type:  enhancement   |     Status:  new
  Priority:  normal        |  Milestone:  7.2.0
 Component:  Imagery       |    Version:  unspecified
Resolution:                |   Keywords:  SLIC image segmentation
       CPU:  Unspecified   |   Platform:  Unspecified
---------------------------+-------------------------------------

Comment (by mlennert):

 Replying to [comment:6 rashadkm]:
 > Replying to [comment:5 mlennert]:
 > > Replying to [comment:4 rashadkm]:
 > > > Replying to [comment:3 mlennert]:
 > > > > After some discussion with MarkusM, I see three options, all based
 on the source code published at
 [http://ivrl.epfl.ch/research/superpixels], which is GPL3:
 > > > >
 > > > >  * Integrate the code as is into GRASS. Disadvantage: it's C++ and
 we would have to maintain it. Advantage: code exists, so less work, we
 would "only" have to write the GRASS io wrapper
 > > > >  * Translate the original code to C and integrate into GRASS.
 Disadvantage: more work, we have to maintain; Advantage: no C++, no
 installation by user, native implementation in GRASS
 > > > >  * Write a GRASS module that calls the compiled command line tool.
 Disadvantage: the user would have to install and compile the code.
 Advantage: less work for us, others maintain
 > > >
 > > > mortiz,
 > > > the second option seems better than others. right?
 > >
 > > I personally would prefer it, yes, but it means more work and someone
 has to do it. Are you volunteering ? :-)
 > I am interested to work.. given help from all grass devs ;).

 Well, maybe not all, but I'm willing to help, and we should definitely
 have MarkusM on board.

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/3142#comment:7>
GRASS GIS <https://grass.osgeo.org>



More information about the grass-dev mailing list