WxNviz - Revision history

Neteler: remove hardcoded version specific urls, use latest version

2018-12-04T10:56:29Z

remove hardcoded version specific urls, use latest version

← Older revision		Revision as of 10:56, 4 December 2018
Line 3:		Line 3:
	'''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).		'''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).

	For usage instructions, see also the {{cmd\|wxGUI.nviz~~\|version=70~~\|desc=manual page}}.		For usage instructions, see also the {{cmd\|wxGUI.nviz\|desc=manual page}}.

	__TOC__		__TOC__

⚠️HamishBowman: /* See also */ +cats

2013-05-30T02:50:04Z

Neteler: + Troubleshooting

2013-05-25T15:44:46Z

+ Troubleshooting

← Older revision		Revision as of 15:44, 25 May 2013
Line 60:		Line 60:

	<strike></strike>		<strike></strike>

			== Troubleshooting ==

			* Nothing is rendered at all:
			: Please note that with wxGTK port of wxPython (Linux systems), a problem might appear during wxNviz initialization (nothing is rendered at all) or when rendering vectors (bad order of rendering surfaces and vectors). If you encounter such problems, try to change a depth buffer number in wxGUI Menu > Settings > Preferences > Map Display > Advanced (possible numbers are 0, 16, 24, 32). It is currently not possible to automatically find out the right number which is working for your computer.

	== Known issues ==		== Known issues ==

Neteler: fix wxGUI caps letter in links nightmare

2013-05-25T12:26:14Z

fix wxGUI caps letter in links nightmare

← Older revision		Revision as of 12:26, 25 May 2013
Line 3:		Line 3:
	'''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).		'''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).

	For usage instructions, see also the {{cmd\|wxGUI.~~Nviz~~\|version=70\|desc=manual page}}.		For usage instructions, see also the {{cmd\|wxGUI.nviz\|version=70\|desc=manual page}}.

	__TOC__		__TOC__

Neteler: make man page link more visible

2013-05-25T12:20:54Z

make man page link more visible

← Older revision		Revision as of 12:20, 25 May 2013
Line 1:		Line 1:
	Back to [[WxPython-based GUI for GRASS\|wxGUI]] page.		''(Back to [[WxPython-based GUI for GRASS\|wxGUI]] page.)''

	~~See~~ also {{cmd\|wxGUI.Nviz\|version=70\|desc=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).

			For usage instructions, see also the {{cmd\|wxGUI.Nviz\|version=70\|desc=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).
	__TOC__		__TOC__
	== Screenshots ==		== Screenshots ==

Annakrat: comparison of nviz and wxNviz functionality

2012-10-27T07:09:09Z

comparison of nviz and wxNviz functionality

@@ Line 80: / Line 80: @@
 ###this may be in ogsf becuase slices in nviz do not work with this data either </strike>
 #<strike>changing color to constant did not change the color of the isosurface</strike>
 == Google Summer of Code ==

Annakrat: /* Known issues */

2012-05-23T14:02:10Z

Known issues

⚠️Landa: /* Known issues */

2012-02-08T23:39:14Z

Known issues

← Older revision		Revision as of 23:39, 8 February 2012
Line 81:		Line 81:
	###this may be in ogsf becuase slices in nviz do not work with this data either		###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		#changing color to constant did not change the color of the isosurface

	~~[[Sv:Main Page/sv\|sv:Main Page/sv]]~~

	~~[[Pl:WxNviz/pl\|pl:WxNviz/pl]]~~

	~~[[Pl:WxNviz/pl\|pl:WxNviz/pl]]~~

	~~[[pl:WxNviz/pl\|pl:WxNviz/pl]]~~

	== Google Summer of Code ==		== Google Summer of Code ==

⚠️MilenaN: Reverted edits by Reverse22 (talk) to last revision by Helena

2011-12-30T21:32:37Z

Reverted edits by Reverse22 (talk) to last revision by Helena

← Older revision		Revision as of 21:32, 30 December 2011
Line 109:		Line 109:

	{{WxGUI}}		{{WxGUI}}


	~~==Other==~~
	~~[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse phone lookup]~~

	~~[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]~~

⚠️Reverse22 at 20:58, 30 December 2011

2011-12-30T20:58:48Z

← Older revision		Revision as of 20:58, 30 December 2011
Line 109:		Line 109:

	{{WxGUI}}		{{WxGUI}}


			==Other==
			[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse phone lookup]

			[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

← Older revision		Revision as of 02:50, 30 May 2013
Line 126:		Line 126:

	{{WxGUI}}		{{WxGUI}}

			[[Category:NVIZ]]
			[[Category:Visualization]]

← Older revision		Revision as of 14:02, 23 May 2012
Line 66:		Line 66:
	#<strike>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</strike>		#<strike>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</strike>
	#:Fixed in {{rev\|46208}}		#:Fixed in {{rev\|46208}}
	#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		#Adding draw, draw current and clear button may be useful
	#Thematic mapping is available in GRASS 7 only		#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		#Display region in 3D does not change accordingly to display region in 2D in version <= 6.5
	#Appearance:		#Appearance:
	## I need to click View tab to get the arrow draw, same for the scale bar		## I <strike>need to click View tab to get the arrow draw, same for the scale bar </strike>
	##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).		##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		#General
	##<strike>when I go from 3D view to 2D and then back to 3D I lose most of my settings </strike>		##<strike>when I go from 3D view to 2D and then back to 3D I lose most of my settings </strike>
	##similarly, when I add volume to Map layers I lose my view settings and the 3D view goes back to default		##<strike>similarly, when I add volume to Map layers I lose my view settings and the 3D view goes back to default </strike>
	#Volumes:		#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.		##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		##<strike>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		###this may be in ogsf becuase slices in nviz do not work with this data either </strike>
	#changing color to constant did not change the color of the isosurface		#<strike>changing color to constant did not change the color of the isosurface</strike>

	== Google Summer of Code ==		== Google Summer of Code ==