[GRASS5] r3.mapcalc doesn't work, isosurfaces

[Sören Gebbert]

Hi.

On Tuesday 22 November 2005 21:49, Joel Peter William Pitt wrote:
> Okay, I got the latest CVS version and there are r3.to.rast and 
> r3.in.rast in there. They just don't get compiled by default because 
> they are not in the raster3d Makefile.
> 
> I've managed to get my timeseries into a r3 file. However things are a 
> bit buggy it seems.

Are there bugs in r3.in.rast? And if yes, what kind of bugs? 
If there are bugs, i will try to fix them.
I know that in r3.to.rast the NULL handling was wrong, but
that was fixed some days ago in the CVS.

> 
> Is the following supposed to work for volumes?
> r3.mapcalc "test2=test"
> 
> At the moment any r3.mapcalc operations involving another r3 file seem 
> to result in a file full of nan's...
> 
> $ r3.info -r test
> min=1.000000
> max=1.000000
> 
> $ r3.info -r test2
> min=nan
> max=nan
> 
I have no problems. 

Mapset <data> in Location <slovakia3d>GRASS 6.1.cvs > r3.in.rast input=dem500 at PERMANENT output=dem3d
Open raster map dem500 at PERMANENT
Open raster map dem500
Open raster map dem500
Open raster map dem500
Open raster map dem500
Open raster map dem500
Creating 3D raster map
 100%
 100%
 100%
 100%
 100%
 100%
 Mapset <data> in Location <slovakia3d>GRASS 6.1.cvs > r3.info -r dem3d
min=0.000000
max=2230.092041
Mapset <data> in Location <slovakia3d>GRASS 6.1.cvs > r3.mapcalc "test = dem3d"
 100%
Mapset <data> in Location <slovakia3d>GRASS 6.1.cvs > r3.info -r test
min=0.000000
max=2230.092041
Mapset <data> in Location <slovakia3d>GRASS 6.1.cvs > 

What kind of maps (floar or double) and projection are you using? Are you using a mask?
I know that there are some problems with mask support in 3d maps. 

> Also, is the interpolation done by NVIZ on volumes able to handle 
> boolean values? Imagine a pyramid of value 1 surrounded by zero/null, 
> and occasional occurences of of cells equal to 1 outside of this 
> pyramid. I set a threshold of 1.0 on the volume in NVIZ but nothing 
> appears.... any ideas?

nope.

> 
> Thanks,
> Joel
> 
> Helena Mitasova wrote:
> 
> > I will leave others to answer your NULL question (just another reason 
> > to start working on new raster map storage format for GRASS7).
> >
> > Regarding using 3d rasters for storing timeseries we need it badly for 
> > the simwe programs and I tried to convert an output of simulation to 
> > 3d raster using
> > Soeren's r3.in.rast (I noticed it is not in GRASS CVS? - but you can 
> > get it from here:
> > http://www-pool.math.tu-berlin.de/~soeren/grass/modules/) and then 
> > convert back using r3.to.rast for viewing, analysis etc.
> > It works and if nothing else storing time series as 3d raster makes 
> > mapsets with multiple simulation runs much more manageable.
> > It would be great if you could test whether it also takes much less 
> > space and how it would work with 3d mask.
> > If it is indeed more space efficient, it may be worth to write few 
> > modules to work with such timeseries (e.g. extend xganim and 
> > r.out.mpeg to work with it, etc.).
> > I would then make it an option to write the timeseries output of simwe 
> > programs either as 2d rasters or a 3d single file.
> > Please, let me know whatever you find useful regarding to handling of 
> > timeseries in GRASS, it will help our work too,
> >
> > Helena
> >
> 
> 
> -- 
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> Joel Pitt, Room B534
> Bio-Protection & Ecology Division
> PO Box 84
> Lincoln University 8150
> New Zealand
>