GRASS SoC Ideas 2012 - Revision history

⚠️Wenzeslaus: /* Volume modeling */

2015-12-19T03:49:47Z

Volume modeling

← Older revision		Revision as of 03:49, 19 December 2015
Line 133:		Line 133:
	=== Volume modeling ===		=== Volume modeling ===

	# Develop '''r3.flow''' for computing 3D flow lines and 3D flow accumulation from 3D rasters		# Develop '''r3.flow''' for computing 3D flow lines and 3D flow accumulation from 3D rasters (implemented in [https://trac.osgeo.org/grass/wiki/GSoC/2014/ImplementationOf3DRasterFlowLine GSoC 2014])
	# Enhance volume interpolation module '''{{cmd\|v.vol.rst}}''' for handling of data in space-time cube, including computation of gradients and hypercurvatures		# Enhance volume interpolation module '''{{cmd\|v.vol.rst}}''' for handling of data in space-time cube, including computation of gradients and hypercurvatures

⚠️Landa at 14:49, 27 June 2014

2014-06-27T14:49:16Z

← Older revision		Revision as of 14:49, 27 June 2014
Line 178:		Line 178:

	* Please review the submitting files for our coding standards		* Please review the submitting files for our coding standards
	** {{~~src~~\|SUBMITTING~~\|branch=trunk}} for C coding rules~~		** {{twiki\|Submitting\|SUBMITTING}}
	** {{src\|SUBMITTING_PYTHON\|branch=trunk}} for Python coding rules
	** {{src\|SUBMITTING_DOCS\|branch=trunk}} ~~for Documentantion coding rules~~

	* There is lots of good info at the [http://trac.osgeo.org/grass/wiki GRASS Developer's wiki]		* There is lots of good info at the [http://trac.osgeo.org/grass/wiki GRASS Developer's wiki]

⚠️Wenzeslaus: /* Improved Python interface */ note pygrass

2014-02-06T03:32:59Z

Improved Python interface: note pygrass

← Older revision		Revision as of 03:32, 6 February 2014
Line 145:		Line 145:

	'''Willing to Mentor:''' [[User:Huhabla\|Sören Gebbert]]		'''Willing to Mentor:''' [[User:Huhabla\|Sören Gebbert]]

			''Accepted as Python high level map interaction for GRASS GIS (PyGRASS).''

	=== Other ===		=== Other ===

⚠️Wenzeslaus: /* Ideas */ note wxGUI toolboxes, remove add idea

2014-02-06T03:30:30Z

Ideas: note wxGUI toolboxes, remove add idea

← Older revision		Revision as of 03:30, 6 February 2014
Line 70:		Line 70:
	</gallery>		</gallery>
	</center>		</center>
	~~# ''Your idea here''~~

	'''Willing to Mentor:''' [[User:Landa\|Martin Landa]], [[User:MarisN\|Maris Nartiss]], [[User:Mmetz\|Markus Metz]], (''your name here'')		'''Willing to Mentor:''' [[User:Landa\|Martin Landa]], [[User:MarisN\|Maris Nartiss]], [[User:Mmetz\|Markus Metz]], (''your name here'')
Line 78:		Line 78:
	#Add '''[[OpenMP]] parallelization''' where appropriate, for example {{cmd\|r.cost}}, {{cmd\|r.surf.contour}}, {{cmd\|r.watershed}}. It is important to understand which modules are processor bound, and concentrate on them. i.e. do not needlessly complicate the code of non-long running processor bound modules. A good working knowledge of ANSI C and {{wikipedia\|OpenMP}} is required. ({{wikipedia\|OpenCL}} and {{wikipedia\|pthreads}} are fine too!)		#Add '''[[OpenMP]] parallelization''' where appropriate, for example {{cmd\|r.cost}}, {{cmd\|r.surf.contour}}, {{cmd\|r.watershed}}. It is important to understand which modules are processor bound, and concentrate on them. i.e. do not needlessly complicate the code of non-long running processor bound modules. A good working knowledge of ANSI C and {{wikipedia\|OpenMP}} is required. ({{wikipedia\|OpenCL}} and {{wikipedia\|pthreads}} are fine too!)
	#Create a new GRASS module to find the {{wikipedia\|topographic_prominence}} of peaks from a raster elevation map within the region. (probably this would only make up 1/4 to 1/2 of a multi-part GSoC project)		#Create a new GRASS module to find the {{wikipedia\|topographic_prominence}} of peaks from a raster elevation map within the region. (probably this would only make up 1/4 to 1/2 of a multi-part GSoC project)
	~~# ''Your suggestion here!''~~

	'''Willing to Mentor:''' Hamish (co-mentor parallelization and prominence projects), Wolf Bergenheim(''your name here'')		'''Willing to Mentor:''' Hamish (co-mentor parallelization and prominence projects), Wolf Bergenheim(''your name here'')
Line 89:		Line 89:
	# Speed up [[wxGUI]] handling and 2D display of large point clouds (several million points). This is likely to include additional "Level-1 Vector" support in the backend modules (for which a working knowledge of ANSI C is req'd).		# Speed up [[wxGUI]] handling and 2D display of large point clouds (several million points). This is likely to include additional "Level-1 Vector" support in the backend modules (for which a working knowledge of ANSI C is req'd).
	# Create graphical vector attribute data merging tool and provide necessary functionality in v.patch to allow merging of two vector datasets with different attribute data tables. Tool should provide a GUI way to map attribute table columns, create new ones and, where possible, change data type during merging.		# Create graphical vector attribute data merging tool and provide necessary functionality in v.patch to allow merging of two vector datasets with different attribute data tables. Tool should provide a GUI way to map attribute table columns, create new ones and, where possible, change data type during merging.
	~~# ''Your idea here'' ...~~


Line 104:		Line 104:
	# Implement region-based classification		# Implement region-based classification
	# Implement hierarchical classification tools (e.g. being able to create a large class "forest", with subclasses of different types of forests)		# Implement hierarchical classification tools (e.g. being able to create a large class "forest", with subclasses of different types of forests)
	~~# ''Your idea here''~~

	See the [[Image_processing#Ideas_collection_for_improving_GRASS.27_Image_processing_capabilities\|ideas for imagery improvement]] and [http://trac.osgeo.org/grass/wiki/Grass7/ImageryLib GRASS 7 ideas] wiki pages for more details.		See the [[Image_processing#Ideas_collection_for_improving_GRASS.27_Image_processing_capabilities\|ideas for imagery improvement]] and [http://trac.osgeo.org/grass/wiki/Grass7/ImageryLib GRASS 7 ideas] wiki pages for more details.
Line 116:		Line 116:
	## QGIS/GRASS plugins to invoke an Inkscape process and send a data set.		## QGIS/GRASS plugins to invoke an Inkscape process and send a data set.
	## Inkscape plugin to query various OSGeo projects and display various data sets as layers.		## Inkscape plugin to query various OSGeo projects and display various data sets as layers.
	~~# ''Your idea here ...''~~

	'''Willing to Mentor:''' Hamish (as a co-mentor)		'''Willing to Mentor:''' Hamish (as a co-mentor)
Line 152:		Line 152:
	# Implement selected modules (in C/C++) for geospatial analysis (kriging, etc.) based on [http://hpgl.aoizora.org/ HPGL] library (see also [http://hub.qgis.org/projects/quantum-gis/wiki/Python_Plugin_Ideas#Add-and-R-Free-geostatistic-toolbox-using-HPGL QGIS plugin wish]).		# Implement selected modules (in C/C++) for geospatial analysis (kriging, etc.) based on [http://hpgl.aoizora.org/ HPGL] library (see also [http://hub.qgis.org/projects/quantum-gis/wiki/Python_Plugin_Ideas#Add-and-R-Free-geostatistic-toolbox-using-HPGL QGIS plugin wish]).
	# Design and implement modern '''metadata management system''' for GRASS to support [http://www.opengeospatial.org/standards/cat OGC CSW] and INSPIRE discovery a view services		# Design and implement modern '''metadata management system''' for GRASS to support [http://www.opengeospatial.org/standards/cat OGC CSW] and INSPIRE discovery a view services
	~~<!--~~		# Design '''GRASS toolboxes environment''', see [[GRASS repository layout proposal]] for detailed information. This would also include general clean up and organization of existing GRASS modules in trunk and add-ons. ''[http://trac.osgeo.org/grass/wiki/wxGUIDevelopment/Toolboxes Toolboxes for wxGUI] implemented outside GSoC.''
	# Design '''GRASS toolboxes environment''', see [[GRASS repository layout proposal]] for detailed information. This would also include general clean up and organization of existing GRASS modules in trunk and add-ons.
	~~-->~~
	# ''~~Your idea here~~''

	'''Willing to Mentor:''' Wolf Bergenheim (Python API, metadata management), [[User:Landa\|Martin Landa]] (for HPGL) (''your name here'')		'''Willing to Mentor:''' Wolf Bergenheim (Python API, metadata management), [[User:Landa\|Martin Landa]] (for HPGL) (''your name here'')

⚠️Wenzeslaus: /* wxGUI */ noting implemented animation and mapswipe

2014-02-06T03:22:38Z

wxGUI: noting implemented animation and mapswipe

← Older revision		Revision as of 03:22, 6 February 2014
Line 61:		Line 61:
	=== [[wxGUI]] ===		=== [[wxGUI]] ===

	# Develop GUI support in wxPython for visualy analyzing series of raster map layers. The module should provide users with capabilities to browse and animate raster (and potentially also vector) data series in a 2D display and save outputs to animated GIF, MOV, or MPEG files. A related module that displays the series as small images and support re-ordering, deleting and adding raster maps (frames) to the series would also be helpful. To compare visually two images a slider functionality could be added to the 2D display, for example, to compare before and after images, or two consequent images in series. The series of data layers can be handled as multiple standard raster or vector layers or using the new time series support. See existing modules {{cmd\|xganim}}, {{cmd\|r.out.mpeg}}, [[NVIZ]]'s animation tools, and the [[Movies]] creation wiki page. There is also a related capability in the TclTk GUI. (co-mentor Helena Mitasova).		# Develop GUI support in wxPython for visualy analyzing series of raster map layers. The module should provide users with capabilities to browse and animate raster (and potentially also vector) data series in a 2D display and save outputs to animated GIF, MOV, or MPEG files. A related module that displays the series as small images and support re-ordering, deleting and adding raster maps (frames) to the series would also be helpful. To compare visually two images a slider functionality could be added to the 2D display, for example, to compare before and after images, or two consequent images in series. The series of data layers can be handled as multiple standard raster or vector layers or using the new time series support. See existing modules {{cmd\|xganim}}, {{cmd\|r.out.mpeg}}, [[NVIZ]]'s animation tools, and the [[Movies]] creation wiki page. There is also a related capability in the TclTk GUI. (co-mentor Helena Mitasova). ''This was implemented outside GSoC as {{Cmd\|g.gui.animation\|ver=70}} (GRASS Animation Tool) and {{Cmd\|g.gui.mapswipe\|ver=70}} (GRASS Mapswipe).''
	# Develop an interactive vector geometry selection and export tool for [[wxGUI]] as described in the trac ticket [http://trac.osgeo.org/grass/ticket/1471 #1471]		# Develop an interactive vector geometry selection and export tool for [[wxGUI]] as described in the trac ticket [http://trac.osgeo.org/grass/ticket/1471 #1471]
	# Offer also (optional) "conventional" '''GUI layout''': For some users, the current approach of separate windows (SDI) leads to a '''windows flooding'''. This is a common complaint especially from newbies. Especially on large monitors or dual screen systems catching the [[wxGUI]] windows can be tedious when they appear on separate monitors (depends on windows manager, the much used KDE scatters typically the wxGUI windows all over the screen real estate). Almost each task generates a new wxGUI window which is freely floating around on the screen: [http://grass.osgeo.org/grass63/screenshots/images/wxgrass_digit-03.png example 1] and [http://grass.osgeo.org/grass63/screenshots/images/wxgrass_digit-01.png example 2]. On a dual-screen this may sum up to 50cm of distance! The idea is to capture all those windows in one frame. For details, see [[wxGUI#Layout\| wxGUI layout]].		# Offer also (optional) "conventional" '''GUI layout''': For some users, the current approach of separate windows (SDI) leads to a '''windows flooding'''. This is a common complaint especially from newbies. Especially on large monitors or dual screen systems catching the [[wxGUI]] windows can be tedious when they appear on separate monitors (depends on windows manager, the much used KDE scatters typically the wxGUI windows all over the screen real estate). Almost each task generates a new wxGUI window which is freely floating around on the screen: [http://grass.osgeo.org/grass63/screenshots/images/wxgrass_digit-03.png example 1] and [http://grass.osgeo.org/grass63/screenshots/images/wxgrass_digit-01.png example 2]. On a dual-screen this may sum up to 50cm of distance! The idea is to capture all those windows in one frame. For details, see [[wxGUI#Layout\| wxGUI layout]].

⚠️Landa: /* Accepted Ideas */

2013-05-27T21:23:00Z

Accepted Ideas

← Older revision		Revision as of 21:23, 27 May 2013
Line 195:		Line 195:
	#: Mentor: Sören Gebbert		#: Mentor: Sören Gebbert
	#: Backup mentors: Luca Delucchi, Martin Landa		#: Backup mentors: Luca Delucchi, Martin Landa
	#: Wiki page: [[GRASS ~~SoC~~ 2012 High level map interaction]]		#: Wiki page: [[GRASS GSoC 2012 High level map interaction]]
	# ''GRASS GIS WxGui front end for vector analysis modules'' ([http://www.google-melange.com/gsoc/project/google/gsoc2012/turek/38001 abstract])		# ''GRASS GIS WxGui front end for vector analysis modules'' ([http://www.google-melange.com/gsoc/project/google/gsoc2012/turek/38001 abstract])
	#: Student: Stepan Turek		#: Student: Stepan Turek

⚠️Landa: /* Accepted Ideas */

2013-05-27T21:22:06Z

Accepted Ideas

← Older revision		Revision as of 21:22, 27 May 2013
Line 195:		Line 195:
	#: Mentor: Sören Gebbert		#: Mentor: Sören Gebbert
	#: Backup mentors: Luca Delucchi, Martin Landa		#: Backup mentors: Luca Delucchi, Martin Landa
	#: Wiki page: [[GRASS SoC ~~Ideas~~ 2012/High level map interaction]]		#: Wiki page: [[GRASS SoC 2012 High level map interaction]]
	# ''GRASS GIS WxGui front end for vector analysis modules'' ([http://www.google-melange.com/gsoc/project/google/gsoc2012/turek/38001 abstract])		# ''GRASS GIS WxGui front end for vector analysis modules'' ([http://www.google-melange.com/gsoc/project/google/gsoc2012/turek/38001 abstract])
	#: Student: Stepan Turek		#: Student: Stepan Turek

⚠️MarisN: /* Vector */ Add atribute merging proposal

2013-01-23T05:43:54Z

Vector: Add atribute merging proposal

← Older revision		Revision as of 05:43, 23 January 2013
Line 88:		Line 88:
	# Add '''break lines support to interpolation modules''' ({{cmd\|v.surf.rst}}, {{cmd\|v.surf.idw}}, {{cmd\|v.surf.bspline}}). Current implementations provide no support to specify locations of cliffs or faults* thus leading to improper results within non-continous datasets. See [http://www.spatialanalysisonline.com/output/html/Breaklinesandnaturalboundaries.html Geospatial Analysis - a comprehensive guide. 3rd edition] for description. [*] well, some support exists, see {{AddonCmd\|v.surf.icw}}.		# Add '''break lines support to interpolation modules''' ({{cmd\|v.surf.rst}}, {{cmd\|v.surf.idw}}, {{cmd\|v.surf.bspline}}). Current implementations provide no support to specify locations of cliffs or faults* thus leading to improper results within non-continous datasets. See [http://www.spatialanalysisonline.com/output/html/Breaklinesandnaturalboundaries.html Geospatial Analysis - a comprehensive guide. 3rd edition] for description. [*] well, some support exists, see {{AddonCmd\|v.surf.icw}}.
	# Speed up [[wxGUI]] handling and 2D display of large point clouds (several million points). This is likely to include additional "Level-1 Vector" support in the backend modules (for which a working knowledge of ANSI C is req'd).		# Speed up [[wxGUI]] handling and 2D display of large point clouds (several million points). This is likely to include additional "Level-1 Vector" support in the backend modules (for which a working knowledge of ANSI C is req'd).
			# Create graphical vector attribute data merging tool and provide necessary functionality in v.patch to allow merging of two vector datasets with different attribute data tables. Tool should provide a GUI way to map attribute table columns, create new ones and, where possible, change data type during merging.
	# ''Your idea here'' ...		# ''Your idea here'' ...

Neteler: rmoved outdated ideas pages

2012-12-22T17:41:35Z

rmoved outdated ideas pages

← Older revision		Revision as of 17:41, 22 December 2012
Line 55:		Line 55:
	== Ideas ==		== Ideas ==

	* Also review ideas from ~~[[GRASS SoC Ideas 2007#Ideas\|2007]], [[GRASS SoC Ideas 2008#Ideas\|2008]],~~ [[GRASS SoC Ideas 2009#Ideas\|2009]], [[GRASS SoC Ideas 2010#Ideas\|2010]], and [[GRASS SoC Ideas 2011#Ideas\|2011]] which are still open.		* Also review ideas from [[GRASS SoC Ideas 2009#Ideas\|2009]], [[GRASS SoC Ideas 2010#Ideas\|2010]], and [[GRASS SoC Ideas 2011#Ideas\|2011]] which are still open.

	* Project ideas of '''your own''' are also most welcome and often the best.		* Project ideas of '''your own''' are also most welcome and often the best.

⚠️Landa: /* Accepted Ideas */

2012-05-06T09:27:52Z

Accepted Ideas

← Older revision		Revision as of 09:27, 6 May 2012
Line 199:		Line 199:
	#: Mentor: Martin Landa		#: Mentor: Martin Landa
	#: Backup mentor: Markus Metz		#: Backup mentor: Markus Metz
	#: Wiki page: ~~wiki/blog page maintained by the student (typically in this~~ GRASS ~~wiki, or the trac development wiki, with weekly progress reports)~~		#: Wiki page: [[GRASS GSoC 2012 WxGUI front end for vector analysis modules]]
	# ''Image Segmentation in GRASS GIS'' ([http://www.google-melange.com/gsoc/project/google/gsoc2012/emomsen/20001 abstract])		# ''Image Segmentation in GRASS GIS'' ([http://www.google-melange.com/gsoc/project/google/gsoc2012/emomsen/20001 abstract])
	#: Student: Eric Momsen		#: Student: Eric Momsen