Digitizing Area Features - Revision history

⚠️Wenzeslaus: add template outdated

2016-02-01T02:21:12Z

add template outdated

← Older revision		Revision as of 02:21, 1 February 2016
Line 1:		Line 1:
			{{OutDated}}

	=Digitizing area features with attributes=		=Digitizing area features with attributes=

Line 81:		Line 83:
	[[Category:FAQ]]		[[Category:FAQ]]
	[[Category:Vector]]		[[Category:Vector]]
	~~[[Category:OutDated]]~~

⚠️Wenzeslaus: add Category:OutDated

2016-02-01T02:19:56Z

add Category:OutDated

← Older revision		Revision as of 02:19, 1 February 2016
Line 81:		Line 81:
	[[Category:FAQ]]		[[Category:FAQ]]
	[[Category:Vector]]		[[Category:Vector]]
			[[Category:OutDated]]

Neteler: /* Specific instructions for digitizing areas */

2011-12-07T00:26:34Z

Specific instructions for digitizing areas

← Older revision		Revision as of 00:26, 7 December 2011
Line 80:		Line 80:
	[[Category:Documentation]]		[[Category:Documentation]]
	[[Category:FAQ]]		[[Category:FAQ]]
			[[Category:Vector]]

Neteler: url fix

2011-02-11T13:43:48Z

url fix

