[GRASS-dev] Python-based v.mapcalc to Addons

[Vaclav Petras]

Hi Soeren,

I've tried v.mapcalc from Thomas' GSoC and I think it should go at least to
Addons. Does one of you want to commit it or should I do that? Some, rather
trivial, changes are need to make it work (attached), I can apply them
later if you want.

I also suggest removing the v.mapcalc which is now in addons. Perhaps the
functionality is different but since it was not finished, there is no
functionality which can be used. Unless somebody will work on it soon, I
don't see a reason to keep it there. (Alternatively, it can be renamed.)

Best,
Vaclav


On Tue, Oct 13, 2015 at 3:15 AM, Sören Gebbert <soerengebbert at googlemail.com
> wrote:

> Hi,
> the GSoC implementation of v.mapcalc is still available:
>
> https://code.google.com/p/grass-gis-temporal-algebra/source/browse/#svn%2Ftrunk%2Fv.mapcalc
>
> However, the approach in the GSoC v.mapcalc is very different from the
> v.mapcalc addon from 2002.
> The algebraic expressions are applied to whole vector maps, rather
> than single points, list of points, lines or polygons.
>
> Best regards
> Soeren
>
>
> 2015-10-13 3:53 GMT+02:00 Vaclav Petras <wenzeslaus at gmail.com>:
> >
> > On Mon, Oct 12, 2015 at 6:24 AM, Glynn Clements <
> glynn at gclements.plus.com>
> > wrote:
> >>
> >> Markus Neteler wrote:
> >>
> >> > <p.vanbreugel at gmail.com> wrote:
> >> > ...
> >> > > Sorry for the late follow up. The add-on installs now. When trying
> to
> >> > > run
> >> > > it, however, nothing happens.
> >> >
> >> > It does not have a parser (yet?), so I suppose it reads from stdin.
> >>
> >> Yes.
> >>
> >> But it doesn't have any code to read or write GRASS vectors, either.
> >> v.mapcalc appears to be a work-in-progress which hasn't actually made
> >> noticeable progress since it was added.
> >
> > Then I suggest to remove it from the Makefile parent directory and also
> > disable it in the addons build scripts if there is something more needed
> > than r66406 [1] which is blacklisting it somehow already. It does not
> > fulfill what user would expect (at least some functionality). Those who
> want
> > to continue development will get it through svn.
> >
> > I'm not sure happened [2] with the v.mapcalc implemented as a test case
> in
> > GSoC [3] and if the functionality can be still used. But this seems like
> a
> > good alternative to the code in addons.
> >
> > Vaclav
> >
> > [1] https://trac.osgeo.org/grass/changeset/66406
> > [2] https://lists.osgeo.org/pipermail/grass-dev/2013-October/065908.html
> > [3]
> >
> https://grasswiki.osgeo.org/wiki/GRASS_GSoC_2013_Temporal_GIS_Algebra_for_raster_and_vector_data_in_GRASS#v.mapcalc
> >
> > _______________________________________________
> > 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/20160104/c0374910/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: vmapcalc.patch
Type: text/x-patch
Size: 8631 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20160104/c0374910/attachment.bin>