[GRASS-dev] on the fly grass location
Hi all. As it has been discussed earlier, having location generated (and destroyed) on the fly would help a lot the casual qgis grass user to approach grass. The idea is to run an analysis by loading (r.external, v.external, v.in.ogr) data, generating a location from it, run, save the results as tif or shp, and destroy the location at the end, all without users noticing it (but explaining for future reuse). The good news is that here at the hackfest we got a voulnteer willing to help with the coding (preferably in Python). Welcome Peter Loewe! Anybody willing to help him with the first steps? All the best. -- http://www.faunalia.it/pc ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] on the fly grass location
On Sun, Nov 14, 2010 at 9:54 AM, Paolo Cavallini cavall...@faunalia.it wrote: Hi all. As it has been discussed earlier, having location generated (and destroyed) on the fly would help a lot the casual qgis grass user to approach grass. The idea is to run an analysis by loading (r.external, v.external, v.in.ogr) data, generating a location from it, run, save the results as tif or shp, and destroy the location at the end, all without users noticing it (but explaining for future reuse). The good news is that here at the hackfest we got a voulnteer willing to help with the coding (preferably in Python). Welcome Peter Loewe! Great, Peter! Anybody willing to help him with the first steps? Sure - note that all ingredients are already there including the demolocation which comes with any GRASS binary package. Maybe that's easier discussed over chat? Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] on the fly grass location
On Sun, Nov 14, 2010 at 10:24 AM, Markus Neteler nete...@osgeo.org wrote: On Sun, Nov 14, 2010 at 9:54 AM, Paolo Cavallini cavall...@faunalia.it wrote: Hi all. As it has been discussed earlier, having location generated (and destroyed) on the fly would help a lot the casual qgis grass user to approach grass. The idea is to run an analysis by loading (r.external, v.external, v.in.ogr) data, generating a location from it, run, save the results as tif or shp, and destroy the location at the end, all without users noticing it (but explaining for future reuse). The good news is that here at the hackfest we got a voulnteer willing to help with the coding (preferably in Python). Welcome Peter Loewe! Great, Peter! Anybody willing to help him with the first steps? Sure - note that all ingredients are already there including the demolocation which comes with any GRASS binary package. Maybe that's easier discussed over chat? Forgot to mention this Wiki page http://grass.osgeo.org/wiki/Working_with_GRASS_without_starting_it_explicitly Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
