[GRASS5] NVIZ with volume + g.list -> rast3d

GRASS GIS GRASS GIS developer
1

Helena, Jaro,

I just tested the new NVIZ - it seems to work well,
congratulations!

I managed to visualize slices, but I didn't
understand yet how to visualize isosurfaces.
It may be useful to see the possible range
of data to select the appropriate value(s).

Thanks again for the nice enhancement,

Markus

PS: I have added 3D raster listing to g.list:
GRASS 5.7.cvs:~/grassdata > g.list rast3d
----------------------------------------------
raster3D files available in mapset jaro:
zrazky2.g3d

2

PS: I have added 3D raster listing to g.list:
GRASS 5.7.cvs:~/grassdata > g.list rast3d

Markus,

there is also g3.list for listing the 3d files (as well
as few other g3.* commands http://grass.itc.it/gdp/html_grass5/grid3d.html)
It looks like adding 3d option to the existing g.* commands is a better
approach than having separate g3.* commands (I find it more intuitive).
It is just a few commands (copy, rename, remove, region and projinfo/setproj)
and we can retire the g3.* scripts.

Helena

----------------------------------------------
raster3D files available in mapset jaro:
zrazky2.g3d

_______________________________________________
grass5 mailing list
grass5@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass5

3

I compiled the new 57 smoothly and tested nviz volumes again -
they work nicely. I would like to ask others to test it to make sure
that nothing is broken as this was a big addition - you can try
a ready to use location slovakia from here:

http://skagit.meas.ncsu.edu/~helena/grasswork/grassbookdat/slovakia3d.tar.gz

use dem500 for a DEM and there is only one 3D file precip3d.500z50 that you can use
for isosurfaces and cross-sections.
To see the isosurfaces use values between 600 and 1300
(the following image has 700 and 1000 with transparency of approx 100
and 1300 with no transparency) and set the polygon resolution to 3 or less
(note that for resolution 1 you may need to wait a little depending on your machine)
You should get something like this:
http://skagit.meas.ncsu.edu/~helena/grasswork/slovakiavol.jpg

the previous images are here
http://skagit.meas.ncsu.edu/~helena/grasswork/zrzky3dres1.jpg
http://skagit.meas.ncsu.edu/~helena/grasswork/zrazky3d.jpg

Markus, you can add it to the GRASS57 data sets, if you find it without problems,
it is the same one as we have for the book, updated for 57 by importing the sites
as vector data and by adding a grid3 file interpolated in GRASS53 - same parameters
as in the book, except grid3 is output. maybe we should rename it slovakia57
as we have with other locations.

I was able to get it not draw the isosurfaces (the previously reported problem)
when I ran it from a different mapset with no WIND3, it then gives a warning and uses
DEFAULTWIND3 which in my case was set for a different area.
You don't see the warning because nviz writes so
much stuff - so maybe it is time to make all that talking optional (I will
take out the references but Bob, would you be so kind and remove everything else
that is not necessary?)

There is a million little things that need to be done to have a decent
volume support in GRASS but we are getting there,

Helena

Markus Neteler wrote:

Helena, Jaro,

I just tested the new NVIZ - it seems to work well,
congratulations!

I managed to visualize slices, but I didn't
understand yet how to visualize isosurfaces.
It may be useful to see the possible range
of data to select the appropriate value(s).

Thanks again for the nice enhancement,

Markus

PS: I have added 3D raster listing to g.list:
GRASS 5.7.cvs:~/grassdata > g.list rast3d
----------------------------------------------
raster3D files available in mapset jaro:
zrazky2.g3d

_______________________________________________
grass5 mailing list
grass5@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass5

4

Wow! This is amazing. This has tremendous potential for archaeology (and
geosciences of course). Congratulations.

Michael

On 11/12/04 8:23 AM, "Helena" <hmitaso@unity.ncsu.edu> wrote:

I compiled the new 57 smoothly and tested nviz volumes again -
they work nicely. I would like to ask others to test it to make sure
that nothing is broken as this was a big addition - you can try
a ready to use location slovakia from here:

http://skagit.meas.ncsu.edu/~helena/grasswork/grassbookdat/slovakia3d.tar.gz

use dem500 for a DEM and there is only one 3D file precip3d.500z50 that you
can use
for isosurfaces and cross-sections.
To see the isosurfaces use values between 600 and 1300
(the following image has 700 and 1000 with transparency of approx 100
and 1300 with no transparency) and set the polygon resolution to 3 or less
(note that for resolution 1 you may need to wait a little depending on your
machine)
You should get something like this:
http://skagit.meas.ncsu.edu/~helena/grasswork/slovakiavol.jpg

the previous images are here
http://skagit.meas.ncsu.edu/~helena/grasswork/zrzky3dres1.jpg
http://skagit.meas.ncsu.edu/~helena/grasswork/zrazky3d.jpg

Markus, you can add it to the GRASS57 data sets, if you find it without
problems,
it is the same one as we have for the book, updated for 57 by importing the
sites
as vector data and by adding a grid3 file interpolated in GRASS53 - same
parameters
as in the book, except grid3 is output. maybe we should rename it slovakia57
as we have with other locations.

I was able to get it not draw the isosurfaces (the previously reported
problem)
when I ran it from a different mapset with no WIND3, it then gives a warning
and uses
DEFAULTWIND3 which in my case was set for a different area.
You don't see the warning because nviz writes so
much stuff - so maybe it is time to make all that talking optional (I will
take out the references but Bob, would you be so kind and remove everything
else
that is not necessary?)

There is a million little things that need to be done to have a decent
volume support in GRASS but we are getting there,

Helena

Markus Neteler wrote:

Helena, Jaro,

I just tested the new NVIZ - it seems to work well,
congratulations!

I managed to visualize slices, but I didn't
understand yet how to visualize isosurfaces.
It may be useful to see the possible range
of data to select the appropriate value(s).

Thanks again for the nice enhancement,

Markus

PS: I have added 3D raster listing to g.list:
GRASS 5.7.cvs:~/grassdata > g.list rast3d
----------------------------------------------
raster3D files available in mapset jaro:
zrazky2.g3d

_______________________________________________
grass5 mailing list
grass5@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass5

____________________
C. Michael Barton, Professor of Anthropology
School of Human Evolution and Social Change
PO Box 872402
Arizona State University
Tempe, AZ 85287-2402
USA

Phone: 480-965-6262
Fax: 480-965-7671
www: <www.public.asu.edu/~cmbarton>

5

I have added 2 modfications from Tomas to nviz volume support:

1. Default polygon resolution for drawing isosurfaces is now a smaller number
(higher resolution) to avoid situation when nothing is drawn.

2. Load state/Save state was added for volume objects.

Bob, after the nviz startup has changed, Load state/Save state does not work
- it gives an Error: can't read env(GISDBASE)
Can this be fixed before the release or should I file a bug report?

Let me know if there are any problems with the new additions,

Helena

6

On Sun, Dec 05, 2004 at 08:23:14PM -0500, Helena wrote:

I have added 2 modfications from Tomas to nviz volume support:

1. Default polygon resolution for drawing isosurfaces is now a smaller
number
(higher resolution) to avoid situation when nothing is drawn.

2. Load state/Save state was added for volume objects.

Bob, after the nviz startup has changed, Load state/Save state does not work
- it gives an Error: can't read env(GISDBASE)
Can this be fixed before the release or should I file a bug report?

Maybe the same thing as this one?

http://grass.itc.it/pipermail/grass5/2004-December/016320.html
(see at bottom).

Markus

7

Helena,

Helena wrote:

I have added 2 modfications from Tomas to nviz volume support:

1. Default polygon resolution for drawing isosurfaces is now a smaller number
(higher resolution) to avoid situation when nothing is drawn.

2. Load state/Save state was added for volume objects.

Bob, after the nviz startup has changed, Load state/Save state does not work
- it gives an Error: can't read env(GISDBASE)
Can this be fixed before the release or should I file a bug report?

I will grab the above updates today and look into fixing the above problem. My guess is that it should not be too difficult to fix. I will let you know.

Let me know if there are any problems with the new additions,

Helena

--
Bob

8

Helena,

I have applied a couple of nviz fixes to CVS.

I could not re-produce the GISDBASE error, but it was being generated from the fileBrowser.tcl script. It was looking from an "images" directory in your mapset. It is probably a throw-back to an earlier version for saving screen-captures to an "images" directory in your mapset. I have removed reference to GISDBASE and the the fileBrowser simply starts in your current directory (pwd).

I also fixed an error in attIsosurfPopup.tcl which complained about an unknown reference to DEBUG.

Everything else seems to be working fine.

--
Bob

Helena wrote:

I have added 2 modfications from Tomas to nviz volume support:

1. Default polygon resolution for drawing isosurfaces is now a smaller number
(higher resolution) to avoid situation when nothing is drawn.

2. Load state/Save state was added for volume objects.

Bob, after the nviz startup has changed, Load state/Save state does not work
- it gives an Error: can't read env(GISDBASE)
Can this be fixed before the release or should I file a bug report?

Let me know if there are any problems with the new additions,

Helena