GRASS 6 Terminology - Revision history

⚠️Dmci at 15:25, 31 January 2016

2016-01-31T15:25:14Z

← Older revision		Revision as of 15:25, 31 January 2016
Line 5:		Line 5:
	* '''LOCATION''': This is the name of an available geographic location. It contains a series of MAPSETS which share a common map projection.		* '''LOCATION''': This is the name of an available geographic location. It contains a series of MAPSETS which share a common map projection.
	: Typically its name will be based on the larger job/project you are working on, a reflection of the map projection which it will use, or a combination of both of these. For example: "''The_Rockies''", "''UTM18_nad27''", "''LL_wgs84''", "''Spearfish60''", "''simple_xy''".		: Typically its name will be based on the larger job/project you are working on, a reflection of the map projection which it will use, or a combination of both of these. For example: "''The_Rockies''", "''UTM18_nad27''", "''LL_wgs84''", "''Spearfish60''", "''simple_xy''".


	* '''MAPSET''': Every GRASS session runs under the name of a MAPSET. A MAPSET may be a geographical subset or as large as the parent LOCATION. Technically they are subdirectories under any location. In a networked environment with several users working within the same location, mapsets play a special role. Users may only select (and thus modify) a mapset that they own (i.e., have created). However, data in all mapsets for a given location can be read by anyone (unless prevented by UNIX file permissions). The "PERMANENT" mapset usually contains the read-only base maps like the elevation model, while the other locations are readable and writable by their owners. The "PERMANENT" mapset also contains some information about the location itself that is not found in the mapsets (projection info etc.), thus it must exist in every location.		* '''MAPSET''': Every GRASS session runs under the name of a MAPSET. A MAPSET may be a geographical subset or as large as the parent LOCATION. Technically they are subdirectories under any location. In a networked environment with several users working within the same location, mapsets play a special role. Users may only select (and thus modify) a mapset that they own (i.e., have created). However, data in all mapsets for a given location can be read by anyone (unless prevented by UNIX file permissions). The "PERMANENT" mapset usually contains the read-only base maps like the elevation model, while the other locations are readable and writable by their owners. The "PERMANENT" mapset also contains some information about the location itself that is not found in the mapsets (projection info etc.), thus it must exist in every location.

⚠️Dmci: reorder database --> location --> mapset for consistency with image

2016-01-31T15:24:55Z

reorder database --> location --> mapset for consistency with image

← Older revision		Revision as of 15:24, 31 January 2016
Line 1:		Line 1:
	== General ==		== General ==

			* '''DATABASE''': This is the unix directory containing the geographic LOCATIONS (also called GIS'''D'''BASE). For a desktop GIS user typically this will be a subdirectory called <tt>grassdata</tt> in your home directory.

	* '''LOCATION''': This is the name of an available geographic location. It contains a series of MAPSETS which share a common map projection.		* '''LOCATION''': This is the name of an available geographic location. It contains a series of MAPSETS which share a common map projection.
Line 7:		Line 9:
	* '''MAPSET''': Every GRASS session runs under the name of a MAPSET. A MAPSET may be a geographical subset or as large as the parent LOCATION. Technically they are subdirectories under any location. In a networked environment with several users working within the same location, mapsets play a special role. Users may only select (and thus modify) a mapset that they own (i.e., have created). However, data in all mapsets for a given location can be read by anyone (unless prevented by UNIX file permissions). The "PERMANENT" mapset usually contains the read-only base maps like the elevation model, while the other locations are readable and writable by their owners. The "PERMANENT" mapset also contains some information about the location itself that is not found in the mapsets (projection info etc.), thus it must exist in every location.		* '''MAPSET''': Every GRASS session runs under the name of a MAPSET. A MAPSET may be a geographical subset or as large as the parent LOCATION. Technically they are subdirectories under any location. In a networked environment with several users working within the same location, mapsets play a special role. Users may only select (and thus modify) a mapset that they own (i.e., have created). However, data in all mapsets for a given location can be read by anyone (unless prevented by UNIX file permissions). The "PERMANENT" mapset usually contains the read-only base maps like the elevation model, while the other locations are readable and writable by their owners. The "PERMANENT" mapset also contains some information about the location itself that is not found in the mapsets (projection info etc.), thus it must exist in every location.
	: The MAPSETS might be named for their owner (on a networked multi-user system) (''e.g. user1''), a specific area or study site within the greater region (''e.g. Wade_County''), all maps concerning a specific field study (''e.g. Jan2008''), or whatever is useful to organize your data.		: The MAPSETS might be named for their owner (on a networked multi-user system) (''e.g. user1''), a specific area or study site within the greater region (''e.g. Wade_County''), all maps concerning a specific field study (''e.g. Jan2008''), or whatever is useful to organize your data.


	* '''DATABASE''': This is the unix directory containing the geographic LOCATIONS (also called GIS'''D'''BASE). For a desktop GIS user typically this will be a subdirectory called <tt>grassdata</tt> in your home directory.

Neteler: /* Raster maps */

2014-09-11T14:38:16Z

Raster maps

