this bug's URL: http://intevation.de/rt/webrt?serial_num=2885
-------------------------------------------------------------------------
Subject: g3d region problem
Platform: GNU/Linux/i386
grass obtained from: Trento Italy site
grass binary for platform: Compiled from Sources
GRASS Version: 5.7 weekly snapshot: 12-25-04
g3d-files appear to be immune to changes to the current region made by
d.zoom
example: A g3d-file is created from several rasters in a location (including
setting the r3-parameters for g.region). Then the current region is modified
by zooming in using d.zoom.
When NVIZ is now called up, the 2d-region settings are as to be expected,
yet the 3d-volume settings are way up in limbo: strange volumes (from outer
space?) roam the skies.
a workaround is to recreate the g3d-file after each zooming-step.
Cheers,
Peter Loewe
-------------------------------------------- Managed by Request Tracker
Request Tracker wrote:
this bug's URL: http://intevation.de/rt/webrt?serial_num=2885
-------------------------------------------------------------------------
Subject: g3d region problem
Platform: GNU/Linux/i386
grass obtained from: Trento Italy site
grass binary for platform: Compiled from Sources
GRASS Version: 5.7 weekly snapshot: 12-25-04
g3d-files appear to be immune to changes to the current region made by d.zoom
example: A g3d-file is created from several rasters in a location (including setting the r3-parameters for g.region). Then the current region is modified by zooming in using d.zoom. When NVIZ is now called up, the 2d-region settings are as to be expected, yet the 3d-volume settings are way up in limbo: strange volumes (from outer space?) roam the skies.
a workaround is to recreate the g3d-file after each zooming-step.
Cheers, Peter Loewe
The problem is in NVIZ or in the module creating the raster 3D?
Can you post the output from?:
g.region -p3
r3.mapcalc "test=1"
r3.info test1
Radim