Hi Vaclav, 2013/9/21 Vaclav Petras <[email protected]>: > Hi, > > when I saw recent changes [1] in > > grass/trunk/vector/v.mapcalc/ > > I realized that there is a v.mapcalc in trunk (compilation is disabled). > > However, here is also a v.mapcalc in GSoC project for temporal algebra [2]. > > I'm wondering how they compare with each other and what is the plan?
The v.mapcalc version of the GSoC project focuses on boolean operations between whole maps. It is not possible to access single features like points, lines or areas. It was implemented so that Thomas lean howto use lexer/parser and calling grass modules with pygrass. The boolean vector operations are the basis for the spatial part of the temporal vector algebra. I am not quite sure what grass/trunk/vector/v.mapcalc/ is capable of, or if there will be anyone willingly to finish this module? GSoC v.mapcalc will stay in the google repository. My plan is to cleanup and merge the code of the temporal algebra modules and to implement t.rast3d.mapcalc using PLY, so there will be t.rast.mapcalc, t.rast3d.mapcalc and t.vect.mapcalc. This code will then be moved into the temporal framework in grass7. Best regards Soeren > > Best, > Vaclav > > [1] https://trac.osgeo.org/grass/ticket/1321 > [2] > http://grasswiki.osgeo.org/wiki/GRASS_GSoC_2013_Temporal_GIS_Algebra_for_raster_and_vector_data_in_GRASS#v.mapcalc > > > > _______________________________________________ > grass-dev mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/grass-dev _______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
