GRASS-Wiki - User contributions [en]

Documentation and Education Working Group

2023-10-12T17:23:29Z

⚠️Helena: /* Members */

Documentation and education working group is established to coordinate the development of documentation and education materials to meet the needs of a wide range of GRASS users.

== Scope ==
* coordinate development of documentation and education materials
* coordinate development of sample datasets and localized datasets
* decide on best formats and place for documentation, tutorials
* develop onboarding materials for contributors of documentation and education materials

== Members ==
Let us know who you are and what are your interests and topics you want to discuss and develop as part of this group.

; [https://wiki.osgeo.org/wiki/User:Helena Helena Mitasova] (working group coordinator)
: Professor at North Carolina State University
: Interested in wiki pages cleanup, manual pages updates, integration of GRASS in courses, localized data sets

; [https://wiki.osgeo.org/wiki/Anna_Petrasova Anna Petrasova]
: Researcher, educator and software developer at North Carolina State University
: Topics of interest include developing tutorials and workshops in Jupyter Notebooks, onboarding materials

; Eric Patton
:

; Florian Betz
:

; Hernán De Angelis
:

; Micha Silver
:

; Titus Kiprutto
:

; Paulo van Breugel
:

; Brendan Harmon
:

; Giuseppe Amatulli
:

; Michael Barton
:

; Massimo Di Stefano
:

; Carlos Grohmann
:

To be added to this working group, please contact the group coordinator.

== Communication Channels ==
* [https://lists.osgeo.org/mailman/listinfo/grass-user grass-user] and [https://lists.osgeo.org/mailman/listinfo/grass-dev grass-dev] mailing lists
* [https://github.com/OSGeo/grass OSGeo/grass GitHub issues and pull requests] and [https://github.com/orgs/OSGeo/projects/3 GitHub project]
* [https://app.gitter.im/#/room/#grassgis_documentation:gitter.im grassgis/documentation gitter room]

[[Category:Community]]
[[Category:Working_Groups]]

GRASS Community Meeting Prague 2023

2023-04-01T23:10:10Z

⚠️Helena: /* In person */

{{toc|right}}
The GRASS GIS team is organizing the ''GRASS GIS Community Meeting with contributors, power users and developers'' from '''June 2 to June 6, 2023''' to celebrate GRASS GIS '''40th birthday'''.

<gallery mode="slideshow">
Image:grass-sprint-prague.jpg|Prague 2013
Image:Grass_sprint2018_bonn_fotowall.jpg|Bonn 2018
</gallery>

== Purpose ==

GRASS GIS Community Meeting is a great occasion for folks to support the development by actively contributing to the source code, documentation (manuals, wiki, tutorials), translations, website or likewise. The '''community''' meeting is also a get-together where supporters, contributors, power users and developers make decisions and tackle larger problems related to the project, discuss and collaboratively resolve bugs, plan the direction for the project and work on new features. We welcome people committed to improving the GRASS GIS project and the interfaces to QGIS, GDAL, PostGIS, R statistics, OGC Services and willing to '''celebrate with us the 40th GRASS GIS birthday!!'''

For the detailed agenda, see below.

== Sponsors ==

We welcome '''financial contributions''' to support the meeting and we are looking for sponsors to cover costs such as meals or to help reducing travelling and accommodation expenses for GRASS developers with far arrival. If you are interested in sponsoring the GRASS Community Meeting, please read about

:::'''sponsoring the GRASS GIS project''' at '''[https://grass.osgeo.org/contribute/sponsoring/ https://grass.osgeo.org/contribute/sponsoring/]'''

Note that it is also possible to buy a round of beers for the developers with a quick click using the Open Collective "Contribute Money" button https://opencollective.com/osgeo/projects/grass

Any surplus at the end of the event will be turned over to the GRASS GIS project.

This GRASS Community Meeting is a great occasion for you to support the development of GRASS. With your contribution you'll enable more developers to meet. Community meetings are important opportunities for developers to discuss, fix bugs, plan the direction for the project and work on new features. Please see below for the detailed agenda. The developers and contributors are donating their valuable time, so it would be great if in-kind funding can be made available from within the community to cover out-of-pocket expenses. All of the work that takes place at the community meeting will be directly contributed back into the GRASS project to the benefit of everyone who uses it.

=== Thanks to our sponsors ===

We are grateful for the support which we have received to organize this GRASS Community Meeting:

TBD

== Timing ==

'''When''': June 2-6, 2023

Of course you are invited to join or leave the meeting whenever you want.

== Venue ==

[[Image:logo_cvut.jpg|130px|left]]
Department of Geomatics 
[https://www.fsv.cvut.cz/?lang=en Faculty of Civil Engineering] 
[https://www.cvut.cz/en Czech Technical University in Prague], {{wikipedia|Czech Republic}} 
Thákurova 7/2077, Prague 
Room B868 
[https://en.mapy.cz/s/debazefuse Map] 

Prague has an international [http://www.prg.aero/en/ airport] and is also reachable by train, bus or car.

== Accommodation and Costs ==

Participants should plan for the following costs:

* The participation is free of charge
* Travel to Prague, variable depending on where you come from
* Accommodation and meals (with the donated sponsorship money we will try to cover some expenses of the participants)
'''Please note''': The currency in Czech Republic is {{wikipedia|Czech crown}} (CZK, koruna, Kč). 100 Czech crowns are about 4 Euros (see [https://www.cnb.cz/cs/financni-trhy/devizovy-trh/kurzy-devizoveho-trhu/kurzy-devizoveho-trhu/ current rates]).

Please let us know your time of arrival and departure, so we can book accommodations and organize the logistics.

Financial support: (partial) travel grants can be payed upon request thanks to our sponsors!

== Agenda - What we plan to do ==

'''Note:''' The program is generally open for your ideas. Please write an email to the [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developer list] to discuss your contribution.

During the meeting we will work on GRASS GIS on these tasks (please add more!):

* We will update and revise the [https://github.com/qgis/QGIS/tree/master/python/plugins/grassprovider GRASS GIS Integration with QGIS] to simplify maintenance.
* Furthermore, we will migrate the compilation technology to CMake to significantly improve the Windows builds including PDAL support and become binary compatible with OSGeo4W.
* The extensive GRASS documentation will be converted from HTML to Markdown to facilitate future collaboration.
* Pictures, examples and workflows will be added to the documentation where they are still missing.
* Software maintenance processes are automated and documented to reduce the burden on maintainers and thus improve the sustainability of the project.

This means that there are tasks from both the programming and documentation areas to appeal to a wide range of interested parties.

Further details about the action items you '''find [[Talk:GRASS Community Meeting Prague 2023|here]]''' and below. Topics cover non-technical, semi-technical, and technical issues.

=== Timeline ===

Will be specified later.

==== Friday, 2 June ====

==== Saturday, 3 June ====

==== Sunday, 4 June ====

==== Monday, 5 June ====

==== Tuesday, 6 June ====

== Participation ==

We are planning for an attendance of 20 people (i.e., coding places) but of course you are welcome to join us and bring new ideas with you: we'll make more places available. Please add your name here or contact [[User:Landa|Martin Landa]] <tt><landa.martin at gmail.com></tt>:

=== In person ===

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;"
!width=50px|'''Number'''
!width=130px|'''Participant '''
!width=100px|'''Country'''
!width=100px|'''Arrival'''
!width=100px|'''Departure'''
!'''Topics'''
!width=75px|'''T-Shirt'''
!'''Notes'''
|-
|1
|[[User:Landa|Martin Landa]]
| Czech Republic
| June 2
| June 6
|
| XL
|
|-
|2
| Micha Silver
| Israel
| June 2
| June 6
| Addon to derive soil moisture from Sentinel 2
| XXL
|
|-
|3
|[https://www.osgeo.org/member/kudrnovsky/ Helmut Kudrnovsky]
| Austria
| June 2
| June 4
|
| L
|
|-
|4
|[[User:Neteler|Markus Neteler]]
| Germany
| June 2
| June 6 (12:43)
|
| L
|
|-
|5
|[[User:pesekon2|Ondřej Pešek]]
| Czech Republic
| June 2
| June 6
|
| M
|
|-
|6
| [[User:helena|Helena Mitasova]]
| United States
| June 2
| June 6
|
| S
|
|-
|}

=== Via chat or hangout ===

Join our [https://app.gitter.im/#/room/#grassgis_community:gitter.im Gitter chatroom]

TBD: Google Meet / Zoom / ???

==== Timing of hangout meetings ====

TBD

=== Collaborative document scratching ===

TBD

== Individual Preparation ==

* Bring your own computer
* Bring {{wikipedia|AC adapter|power connector adapter}} if needed (Czech Republic: 230V, 50Hz, {{wikipedia|File:Euro-Flachstecker_2.jpg|Type C Europlugs}} are common and also {{wikipedia|File:French_plug_and_socket.jpg|Type E}})
* Install subversion and the compiler tools, and come with a working GRASS development environment if possible.

== Broadcast & Video ==

During the event :)

== Photos ==

Also during the event :)

== FAQ ==

* '''How was it last time?'''
** Very nice, see [[GRASS_GIS at OSGeo Virtual Community Sprint 2020]]!
* ''Is the GRASS Community Meeting just a coding event?''
** It is mainly a coding and documentation event. It is a working session for people who are already participants in the GRASS project and/or are committed to improving the GRASS project.
** On demand we can do some presentations of current working GRASS implementation and new upcoming features to spread the idea of Open Source GIS software.
* ''Is the GRASS Community Meeting for developers only?''
** No: anybody can help, with testing, checking out bugs and fixes, documentation and more.
* ''Where can I get help and more information about the community meeting?''
** Contact [[User:Landa|Martin Landa]] <tt><landa.martin at gmail.com></tt>

== Press Release ==

TBD: After the event :-)

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2023]]

GRASS GIS Community Sprint Bonn 2018

2018-03-19T12:45:37Z

⚠️Helena: /* Via IRC chat */

{{toc|right}}

The '''GRASS GIS community''' will join the general '''OSGeo Code Sprint''' at [http://www.basecamp-bonn.com/ BaseCamp in Bonn], following the annual FOSSGIS conference (German Speaking OSGeo Local Chapter conference in Bonn, Germany)

<center>
[[File:GRASS_GIS_Code_Sprint_2018.png|320px]]
</center>

== Timing, Venue ==

OSGeo Code Sprint: '''March 18 - 25, 2018 at [http://www.basecamp-bonn.com/ BaseCamp, Bonn], Germany'''.

Location: [http://www.openstreetmap.org/way/44335958#map=18/50.70763/7.12316| OpenStreetMap]

== Sponsors ==

Please check more info on the Bonn Code Sprint 2018 [https://wiki.osgeo.org/wiki/OSGeo_Code_Sprint_2018 here].

We also welcome direct '''financial contributions''' to help reducing travelling and accommodation expenses for GRASS developers with far arrival If you are interested to sponsor the GRASS Community Sprint, please read about

:::'''sponsoring the GRASS project''' at '''[http://grass.osgeo.org/donations http://grass.osgeo.org/donations]'''

Note that it is also possible to buy a round of beer for the developers with a quick click using the PayPal "Buy [pizza/beer/...] Now" button [[Image:Btn_donate_SM.gif|center|link=http://grass.osgeo.org/donations/]]

For any questions, please contact [[User:Neteler|Markus Neteler]] <tt><neteler at osgeo.org></tt>. Any surplus at the end of the event will be turned over to the GRASS GIS project.

This GRASS GIS Community Sprint is a great occasion for you to support the development of GRASS. With your contribution you'll enable more developers to meet. The community sprint is an important opportunity for the GRASS developers to discuss and collaboratively resolve bugs, plan the direction for the project and work on new features. Please see below for the more detailed agenda. The developers and contributors are donating their valuable time, so it would be great if in-kind funding can be made available from within the community to cover out-of-pocket expenses. All of the work that takes place at the community sprint will be directly contributed back into the GRASS project to the benefit of everyone who uses it.
This Bonn event is especially interesting since '''important OSGeo projects come together'''!

== Agenda - What we plan to do ==

=== New GRASS GIS startup style ===

* To simplify GRASS GIS startup,
** first the full GUI should be shown and immediately the location dialog popped up _inside_ GRASS GIS
** default SRS: long-lat 4326
* Rationale: don't continue to be different from the rest of the world when not needed
** New solution needs to cover following scenarios:
*** GISDBASE does not exist;
*** GISDBASE exists, but there is no location with EPSG:4326;
*** Selected location/mapset must be propagated down to background CLI process too.

=== Move to Git ===

* Choose among different options: OSGeo Git, Github, GitLab
* Participants are invited to study Git in advance :-)
* Consider moving only GRASS 8 (or 7.7) without history and push history into a separate repository. Rationale – repository checkout will have to contain all branches thus blowing-up checkout size. There is an option to use several git repos "chained" together to have access to full history without having it to live in a single repository. Here's an example: https://archive.org/details/git-history-of-linux https://stackoverflow.com/questions/161928/what-are-git-info-grafts-for

=== New website ===

* <del>Choose among different options</del>: '''Wordpress''' <del>,Sphinx</del>, ... ? A new Wordpress installation is requested in SAC ([https://trac.osgeo.org/osgeo/ticket/2131 ticket]). {{done}}
** https://staging.grass.osgeo.org/ (login with OSGeo-ID)

=== Python interface for external usage ===

* complete the new "grass-session" pip package (https://github.com/zarch/grass-session)
* change packaging to for better support of site-package

=== Integration with QGIS Processing ===

After some intensive discussions the decision of the QGIS devs is to continue with the "Processing" support (see [https://lists.osgeo.org/pipermail/grass-dev/2018-February/087557.html summary email by P Cavallini])

Action item: update the GRASS GIS processing provider. A boilerplate could be the new [https://github.com/alexbruy/processing-saga SAGA processing provider].

=== Port wxGUI to wxPython 4 ===

* Finish porting wxGUI code to the new wxPython 4
* It also includes porting code to Python 3

=== Finish the full Python 3 support ===

* Includes also wxGUI support for wxPython 4
* ...

== Planned participation ==

For organizational reasons, please '''additionally register''' at: https://wiki.osgeo.org/wiki/OSGeo_Code_Sprint_2018#Participants <<--- important!

=== In person ===

Please add your name here or contact [[User:Lucadelu|Luca Delucchi]] <tt><lucadeluge at gmail com></tt>:

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;"
|width=50px|'''No'''
|width=130px|'''Participant '''
|width=100px|'''Country'''
|width=100px|'''Arrival'''
|width=100px|'''Departure'''
|'''Topic'''
|width=75px|'''T-Shirt'''
|'''Notes'''
|-
|1
|[[User:Neteler|Markus Neteler]]
|Germany
|18.3.
|25.3.
|Migration to git discussion, GRASS GIS 8, new GRASS GIS startup
|M
|
|-
|2
|[[User:Landa|Martin Landa]]
|Czech Republic
|18.3.
|25.3.
|Migration to git discussion, website discussion, GRASS GIS 8
|L
|
|-
|3
|Stefan Blumentrath
|Germany/Norway
|20.03.
|25.03.
|Flexible
|L
|
|-
|4
|[[User:Veroandreo|Veronica Andreo]]
|Argentina/Netherlands
|18.3
|??.??
|TGRASS, Documentation, website discussion
|S
|
|-
|5
|[[User:Lucadelu|Luca Delucchi]]
|Italy
|18.3
|??.??
|Migration to git discussion, TGRASS, testsuite, website discussion
|L
|
|-
|6
|[[User:Mlennert|Moritz Lennert]]
|Belgium
|18.3
|21.3
|Migration to git discussion, website discussion, GRASS 8, new GRASS GIS startup, work on OBIA addons, ...
|M
|
|-
|7
|Markus Metz
|Germany
|18.3.
|22.3.
|Migration to git discussion, website discussion, GRASS 8, new GRASS GIS startup
|M
|
|-
|8
|Ondřej Pešek
|Czech Republic
|18.3.
|25.3.
|Artificial neural networks in GRASS GIS, g.gui.modeler, SOS tools
|M
|
|-
|9
|[[User:Radeknovotny94|Radek Novotný]]
|Czech Republic
|18.3.
|23.3.
|Integration with QGIS Processing
|L
|
|-
|10
|Anika Bettge
|Germany
|20.3.
|20.3.
|Segmentaion and classification
|
|
|-
|11
|Nikos Alexandris
|Germany
|19.3.
|23.3.
| GRASS workflows + distributed file system (i.e. https://github.com/cern-eos/eos), Publishing r.estimap ([[Talk:GRASS_GIS_Community_Sprint_Autumn_2017#Nikos_Alexandris|started in November 2017]]), Tests suggested in https://trac.osgeo.org/grass/ticket/774
|S/M
|
|-
|#
|...
|
|
|
|
|
|
|-
|}

=== Via IRC chat ===

(IRC is a nice archaic chat system, see [[IRC]])

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;"
|width=50px|'''No'''
|width=130px|'''Participant '''
|width=100px|'''Country'''
|'''Note'''
|-
|1
|Yann Chemin
|Sri Lanka
|
|-
|2
|[[User:hellik|Helmut Kudrnovsky]]
|Austria
|
|-
|3
|[[User:Wenzeslaus|Vaclav Petras]]
|USA
|Available for video call on Monday, Mar 19
|-
|4
|[[User:Annakrat|Anna Petrasova]]
|USA
|Available for video call on Monday, Mar 19
|-
|5
|[[User:helena|Helena Mitasova]]
|USA
|Available for video call on Monday, Mar 19
|-
|}

== Individual Preparation ==

* Bring your own computer
* Bring [http://en.wikipedia.org/wiki/Mains_electricity_by_country your power connector adapter] if needed (photo: [https://en.wikipedia.org/wiki/File:Schuko_plug_and_socket.png Germany]). See also http://www.power-plugs-sockets.com/
* Install subversion and the compiler tools, and come with a working GRASS development environment if possible.

== Photos ==

We have to remember to take at least one group photo! :-)

== Reports ==

See [[Talk:GRASS_Community_Sprint_Bonn_2018]]

== FAQ ==

* ''Is the GRASS Community Sprint just a coding event?''
** It is mainly a coding and documentation event. It is a working session for people who are already participants in the GRASS project and/or are committed to improving the GRASS project.
** On demand we can do some presentations of current working GRASS implementation and new upcoming features to spread the idea of Open Source GIS software
* ''Is the GRASS Community Sprint for developers only?''
** No: anybody can help, with testing, checking out bugs and fixes, documentation and more.
* ''Where can I get help and more information about the community sprint?''
** Contact [[User:Lucadelu|Luca Delucchi]] <tt><lucadeluge at gmail com></tt>

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2018]]

GRASS GIS ISPRS Prague meetup 2016

2016-06-28T23:10:26Z

⚠️Helena:

People contributing or interested in contributing to GRASS GIS are welcome to meet during [http://www.isprs2016-prague.com/ ISPRS Congress] held in Prague 12-19th July 2016, Czech Republic. Details will be published later or during the congress.

Contact person: [[User:Landa|Martin Landa]] (landa.martin gmail com)

== People ==

Are you going to ISPRS Congress, or you are just in Prague and willing to meet? Please put your name to the table bellow.

{| class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;"
|-
! No
! Participant
! Arrival
! Departure
! ISPRS participation
! Note
|-
| 1
| Martin Landa
| 12/7
| 19/7
| Yes
| Contact person
|-
| 2
| Helena Mitasova
| 15/7
| 19/7
| yes
|
|-}

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2016]]

GRASS SoC Ideas 2013

2013-04-27T03:47:32Z

⚠️Helena: /* Symbology / Cartography */

<center>
[[Image:grasslogo_vector_small.png|link=http://grass.osgeo.org]] @ [[Image:Gsoc-2013-logo-color.jpg|250px|link=http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2013]] @ [[Image:OSGeo 220pix.png|link=http://www.osgeo.org]]
</center>

__TOC__

== About ==

This is the GRASS page for [http://wiki.osgeo.org/index.php/Google_Summer_of_Code_2013 Google Summer of Code 2013] (see the [http://www.google-melange.com/document/show/gsoc_program/google/gsoc2013/help_page#2._What_is_the_program_timeline timeline]). Here we will list project ideas and and other information related to the GRASS GSoC projects.

== Ideas ==

* '''Also review ideas from''' [[GRASS SoC Ideas 2009#Ideas|2009]], [[GRASS SoC Ideas 2010#Ideas|2010]], [[GRASS SoC Ideas 2011#Ideas|2011]] and [[GRASS SoC Ideas 2012#Ideas|2012]] which are still open.

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

=== General ===

* Implement a buffered binary balanced search tree using external memory: Rationale: some modules and library functions use a binary search tree, which can lead to out-of-memory errors for large datasets. A buffered binary balanced search tree using external memory would solve this problem and enhance the capability of GRASS to work with large datasets on limited hardware resources.

* [[Parallel_GRASS_jobs|Parallelize]] CPU-heavy modules using [[OpenMP]], OpenCL ([[GPU]]), and/or pthreads.

* If you're really stuck for ideas, [https://trac.osgeo.org/grass/query?status=assigned&status=new&status=reopened&group=component&order=priority&col=id&col=summary&col=status&col=type&col=owner&col=priority&col=milestone&type=enhancement hunt around the wish list in the trac system].

* Clean-room write a LGPL or BSD/MIT-X GRASS data format plugin for GDAL/OGR. An option should exist to support both GRASS 6 and 7 versions of the format.

* Improve and fix bugs in the QGIS GRASS Toolbox. Generally make it smoother to pass projects and workflows between the two.

=== Symbology / Cartography ===

* Allow display of a vector legend in the map display (equivalent to current {{cmd|d.legend}} implementation for rasters)

* Expand [[IconSymbols|symbology]] and re-classify groups
:: ''note that SoC only accepts coding projects, not graphics design or documentation projects.''
:* Add svg/eps support to a d.* module and {{Cmd|ps.map}} would be quite helpful. See the {{Cmd|d.graph}} help page and {{Cmd|ps.map}}'s "eps" and "vpoints" instructions. The first step would be to write a stand-alone tool in C to create d.graph commands; the second step would be to add as a new option in ''d.graph''; a third step would be to backport this to GRASS 6's graphics API. See also {{trac|733}} wish re. implementing Bézier curves in the display drivers.
:: Willing to co-mentor: Hamish

* Rework the complete set of thematic cartography tools such as {{Cmd|d.vect.thematic}} and {{Cmd|d.thematic.area}} and the related classification routines. This would comprise:
** Revising the classification algorithms already implemented and possibly adding new ones (kmeans, Jenks)
** Replace the existing d.vect.thematic script with a C-based module (in the likes of d.thematic.area) combing thematic cartography of points, lines and areas
** Include representation of legend of the thematic map
** Use [http://colorbrewer2.org/ colorbrewer] rules to make classifications pretty
** Implement one or several specific GUI interface(s) to this new module
:: ''note that since d.vect.thematic was written {{Cmd|d.vect}} has added DB-column based sizing, rotation, and other tasks making parts of d.vect.thematic ready for much simplification.''
:* Generalized ASCII table input for {{Cmd|d.legend}} (see {{trac|89}} wish)
:* Histogram sidebar support for {{Cmd|d.legend}} and {{Cmd|ps.map}} (see {{trac|1049}} wish)
:: Willing to co-mentor d.legend bits: Hamish
: Willing to co-mentor components of symbology/cartography project: Helena

=== Imagery ===

* Based on the work on [[GRASS_GSoC_2012_Image_Segmentation|segmentation]] in GSoC 2012 develop routines for object-based (or region-based) image classification. This probably entails:
** Characterizing segments. This includes producing statistics such as mean, median, variance of the segmented data within each delineated segment (customized interface to r.statistics2).
** Classifying segments based on the characteristics and (possibly) training areas
** Interface with other modules in a consistent workflow (i.cluster, r.fuzzy, etc)

* Implement hierarchical classification tools (e.g. being able to create a large class "forest" with subclasses of different types of forests). Hierarchical classification is already used internally by i.gensigset/i.smap. Hierarchical segmentation can currently be done by using the output of a previous run of i.segment as input for the next run of i.segment with increased threshold.

* Interface with the [http://www.orfeo-toolbox.org/otb/ Orfeo toolbox (OTB)], which is an open source, [http://www.itk.org ITK]-based, C++ library of (spatial) image processing library. OTB implements a very wide set of interesting features for anybody working with raster data - in particular satellite imagery: radiometric corrections, orthorectification, filtering, feature extraction, image segmentation, classification, change detection, etc.

=== Vector ===

# Line intersection: implement an efficient algorithm based on literature review, focusing on the [http://en.wikipedia.org/wiki/Bentley-Ottmann_algorithm Bentley-Ottmann algorithm] and its derivates. The best or best two should be implemented. Coupled to the problem of calculating line intersections is the problem of calculating segment intersections, currently implemented in [http://grass.osgeo.org/programming7/vector_2Vlib_2intersect_8c.html#ab4f5f3d99742378f0f284966f59bafe7 Vect_segment_intersection()] and [http://grass.osgeo.org/programming7/linecros_8c.html#a4fb52c4fc60df4fcae5e676134f08be9 dig_find_intersection()], which could also be replaced with more efficient algorithms.
#* Rationale: the current function Vect_line_intersection() is "home-brew" and rather slow for lines with many segments, whereas the Bentley-Ottmann algorithm can find line intersections in logarithmic time per intersection.
#* Requirements: at least interest in, preferably knowledge of the art of searching and sorting (search trees, priority queues, heaps).
#* Implementation goals: One function to search for intersections between two lines, ignoring self-intersections, and another function to test one single line for self-intersections. The API and output should be compatible with the current Vect_line_intersection() function. Optionally an alternative to Vect_segment_intersection().
# ''Your suggestion here!''

'''Willing to Mentor:''' Markus Metz

=== Temporal GIS Algebra for raster and vector data ===

We (Soeren Gebbert and Thomas Leppelt) would like to develop a temporal GIS algebra for raster and vector data in GRASS7.

Role:
* Mentor: Soeren Gebbert
* GSoC Student: Thomas Leppelt

Implementation goals:

* Spatio-temporal vector algebra module t.vect.mapcalc
** The algebra will be based on vector map operations provided from {{Cmd|v.overlay}} (and, or, xor, not), {{Cmd|v.buffer}} (buff_point, buff_line, buff_area), {{Cmd|v.patch}} (patch), ... , temporal variables (day of year, weekday, datum, time, ...) and temporal topology relations (predecessor, successor, follows, equals, ...)
** The resulting module will be able to process space time vector datasets using expressions like:

<source lang="bash">
# Compute the intersection between the space time vector datasets A and B
# from maps with equal time stamps. The STVDS A is used as temporal reference.
# A new STVDS C will be created with the same time stamps as A.
t.vect.mapcalc inputs=A,B timeref=A output=C expr="C = if(equal(B), and(A,B))"

time |STVDS|STVDS|STVDS
stamp | A | B | C
-------------------------------------
Jan 2001 | a1 | b1 | v.overlay ain=a1 bin=b1 op=and out=c1
Feb 2001 | a2 | |
Mar 2001 | | b2 |
Apr 2001 | a3 | |
May 2001 | a4 | b3 | v.overlay ain=a4 bin=b3 op=and out=c2
Jun 2001 | | b4 |

# Nested operations are supported and temporal neighborhood computation
t.vect.mapcalc input=A,B,C tempref=A output=D \
expr="D = if(successor(B) && predecessor(C), and(A, xor(successor(B), buff_point(predecessor(C), 100)))"

# Date and time can be used in the expression
t.vect.mapcalc input=A,B timeref=A output=C \
expr="C = if(start_year() >= 2001 && start_month() > 6, and(A,B), not(A,B))"
</source>

* Spatio-temporal raster algebra module t.rast.mapcalc
** The algebra will be based on the existing {{Cmd|r.mapcalc}} raster map algebra, temporal variables (day of year, weekday, datum, time, ...) and temporal topology relations (predecessor, successor, follows, equals, ...)
{{GSoC}}
** The resulting module will be able to process space time raster datasets using expressions like:

<source lang="bash">
# Compute the sum between the space time raster datasets A and B
# from maps with equal time stamps. The STRDS A is used as temporal reference.
# A new STRDS C will be created with the same time stamps as A.
t.rast.mapcalc inputs=A,B timeref=A output=C expr="C = if(equal(B), A + B)"

# Spatio-temporal neighborhood computation. STRDS C will have the same time stamps as A.
t.rast.mapcalc input=B timeref=A output=C \
expr="C = if(successor(B) && predecessor(B), (successor(B)[0,0] + B[0,0] + predecessor(B)[0,0])/3.0, B[0,0])"
</source>

* The GRASS GIS temporal framework will be utilized and the pygrass module interface
* PLY will be used for lexical analysis and parser generation
* Temporal algebra will be equivalent for booth modules with about 60 internal variables and functions

GRASS Community Sprint Prague 2013

2013-04-19T03:53:45Z

⚠️Helena: /* In person */

{{toc|right}}
The GRASS GIS [[team]] will organize the '''4th GRASS Developer and Power User Meeting, aka 'GRASS GIS Community Sprint'''' from '''July 12 to July 18, 2013'''. The sprint is following the [http://geoinformatics.fsv.cvut.cz/gwiki/Geoinformatics_FCE_CTU_2013 Geoinformatics conference], 11-12 July 2013, Czech Technical University in {{wikipedia|Prague}}, {{wikipedia|Czech Republic}}.


'''Important dates:'''

* 11 (Thusday) - 12 (Friday) July 2013: [http://geoinformatics.fsv.cvut.cz/gwiki/Geoinformatics_FCE_CTU_2013 Geoinformatics conference]

* '''12 (Friday) - 18 (Thusday) July 2013: GRASS GIS Community Sprint''' @ [http://www.fsv.cvut.cz/ FCE CTU]

== Purpose ==

This fourth edition of the GRASS GIS Community Sprint 2013 is a great occasion for folks to support the development by actively contributing to the source code, manuals or likewise. The '''community''' sprint is a get-together for GRASS project members and supporters and related [http://www.osgeo.org OSGeo] projects to make decisions and tackle larger problems. For this meeting, we welcome people committed to improving the GRASS GIS project and the interfaces to [[QGIS GRASS Cookbook|QGIS]], [[GDAL]], [[PostGIS]], [[R statistics]], [[GRASS and Sextante|Sextante, gvSIG]], OGC Services (esp. [[WPS]]) and more. This includes developers, documenters, bug reporters, translators and others.

For this meeting, we welcome people committed to improving the GRASS GIS and related projects. This includes developers, document writers, wish and bug reporters, translators etc.

== Sponsors ==

We welcome '''financial contributions''' to support the meeting and we are looking for sponsors to cover costs such as meals or to help reducing travelling and accommodation expenses for GRASS developers with far arrival If you are interested to sponsor the GRASS Community Sprint, please read about

:::'''sponsoring the GRASS project at [http://grass.osgeo.org/donations http://grass.osgeo.org/donations]'''

For questions, please contact [[User:Neteler|Markus Neteler]] <tt><neteler at osgeo.org></tt>. Any surplus at the end of the event will be turned over to the GRASS GIS project.

This fourth GRASS Community Sprint is a great occasion for you to support the development of GRASS. With your contribution you'll enable more developers to meet. The community sprint is an important opportunity for the GRASS developers to discuss and collaboratively resolve bugs, plan the direction for the project and work on new features. Please see below for the more detailed agenda. The developers and contributors are donating their valuable time, so it would be great if in-kind funding can be made available from within the community to cover out-of-pocket expenses. All of the work that takes place at the community sprint will be directly contributed back into the GRASS project to the benefit of everyone who uses it.

=== Thanks to our sponsors ===

We are grateful for the support which we have received to organize this GRASS Community Sprint:


== Timing ==

'''When''': 12-18 July, 2013

Of course you are invited to join or leave the community sprint whenever you want.

'''Duration''': tbd

* Friday (12. July) is day of arrival
** First meeting in the afternoon (after the [http://geoinformatics.fsv.cvut.cz/gwiki/Geoinformatics_FCE_CTU_2013 Geoinformatics conference]) to define the agenda
* Saturday to Wednesday
** Full days
* Thursday (18. July) is day of departure
** Probably hacking for people with a flight later in the evening

== Venue ==
[[Image:logo_cvut.jpg|130px|left]]
Department of Mapping and Cartography 
[http://www.fsv.cvut.cz Faculty of Civil Engineering] 
[http://www.cvut.cz Czech Technical University in Prague], {{wikipedia|Czech Republic}} 
[http://geoinformatics.fsv.cvut.cz/gwiki/Room_B367 Room B367] 

'''[http://geoinformatics.fsv.cvut.cz/gwiki/Where_you_can_find_us Location & Transportations]'''

Prague has an international [http://www.prg.aero/en/ airport] and is also reachable by train, bus or car.

== Accommodation and Costs ==

Participants should plan for the following costs:

* The participation is free of charge
* Travel to Prague, variable depending on where you come from
* Accommodation and meals (with the donated sponsorship money we will try to cover some expenses of the participants)
'''Please note''': The currency in Czech Republic is {{wikipedia|Czech crown}} (CZK, koruna, Kč). 100 Czech crowns are about 4 Euros (see [http://www.cnb.cz/en/financial_markets/foreign_exchange_market/exchange_rate_fixing/daily.jsp current rates]).

'''[http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague Accommodation in Prague]'''

:* [http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague#Masarykova_Kolej_Hotel Masarykova Kolej Hotel]
:* [http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague#Hotel_DAP Hotel DAP]
:* [http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague#Hotel_Krystal Hotel Krystal]
:* [http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague#Pension_Hanspaulka Pension Hanspaulka]
:* [http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague#Hotel_Silenzio Hotel Silenzio]
:* [http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague#Student_hostels_.28CTU.29 Student hostels (CTU)]
:* Special offer: ''sleeping for free in the kindergarten'' (30min by city urban mass transportation from the university campus, sleeping bag required, kitchen and WC available, no showers, in working days available only from 8 p.m. to 8 a.m.), contact [[User:Landa|Martin Landa]] for details
:* See also http://www.hotel.cz/praha-6/accommodation/

Please let us know your time of arrival and leaving, so we can book for the accommodations and organize the logistics.

Financial support: (partial) travel grants can be payed upon request thanks to our sponsors!

== Weather and Common Item Prices ==

* In July the weather in Prague is usually warm ([http://www.prague-spot.com/climate 20 or more degrees by day])
* A espresso coffee is about 25 CZK (1 euro), a beer (half of liter) in a common pub is around 30 CZK (1 euro 20 cents), can be more in special pubs. In Prague you can have a full meal (see {{wikipedia|Czech cuisine}} for details) for 100 - 150 CZK (4 - 6 euros), but beware of tourist restaurants, the price can easily rise. It's quite easy to find in Prague also Italian or Chinese restaurants.

== Agenda - What we plan to do ==

'''Note:''' The program is generally open for your ideas. Please write an email to the [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developer list] to discuss your contribution.

Further details about the action items you '''find [[Talk:GRASS Community Sprint Prague 2013|here]]''' and below. Topics cover non-technical, semi-technical, and technical issues.

=== Timeline ===

==== Friday, 12 July ====
* ''(time to be defined)'': Kick-off in the Faculty of Civil Engineering, building B, room 367 (3rd floor, [http://geoinformatics.fsv.cvut.cz/gwiki/Where_you_can_find_us map])
* Participants presentation


==== Saturday, 13 July ====

* 9:00-evening


==== Sunday, 14 July ====

* 9:00-evening


==== Monday, 15 July ====

* 9:00-evening


==== Tuesday, 16 July ====

* 9:00-evening


==== Wednesday, 17 July ====

* 9:00-evening

==== Thursday, 18 July ====

* Last meeting
* Farewell and have a good trip home

== Participation ==

We are planning for an attendance of 20 people (i.e., coding places) but of course you are welcome to join us and bring new ideas with you: we'll make more places available. Please add your name here or contact [[User:Landa|Martin Landa]] <tt><landa.martin at gmail.com></tt>:

=== In person ===

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;"
!width=50px|'''Number'''
!width=130px|'''Participant '''
!width=100px|'''Country'''
!width=100px|'''Arrival'''
!width=100px|'''Departure'''
!'''Topic'''
!width=75px|'''T-Shirt'''
!'''Notes'''
|-
|1
|[[User:Landa|Martin Landa]]
|Czech Republic
| July 12
| July 18
| Toolbox concept, vector engine in GRASS 7, wxGUI, PostGIS Topology support, 3D topology
| L
|
|-
|2
| [[User:Neteler|Markus Neteler]]
| Italy
| July 12
| July 18
| Varia
| M
|
|-
|3
| [[User:Helena|Helena Mitasova]]
| USA
| July 16 pm
| July 18
| Data exchange, metadata, GRASS7 data sets, temporal data
| M
|
|-
|4
| and you ...
|
|
|
|
|
|
|-
|}

=== Via IRC chat or hangout===

: [irc://freenode/grass #grass] on Freenode
: [http://www.google.com/+/learnmore/hangouts/ G+ hangout]
:: (to be investigated; smartphones only? (''not sure, but I don't think so'')
:: do you have to be signed up with a Google+ social media account?
:: is Jitsi on a desktop computer compatible? --''not sure, but Jisti offers its own work-alike free multi-person video chat for XMPP(Jabber compatibles) which is not limited to 10 people: [https://jitsi.org/Projects/JitsiVideobridge VideoBridge]'')

For details, see [[IRC]]

Please add yourself here below (please add also your gmail account for G+ hangout):

* [[User:Landa|Martin Landa]], [http://www.timeanddate.com/worldclock/city.html?n=204 timezone]. Gmail is <landa.martin@> expanded
* ...

'''Timing of hangout meetings:'''

* Date, time: [http://doodle.com/f2qfqixqeqkkmskh doodle-poll]

=== Collaborative document scratching ===

(Power) users from all over the world are kindly invited to assist with testing of new and existing functionality. To collect results and notes, we set up an interactive, collaborative editing tool which works in real-time:

Please check http://titanpad.com/I51nq1SrNc

== Individual Preparation ==

* Bring your own computer
* Bring {{wikipedia|AC adapter|power connector adapter}} if needed (Czech Republic: 230V, 50Hz, {{wikipedia|File:Euro-Flachstecker_2.jpg|Type C Europlugs}} are common and also {{wikipedia|File:French_plug_and_socket.jpg|Type E}})
* Install subversion and the compiler tools, and come with a working GRASS development environment if possible.

== Broadcast & Video ==

During the event :)

== Photos ==

Also during the event :)

== FAQ ==

* '''How was it last time?'''
** Very nice, see [[GRASS Community Sprint Genova 2013]]!
* ''Is the GRASS Community Sprint just a coding event?''
** It is mainly a coding and documentation event. It is a working session for people who are already participants in the GRASS project and/or are committed to improving the GRASS project.
** On demand we can do some presentations of current working GRASS implementation and new upcoming features to spread the idea of Open Source GIS software
* ''Is the GRASS Community Sprint for developers only?''
** No: anybody can help, with testing, checking out bugs and fixes, documentation and more.
* ''Where can I get help and more information about the community sprint?''
** Contact [[User:Landa|Martin Landa]] <tt><landa.martin at gmail.com></tt>

== Press Release ==

''(to be done)''


[[Category: Workshops]]

User:Helena

2013-01-30T14:53:13Z

⚠️Helena:

Associate Professor at North Carolina State University, member of GRASS PSC and OSGeo foundation

http://wiki.osgeo.org/wiki/OSGeo_Advocate#Helena_Mitasova

http://www.meas.ncsu.edu/faculty/mitasova/mitasova.html

Talk:GRASS Community Sprint Prague 2012

2012-06-26T00:20:39Z

⚠️Helena: /* Reports */

== Reports ==

=== [[User:Landa|Martin Landa]] ===

* OSGeo4W GRASS package configuration: added libLAS support (http://liblas.org/osgeo4w.html) - {{rev|51677}} & {{rev|51679}}
* various wxGUI fixes
* implement saving list of executed commands in wxGUI - {{rev|51798}}
* wxGUI about window issues - {{rev|51830}}
* wxGUI vector/raster importer: updated list of formats (db/protocol): 'PostGIS WKT Raster driver', 'CouchDB', 'WFS','GeoRSS'

=== Markus Metz ===

* R-tree made n-dimensional (from 3D) for temporal GIS support - esp. {{rev|51799}}

=== [[User:Neteler|Markus Neteler]] ===

* Fundraising for this Community Sprint (with great help from Arnulf Christl)
* PSC composition discussion
* fix r.lake segfault for seed map ({{rev|51752}}) together with Markus Metz
* backport of wxGUI language selector (.bat file update yet missing for Windows) - together with Luca Delucchi
* Lidar DEM based example added to {{cmd|r.lake}}
* Testing QGIS-Sextante-GRASS integration:
** Location is generated on the fly, excellent
** v.buffer works
** r.terraflow works but result is not shown
** Parameter [http://sextante.googlecode.com/svn/trunk/soft/bindings/qgis-plugin/src/sextante/grass/grass.txt descriptions] are lacking in the internal control files (params/flags are duplicated), reported as http://hub.qgis.org/issues/5645
** GRASS integration should use private, not user's .grassrc6 file, reported as http://hub.qgis.org/issues/5644

=== [[User:Annakrat|Anna Kratochvilova]] ===
* wxGUI/digitizer: add help button to digitizer toolbar ({{rev|51742}})
* wxGUI: fix histogram tool (the one using the d.histogram) ({{rev|51753}})
* wxNviz: revert changes in zexag and improve its behaviour for latlon projections ({{rev|51695}})
* wxGUI: fixes for d.rast.num and d.rast.arrow

=== [[User:MilenaN|Milena Nowotarska]] ===
* WinGRASS bug hunting
* translation

=== [[User:Wenzeslaus|Vaclav Petras]] ===
* wxGUI: separating d.mon-related code ({{rev|51758}}, {{rev|51804}}), d.mon bugfixing ({{rev|51829}}, {{rev|51836}})
* wxGUI: refactoring to get simplified Map Display for d.mon (nothing to commit yet)
* wiki: [[Using QtCreator for GRASS C development]]
* other: {{trac|1663}}, {{trac|1664}}

=== [[User:NikosA|Nikos Alexandris]] ===
* Testing grass_trunk scripts (+ other modules) look at [http://titanpad.com/I51nq1SrNc GRASS Community Sprint Dashboard]
* Brainstorming about a Visual Guide to GRASS-GIS' modules capabilities [http://grass.osgeo.org/wiki/Talk:GRASS_Community_Sprint_Prague_2012#Wishes_for_the_Community_Sprint under wishes]

=== [[User:lucadelu|Luca Delucchi]] ===
* create v.in.geopaparazzi
* translation status in about gui {{rev|51838}} {{rev|51840}} {{rev|51844}} {{rev|51845}}
* several improvements in About GUI (translation status, used language, improvement font's styles)
* Some improvement into r.li.setup not finish yet

=== [[User:Turek|Stepan Turek]] ===
* r.in.wms2 - improved support of WMS 1.3.0 standard and added more examples into manual ({{rev|51700}})
* worked on feature for interactive inserting of coordinates into parameter field
* worked on improvement of mouse events handlers unregistration from map window
* discussed GSoC project with mentors
* studied WxGui code
* thanks to Václav, Anna and Martin for help

=== [[User:Huhabla|Soeren Gebbert]] ===
* Presentation and demonstration of the new temporal GIS framework
* Implementation of scaled time axis for space time voxel cubes [http://trac.osgeo.org/grass/changeset/51779 r51779]
* Discussion and specification of the new Python GRASS API with Pietro Zambelli and other GRASS developer
* Discussion about a better integration of the temporal GIS framework modules in the GRASS GUI with Martin Landa
* Bug hunting [http://trac.osgeo.org/grass/changeset/51714], [http://trac.osgeo.org/grass/changeset/51793] and tests writing for the 3D raster library
* Discussion and specification of the new GRASS [http://grass.osgeo.org/wiki/Toolboxes toolbox] approach
* Moved the ilist functions and struct from vector lib to gis lib [[http://trac.osgeo.org/grass/changeset/51796]

=== [[User:helena|Helena Mitasova]] ===
* discussed adjustments in wxnviz and future work on visual analytics in space-time cube with Anna
* explored potential for collaborations in FOSS4G education and OSGeo research and edu lab with Martin,
* clarified some wxgui zoom-region issues with Martin
* sanbox for NCSU students
* discussed updates for PSC membership with Markus
* reviewed the new website status and evaluated possibilities to move forward
* discussed situation with libLAS and lasTools

== Wishes for the Community Sprint ==

* Visual Guide to GRASS GIS modules: scratch a collection of per-module dedicated||or tutorial/task oriented, simple, minimalistic yet attractive, bullet-proof visual examples
**exemplify what GRASS modules do rather than how they do it, thus different than the manuals -- ''rephrase title?''
***make use of existing grass modules list(s), like (this old) [http://grass.itc.it/gdp/grassmanuals/grass63_module_list.pdf GRASS GIS 6.3 Command list (PDF document)]
***: ''HB: A version for GRASS 6.4 [http://grass.osgeo.org/gdp/grassmanuals/grass64_module_list.pdf is here]. How to advertise it better? The script to make it is in SVN, see tools/module_synopsis.sh''
***visuals should clearly refer to both commands (CLI) and (their) respective menu entry (in GUI)
***ignore modules which cannot be visualised?
**check if (and some-how) task-oriented visual examples could be build out of per-modules examples
**setup specific styling rules (?)
***only one descriptive sentence per module or task
***visuals clearly refer to both commands (CLI) and (their) respective menu entry (in GUI)
***limited caption(s) describing visuals
**end-up with some independent and beautiful TeXy PDF
**visually enrich existing manuals and/or grass-wiki
** or consider Sphinx
**Random examples
***Important concepts in GRASS-GIS' raster processing workflow
[[Image:nc_spm_08_the_computational_region_concept_800px_height.png|400px|thumb|center|Understanding the concept of computational region -- (1) North Carolina DEM 500m (elev_state_500m), (2) basins derived from the DEM by r.watershed (threshhold=50K), (3) a selected basin within which grass raster modules will operate]]
***combination of r.slope.aspect, r.buffer2 (grass70) and r.blend
[[Image:Nc_spm_09_r.blend_of_aspect_and_streams_derived_buffered.png|400px|thumb|center|r.blend -- combined streams, buffered streams and aspect]]
* Review of the python + ctypes example scripts.
: The examples given in the code for {{src|doc/python/raster_example_ctypes.py|version=trunk}}, vector_example_ctypes.py and on the [[Python Ctypes Examples|Ctypes wiki page]] have so far for me all been broken in some way or another. Either grass7 API in grass6 example, typos, incomplete, etc. have made almost all of them fail out of the box. As this is teaching code we should make sure it's perfect :-). See also bug in trac about possible memory leak in r.example.

* Extend {{cmd|r.colors}} documentation by an example for a user-generated logarithmic color table.
: + 'r.colors -e' example may be of more interest, even if many people don't know about it.
: + an example of the 'd.legend use=0.001,0.01,0.1,1,10,100' trick with log scale color rules

* I (Hamish) recently added support for Alessandro Frigeri's Planetary ellipsoid list (trunk/lib/gis/ellipse.table.solar.system) to the wx location wizard, but it is still buggy, and I think I broke e.g. "airy" too. any python experts able to help? tx.

* In the wiki, [[Template:AddonCmd]] could use an update for GRASS 7 entries. The page layout is a bit different (different pages for different groups), so either a new Template:AddonCmd7 is needed, or a bunch of fancy logic added to e.g. the way than man pages can have their version added as a "<tt>|version=</tt>" with [[Template:Cmd]].
::: (ML) This template points to [[GRASS AddOns]] page. To implement this wish we would need separate wiki pages, eg. GRASS 6 AddOns and GRASS 7 AddOns. Or the template could also point to the source code - something like [GRASS_Addons#<module>] ([trac/addons/grass<version>/<module> src]).
:::: We also have [[AddOns/GRASS7]], so the structure is totally confused. We need to keep [[AddOns]] as landing pages as it has been highly cited

* Enhance [[Template:wikipedia]] so that alternate names can be given (like with [[Template:Cmd]]), mainly to avoid having to use "_" for spaces in the presented link-text.

== Testing by power users ==

(Power) users from all over the world are kindly invited to assist with testing of new and existing functionality. To collect results and notes, we set up an interactive, collaborative editing tool which works in real-time:

Please check http://titanpad.com/I51nq1SrNc

== Non-Technical ==

=== {{done}} Discuss role and current composition of GRASS-PSC ===

Discussion about GRASS [[PSC]]:
* Every year members are requested to confirm to continue their work in the PSC.
* After the Community Sprint 2012, the Chair will request updates to the [[RFC1]] from the PSC members.
* Answer within five business days needed.
* In case of no continuation/no answer, a member is replaced in order to refresh the PSC.
* To be eligible for PSC membership, a person should have a demonstrated and substantial involvement in GRASS GIS (operation of the PSC is defined at [[RFC1]]).

=== Misc ===

* {{done}} Discuss Google Summer of Code (two students are here)
* Discuss GRASS 6.4.3 and 7.0 release schedule
* Define make a manual test procedure for users to simplify testing before new releases, write this up in the wiki ([http://trac.osgeo.org/grass/wiki/HowToTestGrass6 example])

== Semi-Technical ==

=== {{done}} Improve Web site or use CMS ===
* Discussion about [[CMS]]
** Prototype site: http://grass.fem-environment.eu/
** Problem: enormous job
** Involvement of people, see nice example at http://www.mageia.org/en/contribute/

=== Misc ===
* Document tips & tricks for GRASS compilation with the wxGUI
: there is [http://trac.osgeo.org/grass/wiki/CompileOnWindows Compilation on MS-Windows]
* Discuss new GRASS Book 4th edition in conjunction with the GRASS GIS 7.0 release in early 2013

== Technical ==

=== OSGeo4W ===

* [{{done}} (martinl) - {{rev|51677}} & {{rev|51679}}] GRASS package configuration: add liblas support (http://liblas.org/osgeo4w.html) ([http://wingrass.fsv.cvut.cz/grass64/ download])

=== Android ===

* continue the Android compilation (needs especially the elimination of XDR in rast and rast3d)

=== QGIS-Sextante-GRASS interface ===

* work on new integration with [http://plugins.qgis.org/plugins/sextante/ QGIS-Sextante]

=== Update the GDAL-GRASS interface to GRASS 7 ===

* see http://trac.osgeo.org/gdal/ticket/2953
* LGPL grass IO code written from scratch?

=== Rules Based programming and Agent Based Modelling ===

* Tutorial/Documentation on g.infer
* [http://trac.osgeo.org/grass/browser/grass-addons/grass7/raster/r.agent r.agent] in GRASS 7

=== Time series ===

* {{done}} Seminar on Temporal GIS framework demo and discussion: by Soeren Gebbert
* Add content to http://grass.osgeo.org/grass70/manuals/html70_user/temporalintro.html from Soeren's tutorial
* Discuss temporal GIS wxGUI and WPS integration
* Discuss massive parallel computation of spatio-temporal datasets

=== Automated command use statistics ===

* modify {{Cmd|g.parser}} to write out the list of used commands (without parameters) into a text file for simple, automated command use statistics
: HB: ''I've already written a script to do this. (a while ago, I'll have to dig it out)''

=== Mobile: inventory of mobile and touch implementations ===

* [{{done}} (lucadelu) {{rev|51791}} & {{rev|51792}}] [http://code.google.com/p/geopaparazzi/ Geopaparazzi], v.in.geopaparazzi
* GRASS on Android (patches by MN)

=== Cloud computing ===

* g.cloud
* cluster usage best practices

=== GSoC 2012 ===

* v.net.* front end, WMS
* Python API
* Image Segmentation

=== GRASS 7 ===
* [[PostGIS]] Topology support
* New features for vector engine
* Discuss Toolbox concept
* Discuss how to implement [[GRASS Metadata Management]]
* [{{done}} (lucadelu) - {{rev|51735}}] Fix category in {{Cmd|v.in.mapgen|version=70}}
* [{{done}} ] New addons module [[AddOns/GRASS7|r.massmov]]

=== Model integration ===

* GRASS and [http://www.coulthard.org.uk/CAESAR.html Caesar model]

=== GRASS modules fixes ===

* {{Cmd|i.atcorr}} debugging
** Figure out how to get visibility/aerosol depth at 550nm (perhaps from MODIS atmosphere?)
** Under certain circumstances i.atcorr produces NULL data
* GRASS 6.4.3 - [http://trac.osgeo.org/grass/query?status=new&status=assigned&status=reopened&group=type&order=priority&priority=blocker&priority=critical&milestone=6.4.3&milestone=6.4.2&milestone=6.4.1&milestone=6.4.0 Release critical issues to be fixed]

=== Signal handling ===

* The Python based scripts should catch CTRL-C to avoid that clutter is left behind & that ugly traceback messages are printed to the terminal.

Suggestion by Anne Ghisla (yet not working... ):
<source lang="python">
Index: lib/init/grass.py
===================================================================
--- lib/init/grass.py (revision 51604)
+++ lib/init/grass.py (working copy)
@@ -30,7 +30,12 @@
import subprocess
import re
import platform
+import signal

+# catch user-sent CTRL-C
+signal.signal(signal.SIGINT, lambda a,b:cleanup())
+signal.siginterrupt(signal.SIGINT, False)
+
# Variables substituted during build process
if os.environ.has_key('GISBASE'):
gisbase = os.environ['GISBASE']
</source>

* Currently if vector creation modules fail to create/import they still leave behind the empty skeleton of a map, so you need to use --o for the next time. It would be nice if cleanup could occur. This doesn't happen (visibly) with raster maps as they are composed in $MAPSET/.tmp/ and only moved into the main $MAPSET elements once everything is finished. Vector maps on the otherhand write to the MAPSET in-place.

=== Fix wxGUI problems ===

==== Add a "change language" option in GRASS GUI ====

Implement the diff provided here: http://trac.osgeo.org/grass/ticket/879

==== Fix several issues ====

A. Clerici: please fix:
* ticket https://trac.osgeo.org/grass/ticket/1564
* {{done}} ([[User:annakrat | Anna Kratochvilova]]) - {{rev|51824}}, {{rev|51825}}, {{rev|51827}}. ticket https://trac.osgeo.org/grass/ticket/1570
* wxGUI bugs (GRASS6.4.2RC3 under Fedora 16):
** {{done}} ([[User:annakrat | Anna Kratochvilova]]) - {{rev|51753}}, {{rev|51772}}, {{rev|51773}}. In the 'Create histogram of raster map' function, the style pie and the Color for text and axes options are not working. The options run fine on the tcltk GUI and in command line mode.
** In the 'Add scalebar and north arrow', the scale can be modified only once and the option can't be re-entered nor the scale can't be deleted. Also in this case there are no problems with the tcltk GUI.
** {{done}} ([[User:annakrat | Anna Kratochvilova]]) - {{rev|51824}}, {{rev|51825}}, {{rev|51827}}. The option 'Add raster cell arrows' seems not to work properly. It seems that the arrows in the Map Display cannot zoomed in. It can be checked by the following steps:
*** Load and display the aspect (Spearfish) map; Open the d.rast.arrows panel through the GUI button and choose the same map aspect. Click Apply: the Map Display appears green as expected for the very high resolution; Choose 10 for the 'Draw arrow every Nth grid cell:' option and none as 'Color for drawing grid or “none”' option. The arrows are displayed on the cells of aspect map; To make the arrows visible choose slope as 'Raster map containing values used for arrow length:' and 10.0 as 'Scale factor for arrows'. Zoom in a very small area: the cells of aspect map are enlarged, but the density of arrows remains the same; The direction is correctly the same for all arrows inside the same cell but it seems that instead of having an arrow each 10 aspect cells, there is an arrow each 10 pixel of the screen (with tcltk GUI the procedure works fine)
* Improve the GRASS 7 wx0..6 monitors
** Some improvements done by Vaclav Petras

==== Layout ====

Optionally, have all-in-one GUI window (requested by many new users!):
<center>
{|
|-
| [[Image:Wxgui_current.png|250px|thumb|center|Current wxGUI layout with detached window components]]
| [[Image:Wxgui_proposal.png|200px|thumb|center|'''Proposal''' for wxGUI layout modification (Recomposition of existing toolbars, mapview and menus by simple rearrangement into one frame)]]
|-
|}
</center>

Proposed solution: wxLayoutAlgorithm(), see [[WxGUI#What_others_do]]

Optionally, a minimalistic cointegration of a map display and the command console. See also this post in grass-user [http://lists.osgeo.org/pipermail/grass-user/2011-April/060346.html Re: [GRASS-user<nowiki>]</nowiki> replacement for d.mon in GRASS 7.0?]
<center>
{|
|-
|[[Image:grass-gis_minimalistic_map-display_with_comman-console__layout_mockup.png|200px|thumb|left|alt text]]
|}
</center>

==== r.li.setup ====
work on {{Cmd|r.li.setup}} for GRASS7

==== Saving History ====

* when using the wxGUI, it needs to write back to the shell history
: `cat wxgui_history.log >> $MAPSET/.bash_history`
: Since the wxGUI shell quoting is not perfect, maybe it is better not to write directly to real shell history, but maintain its own in ~/.grass7/history.

==== Digitizing toolbar ====

* missing string "Select vector map" from the drop-down widget on digitizing toolbar
: on winGRASS, nightly build of 24th May
* after editing vector objects and saving, the changes are not applied on the map. Must be some refresh problem.
* Highlighting problem
: objects selected in the attribute table are not highlighted on the map
: objects selected ton the map are not highlighted in the attribute table.
* Bounding box of a layer broken after deletion of some objects with broken geometry, also displaying of the attribute table broken with a message that the map layer is not a vector one,
: closing the layer from the layer tree also not possible
: after closing GRASS6.4.3 and reopening the project, the layer is restored with all the changes applayed.

==== Attribute manager ====

* Editing attribute table broken
: cannot delete a row, permission denied
: different than selected row dissapears after not succesful row deletion but is back after refreshing the table.
* Not able to insert a value into a table, permision to the temp file denied.
* Too small area for displaying the table data after connecting a table to the vector map.
: Add a table to the vector layer in wxGUI GRASS6.4.3 with: Show attribute table > Manage layers tab.
: Go to Browse data tab, the area to thisplay the attributes is extreemly small and cannot be stretched.
: After closing the table manager and reopening, the area is normal wide again.
* SQL simple select "explodes" if selecting a string attribute without quotes

==== Map Display ====

* Clicking with a Query tool on a vector object randomly not able to find an object to display its attributes.
**[{{done}} ([[User:annakrat | Anna Kratochvilova]]) - {{rev|51810}}, {{rev|51811}}]

==== I18N ====

* Solve module description string duplication in both grassmods.po and grasswxpy.po files.
** Before fixing this problem in code, please find a way to automagically copy the translated strings to the proper .po files for all the languages.
** The problem is that the wxGUI menustrings are copied into grasswxpy_XX.po while the strings are already translated in grassmods_XX.py
* {{done}} Add current "language" output into "about" panel
* {{done}} Add new tab about "languages statistics" into "about" panel
* {{done}} Improvment "about" panel style

==== Project file ====
* Find a way to successfully open a project file made in GRASS6.4 in GRASS7.
: Due to changes (e.g. removal of some flags, e.g. -o flag of d.rast), the project file is not opened in a correct way. The user can see the layers in the layer tree, but they cannot be displayed in the map canvas. A warning would help.
* add version into file tags

=== Python coding hints ===

* Consider Spyder, a powerful interactive development environment for the Python: http://code.google.com/p/spyderlib/
* use pylint, the python code static checker: http://pypi.python.org/pypi/pylint

== Not to forget about the next time ==

First day:
* presentation of participants

First or second day:
* group photo

GRASS Community Sprint Prague 2012

2012-04-05T02:07:45Z

⚠️Helena: /* In person */

The GRASS GIS team will organize a '''GRASS Developer and Power User Meeting, aka 'GRASS Community Sprint'''' from '''May 23 to May 28, 2012'''. The sprint is following the [http://foss4g-cee.org/ FOSS4G-CEE] & [http://geoinformatics.fsv.cvut.cz/gwiki/Geoinformatics_FCE_CTU_2012 Geoinformatics] ''(Free and Open Source Software for Geospatial in Central and East Europe)'', 21-23 May 2012, [http://en.wikipedia.org/wiki/Prague Prague], [http://en.wikipedia.org/wiki/Czech_Republic Czech Republic].

'''Important dates:'''

* 21 (Monday) - 23 (Wednesday) May 2012: [http://foss4g-cee.org/ FOSS4G-CEE & Geoinformatics conference]

* '''23 (Wednesday) - 28 (Monday) May 2012: GRASS GIS Community Sprint''' @ [http://www.fsv.cvut.cz/ FCE CTU]

== Purpose ==

Get together GRASS GIS project members to make decisions and tackle larger problems.

For this meeting, we welcome people committed to improving the GRASS GIS project. This includes developers, document writers, wish and bug reporters, translators etc.

== Sponsors ==

We welcome financial contributions to support the meeting and we are looking for sponsors to cover costs such as meals or to help reducing travelling and accommodation expenses for GRASS developers with far arrival If you are interested to sponsor the GRASS Community Sprint, please read about

:::'''sponsoring the GRASS project at [http://grass.osgeo.org/donation.php http://grass.osgeo.org/donation.php]'''

and, if needed, contact [[User:Neteler|Markus Neteler]] <tt><neteler at osgeo.org></tt>. Any surplus at the end of the event will be turned over to the GRASS GIS project.

The first GRASS Community Sprint is a great occasion for you to support the development of GRASS. With your contribution you'll enable more developers to meet in Prague. The community sprint is an important opportunity for the GRASS developers to discuss and collaboratively resolve bugs, plan the direction for the project and work on new features. Please see below for the more detailed agenda. The developers and contributors are donating their valuable time, so it would be great if in-kind funding can be made available from within the community to cover out-of-pocket expenses. All of the work that takes place at the community sprint will be directly contributed back into the GRASS project to the benefit of everyone who uses it.

=== Thanks to our sponsors ===

We are grateful for the support which we have received to organize this GRASS Community Sprint:

@TODO

== Timing ==

'''When''': Wednesday, May 23, 2012 (day of arrival) - Monday, May 28, 2012 (day of departure)

Of course you are invited to join or leave the community sprint whenever you want.

'''Duration''':

* Wednesday is day of arrival
** First meeting in the evening (after the [http://foss4g-cee.org/ FOSS4G-CEE & Geoinfomatics conference]) to define the agenda
* Thursday to Sunday
** Full days
* Monday is day of departure
** Probably hacking for people with a flight later in the evening

== Venue ==
[[Image:logo_cvut.jpg|130px|left]]
Department of Mapping and Cartography 
[http://www.fsv.cvut.cz Faculty of Civil Engineering] 
[http://www.cvut.cz Czech Technical University in Prague], [http://en.wikipedia.org/wiki/Czech_Republic Czech Republic] 
[http://geoinformatics.fsv.cvut.cz/gwiki/Room_B367 Room B367] 

'''[http://geoinformatics.fsv.cvut.cz/gwiki/Where_you_can_find_us Location & Transportations]'''

Prague has an international [http://www.prg.aero/en/ airport] and is also reachable by train, bus or car.

== Accommodation and Costs ==

Participants should plan for the following costs:

* Travel to Prague, variable depending on where you come from
* Accommodation and meals
'''Please note''': The currency in Czech Republic is [http://en.wikipedia.org/wiki/Czech_crown crown] (CZK, koruna, Kč). 100 Czech crowns are about 4 Euros (see [http://www.cnb.cz/en/financial_markets/foreign_exchange_market/exchange_rate_fixing/daily.jsp current rates]).

'''[http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague Accommodation in Prague]'''

:* [http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague#Masarykova_Kolej_Hotel Masarykova Kolej Hotel]
:* [http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague#Hotel_DAP Hotel DAP]
:* [http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague#Hotel_Krystal Hotel Krystal]
:* [http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague#Pension_Hanspaulka Pension Hanspaulka]
:* [http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague#Hotel_Silenzio Hotel Silenzio]
:* Special offer: ''sleeping for free in the kindergarten'' (30min by city urban mass transportation from the university campus, sleeping bag required, kitchen and WC available, no showers, in working days available only from 8 p.m. to 8 a.m.), contact [[User:Landa|Martin Landa]] for details
:* See also http://www.hotel.cz/praha-6/accommodation/

Please let us know your time of arrival and leaving, so we can book for the accommodations and organize the logistics.

Financial support: (partial) travel grants can be payed upon request thanks to our sponsors!

== Weather and Common Item Prices ==

* In May the weather in Prague is usually quite warm ([http://www.prague-spot.com/climate 15 or more degrees by day])
* A espresso coffee is about 20 CZK (80 cents), a beer (half of liter) in a common pub is around 25 CZK (1 euro), can be more in special pubs. In Prague you can have a full meal (see [http://en.wikipedia.org/wiki/Czech_cuisine Czech cuisine]) for still 75 - 150 CZK (3 - 6 euros), but beware of tourist restaurants, the prize can easily rise. It's quite easy to find in Prague also Italian or Chinese restaurants.

== Agenda - What we plan to do ==

'''Note:''' The program is generally open for your ideas. Please write an email to the [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developer list] to discuss your contribution.

@TODO

=== Timeline ===

==== Wednesday, 23 May ====
* Kick-off at ''<time to be defined>''

@TODO

=== Topics ===

==== Non-technical ====

@TODO

==== Semi-technical ====

@TODO

==== Technical ====

@TODO

== Participation ==

We are planning for attendance of 20 people (i.e., hacking places) but of course you are welcome to join us and bring new ideas with you, as more places are available. Please add your name here or contact [[User:Landa|Martin Landa]] <tt><landa.martin at gmail.com></tt>:

=== In person ===

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;"
!width=50px|'''No'''
!width=130px|'''Participant '''
!width=100px|'''Country'''
!width=100px|'''Arrival'''
!width=100px|'''Departure'''
!'''Topic'''
!width=75px|'''T-Shirt'''
!'''Notes'''
|-
|1
|[[User:Landa|Martin Landa]]
|Czech Republic
| May 20
| May 28
|Toolbox concept, vector engine in GRASS 7, wxGUI
| L
|
|-
|2
|[[User:Neteler|Markus Neteler]]
|Italy
| May 20
| May 26
|odds and ends, varia
| M
|
|-
|3
|[[User:Lucadelu|Luca Delucchi]]
|Italy
| May 20
| May 26
| r.modis, r.li.setup gui, v.in.geopaparazzi (only if andrea antonello come to Prague)
| L
|
|-
|4
|[[User:moovida|Andrea Antonello]]
|Italy
| May 21/22
| May 25/26
| v.in.geopaparazzi, grass-uDig link, singing at the pub with Luca Delucchi
| L
|
|-
|5
|[[User:silli|Silvia Franceschi]]
|Italy
| May 21/22
| May 25/26
| Tutorial/Documentation around the hydraulic toolchain in grass
| S
|
|-
|6
|[[User:peter.loewe|Peter Loewe]]
|Germany
| May 20/21
| May 25/26
| collecting beer-money while Luca and Andrea sing in pubs ; i.atcorr debugging ; g.cloud ? ; r.tsunami ? ; Tutorial/Documentation on g.infer
| S
|
|-
|7
|[[User:Annakrat|Anna Kratochvilova]]
|Czech Republic
| May 20
| May 28
| imagery, wxGUI
| S
|
|-
|8
|[[User:Vaclav|Vaclav Petras]]
|Czech Republic
| May 20
| May 28
| imagery, wxGUI, Toolbox concept ?
| M
|
|-
|9
|[[User:Helena|Helena Mitasova]]
|USA
|May 21
|May 25/26
|toolbox concept, student sandbox, wxnviz z-scale, inventory of mobile and touch implementations, GRASS on-line and cloud
|
|-
|}

=== Via IRC chat ===

@TODO

=== Collaborative document scratching ===

* EtherPad: http://etherpad.osuosl.org

== Individual Preparation ==

* Bring your own computer
* Bring [http://en.wikipedia.org/wiki/Mains_electricity_by_country power connector adapter] if needed (Czech Republic: 230V, 50Hz, [http://en.wikipedia.org/wiki/File:Euro-Flachstecker_2.jpg Type C Europlugs] are common and also [http://en.wikipedia.org/wiki/File:French_plug_and_socket.jpg Type E])
* Install subversion and the compiler tools, and come with a working GRASS development environment if possible.

== Broadcast & Video ==

During the event :)

== Photos ==

Also during the event :)

== FAQ ==

* How was it last year?
** Very nice, see [[GRASS Community Sprint Prague 2011]]!
* ''Is the GRASS Community Sprint just a coding event?''
** It is mainly a coding and documentation event. It is a working session for people who are already participants in the GRASS project and/or are committed to improving the GRASS project.
** On demand we can do some presentations of current working GRASS implementation and new upcoming features to spread the idea of Open Source GIS software
* ''Is the GRASS Community Sprint for developers only?''
** No: anybody can help, with testing, checking out bugs and fixes, documentation and more.
* ''Where can I get help and more information about the community sprint?''
** Contact [[User:Landa|Martin Landa]] <tt><landa.martin at gmail.com></tt>

[[Category: Workshops]]

GRASS SoC Ideas 2012

2012-03-22T04:03:36Z

⚠️Helena: /* wxGUI */

<center>

[[Image:grasslogo_vector_small.png|link=http://grass.osgeo.org]] @ [[Image:Gsoc-2012-logo-color.png|250px|link=http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2012]] @ [[Image:OSGeo 220pix.png|link=http://www.osgeo.org]]
</center>

* See also previous Google Summer of Code [[GRASS SoC Ideas 2011|ideas from 2011]].

* Visit the [http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2012 main OSGeo Google Summer of Code 2012 @ OSGeo wiki page].

__TOC__
== About ==

This is the GRASS page for [http://wiki.osgeo.org/index.php/Google_Summer_of_Code Google Summer of Code 2012]. Here we will list project ideas and and other information related to the GRASS GSoC projects.

* [http://code.google.com/soc/ Official Google Summer of Code 2012 homepage]
* [http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2012 OSGeo SoC 2012 homepage]

Promotion:
* OSGeo Flyer at <s>http://svn.osgeo.org/osgeo/marketing/flyer/google_summer_of_code/OSGeo_GSoC_2012.pdf </s>(todo)
* Videos at http://code.google.com/p/google-summer-of-code/wiki/Videos
* More Flyers at http://code.google.com/p/google-summer-of-code/wiki/GsocFlyers

== Timeline ==

* '''[http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2012/faqs#timeline The official timeline]'''

== Required Steps ==

* '''List ideas'''

* Assign Mentors to Ideas

* Notify OSGeo

* Mentors evaluate student applications

* Accepted students announced

* Students subscribe to the [http://lists.osgeo.org/mailman/listinfo/grass-dev grass-dev mailing list] and introduce themselves

* Mentor will create directory structure in the [http://trac.osgeo.org/grass/browser/grass-addons GRASS add-ons SVN] for projects and setup access for students
** Students must read and post agreement to [http://grass.osgeo.org/programming7/rfc2_psc.html RFC2] to the [http://lists.osgeo.org/mailman/listinfo/grass-psc grass-psc mailing list] to gain SVN access
** Create a Wiki page for each accepted project, to be used as a progress reporting tool

* Coding begins...

* Students and mentors: Complete the Mid-term survey

* Final commit and packaging for Google

== 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.

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

=== [[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 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]].
<center>
<gallery widths=400 heights=250>
Image:Wxgui_current.png|Current wxGUI layout with detached window components
Image:Wxgui_proposal.png|Proposal for wxGUI layout modification (Recomposition of existing toolbars, mapview and menus)
</gallery>
</center>
# ''Your idea here''

'''Willing to Mentor:''' [[User:Landa|Martin Landa]], [[User:MarisN|Maris Nartiss]], [[User:Mmetz|Markus Metz]], (''your name here'')

=== Raster ===

#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)
# Expand maximum grid size for {{cmd|r.watershed}}. [[LIDAR]]-based elevation grids are at finer resolution than previous elevation models, often overwhelming the integer variable limit for grid size.
# ''Your suggestion here!''

'''Willing to Mentor:''' Hamish (co-mentor parallelization and prominence projects), Wolf Bergenheim(''your name here'')

=== Vector ===

# Add '''[[OpenMP]] parallelization''' where appropriate, for example, {{cmd|v.surf.rst}} and {{cmd|v.vol.rst}} ''(co-mentor Helena Mitasova)''. (OpenCL and pthreads are fine too!) See above idea in the [[GRASS SoC Ideas 2012#Raster|Raster section]].
# Better '''support for wrap-around at 180 longitude''': Currently the raster engine is pretty good at wrapping data over 180 longitude. The vector data isn't, but it should be. This is a great task if by the end of the summer you'd like to be familiar with the implementation method of an entire vector stack of a fully featured modern GIS.
# 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).
# ''Your idea here'' ...

'''Willing to Mentor:''' [[User:Landa|Martin Landa]], [[User:Mmetz|Markus Metz]], Hamish (co-mentor for parallelization), Wolf Bergenheim, (''your name here'')

=== Imagery ===

# GRASS's imagery modules (for satellite, scanned maps, and orthophotos) act as enhanced raster modules. In GRASS 5 and 6 they were mostly implemented using interactive X-monitors which are not available in MS Windows and so are removed in the new cross-platform code of GRASS 7.
#* We need someone willing to '''port the old modules to work with GRASS 7''', including writing new '''wxPython GUI frontends''' to a number of existing tools and updating the imagery libraries to current raster library standards.
#* In addition, there are a number of '''improved/automated georectification tools''' which have not been merged into GRASS 5/6 which it would be nice to have updated and merged into the main code.
# Implement '''[[OpenMP]] (multithreading)''' as much as possible (where appropriate; OpenCL and pthreads are fine too)
# In addition to the porting of the georectification tools mentioned above, it would be interesting to implement an orthorectification tool for satellite imagery. Currently, GRASS only has {{cmd|i.ortho.photo}} for aerial photographs.
# Implement image segmentation algorithms and tools
# 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)
# ''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.

'''Willing to Mentor:''' Hamish (co-mentor for parallelization), (''your name here'')

=== Cartography and display ===

# Add SVG (and perhaps EPS) support to the display library, for use via {{cmd|d.graph}} and/or {{cmd|d.vect}}, and add SVG support to {{cmd|ps.map}} via a SVG to EPS converter tool (probably by adapting an existing GPL-compatible library). Code to be written in ANSI C. Step 1 is adding a Bézier curve rendering library function.
# Integrate Quantum/GRASS SVG output plugin with Inkscape. Python can serve as a common glue between these tools. The project would facilitate easy cartographic workflow while utilizing the advanced design functionality of Inkscape. This would be a two way bridge:
## 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.
# ''Your idea here ...''

'''Willing to Mentor:''' Hamish (as a co-mentor)

=== 3D visualization ===

# Optimize OGSF (and NVIZ/wxNVIZ) to '''display large 3D point clouds with uninterupted tought speed'''. OGSF + (wx)NVIZ should be able to rotate point cloud (i.e. LiDAR dataset) with 4 millions of points on medium hardware (i.e. 2GHz CPU with 2Gb RAM and GPU with hardware transform and lighting support and dedicated video RAM) with response time not greater than 1.0 second.
# Design and implement '''text displaying and styling in OGSF library''' and it's front-ends (NVIZ, [[wxNVIZ]]). Solution should be user configurable (fonts, colors, effects etc.) and multilanguage friendly.
# Design and implement user-provided '''symbol support in OGSF library''' and it's front-ends (NVIZ, [[wxNVIZ]]). Solution should support GRASS symbols, SVG, and/or simple EPS symbols.

# Drape multiple color maps over topography (equivalent to running r.patch or r.composite and draping the result; second raster is currently supported as transparency).
# Improve handling of z-exageration so that z-exag=1 is a realistic representation of landscape in terms of vertical scaling. Other default settings could also be improved to support wider range of data and improve robustness.

'''Willing to Mentor:''' [[User:Landa|Martin Landa]] (for 2), co-mentor for 1 and 5: Helena Mitasova, (''your name here'')

=== Volume modeling ===

# Develop '''r3.flow''' for computing 3D flow lines and 3D flow accumulation from 3D rasters
# Enhance volume interpolation module '''{{cmd|v.vol.rst}}''' for handling of data in space-time cube, including computation of gradients and hypercurvatures

'''Willing to Mentor:''' co-mentor Helena Mitasova, (''your name here'')

=== Other ===

* See also the [https://trac.osgeo.org/grass/query?status=assigned&status=new&status=reopened&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&type=enhancement GRASS wish list]

# 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 '''sophisticated Python scripting interface''' for GRASS based on [http://grass.osgeo.org/programming7/pythonlib.html GRASS Python Scripting Library]
# ''Your idea here''

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

== Guidelines for Students ==

How do you maximize your chances of getting picked? First read the [http://code.google.com/p/google-summer-of-code/wiki/AdviceforStudents Google SoC FAQ]. Then talk to us about your idea. Try emailing our [http://lists.osgeo.org/mailman/listinfo/grass-dev dev-mailing list], or come and talk to us in [[IRC]] (#grass). You can also reach the mentors directly by emailing:
* [http://lists.osgeo.org/mailman/listinfo/soc The OSGeo SoC mailing list]



* If you are thinking about applying, do make a point of reading the "[http://google-opensource.blogspot.co.nz/2011/02/flip-bits-not-burgers-student-guide.html Flip bits not Burgers: The Student's Guide to the Summer of Code]" eBook

=== Getting started with GRASS coding ===

* The source code is maintained in a [http://trac.osgeo.org/grass/browser/grass/trunk SVN server] which is easy to browse

* Please review the submitting files for our coding standards
** {{src|SUBMITTING|branch=trunk}} for C coding rules
** {{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]
: See also the [[Development|development section]] of the GRASS user's wiki

== Guidelines for Mentors ==

* Un(?)official book: http://www.booki.cc/gsoc-mentoring/
* Some more hints on the [http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2012_Administrative#Links OSGeo wiki]

== Accepted Ideas ==

# ''Project name''
#: Student: Your name here
#: Mentor: Your mentor's name here
#: Backup mentor: Your backup mentor's name here
#: Wiki page: wiki page maintained by you (typically in this GRASS wiki, or the trac development wiki)
# ''Project name''
#: Student: Someone else's name here
#: Mentor: Their mentor's name here
#: Backup mentor: Their backup mentor's name here
#: Wiki page: wiki page maintained by them (typically in this GRASS wiki, or the trac development wiki)

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

GRASS SoC Ideas 2012

2012-03-22T04:01:40Z

⚠️Helena: /* 3D visualization */

<center>

[[Image:grasslogo_vector_small.png|link=http://grass.osgeo.org]] @ [[Image:Gsoc-2012-logo-color.png|250px|link=http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2012]] @ [[Image:OSGeo 220pix.png|link=http://www.osgeo.org]]
</center>

* See also previous Google Summer of Code [[GRASS SoC Ideas 2011|ideas from 2011]].

* Visit the [http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2012 main OSGeo Google Summer of Code 2012 @ OSGeo wiki page].

__TOC__
== About ==

This is the GRASS page for [http://wiki.osgeo.org/index.php/Google_Summer_of_Code Google Summer of Code 2012]. Here we will list project ideas and and other information related to the GRASS GSoC projects.

* [http://code.google.com/soc/ Official Google Summer of Code 2012 homepage]
* [http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2012 OSGeo SoC 2012 homepage]

Promotion:
* OSGeo Flyer at <s>http://svn.osgeo.org/osgeo/marketing/flyer/google_summer_of_code/OSGeo_GSoC_2012.pdf </s>(todo)
* Videos at http://code.google.com/p/google-summer-of-code/wiki/Videos
* More Flyers at http://code.google.com/p/google-summer-of-code/wiki/GsocFlyers

== Timeline ==

* '''[http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2012/faqs#timeline The official timeline]'''

== Required Steps ==

* '''List ideas'''

* Assign Mentors to Ideas

* Notify OSGeo

* Mentors evaluate student applications

* Accepted students announced

* Students subscribe to the [http://lists.osgeo.org/mailman/listinfo/grass-dev grass-dev mailing list] and introduce themselves

* Mentor will create directory structure in the [http://trac.osgeo.org/grass/browser/grass-addons GRASS add-ons SVN] for projects and setup access for students
** Students must read and post agreement to [http://grass.osgeo.org/programming7/rfc2_psc.html RFC2] to the [http://lists.osgeo.org/mailman/listinfo/grass-psc grass-psc mailing list] to gain SVN access
** Create a Wiki page for each accepted project, to be used as a progress reporting tool

* Coding begins...

* Students and mentors: Complete the Mid-term survey

* Final commit and packaging for Google

== 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.

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

=== [[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. (co-mentor Helena Mitasova).
# 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]].
<center>
<gallery widths=400 heights=250>
Image:Wxgui_current.png|Current wxGUI layout with detached window components
Image:Wxgui_proposal.png|Proposal for wxGUI layout modification (Recomposition of existing toolbars, mapview and menus)
</gallery>
</center>
# ''Your idea here''

'''Willing to Mentor:''' [[User:Landa|Martin Landa]], [[User:MarisN|Maris Nartiss]], [[User:Mmetz|Markus Metz]], (''your name here'')

=== Raster ===

#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)
# Expand maximum grid size for {{cmd|r.watershed}}. [[LIDAR]]-based elevation grids are at finer resolution than previous elevation models, often overwhelming the integer variable limit for grid size.
# ''Your suggestion here!''

'''Willing to Mentor:''' Hamish (co-mentor parallelization and prominence projects), Wolf Bergenheim(''your name here'')

=== Vector ===

# Add '''[[OpenMP]] parallelization''' where appropriate, for example, {{cmd|v.surf.rst}} and {{cmd|v.vol.rst}} ''(co-mentor Helena Mitasova)''. (OpenCL and pthreads are fine too!) See above idea in the [[GRASS SoC Ideas 2012#Raster|Raster section]].
# Better '''support for wrap-around at 180 longitude''': Currently the raster engine is pretty good at wrapping data over 180 longitude. The vector data isn't, but it should be. This is a great task if by the end of the summer you'd like to be familiar with the implementation method of an entire vector stack of a fully featured modern GIS.
# 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).
# ''Your idea here'' ...

'''Willing to Mentor:''' [[User:Landa|Martin Landa]], [[User:Mmetz|Markus Metz]], Hamish (co-mentor for parallelization), Wolf Bergenheim, (''your name here'')

=== Imagery ===

# GRASS's imagery modules (for satellite, scanned maps, and orthophotos) act as enhanced raster modules. In GRASS 5 and 6 they were mostly implemented using interactive X-monitors which are not available in MS Windows and so are removed in the new cross-platform code of GRASS 7.
#* We need someone willing to '''port the old modules to work with GRASS 7''', including writing new '''wxPython GUI frontends''' to a number of existing tools and updating the imagery libraries to current raster library standards.
#* In addition, there are a number of '''improved/automated georectification tools''' which have not been merged into GRASS 5/6 which it would be nice to have updated and merged into the main code.
# Implement '''[[OpenMP]] (multithreading)''' as much as possible (where appropriate; OpenCL and pthreads are fine too)
# In addition to the porting of the georectification tools mentioned above, it would be interesting to implement an orthorectification tool for satellite imagery. Currently, GRASS only has {{cmd|i.ortho.photo}} for aerial photographs.
# Implement image segmentation algorithms and tools
# 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)
# ''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.

'''Willing to Mentor:''' Hamish (co-mentor for parallelization), (''your name here'')

=== Cartography and display ===

# Add SVG (and perhaps EPS) support to the display library, for use via {{cmd|d.graph}} and/or {{cmd|d.vect}}, and add SVG support to {{cmd|ps.map}} via a SVG to EPS converter tool (probably by adapting an existing GPL-compatible library). Code to be written in ANSI C. Step 1 is adding a Bézier curve rendering library function.
# Integrate Quantum/GRASS SVG output plugin with Inkscape. Python can serve as a common glue between these tools. The project would facilitate easy cartographic workflow while utilizing the advanced design functionality of Inkscape. This would be a two way bridge:
## 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.
# ''Your idea here ...''

'''Willing to Mentor:''' Hamish (as a co-mentor)

=== 3D visualization ===

# Optimize OGSF (and NVIZ/wxNVIZ) to '''display large 3D point clouds with uninterupted tought speed'''. OGSF + (wx)NVIZ should be able to rotate point cloud (i.e. LiDAR dataset) with 4 millions of points on medium hardware (i.e. 2GHz CPU with 2Gb RAM and GPU with hardware transform and lighting support and dedicated video RAM) with response time not greater than 1.0 second.
# Design and implement '''text displaying and styling in OGSF library''' and it's front-ends (NVIZ, [[wxNVIZ]]). Solution should be user configurable (fonts, colors, effects etc.) and multilanguage friendly.
# Design and implement user-provided '''symbol support in OGSF library''' and it's front-ends (NVIZ, [[wxNVIZ]]). Solution should support GRASS symbols, SVG, and/or simple EPS symbols.

# Drape multiple color maps over topography (equivalent to running r.patch or r.composite and draping the result; second raster is currently supported as transparency).
# Improve handling of z-exageration so that z-exag=1 is a realistic representation of landscape in terms of vertical scaling. Other default settings could also be improved to support wider range of data and improve robustness.

'''Willing to Mentor:''' [[User:Landa|Martin Landa]] (for 2), co-mentor for 1 and 5: Helena Mitasova, (''your name here'')

=== Volume modeling ===

# Develop '''r3.flow''' for computing 3D flow lines and 3D flow accumulation from 3D rasters
# Enhance volume interpolation module '''{{cmd|v.vol.rst}}''' for handling of data in space-time cube, including computation of gradients and hypercurvatures

'''Willing to Mentor:''' co-mentor Helena Mitasova, (''your name here'')

=== Other ===

* See also the [https://trac.osgeo.org/grass/query?status=assigned&status=new&status=reopened&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&type=enhancement GRASS wish list]

# 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 '''sophisticated Python scripting interface''' for GRASS based on [http://grass.osgeo.org/programming7/pythonlib.html GRASS Python Scripting Library]
# ''Your idea here''

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

== Guidelines for Students ==

How do you maximize your chances of getting picked? First read the [http://code.google.com/p/google-summer-of-code/wiki/AdviceforStudents Google SoC FAQ]. Then talk to us about your idea. Try emailing our [http://lists.osgeo.org/mailman/listinfo/grass-dev dev-mailing list], or come and talk to us in [[IRC]] (#grass). You can also reach the mentors directly by emailing:
* [http://lists.osgeo.org/mailman/listinfo/soc The OSGeo SoC mailing list]



* If you are thinking about applying, do make a point of reading the "[http://google-opensource.blogspot.co.nz/2011/02/flip-bits-not-burgers-student-guide.html Flip bits not Burgers: The Student's Guide to the Summer of Code]" eBook

=== Getting started with GRASS coding ===

* The source code is maintained in a [http://trac.osgeo.org/grass/browser/grass/trunk SVN server] which is easy to browse

* Please review the submitting files for our coding standards
** {{src|SUBMITTING|branch=trunk}} for C coding rules
** {{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]
: See also the [[Development|development section]] of the GRASS user's wiki

== Guidelines for Mentors ==

* Un(?)official book: http://www.booki.cc/gsoc-mentoring/
* Some more hints on the [http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2012_Administrative#Links OSGeo wiki]

== Accepted Ideas ==

# ''Project name''
#: Student: Your name here
#: Mentor: Your mentor's name here
#: Backup mentor: Your backup mentor's name here
#: Wiki page: wiki page maintained by you (typically in this GRASS wiki, or the trac development wiki)
# ''Project name''
#: Student: Someone else's name here
#: Mentor: Their mentor's name here
#: Backup mentor: Their backup mentor's name here
#: Wiki page: wiki page maintained by them (typically in this GRASS wiki, or the trac development wiki)

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

GRASS SoC Ideas 2012

2012-03-22T03:53:56Z

⚠️Helena: /* wxGUI */

<center>

[[Image:grasslogo_vector_small.png|link=http://grass.osgeo.org]] @ [[Image:Gsoc-2012-logo-color.png|250px|link=http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2012]] @ [[Image:OSGeo 220pix.png|link=http://www.osgeo.org]]
</center>

* See also previous Google Summer of Code [[GRASS SoC Ideas 2011|ideas from 2011]].

* Visit the [http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2012 main OSGeo Google Summer of Code 2012 @ OSGeo wiki page].

__TOC__
== About ==

This is the GRASS page for [http://wiki.osgeo.org/index.php/Google_Summer_of_Code Google Summer of Code 2012]. Here we will list project ideas and and other information related to the GRASS GSoC projects.

* [http://code.google.com/soc/ Official Google Summer of Code 2012 homepage]
* [http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2012 OSGeo SoC 2012 homepage]

Promotion:
* OSGeo Flyer at <s>http://svn.osgeo.org/osgeo/marketing/flyer/google_summer_of_code/OSGeo_GSoC_2012.pdf </s>(todo)
* Videos at http://code.google.com/p/google-summer-of-code/wiki/Videos
* More Flyers at http://code.google.com/p/google-summer-of-code/wiki/GsocFlyers

== Timeline ==

* '''[http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2012/faqs#timeline The official timeline]'''

== Required Steps ==

* '''List ideas'''

* Assign Mentors to Ideas

* Notify OSGeo

* Mentors evaluate student applications

* Accepted students announced

* Students subscribe to the [http://lists.osgeo.org/mailman/listinfo/grass-dev grass-dev mailing list] and introduce themselves

* Mentor will create directory structure in the [http://trac.osgeo.org/grass/browser/grass-addons GRASS add-ons SVN] for projects and setup access for students
** Students must read and post agreement to [http://grass.osgeo.org/programming7/rfc2_psc.html RFC2] to the [http://lists.osgeo.org/mailman/listinfo/grass-psc grass-psc mailing list] to gain SVN access
** Create a Wiki page for each accepted project, to be used as a progress reporting tool

* Coding begins...

* Students and mentors: Complete the Mid-term survey

* Final commit and packaging for Google

== 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.

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

=== [[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. (co-mentor Helena Mitasova).
# 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]].
<center>
<gallery widths=400 heights=250>
Image:Wxgui_current.png|Current wxGUI layout with detached window components
Image:Wxgui_proposal.png|Proposal for wxGUI layout modification (Recomposition of existing toolbars, mapview and menus)
</gallery>
</center>
# ''Your idea here''

'''Willing to Mentor:''' [[User:Landa|Martin Landa]], [[User:MarisN|Maris Nartiss]], [[User:Mmetz|Markus Metz]], (''your name here'')

=== Raster ===

#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)
# Expand maximum grid size for {{cmd|r.watershed}}. [[LIDAR]]-based elevation grids are at finer resolution than previous elevation models, often overwhelming the integer variable limit for grid size.
# ''Your suggestion here!''

'''Willing to Mentor:''' Hamish (co-mentor parallelization and prominence projects), Wolf Bergenheim(''your name here'')

=== Vector ===

# Add '''[[OpenMP]] parallelization''' where appropriate, for example, {{cmd|v.surf.rst}} and {{cmd|v.vol.rst}} ''(co-mentor Helena Mitasova)''. (OpenCL and pthreads are fine too!) See above idea in the [[GRASS SoC Ideas 2012#Raster|Raster section]].
# Better '''support for wrap-around at 180 longitude''': Currently the raster engine is pretty good at wrapping data over 180 longitude. The vector data isn't, but it should be. This is a great task if by the end of the summer you'd like to be familiar with the implementation method of an entire vector stack of a fully featured modern GIS.
# 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).
# ''Your idea here'' ...

'''Willing to Mentor:''' [[User:Landa|Martin Landa]], [[User:Mmetz|Markus Metz]], Hamish (co-mentor for parallelization), Wolf Bergenheim, (''your name here'')

=== Imagery ===

# GRASS's imagery modules (for satellite, scanned maps, and orthophotos) act as enhanced raster modules. In GRASS 5 and 6 they were mostly implemented using interactive X-monitors which are not available in MS Windows and so are removed in the new cross-platform code of GRASS 7.
#* We need someone willing to '''port the old modules to work with GRASS 7''', including writing new '''wxPython GUI frontends''' to a number of existing tools and updating the imagery libraries to current raster library standards.
#* In addition, there are a number of '''improved/automated georectification tools''' which have not been merged into GRASS 5/6 which it would be nice to have updated and merged into the main code.
# Implement '''[[OpenMP]] (multithreading)''' as much as possible (where appropriate; OpenCL and pthreads are fine too)
# In addition to the porting of the georectification tools mentioned above, it would be interesting to implement an orthorectification tool for satellite imagery. Currently, GRASS only has {{cmd|i.ortho.photo}} for aerial photographs.
# Implement image segmentation algorithms and tools
# 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)
# ''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.

'''Willing to Mentor:''' Hamish (co-mentor for parallelization), (''your name here'')

=== Cartography and display ===

# Add SVG (and perhaps EPS) support to the display library, for use via {{cmd|d.graph}} and/or {{cmd|d.vect}}, and add SVG support to {{cmd|ps.map}} via a SVG to EPS converter tool (probably by adapting an existing GPL-compatible library). Code to be written in ANSI C. Step 1 is adding a Bézier curve rendering library function.
# Integrate Quantum/GRASS SVG output plugin with Inkscape. Python can serve as a common glue between these tools. The project would facilitate easy cartographic workflow while utilizing the advanced design functionality of Inkscape. This would be a two way bridge:
## 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.
# ''Your idea here ...''

'''Willing to Mentor:''' Hamish (as a co-mentor)

=== 3D visualization ===

# Optimize OGSF (and NVIZ/wxNVIZ) to '''display large 3D point clouds with uninterupted tought speed'''. OGSF + (wx)NVIZ should be able to rotate point cloud (i.e. LiDAR dataset) with 4 millions of points on medium hardware (i.e. 2GHz CPU with 2Gb RAM and GPU with hardware transform and lighting support and dedicated video RAM) with response time not greater than 1.0 second.
# Design and implement '''text displaying and styling in OGSF library''' and it's front-ends (NVIZ, [[wxNVIZ]]). Solution should be user configurable (fonts, colors, effects etc.) and multilanguage friendly.
# Design and implement user-provided '''symbol support in OGSF library''' and it's front-ends (NVIZ, [[wxNVIZ]]). Solution should support GRASS symbols, SVG, and/or simple EPS symbols.

# Drape multiple color maps over topography (equivalent to running r.patch or r.composite and draping the result; second raster is currently supported as transparency).

'''Willing to Mentor:''' [[User:Landa|Martin Landa]] (for 2), co-mentor for 1 and 4: Helena Mitasova, (''your name here'')

=== Volume modeling ===

# Develop '''r3.flow''' for computing 3D flow lines and 3D flow accumulation from 3D rasters
# Enhance volume interpolation module '''{{cmd|v.vol.rst}}''' for handling of data in space-time cube, including computation of gradients and hypercurvatures

'''Willing to Mentor:''' co-mentor Helena Mitasova, (''your name here'')

=== Other ===

* See also the [https://trac.osgeo.org/grass/query?status=assigned&status=new&status=reopened&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&type=enhancement GRASS wish list]

# 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 '''sophisticated Python scripting interface''' for GRASS based on [http://grass.osgeo.org/programming7/pythonlib.html GRASS Python Scripting Library]
# ''Your idea here''

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

== Guidelines for Students ==

How do you maximize your chances of getting picked? First read the [http://code.google.com/p/google-summer-of-code/wiki/AdviceforStudents Google SoC FAQ]. Then talk to us about your idea. Try emailing our [http://lists.osgeo.org/mailman/listinfo/grass-dev dev-mailing list], or come and talk to us in [[IRC]] (#grass). You can also reach the mentors directly by emailing:
* [http://lists.osgeo.org/mailman/listinfo/soc The OSGeo SoC mailing list]



* If you are thinking about applying, do make a point of reading the "[http://google-opensource.blogspot.co.nz/2011/02/flip-bits-not-burgers-student-guide.html Flip bits not Burgers: The Student's Guide to the Summer of Code]" eBook

=== Getting started with GRASS coding ===

* The source code is maintained in a [http://trac.osgeo.org/grass/browser/grass/trunk SVN server] which is easy to browse

* Please review the submitting files for our coding standards
** {{src|SUBMITTING|branch=trunk}} for C coding rules
** {{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]
: See also the [[Development|development section]] of the GRASS user's wiki

== Guidelines for Mentors ==

* Un(?)official book: http://www.booki.cc/gsoc-mentoring/
* Some more hints on the [http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2012_Administrative#Links OSGeo wiki]

== Accepted Ideas ==

# ''Project name''
#: Student: Your name here
#: Mentor: Your mentor's name here
#: Backup mentor: Your backup mentor's name here
#: Wiki page: wiki page maintained by you (typically in this GRASS wiki, or the trac development wiki)
# ''Project name''
#: Student: Someone else's name here
#: Mentor: Their mentor's name here
#: Backup mentor: Their backup mentor's name here
#: Wiki page: wiki page maintained by them (typically in this GRASS wiki, or the trac development wiki)

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

GRASS SoC Ideas 2012

2012-03-22T03:49:19Z

⚠️Helena: /* wxGUI */

<center>

[[Image:grasslogo_vector_small.png|link=http://grass.osgeo.org]] @ [[Image:Gsoc-2012-logo-color.png|250px|link=http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2012]] @ [[Image:OSGeo 220pix.png|link=http://www.osgeo.org]]
</center>

* See also previous Google Summer of Code [[GRASS SoC Ideas 2011|ideas from 2011]].

* Visit the [http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2012 main OSGeo Google Summer of Code 2012 @ OSGeo wiki page].

__TOC__
== About ==

This is the GRASS page for [http://wiki.osgeo.org/index.php/Google_Summer_of_Code Google Summer of Code 2012]. Here we will list project ideas and and other information related to the GRASS GSoC projects.

* [http://code.google.com/soc/ Official Google Summer of Code 2012 homepage]
* [http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2012 OSGeo SoC 2012 homepage]

Promotion:
* OSGeo Flyer at <s>http://svn.osgeo.org/osgeo/marketing/flyer/google_summer_of_code/OSGeo_GSoC_2012.pdf </s>(todo)
* Videos at http://code.google.com/p/google-summer-of-code/wiki/Videos
* More Flyers at http://code.google.com/p/google-summer-of-code/wiki/GsocFlyers

== Timeline ==

* '''[http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2012/faqs#timeline The official timeline]'''

== Required Steps ==

* '''List ideas'''

* Assign Mentors to Ideas

* Notify OSGeo

* Mentors evaluate student applications

* Accepted students announced

* Students subscribe to the [http://lists.osgeo.org/mailman/listinfo/grass-dev grass-dev mailing list] and introduce themselves

* Mentor will create directory structure in the [http://trac.osgeo.org/grass/browser/grass-addons GRASS add-ons SVN] for projects and setup access for students
** Students must read and post agreement to [http://grass.osgeo.org/programming7/rfc2_psc.html RFC2] to the [http://lists.osgeo.org/mailman/listinfo/grass-psc grass-psc mailing list] to gain SVN access
** Create a Wiki page for each accepted project, to be used as a progress reporting tool

* Coding begins...

* Students and mentors: Complete the Mid-term survey

* Final commit and packaging for Google

== 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.

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

=== [[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 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. (co-mentor Helena Mitasova).
# 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]].
<center>
<gallery widths=400 heights=250>
Image:Wxgui_current.png|Current wxGUI layout with detached window components
Image:Wxgui_proposal.png|Proposal for wxGUI layout modification (Recomposition of existing toolbars, mapview and menus)
</gallery>
</center>
# ''Your idea here''

'''Willing to Mentor:''' [[User:Landa|Martin Landa]], [[User:MarisN|Maris Nartiss]], [[User:Mmetz|Markus Metz]], (''your name here'')

=== Raster ===

#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)
# Expand maximum grid size for {{cmd|r.watershed}}. [[LIDAR]]-based elevation grids are at finer resolution than previous elevation models, often overwhelming the integer variable limit for grid size.
# ''Your suggestion here!''

'''Willing to Mentor:''' Hamish (co-mentor parallelization and prominence projects), Wolf Bergenheim(''your name here'')

=== Vector ===

# Add '''[[OpenMP]] parallelization''' where appropriate, for example, {{cmd|v.surf.rst}} and {{cmd|v.vol.rst}} ''(co-mentor Helena Mitasova)''. (OpenCL and pthreads are fine too!) See above idea in the [[GRASS SoC Ideas 2012#Raster|Raster section]].
# Better '''support for wrap-around at 180 longitude''': Currently the raster engine is pretty good at wrapping data over 180 longitude. The vector data isn't, but it should be. This is a great task if by the end of the summer you'd like to be familiar with the implementation method of an entire vector stack of a fully featured modern GIS.
# 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).
# ''Your idea here'' ...

'''Willing to Mentor:''' [[User:Landa|Martin Landa]], [[User:Mmetz|Markus Metz]], Hamish (co-mentor for parallelization), Wolf Bergenheim, (''your name here'')

=== Imagery ===

# GRASS's imagery modules (for satellite, scanned maps, and orthophotos) act as enhanced raster modules. In GRASS 5 and 6 they were mostly implemented using interactive X-monitors which are not available in MS Windows and so are removed in the new cross-platform code of GRASS 7.
#* We need someone willing to '''port the old modules to work with GRASS 7''', including writing new '''wxPython GUI frontends''' to a number of existing tools and updating the imagery libraries to current raster library standards.
#* In addition, there are a number of '''improved/automated georectification tools''' which have not been merged into GRASS 5/6 which it would be nice to have updated and merged into the main code.
# Implement '''[[OpenMP]] (multithreading)''' as much as possible (where appropriate; OpenCL and pthreads are fine too)
# In addition to the porting of the georectification tools mentioned above, it would be interesting to implement an orthorectification tool for satellite imagery. Currently, GRASS only has {{cmd|i.ortho.photo}} for aerial photographs.
# Implement image segmentation algorithms and tools
# 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)
# ''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.

'''Willing to Mentor:''' Hamish (co-mentor for parallelization), (''your name here'')

=== Cartography and display ===

# Add SVG (and perhaps EPS) support to the display library, for use via {{cmd|d.graph}} and/or {{cmd|d.vect}}, and add SVG support to {{cmd|ps.map}} via a SVG to EPS converter tool (probably by adapting an existing GPL-compatible library). Code to be written in ANSI C. Step 1 is adding a Bézier curve rendering library function.
# Integrate Quantum/GRASS SVG output plugin with Inkscape. Python can serve as a common glue between these tools. The project would facilitate easy cartographic workflow while utilizing the advanced design functionality of Inkscape. This would be a two way bridge:
## 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.
# ''Your idea here ...''

'''Willing to Mentor:''' Hamish (as a co-mentor)

=== 3D visualization ===

# Optimize OGSF (and NVIZ/wxNVIZ) to '''display large 3D point clouds with uninterupted tought speed'''. OGSF + (wx)NVIZ should be able to rotate point cloud (i.e. LiDAR dataset) with 4 millions of points on medium hardware (i.e. 2GHz CPU with 2Gb RAM and GPU with hardware transform and lighting support and dedicated video RAM) with response time not greater than 1.0 second.
# Design and implement '''text displaying and styling in OGSF library''' and it's front-ends (NVIZ, [[wxNVIZ]]). Solution should be user configurable (fonts, colors, effects etc.) and multilanguage friendly.
# Design and implement user-provided '''symbol support in OGSF library''' and it's front-ends (NVIZ, [[wxNVIZ]]). Solution should support GRASS symbols, SVG, and/or simple EPS symbols.

# Drape multiple color maps over topography (equivalent to running r.patch or r.composite and draping the result; second raster is currently supported as transparency).

'''Willing to Mentor:''' [[User:Landa|Martin Landa]] (for 2), co-mentor for 1 and 4: Helena Mitasova, (''your name here'')

=== Volume modeling ===

# Develop '''r3.flow''' for computing 3D flow lines and 3D flow accumulation from 3D rasters
# Enhance volume interpolation module '''{{cmd|v.vol.rst}}''' for handling of data in space-time cube, including computation of gradients and hypercurvatures

'''Willing to Mentor:''' co-mentor Helena Mitasova, (''your name here'')

=== Other ===

* See also the [https://trac.osgeo.org/grass/query?status=assigned&status=new&status=reopened&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&type=enhancement GRASS wish list]

# 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 '''sophisticated Python scripting interface''' for GRASS based on [http://grass.osgeo.org/programming7/pythonlib.html GRASS Python Scripting Library]
# ''Your idea here''

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

== Guidelines for Students ==

How do you maximize your chances of getting picked? First read the [http://code.google.com/p/google-summer-of-code/wiki/AdviceforStudents Google SoC FAQ]. Then talk to us about your idea. Try emailing our [http://lists.osgeo.org/mailman/listinfo/grass-dev dev-mailing list], or come and talk to us in [[IRC]] (#grass). You can also reach the mentors directly by emailing:
* [http://lists.osgeo.org/mailman/listinfo/soc The OSGeo SoC mailing list]



* If you are thinking about applying, do make a point of reading the "[http://google-opensource.blogspot.co.nz/2011/02/flip-bits-not-burgers-student-guide.html Flip bits not Burgers: The Student's Guide to the Summer of Code]" eBook

=== Getting started with GRASS coding ===

* The source code is maintained in a [http://trac.osgeo.org/grass/browser/grass/trunk SVN server] which is easy to browse

* Please review the submitting files for our coding standards
** {{src|SUBMITTING|branch=trunk}} for C coding rules
** {{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]
: See also the [[Development|development section]] of the GRASS user's wiki

== Guidelines for Mentors ==

* Un(?)official book: http://www.booki.cc/gsoc-mentoring/
* Some more hints on the [http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2012_Administrative#Links OSGeo wiki]

== Accepted Ideas ==

# ''Project name''
#: Student: Your name here
#: Mentor: Your mentor's name here
#: Backup mentor: Your backup mentor's name here
#: Wiki page: wiki page maintained by you (typically in this GRASS wiki, or the trac development wiki)
# ''Project name''
#: Student: Someone else's name here
#: Mentor: Their mentor's name here
#: Backup mentor: Their backup mentor's name here
#: Wiki page: wiki page maintained by them (typically in this GRASS wiki, or the trac development wiki)

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

GRASS SoC Ideas 2012

2012-03-22T03:46:01Z

⚠️Helena: /* wxGUI */

<center>

[[Image:grasslogo_vector_small.png|link=http://grass.osgeo.org]] @ [[Image:Gsoc-2012-logo-color.png|250px|link=http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2012]] @ [[Image:OSGeo 220pix.png|link=http://www.osgeo.org]]
</center>

* See also previous Google Summer of Code [[GRASS SoC Ideas 2011|ideas from 2011]].

* Visit the [http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2012 main OSGeo Google Summer of Code 2012 @ OSGeo wiki page].

__TOC__
== About ==

This is the GRASS page for [http://wiki.osgeo.org/index.php/Google_Summer_of_Code Google Summer of Code 2012]. Here we will list project ideas and and other information related to the GRASS GSoC projects.

* [http://code.google.com/soc/ Official Google Summer of Code 2012 homepage]
* [http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2012 OSGeo SoC 2012 homepage]

Promotion:
* OSGeo Flyer at <s>http://svn.osgeo.org/osgeo/marketing/flyer/google_summer_of_code/OSGeo_GSoC_2012.pdf </s>(todo)
* Videos at http://code.google.com/p/google-summer-of-code/wiki/Videos
* More Flyers at http://code.google.com/p/google-summer-of-code/wiki/GsocFlyers

== Timeline ==

* '''[http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2012/faqs#timeline The official timeline]'''

== Required Steps ==

* '''List ideas'''

* Assign Mentors to Ideas

* Notify OSGeo

* Mentors evaluate student applications

* Accepted students announced

* Students subscribe to the [http://lists.osgeo.org/mailman/listinfo/grass-dev grass-dev mailing list] and introduce themselves

* Mentor will create directory structure in the [http://trac.osgeo.org/grass/browser/grass-addons GRASS add-ons SVN] for projects and setup access for students
** Students must read and post agreement to [http://grass.osgeo.org/programming7/rfc2_psc.html RFC2] to the [http://lists.osgeo.org/mailman/listinfo/grass-psc grass-psc mailing list] to gain SVN access
** Create a Wiki page for each accepted project, to be used as a progress reporting tool

* Coding begins...

* Students and mentors: Complete the Mid-term survey

* Final commit and packaging for Google

== 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.

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

=== [[wxGUI]] ===

# Develop GUI support in wxPython for visualy analyzing series of data layers.
The module should provide users with capabilities to browse and animate raster and 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 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. (co-mentor Helena Mitasova).
# 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]].
<center>
<gallery widths=400 heights=250>
Image:Wxgui_current.png|Current wxGUI layout with detached window components
Image:Wxgui_proposal.png|Proposal for wxGUI layout modification (Recomposition of existing toolbars, mapview and menus)
</gallery>
</center>
# ''Your idea here''

'''Willing to Mentor:''' [[User:Landa|Martin Landa]], [[User:MarisN|Maris Nartiss]], [[User:Mmetz|Markus Metz]], (''your name here'')

=== Raster ===

#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)
# Expand maximum grid size for {{cmd|r.watershed}}. [[LIDAR]]-based elevation grids are at finer resolution than previous elevation models, often overwhelming the integer variable limit for grid size.
# ''Your suggestion here!''

'''Willing to Mentor:''' Hamish (co-mentor parallelization and prominence projects), Wolf Bergenheim(''your name here'')

=== Vector ===

# Add '''[[OpenMP]] parallelization''' where appropriate, for example, {{cmd|v.surf.rst}} and {{cmd|v.vol.rst}} ''(co-mentor Helena Mitasova)''. (OpenCL and pthreads are fine too!) See above idea in the [[GRASS SoC Ideas 2012#Raster|Raster section]].
# Better '''support for wrap-around at 180 longitude''': Currently the raster engine is pretty good at wrapping data over 180 longitude. The vector data isn't, but it should be. This is a great task if by the end of the summer you'd like to be familiar with the implementation method of an entire vector stack of a fully featured modern GIS.
# 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).
# ''Your idea here'' ...

'''Willing to Mentor:''' [[User:Landa|Martin Landa]], [[User:Mmetz|Markus Metz]], Hamish (co-mentor for parallelization), Wolf Bergenheim, (''your name here'')

=== Imagery ===

# GRASS's imagery modules (for satellite, scanned maps, and orthophotos) act as enhanced raster modules. In GRASS 5 and 6 they were mostly implemented using interactive X-monitors which are not available in MS Windows and so are removed in the new cross-platform code of GRASS 7.
#* We need someone willing to '''port the old modules to work with GRASS 7''', including writing new '''wxPython GUI frontends''' to a number of existing tools and updating the imagery libraries to current raster library standards.
#* In addition, there are a number of '''improved/automated georectification tools''' which have not been merged into GRASS 5/6 which it would be nice to have updated and merged into the main code.
# Implement '''[[OpenMP]] (multithreading)''' as much as possible (where appropriate; OpenCL and pthreads are fine too)
# In addition to the porting of the georectification tools mentioned above, it would be interesting to implement an orthorectification tool for satellite imagery. Currently, GRASS only has {{cmd|i.ortho.photo}} for aerial photographs.
# Implement image segmentation algorithms and tools
# 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)
# ''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.

'''Willing to Mentor:''' Hamish (co-mentor for parallelization), (''your name here'')

=== Cartography and display ===

# Add SVG (and perhaps EPS) support to the display library, for use via {{cmd|d.graph}} and/or {{cmd|d.vect}}, and add SVG support to {{cmd|ps.map}} via a SVG to EPS converter tool (probably by adapting an existing GPL-compatible library). Code to be written in ANSI C. Step 1 is adding a Bézier curve rendering library function.
# Integrate Quantum/GRASS SVG output plugin with Inkscape. Python can serve as a common glue between these tools. The project would facilitate easy cartographic workflow while utilizing the advanced design functionality of Inkscape. This would be a two way bridge:
## 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.
# ''Your idea here ...''

'''Willing to Mentor:''' Hamish (as a co-mentor)

=== 3D visualization ===

# Optimize OGSF (and NVIZ/wxNVIZ) to '''display large 3D point clouds with uninterupted tought speed'''. OGSF + (wx)NVIZ should be able to rotate point cloud (i.e. LiDAR dataset) with 4 millions of points on medium hardware (i.e. 2GHz CPU with 2Gb RAM and GPU with hardware transform and lighting support and dedicated video RAM) with response time not greater than 1.0 second.
# Design and implement '''text displaying and styling in OGSF library''' and it's front-ends (NVIZ, [[wxNVIZ]]). Solution should be user configurable (fonts, colors, effects etc.) and multilanguage friendly.
# Design and implement user-provided '''symbol support in OGSF library''' and it's front-ends (NVIZ, [[wxNVIZ]]). Solution should support GRASS symbols, SVG, and/or simple EPS symbols.

# Drape multiple color maps over topography (equivalent to running r.patch or r.composite and draping the result; second raster is currently supported as transparency).

'''Willing to Mentor:''' [[User:Landa|Martin Landa]] (for 2), co-mentor for 1 and 4: Helena Mitasova, (''your name here'')

=== Volume modeling ===

# Develop '''r3.flow''' for computing 3D flow lines and 3D flow accumulation from 3D rasters
# Enhance volume interpolation module '''{{cmd|v.vol.rst}}''' for handling of data in space-time cube, including computation of gradients and hypercurvatures

'''Willing to Mentor:''' co-mentor Helena Mitasova, (''your name here'')

=== Other ===

* See also the [https://trac.osgeo.org/grass/query?status=assigned&status=new&status=reopened&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&type=enhancement GRASS wish list]

# 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 '''sophisticated Python scripting interface''' for GRASS based on [http://grass.osgeo.org/programming7/pythonlib.html GRASS Python Scripting Library]
# ''Your idea here''

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

== Guidelines for Students ==

How do you maximize your chances of getting picked? First read the [http://code.google.com/p/google-summer-of-code/wiki/AdviceforStudents Google SoC FAQ]. Then talk to us about your idea. Try emailing our [http://lists.osgeo.org/mailman/listinfo/grass-dev dev-mailing list], or come and talk to us in [[IRC]] (#grass). You can also reach the mentors directly by emailing:
* [http://lists.osgeo.org/mailman/listinfo/soc The OSGeo SoC mailing list]



* If you are thinking about applying, do make a point of reading the "[http://google-opensource.blogspot.co.nz/2011/02/flip-bits-not-burgers-student-guide.html Flip bits not Burgers: The Student's Guide to the Summer of Code]" eBook

=== Getting started with GRASS coding ===

* The source code is maintained in a [http://trac.osgeo.org/grass/browser/grass/trunk SVN server] which is easy to browse

* Please review the submitting files for our coding standards
** {{src|SUBMITTING|branch=trunk}} for C coding rules
** {{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]
: See also the [[Development|development section]] of the GRASS user's wiki

== Guidelines for Mentors ==

* Un(?)official book: http://www.booki.cc/gsoc-mentoring/
* Some more hints on the [http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2012_Administrative#Links OSGeo wiki]

== Accepted Ideas ==

# ''Project name''
#: Student: Your name here
#: Mentor: Your mentor's name here
#: Backup mentor: Your backup mentor's name here
#: Wiki page: wiki page maintained by you (typically in this GRASS wiki, or the trac development wiki)
# ''Project name''
#: Student: Someone else's name here
#: Mentor: Their mentor's name here
#: Backup mentor: Their backup mentor's name here
#: Wiki page: wiki page maintained by them (typically in this GRASS wiki, or the trac development wiki)

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

WxNviz

2011-11-28T00:05:17Z

⚠️Helena:

Back to [[WxPython-based GUI for GRASS|wxGUI]] page.

See also {{cmd|wxGUI.Nviz|version=70|desc=manual page}}.

'''wxNviz''' is a [[wxGUI]] extension which allows users to realistically render multiple surfaces (raster data) in a 3D space, optionally using thematic coloring, draping 2D vector data over the surfaces, displaying 3D vector data in the space, and visualization of volume data (3D raster data).
__TOC__
== Screenshots ==
<center>
<gallery perrow=3 widths=200>
Image:Wxnviz-alpha-0.png|2008-06-27: Display raster map from layer tree in 2.5D (surface)
Image:Wxnviz-alpha-1.png|2008-07-05: Support for vector data (2D lines) added
Image:Wxnviz-alpha-2.png|2008-07-26: Support for vector point data
Image:Wxnviz-alpha-3.png|2008-08-02: 3D vector data support
Image:Wxnviz-alpha-4.png|2008-08-09: Initial support for volumetric data
Image:Wxnviz-lmgr.png|2010-05-31: 3D view tools window integrated into Layer Manager
Image:Wxnviz-light.png|Lighting control panel in Layer Manager (2010-06-17)
Image:Wxnviz-fringe.png|Fringe control panel in Layer Manager (2010-06-23)
Image:Wxnviz-redirect.png|Redirect messages to wxGUI (2010-08-08)
Image:Wxnviz-volumes.png|Displaying raster (surface), 2D vector and 3D raster (volume) in the 3D space (2010-08-16)
Image:WxNviz surface page.png|Surface page of WxNviz modified (2011-06-02)
Image:WxNviz_constant_surface_page.png|Constant surface page added (2011-06-02)
Image:WxNviz_lighting.png|Lighting fixed (2011-05-02)
Image:WxNviz_cutting_planes_1.png|Cutting planes (shading blend) (2011-06-10)
Image:WxNviz_cutting_planes_2.png|Cutting planes (shading top color) (2011-06-10)
Image:WxNviz_view_page.png|View page modified (2011-06-10)
Image:Nviz_cmd_cutting_planes.png‎|Picture of surfaces cut by two planes (generated by nviz_cmd) (2011-06-30)
Image:WxNviz_generate_command.png‎|Command for nviz_cmd generated by wxNviz (2011-07-01)
Image:WxNviz_north_arrow.png‎|North Arrow implemented (2011-07-08)
Image:WxNviz_volumes.png‎|Colored isosurfaces with transparency (2011-07-08)
Image:WxNviz_volume_slices_1.png‎|Partially transparent slice (2011-07-14)
Image:WxNviz_volume_slices_2.png‎|Combination of slices and isosurface (2011-07-14)
Image:WxNviz_overlays.png‎|Raster legend, text label and north arrow (2011-07-22)
Image:WxNviz_thematic_points_colors‎.png|Thematic mapping (colors) for points (2011-08-05)
Image:WxNviz_colorrules_dialog.png|Dialog for {{cmd|v.colors}} opened from 3D view (2011-08-05)
</gallery>
</center>
== Animations ==
{{YouTube|AByFPKHvgu4|desc=Using fly-through mode for creating animation}}

== Video tutorials ==

{{YouTube|ib1-mBbWkv4|desc=Loading data, settings layer properties}}
{{YouTube|ZLDstyumxv0|desc=Visualizing fringes and north arrow}}
{{YouTube|CmK-fEyf2SY|desc=3D raster maps (volumes) in the space (isosurface and slice mode)}}
{{YouTube|13wj5KWEweE|desc=Color thematic mapping}}

=== Older tutorials (2010) ===

{{YouTube|Ej_rBc9sgvE|desc=Loading data, settings layer properties}}
{{YouTube|iWyaBL2Krto|desc=Visualizing fringes}}
{{YouTube|ioE_hHMHqKg|desc=3D raster maps (volumes) in the space}}

== Ideas ==

* Fog support (see [http://gpwiki.org/index.php/OpenGL:Tutorials:Tutorial_Framework:Light_and_Fog], [http://www.swiftless.com/tutorials/opengl/fog.html], [http://nehe.gamedev.net/data/lessons/lesson.asp?lesson=16])
* Vertical labels (take from geonames.org point data): like in http://tev.fbk.eu/marmota/blog/?p=82
* Second interactive light source for isosurface visualization
* Tick marks and coordinate values to x,y,z axis when drawing fringe

<strike></strike>

== Known issues ==

#List of [http://trac.osgeo.org/grass/query?status=assigned&status=new&status=reopened&order=priority&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&keywords=~wxNviz open] and [http://trac.osgeo.org/grass/query?status=assigned&status=closed&order=priority&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&keywords=~wxNviz closed] tickets
#<strike>Adding vector data crashes wxGUI on Mac</strike>
#<strike>Viewing height sometimes sets to 1 after switching to 2D and back to 3D View (or with the simultaneous 2D view - very nice feature) and even after View is reset, it keeps getting back at 1 each time the slider is touched</strike>
#:Fixed in {{rev|46208}}
#Isosurfaces tested with Nags Head time series data (I will provide link) don't seem to be working, after setting 3D region and adding 3D raster nothing gets drawn, when moving the related DEM around only line rectangle shows instead of a box.
#Adding draw, draw current and clear button may be useful
#Thematic mapping is available in GRASS 7 only
#Display region in 3D does not change accordingly to display region in 2D in version <= 6.5
#Appearance:
## I need to click View tab to get the arrow draw, same for the scale bar
##add legend > OK: nothing gets drawn in 3D but the legend shows up when I switch to 2D but when I clicked delete scalebar (which was not drawn), my surface disapeared but the legend showed up along with white and black background (which I assume was supposed to be transparent, because when I moved the legend the surface was under it - we already discussed this, it may be my problem, because it works for Michael).
#General
##<strike>when I go from 3D view to 2D and then back to 3D I lose most of my settings </strike>
##similarly, when I add volume to Map layers I lose my view settings and the 3D view goes back to default
#Volumes:
##change of region by g.region seems to be ignored (or I missed something), I had to restart GRASS with the new region to get the 3D region for volumes right. Given that the default top, botom is 1,0, if GRASS starts with the default 3D region settings volumes do not work because there is just one level.
##isosurfaces work with my terrestrial lidar data but the slices don't, it seems that it is due my resolution being 0.3m, when I change it to 1m I get at least some limited slicing
###this may be in ogsf becuase slices in nviz do not work with this data either
#changing color to constant did not change the color of the isosurface

[[Sv:Main Page/sv|sv:Main Page/sv]]

[[Pl:WxNviz/pl|pl:WxNviz/pl]]

[[Pl:WxNviz/pl|pl:WxNviz/pl]]

[[pl:WxNviz/pl|pl:WxNviz/pl]]

== Google Summer of Code ==

=== [[wxNviz GSoC 2008|2008]] ===

* [http://trac.osgeo.org/grass/wiki/SoCProjects#wxNvizdevelopmentforenhanced34Dvisualizationandanalysis Accepted Google Summer of Code 2008 project]

=== [[wxNviz GSoC 2010|2010]] ===

* [http://trac.osgeo.org/grass/wiki/SoCProjects#wxNvizdevelopmentforenhanced34Dvisualizationandanalysis Accepted Google Summer of Code 2010 project]

=== [[wxNviz GSoC 2011|2011]] ===

* [http://trac.osgeo.org/grass/wiki/SoCProjects#CompletionofwxGUINvizextensionfor3DdatavisualizationinGRASSGIS Accepted Google Summer of Code 2011 project]

== See also ==

* http://lists.osgeo.org/pipermail/grass-dev/2008-February/035792.html

{{WxGUI}}

WxNviz

2011-11-27T23:55:47Z

⚠️Helena: /* Known issues */

Back to [[WxPython-based GUI for GRASS|wxGUI]] page.

See also {{cmd|wxGUI.Nviz|version=70|desc=manual page}}.

'''wxNviz''' is a [[wxGUI]] extension which allows users to realistically render multiple surfaces (raster data) in a 3D space, optionally using thematic coloring, draping 2D vector data over the surfaces, displaying 3D vector data in the space, and visualization of volume data (3D raster data).
__TOC__
== Screenshots ==
<center>
<gallery perrow=3 widths=200>
Image:Wxnviz-alpha-0.png|2008-06-27: Display raster map from layer tree in 2.5D (surface)
Image:Wxnviz-alpha-1.png|2008-07-05: Support for vector data (2D lines) added
Image:Wxnviz-alpha-2.png|2008-07-26: Support for vector point data
Image:Wxnviz-alpha-3.png|2008-08-02: 3D vector data support
Image:Wxnviz-alpha-4.png|2008-08-09: Initial support for volumetric data
Image:Wxnviz-lmgr.png|2010-05-31: 3D view tools window integrated into Layer Manager
Image:Wxnviz-light.png|Lighting control panel in Layer Manager (2010-06-17)
Image:Wxnviz-fringe.png|Fringe control panel in Layer Manager (2010-06-23)
Image:Wxnviz-redirect.png|Redirect messages to wxGUI (2010-08-08)
Image:Wxnviz-volumes.png|Displaying raster (surface), 2D vector and 3D raster (volume) in the 3D space (2010-08-16)
Image:WxNviz surface page.png|Surface page of WxNviz modified (2011-06-02)
Image:WxNviz_constant_surface_page.png|Constant surface page added (2011-06-02)
Image:WxNviz_lighting.png|Lighting fixed (2011-05-02)
Image:WxNviz_cutting_planes_1.png|Cutting planes (shading blend) (2011-06-10)
Image:WxNviz_cutting_planes_2.png|Cutting planes (shading top color) (2011-06-10)
Image:WxNviz_view_page.png|View page modified (2011-06-10)
Image:Nviz_cmd_cutting_planes.png‎|Picture of surfaces cut by two planes (generated by nviz_cmd) (2011-06-30)
Image:WxNviz_generate_command.png‎|Command for nviz_cmd generated by wxNviz (2011-07-01)
Image:WxNviz_north_arrow.png‎|North Arrow implemented (2011-07-08)
Image:WxNviz_volumes.png‎|Colored isosurfaces with transparency (2011-07-08)
Image:WxNviz_volume_slices_1.png‎|Partially transparent slice (2011-07-14)
Image:WxNviz_volume_slices_2.png‎|Combination of slices and isosurface (2011-07-14)
Image:WxNviz_overlays.png‎|Raster legend, text label and north arrow (2011-07-22)
Image:WxNviz_thematic_points_colors‎.png|Thematic mapping (colors) for points (2011-08-05)
Image:WxNviz_colorrules_dialog.png|Dialog for {{cmd|v.colors}} opened from 3D view (2011-08-05)
</gallery>
</center>
== Animations ==
{{YouTube|AByFPKHvgu4|desc=Using fly-through mode for creating animation}}

== Video tutorials ==

{{YouTube|ib1-mBbWkv4|desc=Loading data, settings layer properties}}
{{YouTube|ZLDstyumxv0|desc=Visualizing fringes and north arrow}}
{{YouTube|CmK-fEyf2SY|desc=3D raster maps (volumes) in the space (isosurface and slice mode)}}
{{YouTube|13wj5KWEweE|desc=Color thematic mapping}}

=== Older tutorials (2010) ===

{{YouTube|Ej_rBc9sgvE|desc=Loading data, settings layer properties}}
{{YouTube|iWyaBL2Krto|desc=Visualizing fringes}}
{{YouTube|ioE_hHMHqKg|desc=3D raster maps (volumes) in the space}}

== Ideas ==

* Fog support (see [http://gpwiki.org/index.php/OpenGL:Tutorials:Tutorial_Framework:Light_and_Fog], [http://www.swiftless.com/tutorials/opengl/fog.html], [http://nehe.gamedev.net/data/lessons/lesson.asp?lesson=16])
* Vertical labels (take from geonames.org point data): like in http://tev.fbk.eu/marmota/blog/?p=82
* Second interactive light source for isosurface visualization
* Tick marks and coordinate values to x,y,z axis when drawing fringe

<strike></strike>

== Known issues ==

#List of [http://trac.osgeo.org/grass/query?status=assigned&status=new&status=reopened&order=priority&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&keywords=~wxNviz open] and [http://trac.osgeo.org/grass/query?status=assigned&status=closed&order=priority&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&keywords=~wxNviz closed] tickets
#<strike>Adding vector data crashes wxGUI on Mac</strike>
#<strike>Viewing height sometimes sets to 1 after switching to 2D and back to 3D View (or with the simultaneous 2D view - very nice feature) and even after View is reset, it keeps getting back at 1 each time the slider is touched</strike>
#:Fixed in {{rev|46208}}
#Isosurfaces tested with Nags Head time series data (I will provide link) don't seem to be working, after setting 3D region and adding 3D raster nothing gets drawn, when moving the related DEM around only line rectangle shows instead of a box.
#Adding draw, draw current and clear button may be useful
#Thematic mapping is available in GRASS 7 only
#Display region in 3D does not change accordingly to display region in 2D in version <= 6.5
#Appearance:
## I need to click View tab to get the arrow draw, same for the scale bar
##add legend > OK: nothing gets drawn in 3D but the legend shows up when I switch to 2D but when I clicked delete scalebar (which was not drawn), my surface disapeared but the legend showed up along with white and black background (which I assume was supposed to be transparent, because when I moved the legend the surface was under it - we already discussed this, it may be my problem, because it works for Michael).
#General
##when I go from 3D view to 2D and then back to 3D I lose most of my settings (viewing position, zexag, fringe size etc. - this would be OK if I could get a warning and question whether I want to save my 3D viewing state before switching)
##similarly, when I add volume to Map layers I lose my view settings and the 3D view goes back to default
#Volumes:
##change of region by g.region seems to be ignored (or I missed something), I had to restart GRASS with the new region to get the 3D region for volumes right. Given that the default top, botom is 1,0, if GRASS starts with the default 3D region settings volumes do not work because there is just one level.
##isosurfaces work with my terrestrial lidar data but the slices don't, it seems that it is due my resolution being 0.3m, when I change it to 1m I get at least some limited slicing
###this may be in ogsf becuase slices in nviz do not work with this data either
#changing color to constant did not change the color of the isosurface

[[Sv:Main Page/sv|sv:Main Page/sv]]

[[pl:WxNviz/pl|pl:WxNviz/pl]]

== Google Summer of Code ==

=== [[wxNviz GSoC 2008|2008]] ===

* [http://trac.osgeo.org/grass/wiki/SoCProjects#wxNvizdevelopmentforenhanced34Dvisualizationandanalysis Accepted Google Summer of Code 2008 project]

=== [[wxNviz GSoC 2010|2010]] ===

* [http://trac.osgeo.org/grass/wiki/SoCProjects#wxNvizdevelopmentforenhanced34Dvisualizationandanalysis Accepted Google Summer of Code 2010 project]

=== [[wxNviz GSoC 2011|2011]] ===

* [http://trac.osgeo.org/grass/wiki/SoCProjects#CompletionofwxGUINvizextensionfor3DdatavisualizationinGRASSGIS Accepted Google Summer of Code 2011 project]

== See also ==

* http://lists.osgeo.org/pipermail/grass-dev/2008-February/035792.html

{{WxGUI}}

Sample datasets

2011-09-20T03:20:39Z

⚠️Helena: /* New MAPSET Time_series_coast */

Most of GRASS's tutorials and help page examples are built around two sample datasets. You can {{website|download/data.php|download them from the GRASS website}} (or a {{website|mirrors.php|local mirror}})

* '''Spearfish, South Dakota''' - this dataset has been with GRASS for many years.

* '''North Carolina''' - this is a newly developed dataset with modern layers. (e.g. shortest path bus routing, SQL database queries)
** The original shapefiles for Wake county in the North Carolina dataset are available at [http://www.wakegov.com/gis/services/data.htm http://www.wakegov.com/gis/services/data.htm]
** Metadata for these shapefiles are available at [ftp://wakeftp.co.wake.nc.us/gis/Webdownloads/METADATA/ ftp://wakeftp.co.wake.nc.us/gis/Webdownloads/METADATA/]

If you would like to experiment with some local data, have a look at the [[Global datasets]] wiki page.

== Ideas for new datasets ==

=== Data organization ===

* provided as separate MAPSETS that can be inserted into nc_spm_08 or gisdemo_ncspm
* each MAPSET will have at least one example of application

=== Proposed new MAPSETS ===

* Road and street networks (nconemap, ncdot) from [http://www.ncdot.org/it/gis/DataDistribution/DOTData/default.html http://www.ncdot.org/it/gis/DataDistribution/DOTData/default.html]
* LRS road network, Integrated Statewide Road network, Bike Paths
* updated streets for wake [http://www.wakegov.com/gis/services/data.htm http://www.wakegov.com/gis/services/data.htm]
* add boundaries and POI for reference?
* include emergency centers ? hurricane evacuation routes? potential emergency shelters?
* include stream network?

==== New MAPSET Time_series_coast ====
* Coastal lidar point clouds, 1m res DEMs, 15 years in 10-15 snapshots, plus 1974 DEM for Jockey's Ridge,
aerial photos starting in 1936. The data set is rather complex with variable spatial coverage and time step,
(see the description) but should be useful for testing and teaching more complex analyses.
* mapset that includes DEMs and orthos for Jockey's ridge
http://courses.ncsu.edu/mea792/common/media/nc_coast_demseries.zip
http://courses.ncsu.edu/mea792/common/media/readme_nc_coast_demseries.txt
* to keep the mapset at reasonable size the raw x,y,z point clouds
are packaged separately, they can be imported with v.in.ascii or r.in.xyz
http://courses.ncsu.edu/mea792/common/media/nc_coast_pointseries.zip
* reference location for North Carolina with projection information (nc_spm_08 can also be used)
http://courses.ncsu.edu/mea792/common/media/gisdemo.zip
* "Getting started" with this data set assignment
http://courses.ncsu.edu/mea792/common/Assign_GISamodel/a_timeseries.html

(I will add a space-time cube practice soon).
* TODO: add 2009, 2010, 2011 lidar data and 2011 imagery
* smaller data set with DEMs only [http://courses.ncsu.edu/mea582/common/media/01/NagsHead_series.zip http://courses.ncsu.edu/mea582/common/media/01/NagsHead_series.zip]

==== New MAPSET Landuse_img ====
* new 4 channel 1m res 2009 imagery NAID
* new NLCD 2006 from USGS and NLCD2001
* 0.15m res ortho?
* Include any post storm, post hurricane, post flood imagery for training purposes? See example here: [http://www.ncdot.org/it/gis/DataDistribution/SpecialData/NCStormDamageAndCleanup.html http://www.ncdot.org/it/gis/DataDistribution/SpecialData/NCStormDamageAndCleanup.html]

==== New MAPSET Time_series_census ====
this may take more time to prepare

data are available for 1970,80,90,2000,2010

combine with election districts?

=== LOCATIONS ===
* Clean up and provide nc_ll, nc_utm, nc_spf for testing projections

=== EXTERNAL data sets for testing external data formats ===
* point cloud asci, las
* shape
* geodatabase?
* MRsid, geotiff?

==== Anything else from here? ====
* Course material [http://courses.ncsu.edu/mea582/common/GIS_anal_lecture/GIS_Anal_webdata.html http://courses.ncsu.edu/mea582/common/GIS_anal_lecture/GIS_Anal_webdata.html]
* Additional data for North Carolina [http://www.nconemap.com/Default.aspx?tabid=286 http://www.nconemap.com/Default.aspx?tabid=286]
* Additional data for Wake county in North Carolina [http://www.wakegov.com/gis/services/data.htm http://www.wakegov.com/gis/services/data.htm]

[[Category: Geodata]]

WxNviz

2011-07-01T02:28:22Z

⚠️Helena: /* Ideas */

Back to [[WxPython-based GUI for GRASS|wxGUI]] page.

See also {{cmd|wxGUI.Nviz|version=70}} manual page.

'''wxNviz''' is a [[wxGUI]] extension which allows users to realistically render multiple surfaces (raster data) in a 3D space, optionally using thematic coloring, draping 2D vector data over the surfaces, displaying 3D vector data in the space, and visualization of volume data (3D raster data).
__TOC__
== Screenshots ==
<center>
{|
|-
| [[Image:Wxnviz-alpha-0.png|250px|thumb|2008-06-27: Display raster map from layer tree in 2.5D (surface)]] ||
[[Image:Wxnviz-alpha-1.png|250px|thumb|2008-07-05: Support for vector data (2D lines) added]]
|-
| [[Image:Wxnviz-alpha-2.png|250px|thumb|2008-07-26: Support for vector point data]] ||
[[Image:Wxnviz-alpha-3.png|250px|thumb|2008-08-02: 3D vector data support]]
|-
| [[Image:Wxnviz-alpha-4.png|250px|thumb|2008-08-09: Initial support for volumetric data]] ||
[[Image:Wxnviz-lmgr.png|250px|thumb|2010-05-31: 3D view tools window integrated into Layer Manager]]
|-
| [[Image:Wxnviz-light.png|250px|thumb|center|Lighting control panel in Layer Manager (2010-06-17)]] ||
[[Image:Wxnviz-fringe.png|250px|thumb|center|Fringe control panel in Layer Manager (2010-06-23)]]
|-
| [[Image:Wxnviz-redirect.png|250px|thumb|center|Redirect messages to wxGUI (2010-08-08)]] ||
[[Image:Wxnviz-volumes.png|250px|thumb|center|Displaying raster (surface), 2D vector and 3D raster (volume) in the 3D space (2010-08-16)]]
|}
</center>

== HowTo ==

{{YouTube|Ej_rBc9sgvE|desc=Loading data, settings layer properties}}
{{YouTube|iWyaBL2Krto|desc=Visualizing fringes}}
{{YouTube|ioE_hHMHqKg|desc=3D raster maps (volumes) in the space}}

== Ideas ==

* Fog support (see [http://gpwiki.org/index.php/OpenGL:Tutorials:Tutorial_Framework:Light_and_Fog], [http://www.swiftless.com/tutorials/opengl/fog.html], [http://nehe.gamedev.net/data/lessons/lesson.asp?lesson=16])
* Vertical labels (take from geonames.org point data): like in http://tev.fbk.eu/marmota/blog/?p=82
* Second interactive light source for isosurface visualization
* Tick marks and coordinate values to x,y,z axis when drawing fringe

== Known issues ==

# List of [http://trac.osgeo.org/grass/query?status=assigned&status=new&status=reopened&order=priority&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&keywords=~wxNviz open] and [http://trac.osgeo.org/grass/query?status=assigned&status=closed&order=priority&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&keywords=~wxNviz closed] tickets
# Light settings do not work on Mac
# Adding vector data crashes wxGUI on Mac
# Rendering at fine resolution works only when changing viewing position or clicking the buttons that increase the numbers for perspective, twist, height and z-exag. Moving sliders does the required change but there is no redraw to full resolution
# Viewing height sometimes sets to 1 after switching to 2D and back to 3D View (or with the simultaneous 2D view - very nice feature) and even after View is reset, it keeps getting back at 1 each time the slider is touched
#:Hopefully fixed in {{rev|46208}}
# Typing in the height or z-exag numbers and ENTER does not do anything but the typed number gets accepted after clicking on the increase/decrease button, it is not possible to set the height value beyond the initial maximum
# Adding fringe just flashes it but it does not stay
# Isosurfaces tested with Nags Head time series data (I will provide link) don't seem to be working, after setting 3D region and adding 3D raster nothing gets drawn, when moving the related DEM around only line rectangle shows instead of a box.
# Adding draw, draw current and clear button may be useful

==Missing features==

* cutting planes for multiple surfaces
* 3D points with multiple attributes

== Google Summer of Code ==

=== [[wxNviz GSoC 2008|2008]] ===

* [http://trac.osgeo.org/grass/wiki/SoCProjects#wxNvizdevelopmentforenhanced34Dvisualizationandanalysis Accepted Google Summer of Code 2008 project]

=== [[wxNviz GSoC 2010|2010]] ===

* [http://trac.osgeo.org/grass/wiki/SoCProjects#wxNvizdevelopmentforenhanced34Dvisualizationandanalysis Accepted Google Summer of Code 2010 project]

=== [[wxNviz GSoC 2011|2011]] ===

* [http://trac.osgeo.org/grass/wiki/SoCProjects#CompletionofwxGUINvizextensionfor3DdatavisualizationinGRASSGIS Accepted Google Summer of Code 2011 project]

== See also ==

* http://lists.osgeo.org/pipermail/grass-dev/2008-February/035792.html

{{WxGUI}}

Talk:GRASS Community Sprint Prague 2011

2011-05-31T19:22:07Z

⚠️Helena: /* Reports */

== Reports ==

=== [[User:Lucadelu|Luca Delucchi]] ===
* creation of v.pack and v.unpack modules add upload in GRASS addons (please test it add bug report) {{rev|46388}}
* fix a bug on pyModis with Stefano Cavallari, the library that I'll use for [[R.modis|r.modis]] [https://github.com/lucadelu/pyModis/commit/7369cf63140f611dc9b4a5e78820f6c333ecdcd6]
* implement a new class in pyModis to parse XML files of MODIS products [https://github.com/lucadelu/pyModis/commit/c4565cc61bed4f1f160222feb170933ba03956ab]
* create wiki page for my Google summer of code project [[R.modis|r.modis]]

=== [[User:Landa|Martin Landa]] ===

* Mediawiki youtube extension - http://lists.osgeo.org/pipermail/grass-user/2011-May/060863.html
* nviz_cmd: remove double parameter & cosmetics in params description - {{rev|46349}}
* wx.psmap moved from addons to the main repo (author: Anna Kratochvilova) - {{rev|46356}}
* various minor changes in wxGUI - {{rev|46392}}

=== Vaclav Petras ===

* wxGUI menu customization - {{rev|46397}}
* wxGUI GSelect height customization - {{rev|46397}}

=== [[User:Neteler|Markus Neteler]] ===
* Sponsor money management
* Nicer [http://grass.osgeo.org/donation.php donations page], together with Stefano Cavallari who implemented the Paypal connector
* r.mask: catch user error - [https://trac.osgeo.org/grass/changeset/46372 r46372]
* grass-addons/grass7/display/d.mon: fix missing Makefile - [https://trac.osgeo.org/grass/changeset/46370 r46370]
* [[Toolboxes]] assignment together with Helena Mitasova
*

=== Robert Szczepanek ===
* continued Polish translation

=== Milena Nowotarska ===
* continued Polish translation
* work on wxGUI menu improvements

=== Markus Metz ===
* r.mask: bug fixed for reclassed maps in 6.x - [https://trac.osgeo.org/grass/changeset/46345/ r46345], [https://trac.osgeo.org/grass/changeset/46346/ r46346]
* LiDAR, LAS handling: creation of import modules [r|v].in.lidar for the [http://www.liblas.org/ ASPRS LiDAR LAS format]
* GRASS 7 development
** time series, together with Helena Mitasova and Sören Gebbert (project leader): design of a true temporal GIS
** scalable vector topology, with Radim Blazek

=== [[User:Madi|Margherita Di Leo]] ===
* Scratch for r.stream GUI (GSoC Project) - [[Wx.stream_gsoc2011]]
* r.threshold: New module useful to find optimal threshold for stream extraction {{rev|46403}}

=== Andrea Antonello ===
* Generic OMS3/Java wrapper for GRASS modules for generic use in the java world.
* Complete description [http://jgrasstechtips.blogspot.com/2011/05/oms3-grass-modules-wrapper-at-prague.html here], since I didn't want to spam with images.

=== Sören Gebbert ===
* Implementing time as new dimension into GRASS GIS to create a true temporal GIS, together with Helena Mitasova and Markus Metz
* Implemented direct access to GRASS GIS 7 libraries (libgis, libraster, libvect, libdb, ...) from the Java programming language in [http://code.google.com/p/vtk-grass-bridge vtk-grass-bridge]
* Discussion about new approaches in grid and cloud computing with GRASS GIS, leaded by Peter Loewe
* Designing a new test suite and test frame work for GRASS GIS, together with Anne Ghisla
* New approaches in web processing services and GRASS GIS, together with Paweł Netzel and Luca Delucchi

=== Paweł Netzel ===
* work on wxGUI menu improvements

=== [[User:AnneGhisla | Anne Ghisla]] ===
* [[Test Suite]] proposal together with Sören Gebbert
* Added datatype check in r.mask Python script (GRASS7) [[https://trac.osgeo.org/grass/changeset/46379 | 46379]], porting GRASS6 shell script [[https://trac.osgeo.org/grass/changeset/46372 | 43672]]
* Google Summer of Code guidance for GRASS students and mentors who attended the sprint

=== [[User:Annalisapg | Annalisa Minelli]] ===
* Testing r.viewshed module and study of its integration in other visibility tools with Markus Metz
* Bugfixing in v.mainchannel code with Markus Neteler
* Begun translation of r.broscoe.sh module in python language using r.stream.* suite - python implementation of Van der Waerden statistical test

=== [[User:annakrat | Anna Kratochvilova]] ===
* Project plan for [[WxNviz GSoC 2011]] was discussed with mentors (Martin Landa, Helena Mitasova)
* Fixing bugs in [[wxNviz]]

===[[User:helena | Helena Mitasova]]===
* testing wxNviz status with Anna, setting priorities
* LiDAR, LAS format handling discussion with Markus Metz
* space time cube and voxel flowrouting capabilities with Markus Metz
* discussion about time series support with Soren Gebbert and Markus Metz
* toolbox organizatioon for r* commands with Markus Neteler
* r.mask and g3.region issues with Markus Neteler and Soeren Gebbert
* startup tutorials, wxGUI suggestions and testing options with Martin Landa

== Press release ==

Please see http://grass.osgeo.org/announces/community_sprint_prague2011.html

== Organizer's page ==

* Sponsors
** {{done}} [http://grass.osgeo.org/announces/donate-now.html Find] and coordinate them

* {{done}} ([http://geoinformatics.fsv.cvut.cz/gwiki/Room_B367 B367]) Hackfest Room
** {{done}} Wifi or switch(es)
** {{done}} extension cables
** {{done}} video projector
** {{done}} Opportunity to prepare coffee or likewise (if possible)

* Video broadcasting
** camera for streaming (maybe not needed)

* Accommodation
** {{done}} Reserve sufficient (cheap) rooms in advance
** {{done}} Find some really low budget places

* Social dinner
** {{done}} Sunday evening

* City tour
** {{done}} Consider one city walk event to get distracted :)

* Documentation
** {{done}} [[IRC]] broadcast on #grass
** [http://etherpad.osuosl.org/ Etherpad] for live notes
** Fotos
** '''Press release which includes the relevant sponsor names''' for newspapers and GRASS communication channels

=== Hints for the Preparation ===
* Very useful guide: http://wiki.osgeo.org/wiki/FOSS4G2007_Lessons_Learned

Toolboxes

2011-05-11T23:32:08Z

⚠️Helena: /* Raster */

* See [http://lists.osgeo.org/pipermail/grass-dev/2010-April/050210.html original post by Jarosław Jasiewicz]

* Discussion about the suitability of the proposed change on the [[Talk:GRASS_repository_layout_proposal|talk]] side of this wiki page; discussion of the possible method on this side of the page.

<pre>
Hi all!

That rather radical ideas I present here are rather for future, at least for GRASS 8,
but I'd like present it now for long-term reflection.

Probably all notice that for over two years there is big increase in add-on repository
(including me). There are modules of different quality: from fully GRASS toolsets,
to shell or python scripts, from actively developed tools to abandoned,
from all-purpose tools to very specialized etc. I also think that that activity
will be grown due to substitute shell script by python

Similar situation is in main GRASS branch: there are modules for all like conversion tools,
interpolation methods, georeferencing etc, and very specialized modules for very limited
group of users (like wild fire), there are also some modules out of date.

I'm not enthusiastic about moving new modules into main branch. Almost every module has
different coding style and it will lasting in future that GRASS would be difficult to maintain.
On the other hand some people complains that some interesting modules are only available as
add-ons (I assume for some reasons they cannot install it)

So my suggestion is to rearrange future GRASS form two layers (main branch/add-on) into
three layers architecture:

1) GRASS core layer: much limited limited than now, only GIS environment and basic,
all-puropse tools, slow changes, great stability
2) GRASS toolset layer: oficcial GRASS thematic tools and toolsets (like terrain analysis,
hydrological analysis, photo-interpretation, landscape analysis etc,) every toolset with its
maintainer, rapid development, new ready to use tools after quality control may appear here,
also some of current main branch tool shall be moved to that layer
3) GRASS community layer: everything else like experimental, actively development new tools,
that what do not pass quality control, simple scripts, etc....

What benefits:
for developers and contributors: much clear situation and better publication path.
Toolset layer should be much more open for new tools than current GRASS main branch

for users: faster access to new tools.
There is no doubt that new tools are faster developed (less risk) than GRASS core
Binaries with toolsets could be maintained as separate apt/urpmi/pacman/yum/exe etc packages,
so it may appear in linux repository separetly form GRASS core.

There is only loose ideas. Most of them are of course taken from R (core/toolsets/rest of packages;
separate core and package development) but I think it is worth of some discuss ...

regards
Jarek
</pre>
__TOC__
== Repository layout ==
=== Current repository layout ===

<pre>
- grass
|- trunk
|- raster/
|- vector/
|- ...

- grass-addons
|- raster/
|- vector/
|- ...
</pre>

=== Proposed repository layout ===

<pre>
- grass
|- trunk
|- raster/
|- vector/
|- ...

- grass-tools
|- trunk
|- raster/
|- vector/
|- ...

- grass-addons
|- raster/
|- vector/
|- ...
</pre>

== Proposed toolboxes ==

'''Toolbox''' is a topic-based set of modules used for solving common GIS analysis, like hydrology, networking, LRS, etc. Toolbox should be easily installed by the user using {{cmd|g.extension|version=70}}

* add toolbox

g.extension toolbox=hydrology operation=add

Source code of the selected modules is downloaded from SVN, compiled and afterwards also installed to the user-specified (~/.grass7) or system (/usr/lib/grass7) directory.

Give the possibility with a flag (like -a) to install also modules from addons related that toolbox

g.extension -a toolbox=hydrology operation=add

* remove toolbox

g.extension toolbox=hydrology operation=remove

* list of modules of selected toolbox

g.extension -l toolbox=hydrology

User can also add/remove selected module

g.extension module=r.stream.angle operation=add

=== List of toolboxes ===
{|class="wikitable"
|'''Toolbox name''' || '''Toolbox code''' || '''Description'''||'''Correlate toolbox'''
|-
| ''3D Raster''
| R3
| All `r3.*` modules
|
|-
| ''3D Visualization''
| V3
| {{cmd|nviz_cmd|version=70}}
|
|-
| ''Cartography''
| CA
| {{cmd|ps.map|version=70}}, {{AddonCmd|ps.output}}
|
|-
| ''Database''
| DB
| All `db.*` modules
| ''Vector analysis''
|-
| ''Geostatistcal''
| GS
| {{cmd|v.krige|version=70}} maybe other
|
|-
| ''GUI''
| GI
| [[wxGUI]]
|
|-
| ''Hydrology''
| HY
| {{cmd|r.watershed|version=70}}, {{cmd|r.terraflow|version=70}}, `r.stream.*` modules in addons, maybe other, r.flow, r.sim.water, r.sim.sediment
| ''Raster analysis''
|-
| ''Imagery''
| IM
| All `i.*` modules, selected r.* modules
|
|-
| ''Landascape analysis''
| LA
| All `r.li.*` modules, maybe other
| ''Raster analysis''
|-
| ''Lidar analysis''
| LI
| All `v.lidar.*` modules, {{cmd|v.surf.bspline|version=70}}, r.in.xyz
|
|-
| ''Linear Reference Systems''
| LS
| All `v.lrs.*` modules
| ''Vector analysis''
|-
| ''Network analysis''
| NA
| All `v.net.*` modules, maybe other
| ''Vector analysis''
|-
| ''Raster analysis''
| RA
| A lot of basic `r.*` modules (like {{cmd|r.buffer,|version=70}} {{cmd|r.reclass|version=70}}, {{cmd|r.fillnull|version=70}}...)
|
|-
| ''Terrain analysis''
| TA
| Different kind of analysis: soil ({{cmd|r.sun,|version=70}}), terrain ({{cmd|r.slope.aspect|version=70}}, {{cmd|r.los|version=70}}), geomorphometry ({{cmd|r.param.scale|version=70}})
| ''Raster analysis''
|-
| ''Vector analysis''
| VA
| A lot of basic `v.*` modules (like {{cmd|v.buffer|version=70}}, {{cmd|v.centroid|version=70}}, {{cmd|v.overlay|version=70}}...)
| ''Database''
|}
HM comment: do we need import/export Toolbox for all of the specialized *.in* and *.out.* commands? gdal/ogr commands should be in core.

== List of modules (trunk) ==

=== Display ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|d.barscale|version=70}} || ? ||
|-
| {{cmd|d.colorlist|version=70}} || ? ||
|-
| {{cmd|d.colortable|version=70}} || ? ||
|-
| {{cmd|d.correlate|version=70}} || ? ||
|-
| {{cmd|d.erase|version=70}} || ? ||
|-
| {{cmd|d.font|version=70}} || ? ||
|-
| {{cmd|d.fontlist|version=70}} || ? ||
|-
| {{cmd|d.geodesic|version=70}} || ? ||
|-
| {{cmd|d.graph|version=70}} || ? ||
|-
| {{cmd|d.grid|version=70}} || ? ||
|-
| {{cmd|d.his|version=70}} || ? ||
|-
| {{cmd|d.histogram|version=70}} || ? ||
|-
| {{cmd|d.info|version=70}} || ? ||
|-
| {{cmd|d.labels|version=70}} || ? ||
|-
| {{cmd|d.legend|version=70}} || ? ||
|-
| {{cmd|d.linegraph|version=70}} || ? ||
|-
| {{cmd|d.nviz|version=70}} || ? ||
|-
| {{cmd|d.path|version=70}} || ? ||
|-
| {{cmd|d.polar|version=70}} || ? ||
|-
| {{cmd|d.profile|version=70}} || ? ||
|-
| {{cmd|d.rast|version=70}} || ? ||
|-
| {{cmd|d.rast.arrow|version=70}} || ? ||
|-
| {{cmd|d.rast.edit|version=70}} || ? ||
|-
| {{cmd|d.rast.leg|version=70}} || ? ||
|-
| {{cmd|d.rast.num|version=70}} || ? ||
|-
| {{cmd|d.rgb|version=70}} || ? ||
|-
| {{cmd|d.rhumbline|version=70}} || ? ||
|-
| {{cmd|d.shadedmap|version=70}} || ? ||
|-
| {{cmd|d.text|version=70}} || ? ||
|-
| {{cmd|d.thematic.area|version=70}} || ? ||
|-
| {{cmd|d.title|version=70}} || ? ||
|-
| {{cmd|d.vect|version=70}} || ? ||
|-
| {{cmd|d.vect.chart|version=70}} || ? ||
|-
| {{cmd|d.vect.thematic|version=70}} || ? ||
|-
| {{cmd|d.where|version=70}} || ? ||
|-
|}

=== Database ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|db.columns|version=70}} || ? ||
|-
| {{cmd|db.connect|version=70}} || ? ||
|-
| {{cmd|db.copy|version=70}} || ? ||
|-
| {{cmd|db.createdb|version=70}} || ? ||
|-
| {{cmd|db.databases|version=70}} || ? ||
|-
| {{cmd|db.describe|version=70}} || ? ||
|-
| {{cmd|db.drivers|version=70}} || ? ||
|-
| {{cmd|db.dropcolumn|version=70}} || ? ||
|-
| {{cmd|db.dropdb|version=70}} || ? ||
|-
| {{cmd|db.droptable|version=70}} || ? ||
|-
| {{cmd|db.droptable|version=70}} || ? ||
|-
| {{cmd|db.execute|version=70}} || ? ||
|-
| {{cmd|db.in.ogr|version=70}} || ? ||
|-
| {{cmd|db.login|version=70}} || ? ||
|-
| {{cmd|db.out.ogr|version=70}} || ? ||
|-
| {{cmd|db.select|version=70}} || ? ||
|-
| {{cmd|db.tables|version=70}} || ? ||
|-
| {{cmd|db.test|version=70}} || ? ||
|-
|}

=== General ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|g.access|version=70}} || C ||
|-
| {{cmd|g.cairocomp|version=70}} || C ||
|-
| {{cmd|g.copy|version=70}} || C ||
|-
| {{cmd|g.dirseps|version=70}} || C ||
|-
| {{cmd|g.extension|version=70}} || C ||
|-
| {{cmd|g.filename|version=70}} || C ||
|-
| {{cmd|g.findetc|version=70}} || C ||
|-
| {{cmd|g.findfile|version=70}} || C ||
|-
| {{cmd|g.gisenv|version=70}} || C ||
|-
| {{cmd|g.gui|version=70}} || C ||
|-
| {{cmd|g.list|version=70}} || C ||
|-
| {{cmd|g.manual|version=70}} || C ||
|-
| {{cmd|g.mapset|version=70}} || C ||
|-
| {{cmd|g.mapsets|version=70}} || C ||
|-
| {{cmd|g.message|version=70}} || C ||
|-
| {{cmd|g.mkfontcap|version=70}} || C ||
|-
| {{cmd|g.mlist|version=70}} || C ||
|-
| {{cmd|g.mremove|version=70}} || C ||
|-
| {{cmd|g.parser|version=70}} || C ||
|-
| {{cmd|g.pnmcomp|version=70}} || C ||
|-
| {{cmd|g.ppmtopng|version=70}} || C ||
|-
| {{cmd|g.proj|version=70}} || C ||
|-
| {{cmd|g.region|version=70}} || C ||
|-
| {{cmd|g.remove|version=70}} || C ||
|-
| {{cmd|g.rename|version=70}} || C ||
|-
| {{cmd|g.tempfile|version=70}} || C ||
|-
| {{cmd|g.transform|version=70}} || C ||
|-
| {{cmd|g.version|version=70}} || C ||
|-
|}

=== Imagery ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|i.albedo|version=70}} || ? ||
|-
| {{cmd|i.atcorr|version=70}} || ? ||
|-
| {{cmd|i.biomass|version=70}} || ? ||
|-
| {{cmd|i.cca|version=70}} || ? ||
|-
| {{cmd|i.cluster|version=70}} || ? ||
|-
| {{cmd|i.eb.eta|version=70}} || ? ||
|-
| {{cmd|i.eb.evapfr|version=70}} || ? ||
|-
| {{cmd|i.eb.h_SEBAL01|version=70}} || ? ||
|-
| {{cmd|i.eb.soilheatflux|version=70}} || ? ||
|-
| {{cmd|i.emissivity|version=70}} || ? ||
|-
| {{cmd|i.evapo.time|version=70}} || ? ||
|-
| {{cmd|i.fft|version=70}} || ? ||
|-
| {{cmd|i.fusion.brovey|version=70}} || ? ||
|-
| {{cmd|i.gensig|version=70}} || ? ||
|-
| {{cmd|i.gensigset|version=70}} || ? ||
|-
| {{cmd|i.group|version=70}} || ? ||
|-
| {{cmd|i.his.rgb|version=70}} || ? ||
|-
| {{cmd|i.ifft|version=70}} || ? ||
|-
| {{cmd|i.image.mosaic|version=70}} || ? ||
|-
| {{cmd|i.in.spotvgt|version=70}} || ? ||
|-
| {{cmd|i.landsat.rgb|version=70}} || ? ||
|-
| {{cmd|i.latlong|version=70}} || ? ||
|-
| {{cmd|i.maxlik|version=70}} || ? ||
|-
| {{cmd|i.modis.qc|version=70}} || ? ||
|-
| {{cmd|i.oif|version=70}} || ? ||
|-
| {{cmd|i.pca|version=70}} || ? ||
|-
| {{cmd|i.rectify|version=70}} || ? ||
|-
| {{cmd|i.rgb.his|version=70}} || ? ||
|-
| {{cmd|i.smap|version=70}} || ? ||
|-
| {{cmd|i.spectral|version=70}} || ? ||
|-
| {{cmd|i.sunhours|version=70}} || ? ||
|-
| {{cmd|i.target|version=70}} || ? ||
|-
| {{cmd|i.tasscap|version=70}} || ? ||
|-
| {{cmd|i.vi|version=70}} || ? ||
|-
| {{cmd|i.zc|version=70}} || ? ||
|-
|}

=== Misc ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|m.cogo|version=70}} || ? ||
|-
| {{cmd|m.measure|version=70}} || ? ||
|-
| {{cmd|m.proj|version=70}} || ? ||
|-
|}

=== Postscript ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|ps.map|version=70}} || ? ||
|-
|}

=== Raster ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|r.basins.fill|version=70}} || ? ||
|-
| {{cmd|r.bitpattern|version=70}} || ? ||
|-
| {{cmd|r.blend|version=70}} || ? ||
|-
| {{cmd|r.buffer|version=70}} || ? ||
|-
| {{cmd|r.buffer2|version=70}} || ? ||
|-
| {{cmd|r.carve|version=70}} || T ||TA
|-
| {{cmd|r.category|version=70}} || ? ||
|-
| {{cmd|r.circle|version=70}} || ? ||
|-
| {{cmd|r.clump|version=70}} || ? ||
|-
| {{cmd|r.coin|version=70}} || ? ||
|-
| {{cmd|r.colors|version=70}} || C ||
|-
| {{cmd|r.colors.out|version=70}} || ? ||
|-
| {{cmd|r.colors.stddev|version=70}} || ? ||
|-
| {{cmd|r.composite|version=70}} || ? ||
|-
| {{cmd|r.compress|version=70}} || ? ||
|-
| {{cmd|r.contour|version=70}} || C ||
|-
| {{cmd|r.cost|version=70}} || ? ||
|-
| {{cmd|r.covar|version=70}} || ? ||
|-
| {{cmd|r.cross|version=70}} || ? ||
|-
| {{cmd|r.describe|version=70}} || ? ||
|-
| {{cmd|r.distance|version=70}} || ? ||
|-
| {{cmd|r.drain|version=70}} || ? ||
|-
| {{cmd|r.external|version=70}} || ? ||
|-
| {{cmd|r.external.out|version=70}} || ? ||
|-
| {{cmd|r.fill.dir|version=70}} || ? ||
|-
| {{cmd|r.fillnulls|version=70}} || ? ||
|-
| {{cmd|r.flow|version=70}} || T ||HY
|-
| {{cmd|r.grow|version=70}} || ? ||
|-
| {{cmd|r.grow.distance|version=70}} || ? ||
|-
| {{cmd|r.gwflow|version=70}} || T ||HY
|-
| {{cmd|r.his|version=70}} || ? ||
|-
| {{cmd|r.horizon|version=70}} || ? ||
|-
| {{cmd|r.in.arc|version=70}} || ? ||
|-
| {{cmd|r.in.ascii|version=70}} || ? ||
|-
| {{cmd|r.in.aster|version=70}} || ? ||
|-
| {{cmd|r.in.bin|version=70}} || ? ||
|-
| {{cmd|r.in.gdal|version=70}} || ? ||
|-
| {{cmd|r.in.gridatb|version=70}} || ? ||
|-
| {{cmd|r.in.mat|version=70}} || ? ||
|-
| {{cmd|r.in.png|version=70}} || ? ||
|-
| {{cmd|r.in.poly|version=70}} || ? ||
|-
| {{cmd|r.in.srtm|version=70}} || ? ||
|-
| {{cmd|r.in.wms|version=70}} || ? ||
|-
| {{cmd|r.in.xyz|version=70}} || C ||
|-
| {{cmd|r.info|version=70}} || C ||
|-
| {{cmd|r.kappa|version=70}} || ? ||
|-
| {{cmd|r.lake|version=70}} || T ||HY
|-
| {{cmd|r.li.cwed|version=70}} || ? ||
|-
| {{cmd|r.li.dominance|version=70}} || ? ||
|-
| {{cmd|r.li.edgedensity|version=70}} || ? ||
|-
| {{cmd|r.li.mpa|version=70}} || ? ||
|-
| {{cmd|r.li.mps|version=70}} || ? ||
|-
| {{cmd|r.li.padcv|version=70}} || ? ||
|-
| {{cmd|r.li.padrange|version=70}} || ? ||
|-
| {{cmd|r.li.padsd|version=70}} || ? ||
|-
| {{cmd|r.li.patchdensity|version=70}} || ? ||
|-
| {{cmd|r.li.patchnum|version=70}} || ? ||
|-
| {{cmd|r.li.richness|version=70}} || ? ||
|-
| {{cmd|r.li.shannon|version=70}} || ? ||
|-
| {{cmd|r.li.shape|version=70}} || ? ||
|-
| {{cmd|r.li.simpson|version=70}} || ? ||
|-
| {{cmd|r.los|version=70}} || T||TA
|-
| {{cmd|r.mapcalc|version=70}} || C ||
|-
| {{cmd|r.mask|version=70}} || C ||
|-
| {{cmd|r.mfilter|version=70}} || ? ||
|-
| {{cmd|r.mode|version=70}} || ? ||
|-
| {{cmd|r.neighbors|version=70}} || C ||
|-
| {{cmd|r.null|version=70}} || C ||
|-
| {{cmd|r.out.arc|version=70}} || ? ||
|-
| {{cmd|r.out.ascii|version=70}} || ? ||
|-
| {{cmd|r.out.bin|version=70}} || ? ||
|-
| {{cmd|r.out.gdal|version=70}} || ? ||
|-
| {{cmd|r.out.gridatb|version=70}} || ? ||
|-
| {{cmd|r.out.mat|version=70}} || ? ||
|-
| {{cmd|r.out.mpeg|version=70}} || ? ||
|-
| {{cmd|r.out.png|version=70}} || ? ||
|-
| {{cmd|r.out.pov|version=70}} || ? ||
|-
| {{cmd|r.out.ppm|version=70}} || ? ||
|-
| {{cmd|r.out.ppm3|version=70}} || ? ||
|-
| {{cmd|r.out.tiff|version=70}} || ? ||
|-
| {{cmd|r.out.vrml|version=70}} || ? ||
|-
| {{cmd|r.out.vtk|version=70}} || ? ||
|-
| {{cmd|r.out.xyz|version=70}} || ? ||
|-
| {{cmd|r.param.scale|version=70}} || T ||TA
|-
| {{cmd|r.patch|version=70}} || C ||
|-
| {{cmd|r.plane|version=70}} || ? ||
|-
| {{cmd|r.profile|version=70}} || ? ||
|-
| {{cmd|r.proj|version=70}} || C ||
|-
| {{cmd|r.quant|version=70}} || ? ||
|-
| {{cmd|r.quantile|version=70}} || ? ||
|-
| {{cmd|r.random|version=70}} || ? ||
|-
| {{cmd|r.random.cells|version=70}} || ? ||
|-
| {{cmd|r.random.surface|version=70}} || ? ||
|-
| {{cmd|r.reclass|version=70}} || ? ||
|-
| {{cmd|r.reclass.area|version=70}} || ? ||
|-
| {{cmd|r.recode|version=70}} || C ||
|-
| {{cmd|r.region|version=70}} || ? ||
|-
| {{cmd|r.regression.line|version=70}} || C ||
|-
| {{cmd|r.report|version=70}} || C||
|-
| {{cmd|r.resamp.bspline|version=70}} || C ||
|-
| {{cmd|r.resamp.filter|version=70}} || ? ||
|-
| {{cmd|r.resamp.interp|version=70}} || C ||
|-
| {{cmd|r.resamp.rst|version=70}} || ? ||
|-
| {{cmd|r.resamp.stats|version=70}} || ? ||
|-
| {{cmd|r.resample|version=70}} || ? ||
|-
| {{cmd|r.rescale|version=70}} || ? ||
|-
| {{cmd|r.rescale.eq|version=70}} || ? ||
|-
| {{cmd|r.ros|version=70}} || ? ||
|-
| {{cmd|r.series|version=70}} || C ||
|-
| {{cmd|r.shaded.relief|version=70}} || C ||
|-
| {{cmd|r.sim.sediment|version=70}} || T ||HY
|-
| {{cmd|r.sim.water|version=70}} || T ||HY
|-
| {{cmd|r.slope.aspect|version=70}} || T ||TA
|-
| {{cmd|r.solute.transport|version=70}} || T ||?
|-
| {{cmd|r.spread|version=70}} || ? ||
|-
| {{cmd|r.spreadpath|version=70}} || ? ||
|-
| {{cmd|r.statistics|version=70}} || ? ||
|-
| {{cmd|r.statistics2|version=70}} || ? ||
|-
| {{cmd|r.statistics3|version=70}} || ? ||
|-
| {{cmd|r.stats|version=70}} || ? ||
|-
| {{cmd|r.sun|version=70}} || T ||TA
|-
| {{cmd|r.sunmask|version=70}} || ? ||
|-
| {{cmd|r.support|version=70}} || C||
|-
| {{cmd|r.support.stats|version=70}} || ? ||
|-
| {{cmd|r.surf.area|version=70}} || ? ||
|-
| {{cmd|r.surf.contour|version=70}} || ? ||
|-
| {{cmd|r.surf.fractal|version=70}} || ? ||
|-
| {{cmd|r.surf.gauss|version=70}} || ? ||
|-
| {{cmd|r.surf.idw|version=70}} || ? ||
|-
| {{cmd|r.surf.idw2|version=70}} || ? ||
|-
| {{cmd|r.surf.random|version=70}} || ? ||
|-
| {{cmd|r.terraflow|version=70}} || T ||HY
|-
| {{cmd|r.texture|version=70}} || ? ||
|-
| {{cmd|r.thin|version=70}} || C ||
|-
| {{cmd|r.tileset|version=70}} || ? ||
|-
| {{cmd|r.timestamp|version=70}} || C ||
|-
| {{cmd|r.to.rast3|version=70}} || C ||
|-
| {{cmd|r.to.rast3elev|version=70}} || ? ||
|-
| {{cmd|r.to.vect|version=70}} || C ||
|-
| {{cmd|r.topidx|version=70}} || T ||HY
|-
| {{cmd|r.topmodel|version=70}} || T ||HY
|-
| {{cmd|r.transect|version=70}} || ? ||
|-
| {{cmd|r.univar|version=70}} || C ||
|-
| {{cmd|r.uslek|version=70}} || T ||HY
|-
| {{cmd|r.usler|version=70}} || T ||HY
|-
| {{cmd|r.volume|version=70}} || ? ||
|-
| {{cmd|r.walk|version=70}} || ? ||
|-
| {{cmd|r.water.outlet|version=70}} || T||HY
|-
| {{cmd|r.watershed|version=70}} || T ||HY
|-
| {{cmd|r.what|version=70}} || C ||
|-
| {{cmd|r.what.color|version=70}} || ? ||
|-
|}

=== 3D raster ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|r3.cross.rast|version=70}} || T || 3D Raster
|-
| {{cmd|r3.gwflow|version=70}} || T || 3D Raster
|-
| {{cmd|r3.in.ascii|version=70}} || T || 3D Raster
|-
| {{cmd|r3.in.v5d|version=70}} || T || 3D Raster
|-
| {{cmd|r3.info|version=70}} || T || 3D Raster
|-
| {{cmd|r3.mapcalc|version=70}} || T || 3D Raster
|-
| {{cmd|r3.mask|version=70}} || T || 3D Raster
|-
| {{cmd|r3.mkdspf|version=70}} || T || 3D Raster
|-
| {{cmd|r3.null|version=70}} || T || 3D Raster
|-
| {{cmd|r3.out.ascii|version=70}} || T || 3D Raster
|-
| {{cmd|r3.out.v5d|version=70}} || T || 3D Raster
|-
| {{cmd|r3.out.vtk|version=70}} || T || 3D Raster
|-
| {{cmd|r3.stats|version=70}} || T || 3D Raster
|-
| {{cmd|r3.timestamp|version=70}} || T || 3D Raster
|-
| {{cmd|r3.to.rast|version=70}} || T || 3D Raster
|-
| {{cmd|r3.univar|version=70}} || T || 3D Raster
|-
|}

=== Vector ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|v.autokrige|version=70}} || ? ||
|-
| {{cmd|v.buffer|version=70}} || ? ||
|-
| {{cmd|v.build|version=70}} || ? ||
|-
| {{cmd|v.build.all|version=70}} || ? ||
|-
| {{cmd|v.build.polylines|version=70}} || ? ||
|-
| {{cmd|v.category|version=70}} || ? ||
|-
| {{cmd|v.centroids|version=70}} || ? ||
|-
| {{cmd|v.class|version=70}} || ? ||
|-
| {{cmd|v.clean|version=70}} || ? ||
|-
| {{cmd|v.colors|version=70}} || ? ||
|-
| {{cmd|v.convert|version=70}} || ? ||
|-
| {{cmd|v.convert.all|version=70}} || ? ||
|-
| {{cmd|v.db.addcolumn|version=70}} || ? ||
|-
| {{cmd|v.db.addtable|version=70}} || ? ||
|-
| {{cmd|v.db.connect|version=70}} || ? ||
|-
| {{cmd|v.db.dropcolumn|version=70}} || ? ||
|-
| {{cmd|v.db.droprow|version=70}} || ? ||
|-
| {{cmd|v.db.droptable|version=70}} || ? ||
|-
| {{cmd|v.db.join|version=70}} || ? ||
|-
| {{cmd|v.db.reconnect.all|version=70}} || ? ||
|-
| {{cmd|v.db.renamecolumn|version=70}} || ? ||
|-
| {{cmd|v.db.select|version=70}} || ? ||
|-
| {{cmd|v.db.univar|version=70}} || ? ||
|-
| {{cmd|v.db.update|version=70}} || ? ||
|-
| {{cmd|v.delaunay|version=70}} || ? ||
|-
| {{cmd|v.dissolve|version=70}} || ? ||
|-
| {{cmd|v.distance|version=70}} || ? ||
|-
| {{cmd|v.drape|version=70}} || ? ||
|-
| {{cmd|v.edit|version=70}} || ? ||
|-
| {{cmd|v.external|version=70}} || ? ||
|-
| {{cmd|v.extract|version=70}} || ? ||
|-
| {{cmd|v.extrude|version=70}} || ? ||
|-
| {{cmd|v.generalize|version=70}} || ? ||
|-
| {{cmd|v.hull|version=70}} || ? ||
|-
| {{cmd|v.in.ascii|version=70}} || ? ||
|-
| {{cmd|v.in.db|version=70}} || ? ||
|-
| {{cmd|v.in.dxf|version=70}} || ? ||
|-
| {{cmd|v.in.e00|version=70}} || ? ||
|-
| {{cmd|v.in.geonames|version=70}} || ? ||
|-
| {{cmd|v.in.gns|version=70}} || ? ||
|-
| {{cmd|v.in.lines|version=70}} || ? ||
|-
| {{cmd|v.in.mapgen|version=70}} || ? ||
|-
| {{cmd|v.in.ogr|version=70}} || ? ||
|-
| {{cmd|v.in.postgis|version=70}} || ? ||
|-
| {{cmd|v.in.region|version=70}} || ? ||
|-
| {{cmd|v.in.sites|version=70}} || ? ||
|-
| {{cmd|v.in.sites.all|version=70}} || ? ||
|-
| {{cmd|v.in.wfs|version=70}} || ? ||
|-
| {{cmd|v.info|version=70}} || ? ||
|-
| {{cmd|v.kcv|version=70}} || ? ||
|-
| {{cmd|v.kernel|version=70}} || ? ||
|-
| {{cmd|v.krige|version=70}} || ? ||
|-
| {{cmd|v.label|version=70}} || ? ||
|-
| {{cmd|v.lidar.correction|version=70}} || ? ||
|-
| {{cmd|v.lidar.edgedetection|version=70}} || ? ||
|-
| {{cmd|v.lidar.growing|version=70}} || ? ||
|-
| {{cmd|v.lrs.create|version=70}} || ? ||
|-
| {{cmd|v.lrs.label|version=70}} || ? ||
|-
| {{cmd|v.lrs.segment|version=70}} || ? ||
|-
| {{cmd|v.lrs.where|version=70}} || ? ||
|-
| {{cmd|v.mkgrid|version=70}} || ? ||
|-
| {{cmd|v.neighbors|version=70}} || ? ||
|-
| {{cmd|v.net|version=70}} || ? ||
|-
| {{cmd|v.net.alloc|version=70}} || ? ||
|-
| {{cmd|v.net.allpairs|version=70}} || ? ||
|-
| {{cmd|v.net.bridge|version=70}} || ? ||
|-
| {{cmd|v.net.centrality|version=70}} || ? ||
|-
| {{cmd|v.net.components|version=70}} || ? ||
|-
| {{cmd|v.net.connectivity|version=70}} || ? ||
|-
| {{cmd|v.net.distance|version=70}} || ? ||
|-
| {{cmd|v.net.flow|version=70}} || ? ||
|-
| {{cmd|v.net.iso|version=70}} || ? ||
|-
| {{cmd|v.net.path|version=70}} || ? ||
|-
| {{cmd|v.net.salesman|version=70}} || ? ||
|-
| {{cmd|v.net.spanningtree|version=70}} || ? ||
|-
| {{cmd|v.net.steiner|version=70}} || ? ||
|-
| {{cmd|v.net.timetable|version=70}} || ? ||
|-
| {{cmd|v.net.visibility|version=70}} || ? ||
|-
| {{cmd|v.normal|version=70}} || ? ||
|-
| {{cmd|v.out.ascii|version=70}} || ? ||
|-
| {{cmd|v.out.dxf|version=70}} || ? ||
|-
| {{cmd|v.out.gps|version=70}} || ? ||
|-
| {{cmd|v.out.ogr|version=70}} || ? ||
|-
| {{cmd|v.out.postgis|version=70}} || ? ||
|-
| {{cmd|v.out.pov|version=70}} || ? ||
|-
| {{cmd|v.out.svg|version=70}} || ? ||
|-
| {{cmd|v.out.vtk|version=70}} || ? ||
|-
| {{cmd|v.outlier|version=70}} || ? ||
|-
| {{cmd|v.overlay|version=70}} || ? ||
|-
| {{cmd|v.parallel|version=70}} || ? ||
|-
| {{cmd|v.patch|version=70}} || ? ||
|-
| {{cmd|v.perturb|version=70}} || ? ||
|-
| {{cmd|v.proj|version=70}} || ? ||
|-
| {{cmd|v.qcount|version=70}} || ? ||
|-
| {{cmd|v.random|version=70}} || ? ||
|-
| {{cmd|v.rast.stats|version=70}} || ? ||
|-
| {{cmd|v.reclass|version=70}} || ? ||
|-
| {{cmd|v.report|version=70}} || ? ||
|-
| {{cmd|v.sample|version=70}} || ? ||
|-
| {{cmd|v.segment|version=70}} || ? ||
|-
| {{cmd|v.select|version=70}} || ? ||
|-
| {{cmd|v.split|version=70}} || ? ||
|-
| {{cmd|v.support|version=70}} || ? ||
|-
| {{cmd|v.surf.bspline|version=70}} || ? ||
|-
| {{cmd|v.surf.idw|version=70}} || ? ||
|-
| {{cmd|v.surf.rst|version=70}} || ? ||
|-
| {{cmd|v.to.3d|version=70}} || ? ||
|-
| {{cmd|v.to.db|version=70}} || ? ||
|-
| {{cmd|v.to.points|version=70}} || ? ||
|-
| {{cmd|v.to.rast|version=70}} || ? ||
|-
| {{cmd|v.to.rast3|version=70}} || ? ||
|-
| {{cmd|v.transform|version=70}} || ? ||
|-
| {{cmd|v.type|version=70}} || ? ||
|-
| {{cmd|v.univar|version=70}} || ? ||
|-
| {{cmd|v.vol.rst|version=70}} || ? ||
|-
| {{cmd|v.voronoi|version=70}} || ? ||
|-
| {{cmd|v.what|version=70}} || ? ||
|-
| {{cmd|v.what.rast|version=70}} || ? ||
|-
| {{cmd|v.what.vect|version=70}} || ? ||
|-
|}

=== Various ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|nviz|version=70}} || ? ||
|-
| {{cmd|nviz_cmd|version=70}} || ? ||
|-
| {{cmd|wximgview|version=70}} || ? ||
|-
| {{cmd|wxpyimgview|version=70}} || ? ||
|-
| {{cmd|xganim|version=70}} || ? ||
|-
| {{cmd|ximgview|version=70}} || ? ||
|-
|}

== List of selected AddOns modules ==

See [[GRASS AddOns]] for full list of available modules. Feel free to extend this list.

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)''' || '''Note'''
|-
| {{AddonCmd|r.stream.angle}} || T || HY ||
|-
| {{AddonCmd|r.seg}} || T || IM || It could be rename to `i.seg`
|-
| {{AddonCmd|i.topocorr}} || T || IM ||
|-
| {{AddonCmd|r.diversity}} || T || LA ||
|-
| {{AddonCmd|Ps.output}} || ? || ||
|-
| ... || ? || ||
|-
|}

== How to implement ==

=== propose 1 ===
* add html tag <param> in the description.html with these options:
<param name = "core"> for core module
<param name = "tool" value="tool_code/codes"> for toolbox
<param name = "addons" [value="tool_code/codes"]> for addons, value is optional

* create a script to generate a xml file for each toolbox
* add toolbox option in g.extension to read the xml and install the modules

[[Category:Development]]

Toolboxes

2011-05-11T23:26:55Z

⚠️Helena: /* Raster */

* See [http://lists.osgeo.org/pipermail/grass-dev/2010-April/050210.html original post by Jarosław Jasiewicz]

* Discussion about the suitability of the proposed change on the [[Talk:GRASS_repository_layout_proposal|talk]] side of this wiki page; discussion of the possible method on this side of the page.

<pre>
Hi all!

That rather radical ideas I present here are rather for future, at least for GRASS 8,
but I'd like present it now for long-term reflection.

Probably all notice that for over two years there is big increase in add-on repository
(including me). There are modules of different quality: from fully GRASS toolsets,
to shell or python scripts, from actively developed tools to abandoned,
from all-purpose tools to very specialized etc. I also think that that activity
will be grown due to substitute shell script by python

Similar situation is in main GRASS branch: there are modules for all like conversion tools,
interpolation methods, georeferencing etc, and very specialized modules for very limited
group of users (like wild fire), there are also some modules out of date.

I'm not enthusiastic about moving new modules into main branch. Almost every module has
different coding style and it will lasting in future that GRASS would be difficult to maintain.
On the other hand some people complains that some interesting modules are only available as
add-ons (I assume for some reasons they cannot install it)

So my suggestion is to rearrange future GRASS form two layers (main branch/add-on) into
three layers architecture:

1) GRASS core layer: much limited limited than now, only GIS environment and basic,
all-puropse tools, slow changes, great stability
2) GRASS toolset layer: oficcial GRASS thematic tools and toolsets (like terrain analysis,
hydrological analysis, photo-interpretation, landscape analysis etc,) every toolset with its
maintainer, rapid development, new ready to use tools after quality control may appear here,
also some of current main branch tool shall be moved to that layer
3) GRASS community layer: everything else like experimental, actively development new tools,
that what do not pass quality control, simple scripts, etc....

What benefits:
for developers and contributors: much clear situation and better publication path.
Toolset layer should be much more open for new tools than current GRASS main branch

for users: faster access to new tools.
There is no doubt that new tools are faster developed (less risk) than GRASS core
Binaries with toolsets could be maintained as separate apt/urpmi/pacman/yum/exe etc packages,
so it may appear in linux repository separetly form GRASS core.

There is only loose ideas. Most of them are of course taken from R (core/toolsets/rest of packages;
separate core and package development) but I think it is worth of some discuss ...

regards
Jarek
</pre>
__TOC__
== Repository layout ==
=== Current repository layout ===

<pre>
- grass
|- trunk
|- raster/
|- vector/
|- ...

- grass-addons
|- raster/
|- vector/
|- ...
</pre>

=== Proposed repository layout ===

<pre>
- grass
|- trunk
|- raster/
|- vector/
|- ...

- grass-tools
|- trunk
|- raster/
|- vector/
|- ...

- grass-addons
|- raster/
|- vector/
|- ...
</pre>

== Proposed toolboxes ==

'''Toolbox''' is a topic-based set of modules used for solving common GIS analysis, like hydrology, networking, LRS, etc. Toolbox should be easily installed by the user using {{cmd|g.extension|version=70}}

* add toolbox

g.extension toolbox=hydrology operation=add

Source code of the selected modules is downloaded from SVN, compiled and afterwards also installed to the user-specified (~/.grass7) or system (/usr/lib/grass7) directory.

Give the possibility with a flag (like -a) to install also modules from addons related that toolbox

g.extension -a toolbox=hydrology operation=add

* remove toolbox

g.extension toolbox=hydrology operation=remove

* list of modules of selected toolbox

g.extension -l toolbox=hydrology

User can also add/remove selected module

g.extension module=r.stream.angle operation=add

=== List of toolboxes ===
{|class="wikitable"
|'''Toolbox name''' || '''Toolbox code''' || '''Description'''||'''Correlate toolbox'''
|-
| ''3D Raster''
| R3
| All `r3.*` modules
|
|-
| ''3D Visualization''
| V3
| {{cmd|nviz_cmd|version=70}}
|
|-
| ''Cartography''
| CA
| {{cmd|ps.map|version=70}}, {{AddonCmd|ps.output}}
|
|-
| ''Database''
| DB
| All `db.*` modules
| ''Vector analysis''
|-
| ''Geostatistcal''
| GS
| {{cmd|v.krige|version=70}} maybe other
|
|-
| ''GUI''
| GI
| [[wxGUI]]
|
|-
| ''Hydrology''
| HY
| {{cmd|r.watershed|version=70}}, {{cmd|r.terraflow|version=70}}, `r.stream.*` modules in addons, maybe other, r.flow, r.sim.water, r.sim.sediment
| ''Raster analysis''
|-
| ''Imagery''
| IM
| All `i.*` modules, selected r.* modules
|
|-
| ''Landascape analysis''
| LA
| All `r.li.*` modules, maybe other
| ''Raster analysis''
|-
| ''Lidar analysis''
| LI
| All `v.lidar.*` modules, {{cmd|v.surf.bspline|version=70}}, r.in.xyz
|
|-
| ''Linear Reference Systems''
| LS
| All `v.lrs.*` modules
| ''Vector analysis''
|-
| ''Network analysis''
| NA
| All `v.net.*` modules, maybe other
| ''Vector analysis''
|-
| ''Raster analysis''
| RA
| A lot of basic `r.*` modules (like {{cmd|r.buffer,|version=70}} {{cmd|r.reclass|version=70}}, {{cmd|r.fillnull|version=70}}...)
|
|-
| ''Terrain analysis''
| TA
| Different kind of analysis: soil ({{cmd|r.sun,|version=70}}), terrain ({{cmd|r.slope.aspect|version=70}}, {{cmd|r.los|version=70}}), geomorphometry ({{cmd|r.param.scale|version=70}})
| ''Raster analysis''
|-
| ''Vector analysis''
| VA
| A lot of basic `v.*` modules (like {{cmd|v.buffer|version=70}}, {{cmd|v.centroid|version=70}}, {{cmd|v.overlay|version=70}}...)
| ''Database''
|}
HM comment: do we need import/export Toolbox for all of the specialized *.in* and *.out.* commands? gdal/ogr commands should be in core.

== List of modules (trunk) ==

=== Display ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|d.barscale|version=70}} || ? ||
|-
| {{cmd|d.colorlist|version=70}} || ? ||
|-
| {{cmd|d.colortable|version=70}} || ? ||
|-
| {{cmd|d.correlate|version=70}} || ? ||
|-
| {{cmd|d.erase|version=70}} || ? ||
|-
| {{cmd|d.font|version=70}} || ? ||
|-
| {{cmd|d.fontlist|version=70}} || ? ||
|-
| {{cmd|d.geodesic|version=70}} || ? ||
|-
| {{cmd|d.graph|version=70}} || ? ||
|-
| {{cmd|d.grid|version=70}} || ? ||
|-
| {{cmd|d.his|version=70}} || ? ||
|-
| {{cmd|d.histogram|version=70}} || ? ||
|-
| {{cmd|d.info|version=70}} || ? ||
|-
| {{cmd|d.labels|version=70}} || ? ||
|-
| {{cmd|d.legend|version=70}} || ? ||
|-
| {{cmd|d.linegraph|version=70}} || ? ||
|-
| {{cmd|d.nviz|version=70}} || ? ||
|-
| {{cmd|d.path|version=70}} || ? ||
|-
| {{cmd|d.polar|version=70}} || ? ||
|-
| {{cmd|d.profile|version=70}} || ? ||
|-
| {{cmd|d.rast|version=70}} || ? ||
|-
| {{cmd|d.rast.arrow|version=70}} || ? ||
|-
| {{cmd|d.rast.edit|version=70}} || ? ||
|-
| {{cmd|d.rast.leg|version=70}} || ? ||
|-
| {{cmd|d.rast.num|version=70}} || ? ||
|-
| {{cmd|d.rgb|version=70}} || ? ||
|-
| {{cmd|d.rhumbline|version=70}} || ? ||
|-
| {{cmd|d.shadedmap|version=70}} || ? ||
|-
| {{cmd|d.text|version=70}} || ? ||
|-
| {{cmd|d.thematic.area|version=70}} || ? ||
|-
| {{cmd|d.title|version=70}} || ? ||
|-
| {{cmd|d.vect|version=70}} || ? ||
|-
| {{cmd|d.vect.chart|version=70}} || ? ||
|-
| {{cmd|d.vect.thematic|version=70}} || ? ||
|-
| {{cmd|d.where|version=70}} || ? ||
|-
|}

=== Database ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|db.columns|version=70}} || ? ||
|-
| {{cmd|db.connect|version=70}} || ? ||
|-
| {{cmd|db.copy|version=70}} || ? ||
|-
| {{cmd|db.createdb|version=70}} || ? ||
|-
| {{cmd|db.databases|version=70}} || ? ||
|-
| {{cmd|db.describe|version=70}} || ? ||
|-
| {{cmd|db.drivers|version=70}} || ? ||
|-
| {{cmd|db.dropcolumn|version=70}} || ? ||
|-
| {{cmd|db.dropdb|version=70}} || ? ||
|-
| {{cmd|db.droptable|version=70}} || ? ||
|-
| {{cmd|db.droptable|version=70}} || ? ||
|-
| {{cmd|db.execute|version=70}} || ? ||
|-
| {{cmd|db.in.ogr|version=70}} || ? ||
|-
| {{cmd|db.login|version=70}} || ? ||
|-
| {{cmd|db.out.ogr|version=70}} || ? ||
|-
| {{cmd|db.select|version=70}} || ? ||
|-
| {{cmd|db.tables|version=70}} || ? ||
|-
| {{cmd|db.test|version=70}} || ? ||
|-
|}

=== General ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|g.access|version=70}} || C ||
|-
| {{cmd|g.cairocomp|version=70}} || C ||
|-
| {{cmd|g.copy|version=70}} || C ||
|-
| {{cmd|g.dirseps|version=70}} || C ||
|-
| {{cmd|g.extension|version=70}} || C ||
|-
| {{cmd|g.filename|version=70}} || C ||
|-
| {{cmd|g.findetc|version=70}} || C ||
|-
| {{cmd|g.findfile|version=70}} || C ||
|-
| {{cmd|g.gisenv|version=70}} || C ||
|-
| {{cmd|g.gui|version=70}} || C ||
|-
| {{cmd|g.list|version=70}} || C ||
|-
| {{cmd|g.manual|version=70}} || C ||
|-
| {{cmd|g.mapset|version=70}} || C ||
|-
| {{cmd|g.mapsets|version=70}} || C ||
|-
| {{cmd|g.message|version=70}} || C ||
|-
| {{cmd|g.mkfontcap|version=70}} || C ||
|-
| {{cmd|g.mlist|version=70}} || C ||
|-
| {{cmd|g.mremove|version=70}} || C ||
|-
| {{cmd|g.parser|version=70}} || C ||
|-
| {{cmd|g.pnmcomp|version=70}} || C ||
|-
| {{cmd|g.ppmtopng|version=70}} || C ||
|-
| {{cmd|g.proj|version=70}} || C ||
|-
| {{cmd|g.region|version=70}} || C ||
|-
| {{cmd|g.remove|version=70}} || C ||
|-
| {{cmd|g.rename|version=70}} || C ||
|-
| {{cmd|g.tempfile|version=70}} || C ||
|-
| {{cmd|g.transform|version=70}} || C ||
|-
| {{cmd|g.version|version=70}} || C ||
|-
|}

=== Imagery ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|i.albedo|version=70}} || ? ||
|-
| {{cmd|i.atcorr|version=70}} || ? ||
|-
| {{cmd|i.biomass|version=70}} || ? ||
|-
| {{cmd|i.cca|version=70}} || ? ||
|-
| {{cmd|i.cluster|version=70}} || ? ||
|-
| {{cmd|i.eb.eta|version=70}} || ? ||
|-
| {{cmd|i.eb.evapfr|version=70}} || ? ||
|-
| {{cmd|i.eb.h_SEBAL01|version=70}} || ? ||
|-
| {{cmd|i.eb.soilheatflux|version=70}} || ? ||
|-
| {{cmd|i.emissivity|version=70}} || ? ||
|-
| {{cmd|i.evapo.time|version=70}} || ? ||
|-
| {{cmd|i.fft|version=70}} || ? ||
|-
| {{cmd|i.fusion.brovey|version=70}} || ? ||
|-
| {{cmd|i.gensig|version=70}} || ? ||
|-
| {{cmd|i.gensigset|version=70}} || ? ||
|-
| {{cmd|i.group|version=70}} || ? ||
|-
| {{cmd|i.his.rgb|version=70}} || ? ||
|-
| {{cmd|i.ifft|version=70}} || ? ||
|-
| {{cmd|i.image.mosaic|version=70}} || ? ||
|-
| {{cmd|i.in.spotvgt|version=70}} || ? ||
|-
| {{cmd|i.landsat.rgb|version=70}} || ? ||
|-
| {{cmd|i.latlong|version=70}} || ? ||
|-
| {{cmd|i.maxlik|version=70}} || ? ||
|-
| {{cmd|i.modis.qc|version=70}} || ? ||
|-
| {{cmd|i.oif|version=70}} || ? ||
|-
| {{cmd|i.pca|version=70}} || ? ||
|-
| {{cmd|i.rectify|version=70}} || ? ||
|-
| {{cmd|i.rgb.his|version=70}} || ? ||
|-
| {{cmd|i.smap|version=70}} || ? ||
|-
| {{cmd|i.spectral|version=70}} || ? ||
|-
| {{cmd|i.sunhours|version=70}} || ? ||
|-
| {{cmd|i.target|version=70}} || ? ||
|-
| {{cmd|i.tasscap|version=70}} || ? ||
|-
| {{cmd|i.vi|version=70}} || ? ||
|-
| {{cmd|i.zc|version=70}} || ? ||
|-
|}

=== Misc ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|m.cogo|version=70}} || ? ||
|-
| {{cmd|m.measure|version=70}} || ? ||
|-
| {{cmd|m.proj|version=70}} || ? ||
|-
|}

=== Postscript ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|ps.map|version=70}} || ? ||
|-
|}

=== Raster ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|r.basins.fill|version=70}} || ? ||
|-
| {{cmd|r.bitpattern|version=70}} || ? ||
|-
| {{cmd|r.blend|version=70}} || ? ||
|-
| {{cmd|r.buffer|version=70}} || ? ||
|-
| {{cmd|r.buffer2|version=70}} || ? ||
|-
| {{cmd|r.carve|version=70}} || ? ||
|-
| {{cmd|r.category|version=70}} || ? ||
|-
| {{cmd|r.circle|version=70}} || ? ||
|-
| {{cmd|r.clump|version=70}} || ? ||
|-
| {{cmd|r.coin|version=70}} || ? ||
|-
| {{cmd|r.colors|version=70}} || C ||
|-
| {{cmd|r.colors.out|version=70}} || ? ||
|-
| {{cmd|r.colors.stddev|version=70}} || ? ||
|-
| {{cmd|r.composite|version=70}} || ? ||
|-
| {{cmd|r.compress|version=70}} || ? ||
|-
| {{cmd|r.contour|version=70}} || ? ||
|-
| {{cmd|r.cost|version=70}} || ? ||
|-
| {{cmd|r.covar|version=70}} || ? ||
|-
| {{cmd|r.cross|version=70}} || ? ||
|-
| {{cmd|r.describe|version=70}} || ? ||
|-
| {{cmd|r.distance|version=70}} || ? ||
|-
| {{cmd|r.drain|version=70}} || ? ||
|-
| {{cmd|r.external|version=70}} || ? ||
|-
| {{cmd|r.external.out|version=70}} || ? ||
|-
| {{cmd|r.fill.dir|version=70}} || ? ||
|-
| {{cmd|r.fillnulls|version=70}} || ? ||
|-
| {{cmd|r.flow|version=70}} || T ||HY
|-
| {{cmd|r.grow|version=70}} || ? ||
|-
| {{cmd|r.grow.distance|version=70}} || ? ||
|-
| {{cmd|r.gwflow|version=70}} || T ||HY
|-
| {{cmd|r.his|version=70}} || ? ||
|-
| {{cmd|r.horizon|version=70}} || ? ||
|-
| {{cmd|r.in.arc|version=70}} || ? ||
|-
| {{cmd|r.in.ascii|version=70}} || ? ||
|-
| {{cmd|r.in.aster|version=70}} || ? ||
|-
| {{cmd|r.in.bin|version=70}} || ? ||
|-
| {{cmd|r.in.gdal|version=70}} || ? ||
|-
| {{cmd|r.in.gridatb|version=70}} || ? ||
|-
| {{cmd|r.in.mat|version=70}} || ? ||
|-
| {{cmd|r.in.png|version=70}} || ? ||
|-
| {{cmd|r.in.poly|version=70}} || ? ||
|-
| {{cmd|r.in.srtm|version=70}} || ? ||
|-
| {{cmd|r.in.wms|version=70}} || ? ||
|-
| {{cmd|r.in.xyz|version=70}} || C ||
|-
| {{cmd|r.info|version=70}} || C ||
|-
| {{cmd|r.kappa|version=70}} || ? ||
|-
| {{cmd|r.lake|version=70}} || T ||HY
|-
| {{cmd|r.li.cwed|version=70}} || ? ||
|-
| {{cmd|r.li.dominance|version=70}} || ? ||
|-
| {{cmd|r.li.edgedensity|version=70}} || ? ||
|-
| {{cmd|r.li.mpa|version=70}} || ? ||
|-
| {{cmd|r.li.mps|version=70}} || ? ||
|-
| {{cmd|r.li.padcv|version=70}} || ? ||
|-
| {{cmd|r.li.padrange|version=70}} || ? ||
|-
| {{cmd|r.li.padsd|version=70}} || ? ||
|-
| {{cmd|r.li.patchdensity|version=70}} || ? ||
|-
| {{cmd|r.li.patchnum|version=70}} || ? ||
|-
| {{cmd|r.li.richness|version=70}} || ? ||
|-
| {{cmd|r.li.shannon|version=70}} || ? ||
|-
| {{cmd|r.li.shape|version=70}} || ? ||
|-
| {{cmd|r.li.simpson|version=70}} || ? ||
|-
| {{cmd|r.los|version=70}} || ? ||
|-
| {{cmd|r.mapcalc|version=70}} || C ||
|-
| {{cmd|r.mask|version=70}} || C ||
|-
| {{cmd|r.mfilter|version=70}} || ? ||
|-
| {{cmd|r.mode|version=70}} || ? ||
|-
| {{cmd|r.neighbors|version=70}} || C ||
|-
| {{cmd|r.null|version=70}} || C ||
|-
| {{cmd|r.out.arc|version=70}} || ? ||
|-
| {{cmd|r.out.ascii|version=70}} || ? ||
|-
| {{cmd|r.out.bin|version=70}} || ? ||
|-
| {{cmd|r.out.gdal|version=70}} || ? ||
|-
| {{cmd|r.out.gridatb|version=70}} || ? ||
|-
| {{cmd|r.out.mat|version=70}} || ? ||
|-
| {{cmd|r.out.mpeg|version=70}} || ? ||
|-
| {{cmd|r.out.png|version=70}} || ? ||
|-
| {{cmd|r.out.pov|version=70}} || ? ||
|-
| {{cmd|r.out.ppm|version=70}} || ? ||
|-
| {{cmd|r.out.ppm3|version=70}} || ? ||
|-
| {{cmd|r.out.tiff|version=70}} || ? ||
|-
| {{cmd|r.out.vrml|version=70}} || ? ||
|-
| {{cmd|r.out.vtk|version=70}} || ? ||
|-
| {{cmd|r.out.xyz|version=70}} || ? ||
|-
| {{cmd|r.param.scale|version=70}} || T ||
|-
| {{cmd|r.patch|version=70}} || C ||
|-
| {{cmd|r.plane|version=70}} || ? ||
|-
| {{cmd|r.profile|version=70}} || ? ||
|-
| {{cmd|r.proj|version=70}} || C ||
|-
| {{cmd|r.quant|version=70}} || ? ||
|-
| {{cmd|r.quantile|version=70}} || ? ||
|-
| {{cmd|r.random|version=70}} || ? ||
|-
| {{cmd|r.random.cells|version=70}} || ? ||
|-
| {{cmd|r.random.surface|version=70}} || ? ||
|-
| {{cmd|r.reclass|version=70}} || ? ||
|-
| {{cmd|r.reclass.area|version=70}} || ? ||
|-
| {{cmd|r.recode|version=70}} || C ||
|-
| {{cmd|r.region|version=70}} || ? ||
|-
| {{cmd|r.regression.line|version=70}} || C ||
|-
| {{cmd|r.report|version=70}} || C||
|-
| {{cmd|r.resamp.bspline|version=70}} || C ||
|-
| {{cmd|r.resamp.filter|version=70}} || ? ||
|-
| {{cmd|r.resamp.interp|version=70}} || C ||
|-
| {{cmd|r.resamp.rst|version=70}} || ? ||
|-
| {{cmd|r.resamp.stats|version=70}} || ? ||
|-
| {{cmd|r.resample|version=70}} || ? ||
|-
| {{cmd|r.rescale|version=70}} || ? ||
|-
| {{cmd|r.rescale.eq|version=70}} || ? ||
|-
| {{cmd|r.ros|version=70}} || ? ||
|-
| {{cmd|r.series|version=70}} || C ||
|-
| {{cmd|r.shaded.relief|version=70}} || C ||
|-
| {{cmd|r.sim.sediment|version=70}} || T ||HY
|-
| {{cmd|r.sim.water|version=70}} || T ||HY
|-
| {{cmd|r.slope.aspect|version=70}} || C ||
|-
| {{cmd|r.solute.transport|version=70}} || T ||?
|-
| {{cmd|r.spread|version=70}} || ? ||
|-
| {{cmd|r.spreadpath|version=70}} || ? ||
|-
| {{cmd|r.statistics|version=70}} || ? ||
|-
| {{cmd|r.statistics2|version=70}} || ? ||
|-
| {{cmd|r.statistics3|version=70}} || ? ||
|-
| {{cmd|r.stats|version=70}} || ? ||
|-
| {{cmd|r.sun|version=70}} || ? ||
|-
| {{cmd|r.sunmask|version=70}} || ? ||
|-
| {{cmd|r.support|version=70}} || C||
|-
| {{cmd|r.support.stats|version=70}} || ? ||
|-
| {{cmd|r.surf.area|version=70}} || ? ||
|-
| {{cmd|r.surf.contour|version=70}} || ? ||
|-
| {{cmd|r.surf.fractal|version=70}} || ? ||
|-
| {{cmd|r.surf.gauss|version=70}} || ? ||
|-
| {{cmd|r.surf.idw|version=70}} || ? ||
|-
| {{cmd|r.surf.idw2|version=70}} || ? ||
|-
| {{cmd|r.surf.random|version=70}} || ? ||
|-
| {{cmd|r.terraflow|version=70}} || T ||HY
|-
| {{cmd|r.texture|version=70}} || ? ||
|-
| {{cmd|r.thin|version=70}} || C ||
|-
| {{cmd|r.tileset|version=70}} || ? ||
|-
| {{cmd|r.timestamp|version=70}} || C ||
|-
| {{cmd|r.to.rast3|version=70}} || C ||
|-
| {{cmd|r.to.rast3elev|version=70}} || ? ||
|-
| {{cmd|r.to.vect|version=70}} || C ||
|-
| {{cmd|r.topidx|version=70}} || T ||HY
|-
| {{cmd|r.topmodel|version=70}} || T ||HY
|-
| {{cmd|r.transect|version=70}} || ? ||
|-
| {{cmd|r.univar|version=70}} || C ||
|-
| {{cmd|r.uslek|version=70}} || T ||HY
|-
| {{cmd|r.usler|version=70}} || T ||HY
|-
| {{cmd|r.volume|version=70}} || ? ||
|-
| {{cmd|r.walk|version=70}} || ? ||
|-
| {{cmd|r.water.outlet|version=70}} || T||HY
|-
| {{cmd|r.watershed|version=70}} || T ||HY
|-
| {{cmd|r.what|version=70}} || C ||
|-
| {{cmd|r.what.color|version=70}} || ? ||
|-
|}

=== 3D raster ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|r3.cross.rast|version=70}} || T || 3D Raster
|-
| {{cmd|r3.gwflow|version=70}} || T || 3D Raster
|-
| {{cmd|r3.in.ascii|version=70}} || T || 3D Raster
|-
| {{cmd|r3.in.v5d|version=70}} || T || 3D Raster
|-
| {{cmd|r3.info|version=70}} || T || 3D Raster
|-
| {{cmd|r3.mapcalc|version=70}} || T || 3D Raster
|-
| {{cmd|r3.mask|version=70}} || T || 3D Raster
|-
| {{cmd|r3.mkdspf|version=70}} || T || 3D Raster
|-
| {{cmd|r3.null|version=70}} || T || 3D Raster
|-
| {{cmd|r3.out.ascii|version=70}} || T || 3D Raster
|-
| {{cmd|r3.out.v5d|version=70}} || T || 3D Raster
|-
| {{cmd|r3.out.vtk|version=70}} || T || 3D Raster
|-
| {{cmd|r3.stats|version=70}} || T || 3D Raster
|-
| {{cmd|r3.timestamp|version=70}} || T || 3D Raster
|-
| {{cmd|r3.to.rast|version=70}} || T || 3D Raster
|-
| {{cmd|r3.univar|version=70}} || T || 3D Raster
|-
|}

=== Vector ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|v.autokrige|version=70}} || ? ||
|-
| {{cmd|v.buffer|version=70}} || ? ||
|-
| {{cmd|v.build|version=70}} || ? ||
|-
| {{cmd|v.build.all|version=70}} || ? ||
|-
| {{cmd|v.build.polylines|version=70}} || ? ||
|-
| {{cmd|v.category|version=70}} || ? ||
|-
| {{cmd|v.centroids|version=70}} || ? ||
|-
| {{cmd|v.class|version=70}} || ? ||
|-
| {{cmd|v.clean|version=70}} || ? ||
|-
| {{cmd|v.colors|version=70}} || ? ||
|-
| {{cmd|v.convert|version=70}} || ? ||
|-
| {{cmd|v.convert.all|version=70}} || ? ||
|-
| {{cmd|v.db.addcolumn|version=70}} || ? ||
|-
| {{cmd|v.db.addtable|version=70}} || ? ||
|-
| {{cmd|v.db.connect|version=70}} || ? ||
|-
| {{cmd|v.db.dropcolumn|version=70}} || ? ||
|-
| {{cmd|v.db.droprow|version=70}} || ? ||
|-
| {{cmd|v.db.droptable|version=70}} || ? ||
|-
| {{cmd|v.db.join|version=70}} || ? ||
|-
| {{cmd|v.db.reconnect.all|version=70}} || ? ||
|-
| {{cmd|v.db.renamecolumn|version=70}} || ? ||
|-
| {{cmd|v.db.select|version=70}} || ? ||
|-
| {{cmd|v.db.univar|version=70}} || ? ||
|-
| {{cmd|v.db.update|version=70}} || ? ||
|-
| {{cmd|v.delaunay|version=70}} || ? ||
|-
| {{cmd|v.dissolve|version=70}} || ? ||
|-
| {{cmd|v.distance|version=70}} || ? ||
|-
| {{cmd|v.drape|version=70}} || ? ||
|-
| {{cmd|v.edit|version=70}} || ? ||
|-
| {{cmd|v.external|version=70}} || ? ||
|-
| {{cmd|v.extract|version=70}} || ? ||
|-
| {{cmd|v.extrude|version=70}} || ? ||
|-
| {{cmd|v.generalize|version=70}} || ? ||
|-
| {{cmd|v.hull|version=70}} || ? ||
|-
| {{cmd|v.in.ascii|version=70}} || ? ||
|-
| {{cmd|v.in.db|version=70}} || ? ||
|-
| {{cmd|v.in.dxf|version=70}} || ? ||
|-
| {{cmd|v.in.e00|version=70}} || ? ||
|-
| {{cmd|v.in.geonames|version=70}} || ? ||
|-
| {{cmd|v.in.gns|version=70}} || ? ||
|-
| {{cmd|v.in.lines|version=70}} || ? ||
|-
| {{cmd|v.in.mapgen|version=70}} || ? ||
|-
| {{cmd|v.in.ogr|version=70}} || ? ||
|-
| {{cmd|v.in.postgis|version=70}} || ? ||
|-
| {{cmd|v.in.region|version=70}} || ? ||
|-
| {{cmd|v.in.sites|version=70}} || ? ||
|-
| {{cmd|v.in.sites.all|version=70}} || ? ||
|-
| {{cmd|v.in.wfs|version=70}} || ? ||
|-
| {{cmd|v.info|version=70}} || ? ||
|-
| {{cmd|v.kcv|version=70}} || ? ||
|-
| {{cmd|v.kernel|version=70}} || ? ||
|-
| {{cmd|v.krige|version=70}} || ? ||
|-
| {{cmd|v.label|version=70}} || ? ||
|-
| {{cmd|v.lidar.correction|version=70}} || ? ||
|-
| {{cmd|v.lidar.edgedetection|version=70}} || ? ||
|-
| {{cmd|v.lidar.growing|version=70}} || ? ||
|-
| {{cmd|v.lrs.create|version=70}} || ? ||
|-
| {{cmd|v.lrs.label|version=70}} || ? ||
|-
| {{cmd|v.lrs.segment|version=70}} || ? ||
|-
| {{cmd|v.lrs.where|version=70}} || ? ||
|-
| {{cmd|v.mkgrid|version=70}} || ? ||
|-
| {{cmd|v.neighbors|version=70}} || ? ||
|-
| {{cmd|v.net|version=70}} || ? ||
|-
| {{cmd|v.net.alloc|version=70}} || ? ||
|-
| {{cmd|v.net.allpairs|version=70}} || ? ||
|-
| {{cmd|v.net.bridge|version=70}} || ? ||
|-
| {{cmd|v.net.centrality|version=70}} || ? ||
|-
| {{cmd|v.net.components|version=70}} || ? ||
|-
| {{cmd|v.net.connectivity|version=70}} || ? ||
|-
| {{cmd|v.net.distance|version=70}} || ? ||
|-
| {{cmd|v.net.flow|version=70}} || ? ||
|-
| {{cmd|v.net.iso|version=70}} || ? ||
|-
| {{cmd|v.net.path|version=70}} || ? ||
|-
| {{cmd|v.net.salesman|version=70}} || ? ||
|-
| {{cmd|v.net.spanningtree|version=70}} || ? ||
|-
| {{cmd|v.net.steiner|version=70}} || ? ||
|-
| {{cmd|v.net.timetable|version=70}} || ? ||
|-
| {{cmd|v.net.visibility|version=70}} || ? ||
|-
| {{cmd|v.normal|version=70}} || ? ||
|-
| {{cmd|v.out.ascii|version=70}} || ? ||
|-
| {{cmd|v.out.dxf|version=70}} || ? ||
|-
| {{cmd|v.out.gps|version=70}} || ? ||
|-
| {{cmd|v.out.ogr|version=70}} || ? ||
|-
| {{cmd|v.out.postgis|version=70}} || ? ||
|-
| {{cmd|v.out.pov|version=70}} || ? ||
|-
| {{cmd|v.out.svg|version=70}} || ? ||
|-
| {{cmd|v.out.vtk|version=70}} || ? ||
|-
| {{cmd|v.outlier|version=70}} || ? ||
|-
| {{cmd|v.overlay|version=70}} || ? ||
|-
| {{cmd|v.parallel|version=70}} || ? ||
|-
| {{cmd|v.patch|version=70}} || ? ||
|-
| {{cmd|v.perturb|version=70}} || ? ||
|-
| {{cmd|v.proj|version=70}} || ? ||
|-
| {{cmd|v.qcount|version=70}} || ? ||
|-
| {{cmd|v.random|version=70}} || ? ||
|-
| {{cmd|v.rast.stats|version=70}} || ? ||
|-
| {{cmd|v.reclass|version=70}} || ? ||
|-
| {{cmd|v.report|version=70}} || ? ||
|-
| {{cmd|v.sample|version=70}} || ? ||
|-
| {{cmd|v.segment|version=70}} || ? ||
|-
| {{cmd|v.select|version=70}} || ? ||
|-
| {{cmd|v.split|version=70}} || ? ||
|-
| {{cmd|v.support|version=70}} || ? ||
|-
| {{cmd|v.surf.bspline|version=70}} || ? ||
|-
| {{cmd|v.surf.idw|version=70}} || ? ||
|-
| {{cmd|v.surf.rst|version=70}} || ? ||
|-
| {{cmd|v.to.3d|version=70}} || ? ||
|-
| {{cmd|v.to.db|version=70}} || ? ||
|-
| {{cmd|v.to.points|version=70}} || ? ||
|-
| {{cmd|v.to.rast|version=70}} || ? ||
|-
| {{cmd|v.to.rast3|version=70}} || ? ||
|-
| {{cmd|v.transform|version=70}} || ? ||
|-
| {{cmd|v.type|version=70}} || ? ||
|-
| {{cmd|v.univar|version=70}} || ? ||
|-
| {{cmd|v.vol.rst|version=70}} || ? ||
|-
| {{cmd|v.voronoi|version=70}} || ? ||
|-
| {{cmd|v.what|version=70}} || ? ||
|-
| {{cmd|v.what.rast|version=70}} || ? ||
|-
| {{cmd|v.what.vect|version=70}} || ? ||
|-
|}

=== Various ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|nviz|version=70}} || ? ||
|-
| {{cmd|nviz_cmd|version=70}} || ? ||
|-
| {{cmd|wximgview|version=70}} || ? ||
|-
| {{cmd|wxpyimgview|version=70}} || ? ||
|-
| {{cmd|xganim|version=70}} || ? ||
|-
| {{cmd|ximgview|version=70}} || ? ||
|-
|}

== List of selected AddOns modules ==

See [[GRASS AddOns]] for full list of available modules. Feel free to extend this list.

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)''' || '''Note'''
|-
| {{AddonCmd|r.stream.angle}} || T || HY ||
|-
| {{AddonCmd|r.seg}} || T || IM || It could be rename to `i.seg`
|-
| {{AddonCmd|i.topocorr}} || T || IM ||
|-
| {{AddonCmd|r.diversity}} || T || LA ||
|-
| {{AddonCmd|Ps.output}} || ? || ||
|-
| ... || ? || ||
|-
|}

== How to implement ==

=== propose 1 ===
* add html tag <param> in the description.html with these options:
<param name = "core"> for core module
<param name = "tool" value="tool_code/codes"> for toolbox
<param name = "addons" [value="tool_code/codes"]> for addons, value is optional

* create a script to generate a xml file for each toolbox
* add toolbox option in g.extension to read the xml and install the modules

[[Category:Development]]

Toolboxes

2011-05-08T03:52:23Z

⚠️Helena: /* List of toolboxes */

* See [http://lists.osgeo.org/pipermail/grass-dev/2010-April/050210.html original post by Jarosław Jasiewicz]

* Discussion about the suitability of the proposed change on the [[Talk:GRASS_repository_layout_proposal|talk]] side of this wiki page; discussion of the possible method on this side of the page.

<pre>
Hi all!

That rather radical ideas I present here are rather for future, at least for GRASS 8,
but I'd like present it now for long-term reflection.

Probably all notice that for over two years there is big increase in add-on repository
(including me). There are modules of different quality: from fully GRASS toolsets,
to shell or python scripts, from actively developed tools to abandoned,
from all-purpose tools to very specialized etc. I also think that that activity
will be grown due to substitute shell script by python

Similar situation is in main GRASS branch: there are modules for all like conversion tools,
interpolation methods, georeferencing etc, and very specialized modules for very limited
group of users (like wild fire), there are also some modules out of date.

I'm not enthusiastic about moving new modules into main branch. Almost every module has
different coding style and it will lasting in future that GRASS would be difficult to maintain.
On the other hand some people complains that some interesting modules are only available as
add-ons (I assume for some reasons they cannot install it)

So my suggestion is to rearrange future GRASS form two layers (main branch/add-on) into
three layers architecture:

1) GRASS core layer: much limited limited than now, only GIS environment and basic,
all-puropse tools, slow changes, great stability
2) GRASS toolset layer: oficcial GRASS thematic tools and toolsets (like terrain analysis,
hydrological analysis, photo-interpretation, landscape analysis etc,) every toolset with its
maintainer, rapid development, new ready to use tools after quality control may appear here,
also some of current main branch tool shall be moved to that layer
3) GRASS community layer: everything else like experimental, actively development new tools,
that what do not pass quality control, simple scripts, etc....

What benefits:
for developers and contributors: much clear situation and better publication path.
Toolset layer should be much more open for new tools than current GRASS main branch

for users: faster access to new tools.
There is no doubt that new tools are faster developed (less risk) than GRASS core
Binaries with toolsets could be maintained as separate apt/urpmi/pacman/yum/exe etc packages,
so it may appear in linux repository separetly form GRASS core.

There is only loose ideas. Most of them are of course taken from R (core/toolsets/rest of packages;
separate core and package development) but I think it is worth of some discuss ...

regards
Jarek
</pre>
__TOC__
== Repository layout ==
=== Current repository layout ===

<pre>
- grass
|- trunk
|- raster/
|- vector/
|- ...

- grass-addons
|- raster/
|- vector/
|- ...
</pre>

=== Proposed repository layout ===

<pre>
- grass
|- trunk
|- raster/
|- vector/
|- ...

- grass-tools
|- trunk
|- raster/
|- vector/
|- ...

- grass-addons
|- raster/
|- vector/
|- ...
</pre>

== Proposed toolboxes ==

'''Toolbox''' is a topic-based set of modules used for solving common GIS analysis, like hydrology, networking, LRS, etc. Toolbox should be easily installed by the user using {{cmd|g.extension|version=70}}

* add toolbox

g.extension toolbox=hydrology operation=add

Source code of the selected modules is downloaded from SVN, compiled and afterwards also installed to the user-specified (~/.grass7) or system (/usr/lib/grass7) directory.

Give the possibility with a flag (like -a) to install also modules from addons related that toolbox

g.extension -a toolbox=hydrology operation=add

* remove toolbox

g.extension toolbox=hydrology operation=remove

* list of modules of selected toolbox

g.extension -l toolbox=hydrology

User can also add/remove selected module

g.extension module=r.stream.angle operation=add

=== List of toolboxes ===
{|class="wikitable"
|'''Toolbox name''' || '''Toolbox code''' || '''Description'''||'''Correlate toolbox'''
|-
| ''3D Raster''
| R3
| All `r3.*` modules
|
|-
| ''3D Visualization''
| V3
| {{cmd|nviz_cmd|version=70}}
|
|-
| ''Cartography''
| CA
| {{cmd|ps.map|version=70}}, {{AddonCmd|ps.output}}
|
|-
| ''Database''
| DB
| All `db.*` modules
| ''Vector analysis''
|-
| ''Geostatistcal''
| GS
| {{cmd|v.krige|version=70}} maybe other
|
|-
| ''GUI''
| GI
| [[wxGUI]]
|
|-
| ''Hydrology''
| HY
| {{cmd|r.watershed|version=70}}, {{cmd|r.terraflow|version=70}}, `r.stream.*` modules in addons, maybe other, r.flow, r.sim.water, r.sim.sediment
| ''Raster analysis''
|-
| ''Imagery''
| IM
| All `i.*` modules, selected r.* modules
|
|-
| ''Landascape analysis''
| LA
| All `r.li.*` modules, maybe other
| ''Raster analysis''
|-
| ''Lidar analysis''
| LI
| All `v.lidar.*` modules, {{cmd|v.surf.bspline|version=70}}, r.in.xyz
|
|-
| ''Linear Reference Systems''
| LS
| All `v.lrs.*` modules
| ''Vector analysis''
|-
| ''Network analysis''
| NA
| All `v.net.*` modules, maybe other
| ''Vector analysis''
|-
| ''Raster analysis''
| RA
| A lot of basic `r.*` modules (like {{cmd|r.buffer,|version=70}} {{cmd|r.reclass|version=70}}, {{cmd|r.fillnull|version=70}}...)
|
|-
| ''Terrain analysis''
| TA
| Different kind of analysis: soil ({{cmd|r.sun,|version=70}}), terrain ({{cmd|r.slope.aspect|version=70}}, {{cmd|r.los|version=70}}), geomorphometry ({{cmd|r.param.scale|version=70}})
| ''Raster analysis''
|-
| ''Vector analysis''
| VA
| A lot of basic `v.*` modules (like {{cmd|v.buffer|version=70}}, {{cmd|v.centroid|version=70}}, {{cmd|v.overlay|version=70}}...)
| ''Database''
|}
HM comment: do we need import/export Toolbox for all of the specialized *.in* and *.out.* commands? gdal/ogr commands should be in core.

== List of modules (trunk) ==

=== Display ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|d.barscale|version=70}} || ? ||
|-
| {{cmd|d.colorlist|version=70}} || ? ||
|-
| {{cmd|d.colortable|version=70}} || ? ||
|-
| {{cmd|d.correlate|version=70}} || ? ||
|-
| {{cmd|d.erase|version=70}} || ? ||
|-
| {{cmd|d.font|version=70}} || ? ||
|-
| {{cmd|d.fontlist|version=70}} || ? ||
|-
| {{cmd|d.geodesic|version=70}} || ? ||
|-
| {{cmd|d.graph|version=70}} || ? ||
|-
| {{cmd|d.grid|version=70}} || ? ||
|-
| {{cmd|d.his|version=70}} || ? ||
|-
| {{cmd|d.histogram|version=70}} || ? ||
|-
| {{cmd|d.info|version=70}} || ? ||
|-
| {{cmd|d.labels|version=70}} || ? ||
|-
| {{cmd|d.legend|version=70}} || ? ||
|-
| {{cmd|d.linegraph|version=70}} || ? ||
|-
| {{cmd|d.nviz|version=70}} || ? ||
|-
| {{cmd|d.path|version=70}} || ? ||
|-
| {{cmd|d.polar|version=70}} || ? ||
|-
| {{cmd|d.profile|version=70}} || ? ||
|-
| {{cmd|d.rast|version=70}} || ? ||
|-
| {{cmd|d.rast.arrow|version=70}} || ? ||
|-
| {{cmd|d.rast.edit|version=70}} || ? ||
|-
| {{cmd|d.rast.leg|version=70}} || ? ||
|-
| {{cmd|d.rast.num|version=70}} || ? ||
|-
| {{cmd|d.rgb|version=70}} || ? ||
|-
| {{cmd|d.rhumbline|version=70}} || ? ||
|-
| {{cmd|d.shadedmap|version=70}} || ? ||
|-
| {{cmd|d.text|version=70}} || ? ||
|-
| {{cmd|d.thematic.area|version=70}} || ? ||
|-
| {{cmd|d.title|version=70}} || ? ||
|-
| {{cmd|d.vect|version=70}} || ? ||
|-
| {{cmd|d.vect.chart|version=70}} || ? ||
|-
| {{cmd|d.vect.thematic|version=70}} || ? ||
|-
| {{cmd|d.where|version=70}} || ? ||
|-
|}

=== Database ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|db.columns|version=70}} || ? ||
|-
| {{cmd|db.connect|version=70}} || ? ||
|-
| {{cmd|db.copy|version=70}} || ? ||
|-
| {{cmd|db.createdb|version=70}} || ? ||
|-
| {{cmd|db.databases|version=70}} || ? ||
|-
| {{cmd|db.describe|version=70}} || ? ||
|-
| {{cmd|db.drivers|version=70}} || ? ||
|-
| {{cmd|db.dropcolumn|version=70}} || ? ||
|-
| {{cmd|db.dropdb|version=70}} || ? ||
|-
| {{cmd|db.droptable|version=70}} || ? ||
|-
| {{cmd|db.droptable|version=70}} || ? ||
|-
| {{cmd|db.execute|version=70}} || ? ||
|-
| {{cmd|db.in.ogr|version=70}} || ? ||
|-
| {{cmd|db.login|version=70}} || ? ||
|-
| {{cmd|db.out.ogr|version=70}} || ? ||
|-
| {{cmd|db.select|version=70}} || ? ||
|-
| {{cmd|db.tables|version=70}} || ? ||
|-
| {{cmd|db.test|version=70}} || ? ||
|-
|}

=== General ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|g.access|version=70}} || C ||
|-
| {{cmd|g.cairocomp|version=70}} || C ||
|-
| {{cmd|g.copy|version=70}} || C ||
|-
| {{cmd|g.dirseps|version=70}} || C ||
|-
| {{cmd|g.extension|version=70}} || C ||
|-
| {{cmd|g.filename|version=70}} || C ||
|-
| {{cmd|g.findetc|version=70}} || C ||
|-
| {{cmd|g.findfile|version=70}} || C ||
|-
| {{cmd|g.gisenv|version=70}} || C ||
|-
| {{cmd|g.gui|version=70}} || C ||
|-
| {{cmd|g.list|version=70}} || C ||
|-
| {{cmd|g.manual|version=70}} || C ||
|-
| {{cmd|g.mapset|version=70}} || C ||
|-
| {{cmd|g.mapsets|version=70}} || C ||
|-
| {{cmd|g.message|version=70}} || C ||
|-
| {{cmd|g.mkfontcap|version=70}} || C ||
|-
| {{cmd|g.mlist|version=70}} || C ||
|-
| {{cmd|g.mremove|version=70}} || C ||
|-
| {{cmd|g.parser|version=70}} || C ||
|-
| {{cmd|g.pnmcomp|version=70}} || C ||
|-
| {{cmd|g.ppmtopng|version=70}} || C ||
|-
| {{cmd|g.proj|version=70}} || C ||
|-
| {{cmd|g.region|version=70}} || C ||
|-
| {{cmd|g.remove|version=70}} || C ||
|-
| {{cmd|g.rename|version=70}} || C ||
|-
| {{cmd|g.tempfile|version=70}} || C ||
|-
| {{cmd|g.transform|version=70}} || C ||
|-
| {{cmd|g.version|version=70}} || C ||
|-
|}

=== Imagery ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|i.albedo|version=70}} || ? ||
|-
| {{cmd|i.atcorr|version=70}} || ? ||
|-
| {{cmd|i.biomass|version=70}} || ? ||
|-
| {{cmd|i.cca|version=70}} || ? ||
|-
| {{cmd|i.cluster|version=70}} || ? ||
|-
| {{cmd|i.eb.eta|version=70}} || ? ||
|-
| {{cmd|i.eb.evapfr|version=70}} || ? ||
|-
| {{cmd|i.eb.h_SEBAL01|version=70}} || ? ||
|-
| {{cmd|i.eb.soilheatflux|version=70}} || ? ||
|-
| {{cmd|i.emissivity|version=70}} || ? ||
|-
| {{cmd|i.evapo.time|version=70}} || ? ||
|-
| {{cmd|i.fft|version=70}} || ? ||
|-
| {{cmd|i.fusion.brovey|version=70}} || ? ||
|-
| {{cmd|i.gensig|version=70}} || ? ||
|-
| {{cmd|i.gensigset|version=70}} || ? ||
|-
| {{cmd|i.group|version=70}} || ? ||
|-
| {{cmd|i.his.rgb|version=70}} || ? ||
|-
| {{cmd|i.ifft|version=70}} || ? ||
|-
| {{cmd|i.image.mosaic|version=70}} || ? ||
|-
| {{cmd|i.in.spotvgt|version=70}} || ? ||
|-
| {{cmd|i.landsat.rgb|version=70}} || ? ||
|-
| {{cmd|i.latlong|version=70}} || ? ||
|-
| {{cmd|i.maxlik|version=70}} || ? ||
|-
| {{cmd|i.modis.qc|version=70}} || ? ||
|-
| {{cmd|i.oif|version=70}} || ? ||
|-
| {{cmd|i.pca|version=70}} || ? ||
|-
| {{cmd|i.rectify|version=70}} || ? ||
|-
| {{cmd|i.rgb.his|version=70}} || ? ||
|-
| {{cmd|i.smap|version=70}} || ? ||
|-
| {{cmd|i.spectral|version=70}} || ? ||
|-
| {{cmd|i.sunhours|version=70}} || ? ||
|-
| {{cmd|i.target|version=70}} || ? ||
|-
| {{cmd|i.tasscap|version=70}} || ? ||
|-
| {{cmd|i.vi|version=70}} || ? ||
|-
| {{cmd|i.zc|version=70}} || ? ||
|-
|}

=== Misc ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|m.cogo|version=70}} || ? ||
|-
| {{cmd|m.measure|version=70}} || ? ||
|-
| {{cmd|m.proj|version=70}} || ? ||
|-
|}

=== Postscript ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|ps.map|version=70}} || ? ||
|-
|}

=== Raster ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|r.basins.fill|version=70}} || ? ||
|-
| {{cmd|r.bitpattern|version=70}} || ? ||
|-
| {{cmd|r.blend|version=70}} || ? ||
|-
| {{cmd|r.buffer|version=70}} || ? ||
|-
| {{cmd|r.buffer2|version=70}} || ? ||
|-
| {{cmd|r.carve|version=70}} || ? ||
|-
| {{cmd|r.category|version=70}} || ? ||
|-
| {{cmd|r.circle|version=70}} || ? ||
|-
| {{cmd|r.clump|version=70}} || ? ||
|-
| {{cmd|r.coin|version=70}} || ? ||
|-
| {{cmd|r.colors|version=70}} || C ||
|-
| {{cmd|r.colors.out|version=70}} || ? ||
|-
| {{cmd|r.colors.stddev|version=70}} || ? ||
|-
| {{cmd|r.composite|version=70}} || ? ||
|-
| {{cmd|r.compress|version=70}} || ? ||
|-
| {{cmd|r.contour|version=70}} || ? ||
|-
| {{cmd|r.cost|version=70}} || ? ||
|-
| {{cmd|r.covar|version=70}} || ? ||
|-
| {{cmd|r.cross|version=70}} || ? ||
|-
| {{cmd|r.describe|version=70}} || ? ||
|-
| {{cmd|r.distance|version=70}} || ? ||
|-
| {{cmd|r.drain|version=70}} || ? ||
|-
| {{cmd|r.external|version=70}} || ? ||
|-
| {{cmd|r.external.out|version=70}} || ? ||
|-
| {{cmd|r.fill.dir|version=70}} || ? ||
|-
| {{cmd|r.fillnulls|version=70}} || ? ||
|-
| {{cmd|r.flow|version=70}} || HY ||
|-
| {{cmd|r.grow|version=70}} || ? ||
|-
| {{cmd|r.grow.distance|version=70}} || ? ||
|-
| {{cmd|r.gwflow|version=70}} || ? ||
|-
| {{cmd|r.his|version=70}} || ? ||
|-
| {{cmd|r.horizon|version=70}} || ? ||
|-
| {{cmd|r.in.arc|version=70}} || ? ||
|-
| {{cmd|r.in.ascii|version=70}} || ? ||
|-
| {{cmd|r.in.aster|version=70}} || ? ||
|-
| {{cmd|r.in.bin|version=70}} || ? ||
|-
| {{cmd|r.in.gdal|version=70}} || ? ||
|-
| {{cmd|r.in.gridatb|version=70}} || ? ||
|-
| {{cmd|r.in.mat|version=70}} || ? ||
|-
| {{cmd|r.in.png|version=70}} || ? ||
|-
| {{cmd|r.in.poly|version=70}} || ? ||
|-
| {{cmd|r.in.srtm|version=70}} || ? ||
|-
| {{cmd|r.in.wms|version=70}} || ? ||
|-
| {{cmd|r.in.xyz|version=70}} || C ||
|-
| {{cmd|r.info|version=70}} || C ||
|-
| {{cmd|r.kappa|version=70}} || ? ||
|-
| {{cmd|r.lake|version=70}} || ? ||
|-
| {{cmd|r.li.cwed|version=70}} || ? ||
|-
| {{cmd|r.li.dominance|version=70}} || ? ||
|-
| {{cmd|r.li.edgedensity|version=70}} || ? ||
|-
| {{cmd|r.li.mpa|version=70}} || ? ||
|-
| {{cmd|r.li.mps|version=70}} || ? ||
|-
| {{cmd|r.li.padcv|version=70}} || ? ||
|-
| {{cmd|r.li.padrange|version=70}} || ? ||
|-
| {{cmd|r.li.padsd|version=70}} || ? ||
|-
| {{cmd|r.li.patchdensity|version=70}} || ? ||
|-
| {{cmd|r.li.patchnum|version=70}} || ? ||
|-
| {{cmd|r.li.richness|version=70}} || ? ||
|-
| {{cmd|r.li.shannon|version=70}} || ? ||
|-
| {{cmd|r.li.shape|version=70}} || ? ||
|-
| {{cmd|r.li.simpson|version=70}} || ? ||
|-
| {{cmd|r.los|version=70}} || ? ||
|-
| {{cmd|r.mapcalc|version=70}} || C ||
|-
| {{cmd|r.mask|version=70}} || C ||
|-
| {{cmd|r.mfilter|version=70}} || ? ||
|-
| {{cmd|r.mode|version=70}} || ? ||
|-
| {{cmd|r.neighbors|version=70}} || C ||
|-
| {{cmd|r.null|version=70}} || C ||
|-
| {{cmd|r.out.arc|version=70}} || ? ||
|-
| {{cmd|r.out.ascii|version=70}} || ? ||
|-
| {{cmd|r.out.bin|version=70}} || ? ||
|-
| {{cmd|r.out.gdal|version=70}} || ? ||
|-
| {{cmd|r.out.gridatb|version=70}} || ? ||
|-
| {{cmd|r.out.mat|version=70}} || ? ||
|-
| {{cmd|r.out.mpeg|version=70}} || ? ||
|-
| {{cmd|r.out.png|version=70}} || ? ||
|-
| {{cmd|r.out.pov|version=70}} || ? ||
|-
| {{cmd|r.out.ppm|version=70}} || ? ||
|-
| {{cmd|r.out.ppm3|version=70}} || ? ||
|-
| {{cmd|r.out.tiff|version=70}} || ? ||
|-
| {{cmd|r.out.vrml|version=70}} || ? ||
|-
| {{cmd|r.out.vtk|version=70}} || ? ||
|-
| {{cmd|r.out.xyz|version=70}} || ? ||
|-
| {{cmd|r.param.scale|version=70}} || ? ||
|-
| {{cmd|r.patch|version=70}} || C ||
|-
| {{cmd|r.plane|version=70}} || ? ||
|-
| {{cmd|r.profile|version=70}} || ? ||
|-
| {{cmd|r.proj|version=70}} || C ||
|-
| {{cmd|r.quant|version=70}} || ? ||
|-
| {{cmd|r.quantile|version=70}} || ? ||
|-
| {{cmd|r.random|version=70}} || ? ||
|-
| {{cmd|r.random.cells|version=70}} || ? ||
|-
| {{cmd|r.random.surface|version=70}} || ? ||
|-
| {{cmd|r.reclass|version=70}} || ? ||
|-
| {{cmd|r.reclass.area|version=70}} || ? ||
|-
| {{cmd|r.recode|version=70}} || C ||
|-
| {{cmd|r.region|version=70}} || ? ||
|-
| {{cmd|r.regression.line|version=70}} || C ||
|-
| {{cmd|r.report|version=70}} || ? ||
|-
| {{cmd|r.resamp.bspline|version=70}} || C ||
|-
| {{cmd|r.resamp.filter|version=70}} || ? ||
|-
| {{cmd|r.resamp.interp|version=70}} || C ||
|-
| {{cmd|r.resamp.rst|version=70}} || ? ||
|-
| {{cmd|r.resamp.stats|version=70}} || ? ||
|-
| {{cmd|r.resample|version=70}} || ? ||
|-
| {{cmd|r.rescale|version=70}} || ? ||
|-
| {{cmd|r.rescale.eq|version=70}} || ? ||
|-
| {{cmd|r.ros|version=70}} || ? ||
|-
| {{cmd|r.series|version=70}} || C ||
|-
| {{cmd|r.shaded.relief|version=70}} || C ||
|-
| {{cmd|r.sim.sediment|version=70}} || HY ||
|-
| {{cmd|r.sim.water|version=70}} || HY ||
|-
| {{cmd|r.slope.aspect|version=70}} || ? ||
|-
| {{cmd|r.solute.transport|version=70}} || ? ||
|-
| {{cmd|r.spread|version=70}} || ? ||
|-
| {{cmd|r.spreadpath|version=70}} || ? ||
|-
| {{cmd|r.statistics|version=70}} || ? ||
|-
| {{cmd|r.statistics2|version=70}} || ? ||
|-
| {{cmd|r.statistics3|version=70}} || ? ||
|-
| {{cmd|r.stats|version=70}} || ? ||
|-
| {{cmd|r.sun|version=70}} || ? ||
|-
| {{cmd|r.sunmask|version=70}} || ? ||
|-
| {{cmd|r.support|version=70}} || C||
|-
| {{cmd|r.support.stats|version=70}} || ? ||
|-
| {{cmd|r.surf.area|version=70}} || ? ||
|-
| {{cmd|r.surf.contour|version=70}} || ? ||
|-
| {{cmd|r.surf.fractal|version=70}} || ? ||
|-
| {{cmd|r.surf.gauss|version=70}} || ? ||
|-
| {{cmd|r.surf.idw|version=70}} || ? ||
|-
| {{cmd|r.surf.idw2|version=70}} || ? ||
|-
| {{cmd|r.surf.random|version=70}} || ? ||
|-
| {{cmd|r.terraflow|version=70}} || HY ||
|-
| {{cmd|r.texture|version=70}} || ? ||
|-
| {{cmd|r.thin|version=70}} || ? ||
|-
| {{cmd|r.tileset|version=70}} || ? ||
|-
| {{cmd|r.timestamp|version=70}} || ? ||
|-
| {{cmd|r.to.rast3|version=70}} || ? ||
|-
| {{cmd|r.to.rast3elev|version=70}} || ? ||
|-
| {{cmd|r.to.vect|version=70}} || C ||
|-
| {{cmd|r.topidx|version=70}} || HY ||
|-
| {{cmd|r.topmodel|version=70}} || HY ||
|-
| {{cmd|r.transect|version=70}} || ? ||
|-
| {{cmd|r.univar|version=70}} || C ||
|-
| {{cmd|r.uslek|version=70}} || ? ||
|-
| {{cmd|r.usler|version=70}} || ? ||
|-
| {{cmd|r.volume|version=70}} || ? ||
|-
| {{cmd|r.walk|version=70}} || ? ||
|-
| {{cmd|r.water.outlet|version=70}} || HY ||
|-
| {{cmd|r.watershed|version=70}} || HY ||
|-
| {{cmd|r.what|version=70}} || C ||
|-
| {{cmd|r.what.color|version=70}} || ? ||
|-
|}

=== 3D raster ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|r3.cross.rast|version=70}} || T || 3D Raster
|-
| {{cmd|r3.gwflow|version=70}} || T || 3D Raster
|-
| {{cmd|r3.in.ascii|version=70}} || T || 3D Raster
|-
| {{cmd|r3.in.v5d|version=70}} || T || 3D Raster
|-
| {{cmd|r3.info|version=70}} || T || 3D Raster
|-
| {{cmd|r3.mapcalc|version=70}} || T || 3D Raster
|-
| {{cmd|r3.mask|version=70}} || T || 3D Raster
|-
| {{cmd|r3.mkdspf|version=70}} || T || 3D Raster
|-
| {{cmd|r3.null|version=70}} || T || 3D Raster
|-
| {{cmd|r3.out.ascii|version=70}} || T || 3D Raster
|-
| {{cmd|r3.out.v5d|version=70}} || T || 3D Raster
|-
| {{cmd|r3.out.vtk|version=70}} || T || 3D Raster
|-
| {{cmd|r3.stats|version=70}} || T || 3D Raster
|-
| {{cmd|r3.timestamp|version=70}} || T || 3D Raster
|-
| {{cmd|r3.to.rast|version=70}} || T || 3D Raster
|-
| {{cmd|r3.univar|version=70}} || T || 3D Raster
|-
|}

=== Vector ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|v.autokrige|version=70}} || ? ||
|-
| {{cmd|v.buffer|version=70}} || ? ||
|-
| {{cmd|v.build|version=70}} || ? ||
|-
| {{cmd|v.build.all|version=70}} || ? ||
|-
| {{cmd|v.build.polylines|version=70}} || ? ||
|-
| {{cmd|v.category|version=70}} || ? ||
|-
| {{cmd|v.centroids|version=70}} || ? ||
|-
| {{cmd|v.class|version=70}} || ? ||
|-
| {{cmd|v.clean|version=70}} || ? ||
|-
| {{cmd|v.colors|version=70}} || ? ||
|-
| {{cmd|v.convert|version=70}} || ? ||
|-
| {{cmd|v.convert.all|version=70}} || ? ||
|-
| {{cmd|v.db.addcolumn|version=70}} || ? ||
|-
| {{cmd|v.db.addtable|version=70}} || ? ||
|-
| {{cmd|v.db.connect|version=70}} || ? ||
|-
| {{cmd|v.db.dropcolumn|version=70}} || ? ||
|-
| {{cmd|v.db.droprow|version=70}} || ? ||
|-
| {{cmd|v.db.droptable|version=70}} || ? ||
|-
| {{cmd|v.db.join|version=70}} || ? ||
|-
| {{cmd|v.db.reconnect.all|version=70}} || ? ||
|-
| {{cmd|v.db.renamecolumn|version=70}} || ? ||
|-
| {{cmd|v.db.select|version=70}} || ? ||
|-
| {{cmd|v.db.univar|version=70}} || ? ||
|-
| {{cmd|v.db.update|version=70}} || ? ||
|-
| {{cmd|v.delaunay|version=70}} || ? ||
|-
| {{cmd|v.dissolve|version=70}} || ? ||
|-
| {{cmd|v.distance|version=70}} || ? ||
|-
| {{cmd|v.drape|version=70}} || ? ||
|-
| {{cmd|v.edit|version=70}} || ? ||
|-
| {{cmd|v.external|version=70}} || ? ||
|-
| {{cmd|v.extract|version=70}} || ? ||
|-
| {{cmd|v.extrude|version=70}} || ? ||
|-
| {{cmd|v.generalize|version=70}} || ? ||
|-
| {{cmd|v.hull|version=70}} || ? ||
|-
| {{cmd|v.in.ascii|version=70}} || ? ||
|-
| {{cmd|v.in.db|version=70}} || ? ||
|-
| {{cmd|v.in.dxf|version=70}} || ? ||
|-
| {{cmd|v.in.e00|version=70}} || ? ||
|-
| {{cmd|v.in.geonames|version=70}} || ? ||
|-
| {{cmd|v.in.gns|version=70}} || ? ||
|-
| {{cmd|v.in.lines|version=70}} || ? ||
|-
| {{cmd|v.in.mapgen|version=70}} || ? ||
|-
| {{cmd|v.in.ogr|version=70}} || ? ||
|-
| {{cmd|v.in.postgis|version=70}} || ? ||
|-
| {{cmd|v.in.region|version=70}} || ? ||
|-
| {{cmd|v.in.sites|version=70}} || ? ||
|-
| {{cmd|v.in.sites.all|version=70}} || ? ||
|-
| {{cmd|v.in.wfs|version=70}} || ? ||
|-
| {{cmd|v.info|version=70}} || ? ||
|-
| {{cmd|v.kcv|version=70}} || ? ||
|-
| {{cmd|v.kernel|version=70}} || ? ||
|-
| {{cmd|v.krige|version=70}} || ? ||
|-
| {{cmd|v.label|version=70}} || ? ||
|-
| {{cmd|v.lidar.correction|version=70}} || ? ||
|-
| {{cmd|v.lidar.edgedetection|version=70}} || ? ||
|-
| {{cmd|v.lidar.growing|version=70}} || ? ||
|-
| {{cmd|v.lrs.create|version=70}} || ? ||
|-
| {{cmd|v.lrs.label|version=70}} || ? ||
|-
| {{cmd|v.lrs.segment|version=70}} || ? ||
|-
| {{cmd|v.lrs.where|version=70}} || ? ||
|-
| {{cmd|v.mkgrid|version=70}} || ? ||
|-
| {{cmd|v.neighbors|version=70}} || ? ||
|-
| {{cmd|v.net|version=70}} || ? ||
|-
| {{cmd|v.net.alloc|version=70}} || ? ||
|-
| {{cmd|v.net.allpairs|version=70}} || ? ||
|-
| {{cmd|v.net.bridge|version=70}} || ? ||
|-
| {{cmd|v.net.centrality|version=70}} || ? ||
|-
| {{cmd|v.net.components|version=70}} || ? ||
|-
| {{cmd|v.net.connectivity|version=70}} || ? ||
|-
| {{cmd|v.net.distance|version=70}} || ? ||
|-
| {{cmd|v.net.flow|version=70}} || ? ||
|-
| {{cmd|v.net.iso|version=70}} || ? ||
|-
| {{cmd|v.net.path|version=70}} || ? ||
|-
| {{cmd|v.net.salesman|version=70}} || ? ||
|-
| {{cmd|v.net.spanningtree|version=70}} || ? ||
|-
| {{cmd|v.net.steiner|version=70}} || ? ||
|-
| {{cmd|v.net.timetable|version=70}} || ? ||
|-
| {{cmd|v.net.visibility|version=70}} || ? ||
|-
| {{cmd|v.normal|version=70}} || ? ||
|-
| {{cmd|v.out.ascii|version=70}} || ? ||
|-
| {{cmd|v.out.dxf|version=70}} || ? ||
|-
| {{cmd|v.out.gps|version=70}} || ? ||
|-
| {{cmd|v.out.ogr|version=70}} || ? ||
|-
| {{cmd|v.out.postgis|version=70}} || ? ||
|-
| {{cmd|v.out.pov|version=70}} || ? ||
|-
| {{cmd|v.out.svg|version=70}} || ? ||
|-
| {{cmd|v.out.vtk|version=70}} || ? ||
|-
| {{cmd|v.outlier|version=70}} || ? ||
|-
| {{cmd|v.overlay|version=70}} || ? ||
|-
| {{cmd|v.parallel|version=70}} || ? ||
|-
| {{cmd|v.patch|version=70}} || ? ||
|-
| {{cmd|v.perturb|version=70}} || ? ||
|-
| {{cmd|v.proj|version=70}} || ? ||
|-
| {{cmd|v.qcount|version=70}} || ? ||
|-
| {{cmd|v.random|version=70}} || ? ||
|-
| {{cmd|v.rast.stats|version=70}} || ? ||
|-
| {{cmd|v.reclass|version=70}} || ? ||
|-
| {{cmd|v.report|version=70}} || ? ||
|-
| {{cmd|v.sample|version=70}} || ? ||
|-
| {{cmd|v.segment|version=70}} || ? ||
|-
| {{cmd|v.select|version=70}} || ? ||
|-
| {{cmd|v.split|version=70}} || ? ||
|-
| {{cmd|v.support|version=70}} || ? ||
|-
| {{cmd|v.surf.bspline|version=70}} || ? ||
|-
| {{cmd|v.surf.idw|version=70}} || ? ||
|-
| {{cmd|v.surf.rst|version=70}} || ? ||
|-
| {{cmd|v.to.3d|version=70}} || ? ||
|-
| {{cmd|v.to.db|version=70}} || ? ||
|-
| {{cmd|v.to.points|version=70}} || ? ||
|-
| {{cmd|v.to.rast|version=70}} || ? ||
|-
| {{cmd|v.to.rast3|version=70}} || ? ||
|-
| {{cmd|v.transform|version=70}} || ? ||
|-
| {{cmd|v.type|version=70}} || ? ||
|-
| {{cmd|v.univar|version=70}} || ? ||
|-
| {{cmd|v.vol.rst|version=70}} || ? ||
|-
| {{cmd|v.voronoi|version=70}} || ? ||
|-
| {{cmd|v.what|version=70}} || ? ||
|-
| {{cmd|v.what.rast|version=70}} || ? ||
|-
| {{cmd|v.what.vect|version=70}} || ? ||
|-
|}

=== Various ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|nviz|version=70}} || ? ||
|-
| {{cmd|nviz_cmd|version=70}} || ? ||
|-
| {{cmd|wximgview|version=70}} || ? ||
|-
| {{cmd|wxpyimgview|version=70}} || ? ||
|-
| {{cmd|xganim|version=70}} || ? ||
|-
| {{cmd|ximgview|version=70}} || ? ||
|-
|}

== List of selected AddOns modules ==

See [[GRASS AddOns]] for full list of available modules. Feel free to extend this list.

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)''' || '''Note'''
|-
| {{AddonCmd|r.stream.angle}} || T || HY ||
|-
| {{AddonCmd|r.seg}} || T || IM || It could be rename to `i.seg`
|-
| {{AddonCmd|i.topocorr}} || T || IM ||
|-
| {{AddonCmd|r.diversity}} || T || LA ||
|-
| {{AddonCmd|Ps.output}} || ? || ||
|-
| ... || ? || ||
|-
|}

== How to implement ==

=== propose 1 ===
* add html tag <param> in the description.html with these options:
<param name = "core"> for core module
<param name = "tool" value="tool_code/codes"> for toolbox
<param name = "addons" [value="tool_code/codes"]> for addons, value is optional

* create a script to generate a xml file for each toolbox
* add toolbox option in g.extension to read the xml and install the modules

[[Category:Development]]

Toolboxes

2011-05-08T03:48:28Z

⚠️Helena: /* Raster */

* See [http://lists.osgeo.org/pipermail/grass-dev/2010-April/050210.html original post by Jarosław Jasiewicz]

* Discussion about the suitability of the proposed change on the [[Talk:GRASS_repository_layout_proposal|talk]] side of this wiki page; discussion of the possible method on this side of the page.

<pre>
Hi all!

That rather radical ideas I present here are rather for future, at least for GRASS 8,
but I'd like present it now for long-term reflection.

Probably all notice that for over two years there is big increase in add-on repository
(including me). There are modules of different quality: from fully GRASS toolsets,
to shell or python scripts, from actively developed tools to abandoned,
from all-purpose tools to very specialized etc. I also think that that activity
will be grown due to substitute shell script by python

Similar situation is in main GRASS branch: there are modules for all like conversion tools,
interpolation methods, georeferencing etc, and very specialized modules for very limited
group of users (like wild fire), there are also some modules out of date.

I'm not enthusiastic about moving new modules into main branch. Almost every module has
different coding style and it will lasting in future that GRASS would be difficult to maintain.
On the other hand some people complains that some interesting modules are only available as
add-ons (I assume for some reasons they cannot install it)

So my suggestion is to rearrange future GRASS form two layers (main branch/add-on) into
three layers architecture:

1) GRASS core layer: much limited limited than now, only GIS environment and basic,
all-puropse tools, slow changes, great stability
2) GRASS toolset layer: oficcial GRASS thematic tools and toolsets (like terrain analysis,
hydrological analysis, photo-interpretation, landscape analysis etc,) every toolset with its
maintainer, rapid development, new ready to use tools after quality control may appear here,
also some of current main branch tool shall be moved to that layer
3) GRASS community layer: everything else like experimental, actively development new tools,
that what do not pass quality control, simple scripts, etc....

What benefits:
for developers and contributors: much clear situation and better publication path.
Toolset layer should be much more open for new tools than current GRASS main branch

for users: faster access to new tools.
There is no doubt that new tools are faster developed (less risk) than GRASS core
Binaries with toolsets could be maintained as separate apt/urpmi/pacman/yum/exe etc packages,
so it may appear in linux repository separetly form GRASS core.

There is only loose ideas. Most of them are of course taken from R (core/toolsets/rest of packages;
separate core and package development) but I think it is worth of some discuss ...

regards
Jarek
</pre>
__TOC__
== Repository layout ==
=== Current repository layout ===

<pre>
- grass
|- trunk
|- raster/
|- vector/
|- ...

- grass-addons
|- raster/
|- vector/
|- ...
</pre>

=== Proposed repository layout ===

<pre>
- grass
|- trunk
|- raster/
|- vector/
|- ...

- grass-tools
|- trunk
|- raster/
|- vector/
|- ...

- grass-addons
|- raster/
|- vector/
|- ...
</pre>

== Proposed toolboxes ==

'''Toolbox''' is a topic-based set of modules used for solving common GIS analysis, like hydrology, networking, LRS, etc. Toolbox should be easily installed by the user using {{cmd|g.extension|version=70}}

* add toolbox

g.extension toolbox=hydrology operation=add

Source code of the selected modules is downloaded from SVN, compiled and afterwards also installed to the user-specified (~/.grass7) or system (/usr/lib/grass7) directory.

Give the possibility with a flag (like -a) to install also modules from addons related that toolbox

g.extension -a toolbox=hydrology operation=add

* remove toolbox

g.extension toolbox=hydrology operation=remove

* list of modules of selected toolbox

g.extension -l toolbox=hydrology

User can also add/remove selected module

g.extension module=r.stream.angle operation=add

=== List of toolboxes ===
{|class="wikitable"
|'''Toolbox name''' || '''Toolbox code''' || '''Description'''||'''Correlate toolbox'''
|-
| ''3D Raster''
| R3
| All `r3.*` modules
|
|-
| ''3D Visualization''
| V3
| {{cmd|nviz_cmd|version=70}}
|
|-
| ''Cartography''
| CA
| {{cmd|ps.map|version=70}}, {{AddonCmd|ps.output}}
|
|-
| ''Database''
| DB
| All `db.*` modules
| ''Vector analysis''
|-
| ''Geostatistcal''
| GS
| {{cmd|v.krige|version=70}} maybe other
|
|-
| ''GUI''
| GI
| [[wxGUI]]
|
|-
| ''Hydrology''
| HY
| {{cmd|r.watershed|version=70}}, {{cmd|r.terraflow|version=70}}, `r.stream.*` modules in addons, maybe other, r.flow, r.sim.water, r.sim.sediment
| ''Raster analysis''
|-
| ''Imagery''
| IM
| All `i.*` modules, selected r.* modules
|
|-
| ''Landascape analysis''
| LA
| All `r.li.*` modules, maybe other
| ''Raster analysis''
|-
| ''Lidar analysis''
| LI
| All `v.lidar.*` modules, {{cmd|v.surf.bspline|version=70}}, r.in.xyz
|
|-
| ''Linear Reference Systems''
| LS
| All `v.lrs.*` modules
| ''Vector analysis''
|-
| ''Network analysis''
| NA
| All `v.net.*` modules, maybe other
| ''Vector analysis''
|-
| ''Raster analysis''
| RA
| A lot of basic `r.*` modules (like {{cmd|r.buffer,|version=70}} {{cmd|r.reclass|version=70}}, {{cmd|r.fillnull|version=70}}...)
|
|-
| ''Terrain analysis''
| TA
| Different kind of analysis: soil ({{cmd|r.sun,|version=70}}), terrain ({{cmd|r.slope.aspect|version=70}}, {{cmd|r.los|version=70}}), geomorphometry ({{cmd|r.param.scale|version=70}})
| ''Raster analysis''
|-
| ''Vector analysis''
| VA
| A lot of basic `v.*` modules (like {{cmd|v.buffer|version=70}}, {{cmd|v.centroid|version=70}}, {{cmd|v.overlay|version=70}}...)
| ''Database''
|}

== List of modules (trunk) ==

=== Display ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|d.barscale|version=70}} || ? ||
|-
| {{cmd|d.colorlist|version=70}} || ? ||
|-
| {{cmd|d.colortable|version=70}} || ? ||
|-
| {{cmd|d.correlate|version=70}} || ? ||
|-
| {{cmd|d.erase|version=70}} || ? ||
|-
| {{cmd|d.font|version=70}} || ? ||
|-
| {{cmd|d.fontlist|version=70}} || ? ||
|-
| {{cmd|d.geodesic|version=70}} || ? ||
|-
| {{cmd|d.graph|version=70}} || ? ||
|-
| {{cmd|d.grid|version=70}} || ? ||
|-
| {{cmd|d.his|version=70}} || ? ||
|-
| {{cmd|d.histogram|version=70}} || ? ||
|-
| {{cmd|d.info|version=70}} || ? ||
|-
| {{cmd|d.labels|version=70}} || ? ||
|-
| {{cmd|d.legend|version=70}} || ? ||
|-
| {{cmd|d.linegraph|version=70}} || ? ||
|-
| {{cmd|d.nviz|version=70}} || ? ||
|-
| {{cmd|d.path|version=70}} || ? ||
|-
| {{cmd|d.polar|version=70}} || ? ||
|-
| {{cmd|d.profile|version=70}} || ? ||
|-
| {{cmd|d.rast|version=70}} || ? ||
|-
| {{cmd|d.rast.arrow|version=70}} || ? ||
|-
| {{cmd|d.rast.edit|version=70}} || ? ||
|-
| {{cmd|d.rast.leg|version=70}} || ? ||
|-
| {{cmd|d.rast.num|version=70}} || ? ||
|-
| {{cmd|d.rgb|version=70}} || ? ||
|-
| {{cmd|d.rhumbline|version=70}} || ? ||
|-
| {{cmd|d.shadedmap|version=70}} || ? ||
|-
| {{cmd|d.text|version=70}} || ? ||
|-
| {{cmd|d.thematic.area|version=70}} || ? ||
|-
| {{cmd|d.title|version=70}} || ? ||
|-
| {{cmd|d.vect|version=70}} || ? ||
|-
| {{cmd|d.vect.chart|version=70}} || ? ||
|-
| {{cmd|d.vect.thematic|version=70}} || ? ||
|-
| {{cmd|d.where|version=70}} || ? ||
|-
|}

=== Database ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|db.columns|version=70}} || ? ||
|-
| {{cmd|db.connect|version=70}} || ? ||
|-
| {{cmd|db.copy|version=70}} || ? ||
|-
| {{cmd|db.createdb|version=70}} || ? ||
|-
| {{cmd|db.databases|version=70}} || ? ||
|-
| {{cmd|db.describe|version=70}} || ? ||
|-
| {{cmd|db.drivers|version=70}} || ? ||
|-
| {{cmd|db.dropcolumn|version=70}} || ? ||
|-
| {{cmd|db.dropdb|version=70}} || ? ||
|-
| {{cmd|db.droptable|version=70}} || ? ||
|-
| {{cmd|db.droptable|version=70}} || ? ||
|-
| {{cmd|db.execute|version=70}} || ? ||
|-
| {{cmd|db.in.ogr|version=70}} || ? ||
|-
| {{cmd|db.login|version=70}} || ? ||
|-
| {{cmd|db.out.ogr|version=70}} || ? ||
|-
| {{cmd|db.select|version=70}} || ? ||
|-
| {{cmd|db.tables|version=70}} || ? ||
|-
| {{cmd|db.test|version=70}} || ? ||
|-
|}

=== General ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|g.access|version=70}} || C ||
|-
| {{cmd|g.cairocomp|version=70}} || C ||
|-
| {{cmd|g.copy|version=70}} || C ||
|-
| {{cmd|g.dirseps|version=70}} || C ||
|-
| {{cmd|g.extension|version=70}} || C ||
|-
| {{cmd|g.filename|version=70}} || C ||
|-
| {{cmd|g.findetc|version=70}} || C ||
|-
| {{cmd|g.findfile|version=70}} || C ||
|-
| {{cmd|g.gisenv|version=70}} || C ||
|-
| {{cmd|g.gui|version=70}} || C ||
|-
| {{cmd|g.list|version=70}} || C ||
|-
| {{cmd|g.manual|version=70}} || C ||
|-
| {{cmd|g.mapset|version=70}} || C ||
|-
| {{cmd|g.mapsets|version=70}} || C ||
|-
| {{cmd|g.message|version=70}} || C ||
|-
| {{cmd|g.mkfontcap|version=70}} || C ||
|-
| {{cmd|g.mlist|version=70}} || C ||
|-
| {{cmd|g.mremove|version=70}} || C ||
|-
| {{cmd|g.parser|version=70}} || C ||
|-
| {{cmd|g.pnmcomp|version=70}} || C ||
|-
| {{cmd|g.ppmtopng|version=70}} || C ||
|-
| {{cmd|g.proj|version=70}} || C ||
|-
| {{cmd|g.region|version=70}} || C ||
|-
| {{cmd|g.remove|version=70}} || C ||
|-
| {{cmd|g.rename|version=70}} || C ||
|-
| {{cmd|g.tempfile|version=70}} || C ||
|-
| {{cmd|g.transform|version=70}} || C ||
|-
| {{cmd|g.version|version=70}} || C ||
|-
|}

=== Imagery ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|i.albedo|version=70}} || ? ||
|-
| {{cmd|i.atcorr|version=70}} || ? ||
|-
| {{cmd|i.biomass|version=70}} || ? ||
|-
| {{cmd|i.cca|version=70}} || ? ||
|-
| {{cmd|i.cluster|version=70}} || ? ||
|-
| {{cmd|i.eb.eta|version=70}} || ? ||
|-
| {{cmd|i.eb.evapfr|version=70}} || ? ||
|-
| {{cmd|i.eb.h_SEBAL01|version=70}} || ? ||
|-
| {{cmd|i.eb.soilheatflux|version=70}} || ? ||
|-
| {{cmd|i.emissivity|version=70}} || ? ||
|-
| {{cmd|i.evapo.time|version=70}} || ? ||
|-
| {{cmd|i.fft|version=70}} || ? ||
|-
| {{cmd|i.fusion.brovey|version=70}} || ? ||
|-
| {{cmd|i.gensig|version=70}} || ? ||
|-
| {{cmd|i.gensigset|version=70}} || ? ||
|-
| {{cmd|i.group|version=70}} || ? ||
|-
| {{cmd|i.his.rgb|version=70}} || ? ||
|-
| {{cmd|i.ifft|version=70}} || ? ||
|-
| {{cmd|i.image.mosaic|version=70}} || ? ||
|-
| {{cmd|i.in.spotvgt|version=70}} || ? ||
|-
| {{cmd|i.landsat.rgb|version=70}} || ? ||
|-
| {{cmd|i.latlong|version=70}} || ? ||
|-
| {{cmd|i.maxlik|version=70}} || ? ||
|-
| {{cmd|i.modis.qc|version=70}} || ? ||
|-
| {{cmd|i.oif|version=70}} || ? ||
|-
| {{cmd|i.pca|version=70}} || ? ||
|-
| {{cmd|i.rectify|version=70}} || ? ||
|-
| {{cmd|i.rgb.his|version=70}} || ? ||
|-
| {{cmd|i.smap|version=70}} || ? ||
|-
| {{cmd|i.spectral|version=70}} || ? ||
|-
| {{cmd|i.sunhours|version=70}} || ? ||
|-
| {{cmd|i.target|version=70}} || ? ||
|-
| {{cmd|i.tasscap|version=70}} || ? ||
|-
| {{cmd|i.vi|version=70}} || ? ||
|-
| {{cmd|i.zc|version=70}} || ? ||
|-
|}

=== Misc ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|m.cogo|version=70}} || ? ||
|-
| {{cmd|m.measure|version=70}} || ? ||
|-
| {{cmd|m.proj|version=70}} || ? ||
|-
|}

=== Postscript ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|ps.map|version=70}} || ? ||
|-
|}

=== Raster ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|r.basins.fill|version=70}} || ? ||
|-
| {{cmd|r.bitpattern|version=70}} || ? ||
|-
| {{cmd|r.blend|version=70}} || ? ||
|-
| {{cmd|r.buffer|version=70}} || ? ||
|-
| {{cmd|r.buffer2|version=70}} || ? ||
|-
| {{cmd|r.carve|version=70}} || ? ||
|-
| {{cmd|r.category|version=70}} || ? ||
|-
| {{cmd|r.circle|version=70}} || ? ||
|-
| {{cmd|r.clump|version=70}} || ? ||
|-
| {{cmd|r.coin|version=70}} || ? ||
|-
| {{cmd|r.colors|version=70}} || C ||
|-
| {{cmd|r.colors.out|version=70}} || ? ||
|-
| {{cmd|r.colors.stddev|version=70}} || ? ||
|-
| {{cmd|r.composite|version=70}} || ? ||
|-
| {{cmd|r.compress|version=70}} || ? ||
|-
| {{cmd|r.contour|version=70}} || ? ||
|-
| {{cmd|r.cost|version=70}} || ? ||
|-
| {{cmd|r.covar|version=70}} || ? ||
|-
| {{cmd|r.cross|version=70}} || ? ||
|-
| {{cmd|r.describe|version=70}} || ? ||
|-
| {{cmd|r.distance|version=70}} || ? ||
|-
| {{cmd|r.drain|version=70}} || ? ||
|-
| {{cmd|r.external|version=70}} || ? ||
|-
| {{cmd|r.external.out|version=70}} || ? ||
|-
| {{cmd|r.fill.dir|version=70}} || ? ||
|-
| {{cmd|r.fillnulls|version=70}} || ? ||
|-
| {{cmd|r.flow|version=70}} || HY ||
|-
| {{cmd|r.grow|version=70}} || ? ||
|-
| {{cmd|r.grow.distance|version=70}} || ? ||
|-
| {{cmd|r.gwflow|version=70}} || ? ||
|-
| {{cmd|r.his|version=70}} || ? ||
|-
| {{cmd|r.horizon|version=70}} || ? ||
|-
| {{cmd|r.in.arc|version=70}} || ? ||
|-
| {{cmd|r.in.ascii|version=70}} || ? ||
|-
| {{cmd|r.in.aster|version=70}} || ? ||
|-
| {{cmd|r.in.bin|version=70}} || ? ||
|-
| {{cmd|r.in.gdal|version=70}} || ? ||
|-
| {{cmd|r.in.gridatb|version=70}} || ? ||
|-
| {{cmd|r.in.mat|version=70}} || ? ||
|-
| {{cmd|r.in.png|version=70}} || ? ||
|-
| {{cmd|r.in.poly|version=70}} || ? ||
|-
| {{cmd|r.in.srtm|version=70}} || ? ||
|-
| {{cmd|r.in.wms|version=70}} || ? ||
|-
| {{cmd|r.in.xyz|version=70}} || C ||
|-
| {{cmd|r.info|version=70}} || C ||
|-
| {{cmd|r.kappa|version=70}} || ? ||
|-
| {{cmd|r.lake|version=70}} || ? ||
|-
| {{cmd|r.li.cwed|version=70}} || ? ||
|-
| {{cmd|r.li.dominance|version=70}} || ? ||
|-
| {{cmd|r.li.edgedensity|version=70}} || ? ||
|-
| {{cmd|r.li.mpa|version=70}} || ? ||
|-
| {{cmd|r.li.mps|version=70}} || ? ||
|-
| {{cmd|r.li.padcv|version=70}} || ? ||
|-
| {{cmd|r.li.padrange|version=70}} || ? ||
|-
| {{cmd|r.li.padsd|version=70}} || ? ||
|-
| {{cmd|r.li.patchdensity|version=70}} || ? ||
|-
| {{cmd|r.li.patchnum|version=70}} || ? ||
|-
| {{cmd|r.li.richness|version=70}} || ? ||
|-
| {{cmd|r.li.shannon|version=70}} || ? ||
|-
| {{cmd|r.li.shape|version=70}} || ? ||
|-
| {{cmd|r.li.simpson|version=70}} || ? ||
|-
| {{cmd|r.los|version=70}} || ? ||
|-
| {{cmd|r.mapcalc|version=70}} || C ||
|-
| {{cmd|r.mask|version=70}} || C ||
|-
| {{cmd|r.mfilter|version=70}} || ? ||
|-
| {{cmd|r.mode|version=70}} || ? ||
|-
| {{cmd|r.neighbors|version=70}} || C ||
|-
| {{cmd|r.null|version=70}} || C ||
|-
| {{cmd|r.out.arc|version=70}} || ? ||
|-
| {{cmd|r.out.ascii|version=70}} || ? ||
|-
| {{cmd|r.out.bin|version=70}} || ? ||
|-
| {{cmd|r.out.gdal|version=70}} || ? ||
|-
| {{cmd|r.out.gridatb|version=70}} || ? ||
|-
| {{cmd|r.out.mat|version=70}} || ? ||
|-
| {{cmd|r.out.mpeg|version=70}} || ? ||
|-
| {{cmd|r.out.png|version=70}} || ? ||
|-
| {{cmd|r.out.pov|version=70}} || ? ||
|-
| {{cmd|r.out.ppm|version=70}} || ? ||
|-
| {{cmd|r.out.ppm3|version=70}} || ? ||
|-
| {{cmd|r.out.tiff|version=70}} || ? ||
|-
| {{cmd|r.out.vrml|version=70}} || ? ||
|-
| {{cmd|r.out.vtk|version=70}} || ? ||
|-
| {{cmd|r.out.xyz|version=70}} || ? ||
|-
| {{cmd|r.param.scale|version=70}} || ? ||
|-
| {{cmd|r.patch|version=70}} || C ||
|-
| {{cmd|r.plane|version=70}} || ? ||
|-
| {{cmd|r.profile|version=70}} || ? ||
|-
| {{cmd|r.proj|version=70}} || C ||
|-
| {{cmd|r.quant|version=70}} || ? ||
|-
| {{cmd|r.quantile|version=70}} || ? ||
|-
| {{cmd|r.random|version=70}} || ? ||
|-
| {{cmd|r.random.cells|version=70}} || ? ||
|-
| {{cmd|r.random.surface|version=70}} || ? ||
|-
| {{cmd|r.reclass|version=70}} || ? ||
|-
| {{cmd|r.reclass.area|version=70}} || ? ||
|-
| {{cmd|r.recode|version=70}} || C ||
|-
| {{cmd|r.region|version=70}} || ? ||
|-
| {{cmd|r.regression.line|version=70}} || C ||
|-
| {{cmd|r.report|version=70}} || ? ||
|-
| {{cmd|r.resamp.bspline|version=70}} || C ||
|-
| {{cmd|r.resamp.filter|version=70}} || ? ||
|-
| {{cmd|r.resamp.interp|version=70}} || C ||
|-
| {{cmd|r.resamp.rst|version=70}} || ? ||
|-
| {{cmd|r.resamp.stats|version=70}} || ? ||
|-
| {{cmd|r.resample|version=70}} || ? ||
|-
| {{cmd|r.rescale|version=70}} || ? ||
|-
| {{cmd|r.rescale.eq|version=70}} || ? ||
|-
| {{cmd|r.ros|version=70}} || ? ||
|-
| {{cmd|r.series|version=70}} || C ||
|-
| {{cmd|r.shaded.relief|version=70}} || C ||
|-
| {{cmd|r.sim.sediment|version=70}} || HY ||
|-
| {{cmd|r.sim.water|version=70}} || HY ||
|-
| {{cmd|r.slope.aspect|version=70}} || ? ||
|-
| {{cmd|r.solute.transport|version=70}} || ? ||
|-
| {{cmd|r.spread|version=70}} || ? ||
|-
| {{cmd|r.spreadpath|version=70}} || ? ||
|-
| {{cmd|r.statistics|version=70}} || ? ||
|-
| {{cmd|r.statistics2|version=70}} || ? ||
|-
| {{cmd|r.statistics3|version=70}} || ? ||
|-
| {{cmd|r.stats|version=70}} || ? ||
|-
| {{cmd|r.sun|version=70}} || ? ||
|-
| {{cmd|r.sunmask|version=70}} || ? ||
|-
| {{cmd|r.support|version=70}} || C||
|-
| {{cmd|r.support.stats|version=70}} || ? ||
|-
| {{cmd|r.surf.area|version=70}} || ? ||
|-
| {{cmd|r.surf.contour|version=70}} || ? ||
|-
| {{cmd|r.surf.fractal|version=70}} || ? ||
|-
| {{cmd|r.surf.gauss|version=70}} || ? ||
|-
| {{cmd|r.surf.idw|version=70}} || ? ||
|-
| {{cmd|r.surf.idw2|version=70}} || ? ||
|-
| {{cmd|r.surf.random|version=70}} || ? ||
|-
| {{cmd|r.terraflow|version=70}} || HY ||
|-
| {{cmd|r.texture|version=70}} || ? ||
|-
| {{cmd|r.thin|version=70}} || ? ||
|-
| {{cmd|r.tileset|version=70}} || ? ||
|-
| {{cmd|r.timestamp|version=70}} || ? ||
|-
| {{cmd|r.to.rast3|version=70}} || ? ||
|-
| {{cmd|r.to.rast3elev|version=70}} || ? ||
|-
| {{cmd|r.to.vect|version=70}} || C ||
|-
| {{cmd|r.topidx|version=70}} || HY ||
|-
| {{cmd|r.topmodel|version=70}} || HY ||
|-
| {{cmd|r.transect|version=70}} || ? ||
|-
| {{cmd|r.univar|version=70}} || C ||
|-
| {{cmd|r.uslek|version=70}} || ? ||
|-
| {{cmd|r.usler|version=70}} || ? ||
|-
| {{cmd|r.volume|version=70}} || ? ||
|-
| {{cmd|r.walk|version=70}} || ? ||
|-
| {{cmd|r.water.outlet|version=70}} || HY ||
|-
| {{cmd|r.watershed|version=70}} || HY ||
|-
| {{cmd|r.what|version=70}} || C ||
|-
| {{cmd|r.what.color|version=70}} || ? ||
|-
|}

=== 3D raster ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|r3.cross.rast|version=70}} || T || 3D Raster
|-
| {{cmd|r3.gwflow|version=70}} || T || 3D Raster
|-
| {{cmd|r3.in.ascii|version=70}} || T || 3D Raster
|-
| {{cmd|r3.in.v5d|version=70}} || T || 3D Raster
|-
| {{cmd|r3.info|version=70}} || T || 3D Raster
|-
| {{cmd|r3.mapcalc|version=70}} || T || 3D Raster
|-
| {{cmd|r3.mask|version=70}} || T || 3D Raster
|-
| {{cmd|r3.mkdspf|version=70}} || T || 3D Raster
|-
| {{cmd|r3.null|version=70}} || T || 3D Raster
|-
| {{cmd|r3.out.ascii|version=70}} || T || 3D Raster
|-
| {{cmd|r3.out.v5d|version=70}} || T || 3D Raster
|-
| {{cmd|r3.out.vtk|version=70}} || T || 3D Raster
|-
| {{cmd|r3.stats|version=70}} || T || 3D Raster
|-
| {{cmd|r3.timestamp|version=70}} || T || 3D Raster
|-
| {{cmd|r3.to.rast|version=70}} || T || 3D Raster
|-
| {{cmd|r3.univar|version=70}} || T || 3D Raster
|-
|}

=== Vector ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|v.autokrige|version=70}} || ? ||
|-
| {{cmd|v.buffer|version=70}} || ? ||
|-
| {{cmd|v.build|version=70}} || ? ||
|-
| {{cmd|v.build.all|version=70}} || ? ||
|-
| {{cmd|v.build.polylines|version=70}} || ? ||
|-
| {{cmd|v.category|version=70}} || ? ||
|-
| {{cmd|v.centroids|version=70}} || ? ||
|-
| {{cmd|v.class|version=70}} || ? ||
|-
| {{cmd|v.clean|version=70}} || ? ||
|-
| {{cmd|v.colors|version=70}} || ? ||
|-
| {{cmd|v.convert|version=70}} || ? ||
|-
| {{cmd|v.convert.all|version=70}} || ? ||
|-
| {{cmd|v.db.addcolumn|version=70}} || ? ||
|-
| {{cmd|v.db.addtable|version=70}} || ? ||
|-
| {{cmd|v.db.connect|version=70}} || ? ||
|-
| {{cmd|v.db.dropcolumn|version=70}} || ? ||
|-
| {{cmd|v.db.droprow|version=70}} || ? ||
|-
| {{cmd|v.db.droptable|version=70}} || ? ||
|-
| {{cmd|v.db.join|version=70}} || ? ||
|-
| {{cmd|v.db.reconnect.all|version=70}} || ? ||
|-
| {{cmd|v.db.renamecolumn|version=70}} || ? ||
|-
| {{cmd|v.db.select|version=70}} || ? ||
|-
| {{cmd|v.db.univar|version=70}} || ? ||
|-
| {{cmd|v.db.update|version=70}} || ? ||
|-
| {{cmd|v.delaunay|version=70}} || ? ||
|-
| {{cmd|v.dissolve|version=70}} || ? ||
|-
| {{cmd|v.distance|version=70}} || ? ||
|-
| {{cmd|v.drape|version=70}} || ? ||
|-
| {{cmd|v.edit|version=70}} || ? ||
|-
| {{cmd|v.external|version=70}} || ? ||
|-
| {{cmd|v.extract|version=70}} || ? ||
|-
| {{cmd|v.extrude|version=70}} || ? ||
|-
| {{cmd|v.generalize|version=70}} || ? ||
|-
| {{cmd|v.hull|version=70}} || ? ||
|-
| {{cmd|v.in.ascii|version=70}} || ? ||
|-
| {{cmd|v.in.db|version=70}} || ? ||
|-
| {{cmd|v.in.dxf|version=70}} || ? ||
|-
| {{cmd|v.in.e00|version=70}} || ? ||
|-
| {{cmd|v.in.geonames|version=70}} || ? ||
|-
| {{cmd|v.in.gns|version=70}} || ? ||
|-
| {{cmd|v.in.lines|version=70}} || ? ||
|-
| {{cmd|v.in.mapgen|version=70}} || ? ||
|-
| {{cmd|v.in.ogr|version=70}} || ? ||
|-
| {{cmd|v.in.postgis|version=70}} || ? ||
|-
| {{cmd|v.in.region|version=70}} || ? ||
|-
| {{cmd|v.in.sites|version=70}} || ? ||
|-
| {{cmd|v.in.sites.all|version=70}} || ? ||
|-
| {{cmd|v.in.wfs|version=70}} || ? ||
|-
| {{cmd|v.info|version=70}} || ? ||
|-
| {{cmd|v.kcv|version=70}} || ? ||
|-
| {{cmd|v.kernel|version=70}} || ? ||
|-
| {{cmd|v.krige|version=70}} || ? ||
|-
| {{cmd|v.label|version=70}} || ? ||
|-
| {{cmd|v.lidar.correction|version=70}} || ? ||
|-
| {{cmd|v.lidar.edgedetection|version=70}} || ? ||
|-
| {{cmd|v.lidar.growing|version=70}} || ? ||
|-
| {{cmd|v.lrs.create|version=70}} || ? ||
|-
| {{cmd|v.lrs.label|version=70}} || ? ||
|-
| {{cmd|v.lrs.segment|version=70}} || ? ||
|-
| {{cmd|v.lrs.where|version=70}} || ? ||
|-
| {{cmd|v.mkgrid|version=70}} || ? ||
|-
| {{cmd|v.neighbors|version=70}} || ? ||
|-
| {{cmd|v.net|version=70}} || ? ||
|-
| {{cmd|v.net.alloc|version=70}} || ? ||
|-
| {{cmd|v.net.allpairs|version=70}} || ? ||
|-
| {{cmd|v.net.bridge|version=70}} || ? ||
|-
| {{cmd|v.net.centrality|version=70}} || ? ||
|-
| {{cmd|v.net.components|version=70}} || ? ||
|-
| {{cmd|v.net.connectivity|version=70}} || ? ||
|-
| {{cmd|v.net.distance|version=70}} || ? ||
|-
| {{cmd|v.net.flow|version=70}} || ? ||
|-
| {{cmd|v.net.iso|version=70}} || ? ||
|-
| {{cmd|v.net.path|version=70}} || ? ||
|-
| {{cmd|v.net.salesman|version=70}} || ? ||
|-
| {{cmd|v.net.spanningtree|version=70}} || ? ||
|-
| {{cmd|v.net.steiner|version=70}} || ? ||
|-
| {{cmd|v.net.timetable|version=70}} || ? ||
|-
| {{cmd|v.net.visibility|version=70}} || ? ||
|-
| {{cmd|v.normal|version=70}} || ? ||
|-
| {{cmd|v.out.ascii|version=70}} || ? ||
|-
| {{cmd|v.out.dxf|version=70}} || ? ||
|-
| {{cmd|v.out.gps|version=70}} || ? ||
|-
| {{cmd|v.out.ogr|version=70}} || ? ||
|-
| {{cmd|v.out.postgis|version=70}} || ? ||
|-
| {{cmd|v.out.pov|version=70}} || ? ||
|-
| {{cmd|v.out.svg|version=70}} || ? ||
|-
| {{cmd|v.out.vtk|version=70}} || ? ||
|-
| {{cmd|v.outlier|version=70}} || ? ||
|-
| {{cmd|v.overlay|version=70}} || ? ||
|-
| {{cmd|v.parallel|version=70}} || ? ||
|-
| {{cmd|v.patch|version=70}} || ? ||
|-
| {{cmd|v.perturb|version=70}} || ? ||
|-
| {{cmd|v.proj|version=70}} || ? ||
|-
| {{cmd|v.qcount|version=70}} || ? ||
|-
| {{cmd|v.random|version=70}} || ? ||
|-
| {{cmd|v.rast.stats|version=70}} || ? ||
|-
| {{cmd|v.reclass|version=70}} || ? ||
|-
| {{cmd|v.report|version=70}} || ? ||
|-
| {{cmd|v.sample|version=70}} || ? ||
|-
| {{cmd|v.segment|version=70}} || ? ||
|-
| {{cmd|v.select|version=70}} || ? ||
|-
| {{cmd|v.split|version=70}} || ? ||
|-
| {{cmd|v.support|version=70}} || ? ||
|-
| {{cmd|v.surf.bspline|version=70}} || ? ||
|-
| {{cmd|v.surf.idw|version=70}} || ? ||
|-
| {{cmd|v.surf.rst|version=70}} || ? ||
|-
| {{cmd|v.to.3d|version=70}} || ? ||
|-
| {{cmd|v.to.db|version=70}} || ? ||
|-
| {{cmd|v.to.points|version=70}} || ? ||
|-
| {{cmd|v.to.rast|version=70}} || ? ||
|-
| {{cmd|v.to.rast3|version=70}} || ? ||
|-
| {{cmd|v.transform|version=70}} || ? ||
|-
| {{cmd|v.type|version=70}} || ? ||
|-
| {{cmd|v.univar|version=70}} || ? ||
|-
| {{cmd|v.vol.rst|version=70}} || ? ||
|-
| {{cmd|v.voronoi|version=70}} || ? ||
|-
| {{cmd|v.what|version=70}} || ? ||
|-
| {{cmd|v.what.rast|version=70}} || ? ||
|-
| {{cmd|v.what.vect|version=70}} || ? ||
|-
|}

=== Various ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|nviz|version=70}} || ? ||
|-
| {{cmd|nviz_cmd|version=70}} || ? ||
|-
| {{cmd|wximgview|version=70}} || ? ||
|-
| {{cmd|wxpyimgview|version=70}} || ? ||
|-
| {{cmd|xganim|version=70}} || ? ||
|-
| {{cmd|ximgview|version=70}} || ? ||
|-
|}

== List of selected AddOns modules ==

See [[GRASS AddOns]] for full list of available modules. Feel free to extend this list.

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)''' || '''Note'''
|-
| {{AddonCmd|r.stream.angle}} || T || HY ||
|-
| {{AddonCmd|r.seg}} || T || IM || It could be rename to `i.seg`
|-
| {{AddonCmd|i.topocorr}} || T || IM ||
|-
| {{AddonCmd|r.diversity}} || T || LA ||
|-
| {{AddonCmd|Ps.output}} || ? || ||
|-
| ... || ? || ||
|-
|}

== How to implement ==

=== propose 1 ===
* add html tag <param> in the description.html with these options:
<param name = "core"> for core module
<param name = "tool" value="tool_code/codes"> for toolbox
<param name = "addons" [value="tool_code/codes"]> for addons, value is optional

* create a script to generate a xml file for each toolbox
* add toolbox option in g.extension to read the xml and install the modules

[[Category:Development]]

Toolboxes

2011-05-08T03:34:09Z

⚠️Helena: /* List of toolboxes */

* See [http://lists.osgeo.org/pipermail/grass-dev/2010-April/050210.html original post by Jarosław Jasiewicz]

* Discussion about the suitability of the proposed change on the [[Talk:GRASS_repository_layout_proposal|talk]] side of this wiki page; discussion of the possible method on this side of the page.

<pre>
Hi all!

That rather radical ideas I present here are rather for future, at least for GRASS 8,
but I'd like present it now for long-term reflection.

Probably all notice that for over two years there is big increase in add-on repository
(including me). There are modules of different quality: from fully GRASS toolsets,
to shell or python scripts, from actively developed tools to abandoned,
from all-purpose tools to very specialized etc. I also think that that activity
will be grown due to substitute shell script by python

Similar situation is in main GRASS branch: there are modules for all like conversion tools,
interpolation methods, georeferencing etc, and very specialized modules for very limited
group of users (like wild fire), there are also some modules out of date.

I'm not enthusiastic about moving new modules into main branch. Almost every module has
different coding style and it will lasting in future that GRASS would be difficult to maintain.
On the other hand some people complains that some interesting modules are only available as
add-ons (I assume for some reasons they cannot install it)

So my suggestion is to rearrange future GRASS form two layers (main branch/add-on) into
three layers architecture:

1) GRASS core layer: much limited limited than now, only GIS environment and basic,
all-puropse tools, slow changes, great stability
2) GRASS toolset layer: oficcial GRASS thematic tools and toolsets (like terrain analysis,
hydrological analysis, photo-interpretation, landscape analysis etc,) every toolset with its
maintainer, rapid development, new ready to use tools after quality control may appear here,
also some of current main branch tool shall be moved to that layer
3) GRASS community layer: everything else like experimental, actively development new tools,
that what do not pass quality control, simple scripts, etc....

What benefits:
for developers and contributors: much clear situation and better publication path.
Toolset layer should be much more open for new tools than current GRASS main branch

for users: faster access to new tools.
There is no doubt that new tools are faster developed (less risk) than GRASS core
Binaries with toolsets could be maintained as separate apt/urpmi/pacman/yum/exe etc packages,
so it may appear in linux repository separetly form GRASS core.

There is only loose ideas. Most of them are of course taken from R (core/toolsets/rest of packages;
separate core and package development) but I think it is worth of some discuss ...

regards
Jarek
</pre>
__TOC__
== Repository layout ==
=== Current repository layout ===

<pre>
- grass
|- trunk
|- raster/
|- vector/
|- ...

- grass-addons
|- raster/
|- vector/
|- ...
</pre>

=== Proposed repository layout ===

<pre>
- grass
|- trunk
|- raster/
|- vector/
|- ...

- grass-tools
|- trunk
|- raster/
|- vector/
|- ...

- grass-addons
|- raster/
|- vector/
|- ...
</pre>

== Proposed toolboxes ==

'''Toolbox''' is a topic-based set of modules used for solving common GIS analysis, like hydrology, networking, LRS, etc. Toolbox should be easily installed by the user using {{cmd|g.extension|version=70}}

* add toolbox

g.extension toolbox=hydrology operation=add

Source code of the selected modules is downloaded from SVN, compiled and afterwards also installed to the user-specified (~/.grass7) or system (/usr/lib/grass7) directory.

Give the possibility with a flag (like -a) to install also modules from addons related that toolbox

g.extension -a toolbox=hydrology operation=add

* remove toolbox

g.extension toolbox=hydrology operation=remove

* list of modules of selected toolbox

g.extension -l toolbox=hydrology

User can also add/remove selected module

g.extension module=r.stream.angle operation=add

=== List of toolboxes ===
{|class="wikitable"
|'''Toolbox name''' || '''Toolbox code''' || '''Description'''||'''Correlate toolbox'''
|-
| ''3D Raster''
| R3
| All `r3.*` modules
|
|-
| ''3D Visualization''
| V3
| {{cmd|nviz_cmd|version=70}}
|
|-
| ''Cartography''
| CA
| {{cmd|ps.map|version=70}}, {{AddonCmd|ps.output}}
|
|-
| ''Database''
| DB
| All `db.*` modules
| ''Vector analysis''
|-
| ''Geostatistcal''
| GS
| {{cmd|v.krige|version=70}} maybe other
|
|-
| ''GUI''
| GI
| [[wxGUI]]
|
|-
| ''Hydrology''
| HY
| {{cmd|r.watershed|version=70}}, {{cmd|r.terraflow|version=70}}, `r.stream.*` modules in addons, maybe other, r.flow, r.sim.water, r.sim.sediment
| ''Raster analysis''
|-
| ''Imagery''
| IM
| All `i.*` modules, selected r.* modules
|
|-
| ''Landascape analysis''
| LA
| All `r.li.*` modules, maybe other
| ''Raster analysis''
|-
| ''Lidar analysis''
| LI
| All `v.lidar.*` modules, {{cmd|v.surf.bspline|version=70}}, r.in.xyz
|
|-
| ''Linear Reference Systems''
| LS
| All `v.lrs.*` modules
| ''Vector analysis''
|-
| ''Network analysis''
| NA
| All `v.net.*` modules, maybe other
| ''Vector analysis''
|-
| ''Raster analysis''
| RA
| A lot of basic `r.*` modules (like {{cmd|r.buffer,|version=70}} {{cmd|r.reclass|version=70}}, {{cmd|r.fillnull|version=70}}...)
|
|-
| ''Terrain analysis''
| TA
| Different kind of analysis: soil ({{cmd|r.sun,|version=70}}), terrain ({{cmd|r.slope.aspect|version=70}}, {{cmd|r.los|version=70}}), geomorphometry ({{cmd|r.param.scale|version=70}})
| ''Raster analysis''
|-
| ''Vector analysis''
| VA
| A lot of basic `v.*` modules (like {{cmd|v.buffer|version=70}}, {{cmd|v.centroid|version=70}}, {{cmd|v.overlay|version=70}}...)
| ''Database''
|}

== List of modules (trunk) ==

=== Display ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|d.barscale|version=70}} || ? ||
|-
| {{cmd|d.colorlist|version=70}} || ? ||
|-
| {{cmd|d.colortable|version=70}} || ? ||
|-
| {{cmd|d.correlate|version=70}} || ? ||
|-
| {{cmd|d.erase|version=70}} || ? ||
|-
| {{cmd|d.font|version=70}} || ? ||
|-
| {{cmd|d.fontlist|version=70}} || ? ||
|-
| {{cmd|d.geodesic|version=70}} || ? ||
|-
| {{cmd|d.graph|version=70}} || ? ||
|-
| {{cmd|d.grid|version=70}} || ? ||
|-
| {{cmd|d.his|version=70}} || ? ||
|-
| {{cmd|d.histogram|version=70}} || ? ||
|-
| {{cmd|d.info|version=70}} || ? ||
|-
| {{cmd|d.labels|version=70}} || ? ||
|-
| {{cmd|d.legend|version=70}} || ? ||
|-
| {{cmd|d.linegraph|version=70}} || ? ||
|-
| {{cmd|d.nviz|version=70}} || ? ||
|-
| {{cmd|d.path|version=70}} || ? ||
|-
| {{cmd|d.polar|version=70}} || ? ||
|-
| {{cmd|d.profile|version=70}} || ? ||
|-
| {{cmd|d.rast|version=70}} || ? ||
|-
| {{cmd|d.rast.arrow|version=70}} || ? ||
|-
| {{cmd|d.rast.edit|version=70}} || ? ||
|-
| {{cmd|d.rast.leg|version=70}} || ? ||
|-
| {{cmd|d.rast.num|version=70}} || ? ||
|-
| {{cmd|d.rgb|version=70}} || ? ||
|-
| {{cmd|d.rhumbline|version=70}} || ? ||
|-
| {{cmd|d.shadedmap|version=70}} || ? ||
|-
| {{cmd|d.text|version=70}} || ? ||
|-
| {{cmd|d.thematic.area|version=70}} || ? ||
|-
| {{cmd|d.title|version=70}} || ? ||
|-
| {{cmd|d.vect|version=70}} || ? ||
|-
| {{cmd|d.vect.chart|version=70}} || ? ||
|-
| {{cmd|d.vect.thematic|version=70}} || ? ||
|-
| {{cmd|d.where|version=70}} || ? ||
|-
|}

=== Database ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|db.columns|version=70}} || ? ||
|-
| {{cmd|db.connect|version=70}} || ? ||
|-
| {{cmd|db.copy|version=70}} || ? ||
|-
| {{cmd|db.createdb|version=70}} || ? ||
|-
| {{cmd|db.databases|version=70}} || ? ||
|-
| {{cmd|db.describe|version=70}} || ? ||
|-
| {{cmd|db.drivers|version=70}} || ? ||
|-
| {{cmd|db.dropcolumn|version=70}} || ? ||
|-
| {{cmd|db.dropdb|version=70}} || ? ||
|-
| {{cmd|db.droptable|version=70}} || ? ||
|-
| {{cmd|db.droptable|version=70}} || ? ||
|-
| {{cmd|db.execute|version=70}} || ? ||
|-
| {{cmd|db.in.ogr|version=70}} || ? ||
|-
| {{cmd|db.login|version=70}} || ? ||
|-
| {{cmd|db.out.ogr|version=70}} || ? ||
|-
| {{cmd|db.select|version=70}} || ? ||
|-
| {{cmd|db.tables|version=70}} || ? ||
|-
| {{cmd|db.test|version=70}} || ? ||
|-
|}

=== General ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|g.access|version=70}} || C ||
|-
| {{cmd|g.cairocomp|version=70}} || C ||
|-
| {{cmd|g.copy|version=70}} || C ||
|-
| {{cmd|g.dirseps|version=70}} || C ||
|-
| {{cmd|g.extension|version=70}} || C ||
|-
| {{cmd|g.filename|version=70}} || C ||
|-
| {{cmd|g.findetc|version=70}} || C ||
|-
| {{cmd|g.findfile|version=70}} || C ||
|-
| {{cmd|g.gisenv|version=70}} || C ||
|-
| {{cmd|g.gui|version=70}} || C ||
|-
| {{cmd|g.list|version=70}} || C ||
|-
| {{cmd|g.manual|version=70}} || C ||
|-
| {{cmd|g.mapset|version=70}} || C ||
|-
| {{cmd|g.mapsets|version=70}} || C ||
|-
| {{cmd|g.message|version=70}} || C ||
|-
| {{cmd|g.mkfontcap|version=70}} || C ||
|-
| {{cmd|g.mlist|version=70}} || C ||
|-
| {{cmd|g.mremove|version=70}} || C ||
|-
| {{cmd|g.parser|version=70}} || C ||
|-
| {{cmd|g.pnmcomp|version=70}} || C ||
|-
| {{cmd|g.ppmtopng|version=70}} || C ||
|-
| {{cmd|g.proj|version=70}} || C ||
|-
| {{cmd|g.region|version=70}} || C ||
|-
| {{cmd|g.remove|version=70}} || C ||
|-
| {{cmd|g.rename|version=70}} || C ||
|-
| {{cmd|g.tempfile|version=70}} || C ||
|-
| {{cmd|g.transform|version=70}} || C ||
|-
| {{cmd|g.version|version=70}} || C ||
|-
|}

=== Imagery ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|i.albedo|version=70}} || ? ||
|-
| {{cmd|i.atcorr|version=70}} || ? ||
|-
| {{cmd|i.biomass|version=70}} || ? ||
|-
| {{cmd|i.cca|version=70}} || ? ||
|-
| {{cmd|i.cluster|version=70}} || ? ||
|-
| {{cmd|i.eb.eta|version=70}} || ? ||
|-
| {{cmd|i.eb.evapfr|version=70}} || ? ||
|-
| {{cmd|i.eb.h_SEBAL01|version=70}} || ? ||
|-
| {{cmd|i.eb.soilheatflux|version=70}} || ? ||
|-
| {{cmd|i.emissivity|version=70}} || ? ||
|-
| {{cmd|i.evapo.time|version=70}} || ? ||
|-
| {{cmd|i.fft|version=70}} || ? ||
|-
| {{cmd|i.fusion.brovey|version=70}} || ? ||
|-
| {{cmd|i.gensig|version=70}} || ? ||
|-
| {{cmd|i.gensigset|version=70}} || ? ||
|-
| {{cmd|i.group|version=70}} || ? ||
|-
| {{cmd|i.his.rgb|version=70}} || ? ||
|-
| {{cmd|i.ifft|version=70}} || ? ||
|-
| {{cmd|i.image.mosaic|version=70}} || ? ||
|-
| {{cmd|i.in.spotvgt|version=70}} || ? ||
|-
| {{cmd|i.landsat.rgb|version=70}} || ? ||
|-
| {{cmd|i.latlong|version=70}} || ? ||
|-
| {{cmd|i.maxlik|version=70}} || ? ||
|-
| {{cmd|i.modis.qc|version=70}} || ? ||
|-
| {{cmd|i.oif|version=70}} || ? ||
|-
| {{cmd|i.pca|version=70}} || ? ||
|-
| {{cmd|i.rectify|version=70}} || ? ||
|-
| {{cmd|i.rgb.his|version=70}} || ? ||
|-
| {{cmd|i.smap|version=70}} || ? ||
|-
| {{cmd|i.spectral|version=70}} || ? ||
|-
| {{cmd|i.sunhours|version=70}} || ? ||
|-
| {{cmd|i.target|version=70}} || ? ||
|-
| {{cmd|i.tasscap|version=70}} || ? ||
|-
| {{cmd|i.vi|version=70}} || ? ||
|-
| {{cmd|i.zc|version=70}} || ? ||
|-
|}

=== Misc ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|m.cogo|version=70}} || ? ||
|-
| {{cmd|m.measure|version=70}} || ? ||
|-
| {{cmd|m.proj|version=70}} || ? ||
|-
|}

=== Postscript ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|ps.map|version=70}} || ? ||
|-
|}

=== Raster ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|r.basins.fill|version=70}} || ? ||
|-
| {{cmd|r.bitpattern|version=70}} || ? ||
|-
| {{cmd|r.blend|version=70}} || ? ||
|-
| {{cmd|r.buffer|version=70}} || ? ||
|-
| {{cmd|r.buffer2|version=70}} || ? ||
|-
| {{cmd|r.carve|version=70}} || ? ||
|-
| {{cmd|r.category|version=70}} || ? ||
|-
| {{cmd|r.circle|version=70}} || ? ||
|-
| {{cmd|r.clump|version=70}} || ? ||
|-
| {{cmd|r.coin|version=70}} || ? ||
|-
| {{cmd|r.colors|version=70}} || ? ||
|-
| {{cmd|r.colors.out|version=70}} || ? ||
|-
| {{cmd|r.colors.stddev|version=70}} || ? ||
|-
| {{cmd|r.composite|version=70}} || ? ||
|-
| {{cmd|r.compress|version=70}} || ? ||
|-
| {{cmd|r.contour|version=70}} || ? ||
|-
| {{cmd|r.cost|version=70}} || ? ||
|-
| {{cmd|r.covar|version=70}} || ? ||
|-
| {{cmd|r.cross|version=70}} || ? ||
|-
| {{cmd|r.describe|version=70}} || ? ||
|-
| {{cmd|r.distance|version=70}} || ? ||
|-
| {{cmd|r.drain|version=70}} || ? ||
|-
| {{cmd|r.external|version=70}} || ? ||
|-
| {{cmd|r.external.out|version=70}} || ? ||
|-
| {{cmd|r.fill.dir|version=70}} || ? ||
|-
| {{cmd|r.fillnulls|version=70}} || ? ||
|-
| {{cmd|r.flow|version=70}} || ? ||
|-
| {{cmd|r.grow|version=70}} || ? ||
|-
| {{cmd|r.grow.distance|version=70}} || ? ||
|-
| {{cmd|r.gwflow|version=70}} || ? ||
|-
| {{cmd|r.his|version=70}} || ? ||
|-
| {{cmd|r.horizon|version=70}} || ? ||
|-
| {{cmd|r.in.arc|version=70}} || ? ||
|-
| {{cmd|r.in.ascii|version=70}} || ? ||
|-
| {{cmd|r.in.aster|version=70}} || ? ||
|-
| {{cmd|r.in.bin|version=70}} || ? ||
|-
| {{cmd|r.in.gdal|version=70}} || ? ||
|-
| {{cmd|r.in.gridatb|version=70}} || ? ||
|-
| {{cmd|r.in.mat|version=70}} || ? ||
|-
| {{cmd|r.in.png|version=70}} || ? ||
|-
| {{cmd|r.in.poly|version=70}} || ? ||
|-
| {{cmd|r.in.srtm|version=70}} || ? ||
|-
| {{cmd|r.in.wms|version=70}} || ? ||
|-
| {{cmd|r.in.xyz|version=70}} || ? ||
|-
| {{cmd|r.info|version=70}} || ? ||
|-
| {{cmd|r.kappa|version=70}} || ? ||
|-
| {{cmd|r.lake|version=70}} || ? ||
|-
| {{cmd|r.li.cwed|version=70}} || ? ||
|-
| {{cmd|r.li.dominance|version=70}} || ? ||
|-
| {{cmd|r.li.edgedensity|version=70}} || ? ||
|-
| {{cmd|r.li.mpa|version=70}} || ? ||
|-
| {{cmd|r.li.mps|version=70}} || ? ||
|-
| {{cmd|r.li.padcv|version=70}} || ? ||
|-
| {{cmd|r.li.padrange|version=70}} || ? ||
|-
| {{cmd|r.li.padsd|version=70}} || ? ||
|-
| {{cmd|r.li.patchdensity|version=70}} || ? ||
|-
| {{cmd|r.li.patchnum|version=70}} || ? ||
|-
| {{cmd|r.li.richness|version=70}} || ? ||
|-
| {{cmd|r.li.shannon|version=70}} || ? ||
|-
| {{cmd|r.li.shape|version=70}} || ? ||
|-
| {{cmd|r.li.simpson|version=70}} || ? ||
|-
| {{cmd|r.los|version=70}} || ? ||
|-
| {{cmd|r.mapcalc|version=70}} || ? ||
|-
| {{cmd|r.mask|version=70}} || ? ||
|-
| {{cmd|r.mfilter|version=70}} || ? ||
|-
| {{cmd|r.mode|version=70}} || ? ||
|-
| {{cmd|r.neighbors|version=70}} || ? ||
|-
| {{cmd|r.null|version=70}} || ? ||
|-
| {{cmd|r.out.arc|version=70}} || ? ||
|-
| {{cmd|r.out.ascii|version=70}} || ? ||
|-
| {{cmd|r.out.bin|version=70}} || ? ||
|-
| {{cmd|r.out.gdal|version=70}} || ? ||
|-
| {{cmd|r.out.gridatb|version=70}} || ? ||
|-
| {{cmd|r.out.mat|version=70}} || ? ||
|-
| {{cmd|r.out.mpeg|version=70}} || ? ||
|-
| {{cmd|r.out.png|version=70}} || ? ||
|-
| {{cmd|r.out.pov|version=70}} || ? ||
|-
| {{cmd|r.out.ppm|version=70}} || ? ||
|-
| {{cmd|r.out.ppm3|version=70}} || ? ||
|-
| {{cmd|r.out.tiff|version=70}} || ? ||
|-
| {{cmd|r.out.vrml|version=70}} || ? ||
|-
| {{cmd|r.out.vtk|version=70}} || ? ||
|-
| {{cmd|r.out.xyz|version=70}} || ? ||
|-
| {{cmd|r.param.scale|version=70}} || ? ||
|-
| {{cmd|r.patch|version=70}} || ? ||
|-
| {{cmd|r.plane|version=70}} || ? ||
|-
| {{cmd|r.profile|version=70}} || ? ||
|-
| {{cmd|r.proj|version=70}} || ? ||
|-
| {{cmd|r.quant|version=70}} || ? ||
|-
| {{cmd|r.quantile|version=70}} || ? ||
|-
| {{cmd|r.random|version=70}} || ? ||
|-
| {{cmd|r.random.cells|version=70}} || ? ||
|-
| {{cmd|r.random.surface|version=70}} || ? ||
|-
| {{cmd|r.reclass|version=70}} || ? ||
|-
| {{cmd|r.reclass.area|version=70}} || ? ||
|-
| {{cmd|r.recode|version=70}} || ? ||
|-
| {{cmd|r.region|version=70}} || ? ||
|-
| {{cmd|r.regression.line|version=70}} || ? ||
|-
| {{cmd|r.report|version=70}} || ? ||
|-
| {{cmd|r.resamp.bspline|version=70}} || ? ||
|-
| {{cmd|r.resamp.filter|version=70}} || ? ||
|-
| {{cmd|r.resamp.interp|version=70}} || ? ||
|-
| {{cmd|r.resamp.rst|version=70}} || ? ||
|-
| {{cmd|r.resamp.stats|version=70}} || ? ||
|-
| {{cmd|r.resample|version=70}} || ? ||
|-
| {{cmd|r.rescale|version=70}} || ? ||
|-
| {{cmd|r.rescale.eq|version=70}} || ? ||
|-
| {{cmd|r.ros|version=70}} || ? ||
|-
| {{cmd|r.series|version=70}} || ? ||
|-
| {{cmd|r.shaded.relief|version=70}} || ? ||
|-
| {{cmd|r.sim.sediment|version=70}} || ? ||
|-
| {{cmd|r.sim.water|version=70}} || ? ||
|-
| {{cmd|r.slope.aspect|version=70}} || ? ||
|-
| {{cmd|r.solute.transport|version=70}} || ? ||
|-
| {{cmd|r.spread|version=70}} || ? ||
|-
| {{cmd|r.spreadpath|version=70}} || ? ||
|-
| {{cmd|r.statistics|version=70}} || ? ||
|-
| {{cmd|r.statistics2|version=70}} || ? ||
|-
| {{cmd|r.statistics3|version=70}} || ? ||
|-
| {{cmd|r.stats|version=70}} || ? ||
|-
| {{cmd|r.sun|version=70}} || ? ||
|-
| {{cmd|r.sunmask|version=70}} || ? ||
|-
| {{cmd|r.support|version=70}} || ? ||
|-
| {{cmd|r.support.stats|version=70}} || ? ||
|-
| {{cmd|r.surf.area|version=70}} || ? ||
|-
| {{cmd|r.surf.contour|version=70}} || ? ||
|-
| {{cmd|r.surf.fractal|version=70}} || ? ||
|-
| {{cmd|r.surf.gauss|version=70}} || ? ||
|-
| {{cmd|r.surf.idw|version=70}} || ? ||
|-
| {{cmd|r.surf.idw2|version=70}} || ? ||
|-
| {{cmd|r.surf.random|version=70}} || ? ||
|-
| {{cmd|r.terraflow|version=70}} || ? ||
|-
| {{cmd|r.texture|version=70}} || ? ||
|-
| {{cmd|r.thin|version=70}} || ? ||
|-
| {{cmd|r.tileset|version=70}} || ? ||
|-
| {{cmd|r.timestamp|version=70}} || ? ||
|-
| {{cmd|r.to.rast3|version=70}} || ? ||
|-
| {{cmd|r.to.rast3elev|version=70}} || ? ||
|-
| {{cmd|r.to.vect|version=70}} || ? ||
|-
| {{cmd|r.topidx|version=70}} || ? ||
|-
| {{cmd|r.topmodel|version=70}} || ? ||
|-
| {{cmd|r.transect|version=70}} || ? ||
|-
| {{cmd|r.univar|version=70}} || ? ||
|-
| {{cmd|r.uslek|version=70}} || ? ||
|-
| {{cmd|r.usler|version=70}} || ? ||
|-
| {{cmd|r.volume|version=70}} || ? ||
|-
| {{cmd|r.walk|version=70}} || ? ||
|-
| {{cmd|r.water.outlet|version=70}} || ? ||
|-
| {{cmd|r.watershed|version=70}} || ? ||
|-
| {{cmd|r.what|version=70}} || ? ||
|-
| {{cmd|r.what.color|version=70}} || ? ||
|-
|}

=== 3D raster ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|r3.cross.rast|version=70}} || T || 3D Raster
|-
| {{cmd|r3.gwflow|version=70}} || T || 3D Raster
|-
| {{cmd|r3.in.ascii|version=70}} || T || 3D Raster
|-
| {{cmd|r3.in.v5d|version=70}} || T || 3D Raster
|-
| {{cmd|r3.info|version=70}} || T || 3D Raster
|-
| {{cmd|r3.mapcalc|version=70}} || T || 3D Raster
|-
| {{cmd|r3.mask|version=70}} || T || 3D Raster
|-
| {{cmd|r3.mkdspf|version=70}} || T || 3D Raster
|-
| {{cmd|r3.null|version=70}} || T || 3D Raster
|-
| {{cmd|r3.out.ascii|version=70}} || T || 3D Raster
|-
| {{cmd|r3.out.v5d|version=70}} || T || 3D Raster
|-
| {{cmd|r3.out.vtk|version=70}} || T || 3D Raster
|-
| {{cmd|r3.stats|version=70}} || T || 3D Raster
|-
| {{cmd|r3.timestamp|version=70}} || T || 3D Raster
|-
| {{cmd|r3.to.rast|version=70}} || T || 3D Raster
|-
| {{cmd|r3.univar|version=70}} || T || 3D Raster
|-
|}

=== Vector ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|v.autokrige|version=70}} || ? ||
|-
| {{cmd|v.buffer|version=70}} || ? ||
|-
| {{cmd|v.build|version=70}} || ? ||
|-
| {{cmd|v.build.all|version=70}} || ? ||
|-
| {{cmd|v.build.polylines|version=70}} || ? ||
|-
| {{cmd|v.category|version=70}} || ? ||
|-
| {{cmd|v.centroids|version=70}} || ? ||
|-
| {{cmd|v.class|version=70}} || ? ||
|-
| {{cmd|v.clean|version=70}} || ? ||
|-
| {{cmd|v.colors|version=70}} || ? ||
|-
| {{cmd|v.convert|version=70}} || ? ||
|-
| {{cmd|v.convert.all|version=70}} || ? ||
|-
| {{cmd|v.db.addcolumn|version=70}} || ? ||
|-
| {{cmd|v.db.addtable|version=70}} || ? ||
|-
| {{cmd|v.db.connect|version=70}} || ? ||
|-
| {{cmd|v.db.dropcolumn|version=70}} || ? ||
|-
| {{cmd|v.db.droprow|version=70}} || ? ||
|-
| {{cmd|v.db.droptable|version=70}} || ? ||
|-
| {{cmd|v.db.join|version=70}} || ? ||
|-
| {{cmd|v.db.reconnect.all|version=70}} || ? ||
|-
| {{cmd|v.db.renamecolumn|version=70}} || ? ||
|-
| {{cmd|v.db.select|version=70}} || ? ||
|-
| {{cmd|v.db.univar|version=70}} || ? ||
|-
| {{cmd|v.db.update|version=70}} || ? ||
|-
| {{cmd|v.delaunay|version=70}} || ? ||
|-
| {{cmd|v.dissolve|version=70}} || ? ||
|-
| {{cmd|v.distance|version=70}} || ? ||
|-
| {{cmd|v.drape|version=70}} || ? ||
|-
| {{cmd|v.edit|version=70}} || ? ||
|-
| {{cmd|v.external|version=70}} || ? ||
|-
| {{cmd|v.extract|version=70}} || ? ||
|-
| {{cmd|v.extrude|version=70}} || ? ||
|-
| {{cmd|v.generalize|version=70}} || ? ||
|-
| {{cmd|v.hull|version=70}} || ? ||
|-
| {{cmd|v.in.ascii|version=70}} || ? ||
|-
| {{cmd|v.in.db|version=70}} || ? ||
|-
| {{cmd|v.in.dxf|version=70}} || ? ||
|-
| {{cmd|v.in.e00|version=70}} || ? ||
|-
| {{cmd|v.in.geonames|version=70}} || ? ||
|-
| {{cmd|v.in.gns|version=70}} || ? ||
|-
| {{cmd|v.in.lines|version=70}} || ? ||
|-
| {{cmd|v.in.mapgen|version=70}} || ? ||
|-
| {{cmd|v.in.ogr|version=70}} || ? ||
|-
| {{cmd|v.in.postgis|version=70}} || ? ||
|-
| {{cmd|v.in.region|version=70}} || ? ||
|-
| {{cmd|v.in.sites|version=70}} || ? ||
|-
| {{cmd|v.in.sites.all|version=70}} || ? ||
|-
| {{cmd|v.in.wfs|version=70}} || ? ||
|-
| {{cmd|v.info|version=70}} || ? ||
|-
| {{cmd|v.kcv|version=70}} || ? ||
|-
| {{cmd|v.kernel|version=70}} || ? ||
|-
| {{cmd|v.krige|version=70}} || ? ||
|-
| {{cmd|v.label|version=70}} || ? ||
|-
| {{cmd|v.lidar.correction|version=70}} || ? ||
|-
| {{cmd|v.lidar.edgedetection|version=70}} || ? ||
|-
| {{cmd|v.lidar.growing|version=70}} || ? ||
|-
| {{cmd|v.lrs.create|version=70}} || ? ||
|-
| {{cmd|v.lrs.label|version=70}} || ? ||
|-
| {{cmd|v.lrs.segment|version=70}} || ? ||
|-
| {{cmd|v.lrs.where|version=70}} || ? ||
|-
| {{cmd|v.mkgrid|version=70}} || ? ||
|-
| {{cmd|v.neighbors|version=70}} || ? ||
|-
| {{cmd|v.net|version=70}} || ? ||
|-
| {{cmd|v.net.alloc|version=70}} || ? ||
|-
| {{cmd|v.net.allpairs|version=70}} || ? ||
|-
| {{cmd|v.net.bridge|version=70}} || ? ||
|-
| {{cmd|v.net.centrality|version=70}} || ? ||
|-
| {{cmd|v.net.components|version=70}} || ? ||
|-
| {{cmd|v.net.connectivity|version=70}} || ? ||
|-
| {{cmd|v.net.distance|version=70}} || ? ||
|-
| {{cmd|v.net.flow|version=70}} || ? ||
|-
| {{cmd|v.net.iso|version=70}} || ? ||
|-
| {{cmd|v.net.path|version=70}} || ? ||
|-
| {{cmd|v.net.salesman|version=70}} || ? ||
|-
| {{cmd|v.net.spanningtree|version=70}} || ? ||
|-
| {{cmd|v.net.steiner|version=70}} || ? ||
|-
| {{cmd|v.net.timetable|version=70}} || ? ||
|-
| {{cmd|v.net.visibility|version=70}} || ? ||
|-
| {{cmd|v.normal|version=70}} || ? ||
|-
| {{cmd|v.out.ascii|version=70}} || ? ||
|-
| {{cmd|v.out.dxf|version=70}} || ? ||
|-
| {{cmd|v.out.gps|version=70}} || ? ||
|-
| {{cmd|v.out.ogr|version=70}} || ? ||
|-
| {{cmd|v.out.postgis|version=70}} || ? ||
|-
| {{cmd|v.out.pov|version=70}} || ? ||
|-
| {{cmd|v.out.svg|version=70}} || ? ||
|-
| {{cmd|v.out.vtk|version=70}} || ? ||
|-
| {{cmd|v.outlier|version=70}} || ? ||
|-
| {{cmd|v.overlay|version=70}} || ? ||
|-
| {{cmd|v.parallel|version=70}} || ? ||
|-
| {{cmd|v.patch|version=70}} || ? ||
|-
| {{cmd|v.perturb|version=70}} || ? ||
|-
| {{cmd|v.proj|version=70}} || ? ||
|-
| {{cmd|v.qcount|version=70}} || ? ||
|-
| {{cmd|v.random|version=70}} || ? ||
|-
| {{cmd|v.rast.stats|version=70}} || ? ||
|-
| {{cmd|v.reclass|version=70}} || ? ||
|-
| {{cmd|v.report|version=70}} || ? ||
|-
| {{cmd|v.sample|version=70}} || ? ||
|-
| {{cmd|v.segment|version=70}} || ? ||
|-
| {{cmd|v.select|version=70}} || ? ||
|-
| {{cmd|v.split|version=70}} || ? ||
|-
| {{cmd|v.support|version=70}} || ? ||
|-
| {{cmd|v.surf.bspline|version=70}} || ? ||
|-
| {{cmd|v.surf.idw|version=70}} || ? ||
|-
| {{cmd|v.surf.rst|version=70}} || ? ||
|-
| {{cmd|v.to.3d|version=70}} || ? ||
|-
| {{cmd|v.to.db|version=70}} || ? ||
|-
| {{cmd|v.to.points|version=70}} || ? ||
|-
| {{cmd|v.to.rast|version=70}} || ? ||
|-
| {{cmd|v.to.rast3|version=70}} || ? ||
|-
| {{cmd|v.transform|version=70}} || ? ||
|-
| {{cmd|v.type|version=70}} || ? ||
|-
| {{cmd|v.univar|version=70}} || ? ||
|-
| {{cmd|v.vol.rst|version=70}} || ? ||
|-
| {{cmd|v.voronoi|version=70}} || ? ||
|-
| {{cmd|v.what|version=70}} || ? ||
|-
| {{cmd|v.what.rast|version=70}} || ? ||
|-
| {{cmd|v.what.vect|version=70}} || ? ||
|-
|}

=== Various ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|nviz|version=70}} || ? ||
|-
| {{cmd|nviz_cmd|version=70}} || ? ||
|-
| {{cmd|wximgview|version=70}} || ? ||
|-
| {{cmd|wxpyimgview|version=70}} || ? ||
|-
| {{cmd|xganim|version=70}} || ? ||
|-
| {{cmd|ximgview|version=70}} || ? ||
|-
|}

== List of selected AddOns modules ==

See [[GRASS AddOns]] for full list of available modules. Feel free to extend this list.

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)''' || '''Note'''
|-
| {{AddonCmd|r.stream.angle}} || T || HY ||
|-
| {{AddonCmd|r.seg}} || T || IM || It could be rename to `i.seg`
|-
| {{AddonCmd|i.topocorr}} || T || IM ||
|-
| {{AddonCmd|r.diversity}} || T || LA ||
|-
| {{AddonCmd|Ps.output}} || ? || ||
|-
| ... || ? || ||
|-
|}

== How to implement ==

=== propose 1 ===
* add html tag <param> in the description.html with these options:
<param name = "core"> for core module
<param name = "tool" value="tool_code/codes"> for toolbox
<param name = "addons" [value="tool_code/codes"]> for addons, value is optional

* create a script to generate a xml file for each toolbox
* add toolbox option in g.extension to read the xml and install the modules

[[Category:Development]]

Toolboxes

2011-05-08T03:30:50Z

⚠️Helena: /* List of toolboxes */

* See [http://lists.osgeo.org/pipermail/grass-dev/2010-April/050210.html original post by Jarosław Jasiewicz]

* Discussion about the suitability of the proposed change on the [[Talk:GRASS_repository_layout_proposal|talk]] side of this wiki page; discussion of the possible method on this side of the page.

<pre>
Hi all!

That rather radical ideas I present here are rather for future, at least for GRASS 8,
but I'd like present it now for long-term reflection.

Probably all notice that for over two years there is big increase in add-on repository
(including me). There are modules of different quality: from fully GRASS toolsets,
to shell or python scripts, from actively developed tools to abandoned,
from all-purpose tools to very specialized etc. I also think that that activity
will be grown due to substitute shell script by python

Similar situation is in main GRASS branch: there are modules for all like conversion tools,
interpolation methods, georeferencing etc, and very specialized modules for very limited
group of users (like wild fire), there are also some modules out of date.

I'm not enthusiastic about moving new modules into main branch. Almost every module has
different coding style and it will lasting in future that GRASS would be difficult to maintain.
On the other hand some people complains that some interesting modules are only available as
add-ons (I assume for some reasons they cannot install it)

So my suggestion is to rearrange future GRASS form two layers (main branch/add-on) into
three layers architecture:

1) GRASS core layer: much limited limited than now, only GIS environment and basic,
all-puropse tools, slow changes, great stability
2) GRASS toolset layer: oficcial GRASS thematic tools and toolsets (like terrain analysis,
hydrological analysis, photo-interpretation, landscape analysis etc,) every toolset with its
maintainer, rapid development, new ready to use tools after quality control may appear here,
also some of current main branch tool shall be moved to that layer
3) GRASS community layer: everything else like experimental, actively development new tools,
that what do not pass quality control, simple scripts, etc....

What benefits:
for developers and contributors: much clear situation and better publication path.
Toolset layer should be much more open for new tools than current GRASS main branch

for users: faster access to new tools.
There is no doubt that new tools are faster developed (less risk) than GRASS core
Binaries with toolsets could be maintained as separate apt/urpmi/pacman/yum/exe etc packages,
so it may appear in linux repository separetly form GRASS core.

There is only loose ideas. Most of them are of course taken from R (core/toolsets/rest of packages;
separate core and package development) but I think it is worth of some discuss ...

regards
Jarek
</pre>
__TOC__
== Repository layout ==
=== Current repository layout ===

<pre>
- grass
|- trunk
|- raster/
|- vector/
|- ...

- grass-addons
|- raster/
|- vector/
|- ...
</pre>

=== Proposed repository layout ===

<pre>
- grass
|- trunk
|- raster/
|- vector/
|- ...

- grass-tools
|- trunk
|- raster/
|- vector/
|- ...

- grass-addons
|- raster/
|- vector/
|- ...
</pre>

== Proposed toolboxes ==

'''Toolbox''' is a topic-based set of modules used for solving common GIS analysis, like hydrology, networking, LRS, etc. Toolbox should be easily installed by the user using {{cmd|g.extension|version=70}}

* add toolbox

g.extension toolbox=hydrology operation=add

Source code of the selected modules is downloaded from SVN, compiled and afterwards also installed to the user-specified (~/.grass7) or system (/usr/lib/grass7) directory.

Give the possibility with a flag (like -a) to install also modules from addons related that toolbox

g.extension -a toolbox=hydrology operation=add

* remove toolbox

g.extension toolbox=hydrology operation=remove

* list of modules of selected toolbox

g.extension -l toolbox=hydrology

User can also add/remove selected module

g.extension module=r.stream.angle operation=add

=== List of toolboxes ===
{|class="wikitable"
|'''Toolbox name''' || '''Toolbox code''' || '''Description'''||'''Correlate toolbox'''
|-
| ''3D Raster''
| R3
| All `r3.*` modules
|
|-
| ''3D Visualization''
| V3
| {{cmd|nviz_cmd|version=70}}
|
|-
| ''Cartography''
| CA
| {{cmd|ps.map|version=70}}, {{AddonCmd|ps.output}}
|
|-
| ''Database''
| DB
| All `db.*` modules
| ''Vector analysis''
|-
| ''Geostatistcal''
| GS
| {{cmd|v.krige|version=70}} maybe other
|
|-
| ''GUI''
| GI
| [[wxGUI]]
|
|-
| ''Hydrology''
| HY
| {{cmd|r.watershed|version=70}}, {{cmd|r.terraflow|version=70}}, `r.stream.*` modules in addons, maybe other, r.flow, r.sim.water, r.sim.sediment
| ''Raster analysis''
|-
| ''Imagery''
| IM
| All `i.*` modules
|
|-
| ''Landascape analysis''
| LA
| All `r.li.*` modules, maybe other
| ''Raster analysis''
|-
| ''Lidar analysis''
| LI
| All `v.lidar.*` modules, {{cmd|v.surf.bspline|version=70}}, r.in.xyz
|
|-
| ''Linear Reference Systems''
| LS
| All `v.lrs.*` modules
| ''Vector analysis''
|-
| ''Network analysis''
| NA
| All `v.net.*` modules, maybe other
| ''Vector analysis''
|-
| ''Raster analysis''
| RA
| A lot of basic `r.*` modules (like {{cmd|r.buffer,|version=70}} {{cmd|r.reclass|version=70}}, {{cmd|r.fillnull|version=70}}...)
|
|-
| ''Terrain analysis''
| TA
| Different kind of analysis: soil ({{cmd|r.sun,|version=70}}), terrain ({{cmd|r.slope.aspect|version=70}}, {{cmd|r.los|version=70}}), geomorphometry ({{cmd|r.param.scale|version=70}})
| ''Raster analysis''
|-
| ''Vector analysis''
| VA
| A lot of basic `v.*` modules (like {{cmd|v.buffer|version=70}}, {{cmd|v.centroid|version=70}}, {{cmd|v.overlay|version=70}}...)
| ''Database''
|}

== List of modules (trunk) ==

=== Display ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|d.barscale|version=70}} || ? ||
|-
| {{cmd|d.colorlist|version=70}} || ? ||
|-
| {{cmd|d.colortable|version=70}} || ? ||
|-
| {{cmd|d.correlate|version=70}} || ? ||
|-
| {{cmd|d.erase|version=70}} || ? ||
|-
| {{cmd|d.font|version=70}} || ? ||
|-
| {{cmd|d.fontlist|version=70}} || ? ||
|-
| {{cmd|d.geodesic|version=70}} || ? ||
|-
| {{cmd|d.graph|version=70}} || ? ||
|-
| {{cmd|d.grid|version=70}} || ? ||
|-
| {{cmd|d.his|version=70}} || ? ||
|-
| {{cmd|d.histogram|version=70}} || ? ||
|-
| {{cmd|d.info|version=70}} || ? ||
|-
| {{cmd|d.labels|version=70}} || ? ||
|-
| {{cmd|d.legend|version=70}} || ? ||
|-
| {{cmd|d.linegraph|version=70}} || ? ||
|-
| {{cmd|d.nviz|version=70}} || ? ||
|-
| {{cmd|d.path|version=70}} || ? ||
|-
| {{cmd|d.polar|version=70}} || ? ||
|-
| {{cmd|d.profile|version=70}} || ? ||
|-
| {{cmd|d.rast|version=70}} || ? ||
|-
| {{cmd|d.rast.arrow|version=70}} || ? ||
|-
| {{cmd|d.rast.edit|version=70}} || ? ||
|-
| {{cmd|d.rast.leg|version=70}} || ? ||
|-
| {{cmd|d.rast.num|version=70}} || ? ||
|-
| {{cmd|d.rgb|version=70}} || ? ||
|-
| {{cmd|d.rhumbline|version=70}} || ? ||
|-
| {{cmd|d.shadedmap|version=70}} || ? ||
|-
| {{cmd|d.text|version=70}} || ? ||
|-
| {{cmd|d.thematic.area|version=70}} || ? ||
|-
| {{cmd|d.title|version=70}} || ? ||
|-
| {{cmd|d.vect|version=70}} || ? ||
|-
| {{cmd|d.vect.chart|version=70}} || ? ||
|-
| {{cmd|d.vect.thematic|version=70}} || ? ||
|-
| {{cmd|d.where|version=70}} || ? ||
|-
|}

=== Database ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|db.columns|version=70}} || ? ||
|-
| {{cmd|db.connect|version=70}} || ? ||
|-
| {{cmd|db.copy|version=70}} || ? ||
|-
| {{cmd|db.createdb|version=70}} || ? ||
|-
| {{cmd|db.databases|version=70}} || ? ||
|-
| {{cmd|db.describe|version=70}} || ? ||
|-
| {{cmd|db.drivers|version=70}} || ? ||
|-
| {{cmd|db.dropcolumn|version=70}} || ? ||
|-
| {{cmd|db.dropdb|version=70}} || ? ||
|-
| {{cmd|db.droptable|version=70}} || ? ||
|-
| {{cmd|db.droptable|version=70}} || ? ||
|-
| {{cmd|db.execute|version=70}} || ? ||
|-
| {{cmd|db.in.ogr|version=70}} || ? ||
|-
| {{cmd|db.login|version=70}} || ? ||
|-
| {{cmd|db.out.ogr|version=70}} || ? ||
|-
| {{cmd|db.select|version=70}} || ? ||
|-
| {{cmd|db.tables|version=70}} || ? ||
|-
| {{cmd|db.test|version=70}} || ? ||
|-
|}

=== General ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|g.access|version=70}} || C ||
|-
| {{cmd|g.cairocomp|version=70}} || C ||
|-
| {{cmd|g.copy|version=70}} || C ||
|-
| {{cmd|g.dirseps|version=70}} || C ||
|-
| {{cmd|g.extension|version=70}} || C ||
|-
| {{cmd|g.filename|version=70}} || C ||
|-
| {{cmd|g.findetc|version=70}} || C ||
|-
| {{cmd|g.findfile|version=70}} || C ||
|-
| {{cmd|g.gisenv|version=70}} || C ||
|-
| {{cmd|g.gui|version=70}} || C ||
|-
| {{cmd|g.list|version=70}} || C ||
|-
| {{cmd|g.manual|version=70}} || C ||
|-
| {{cmd|g.mapset|version=70}} || C ||
|-
| {{cmd|g.mapsets|version=70}} || C ||
|-
| {{cmd|g.message|version=70}} || C ||
|-
| {{cmd|g.mkfontcap|version=70}} || C ||
|-
| {{cmd|g.mlist|version=70}} || C ||
|-
| {{cmd|g.mremove|version=70}} || C ||
|-
| {{cmd|g.parser|version=70}} || C ||
|-
| {{cmd|g.pnmcomp|version=70}} || C ||
|-
| {{cmd|g.ppmtopng|version=70}} || C ||
|-
| {{cmd|g.proj|version=70}} || C ||
|-
| {{cmd|g.region|version=70}} || C ||
|-
| {{cmd|g.remove|version=70}} || C ||
|-
| {{cmd|g.rename|version=70}} || C ||
|-
| {{cmd|g.tempfile|version=70}} || C ||
|-
| {{cmd|g.transform|version=70}} || C ||
|-
| {{cmd|g.version|version=70}} || C ||
|-
|}

=== Imagery ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|i.albedo|version=70}} || ? ||
|-
| {{cmd|i.atcorr|version=70}} || ? ||
|-
| {{cmd|i.biomass|version=70}} || ? ||
|-
| {{cmd|i.cca|version=70}} || ? ||
|-
| {{cmd|i.cluster|version=70}} || ? ||
|-
| {{cmd|i.eb.eta|version=70}} || ? ||
|-
| {{cmd|i.eb.evapfr|version=70}} || ? ||
|-
| {{cmd|i.eb.h_SEBAL01|version=70}} || ? ||
|-
| {{cmd|i.eb.soilheatflux|version=70}} || ? ||
|-
| {{cmd|i.emissivity|version=70}} || ? ||
|-
| {{cmd|i.evapo.time|version=70}} || ? ||
|-
| {{cmd|i.fft|version=70}} || ? ||
|-
| {{cmd|i.fusion.brovey|version=70}} || ? ||
|-
| {{cmd|i.gensig|version=70}} || ? ||
|-
| {{cmd|i.gensigset|version=70}} || ? ||
|-
| {{cmd|i.group|version=70}} || ? ||
|-
| {{cmd|i.his.rgb|version=70}} || ? ||
|-
| {{cmd|i.ifft|version=70}} || ? ||
|-
| {{cmd|i.image.mosaic|version=70}} || ? ||
|-
| {{cmd|i.in.spotvgt|version=70}} || ? ||
|-
| {{cmd|i.landsat.rgb|version=70}} || ? ||
|-
| {{cmd|i.latlong|version=70}} || ? ||
|-
| {{cmd|i.maxlik|version=70}} || ? ||
|-
| {{cmd|i.modis.qc|version=70}} || ? ||
|-
| {{cmd|i.oif|version=70}} || ? ||
|-
| {{cmd|i.pca|version=70}} || ? ||
|-
| {{cmd|i.rectify|version=70}} || ? ||
|-
| {{cmd|i.rgb.his|version=70}} || ? ||
|-
| {{cmd|i.smap|version=70}} || ? ||
|-
| {{cmd|i.spectral|version=70}} || ? ||
|-
| {{cmd|i.sunhours|version=70}} || ? ||
|-
| {{cmd|i.target|version=70}} || ? ||
|-
| {{cmd|i.tasscap|version=70}} || ? ||
|-
| {{cmd|i.vi|version=70}} || ? ||
|-
| {{cmd|i.zc|version=70}} || ? ||
|-
|}

=== Misc ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|m.cogo|version=70}} || ? ||
|-
| {{cmd|m.measure|version=70}} || ? ||
|-
| {{cmd|m.proj|version=70}} || ? ||
|-
|}

=== Postscript ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|ps.map|version=70}} || ? ||
|-
|}

=== Raster ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|r.basins.fill|version=70}} || ? ||
|-
| {{cmd|r.bitpattern|version=70}} || ? ||
|-
| {{cmd|r.blend|version=70}} || ? ||
|-
| {{cmd|r.buffer|version=70}} || ? ||
|-
| {{cmd|r.buffer2|version=70}} || ? ||
|-
| {{cmd|r.carve|version=70}} || ? ||
|-
| {{cmd|r.category|version=70}} || ? ||
|-
| {{cmd|r.circle|version=70}} || ? ||
|-
| {{cmd|r.clump|version=70}} || ? ||
|-
| {{cmd|r.coin|version=70}} || ? ||
|-
| {{cmd|r.colors|version=70}} || ? ||
|-
| {{cmd|r.colors.out|version=70}} || ? ||
|-
| {{cmd|r.colors.stddev|version=70}} || ? ||
|-
| {{cmd|r.composite|version=70}} || ? ||
|-
| {{cmd|r.compress|version=70}} || ? ||
|-
| {{cmd|r.contour|version=70}} || ? ||
|-
| {{cmd|r.cost|version=70}} || ? ||
|-
| {{cmd|r.covar|version=70}} || ? ||
|-
| {{cmd|r.cross|version=70}} || ? ||
|-
| {{cmd|r.describe|version=70}} || ? ||
|-
| {{cmd|r.distance|version=70}} || ? ||
|-
| {{cmd|r.drain|version=70}} || ? ||
|-
| {{cmd|r.external|version=70}} || ? ||
|-
| {{cmd|r.external.out|version=70}} || ? ||
|-
| {{cmd|r.fill.dir|version=70}} || ? ||
|-
| {{cmd|r.fillnulls|version=70}} || ? ||
|-
| {{cmd|r.flow|version=70}} || ? ||
|-
| {{cmd|r.grow|version=70}} || ? ||
|-
| {{cmd|r.grow.distance|version=70}} || ? ||
|-
| {{cmd|r.gwflow|version=70}} || ? ||
|-
| {{cmd|r.his|version=70}} || ? ||
|-
| {{cmd|r.horizon|version=70}} || ? ||
|-
| {{cmd|r.in.arc|version=70}} || ? ||
|-
| {{cmd|r.in.ascii|version=70}} || ? ||
|-
| {{cmd|r.in.aster|version=70}} || ? ||
|-
| {{cmd|r.in.bin|version=70}} || ? ||
|-
| {{cmd|r.in.gdal|version=70}} || ? ||
|-
| {{cmd|r.in.gridatb|version=70}} || ? ||
|-
| {{cmd|r.in.mat|version=70}} || ? ||
|-
| {{cmd|r.in.png|version=70}} || ? ||
|-
| {{cmd|r.in.poly|version=70}} || ? ||
|-
| {{cmd|r.in.srtm|version=70}} || ? ||
|-
| {{cmd|r.in.wms|version=70}} || ? ||
|-
| {{cmd|r.in.xyz|version=70}} || ? ||
|-
| {{cmd|r.info|version=70}} || ? ||
|-
| {{cmd|r.kappa|version=70}} || ? ||
|-
| {{cmd|r.lake|version=70}} || ? ||
|-
| {{cmd|r.li.cwed|version=70}} || ? ||
|-
| {{cmd|r.li.dominance|version=70}} || ? ||
|-
| {{cmd|r.li.edgedensity|version=70}} || ? ||
|-
| {{cmd|r.li.mpa|version=70}} || ? ||
|-
| {{cmd|r.li.mps|version=70}} || ? ||
|-
| {{cmd|r.li.padcv|version=70}} || ? ||
|-
| {{cmd|r.li.padrange|version=70}} || ? ||
|-
| {{cmd|r.li.padsd|version=70}} || ? ||
|-
| {{cmd|r.li.patchdensity|version=70}} || ? ||
|-
| {{cmd|r.li.patchnum|version=70}} || ? ||
|-
| {{cmd|r.li.richness|version=70}} || ? ||
|-
| {{cmd|r.li.shannon|version=70}} || ? ||
|-
| {{cmd|r.li.shape|version=70}} || ? ||
|-
| {{cmd|r.li.simpson|version=70}} || ? ||
|-
| {{cmd|r.los|version=70}} || ? ||
|-
| {{cmd|r.mapcalc|version=70}} || ? ||
|-
| {{cmd|r.mask|version=70}} || ? ||
|-
| {{cmd|r.mfilter|version=70}} || ? ||
|-
| {{cmd|r.mode|version=70}} || ? ||
|-
| {{cmd|r.neighbors|version=70}} || ? ||
|-
| {{cmd|r.null|version=70}} || ? ||
|-
| {{cmd|r.out.arc|version=70}} || ? ||
|-
| {{cmd|r.out.ascii|version=70}} || ? ||
|-
| {{cmd|r.out.bin|version=70}} || ? ||
|-
| {{cmd|r.out.gdal|version=70}} || ? ||
|-
| {{cmd|r.out.gridatb|version=70}} || ? ||
|-
| {{cmd|r.out.mat|version=70}} || ? ||
|-
| {{cmd|r.out.mpeg|version=70}} || ? ||
|-
| {{cmd|r.out.png|version=70}} || ? ||
|-
| {{cmd|r.out.pov|version=70}} || ? ||
|-
| {{cmd|r.out.ppm|version=70}} || ? ||
|-
| {{cmd|r.out.ppm3|version=70}} || ? ||
|-
| {{cmd|r.out.tiff|version=70}} || ? ||
|-
| {{cmd|r.out.vrml|version=70}} || ? ||
|-
| {{cmd|r.out.vtk|version=70}} || ? ||
|-
| {{cmd|r.out.xyz|version=70}} || ? ||
|-
| {{cmd|r.param.scale|version=70}} || ? ||
|-
| {{cmd|r.patch|version=70}} || ? ||
|-
| {{cmd|r.plane|version=70}} || ? ||
|-
| {{cmd|r.profile|version=70}} || ? ||
|-
| {{cmd|r.proj|version=70}} || ? ||
|-
| {{cmd|r.quant|version=70}} || ? ||
|-
| {{cmd|r.quantile|version=70}} || ? ||
|-
| {{cmd|r.random|version=70}} || ? ||
|-
| {{cmd|r.random.cells|version=70}} || ? ||
|-
| {{cmd|r.random.surface|version=70}} || ? ||
|-
| {{cmd|r.reclass|version=70}} || ? ||
|-
| {{cmd|r.reclass.area|version=70}} || ? ||
|-
| {{cmd|r.recode|version=70}} || ? ||
|-
| {{cmd|r.region|version=70}} || ? ||
|-
| {{cmd|r.regression.line|version=70}} || ? ||
|-
| {{cmd|r.report|version=70}} || ? ||
|-
| {{cmd|r.resamp.bspline|version=70}} || ? ||
|-
| {{cmd|r.resamp.filter|version=70}} || ? ||
|-
| {{cmd|r.resamp.interp|version=70}} || ? ||
|-
| {{cmd|r.resamp.rst|version=70}} || ? ||
|-
| {{cmd|r.resamp.stats|version=70}} || ? ||
|-
| {{cmd|r.resample|version=70}} || ? ||
|-
| {{cmd|r.rescale|version=70}} || ? ||
|-
| {{cmd|r.rescale.eq|version=70}} || ? ||
|-
| {{cmd|r.ros|version=70}} || ? ||
|-
| {{cmd|r.series|version=70}} || ? ||
|-
| {{cmd|r.shaded.relief|version=70}} || ? ||
|-
| {{cmd|r.sim.sediment|version=70}} || ? ||
|-
| {{cmd|r.sim.water|version=70}} || ? ||
|-
| {{cmd|r.slope.aspect|version=70}} || ? ||
|-
| {{cmd|r.solute.transport|version=70}} || ? ||
|-
| {{cmd|r.spread|version=70}} || ? ||
|-
| {{cmd|r.spreadpath|version=70}} || ? ||
|-
| {{cmd|r.statistics|version=70}} || ? ||
|-
| {{cmd|r.statistics2|version=70}} || ? ||
|-
| {{cmd|r.statistics3|version=70}} || ? ||
|-
| {{cmd|r.stats|version=70}} || ? ||
|-
| {{cmd|r.sun|version=70}} || ? ||
|-
| {{cmd|r.sunmask|version=70}} || ? ||
|-
| {{cmd|r.support|version=70}} || ? ||
|-
| {{cmd|r.support.stats|version=70}} || ? ||
|-
| {{cmd|r.surf.area|version=70}} || ? ||
|-
| {{cmd|r.surf.contour|version=70}} || ? ||
|-
| {{cmd|r.surf.fractal|version=70}} || ? ||
|-
| {{cmd|r.surf.gauss|version=70}} || ? ||
|-
| {{cmd|r.surf.idw|version=70}} || ? ||
|-
| {{cmd|r.surf.idw2|version=70}} || ? ||
|-
| {{cmd|r.surf.random|version=70}} || ? ||
|-
| {{cmd|r.terraflow|version=70}} || ? ||
|-
| {{cmd|r.texture|version=70}} || ? ||
|-
| {{cmd|r.thin|version=70}} || ? ||
|-
| {{cmd|r.tileset|version=70}} || ? ||
|-
| {{cmd|r.timestamp|version=70}} || ? ||
|-
| {{cmd|r.to.rast3|version=70}} || ? ||
|-
| {{cmd|r.to.rast3elev|version=70}} || ? ||
|-
| {{cmd|r.to.vect|version=70}} || ? ||
|-
| {{cmd|r.topidx|version=70}} || ? ||
|-
| {{cmd|r.topmodel|version=70}} || ? ||
|-
| {{cmd|r.transect|version=70}} || ? ||
|-
| {{cmd|r.univar|version=70}} || ? ||
|-
| {{cmd|r.uslek|version=70}} || ? ||
|-
| {{cmd|r.usler|version=70}} || ? ||
|-
| {{cmd|r.volume|version=70}} || ? ||
|-
| {{cmd|r.walk|version=70}} || ? ||
|-
| {{cmd|r.water.outlet|version=70}} || ? ||
|-
| {{cmd|r.watershed|version=70}} || ? ||
|-
| {{cmd|r.what|version=70}} || ? ||
|-
| {{cmd|r.what.color|version=70}} || ? ||
|-
|}

=== 3D raster ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|r3.cross.rast|version=70}} || T || 3D Raster
|-
| {{cmd|r3.gwflow|version=70}} || T || 3D Raster
|-
| {{cmd|r3.in.ascii|version=70}} || T || 3D Raster
|-
| {{cmd|r3.in.v5d|version=70}} || T || 3D Raster
|-
| {{cmd|r3.info|version=70}} || T || 3D Raster
|-
| {{cmd|r3.mapcalc|version=70}} || T || 3D Raster
|-
| {{cmd|r3.mask|version=70}} || T || 3D Raster
|-
| {{cmd|r3.mkdspf|version=70}} || T || 3D Raster
|-
| {{cmd|r3.null|version=70}} || T || 3D Raster
|-
| {{cmd|r3.out.ascii|version=70}} || T || 3D Raster
|-
| {{cmd|r3.out.v5d|version=70}} || T || 3D Raster
|-
| {{cmd|r3.out.vtk|version=70}} || T || 3D Raster
|-
| {{cmd|r3.stats|version=70}} || T || 3D Raster
|-
| {{cmd|r3.timestamp|version=70}} || T || 3D Raster
|-
| {{cmd|r3.to.rast|version=70}} || T || 3D Raster
|-
| {{cmd|r3.univar|version=70}} || T || 3D Raster
|-
|}

=== Vector ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|v.autokrige|version=70}} || ? ||
|-
| {{cmd|v.buffer|version=70}} || ? ||
|-
| {{cmd|v.build|version=70}} || ? ||
|-
| {{cmd|v.build.all|version=70}} || ? ||
|-
| {{cmd|v.build.polylines|version=70}} || ? ||
|-
| {{cmd|v.category|version=70}} || ? ||
|-
| {{cmd|v.centroids|version=70}} || ? ||
|-
| {{cmd|v.class|version=70}} || ? ||
|-
| {{cmd|v.clean|version=70}} || ? ||
|-
| {{cmd|v.colors|version=70}} || ? ||
|-
| {{cmd|v.convert|version=70}} || ? ||
|-
| {{cmd|v.convert.all|version=70}} || ? ||
|-
| {{cmd|v.db.addcolumn|version=70}} || ? ||
|-
| {{cmd|v.db.addtable|version=70}} || ? ||
|-
| {{cmd|v.db.connect|version=70}} || ? ||
|-
| {{cmd|v.db.dropcolumn|version=70}} || ? ||
|-
| {{cmd|v.db.droprow|version=70}} || ? ||
|-
| {{cmd|v.db.droptable|version=70}} || ? ||
|-
| {{cmd|v.db.join|version=70}} || ? ||
|-
| {{cmd|v.db.reconnect.all|version=70}} || ? ||
|-
| {{cmd|v.db.renamecolumn|version=70}} || ? ||
|-
| {{cmd|v.db.select|version=70}} || ? ||
|-
| {{cmd|v.db.univar|version=70}} || ? ||
|-
| {{cmd|v.db.update|version=70}} || ? ||
|-
| {{cmd|v.delaunay|version=70}} || ? ||
|-
| {{cmd|v.dissolve|version=70}} || ? ||
|-
| {{cmd|v.distance|version=70}} || ? ||
|-
| {{cmd|v.drape|version=70}} || ? ||
|-
| {{cmd|v.edit|version=70}} || ? ||
|-
| {{cmd|v.external|version=70}} || ? ||
|-
| {{cmd|v.extract|version=70}} || ? ||
|-
| {{cmd|v.extrude|version=70}} || ? ||
|-
| {{cmd|v.generalize|version=70}} || ? ||
|-
| {{cmd|v.hull|version=70}} || ? ||
|-
| {{cmd|v.in.ascii|version=70}} || ? ||
|-
| {{cmd|v.in.db|version=70}} || ? ||
|-
| {{cmd|v.in.dxf|version=70}} || ? ||
|-
| {{cmd|v.in.e00|version=70}} || ? ||
|-
| {{cmd|v.in.geonames|version=70}} || ? ||
|-
| {{cmd|v.in.gns|version=70}} || ? ||
|-
| {{cmd|v.in.lines|version=70}} || ? ||
|-
| {{cmd|v.in.mapgen|version=70}} || ? ||
|-
| {{cmd|v.in.ogr|version=70}} || ? ||
|-
| {{cmd|v.in.postgis|version=70}} || ? ||
|-
| {{cmd|v.in.region|version=70}} || ? ||
|-
| {{cmd|v.in.sites|version=70}} || ? ||
|-
| {{cmd|v.in.sites.all|version=70}} || ? ||
|-
| {{cmd|v.in.wfs|version=70}} || ? ||
|-
| {{cmd|v.info|version=70}} || ? ||
|-
| {{cmd|v.kcv|version=70}} || ? ||
|-
| {{cmd|v.kernel|version=70}} || ? ||
|-
| {{cmd|v.krige|version=70}} || ? ||
|-
| {{cmd|v.label|version=70}} || ? ||
|-
| {{cmd|v.lidar.correction|version=70}} || ? ||
|-
| {{cmd|v.lidar.edgedetection|version=70}} || ? ||
|-
| {{cmd|v.lidar.growing|version=70}} || ? ||
|-
| {{cmd|v.lrs.create|version=70}} || ? ||
|-
| {{cmd|v.lrs.label|version=70}} || ? ||
|-
| {{cmd|v.lrs.segment|version=70}} || ? ||
|-
| {{cmd|v.lrs.where|version=70}} || ? ||
|-
| {{cmd|v.mkgrid|version=70}} || ? ||
|-
| {{cmd|v.neighbors|version=70}} || ? ||
|-
| {{cmd|v.net|version=70}} || ? ||
|-
| {{cmd|v.net.alloc|version=70}} || ? ||
|-
| {{cmd|v.net.allpairs|version=70}} || ? ||
|-
| {{cmd|v.net.bridge|version=70}} || ? ||
|-
| {{cmd|v.net.centrality|version=70}} || ? ||
|-
| {{cmd|v.net.components|version=70}} || ? ||
|-
| {{cmd|v.net.connectivity|version=70}} || ? ||
|-
| {{cmd|v.net.distance|version=70}} || ? ||
|-
| {{cmd|v.net.flow|version=70}} || ? ||
|-
| {{cmd|v.net.iso|version=70}} || ? ||
|-
| {{cmd|v.net.path|version=70}} || ? ||
|-
| {{cmd|v.net.salesman|version=70}} || ? ||
|-
| {{cmd|v.net.spanningtree|version=70}} || ? ||
|-
| {{cmd|v.net.steiner|version=70}} || ? ||
|-
| {{cmd|v.net.timetable|version=70}} || ? ||
|-
| {{cmd|v.net.visibility|version=70}} || ? ||
|-
| {{cmd|v.normal|version=70}} || ? ||
|-
| {{cmd|v.out.ascii|version=70}} || ? ||
|-
| {{cmd|v.out.dxf|version=70}} || ? ||
|-
| {{cmd|v.out.gps|version=70}} || ? ||
|-
| {{cmd|v.out.ogr|version=70}} || ? ||
|-
| {{cmd|v.out.postgis|version=70}} || ? ||
|-
| {{cmd|v.out.pov|version=70}} || ? ||
|-
| {{cmd|v.out.svg|version=70}} || ? ||
|-
| {{cmd|v.out.vtk|version=70}} || ? ||
|-
| {{cmd|v.outlier|version=70}} || ? ||
|-
| {{cmd|v.overlay|version=70}} || ? ||
|-
| {{cmd|v.parallel|version=70}} || ? ||
|-
| {{cmd|v.patch|version=70}} || ? ||
|-
| {{cmd|v.perturb|version=70}} || ? ||
|-
| {{cmd|v.proj|version=70}} || ? ||
|-
| {{cmd|v.qcount|version=70}} || ? ||
|-
| {{cmd|v.random|version=70}} || ? ||
|-
| {{cmd|v.rast.stats|version=70}} || ? ||
|-
| {{cmd|v.reclass|version=70}} || ? ||
|-
| {{cmd|v.report|version=70}} || ? ||
|-
| {{cmd|v.sample|version=70}} || ? ||
|-
| {{cmd|v.segment|version=70}} || ? ||
|-
| {{cmd|v.select|version=70}} || ? ||
|-
| {{cmd|v.split|version=70}} || ? ||
|-
| {{cmd|v.support|version=70}} || ? ||
|-
| {{cmd|v.surf.bspline|version=70}} || ? ||
|-
| {{cmd|v.surf.idw|version=70}} || ? ||
|-
| {{cmd|v.surf.rst|version=70}} || ? ||
|-
| {{cmd|v.to.3d|version=70}} || ? ||
|-
| {{cmd|v.to.db|version=70}} || ? ||
|-
| {{cmd|v.to.points|version=70}} || ? ||
|-
| {{cmd|v.to.rast|version=70}} || ? ||
|-
| {{cmd|v.to.rast3|version=70}} || ? ||
|-
| {{cmd|v.transform|version=70}} || ? ||
|-
| {{cmd|v.type|version=70}} || ? ||
|-
| {{cmd|v.univar|version=70}} || ? ||
|-
| {{cmd|v.vol.rst|version=70}} || ? ||
|-
| {{cmd|v.voronoi|version=70}} || ? ||
|-
| {{cmd|v.what|version=70}} || ? ||
|-
| {{cmd|v.what.rast|version=70}} || ? ||
|-
| {{cmd|v.what.vect|version=70}} || ? ||
|-
|}

=== Various ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|nviz|version=70}} || ? ||
|-
| {{cmd|nviz_cmd|version=70}} || ? ||
|-
| {{cmd|wximgview|version=70}} || ? ||
|-
| {{cmd|wxpyimgview|version=70}} || ? ||
|-
| {{cmd|xganim|version=70}} || ? ||
|-
| {{cmd|ximgview|version=70}} || ? ||
|-
|}

== List of selected AddOns modules ==

See [[GRASS AddOns]] for full list of available modules. Feel free to extend this list.

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)''' || '''Note'''
|-
| {{AddonCmd|r.stream.angle}} || T || HY ||
|-
| {{AddonCmd|r.seg}} || T || IM || It could be rename to `i.seg`
|-
| {{AddonCmd|i.topocorr}} || T || IM ||
|-
| {{AddonCmd|r.diversity}} || T || LA ||
|-
| {{AddonCmd|Ps.output}} || ? || ||
|-
| ... || ? || ||
|-
|}

== How to implement ==

=== propose 1 ===
* add html tag <param> in the description.html with these options:
<param name = "core"> for core module
<param name = "tool" value="tool_code/codes"> for toolbox
<param name = "addons" [value="tool_code/codes"]> for addons, value is optional

* create a script to generate a xml file for each toolbox
* add toolbox option in g.extension to read the xml and install the modules

[[Category:Development]]

Toolboxes

2011-05-08T03:29:17Z

⚠️Helena: /* List of toolboxes */

* See [http://lists.osgeo.org/pipermail/grass-dev/2010-April/050210.html original post by Jarosław Jasiewicz]

* Discussion about the suitability of the proposed change on the [[Talk:GRASS_repository_layout_proposal|talk]] side of this wiki page; discussion of the possible method on this side of the page.

<pre>
Hi all!

That rather radical ideas I present here are rather for future, at least for GRASS 8,
but I'd like present it now for long-term reflection.

Probably all notice that for over two years there is big increase in add-on repository
(including me). There are modules of different quality: from fully GRASS toolsets,
to shell or python scripts, from actively developed tools to abandoned,
from all-purpose tools to very specialized etc. I also think that that activity
will be grown due to substitute shell script by python

Similar situation is in main GRASS branch: there are modules for all like conversion tools,
interpolation methods, georeferencing etc, and very specialized modules for very limited
group of users (like wild fire), there are also some modules out of date.

I'm not enthusiastic about moving new modules into main branch. Almost every module has
different coding style and it will lasting in future that GRASS would be difficult to maintain.
On the other hand some people complains that some interesting modules are only available as
add-ons (I assume for some reasons they cannot install it)

So my suggestion is to rearrange future GRASS form two layers (main branch/add-on) into
three layers architecture:

1) GRASS core layer: much limited limited than now, only GIS environment and basic,
all-puropse tools, slow changes, great stability
2) GRASS toolset layer: oficcial GRASS thematic tools and toolsets (like terrain analysis,
hydrological analysis, photo-interpretation, landscape analysis etc,) every toolset with its
maintainer, rapid development, new ready to use tools after quality control may appear here,
also some of current main branch tool shall be moved to that layer
3) GRASS community layer: everything else like experimental, actively development new tools,
that what do not pass quality control, simple scripts, etc....

What benefits:
for developers and contributors: much clear situation and better publication path.
Toolset layer should be much more open for new tools than current GRASS main branch

for users: faster access to new tools.
There is no doubt that new tools are faster developed (less risk) than GRASS core
Binaries with toolsets could be maintained as separate apt/urpmi/pacman/yum/exe etc packages,
so it may appear in linux repository separetly form GRASS core.

There is only loose ideas. Most of them are of course taken from R (core/toolsets/rest of packages;
separate core and package development) but I think it is worth of some discuss ...

regards
Jarek
</pre>
__TOC__
== Repository layout ==
=== Current repository layout ===

<pre>
- grass
|- trunk
|- raster/
|- vector/
|- ...

- grass-addons
|- raster/
|- vector/
|- ...
</pre>

=== Proposed repository layout ===

<pre>
- grass
|- trunk
|- raster/
|- vector/
|- ...

- grass-tools
|- trunk
|- raster/
|- vector/
|- ...

- grass-addons
|- raster/
|- vector/
|- ...
</pre>

== Proposed toolboxes ==

'''Toolbox''' is a topic-based set of modules used for solving common GIS analysis, like hydrology, networking, LRS, etc. Toolbox should be easily installed by the user using {{cmd|g.extension|version=70}}

* add toolbox

g.extension toolbox=hydrology operation=add

Source code of the selected modules is downloaded from SVN, compiled and afterwards also installed to the user-specified (~/.grass7) or system (/usr/lib/grass7) directory.

Give the possibility with a flag (like -a) to install also modules from addons related that toolbox

g.extension -a toolbox=hydrology operation=add

* remove toolbox

g.extension toolbox=hydrology operation=remove

* list of modules of selected toolbox

g.extension -l toolbox=hydrology

User can also add/remove selected module

g.extension module=r.stream.angle operation=add

=== List of toolboxes ===
{|class="wikitable"
|'''Toolbox name''' || '''Toolbox code''' || '''Description'''||'''Correlate toolbox'''
|-
| ''3D Raster''
| R3
| All `r3.*` modules
|
|-
| ''3D Visualization''
| V3
| {{cmd|nviz_cmd|version=70}}
|
|-
| ''Cartography''
| CA
| {{cmd|ps.map|version=70}}, {{AddonCmd|ps.output}}
|
|-
| ''Database''
| DB
| All `db.*` modules
| ''Vector analysis''
|-
| ''Geostatistcal''
| GS
| {{cmd|v.krige|version=70}} maybe other
|
|-
| ''GUI''
| GI
| [[wxGUI]]
|
|-
| ''Hydrology''
| HY
| {{cmd|r.watershed|version=70}}, {{cmd|r.terraflow|version=70}}, `r.stream.*` modules in addons, maybe other, r.flow, r.sim.water, r.sim.sediment
| ''Raster analysis''
|-
| ''Imagery''
| IM
| All `i.*` modules
|
|-
| ''Landascape analysis''
| LA
| All `r.li.*` modules, maybe other
| ''Raster analysis''
|-
| ''Lidar analysis''
| LI
| All `v.lidar.*` modules, {{cmd|v.surf.bspline|version=70}}
|
|-
| ''Linear Reference Systems''
| LS
| All `v.lrs.*` modules
| ''Vector analysis''
|-
| ''Network analysis''
| NA
| All `v.net.*` modules, maybe other
| ''Vector analysis''
|-
| ''Raster analysis''
| RA
| A lot of basic `r.*` modules (like {{cmd|r.buffer,|version=70}} {{cmd|r.reclass|version=70}}, {{cmd|r.fillnull|version=70}}...)
|
|-
| ''Terrain analysis''
| TA
| Different kind of analysis: soil ({{cmd|r.sun,|version=70}}), terrain ({{cmd|r.slope.aspect|version=70}}, {{cmd|r.los|version=70}}), geomorphometry ({{cmd|r.param.scale|version=70}})
| ''Raster analysis''
|-
| ''Vector analysis''
| VA
| A lot of basic `v.*` modules (like {{cmd|v.buffer|version=70}}, {{cmd|v.centroid|version=70}}, {{cmd|v.overlay|version=70}}...)
| ''Database''
|}

== List of modules (trunk) ==

=== Display ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|d.barscale|version=70}} || ? ||
|-
| {{cmd|d.colorlist|version=70}} || ? ||
|-
| {{cmd|d.colortable|version=70}} || ? ||
|-
| {{cmd|d.correlate|version=70}} || ? ||
|-
| {{cmd|d.erase|version=70}} || ? ||
|-
| {{cmd|d.font|version=70}} || ? ||
|-
| {{cmd|d.fontlist|version=70}} || ? ||
|-
| {{cmd|d.geodesic|version=70}} || ? ||
|-
| {{cmd|d.graph|version=70}} || ? ||
|-
| {{cmd|d.grid|version=70}} || ? ||
|-
| {{cmd|d.his|version=70}} || ? ||
|-
| {{cmd|d.histogram|version=70}} || ? ||
|-
| {{cmd|d.info|version=70}} || ? ||
|-
| {{cmd|d.labels|version=70}} || ? ||
|-
| {{cmd|d.legend|version=70}} || ? ||
|-
| {{cmd|d.linegraph|version=70}} || ? ||
|-
| {{cmd|d.nviz|version=70}} || ? ||
|-
| {{cmd|d.path|version=70}} || ? ||
|-
| {{cmd|d.polar|version=70}} || ? ||
|-
| {{cmd|d.profile|version=70}} || ? ||
|-
| {{cmd|d.rast|version=70}} || ? ||
|-
| {{cmd|d.rast.arrow|version=70}} || ? ||
|-
| {{cmd|d.rast.edit|version=70}} || ? ||
|-
| {{cmd|d.rast.leg|version=70}} || ? ||
|-
| {{cmd|d.rast.num|version=70}} || ? ||
|-
| {{cmd|d.rgb|version=70}} || ? ||
|-
| {{cmd|d.rhumbline|version=70}} || ? ||
|-
| {{cmd|d.shadedmap|version=70}} || ? ||
|-
| {{cmd|d.text|version=70}} || ? ||
|-
| {{cmd|d.thematic.area|version=70}} || ? ||
|-
| {{cmd|d.title|version=70}} || ? ||
|-
| {{cmd|d.vect|version=70}} || ? ||
|-
| {{cmd|d.vect.chart|version=70}} || ? ||
|-
| {{cmd|d.vect.thematic|version=70}} || ? ||
|-
| {{cmd|d.where|version=70}} || ? ||
|-
|}

=== Database ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|db.columns|version=70}} || ? ||
|-
| {{cmd|db.connect|version=70}} || ? ||
|-
| {{cmd|db.copy|version=70}} || ? ||
|-
| {{cmd|db.createdb|version=70}} || ? ||
|-
| {{cmd|db.databases|version=70}} || ? ||
|-
| {{cmd|db.describe|version=70}} || ? ||
|-
| {{cmd|db.drivers|version=70}} || ? ||
|-
| {{cmd|db.dropcolumn|version=70}} || ? ||
|-
| {{cmd|db.dropdb|version=70}} || ? ||
|-
| {{cmd|db.droptable|version=70}} || ? ||
|-
| {{cmd|db.droptable|version=70}} || ? ||
|-
| {{cmd|db.execute|version=70}} || ? ||
|-
| {{cmd|db.in.ogr|version=70}} || ? ||
|-
| {{cmd|db.login|version=70}} || ? ||
|-
| {{cmd|db.out.ogr|version=70}} || ? ||
|-
| {{cmd|db.select|version=70}} || ? ||
|-
| {{cmd|db.tables|version=70}} || ? ||
|-
| {{cmd|db.test|version=70}} || ? ||
|-
|}

=== General ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|g.access|version=70}} || C ||
|-
| {{cmd|g.cairocomp|version=70}} || C ||
|-
| {{cmd|g.copy|version=70}} || C ||
|-
| {{cmd|g.dirseps|version=70}} || C ||
|-
| {{cmd|g.extension|version=70}} || C ||
|-
| {{cmd|g.filename|version=70}} || C ||
|-
| {{cmd|g.findetc|version=70}} || C ||
|-
| {{cmd|g.findfile|version=70}} || C ||
|-
| {{cmd|g.gisenv|version=70}} || C ||
|-
| {{cmd|g.gui|version=70}} || C ||
|-
| {{cmd|g.list|version=70}} || C ||
|-
| {{cmd|g.manual|version=70}} || C ||
|-
| {{cmd|g.mapset|version=70}} || C ||
|-
| {{cmd|g.mapsets|version=70}} || C ||
|-
| {{cmd|g.message|version=70}} || C ||
|-
| {{cmd|g.mkfontcap|version=70}} || C ||
|-
| {{cmd|g.mlist|version=70}} || C ||
|-
| {{cmd|g.mremove|version=70}} || C ||
|-
| {{cmd|g.parser|version=70}} || C ||
|-
| {{cmd|g.pnmcomp|version=70}} || C ||
|-
| {{cmd|g.ppmtopng|version=70}} || C ||
|-
| {{cmd|g.proj|version=70}} || C ||
|-
| {{cmd|g.region|version=70}} || C ||
|-
| {{cmd|g.remove|version=70}} || C ||
|-
| {{cmd|g.rename|version=70}} || C ||
|-
| {{cmd|g.tempfile|version=70}} || C ||
|-
| {{cmd|g.transform|version=70}} || C ||
|-
| {{cmd|g.version|version=70}} || C ||
|-
|}

=== Imagery ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|i.albedo|version=70}} || ? ||
|-
| {{cmd|i.atcorr|version=70}} || ? ||
|-
| {{cmd|i.biomass|version=70}} || ? ||
|-
| {{cmd|i.cca|version=70}} || ? ||
|-
| {{cmd|i.cluster|version=70}} || ? ||
|-
| {{cmd|i.eb.eta|version=70}} || ? ||
|-
| {{cmd|i.eb.evapfr|version=70}} || ? ||
|-
| {{cmd|i.eb.h_SEBAL01|version=70}} || ? ||
|-
| {{cmd|i.eb.soilheatflux|version=70}} || ? ||
|-
| {{cmd|i.emissivity|version=70}} || ? ||
|-
| {{cmd|i.evapo.time|version=70}} || ? ||
|-
| {{cmd|i.fft|version=70}} || ? ||
|-
| {{cmd|i.fusion.brovey|version=70}} || ? ||
|-
| {{cmd|i.gensig|version=70}} || ? ||
|-
| {{cmd|i.gensigset|version=70}} || ? ||
|-
| {{cmd|i.group|version=70}} || ? ||
|-
| {{cmd|i.his.rgb|version=70}} || ? ||
|-
| {{cmd|i.ifft|version=70}} || ? ||
|-
| {{cmd|i.image.mosaic|version=70}} || ? ||
|-
| {{cmd|i.in.spotvgt|version=70}} || ? ||
|-
| {{cmd|i.landsat.rgb|version=70}} || ? ||
|-
| {{cmd|i.latlong|version=70}} || ? ||
|-
| {{cmd|i.maxlik|version=70}} || ? ||
|-
| {{cmd|i.modis.qc|version=70}} || ? ||
|-
| {{cmd|i.oif|version=70}} || ? ||
|-
| {{cmd|i.pca|version=70}} || ? ||
|-
| {{cmd|i.rectify|version=70}} || ? ||
|-
| {{cmd|i.rgb.his|version=70}} || ? ||
|-
| {{cmd|i.smap|version=70}} || ? ||
|-
| {{cmd|i.spectral|version=70}} || ? ||
|-
| {{cmd|i.sunhours|version=70}} || ? ||
|-
| {{cmd|i.target|version=70}} || ? ||
|-
| {{cmd|i.tasscap|version=70}} || ? ||
|-
| {{cmd|i.vi|version=70}} || ? ||
|-
| {{cmd|i.zc|version=70}} || ? ||
|-
|}

=== Misc ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|m.cogo|version=70}} || ? ||
|-
| {{cmd|m.measure|version=70}} || ? ||
|-
| {{cmd|m.proj|version=70}} || ? ||
|-
|}

=== Postscript ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|ps.map|version=70}} || ? ||
|-
|}

=== Raster ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|r.basins.fill|version=70}} || ? ||
|-
| {{cmd|r.bitpattern|version=70}} || ? ||
|-
| {{cmd|r.blend|version=70}} || ? ||
|-
| {{cmd|r.buffer|version=70}} || ? ||
|-
| {{cmd|r.buffer2|version=70}} || ? ||
|-
| {{cmd|r.carve|version=70}} || ? ||
|-
| {{cmd|r.category|version=70}} || ? ||
|-
| {{cmd|r.circle|version=70}} || ? ||
|-
| {{cmd|r.clump|version=70}} || ? ||
|-
| {{cmd|r.coin|version=70}} || ? ||
|-
| {{cmd|r.colors|version=70}} || ? ||
|-
| {{cmd|r.colors.out|version=70}} || ? ||
|-
| {{cmd|r.colors.stddev|version=70}} || ? ||
|-
| {{cmd|r.composite|version=70}} || ? ||
|-
| {{cmd|r.compress|version=70}} || ? ||
|-
| {{cmd|r.contour|version=70}} || ? ||
|-
| {{cmd|r.cost|version=70}} || ? ||
|-
| {{cmd|r.covar|version=70}} || ? ||
|-
| {{cmd|r.cross|version=70}} || ? ||
|-
| {{cmd|r.describe|version=70}} || ? ||
|-
| {{cmd|r.distance|version=70}} || ? ||
|-
| {{cmd|r.drain|version=70}} || ? ||
|-
| {{cmd|r.external|version=70}} || ? ||
|-
| {{cmd|r.external.out|version=70}} || ? ||
|-
| {{cmd|r.fill.dir|version=70}} || ? ||
|-
| {{cmd|r.fillnulls|version=70}} || ? ||
|-
| {{cmd|r.flow|version=70}} || ? ||
|-
| {{cmd|r.grow|version=70}} || ? ||
|-
| {{cmd|r.grow.distance|version=70}} || ? ||
|-
| {{cmd|r.gwflow|version=70}} || ? ||
|-
| {{cmd|r.his|version=70}} || ? ||
|-
| {{cmd|r.horizon|version=70}} || ? ||
|-
| {{cmd|r.in.arc|version=70}} || ? ||
|-
| {{cmd|r.in.ascii|version=70}} || ? ||
|-
| {{cmd|r.in.aster|version=70}} || ? ||
|-
| {{cmd|r.in.bin|version=70}} || ? ||
|-
| {{cmd|r.in.gdal|version=70}} || ? ||
|-
| {{cmd|r.in.gridatb|version=70}} || ? ||
|-
| {{cmd|r.in.mat|version=70}} || ? ||
|-
| {{cmd|r.in.png|version=70}} || ? ||
|-
| {{cmd|r.in.poly|version=70}} || ? ||
|-
| {{cmd|r.in.srtm|version=70}} || ? ||
|-
| {{cmd|r.in.wms|version=70}} || ? ||
|-
| {{cmd|r.in.xyz|version=70}} || ? ||
|-
| {{cmd|r.info|version=70}} || ? ||
|-
| {{cmd|r.kappa|version=70}} || ? ||
|-
| {{cmd|r.lake|version=70}} || ? ||
|-
| {{cmd|r.li.cwed|version=70}} || ? ||
|-
| {{cmd|r.li.dominance|version=70}} || ? ||
|-
| {{cmd|r.li.edgedensity|version=70}} || ? ||
|-
| {{cmd|r.li.mpa|version=70}} || ? ||
|-
| {{cmd|r.li.mps|version=70}} || ? ||
|-
| {{cmd|r.li.padcv|version=70}} || ? ||
|-
| {{cmd|r.li.padrange|version=70}} || ? ||
|-
| {{cmd|r.li.padsd|version=70}} || ? ||
|-
| {{cmd|r.li.patchdensity|version=70}} || ? ||
|-
| {{cmd|r.li.patchnum|version=70}} || ? ||
|-
| {{cmd|r.li.richness|version=70}} || ? ||
|-
| {{cmd|r.li.shannon|version=70}} || ? ||
|-
| {{cmd|r.li.shape|version=70}} || ? ||
|-
| {{cmd|r.li.simpson|version=70}} || ? ||
|-
| {{cmd|r.los|version=70}} || ? ||
|-
| {{cmd|r.mapcalc|version=70}} || ? ||
|-
| {{cmd|r.mask|version=70}} || ? ||
|-
| {{cmd|r.mfilter|version=70}} || ? ||
|-
| {{cmd|r.mode|version=70}} || ? ||
|-
| {{cmd|r.neighbors|version=70}} || ? ||
|-
| {{cmd|r.null|version=70}} || ? ||
|-
| {{cmd|r.out.arc|version=70}} || ? ||
|-
| {{cmd|r.out.ascii|version=70}} || ? ||
|-
| {{cmd|r.out.bin|version=70}} || ? ||
|-
| {{cmd|r.out.gdal|version=70}} || ? ||
|-
| {{cmd|r.out.gridatb|version=70}} || ? ||
|-
| {{cmd|r.out.mat|version=70}} || ? ||
|-
| {{cmd|r.out.mpeg|version=70}} || ? ||
|-
| {{cmd|r.out.png|version=70}} || ? ||
|-
| {{cmd|r.out.pov|version=70}} || ? ||
|-
| {{cmd|r.out.ppm|version=70}} || ? ||
|-
| {{cmd|r.out.ppm3|version=70}} || ? ||
|-
| {{cmd|r.out.tiff|version=70}} || ? ||
|-
| {{cmd|r.out.vrml|version=70}} || ? ||
|-
| {{cmd|r.out.vtk|version=70}} || ? ||
|-
| {{cmd|r.out.xyz|version=70}} || ? ||
|-
| {{cmd|r.param.scale|version=70}} || ? ||
|-
| {{cmd|r.patch|version=70}} || ? ||
|-
| {{cmd|r.plane|version=70}} || ? ||
|-
| {{cmd|r.profile|version=70}} || ? ||
|-
| {{cmd|r.proj|version=70}} || ? ||
|-
| {{cmd|r.quant|version=70}} || ? ||
|-
| {{cmd|r.quantile|version=70}} || ? ||
|-
| {{cmd|r.random|version=70}} || ? ||
|-
| {{cmd|r.random.cells|version=70}} || ? ||
|-
| {{cmd|r.random.surface|version=70}} || ? ||
|-
| {{cmd|r.reclass|version=70}} || ? ||
|-
| {{cmd|r.reclass.area|version=70}} || ? ||
|-
| {{cmd|r.recode|version=70}} || ? ||
|-
| {{cmd|r.region|version=70}} || ? ||
|-
| {{cmd|r.regression.line|version=70}} || ? ||
|-
| {{cmd|r.report|version=70}} || ? ||
|-
| {{cmd|r.resamp.bspline|version=70}} || ? ||
|-
| {{cmd|r.resamp.filter|version=70}} || ? ||
|-
| {{cmd|r.resamp.interp|version=70}} || ? ||
|-
| {{cmd|r.resamp.rst|version=70}} || ? ||
|-
| {{cmd|r.resamp.stats|version=70}} || ? ||
|-
| {{cmd|r.resample|version=70}} || ? ||
|-
| {{cmd|r.rescale|version=70}} || ? ||
|-
| {{cmd|r.rescale.eq|version=70}} || ? ||
|-
| {{cmd|r.ros|version=70}} || ? ||
|-
| {{cmd|r.series|version=70}} || ? ||
|-
| {{cmd|r.shaded.relief|version=70}} || ? ||
|-
| {{cmd|r.sim.sediment|version=70}} || ? ||
|-
| {{cmd|r.sim.water|version=70}} || ? ||
|-
| {{cmd|r.slope.aspect|version=70}} || ? ||
|-
| {{cmd|r.solute.transport|version=70}} || ? ||
|-
| {{cmd|r.spread|version=70}} || ? ||
|-
| {{cmd|r.spreadpath|version=70}} || ? ||
|-
| {{cmd|r.statistics|version=70}} || ? ||
|-
| {{cmd|r.statistics2|version=70}} || ? ||
|-
| {{cmd|r.statistics3|version=70}} || ? ||
|-
| {{cmd|r.stats|version=70}} || ? ||
|-
| {{cmd|r.sun|version=70}} || ? ||
|-
| {{cmd|r.sunmask|version=70}} || ? ||
|-
| {{cmd|r.support|version=70}} || ? ||
|-
| {{cmd|r.support.stats|version=70}} || ? ||
|-
| {{cmd|r.surf.area|version=70}} || ? ||
|-
| {{cmd|r.surf.contour|version=70}} || ? ||
|-
| {{cmd|r.surf.fractal|version=70}} || ? ||
|-
| {{cmd|r.surf.gauss|version=70}} || ? ||
|-
| {{cmd|r.surf.idw|version=70}} || ? ||
|-
| {{cmd|r.surf.idw2|version=70}} || ? ||
|-
| {{cmd|r.surf.random|version=70}} || ? ||
|-
| {{cmd|r.terraflow|version=70}} || ? ||
|-
| {{cmd|r.texture|version=70}} || ? ||
|-
| {{cmd|r.thin|version=70}} || ? ||
|-
| {{cmd|r.tileset|version=70}} || ? ||
|-
| {{cmd|r.timestamp|version=70}} || ? ||
|-
| {{cmd|r.to.rast3|version=70}} || ? ||
|-
| {{cmd|r.to.rast3elev|version=70}} || ? ||
|-
| {{cmd|r.to.vect|version=70}} || ? ||
|-
| {{cmd|r.topidx|version=70}} || ? ||
|-
| {{cmd|r.topmodel|version=70}} || ? ||
|-
| {{cmd|r.transect|version=70}} || ? ||
|-
| {{cmd|r.univar|version=70}} || ? ||
|-
| {{cmd|r.uslek|version=70}} || ? ||
|-
| {{cmd|r.usler|version=70}} || ? ||
|-
| {{cmd|r.volume|version=70}} || ? ||
|-
| {{cmd|r.walk|version=70}} || ? ||
|-
| {{cmd|r.water.outlet|version=70}} || ? ||
|-
| {{cmd|r.watershed|version=70}} || ? ||
|-
| {{cmd|r.what|version=70}} || ? ||
|-
| {{cmd|r.what.color|version=70}} || ? ||
|-
|}

=== 3D raster ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|r3.cross.rast|version=70}} || T || 3D Raster
|-
| {{cmd|r3.gwflow|version=70}} || T || 3D Raster
|-
| {{cmd|r3.in.ascii|version=70}} || T || 3D Raster
|-
| {{cmd|r3.in.v5d|version=70}} || T || 3D Raster
|-
| {{cmd|r3.info|version=70}} || T || 3D Raster
|-
| {{cmd|r3.mapcalc|version=70}} || T || 3D Raster
|-
| {{cmd|r3.mask|version=70}} || T || 3D Raster
|-
| {{cmd|r3.mkdspf|version=70}} || T || 3D Raster
|-
| {{cmd|r3.null|version=70}} || T || 3D Raster
|-
| {{cmd|r3.out.ascii|version=70}} || T || 3D Raster
|-
| {{cmd|r3.out.v5d|version=70}} || T || 3D Raster
|-
| {{cmd|r3.out.vtk|version=70}} || T || 3D Raster
|-
| {{cmd|r3.stats|version=70}} || T || 3D Raster
|-
| {{cmd|r3.timestamp|version=70}} || T || 3D Raster
|-
| {{cmd|r3.to.rast|version=70}} || T || 3D Raster
|-
| {{cmd|r3.univar|version=70}} || T || 3D Raster
|-
|}

=== Vector ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|v.autokrige|version=70}} || ? ||
|-
| {{cmd|v.buffer|version=70}} || ? ||
|-
| {{cmd|v.build|version=70}} || ? ||
|-
| {{cmd|v.build.all|version=70}} || ? ||
|-
| {{cmd|v.build.polylines|version=70}} || ? ||
|-
| {{cmd|v.category|version=70}} || ? ||
|-
| {{cmd|v.centroids|version=70}} || ? ||
|-
| {{cmd|v.class|version=70}} || ? ||
|-
| {{cmd|v.clean|version=70}} || ? ||
|-
| {{cmd|v.colors|version=70}} || ? ||
|-
| {{cmd|v.convert|version=70}} || ? ||
|-
| {{cmd|v.convert.all|version=70}} || ? ||
|-
| {{cmd|v.db.addcolumn|version=70}} || ? ||
|-
| {{cmd|v.db.addtable|version=70}} || ? ||
|-
| {{cmd|v.db.connect|version=70}} || ? ||
|-
| {{cmd|v.db.dropcolumn|version=70}} || ? ||
|-
| {{cmd|v.db.droprow|version=70}} || ? ||
|-
| {{cmd|v.db.droptable|version=70}} || ? ||
|-
| {{cmd|v.db.join|version=70}} || ? ||
|-
| {{cmd|v.db.reconnect.all|version=70}} || ? ||
|-
| {{cmd|v.db.renamecolumn|version=70}} || ? ||
|-
| {{cmd|v.db.select|version=70}} || ? ||
|-
| {{cmd|v.db.univar|version=70}} || ? ||
|-
| {{cmd|v.db.update|version=70}} || ? ||
|-
| {{cmd|v.delaunay|version=70}} || ? ||
|-
| {{cmd|v.dissolve|version=70}} || ? ||
|-
| {{cmd|v.distance|version=70}} || ? ||
|-
| {{cmd|v.drape|version=70}} || ? ||
|-
| {{cmd|v.edit|version=70}} || ? ||
|-
| {{cmd|v.external|version=70}} || ? ||
|-
| {{cmd|v.extract|version=70}} || ? ||
|-
| {{cmd|v.extrude|version=70}} || ? ||
|-
| {{cmd|v.generalize|version=70}} || ? ||
|-
| {{cmd|v.hull|version=70}} || ? ||
|-
| {{cmd|v.in.ascii|version=70}} || ? ||
|-
| {{cmd|v.in.db|version=70}} || ? ||
|-
| {{cmd|v.in.dxf|version=70}} || ? ||
|-
| {{cmd|v.in.e00|version=70}} || ? ||
|-
| {{cmd|v.in.geonames|version=70}} || ? ||
|-
| {{cmd|v.in.gns|version=70}} || ? ||
|-
| {{cmd|v.in.lines|version=70}} || ? ||
|-
| {{cmd|v.in.mapgen|version=70}} || ? ||
|-
| {{cmd|v.in.ogr|version=70}} || ? ||
|-
| {{cmd|v.in.postgis|version=70}} || ? ||
|-
| {{cmd|v.in.region|version=70}} || ? ||
|-
| {{cmd|v.in.sites|version=70}} || ? ||
|-
| {{cmd|v.in.sites.all|version=70}} || ? ||
|-
| {{cmd|v.in.wfs|version=70}} || ? ||
|-
| {{cmd|v.info|version=70}} || ? ||
|-
| {{cmd|v.kcv|version=70}} || ? ||
|-
| {{cmd|v.kernel|version=70}} || ? ||
|-
| {{cmd|v.krige|version=70}} || ? ||
|-
| {{cmd|v.label|version=70}} || ? ||
|-
| {{cmd|v.lidar.correction|version=70}} || ? ||
|-
| {{cmd|v.lidar.edgedetection|version=70}} || ? ||
|-
| {{cmd|v.lidar.growing|version=70}} || ? ||
|-
| {{cmd|v.lrs.create|version=70}} || ? ||
|-
| {{cmd|v.lrs.label|version=70}} || ? ||
|-
| {{cmd|v.lrs.segment|version=70}} || ? ||
|-
| {{cmd|v.lrs.where|version=70}} || ? ||
|-
| {{cmd|v.mkgrid|version=70}} || ? ||
|-
| {{cmd|v.neighbors|version=70}} || ? ||
|-
| {{cmd|v.net|version=70}} || ? ||
|-
| {{cmd|v.net.alloc|version=70}} || ? ||
|-
| {{cmd|v.net.allpairs|version=70}} || ? ||
|-
| {{cmd|v.net.bridge|version=70}} || ? ||
|-
| {{cmd|v.net.centrality|version=70}} || ? ||
|-
| {{cmd|v.net.components|version=70}} || ? ||
|-
| {{cmd|v.net.connectivity|version=70}} || ? ||
|-
| {{cmd|v.net.distance|version=70}} || ? ||
|-
| {{cmd|v.net.flow|version=70}} || ? ||
|-
| {{cmd|v.net.iso|version=70}} || ? ||
|-
| {{cmd|v.net.path|version=70}} || ? ||
|-
| {{cmd|v.net.salesman|version=70}} || ? ||
|-
| {{cmd|v.net.spanningtree|version=70}} || ? ||
|-
| {{cmd|v.net.steiner|version=70}} || ? ||
|-
| {{cmd|v.net.timetable|version=70}} || ? ||
|-
| {{cmd|v.net.visibility|version=70}} || ? ||
|-
| {{cmd|v.normal|version=70}} || ? ||
|-
| {{cmd|v.out.ascii|version=70}} || ? ||
|-
| {{cmd|v.out.dxf|version=70}} || ? ||
|-
| {{cmd|v.out.gps|version=70}} || ? ||
|-
| {{cmd|v.out.ogr|version=70}} || ? ||
|-
| {{cmd|v.out.postgis|version=70}} || ? ||
|-
| {{cmd|v.out.pov|version=70}} || ? ||
|-
| {{cmd|v.out.svg|version=70}} || ? ||
|-
| {{cmd|v.out.vtk|version=70}} || ? ||
|-
| {{cmd|v.outlier|version=70}} || ? ||
|-
| {{cmd|v.overlay|version=70}} || ? ||
|-
| {{cmd|v.parallel|version=70}} || ? ||
|-
| {{cmd|v.patch|version=70}} || ? ||
|-
| {{cmd|v.perturb|version=70}} || ? ||
|-
| {{cmd|v.proj|version=70}} || ? ||
|-
| {{cmd|v.qcount|version=70}} || ? ||
|-
| {{cmd|v.random|version=70}} || ? ||
|-
| {{cmd|v.rast.stats|version=70}} || ? ||
|-
| {{cmd|v.reclass|version=70}} || ? ||
|-
| {{cmd|v.report|version=70}} || ? ||
|-
| {{cmd|v.sample|version=70}} || ? ||
|-
| {{cmd|v.segment|version=70}} || ? ||
|-
| {{cmd|v.select|version=70}} || ? ||
|-
| {{cmd|v.split|version=70}} || ? ||
|-
| {{cmd|v.support|version=70}} || ? ||
|-
| {{cmd|v.surf.bspline|version=70}} || ? ||
|-
| {{cmd|v.surf.idw|version=70}} || ? ||
|-
| {{cmd|v.surf.rst|version=70}} || ? ||
|-
| {{cmd|v.to.3d|version=70}} || ? ||
|-
| {{cmd|v.to.db|version=70}} || ? ||
|-
| {{cmd|v.to.points|version=70}} || ? ||
|-
| {{cmd|v.to.rast|version=70}} || ? ||
|-
| {{cmd|v.to.rast3|version=70}} || ? ||
|-
| {{cmd|v.transform|version=70}} || ? ||
|-
| {{cmd|v.type|version=70}} || ? ||
|-
| {{cmd|v.univar|version=70}} || ? ||
|-
| {{cmd|v.vol.rst|version=70}} || ? ||
|-
| {{cmd|v.voronoi|version=70}} || ? ||
|-
| {{cmd|v.what|version=70}} || ? ||
|-
| {{cmd|v.what.rast|version=70}} || ? ||
|-
| {{cmd|v.what.vect|version=70}} || ? ||
|-
|}

=== Various ===

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)'''
|-
| {{cmd|nviz|version=70}} || ? ||
|-
| {{cmd|nviz_cmd|version=70}} || ? ||
|-
| {{cmd|wximgview|version=70}} || ? ||
|-
| {{cmd|wxpyimgview|version=70}} || ? ||
|-
| {{cmd|xganim|version=70}} || ? ||
|-
| {{cmd|ximgview|version=70}} || ? ||
|-
|}

== List of selected AddOns modules ==

See [[GRASS AddOns]] for full list of available modules. Feel free to extend this list.

{|class="wikitable"
|'''Module''' || '''Core/Tools/Addons''' || '''Toolbox(es)''' || '''Note'''
|-
| {{AddonCmd|r.stream.angle}} || T || HY ||
|-
| {{AddonCmd|r.seg}} || T || IM || It could be rename to `i.seg`
|-
| {{AddonCmd|i.topocorr}} || T || IM ||
|-
| {{AddonCmd|r.diversity}} || T || LA ||
|-
| {{AddonCmd|Ps.output}} || ? || ||
|-
| ... || ? || ||
|-
|}

== How to implement ==

=== propose 1 ===
* add html tag <param> in the description.html with these options:
<param name = "core"> for core module
<param name = "tool" value="tool_code/codes"> for toolbox
<param name = "addons" [value="tool_code/codes"]> for addons, value is optional

* create a script to generate a xml file for each toolbox
* add toolbox option in g.extension to read the xml and install the modules

[[Category:Development]]

Time series development

2011-05-02T02:44:13Z

⚠️Helena: /* Open Issues */

* ''see also the [[Time series]] user-help wiki page''

== About ==
This page is born out of discussions in Lausanne. A lot of people seem to be interested in having some standardized, documented format for dealing with time series in GRASS, so that we can deal with data (e.g. climate station, water gauges), link with models, etc., without having to come up with a custom solution each time. This could also lead to modules to help with interpolation to deal with missing values, etc.

There was also discussion of possibly setting up a mailing list. Do we want this?
: I would vote against just-another-mailing list [[User:Neteler|Neteler]] 23:51, 18 September 2006 (CEST)

==== Ideas from MN ====

* each imported raster map get's automatically "registered" in an SQL table
** Table structure:
*** map name
*** map creator (optional)
*** time stamp of import
*** time stamp of map production (optional)
*** time range of validity (optional)
* g.list, g.rename etc. tools have a new "where" parameter do search maps in this table
* g.remove will also remove row from SQL table
* SQL commands can be used for search by time stamps

==== maxi's proposal ====
* what about a table with time series (sort of header of each time series) and another table for each time serie with a list of associated filename and related timestamp?
** time series head table structure:
*** series name
*** creator name
*** timestamp of creation
*** range of validity
*** time step
*** ....
** time serie associated map (table named like the related time serie):
*** timestamp
*** map name
*** timestamp of import

==== Soerens ideas ====

===== a temporal gis extension for grass =====

''The temporal extension should not only help to manage temporal data, the data should also be easy to analyse and visualize in time.''

====== temproal gis implementation in grass ======

* a seperate library in grass (dir temporal_gis or tgis)
* should manage raster, raster3d, vector maps and groups of raster maps (imagery groups)
* the existing timestamps should be used for registration in a temporal database
* maps can be registered and unregistered in the temporal database
* it should be possible to cretae several temporal tables in the database
** '''those tables are a new datatype in grass'''
** the tables should be used for thematic time series
** maps and groups may be registered in different tables
** it should be very easy to register and unregister thousands of maps in the database
** tables will have a description, history, transaction log, ceration time and modification time
** statistical Informations about the maps (ranges) should be stored in the database
** if the raster map changes the table should be easily updatable (automatic update implemented in the libs -> if map is closed update the temporal table)
* the temporal database should allow temporal queries for one, several or all tables in the database
* if an sql database is used for map storing the full functionality of the grass-db-lib will be used
* grass temporal gis library functions should begin with a T_, example:
T_register_rast_in_table(mapset, name, table)
T_unregister_rast_in_table(mapset, name, table)
T_query_table(table, sort, sqlstring)
...

===== changes to existing libs/modules =====

* timestamps support for groups must be added
* r.timestamp, r3.timestamp and v.timestamp should be implemented in g.timestamp with group support
* support for temporal region (starttime, endtime, timesteps) in g.region
* g.remove, g.rename and g.copy will need to have access to the temporal database
** if a maps is removed and registered in temporal tables, the table entry should also be removed
** every map keeps the info in which temporal tables it is registered (additional file or info in header)
* the timestamp should be automatically created if a map is created
* g.list should list all temporal databases, not the registered maps (t.info should do this)
* if automatically temporal table update is requested, all the file io libs of raster, raster3d, vector maps and groups have to be extended

===== temporal database concepts =====

====== SQL databases with a time datatype ======

* the temporal database in which the maps/groups are registered should provide temporal queries
** select all maps between 20 jan 2002 and 13 feb 2004
** select all maps with a valid range of 3 months
** select all maps with datum < 13 sep 1999
** select all maps with a valid range of 10 years and a value range between [20:45]
* Postgresql is one Open Source database which supports such queries and suitable temporal datatypes [[http://www.postgresql.org/files/documentation/books/pghandbuch/html/datatype-datetime.html]] and [[http://www.postgresql.org/files/documentation/books/pghandbuch/html/functions-datetime.html]]
* since version 3.0.x sqlite also supports temporal queries and datatypes [[http://www.sqlite.org/cvstrac/wiki?p=DateAndTimeFunctions]]

====== SQL databases without a time datatype ======

* sql databses which are able to handle double data types can be used
** if the timestamps of the maps are converted into a double data type (seconds) befor send to the database
*** 21 jan 2004 14:35:21 = 7897456389 seconds
** the conversion have to be done automatically by the grass lib
** temporal queries are partly available with staments like " select * from table where dateLarger(date, '20 jan 2006')"
** complex WHERE statements may not be available because the dates have to be converted into seconds
e.g: where="startdate < 20 jan 2006 AND startdate > 14 sep 1990 AND daterange < 4 years 3 mon"
will be hard to implement, the dates have to be parsed and replaced by one number (seconds)

====== text based databases ======

* another way is to implement this functionality with text tables
* the time stamps are managed in a double linked list
* the query functionality is not that powerful then a postgresql database
* only simple temporal queries are possible

text database example:

temporal_gis
|-- group
| `-- Landsat_2006_2010
| |-- head
| |-- hist
| |-- list
| |-- range
| |-- time_wind
| `-- transaction_log
|-- raster
| |-- landuse_2006_2010
| | |-- head
| | |-- hist
| | |-- list
| | |-- range
| | |-- time_wind
| | `-- transaction_log
| `-- soils_2006_2010
| |-- head
| |-- hist
| |-- list
| |-- range
| |-- time_wind
| `-- transaction_log
|-- raster3d
| `-- phdist_2006_2010
| |-- head
| |-- hist
| |-- list
| |-- range
| |-- time_wind
| `-- transaction_log
`-- vector
`-- observ_wells_2006_2010
|-- head
|-- hist
|-- list
|-- range
|-- time_wind
`-- transaction_log

===== timestamps in temporal database =====

* the following timestamps should be created in the database
** a valid timestamp with startime or start- and endtime
** creation time
** modification time
** if the maps have a valid start and endtime the event duration should be calculated by the database automatically

===== temporal management tools =====

* the time is a new datatype in grass
* therefore the temporal management should be done by specific commands starting with t.*
* tools for queries, register, unregister und extraction of maps from the temporal database have to be implemented, like t.info, t.register, t.unregister and t.extract ...

Example t.register:

GRASS 6.3.cvs > t.register help

Description:
Register groups, raster, raster3d and vector maps into the temporal database

Keywords:
temporal, time

Usage:
t.register [-s] [tgroup=string[,string,...]]
[trast=string[,string,...]] [trast3d=string[,string,...]]
[tvect=string[,string,...]] [group=string[,string,...]]
[rast=string[,string,...]] [rast3d=string[,string,...]]
[vect=string[,string,...]] [date=timestamp[,timestamp,...]]
[timestep=timestep[,timestep,...]]

Flags:
-s Use the timestep between new maps.

Parameters:
tgroup Temporal group database(s) in which the group(s) should be registered
trast Temporal raster database(s) in which the raster(s) should be registered
trast3d Temporal raster3d database(s) in which the raster3d(s) should be registered
tvect Temporal vector database(s) in which the vector(s) should be registered
group Group(s) to be registered in the temporal group database
rast Raster map(s) to be registered in the temporal raster database
rast3d Raster3d map(s) to be registered in the temporal raster3d database
vect Vector map(s) to be registered in the temporal vector database
date datetime, datetime1/datetime2 for map(s)
timestep timestep between the maps

====== example ======

register 3 raster maps beginning from 20 jan 2001 with a timestep of 3 month in temporal database table Landsat
t.register -s trast=Landsat rast=LandsatJan,LandsatApr,LandsatJul date="20 jan 2001" timestep="3 mon"

Table:
1 LandsatJan 20 jan 2001 ...
2 LandsatApr 20 apr 2001 ...
3 LandsatJul 20 jul 2001 ...

===== OO Layer =====

* it should be possible to have data access with spatial-temporal functions:
** value = g4dDataObject->Get4DValue(x, y, z, timestamp) -- for volume maps
** value = g4dDataObject->Get4DValue(x, y, timestamp) -- for raster maps

* based on this functionality a 4d animation tool based on VTK should be implemented
[[User:Huhabla|huhabla]] 00:19, 26 September 2006 (CEST)

===== Implemented Prototype: r.rast4d=====

http://trac.osgeo.org/grass/browser/grass-addons/raster/r.rast4d

==== Jachym's notes ====
On IRC, we discussed, that time series would be stored in database (PostgreSQL). If data format would be like YYYY-MM-DD-HH-MM-SS, the "database" could be some textfile, which would be sortable via standard 'sort' and g.* modules would not need to speek SQL - KISS, works even on a toaster.

g.list rast should print all raster maps. Raster map belonging to time serie does not stop to be raster map. New data type "times" has to be created, so that modules like g.list, g.remove ... can handle it.

If "times" is going to be new GRASS data type, new t.* group of commands has to be introduced, to have equivalent commands for r.what, d.rast, r.schmeiß.mich.tot, ...

==== Alessandro Frigeri's notes ====
Scale/resolution issues:
* Implementation of absolute and relative time scale (e.g. numerical modeling is likely to require times referred to the start of the simulation, remote sensed data is commonly referred to UTC time).
* Implementation of Units Of Measure conversions for time (see specific issue on Units Of Measure implementation) so we can analyze time-series in their more natural unit and resolution (geologic events are in Mega or Giga years while surface temperature variations are in the order of magniture of hours, or kilo seconds)

==== Open Issues ====
* will 'g.list rast' show also rasters belonging to time series?
* how to deal with huge file number in a folder? (very long serie often deals with a huge number of maps)
** limitation: how many rasters can a folder contain ('fileno' in /etc/security/limits.conf).
** efficiency: huge number of files will tremendiously slow down each map listing procedures.
* associated color table: only one color table should serve one series (avoid multiple color table for each map)
* linear regression in r.series should be modified to support irregular time intervals in time series (will that be a t.series ?)

[[Category:Development]]

GRASS Community Sprint Prague 2011

2011-05-02T02:18:21Z

⚠️Helena: /* Technical */

__TOC__

Succeeding the [http://geoinformatics.fsv.cvut.cz/gwiki/Geoinformatics_FCE_CTU_2011 Geoinformatics FCE CTU 2011] ''(International Conference on Free Software and Open Source in Geoinformatics)'', 19-20 May 2011, [http://en.wikipedia.org/wiki/Prague Prague], [http://en.wikipedia.org/wiki/Czech_Republic Czech Republic], the GRASS GIS project will hold a '''GRASS Developer and Power User Meeting, aka 'GRASS Community Sprint'''' ''from May 20 to May 25, 2011''.

'''Important dates:'''

* 19 (Thursday) - 20 (Friday) May 2011: Geoinformatics FCE CTU 2011 conference

* '''20 (Friday) - 25 (Wednesday) May 2011: GRASS Community Sprint @ [http://www.fsv.cvut.cz/ FCE CTU]'''

== Purpose ==

Get together GRASS project members to make decisions and tackle larger problems.

For this meeting, we welcome people committed to improving the GRASS GIS project. This includes developers, documenters, bug reporters, translators etc.

== Sponsors ==



If you are interested to sponsor the GRASS Community Sprint, please read about 
    '''sponsoring the GRASS project at [http://grass.osgeo.org/donation.php http://grass.osgeo.org/donation.php]''' 
and, if needed, contact [[User:Neteler|Markus Neteler]] <tt><neteler at osgeo.org></tt>. Any surplus at the end of the event will be turned over to the GRASS GIS project.

The first GRASS Community Sprint is a great occasion for you to support the development of GRASS. With your contribution you'll enable more developers to meet in Prague. The community sprint is an important opportunity for the GRASS developers to discuss and collaboratively resolve bugs, plan the direction for the project and work on new features. Please see below for the more detailed agenda. The developers and contributors are donating their valuable time, so it would be great if in-kind funding can be made available from within the community to cover out-of-pocket expenses. All of the work that takes place at the community sprint will be directly contributed back into the GRASS project to the benefit of everyone who uses it.

=== Thanks to our sponsors ===

* [http://gfoss.it/ GFOSS.it Associazione Italiana per l'Informazione Geografica Libera]
* Stefan Sylla, [http://sylla-consult.de/en/ sylla-consult], Frankfurt, Germany

== Timing ==

'''When''': Friday, May 20, 2011 (day of arrival) - Wednesday, May 25, 2011 (day of departure)

Of course you are invited to join or leave the community sprint whenever you want.

'''Duration''':

* Friday is day of arrival
** First meeting in the evening (after the [http://geoinformatics.fsv.cvut.cz/gwiki/Geoinformatics_FCE_CTU_2011 conference]) to define the agenda
* Saturday to Tuesday
** Full days
* Wednesday is day of departure
** Probably hacking for people with a flight later in the evening

== Venue ==
[[Image:logo_cvut.jpg|130px|left]]
Department of Mapping and Cartography 
[http://www.fsv.cvut.cz Faculty of Civil Engineering] 
[http://www.cvut.cz Czech Technical University in Prague], [http://en.wikipedia.org/wiki/Czech_Republic Czech Republic] 
[http://geoinformatics.fsv.cvut.cz/gwiki/Room_B367 Room B367] 

'''[http://geoinformatics.fsv.cvut.cz/gwiki/Where_you_can_find_us Location & Transportations]'''

Prague has an international [http://www.prg.aero/en/ airport] and is also reachable by train, bus or car.

== Accommodation and Costs ==

Participants should plan for the following costs:

* Travel to Prague, variable depending on where you come from
* Accommodation and meals
'''Please note''': The currency in Czech Republic is [http://en.wikipedia.org/wiki/Czech_crown crown] (CZK, koruna, Kč). 100 Czech crowns are about 4 Euros (see [http://www.cnb.cz/en/financial_markets/foreign_exchange_market/exchange_rate_fixing/daily.jsp current rates]).

'''[http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague Accommodation in Prague]'''

:* [http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague#Masarykova_Kolej_Hotel Masarykova Kolej Hotel]
:* [http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague#Hotel_DAP Hotel DAP]
:* [http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague#Hotel_Krystal Hotel Krystal]
:* [http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague#Pension_Hanspaulka Pension Hanspaulka]
:* [http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague#Hotel_Silenzio Hotel Silenzio]
:* Special offer: ''sleeping for free in the kindergarten'' (30min by city urban mass transportation from the university campus, sleeping bag required, kitchen and WC available, no showers, in working days only available from 8 p.m. to 8 a.m.), contact [[User:Landa|Martin Landa]] for details
:* See also http://www.hotel.cz/praha-6/accommodation/

Please let us know your time of arrival and leaving, so we can book for the accommodations and organize the logistics.

'''TO BE DEFINED:''' We will cover as much as possible thanks to our sponsors.

== Weather and Common Item Prices ==

* In May the weather in Prague is usually quite warm ([http://www.prague-spot.com/climate 15 or more degrees by day])
* A espresso coffee is about 20 CZK (80 cents), a beer (half of liter) in a common pub is around 25 CZK (1 euro), can be more in special pubs. In Prague you can have a full meal (see [http://en.wikipedia.org/wiki/Czech_cuisine Czech cuisine]) for still 75 - 150 CZK (3 - 6 euros), but beware of tourist restaurants, the prize can easily rise. It's quite easy to find in Prague also Italian or Chinese restaurants.

== Agenda - What we plan to do ==

'''Note:''' The program is generally open for your ideas. Please write an email to the [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developer list] to discuss your contribution.

=== Timeline ===

* Friday, 20 May:
** Welcome meeting
** Discuss and finetune agenda

* Saturday, 21 May:
** Morning:
** Afternoon:
** Evening: '''[http://www.youtube.com/watch?v=Jf6NFRGO9ak Valentina Shuklina's] concert in [http://www.cafe-technika.cz Café Technika]'''

* Sunday, 22 May:
** Community Sprinting 1
** Evening: '''Social dinner'''

* Monday, 23 May:
** Community Sprinting 2

* Tuesday, 24 May:
** Community Sprinting 3

* Wednesday, 25 May:
** Finish press release (including thanks to sponsors with names)
** Wrap up and see you soon

=== Topics ===

==== Non-technical ====

* Discuss new sponsoring concept
* Populate new GRASS Website with content from old website
* ...

==== Semi-technical ====

* Improve manual with more examples and screenshots
* Outline screen capture videos for "Getting started with GRASS" and for using wxGUI for various specific tasks
* Change manual to use Sphinx (see related {{trac|151}})
* Support translated manual pages (see related {{trac|846}})
* Design new project web site engine based on CMS
* ...

==== Technical ====

wxGUI: graphical user interface
* wxGUI: add language selector at startup or in GUI configuration
* wxGUI modeller improvements
* wxGUI: further improve the integration of CLI and GUI
* wxNVIZ: consider to switch to [[OpenSceneGraph]] for 3D visualization
* ...

Built system, installation:
* autocompilation job for GRASS-Addons
* backport Makefile system from GRASS 7 to GRASS 6
* Improve {{cmd|g.extension}} (enable to use prepared winGRASS Addon binaries)
* Define new [[GRASS repository layout proposal|toolbox concept]]
* Daily generated OSGeo4W packages for 6.5svn, 7.0svn.
* ...

Documentation:
* develop something like the wxGUI module search tree for the HTML pages

Testing and benchmarking:
* write tests for different core modules (see Soeren's testsuite)
* discuss testing procedure for GUI
* benchmarking between GRASS, QGIS, Sextante, gvSIG, ... for watershed calculation, import, export, extract, ...

Capabilities:
* Discussion and implementation time frame of temporal GIS capabilities in GRASS [[Time series development]]
* Discussion about a new parser interface for better command line, GUI and WPS support. Discussion started here: http://trac.osgeo.org/grass/ticket/1031
* Improve [[WPS]] support
* Discuss improvements in GRASS 7 vector engine (OGR support, lightweight topology structures, better 3D support)
* Discuss fundamental changes in raster and vector engine for GRASS 8
* winGRASS: GRASS and R-stats integration improvements (see related {{trac|1149}})
* Implement [http://www.gaia-gis.it/spatialite/ RasterLite] as GRASS raster database
* ...

;Discussion on ML
* http://lists.osgeo.org/pipermail/grass-user/2011-March/059830.html

== Participation ==

We are planning for attendance of 20/30 people (i.e., hacking places) but of course you are welcome to join us and bring new ideas with you, as more places are available. Please add your name here or contact [[User:Landa|Martin Landa]] <tt><landa.martin at gmail.com></tt>:

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;"
|width=50px|'''No'''
|width=150px|'''Participant '''
|width=100px|'''Arrival'''
|width=100px|'''Departure'''
|'''Topic'''
|width=75px|'''T-Shirt'''
|'''Notes'''
|-
|1
|[[User:Landa|Martin Landa]]
| May 20
| May 25
|Toolbox concept, vector engine in GRASS 7, wxGUI
| M
|
|-
|2
|[[User:Neteler|Markus Neteler]]
|May 17
|May 23
| sponsoring, coding, manual, odds and ends
| M
|
|-
|3
|[[User:Lucadelu|Luca Delucchi]]
|
|
|New toolbox concept,translation
|
|
|-
|4
|[[User:RobertSzczepanek|Robert Szczepanek]]
|May 19
|May 23
|wxGUI, hydrological toolbox, translation
|M
|
|-
|5
|[[User:madi|Margherita Di Leo]]
|May 16
|May 25
| [http://grass.osgeo.org/devel/i18n.php Translation] , python api, wxGUI
| L
|
|-
|6
|[[User:annalisapg|Annalisa Minelli]]
|May 16
|May 25
|[http://grass.osgeo.org/devel/i18n.php Translation], python api
|S
|
|-
|7
|[[User:AnneGhisla|Anne Ghisla]]
|
|
|wxGUI development, v.krige
|
|to be confirmed (but 80% sure)
|-
|8
|[[User:Afrigeri|Alessandro Frigeri]]
|May 18
|May 25
|Planetary SRS in GRASS GIS - OGC W*S tweakings for IAU GCS
|M
|
|-
|9
|[[User:huhabla|Sören Gebbert]]
| May 20
| May 23
|Time series development, Web Processing Service support, wps-grass-bridge, New parser interface, vtk-grass-bridge
| L
|
|-
|-
|10
|[[User:MilenaN|Milena Nowotarska]]
|
|
|wxGUI, translation
|
|
|-
|11
|[[User:helena|Helena Mitasova]]
|May 22
|May 25
|wxnviz, v.vol.rst, r3 and time series, toolbox concept
|S
|
|-
|12
|[[User:blazek|Radim Blazek]]
|?
|?
|QGIS friendliness lobbying
|XL
|
|-
|13
|[[User:peter.loewe|Peter Loewe]]
|May 20
|May 23
|GRASS on computation grids lobbying, povray, paraview/vtk
|XL
|
|-
|14
|[[User:moovida|Andrea Antonello]]
|May 18
|May 23
|GRASS toolbox for uDig, Geopaparazzi import module for GRASS, Hopefully get knowledge about new raster format
|L
|to be confirmed (but 87% sure)
|-
|15
|[[User:mmetz|Markus Metz]]
|
|
|vector engine in GRASS 7, support for massive datasets
|L
|
|-
|
|''add yourself here...''
|
|
|
|
|-
|}

== Individual Preparation ==

* Bring your own computer
* Install subversion and the compiler tools, and come with a working GRASS development environment if possible.


== FAQ ==

* ''Is the GRASS Community Sprint just a coding event?''
** It is mainly a coding and documentation event. It is a working session for people who are already participants in the GRASS project and/or are committed to improving the GRASS project.
** On demand we can do some presentations of current working GRASS implementation and new upcoming features to spread the idea of Open Source GIS software
* ''Is the GRASS Community Sprint for developers only?''
** No: anybody can help, with testing, checking out bugs and fixes, documentation and more.
* ''Where can I get help and more information about the community sprint?''
** Contact [[User:Landa|Martin Landa]] <tt><landa.martin at gmail.com></tt>

[[Category: Workshops]]

GRASS Community Sprint Prague 2011

2011-05-02T02:11:02Z

⚠️Helena: /* Semi-technical */

__TOC__

Succeeding the [http://geoinformatics.fsv.cvut.cz/gwiki/Geoinformatics_FCE_CTU_2011 Geoinformatics FCE CTU 2011] ''(International Conference on Free Software and Open Source in Geoinformatics)'', 19-20 May 2011, [http://en.wikipedia.org/wiki/Prague Prague], [http://en.wikipedia.org/wiki/Czech_Republic Czech Republic], the GRASS GIS project will hold a '''GRASS Developer and Power User Meeting, aka 'GRASS Community Sprint'''' ''from May 20 to May 25, 2011''.

'''Important dates:'''

* 19 (Thursday) - 20 (Friday) May 2011: Geoinformatics FCE CTU 2011 conference

* '''20 (Friday) - 25 (Wednesday) May 2011: GRASS Community Sprint @ [http://www.fsv.cvut.cz/ FCE CTU]'''

== Purpose ==

Get together GRASS project members to make decisions and tackle larger problems.

For this meeting, we welcome people committed to improving the GRASS GIS project. This includes developers, documenters, bug reporters, translators etc.

== Sponsors ==



If you are interested to sponsor the GRASS Community Sprint, please read about 
    '''sponsoring the GRASS project at [http://grass.osgeo.org/donation.php http://grass.osgeo.org/donation.php]''' 
and, if needed, contact [[User:Neteler|Markus Neteler]] <tt><neteler at osgeo.org></tt>. Any surplus at the end of the event will be turned over to the GRASS GIS project.

The first GRASS Community Sprint is a great occasion for you to support the development of GRASS. With your contribution you'll enable more developers to meet in Prague. The community sprint is an important opportunity for the GRASS developers to discuss and collaboratively resolve bugs, plan the direction for the project and work on new features. Please see below for the more detailed agenda. The developers and contributors are donating their valuable time, so it would be great if in-kind funding can be made available from within the community to cover out-of-pocket expenses. All of the work that takes place at the community sprint will be directly contributed back into the GRASS project to the benefit of everyone who uses it.

=== Thanks to our sponsors ===

* [http://gfoss.it/ GFOSS.it Associazione Italiana per l'Informazione Geografica Libera]
* Stefan Sylla, [http://sylla-consult.de/en/ sylla-consult], Frankfurt, Germany

== Timing ==

'''When''': Friday, May 20, 2011 (day of arrival) - Wednesday, May 25, 2011 (day of departure)

Of course you are invited to join or leave the community sprint whenever you want.

'''Duration''':

* Friday is day of arrival
** First meeting in the evening (after the [http://geoinformatics.fsv.cvut.cz/gwiki/Geoinformatics_FCE_CTU_2011 conference]) to define the agenda
* Saturday to Tuesday
** Full days
* Wednesday is day of departure
** Probably hacking for people with a flight later in the evening

== Venue ==
[[Image:logo_cvut.jpg|130px|left]]
Department of Mapping and Cartography 
[http://www.fsv.cvut.cz Faculty of Civil Engineering] 
[http://www.cvut.cz Czech Technical University in Prague], [http://en.wikipedia.org/wiki/Czech_Republic Czech Republic] 
[http://geoinformatics.fsv.cvut.cz/gwiki/Room_B367 Room B367] 

'''[http://geoinformatics.fsv.cvut.cz/gwiki/Where_you_can_find_us Location & Transportations]'''

Prague has an international [http://www.prg.aero/en/ airport] and is also reachable by train, bus or car.

== Accommodation and Costs ==

Participants should plan for the following costs:

* Travel to Prague, variable depending on where you come from
* Accommodation and meals
'''Please note''': The currency in Czech Republic is [http://en.wikipedia.org/wiki/Czech_crown crown] (CZK, koruna, Kč). 100 Czech crowns are about 4 Euros (see [http://www.cnb.cz/en/financial_markets/foreign_exchange_market/exchange_rate_fixing/daily.jsp current rates]).

'''[http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague Accommodation in Prague]'''

:* [http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague#Masarykova_Kolej_Hotel Masarykova Kolej Hotel]
:* [http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague#Hotel_DAP Hotel DAP]
:* [http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague#Hotel_Krystal Hotel Krystal]
:* [http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague#Pension_Hanspaulka Pension Hanspaulka]
:* [http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague#Hotel_Silenzio Hotel Silenzio]
:* Special offer: ''sleeping for free in the kindergarten'' (30min by city urban mass transportation from the university campus, sleeping bag required, kitchen and WC available, no showers, in working days only available from 8 p.m. to 8 a.m.), contact [[User:Landa|Martin Landa]] for details
:* See also http://www.hotel.cz/praha-6/accommodation/

Please let us know your time of arrival and leaving, so we can book for the accommodations and organize the logistics.

'''TO BE DEFINED:''' We will cover as much as possible thanks to our sponsors.

== Weather and Common Item Prices ==

* In May the weather in Prague is usually quite warm ([http://www.prague-spot.com/climate 15 or more degrees by day])
* A espresso coffee is about 20 CZK (80 cents), a beer (half of liter) in a common pub is around 25 CZK (1 euro), can be more in special pubs. In Prague you can have a full meal (see [http://en.wikipedia.org/wiki/Czech_cuisine Czech cuisine]) for still 75 - 150 CZK (3 - 6 euros), but beware of tourist restaurants, the prize can easily rise. It's quite easy to find in Prague also Italian or Chinese restaurants.

== Agenda - What we plan to do ==

'''Note:''' The program is generally open for your ideas. Please write an email to the [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developer list] to discuss your contribution.

=== Timeline ===

* Friday, 20 May:
** Welcome meeting
** Discuss and finetune agenda

* Saturday, 21 May:
** Morning:
** Afternoon:
** Evening: '''[http://www.youtube.com/watch?v=Jf6NFRGO9ak Valentina Shuklina's] concert in [http://www.cafe-technika.cz Café Technika]'''

* Sunday, 22 May:
** Community Sprinting 1
** Evening: '''Social dinner'''

* Monday, 23 May:
** Community Sprinting 2

* Tuesday, 24 May:
** Community Sprinting 3

* Wednesday, 25 May:
** Finish press release (including thanks to sponsors with names)
** Wrap up and see you soon

=== Topics ===

==== Non-technical ====

* Discuss new sponsoring concept
* Populate new GRASS Website with content from old website
* ...

==== Semi-technical ====

* Improve manual with more examples and screenshots
* Outline screen capture videos for "Getting started with GRASS" and for using wxGUI for various specific tasks
* Change manual to use Sphinx (see related {{trac|151}})
* Support translated manual pages (see related {{trac|846}})
* Design new project web site engine based on CMS
* ...

==== Technical ====

wxGUI: graphical user interface
* wxGUI: add language selector at startup or in GUI configuration
* wxGUI modeller improvements
* wxNVIZ: consider to switch to [[OpenSceneGraph]] for 3D visualization
* ...

Built system, installation:
* autocompilation job for GRASS-Addons
* backport Makefile system from GRASS 7 to GRASS 6
* Improve {{cmd|g.extension}} (enable to use prepared winGRASS Addon binaries)
* Define new [[GRASS repository layout proposal|toolbox concept]]
* Daily generated OSGeo4W packages for 6.5svn, 7.0svn.
* ...

Documentation:
* develop something like the wxGUI module search tree for the HTML pages

Testing and benchmarking:
* write tests for different core modules (see Soeren's testsuite)
* benchmarking between GRASS, QGIS, Sextante, gvSIG, ... for watershed calculation, import, export, extract, ...

Capabilities:
* Discussion and implementation time frame of temporal GIS capabilities in GRASS [[Time series development]]
* Discussion about a new parser interface for better command line, GUI and WPS support. Discussion started here: http://trac.osgeo.org/grass/ticket/1031
* Improve [[WPS]] support
* Discuss improvements in GRASS 7 vector engine (OGR support, lightweight topology structures, better 3D support)
* Discuss fundamental changes in raster and vector engine for GRASS 8
* winGRASS: GRASS and R-stats integration improvements (see related {{trac|1149}})
* Implement [http://www.gaia-gis.it/spatialite/ RasterLite] as GRASS raster database
* ...

;Discussion on ML
* http://lists.osgeo.org/pipermail/grass-user/2011-March/059830.html

== Participation ==

We are planning for attendance of 20/30 people (i.e., hacking places) but of course you are welcome to join us and bring new ideas with you, as more places are available. Please add your name here or contact [[User:Landa|Martin Landa]] <tt><landa.martin at gmail.com></tt>:

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;"
|width=50px|'''No'''
|width=150px|'''Participant '''
|width=100px|'''Arrival'''
|width=100px|'''Departure'''
|'''Topic'''
|width=75px|'''T-Shirt'''
|'''Notes'''
|-
|1
|[[User:Landa|Martin Landa]]
| May 20
| May 25
|Toolbox concept, vector engine in GRASS 7, wxGUI
| M
|
|-
|2
|[[User:Neteler|Markus Neteler]]
|May 17
|May 23
| sponsoring, coding, manual, odds and ends
| M
|
|-
|3
|[[User:Lucadelu|Luca Delucchi]]
|
|
|New toolbox concept,translation
|
|
|-
|4
|[[User:RobertSzczepanek|Robert Szczepanek]]
|May 19
|May 23
|wxGUI, hydrological toolbox, translation
|M
|
|-
|5
|[[User:madi|Margherita Di Leo]]
|May 16
|May 25
| [http://grass.osgeo.org/devel/i18n.php Translation] , python api, wxGUI
| L
|
|-
|6
|[[User:annalisapg|Annalisa Minelli]]
|May 16
|May 25
|[http://grass.osgeo.org/devel/i18n.php Translation], python api
|S
|
|-
|7
|[[User:AnneGhisla|Anne Ghisla]]
|
|
|wxGUI development, v.krige
|
|to be confirmed (but 80% sure)
|-
|8
|[[User:Afrigeri|Alessandro Frigeri]]
|May 18
|May 25
|Planetary SRS in GRASS GIS - OGC W*S tweakings for IAU GCS
|M
|
|-
|9
|[[User:huhabla|Sören Gebbert]]
| May 20
| May 23
|Time series development, Web Processing Service support, wps-grass-bridge, New parser interface, vtk-grass-bridge
| L
|
|-
|-
|10
|[[User:MilenaN|Milena Nowotarska]]
|
|
|wxGUI, translation
|
|
|-
|11
|[[User:helena|Helena Mitasova]]
|May 22
|May 25
|wxnviz, v.vol.rst, r3 and time series, toolbox concept
|S
|
|-
|12
|[[User:blazek|Radim Blazek]]
|?
|?
|QGIS friendliness lobbying
|XL
|
|-
|13
|[[User:peter.loewe|Peter Loewe]]
|May 20
|May 23
|GRASS on computation grids lobbying, povray, paraview/vtk
|XL
|
|-
|14
|[[User:moovida|Andrea Antonello]]
|May 18
|May 23
|GRASS toolbox for uDig, Geopaparazzi import module for GRASS, Hopefully get knowledge about new raster format
|L
|to be confirmed (but 87% sure)
|-
|15
|[[User:mmetz|Markus Metz]]
|
|
|vector engine in GRASS 7, support for massive datasets
|L
|
|-
|
|''add yourself here...''
|
|
|
|
|-
|}

== Individual Preparation ==

* Bring your own computer
* Install subversion and the compiler tools, and come with a working GRASS development environment if possible.


== FAQ ==

* ''Is the GRASS Community Sprint just a coding event?''
** It is mainly a coding and documentation event. It is a working session for people who are already participants in the GRASS project and/or are committed to improving the GRASS project.
** On demand we can do some presentations of current working GRASS implementation and new upcoming features to spread the idea of Open Source GIS software
* ''Is the GRASS Community Sprint for developers only?''
** No: anybody can help, with testing, checking out bugs and fixes, documentation and more.
* ''Where can I get help and more information about the community sprint?''
** Contact [[User:Landa|Martin Landa]] <tt><landa.martin at gmail.com></tt>

[[Category: Workshops]]

User:Helena

2011-04-16T22:43:52Z

⚠️Helena: Created page with "Associate Professor at North Carolina State University, member of GRASS PSC and OSGeo foundation http://www.meas.ncsu.edu/faculty/mitasova/mitasova.html"

Associate Professor at North Carolina State University, member of GRASS PSC and OSGeo foundation

http://www.meas.ncsu.edu/faculty/mitasova/mitasova.html

GRASS Community Sprint Prague 2011

2011-04-16T22:35:27Z

⚠️Helena: /* Participation */

__TOC__

Succeeding the [http://geoinformatics.fsv.cvut.cz/gwiki/Geoinformatics_FCE_CTU_2011 Geoinformatics FCE CTU 2011] ''(International Conference on Free Software and Open Source in Geoinformatics)'', 19-20 May 2011, [http://en.wikipedia.org/wiki/Prague Prague], [http://en.wikipedia.org/wiki/Czech_Republic Czech Republic], the GRASS GIS project will hold a '''GRASS Developer and Power User Meeting, aka 'GRASS Community Sprint'''' ''from May 20 to May 25, 2011''.

'''Important dates:'''

* 19 (Thursday) - 20 (Friday) May 2011: Geoinformatics FCE CTU 2011 conference

* '''20 (Friday) - 25 (Wednesday) May 2011: GRASS Community Sprint @ [http://www.fsv.cvut.cz/ FCE CTU]'''

== Purpose ==

Get together GRASS project members to make decisions and tackle larger problems.

For this meeting, we welcome people committed to improving the GRASS GIS project. This includes developers, documenters, bug reporters, translators etc.

== Sponsors ==



If you are interested to sponsor the GRASS Community Sprint, please read about 
    '''sponsoring the GRASS project at [http://grass.osgeo.org/donation.php http://grass.osgeo.org/donation.php]''' 
and, if needed, contact [[User:Neteler|Markus Neteler]] <tt><neteler at osgeo.org></tt>. Any surplus at the end of the event will be turned over to the GRASS GIS project.

The first GRASS Community Sprint is a great occasion for you to support the development of GRASS. With your contribution you'll enable more developers to meet in Prague. The community sprint is an important opportunity for the GRASS developers to discuss and collaboratively resolve bugs, plan the direction for the project and work on new features. Please see below for the more detailed agenda. The developers and contributors are donating their valuable time, so it would be great if in-kind funding can be made available from within the community to cover out-of-pocket expenses. All of the work that takes place at the community sprint will be directly contributed back into the GRASS project to the benefit of everyone who uses it.

=== Thanks to our sponsors ===

* [http://gfoss.it/ Associazione Italiana per l'Informazione Geografica Libera]
* Stefan Sylla, [http://sylla-consult.de/en/ sylla-consult], Frankfurt, Germany

== Timing ==

'''When''': Friday, May 20, 2011 (day of arrival) - Wednesday, May 25, 2011 (day of departure)

Of course you are invited to join or leave the community sprint whenever you want.

'''Duration''':

* Friday is day of arrival
** First meeting in the evening (after the [http://geoinformatics.fsv.cvut.cz/gwiki/Geoinformatics_FCE_CTU_2011 conference]) to define the agenda
* Saturday to Tuesday
** Full days
* Wednesday is day of departure
** Probably hacking for people with a flight later in the evening

== Venue ==
[[Image:logo_cvut.jpg|130px|left]]
Department of Mapping and Cartography 
[http://www.fsv.cvut.cz Faculty of Civil Engineering] 
[http://www.cvut.cz Czech Technical University in Prague], [http://en.wikipedia.org/wiki/Czech_Republic Czech Republic] 
Room ''<to be defined>'' 

'''[http://geoinformatics.fsv.cvut.cz/gwiki/Where_you_can_find_us Location & Transportations]'''

Prague has an international [http://www.prg.aero/en/ airport] and is also reachable by train, bus or car.

== Accommodation and Costs ==

Participants should plan for the following costs:

* Travel to Prague, variable depending on where you come from
* Accommodation and meals
'''Please note''': The currency in Czech Republic is [http://en.wikipedia.org/wiki/Czech_crown crown] (CZK, koruna, Kč). 100 Czech crowns are about 4 Euros (see [http://www.cnb.cz/en/financial_markets/foreign_exchange_market/exchange_rate_fixing/daily.jsp current rates]).

'''[http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague Accommodation in Prague]'''

:* [http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague#Masarykova_Kolej_Hotel Masarykova Kolej Hotel]
:* [http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague#Hotel_DAP Hotel DAP]
:* [http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague#Hotel_Krystal Hotel Krystal]
:* [http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague#Pension_Hanspaulka Pension Hanspaulka]
:* [http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague#Hotel_Silenzio Hotel Silenzio]
:* Special offer: ''sleeping for free in the kindergarten'' (30min by city urban mass transportation from the university campus, sleeping bag required, kitchen and WC available, no showers, in working days only available from 8 p.m. to 8 a.m.), contact [[User:Landa|Martin Landa]] for details
:* See also http://www.hotel.cz/praha-6/accommodation/

Please let us know your time of arrival and leaving, so we can book for the accommodations and organize the logistics.

'''TO BE DEFINED:''' We will cover as much as possible thanks to our sponsors.

== Weather and Common Item Prices ==

* In May the weather in Prague is usually quite warm ([http://www.prague-spot.com/climate 15 or more degrees by day])
* A espresso coffee is about 20 CZK (80 cents), a beer (half of liter) in a common pub is around 25 CZK (1 euro), can be more in special pubs. In Prague you can have a full meal (see [http://en.wikipedia.org/wiki/Czech_cuisine Czech cuisine]) for still 75 - 150 CZK (3 - 6 euros), but beware of tourist restaurants, the prize can easily rise. It's quite easy to find in Prague also Italian or Chinese restaurants.

== Agenda ==

'''Note:''' The program is generally open for your ideas. Please write an email to the [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developer list] to discuss your contribution.

=== Topics ===

==== Non-technical ====

* Discuss new sponsoring concept
* ...

==== Semi-technical ====

* Change manual to use Sphinx (see related {{trac|151}})
* Support translated manual pages (see related {{trac|846}})
* Design new project web site engine based on CMS
* ...

==== Technical ====

* backport Makefile system from GRASS 7 to GRASS 6
* Improve {{cmd|g.extension}} (enable to use prepared winGRASS Addon binaries)
* Define new [[GRASS repository layout proposal|toolbox concept]]
* Discussion and implementation time frame of temporal GIS capabilities in GRASS [[Time_series_development]]
* Discussion about a new parser interface for better command line, GUI and WPS support. Discussion started here: http://trac.osgeo.org/grass/ticket/1031
* Improve [[WPS]] support
* Discuss improvements in GRASS 7 vector engine (OGR support, lightweight topology structures, better 3D support)
* Discuss fundamental changes in raster and vector engine for GRASS 8
* ...

;Discussion on ML
* http://lists.osgeo.org/pipermail/grass-user/2011-March/059830.html

== Participation ==

We are planning for attendance of 20/30 people (i.e., hacking places) but of course you are welcome to join us and bring new ideas with you, as more places are available. Please add your name here or contact [[User:Landa|Martin Landa]] <tt><landa.martin at gmail.com></tt>:

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;"
|width=50px|'''No'''
|width=150px|'''Participant '''
|width=100px|'''Arrival'''
|width=100px|'''Departure'''
|'''Topic'''
|width=75px|'''T-Shirt'''
|'''Notes'''
|-
|1
|[[User:Landa|Martin Landa]]
| May 20
| May 25
|Toolbox concept, vector engine in GRASS 7, wxGUI
| M
|
|-
|2
|[[User:Neteler|Markus Neteler]]
|
|
|
|
|
|-
|3
|[[User:Lucadelu|Luca Delucchi]]
|
|
|New toolbox concept,translation
|
|
|-
|4
|[[User:RobertSzczepanek|Robert Szczepanek]]
|
|
|wxGUI, hydrological toolbox, translation
|
|
|-
|5
|[[User:madi|Margherita Di Leo]]
|
|
|[http://grass.osgeo.org/devel/i18n.php Translation] , python api
|
|
|-
|6
|[[User:annalisapg|Annalisa Minelli]]
|
|
|[http://grass.osgeo.org/devel/i18n.php Translation], python api
|
|
|-
|7
|[[User:AnneGhisla|Anne Ghisla]]
|
|
|wxGUI development, v.krige
|
|to be confirmed (but 80% sure)
|-
|8
|[[User:Afrigeri|Alessandro Frigeri]]
|
|
| Planetary SRS in GRASS GIS - OGC W*S tweakings for IAU GCS
|
|
|-
|9
|[[User:huhabla|Sören Gebbert]]
| May 20
| May 23
|Time series development, Web Processing Service support, wps-grass-bridge, New parser interface, vtk-grass-bridge
| L
|
|-
|-
|10
|[[User:MilenaN|Milena Nowotarska]]
|
|
|wxGUI, translation
|
|
|-
|11
|[[User:helena|Helena Mitasova]]
|May 22
|May 25
|wxnviz, v.vol.rst, r3 and time series, toolbox concept
|S
|
|-
|''add yourself here...''
|
|
|
|
|
|-
|}

== Individual Preparation ==

* Bring your own computer
* Install subversion and the compiler tools, and come with a working GRASS development environment if possible.


== FAQ ==

* ''Is the GRASS Community Sprint just a coding event?''
** It is mainly a coding and documentation event. It is a working session for people who are already participants in the GRASS project and/or are committed to improving the GRASS project.
** On demand we can do some presentations of current working GRASS implementation and new upcoming features to spread the idea of Open Source GIS software
* ''Is the GRASS Community Sprint for developers only?''
** No: anybody can help, with testing, checking out bugs and fixes, documentation and more.
* ''Where can I get help and more information about the community sprint?''
** Contact [[User:Landa|Martin Landa]] <tt><landa.martin at gmail.com></tt>

[[Category: Workshops]]

GRASS Community Sprint Prague 2011

2011-04-16T22:33:24Z

⚠️Helena: /* Participation */

__TOC__

Succeeding the [http://geoinformatics.fsv.cvut.cz/gwiki/Geoinformatics_FCE_CTU_2011 Geoinformatics FCE CTU 2011] ''(International Conference on Free Software and Open Source in Geoinformatics)'', 19-20 May 2011, [http://en.wikipedia.org/wiki/Prague Prague], [http://en.wikipedia.org/wiki/Czech_Republic Czech Republic], the GRASS GIS project will hold a '''GRASS Developer and Power User Meeting, aka 'GRASS Community Sprint'''' ''from May 20 to May 25, 2011''.

'''Important dates:'''

* 19 (Thursday) - 20 (Friday) May 2011: Geoinformatics FCE CTU 2011 conference

* '''20 (Friday) - 25 (Wednesday) May 2011: GRASS Community Sprint @ [http://www.fsv.cvut.cz/ FCE CTU]'''

== Purpose ==

Get together GRASS project members to make decisions and tackle larger problems.

For this meeting, we welcome people committed to improving the GRASS GIS project. This includes developers, documenters, bug reporters, translators etc.

== Sponsors ==



If you are interested to sponsor the GRASS Community Sprint, please read about 
    '''sponsoring the GRASS project at [http://grass.osgeo.org/donation.php http://grass.osgeo.org/donation.php]''' 
and, if needed, contact [[User:Neteler|Markus Neteler]] <tt><neteler at osgeo.org></tt>. Any surplus at the end of the event will be turned over to the GRASS GIS project.

The first GRASS Community Sprint is a great occasion for you to support the development of GRASS. With your contribution you'll enable more developers to meet in Prague. The community sprint is an important opportunity for the GRASS developers to discuss and collaboratively resolve bugs, plan the direction for the project and work on new features. Please see below for the more detailed agenda. The developers and contributors are donating their valuable time, so it would be great if in-kind funding can be made available from within the community to cover out-of-pocket expenses. All of the work that takes place at the community sprint will be directly contributed back into the GRASS project to the benefit of everyone who uses it.

=== Thanks to our sponsors ===

* [http://gfoss.it/ Associazione Italiana per l'Informazione Geografica Libera]
* Stefan Sylla, [http://sylla-consult.de/en/ sylla-consult], Frankfurt, Germany

== Timing ==

'''When''': Friday, May 20, 2011 (day of arrival) - Wednesday, May 25, 2011 (day of departure)

Of course you are invited to join or leave the community sprint whenever you want.

'''Duration''':

* Friday is day of arrival
** First meeting in the evening (after the [http://geoinformatics.fsv.cvut.cz/gwiki/Geoinformatics_FCE_CTU_2011 conference]) to define the agenda
* Saturday to Tuesday
** Full days
* Wednesday is day of departure
** Probably hacking for people with a flight later in the evening

== Venue ==
[[Image:logo_cvut.jpg|130px|left]]
Department of Mapping and Cartography 
[http://www.fsv.cvut.cz Faculty of Civil Engineering] 
[http://www.cvut.cz Czech Technical University in Prague], [http://en.wikipedia.org/wiki/Czech_Republic Czech Republic] 
Room ''<to be defined>'' 

'''[http://geoinformatics.fsv.cvut.cz/gwiki/Where_you_can_find_us Location & Transportations]'''

Prague has an international [http://www.prg.aero/en/ airport] and is also reachable by train, bus or car.

== Accommodation and Costs ==

Participants should plan for the following costs:

* Travel to Prague, variable depending on where you come from
* Accommodation and meals
'''Please note''': The currency in Czech Republic is [http://en.wikipedia.org/wiki/Czech_crown crown] (CZK, koruna, Kč). 100 Czech crowns are about 4 Euros (see [http://www.cnb.cz/en/financial_markets/foreign_exchange_market/exchange_rate_fixing/daily.jsp current rates]).

'''[http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague Accommodation in Prague]'''

:* [http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague#Masarykova_Kolej_Hotel Masarykova Kolej Hotel]
:* [http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague#Hotel_DAP Hotel DAP]
:* [http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague#Hotel_Krystal Hotel Krystal]
:* [http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague#Pension_Hanspaulka Pension Hanspaulka]
:* [http://geoinformatics.fsv.cvut.cz/gwiki/Accommodation_in_Prague#Hotel_Silenzio Hotel Silenzio]
:* Special offer: ''sleeping for free in the kindergarten'' (30min by city urban mass transportation from the university campus, sleeping bag required, kitchen and WC available, no showers, in working days only available from 8 p.m. to 8 a.m.), contact [[User:Landa|Martin Landa]] for details
:* See also http://www.hotel.cz/praha-6/accommodation/

Please let us know your time of arrival and leaving, so we can book for the accommodations and organize the logistics.

'''TO BE DEFINED:''' We will cover as much as possible thanks to our sponsors.

== Weather and Common Item Prices ==

* In May the weather in Prague is usually quite warm ([http://www.prague-spot.com/climate 15 or more degrees by day])
* A espresso coffee is about 20 CZK (80 cents), a beer (half of liter) in a common pub is around 25 CZK (1 euro), can be more in special pubs. In Prague you can have a full meal (see [http://en.wikipedia.org/wiki/Czech_cuisine Czech cuisine]) for still 75 - 150 CZK (3 - 6 euros), but beware of tourist restaurants, the prize can easily rise. It's quite easy to find in Prague also Italian or Chinese restaurants.

== Agenda ==

'''Note:''' The program is generally open for your ideas. Please write an email to the [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developer list] to discuss your contribution.

=== Topics ===

==== Non-technical ====

* Discuss new sponsoring concept
* ...

==== Semi-technical ====

* Change manual to use Sphinx (see related {{trac|151}})
* Support translated manual pages (see related {{trac|846}})
* Design new project web site engine based on CMS
* ...

==== Technical ====

* backport Makefile system from GRASS 7 to GRASS 6
* Improve {{cmd|g.extension}} (enable to use prepared winGRASS Addon binaries)
* Define new [[GRASS repository layout proposal|toolbox concept]]
* Discussion and implementation time frame of temporal GIS capabilities in GRASS [[Time_series_development]]
* Discussion about a new parser interface for better command line, GUI and WPS support. Discussion started here: http://trac.osgeo.org/grass/ticket/1031
* Improve [[WPS]] support
* Discuss improvements in GRASS 7 vector engine (OGR support, lightweight topology structures, better 3D support)
* Discuss fundamental changes in raster and vector engine for GRASS 8
* ...

;Discussion on ML
* http://lists.osgeo.org/pipermail/grass-user/2011-March/059830.html

== Participation ==

We are planning for attendance of 20/30 people (i.e., hacking places) but of course you are welcome to join us and bring new ideas with you, as more places are available. Please add your name here or contact [[User:Landa|Martin Landa]] <tt><landa.martin at gmail.com></tt>:

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;"
|width=50px|'''No'''
|width=150px|'''Participant '''
|width=100px|'''Arrival'''
|width=100px|'''Departure'''
|'''Topic'''
|width=75px|'''T-Shirt'''
|'''Notes'''
|-
|1
|[[User:Landa|Martin Landa]]
| May 20
| May 25
|Toolbox concept, vector engine in GRASS 7, wxGUI
| M
|
|-
|2
|[[User:Neteler|Markus Neteler]]
|
|
|
|
|
|-
|3
|[[User:Lucadelu|Luca Delucchi]]
|
|
|New toolbox concept,translation
|
|
|-
|4
|[[User:RobertSzczepanek|Robert Szczepanek]]
|
|
|wxGUI, hydrological toolbox, translation
|
|
|-
|5
|[[User:madi|Margherita Di Leo]]
|
|
|[http://grass.osgeo.org/devel/i18n.php Translation] , python api
|
|
|-
|6
|[[User:annalisapg|Annalisa Minelli]]
|
|
|[http://grass.osgeo.org/devel/i18n.php Translation], python api
|
|
|-
|7
|[[User:AnneGhisla|Anne Ghisla]]
|
|
|wxGUI development, v.krige
|
|to be confirmed (but 80% sure)
|-
|8
|[[User:Afrigeri|Alessandro Frigeri]]
|
|
| Planetary SRS in GRASS GIS - OGC W*S tweakings for IAU GCS
|
|
|-
|9
|[[User:huhabla|Sören Gebbert]]
| May 20
| May 23
|Time series development, Web Processing Service support, wps-grass-bridge, New parser interface, vtk-grass-bridge
| L
|
|-
|-
|10
|[[User:MilenaN|Milena Nowotarska]]
|
|
|wxGUI, translation
|
|
|-
|11
|[[User:helena|Helena Mitasova]]
|
|
|wxnviz, v.vol.rst, r3 and time series, toolbox concept
|S
|
|-
|''add yourself here...''
|
|
|
|
|
|-
|}

== Individual Preparation ==

* Bring your own computer
* Install subversion and the compiler tools, and come with a working GRASS development environment if possible.


== FAQ ==

* ''Is the GRASS Community Sprint just a coding event?''
** It is mainly a coding and documentation event. It is a working session for people who are already participants in the GRASS project and/or are committed to improving the GRASS project.
** On demand we can do some presentations of current working GRASS implementation and new upcoming features to spread the idea of Open Source GIS software
* ''Is the GRASS Community Sprint for developers only?''
** No: anybody can help, with testing, checking out bugs and fixes, documentation and more.
* ''Where can I get help and more information about the community sprint?''
** Contact [[User:Landa|Martin Landa]] <tt><landa.martin at gmail.com></tt>

[[Category: Workshops]]

GRASS SoC Ideas 2011

2011-03-30T21:51:10Z

⚠️Helena: /* wxGUI */

[[Image:gsoc_2011_logo.png|350px|right]]
__TOC__
== About ==

This is the GRASS page for [http://wiki.osgeo.org/index.php/Google_Summer_of_Code Google Summer of Code] 2011. Here we will list project ideas and and other information related to the GRASS GSoC projects.

* [http://code.google.com/soc/ Official Google Summer of Code 2011 homepage]
* [http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2011 OSGeo SoC 2011 homepage]

Promotion:
* OSGeo Flyer at http://svn.osgeo.org/osgeo/marketing/flyer/google_summer_of_code/OSGeo_GSoC_2011.pdf
* Videos at http://code.google.com/p/google-summer-of-code/wiki/Videos
* More Flyers at http://code.google.com/p/google-summer-of-code/wiki/GsocFlyers

== Timeline ==

See [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2011/timeline GSoC timeline]

* {{Done}} Mentoring organization applications open (March 11)

* {{Done}} Accepted mentoring organizations announced (March 18)

* {{Done}} Interested students should initiate preliminary discussions with projects (March 18-27)

* '''Student applications open (March 28)'''

* Deadline for student's applications (April 8)
: Registering your application early (before the deadline) allows us to give you feedback for revisions before the final deadline, enhancing your proposal and thus giving you a better chance of success.

* Mentor assignments and application reviews deadline (April 22)

* Accepted proposals announced (April 25)

* Community bonding time (getting to know the students)

* Work Begins (May 23)

* Midterm evaluation (July 11-15)

* Pencils down! (August 15)

* Final evaluations submitted to Google (August 22)

* Final results of GSoC 2011 announced (August 29)

* Students can begin submitting required code samples to Google (August 30)

== Required Steps ==

* List ideas

* Assign Mentors to Ideas

* Notify OSGeo

* Mentors evaluate student applications

* Accepted students announced

* Students subscribe to the [http://lists.osgeo.org/mailman/listinfo/grass-dev grass-dev mailing list] and introduce themselves

* Mentor will create directory structure in the [http://trac.osgeo.org/grass/browser/grass-addons GRASS add-ons SVN] for projects and setup access for students
** Students must read and post agreement to [http://grass.osgeo.org/programming7/rfc2_psc.html RFC2] to the [http://lists.osgeo.org/mailman/listinfo/grass-psc grass-psc mailing list] to gain SVN access
** Create a Wiki page for each accepted project, to be used as a progress reporting tool

* Coding begins...

* Students and mentors: Complete the Mid-term survey

* Final commit and packaging for Google

== Ideas ==

* '''Also review ideas from [[GRASS SoC Ideas 2007#Ideas|2007]], [[GRASS SoC Ideas 2008#Ideas|2008]], [[GRASS SoC Ideas 2009#Ideas|2009]], and [[GRASS SoC Ideas 2010#Ideas|2010]] which are still open'''.
* Project ideas of your own are also most welcome.

=== wxGUI ===

# 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]].
#:<center>
#:[[Image:Wxgui_current.png|300px|thumb|left|Current wxGUI layout with detached window components]]
[[Image:Wxgui_proposal.png|300px|thumb|center|Proposal for wxGUI layout modification (Recomposition of existing toolbars, mapview and menus)]]
#:</center>
# Add '''WMS and/or TiledMapService and/or WMS-T layer support''' for wxGUI. Tiles/WMS images should not be stored as GRASS rasters but only used for displaying purposes (i.e. stored in temp folder). Such tool should provide user-friendly setting choices based on service GetCapabilities response.
# Develop a GUI module in wxPython for '''creating animations''' from multiple maps and saving animation outputs to animated GIF, MOV, or MPEG files. See existing modules {{cmd|xganim}}, {{cmd|r.out.mpeg}}, [[NVIZ]]'s animation tools, and the [[Movies]] creation wiki page. (co-mentor Helena Mitasova).
'''Willing to Mentor:''' [[User:Landa|Martin Landa]], [[User:MarisN|Maris Nartiss]], (''your name here'')

=== Raster ===

# 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 OpenMP is required.
# r.in.modis a module to import MODIS products. It will be able to download tile/s and import it/them. It will create also the mosaic from original MODIS tiles and import it. (Proposed by [[User:lucadelu|lucadelu]] with [[User:Neteler|MarkusN]] like mentor)
# ''Your idea here''

'''Willing to Mentor:''' (''your name here'')

=== Vector ===

# Add '''[[OpenMP]] parallelization''' where appropriate, for example, {{cmd|v.surf.rst}} and {{cmd|v.vol.rst}} ''(co-mentor Helena Mitasova)'' . See above idea in the [[GRASS SoC Ideas 2011#Raster|Raster section]].
# Better '''support for wrap-around at 180 longitude''': Currently the raster engine is pretty good at wrapping data over 180 longitude. The vector data isn't, but it should be. This is a great task if by the end of the summer you'd like to be familiar with the implementation method of an entire vector stack of a fully featured modern GIS.
# 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).

'''Willing to Mentor:''' [[User:Landa|Martin Landa]], (''your name here'')

=== Imagery ===

# GRASS's imagery modules (for satellite, scanned maps, and orthophotos) act as enhanced raster modules. In GRASS 5 and 6 they were mostly implemented using interactive X-monitors which are not available in MS Windows and so are removed in the new cross-platform code of GRASS 7.
#* We need someone willing to '''port the old modules to work with GRASS 7''', including writing new '''wxPython GUI frontends''' to a number of existing tools and updating the imagery libraries to current raster library standards.
#* In addition, there are a number of '''improved/automated georectification tools''' which have not been merged into GRASS 5/6 which it would be nice to have updated and merged into the main code.
# Implement '''[[OpenMP]] (multithreading)''' as much as possible (where appropriate)
# ''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.

'''Willing to Mentor:''' (''your name here'')

=== 3D visualization ===

# Optimize OGSF (and NVIZ/wxNVIZ) to '''display large 3D point clouds with uninterupted tought speed'''. OGSF + (wx)NVIZ should be able to rotate point cloud (i.e. LiDAR dataset) with 4 millions of points on medium hardware (i.e. 2GHz CPU with 2Gb RAM and GPU with hardware transform and lighting support and dedicated video RAM) with response time not greater than 1.0 second.
# Design and implement '''text displaying and styling in OGSF library''' and it's front-ends (NVIZ, [[wxNVIZ]]). Solution should be user configurable (fonts, colors, effects etc.) and multilanguage friendly.
# Design and implement user-provided '''symbol support in OGSF library''' and it's front-ends (NVIZ, [[wxNVIZ]]). Solution should support GRASS symbols, SVG, and/or simple EPS symbols.
# Add/fix missing features to [[wxNVIZ]] (lighting, robust handling of z-exageration and viewing position including latlong data, cutting planes, multiattribute 3D points, decorations: scale, north, legend, text, isosurfaces and slicing)
# Drape multiple color maps over topography (equivalent to running r.patch or r.composite and draping the result; second raster is currently supported as transparency).
'''Willing to Mentor:''' [[User:Landa|Martin Landa]] (for 2), co-mentor for 1 and 4: Helena Mitasova, (''your name here'')

=== Volume modeling ===

# implement color management for 3D rasters : '''r3.colors'''
# develop '''r3.flow''' for computing 3D flow lines and 3D flow accumulation from 3D rasters
# enhance volume interpolation module '''{{cmd|v.vol.rst}}''' for handling of data in space-time cube, including computation of gradients and hypercurvatures

'''Willing to Mentor:''' co-mentor Helena Mitasova, (''your name here'')

=== Other ===

# 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 '''sophisticated Python scripting interface''' for GRASS based on [http://grass.osgeo.org/programming7/pythonlib.html GRASS Python Scripting Library]
# ''Your idea here''

'''Willing to Mentor:''' (''your name here'')

== Guidelines for Students ==

How do you maximize your chances of getting picked? First read the [http://code.google.com/p/google-summer-of-code/wiki/AdviceforStudents Google SoC FAQ]. Then talk to us about your idea. Try emailing our [http://lists.osgeo.org/mailman/listinfo/grass-dev dev-mailing list], or come and talk to us in [[IRC]] (#grass). You can also reach the mentors directly by emailing:
* [http://lists.osgeo.org/mailman/listinfo/soc The OSGeo SoC mailing list]
* Wolf Bergenheim (<tt>wolf+grass at bergenheim.net</tt>)

=== Getting started with GRASS coding ===

* The source code is maintained in a [http://trac.osgeo.org/grass/browser/grass/trunk SVN server] which is easy to browse
: Please review the [http://svn.osgeo.org/grass/grass/trunk/SUBMITTING SUBMITTING] files there for our coding standards.

* There is lots of good info at the [http://trac.osgeo.org/grass/wiki GRASS Developer's wiki]
: See also the [[Development|development section]] of the GRASS user's wiki

== Accepted Ideas ==

* ''tbd''

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

GRASS SoC Ideas 2011

2011-03-30T21:47:48Z

⚠️Helena: /* 3D visualization */

[[Image:gsoc_2011_logo.png|350px|right]]
__TOC__
== About ==

This is the GRASS page for [http://wiki.osgeo.org/index.php/Google_Summer_of_Code Google Summer of Code] 2011. Here we will list project ideas and and other information related to the GRASS GSoC projects.

* [http://code.google.com/soc/ Official Google Summer of Code 2011 homepage]
* [http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2011 OSGeo SoC 2011 homepage]

Promotion:
* OSGeo Flyer at http://svn.osgeo.org/osgeo/marketing/flyer/google_summer_of_code/OSGeo_GSoC_2011.pdf
* Videos at http://code.google.com/p/google-summer-of-code/wiki/Videos
* More Flyers at http://code.google.com/p/google-summer-of-code/wiki/GsocFlyers

== Timeline ==

See [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2011/timeline GSoC timeline]

* {{Done}} Mentoring organization applications open (March 11)

* {{Done}} Accepted mentoring organizations announced (March 18)

* {{Done}} Interested students should initiate preliminary discussions with projects (March 18-27)

* '''Student applications open (March 28)'''

* Deadline for student's applications (April 8)
: Registering your application early (before the deadline) allows us to give you feedback for revisions before the final deadline, enhancing your proposal and thus giving you a better chance of success.

* Mentor assignments and application reviews deadline (April 22)

* Accepted proposals announced (April 25)

* Community bonding time (getting to know the students)

* Work Begins (May 23)

* Midterm evaluation (July 11-15)

* Pencils down! (August 15)

* Final evaluations submitted to Google (August 22)

* Final results of GSoC 2011 announced (August 29)

* Students can begin submitting required code samples to Google (August 30)

== Required Steps ==

* List ideas

* Assign Mentors to Ideas

* Notify OSGeo

* Mentors evaluate student applications

* Accepted students announced

* Students subscribe to the [http://lists.osgeo.org/mailman/listinfo/grass-dev grass-dev mailing list] and introduce themselves

* Mentor will create directory structure in the [http://trac.osgeo.org/grass/browser/grass-addons GRASS add-ons SVN] for projects and setup access for students
** Students must read and post agreement to [http://grass.osgeo.org/programming7/rfc2_psc.html RFC2] to the [http://lists.osgeo.org/mailman/listinfo/grass-psc grass-psc mailing list] to gain SVN access
** Create a Wiki page for each accepted project, to be used as a progress reporting tool

* Coding begins...

* Students and mentors: Complete the Mid-term survey

* Final commit and packaging for Google

== Ideas ==

* '''Also review ideas from [[GRASS SoC Ideas 2007#Ideas|2007]], [[GRASS SoC Ideas 2008#Ideas|2008]], [[GRASS SoC Ideas 2009#Ideas|2009]], and [[GRASS SoC Ideas 2010#Ideas|2010]] which are still open'''.
* Project ideas of your own are also most welcome.

=== wxGUI ===

# 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]].
#:<center>
#:[[Image:Wxgui_current.png|400px|thumb|left|Current wxGUI layout with detached window components]]
[[Image:Wxgui_proposal.png|400px|thumb|center|Proposal for wxGUI layout modification (Recomposition of existing toolbars, mapview and menus)]]
#:</center>
# Add '''WMS and/or TiledMapService and/or WMS-T layer support''' for wxGUI. Tiles/WMS images should not be stored as GRASS rasters but only used for displaying purposes (i.e. stored in temp folder). Such tool should provide user-friendly setting choices based on service GetCapabilities response.
# Develop a GUI module in wxPython for '''creating animations''' from multiple maps and saving animation outputs to animated GIF, MOV, or MPEG files. See existing modules {{cmd|xganim}}, {{cmd|r.out.mpeg}}, [[NVIZ]]'s animation tools, and the [[Movies]] creation wiki page. (co-mentor Helena Mitasova).
'''Willing to Mentor:''' [[User:Landa|Martin Landa]], [[User:MarisN|Maris Nartiss]], (''your name here'')

=== Raster ===

# 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 OpenMP is required.
# r.in.modis a module to import MODIS products. It will be able to download tile/s and import it/them. It will create also the mosaic from original MODIS tiles and import it. (Proposed by [[User:lucadelu|lucadelu]] with [[User:Neteler|MarkusN]] like mentor)
# ''Your idea here''

'''Willing to Mentor:''' (''your name here'')

=== Vector ===

# Add '''[[OpenMP]] parallelization''' where appropriate, for example, {{cmd|v.surf.rst}} and {{cmd|v.vol.rst}} ''(co-mentor Helena Mitasova)'' . See above idea in the [[GRASS SoC Ideas 2011#Raster|Raster section]].
# Better '''support for wrap-around at 180 longitude''': Currently the raster engine is pretty good at wrapping data over 180 longitude. The vector data isn't, but it should be. This is a great task if by the end of the summer you'd like to be familiar with the implementation method of an entire vector stack of a fully featured modern GIS.
# 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).

'''Willing to Mentor:''' [[User:Landa|Martin Landa]], (''your name here'')

=== Imagery ===

# GRASS's imagery modules (for satellite, scanned maps, and orthophotos) act as enhanced raster modules. In GRASS 5 and 6 they were mostly implemented using interactive X-monitors which are not available in MS Windows and so are removed in the new cross-platform code of GRASS 7.
#* We need someone willing to '''port the old modules to work with GRASS 7''', including writing new '''wxPython GUI frontends''' to a number of existing tools and updating the imagery libraries to current raster library standards.
#* In addition, there are a number of '''improved/automated georectification tools''' which have not been merged into GRASS 5/6 which it would be nice to have updated and merged into the main code.
# Implement '''[[OpenMP]] (multithreading)''' as much as possible (where appropriate)
# ''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.

'''Willing to Mentor:''' (''your name here'')

=== 3D visualization ===

# Optimize OGSF (and NVIZ/wxNVIZ) to '''display large 3D point clouds with uninterupted tought speed'''. OGSF + (wx)NVIZ should be able to rotate point cloud (i.e. LiDAR dataset) with 4 millions of points on medium hardware (i.e. 2GHz CPU with 2Gb RAM and GPU with hardware transform and lighting support and dedicated video RAM) with response time not greater than 1.0 second.
# Design and implement '''text displaying and styling in OGSF library''' and it's front-ends (NVIZ, [[wxNVIZ]]). Solution should be user configurable (fonts, colors, effects etc.) and multilanguage friendly.
# Design and implement user-provided '''symbol support in OGSF library''' and it's front-ends (NVIZ, [[wxNVIZ]]). Solution should support GRASS symbols, SVG, and/or simple EPS symbols.
# Add/fix missing features to [[wxNVIZ]] (lighting, robust handling of z-exageration and viewing position including latlong data, cutting planes, multiattribute 3D points, decorations: scale, north, legend, text, isosurfaces and slicing)
# Drape multiple color maps over topography (equivalent to running r.patch or r.composite and draping the result; second raster is currently supported as transparency).
'''Willing to Mentor:''' [[User:Landa|Martin Landa]] (for 2), co-mentor for 1 and 4: Helena Mitasova, (''your name here'')

=== Volume modeling ===

# implement color management for 3D rasters : '''r3.colors'''
# develop '''r3.flow''' for computing 3D flow lines and 3D flow accumulation from 3D rasters
# enhance volume interpolation module '''{{cmd|v.vol.rst}}''' for handling of data in space-time cube, including computation of gradients and hypercurvatures

'''Willing to Mentor:''' co-mentor Helena Mitasova, (''your name here'')

=== Other ===

# 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 '''sophisticated Python scripting interface''' for GRASS based on [http://grass.osgeo.org/programming7/pythonlib.html GRASS Python Scripting Library]
# ''Your idea here''

'''Willing to Mentor:''' (''your name here'')

== Guidelines for Students ==

How do you maximize your chances of getting picked? First read the [http://code.google.com/p/google-summer-of-code/wiki/AdviceforStudents Google SoC FAQ]. Then talk to us about your idea. Try emailing our [http://lists.osgeo.org/mailman/listinfo/grass-dev dev-mailing list], or come and talk to us in [[IRC]] (#grass). You can also reach the mentors directly by emailing:
* [http://lists.osgeo.org/mailman/listinfo/soc The OSGeo SoC mailing list]
* Wolf Bergenheim (<tt>wolf+grass at bergenheim.net</tt>)

=== Getting started with GRASS coding ===

* The source code is maintained in a [http://trac.osgeo.org/grass/browser/grass/trunk SVN server] which is easy to browse
: Please review the [http://svn.osgeo.org/grass/grass/trunk/SUBMITTING SUBMITTING] files there for our coding standards.

* There is lots of good info at the [http://trac.osgeo.org/grass/wiki GRASS Developer's wiki]
: See also the [[Development|development section]] of the GRASS user's wiki

== Accepted Ideas ==

* ''tbd''

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

GRASS SoC Ideas 2011

2011-03-27T03:23:29Z

⚠️Helena: /* wxGUI */

{{ToModify}}
[[Image:gsoc_2011_logo.png|350px|right]]
__TOC__
== About ==

This is the GRASS page for [http://wiki.osgeo.org/index.php/Google_Summer_of_Code Google Summer of Code] 2011. Here we will list project ideas and and other information related to the GRASS GSoC projects.

* [http://code.google.com/soc/ Official Google Summer of Code 2011 homepage]
* [http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2011 OSGeo SoC 2011 homepage]

Promotion:
* OSGeo Flyer at http://svn.osgeo.org/osgeo/marketing/flyer/google_summer_of_code/OSGeo_GSoC_2011.pdf
* Videos at http://code.google.com/p/google-summer-of-code/wiki/Videos
* More Flyers at http://code.google.com/p/google-summer-of-code/wiki/GsocFlyers

== Timeline ==

See [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2011/timeline GSoC timeline]

* {{Done}} Mentoring organization applications open (March 11)

* {{Done}} Accepted mentoring organizations announced (March 18)

* '''Interested students should initiate preliminary discussions with projects (March 18-27)'''

* Student applications open (March 28)

* Deadline for student's applications (April 8)
: Registering your application early (before the deadline) allows us to give you feedback for revisions before the final deadline, enhancing your proposal and thus giving you a better chance of success.

* Mentor assignments and application reviews deadline (April 22)

* Accepted proposals announced (April 25)

* Community bonding time (getting to know the students)

* Work Begins (May 23)

* Midterm evaluation (July 11-15)

* Pencils down! (August 15)

* Final evaluations submitted to Google (August 22)

* Final results of GSoC 2011 announced (August 29)

* Students can begin submitting required code samples to Google (August 30)

== Required Steps ==

* List ideas

* Assign Mentors to Ideas

* Notify OSGeo

* Mentors evaluate student applications

* Accepted students announced

* Students subscribe to the [http://lists.osgeo.org/mailman/listinfo/grass-dev grass-dev mailing list] and introduce themselves

* Create directory structure in the [http://trac.osgeo.org/grass/browser/grass-addons GRASS add-ons SVN] for projects and setup access for students
** Students must read and post agreement to [http://grass.osgeo.org/programming7/rfc2_psc.html RFC2] to the [http://lists.osgeo.org/mailman/listinfo/grass-psc grass-psc mailing list] to gain SVN access
** Create a Wiki page for each accepted project, to be used as a progress reporting tool

* Coding begins...

* Students and mentors: Complete the Mid-term survey

* Final commit and packaging for Google

== Ideas ==

* '''Also review ideas from [[GRASS SoC Ideas 2007#Ideas|2007]], [[GRASS SoC Ideas 2008#Ideas|2008]], [[GRASS SoC Ideas 2009#Ideas|2009]], and [[GRASS SoC Ideas 2010#Ideas|2010]] which are still open'''.
* Project ideas of your own are also most welcome.

=== wxGUI ===

# 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]].
#:<center>
#:[[Image:Wxgui_current.png|400px|thumb|left|Current wxGUI layout with detached window components]]
[[Image:Wxgui_proposal.png|400px|thumb|center|Proposal for wxGUI layout modification (Recomposition of existing toolbars, mapview and menus)]]
#:</center>
# Add '''WMS and/or TiledMapService and/or WMS-T layer support''' for wxGUI. Tiles/WMS images should not be stored as GRASS rasters but only used for displaying purposes (i.e. stored in temp folder). Such tool should provide user-friendly setting choices based on service GetCapabilities response.
# Develop a GUI module in wxPython for creating animations from multiple maps and saving animation outputs to animated GIF, MOV, or MPEG files. See existing modules xganim, r.out.mpeg, and nviz's animation tools (co-mentor Helena Mitasova).
'''Willing to Mentor:''' [[User:Landa|Martin Landa]], [[User:MarisN|Maris Nartiss]], (''your name here'')

=== Raster ===

# ''Your idea here''

'''Willing to Mentor:''' (''your name here'')

=== Vector ===

# Add '''[[OpenMP]] parallelization''' where appropriate, for example, {{cmd|v.surf.rst}} and {{cmd|v.vol.rst}} ''(co-mentor Helena Mitasova)'' . See above idea in the [[GRASS SoC Ideas 2011#Raster|Raster section]].
# Better '''support for wrap-around at 180 longitude''': Currently the raster engine is pretty good at wrapping data over 180 longitude. The vector data isn't, but it should be. This is a great task if by the end of the summer you'd like to be familiar with the implementation method of an entire vector stack of a fully featured modern GIS.
# Add '''break lines support to interpolation modules''' (v.surf.rst, v.surf.idw, v.surf.bspline). Current implementations provide no support to specify locations of clifs 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.
# Speed up wxGUI handling and 2D display of large point clouds (several million points) ''

'''Willing to Mentor:''' [[User:Landa|Martin Landa]], (''your name here'')

=== Imagery ===

# GRASS's imagery modules (for satellite, scanned maps, and orthophotos) act as enhanced raster modules. In GRASS 5 and 6 they were mostly implemented using interactive X-monitors which are not available in MS Windows and so are removed in the new cross-platform code of GRASS 7.
#* We need someone willing to port the old modules to work with GRASS 7, including writing new wxPython GUI frontends to a number of existing tools and updating the imagery libraries to current raster library standards.
#* In addition, there are a number of improved/automated georectification tools which have not been merged into GRASS 5/6 which it would be nice to have updated and merged into the main code.
# Implement [[OpenMP]] (multithreading) as much as possible
# ''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.

'''Willing to Mentor:''' (''your name here'')

=== 3D visualization ===

# Optimize OGSF (and NVIZ/wxNVIZ) to '''display large 3D point clouds with uninterupted tought speed'''. OGSF + (wx)NVIZ should be able to rotate point cloud (i.e. LiDAR dataset) with 4 millions of points on medium hardware (i.e. 2GHz CPU with 2Gb RAM and GPU with hardware transform and lighting support and dedicated video RAM) with response time not greater than 1.0 second.
# Design and implement '''text displaying and styling in OGSF library''' and it's front-ends (NVIZ, [[wxNVIZ]]). Solution should be user configurable (fonts, colors, effects etc.) and multilanguage friendly.
# Design and implement user-provided '''symbol support in OGSF library''' and it's front-ends (NVIZ, [[wxNVIZ]]). Solution should support GRASS symbols, SVG, and/or simple EPS symbols.
# Add/fix missing features to [[wxNVIZ]] (lighting, robust handling of z-exageration and viewing position including latlong data, cutting planes, multiattribute 3D points, decorations: scale, north, legend, text, isosurfaces and slicing)
'''Willing to Mentor:''' (''your name here, co-mentor for 1 and 4: Helena Mitasova'')

=== Volume modeling ===

# implement color management for 3D rasters : '''r3.colors'''
# develop '''r3.flow''' for computing 3D flow lines and 3D flow accumulation from 3D rasters
# enhance volume interpolation module '''v.vol.rst''' for handling of data in space-time cube, including computation of gradients and hypercurvatures

'''Willing to Mentor:''' (''your name here, co-mentor Helena Mitasova'')

=== Other ===

# 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.
# Design '''sophisticated Python scripting interface''' for GRASS based on [http://grass.osgeo.org/programming7/pythonlib.html GRASS Python Scripting Library]
# ''Your idea here''

'''Willing to Mentor:''' (''your name here'')

== Guidelines for Students ==

How do you maximize your chances of getting picked? First read the [http://code.google.com/p/google-summer-of-code/wiki/AdviceforStudents Google SoC FAQ]. Then talk to us about your idea. Try emailing our [http://lists.osgeo.org/mailman/listinfo/grass-dev dev-mailing list], or come and talk to us in [[IRC]] (#grass). You can also reach the mentors directly by emailing:
* [http://lists.osgeo.org/mailman/listinfo/soc The OSGeo SoC mailing list]
* Wolf Bergenheim (<tt>wolf+grass at bergenheim.net</tt>)

=== Getting started with GRASS coding ===

* The source code is maintained in a [http://trac.osgeo.org/grass/browser/grass/trunk SVN server] which is easy to browse
: Please review the [http://svn.osgeo.org/grass/grass/trunk/SUBMITTING SUBMITTING] files there for our coding standards.

* There is lots of good info at the [http://trac.osgeo.org/grass/wiki GRASS Developer's wiki]
: See also the [[Development|development section]] of the GRASS user's wiki

== Accepted Ideas ==

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

GRASS SoC Ideas 2011

2011-03-27T03:19:10Z

⚠️Helena: /* 3D visualization */

{{ToModify}}
[[Image:gsoc_2011_logo.png|350px|right]]
__TOC__
== About ==

This is the GRASS page for [http://wiki.osgeo.org/index.php/Google_Summer_of_Code Google Summer of Code] 2011. Here we will list project ideas and and other information related to the GRASS GSoC projects.

* [http://code.google.com/soc/ Official Google Summer of Code 2011 homepage]
* [http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2011 OSGeo SoC 2011 homepage]

Promotion:
* OSGeo Flyer at http://svn.osgeo.org/osgeo/marketing/flyer/google_summer_of_code/OSGeo_GSoC_2011.pdf
* Videos at http://code.google.com/p/google-summer-of-code/wiki/Videos
* More Flyers at http://code.google.com/p/google-summer-of-code/wiki/GsocFlyers

== Timeline ==

See [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2011/timeline GSoC timeline]

* {{Done}} Mentoring organization applications open (March 11)

* {{Done}} Accepted mentoring organizations announced (March 18)

* '''Interested students should initiate preliminary discussions with projects (March 18-27)'''

* Student applications open (March 28)

* Deadline for student's applications (April 8)
: Registering your application early (before the deadline) allows us to give you feedback for revisions before the final deadline, enhancing your proposal and thus giving you a better chance of success.

* Mentor assignments and application reviews deadline (April 22)

* Accepted proposals announced (April 25)

* Community bonding time (getting to know the students)

* Work Begins (May 23)

* Midterm evaluation (July 11-15)

* Pencils down! (August 15)

* Final evaluations submitted to Google (August 22)

* Final results of GSoC 2011 announced (August 29)

* Students can begin submitting required code samples to Google (August 30)

== Required Steps ==

* List ideas

* Assign Mentors to Ideas

* Notify OSGeo

* Mentors evaluate student applications

* Accepted students announced

* Students subscribe to the [http://lists.osgeo.org/mailman/listinfo/grass-dev grass-dev mailing list] and introduce themselves

* Create directory structure in the [http://trac.osgeo.org/grass/browser/grass-addons GRASS add-ons SVN] for projects and setup access for students
** Students must read and post agreement to [http://grass.osgeo.org/programming7/rfc2_psc.html RFC2] to the [http://lists.osgeo.org/mailman/listinfo/grass-psc grass-psc mailing list] to gain SVN access
** Create a Wiki page for each accepted project, to be used as a progress reporting tool

* Coding begins...

* Students and mentors: Complete the Mid-term survey

* Final commit and packaging for Google

== Ideas ==

* '''Also review ideas from [[GRASS SoC Ideas 2007#Ideas|2007]], [[GRASS SoC Ideas 2008#Ideas|2008]], [[GRASS SoC Ideas 2009#Ideas|2009]], and [[GRASS SoC Ideas 2010#Ideas|2010]] which are still open'''.
* Project ideas of your own are also most welcome.

=== wxGUI ===

# 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]].
#:<center>
#:[[Image:Wxgui_current.png|480px|thumb|center|Current wxGUI layout with detached window components]]
#:[[Image:Wxgui_proposal.png|480px|thumb|center|Proposal for wxGUI layout modification (Recomposition of existing toolbars, mapview and menus)]]
#:</center>
# Add '''WMS and/or TiledMapService and/or WMS-T layer support''' for wxGUI. Tiles/WMS images should not be stored as GRASS rasters but only used for displaying purposes (i.e. stored in temp folder). Such tool should provide user-friendly setting choices based on service GetCapabilities response.
# Develop a GUI module in wxPython for creating animations from multiple maps and saving animation outputs to animated GIF, MOV, or MPEG files. See existing modules xganim, r.out.mpeg, and nviz's animation tools (co-mentor Helena Mitasova).
'''Willing to Mentor:''' [[User:Landa|Martin Landa]], [[User:MarisN|Maris Nartiss]], (''your name here'')

=== Raster ===

# ''Your idea here''

'''Willing to Mentor:''' (''your name here'')

=== Vector ===

# Add '''[[OpenMP]] parallelization''' where appropriate, for example, {{cmd|v.surf.rst}} and {{cmd|v.vol.rst}} ''(co-mentor Helena Mitasova)'' . See above idea in the [[GRASS SoC Ideas 2011#Raster|Raster section]].
# Better '''support for wrap-around at 180 longitude''': Currently the raster engine is pretty good at wrapping data over 180 longitude. The vector data isn't, but it should be. This is a great task if by the end of the summer you'd like to be familiar with the implementation method of an entire vector stack of a fully featured modern GIS.
# Add '''break lines support to interpolation modules''' (v.surf.rst, v.surf.idw, v.surf.bspline). Current implementations provide no support to specify locations of clifs 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.
# Speed up wxGUI handling and 2D display of large point clouds (several million points) ''

'''Willing to Mentor:''' [[User:Landa|Martin Landa]], (''your name here'')

=== Imagery ===

# GRASS's imagery modules (for satellite, scanned maps, and orthophotos) act as enhanced raster modules. In GRASS 5 and 6 they were mostly implemented using interactive X-monitors which are not available in MS Windows and so are removed in the new cross-platform code of GRASS 7.
#* We need someone willing to port the old modules to work with GRASS 7, including writing new wxPython GUI frontends to a number of existing tools and updating the imagery libraries to current raster library standards.
#* In addition, there are a number of improved/automated georectification tools which have not been merged into GRASS 5/6 which it would be nice to have updated and merged into the main code.
# Implement [[OpenMP]] (multithreading) as much as possible
# ''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.

'''Willing to Mentor:''' (''your name here'')

=== 3D visualization ===

# Optimize OGSF (and NVIZ/wxNVIZ) to '''display large 3D point clouds with uninterupted tought speed'''. OGSF + (wx)NVIZ should be able to rotate point cloud (i.e. LiDAR dataset) with 4 millions of points on medium hardware (i.e. 2GHz CPU with 2Gb RAM and GPU with hardware transform and lighting support and dedicated video RAM) with response time not greater than 1.0 second.
# Design and implement '''text displaying and styling in OGSF library''' and it's front-ends (NVIZ, [[wxNVIZ]]). Solution should be user configurable (fonts, colors, effects etc.) and multilanguage friendly.
# Design and implement user-provided '''symbol support in OGSF library''' and it's front-ends (NVIZ, [[wxNVIZ]]). Solution should support GRASS symbols, SVG, and/or simple EPS symbols.
# Add/fix missing features to [[wxNVIZ]] (lighting, robust handling of z-exageration and viewing position including latlong data, cutting planes, multiattribute 3D points, decorations: scale, north, legend, text, isosurfaces and slicing)
'''Willing to Mentor:''' (''your name here, co-mentor for 1 and 4: Helena Mitasova'')

=== Volume modeling ===

# implement color management for 3D rasters : '''r3.colors'''
# develop '''r3.flow''' for computing 3D flow lines and 3D flow accumulation from 3D rasters
# enhance volume interpolation module '''v.vol.rst''' for handling of data in space-time cube, including computation of gradients and hypercurvatures

'''Willing to Mentor:''' (''your name here, co-mentor Helena Mitasova'')

=== Other ===

# 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.
# Design '''sophisticated Python scripting interface''' for GRASS based on [http://grass.osgeo.org/programming7/pythonlib.html GRASS Python Scripting Library]
# ''Your idea here''

'''Willing to Mentor:''' (''your name here'')

== Guidelines for Students ==

How do you maximize your chances of getting picked? First read the [http://code.google.com/p/google-summer-of-code/wiki/AdviceforStudents Google SoC FAQ]. Then talk to us about your idea. Try emailing our [http://lists.osgeo.org/mailman/listinfo/grass-dev dev-mailing list], or come and talk to us in [[IRC]] (#grass). You can also reach the mentors directly by emailing:
* [http://lists.osgeo.org/mailman/listinfo/soc The OSGeo SoC mailing list]
* Wolf Bergenheim (<tt>wolf+grass at bergenheim.net</tt>)

=== Getting started with GRASS coding ===

* The source code is maintained in a [http://trac.osgeo.org/grass/browser/grass/trunk SVN server] which is easy to browse
: Please review the [http://svn.osgeo.org/grass/grass/trunk/SUBMITTING SUBMITTING] files there for our coding standards.

* There is lots of good info at the [http://trac.osgeo.org/grass/wiki GRASS Developer's wiki]
: See also the [[Development|development section]] of the GRASS user's wiki

== Accepted Ideas ==

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

GRASS SoC Ideas 2011

2011-03-27T03:10:07Z

⚠️Helena: /* 3D visualization */

{{ToModify}}
[[Image:gsoc_2011_logo.png|350px|right]]
__TOC__
== About ==

This is the GRASS page for [http://wiki.osgeo.org/index.php/Google_Summer_of_Code Google Summer of Code] 2011. Here we will list project ideas and and other information related to the GRASS GSoC projects.

* [http://code.google.com/soc/ Official Google Summer of Code 2011 homepage]
* [http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2011 OSGeo SoC 2011 homepage]

Promotion:
* OSGeo Flyer at http://svn.osgeo.org/osgeo/marketing/flyer/google_summer_of_code/OSGeo_GSoC_2011.pdf
* Videos at http://code.google.com/p/google-summer-of-code/wiki/Videos
* More Flyers at http://code.google.com/p/google-summer-of-code/wiki/GsocFlyers

== Timeline ==

See [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2011/timeline GSoC timeline]

* {{Done}} Mentoring organization applications open (March 11)

* {{Done}} Accepted mentoring organizations announced (March 18)

* '''Interested students should initiate preliminary discussions with projects (March 18-27)'''

* Student applications open (March 28)

* Deadline for student's applications (April 8)
: Registering your application early (before the deadline) allows us to give you feedback for revisions before the final deadline, enhancing your proposal and thus giving you a better chance of success.

* Mentor assignments and application reviews deadline (April 22)

* Accepted proposals announced (April 25)

* Community bonding time (getting to know the students)

* Work Begins (May 23)

* Midterm evaluation (July 11-15)

* Pencils down! (August 15)

* Final evaluations submitted to Google (August 22)

* Final results of GSoC 2011 announced (August 29)

* Students can begin submitting required code samples to Google (August 30)

== Required Steps ==

* List ideas

* Assign Mentors to Ideas

* Notify OSGeo

* Mentors evaluate student applications

* Accepted students announced

* Students subscribe to the [http://lists.osgeo.org/mailman/listinfo/grass-dev grass-dev mailing list] and introduce themselves

* Create directory structure in the [http://trac.osgeo.org/grass/browser/grass-addons GRASS add-ons SVN] for projects and setup access for students
** Students must read and post agreement to [http://grass.osgeo.org/programming7/rfc2_psc.html RFC2] to the [http://lists.osgeo.org/mailman/listinfo/grass-psc grass-psc mailing list] to gain SVN access
** Create a Wiki page for each accepted project, to be used as a progress reporting tool

* Coding begins...

* Students and mentors: Complete the Mid-term survey

* Final commit and packaging for Google

== Ideas ==

* '''Also review ideas from [[GRASS SoC Ideas 2007#Ideas|2007]], [[GRASS SoC Ideas 2008#Ideas|2008]], [[GRASS SoC Ideas 2009#Ideas|2009]], and [[GRASS SoC Ideas 2010#Ideas|2010]] which are still open'''.
* Project ideas of your own are also most welcome.

=== wxGUI ===

# 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]].
#:<center>
#:[[Image:Wxgui_current.png|480px|thumb|center|Current wxGUI layout with detached window components]]
#:[[Image:Wxgui_proposal.png|480px|thumb|center|Proposal for wxGUI layout modification (Recomposition of existing toolbars, mapview and menus)]]
#:</center>
# Add '''WMS and/or TiledMapService and/or WMS-T layer support''' for wxGUI. Tiles/WMS images should not be stored as GRASS rasters but only used for displaying purposes (i.e. stored in temp folder). Such tool should provide user-friendly setting choices based on service GetCapabilities response.
# Develop a GUI module in wxPython for creating animations from multiple maps and saving animation outputs to animated GIF, MOV, or MPEG files. See existing modules xganim, r.out.mpeg, and nviz's animation tools (co-mentor Helena Mitasova).
'''Willing to Mentor:''' [[User:Landa|Martin Landa]], [[User:MarisN|Maris Nartiss]], (''your name here'')

=== Raster ===

# ''Your idea here''

'''Willing to Mentor:''' (''your name here'')

=== Vector ===

# Add '''[[OpenMP]] parallelization''' where appropriate, for example, {{cmd|v.surf.rst}} and {{cmd|v.vol.rst}} ''(co-mentor Helena Mitasova)'' . See above idea in the [[GRASS SoC Ideas 2011#Raster|Raster section]].
# Better '''support for wrap-around at 180 longitude''': Currently the raster engine is pretty good at wrapping data over 180 longitude. The vector data isn't, but it should be. This is a great task if by the end of the summer you'd like to be familiar with the implementation method of an entire vector stack of a fully featured modern GIS.
# Add '''break lines support to interpolation modules''' (v.surf.rst, v.surf.idw, v.surf.bspline). Current implementations provide no support to specify locations of clifs 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.
# Speed up wxGUI handling and 2D display of large point clouds (several million points) ''

'''Willing to Mentor:''' [[User:Landa|Martin Landa]], (''your name here'')

=== Imagery ===

# GRASS's imagery modules (for satellite, scanned maps, and orthophotos) act as enhanced raster modules. In GRASS 5 and 6 they were mostly implemented using interactive X-monitors which are not available in MS Windows and so are removed in the new cross-platform code of GRASS 7.
#* We need someone willing to port the old modules to work with GRASS 7, including writing new wxPython GUI frontends to a number of existing tools and updating the imagery libraries to current raster library standards.
#* In addition, there are a number of improved/automated georectification tools which have not been merged into GRASS 5/6 which it would be nice to have updated and merged into the main code.
# Implement [[OpenMP]] (multithreading) as much as possible
# ''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.

'''Willing to Mentor:''' (''your name here'')

=== 3D visualization ===

# Optimize OGSF (and NVIZ/wxNVIZ) to '''display large 3D point clouds with uninterupted tought speed'''. OGSF + (wx)NVIZ should be able to rotate point cloud (i.e. LiDAR dataset) with 4 millions of points on medium hardware (i.e. 2GHz CPU with 2Gb RAM and GPU with hardware transform and lighting support and dedicated video RAM) with response time not greater than 1.0 second.
# Design and implement '''text displaying and styling in OGSF library''' and it's front-ends (NVIZ, [[wxNVIZ]]). Solution should be user configurable (fonts, colors, effects etc.) and multilanguage friendly.
# Design and implement user-provided '''symbol support in OGSF library''' and it's front-ends (NVIZ, [[wxNVIZ]]). Solution should support GRASS symbols, SVG, and/or simple EPS symbols.
# Add/fix missing features to [[wxNVIZ]] (lighting, robust handling of z-exageration and viewing position including latlong data, cutting planes, multiattribute 3D points, decorations: scale, north, legend, text, isosurfaces and slicing)
'''Willing to Mentor:''' (''co-mentor for 1 and 4: Helena Mitasova'')

=== Other ===

# 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.
# Design '''sophisticated Python scripting interface''' for GRASS based on [http://grass.osgeo.org/programming7/pythonlib.html GRASS Python Scripting Library]
# ''Your idea here''

'''Willing to Mentor:''' (''your name here'')

== Guidelines for Students ==

How do you maximize your chances of getting picked? First read the [http://code.google.com/p/google-summer-of-code/wiki/AdviceforStudents Google SoC FAQ]. Then talk to us about your idea. Try emailing our [http://lists.osgeo.org/mailman/listinfo/grass-dev dev-mailing list], or come and talk to us in [[IRC]] (#grass). You can also reach the mentors directly by emailing:
* [http://lists.osgeo.org/mailman/listinfo/soc The OSGeo SoC mailing list]
* Wolf Bergenheim (<tt>wolf+grass at bergenheim.net</tt>)

=== Getting started with GRASS coding ===

* The source code is maintained in a [http://trac.osgeo.org/grass/browser/grass/trunk SVN server] which is easy to browse
: Please review the [http://svn.osgeo.org/grass/grass/trunk/SUBMITTING SUBMITTING] files there for our coding standards.

* There is lots of good info at the [http://trac.osgeo.org/grass/wiki GRASS Developer's wiki]
: See also the [[Development|development section]] of the GRASS user's wiki

== Accepted Ideas ==

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

GRASS SoC Ideas 2011

2011-03-27T03:07:14Z

⚠️Helena: /* 3D visualization */

{{ToModify}}
[[Image:gsoc_2011_logo.png|350px|right]]
__TOC__
== About ==

This is the GRASS page for [http://wiki.osgeo.org/index.php/Google_Summer_of_Code Google Summer of Code] 2011. Here we will list project ideas and and other information related to the GRASS GSoC projects.

* [http://code.google.com/soc/ Official Google Summer of Code 2011 homepage]
* [http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2011 OSGeo SoC 2011 homepage]

Promotion:
* OSGeo Flyer at http://svn.osgeo.org/osgeo/marketing/flyer/google_summer_of_code/OSGeo_GSoC_2011.pdf
* Videos at http://code.google.com/p/google-summer-of-code/wiki/Videos
* More Flyers at http://code.google.com/p/google-summer-of-code/wiki/GsocFlyers

== Timeline ==

See [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2011/timeline GSoC timeline]

* {{Done}} Mentoring organization applications open (March 11)

* {{Done}} Accepted mentoring organizations announced (March 18)

* '''Interested students should initiate preliminary discussions with projects (March 18-27)'''

* Student applications open (March 28)

* Deadline for student's applications (April 8)
: Registering your application early (before the deadline) allows us to give you feedback for revisions before the final deadline, enhancing your proposal and thus giving you a better chance of success.

* Mentor assignments and application reviews deadline (April 22)

* Accepted proposals announced (April 25)

* Community bonding time (getting to know the students)

* Work Begins (May 23)

* Midterm evaluation (July 11-15)

* Pencils down! (August 15)

* Final evaluations submitted to Google (August 22)

* Final results of GSoC 2011 announced (August 29)

* Students can begin submitting required code samples to Google (August 30)

== Required Steps ==

* List ideas

* Assign Mentors to Ideas

* Notify OSGeo

* Mentors evaluate student applications

* Accepted students announced

* Students subscribe to the [http://lists.osgeo.org/mailman/listinfo/grass-dev grass-dev mailing list] and introduce themselves

* Create directory structure in the [http://trac.osgeo.org/grass/browser/grass-addons GRASS add-ons SVN] for projects and setup access for students
** Students must read and post agreement to [http://grass.osgeo.org/programming7/rfc2_psc.html RFC2] to the [http://lists.osgeo.org/mailman/listinfo/grass-psc grass-psc mailing list] to gain SVN access
** Create a Wiki page for each accepted project, to be used as a progress reporting tool

* Coding begins...

* Students and mentors: Complete the Mid-term survey

* Final commit and packaging for Google

== Ideas ==

* '''Also review ideas from [[GRASS SoC Ideas 2007#Ideas|2007]], [[GRASS SoC Ideas 2008#Ideas|2008]], [[GRASS SoC Ideas 2009#Ideas|2009]], and [[GRASS SoC Ideas 2010#Ideas|2010]] which are still open'''.
* Project ideas of your own are also most welcome.

=== wxGUI ===

# 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]].
#:<center>
#:[[Image:Wxgui_current.png|480px|thumb|center|Current wxGUI layout with detached window components]]
#:[[Image:Wxgui_proposal.png|480px|thumb|center|Proposal for wxGUI layout modification (Recomposition of existing toolbars, mapview and menus)]]
#:</center>
# Add '''WMS and/or TiledMapService and/or WMS-T layer support''' for wxGUI. Tiles/WMS images should not be stored as GRASS rasters but only used for displaying purposes (i.e. stored in temp folder). Such tool should provide user-friendly setting choices based on service GetCapabilities response.
# Develop a GUI module in wxPython for creating animations from multiple maps and saving animation outputs to animated GIF, MOV, or MPEG files. See existing modules xganim, r.out.mpeg, and nviz's animation tools (co-mentor Helena Mitasova).
'''Willing to Mentor:''' [[User:Landa|Martin Landa]], [[User:MarisN|Maris Nartiss]], (''your name here'')

=== Raster ===

# ''Your idea here''

'''Willing to Mentor:''' (''your name here'')

=== Vector ===

# Add '''[[OpenMP]] parallelization''' where appropriate, for example, {{cmd|v.surf.rst}} and {{cmd|v.vol.rst}} ''(co-mentor Helena Mitasova)'' . See above idea in the [[GRASS SoC Ideas 2011#Raster|Raster section]].
# Better '''support for wrap-around at 180 longitude''': Currently the raster engine is pretty good at wrapping data over 180 longitude. The vector data isn't, but it should be. This is a great task if by the end of the summer you'd like to be familiar with the implementation method of an entire vector stack of a fully featured modern GIS.
# Add '''break lines support to interpolation modules''' (v.surf.rst, v.surf.idw, v.surf.bspline). Current implementations provide no support to specify locations of clifs 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.
# Speed up wxGUI handling and 2D display of large point clouds (several million points) ''

'''Willing to Mentor:''' [[User:Landa|Martin Landa]], (''your name here'')

=== Imagery ===

# GRASS's imagery modules (for satellite, scanned maps, and orthophotos) act as enhanced raster modules. In GRASS 5 and 6 they were mostly implemented using interactive X-monitors which are not available in MS Windows and so are removed in the new cross-platform code of GRASS 7.
#* We need someone willing to port the old modules to work with GRASS 7, including writing new wxPython GUI frontends to a number of existing tools and updating the imagery libraries to current raster library standards.
#* In addition, there are a number of improved/automated georectification tools which have not been merged into GRASS 5/6 which it would be nice to have updated and merged into the main code.
# Implement [[OpenMP]] (multithreading) as much as possible
# ''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.

'''Willing to Mentor:''' (''your name here'')

=== 3D visualization ===

# Optimize OGSF (and NVIZ/wxNVIZ) to '''display large 3D point clouds with uninterupted tought speed'''. OGSF + (wx)NVIZ should be able to rotate point cloud (i.e. LiDAR dataset) with 4 millions of points on medium hardware (i.e. 2GHz CPU with 2Gb RAM and GPU with hardware transform and lighting support and dedicated video RAM) with response time not greater than 1.0 second.
# Design and implement '''text displaying and styling in OGSF library''' and it's front-ends (NVIZ, [[wxNVIZ]]). Solution should be user configurable (fonts, colors, effects etc.) and multilanguage friendly.
# Design and implement user-provided '''symbol support in OGSF library''' and it's front-ends (NVIZ, [[wxNVIZ]]). Solution should support GRASS symbols, SVG, and/or simple EPS symbols.
# Add/fix missing features to [[wxNVIZ]] (lighting, robust handling of z-exageration and viewing position including latlong data, cutting planes, multiattribute 3D points, decorations: scale, north, legend, text, isosurfaces and slicing)
'''Willing to Mentor:''' (''your name here'')

=== Other ===

# 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.
# Design '''sophisticated Python scripting interface''' for GRASS based on [http://grass.osgeo.org/programming7/pythonlib.html GRASS Python Scripting Library]
# ''Your idea here''

'''Willing to Mentor:''' (''your name here'')

== Guidelines for Students ==

How do you maximize your chances of getting picked? First read the [http://code.google.com/p/google-summer-of-code/wiki/AdviceforStudents Google SoC FAQ]. Then talk to us about your idea. Try emailing our [http://lists.osgeo.org/mailman/listinfo/grass-dev dev-mailing list], or come and talk to us in [[IRC]] (#grass). You can also reach the mentors directly by emailing:
* [http://lists.osgeo.org/mailman/listinfo/soc The OSGeo SoC mailing list]
* Wolf Bergenheim (<tt>wolf+grass at bergenheim.net</tt>)

=== Getting started with GRASS coding ===

* The source code is maintained in a [http://trac.osgeo.org/grass/browser/grass/trunk SVN server] which is easy to browse
: Please review the [http://svn.osgeo.org/grass/grass/trunk/SUBMITTING SUBMITTING] files there for our coding standards.

* There is lots of good info at the [http://trac.osgeo.org/grass/wiki GRASS Developer's wiki]
: See also the [[Development|development section]] of the GRASS user's wiki

== Accepted Ideas ==

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

GRASS SoC Ideas 2011

2011-03-27T03:00:19Z

⚠️Helena: /* Vector */

{{ToModify}}
[[Image:gsoc_2011_logo.png|350px|right]]
__TOC__
== About ==

This is the GRASS page for [http://wiki.osgeo.org/index.php/Google_Summer_of_Code Google Summer of Code] 2011. Here we will list project ideas and and other information related to the GRASS GSoC projects.

* [http://code.google.com/soc/ Official Google Summer of Code 2011 homepage]
* [http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2011 OSGeo SoC 2011 homepage]

Promotion:
* OSGeo Flyer at http://svn.osgeo.org/osgeo/marketing/flyer/google_summer_of_code/OSGeo_GSoC_2011.pdf
* Videos at http://code.google.com/p/google-summer-of-code/wiki/Videos
* More Flyers at http://code.google.com/p/google-summer-of-code/wiki/GsocFlyers

== Timeline ==

See [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2011/timeline GSoC timeline]

* {{Done}} Mentoring organization applications open (March 11)

* {{Done}} Accepted mentoring organizations announced (March 18)

* '''Interested students should initiate preliminary discussions with projects (March 18-27)'''

* Student applications open (March 28)

* Deadline for student's applications (April 8)
: Registering your application early (before the deadline) allows us to give you feedback for revisions before the final deadline, enhancing your proposal and thus giving you a better chance of success.

* Mentor assignments and application reviews deadline (April 22)

* Accepted proposals announced (April 25)

* Community bonding time (getting to know the students)

* Work Begins (May 23)

* Midterm evaluation (July 11-15)

* Pencils down! (August 15)

* Final evaluations submitted to Google (August 22)

* Final results of GSoC 2011 announced (August 29)

* Students can begin submitting required code samples to Google (August 30)

== Required Steps ==

* List ideas

* Assign Mentors to Ideas

* Notify OSGeo

* Mentors evaluate student applications

* Accepted students announced

* Students subscribe to the [http://lists.osgeo.org/mailman/listinfo/grass-dev grass-dev mailing list] and introduce themselves

* Create directory structure in the [http://trac.osgeo.org/grass/browser/grass-addons GRASS add-ons SVN] for projects and setup access for students
** Students must read and post agreement to [http://grass.osgeo.org/programming7/rfc2_psc.html RFC2] to the [http://lists.osgeo.org/mailman/listinfo/grass-psc grass-psc mailing list] to gain SVN access
** Create a Wiki page for each accepted project, to be used as a progress reporting tool

* Coding begins...

* Students and mentors: Complete the Mid-term survey

* Final commit and packaging for Google

== Ideas ==

* '''Also review ideas from [[GRASS SoC Ideas 2007#Ideas|2007]], [[GRASS SoC Ideas 2008#Ideas|2008]], [[GRASS SoC Ideas 2009#Ideas|2009]], and [[GRASS SoC Ideas 2010#Ideas|2010]] which are still open'''.
* Project ideas of your own are also most welcome.

=== wxGUI ===

# 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]].
#:<center>
#:[[Image:Wxgui_current.png|480px|thumb|center|Current wxGUI layout with detached window components]]
#:[[Image:Wxgui_proposal.png|480px|thumb|center|Proposal for wxGUI layout modification (Recomposition of existing toolbars, mapview and menus)]]
#:</center>
# Add '''WMS and/or TiledMapService and/or WMS-T layer support''' for wxGUI. Tiles/WMS images should not be stored as GRASS rasters but only used for displaying purposes (i.e. stored in temp folder). Such tool should provide user-friendly setting choices based on service GetCapabilities response.
# Develop a GUI module in wxPython for creating animations from multiple maps and saving animation outputs to animated GIF, MOV, or MPEG files. See existing modules xganim, r.out.mpeg, and nviz's animation tools (co-mentor Helena Mitasova).
'''Willing to Mentor:''' [[User:Landa|Martin Landa]], [[User:MarisN|Maris Nartiss]], (''your name here'')

=== Raster ===

# ''Your idea here''

'''Willing to Mentor:''' (''your name here'')

=== Vector ===

# Add '''[[OpenMP]] parallelization''' where appropriate, for example, {{cmd|v.surf.rst}} and {{cmd|v.vol.rst}} ''(co-mentor Helena Mitasova)'' . See above idea in the [[GRASS SoC Ideas 2011#Raster|Raster section]].
# Better '''support for wrap-around at 180 longitude''': Currently the raster engine is pretty good at wrapping data over 180 longitude. The vector data isn't, but it should be. This is a great task if by the end of the summer you'd like to be familiar with the implementation method of an entire vector stack of a fully featured modern GIS.
# Add '''break lines support to interpolation modules''' (v.surf.rst, v.surf.idw, v.surf.bspline). Current implementations provide no support to specify locations of clifs 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.
# Speed up wxGUI handling and 2D display of large point clouds (several million points) ''

'''Willing to Mentor:''' [[User:Landa|Martin Landa]], (''your name here'')

=== Imagery ===

# GRASS's imagery modules (for satellite, scanned maps, and orthophotos) act as enhanced raster modules. In GRASS 5 and 6 they were mostly implemented using interactive X-monitors which are not available in MS Windows and so are removed in the new cross-platform code of GRASS 7.
#* We need someone willing to port the old modules to work with GRASS 7, including writing new wxPython GUI frontends to a number of existing tools and updating the imagery libraries to current raster library standards.
#* In addition, there are a number of improved/automated georectification tools which have not been merged into GRASS 5/6 which it would be nice to have updated and merged into the main code.
# Implement [[OpenMP]] (multithreading) as much as possible
# ''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.

'''Willing to Mentor:''' (''your name here'')

=== 3D visualization ===

# Optimize OGSF (and NVIZ/wxNVIZ) to '''display large 3D point clouds with uninterupted tought speed'''. OGSF + (wx)NVIZ should be able to rotate point cloud (i.e. LiDAR dataset) with 4 millions of points on medium hardware (i.e. 2GHz CPU with 2Gb RAM and GPU with hardware transform and lighting support and dedicated video RAM) with response time not greater than 1.0 second.
# Design and implement '''text displaying and styling in OGSF library''' and it's front-ends (NVIZ, [[wxNVIZ]]). Solution should be user configurable (fonts, colors, effects etc.) and multilanguage friendly.
# Design and implement user-provided '''symbol support in OGSF library''' and it's front-ends (NVIZ, [[wxNVIZ]]). Solution should support GRASS symbols, SVG, and/or simple EPS symbols.

'''Willing to Mentor:''' (''your name here'')

=== Other ===

# 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.
# Design '''sophisticated Python scripting interface''' for GRASS based on [http://grass.osgeo.org/programming7/pythonlib.html GRASS Python Scripting Library]
# ''Your idea here''

'''Willing to Mentor:''' (''your name here'')

== Guidelines for Students ==

How do you maximize your chances of getting picked? First read the [http://code.google.com/p/google-summer-of-code/wiki/AdviceforStudents Google SoC FAQ]. Then talk to us about your idea. Try emailing our [http://lists.osgeo.org/mailman/listinfo/grass-dev dev-mailing list], or come and talk to us in [[IRC]] (#grass). You can also reach the mentors directly by emailing:
* [http://lists.osgeo.org/mailman/listinfo/soc The OSGeo SoC mailing list]
* Wolf Bergenheim (<tt>wolf+grass at bergenheim.net</tt>)

=== Getting started with GRASS coding ===

* The source code is maintained in a [http://trac.osgeo.org/grass/browser/grass/trunk SVN server] which is easy to browse
: Please review the [http://svn.osgeo.org/grass/grass/trunk/SUBMITTING SUBMITTING] files there for our coding standards.

* There is lots of good info at the [http://trac.osgeo.org/grass/wiki GRASS Developer's wiki]
: See also the [[Development|development section]] of the GRASS user's wiki

== Accepted Ideas ==

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

GRASS SoC Ideas 2011

2011-03-27T02:48:19Z

⚠️Helena: /* 3D visualization */

{{ToModify}}
[[Image:gsoc_2011_logo.png|350px|right]]
__TOC__
== About ==

This is the GRASS page for [http://wiki.osgeo.org/index.php/Google_Summer_of_Code Google Summer of Code] 2011. Here we will list project ideas and and other information related to the GRASS GSoC projects.

* [http://code.google.com/soc/ Official Google Summer of Code 2011 homepage]
* [http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2011 OSGeo SoC 2011 homepage]

Promotion:
* OSGeo Flyer at http://svn.osgeo.org/osgeo/marketing/flyer/google_summer_of_code/OSGeo_GSoC_2011.pdf
* Videos at http://code.google.com/p/google-summer-of-code/wiki/Videos
* More Flyers at http://code.google.com/p/google-summer-of-code/wiki/GsocFlyers

== Timeline ==

See [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2011/timeline GSoC timeline]

* {{Done}} Mentoring organization applications open (March 11)

* {{Done}} Accepted mentoring organizations announced (March 18)

* '''Interested students should initiate preliminary discussions with projects (March 18-27)'''

* Student applications open (March 28)

* Deadline for student's applications (April 8)
: Registering your application early (before the deadline) allows us to give you feedback for revisions before the final deadline, enhancing your proposal and thus giving you a better chance of success.

* Mentor assignments and application reviews deadline (April 22)

* Accepted proposals announced (April 25)

* Community bonding time (getting to know the students)

* Work Begins (May 23)

* Midterm evaluation (July 11-15)

* Pencils down! (August 15)

* Final evaluations submitted to Google (August 22)

* Final results of GSoC 2011 announced (August 29)

* Students can begin submitting required code samples to Google (August 30)

== Required Steps ==

* List ideas

* Assign Mentors to Ideas

* Notify OSGeo

* Mentors evaluate student applications

* Accepted students announced

* Students subscribe to the [http://lists.osgeo.org/mailman/listinfo/grass-dev grass-dev mailing list] and introduce themselves

* Create directory structure in the [http://trac.osgeo.org/grass/browser/grass-addons GRASS add-ons SVN] for projects and setup access for students
** Students must read and post agreement to [http://grass.osgeo.org/programming7/rfc2_psc.html RFC2] to the [http://lists.osgeo.org/mailman/listinfo/grass-psc grass-psc mailing list] to gain SVN access
** Create a Wiki page for each accepted project, to be used as a progress reporting tool

* Coding begins...

* Students and mentors: Complete the Mid-term survey

* Final commit and packaging for Google

== Ideas ==

* '''Also review ideas from [[GRASS SoC Ideas 2007#Ideas|2007]], [[GRASS SoC Ideas 2008#Ideas|2008]], [[GRASS SoC Ideas 2009#Ideas|2009]], and [[GRASS SoC Ideas 2010#Ideas|2010]] which are still open'''.
* Project ideas of your own are also most welcome.

=== wxGUI ===

# 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]].
#:<center>
#:[[Image:Wxgui_current.png|480px|thumb|center|Current wxGUI layout with detached window components]]
#:[[Image:Wxgui_proposal.png|480px|thumb|center|Proposal for wxGUI layout modification (Recomposition of existing toolbars, mapview and menus)]]
#:</center>
# Add '''WMS and/or TiledMapService and/or WMS-T layer support''' for wxGUI. Tiles/WMS images should not be stored as GRASS rasters but only used for displaying purposes (i.e. stored in temp folder). Such tool should provide user-friendly setting choices based on service GetCapabilities response.
# Develop a GUI module in wxPython for creating animations from multiple maps and saving animation outputs to animated GIF, MOV, or MPEG files. See existing modules xganim, r.out.mpeg, and nviz's animation tools (co-mentor Helena Mitasova).
'''Willing to Mentor:''' [[User:Landa|Martin Landa]], [[User:MarisN|Maris Nartiss]], (''your name here'')

=== Raster ===

# ''Your idea here''

'''Willing to Mentor:''' (''your name here'')

=== Vector ===

# Add '''[[OpenMP]] parallelization''' where appropriate, for example, {{cmd|v.surf.rst}} and {{cmd|v.vol.rst}} ''(co-mentor Helena Mitasova)'' . See above idea in the [[GRASS SoC Ideas 2011#Raster|Raster section]].
# Better '''support for wrap-around at 180 longitude''': Currently the raster engine is pretty good at wrapping data over 180 longitude. The vector data isn't, but it should be. This is a great task if by the end of the summer you'd like to be familiar with the implementation method of an entire vector stack of a fully featured modern GIS.
# Add '''break lines support to interpolation modules''' (v.surf.rst, v.surf.idw, v.surf.bspline). Current implementations provide no support to specify locations of clifs 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.
# ''Your idea here''

'''Willing to Mentor:''' [[User:Landa|Martin Landa]], (''your name here'')

=== Imagery ===

# GRASS's imagery modules (for satellite, scanned maps, and orthophotos) act as enhanced raster modules. In GRASS 5 and 6 they were mostly implemented using interactive X-monitors which are not available in MS Windows and so are removed in the new cross-platform code of GRASS 7.
#* We need someone willing to port the old modules to work with GRASS 7, including writing new wxPython GUI frontends to a number of existing tools and updating the imagery libraries to current raster library standards.
#* In addition, there are a number of improved/automated georectification tools which have not been merged into GRASS 5/6 which it would be nice to have updated and merged into the main code.
# Implement [[OpenMP]] (multithreading) as much as possible
# ''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.

'''Willing to Mentor:''' (''your name here'')

=== 3D visualization ===

# Optimize OGSF (and NVIZ/wxNVIZ) to '''display large 3D point clouds with uninterupted tought speed'''. OGSF + (wx)NVIZ should be able to rotate point cloud (i.e. LiDAR dataset) with 4 millions of points on medium hardware (i.e. 2GHz CPU with 2Gb RAM and GPU with hardware transform and lighting support and dedicated video RAM) with response time not greater than 1.0 second.
# Design and implement '''text displaying and styling in OGSF library''' and it's front-ends (NVIZ, [[wxNVIZ]]). Solution should be user configurable (fonts, colors, effects etc.) and multilanguage friendly.
# Design and implement user-provided '''symbol support in OGSF library''' and it's front-ends (NVIZ, [[wxNVIZ]]). Solution should support GRASS symbols, SVG, and/or simple EPS symbols.

'''Willing to Mentor:''' (''your name here'')

=== Other ===

# 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.
# Design '''sophisticated Python scripting interface''' for GRASS based on [http://grass.osgeo.org/programming7/pythonlib.html GRASS Python Scripting Library]
# ''Your idea here''

'''Willing to Mentor:''' (''your name here'')

== Guidelines for Students ==

How do you maximize your chances of getting picked? First read the [http://code.google.com/p/google-summer-of-code/wiki/AdviceforStudents Google SoC FAQ]. Then talk to us about your idea. Try emailing our [http://lists.osgeo.org/mailman/listinfo/grass-dev dev-mailing list], or come and talk to us in [[IRC]] (#grass). You can also reach the mentors directly by emailing:
* [http://lists.osgeo.org/mailman/listinfo/soc The OSGeo SoC mailing list]
* Wolf Bergenheim (<tt>wolf+grass at bergenheim.net</tt>)

=== Getting started with GRASS coding ===

* The source code is maintained in a [http://trac.osgeo.org/grass/browser/grass/trunk SVN server] which is easy to browse
: Please review the [http://svn.osgeo.org/grass/grass/trunk/SUBMITTING SUBMITTING] files there for our coding standards.

* There is lots of good info at the [http://trac.osgeo.org/grass/wiki GRASS Developer's wiki]
: See also the [[Development|development section]] of the GRASS user's wiki

== Accepted Ideas ==

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

GRASS SoC Ideas 2011

2011-03-27T02:46:12Z

⚠️Helena: /* wxGUI */

{{ToModify}}
[[Image:gsoc_2011_logo.png|350px|right]]
__TOC__
== About ==

This is the GRASS page for [http://wiki.osgeo.org/index.php/Google_Summer_of_Code Google Summer of Code] 2011. Here we will list project ideas and and other information related to the GRASS GSoC projects.

* [http://code.google.com/soc/ Official Google Summer of Code 2011 homepage]
* [http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2011 OSGeo SoC 2011 homepage]

Promotion:
* OSGeo Flyer at http://svn.osgeo.org/osgeo/marketing/flyer/google_summer_of_code/OSGeo_GSoC_2011.pdf
* Videos at http://code.google.com/p/google-summer-of-code/wiki/Videos
* More Flyers at http://code.google.com/p/google-summer-of-code/wiki/GsocFlyers

== Timeline ==

See [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2011/timeline GSoC timeline]

* {{Done}} Mentoring organization applications open (March 11)

* {{Done}} Accepted mentoring organizations announced (March 18)

* '''Interested students should initiate preliminary discussions with projects (March 18-27)'''

* Student applications open (March 28)

* Deadline for student's applications (April 8)
: Registering your application early (before the deadline) allows us to give you feedback for revisions before the final deadline, enhancing your proposal and thus giving you a better chance of success.

* Mentor assignments and application reviews deadline (April 22)

* Accepted proposals announced (April 25)

* Community bonding time (getting to know the students)

* Work Begins (May 23)

* Midterm evaluation (July 11-15)

* Pencils down! (August 15)

* Final evaluations submitted to Google (August 22)

* Final results of GSoC 2011 announced (August 29)

* Students can begin submitting required code samples to Google (August 30)

== Required Steps ==

* List ideas

* Assign Mentors to Ideas

* Notify OSGeo

* Mentors evaluate student applications

* Accepted students announced

* Students subscribe to the [http://lists.osgeo.org/mailman/listinfo/grass-dev grass-dev mailing list] and introduce themselves

* Create directory structure in the [http://trac.osgeo.org/grass/browser/grass-addons GRASS add-ons SVN] for projects and setup access for students
** Students must read and post agreement to [http://grass.osgeo.org/programming7/rfc2_psc.html RFC2] to the [http://lists.osgeo.org/mailman/listinfo/grass-psc grass-psc mailing list] to gain SVN access
** Create a Wiki page for each accepted project, to be used as a progress reporting tool

* Coding begins...

* Students and mentors: Complete the Mid-term survey

* Final commit and packaging for Google

== Ideas ==

* '''Also review ideas from [[GRASS SoC Ideas 2007#Ideas|2007]], [[GRASS SoC Ideas 2008#Ideas|2008]], [[GRASS SoC Ideas 2009#Ideas|2009]], and [[GRASS SoC Ideas 2010#Ideas|2010]] which are still open'''.
* Project ideas of your own are also most welcome.

=== wxGUI ===

# 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]].
#:<center>
#:[[Image:Wxgui_current.png|480px|thumb|center|Current wxGUI layout with detached window components]]
#:[[Image:Wxgui_proposal.png|480px|thumb|center|Proposal for wxGUI layout modification (Recomposition of existing toolbars, mapview and menus)]]
#:</center>
# Add '''WMS and/or TiledMapService and/or WMS-T layer support''' for wxGUI. Tiles/WMS images should not be stored as GRASS rasters but only used for displaying purposes (i.e. stored in temp folder). Such tool should provide user-friendly setting choices based on service GetCapabilities response.
# Develop a GUI module in wxPython for creating animations from multiple maps and saving animation outputs to animated GIF, MOV, or MPEG files. See existing modules xganim, r.out.mpeg, and nviz's animation tools (co-mentor Helena Mitasova).
'''Willing to Mentor:''' [[User:Landa|Martin Landa]], [[User:MarisN|Maris Nartiss]], (''your name here'')

=== Raster ===

# ''Your idea here''

'''Willing to Mentor:''' (''your name here'')

=== Vector ===

# Add '''[[OpenMP]] parallelization''' where appropriate, for example, {{cmd|v.surf.rst}} and {{cmd|v.vol.rst}} ''(co-mentor Helena Mitasova)'' . See above idea in the [[GRASS SoC Ideas 2011#Raster|Raster section]].
# Better '''support for wrap-around at 180 longitude''': Currently the raster engine is pretty good at wrapping data over 180 longitude. The vector data isn't, but it should be. This is a great task if by the end of the summer you'd like to be familiar with the implementation method of an entire vector stack of a fully featured modern GIS.
# Add '''break lines support to interpolation modules''' (v.surf.rst, v.surf.idw, v.surf.bspline). Current implementations provide no support to specify locations of clifs 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.
# ''Your idea here''

'''Willing to Mentor:''' [[User:Landa|Martin Landa]], (''your name here'')

=== Imagery ===

# GRASS's imagery modules (for satellite, scanned maps, and orthophotos) act as enhanced raster modules. In GRASS 5 and 6 they were mostly implemented using interactive X-monitors which are not available in MS Windows and so are removed in the new cross-platform code of GRASS 7.
#* We need someone willing to port the old modules to work with GRASS 7, including writing new wxPython GUI frontends to a number of existing tools and updating the imagery libraries to current raster library standards.
#* In addition, there are a number of improved/automated georectification tools which have not been merged into GRASS 5/6 which it would be nice to have updated and merged into the main code.
# Implement [[OpenMP]] (multithreading) as much as possible
# ''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.

'''Willing to Mentor:''' (''your name here'')

=== 3D visualization ===

# Optimize OGSF (and NVIZ/wxNVIZ) to '''display large 3D point colouds with uninterupted tought speed'''. OGSF + (wx)NVIZ should be able to rotate point cloud (i.e. LiDAR dataset) with 4 millions of points on medium hardware (i.e. 2GHz CPU with 2Gb RAM and GPU with hardware transform and lighting support and dedicated video RAM) with response time not greater than 1.0 second.
# Design and implement '''text displaying and styling in OGSF library''' and it's front-ends (NVIZ, [[wxNVIZ]]). Solution should be user configurable (fonts, colors, effects etc.) and multilanguage friendly.
# Design and implement user-provided '''symbol support in OGSF library''' and it's front-ends (NVIZ, [[wxNVIZ]]). Solution should support GRASS symbols, SVG, and/or simple EPS symbols.

'''Willing to Mentor:''' (''your name here'')

=== Other ===

# 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.
# Design '''sophisticated Python scripting interface''' for GRASS based on [http://grass.osgeo.org/programming7/pythonlib.html GRASS Python Scripting Library]
# ''Your idea here''

'''Willing to Mentor:''' (''your name here'')

== Guidelines for Students ==

How do you maximize your chances of getting picked? First read the [http://code.google.com/p/google-summer-of-code/wiki/AdviceforStudents Google SoC FAQ]. Then talk to us about your idea. Try emailing our [http://lists.osgeo.org/mailman/listinfo/grass-dev dev-mailing list], or come and talk to us in [[IRC]] (#grass). You can also reach the mentors directly by emailing:
* [http://lists.osgeo.org/mailman/listinfo/soc The OSGeo SoC mailing list]
* Wolf Bergenheim (<tt>wolf+grass at bergenheim.net</tt>)

=== Getting started with GRASS coding ===

* The source code is maintained in a [http://trac.osgeo.org/grass/browser/grass/trunk SVN server] which is easy to browse
: Please review the [http://svn.osgeo.org/grass/grass/trunk/SUBMITTING SUBMITTING] files there for our coding standards.

* There is lots of good info at the [http://trac.osgeo.org/grass/wiki GRASS Developer's wiki]
: See also the [[Development|development section]] of the GRASS user's wiki

== Accepted Ideas ==

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

WxNviz

2011-03-27T02:29:46Z

⚠️Helena: /* Known issues */

Back to [[WxPython-based GUI for GRASS|wxGUI]] page.

See also {{cmd|wxGUI.Nviz|version=70}} manual page.

'''wxNviz''' is a [[wxGUI]] extension which allows users to realistically render multiple surfaces (raster data) in a 3D space, optionally using thematic coloring, draping 2D vector data over the surfaces, displaying 3D vector data in the space, and visualization of volume data (3D raster data).
__TOC__
== Screenshots ==
<center>
{|
|-
| [[Image:Wxnviz-alpha-0.png|250px|thumb|2008-06-27: Display raster map from layer tree in 2.5D (surface)]] ||
[[Image:Wxnviz-alpha-1.png|250px|thumb|2008-07-05: Support for vector data (2D lines) added]]
|-
| [[Image:Wxnviz-alpha-2.png|250px|thumb|2008-07-26: Support for vector point data]] ||
[[Image:Wxnviz-alpha-3.png|250px|thumb|2008-08-02: 3D vector data support]]
|-
| [[Image:Wxnviz-alpha-4.png|250px|thumb|2008-08-09: Initial support for volumetric data]] ||
[[Image:Wxnviz-lmgr.png|250px|thumb|2010-05-31: 3D view tools window integrated into Layer Manager]]
|-
| [[Image:Wxnviz-light.png|250px|thumb|center|Lighting control panel in Layer Manager (2010-06-17)]] ||
[[Image:Wxnviz-fringe.png|250px|thumb|center|Fringe control panel in Layer Manager (2010-06-23)]]
|-
| [[Image:Wxnviz-redirect.png|250px|thumb|center|Redirect messages to wxGUI (2010-08-08)]] ||
[[Image:Wxnviz-volumes.png|250px|thumb|center|Displaying raster (surface), 2D vector and 3D raster (volume) in the 3D space (2010-08-16)]]
|}
</center>

== HowTo ==

* [http://gama.fsv.cvut.cz/~landa/grass/swf/wxnviz-loading-data.html Loading data, settings layer properties]
* [http://gama.fsv.cvut.cz/~landa/grass/swf/wxnviz-fringe.html Visualizing fringes]
* [http://gama.fsv.cvut.cz/~landa/grass/swf/wxnviz-volumes.html 3D raster maps (volumes) in the space]

== Ideas ==

* Fog support (see [http://gpwiki.org/index.php/OpenGL:Tutorials:Tutorial_Framework:Light_and_Fog], [http://www.swiftless.com/tutorials/opengl/fog.html], [http://nehe.gamedev.net/data/lessons/lesson.asp?lesson=16])
* Vertical labels (take from geonames.org point data): like in http://tev.fbk.eu/marmota/blog/?p=82

== Known issues ==

* List of [http://trac.osgeo.org/grass/query?status=assigned&status=new&status=reopened&order=priority&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&keywords=~wxNviz open] and [http://trac.osgeo.org/grass/query?status=assigned&status=closed&order=priority&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&keywords=~wxNviz closed] tickets
* Light settings do not work on Mac
* Adding vector data crashes wxGUI on Mac
* Rendering at fine resolution works only when changing viewing position or clicking the buttons that increase the numbers for perspective, twist, height and z-exag. Moving sliders does the required change but there is no redraw to full resolution
* Viewing height sometimes sets to 1 after switching to 2D and back to 3D View (or with the simultaneous 2D view - very nice feature) and even after View is reset, it keeps getting back at 1 each time the slider is touched
* Typing in the height or z-exag numbers and ENTER does not do anything but the typed number gets accepted after clicking on the increase/decrease button, it is not possible to set the height value beyond the initial maximum
* Adding fringe just flashes it but it does not stay
* Isosurfaces tested with Nags Head time series data (I will provide link) don't seem to be working, after setting 3D region and adding 3D raster nothing gets drawn, when moving the related DEM around only line rectangle shows instead of a box.
* Adding draw, draw current and clear button may be useful

==Missing features==

* cutting planes for multiple surfaces
* 3D points with multiple attributes

== Google Summer of Code ==

=== [[wxNviz GSoC 2008|2008]] ===

* [http://trac.osgeo.org/grass/wiki/SoCProjects#wxNvizdevelopmentforenhanced34Dvisualizationandanalysis Accepted Google Summer of Code 2008 project]

=== [[wxNviz GSoC 2010|2010]] ===

* [http://trac.osgeo.org/grass/wiki/SoCProjects#wxNvizdevelopmentforenhanced34Dvisualizationandanalysis Accepted Google Summer of Code 2010 project]

== See also ==

* http://lists.osgeo.org/pipermail/grass-dev/2008-February/035792.html

{{WxGUI}}

WxNviz

2011-03-27T02:27:30Z

⚠️Helena: /* Known issues */

Back to [[WxPython-based GUI for GRASS|wxGUI]] page.

See also {{cmd|wxGUI.Nviz|version=70}} manual page.

'''wxNviz''' is a [[wxGUI]] extension which allows users to realistically render multiple surfaces (raster data) in a 3D space, optionally using thematic coloring, draping 2D vector data over the surfaces, displaying 3D vector data in the space, and visualization of volume data (3D raster data).
__TOC__
== Screenshots ==
<center>
{|
|-
| [[Image:Wxnviz-alpha-0.png|250px|thumb|2008-06-27: Display raster map from layer tree in 2.5D (surface)]] ||
[[Image:Wxnviz-alpha-1.png|250px|thumb|2008-07-05: Support for vector data (2D lines) added]]
|-
| [[Image:Wxnviz-alpha-2.png|250px|thumb|2008-07-26: Support for vector point data]] ||
[[Image:Wxnviz-alpha-3.png|250px|thumb|2008-08-02: 3D vector data support]]
|-
| [[Image:Wxnviz-alpha-4.png|250px|thumb|2008-08-09: Initial support for volumetric data]] ||
[[Image:Wxnviz-lmgr.png|250px|thumb|2010-05-31: 3D view tools window integrated into Layer Manager]]
|-
| [[Image:Wxnviz-light.png|250px|thumb|center|Lighting control panel in Layer Manager (2010-06-17)]] ||
[[Image:Wxnviz-fringe.png|250px|thumb|center|Fringe control panel in Layer Manager (2010-06-23)]]
|-
| [[Image:Wxnviz-redirect.png|250px|thumb|center|Redirect messages to wxGUI (2010-08-08)]] ||
[[Image:Wxnviz-volumes.png|250px|thumb|center|Displaying raster (surface), 2D vector and 3D raster (volume) in the 3D space (2010-08-16)]]
|}
</center>

== HowTo ==

* [http://gama.fsv.cvut.cz/~landa/grass/swf/wxnviz-loading-data.html Loading data, settings layer properties]
* [http://gama.fsv.cvut.cz/~landa/grass/swf/wxnviz-fringe.html Visualizing fringes]
* [http://gama.fsv.cvut.cz/~landa/grass/swf/wxnviz-volumes.html 3D raster maps (volumes) in the space]

== Ideas ==

* Fog support (see [http://gpwiki.org/index.php/OpenGL:Tutorials:Tutorial_Framework:Light_and_Fog], [http://www.swiftless.com/tutorials/opengl/fog.html], [http://nehe.gamedev.net/data/lessons/lesson.asp?lesson=16])
* Vertical labels (take from geonames.org point data): like in http://tev.fbk.eu/marmota/blog/?p=82

== Known issues ==

* List of [http://trac.osgeo.org/grass/query?status=assigned&status=new&status=reopened&order=priority&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&keywords=~wxNviz open] and [http://trac.osgeo.org/grass/query?status=assigned&status=closed&order=priority&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&keywords=~wxNviz closed] tickets
* Light settings do not work on Mac
* Adding vector data crashes wxGUI on Mac
* Rendering at fine resolution works only when changing viewing position or clicking the buttons that increase the numbers for perspective, twist, height and z-exag. Moving sliders does the required change but there is no redraw to full resolution
* Viewing height sometimes sets to 1 after switching to 2D and back to 3D View (or with the simultaneous 2D view - very nice feature) and even after View is reset, it keeps getting back at 1 each time the slider is touched
* Typing in the height or z-exag numbers and ENTER does not do anything but the typed number gets accepted after clicking on the increase/decrease button, it is not possible to set the height value beyond the initial maximum
* Adding fringe just flashes it but it does not stay
* Isosurfaces tested with Nags Head time series data (I will provide link) don't seem to be working, after setting 3D region and adding 3D raster nothing gets drawn, when moving the related DEM around only line rectangle shows instead of a box.
it shows only rectangle instead of box* Adding draw, draw current and clear button may be useful

==Missing features==

* cutting planes for multiple surfaces
* 3D points with multiple attributes

== Google Summer of Code ==

=== [[wxNviz GSoC 2008|2008]] ===

* [http://trac.osgeo.org/grass/wiki/SoCProjects#wxNvizdevelopmentforenhanced34Dvisualizationandanalysis Accepted Google Summer of Code 2008 project]

=== [[wxNviz GSoC 2010|2010]] ===

* [http://trac.osgeo.org/grass/wiki/SoCProjects#wxNvizdevelopmentforenhanced34Dvisualizationandanalysis Accepted Google Summer of Code 2010 project]

== See also ==

* http://lists.osgeo.org/pipermail/grass-dev/2008-February/035792.html

{{WxGUI}}

WxNviz

2011-03-27T01:49:40Z

⚠️Helena: /* Known issues */

Back to [[WxPython-based GUI for GRASS|wxGUI]] page.

See also {{cmd|wxGUI.Nviz|version=70}} manual page.

'''wxNviz''' is a [[wxGUI]] extension which allows users to realistically render multiple surfaces (raster data) in a 3D space, optionally using thematic coloring, draping 2D vector data over the surfaces, displaying 3D vector data in the space, and visualization of volume data (3D raster data).
__TOC__
== Screenshots ==
<center>
{|
|-
| [[Image:Wxnviz-alpha-0.png|250px|thumb|2008-06-27: Display raster map from layer tree in 2.5D (surface)]] ||
[[Image:Wxnviz-alpha-1.png|250px|thumb|2008-07-05: Support for vector data (2D lines) added]]
|-
| [[Image:Wxnviz-alpha-2.png|250px|thumb|2008-07-26: Support for vector point data]] ||
[[Image:Wxnviz-alpha-3.png|250px|thumb|2008-08-02: 3D vector data support]]
|-
| [[Image:Wxnviz-alpha-4.png|250px|thumb|2008-08-09: Initial support for volumetric data]] ||
[[Image:Wxnviz-lmgr.png|250px|thumb|2010-05-31: 3D view tools window integrated into Layer Manager]]
|-
| [[Image:Wxnviz-light.png|250px|thumb|center|Lighting control panel in Layer Manager (2010-06-17)]] ||
[[Image:Wxnviz-fringe.png|250px|thumb|center|Fringe control panel in Layer Manager (2010-06-23)]]
|-
| [[Image:Wxnviz-redirect.png|250px|thumb|center|Redirect messages to wxGUI (2010-08-08)]] ||
[[Image:Wxnviz-volumes.png|250px|thumb|center|Displaying raster (surface), 2D vector and 3D raster (volume) in the 3D space (2010-08-16)]]
|}
</center>

== HowTo ==

* [http://gama.fsv.cvut.cz/~landa/grass/swf/wxnviz-loading-data.html Loading data, settings layer properties]
* [http://gama.fsv.cvut.cz/~landa/grass/swf/wxnviz-fringe.html Visualizing fringes]
* [http://gama.fsv.cvut.cz/~landa/grass/swf/wxnviz-volumes.html 3D raster maps (volumes) in the space]

== Ideas ==

* Fog support (see [http://gpwiki.org/index.php/OpenGL:Tutorials:Tutorial_Framework:Light_and_Fog], [http://www.swiftless.com/tutorials/opengl/fog.html], [http://nehe.gamedev.net/data/lessons/lesson.asp?lesson=16])
* Vertical labels (take from geonames.org point data): like in http://tev.fbk.eu/marmota/blog/?p=82

== Known issues ==

* List of [http://trac.osgeo.org/grass/query?status=assigned&status=new&status=reopened&order=priority&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&keywords=~wxNviz open] and [http://trac.osgeo.org/grass/query?status=assigned&status=closed&order=priority&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&keywords=~wxNviz closed] tickets
* Light settings do not work on Mac
* Adding vector data crashes wxGUI on Mac
* Rendering at fine resolution works only when changing viewing position or clicking the buttons that increase the numbers for perspective, twist, height and z-exag. Moving sliders does the required change but there is no redraw to full resolution
* Viewing height sometimes sets to 1 after switching to 2D and back to 3D View (or with the simultaneous 2D view - very nice feature) and even after View is reset, it keeps getting back at 1 each time the slider is touched
* Typing in the height or z-exag numbers and ENTER does not do anything but the typed number gets accepted after clicking on the increase/decrease button, it is not possible to set the height value beyond the initial maximum
* Adding fringe just flashes it but it does not stay
* Adding draw, draw current and clear button may be useful

==Missing features==

* cutting planes for multiple surfaces
* 3D points with multiple attributes

== Google Summer of Code ==

=== [[wxNviz GSoC 2008|2008]] ===

* [http://trac.osgeo.org/grass/wiki/SoCProjects#wxNvizdevelopmentforenhanced34Dvisualizationandanalysis Accepted Google Summer of Code 2008 project]

=== [[wxNviz GSoC 2010|2010]] ===

* [http://trac.osgeo.org/grass/wiki/SoCProjects#wxNvizdevelopmentforenhanced34Dvisualizationandanalysis Accepted Google Summer of Code 2010 project]

== See also ==

* http://lists.osgeo.org/pipermail/grass-dev/2008-February/035792.html

{{WxGUI}}

WxNviz

2011-03-27T01:46:31Z

⚠️Helena: /* Know issues */

Back to [[WxPython-based GUI for GRASS|wxGUI]] page.

See also {{cmd|wxGUI.Nviz|version=70}} manual page.

'''wxNviz''' is a [[wxGUI]] extension which allows users to realistically render multiple surfaces (raster data) in a 3D space, optionally using thematic coloring, draping 2D vector data over the surfaces, displaying 3D vector data in the space, and visualization of volume data (3D raster data).
__TOC__
== Screenshots ==
<center>
{|
|-
| [[Image:Wxnviz-alpha-0.png|250px|thumb|2008-06-27: Display raster map from layer tree in 2.5D (surface)]] ||
[[Image:Wxnviz-alpha-1.png|250px|thumb|2008-07-05: Support for vector data (2D lines) added]]
|-
| [[Image:Wxnviz-alpha-2.png|250px|thumb|2008-07-26: Support for vector point data]] ||
[[Image:Wxnviz-alpha-3.png|250px|thumb|2008-08-02: 3D vector data support]]
|-
| [[Image:Wxnviz-alpha-4.png|250px|thumb|2008-08-09: Initial support for volumetric data]] ||
[[Image:Wxnviz-lmgr.png|250px|thumb|2010-05-31: 3D view tools window integrated into Layer Manager]]
|-
| [[Image:Wxnviz-light.png|250px|thumb|center|Lighting control panel in Layer Manager (2010-06-17)]] ||
[[Image:Wxnviz-fringe.png|250px|thumb|center|Fringe control panel in Layer Manager (2010-06-23)]]
|-
| [[Image:Wxnviz-redirect.png|250px|thumb|center|Redirect messages to wxGUI (2010-08-08)]] ||
[[Image:Wxnviz-volumes.png|250px|thumb|center|Displaying raster (surface), 2D vector and 3D raster (volume) in the 3D space (2010-08-16)]]
|}
</center>

== HowTo ==

* [http://gama.fsv.cvut.cz/~landa/grass/swf/wxnviz-loading-data.html Loading data, settings layer properties]
* [http://gama.fsv.cvut.cz/~landa/grass/swf/wxnviz-fringe.html Visualizing fringes]
* [http://gama.fsv.cvut.cz/~landa/grass/swf/wxnviz-volumes.html 3D raster maps (volumes) in the space]

== Ideas ==

* Fog support (see [http://gpwiki.org/index.php/OpenGL:Tutorials:Tutorial_Framework:Light_and_Fog], [http://www.swiftless.com/tutorials/opengl/fog.html], [http://nehe.gamedev.net/data/lessons/lesson.asp?lesson=16])
* Vertical labels (take from geonames.org point data): like in http://tev.fbk.eu/marmota/blog/?p=82

== Known issues ==

* List of [http://trac.osgeo.org/grass/query?status=assigned&status=new&status=reopened&order=priority&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&keywords=~wxNviz open] and [http://trac.osgeo.org/grass/query?status=assigned&status=closed&order=priority&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&keywords=~wxNviz closed] tickets
* Light settings do not work on Mac
* Adding vector data crashes wxGUI on Mac
* Rendering at fine resolution works only when changing viewing position or clicking the buttons that increase the numbers for perspective, twist, height and z-exag. Moving sliders does the required change but there is no redraw to full resolution
* Viewing height sometimes sets to 1 after switching to 2D and back to 3D View (or with the simultaneous 2D view - very nice feature) and even after View is reset, it keeps getting back at 1 each time the slider is touched
* Typing in the height or z-exag numbers and ENTER does not do anything but the typed number gets accepted after clicking on the increase/decrease button, it is not possible to set the height value beyond the initial maximum
* Adding fringe just flashes it but it does not stay
* Adding draw, draw current and clear button may be useful

== Google Summer of Code ==

=== [[wxNviz GSoC 2008|2008]] ===

* [http://trac.osgeo.org/grass/wiki/SoCProjects#wxNvizdevelopmentforenhanced34Dvisualizationandanalysis Accepted Google Summer of Code 2008 project]

=== [[wxNviz GSoC 2010|2010]] ===

* [http://trac.osgeo.org/grass/wiki/SoCProjects#wxNvizdevelopmentforenhanced34Dvisualizationandanalysis Accepted Google Summer of Code 2010 project]

== See also ==

* http://lists.osgeo.org/pipermail/grass-dev/2008-February/035792.html

{{WxGUI}}

WxNviz

2010-08-17T02:16:04Z

⚠️Helena: /* Know issues */

Back to [[WxPython-based GUI for GRASS|wxGUI]] page.

See also {{cmd|wxGUI.Nviz|version=70}} manual page.

'''wxNviz''' is a [[wxGUI]] extension which allows users to realistically render multiple surfaces (raster data) in a 3D space, optionally using thematic coloring, draping 2D vector data over the surfaces, displaying 3D vector data in the space, and visualization of volume data (3D raster data).
__TOC__
== Screenshots ==
<center>
{|
|-
| [[Image:Wxnviz-alpha-0.png|250px|thumb|2008-06-27: Display raster map from layer tree in 2.5D (surface)]] ||
[[Image:Wxnviz-alpha-1.png|250px|thumb|2008-07-05: Support for vector data (2D lines) added]]
|-
| [[Image:Wxnviz-alpha-2.png|250px|thumb|2008-07-26: Support for vector point data]] ||
[[Image:Wxnviz-alpha-3.png|250px|thumb|2008-08-02: 3D vector data support]]
|-
| [[Image:Wxnviz-alpha-4.png|250px|thumb|2008-08-09: Initial support for volumetric data]] ||
[[Image:Wxnviz-lmgr.png|250px|thumb|2010-05-31: 3D view tools window integrated into Layer Manager]]
|-
| [[Image:Wxnviz-light.png|250px|thumb|center|Lighting control panel in Layer Manager (2010-06-17)]] ||
[[Image:Wxnviz-fringe.png|250px|thumb|center|Fringe control panel in Layer Manager (2010-06-23)]]
|-
| [[Image:Wxnviz-redirect.png|250px|thumb|center|Redirect messages to wxGUI (2010-08-08)]] ||
[[Image:Wxnviz-volumes.png|250px|thumb|center|Displaying raster (surface), 2D vector and 3D raster (volume) in the 3D space (2010-08-16)]]
|}
</center>

== HowTo ==

* [http://gama.fsv.cvut.cz/~landa/grass/swf/wxnviz-loading-data.html Loading data, settings layer properties]
* [http://gama.fsv.cvut.cz/~landa/grass/swf/wxnviz-fringe.html Visualizing fringes]
* [http://gama.fsv.cvut.cz/~landa/grass/swf/wxnviz-volumes.html 3D raster maps (volumes) in the space]

== Ideas ==

* Fog support (see [http://gpwiki.org/index.php/OpenGL:Tutorials:Tutorial_Framework:Light_and_Fog], [http://www.swiftless.com/tutorials/opengl/fog.html], [http://nehe.gamedev.net/data/lessons/lesson.asp?lesson=16])
* Vertical labels (take from geonames.org point data): like in http://tev.fbk.eu/marmota/blog/?p=82

== Know issues ==

* List of [http://trac.osgeo.org/grass/query?status=assigned&status=new&status=reopened&order=priority&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&keywords=~wxNviz open] and [http://trac.osgeo.org/grass/query?status=assigned&status=closed&order=priority&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&keywords=~wxNviz closed] tickets
* Light settings doesn't work
* Map canvas is flickering when adding new vector map layer - it crashes wxGUi for me on Mac
* it still does not clean the View pannel when switching from 3d back to 2d
*rendering at high res works only when changing viewing position or clicking the buttons that increase the numbers for persp, twist, height and z-exag. Moving sliders does the required change but there is no redraw to full resolution
* adding draw, draw current and clear button may be useful
* typing in the height or z-exag numbers and ENTER does not do anything but the typed number gets accepted after clicking on
the increase/decrease button
* adding fringe just flashes it but it does not stay there.

== Google Summer of Code ==

=== [[wxNviz GSoC 2008|2008]] ===

* [http://trac.osgeo.org/grass/wiki/SoCProjects#wxNvizdevelopmentforenhanced34Dvisualizationandanalysis Accepted Google Summer of Code 2008 project]

=== [[wxNviz GSoC 2010|2010]] ===

* [http://trac.osgeo.org/grass/wiki/SoCProjects#wxNvizdevelopmentforenhanced34Dvisualizationandanalysis Accepted Google Summer of Code 2010 project]

== See also ==

* http://lists.osgeo.org/pipermail/grass-dev/2008-February/035792.html

{{WxGUI}}

Talk:WxNviz

2010-04-02T08:10:12Z

⚠️Helena: /* Proposal for Google SoC 2010 */

== Proposal for [[GRASS SoC Ideas 2010|Google SoC 2010]] ==

To continue in [[wxNviz]] development which has been started in the frame of [http://code.google.com/soc/2008/osgeo/appinfo.html?csaid=FB0A81AE65AEC356 Google Summer of Code 2008].

Main goals:

# To implement all missing features from TCL/TK {{cmd|nviz}} application and replace nviz by wxNviz in GRASS 7 (remove TCL/TK dependency)
#* Lighting
#* Decoration (labels, north arrow, scale bar, legend, fringe)
#* Querying (rasters, vectors, volumes)
#* Cutting planes, scaled difference
#* Animations
#* Scripting, including replacement for tool to generate images for dynamic surfaces
#* Point symbols sized and colored based on attributes
#* Make wxNviz working on MS Windows
#* Add more features here...
# New features
#* Fog support (see [http://gpwiki.org/index.php/OpenGL:Tutorials:Tutorial_Framework:Light_and_Fog], [http://www.swiftless.com/tutorials/opengl/fog.html], [http://nehe.gamedev.net/data/lessons/lesson.asp?lesson=16])
#* Vertical labels (take from geonames.org point data): like in http://tev.fbk.eu/marmota/blog/?p=82
#* Add more features here...
# (''optional'') Design and implement text displaying and styling in OGSF library and it's front-end wxNVIZ. Solution should be user configurable (fonts, colors, effects etc.) and multilanguage friendly.
# (''optional'') Design and implement user-provided symbol support in OGSF library and it's front-end wxNVIZ. Solution should support GRASS symbols and/or SVG symbols.

GRASS SoC Ideas 2010

2010-03-15T14:42:53Z

⚠️Helena: /* Vector */

[[Image:gsoc_2010_logo.jpg|right]]

== About ==
<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#FFF5E5;">
'''March 2010: This page is open to contributions - please edit!'''
</div>

This is the GRASS page for [http://wiki.osgeo.org/index.php/Google_Summer_of_Code Google Summer of Code] 2010. Here we will list project ideas and and other information related to the GRASS GSoC projects.

* '''''Note that at this point accepted mentoring organizations have not yet been announced.'''''

* [http://code.google.com/soc/ Official Google Summer of Code 2010 homepage]
* [http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2010 OSGeo SoC 2010 homepage]

Promotion:
OSGeo Flyer at http://svn.osgeo.org/osgeo/marketing/flyer/google_summer_of_code/OSGeo_GSoC_2010.pdf
Videos at http://code.google.com/p/google-summer-of-code/wiki/Videos
More Flyers at http://code.google.com/p/google-summer-of-code/wiki/GsocFlyers

== Timeline ==

([http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/timeline GSoC timeline])

* Mentoring organization applications open (March 8-12)

* Accepted mentoring organizations announced (March 18)

* '''Interested students should initiate preliminary discussions with projects (March 18-29)'''

* Student applications open (March 29)
* Deadline for student's applications (April 9)
: Registering your application early (before the deadline) allows us to give you feedback for revisions before the final deadline, enhancing your proposal and thus giving you a better chance of success.

* Mentor assignments and application reviews deadline (April 21)

* Accepted proposals announced (April 26)

* Community bonding time (getting to know the students)

* Work Begins (May 24)

* Midterm evaluation (July 12-16)

* Pencils down! (August 9)
* Final evaluations submitted to Google (August 16)

== Required Steps ==

* List ideas
* Assign Mentors to Ideas
* Notify OSGeo
* Mentors evaluate student applications
* Accepted students announced
* Students subscribe to the [http://grass.osgeo.org/community/support.php grass-dev mailing list] and introduce themselves
* Create directory structure in the [http://trac.osgeo.org/grass/browser/grass-addons GRASS add-ons SVN] for projects and setup access for students
** Students must read and post agreement to [http://download.osgeo.org/grass/grass6_progman/rfc/ RFC2] to the [http://grass.osgeo.org/community/support.php grass-psc mailing list] to gain SVN access
** Create a Wiki page for each accepted project, to be used as a progress reporting tool
* Coding begins...
* Students and mentors: Complete the Mid-term survey
* Final commit and packaging for Google

== Ideas ==

* '''Also review ideas from [[GRASS SoC Ideas 2008#Ideas|2008]] and [[GRASS SoC Ideas 2009#Ideas|2009]] which are still open'''.
* Project ideas of your own are also most welcome.

=== [[wxGUI]] ===

'''Willing to Mentor:''' ''Helena Mitasova (wxnviz, xganim), (your name here)''

* wxGUI layout customization - reorganize the wxGUI layout to be more similar to QGIS and likeminded with all-in-one-frame interface (see figures below). Essentially follow the [http://en.wikipedia.org/wiki/Human_interface_guidelines Human interface guidelines] and mind your users (and where they come from - think newcomers to the GRASS world - "Don't Limit Your User Base" by being too different from others). If at all possible, this should be implemented as a ''skin'' to give users the choice to also use wxGUI as Multiple Document Interface (MDI, i.e, the wxGUI windows reside under a single parent window). More [[WxGUI#Layout|here]].

<center>
{|
| [[Image:Wxgui_current.png|325px|thumb|center|Current wxGUI layout with detached window components]]
||
| [[Image:Wxgui_proposal.png|200px|thumb|center|Proposal for wxGUI layout modification (Recomposition of existing toolbars, mapview and menus)]]
|}
</center>

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

* Develop a [[WxPython-based_GUI_for_GRASS#Cartography_tools|graphical cartographic module]] GUI front-end for {{cmd|ps.map}}
: ''Willing to co-mentor: H.Bowman'' for ps.map advice but need to find a lead mentor who knows wxGRASS

* Develop a GUI module in wxPython for creating animations from multiple maps and saving animation outputs to animated GIF, MOV, or MPEG files. See existing modules {{cmd|xganim}}, {{cmd|r.out.mpeg}}, and {{cmd|nviz}}'s animation tools.

* Implement [[wxGUI#Graphical_modeller|graphical modeller]].

=== Raster ===

* Implement [[OpenMP]] (multithreading) as much as possible
** 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

* ''Your idea here''

-- 
'''Willing to Mentor:''' (''your name here'')

=== Vector ===

* Large vector maps: Currently a few modules which are important for massive datasets (like LIDAR data) are able to operate on maps which do not have topology built. (thus avoiding the associated per-feature memory overheads) It would be great if more modules could speak to these big-but-dumb maps (starting with {{cmd|v.info}}). This probably isn't enough for a full SoC project, so in addition the vector engine should be audited for places where memory optimization could take place.

* Add OpenMP parallelization where appropriate, for example, v.surf.rst and v.vol.rst ''(co-mentor Helena Mitasova)'' . See above idea in the Raster section.

* Better support for wrap-around at 180 longitude: Currently the raster engine is pretty good at wrapping data over 180 longitude. The vector data isn't, but it should be. This is a great task if by the end of the summer you'd like to be familiar with the implementation method of an entire vector stack of a fully featured modern GIS.

* ''Your idea here''
-- 
'''Willing to Mentor:''' (''your name here'')

=== Imagery ===

* GRASS's imagery modules (for satellite, scanned maps, and orthophotos) act as enhanced raster modules. In GRASS 5 and 6 they were mostly implimented using interactive X-monitors which are not available in MS Windows and so are removed in the new cross-platform code of GRASS 7.
** We need someone willing to port the old modules to work with GRASS 7, including writing new wxPython GUI frontends to a number of existing tools and updating the imagery libraries to current raster library standards.
** In addition, there are a number of improved/automated georectification tools which have not been merged into GRASS 5/6 which it would be nice to have updated and merged into the main code.

* Implement [[OpenMP]] (multithreading) as much as possible

See the [[Image_processing#Ideas_collection_for_improving_GRASS.27_Image_processing_capabilities|Ideas for imagery improvement]] and [[GRASS_7_ideas_collection#Imagery|GRASS 7 ideas]] wiki pages for more details.

'''Willing to Mentor:''' (''your name here'')

=== Other ===

* Design system for building manual pages based on [http://docbook.org DocBook] system

* 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 text displaying and styling in OGSF library and it's front-ends (NVIZ, wxNVIZ). Solution should be user configurable (fonts, colors, effects etc.) and multilanguage friendly.

* Design and implement user-provided symbol support in OGSF library and it's front-ends (NVIZ, wxNVIZ). Solution should support GRASS symbols and/or SVG symbols.

* '''''Zap-a-bug!''''': There are many old and neglected bugs in the [http://grass.osgeo.org/bugtracking/index.php three bug tracker(s)]. Reach 100 points by the end of the summer:
** trival bugs are 1 point
** minor bugs are 2 points
** normal bugs are 3 points
** major bugs are 4 points
** critical bugs are 7 points
** blocker bugs are 10 points
: Rules: Bugs must be in the tracker before I thought of this idea (13 March 2010) and priority is counted from that time as well. (exemptions may be given for fixing wishes and newly reported critical|blocker bugs ''only'' with prior permission of both your mentor and co-mentor). Points for fixing old wishes may be allocated at the discretion of your mentor (but no more than 10pts per wish). The bug fix '''must''' include a code patch, and your mentor is explicitly responsible for deciding when a bug is done and marking it as "fixed" in the trac system, not you. You get no points for bugs fixed before the SoC officially starts, but it could impress the judges and allow you to get in enough practice to hit the ground running. Good sense of humor, communication skills, and a thick skin are a must, as you will not be working in isolation. Students who are officially enrolled at their university and the SoC program with the given name of "Frank" or "Anonymous" (or obvious lingual/gender equivalent) will start the summer with an automatic 10 points. Members of the dev team with SVN write access may award 1 bonus point per week for any bug fixed within that week if they are especially impressed with your solution.
: (A great way to learn the entire GIS and get to know the dev team!)

== Guidelines for Students ==

How do you maximize your chances of getting picked? First read the [http://code.google.com/p/google-summer-of-code/wiki/AdviceforStudents Google SoC FAQ]. Then talk to us about your idea. Try emailing [http://lists.osgeo.org/mailman/listinfo/grass-dev our dev-mailing list], or come and talk to us in [[IRC]] (#grass). You can also reach the mentors directly by emailing:
* [http://lists.osgeo.org/mailman/listinfo/soc The OSGeo SoC mailing list]
* Wolf Bergenheim (wolf+grass@bergenheim.net)

=== Getting started with GRASS coding ===

* The source code is maintained in a [http://trac.osgeo.org/grass/browser/grass/trunk SVN server] which is easy to browse
: Please review the [http://svn.osgeo.org/grass/grass/trunk/SUBMITTING SUBMITTING] files there for our coding standards.

* There is lots of good info at the [http://trac.osgeo.org/grass/wiki GRASS Developer's wiki]
: See also the [[Development|development section]] of the GRASS user's wiki

== Accepted Ideas ==

* TBD


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

GRASS SoC Ideas 2010

2010-03-15T14:38:25Z

⚠️Helena: /* wxGUI */

[[Image:gsoc_2010_logo.jpg|right]]

== About ==
<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#FFF5E5;">
'''March 2010: This page is open to contributions - please edit!'''
</div>

This is the GRASS page for [http://wiki.osgeo.org/index.php/Google_Summer_of_Code Google Summer of Code] 2010. Here we will list project ideas and and other information related to the GRASS GSoC projects.

* '''''Note that at this point accepted mentoring organizations have not yet been announced.'''''

* [http://code.google.com/soc/ Official Google Summer of Code 2010 homepage]
* [http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2010 OSGeo SoC 2010 homepage]

Promotion:
OSGeo Flyer at http://svn.osgeo.org/osgeo/marketing/flyer/google_summer_of_code/OSGeo_GSoC_2010.pdf
Videos at http://code.google.com/p/google-summer-of-code/wiki/Videos
More Flyers at http://code.google.com/p/google-summer-of-code/wiki/GsocFlyers

== Timeline ==

([http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/timeline GSoC timeline])

* Mentoring organization applications open (March 8-12)

* Accepted mentoring organizations announced (March 18)

* '''Interested students should initiate preliminary discussions with projects (March 18-29)'''

* Student applications open (March 29)
* Deadline for student's applications (April 9)
: Registering your application early (before the deadline) allows us to give you feedback for revisions before the final deadline, enhancing your proposal and thus giving you a better chance of success.

* Mentor assignments and application reviews deadline (April 21)

* Accepted proposals announced (April 26)

* Community bonding time (getting to know the students)

* Work Begins (May 24)

* Midterm evaluation (July 12-16)

* Pencils down! (August 9)
* Final evaluations submitted to Google (August 16)

== Required Steps ==

* List ideas
* Assign Mentors to Ideas
* Notify OSGeo
* Mentors evaluate student applications
* Accepted students announced
* Students subscribe to the [http://grass.osgeo.org/community/support.php grass-dev mailing list] and introduce themselves
* Create directory structure in the [http://trac.osgeo.org/grass/browser/grass-addons GRASS add-ons SVN] for projects and setup access for students
** Students must read and post agreement to [http://download.osgeo.org/grass/grass6_progman/rfc/ RFC2] to the [http://grass.osgeo.org/community/support.php grass-psc mailing list] to gain SVN access
** Create a Wiki page for each accepted project, to be used as a progress reporting tool
* Coding begins...
* Students and mentors: Complete the Mid-term survey
* Final commit and packaging for Google

== Ideas ==

* '''Also review ideas from [[GRASS SoC Ideas 2008#Ideas|2008]] and [[GRASS SoC Ideas 2009#Ideas|2009]] which are still open'''.
* Project ideas of your own are also most welcome.

=== [[wxGUI]] ===

'''Willing to Mentor:''' ''Helena Mitasova (wxnviz, xganim), (your name here)''

* wxGUI layout customization - reorganize the wxGUI layout to be more similar to QGIS and likeminded with all-in-one-frame interface (see figures below). Essentially follow the [http://en.wikipedia.org/wiki/Human_interface_guidelines Human interface guidelines] and mind your users (and where they come from - think newcomers to the GRASS world - "Don't Limit Your User Base" by being too different from others). If at all possible, this should be implemented as a ''skin'' to give users the choice to also use wxGUI as Multiple Document Interface (MDI, i.e, the wxGUI windows reside under a single parent window). More [[WxGUI#Layout|here]].

<center>
{|
| [[Image:Wxgui_current.png|325px|thumb|center|Current wxGUI layout with detached window components]]
||
| [[Image:Wxgui_proposal.png|200px|thumb|center|Proposal for wxGUI layout modification (Recomposition of existing toolbars, mapview and menus)]]
|}
</center>

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

* Develop a [[WxPython-based_GUI_for_GRASS#Cartography_tools|graphical cartographic module]] GUI front-end for {{cmd|ps.map}}
: ''Willing to co-mentor: H.Bowman'' for ps.map advice but need to find a lead mentor who knows wxGRASS

* Develop a GUI module in wxPython for creating animations from multiple maps and saving animation outputs to animated GIF, MOV, or MPEG files. See existing modules {{cmd|xganim}}, {{cmd|r.out.mpeg}}, and {{cmd|nviz}}'s animation tools.

* Implement [[wxGUI#Graphical_modeller|graphical modeller]].

=== Raster ===

* Implement [[OpenMP]] (multithreading) as much as possible
** 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

* ''Your idea here''

-- 
'''Willing to Mentor:''' (''your name here'')

=== Vector ===

* Large vector maps: Currently a few modules which are important for massive datasets (like LIDAR data) are able to operate on maps which do not have topology built. (thus avoiding the associated per-feature memory overheads) It would be great if more modules could speak to these big-but-dumb maps (starting with {{cmd|v.info}}). This probably isn't enough for a full SoC project, so in addition the vector engine should be audited for places where memory optimization could take place.

* Add OpenMP parallelization where appropriate. See above idea in the Raster section.

* Better support for wrap-around at 180 longitude: Currently the raster engine is pretty good at wrapping data over 180 longitude. The vector data isn't, but it should be. This is a great task if by the end of the summer you'd like to be familiar with the implementation method of an entire vector stack of a fully featured modern GIS.

* ''Your idea here''
-- 
'''Willing to Mentor:''' (''your name here'')

=== Imagery ===

* GRASS's imagery modules (for satellite, scanned maps, and orthophotos) act as enhanced raster modules. In GRASS 5 and 6 they were mostly implimented using interactive X-monitors which are not available in MS Windows and so are removed in the new cross-platform code of GRASS 7.
** We need someone willing to port the old modules to work with GRASS 7, including writing new wxPython GUI frontends to a number of existing tools and updating the imagery libraries to current raster library standards.
** In addition, there are a number of improved/automated georectification tools which have not been merged into GRASS 5/6 which it would be nice to have updated and merged into the main code.

* Implement [[OpenMP]] (multithreading) as much as possible

See the [[Image_processing#Ideas_collection_for_improving_GRASS.27_Image_processing_capabilities|Ideas for imagery improvement]] and [[GRASS_7_ideas_collection#Imagery|GRASS 7 ideas]] wiki pages for more details.

'''Willing to Mentor:''' (''your name here'')

=== Other ===

* Design system for building manual pages based on [http://docbook.org DocBook] system

* 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 text displaying and styling in OGSF library and it's front-ends (NVIZ, wxNVIZ). Solution should be user configurable (fonts, colors, effects etc.) and multilanguage friendly.

* Design and implement user-provided symbol support in OGSF library and it's front-ends (NVIZ, wxNVIZ). Solution should support GRASS symbols and/or SVG symbols.

* '''''Zap-a-bug!''''': There are many old and neglected bugs in the [http://grass.osgeo.org/bugtracking/index.php three bug tracker(s)]. Reach 100 points by the end of the summer:
** trival bugs are 1 point
** minor bugs are 2 points
** normal bugs are 3 points
** major bugs are 4 points
** critical bugs are 7 points
** blocker bugs are 10 points
: Rules: Bugs must be in the tracker before I thought of this idea (13 March 2010) and priority is counted from that time as well. (exemptions may be given for fixing wishes and newly reported critical|blocker bugs ''only'' with prior permission of both your mentor and co-mentor). Points for fixing old wishes may be allocated at the discretion of your mentor (but no more than 10pts per wish). The bug fix '''must''' include a code patch, and your mentor is explicitly responsible for deciding when a bug is done and marking it as "fixed" in the trac system, not you. You get no points for bugs fixed before the SoC officially starts, but it could impress the judges and allow you to get in enough practice to hit the ground running. Good sense of humor, communication skills, and a thick skin are a must, as you will not be working in isolation. Students who are officially enrolled at their university and the SoC program with the given name of "Frank" or "Anonymous" (or obvious lingual/gender equivalent) will start the summer with an automatic 10 points. Members of the dev team with SVN write access may award 1 bonus point per week for any bug fixed within that week if they are especially impressed with your solution.
: (A great way to learn the entire GIS and get to know the dev team!)

== Guidelines for Students ==

How do you maximize your chances of getting picked? First read the [http://code.google.com/p/google-summer-of-code/wiki/AdviceforStudents Google SoC FAQ]. Then talk to us about your idea. Try emailing [http://lists.osgeo.org/mailman/listinfo/grass-dev our dev-mailing list], or come and talk to us in [[IRC]] (#grass). You can also reach the mentors directly by emailing:
* [http://lists.osgeo.org/mailman/listinfo/soc The OSGeo SoC mailing list]
* Wolf Bergenheim (wolf+grass@bergenheim.net)

=== Getting started with GRASS coding ===

* The source code is maintained in a [http://trac.osgeo.org/grass/browser/grass/trunk SVN server] which is easy to browse
: Please review the [http://svn.osgeo.org/grass/grass/trunk/SUBMITTING SUBMITTING] files there for our coding standards.

* There is lots of good info at the [http://trac.osgeo.org/grass/wiki GRASS Developer's wiki]
: See also the [[Development|development section]] of the GRASS user's wiki

== Accepted Ideas ==

* TBD


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

GRASS SoC Ideas 2010

2010-03-10T04:39:53Z

⚠️Helena: /* wxGUI */