[GRASS-user] a few suggestions and questions

Philipp Steigenberger userlist at online.de
Tue Mar 4 03:38:24 EST 2008


Carlos "Guâno" Grohmann schrieb:
> Hello all
> 
> first I'd like to make a few suggestions to enhance (IMO) our favorite GIS:
> 
> - normalize the options in all modules. I noticed that while most
> commands take "--overwrite", some (r.neighbors) use "-o"

I guess the problem is, that there are to many modules an it my be a lot 
of work to change them. Also "old" users are used to take the right 
option for the particular module. Another problem. Where to start? Some 
users have vers 6.2.3 others 6.3 svn others 6.3 rc5. If you change the 
manuals in the wiki all will be confused a little more, first of all the 
newbies. And finally there are also some parameters to be normalized. 
i.e  most times you have >output< for output. but sometimes >out< or 
 >elev< or >elevation<. So where to start and who will do?

> - some modules require a dummy value when output a list (r.mask,
> r.proj, v.proj..). Is this really necessary? this is a very confusing
> option (specially for newbies).
> - also, I think that _all_ fields (gui speaking now) where a
> raster/vector map is to be entered should have the select button, no
> matter if it is a field for new maps, because it makes the whole thing
> consistent, and it is easier for new users to understant how things
> work.
> 
> now some issues:
> 
> is plan curvature in r.param.scale broken? I can't get a map of it.
> profc works fine. Also is it possible to make r.param.scale work in
> latlong regions? (please?)
> 
> this is just out of curiosity:
> 
> if there are too many points to be used for interpolation by RST, how
> does it chooses which points will be used?
> 

Not sure.... some ideas: Try to set another region (g.region), use a 
mask_map (raster) or use the  where-parameter (v.surf.rst or v.extract)

> 
> thats all for now,
> 
> cheers
> 
> Carlos
> 


More information about the grass-user mailing list