Re: [GRASS-dev] [GRASS GIS] #1898: adding foss4g-na news item or link from the homepage

#1898: adding foss4g-na news item or link from the homepage --+- Reporter: hamish | Owner: grass-dev@… Type: enhancement | Status: closed Priority: normal

[GRASS-dev] GRASS GSoC idea: Temporal GIS algebra for raster and vector data

Hi all, i would like to participate in the GSoC project this year as mentor for the Temporal GIS algebra for vector and raster data[1] idea. I would like to suggest my colleague Thomas Leppelt[2] as GSoC student who implements the temporal GIS algebra modules. Thomas is a PhD student at our

Re: [GRASS-dev] [GRASS GIS] #1889: wxPy loc'n wiz: don't auto-launch into PERMANENT

#1889: wxPy loc'n wiz: don't auto-launch into PERMANENT -+-- Reporter: hamish | Owner: grass-dev@… Type: defect | Status: new Priority: blocker

[GRASS-dev] could r.cost nearest option be backported to G6?

Hi, A group of colleagues need to use for several runs r.cost with the really useful option nearest (Name for output raster map with nearest start point) which is present in GRASS7. The problem is that for some reasons they can't install G7 but have to keep working for the moment on G6. Would it

Re: [GRASS-dev] could r.cost nearest option be backported to G6?

Margherita wrote: A group of colleagues need to use for several runs r.cost with the really useful option nearest (Name for output raster map with nearest start point) which is present in GRASS7. could someone put some info about what that does in the g7 help page? It would be nice to expand

[GRASS-dev] Python module gui inputs

Hi all, This is my first foray into grass scripting. I'm working on a GRASS 7 python module to create a local relief model from a lidar derived surface. The code works, but for some reason in the auto generated gui for the tool, the field to enter a neighborhood size to use for the low pass

Re: [GRASS-dev] Python module gui inputs

2013/2/27 Eric Goddard egoddard1...@gmail.com: Hi all, Hi Eric, Thanks, Eric #%module #% description: Creates a Local Relief Model from input raster. #% keywords: lrm #% keywords: lidar #% overwrite: yes #%end #%option G_OPT_R_INPUT #% key:input_map #% description: Select

[GRASS-dev] [GRASS GIS] #1899: v.transform man page needs update

#1899: v.transform man page needs update ---+ Reporter: jm | Owner: grass-dev@… Type: defect | Status: new Priority:

Re: [GRASS-dev] Python module gui inputs

Thanks for the response, Luca. I've made the change to the output option, but the neighbor_size option still isn't appearing in the gui. The descriptions will become more verbose once the code and everything is working; what is in the script now is just the bare minimum for it to run. and generate

Re: [GRASS-dev] [GRASS GIS] #1899: v.transform man page needs update

#1899: v.transform man page needs update ---+ Reporter: jm | Owner: grass-dev@… Type: defect | Status: new Priority:

Re: [GRASS-dev] GRASS GSoC idea: Temporal GIS algebra for raster and vector data

I think that is a great project - Soeren thanks for proposing the idea and volunteering as a mentor, Helena On Feb 27, 2013, at 5:37 AM, Sören Gebbert wrote: Hi all, i would like to participate in the GSoC project this year as mentor for the Temporal GIS algebra for vector and raster

Re: [GRASS-dev] [GRASS-user] i.landsat.toar

Hi, perhaps is it possible to have an old branch for grass6 add-ons like there are branch for each grass release ? there are also no more modules in the grass5 add-ons branch, it could be interresting to keep historical code, unmaintened like the grass core code but still available ! Sylvain