Quick wxGUI tutorial - Revision history

Neteler: Define region first when creating new fractal surface map

2015-08-08T12:41:41Z

Define region first when creating new fractal surface map

← Older revision		Revision as of 12:41, 8 August 2015
Line 66:		Line 66:
	===Create a random surface===		===Create a random surface===

	Now let's create a new map. Select <tt>Raster → Generate		Now let's create a new raster map.
	surfaces → Fractal surface</tt> from the menu (near the bottom);
			We first define the extent and resolution of this map. For simplicity, we select a predefined region with the spatial extent of Wake county, Raleigh (NC, USA) and spatial resolution of 30m: Select <tt>Settings → Region → Set region</tt> from the main menu. In this dialog window, select 'wake_30m' for the parameter <tt>Set current region from named region</tt>; and click [Run] (i.e, it defines the [[Computational region]] for raster computations).

			Now select <tt>Raster → Generate surfaces → Fractal surface</tt> from the menu (near the bottom);
	give your new map a name; adjust any options you like in the Options		give your new map a name; adjust any options you like in the Options
	tab (the defaults are fine); and click [Run].		tab (the defaults are fine); and click [Run].

Neteler: /* Setup */

2014-09-07T03:42:05Z

Setup

← Older revision		Revision as of 03:42, 7 September 2014
Line 15:		Line 15:
	== Setup ==		== Setup ==

	This tutorial assumes that you've already [http://grass.osgeo.org/download/ installed GRASS GIS], and have downloaded either the [http://grass.osgeo.org/download/sample-data/ ~~Spearfish or~~ North Carolina sample datasets] from our ~~downloads~~ web page. You'll want to uncompress them first, ~~perhaps~~ into a directory called "grassdata" in your home directory.		This tutorial assumes that you've already [http://grass.osgeo.org/download/ installed GRASS GIS], and have downloaded either the [http://grass.osgeo.org/download/sample-data/ North Carolina sample datasets] from our download web page. You'll want to uncompress them first, ideally into a directory called "grassdata" in your home directory.
	Almost all the [http://grass.osgeo.org/documentation/manuals/ help pages], [http://grass.osgeo.org/documentation/tutorials/ tutorials], and [http://grass.osgeo.org/documentation/books/ books] use these two datasets in their examples, so they are worth grabbing.		Almost all the [http://grass.osgeo.org/documentation/manuals/ help pages], [http://grass.osgeo.org/documentation/tutorials/ tutorials], and [http://grass.osgeo.org/documentation/books/ books] use these two datasets in their examples, so they are worth grabbing.

Neteler: /* Further reading */

2012-12-28T09:26:18Z

Neteler: add links

2012-12-28T09:24:16Z

add links

← Older revision		Revision as of 09:24, 28 December 2012
Line 15:		Line 15:
	== Setup ==		== Setup ==

	This tutorial assumes that you've already installed GRASS, and have downloaded either the Spearfish or North Carolina sample datasets from our downloads web page. You'll want to uncompress them first, perhaps into a directory called "grassdata" in your home directory.		This tutorial assumes that you've already [http://grass.osgeo.org/download/ installed GRASS GIS], and have downloaded either the [http://grass.osgeo.org/download/sample-data/ Spearfish or North Carolina sample datasets] from our downloads web page. You'll want to uncompress them first, perhaps into a directory called "grassdata" in your home directory.
	Almost all the help pages, tutorials, and books use these two datasets in their examples, so they are worth grabbing.		Almost all the [http://grass.osgeo.org/documentation/manuals/ help pages], [http://grass.osgeo.org/documentation/tutorials/ tutorials], and [http://grass.osgeo.org/documentation/books/ books] use these two datasets in their examples, so they are worth grabbing.

	==Running==		==Running==

⚠️HamishBowman: /* Other things to try */

2012-07-25T04:04:26Z

Other things to try

← Older revision		Revision as of 04:04, 25 July 2012
Line 173:		Line 173:
	===Other things to try===		===Other things to try===

	While not covered here, you may like to experiment with the new Cartographic Composer and object-oriented Graphical Modeling Tool; you'll find icons to launch them on the [[wxGUI]] help pages.		While not covered here, you may like to experiment with the new Cartographic Composer and object-oriented Graphical Modeling Tool; you'll find icons to launch them on the lower row of icons in the ''Layer Manager'' window. Further details can be found in [[wxGUI]] help pages.

	The new GUI is written in Python, and if you're a fan of Python programming there are a number of great tools available to you. In the bottom of the 'Layer Manager' window click on the 'Python shell' tab and type ''help(grass.core)'' to see a listing of the functions available in the core GIS python library. Besides the core GIS functions there is also 'array' (NumPy), 'db' (database), 'raster', and 'vector' libraries available. For advanced use 'Pythons CTypes' is supported allowing the Python programmer access to GRASS's extensive C libraries.		The new GUI is written in Python, and if you're a fan of Python programming there are a number of great tools available to you. In the bottom of the 'Layer Manager' window click on the 'Python shell' tab and type ''help(grass.core)'' to see a listing of the functions available in the core GIS python library. Besides the core GIS functions there is also 'array' (NumPy), 'db' (database), 'raster', and 'vector' libraries available. For advanced use 'Pythons CTypes' is supported allowing the Python programmer access to GRASS's extensive C libraries.

⚠️HamishBowman: /* Other things to try */

2012-07-25T04:00:37Z

Other things to try

← Older revision		Revision as of 04:00, 25 July 2012
Line 173:		Line 173:
	===Other things to try===		===Other things to try===

	While not covered in here, you may like to experiment with the new Cartographic Composer and object-oriented Graphical Modeling Tool; you'll find icons to launch them on the [[wxGUI]] help pages.		While not covered here, you may like to experiment with the new Cartographic Composer and object-oriented Graphical Modeling Tool; you'll find icons to launch them on the [[wxGUI]] help pages.

	The new GUI is written in Python, and if you're a fan of Python programming there are a number of great tools available to you. In the bottom of the 'Layer Manager' window click on the 'Python shell' tab and type ''help(grass.core)'' to see a listing of the functions available in the core GIS python library. Besides the core GIS functions there is also 'array' (NumPy), 'db' (database), 'raster', and 'vector' libraries available. For advanced use 'Pythons CTypes' is supported allowing the Python programmer access to GRASS's extensive C libraries.		The new GUI is written in Python, and if you're a fan of Python programming there are a number of great tools available to you. In the bottom of the 'Layer Manager' window click on the 'Python shell' tab and type ''help(grass.core)'' to see a listing of the functions available in the core GIS python library. Besides the core GIS functions there is also 'array' (NumPy), 'db' (database), 'raster', and 'vector' libraries available. For advanced use 'Pythons CTypes' is supported allowing the Python programmer access to GRASS's extensive C libraries.

⚠️HamishBowman: /* 3D visualization */

2012-07-25T03:47:52Z

3D visualization

← Older revision		Revision as of 03:47, 25 July 2012
Line 162:		Line 162:
	===3D visualization===		===3D visualization===

	[[Image:grass-nviz.png\|400px\|~~center~~]]		[[Image:grass-nviz.png\|400px\|right]]

	Start the 3D visualization suite from the <tt>File → NVIZ</tt>		Start the 3D visualization suite from the <tt>File → NVIZ</tt>

⚠️HamishBowman: reshuffle sections

2012-07-25T03:47:03Z

reshuffle sections

← Older revision		Revision as of 03:47, 25 July 2012
Line 1:		Line 1:
	<center><font color="#409840">_\\|/_ GRASS 6.4 _\\|/_</font></center>		<!-- <center><font color="#409840">_\\|/_ GRASS 6.4 _\\|/_</font></center> -->
	==About==		==About==

Line 21:		Line 21:

	To run GRASS, click on the GRASS link on the desktop or from the system menu. From the "Welcome to GRASS" window select either the Spearfish or North Carolina (nc_spm_08) sample datasets for the location, and "user1" for the mapset, then click on [Start Grass].		To run GRASS, click on the GRASS link on the desktop or from the system menu. From the "Welcome to GRASS" window select either the Spearfish or North Carolina (nc_spm_08) sample datasets for the location, and "user1" for the mapset, then click on [Start Grass].

			This will launch GRASS with our [[wxGUI\|brand new GUI written in wxPython]].

			<!--
	This will launch GRASS with our brand new GUI written in wxPython. At		This will launch GRASS with our brand new GUI written in wxPython. At
	the time of writing we have gotten just about all of the kinks out of		the time of writing we have gotten just about all of the kinks out of
Line 27:		Line 30:
	Tcl/Tk GUI is still available if you prefer to use that; you can start		Tcl/Tk GUI is still available if you prefer to use that; you can start
	it by typing <em>g.gui --ui</em> on the command line.		it by typing <em>g.gui --ui</em> on the command line.
			-->

	===Displaying maps===		===Displaying maps===
Line 155:		Line 159:

	Now let's look at the attribute table and SQL builder in more detail. In the 'Layer Manager' click the table icon, it's second from the left on the bottom row. This will open a view of the attached database table. For now we'll just do a simple database query to find watershed basins without a lot of variation in them. Where it says ''SELECT * FROM basin_areas WHERE'' pick ''elev_stdde'' from the pull down list for the standard deviation statistic, then in the text box to its right enter ''< 50'' and click [Apply]. You'll notice the number of loaded records in the information bar along the bottom of the window has shrunk, and that all of the rows with large values for std. dev. are now gone from the displayed table. Right-click on the table data and choose ''Select all''. Again right-click on the table data and this time choose ''Highlight selected features''. You should see e.g. alluvial flood basins and mesas show up in the ''Map Display''.		Now let's look at the attribute table and SQL builder in more detail. In the 'Layer Manager' click the table icon, it's second from the left on the bottom row. This will open a view of the attached database table. For now we'll just do a simple database query to find watershed basins without a lot of variation in them. Where it says ''SELECT * FROM basin_areas WHERE'' pick ''elev_stdde'' from the pull down list for the standard deviation statistic, then in the text box to its right enter ''< 50'' and click [Apply]. You'll notice the number of loaded records in the information bar along the bottom of the window has shrunk, and that all of the rows with large values for std. dev. are now gone from the displayed table. Right-click on the table data and choose ''Select all''. Again right-click on the table data and this time choose ''Highlight selected features''. You should see e.g. alluvial flood basins and mesas show up in the ''Map Display''.

	~~===Other things to try===~~

	~~While not covered in here, you may like to experiment with the new Cartographic Composer and object-oriented Graphical Modeling Tool; you'll find icons to launch them on the [[wxGUI]] help pages.~~

	The new GUI is written in Python, and if you're a fan of Python programming there are a number of great tools available to you. In the bottom of the 'Layer Manager' window click on the 'Python shell' tab and type ''help(grass.core)'' to see a listing of the functions available in the core GIS python library. Besides the core GIS functions there is also 'array' (NumPy), 'db' (database), 'raster', and 'vector' libraries available. For advanced use 'Pythons CTypes' is supported allowing the Python programmer access to GRASS's extensive C libraries.

	===3D visualization===		===3D visualization===
Line 172:		Line 170:
	Select <tt>Visualize→Raster Surfaces</tt> from the menu, and		Select <tt>Visualize→Raster Surfaces</tt> from the menu, and
	set the fine resolution to "1", then move the positioning puck and height slider around to get different views.		set the fine resolution to "1", then move the positioning puck and height slider around to get different views.

			===Other things to try===

			While not covered in here, you may like to experiment with the new Cartographic Composer and object-oriented Graphical Modeling Tool; you'll find icons to launch them on the [[wxGUI]] help pages.

			The new GUI is written in Python, and if you're a fan of Python programming there are a number of great tools available to you. In the bottom of the 'Layer Manager' window click on the 'Python shell' tab and type ''help(grass.core)'' to see a listing of the functions available in the core GIS python library. Besides the core GIS functions there is also 'array' (NumPy), 'db' (database), 'raster', and 'vector' libraries available. For advanced use 'Pythons CTypes' is supported allowing the Python programmer access to GRASS's extensive C libraries.

	===Shutdown and the command line===		===Shutdown and the command line===

⚠️HamishBowman: /* Vector modules */ attrib table and other stuff to try

2012-07-25T03:38:10Z

Vector modules: attrib table and other stuff to try

← Older revision		Revision as of 03:38, 25 July 2012
Line 154:		Line 154:
	You can colorize the areas based on the average elevation values using the {{Cmd\|v.colors}} module. In the Vector menu select 'Manage colors → Color tables'. Select ''basin_areas'' for the input vector map, the ''elev_mean'' attribute column for the column containing the numeric range, and in the 'Colors' tab have it copy the colors from the 'elevation' raster map. After running that right-click on the ''basin_areas'' map in the Layer List and select 'Properties'. In the 'Colors' tab tick the box for getting colors from the map table column. Once you click [Apply] you should see the colors change in the 'Map Display' window.		You can colorize the areas based on the average elevation values using the {{Cmd\|v.colors}} module. In the Vector menu select 'Manage colors → Color tables'. Select ''basin_areas'' for the input vector map, the ''elev_mean'' attribute column for the column containing the numeric range, and in the 'Colors' tab have it copy the colors from the 'elevation' raster map. After running that right-click on the ''basin_areas'' map in the Layer List and select 'Properties'. In the 'Colors' tab tick the box for getting colors from the map table column. Once you click [Apply] you should see the colors change in the 'Map Display' window.

	* ''~~TODO~~''~~: open attribute~~ table ~~editor~~ and ~~build~~ a ~~SQL query~~.		Now let's look at the attribute table and SQL builder in more detail. In the 'Layer Manager' click the table icon, it's second from the left on the bottom row. This will open a view of the attached database table. For now we'll just do a simple database query to find watershed basins without a lot of variation in them. Where it says ''SELECT * FROM basin_areas WHERE'' pick ''elev_stdde'' from the pull down list for the standard deviation statistic, then in the text box to its right enter ''< 50'' and click [Apply]. You'll notice the number of loaded records in the information bar along the bottom of the window has shrunk, and that all of the rows with large values for std. dev. are now gone from the displayed table. Right-click on the table data and choose ''Select all''. Again right-click on the table data and this time choose ''Highlight selected features''. You should see e.g. alluvial flood basins and mesas show up in the ''Map Display''.

			===Other things to try===

			While not covered in here, you may like to experiment with the new Cartographic Composer and object-oriented Graphical Modeling Tool; you'll find icons to launch them on the [[wxGUI]] help pages.

			The new GUI is written in Python, and if you're a fan of Python programming there are a number of great tools available to you. In the bottom of the 'Layer Manager' window click on the 'Python shell' tab and type ''help(grass.core)'' to see a listing of the functions available in the core GIS python library. Besides the core GIS functions there is also 'array' (NumPy), 'db' (database), 'raster', and 'vector' libraries available. For advanced use 'Pythons CTypes' is supported allowing the Python programmer access to GRASS's extensive C libraries.

	===3D visualization===		===3D visualization===

⚠️HamishBowman at 22:06, 24 July 2012

2012-07-24T22:06:53Z

← Older revision		Revision as of 22:06, 24 July 2012
Line 1:		Line 1:
	<center><font color="#409840">_\\|/_ GRASS 6.4.0 _\\|/_</font></center>		<center><font color="#409840">_\\|/_ GRASS 6.4 _\\|/_</font></center>
	==About==		==About==

← Older revision		Revision as of 09:26, 28 December 2012
Line 201:		Line 201:
	==Further reading==		==Further reading==
	* Visit the GRASS website at http://grass.osgeo.org		* Visit the GRASS website at http://grass.osgeo.org
	* Visit the GRASS Wiki help site at http://~~grass~~.osgeo.org/wiki		* Visit the GRASS Wiki help site at http://grasswiki.osgeo.org/wiki
	* [http://grass.osgeo.org/grass64/manuals~~/html64_user~~/helptext.html How to start with GRASS]		* [http://grass.osgeo.org/grass64/manuals/helptext.html How to start with GRASS]
	* More tutorials and overviews can be found [[GRASS_Help#Getting_Started\|here]].		* More tutorials and overviews can be found [[GRASS_Help#Getting_Started\|here]].
	* Synopsis of GRASS modules, including menu positions ({{website\|gdp/grassmanuals/grass64_module_list.pdf\|PDF, 100k}}) ({{website\|gdp/grassmanuals/grass64_module_list.html\|HTML version}})		* Synopsis of GRASS modules, including menu positions ({{website\|gdp/grassmanuals/grass64_module_list.pdf\|PDF, 100k}}) ({{website\|gdp/grassmanuals/grass64_module_list.html\|HTML version}}) (slightly outdated)
	* If the 400 GIS modules which come with GRASS aren't enough for you have a look at the many contributed add-ons at [[AddOns\|http://grass.osgeo.org/wiki/AddOns]]		* If the 400 GIS modules which come with GRASS aren't enough for you have a look at the many contributed add-ons at [[AddOns\|http://grass.osgeo.org/wiki/AddOns]]