[GRASS-dev] Re: [GRASS GIS] #814: r.resamp.stats memory corruption
when resampling from different projection/zone
GRASS GIS
trac at osgeo.org
Thu Nov 19 04:59:44 EST 2009
#814: r.resamp.stats memory corruption when resampling from different
projection/zone
-----------------------+----------------------------------------------------
Reporter: pertusus | Owner: grass-dev at lists.osgeo.org
Type: defect | Status: new
Priority: normal | Milestone: 6.4.0
Component: Raster | Version: 6.4.0 RCs
Resolution: | Keywords:
Platform: Linux | Cpu: x86-32
-----------------------+----------------------------------------------------
Comment (by pertusus):
Replying to [comment:1 glynn]:
>
> Whoa. This shouldn't be possible. Projections are per-location, not per-
mapset. I suggest running
> {{{
> g.region -d
> }}}
> in both mapsets, then trying again.
Ok, I indeed did wrong. After g.region -d in CRU_GRID the region from the
PERMANENT is reused in the mapset and indeed it works (but does nothing,
and certainly doesn't do what I want to...).
> I'm curious as to how you ended up with a WIND file with a different
projection than the DEFAULT_WIND file. If it's because you copied a mapset
directory from one location to another, the answer is "don't do that".
I do this all the time to start a new location, I didn't find another way
to do it not manually (I have a location with only PERMANENT with only
DEFAULT_WIND PROJ_INFO PROJ_UNITS WIND
and I copy it). And I also did it in that case, I took those files from a
different location and put them in the mapset... I found it a bit
cumbersome, but I thought that it was the only way to be able to do what I
want to. Looks like I was wrong, if mapsets have to share a projection,
then, indeed, I am still missing something. Back to the documentation, I
guess.
In any case the memory corruption is certainly something to fix.
--
Ticket URL: <http://trac.osgeo.org/grass/ticket/814#comment:2>
GRASS GIS <http://grass.osgeo.org>
More information about the grass-dev
mailing list