[GRASS-dev] Introduction for GSoC 2017

[Vaclav Petras]

On Wed, Mar 15, 2017 at 3:00 AM, Moritz Lennert <
mlennert at club.worldonline.be> wrote:

>
> >
> >> - A tool to attribute class values to raster objects. This is much
> >>   simpler and "just" a combination of GUI + r.what + form to add a
> >>   value + writing everything to a text file. In other words, it is
> >the
> >>   current GUI raster interrogation tool enhanced to add a value and
> >to
> >>   write info to a file.
> >>
> >
> >This sounds like raster attribute table for GRASS GIS. This needs some
> >serious design.
>
> No, I was not aiming for raster attribute tables. The main motivation for
> me is that when you create segments in an object-based image analysis
> approach and you want to then extract some objects as training objects this
> is currently not easy to do. For such training you have to identify the
> objects and indicate which class they're in. My idea is not to store this
> info within the gisdbase, but to output it to text file (yes, again ;-))
> which can then be used as input to further treatment (e.g. v.class.mlR &
> co).
>
>
>
I don't say that this can't be implemented through external CSV files and
the tools for handling them and transferring raster values into them are
generally useful. The thing I'm uncomfortable about is that it looks like a
raster attribute table from user point of view but it is different and also
at one point CSV won't be enough for some they will need actual database or
SQL. We had ASCII vectors in the past... (not that I would be around for
that ;-)

>Moritz and all,
> >
> >in cases like this, when a GSoC idea can be split into a separate
> >features
> >and they are reasonable feature requests (they wouldn't be part of the
> >idea
> >otherwise, right?), it would be good if we create the appropriate
> >tickets
> >for each of those. We did this last summer when we used keywords (tags)
> >`gsoc2016` and `cartography` for each ticket related to the GSoC
> >Cartography Improvements idea:
> >
> >https://trac.osgeo.org/grass/query?status=assigned&status=
> >closed&status=new&status=reopened&keywords=~gsoc2016+cartography
> >
> >For this idea it could be e.g. `gsoc2017` and `ImageAnalysisGUI`, but
> >please suggest something better (it must be one word, no spaces).
>
> +1
>
> Do you think we should create these tickets now, or as part of the first
> phase of the project ?



Yes, now.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20170319/43067ab6/attachment-0001.html>