WxNviz
Back to wxGUI page.
See also manual page.
wxNviz is a wxGUI extension which allows users to realistically render multiple surfaces (raster data) in a 3D space, optionally using thematic coloring, draping 2D vector data over the surfaces, displaying 3D vector data in the space, and visualization of volume data (3D raster data).
Screenshots
-
2008-06-27: Display raster map from layer tree in 2.5D (surface)
-
2008-07-05: Support for vector data (2D lines) added
-
2008-07-26: Support for vector point data
-
2008-08-02: 3D vector data support
-
2008-08-09: Initial support for volumetric data
-
2010-05-31: 3D view tools window integrated into Layer Manager
-
Lighting control panel in Layer Manager (2010-06-17)
-
Fringe control panel in Layer Manager (2010-06-23)
-
Redirect messages to wxGUI (2010-08-08)
-
Displaying raster (surface), 2D vector and 3D raster (volume) in the 3D space (2010-08-16)
-
Surface page of WxNviz modified (2011-06-02)
-
Constant surface page added (2011-06-02)
-
Lighting fixed (2011-05-02)
-
Cutting planes (shading blend) (2011-06-10)
-
Cutting planes (shading top color) (2011-06-10)
-
View page modified (2011-06-10)
-
Picture of surfaces cut by two planes (generated by nviz_cmd) (2011-06-30)
-
Command for nviz_cmd generated by wxNviz (2011-07-01)
-
North Arrow implemented (2011-07-08)
-
Colored isosurfaces with transparency (2011-07-08)
-
Partially transparent slice (2011-07-14)
-
Combination of slices and isosurface (2011-07-14)
-
Raster legend, text label and north arrow (2011-07-22)
-
Thematic mapping (colors) for points (2011-08-05)
-
Dialog for v.colors opened from 3D view (2011-08-05)
Animations
Video tutorials
Older tutorials (2010)
Ideas
- Fog support (see [1], [2], [3])
- Vertical labels (take from geonames.org point data): like in http://tev.fbk.eu/marmota/blog/?p=82
- Second interactive light source for isosurface visualization
- Tick marks and coordinate values to x,y,z axis when drawing fringe
Known issues
- List of open and closed tickets
- Adding vector data crashes wxGUI on Mac
- Viewing height sometimes sets to 1 after switching to 2D and back to 3D View (or with the simultaneous 2D view - very nice feature) and even after View is reset, it keeps getting back at 1 each time the slider is touched
- Hopefully fixed in r46208
- Isosurfaces tested with Nags Head time series data (I will provide link) don't seem to be working, after setting 3D region and adding 3D raster nothing gets drawn, when moving the related DEM around only line rectangle shows instead of a box.
- Adding draw, draw current and clear button may be useful
- Thematic mapping is available in GRASS 7 only
- Display region in 3D does not change accordingly to display region in 2D in version <= 6.5
- Appearance:
- scale bar does not work with my terrestrial lidar x,y data (but it worked in grass7 with different data)
- add legend > OK: nothing gets drawn in 3D but the legend shows up when I switch to 2D but when I clicked delete scalebar (which was not drawn), my surface disapeared but the legend showed up along with white and black background (which I assume was supposed to be transparent, because when I moved the legend the surface was under it - we already discussed this, it may be my problem, because it works for Michael).
- General
- when I go from 3D view to 2D and then back to 3D I lose most of my settings (viewing position, zexag, fringe size etc. - this would be OK if I could get a warning and question whether I want to save my 3D viewing state before switching)
- similarly, when I add volume to Map layers I lose my view settings and the 3D view goes back to default
- Volumes:
- change of region by g.region seems to be ignored (or I missed something), I had to restart GRASS with the new region to get the 3D region for volumes right. Given that the default top, botom is 1,0, if GRASS starts with the default 3D region settings volumes do not work because there is just one level.
- isosurfaces work with my terrestrial lidar data but the slices don't, it seems that it is due my resolution being 0.3m, when I change it to 1m I get at least some limited slicing
- this may be in ogsf becuase slices in nviz do not work with this data either
- changing color to constant did not change the color of the isosurface