← Older revision		Revision as of 14:38, 11 September 2014
Line 24:		Line 24:
	-->		-->

	== Raster ~~maps~~ ==		== Raster map precision ==

	* '''CELL DATA TYPE''': a raster map from INTEGER type (whole numbers only)		* '''CELL DATA TYPE''': a raster map from INTEGER type (whole numbers only)


	* '''FCELL DATA TYPE''': a raster map from FLOAT type (4 bytes, 7-9 digits precision)		* '''FCELL DATA TYPE''': a raster map from FLOAT type (4 bytes, 7-9 digits precision)


	* '''DCELL DATA TYPE''': a raster map from DOUBLE type (8 bytes, 15-17 digits precision)		* '''DCELL DATA TYPE''': a raster map from DOUBLE type (8 bytes, 15-17 digits precision)
			* '''NULL''': represents "no data" in raster maps, to be distinguished from 0 (zero) data value

	* '''NULL''': represents "no data" in raster maps, to be distinguished from 0 (zero) data value


	* '''INTEGER MAP''': see CELL DATA TYPE		* '''INTEGER MAP''': see CELL DATA TYPE


	* '''FLOAT MAP''': see FCELL DATA TYPE		* '''FLOAT MAP''': see FCELL DATA TYPE


	* '''DOUBLE MAP''': see DCELL DATA TYPE		* '''DOUBLE MAP''': see DCELL DATA TYPE

⚠️HamishBowman: /* Raster 3D maps */ voxel

2014-02-16T21:57:31Z

Raster 3D maps: voxel

← Older revision		Revision as of 21:57, 16 February 2014
Line 48:		Line 48:
	== Raster 3D maps ==		== Raster 3D maps ==

	* '''VOXEL''': A 3-dimensional grid cell. (An individual cube in a greater 3D region block)		* '''VOXEL''': Volumetric Pixel -- a 3-dimensional grid cell. (An individual cube in a greater 3D region block)


	== Vector maps ==		== Vector maps ==

⚠️HamishBowman: /* Raster maps */ precision

2014-02-16T21:56:52Z

Raster maps: precision

← Older revision		Revision as of 21:56, 16 February 2014
Line 29:		Line 29:


	* '''FCELL DATA TYPE''': a raster map from FLOAT type (4 bytes, 6 digits precision)		* '''FCELL DATA TYPE''': a raster map from FLOAT type (4 bytes, 7-9 digits precision)


	* '''DCELL DATA TYPE''': a raster map from DOUBLE type (8 bytes, 15 digits precision)		* '''DCELL DATA TYPE''': a raster map from DOUBLE type (8 bytes, 15-17 digits precision)


Line 45:		Line 45:

	* '''DOUBLE MAP''': see DCELL DATA TYPE		* '''DOUBLE MAP''': see DCELL DATA TYPE


	== Raster 3D maps ==		== Raster 3D maps ==

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

2011-12-30T21:37:04Z

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

← Older revision		Revision as of 21:37, 30 December 2011
Line 89:		Line 89:
	[[Category: Documentation]]		[[Category: Documentation]]
	[[Category: FAQ]]		[[Category: FAQ]]



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

⚠️Reverse22 at 20:50, 30 December 2011

2011-12-30T20:50:39Z

← Older revision		Revision as of 20:50, 30 December 2011
Line 89:		Line 89:
	[[Category: Documentation]]		[[Category: Documentation]]
	[[Category: FAQ]]		[[Category: FAQ]]



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

⚠️FredMaranhao: /* General */

2011-03-16T17:30:13Z

General

← Older revision		Revision as of 17:30, 16 March 2011
Line 15:		Line 15:


	* '''REGION''': The REGION may be the entire area or subset of the chosen LOCATION. It is defined by northern, southern eastern, and western bounds, as well as the raster grid resolution. It is controlled by the {{cmd\|g.region}} module and is of primary importance for raster operations. Its most obvious effect is of setting the map zoom, but it is much more than that.		* '''REGION''': The REGION may be the entire area or subset of the chosen LOCATION. It is defined by northern, southern, eastern, and western bounds, as well as the raster grid resolution. It is controlled by the {{cmd\|g.region}} module and is of primary importance for raster operations. Its most obvious effect is of setting the map zoom, but it is much more than that.

⚠️HamishBowman: /* General */ fig

2010-01-09T14:03:41Z

General: fig

← Older revision		Revision as of 14:03, 9 January 2010
Line 10:		Line 10:

	* '''DATABASE''': This is the unix directory containing the geographic LOCATIONS (also called GIS'''D'''BASE). For a desktop GIS user typically this will be a subdirectory called <tt>grassdata</tt> in your home directory.		* '''DATABASE''': This is the unix directory containing the geographic LOCATIONS (also called GIS'''D'''BASE). For a desktop GIS user typically this will be a subdirectory called <tt>grassdata</tt> in your home directory.


			[[File:Loc_struct.png\|center\|thumb\|600px\|Structure of the GRASS data hierarchy]]


Line 17:		Line 20:
	* '''WINDOW''': see REGION		* '''WINDOW''': see REGION

			<!--
	[https://trac.osgeo.org/grass/browser/grass/branches/releasebranch_5_5/html/spearfish_directorytree.html Sample GRASS 5.0 database directory tree structure (Spearfish data set)]		[https://trac.osgeo.org/grass/browser/grass/branches/releasebranch_5_5/html/spearfish_directorytree.html Sample GRASS 5.0 database directory tree structure (Spearfish data set)]
			-->

	== Raster maps ==		== Raster maps ==

⚠️HamishBowman: /* Map Projections */

2010-01-09T07:23:19Z

Map Projections

← Older revision		Revision as of 07:23, 9 January 2010
Line 73:		Line 73:
	== Map Projections ==		== Map Projections ==

	''See the [[]] wiki page for details.		''See the [[GIS Concepts]] wiki page for details.
	<!--		<!--
	* '''PROJECTION''':		* '''PROJECTION''':