GRASS GSoC 2012 High level map interaction - Revision history

⚠️Landa: Landa moved page GRASS SoC 2012 High level map interaction to GRASS GSoC 2012 High level map interaction

2013-05-27T21:22:29Z

← Older revision	Revision as of 21:22, 27 May 2013
(No difference)

2013-05-27T21:21:47Z

← Older revision		Revision as of 21:21, 27 May 2013
(No difference)

2012-12-08T13:37:16Z

Download

← Older revision		Revision as of 13:37, 8 December 2012
Line 1,450:		Line 1,450:
	Source code:		Source code:
	* <strike>git clone https://code.google.com/p/pygrass/</strike>		* <strike>git clone https://code.google.com/p/pygrass/</strike>
	* <strike>[http://code.google.com/p/pygrass/downloads/list download it] (will be integrated in GRASS 7)</strike> - Integrated as of Nov. 2012.		* <strike>[http://code.google.com/p/pygrass/downloads/list download it] (will be integrated in GRASS 7)</strike> - [http://grass.osgeo.org/programming7/namespacepython_1_1pygrass.html Integrated] as of Nov. 2012.

2012-12-08T13:36:27Z

pyGRASS is now part of GRASS 7

← Older revision		Revision as of 13:36, 8 December 2012
Line 1,449:		Line 1,449:

	Source code:		Source code:
	* git clone https://code.google.com/p/pygrass/		* <strike>git clone https://code.google.com/p/pygrass/</strike>
	* [http://code.google.com/p/pygrass/downloads/list download it] (will be integrated in GRASS 7)		* <strike>[http://code.google.com/p/pygrass/downloads/list download it] (will be integrated in GRASS 7)</strike> - Integrated as of Nov. 2012.

2012-10-08T15:44:28Z

+Download

← Older revision		Revision as of 15:44, 8 October 2012
Line 1,445:		Line 1,445:
	{{Python}}		{{Python}}
	{{GSoC}}		{{GSoC}}

			== Download ==

			Source code:
			* git clone https://code.google.com/p/pygrass/
			* [http://code.google.com/p/pygrass/downloads/list download it] (will be integrated in GRASS 7)

2012-09-16T12:11:18Z

add current link to pyGRASS

← Older revision		Revision as of 12:11, 16 September 2012
Line 14:		Line 14:
	= Proposal for a high level maps interaction =		= Proposal for a high level maps interaction =

	The idea is: extend the python GRASS API to make it more pythonic :-)		The idea is: extend the python GRASS API to make it more pythonic<ref>http://www.ing.unitn.it/~zambelli/projects/pygrass</ref> :-)

	As you can see in the subsequent tests, a lot of functionality are redundant, similarly with `numpy` library<ref>http://numpy.scipy.org/</ref> I think that could be a good idea binding all the ~~grass~~ functions and add some of them as methods of the class.		As you can see in the subsequent tests, a lot of functionality are redundant, similarly with `numpy` library<ref>http://numpy.scipy.org/</ref> I think that could be a good idea binding all the GRASS functions and add some of them as methods of the class.

	For example you can use both:		For example you can use both:

2012-08-17T21:28:34Z

Report11 - 2012-08-17

2012-08-17T21:26:52Z

Project plan

← Older revision		Revision as of 21:26, 17 August 2012
Line 435:		Line 435:
	\|August 10 \|\| Add support for vector attributes \|\| {{done}}		\|August 10 \|\| Add support for vector attributes \|\| {{done}}
	\|-		\|-
	\|'''August 13''' \|\| Suggested 'pencils down' date. Take a week to scrub code, write tests, improve documentation, etc. \|\| ~~missing~~		\|'''August 13''' \|\| Suggested 'pencils down' date. Take a week to scrub code, write tests, improve documentation, etc. \|\| {{done}}
	\|-		\|-
	\|August 17 \|\| ~~Implement~~ Vector ~~class~~ \|\| ~~missing~~		\|August 17 \|\| Add support to the Vector head structure \|\| {{done}}
	\|-		\|-
	\|'''August 20''' \|\| Final evaluation		\|'''August 20''' \|\| Final evaluation

2012-08-17T21:24:58Z

Report12 - 2012-08-17

← Older revision		Revision as of 21:24, 17 August 2012
Line 1,416:		Line 1,416:

	I will add the write mode to the Vector objects.		I will add the write mode to the Vector objects.

			=== Did I meet with any stumbling blocks? ===

			None

			== Report11 - 2012-08-17 ==

			=== What did I do this week? ===

			* Re-organize the code structure;
			* Add more documentation for each class, and when possible add docstring http://www.ing.unitn.it/~zambelli/projects/pygrass/;
			* Add README, AUTHOR, NEWS files to the project root;
			* Add the setup.py file to the project;
			* Split the Vector class into Vector (without topology) and in VectTopo (with the topology support);
			* Add vector head information.

			=== What will I be working on next week? ===

			Going on cleaning and fixing the code.

	=== Did I meet with any stumbling blocks? ===		=== Did I meet with any stumbling blocks? ===

2012-08-10T22:20:23Z

What did I do this week?

← Older revision		Revision as of 22:20, 10 August 2012
Line 1,409:		Line 1,409:
	* move the documentation from ReadTheDocs to: http://www.ing.unitn.it/~zambelli/projects/pygrass in this way I'm able to use the sphinx automodule to document the API.		* move the documentation from ReadTheDocs to: http://www.ing.unitn.it/~zambelli/projects/pygrass in this way I'm able to use the sphinx automodule to document the API.
	* Add more examples and documentation on vector geometry features: http://www.ing.unitn.it/~zambelli/projects/pygrass/vector.html		* Add more examples and documentation on vector geometry features: http://www.ing.unitn.it/~zambelli/projects/pygrass/vector.html
	* Add a basic support for the vector attributes:		* Add a basic support for the vector attributes: http://www.ing.unitn.it/~zambelli/projects/pygrass/attributes.html
	http://www.ing.unitn.it/~zambelli/projects/pygrass/attributes.html

	To run the above examples you need to use the North Carolina mapset, copy and build the topology, and copy the table attributes from dbf to sqlite and/or postgresql.		To run the above examples you need to use the North Carolina mapset, copy and build the topology, and copy the table attributes from dbf to sqlite and/or postgresql.


	=== What will I be working on next week? ===		=== What will I be working on next week? ===