[GRASS-dev] Re: [GRASS-user] problems using r.proj with large
hamish_nospam at yahoo.com
Thu Feb 8 19:09:32 EST 2007
William Kyngesburye wrote:
> Other than the memory option and module name, it doesn't really say
> how it operates differently from r.proj. Some hint about situations
> one might want to use it would be good. Maybe mention that there
> will be more disk activity.
> Add cross-references in each to the other. Both see-also links, and
> in r.proj, a hint about using r.proj.seg for large rasters and where
> memory is limited.
Is the long term plan to fully replace r.proj with r.proj.seg after
r.proj.seg gets enough testing?
> G_mapset() does one-shot initialisation, i.e. it takes a copy of the
> value of the MAPSET variable the first time that it's called, and
> returns the copied value thereafter. G__mapset() returns the value
so will this fix the imediate problem? G__tempfile()
sprintf (name, "%d.%d", pid, uniq++) ;
- G__file_name (path, element, name, G_mapset()) ;
+ G__file_name (path, element, name, G__mapset()) ;
More information about the grass-dev