GRASS SoC Ideas 2009 - Revision history

⚠️Wenzeslaus: /* wxGUI */

2014-02-06T04:27:01Z

wxGUI

← Older revision		Revision as of 04:27, 6 February 2014
Line 67:		Line 67:
	* Implement [[wxGUI#Graphical_Modeller\|graphical modeller]]. ''It is implemented.''		* Implement [[wxGUI#Graphical_Modeller\|graphical modeller]]. ''It is implemented.''

	* Develop a [[WxPython-based_GUI_for_GRASS#Cartography_tools\|graphical cartographic module]] - something like a GUI front-end or replacement for ps.map. ''Implemented outside GSoC as {{~~{Cmd~~\|g.gui.psmap}}}.''		* Develop a [[WxPython-based_GUI_for_GRASS#Cartography_tools\|graphical cartographic module]] - something like a GUI front-end or replacement for ps.map. ''Implemented outside GSoC as {{cmd\|g.gui.psmap}}.''

	* Create a fully functional command line interface with history within the GUI (see [http://trac.osgeo.org/grass/ticket/528#comment:6 suggestion]) ['''update: now mostly complete''']		* Create a fully functional command line interface with history within the GUI (see [http://trac.osgeo.org/grass/ticket/528#comment:6 suggestion]) ['''update: now mostly complete''']

⚠️Wenzeslaus: /* wxGUI */

2014-02-06T04:26:19Z

wxGUI

← Older revision		Revision as of 04:26, 6 February 2014
Line 67:		Line 67:
	* Implement [[wxGUI#Graphical_Modeller\|graphical modeller]]. ''It is implemented.''		* Implement [[wxGUI#Graphical_Modeller\|graphical modeller]]. ''It is implemented.''

	* Develop a [[WxPython-based_GUI_for_GRASS#Cartography_tools\|graphical cartographic module]] - something like a GUI front-end or replacement for ps.map. ''Implemented outside GSoC as {{{Cmd\|g.gui.psmap}}.''		* Develop a [[WxPython-based_GUI_for_GRASS#Cartography_tools\|graphical cartographic module]] - something like a GUI front-end or replacement for ps.map. ''Implemented outside GSoC as {{{Cmd\|g.gui.psmap}}}.''

	* Create a fully functional command line interface with history within the GUI (see [http://trac.osgeo.org/grass/ticket/528#comment:6 suggestion]) ['''update: now mostly complete''']		* Create a fully functional command line interface with history within the GUI (see [http://trac.osgeo.org/grass/ticket/528#comment:6 suggestion]) ['''update: now mostly complete''']

⚠️Wenzeslaus: /* wxGUI */

2014-02-06T04:19:35Z

wxGUI

← Older revision		Revision as of 04:19, 6 February 2014
Line 71:		Line 71:
	* Create a fully functional command line interface with history within the GUI (see [http://trac.osgeo.org/grass/ticket/528#comment:6 suggestion]) ['''update: now mostly complete''']		* Create a fully functional command line interface with history within the GUI (see [http://trac.osgeo.org/grass/ticket/528#comment:6 suggestion]) ['''update: now mostly complete''']

	* Develop a GUI module in wxPython for creating animations from multiple maps and saving animation outputs to animated GIF, MOV, or MPEG files. ''Implemented outside GSoC as {{{Cmd\|g.gui.animation}}.''		* Develop a GUI module in wxPython for creating animations from multiple maps and saving animation outputs to animated GIF, MOV, or MPEG files. ''Implemented outside GSoC as {{Cmd\|g.gui.animation}}.''

	====Kriging GUI====		====Kriging GUI====

⚠️Wenzeslaus: /* wxGUI */ note g.giui.psmap and animation

2014-02-06T04:19:13Z

wxGUI: note g.giui.psmap and animation

← Older revision		Revision as of 04:19, 6 February 2014
Line 61:		Line 61:
	</center>		</center>

	* Implement new [[wxGUI#GEM integration\|extension manager]] which downloads from GRASS Addons SVN (Unix based systems) or from precompiled Windows binaries ([http://trac.osgeo.org/osgeo4w/ OSGeo4W]?). See the [http://cran.at.r-project.org/web/packages/ R packages manager] and Markus's new {{cmd\|g.extension\|version=65}} module in GRASS 6.5+. ~~['''update: now partly complete''']~~		* Implement new [[wxGUI#GEM integration\|extension manager]] which downloads from GRASS Addons SVN (Unix based systems) or from precompiled Windows binaries ([http://trac.osgeo.org/osgeo4w/ OSGeo4W]?). See the [http://cran.at.r-project.org/web/packages/ R packages manager] and Markus's new {{cmd\|g.extension\|version=65}} module in GRASS 6.5+. Now available as {{{Cmd\|g.extension}}} and Extension (Addons) manager in GUI.

	* Continue [[wxNviz]] development for enhanced 3-4D visualization and analysis.		* Continue [[wxNviz]] development for enhanced 3-4D visualization and analysis.

	* Implement [[wxGUI#~~Graphical_modeller~~\|graphical modeller]].		* Implement [[wxGUI#Graphical_Modeller\|graphical modeller]]. ''It is implemented.''

	* Develop a [[WxPython-based_GUI_for_GRASS#Cartography_tools\|graphical cartographic module]] - something like a GUI front-end or replacement for ps.map		* Develop a [[WxPython-based_GUI_for_GRASS#Cartography_tools\|graphical cartographic module]] - something like a GUI front-end or replacement for ps.map. ''Implemented outside GSoC as {{{Cmd\|g.gui.psmap}}.''

	* Create a fully functional command line interface with history within the GUI (see [http://trac.osgeo.org/grass/ticket/528#comment:6 suggestion]) ['''update: now mostly complete''']		* Create a fully functional command line interface with history within the GUI (see [http://trac.osgeo.org/grass/ticket/528#comment:6 suggestion]) ['''update: now mostly complete''']

	* Develop a GUI module in wxPython for creating animations from multiple maps and saving animation outputs to animated GIF, MOV, or MPEG files.		* Develop a GUI module in wxPython for creating animations from multiple maps and saving animation outputs to animated GIF, MOV, or MPEG files. ''Implemented outside GSoC as {{{Cmd\|g.gui.animation}}.''

	====Kriging GUI====		====Kriging GUI====

⚠️Landa: /* Accepted Ideas */

2011-03-13T12:48:12Z

Accepted Ideas

← Older revision		Revision as of 12:48, 13 March 2011
Line 164:		Line 164:
	: ''Develop a plug-in for the ossimPlanet application for interface with other Open Source G.I.S software such as Grass and Qgis. This will allow export of elevation data from grass to OssimPlanet and add the ability to load Grass data (both raster and vector) in Ossim. The end result will be to synchronize the grass maps canvas extent with the Ossimplanet scene.''		: ''Develop a plug-in for the ossimPlanet application for interface with other Open Source G.I.S software such as Grass and Qgis. This will allow export of elevation data from grass to OssimPlanet and add the ability to load Grass data (both raster and vector) in Ossim. The end result will be to synchronize the grass maps canvas extent with the Ossimplanet scene.''

			{{GSoC}}

	~~[[Category:Development]]~~
	~~[[Category:Community]]~~
	~~[[Category:~~GSoC]]

⚠️HamishBowman: /* Accepted Ideas */

2010-03-02T07:20:19Z

Accepted Ideas

← Older revision		Revision as of 07:20, 2 March 2010
Line 151:		Line 151:

	== Accepted Ideas ==		== Accepted Ideas ==

			See: http://socghop.appspot.com/gsoc/org/home/google/gsoc2009/osgeo


	* <u>''Network Analysis''</u> by Daniel Bundala		* <u>''Network Analysis''</u> by Daniel Bundala
Line 161:		Line 164:
	: ''Develop a plug-in for the ossimPlanet application for interface with other Open Source G.I.S software such as Grass and Qgis. This will allow export of elevation data from grass to OssimPlanet and add the ability to load Grass data (both raster and vector) in Ossim. The end result will be to synchronize the grass maps canvas extent with the Ossimplanet scene.''		: ''Develop a plug-in for the ossimPlanet application for interface with other Open Source G.I.S software such as Grass and Qgis. This will allow export of elevation data from grass to OssimPlanet and add the ability to load Grass data (both raster and vector) in Ossim. The end result will be to synchronize the grass maps canvas extent with the Ossimplanet scene.''


	~~See: http://socghop.appspot.com/gsoc/org/home/google/gsoc2009/osgeo~~

⚠️HamishBowman: /* Vector */ chosen

2010-03-02T07:18:30Z

Vector: chosen

← Older revision		Revision as of 07:18, 2 March 2010
Line 119:		Line 119:

	* Further development of network analysis, modules for calculating new indicators such as degree, betweenness, etc, a v.net.distance module (see [http://trac.osgeo.org/grass/ticket/521 ticket 521], integration of time tables (train, public transport) into routing, etc.		* Further development of network analysis, modules for calculating new indicators such as degree, betweenness, etc, a v.net.distance module (see [http://trac.osgeo.org/grass/ticket/521 ticket 521], integration of time tables (train, public transport) into routing, etc.
			: '''[update: chosen as GSoC 2009 project]'''

	* Update and enhance vector querying to give full query capabilities to GRASS vectors. See vector querying section of [http://grass.osgeo.org/wiki/GRASS_6.4_Feature_Plan GRASS 6.4 Feature Plan].		* Update and enhance vector querying to give full query capabilities to GRASS vectors. See vector querying section of [http://grass.osgeo.org/wiki/GRASS_6.4_Feature_Plan GRASS 6.4 Feature Plan].

⚠️HamishBowman: /* Accepted Ideas */ update URL, last year's proj

2010-03-02T07:17:09Z

Accepted Ideas: update URL, last year's proj

← Older revision		Revision as of 07:17, 2 March 2010
Line 151:		Line 151:
	== Accepted Ideas ==		== Accepted Ideas ==

	* See: http://~~code~~.~~google~~.com/~~soc~~/~~2009~~/osgeo~~/about.html~~		* <u>''Network Analysis''</u> by Daniel Bundala
			: ''The goal of this project is to further develop vector network analysis in GRASS. This would involve computation of many centrality measures(degree, closeness, betweeness, eigenvalue…), requested v.net.distance module, time tables integrated into routing, various algorithms such max flows, min cuts, weakly and strongly connected components, minimum spanning trees, all pairs shortest paths, k-connectivity, articulation points, bridges, etc.''

			* <u>''v.krige''</u> by Anne Ghisla
			: ''As GRASS presently lacks kriging capability, it is performed via an add-on, v.autokrige, that delegates analysis to R (package automap). This module is written in bash and has the classical autogenerated GUI. The project aims to rewrite the module in Python, creating a new GUI in wxPython that allows the user to refine parameters. I therefore plan to examinate present v.autokrige code and port it into Python, possibly improving it at the same time, and add a wxPython GUI.''

			* <u>''OssimPlanet integration in Grass and Qgis''</u> by Massimo Di Stefano (Shared with OSSIM and QGIS)
			: ''Develop a plug-in for the ossimPlanet application for interface with other Open Source G.I.S software such as Grass and Qgis. This will allow export of elevation data from grass to OssimPlanet and add the ability to load Grass data (both raster and vector) in Ossim. The end result will be to synchronize the grass maps canvas extent with the Ossimplanet scene.''


			See: http://socghop.appspot.com/gsoc/org/home/google/gsoc2009/osgeo


	[[Category:Development]]		[[Category:Development]]
	[[Category:Community]]		[[Category:Community]]
	[[Category:GSoC]]		[[Category:GSoC]]

⚠️HamishBowman: /* Kriging GUI */

2010-03-02T07:09:15Z

Kriging GUI

← Older revision		Revision as of 07:09, 2 March 2010
Line 75:		Line 75:
	====Kriging GUI====		====Kriging GUI====

	'''Note: has been implemented as {{cmd\|v.krige\|version=70}}'''		'''Note: has been implemented as {{cmd\|v.krige\|version=70}} (GSoC 2009)'''

	Currently GRASS has no native support for Kriging. Kriging is done either with the R package or with the GStat package. Both are command driven and thus a GUI could be created to control the program. R could be maybe called directly or via a script to do the variograms etc.		Currently GRASS has no native support for Kriging. Kriging is done either with the R package or with the GStat package. Both are command driven and thus a GUI could be created to control the program. R could be maybe called directly or via a script to do the variograms etc.

⚠️HamishBowman: /* wxGUI */

2010-03-02T07:07:58Z

wxGUI

← Older revision		Revision as of 07:07, 2 March 2010
Line 61:		Line 61:
	</center>		</center>

	* Implement new [[wxGUI#GEM integration\|extension manager]] which downloads from GRASS Addons SVN (Unix based systems) or from precompiled Windows binaries ([http://trac.osgeo.org/osgeo4w/ OSGeo4W]?). See the [http://cran.at.r-project.org/web/packages/ R packages manager] and Markus's new {{cmd\|g.extension\|version=65}} module in GRASS 6.5+. [~~updatE~~: now partly complete]		* Implement new [[wxGUI#GEM integration\|extension manager]] which downloads from GRASS Addons SVN (Unix based systems) or from precompiled Windows binaries ([http://trac.osgeo.org/osgeo4w/ OSGeo4W]?). See the [http://cran.at.r-project.org/web/packages/ R packages manager] and Markus's new {{cmd\|g.extension\|version=65}} module in GRASS 6.5+. ['''update: now partly complete''']

	* Continue [[wxNviz]] development for enhanced 3-4D visualization and analysis.		* Continue [[wxNviz]] development for enhanced 3-4D visualization and analysis.
Line 69:		Line 69:
	* Develop a [[WxPython-based_GUI_for_GRASS#Cartography_tools\|graphical cartographic module]] - something like a GUI front-end or replacement for ps.map		* Develop a [[WxPython-based_GUI_for_GRASS#Cartography_tools\|graphical cartographic module]] - something like a GUI front-end or replacement for ps.map

	* Create a fully functional command line interface with history within the GUI (see [http://trac.osgeo.org/grass/ticket/528#comment:6 suggestion]) [update: now mostly complete]		* Create a fully functional command line interface with history within the GUI (see [http://trac.osgeo.org/grass/ticket/528#comment:6 suggestion]) ['''update: now mostly complete''']

	* Develop a GUI module in wxPython for creating animations from multiple maps and saving animation outputs to animated GIF, MOV, or MPEG files.		* Develop a GUI module in wxPython for creating animations from multiple maps and saving animation outputs to animated GIF, MOV, or MPEG files.
Line 75:		Line 75:
	====Kriging GUI====		====Kriging GUI====

	'''Note: has been implemented as {{cmd\|v.krige\|version=70}}'''		'''Note: has been implemented as {{cmd\|v.krige\|version=70}}'''

	Currently GRASS has no native support for Kriging. Kriging is done either with the R package or with the GStat package. Both are command driven and thus a GUI could be created to control the program. R could be maybe called directly or via a script to do the variograms etc.		Currently GRASS has no native support for Kriging. Kriging is done either with the R package or with the GStat package. Both are command driven and thus a GUI could be created to control the program. R could be maybe called directly or via a script to do the variograms etc.