Tips for Arc users - Revision history

⚠️Dat at 05:02, 22 July 2016

2016-07-22T05:02:45Z

← Older revision		Revision as of 05:02, 22 July 2016
Line 48:		Line 48:

	==== Various vector operations ====		==== Various vector operations ====
	* ~~Editar diferencias~~		* Editing differences
	: Tips ~~para la~~ [[Digitizing_Area_Features\|~~digitalización de áreas con atributos~~]]		: Tips for [[Digitizing_Area_Features\|Digitizing area features with attributes]]

	~~=== Importación/exportación de rásters ===~~

	* {{cmd\|r.in.gdal}} - Importa archivos ráster a un soportados por [http://www.gdal.org GDAL] a una capa de mapa ráster binaria.
	** Importar una malla binaria ArcInfo a GRASS:
	*** Ver la [http://www.gdal.org/frmt_various.html#AIG página de GDAL para AIC]
	*** Usualmente el archivo .adf más grande es el que se debe importar -- revise los valores de sus datos luego de realizar la importación aun cuando sean visualmente correctos.

			=== Raster import/export ===

			* {{cmd\|r.in.gdal}} - Import [http://www.gdal.org GDAL] supported raster file into a binary raster map layer.
			** Import a binary ArcInfo raster grid into GRASS:
			*** See the [http://www.gdal.org/frmt_various.html#AIG GDAL help page for AIC]
			*** Often the biggest .adf file is the right one to import -- check your data values after importing even if they visually look correct!
	r.in.gdal input=/path/to/map/hdr.adf output=map		r.in.gdal input=/path/to/map/hdr.adf output=map

	* {{cmd\|r.out.gdal}} - ~~Exporta datos ráster a varios formatos~~.		* {{cmd\|r.out.gdal}} - Exports GRASS raster data into various formats.
	** ~~Exportar un ráster como un~~ GeoTIFF ~~para usarlo en~~ ArcView 3.1:		** Export a raster as a GeoTIFF for use with ArcView 3.1:
	r.out.gdal input=map output=map.tif type=Byte createopt="INTERLEAVE=PIXEL,COMPRESS=PACKBITS"		r.out.gdal input=map output=map.tif type=Byte createopt="INTERLEAVE=PIXEL,COMPRESS=PACKBITS"

	==== ~~Importar malla ráster~~ ArcASCII ~~y conectar a la base de datos~~ ====		==== Import ArcASCII raster grid and connect to database ====

	~~El truco está en convertir la cobertura ráster a áreaas vectoriales para sacar ventaja del manejo atributos~~/~~bases de datos de los vectoriales en GRASS~~. ~~Puede usar el comando~~ {{cmd\|r.in.gdal}} ~~para importar~~.		The trick is to convert the raster coverage to vector
			areas to take advantage of GRASS's rich vector attribute/database tie-ins. You can use {{cmd\|r.in.gdal}} for the import.

	# ~~importar malla~~ ArcASCII ~~a una localización~~ UTM55S		# import ArcASCII grid to UTM55S location
	r.in.gdal input=aas_z55.asc output=aas_z55		r.in.gdal input=aas_z55.asc output=aas_z55
	r.colors aas_z55.gdal color=random		r.colors aas_z55.gdal color=random
	r.info aas_z55		r.info aas_z55

	# ~~convertir a áreas vectoriales~~, ~~usando los valores del ráster como categorías~~		# convert to vector areas, using raster value for category
	g.region rast=aas_z55		g.region rast=aas_z55
	r.to.vect -v in=aas_z55.gdal out=aas_z55 feature=area		r.to.vect -v in=aas_z55.gdal out=aas_z55 feature=area

	# ~~deshacerse de la tabla vacía creada~~		# get rid of empty DBF table created by r.to.vect
	v.db.droptable aas_z55		v.db.droptable aas_z55

	# ~~copiar la tabla~~ real ~~al directorio~~ $MAPSET/dbf/		# copy real DBF file into $MAPSET/dbf/ directory
	eval `g.gisenv`		eval `g.gisenv`
	cp /tmp/au/aas_z55.DBF "$GISDBASE/$LOCATION_NAME/$MAPSET/dbf/aas_z55.dbf"		cp /tmp/au/aas_z55.DBF "$GISDBASE/$LOCATION_NAME/$MAPSET/dbf/aas_z55.dbf"

	# ~~conectar la base de datos completa al mapa vectorial~~, ~~usar como columna clave la columna~~ "VALUE"		# connect full DBF database to vector map, use "VALUE" as the key column
	v.db.connect map=aas_z55 driver=dbf table=aas_z55 key=value		v.db.connect map=aas_z55 driver=dbf table=aas_z55 key=value

	~~Y listo~~. ~~Los datos están en la base de datos de~~ GRASS.		Done. The data are in GRASS GIS database.

			==== Import E00 raster grids ====

			* The {{cmd\|v.in.e00}} module only handles vector data. You will have to convert raster E00 data into an Arc ASCII grid before importing into GRASS with {{cmd\|r.in.gdal}}.
			* [http://lists.osgeo.org/pipermail/grass-user/2009-October/052758.html See instructions in this mailing list post] about the "ArcExplorer Import Utility"

			== Linking data to GRASS GIS ==

			You can link data instead of importing them, use {{cmd\|r.external}}, {{cmd\|v.external}}, {{cmd\|r.external.out}}, and {{cmd\|v.external.out}}. Projection of all data must be consistent.

			== Various hydrology and terrain analysis commands ==

	~~==== Importar mallas ráster E00 ====~~		<!-- perhaps this should go to GRASS GIS for ArcGIS users page -->
	* El módulo {{cmd\|v.in~~.e00}} solamente manipula datos vectoriales. Debe convertir los datos ráster E00 al formato Arc ASCII antes de importar a GRASS con el comando {{cmd\|r.in.gdal}}.~~		<!-- but in general, this page could contains some common usecases which includes hydrology -->
	* [http://lists.osgeo.org/pipermail/grass-~~user/2009~~-~~October/052758.html Ver las instrucciones en el correo] sbre la "ArcExplorer Import Utility".~~

	=~~= Enlazar datos en~~ GRASS ==		* Watershed modeling differences:
			** ArcInfo wants a depressionless, filled, hydrologically correct DEM.
			** {{cmd\|r.watershed}} does not need such a DEM, it is happy with a raw DEM even containing depressions, being not filled, and not hydrologically correct (hence, no extra preparations needed!).
			* How to [[Creating_watersheds\|Create watersheds for specific drainage points]] like the Arc Hydro extension
			* See also [[Hydrological Sciences]] for a list of available hydrological GRASS tools
			* [http://www.surfaces.co.il/?p=241 Watershed Analysis with GRASS] (when you know ESRI)
			* [https://grasswiki.osgeo.org/wiki/Creating_watersheds#Calculating_total_drainage_area_for_each_stream_reach Calculating total upstream area for each stream]

	Es posible enlazar los datos, en vez de importarlos usando los comandos {{cmd\|r.external}}, {{cmd\|v.external}}, {{cmd\|r.external.out}}, y {{cmd\|v.external.out}}. Todos los datos deben tener la misma proyección que la Localización de GRASS.== See also ==		== See also ==

	* [[GRASS GIS for ArcGIS users]]		* [[GRASS GIS for ArcGIS users]]
	* [[Terminology comparison between ArcGIS and GRASS GIS]]		* [[Terminology comparison between ArcGIS and GRASS GIS]]

	== ~~Links externos~~ ==		== External links ==

	* ~~Tutorial básci de GRASS en Gostat 2012 (y otros años)~~ [http://geostat-course.org/Topic_NetelerMetz_2012 ~~Tutorial de~~ GRASS GIS].		* Basic [http://geostat-course.org/Topic_NetelerMetz_2012 GRASS GIS tutorial] at Geostat 2012
	* [http://www.appropedia.org/A_transition_from_ArcGIS_to_open_source_GIS_softwares ~~Transición desde~~ ArcGIS ~~a SIGs libres~~].		* [http://www.appropedia.org/A_transition_from_ArcGIS_to_open_source_GIS_softwares A transition from ArcGIS to open source GIS softwares]
	* [http://gis.stackexchange.com/questions/134/can-arcgis-and-osgeo4w-share-the-same-python-install Can ArcGIS and OSGeo4W share the same python install?]		* [http://gis.stackexchange.com/questions/134/can-arcgis-and-osgeo4w-share-the-same-python-install Can ArcGIS and OSGeo4W share the same python install?]

⚠️Dat at 04:58, 22 July 2016

2016-07-22T04:58:31Z

← Older revision		Revision as of 04:58, 22 July 2016
Line 48:		Line 48:

	==== Various vector operations ====		==== Various vector operations ====
	* ~~Editing differences~~		* Editar diferencias
	: Tips ~~for~~ [[Digitizing_Area_Features\|~~Digitizing area features with attributes~~]]		: Tips para la [[Digitizing_Area_Features\|digitalización de áreas con atributos]]

	=== ~~Raster import~~/~~export~~ ===		=== Importación/exportación de rásters ===

			* {{cmd\|r.in.gdal}} - Importa archivos ráster a un soportados por [http://www.gdal.org GDAL] a una capa de mapa ráster binaria.
			** Importar una malla binaria ArcInfo a GRASS:
			*** Ver la [http://www.gdal.org/frmt_various.html#AIG página de GDAL para AIC]
			*** Usualmente el archivo .adf más grande es el que se debe importar -- revise los valores de sus datos luego de realizar la importación aun cuando sean visualmente correctos.

	* {{cmd\|r.in.gdal}} - Import [http://www.gdal.org GDAL] supported raster file into a binary raster map layer.
	** Import a binary ArcInfo raster grid into GRASS:
	*** See the [http://www.gdal.org/frmt_various.html#AIG GDAL help page for AIC]
	*** Often the biggest .adf file is the right one to import -- check your data values after importing even if they visually look correct!
	r.in.gdal input=/path/to/map/hdr.adf output=map		r.in.gdal input=/path/to/map/hdr.adf output=map

	* {{cmd\|r.out.gdal}} - ~~Exports GRASS raster data into various formats~~.		* {{cmd\|r.out.gdal}} - Exporta datos ráster a varios formatos.
	** ~~Export a raster as a~~ GeoTIFF ~~for use with~~ ArcView 3.1:		** Exportar un ráster como un GeoTIFF para usarlo en ArcView 3.1:
	r.out.gdal input=map output=map.tif type=Byte createopt="INTERLEAVE=PIXEL,COMPRESS=PACKBITS"		r.out.gdal input=map output=map.tif type=Byte createopt="INTERLEAVE=PIXEL,COMPRESS=PACKBITS"

	==== ~~Import~~ ArcASCII ~~raster grid and connect to database~~ ====		==== Importar malla ráster ArcASCII y conectar a la base de datos ====

	~~The trick is to convert the raster coverage to vector~~		El truco está en convertir la cobertura ráster a áreaas vectoriales para sacar ventaja del manejo atributos/bases de datos de los vectoriales en GRASS. Puede usar el comando {{cmd\|r.in.gdal}} para importar.
	~~areas to take advantage of~~ GRASS~~'s rich vector attribute/database tie-ins~~. ~~You can use~~ {{cmd\|r.in.gdal}} ~~for the import~~.

	# ~~import~~ ArcASCII ~~grid to~~ UTM55S ~~location~~		# importar malla ArcASCII a una localización UTM55S
	r.in.gdal input=aas_z55.asc output=aas_z55		r.in.gdal input=aas_z55.asc output=aas_z55
	r.colors aas_z55.gdal color=random		r.colors aas_z55.gdal color=random
	r.info aas_z55		r.info aas_z55

	# ~~convert to vector areas~~, ~~using raster value for category~~		# convertir a áreas vectoriales, usando los valores del ráster como categorías
	g.region rast=aas_z55		g.region rast=aas_z55
	r.to.vect -v in=aas_z55.gdal out=aas_z55 feature=area		r.to.vect -v in=aas_z55.gdal out=aas_z55 feature=area

	# ~~get rid of empty DBF table created by r.to.vect~~		# deshacerse de la tabla vacía creada
	v.db.droptable aas_z55		v.db.droptable aas_z55

	# ~~copy~~ real ~~DBF file into~~ $MAPSET/dbf/ ~~directory~~		# copiar la tabla real al directorio $MAPSET/dbf/
	eval `g.gisenv`		eval `g.gisenv`
	cp /tmp/au/aas_z55.DBF "$GISDBASE/$LOCATION_NAME/$MAPSET/dbf/aas_z55.dbf"		cp /tmp/au/aas_z55.DBF "$GISDBASE/$LOCATION_NAME/$MAPSET/dbf/aas_z55.dbf"

	# ~~connect full DBF database to vector map~~, ~~use~~ "VALUE" ~~as the key column~~		# conectar la base de datos completa al mapa vectorial, usar como columna clave la columna "VALUE"
	v.db.connect map=aas_z55 driver=dbf table=aas_z55 key=value		v.db.connect map=aas_z55 driver=dbf table=aas_z55 key=value

	~~Done~~. ~~The data are in~~ GRASS ~~GIS database~~.		Y listo. Los datos están en la base de datos de GRASS.

	~~==== Import E00 raster grids ====~~

	* The {{cmd\|v.in.e00}} module only handles vector data. You will have to convert raster E00 data into an Arc ASCII grid before importing into GRASS with {{cmd\|r.in.gdal}}.
	* [http://lists.osgeo.org/pipermail/grass-user/2009-October/052758.html See instructions in this mailing list post] about the "ArcExplorer Import Utility"

	~~== Linking data to GRASS GIS ==~~

	~~You can link data instead of importing them, use {{cmd\|r.external}}, {{cmd\|v.external}}, {{cmd\|r.external.out}}, and {{cmd\|v.external.out}}. Projection of all data must be consistent.~~

	~~== Various hydrology and terrain analysis commands ==~~

	~~<!-- perhaps this should go to~~ GRASS ~~GIS for ArcGIS users page -->~~		==== Importar mallas ráster E00 ====
	~~<!-- but in general, this page could contains some common usecases which includes hydrology~~ -->		* El módulo {{cmd\|v.in.e00}} solamente manipula datos vectoriales. Debe convertir los datos ráster E00 al formato Arc ASCII antes de importar a GRASS con el comando {{cmd\|r.in.gdal}}.
			* [http://lists.osgeo.org/pipermail/grass-user/2009-October/052758.html Ver las instrucciones en el correo] sbre la "ArcExplorer Import Utility".

	* Watershed modeling differences:		== Enlazar datos en GRASS ==
	** ArcInfo wants a depressionless, filled, hydrologically correct DEM.
	** {{cmd\|r.watershed}} does not need such a DEM, it is happy with a raw DEM even containing depressions, being not filled, and not hydrologically correct (hence, no extra preparations needed!).
	* How to [[Creating_watersheds\|Create watersheds for specific drainage points]] like the Arc Hydro extension
	* See also [[Hydrological Sciences]] for a list of available hydrological GRASS ~~tools~~
	* [http://www.surfaces.co.il/?p=~~241 Watershed Analysis with GRASS] (when you know ESRI)~~
	* [https://grasswiki.osgeo.org/wiki/Creating_watersheds#Calculating_total_drainage_area_for_each_stream_reach Calculating total upstream area for each stream]

	== See also ==		Es posible enlazar los datos, en vez de importarlos usando los comandos {{cmd\|r.external}}, {{cmd\|v.external}}, {{cmd\|r.external.out}}, y {{cmd\|v.external.out}}. Todos los datos deben tener la misma proyección que la Localización de GRASS.== See also ==

	* [[GRASS GIS for ArcGIS users]]		* [[GRASS GIS for ArcGIS users]]
	* [[Terminology comparison between ArcGIS and GRASS GIS]]		* [[Terminology comparison between ArcGIS and GRASS GIS]]

	== ~~External links~~ ==		== Links externos ==

	* ~~Basic~~ [http://geostat-course.org/Topic_NetelerMetz_2012 GRASS GIS ~~tutorial~~] ~~at Geostat 2012~~		* Tutorial básci de GRASS en Gostat 2012 (y otros años) [http://geostat-course.org/Topic_NetelerMetz_2012 Tutorial de GRASS GIS].
	* [http://www.appropedia.org/A_transition_from_ArcGIS_to_open_source_GIS_softwares ~~A transition from~~ ArcGIS ~~to open source GIS softwares~~]		* [http://www.appropedia.org/A_transition_from_ArcGIS_to_open_source_GIS_softwares Transición desde ArcGIS a SIGs libres].
	* [http://gis.stackexchange.com/questions/134/can-arcgis-and-osgeo4w-share-the-same-python-install Can ArcGIS and OSGeo4W share the same python install?]		* [http://gis.stackexchange.com/questions/134/can-arcgis-and-osgeo4w-share-the-same-python-install Can ArcGIS and OSGeo4W share the same python install?]

⚠️Micha: Added one additional item under hydrology

2016-02-01T10:57:36Z

Added one additional item under hydrology

← Older revision		Revision as of 10:57, 1 February 2016
Line 109:		Line 109:
	* See also [[Hydrological Sciences]] for a list of available hydrological GRASS tools		* See also [[Hydrological Sciences]] for a list of available hydrological GRASS tools
	* [http://www.surfaces.co.il/?p=241 Watershed Analysis with GRASS] (when you know ESRI)		* [http://www.surfaces.co.il/?p=241 Watershed Analysis with GRASS] (when you know ESRI)
	* [https://grasswiki.osgeo.org/wiki/Creating_watersheds#Calculating_total_drainage_area_for_each_stream_reach \| Calculating total upstream area for each stream]		* [https://grasswiki.osgeo.org/wiki/Creating_watersheds#Calculating_total_drainage_area_for_each_stream_reach Calculating total upstream area for each stream]

	== See also ==		== See also ==

⚠️Micha: /* Various hydrology and terrain analysis commands */

2016-02-01T10:56:18Z

Various hydrology and terrain analysis commands

← Older revision		Revision as of 10:56, 1 February 2016
Line 109:		Line 109:
	* See also [[Hydrological Sciences]] for a list of available hydrological GRASS tools		* See also [[Hydrological Sciences]] for a list of available hydrological GRASS tools
	* [http://www.surfaces.co.il/?p=241 Watershed Analysis with GRASS] (when you know ESRI)		* [http://www.surfaces.co.il/?p=241 Watershed Analysis with GRASS] (when you know ESRI)
	* [[Calculating_total_drainage_area_for_each_stream_reach \| Calculating total upstream area for each stream]]		* [https://grasswiki.osgeo.org/wiki/Creating_watersheds#Calculating_total_drainage_area_for_each_stream_reach \| Calculating total upstream area for each stream]

	== See also ==		== See also ==

⚠️Micha: One additional internal link in hydrology section

2016-02-01T10:53:19Z

One additional internal link in hydrology section

← Older revision		Revision as of 10:53, 1 February 2016
Line 109:		Line 109:
	* See also [[Hydrological Sciences]] for a list of available hydrological GRASS tools		* See also [[Hydrological Sciences]] for a list of available hydrological GRASS tools
	* [http://www.surfaces.co.il/?p=241 Watershed Analysis with GRASS] (when you know ESRI)		* [http://www.surfaces.co.il/?p=241 Watershed Analysis with GRASS] (when you know ESRI)
			* [[Calculating_total_drainage_area_for_each_stream_reach \| Calculating total upstream area for each stream]]

	== See also ==		== See also ==

⚠️Wenzeslaus: fix sectioning, add r.external

2016-02-01T02:15:14Z

fix sectioning, add r.external

← Older revision		Revision as of 02:15, 1 February 2016
Line 1:		Line 1:
	~~== Basic tutorial for GRASS GIS ==~~		''If you wish to use both GRASS GIS and ArcGIS together, this page is for you.''

	~~See '~~''~~[http://geostat-course.org/Topic_NetelerMetz_2012~~ GRASS GIS ~~tutorial]'~~'' ~~- at Geostat 2012~~

	== Working with your ArcGIS data ==		== Working with your ArcGIS data ==
Line 13:		Line 11:
	The GRASS data structure requires that each data layer have its CRS exactly defined. This is done by maintaining data layers within a "[[Location and Mapsets\|Location]]". Each Location has a strictly defined projection, and datum, and all the data layers (raster and vector) within that location should already be either created in or projected to that CRS. GRASS does '''not''' do "on-the-fly" reprojection to avoid often encountered in other GIS software with datum mismatches. Consequently, data layers in one location are not visible from other locations. However, GRASS does supply a collection of [[Common_Tasks#GIS_Tasks\|tools]] for projecting vector and raster layers from one location to another. Use of these tools is explained in the {{cmd\|projectionintro\|manual}}.		The GRASS data structure requires that each data layer have its CRS exactly defined. This is done by maintaining data layers within a "[[Location and Mapsets\|Location]]". Each Location has a strictly defined projection, and datum, and all the data layers (raster and vector) within that location should already be either created in or projected to that CRS. GRASS does '''not''' do "on-the-fly" reprojection to avoid often encountered in other GIS software with datum mismatches. Consequently, data layers in one location are not visible from other locations. However, GRASS does supply a collection of [[Common_Tasks#GIS_Tasks\|tools]] for projecting vector and raster layers from one location to another. Use of these tools is explained in the {{cmd\|projectionintro\|manual}}.

	=== Vector import/export ~~commands~~ ===		=== Vector import/export ===

	* {{cmd\|v.in.ogr}} - Convert [http://www.gdal.org/ogr OGR] supported vector formats to GRASS vector format.		* {{cmd\|v.in.ogr}} - Convert [http://www.gdal.org/ogr OGR] supported vector formats to GRASS vector format.

	* {{cmd\|v.out.ogr}} - Convert from the GRASS vector format to one of the supported OGR vector formats.		* {{cmd\|v.out.ogr}} - Convert from the GRASS vector format to one of the supported OGR vector formats.

	* {{cmd\|v.in.e00}} - Import a E00 coverage into a GRASS vector map.		* {{cmd\|v.in.e00}} - Import a E00 coverage into a GRASS vector map.


	==== Import of Shapefiles into GRASS ====		==== Import of Shapefiles into GRASS ====
Line 52:		Line 47:
	v.out.ogr input=lines_3d type=line dsn=/tmp olayer=testogr lco="SHPT=ARCZ"		v.out.ogr input=lines_3d type=line dsn=/tmp olayer=testogr lco="SHPT=ARCZ"

	==== Various vector ~~commands~~ ====		==== Various vector operations ====
	* Editing differences		* Editing differences
	: Tips for [[Digitizing_Area_Features\|Digitizing area features with attributes]]		: Tips for [[Digitizing_Area_Features\|Digitizing area features with attributes]]

	=== Raster import/export ~~commands~~ ===		=== Raster import/export ===

	* {{cmd\|r.in.gdal}} - Import [http://www.gdal.org GDAL] supported raster file into a binary raster map layer.		* {{cmd\|r.in.gdal}} - Import [http://www.gdal.org GDAL] supported raster file into a binary raster map layer.
Line 99:		Line 94:
	* [http://lists.osgeo.org/pipermail/grass-user/2009-October/052758.html See instructions in this mailing list post] about the "ArcExplorer Import Utility"		* [http://lists.osgeo.org/pipermail/grass-user/2009-October/052758.html See instructions in this mailing list post] about the "ArcExplorer Import Utility"

	=== Various hydrology and terrain analysis commands ===		== Linking data to GRASS GIS ==

			You can link data instead of importing them, use {{cmd\|r.external}}, {{cmd\|v.external}}, {{cmd\|r.external.out}}, and {{cmd\|v.external.out}}. Projection of all data must be consistent.

			== Various hydrology and terrain analysis commands ==

			<!-- perhaps this should go to GRASS GIS for ArcGIS users page -->
			<!-- but in general, this page could contains some common usecases which includes hydrology -->

	* Watershed modeling differences:		* Watershed modeling differences:
Line 109:		Line 111:

	== See also ==		== See also ==

			* [[GRASS GIS for ArcGIS users]]
			* [[Terminology comparison between ArcGIS and GRASS GIS]]

			== External links ==

			* Basic [http://geostat-course.org/Topic_NetelerMetz_2012 GRASS GIS tutorial] at Geostat 2012
	* [http://www.appropedia.org/A_transition_from_ArcGIS_to_open_source_GIS_softwares A transition from ArcGIS to open source GIS softwares]		* [http://www.appropedia.org/A_transition_from_ArcGIS_to_open_source_GIS_softwares A transition from ArcGIS to open source GIS softwares]
	* [http://gis.stackexchange.com/questions/134/can-arcgis-and-osgeo4w-share-the-same-python-install Can ArcGIS and OSGeo4W share the same python install?]		* [http://gis.stackexchange.com/questions/134/can-arcgis-and-osgeo4w-share-the-same-python-install Can ArcGIS and OSGeo4W share the same python install?]

	~~Wiki pages:~~
	* [[GRASS migration hints]]
	* [[Terminology comparison between ArcGIS and GRASS GIS]]

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

⚠️Wenzeslaus: /* Working with your ArcGIS data */ remove r.in.arc, improve wording and sectioning

2016-02-01T01:59:11Z

Working with your ArcGIS data: remove r.in.arc, improve wording and sectioning

← Older revision		Revision as of 01:59, 1 February 2016
Line 5:		Line 5:
	== Working with your ArcGIS data ==		== Working with your ArcGIS data ==

	~~'''~~Importing ArcGIS Data~~'''~~		=== Importing ArcGIS Data ===

	~~Grass~~ provides ~~convertors~~ for importing ESRI shapefiles, e00 files, and many other GIS formats as well. The key ~~Grass programs~~ for importing vector formats are {{cmd\|v.in.ogr}} (for ESRI ~~shapefiles~~, MapInfo files, SDTS, TIGER, etc.) and {{cmd\|v.in.e00}} for e00 format.		GRASS GIS provides converters for importing ESRI shapefiles, e00 files, and many other GIS formats as well. The key GRASS modules for importing vector formats are {{cmd\|v.in.ogr}} (for ESRI Shapefiles, MapInfo files, SDTS, TIGER, etc.) and {{cmd\|v.in.e00}} for e00 format. For raster data, there is {{cmd\|r.in.gdal}}.

	~~'''~~Coordinate Reference Systems~~'''~~		=== Coordinate Reference Systems ===

	The GRASS data structure requires that each data layer have its CRS exactly defined. This is done by maintaining data layers within a "[[Location and Mapsets\|Location]]". Each Location has a strictly defined projection, and datum, and all the data layers (raster and vector) within that location should already be either created in or projected to that CRS. GRASS does '''not''' do "on-the-fly" reprojection ~~due~~ to ~~the problems~~ often encountered in other GIS software with datum mismatches. So data layers in one location are not visible from other locations. However GRASS does supply a collection of [[Common_Tasks#GIS_Tasks\|tools]] for projecting vector and raster layers from one location to another. Use of these tools is explained in the {{cmd\|projectionintro}} ~~manual~~.		The GRASS data structure requires that each data layer have its CRS exactly defined. This is done by maintaining data layers within a "[[Location and Mapsets\|Location]]". Each Location has a strictly defined projection, and datum, and all the data layers (raster and vector) within that location should already be either created in or projected to that CRS. GRASS does '''not''' do "on-the-fly" reprojection to avoid often encountered in other GIS software with datum mismatches. Consequently, data layers in one location are not visible from other locations. However, GRASS does supply a collection of [[Common_Tasks#GIS_Tasks\|tools]] for projecting vector and raster layers from one location to another. Use of these tools is explained in the {{cmd\|projectionintro\|manual}}.

	=== Vector import/export commands ===		=== Vector import/export commands ===
Line 22:		Line 22:


	==== Import of Shapefiles into ~~Grass~~ ====		==== Import of Shapefiles into GRASS ====

	specify the directory		specify the directory
Line 57:		Line 57:

	=== Raster import/export commands ===		=== Raster import/export commands ===

	* {{cmd\|r.in.arc}} - Convert an ESRI ARC/INFO ascii raster file (GRID) into a GRASS (binary) raster map layer.

	* {{cmd\|r.out.arc}} - Converts a GRASS raster map layer into an ESRI ARCGRID file.
	** [http://listserver.mbari.org/sympa/arc/mbsystem/2009-03/msg00031.html Some tips and tricks for imporing Arc ASCII grids from external software]

	* {{cmd\|r.in.gdal}} - Import [http://www.gdal.org GDAL] supported raster file into a binary raster map layer.		* {{cmd\|r.in.gdal}} - Import [http://www.gdal.org GDAL] supported raster file into a binary raster map layer.
Line 76:		Line 71:

	The trick is to convert the raster coverage to vector		The trick is to convert the raster coverage to vector
	areas to take advantage of GRASS's rich vector attribute/database tie-ins. You can use ~~either {{cmd\|r.in.arc}} or~~ {{cmd\|r.in.gdal}} for the import.		areas to take advantage of GRASS's rich vector attribute/database tie-ins. You can use {{cmd\|r.in.gdal}} for the import.
	~~If using r.in.arc be careful to set the map type to CELL for categorical maps~~.

	# import ArcASCII grid to UTM55S location		# import ArcASCII grid to UTM55S location
Line 98:		Line 92:
	v.db.connect map=aas_z55 driver=dbf table=aas_z55 key=value		v.db.connect map=aas_z55 driver=dbf table=aas_z55 key=value

	~~done!~~		Done. The data are in GRASS GIS database.

	==== Import E00 raster grids ====		==== Import E00 raster grids ====

	The {{cmd\|v.in.e00}} module only handles vector data. You will have to convert raster E00 data into an Arc ASCII grid before importing into GRASS with ~~{{cmd\|r.in.arc}} or~~ {{cmd\|r.in.gdal}}.		* The {{cmd\|v.in.e00}} module only handles vector data. You will have to convert raster E00 data into an Arc ASCII grid before importing into GRASS with {{cmd\|r.in.gdal}}.
			* [http://lists.osgeo.org/pipermail/grass-user/2009-October/052758.html See instructions in this mailing list post] about the "ArcExplorer Import Utility"
	* [http://lists.osgeo.org/pipermail/grass-user/2009-October/052758.html See instructions in this mailing list post] about the
	"ArcExplorer Import Utility"

	=== Various hydrology and terrain analysis commands ===		=== Various hydrology and terrain analysis commands ===

⚠️Wenzeslaus: add arcgis category

2015-08-21T15:09:06Z

add arcgis category

← Older revision		Revision as of 15:09, 21 August 2015
Line 129:		Line 129:
	[[Category: Import]]		[[Category: Import]]
	[[Category: Vector]]		[[Category: Vector]]
			[[Category:ArcGIS]]

Neteler: /* See also */ link to Terminology comparison between ArcGIS and GRASS GIS

2015-08-08T20:20:29Z

← Older revision		Revision as of 20:20, 8 August 2015
Line 120:		Line 120:
	* [http://gis.stackexchange.com/questions/134/can-arcgis-and-osgeo4w-share-the-same-python-install Can ArcGIS and OSGeo4W share the same python install?]		* [http://gis.stackexchange.com/questions/134/can-arcgis-and-osgeo4w-share-the-same-python-install Can ArcGIS and OSGeo4W share the same python install?]

	[[GRASS migration hints]]		Wiki pages:
			* [[GRASS migration hints]]
			* [[Terminology comparison between ArcGIS and GRASS GIS]]

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

Neteler: /* See also */

2013-12-31T18:05:28Z

← Older revision		Revision as of 18:05, 31 December 2013
Line 122:		Line 122:
	[[GRASS migration hints]]		[[GRASS migration hints]]

	[[Category:Documentation]]		[[Category: Documentation]]
	[[Category:FAQ]]		[[Category: FAQ]]
	[[Category: Hydrology]]		[[Category: Hydrology]]
	[[Category: Import]]		[[Category: Import]]
			[[Category: Vector]]