GRASS GIS Standardized Sample Datasets - Revision history

⚠️Wenzeslaus: /* References */ add qgis training manual link

2016-01-13T02:27:26Z

References: add qgis training manual link

← Older revision		Revision as of 02:27, 13 January 2016
Line 100:		Line 100:
	* Petras V., Petrasova, A., Cepero-Perez, K., Neteler, M., Delucchi, L., Landa, M., Mitasova, H. ''[http://wenzeslaus.github.io/foss-in-geospatial-science-education Using Free and Open Source Solutions in Geospatial Science Education]''. FOSS4G Europe 2015. July 16, 2015, Como, Italy. (Contains examples of the different datasets, their usage and authors.)		* Petras V., Petrasova, A., Cepero-Perez, K., Neteler, M., Delucchi, L., Landa, M., Mitasova, H. ''[http://wenzeslaus.github.io/foss-in-geospatial-science-education Using Free and Open Source Solutions in Geospatial Science Education]''. FOSS4G Europe 2015. July 16, 2015, Como, Italy. (Contains examples of the different datasets, their usage and authors.)
	* Petras, V., Petrasova, A., Harmon, B., Meentemeyer, R.K., Mitasova, H. ''[http://www.mdpi.com/2220-9964/4/2/942/pdf Integrating Free and Open Source Solutions into Geospatial Science Education]''. ISPRS International Journal of Geo-Information. 2015, 4, 942-956. [http://dx.doi.org/10.3390/ijgi4020942 doi:10.3390/ijgi4020942] (Contains explanation of usage of the GRASS GIS commands concept to get teaching materials which are easy to maintain.)		* Petras, V., Petrasova, A., Harmon, B., Meentemeyer, R.K., Mitasova, H. ''[http://www.mdpi.com/2220-9964/4/2/942/pdf Integrating Free and Open Source Solutions into Geospatial Science Education]''. ISPRS International Journal of Geo-Information. 2015, 4, 942-956. [http://dx.doi.org/10.3390/ijgi4020942 doi:10.3390/ijgi4020942] (Contains explanation of usage of the GRASS GIS commands concept to get teaching materials which are easy to maintain.)

			== See also ==

			* [http://docs.qgis.org/2.8/en/docs/training_manual/foreword/preparing_data.html QGIS Training manual] which uses similar concept and has instructions to create similar dataset to the provided one with the local geospatial data and has a script to replace some values in the teaching material itself.

	== Contact ==		== Contact ==

	If you are interested in producing and sharing a dataset for your region and you want more information, please contact [[User:Wenzeslaus\|Vaclav Petras]] or ideally [https://lists.osgeo.org/mailman/listinfo/grass-user grass-user] mailing list (you must be subscribed to it to post messages).		If you are interested in producing and sharing a dataset for your region and you want more information, please contact [[User:Wenzeslaus\|Vaclav Petras]] or ideally [https://lists.osgeo.org/mailman/listinfo/grass-user grass-user] mailing list (you must be subscribed to it to post messages).

⚠️Wenzeslaus: Mediawiki actually preserves double newline before the section title, so don't use it

2015-11-12T01:26:02Z

Mediawiki actually preserves double newline before the section title, so don't use it

⚠️Wenzeslaus: spread the side images across the page to fix overlaps with headings and make it more interesting overall

2015-11-11T16:58:56Z

spread the side images across the page to fix overlaps with headings and make it more interesting overall

← Older revision		Revision as of 16:58, 11 November 2015
Line 9:		Line 9:
	GRASS GIS is quite advantageous in this concept as the workflows, including most of the visualizations, can be recoded as commands. These commands can be executed in a command line but they also map one-to-one to use of graphical user interface (GUI). Moreover, the whole set of commands can be executed automatically to check that the instructions work with the given dataset. Similar principles can be applied for other packages especially when Python or R is used, although the translation to GUI is often not as smooth as in case of GRASS GIS and its command line or Python interface (or rgrass7 for that matter). Finally, even applications or courses which are using only GUI can benefit from using a standardized set of names as the sentence or screenshot containing text ''and now add the elevation layer'' will always work regardless the particular dataset used.		GRASS GIS is quite advantageous in this concept as the workflows, including most of the visualizations, can be recoded as commands. These commands can be executed in a command line but they also map one-to-one to use of graphical user interface (GUI). Moreover, the whole set of commands can be executed automatically to check that the instructions work with the given dataset. Similar principles can be applied for other packages especially when Python or R is used, although the translation to GUI is often not as smooth as in case of GRASS GIS and its command line or Python interface (or rgrass7 for that matter). Finally, even applications or courses which are using only GUI can benefit from using a standardized set of names as the sentence or screenshot containing text ''and now add the elevation layer'' will always work regardless the particular dataset used.

			[[File:std_dataset_nc_stripe.png\|thumb\|North Carolina (USA) dataset\|700px]]

	== List of datasets ==		== List of datasets ==
Line 25:		Line 26:

	=== Computing slope and aspect ===		=== Computing slope and aspect ===

			[[File:std_dataset_it_stripe.png\|thumb\|Piemonte (Italy) dataset\|700px]]

	Compute slope, aspect and profile curvature of the terrain:		Compute slope, aspect and profile curvature of the terrain:
Line 50:		Line 53:
	cols=574		cols=574
	-->		-->

	~~[[File:std_dataset_nc_stripe.png\|thumb\|North Carolina (USA) dataset\|700px]]~~
	~~[[File:std_dataset_it_stripe.png\|thumb\|Piemonte (Italy) dataset\|700px]]~~
	~~[[File:std_dataset_pr_stripe.png\|thumb\|Puerto Rico dataset\|700px]]~~
	~~[[File:std_dataset_cz_stripe.png\|thumb\|Czech Republic dataset\|700px]]~~

	=== Visualizing shaded relief ===		=== Visualizing shaded relief ===
Line 76:		Line 74:

	== Internationalization ==		== Internationalization ==

			[[File:std_dataset_pr_stripe.png\|thumb\|Puerto Rico dataset\|700px]]

	The basic idea of the standardized datasets is that one would be able to use the same instructions, likely series of commands in case of GRASS GIS, for different locations in the world to make it more interesting and personal to the audience. However, sometimes English names in the dataset might not be appropriate for the audience. In this case, different language versions of the dataset can be kept and maintained with the help of bulk renaming modules (see below). Providing both versions, national one and the English one, gives more options for example, the audience can use one with the provided teaching materials and the other with the generally available materials elsewhere benefiting from the familiar data.		The basic idea of the standardized datasets is that one would be able to use the same instructions, likely series of commands in case of GRASS GIS, for different locations in the world to make it more interesting and personal to the audience. However, sometimes English names in the dataset might not be appropriate for the audience. In this case, different language versions of the dataset can be kept and maintained with the help of bulk renaming modules (see below). Providing both versions, national one and the English one, gives more options for example, the audience can use one with the provided teaching materials and the other with the generally available materials elsewhere benefiting from the familiar data.
Line 86:		Line 86:

	== Tools to help with managing a dataset ==		== Tools to help with managing a dataset ==

			[[File:std_dataset_cz_stripe.png\|thumb\|Czech Republic dataset\|700px]]

	* [http://grass.osgeo.org/grass70/manuals/g.rename.html g.rename] for changing names of individual raster and vector maps		* [http://grass.osgeo.org/grass70/manuals/g.rename.html g.rename] for changing names of individual raster and vector maps

⚠️Wenzeslaus: explain concepts

2015-11-11T16:48:42Z

explain concepts

@@ Line 1: / Line 1: @@
-{{ToModify}}
+[[File:Three_datasets_with_instructions.png|thumb|Example analysis in three regions with GRASS GIS commands as an example of a workflow]]
 == List of datasets ==
@@ Line 7: / Line 14: @@
 '''Already published:'''
 * [http://grass.osgeo.org/download/sample-data/ North Carolina GRASS Sample Location] (2007, map names partially standardized, content partially standardized, currently used dataset, to be deprecated)
-* [http://geodati.fmach.it/gfoss_geodata/libro_gfoss/ Piemonte, Italy] (2012, map names not standardized, content not standardized, work in progress, see below)
+* [http://geodati.fmach.it/gfoss_geodata/libro_gfoss/ Piemonte, Italy] (2012, map names not standardized, content not standardized, see below for a new standardized version)
 * Spearfish, USA (to be phased out, 1986)
@@ Line 66: / Line 73: @@
 * [http://grass.osgeo.org/grass70/manuals/ GRASS GIS manual] (currently using original, not fully compliant North Carolina GRASS Sample Location)
 * [http://courses.ncsu.edu/gis582/common/ NCSU Geospatial Modeling and Analysis course] and other [http://geospatial.ncsu.edu/osgeorel/courses.html NCSU OSGeoREL courses] (currently using original, not fully compliant North Carolina GRASS Sample Location)
 == Tools to help with managing a dataset ==
@@ Line 73: / Line 91: @@
 * [http://grass.osgeo.org/grass70/manuals/addons/r.in.proj.html r.in.proj] and [http://grass.osgeo.org/grass70/manuals/addons/v.in.proj.html v.in.proj] for importing data with different coordinate system
 * Python script [https://trac.osgeo.org/grass/browser/grass-addons/tools/std_dataset_display.py std_dataset_display.py] for generating some maps and images
 == Contact ==
-If you are interested in producing a dataset for your region, please contact [https://lists.osgeo.org/mailman/listinfo/grass-user grass-user] mailing list or  [[User:Wenzeslaus|Vaclav Petras]].
+If you are interested in producing and sharing a dataset for your region and you want more information, please contact [[User:Wenzeslaus|Vaclav Petras]] or ideally [https://lists.osgeo.org/mailman/listinfo/grass-user grass-user] mailing list (you must be subscribed to it to post messages).

⚠️Matmar: ulr updated

2015-10-13T08:48:35Z

ulr updated

← Older revision		Revision as of 08:48, 13 October 2015
Line 6:		Line 6:

	'''Already published:'''		'''Already published:'''
	* [http://grass.osgeo.org/download/sample-data/ North Carolina GRASS Sample Location] (map names partially standardized, content partially standardized, currently used dataset, to be deprecated)		* [http://grass.osgeo.org/download/sample-data/ North Carolina GRASS Sample Location] (2007, map names partially standardized, content partially standardized, currently used dataset, to be deprecated)
	* [http://geodati.fmach.it/gfoss_geodata/libro_gfoss/ Piemonte, Italy] (map names not standardized, content not standardized, work in progress)		* [http://geodati.fmach.it/gfoss_geodata/libro_gfoss/ Piemonte, Italy] (2012, map names not standardized, content not standardized, work in progress, see below)
	* Spearfish, USA (to be phased out)		* Spearfish, USA (to be phased out, 1986)

	Planning - Future datasets		'''Planning - Future standardized datasets'''
	* [http://trac.osgeo.org/grass/wiki/SampleDataset GRASS GIS North Carolina USA Sample Dataset] (reference for other datasets, under development)		* [http://trac.osgeo.org/grass/wiki/SampleDataset GRASS GIS North Carolina USA Sample Dataset] (reference for other datasets, under development)
	* [http://trac.osgeo.org/grass/wiki/SampleDataset/Italy/~~Piemonte~~ GRASS GIS Piemonte Italy Sample Dataset]		* [http://trac.osgeo.org/grass/wiki/SampleDataset/Italy/Piemont GRASS GIS Piemonte Italy Sample Dataset]
	* [http://trac.osgeo.org/grass/wiki/SampleDataset/World GRASS GIS World Sample Dataset]		* [http://trac.osgeo.org/grass/wiki/SampleDataset/World GRASS GIS World Sample Dataset]

⚠️Wenzeslaus: /* Tools to help with managing a dataset */

2015-07-18T11:50:48Z

Tools to help with managing a dataset

← Older revision		Revision as of 11:50, 18 July 2015
Line 72:		Line 72:
	* [http://grass.osgeo.org/grass70/manuals/addons/g.rename.many.html g.rename.many] for renaming large amount of maps (to standard names or to/from different language)		* [http://grass.osgeo.org/grass70/manuals/addons/g.rename.many.html g.rename.many] for renaming large amount of maps (to standard names or to/from different language)
	* [http://grass.osgeo.org/grass70/manuals/addons/r.in.proj.html r.in.proj] and [http://grass.osgeo.org/grass70/manuals/addons/v.in.proj.html v.in.proj] for importing data with different coordinate system		* [http://grass.osgeo.org/grass70/manuals/addons/r.in.proj.html r.in.proj] and [http://grass.osgeo.org/grass70/manuals/addons/v.in.proj.html v.in.proj] for importing data with different coordinate system
	* [https://trac.osgeo.org/grass/browser/grass-addons/tools/std_dataset_display.py ~~Python script~~ std_dataset_display.py]		* Python script [https://trac.osgeo.org/grass/browser/grass-addons/tools/std_dataset_display.py std_dataset_display.py] for generating some maps and images


			== Contact ==

			If you are interested in producing a dataset for your region, please contact [https://lists.osgeo.org/mailman/listinfo/grass-user grass-user] mailing list or [[User:Wenzeslaus\|Vaclav Petras]].

⚠️Wenzeslaus: /* Tools to help with managing a dataset */ add the display Python script

2015-07-18T11:34:58Z

Tools to help with managing a dataset: add the display Python script

← Older revision		Revision as of 11:34, 18 July 2015
Line 72:		Line 72:
	* [http://grass.osgeo.org/grass70/manuals/addons/g.rename.many.html g.rename.many] for renaming large amount of maps (to standard names or to/from different language)		* [http://grass.osgeo.org/grass70/manuals/addons/g.rename.many.html g.rename.many] for renaming large amount of maps (to standard names or to/from different language)
	* [http://grass.osgeo.org/grass70/manuals/addons/r.in.proj.html r.in.proj] and [http://grass.osgeo.org/grass70/manuals/addons/v.in.proj.html v.in.proj] for importing data with different coordinate system		* [http://grass.osgeo.org/grass70/manuals/addons/r.in.proj.html r.in.proj] and [http://grass.osgeo.org/grass70/manuals/addons/v.in.proj.html v.in.proj] for importing data with different coordinate system
			* [https://trac.osgeo.org/grass/browser/grass-addons/tools/std_dataset_display.py Python script std_dataset_display.py]

Neteler: +World data set link

2015-06-12T12:53:15Z

+World data set link

← Older revision		Revision as of 12:53, 12 June 2015
Line 5:		Line 5:
	== List of datasets ==		== List of datasets ==

	Already published:		'''Already published:'''
	* [http://grass.osgeo.org/download/sample-data/ North Carolina GRASS Sample Location] (map names partially standardized, content partially standardized, currently used dataset, to be ~~depreciated~~)		* [http://grass.osgeo.org/download/sample-data/ North Carolina GRASS Sample Location] (map names partially standardized, content partially standardized, currently used dataset, to be deprecated)
	* [http://geodati.fmach.it/gfoss_geodata/libro_gfoss/ Piemonte, Italy] (map names not standardized, content not standardized, work in progress)		* [http://geodati.fmach.it/gfoss_geodata/libro_gfoss/ Piemonte, Italy] (map names not standardized, content not standardized, work in progress)
	* Spearfish, USA (to be phased out)		* Spearfish, USA (to be phased out)

	Planning - Future datasets		Planning - Future datasets
	* [http://trac.osgeo.org/grass/wiki/SampleDataset GRASS GIS Sample Dataset] (reference for other datasets, under development)		* [http://trac.osgeo.org/grass/wiki/SampleDataset GRASS GIS North Carolina USA Sample Dataset] (reference for other datasets, under development)
	* [http://trac.osgeo.org/grass/wiki/SampleDataset/Italy/Piemonte GRASS GIS Piemonte Italy Sample Dataset]		* [http://trac.osgeo.org/grass/wiki/SampleDataset/Italy/Piemonte GRASS GIS Piemonte Italy Sample Dataset]
			* [http://trac.osgeo.org/grass/wiki/SampleDataset/World GRASS GIS World Sample Dataset]

	== Examples ==		== Examples ==

Neteler: cleanup

2015-06-12T12:19:40Z

cleanup

← Older revision		Revision as of 12:19, 12 June 2015
Line 5:		Line 5:
	== List of datasets ==		== List of datasets ==

	* Future [http:~~//trac.osgeo.org/grass/wiki/SampleDataset GRASS GIS Sample Dataset] (reference for other datasets, under development)~~		Already published:
	* ~~Original~~ [http://grass.osgeo.org/download/sample-data/ North Carolina GRASS Sample Location] (map names partially standardized, content partially standardized, currently used dataset, to be depreciated)		* [http://grass.osgeo.org/download/sample-data/ North Carolina GRASS Sample Location] (map names partially standardized, content partially standardized, currently used dataset, to be depreciated)
	* [http://geodati.fmach.it/gfoss_geodata/libro_gfoss/ Piemonte, Italy] (map names not standardized, content not standardized, work in progress)		* [http://geodati.fmach.it/gfoss_geodata/libro_gfoss/ Piemonte, Italy] (map names not standardized, content not standardized, work in progress)
			* Spearfish, USA (to be phased out)

			Planning - Future datasets
			* [http://trac.osgeo.org/grass/wiki/SampleDataset GRASS GIS Sample Dataset] (reference for other datasets, under development)
			* [http://trac.osgeo.org/grass/wiki/SampleDataset/Italy/Piemonte GRASS GIS Piemonte Italy Sample Dataset]

	== Examples ==		== Examples ==

⚠️Wenzeslaus: /* Computing slope and aspect */ replace individual images by stripe with legends etc.

2015-06-12T03:53:35Z

Computing slope and aspect: replace individual images by stripe with legends etc.

← Older revision		Revision as of 03:53, 12 June 2015
Line 19:		Line 19:

	<!--		<!--
			not used now because this needs individual approach

	Piemonte display region:		Piemonte display region:
	north: 5136489.9425		north: 5136489.9425
Line 36:		Line 38:
	-->		-->

	~~<gallery mode=packed>~~		[[File:std_dataset_nc_stripe.png\|thumb\|North Carolina (USA) dataset\|700px]]
	File:~~std_dataset_nc_aspect~~.png\|~~Aspect (~~North Carolina, USA)		[[File:std_dataset_it_stripe.png\|thumb\|Piemonte (Italy) dataset\|700px]]
	~~File:std_dataset_nc_slope.png~~\|~~Slope (North Carolina, USA)~~		[[File:std_dataset_pr_stripe.png\|thumb\|Puerto Rico dataset\|700px]]
	File:~~std_dataset_nc_profile_curvature~~.png\|~~Profile curvature (North Carolina, USA)~~		[[File:std_dataset_cz_stripe.png\|thumb\|Czech Republic dataset\|700px]]
	~~File:std_dataset_piemonte_aspect.png~~\|~~Aspect~~ (~~Piemonte,~~ Italy)
	File:~~std_dataset_piemonte_slope~~.png\|~~Slope (Piemonte, Italy)~~
	File:~~std_dataset_piemonte_profile_curvature~~.png\|~~Profile curvature (Piemonte, Italy)~~
	~~</gallery>~~

	=== Visualizing shaded relief ===		=== Visualizing shaded relief ===

← Older revision		Revision as of 01:26, 12 November 2015
Line 71:		Line 71:
	* [http://grass.osgeo.org/grass70/manuals/ GRASS GIS manual] (currently using original, not fully compliant North Carolina GRASS Sample Location)		* [http://grass.osgeo.org/grass70/manuals/ GRASS GIS manual] (currently using original, not fully compliant North Carolina GRASS Sample Location)
	* [http://courses.ncsu.edu/gis582/common/ NCSU Geospatial Modeling and Analysis course] and other [http://geospatial.ncsu.edu/osgeorel/courses.html NCSU OSGeoREL courses] (currently using original, not fully compliant North Carolina GRASS Sample Location)		* [http://courses.ncsu.edu/gis582/common/ NCSU Geospatial Modeling and Analysis course] and other [http://geospatial.ncsu.edu/osgeorel/courses.html NCSU OSGeoREL courses] (currently using original, not fully compliant North Carolina GRASS Sample Location)


	== Internationalization ==		== Internationalization ==
Line 78:		Line 77:

	The basic idea of the standardized datasets is that one would be able to use the same instructions, likely series of commands in case of GRASS GIS, for different locations in the world to make it more interesting and personal to the audience. However, sometimes English names in the dataset might not be appropriate for the audience. In this case, different language versions of the dataset can be kept and maintained with the help of bulk renaming modules (see below). Providing both versions, national one and the English one, gives more options for example, the audience can use one with the provided teaching materials and the other with the generally available materials elsewhere benefiting from the familiar data.		The basic idea of the standardized datasets is that one would be able to use the same instructions, likely series of commands in case of GRASS GIS, for different locations in the world to make it more interesting and personal to the audience. However, sometimes English names in the dataset might not be appropriate for the audience. In this case, different language versions of the dataset can be kept and maintained with the help of bulk renaming modules (see below). Providing both versions, national one and the English one, gives more options for example, the audience can use one with the provided teaching materials and the other with the generally available materials elsewhere benefiting from the familiar data.


	== Usages for something else than GRASS GIS ==		== Usages for something else than GRASS GIS ==

	Even courses which teach GRASS GIS and some other software (for example the NCSU courses mentioned elsewhere) and courses using something else than GRASS GIS can use the concept of standardized sample dataset as the main idea is to keep given names and provide basic set of data. A script can be used to provide the dataset in different formats, e.g. GRASS Location for GRASS GIS and GeoTIFFs and SpatialLite for QGIS. GRASS GIS (GRASS Location and Mapset) is a good choice for the primary dataset as it enforces data consistency (coordinate system and topology) and has unified approach to vector, raster and 3D raster data.		Even courses which teach GRASS GIS and some other software (for example the NCSU courses mentioned elsewhere) and courses using something else than GRASS GIS can use the concept of standardized sample dataset as the main idea is to keep given names and provide basic set of data. A script can be used to provide the dataset in different formats, e.g. GRASS Location for GRASS GIS and GeoTIFFs and SpatialLite for QGIS. GRASS GIS (GRASS Location and Mapset) is a good choice for the primary dataset as it enforces data consistency (coordinate system and topology) and has unified approach to vector, raster and 3D raster data.


	== Tools to help with managing a dataset ==		== Tools to help with managing a dataset ==
Line 93:		Line 90:
	* [http://grass.osgeo.org/grass70/manuals/addons/r.in.proj.html r.in.proj] and [http://grass.osgeo.org/grass70/manuals/addons/v.in.proj.html v.in.proj] for importing data with different coordinate system		* [http://grass.osgeo.org/grass70/manuals/addons/r.in.proj.html r.in.proj] and [http://grass.osgeo.org/grass70/manuals/addons/v.in.proj.html v.in.proj] for importing data with different coordinate system
	* Python script [https://trac.osgeo.org/grass/browser/grass-addons/tools/std_dataset_display.py std_dataset_display.py] for generating some maps and images		* Python script [https://trac.osgeo.org/grass/browser/grass-addons/tools/std_dataset_display.py std_dataset_display.py] for generating some maps and images


	== Improving the idea and the datasets ==		== Improving the idea and the datasets ==

	GRASS Trac wiki contains a page dedicated to the development of the concept of the datasets and also pages dedicated to development of the particular datasets. The main Trac wiki page for datasets is {{twiki\|SampleDataset}}. If you see some issues with the data or the concept you can open a bug report or a feature request as an issue in [https://trac.osgeo.org/grass/ GRASS GIS Trac instance] with ''Component'' set to ''Datasets''. Note that you need an OSGeo userID for both Trac wiki and Trac issues.		GRASS Trac wiki contains a page dedicated to the development of the concept of the datasets and also pages dedicated to development of the particular datasets. The main Trac wiki page for datasets is {{twiki\|SampleDataset}}. If you see some issues with the data or the concept you can open a bug report or a feature request as an issue in [https://trac.osgeo.org/grass/ GRASS GIS Trac instance] with ''Component'' set to ''Datasets''. Note that you need an OSGeo userID for both Trac wiki and Trac issues.


	== References ==		== References ==
Line 105:		Line 100:
	* Petras V., Petrasova, A., Cepero-Perez, K., Neteler, M., Delucchi, L., Landa, M., Mitasova, H. ''[http://wenzeslaus.github.io/foss-in-geospatial-science-education Using Free and Open Source Solutions in Geospatial Science Education]''. FOSS4G Europe 2015. July 16, 2015, Como, Italy. (Contains examples of the different datasets, their usage and authors.)		* Petras V., Petrasova, A., Cepero-Perez, K., Neteler, M., Delucchi, L., Landa, M., Mitasova, H. ''[http://wenzeslaus.github.io/foss-in-geospatial-science-education Using Free and Open Source Solutions in Geospatial Science Education]''. FOSS4G Europe 2015. July 16, 2015, Como, Italy. (Contains examples of the different datasets, their usage and authors.)
	* Petras, V., Petrasova, A., Harmon, B., Meentemeyer, R.K., Mitasova, H. ''[http://www.mdpi.com/2220-9964/4/2/942/pdf Integrating Free and Open Source Solutions into Geospatial Science Education]''. ISPRS International Journal of Geo-Information. 2015, 4, 942-956. [http://dx.doi.org/10.3390/ijgi4020942 doi:10.3390/ijgi4020942] (Contains explanation of usage of the GRASS GIS commands concept to get teaching materials which are easy to maintain.)		* Petras, V., Petrasova, A., Harmon, B., Meentemeyer, R.K., Mitasova, H. ''[http://www.mdpi.com/2220-9964/4/2/942/pdf Integrating Free and Open Source Solutions into Geospatial Science Education]''. ISPRS International Journal of Geo-Information. 2015, 4, 942-956. [http://dx.doi.org/10.3390/ijgi4020942 doi:10.3390/ijgi4020942] (Contains explanation of usage of the GRASS GIS commands concept to get teaching materials which are easy to maintain.)


	== Contact ==		== Contact ==

	If you are interested in producing and sharing a dataset for your region and you want more information, please contact [[User:Wenzeslaus\|Vaclav Petras]] or ideally [https://lists.osgeo.org/mailman/listinfo/grass-user grass-user] mailing list (you must be subscribed to it to post messages).		If you are interested in producing and sharing a dataset for your region and you want more information, please contact [[User:Wenzeslaus\|Vaclav Petras]] or ideally [https://lists.osgeo.org/mailman/listinfo/grass-user grass-user] mailing list (you must be subscribed to it to post messages).