← Older revision		Revision as of 13:43, 11 February 2011
Line 26:		Line 26:


	Following are suggestions for adding attributes when using the GRASS digitizer, which more or less duplicate the above process. Detailed explanations of the {{cmd\|v.digit}} interface can be found both in the GRASS ([http://www.grassbook.org/ Book]) and the GDF Hannover ([http://www.gdf-hannover.de/lit_html/grass60_v1.2_en/node56.html tutorial]). The new wxGUI digitizer has a good manual page at: {{cmd\|wxGUI.~~Vector_Digitizing_Tool~~}}.		Following are suggestions for adding attributes when using the GRASS digitizer, which more or less duplicate the above process. Detailed explanations of the {{cmd\|v.digit}} interface can be found both in the GRASS ([http://www.grassbook.org/ Book]) and the GDF Hannover ([http://www.gdf-hannover.de/lit_html/grass60_v1.2_en/node56.html tutorial]). The new wxGUI digitizer has a good manual page at: {{cmd\|wxGUI.Vector_Digitizer}}.

	===General case===		===General case===

⚠️Landa: /* Introduction */

2010-09-23T18:15:07Z

Introduction

← Older revision		Revision as of 18:15, 23 September 2010
Line 5:		Line 5:
	GIS users with experience creating and editing non-topological shapefiles sometimes encounter problems when adding attributes to area features in the GRASS digitizer {{cmd\|v.digit}}. This section will attempt to offer a few tips and clear up this issue. Much has already been written explaining the strict topological vector model which GRASS uses. Please read first:		GIS users with experience creating and editing non-topological shapefiles sometimes encounter problems when adding attributes to area features in the GRASS digitizer {{cmd\|v.digit}}. This section will attempt to offer a few tips and clear up this issue. Much has already been written explaining the strict topological vector model which GRASS uses. Please read first:

	* from the wiki [[Vector FAQ GRASS6]] and [[~~Vectordata~~]]		* from the wiki [[Vector FAQ GRASS6]] and [[Vector Data]]

	* and from the manual pages {{cmd\|vectorintro}}		* and from the manual pages {{cmd\|vectorintro}}

⚠️Landa: use templates

2010-09-23T18:14:08Z

use templates

← Older revision		Revision as of 18:14, 23 September 2010
Line 2:		Line 2:

	==Introduction==		==Introduction==
	GIS users with experience creating and editing non-topological shapefiles sometimes encounter problems when adding attributes to area features in the GRASS digitizer ~~<tt>~~ v.digit ~~</tt>~~. This section will attempt to offer a few tips and clear up this issue. Much has already been written explaining the strict topological vector model which GRASS uses. Please read first:~~<br>~~
	:from the wiki- [~~http://grass.osgeo.org/wiki/Vector_FAQ_GRASS6~~] [~~http://grass.osgeo.org/wiki/~~Vectordata]~~<br>~~		GIS users with experience creating and editing non-topological shapefiles sometimes encounter problems when adding attributes to area features in the GRASS digitizer {{cmd\|v.digit}}. This section will attempt to offer a few tips and clear up this issue. Much has already been written explaining the strict topological vector model which GRASS uses. Please read first:
	:and from the manual pages~~- [http://grass.osgeo.org/grass63/manuals/html63_user/~~vectorintro~~.html]~~
			* from the wiki [[Vector FAQ GRASS6]] and [[Vectordata]]

			* and from the manual pages {{cmd\|vectorintro}}

	==Problem Description==		==Problem Description==

	When creating a polygon shapefile, after the user finishes clicking around the perimeter of the polygon, GIS software applications will often pop up a window with all the attribute columns available and the user enters values for that polygon. In the non-topological shapefile format, the area boundary and the enclosed polygon are one and the same. Thus the boundary attributes also refer to the enclosed area. In the shapefile diagram below the labels A-1, A-2, A-3 are taken from the polygon attribute table. This fact might seem so obvious to shapefile users that they would wonder why it needs mentioning.		When creating a polygon shapefile, after the user finishes clicking around the perimeter of the polygon, GIS software applications will often pop up a window with all the attribute columns available and the user enters values for that polygon. In the non-topological shapefile format, the area boundary and the enclosed polygon are one and the same. Thus the boundary attributes also refer to the enclosed area. In the shapefile diagram below the labels A-1, A-2, A-3 are taken from the polygon attribute table. This fact might seem so obvious to shapefile users that they would wonder why it needs mentioning.

	In the strict topological model used in GRASS, this is not the case. In a GRASS vector the surrounding boundary, and its enclosed area are two separate entities, which have two separate rows in the accompanying attribute table. The boundary is made up of line segments, and the area is represented by its ''centroid'' – a point within the closed boundary. (Centroids should be placed only within closed boundaries.) A line segment which is part of the boundary enclosing an area does not “belong” to that area, rather it often is common to two adjacent areas. In the GRASS vector diagram below, boundary B-1 separates areas A-1 and A-2. Boundaries B-3 and B-8 separate between areas A-1 and A-3. Furthermore, the boundary of area A-2 is composed of B-1, B-2 and B-5. Obviously it would not make sense to attach '''area''' attributes to any boundary, so instead the area ''centroids'' serve to connect to the attribute table rows holding the area attributes. Thus, the labels B-1, B-2, etc. come from the vector attribute table (line features) and the A-1, A-2 labels, also from the attribute table, are ''centroid'' features. Using the GRASS digitizer, ~~<tt>~~v.digit~~</tt>~~, care needs to be taken to attach attributes to the correct features.		In the strict topological model used in GRASS, this is not the case. In a GRASS vector the surrounding boundary, and its enclosed area are two separate entities, which have two separate rows in the accompanying attribute table. The boundary is made up of line segments, and the area is represented by its ''centroid'' – a point within the closed boundary. (Centroids should be placed only within closed boundaries.) A line segment which is part of the boundary enclosing an area does not “belong” to that area, rather it often is common to two adjacent areas. In the GRASS vector diagram below, boundary B-1 separates areas A-1 and A-2. Boundaries B-3 and B-8 separate between areas A-1 and A-3. Furthermore, the boundary of area A-2 is composed of B-1, B-2 and B-5. Obviously it would not make sense to attach '''area''' attributes to any boundary, so instead the area ''centroids'' serve to connect to the attribute table rows holding the area attributes. Thus, the labels B-1, B-2, etc. come from the vector attribute table (line features) and the A-1, A-2 labels, also from the attribute table, are ''centroid'' features. Using the GRASS digitizer, {{cmd\|v.digit}}, care needs to be taken to attach attributes to the correct features.

	[[Image:Shape.png\|left\|400px]] [[Image:Grass_vectors.png\|center\|400px]]		[[Image:Shape.png\|left\|400px]] [[Image:Grass_vectors.png\|center\|400px]]

	==Best Practices==		==Best Practices==
	First, it's worth pointing out that when using ~~<tt>~~v.in.ogr~~</TT>~~ to import a polygon shapefile into GRASS, steps are automatically taken to insure that the resulting vector gets the attributes as expected. (This behind-the-scenes procedure might actually fool naive users into believing that GRASS vectors are just like polygon shapefiles).
			First, it's worth pointing out that when using {{cmd\|v.in.ogr}} to import a polygon shapefile into GRASS, steps are automatically taken to insure that the resulting vector gets the attributes as expected. (This behind-the-scenes procedure might actually fool naive users into believing that GRASS vectors are just like polygon shapefiles).
	*Polygons are imported as boundary lines		*Polygons are imported as boundary lines
	*These lines are split at intersections, and all overlapping boundaries are removed (topologically cleaned)		*These lines are split at intersections, and all overlapping boundaries are removed (topologically cleaned)
Line 21:		Line 26:


	Following are suggestions for adding attributes when using the GRASS digitizer, which more or less duplicate the above process. Detailed explanations of the ~~<tt>~~v.digit~~</tt>~~ interface can be found both in the GRASS ([http://www.grassbook.org/ Book]) and the GDF Hannover ([http://www.gdf-hannover.de/lit_html/grass60_v1.2_en/node56.html tutorial]). The new wxGUI digitizer has a good manual page at: ~~[http://grass.osgeo.org/grass64/manuals/html64_user/~~wxGUI.Vector_Digitizing_Tool.~~html]~~		Following are suggestions for adding attributes when using the GRASS digitizer, which more or less duplicate the above process. Detailed explanations of the {{cmd\|v.digit}} interface can be found both in the GRASS ([http://www.grassbook.org/ Book]) and the GDF Hannover ([http://www.gdf-hannover.de/lit_html/grass60_v1.2_en/node56.html tutorial]). The new wxGUI digitizer has a good manual page at: {{cmd\|wxGUI.Vector_Digitizing_Tool}}.

	===General case===		===General case===
	The process that users should follow when manually creating area vectors with ~~<tt>~~v.digit~~</tt>~~ will produce boundaries with no attributes, and a centroid connected thru its cat value to the area attributes. First, in the ~~<tt>~~v.digit~~</tt>~~ interface, use the settings dialog to set up the attribute table as required by the data, and choose an appropriate snapping tolerance. Also in the settings dialog, under the Attributes tab, there is a drop down list to choose Category Mode (how the cat values will be chosen). For digitizing boundaries, it is possible to <u>choose “No category”</u> since, as explained above, the boundary lines themselves might not require any attributes. Next digitize boundaries, being careful to
			The process that users should follow when manually creating area vectors with {{cmd\|v.digit}} will produce boundaries with no attributes, and a centroid connected thru its cat value to the area attributes. First, in the {{cmd\|v.digit}} interface, use the settings dialog to set up the attribute table as required by the data, and choose an appropriate snapping tolerance. Also in the settings dialog, under the Attributes tab, there is a drop down list to choose Category Mode (how the cat values will be chosen). For digitizing boundaries, it is possible to <u>choose “No category”</u> since, as explained above, the boundary lines themselves might not require any attributes. Next digitize boundaries, being careful to
	*close boundaries which delineate areas.		*close boundaries which delineate areas.
	*never digitize the boundary between adjacent areas twice		*never digitize the boundary between adjacent areas twice
Line 31:		Line 37:

	===A Special Case===		===A Special Case===
	There are situations where attributes need to be attached also to the boundary lines. For example: in a project mapping out species distribution, the boundaries might have an attribute value indicating the rate of spread of a species across a border. In this case, the boundaries will get a cat value (optionally defined as a separate GRASS ~~“layer”~~, with a separate database connection). While digitizing, the user will enter values into the attribute table relevant to each boundary. But still, centroids need to be digitized, and attributes entered for each centroid which are relevant to the areas.		There are situations where attributes need to be attached also to the boundary lines. For example: in a project mapping out species distribution, the boundaries might have an attribute value indicating the rate of spread of a species across a border. In this case, the boundaries will get a cat value (optionally defined as a separate GRASS "layer", with a separate database connection). While digitizing, the user will enter values into the attribute table relevant to each boundary. But still, centroids need to be digitized, and attributes entered for each centroid which are relevant to the areas.

	===Another Special Case===		===Another Special Case===
	In some situations a single boundary line exactly encompasses an area, with no adjacent areas. (In other words, each area is an “isle” in GRASS terminology.) An example might be a vector map of water bodies. Obviously no water body touches any other. And the perimeter is one continuous line. Users might want the attribute table to be attached to both the area and the boundary – perhaps to display the length of the perimeter along the perimeter rather than at the centroid. In order to achieve this, boundaries will be digitized with a cat value, and the centroids will be forced to use that same cat value as the boundary. This is done as follows.~~<br>~~ While working on the boundary, the user should take note of its category value. Next, before marking the centroid, the user will switch the Category Mode to “Manual entry”. Now she digitizes the centroid for that closed boundary and manually types in the <u>same cat value</u> as the surrounding boundary. This creates two vector features: a boundary line and a centroid, with identical category values, and thus a single row in the database. So all attributes are common to both the boundary and the centroid (area).
			In some situations a single boundary line exactly encompasses an area, with no adjacent areas. (In other words, each area is an “isle” in GRASS terminology.) An example might be a vector map of water bodies. Obviously no water body touches any other. And the perimeter is one continuous line. Users might want the attribute table to be attached to both the area and the boundary - perhaps to display the length of the perimeter along the perimeter rather than at the centroid. In order to achieve this, boundaries will be digitized with a cat value, and the centroids will be forced to use that same cat value as the boundary. This is done as follows.

			While working on the boundary, the user should take note of its category value. Next, before marking the centroid, the user will switch the Category Mode to “Manual entry”. Now she digitizes the centroid for that closed boundary and manually types in the <u>same cat value</u> as the surrounding boundary. This creates two vector features: a boundary line and a centroid, with identical category values, and thus a single row in the database. So all attributes are common to both the boundary and the centroid (area).

	===Note: v.centroids===		===Note: v.centroids===
	The GRASS tool for adding missing centroids to closed boundaries is ~~<tt>~~v.centroids~~</tt>~~. It is important to realize that the centroids will be created with category values that have no connection to the enclosing boundaries. If you run ~~<tt>~~v.centroids~~</tt>~~ on a vector that already has closed boundary lines with attribute values, these attribute values will '''not be attached to the area enclosed''', since the new centroids will be assigned some new category value. This point is explained in the ~~<tt>~~v.centroids~~</tt> [[http://grass.osgeo.org/grass63/manuals/html63_user/v.centroids.html~~ manual]] page.
			The GRASS tool for adding missing centroids to closed boundaries is {{cmd\|v.centroids}}. It is important to realize that the centroids will be created with category values that have no connection to the enclosing boundaries. If you run {{cmd\|v.centroids}} on a vector that already has closed boundary lines with attribute values, these attribute values will '''not be attached to the area enclosed''', since the new centroids will be assigned some new category value. This point is explained in the {{cmd\|v.centroids}} manual page.

	~~--[[User:Micha\|Micha]] 22:12, 14 February 2009 (UTC)~~


	===Specific instructions for digitizing areas===		===Specific instructions for digitizing areas===

Neteler: +cats

2010-04-19T16:49:32Z

+cats

← Older revision		Revision as of 16:49, 19 April 2010
Line 70:		Line 70:

	Click 'Save and exit'. You're done.		Click 'Save and exit'. You're done.

			[[Category:Documentation]]
			[[Category:FAQ]]

⚠️Caitifty: /* Specific instructions for digitizing areas */ change code snippet to use tag

2010-04-18T19:59:08Z

Specific instructions for digitizing areas: change code snippet to use <source> tag

← Older revision		Revision as of 19:59, 18 April 2010
Line 54:		Line 54:
	These steps create a new map, give it an attribute table, link the attribute table to the map, and open the new map in v.digit displaying the existing layer/s:		These steps create a new map, give it an attribute table, link the attribute table to the map, and open the new map in v.digit displaying the existing layer/s:

	<~~code~~>		<source lang="bash">
	v.in.ascii -e output=newmapname		v.in.ascii -e output=newmapname

	echo 'create table newmapname (cat integer, DAY date)' \| db.execute		echo 'create table newmapname (cat integer, DAY date)' \| db.execute

	v.db.connect -o map=newmapname table=newmapname		v.db.connect -o map=newmapname table=newmapname

	v.digit map=newmapname bgcmd="d.vect map=existingmap1 type=area fcolor=green; d.vect map=existingmap2"		v.digit map=newmapname bgcmd="d.vect map=existingmap1 type=area fcolor=green; d.vect map=existingmap2"
	</~~code~~>		</source>

	You can create as many attribute fields as you want within the () area, using whatever field types are allowable for the database type you're using. If you're using an 'external' database type like mysql, you can also just create a cat field in this step and use regular mysql commands or tools to add additional fields to the table if that's easier.		You can create as many attribute fields as you want within the () area, using whatever field types are allowable for the database type you're using. If you're using an 'external' database type like mysql, you can also just create a cat field in this step and use regular mysql commands or tools to add additional fields to the table if that's easier.

⚠️Caitifty: /* Specific instructions for digitizing areas */ fix linewrap on code

2010-04-18T19:55:51Z

Specific instructions for digitizing areas: fix linewrap on code

← Older revision		Revision as of 19:55, 18 April 2010
Line 56:		Line 56:
	<code>		<code>
	v.in.ascii -e output=newmapname		v.in.ascii -e output=newmapname

	echo 'create table newmapname (cat integer, DAY date)' \| db.execute		echo 'create table newmapname (cat integer, DAY date)' \| db.execute

	v.db.connect -o map=newmapname table=newmapname		v.db.connect -o map=newmapname table=newmapname

	v.digit map=newmapname bgcmd="d.vect map=existingmap1 type=area fcolor=green; d.vect map=existingmap2"		v.digit map=newmapname bgcmd="d.vect map=existingmap1 type=area fcolor=green; d.vect map=existingmap2"
	</code>		</code>

⚠️Caitifty: Add specific directions for creating an area/centroid with attributes

2010-04-17T20:44:29Z

Add specific directions for creating an area/centroid with attributes

← Older revision		Revision as of 20:44, 17 April 2010
Line 40:		Line 40:

	--[[User:Micha\|Micha]] 22:12, 14 February 2009 (UTC)		--[[User:Micha\|Micha]] 22:12, 14 February 2009 (UTC)


			===Specific instructions for digitizing areas===

			I found this issue to be not that well documented, so here's a specific method for digitizing areas:

			An area comprises two primitives - a boundary and a centroid. The boundary has no attributes; the centroid holds the attributes (if any).

			To create an area, a two step process is needed. First, a boundary is defined, then a centroid added. You can batch them - define all the boundaries then add the centroids. I don't know the rules for overlapping areas though - might be better to do those separately.

			In this example, you have some existing map layers (for example a layer showing some parks as areas and a layer showing roads) and you want to create a new area by manually digitizing an area based on the existing map layers (eg you want to digitize an area bounded by some specific streets near a park).

			These steps create a new map, give it an attribute table, link the attribute table to the map, and open the new map in v.digit displaying the existing layer/s:

			<code>
			v.in.ascii -e output=newmapname
			echo 'create table newmapname (cat integer, DAY date)' \| db.execute
			v.db.connect -o map=newmapname table=newmapname
			v.digit map=newmapname bgcmd="d.vect map=existingmap1 type=area fcolor=green; d.vect map=existingmap2"
			</code>

			You can create as many attribute fields as you want within the () area, using whatever field types are allowable for the database type you're using. If you're using an 'external' database type like mysql, you can also just create a cat field in this step and use regular mysql commands or tools to add additional fields to the table if that's easier.

			In the window that opens, zoom the the relevant area, then click the 'Digitize new boundary' button. IMPORTANT: Before doing anything else, CHANGE MODE TO 'No Category'. Use the tool to define the boundary of the area, and right-click to close the boundary. If the boundary is successfully closed, the boundary line will turn bright green. If not, it'll remain grey. Easiest fix is to click the 'move vertex' button, move one of the vertices back a bit, then using the 'create new boundary' tool, join the two red crosses. This almost always works, for some reason I can never get the original boundary to join properly. The 'settings' tool also lets you change snapping distance, but altering that hasn't helped me much yet. If the boundary isn't bright green after all this, it isn't closed and the next step won't work.

			Select the 'Digitize new centroid' tool. IMPORTANT: Before continuing, CHANGE MODE BACK TO 'Next not used'. Use the tool to select somewhere inside the boundary. The attributes window will open, and you can fill in any area attributes you've created columns for.

			You've now created a new area with attributes. Yay.

			Click 'Save and exit'. You're done.