GRASS-Wiki - User contributions [en]

Talk:GRASS Community Meeting Prague 2023

2023-06-06T10:31:45Z

⚠️MarisN: /* Maris Nartiss */ What has been done so far

__TOC__

== Tasks for participants ==

* Create section for you in the Reports section.
* List all the things you are working on in the section. Update the list each day. Include things you work on with other people.
* Link the [https://github.com/orgs/OSGeo/projects/1/ GRASS Community Meeting Prague 2023] project on GitHub to each PR or issue you are working on or plan to be working on.
* If you are or will be working on an issue or on a PR which is not originally submitted by you, assign yourself to the issue or PR. (You can unassign yourself later if you change your mind.)

== Planning and organizing ==

* Initial planning: Veronica Andreo, Martin Landa, Vaclav Petras, Helmut Kudrnovsky, Anna Petrasova, Huidae Cho, Markus Neteler, Helena Mitasova, Micha Silver, Linda Kladivova
* Funding acquisition: Veronica Andreo, Markus Neteler, Vaclav Petras, Anna Petrasova, Huidae Cho, Luca Delucchi, Venkatesh Raghavan
* Budget: Vaclav Petras, Markus Neteler, Veronica Andreo
* Venue and local organizing: Martin Landa, helpers: Ondrej Pesek, Vaclav Petras
* T-shirts, hoodies, stickers: Vaclav Petras, Anna Petrasova
* Promotion, invitations, and social media: Caitlin Haedrich, Veronica Andreo, Vaclav Petras
* Wiki page: Martin Landa, Markus Neteler, Vaclav Petras, Veronica Andreo
* Virtual meeting organizing: Veronica Andreo
* Photography: Caitlin Haedrich, Maris Nartiss

== Ideas for the meeting agenda ==

Collect ideas here :-)

=== Markus Neteler ===

* Improve QGIS-GRASS GIS integration; update of provider to GRASS GIS 8
* GRASS GIS addons overview generator for entire GitHub (and more?) based on tag "[https://github.com/topics/grass-gis-addons grass-gis-addons]"
* Discuss about a 4th edition of "Open Source GIS: A GRASS GIS Approach"
* message translation: Easy [https://docs.weblate.org/en/latest/user/translating.html#machine-translation machine translation] of messages in [https://weblate.osgeo.org/translate/grass-gis OSGeo-Weblate] with DeepL API
** my tests with DeepL show that the quality is very good; average translation time of a user message shrinks to 15 seconds {{done}}
** note: one needs to login to Weblate to see the "Automatic suggestion" button (using the OSGeo-ID)
* Fix docs:
** Provide better explanation for radius parameter for r.resamp.filter: https://github.com/OSGeo/grass/issues/2569
** improve v.clean docs

=== Vero ===

* '''All - think about GRASS GIS mission and vision''': Where do we want to be as a project in 5 years time? What do we want to have? What do we want to be?
* Participate in discussions about GRASS interfaces with QGIS and R (rgrass)
* Discuss sponsoring
* Student grant for (python) documentation?
* Discuss about wiki clean-up/update (Anna was working on a list of pages)
* Website enhancements: complete open PR's, meet Daniel Torres, new support item in main menu
* Discuss State of GRASS presentation for FOSS4G 2023
* i.landsat if time permits
* ...

=== You ===

== Reports ==

=== Caitlin Haedrich ===
* Photos, social media and wiki page
* grass.jupyter:
** [https://github.com/OSGeo/grass/pull/2996 add feature for animating series of rasters]

=== Vaclav Petras ===

* Rename location to project
** [https://github.com/OSGeo/grass/pull/2993 wxGUI: Rename location to project #2993]
** Discussion
* Python API
** [https://github.com/OSGeo/grass/pull/2923 grass.experimental: Add object to access modules as functions #2923]
* CI
** [https://github.com/OSGeo/grass/pull/3002 CI: Switch Travis to Ubuntu 22.04 (jammmy) #3002]
* Reviews and merges:
** [https://github.com/OSGeo/grass/pull/2974 t.rast.algebra/testsuite: split file test_raster_algebra.py #2974]
** [https://github.com/OSGeo/grass/pull/2189 Imagery: add libsvm based imagery classification #2189]
** [https://github.com/OSGeo/grass-addons/pull/606 r.random.walk: Add module to create random walks #606]

=== Anna Petrasova ===
* [https://github.com/OSGeo/grass/pull/2992 Fix bug in querying]
* review, merge and backport of [https://github.com/OSGeo/grass/pull/2994 fix in datacatalog]
* review of [https://github.com/OSGeo/grass/pull/2520 wxGUI: fix show MASK statusbar button widget if mask is created]
* merge of [https://github.com/OSGeo/grass/pull/2667 wxGUI: adding a button for undocking an AuiNotebook tab to wx.Frame (Single-Window GUI)]
* edit [https://github.com/OSGeo/grass/pull/2990 check min required wx version when starting wxgui]

=== Maris Nartiss ===

* i.svm.* cleanup and preparation for a review
* A conceptual proposal for a new start up screen
* Initial version of imagery signature management module i.signatures
* Remove obsolete parts of locale README file
* Extract translatable messages also from C++ files
* Improve parser library documentation

=== Micha Silver ===
Working on a new GRASS addon: r.optram
[https://github.com/micha-silver/grass-addons/tree/grass8/src/raster/r.optram the repo on github]

02/06: Initialize main file ''r.optram.py''

includes these functions:
# ''getImgList()'' - get list of IMG_FILEs in a Sentinel 2 SAFE Directory
# ''cropToAOI()'' - Crop the images to the Area of Interest
# ''prepareSTR()'' - Convert SWIR to the SWIR Transformed Reflectance
# ''prepareVI()'' - Prepare the (user chosen) vegetation index

03/06:
# Split to three modules: '''r.optram.preprocess, r.optram, r.optram.soilmoisture'''
# new function: ''prepareTrapezoid()'' - to get wet-dry regression lines and slope, intercept values

04/06
# ''prepareTrapezoid()'' function completed.
# (Joined video conf with Roger Bivand on R-GRASS integration.)

05/06
Initialize third file/function: ''r.optram.soilmoisture.py''
# ''createSoilMoisture()'' - creates new GRASS raster for a single date
# Add documentation to modules
# (joined video conf with Nyall Dawson)

TODO list:
* Read Sentinel cloud mask and mask out cloud pixels in '''r.optram.preprocess'''
* large study areas or very long time series will create a big numpy table of variables (vegetation index and STR). A possible solution:
# Determine some "reasonable" maximum size for the numpy table, depending on computer resources.
# Extract a subset of pixels from each raster in the time series, such that the total table pixel values will not exceed that maximum
# The size of the subset will be set by ("reasonable" max / number of rasters in time series)
# Allow user to determine "reasonable" max.
* Currently this addon consists of three sub-modules. Consider to consolidate to one.
* Improve HTML documentation

=== Luís de Sousa ===

==== Work on GRASS add-on [https://grass.osgeo.org/grass82/manuals/addons/r.mblend.html r.mblend] ====

* Module is still maintained and fully functional in GRASS 8.2 (now included in the [https://github.com/OSGeo/grass-addons GRASS global add-ons repository])
* However was not longer producing correct results due to new behaviour in '''v.what.rast'''
* Solution identified, using inner buffer to interpolation area ([https://github.com/OSGeo/grass-addons/pull/910 PR #910])
* A small unit test suite was developed ([https://github.com/OSGeo/grass-addons/pull/911 PR #911])

==== Documentation ====

* Expanded instructions on Pre-commit ([https://github.com/OSGeo/grass/pull/3006 PR #3006])
* Mini guidelines on unit tests for add-ons ([https://github.com/OSGeo/grass-addons/pull/916 PR #916])

=== Aaron Saw Min Sern ===

* Fix bug to complete r.univar parallelization. [https://github.com/OSGeo/grass/pull/2683 PR]

=== Martin Landa ===

* Check min required wx version when starting wxgui [https://github.com/OSGeo/grass/pull/2990 PR #2990]
* Graphical modeler: avoid overlapping module parameters [https://github.com/OSGeo/grass/issues/2991 PR #2991]
* Show ModelRelation in white on dark mode [https://github.com/OSGeo/grass/pull/2997 PR #2997]
* Add OSGeo4W workflow to compile Addons [https://github.com/OSGeo/grass-addons/pull/912 PR #912]
* Integrate Grapical Modeler into single window layout [https://github.com/OSGeo/grass/pull/3003 PR #3003]
* Graphical Modeler: fix command parsing in "add tool" dialog [https://github.com/OSGeo/grass/pull/3022 PR #3022]
* Describe required updates for new version for winGRASS [https://github.com/OSGeo/grass/issues/2406#issuecomment-1578303935 #2406]

=== Markus Neteler ===

* backport of "HTML header charset changed from ISO-8859-1 to UTF-8" [https://github.com/OSGeo/grass/pull/2547 PR #2547] to GRASS GIS 8.2.1 (fixing r.forcircular manual encoding bug)
* improve "Update alpine Docker tag to v3.18 [https://github.com/OSGeo/grass/pull/2953 PR #2953]
* backport of Alpine Dockerfile improvements
* discussion about "location/mapset" vs "project/..." terminology
* initial QGIS-GRASS update discussion
* Google Photo album feeds
* Use of [https://github.com/OSGeo/grass/blob/main/doc/development/submitting/submitting.md#use-pre-commit pre-commit] (recommended to all devs!)
* Participate in a two-hour meeting with Nyall Dawson (QGIS) and the GRASS Community about interfacing GRASS from QGIS
*
* GRASS GIS manual pages: re-styling and conversion of all pages to markdown:
** convert to markdown with pandoc (draft script see https://app.gitter.im/#/room/#grassgis_sprint:gitter.im discussion)
** using mkdocs (https://www.mkdocs.org/): it provides menus and a search window
** check: automatic formatting for mkdocs: https://github.com/KyleKing/mdformat-mkdocs

[[Image:Grass manual readthedocs.png|First attempt to convert the manual to Markdown/mkdocs|500px]]

=== Helmut Kudrnovsky ===

* discuss (win)GRASS-R issues [https://github.com/rsbivand/rgrass/issues/57 initGrass Error] and [https://github.com/OSGeo/grass/issues/2998 feature requests]

* Review and initial tests of PR [https://github.com/OSGeo/grass/pull/2684 compilation with cmake] on Windows

* Participated in a two-hour meeting with Roger, Floris, Vaclav, Anna, Micha, ..... about rgrass development

=== Ondřej Pešek ===

* gmodeler: add export to an actinia script: [https://github.com/OSGeo/grass/pull/3005 PR #3005]
* fix GRASS GIS broken for Python 3.12: [https://github.com/OSGeo/grass/pull/3009 PR #3009], [https://github.com/OSGeo/grass/pull/3010 PR #3010], [https://github.com/OSGeo/grass/pull/3011 PR #3011], [https://github.com/OSGeo/grass/pull/3018 PR #3018]
* fix GRASS GIS addons broken for Python 3.12: [https://github.com/OSGeo/grass-addons/pull/917 PR #917], [https://github.com/OSGeo/grass-addons/pull/918 PR #918], [https://github.com/OSGeo/grass-addons/pull/919 PR #919]

=== Floris Vanderhaeghe ===

* Explore reading straight from the GRASS database into R (https://github.com/rsbivand/rgrass/issues/75)
* Help Markus in improving the documentation of the GDAL-GRASS drivers (https://github.com/OSGeo/gdal-grass)
* Help arranging a meeting with Nyall Dawson for the QGIS GRASS interface
* Participate in a two-hour meeting with Roger Bivand, Vero Andreo, Vaclav, Anna, Helmut, Micha, ..... about rgrass development
* Draft and finalize the meeting minutes of the rgrass meeting
* Participate in a two-hour meeting with Nyall Dawson (QGIS) and the GRASS Community about interfacing GRASS from QGIS

=== Vero Andreo ===

* Participated in the discussion about renaming locations to projects
* Call with Paulo on diverse topics, r.niche.similarity PR revision and merge
* Participated in a two-hour meeting with Roger, Floris, Vaclav, Anna, Helmut, Micha, ..... about rgrass development
* Worked on GRASS Website:
** Apply fixes and merge the [https://github.com/OSGeo/grass-website/pull/362 DOI] and [https://github.com/OSGeo/grass-website/pull/364 first draft of sponsoring tiers] PRs
** Beautify tables and content of sponsoring page [https://github.com/OSGeo/grass-website/pull/368 #368]
** New menu and submenus (some reordered), please comment [https://github.com/OSGeo/grass-website/pull/369 #369]
** Created a news item about rgrass7 retirement with text snippet contributed by Roger Bivand [https://github.com/OSGeo/grass-website/pull/370 #370]
* Other minor revisions

=== Discussion with Nyall (QGIS) ===

* How to improve the integration
** save some of the existing code
** update "Processing" integration
** ...
* GRASS GIS Addon support in QGIS, see
** https://github.com/qgis/QGIS/pull/53048
** https://github.com/qgis/QGIS/pull/53049

GRASS Community Meeting Prague 2023

2023-06-06T08:51:55Z

⚠️MarisN: /* Sponsors */ SunGIS contribution

{{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''' (by contributing to GRASS GIS of course).

<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, OGC Services and desiring to '''celebrate with us the 40th GRASS GIS birthday!!'''

In this meeting, we will work on GRASS GIS and integrations with related OSGeo projects. We will revise connection to QGIS to make it easier to maintain, and we will work on migration of the build to CMake to improve Windows builds including PDAL support. Furthermore, we will start moving documentation to Markdown to make it easier to contribute to and we will add images and examples for tools and workflows which still miss them. Finally, we will automate and document maintenance processes to reduce the burden on maintainers and thus improve the project sustainability.

Note that while we have our general plan, we can't accept any earmarked donations, i.e., we can't make any promises for a specific work to be done. We do require participants to work on GRASS GIS or connections to other projects. However, we leave them the freedom to work on what they think is the best contribution to the project at that time given their skills and time available.

For the detailed agenda and individual's plans, 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 travel and accommodation expenses for GRASS developers who volunteer their time. If you are interested in sponsoring the GRASS Community Meeting, please see our

::: '''[https://opencollective.com/osgeo/projects/grass/contribute/grass-community-meeting-prague-2023-55074 OpenCollective GRASS Community Meeting Prague 2023 Tier]'''

Any surplus at the end of the event will used for future activities of the GRASS GIS project such as the successful [[Student Grants|student mini grant program]].

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:

[[File:Osgeo logo.png|none|left|alt=Light and dark green logo of OSGeo saying Your Open Source Compass|Open Source Geospatial Foundation]]
* [https://www.osgeo.org/ OSGeo]: 7303 USD (approved budget contribution, [https://www.loomio.com/p/2m75BZkL/motion-to-approve-7303-to-support-grass-gis-community-meeting motion])
* Twitter: [https://twitter.com/OSGeo/ @OSGeo] | [https://fosstodon.org/@osgeo @osgeo@fosstodon.org]

[[File:FOSSGIS_eV_logo.png|none|left|400px|alt=Logo of FOSSGIS e.V.|FOSSGIS e.V.]]
* [https://www.fossgis.de/ FOSSGIS e.V.]: 5000 EUR (approved budget contribution, [https://www.fossgis.de/wiki/F%C3%B6rderantr%C3%A4ge/GRASS_GIS_Community_Meeting_2023 request])
* Twitter: [https://twitter.com/FOSSGIS_Verein @FOSSGIS_Verein] | [https://mastodon.online/@FOSSGISeV/ @FOSSGISeV@mastodon.online]

[[File:OSGeo JP logo for web.png|none|left|400px|alt=OSGeo.JP]]
* [https://www.osgeo.jp/ OSGeo Japan]: 550 USD (through Open Collective)

Individuals:
* Hernán De Angelis 20 USD
* MarWe 50 USD
* Nick Brady 50 USD
* José Ramón 50 USD
* Johannes Brauner 30 USD
* Peter Löwe 30 USD
* Evan Kay 10 USD
* Joaquin Perez Valera 5 USD
* Anonymous sponsors 2750 USD

In-kind contributions:

* Department of Geomatics Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU) - space and personnel time (planning, preparation, participation)
* North Carolina State University, Center for Geospatial Analytics - personnel time (planning, preparation, participation)
* mundialis GmbH & Co. KG - personnel time (planning, preparation, participation)
* CONICET - personnel time (planning, preparation)
* Research Institute for Nature and Forest (INBO | Brussels, Belgium) – personnel time + travel and hotel costs of INBO staff
* SunGIS – travel and hotel costs of Maris Nartiss

Personal time and/or financial contributions:
* Martin Landa, Micha Silver, Helmut Kudrnovsky, Markus Neleter, Ondřej Pešek, Helena Mitasova, Vaclav Petras, Anna Petrasova, Corey White, Maris Nartiss, Aaron Saw Min Sern, Luís de Sousa, Caitlin Haedrich, Linda Kladivová, Carmen Tawalika, Floris Vanderhaeghe, Brendan Harmon, Veronica Andreo, Daniel Torres, Loïc Bartoletti

== 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, reimbursements depending on the financial contributions provided by the community
* 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 ===

(agenda is under development, but also flexible)

==== Thursday, 1 June ====

* Arrival

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

* 9:00 meeting starts in the room B-868
* Lunch: 12:45 NTK
* Review the plan for the next days
* API for use in Python and in other projects (e.g., QGIS)
* Parallelizations

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

* Reducing cost of distribution on Windows
* Convert GRASS GIS documentation from HTML to Markdown and implement new documentation system (mkdocs?)
* Group photo 1
* Outdoor social evening

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

* Compilation CMake (Windows, Linux)
* Connections in general, rgrass, qgisprocess
* GRASS GIS addons overview generator for entire GitHub (and more?) based on tag "[https://github.com/topics/grass-gis-addons grass-gis-addons]"
* Group photo 2

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

* Connections in general, QGIS, rgrass, qgisprocess
* Parallelizations
* grass.jupyter

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

* Connections in general, QGIS
* Parallelizations
* grass.jupyter

==== Wednesday, 7 June ====

* Departure

=== Social events ===

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

Dinner at 7pm: [https://www.uveverky.com/kontakt/ U veverku pub] ([https://en.mapy.cz/s/jumomotupu map])

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

Dinner at 6pm: [https://unetickypivovar.cz/en Únětický pivovar] ([https://en.mapy.cz/s/mubutetoba map])

* 3:50pm train from Podbaba (15min walk) to Roztoky
* [https://en.mapy.cz/s/dabavojufa walk 1:30min]
* Bus (355) back from Unetice to Dejvicka: 21:57 or 23:18

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

Dinner at 7pm: [https://www.restauracevltava.cz/ Restaurace Vltava] ([https://en.mapy.cz/s/gonezofozo map])

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

Dinner at 7pm: [https://www.my-paprika.com/ My Paprika] ([https://en.mapy.cz/s/modekehepu map])

* Tram 26 from Dejvicka to Strossmayerovo namesti at 6:26pm

== 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'''
!'''Notes'''
|-
|1
|[[User:Landa|Martin Landa]]
| Czech Republic
| June 1
| June 7
| Python: create_location ([https://github.com/OSGeo/grass/issues/1987 #1987]), Graphical Modeler improvements and single window layout integration
|
|-
|2
| Micha Silver
| Israel
| June 2
| June 6
| Addon to derive soil moisture from Sentinel 2
|
|-
|3
|[https://www.osgeo.org/member/kudrnovsky/ Helmut Kudrnovsky]
| Austria
| June 2 (18:37) by train
| June 4 (18:24) by train
| support CMake transition
|
|-
|4
|[[User:Neteler|Markus Neteler]]
| Germany
| June 2 (17:17)
| June 6 (12:43)
| translations, manual pages, ..., see [[Talk:GRASS_Community_Meeting_Prague_2023#Markus_Neteler|my list in "Discussion" page]]
|
|-
|5
|[[User:pesekon2|Ondřej Pešek]]
| Czech Republic
| June 2 (17:17)
| June 6 (12:43)
| Python 3.12-connected issues, gmodeler
|
|-
|6
| [[User:helena|Helena Mitasova]]
| United States
| June 2
| June 6
|
|
|-
|7
| [[User:wenzeslaus|Vaclav Petras]]
| United States
| June 1
| June 7
| init and other Python API topics, support CMake transition, revise connection with QGIS and other tools, funding
|
|-
|8
| [[User:Annakrat|Anna Petrasova]]
| United States
| June 1
| June 7
| parallelization documentation, grass.jupyter, R and QGIS integration
|
|-
|9
| [[User:Ctwhite|Corey White]]
| United States
| June 2 (10:55)
| June 7
| Connections with other tools, OpenPlains, JSON outputs
|
|-
|10
| [[User:MarisN|Maris Nartiss]]
| Latvia
| June 2 (14:30)
| June 6 (12:00)
| Improvements of imagery modules (push i.svm.*; i.signatures; ?)
|-
|11
| [[User:Aaronsms|Aaron Saw Min Sern]]
| Singapore
| June 1
| June 7
| Support CMake transition, r.mapcalc parallelization
|
|-
|12
| [[User:Ldesousa|Luís de Sousa]]
| The Netherlands
| June 1 (20:00)
| June 5 (20:45)
| Update r.mblend add-on; test CMake transition.
|
|-
|13
| Caitlin Haedrich
| United States
| June 1
| June 7
| grass.jupyter
|
|-
|14
| Linda Kladivová
| Czech Republic
| June 2
| June 6
| Single-Window layout issues and improvements
|
|-
|15
| Carmen Tawalika
| Germany
| June 2 (17:17)
| June 6 (12:43)
| Happy to assist with general topics like documentation + automation, in doubt something related to actinia
|
|-
|16
| Floris Vanderhaeghe
| Belgium
| June 3 (train 19:17)
| June 6 (train 8:25)
| Helping in interfacing GRASS from R (rgrass & qgisprocess packages)
|
|-
|}

If you are arriving or departing on the days of the event, please specify the time, too.

=== Via chat or hangout ===

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

Gitter has a video (and backup will be Zoom).

Participating virtually:

{|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'''
!'''Topics'''
!'''Times, synchronous or fully asynchronous'''
!'''Notes'''
|-
|1
|[[User:Baharmon|Brendan Harmon]]
| United States
| Update integration with QGIS
| Available 8:00 AM CST (UTC-6) onwards
|
|-
|2
|[[User:veroandreo|Veronica Andreo]]
| Argentina
| Mission and vision, interfaces with QGIS and R, sponsoring, ... [https://grasswiki.osgeo.org/wiki/Talk:GRASS_Community_Meeting_Prague_2023#Vero see discussion tab]
| available from 8:00 AM ART (UTC-3) onward
|
|-
|3
|[[User:Nobeeakon|Daniel T]]
| Mexico
|
| some availability through the days :/
|
|-
|4
|[[User:LBartoletti|Loïc Bartoletti]]
| France
| QGIS Integration, support CMake transition
|
|-
|}

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

Follow Gitter.

=== Collaborative document scratching ===

Follow Gitter.

== 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 git and the compiler tools, and come with a working GRASS development environment if possible.

== Broadcast & Video ==

During the event :) Find the latest information on the [https://matrix.to/#/#grassgis_sprint:gitter.im Gitter Channel].

== Photos ==
Day 1
<gallery mode="slideshow">
Image:Devs at work.jpg|Hard at work on the first day
Image:Lively discussion.jpg|Lively discussion
Image:Dinner day 1.jpg|Dinner at a nearby pub
</gallery>

Day 2
<gallery mode="slideshow">
Image:Prague-Community-Meeting-2023.jpg|Group photo
Image:PXL 20230603 085440353.jpg|A full table on day 2
Image:GRASS-smiles.jpg|GRASS GIS development brings smiles
Image:Day2-pizza.jpg|Pizza fuels work!
Image:Day2-collaboration.jpg|Afternoon working and collaborating
Image:Group-photo-hike.jpg|View at Alšova vyhlídka on the way to Únětický pivovar (brewery)
Image:Únětický pivovar.jpg|Beer at Únětický pivovar, a 300-year-old brewery, after a day of hard work
</gallery>

Day 3
<gallery mode="slideshow">
Image:Day3-working.jpg|Working on new features, bug fixes, documentation and more..
Image:Day3-table.jpg|An even fuller table on day 3
Image:Day3-collaboration.jpg|Collaboration and discussion
Image:Beer-pano-day3.jpg|Panoramic photo of a cheers to GRASS's 40th Birthday at Vitala restaurant
</gallery>

Day 4
<gallery mode="slideshow">
Image:Group-photo2-day4.jpg|Group photo on Day 4 on the steps of CVUT Praha
Image:Qgis-call-day4.jpg|Discussing QGIS integration
Image:Toast-grass-40th-birthday.jpg|A toast to GRASS GIS's 40th Birthday and a successful meeting
Image:Beer-and-work-day4.jpg|The work and discussion continues over dinner
</gallery>

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

== Report and press release ==

TBD: After the event :-)

We'll esp. craft a report for our sponsors.

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

Talk:GRASS Community Meeting Prague 2023

2023-06-06T08:39:45Z

⚠️MarisN: /* Maris Nartiss */ What has been done so far

__TOC__

== Tasks for participants ==

* Create section for you in the Reports section.
* List all the things you are working on in the section. Update the list each day. Include things you work on with other people.
* Link the [https://github.com/orgs/OSGeo/projects/1/ GRASS Community Meeting Prague 2023] project on GitHub to each PR or issue you are working on or plan to be working on.
* If you are or will be working on an issue or on a PR which is not originally submitted by you, assign yourself to the issue or PR. (You can unassign yourself later if you change your mind.)

== Planning and organizing ==

* Initial planning: Veronica Andreo, Martin Landa, Vaclav Petras, Helmut Kudrnovsky, Anna Petrasova, Huidae Cho, Markus Neteler, Helena Mitasova, Micha Silver, Linda Kladivova
* Funding acquisition: Veronica Andreo, Markus Neteler, Vaclav Petras, Anna Petrasova, Huidae Cho, Luca Delucchi, Venkatesh Raghavan
* Budget: Vaclav Petras, Markus Neteler, Veronica Andreo
* Venue and local organizing: Martin Landa, helpers: Ondrej Pesek, Vaclav Petras
* T-shirts, hoodies, stickers: Vaclav Petras, Anna Petrasova
* Promotion, invitations, and social media: Caitlin Haedrich, Veronica Andreo, Vaclav Petras
* Wiki page: Martin Landa, Markus Neteler, Vaclav Petras, Veronica Andreo
* Virtual meeting organizing: Veronica Andreo
* Photography: Caitlin Haedrich, Maris Nartiss

== Ideas for the meeting agenda ==

Collect ideas here :-)

=== Markus Neteler ===

* Improve QGIS-GRASS GIS integration; update of provider to GRASS GIS 8
* GRASS GIS addons overview generator for entire GitHub (and more?) based on tag "[https://github.com/topics/grass-gis-addons grass-gis-addons]"
* Discuss about a 4th edition of "Open Source GIS: A GRASS GIS Approach"
* message translation: Easy [https://docs.weblate.org/en/latest/user/translating.html#machine-translation machine translation] of messages in [https://weblate.osgeo.org/translate/grass-gis OSGeo-Weblate] with DeepL API
** my tests with DeepL show that the quality is very good; average translation time of a user message shrinks to 15 seconds {{done}}
** note: one needs to login to Weblate to see the "Automatic suggestion" button (using the OSGeo-ID)
* Fix docs:
** Provide better explanation for radius parameter for r.resamp.filter: https://github.com/OSGeo/grass/issues/2569
** improve v.clean docs

=== Vero ===

* '''All - think about GRASS GIS mission and vision''': Where do we want to be as a project in 5 years time? What do we want to have? What do we want to be?
* Participate in discussions about GRASS interfaces with QGIS and R (rgrass)
* Discuss sponsoring
* Student grant for (python) documentation?
* Discuss about wiki clean-up/update (Anna was working on a list of pages)
* Website enhancements: complete open PR's, meet Daniel Torres, new support item in main menu
* Discuss State of GRASS presentation for FOSS4G 2023
* i.landsat if time permits
* ...

=== You ===

== Reports ==

=== Caitlin Haedrich ===
* Photos, social media and wiki page
* grass.jupyter:
** [https://github.com/OSGeo/grass/pull/2996 add feature for animating series of rasters]

=== Vaclav Petras ===

* Rename location to project
** [https://github.com/OSGeo/grass/pull/2993 wxGUI: Rename location to project #2993]
** Discussion
* Python API
** [https://github.com/OSGeo/grass/pull/2923 grass.experimental: Add object to access modules as functions #2923]
* CI
** [https://github.com/OSGeo/grass/pull/3002 CI: Switch Travis to Ubuntu 22.04 (jammmy) #3002]
* Reviews and merges:
** [https://github.com/OSGeo/grass/pull/2974 t.rast.algebra/testsuite: split file test_raster_algebra.py #2974]
** [https://github.com/OSGeo/grass/pull/2189 Imagery: add libsvm based imagery classification #2189]
** [https://github.com/OSGeo/grass-addons/pull/606 r.random.walk: Add module to create random walks #606]

=== Anna Petrasova ===
* [https://github.com/OSGeo/grass/pull/2992 Fix bug in querying]
* review, merge and backport of [https://github.com/OSGeo/grass/pull/2994 fix in datacatalog]
* review of [https://github.com/OSGeo/grass/pull/2520 wxGUI: fix show MASK statusbar button widget if mask is created]
* merge of [https://github.com/OSGeo/grass/pull/2667 wxGUI: adding a button for undocking an AuiNotebook tab to wx.Frame (Single-Window GUI)]
* edit [https://github.com/OSGeo/grass/pull/2990 check min required wx version when starting wxgui]

=== Maris Nartiss ===

* i.svm.* cleanup and preparation for a review
* A conceptual proposal for a new start up screen
* Initial version of imagery signature management module i.signatures
* Remove obsolete parts of locale README file
* Extract translatable messages also from C++ files

=== Micha Silver ===
Working on a new GRASS addon: r.optram
[https://github.com/micha-silver/grass-addons/tree/grass8/src/raster/r.optram the repo on github]

02/06: Initialize main file ''r.optram.py''

includes these functions:
# ''getImgList()'' - get list of IMG_FILEs in a Sentinel 2 SAFE Directory
# ''cropToAOI()'' - Crop the images to the Area of Interest
# ''prepareSTR()'' - Convert SWIR to the SWIR Transformed Reflectance
# ''prepareVI()'' - Prepare the (user chosen) vegetation index

03/06:
# Split to three modules: '''r.optram.preprocess, r.optram, r.optram.soilmoisture'''
# new function: ''prepareTrapezoid()'' - to get wet-dry regression lines and slope, intercept values

04/06
# ''prepareTrapezoid()'' function completed.
# (Joined video conf with Roger Bivand on R-GRASS integration.)

05/06
Initialize third file/function: ''r.optram.soilmoisture.py''
# ''createSoilMoisture()'' - creates new GRASS raster for a single date
# Add documentation to modules
# (joined video conf with Nyall Dawson)

TODO list:
* Read Sentinel cloud mask and mask out cloud pixels in '''r.optram.preprocess'''
* large study areas or very long time series will create a big numpy table of variables (vegetation index and STR). A possible solution:
# Determine some "reasonable" maximum size for the numpy table, depending on computer resources.
# Extract a subset of pixels from each raster in the time series, such that the total table pixel values will not exceed that maximum
# The size of the subset will be set by ("reasonable" max / number of rasters in time series)
# Allow user to determine "reasonable" max.
* Currently this addon consists of three sub-modules. Consider to consolidate to one.
* Improve HTML documentation

=== Luís de Sousa ===

==== Work on GRASS add-on [https://grass.osgeo.org/grass82/manuals/addons/r.mblend.html r.mblend] ====

* Module is still maintained and fully functional in GRASS 8.2 (now included in the [https://github.com/OSGeo/grass-addons GRASS global add-ons repository])
* However was not longer producing correct results due to new behaviour in '''v.what.rast'''
* Solution identified, using inner buffer to interpolation area ([https://github.com/OSGeo/grass-addons/pull/910 PR #910])
* A small unit test suite was developed ([https://github.com/OSGeo/grass-addons/pull/911 PR #911])

==== Documentation ====

* Expanded instructions on Pre-commit ([https://github.com/OSGeo/grass/pull/3006 PR #3006])
* Mini guidelines on unit tests for add-ons ([https://github.com/OSGeo/grass-addons/pull/916 PR #916])

=== Aaron Saw Min Sern ===

* Fix bug to complete r.univar parallelization. [https://github.com/OSGeo/grass/pull/2683 PR]

=== Martin Landa ===

* Check min required wx version when starting wxgui [https://github.com/OSGeo/grass/pull/2990 PR #2990]
* Graphical modeler: avoid overlapping module parameters [https://github.com/OSGeo/grass/issues/2991 PR #2991]
* Show ModelRelation in white on dark mode [https://github.com/OSGeo/grass/pull/2997 PR #2997]
* Add OSGeo4W workflow to compile Addons [https://github.com/OSGeo/grass-addons/pull/912 PR #912]
* Integrate Grapical Modeler into single window layout [https://github.com/OSGeo/grass/pull/3003 PR #3003]
* Graphical Modeler: fix command parsing in "add tool" dialog [https://github.com/OSGeo/grass/pull/3022 PR #3022]

=== Markus Neteler ===

* backport of "HTML header charset changed from ISO-8859-1 to UTF-8" [https://github.com/OSGeo/grass/pull/2547 PR #2547] to GRASS GIS 8.2.1 (fixing r.forcircular manual encoding bug)
* improve "Update alpine Docker tag to v3.18 [https://github.com/OSGeo/grass/pull/2953 PR #2953]
* backport of Alpine Dockerfile improvements
* discussion about "location/mapset" vs "project/..." terminology
* initial QGIS-GRASS update discussion
* Google Photo album feeds
* Use of [https://github.com/OSGeo/grass/blob/main/doc/development/submitting/submitting.md#use-pre-commit pre-commit] (recommended to all devs!)
* Participate in a two-hour meeting with Nyall Dawson (QGIS) and the GRASS Community about interfacing GRASS from QGIS
*
* GRASS GIS manual pages: re-styling and conversion of all pages to markdown:
** convert to markdown with pandoc (draft script see https://app.gitter.im/#/room/#grassgis_sprint:gitter.im discussion)
** using mkdocs (https://www.mkdocs.org/): it provides menus and a search window
** check: automatic formatting for mkdocs: https://github.com/KyleKing/mdformat-mkdocs

[[Image:Grass manual readthedocs.png|First attempt to convert the manual to Markdown/mkdocs|500px]]

=== Helmut Kudrnovsky ===

* discuss (win)GRASS-R issues [https://github.com/rsbivand/rgrass/issues/57 initGrass Error] and [https://github.com/OSGeo/grass/issues/2998 feature requests]

* Review and initial tests of PR [https://github.com/OSGeo/grass/pull/2684 compilation with cmake] on Windows

* Participated in a two-hour meeting with Roger, Floris, Vaclav, Anna, Micha, ..... about rgrass development

=== Ondřej Pešek ===

* gmodeler: add export to an actinia script: [https://github.com/OSGeo/grass/pull/3005 PR #3005]
* fix GRASS GIS broken for Python 3.12: [https://github.com/OSGeo/grass/pull/3009 PR #3009], [https://github.com/OSGeo/grass/pull/3010 PR #3010], [https://github.com/OSGeo/grass/pull/3011 PR #3011], [https://github.com/OSGeo/grass/pull/3018 PR #3018]
* fix GRASS GIS addons broken for Python 3.12: [https://github.com/OSGeo/grass-addons/pull/917 PR #917], [https://github.com/OSGeo/grass-addons/pull/918 PR #918], [https://github.com/OSGeo/grass-addons/pull/919 PR #919]

=== Floris Vanderhaeghe ===

* Explore reading straight from the GRASS database into R (https://github.com/rsbivand/rgrass/issues/75)
* Help Markus in improving the documentation of the GDAL-GRASS drivers (https://github.com/OSGeo/gdal-grass)
* Help arranging a meeting with Nyall Dawson for the QGIS GRASS interface
* Participate in a two-hour meeting with Roger Bivand, Vero Andreo, Vaclav, Anna, Helmut, Micha, ..... about rgrass development
* Draft and finalize the meeting minutes of the rgrass meeting
* Participate in a two-hour meeting with Nyall Dawson (QGIS) and the GRASS Community about interfacing GRASS from QGIS

=== Vero Andreo ===

* Participated in the discussion about renaming locations to projects
* Call with Paulo on diverse topics, r.niche.similarity PR revision and merge
* Participated in a two-hour meeting with Roger, Floris, Vaclav, Anna, Helmut, Micha, ..... about rgrass development
* Worked on GRASS Website:
** Apply fixes and merge the [https://github.com/OSGeo/grass-website/pull/362 DOI] and [https://github.com/OSGeo/grass-website/pull/364 first draft of sponsoring tiers] PRs
** Beautify tables and content of sponsoring page [https://github.com/OSGeo/grass-website/pull/368 #368]
** New menu and submenus (some reordered), please comment [https://github.com/OSGeo/grass-website/pull/369 #369]
** Created a news item about rgrass7 retirement with text snippet contributed by Roger Bivand [https://github.com/OSGeo/grass-website/pull/370 #370]
* Other minor revisions

=== Discussion with Nyall (QGIS) ===

* How to improve the integration
** save some of the existing code
** update "Processing" integration
** ...
* GRASS GIS Addon support in QGIS, see
** https://github.com/qgis/QGIS/pull/53048
** https://github.com/qgis/QGIS/pull/53049

Talk:GRASS Community Meeting Prague 2023

2023-06-04T14:24:05Z

⚠️MarisN: /* Maris Nartiss */ What has been done so far

Talk:GRASS Community Meeting Prague 2023

2023-06-04T12:57:09Z

⚠️MarisN: /* Maris Nartiss */ What has been done so far

Talk:GRASS Community Meeting Prague 2023

2023-06-03T09:02:48Z

⚠️MarisN: /* Maris Nartiss */ What has been done so far

Talk:GRASS Community Meeting Prague 2023

2023-06-02T14:05:59Z

⚠️MarisN: /* Reports */

GRASS Community Meeting Prague 2023

2023-05-18T07:53:04Z

⚠️MarisN: /* In person */ Arrival / departure times for MarisN

{{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''' (by contributing to GRASS GIS of course).

<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, OGC Services and desiring to '''celebrate with us the 40th GRASS GIS birthday!!'''

In this meeting, we will work on GRASS GIS and integrations with related OSGeo projects. We will revise connection to QGIS to make it easier to maintain, and we will work on migration of the build to CMake to improve Windows builds including PDAL support. Furthermore, we will start moving documentation to Markdown to make it easier to contribute to and we will add images and examples for tools and workflows which still miss them. Finally, we will automate and document maintenance processes to reduce the burden on maintainers and thus improve the project sustainability.

Note that while we have our general plan, we can't accept any earmarked donations, i.e., we can't make any promises for a specific work to be done. We do require participants to work on GRASS GIS or connections to other projects. However, we leave them the freedom to work on what they think is the best contribution to the project at that time given their skills and time available.

For the detailed agenda and individual's plans, 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 travel and accommodation expenses for GRASS developers who volunteer their time. If you are interested in sponsoring the GRASS Community Meeting, please see our

::: '''[https://opencollective.com/osgeo/projects/grass/contribute/grass-community-meeting-prague-2023-55074 OpenCollective GRASS Community Meeting Prague 2023 Tier]'''

Any surplus at the end of the event will used for future activities of the GRASS GIS project such as the successful [[Student Grants|student mini grant program]].

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:

[[File:Osgeo logo.png|none|left|alt=Light and dark green logo of OSGeo saying Your Open Source Compass|Open Source Geospatial Foundation]]
* OSGeo: 7303 USD (approved budget contribution, [https://www.loomio.com/p/2m75BZkL/motion-to-approve-7303-to-support-grass-gis-community-meeting motion])

[[File:FOSSGIS_eV_logo.png|none|left|400px|alt=Logo of FOSSGIS e.V.|FOSSGIS e.V.]]
* FOSSGIS e.V.: 5000 EUR

Individuals:
* MarWe 50 USD
* Nick Brady 50 USD
* Johannes Brauner 30 USD
* Joaquin Perez Valera 5 USD
* Anonymous sponsors 2750 USD

In-kind contributions:

* Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU) - space and personnel time (planning, preparation)
* North Carolina State University - personnel time (planning, preparation)
* mundialis GmbH & Co. KG - personnel time (planning, preparation)
* CONICET - personnel time (planning, preparation)

== 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, reimbursements depending on the financial contributions provided by the community
* 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 ===

(agenda is under development, but also flexible)

==== Thursday, 1 June ====

* Arrival

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

* 10:00 meeting starts in the room B-868
* Review the plan for the next days
* API for use in Python and in other projects (e.g., QGIS)
* Parallelizations

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

* Reducing cost of distribution on Windows
* Group photo 1

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

* Compilation CMake (Windows, Linux)
* Connections in general, rgrass, qgisprocess
* Group photo 2

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

* Connections in general, QGIS, rgrass, qgisprocess
* Parallelizations
* grass.jupyter

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

* Connections in general, QGIS
* Parallelizations
* grass.jupyter

==== Wednesday, 7 June ====

* Departure

== 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'''
!'''Notes'''
|-
|1
|[[User:Landa|Martin Landa]]
| Czech Republic
| June 1
| June 7
| Python: create_location ([https://github.com/OSGeo/grass/issues/1987 #1987]), Graphical Modeler improvements and single window layout integration
|
|-
|2
| Micha Silver
| Israel
| June 2
| June 6
| Addon to derive soil moisture from Sentinel 2
|
|-
|3
|[https://www.osgeo.org/member/kudrnovsky/ Helmut Kudrnovsky]
| Austria
| June 2 (18:37) by train
| June 4 (18:24) by train
| support CMake transition
|
|-
|4
|[[User:Neteler|Markus Neteler]]
| Germany
| June 2 (17:17)
| June 6 (12:43)
| translations, manual pages, ..., see [[Talk:GRASS_Community_Meeting_Prague_2023#Markus_Neteler|my list in "Discussion" page]]
|
|-
|5
|[[User:pesekon2|Ondřej Pešek]]
| Czech Republic
| June 2 (17:17)
| June 6 (12:43)
| Python 3.12-connected issues, gmodeler
|
|-
|6
| [[User:helena|Helena Mitasova]]
| United States
| June 2
| June 6
|
|
|-
|7
| [[User:wenzeslaus|Vaclav Petras]]
| United States
| June 1
| June 7
| init and other Python API topics, support CMake transition, revise connection with QGIS and other tools, funding
|
|-
|8
| [[User:Annakrat|Anna Petrasova]]
| United States
| June 1
| June 7
| parallelization documentation, grass.jupyter, R and QGIS integration
|
|-
|9
| [[User:Ctwhite|Corey White]]
| United States
| June 2 (10:55)
| June 7
| Connections with other tools, OpenPlains, JSON outputs
|
|-
|10
| [[User:MarisN|Maris Nartiss]]
| Latvia
| June 2 (14:30)
| June 6 (12:00)
| Improvements of imagery modules (push i.svm.*; i.signatures; ?)
|-
|11
| [[User:Aaronsms|Aaron Saw Min Sern]]
| Singapore
| June 1
| June 7
| Support CMake transition, r.mapcalc parallelization
|
|-
|12
| [[User:Ldesousa|Luís de Sousa]]
| The Netherlands
| June 1 (20:00)
| June 5 (20:45)
| Update r.mblend add-on; test CMake transition.
|
|-
|13
| Caitlin Haedrich
| United States
| June 1
| June 7
| grass.jupyter
|
|-
|14
| Linda Kladivová
| Czech Republic
| June 2
| June 6
| Single-Window layout issues and improvements
|
|-
|15
| Carmen Tawalika
| Germany
| June 2 (17:17)
| June 6 (12:43)
| Happy to assist with general topics like documentation + automation, in doubt something related to actinia
|
|-
|16
| Floris Vanderhaeghe
| Belgium
| June 3 (train 19:17)
| June 6 (train 8:25)
| Helping in interfacing GRASS from R (rgrass & qgisprocess packages)
|
|-
|}

If you are arriving or departing on the days of the event, please specify the time, too.

=== Via chat or hangout ===

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

TBD: Google Meet / Zoom / ???

Participating virtually:

{|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'''
!'''Topics'''
!'''Times, synchronous or fully asynchronous'''
!'''Notes'''
|-
|1
|[[User:Baharmon|Brendan Harmon]]
| United States
| Update integration with QGIS
|
|
|-
|2
|[[User:veroandreo|Veronica Andreo]]
| Argentina
| Mission and vision, interfaces with QGIS and R, sponsoring, ... [https://grasswiki.osgeo.org/wiki/Talk:GRASS_Community_Meeting_Prague_2023#Vero see discussion tab]
| available from 8:00 AM ART (UTC-3) onward
|
|-
|3
|[[User:Nobeeakon|Daniel T]]
| Mexico
|
| some availability through the days :/
|
|-
|4
|[[User:LBartoletti|Loïc Bartoletti]]
| France
| QGIS Integration, support CMake transition
|
|-
|}

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

Vero: available from 8:00 AM ART (UTC-3) onward

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

== Report and press release ==

TBD: After the event :-)

We'll esp. craft a report for our sponsors.

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

GRASS Community Meeting Prague 2023

2023-05-12T07:16:07Z

⚠️MarisN: /* In person */ Ideas for MarisN.

{{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''' (by contributing to GRASS GIS of course).

<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, OGC Services and desiring to '''celebrate with us the 40th GRASS GIS birthday!!'''

In this meeting, we will work on GRASS GIS and integrations with related OSGeo projects. We will revise connection to QGIS to make it easier to maintain, and we will work on migration of the build to CMake to improve Windows builds including PDAL support. Furthermore, we will start moving documentation to Markdown to make it easier to contribute to and we will add images and examples for tools and workflows which still miss them. Finally, we will automate and document maintenance processes to reduce the burden on maintainers and thus improve the project sustainability.

Note that while we have our general plan, we can't accept any earmarked donations, i.e., we can't make any promises for a specific work to be done. We do require participants to work on GRASS GIS or connections to other projects. However, we leave them the freedom to work on what they think is the best contribution to the project at that time given their skills and time available.

For the detailed agenda and individual's plans, 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 travel and accommodation expenses for GRASS developers who volunteer their time. If you are interested in sponsoring the GRASS Community Meeting, please see our

::: '''[https://opencollective.com/osgeo/projects/grass/contribute/grass-community-meeting-prague-2023-55074 OpenCollective GRASS Community Meeting Prague 2023 Tier]'''

Any surplus at the end of the event will used for future activities of the GRASS GIS project such as the successful [[Student Grants|student mini grant program]].

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:

[[File:Osgeo logo.png|none|left|alt=Light and dark green logo of OSGeo saying Your Open Source Compass|Open Source Geospatial Foundation]]
* OSGeo: 7303 USD (approved budget contribution, [https://www.loomio.com/p/2m75BZkL/motion-to-approve-7303-to-support-grass-gis-community-meeting motion])

[[File:FOSSGIS_eV_logo.png|none|left|400px|alt=Logo of FOSSGIS e.V.|FOSSGIS e.V.]]
* FOSSGIS e.V.: 5000 EUR

Individuals:
* MarWe 50 USD
* Nick Brady 50 USD
* Johannes Brauner 30 USD
* Joaquin Perez Valera 5 USD
* Anonymous sponsors 2750 USD

In-kind contributions:

* Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU) - space and personnel time (planning, preparation)
* North Carolina State University - personnel time (planning, preparation)
* mundialis GmbH & Co. KG - personnel time (planning, preparation)
* CONICET - personnel time (planning, preparation)

== 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, reimbursements depending on the financial contributions provided by the community
* 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 ===

(agenda is under development, but also flexible)

==== Thursday, 1 June ====

* Arrival

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

* 10:00 meeting starts in the room B-868
* Review the plan for the next days
* API for use in Python and in other projects (e.g., QGIS)
* Parallelizations

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

* Reducing cost of distribution on Windows
* Group photo 1

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

* Compilation CMake (Windows, Linux)
* Connections in general, rgrass, qgisprocess
* Group photo 2

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

* Connections in general, QGIS, rgrass, qgisprocess
* Parallelizations
* grass.jupyter

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

* Connections in general, QGIS
* Parallelizations
* grass.jupyter

==== Wednesday, 7 June ====

* Departure

== 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'''
!'''Notes'''
|-
|1
|[[User:Landa|Martin Landa]]
| Czech Republic
| June 1
| June 7
| Python: create_location ([https://github.com/OSGeo/grass/issues/1987 #1987]), Graphical Modeler improvements and single window layout integration
|
|-
|2
| Micha Silver
| Israel
| June 2
| June 6
| Addon to derive soil moisture from Sentinel 2
|
|-
|3
|[https://www.osgeo.org/member/kudrnovsky/ Helmut Kudrnovsky]
| Austria
| June 2 (18:37) by train
| June 4 (18:24) by train
| support CMake transition
|
|-
|4
|[[User:Neteler|Markus Neteler]]
| Germany
| June 2 (17:17)
| June 6 (12:43)
| translations, manual pages, ..., see [[Talk:GRASS_Community_Meeting_Prague_2023#Markus_Neteler|my list in "Discussion" page]]
|
|-
|5
|[[User:pesekon2|Ondřej Pešek]]
| Czech Republic
| June 2 (17:17)
| June 6 (12:43)
| Python 3.12-connected issues, gmodeler
|
|-
|6
| [[User:helena|Helena Mitasova]]
| United States
| June 2
| June 6
|
|
|-
|7
| [[User:wenzeslaus|Vaclav Petras]]
| United States
| June 1
| June 7
| init and other Python API topics, support CMake transition, revise connection with QGIS and other tools, funding
|
|-
|8
| [[User:Annakrat|Anna Petrasova]]
| United States
| June 1
| June 7
| parallelization documentation, grass.jupyter, R and QGIS integration
|
|-
|9
| [[User:Ctwhite|Corey White]]
| United States
| June 2 (10:55)
| June 7
| Connections with other tools, OpenPlains, JSON outputs
|
|-
|10
| [[User:MarisN|Maris Nartiss]]
| Latvia
| June 2
| June 6
| Improvements of imagery modules (push i.svm.*; i.signatures; ?)
|-
|11
| [[User:Aaronsms|Aaron Saw Min Sern]]
| Singapore
| June 1
| June 7
| Support CMake transition, r.mapcalc parallelization
|
|-
|12
| [[User:Ldesousa|Luís de Sousa]]
| The Netherlands
| June 1 (20:00)
| June 5 (20:45)
| Update r.mblend add-on; test CMake transition.
|
|-
|13
| Caitlin Haedrich
| United States
| June 1
| June 7
| grass.jupyter
|
|-
|14
| Linda Kladivová
| Czech Republic
| June 2
| June 6
| Single-Window layout issues and improvements
|
|-
|15
| Carmen Tawalika
| Germany
| June 2 (17:17)
| June 6 (12:43)
| Happy to assist with general topics like documentation + automation, in doubt something related to actinia
|
|-
|16
| Floris Vanderhaeghe
| Belgium
| June 3 (train 19:17)
| June 6 (train 8:25)
| Helping in interfacing GRASS from R (rgrass & qgisprocess packages)
|
|-
|}

If you are arriving or departing on the days of the event, please specify the time, too.

=== Via chat or hangout ===

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

TBD: Google Meet / Zoom / ???

Participating virtually:

{|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'''
!'''Topics'''
!'''Times, synchronous or fully asynchronous'''
!'''Notes'''
|-
|1
|[[User:Baharmon|Brendan Harmon]]
| United States
| Update integration with QGIS
|
|
|-
|2
|[[User:veroandreo|Veronica Andreo]]
| Argentina
| Mission and vision, interfaces with QGIS and R, sponsoring, ... [https://grasswiki.osgeo.org/wiki/Talk:GRASS_Community_Meeting_Prague_2023#Vero see discussion tab]
| available from 8:00 AM ART (UTC-3) onward
|
|-
|3
|[[User:Nobeeakon|Daniel T]]
| Mexico
|
| some availability through the days :/
|
|-
|4
|[[User:LBartoletti|Loïc Bartoletti]]
| France
| QGIS Integration, support CMake transition
|
|-
|}

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

Vero: available from 8:00 AM ART (UTC-3) onward

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

== Report and press release ==

TBD: After the event :-)

We'll esp. craft a report for our sponsors.

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

GRASS Community Meeting Prague 2023

2023-05-12T07:09:23Z

⚠️MarisN: /* Individual Preparation */ We don't use svn any more

{{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''' (by contributing to GRASS GIS of course).

<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, OGC Services and desiring to '''celebrate with us the 40th GRASS GIS birthday!!'''

In this meeting, we will work on GRASS GIS and integrations with related OSGeo projects. We will revise connection to QGIS to make it easier to maintain, and we will work on migration of the build to CMake to improve Windows builds including PDAL support. Furthermore, we will start moving documentation to Markdown to make it easier to contribute to and we will add images and examples for tools and workflows which still miss them. Finally, we will automate and document maintenance processes to reduce the burden on maintainers and thus improve the project sustainability.

Note that while we have our general plan, we can't accept any earmarked donations, i.e., we can't make any promises for a specific work to be done. We do require participants to work on GRASS GIS or connections to other projects. However, we leave them the freedom to work on what they think is the best contribution to the project at that time given their skills and time available.

For the detailed agenda and individual's plans, 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 travel and accommodation expenses for GRASS developers who volunteer their time. If you are interested in sponsoring the GRASS Community Meeting, please see our

::: '''[https://opencollective.com/osgeo/projects/grass/contribute/grass-community-meeting-prague-2023-55074 OpenCollective GRASS Community Meeting Prague 2023 Tier]'''

Any surplus at the end of the event will used for future activities of the GRASS GIS project such as the successful [[Student Grants|student mini grant program]].

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:

[[File:Osgeo logo.png|none|left|alt=Light and dark green logo of OSGeo saying Your Open Source Compass|Open Source Geospatial Foundation]]
* OSGeo: 7303 USD (approved budget contribution, [https://www.loomio.com/p/2m75BZkL/motion-to-approve-7303-to-support-grass-gis-community-meeting motion])

[[File:FOSSGIS_eV_logo.png|none|left|400px|alt=Logo of FOSSGIS e.V.|FOSSGIS e.V.]]
* FOSSGIS e.V.: 5000 EUR

Individuals:
* MarWe 50 USD
* Nick Brady 50 USD
* Johannes Brauner 30 USD
* Joaquin Perez Valera 5 USD
* Anonymous sponsors 2750 USD

In-kind contributions:

* Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU) - space and personnel time (planning, preparation)
* North Carolina State University - personnel time (planning, preparation)
* mundialis GmbH & Co. KG - personnel time (planning, preparation)
* CONICET - personnel time (planning, preparation)

== 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, reimbursements depending on the financial contributions provided by the community
* 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 ===

(agenda is under development, but also flexible)

==== Thursday, 1 June ====

* Arrival

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

* 10:00 meeting starts in the room B-868
* Review the plan for the next days
* API for use in Python and in other projects (e.g., QGIS)
* Parallelizations

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

* Reducing cost of distribution on Windows
* Group photo 1

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

* Compilation CMake (Windows, Linux)
* Connections in general, rgrass, qgisprocess
* Group photo 2

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

* Connections in general, QGIS, rgrass, qgisprocess
* Parallelizations
* grass.jupyter

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

* Connections in general, QGIS
* Parallelizations
* grass.jupyter

==== Wednesday, 7 June ====

* Departure

== 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'''
!'''Notes'''
|-
|1
|[[User:Landa|Martin Landa]]
| Czech Republic
| June 1
| June 7
| Python: create_location ([https://github.com/OSGeo/grass/issues/1987 #1987]), Graphical Modeler improvements and single window layout integration
|
|-
|2
| Micha Silver
| Israel
| June 2
| June 6
| Addon to derive soil moisture from Sentinel 2
|
|-
|3
|[https://www.osgeo.org/member/kudrnovsky/ Helmut Kudrnovsky]
| Austria
| June 2 (18:37) by train
| June 4 (18:24) by train
| support CMake transition
|
|-
|4
|[[User:Neteler|Markus Neteler]]
| Germany
| June 2 (17:17)
| June 6 (12:43)
| translations, manual pages, ..., see [[Talk:GRASS_Community_Meeting_Prague_2023#Markus_Neteler|my list in "Discussion" page]]
|
|-
|5
|[[User:pesekon2|Ondřej Pešek]]
| Czech Republic
| June 2 (17:17)
| June 6 (12:43)
| Python 3.12-connected issues, gmodeler
|
|-
|6
| [[User:helena|Helena Mitasova]]
| United States
| June 2
| June 6
|
|
|-
|7
| [[User:wenzeslaus|Vaclav Petras]]
| United States
| June 1
| June 7
| init and other Python API topics, support CMake transition, revise connection with QGIS and other tools, funding
|
|-
|8
| [[User:Annakrat|Anna Petrasova]]
| United States
| June 1
| June 7
| parallelization documentation, grass.jupyter, R and QGIS integration
|
|-
|9
| [[User:Ctwhite|Corey White]]
| United States
| June 2 (10:55)
| June 7
| Connections with other tools, OpenPlains, JSON outputs
|
|-
|10
| [[User:MarisN|Maris Nartiss]]
| Latvia
| June 2
| June 6
|
|-
|11
| [[User:Aaronsms|Aaron Saw Min Sern]]
| Singapore
| June 1
| June 7
| Support CMake transition, r.mapcalc parallelization
|
|-
|12
| [[User:Ldesousa|Luís de Sousa]]
| The Netherlands
| June 1 (20:00)
| June 5 (20:45)
| Update r.mblend add-on; test CMake transition.
|
|-
|13
| Caitlin Haedrich
| United States
| June 1
| June 7
| grass.jupyter
|
|-
|14
| Linda Kladivová
| Czech Republic
| June 2
| June 6
| Single-Window layout issues and improvements
|
|-
|15
| Carmen Tawalika
| Germany
| June 2 (17:17)
| June 6 (12:43)
| Happy to assist with general topics like documentation + automation, in doubt something related to actinia
|
|-
|16
| Floris Vanderhaeghe
| Belgium
| June 3 (train 19:17)
| June 6 (train 8:25)
| Helping in interfacing GRASS from R (rgrass & qgisprocess packages)
|
|-
|}

If you are arriving or departing on the days of the event, please specify the time, too.

=== Via chat or hangout ===

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

TBD: Google Meet / Zoom / ???

Participating virtually:

{|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'''
!'''Topics'''
!'''Times, synchronous or fully asynchronous'''
!'''Notes'''
|-
|1
|[[User:Baharmon|Brendan Harmon]]
| United States
| Update integration with QGIS
|
|
|-
|2
|[[User:veroandreo|Veronica Andreo]]
| Argentina
| Mission and vision, interfaces with QGIS and R, sponsoring, ... [https://grasswiki.osgeo.org/wiki/Talk:GRASS_Community_Meeting_Prague_2023#Vero see discussion tab]
| available from 8:00 AM ART (UTC-3) onward
|
|-
|3
|[[User:Nobeeakon|Daniel T]]
| Mexico
|
| some availability through the days :/
|
|-
|4
|[[User:LBartoletti|Loïc Bartoletti]]
| France
| QGIS Integration, support CMake transition
|
|-
|}

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

Vero: available from 8:00 AM ART (UTC-3) onward

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

== Report and press release ==

TBD: After the event :-)

We'll esp. craft a report for our sponsors.

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

GRASS Community Meeting Prague 2023

2023-04-04T10:21:00Z

⚠️MarisN: /* In person */

GRASS GCI Ideas 2018

2018-09-16T15:44:31Z

⚠️MarisN: /* Some ideas for tasks */ Replicate a bug

<center>
[[Image:grasslogo_vector_small.png|link=http://grass.osgeo.org]] @ [[Image:GCI-logo.jpg|300px|link=https://developers.google.com/open-source/gci/]] @ [[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
</center>

= About =

This is the GRASS page for [https://wiki.osgeo.org/wiki/Google_Code_In_2018 Google Code-In] 2018. Here we will list task ideas and other information related to the GRASS GCI projects as well as the contest results and contributions by the students.

== What is Google Code-In? ==

Pre-university students ages 13 to 17 are invited to take part in Google Code-in: Our global, online, contest introducing teenagers to the world of open source. With a wide variety of bite-sized tasks, it’s easy for beginners to jump in and get started no matter what skills they have. Mentors from our participating organizations lend a helping hand as participants learn what it’s like to work on an open source project. For more details, see [https://developers.google.com/open-source/gci/ Google Code-In] main page.

== How does it work? ==

# Students search for a '''task''' that interests them and claim it. They have at least ''three days and up to five'' to complete it.
# The student works on the task, getting guidance from mentors, if needed.
# Once the student has finished, he/she submits the work for review through the contest website.
# Mentors from the organization evaluate the work, provide feedback, and if it's complete, accept it! Otherwise, specific feedback is provided, and the student goes back to step #2!
# Go to step #1 and repeat!

More details can be found at: [https://developers.google.com/open-source/gci/how-it-works https://developers.google.com/open-source/gci/how-it-works]

== Tasks ==

The organizations should create a large list of short (3-5 hour) tasks for students to work on. Tasks are categorized as: Code, Documentation/Training, Outreach/Research, Quality Assurance, or User Interface. Some examples of tasks of different categories can be found [https://developers.google.com/open-source/gci/resources/example-tasks here]. Tasks from GCI 2017 can be found here: https://codein.withgoogle.com/archive/2017/organization/5168183002529792/task/

=== Some ideas for tasks ===

* Create a screenshot for the next 76 release announcement
* Design the t-shirt for the next code-sprint
* Add examples to manual pages
* Make a promo video for GRASS GIS
* Make new tutorial videos for GRASS GIS
* Write a short blog entry about GRASS GIS (or a certain module)
* Enhance the visual index
* Make screenshots to populate the visual change log in new features pages (e.g., for [https://trac.osgeo.org/grass/wiki/Grass7/NewFeatures76 New Features GRASS 7.6])
* Create icons/phrases to include in sticker sheets
* Give a talk about GRASS GIS to classmates
* Contribute examples based on NC dataset to manual pages (extensive to add-ons)
* Contribute screenshots to manual pages (extensive to add-ons)
* Try to replicate a bug report on your computer and add your result to the bug comments
* Submit a patch for a certain bug or enhancement ticket
* Contribute tests for modules
* ''add your own idea...''

== Details about the tasks and lessons learnt ==

* Translations are not allowed by Google Code In as tasks.

* A strategic plan is needed to generate a pool of tasks doable in 3-5 hours (from beginner to advanced tasks); '''from ~50 up to ~100 tasks!!'''

* A '''large mentor pool''' that can tackle evaluations of about ~ 100 tasks!! Importantly, the revision of tasks should be rather quick, since the students should complete as many tasks as possible to win the contest.

= Available mentors =
List of available mentors to follow the tasks

* [[User:Lucadelu|Luca Delucchi]]
* [[User:Veroandreo|Veronica Andreo]]
* ...

'''Important''': To sign up as a mentor, write an email to: gci-admin at osgeo dot org

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

GRASS GIS Community Sprint Bonn 2018

2018-03-18T13:36:53Z

⚠️MarisN: /* New GRASS GIS startup style */ Potential problematic areas

{{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
|
|
|-
|#
|...
|
|
|
|
|
|
|-
|}

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

== 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 Community Sprint Bonn 2018

2018-03-17T14:54:00Z

⚠️MarisN: /* Move to Git */ Separate Git repo for history

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

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

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

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

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

User:MarisN

2016-01-27T15:23:36Z

⚠️MarisN: For some time I already have a higher position (but not higher salary)

[[Image:Maris_nartiss.jpg|thumb]]
Dr. geog. Māris Nartišs

Author of r.lake, v.profile modules and a troll. Intolerant, hard to communicate person.
Sometimes I take a bit of care of GRASS GIS translator friendliness, also translate GRASS GIS and QGIS to Latvian language.

Assistant professor (docent) at University of Latvia.

[http://www.gisnet.lv/ About GIS in Latvian]

[http://www.sungis.lv/ Custom spatial solutions, help with GRASS and QGIS at SunGIS ltd]

Will code for food.

GRASS SoC Ideas 2012

2013-01-23T05:43:54Z

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

<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:

* 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 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)
# ''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).
# Create graphical vector attribute data merging tool and provide necessary functionality in v.patch to allow merging of two vector datasets with different attribute data tables. Tool should provide a GUI way to map attribute table columns, create new ones and, where possible, change data type during merging.
# ''Your idea here'' ...

'''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), Markus Metz (orthorectification), (''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, [[User:Huhabla|Sören Gebbert]]

=== Improved Python interface ===

Design '''sophisticated Python scripting interface''' for GRASS based on [http://grass.osgeo.org/programming7/pythonlib.html GRASS Python Scripting Library]. This API should become more intuitive and more integrative

GRASS GIS would gain even more attractiveness!

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

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

# ''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 ==

# ''Python high level map interaction for GRASS GIS'' ([http://www.google-melange.com/gsoc/project/google/gsoc2012/zarch/11001 abstract])
#: Student: Pietro Zambelli
#: Mentor: Sören Gebbert
#: Backup mentors: Luca Delucchi, Martin Landa
#: Wiki page: [[GRASS SoC Ideas 2012/High level map interaction]]
# ''GRASS GIS WxGui front end for vector analysis modules'' ([http://www.google-melange.com/gsoc/project/google/gsoc2012/turek/38001 abstract])
#: Student: Stepan Turek
#: Mentor: Martin Landa
#: Backup mentor: Markus Metz
#: Wiki page: [[GRASS GSoC 2012 WxGUI front end for vector analysis modules]]
# ''Image Segmentation in GRASS GIS'' ([http://www.google-melange.com/gsoc/project/google/gsoc2012/emomsen/20001 abstract])
#: Student: Eric Momsen
#: Mentor: Markus Metz
#: Backup mentors: Moritz Lennert, Pierre Roudier
#: Wiki page: [[GRASS GSoC 2012 Image Segmentation]]



{{GSoC}}

Support

2012-12-20T09:28:10Z

⚠️MarisN: /* Commercial support: Companies and Institutions which offer GRASS Support */ Add SunGIS

== GRASS Community ==

To reach the community, see [[GRASS Community]].

== Commercial support: Freelancers who offer GRASS Support ==

You need a person with programming skills? Check out this list:

* Seth Price <seth@pricepages.org> - low-level raster processing, code optimization, OpenCL
* Mohammed Rashad <rashadkm [at] gmail.com> - Add/Maintain modules(Python and C), UI development
* you
* ...

== Commercial support: Companies and Institutions which offer GRASS Support ==



{| class="wikitable sortable" cellspacing="1" cellpadding="1" border="1"
|-
! scope="col" | Country
! scope="col" | Name
! scope="col" | Competences
! scope="col" | Site
|-
| Germany
| GDF Hannover
| Project management, Data analysis
| http://www.gdf-hannover.de
|-
| Germany
| Geoinformatik Büro Dassau
| Project management, Training, Data analysis, Programming
| http://www.gbd-consult.de
|-
| Italy
| Fondazione Edmund Mach
| Project management, Data analysis, Programming
| http://gis.cri.fmach.it
|-
| India
| Lab for Spatial Informatics
| Project management, Data analysis, Programming, Training
| http://lsi.iiit.ac.in
|-
| Latvia
| SunGIS
| Project management, Data analysis, Programming, Training
| http://www.sungis.lv
|-
| your country
| ...
| ...
| ...
|}

* See also the [http://www.osgeo.org/search_profile OSGeo Commercial Service Providers Index] (and those which are [http://www.osgeo.org/search_profile?SET=1&MUL_TECH%5B%5D=00015 GRASS-specific])

[[Category: FAQ]]

Team

2012-07-19T12:46:41Z

⚠️MarisN: Add Maris Nartiss picture

The GRASS GIS project is an international team effort with scientists and developers participating from various fields. Below is a list of the current team.

All general queries concerning GRASS should be addressed to the respective [http://grass.osgeo.org/community/support.php GRASS mailing lists]. If you miss yourself or somebody else on the lists below, please feel free to edit this Wiki page or send mail to the [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list].

== Current contributors to the development of the GRASS code ==

In alphabetical order; see for example [http://www.ohloh.net/p/grass_gis/contributors here] for contribution statistics.

{| class="wikitable sortable" border="1" style="margin: 1em auto 1em auto; text-align:left"
| [[Image:Grasslogo vector small.png|center]]
| '''Anna Kratochvílová''': GRASS 7 wxGUI development, Prague, CZ, mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list]

|-
| [[Image:benjamin.png|center|center]]
| '''Benjamin Ducke''': extension manager, spatial statistics, archaeological applications, predictive modelling Location: Berlin, Germany, mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list]

|-
| [[Image:Grasslogo vector small.png|center]]
| '''Glynn Clements''': core development, UK, mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list ]

|-
| [[Image:hamish.jpg|center]]
| '''Hamish Bowman''': Development of display, PostScript, raster, and GPS modules as well as general sanitation of the code, help, and web pages. Location: Department of Marine Science, University of Otago. Dunedin, New Zealand mail: hamish_b AT yahoo com [http://hamish.bowman.googlepages.com/grassfiles http://hamish.bowman.googlepages.com/grassfiles]

|-
| [[Image:helena.jpg|center]]
| '''Helena Mitasova''': surface and volume modeling and analysis (RST modules), topographic analysis, hydrologic and erosion modelling, assistance with visualization, working with students on new module development, testing, and bug fixing Location: Raleigh, North Carolina, USA, mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list ][http://skagit.meas.ncsu.edu/~helena/ http://skagit.meas.ncsu.edu/~helena/]

|-
| [[Image:hellik.png|center]]
| '''Helmut Kudrnovsky''': [http://grass.osgeo.org/grass64/binary/mswindows/native/ winGRASS packaging], Austria, mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list]

|-
| [[Image:lucadelu.png|center]]
| '''Luca Delucchi''': Python GRASS development (GUI and Modules), Documentation, Italian Translation, Location: Trento (Italy), mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list]

|-
| [[Image:Maris_nartiss.jpg|thumb|center]]
| '''[[user:MarisN|Maris Nartiss]]''': Tcl/TK GUI development, Latvia, mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list]

|-
| [[Image:Grasslogo vector small.png|center]]
| '''Markus Metz''': GRASS 7 development, massive data processing, vector library, Italy + Germany, mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list]

|-
| [[Image:markus.jpg|center]]
| '''Markus Neteler''': various contributions, coordination, main Web site and mailing lists maintenance, Location: Trento, Italy, mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list], IRC Nick: markusN [http://www.grassbook.org/neteler/ http://www.grassbook.org/neteler/]

|-
| [[Image:mlanda.png|center]]
| '''Martin Landa''': various contributions, vector engine improvements, [http://grass.osgeo.org/wiki/WxGUI wxGUI], Location: Prague, Czech Republic Mail: landa.martin AT gmail.com Homepage: [http://geo.fsv.cvut.cz/~landa http://geo.fsv.cvut.cz/~landa]

|-
| [[Image:michael.jpg|center]]
| '''Michael Barton ''': GRASS native GUI development Location: Tempe, Arizona, USA mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list ][http://www.public.asu.edu/~cmbarton/ http://www.public.asu.edu/~cmbarton/]

|-
| [[Image:Grasslogo vector small.png|center]]
| '''Moritz Lennert''': display tools, mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list]

|-
| [[Image:Grasslogo vector small.png|center]]
| '''Soeren Gebbert''': improvements of [http://www-pool.math.tu-berlin.de/~soeren/grass/ 3D functionality] mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list]

|-
| [[Image:Grasslogo vector small.png|center]]
| '''Vaclav Petras''': GRASS 7 wxGUI development, Prague, CZ, mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list]

|-
| [[Image:Grasslogo vector small.png|center]]
| '''William Kyngesburye''': [http://www.kyngchaos.com/software:grass/ Mac OS X packaging], USA, mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list]

|-
| [[Image:Grasslogo vector small.png|center]]
| '''Yann Chemin''': image processing, mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list]

|-
| [[Image:Grasslogo vector small.png|center]]
| '''''your name''': what-you-do, Location: xyz, mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list], link: ''

|}

== Former or currently inactive developers ==

(in alphabetical order)

{| class="wikitable sortable" border="1" style="margin: 1em auto 1em auto; text-align:left"
| [[Image:Grasslogo vector small.png|center]]
| '''Bob Covill''' Role: visualization, mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list ]

|-
| [[Image:Grasslogo vector small.png|center]]
| '''Brad Douglas''' Role: bug fixing, code portability, imagery modules Location: Fremont, California, USA, IRC Nick: bdouglas, mail: rez AT touchofmadness com

|-
| [[Image:cedric.jpg|center]]
| '''Cedric Shock''' Role: user interface enhancements, debugging Location: Eugene, Oregon, USA, mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list], [http://www.shockfamily.net/cedric/ http://www.shockfamily.net/cedric/]

|-
| [[Image:DaveSampson.png|center]]
| '''Dave Sampson''' Role: tutorials, data sets & public data licensing, GRASS map gallery, Ottawa Chapter of OSGeo, Location: Ottawa, Ontario, Canada, mail: samper.d at gmail dot com [http://davidsampson.ca/ http://davidsampson.ca]

|-
| [[Image:Grasslogo vector small.png|center]]
| '''Huidae Cho''' Role: bug fixing, hydrologic modeling (TOPMODEL modules), DXF modules, FreeType support. Location: Fairfax, Virginia, USA mail: grass4u AT gmail com, IRC Nick: grass4u [http://geni.ath.cx/ http://geni.ath.cx]

|-
| [[Image:jachym.png|center]]
| '''Jachym Cepicky''' Role: bug fixing, support of 3D vectors, tester and translator, Location: Department of Geoinformation Technologies, Mendel University of Agriculture, Brno, Czech Republic, mail: jachym.cepicky AT centrum.cz [http://les-ejk.cz/ http://les-ejk.cz/]

|-
| [[Image:Grasslogo vector small.png|center]]
| '''Jaroslav Hofierka''' Role: development of modules for solar irradiation, flow routing, surface and volume modelling and analysis (RST modules), hydrologic and erosion modelling, assistance with visualization Location: Presov, Slovakia, mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list ]

|-
| [[Image:maciek.png|center]]
| '''Maciej Sieczka''' Role: power user, testing Location: Wroclaw, Poland, mail: msieczka AT sieczka.org [http://www.sieczka.org/ http://www.sieczka.org]

|-
| [[Image:Grasslogo vector small.png|center]]
| '''Marco Pasetti''' Role: Microsoft Windows native binary port of GRASS Location: Brescia, Italy, mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list], link: [http://grass.osgeo.org/grass64/binary/mswindows/native/ WinGRASS Project Homepage]

|-
| [[Image:Grasslogo vector small.png|center]]
| '''Paul Kelly''' Role: Proj integration, mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list ]

|-
| [[Image:radim.jpg|center]]
| '''Radim Blazek''' Role: DBMI, vector engine core developer, Location: Trento, Italy till 2006, mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list]

|-
| [[Image:scott.jpg|center]]
| '''Scott Mitchell''' Role: tutorial and documentation development, web site maintenance, Ottawa User's Group, OSGeo Journal News and Events Editor Location: Ottawa, Ontario, Canada, mail: [http://lists.osgeo.org/mailman/listinfo/grass-web GRASS web site maintenance mailing list] [http://www.carleton.ca/~smitch http://www.carleton.ca/~smitch]

|-
| [[Image:Grasslogo vector small.png|center]]
| '''''your name''': what-you-did, Location: xyz, mail: [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list], link:''

|}

== The following institutions are currently supporting the GRASS-Project ==

Please see our [http://grass.osgeo.org/donation.php GRASS sponsoring] page.

And a ''thank-you'' to:

* the many people who have contributed in the past
* the various users who have contributed bug reports and tested unstable GRASS versions;
* all the sites (and the people behind them) that provide mirrors for the GRASS web pages.

User:MarisN

2012-07-19T12:39:03Z

⚠️MarisN: Add picture and link to SunGIS ltd

[[Image:Maris_nartiss.jpg|thumb]]
Māris Nartišs

Author of r.lake, v.profile modules and a troll. Intolerant, hard to communicate person.

Lecturer at University of Latvia.

[http://www.gisnet.lv/ About GIS in Latvian]

[http://www.sungis.lv/ Custom spatial solutions, help with GRASS and QGIS at SunGIS ltd]

Will code for food.

File:Maris nartiss.jpg

2012-07-19T12:35:11Z

⚠️MarisN: Maris Nartiss

Maris Nartiss

GRASS SoC Ideas 2012

2012-02-25T08:35:51Z

⚠️MarisN: /* wxGUI */ Remove WMS idea, add interactive export tool idea

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

<ol>
<li> 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>
<li> 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).
<li> 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]

<li> ''Your idea here''

</ol>
'''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 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).
# ''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 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'')

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

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

* 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]

# 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) (''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]]

WxGUI WMS service rendering GSoC 2011

2011-08-03T17:32:52Z

⚠️MarisN: /* Documentation */ Overall architecture

== Aim of the project ==
This project aims to introduce several features that make WXGUI more user-friendly. These include adding WMS layer support for WXGUI. The selection features will be displayed as per the based on service GetCapabilities response. The parameters and the layers are to be displayed are extracted out of the xml response.

== State of the art ==

The project uses WMS service to fetch images of the maps. The Get Feature service of WMS services provides a GML based interface to access the information about various layers available. The WMS layer knowledge is used to update the GUI of the GRASS according to the available features for a particular layer. Thw WX-GUI is to be modified and to be integrated with the WMS services.

== Bulletin Board ==

== Documentation ==
Overall architecture. A big picture. Might be not precise. Implementation might differ.

[[File:Wms_architecture.png]]

The sequence diagram and use case diagram for the proposed Gsoc project are shown below
[[File:Example.jpg]]
[[File:usecasegsoc.jpg]]

== Planned Timeline ==

1 - 7 June : To introduce toy changes in the source code. To get familiar with the source file structuring and existing code. Learn WxPython and get Comfortable with it.

7-14 June : To introduce meaningful changes in the WXGUI. Aim to write a module for statically updating the WXGUI without any back end support from WMS services.

14-21 June :To hard code for dynamic updating of GUI without WMS support

21-28 June : To establish correctness of the code , testing of the modules.

29 June - 5 July: To understand the available WMS services. To extract the features available through get feature module.

6 July - 13 July: To hard code for the WMS layer supports available so as to update the front end GUI.

14 July - 21 July: To integrate the front end WXGUI new modules for updating the interface with the backend support from WMS GetCapabilites services.

22 July- 29 July: To introduce get layers service of the WMS services in the front end of WXGUI

== How to test ==

Note: {{twiki|DownloadSource#GRASS7|GRASS 7}} required.

g.extension -s extension=wx.wms

File -> GSoC testing -> WMS

== Weekly GSOC reports==

=== Report #0 29-05-2011. ===

'''1) What do I have completed this week?'''

I have completed the following by this week.
* Creating the uml diagrams (sequence and use case) for the planned architecture of the project.
* Have read GUI documentation from the programmer's manual [0].
* Have gone through the source file structuring.
* Have setup the system, compiled the source and successfully installed it.

'''2) What am I going to achieve for next week?'''

I plan to introduce some toy changes in the source code, like print statements. I will try to familiarize myself with the wxPython.

'''3) Is there any blocking issue?'''

No major bottlenecks till now.

=== Report #1 3-06-2011. ===

'''1) What do I have completed this week?'''

I have completed the following by this week.
* Read the programmers manual for WXGUI [0], [2], [3].
* Written a standalone helloWorld application in WXGUI and learning WXGUI from [3]
* Added a button to GUI of GRASS, which for now essentially does nothing.
* Printing of dummy messages and changing the welcome messages.
* Test uploading on SVN and getting acquainted with svn.

'''2) What am I going to achieve for next week?'''

I plan to update the GUI with respect to available layers. Back end WMS support will be hard coded for the time being.

'''3) Is there any blocking issue?'''

Learning of WXPython. Never used it before. I am trying to get comfortable with it.

=== Report #2 9-06-2011. ===

'''1) What do I have completed this week?'''

This week, I have not been able to do much work due to my visit to Singapore this week and problem with ubuntu system to connect to the network here. I have completed the following by this week.
* Read the [4] , Chapter 1 and 2 for SVN.
* Build a simple text editor in wxpython, build drop down menus in wxpython.
* Test uploading of SVN
* Install Quantum GIS and study it's GUI functionality.

'''2) What am I going to achieve for next week?'''

1) Get familiar with WMS use in QGIS.
2) Continue to get familiar with wxpython and GRASS wxGUI.

'''3) Is there any blocking issue?'''

Network Connectivity problem with my ubuntu system not being able to connect to network delayed the work this week. I am now more comfortable with wxpython now.

=== Report #3 17-06-2011. ===

'''1) What do I have completed this week?'''

By this week I am quite acquanted with wxpython and ready to build applications in it.
* Study QGIS WMS layer support
* Launch a New window with an "Add WMS" button from main window of grass. New window has 3 buttons. Functionality not yet coded for the buttons.
* SVN readme file update.

'''2) What am I going to achieve for next week?'''

1) Add WMS support at the backend of the added new buttons.

'''3) Is there any blocking issue?'''
Nothing major problem till now

=== Report #4 24-06-2011. ===

'''1) What do I have completed this week?'''

* Implemented a button in grass7 GUI, which launches a new window. The new window has 3 button. On pressing the button 'GetCapabilities', xml data is fetched for WMS http://www.gisnet.lv/cgi-bin/topo, and the xml data is displayed as it in the window.
* Parser(Minidom) is used to parse the xml data and display it in the form it is displayed in QGIS

'''2) What am I going to achieve for next week?'''

1) Add functioanlity to retrieve getcappabilities of any wms, currently it is hard coded for one wms.
2) Fetch the maps after the user selects particular layers from the list of layers displayed.

'''3) Is there any blocking issue?'''
No major bottleneck till now

=== Report #5 01-07-2011. ===

'''1) What do I have completed this week?'''

* Major change in GUI done to support layer display and WMS url input
* Taking the URL for the WMS service as a user input implemented, thus hard coding of url removed
* Code committed to svn https://trac.osgeo.org/grass/browser/grass-addons/grass7/gui/wxpython/wx.wms
* Testing of code done on different WMS services.

'''2) What am I going to achieve for next week?'''

1) GUI support for taking user layer selection.
2) Fetching selected layers and storing them in a local cache.
3) To display the fetched map image.

'''3) Is there any blocking issue?'''
No major bottleneck till now

=== Report #6 08-07-2011. ===

'''1) What do I have completed this week?'''

* Functionality for fetching of Maps added.
* A new Window pops up to display the map. The URL for the map for the time being is hard coded.
* Restructuring of the code done.

'''2) What am I going to achieve for next week?'''

1) Major change in GUI to be done to support user Interaction
2) Error checking and renaming of variables in the back end code.

'''3) Is there any blocking issue?'''
No major bottleneck till now

=== Report #7 15-07-2011. ===

'''1) What do I have completed this week?'''
* Change in GUI, Addition of functionality to Manage Servers, Display the fetched layers as a Tree
* GUI now being generated by wxGlade, backend code changed for GUI.
* Renaming of variables completed in most files, variables in two of files to be renamed.

'''2) What am I going to achieve for next week?'''
* Do Exception handling
* Implement WMS Architecture
* Non Blocking Architecture for wxPython

'''3) Is there any blocking issue?'''
No major bottleneck till now

=== Report #8 22-07-2011. ===

'''1) What do I have completed this week?'''
* Implemented Serivce Excpetion Handling.
* Error checking in getmap and getcapabilities done
* WMS Architecture designed

'''2) What am I going to achieve for next week?'''
* Non Blocking Architecture

'''3) Is there any blocking issue?'''
Not able to do multiple selection of layers.

=== Report #9 29-07-2011. ===

'''1) What do I have completed this week?'''
* Storing info in an xml format done

'''2) What am I going to achieve for next week?'''
* Increasing code robustness, error checking, code check

'''3) Is there any blocking issue?'''
No blocking issue

== References ==

{{GSoC}}

* [0] http://grass.osgeo.org/programming6/
* [1] http://geo.fsv.cvut.cz/~landa/publications/2008/gis-ostrava-08/paper/landa-grass-gui-wxpython.pdf
* [2] http://geo.fsv.cvut.cz/~landa/publications/2008/gfoss-it-08/paper/grass-gfoss-tn.pdf
* [3] http://wiki.wxpython.org/
* [4] http://svnbook.red-bean.com/en/1.5/index.html

File:Wms architecture.png

2011-08-03T17:30:59Z

⚠️MarisN: An "big picture" of GSoC wx.wms architecture.

An "big picture" of GSoC wx.wms architecture.

WxGUI WMS service rendering GSoC 2011

2011-06-07T14:15:15Z

⚠️MarisN: /* Weekly GSOC reports */ Minor layout changes

WxGUI WMS service rendering GSoC 2011

2011-05-23T16:18:55Z

⚠️MarisN: Initial page structure

== Aim of the project ==

== State of the art ==

== Bulletin Board ==

== Documentation ==

The sequence diagram and use case diagram for the proposed Gsoc project are shown below

== Planned Timeline ==

== Weekly Reports, from SoC mailing list ==

== References ==

{{GSoC}}

GRASS SoC Ideas 2011

2011-05-01T10:23:38Z

⚠️MarisN: /* wxGUI */ Add link to wxgui WMS GSoC page

[[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)

* {{Done}} Student applications open (March 28)

* {{Done}} 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.

* {{Done}} Mentor assignments and application reviews deadline (April 22)

* {{Done}} 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 ===

<ol>
<li> 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>
<li> 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. [[WXGUI WMS service rendering GSoC 2011|GRASS WXGUI WMS service rendering project GSoC wiki page]]
<li> 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).
<li> Develop a sophisticated '''GUI for r.stream modules'''. The advantage of such GUI is to allow the user to have a simple approach to a sophisticated thing like hydrology.
</ol>
'''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 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]], [[User:Mmetz|Markus Metz]], (''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 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

== Accepted Ideas ==

# [http://www.google-melange.com/gsoc/project/google/gsoc2011/eil8iath/5001 Completion of wxGUI Nviz extension for 3D data visualization in GRASS GIS]
#: Student: Anna Kratochvilova
#: Mentor: [[User:Landa|Martin Landa]]
# [http://www.google-melange.com/gsoc/project/google/gsoc2011/madi468/9001 Graphical User Interface for the hydrological tools r.stream* in GRASS GIS]
#: Student: [[User:Madi|Margherita Di Leo]]
#: Mentor: Jarek Jasiewicz
# [http://www.google-melange.com/gsoc/project/google/gsoc2011/sudeep495/10001 GRASS WXGUI WMS service rendering]
#: Student: sudeep495
#: Mentor: [[User:MarisN|Maris Nartiss]]
# [http://www.google-melange.com/gsoc/project/google/gsoc2011/lucadelu/13001 r.in.modis for GRASS GIS]
#: Student: [[User:Lucadelu|Luca Delucchi]]
#: Mentor: [[User:Neteler|Markus Neteler]]

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

GRASS SoC Ideas 2011

2011-03-26T09:31:03Z

⚠️MarisN: /* Ideas */ Move 3D stuff to separate part; Add LiDAR 3D speedup idea.

{{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.
# ''Your idea here''

'''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]]

User:MarisN

2011-03-26T09:00:24Z

⚠️MarisN: Update with best characteristics of myself.

Māris Nartišs

Author of r.lake, v.profile modules and a troll. Intolerant, hard to communicate person.

Lecturer at University of Latvia.

[http://www.gisnet.lv/ About GIS in Latvian]

Will code for food.

GRASS SoC Ideas 2011

2011-03-26T08:56:05Z

⚠️MarisN: /* wxGUI */ Mentoring offer for WMS support

{{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.
# ''Your idea here''

'''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'')

=== 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 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.
# 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-26T08:52:22Z

⚠️MarisN: Add idea of interpolation with break lines

{{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 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.
# ''Your idea here''

'''Willing to Mentor:''' [[User:Landa|Martin Landa]], (''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'')

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

User:MarisN

2011-03-19T10:43:54Z

⚠️MarisN: Add link to GISnet

Māris Nartišs

Author of r.lake module and troll.

Lecturer at University of Latvia.

[http://www.gisnet.lv/ About GIS in Latvian]

GRASS SoC Ideas 2011

2011-03-19T10:41:09Z

⚠️MarisN: WMS support for wxGUI

Count points in raster cells

2010-07-06T12:26:08Z

⚠️MarisN: Add area counting example

'''Q:''' How can I count the number of points which fall into a raster cell? I want to count vector points by region resolution (quadrat count) and write the results to a raster map (in order to perform r.mapcalc on these observed frequencies).

'''A:''' Use {{cmd|r.in.xyz}} with 'method=n' which will count points per cell (resolution chosen with {{cmd|g.region}}) and write a raster map allocating the number count to the cell.

Example:

v.out.ascii input=myvec format=point | r.in.xyz input=- output=myras method=n type=FCELL x=1 y=2 z=3

'''Q:''' But what if I need to count vector areas and not points per raster cell?

'''A:''' Create vector grid with desired cell size; Overlay it with area layer You want to count; Adjust GRASS region to match vector grid and then use same method as described for points. Example found at [http://www.gisnet.lv/gisnet/2010/07/objektu-skaits-platibas-vieniba-skaitam-laukumus GISnet.lv]

Example:
v.mkgrid map=soil_grid grid=7,9 position=coor coor=595000,4920000 box=1000,1000
v.overlay ainput=soil_grid atype=area binput=soils@PERMANENT btype=area output=soil_on_grid operator=and
g.region vect=soil_grid res=1000
v.out.ascii input=soil_on_grid format=point fs='|' dp=2 layer=1 where="b_label='VaB'" | \
r.in.xyz input=- output=VaB_count method=n

[[Category:FAQ]]

AddOns

2010-03-19T13:06:01Z

⚠️MarisN: v.profile description

This page contains references to user contributions and add-ons (the original GRASS GIS software can be downloaded [http://grass.osgeo.org/download/index.php here]).

__TOC__

== AddOns source code repository ==

The AddOns source code is hosted in [http://svn.osgeo.org/grass/grass-addons/ GRASS-AddOns SVN repository].

To checkout:

svn checkout <nowiki>https://svn.osgeo.org/grass/grass-addons/</nowiki> grass-addons

Please read [http://trac.osgeo.org/grass/wiki/HowToContribute#WriteaccesstotheGRASS-Addons-SVNrepository How to get write access to the GRASS-Addons-SVN repository] and contact the [http://lists.osgeo.org/mailman/listinfo/grass-dev grass-dev] mailing list if you would like to host your module there.

== Building and installing Addons ==

* see the [[Compile and Install#Addons]] wiki page

== Adding something new ==

Please announce your add-on to the GRASS users' mailing list so that others may be aware of your work. Also please consider adding your module to one of the [[Applications]] pages.

=== Copyright and licensing information ===

''Please be sure to include copyright and licensing information in the header comments of your code so that others may know how they can use, extend, modify, and redistribute your work.''

e.g. at the top of a shell script:
<pre>
#!/bin/sh
############################################################################
#
# MODULE: v.in.e00
#
# AUTHOR(S): Markus Neteler, Otto Dassau
#
# PURPOSE: Import E00 data into a GRASS vector map
# Imports single and split E00 files (.e00, .e01, .e02 ...)
#
# COPYRIGHT: (c) 2004, 2005 GDF Hannover bR, http://www.gdf-hannover.de
#
# This program is free software under the GNU General Public
# License (>=v2). Read the file COPYING that comes with GRASS
# for details.
#
#############################################################################
#
# REQUIREMENTS:
# - avcimport: http://avce00.maptools.org

[script follows]
</pre>

=== Coding standards ===

Please have a look at our [http://grass.osgeo.org/grass63/source/SUBMITTING_SCRIPTS Shell script coding standards] before submitting here.

There are other coding standards given for modules written in C, Tcl/Tk, and Python''(?)'' located in the GRASS source code.

=== Documenting your code ===

You can have an help page template auto-generated by using the GRASS [[module command line parser | command line parser]] with the <tt>--html-description</tt> command line option. Please, see also the [http://grass.ibiblio.org/grass63/manuals/html63_user/g.parser.html g.parser help page]

== Miscellaneous Add-ons ==

* [http://trac.osgeo.org/grass/browser/grass-addons/misc/utm_which_zone utm_which_zone.sh] is a shell script to determine UTM zone from Lat/Lon input. Requires [http://www.octave.org Octave] or Matlab to be installed. A shell-only version is [http://dcalvelo.free.fr/grass/utm_which_zone_sh.sh available] which only requires awk. '''Authors''': Hamish Bowman (Octave part), Markus Neteler (shell script wrapper), Daniel Calvelo (sh+awk version)

* Perl scripts for converting data forth and back between Excel files and PostgreSQL: [http://dcalvelo.free.fr/grass/pg2xls.pl pg2xls.pl] reads data from PostgreSQL and produces an excel workbook; [http://dcalvelo.free.fr/grass/xls2sql.pl xls2sql.pl] reads excel files and outputs SQL statements to be fed into an RDBMS. Both scripts need modules from [http://www.cpan.org CPAN], especially [http://search.cpan.org/dist/Spreadsheet-ParseExcel/ Spreadsheet::ParseExcel] for xls2sql.pl and [http://search.cpan.org/~tmtm/Spreadsheet-WriteExcel-FromDB Spreadsheet::WriteExcel::FromDB] and its dependencies for pg2sql.pl. Check the source headers for more info. '''Authors:''' Daniel Calvelo (xls2sql.pl), Markus Neteler (pg2xls.pl)

* [http://dream.lrrl.arch.tu-muenchen.de/~wqual/perl/dbf2sql.tgz dbf2sql] is a Perl script for translating dbf-tables into a sql-command. dbf-tables are read using dbfdump-command from dbd-xbase-perl module ([http://search.cpan.org/~janpaz/DBD-XBase-0.241/ dbd::xbase] and [http://search.cpan.org/~jv/Getopt-Long-2.35/lib/Getopt/Long.pm getopt::long] have to be installed from CPAN first). There are problems, if the last column of the table contains characters. Suggestions for improvements welcome! '''Author:'''Wolfgang Qual

* [http://www.igc.usp.br/pessoais/guano/downloads/azimuth2.c azimuth2.c] is a small C program to calculate the azimuth and length of vector lines exported by GRASS-GIS as ASCII files (like this: v.out.ascii input=vector output=ascii format=standard). It is useful for create rose diagrams of lineament maps. Improvements on the original code after suggestions by Örs Téglásy, Hungary. '''Author:''' Carlos Henrique Grohmann

==GRASS 4.x==

===Raster add-ons for GRASS 4===

* MAGICAL Software: The MAGICAL software comprises a suite of three programs that provide a multi-agent simulation extension for the GRASS GIS software. http://www.ucl.ac.uk/~tcrnmar/simulation/magical/magical.html

==GRASS 5.x==

===Vector add-ons for GRASS 5===

* See here: http://grass.osgeo.org/download/addons.php

===Raster add-ons for GRASS 5===

* See here: http://grass.osgeo.org/download/addons.php

* [http://www.valledemexico.ambitiouslemon.com/gwmodelling.html r.gmtg] The groundwater modelling tool for grass. A module to use MODFLOW within GRASS. '''Author''': Jaime Carrera

* [http://www.bowdoin.edu/~ltoma/research.html r.terracost] Scalable approach for computing least-cost-path surfaces on massive grid terrains. For GRASS 5.3. '''Lead author''': Laura Toma
:Newer version available via SVN:
svn co https://svn.osgeo.org/grass/grass-addons/raster/r.terracost

==GRASS 6.x==

=== Vector add-ons ===

See also

svn co https://svn.osgeo.org/grass/grass-addons/vector

==== v.adehabitat.clusthr, v.adehabitat.kernelUD, v.adehabitat.mcp ====

: Tools to calculate home ranges of animals
: '''Author:''' Clement Calenge

Available via SVN:
svn co https://svn.osgeo.org/grass/grass-addons/vector/adehabitat

==== v.append ====

: [http://www.public.asu.edu/~cmbarton/files/grass_scripts/v.append v.append] is a shell script combining two vector files AND their associated attribute tables. The vector files should be of the same type and, for best results, should have identically formatted attribute tables.

: '''Author:''' Michael Barton

==== v.autokrige ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.autokrige/v.autokrige.py v.autokrige] achieves automatic ordinary kriging from GRASS sites (vector point data), using R with spgrass6 (RGRASS) and automap packages.

: '''Author:''' Mathieu Grelier

==== v.breach ====

: [http://www.sieczka.org/programy_en.html v.breach] creates vector maps of lines and points of continously lowering elevation down the input watercourses, based on the input raster DEM.

: '''Author:''' Maciej Sieczka

==== v.colors ====

: {{cmd|v.colors}} ''moved into main archive''

==== v.count.points.sh ====

: [http://wiki.iosa.it/dokuwiki/spatial_analysis:feature_count v.count.points.sh] counts point features in areas, generates table good as input to d.vect.chart.

: '''Author:''' Stefano Costa

==== v.digatt ====

: [http://phygeo7.geo.uni-augsburg.de/gis2/scripts/v.digatt v.digatt] (shell script) Interactively assign numeric table attributes to series of vector objects. It is meant to be effective by avoiding to type in the attribute value for all single objects again and again. The user is prompted for typing in an attribute value which is assigned to all objects selected by mouseclick afterwards. Next the display is redrawn after updating the table column. Zooming allows to change the region before the old value can be reused or a new one can be typed in (or copied by mouse from another object) in order to assign it to the next series of objects etc. It is tested not very extensively yet. Therefore better work with a copy of your map and consider using v.digit or d.what.vect -e alternatively. [http://phygeo7.geo.uni-augsburg.de/gis2/scripts/v.digatt.png screenshot].

: '''Author:''' Andreas Philipp

==== v.dip ====

: [http://marcin.slodkowski.googlepages.com/v.dip.tgz v.dip] creates points of thickness vectors from the vectors of strike and dip angles. The v.dip is the main ANSI C core program. Program so-called v.dip can run without GRASS environment.

: '''Author:''' Marcin Slodkowski

==== v.flip ====

: [http://www.sieczka.org/programy_en.html v.flip] flips the direction of selected vector lines (redundant since GRASS 6.3 - there is "v.edit tool=flip").

: '''Author:''' Maciej Sieczka

==== v.group ====

: [http://www.shockfamily.net/cedric/grass/v.group v.group] generates a new vector map with the same geometry as an existing map. The new map has categories and a table based on grouping by the values in certain columns of the existing map's table. The values in these columns are preserved in the table for the new map. It's like a v.reclass that preserves data.

: '''Author:''' Cedric Shock

==== v.in.gama ====

: Converts [http://www.gnu.org/software/gama/ GNU GaMa] XML output file to a GRASS vector map layer.

:'''Author:''' Martin Landa

svn co https://svn.osgeo.org/grass/grass-addons/vector/v.in.gama

==== v.in.geoplot ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.in.geoplot v.in.geoplot] converts a [http://www.geoscan-research.co.uk/page9.html/ Geoplot] ASCII export file to a GRASS vector map layer.

:'''Author:''' Benjamin Ducke

svn co https://svn.osgeo.org/grass/grass-addons/vector/v.in.geoplot

==== v.in.gshhs ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.in.gshhs v.in.gshhs] imports [http://www.soest.hawaii.edu/wessel/gshhs/gshhs.html GSHHS] shorelines into a GRASS vector map. GSHHS data are automatically reprojected to the current location.

:'''Authors:''' several, updated to GRASS 6 by Markus Metz

==== v.in.mbsys_fnv ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.in.mbsys_fnv v.in.mbsys_fnv] imports [[MB-System]] navigation files into a GRASS vector map. You can choose from swath area coverage, track lines (including outer port/starboard edges), all bounds as points, etc. An attribute database is created containing the vital statistics of the specified feature such as track length or swath coverage (geodesic), start stop time and location, pitch, roll, heave, etc.

:'''Author:''' Hamish Bowman

==== v.in.ncdc ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.in.ncdc v.in.ncdc] imports an [http://www.ncdc.noaa.gov NCDC] stn file (station data) into a GRASS vector map.

: '''Author:''' Huidae Cho

==== v.in.postgis ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.in.postgis/v.in.postgis.py v.in.postgis] Create a GRASS layer from any sql query on PostGIS data.

: '''Author:''' Mathieu Grelier

==== v.in.osm ====

: [http://kripton.kripserver.net/software/v.in.osm/ v.in.osm]: OpenStreetMap import into GRASS. Yet only supports deprecated API 0.4, will be modified to work with API 0.5 some time soon.

: '''Author:''' Jannis Achstetter

: See also [http://hamish.bowman.googlepages.com/gpsdrivefiles#osm osm2grass.sh] by H Bowman

==== v.in.ovl ====

: [http://grasslab.gisix.com/scripts/v.in.ovl/ v.in.ovl] is a shell script that imports an ASCII vector file created with TOP10|25|50 or similar products.

: '''Author:''' Peter Löwe

==== v.krige ====

: [[V.krige_GSoC_2009 | v.krige]] aims to integrate R functions for kriging (packages automap, gstat, geoR) in a trasparent way. '''Moved into trunk/devbr6 code (r40048)'''

: '''Author:''' Anne Ghisla, as Google Summer of Code 2009 project

: See also [[GRASS_AddOns#v.autokrige]] by Mathieu Grelier

==== v.lda ====

: [http://www.public.asu.edu/~cmbarton/files/grass_scripts/v.lda v.lda] is a shell script for calculating Ian Johnson's (U. Sidney) Local Density Analysis values to measure clustering of point data at different neighborhood radii. There is an option to create a simple line graph of the results. There have been reports of problems creating the line graph on Cygwin installations of GRASS.

==== v.line.center ====

: [http://www.sieczka.org/programy_en.html v.line.center] creates a points vector map with each point located in the middle of the length of the input vector line.

: '''Author:''' Maciej Sieczka

==== v.lmeasure ====

: [http://ngeo.de/grassstuff/v.lmeasure v.lmeasure] and [http://ngeo.de/grassstuff/v.revlmeasure v.revlmeasure] are two perl scripts that place equidistant vector points along a given arbitrary vector line starting from the beginning or end of the vector line, respectively. Resulting vector points are labeled with the distance from origin.

: '''Author:''' Mats Schuh

==== v.out.ascii.db ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.out.ascii.db v.out.ascii.db] is a shell script for exporting vector point data coordinates and selected attribute columns to either a file or to the console.
: ''Superseded in GRASS 6.4 by the new v.out.ascii columns= option.''

: '''Author:''' Hamish Bowman

==== v.out.ascii.mat ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.out.ascii.mat v.out.ascii.mat] is a shell script for exporting vector polygon and polyline data into an ASCII text file suitable for loading into Matlab (or [http://www.gnu.org/software/octave/ Octave]).

: '''Author:''' Hamish Bowman

==== v.out.gmt ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.out.gmt v.out.gmt] is a shell script that exports a polygon vector file into GMT xy file. psbasemap code was copied from Hamish's r.out.gmt.

: '''Author:''' Huidae Cho, Hamish Bowman, Dylan Beaudette

==== v.out.kml ====

: [http://grasslab.gisix.com/scripts/v.out.kml/ v.out.kml] is a shell script that exports a vector file into a KML file for Google Earth or Worldwind. see also [[#r.out.kml|r.out.kml]] and [[#r.out.gmap|r.out.gmap]]

: '''Author:''' Peter Löwe

==== v.out.svg ====

: [http://svg.cc/grass/index.html v.out.svg] is a module that exports SVG notation along with optional attribute data directly from GRASS 6.x vector layers. Now part of [http://svn.osgeo.org/grass/grass/trunk/vector/v.out.svg/ grass6-svn].

: '''Author:''' Klaus Förster

==== v.points.cog ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.points.cog v.points.cog] is a shell script which will create a new point at the center of gravity of each cluster of input points or centroids, grouped by attribute. Among other things this is useful for labeling swarms of points.

: '''Author:''' Hamish Bowman

==== v.profile ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.profile v.profile] is vector map profiling tool similar to r.profile. This module will print out distance and attributes to points/lines along profiling line. It's also usefull to determine places where raster profile crosses vector features (i.e. where to place river marker on river walley crossection).

: '''Author:''' Maris Nartiss

==== v.random.cover ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.random.cover v.random.cover] is a shell script for creating random points constrained within an irregularly shaped vector area. (v.random places points only in current region rectangle). Optionally the user can upload raster values at the points. See also '<tt>r.random cover= vector_output=</tt>'

: '''Author:''' Hamish Bowman

==== v.rasterbounds ====

: [http://les-ejk.cz/programs v.rasterbounds] is a shell script for creating polygon-vector file of rasterfile boundaries. The best version of GRASS is 6.1+. If you are using GRASS < 6.1, you have to be in the same mapset as your raster maps are from.

: '''Author:''' Jachym Cepicky

==== v.rast.stats2 ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.rast.stats2 v.rast.stats2] is an adapted version of the GRASS module v.rast.stats. It uses the grass addon [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.univar2.zonal r.univar2.zonal] to speed up calculation of univariate statistics from a GRASS raster map based on vector polygons.

: '''Authors:''' Markus Neteler, Otto Dassau

==== v.sample.buffer [broken link, please update or delete]====

: [http://www.clubwebcanada.ca/twiens/v.sample.buffer.tgz v.sample.buffer] is a shell script that samples rasters in buffers of a specified size around features in a specified vector file. Sampling results are added as attributes to the vector file. This script was designed for sampling vegetation indices and DEM derived attributes for bird point counts. Sampling results can be one or more basic statistics such as mean, range, max, etc.

: '''Author:''' Trevor Wiens

==== v.select.region ====

: [ftp://gsca.nrcan.gc.ca/outgoing/Patton/Grass/Scripts/v.select.region.tar.bz2 v.select.region] is a shell script that prints out the names of all vectors matching an input search pattern that has geometry (points, line, areas) that fall within a region bounded by an existing vector map, or within the current Grass region.

: '''Author:''' Eric Patton

==== v.selmany ====

: [http://svn.osgeo.org/grass/grass-addons/vector/v.selmany/v.selmany v.selmany] is a shell script that allows to interactively select a set of vector objects on a given layer, then assign them attribute values in a connected database table. The script runs on the command line prompt and within a graphic monitor ; it does not work with DBF driver.

: '''Author:''' Vincent Bain

==== v.surf.icw ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.surf.icw v.surf.icw] is an IDW interpolation method using true distance cost instead of euclidean shortest distance, i.e. ''as the fish swims around an island'' not ''as the bird flies''. This will cleanly travel around hard barriers and a cost surface map may be used to model expensive-cross barriers. Input data points do not need direct line of sight to be considered, but should be kept to less than one hundred as the module becomes very computationally expensive. A number of radial basis function options are available. ([http://grass.osgeo.org/wiki/Image:Inlets_03_SurfSal_icw_big.png screenshot])

: '''Author:''' Hamish Bowman

==== v.surf.idwpow ====

: [http://www.geospatial.it/allegri/grass/v.surf.idwpow.zip v.surf.idwpow] integrates the common v.surf.idw algorithm with the exponential parameter for the distance weights

: '''Author:''' Giovanni Allegri

==== v.surf.krige [deprecated: use v.autokrige instead] ====

: v.surf.krige is a script that do a surface interpolation from vector point data by Kriging method. The interpolated value of a cell is determined by using an omnidirectional variogram model fitted starting from model parameter given by user shown from the experimental semi variogram produced by v.variogram. The script can perform also the Leave-One-out cross validation to test the variogram model "fitted by eye" and an automatic fitted variogram model. The cross validation helps the user to choose the best variogram model to interpolate own data.

: '''Author:''' Pierluigi De Rosa.

==== v.strahler ====

: [http://www.pois.org/florian/downloads/grass/v.strahler.tgz v.strahler] is a module that calculates the Strahler Order for all lines of a given dendritic network.

: '''Author:''' Florian Kindl. Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/vector/v.strahler

==== v.swathwidth ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.swathwidth v.swathwidth] creates a vector map representing the sea bottom coverage of a multibeam (swath) sonar survey.
: ([http://david.p.finlayson.googlepages.com/swathwidth Screenshots])

: '''Authors:''' David Finlayson, Hamish Bowman

==== v.thickness ====

: [http://marcin.slodkowski.googlepages.com/v.thickness.tgz v.thickness] creates points of thickness vectors from the vectors of strike and dip angles.The v.thickness is GUI GRASS script for v.dip.

: '''Author:''' Marcin Slodkowski

==== v.transect.kia ====

: [https://svn.osgeo.org/grass/grass-addons/vector/v.transect.kia v.transect.kia] calculates kilometric abundance indexes (KIA), a common indirect presence index used in wildlife monitoring along line transect surveys.
: Path lenghts can be corrected by draping on a DEM, different type of point objects can be weighted according to their relative importance, and paths can be segmented using a further polygon vector (to calculate, say, abundances per elevation range or per habitat class).
: The module is written in bash and needs a GRASS install compiled with sqlite support.

: '''Author:''' Clara Tattoni and Damiano G. Preatoni

==== v.trees3d ====

: [http://les-ejk.cz/programs/ v.trees3d] is a module for making 3D trees from input vector point file.

: '''Author:''' Jachym Cepicky

==== v.trimesh ====
: [http://www.valledemexico.ambitiouslemon.com/vtrimesh.html v.trimesh] creates a triangular mesh from a vector map using areal constraints for refinement. It uses Jonathan Shewchuk's Triangle library.

: '''Author:''' Jaime Carrera

==== v.what.rast.buffer ====

: [http://trac.osgeo.org/grass/browser/grass-addons/vector/v.what.rast.buffer v.what.rast.buffer] is a script that calculates univariate statistics of raster map(s) from buffers around vector points. Results are written to a file. Resolution is taken from each input map.
: ''see also the [http://starspan.casil.ucdavis.edu StarSpan] software

: '''Author:''' Hamish Bowman

==== v.variogram [deprecated: use v.autokrige instead] ====

: v.variogram is a script that create an omnidirectional experimental semi-variogram. This scripts require R-statistics software installed on your machine. Now the script is updated to run on spgrass6 >= 0.3 and sp >= 0.9 [http://grass.osgeo.org/pipermail/statsgrass/2006-October/000455.html reply].

: '''Author:''' Ivan Marchesini, Pierluigi De Rosa.

==== AniMove ====

: [http://www.faunalia.it/animov/ AniMove] is software for analysis of animal movement and ranging behaviour using QGIS+GRASS+R.

:'''Authors:''' Support by Faunalia.it

==== Utilities ====

===== Shapemerge =====

: [http://perrygeo.googlecode.com/svn/trunk/gis-bin/shpmerge.sh shpmerge] merges all the shapefiles in the current directory into a single output shapefile

:'''Authors:''' Perrygeo

=== Raster add-ons ===

See also

svn co <nowiki>https://svn.osgeo.org/grass/grass-addons/raster</nowiki>

==== r.bilateral ====

: [http://les-ejk.cz/files/programs/grass/r.bilateral.tgz r.bilateral] Bilateral filter is an edge-preserving filter, which combines domain and range filtering. It is written in C language.

: '''Author:''' Jachym Cepicky

==== r.boxcount ====

: r.boxcount and r.boxcount.sh calculate the fractal dimension for a given map. These are versions for grass6 of [http://www.ucl.ac.uk/~tcrnmar/ Mark Lake's modules] for grass43.

: '''Authors:''' Mark Lake, grass6 port: Florian Kindl.

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.boxcount/
svn co https://svn.osgeo.org/grass/grass-addons/raster/r.boxcount.sh/

==== r.burn.frict ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.burn.frict r.burn.frict] converts vector geometries to raster cells, using a simple anti-aliasing method to close "gaps" between diagonal cells. Useful for "burning" vector geometries into a friction surface, making sure that simulated movement does not "slip" through converted cells that have only diagonal neighbours.

:'''Author:''' Benjamin Ducke

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.burn.frict

==== r.colors.quantiles ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.colors.quantiles/r.colors.quantiles r.colors.quantiles] is a shell script used to create raster colors rules based on nquantiles. It uses R and spgrass6 package (RGRASS).

: '''Authors:''' Mathieu Grelier

==== r.colors.stddev ====

: [http://hamish.bowman.googlepages.com/grass_color_maps r.colors.stddev] ''moved into main archive''

==== r.cpt2grass ====

: [http://hamish.bowman.googlepages.com/grass_color_maps r.cpt2grass] is a GRASS script for importing a [http://www.soest.hawaii.edu/gmt/ GMT] .cpt color table into GRASS. It can save to a text file suitable for r.colors or automatically apply the color table to a raster map. For a large collection of GMT .cpt files see http://sview01.wiredworkplace.net/pub/cpt-city/
: Other palette ideas from [http://geography.uoregon.edu/datagraphics/color_scales.htm Univ. Oregon] and [http://oceancolor.gsfc.nasa.gov/PRODUCTS/colorbars.html NASA/Goddard's OceanColor] (latter partially translated for use with GRASS on the [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.colors.tools/palettes grass-addons SVN]).

: '''Author:''' Hamish Bowman

==== r.csr ====

: [http://www.chrisgarstin.com/stuff/r.csr r.csr] integrates several Grass programs to produce colored, shaded-relief rasters in one step. Accepts single or multiple elevation/bathymetry maps as input; optionally will fill data holidays with 3x3 median filter, multiple times, if required; can apply color maps from a) input raster, b) another raster in MAPSET, or c) from a rules file; otherwise, rainbow colorbar is applied. Output colored, shaded-relief rasters can optionally be exported to tiff format if the appropriate flag is given. Shading parameters can be modified, though useful defaults are given.

: '''Author:''' Eric Patton

==== r.cva ====

: [http://www.ucl.ac.uk/~tcrnmar/GIS/r.cva.html r.cva] is a cumulative viewshed analysis module. It is an advanced version of the {{cmd|r.los}} program.

: '''Author:''' [http://www.ucl.ac.uk/~tcrnmar/ Mark Lake]

==== r.denoise ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.denoise r.denoise] denoises (smooths/despeckles) topographic data, particular DEMs derived from radar data (including SRTM), using Xianfang Sun's [http://www.cs.cf.ac.uk/meshfiltering/index_files/Page342.htm denoising algorithm]. It is designed to preserve sharp edges and to denoise with minimal changes to the original data. See the [http://personalpages.manchester.ac.uk/staff/john.stevenson/mdenoise/r.denoise.html manual pages] for details. Further information on Sun's denoising algorithm, including an example, is available [http://personalpages.manchester.ac.uk/staff/john.stevenson/mdenoise here].

: '''Author:''' John Stevenson

==== r.dominant_dir.m and r.calc_terraflow_dir.m ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.terraflow.tools dominant_dir.m and calc_terraflow_dir.m] are two Matlab scripts for determining the dominant flow direction from a r.terraflow MFD map and converting into a GRASS aspect map for use with d.rast.arrow, etc.

: '''Author:''' Hamish Bowman

==== r.eucdist ====

: [http://david.p.finlayson.googlepages.com/r.eucdist r.eucdist] creates a raster map estimating the euclidean distance from known cells.

: '''Author:''' David Finlayson

==== r.fragment ====

: [http://www.chrisgarstin.com/stuff/r.fragment r.fragment] fragments a raster into a user-defined set of smaller tiles according to an input number of rows and columns.
: '''Author:''' Eric Patton

==== r.fuzzy ====
: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.fuzzy r.fuzzy] Calculates membership of every cell in raster according membership function defined by user.
: '''Author:''' Jarek Jasiewicz

==== r.fuzzy.logic ====
: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.fuzzy.logic r.fuzzy.logic] Perform fuzzy operators (AND, OR, NOT, IMP) on membership's map using T-norms and T-conorms for 6 most popular families.
: '''Author:''' Jarek Jasiewicz

==== r.game_of_life ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.game_of_life r.game_of_life] is a shell script which runs Conway's classic Game of Life using GRASS raster modules. It is meant to demonstrate how easy it is to program cellular automata in GRASS as well as various 3D raster volume and time series visualization techniques.

: '''Author:''' Hamish Bowman

==== r.gauss ====

: [http://www.les-ejk.cz/files/programs/grass/r.gauss.tgz r.gauss] is Gaussian and Laplacian of Gaussian filter for GRASS. It is written in C language.

:'''Author:''' Jachym Cepicky

==== r.gradgrid4 ====

: [http://www.uibk.ac.at/geographie/personal/mergili/gradgrid4.zip gradgrid4] is a tool for interpolating values of discrete data points to a raster map, applying a local regression approach with a predictor raster. The model is based on shell and python scripts as well as an R batchfile. It was tested on Fedora Core 6 with GRASS 6.2.1 and R 2.5.1, but should work under most UNIX systems. After unzipping the gradgrid4 folder, store it at any place in your local file system. In the subfolder docs you can find a manual and a publication draft with a detailed description of the concept and the example of an application. The subfolder testloc constitutes a GRASS location with test data.

: '''Author:''' Martin Mergili

==== r.in.mb ====

: [http://blogs.tekmap.ns.ca/archives/458 r.in.mb] is a "GRASS/[[MB-System]] program designed to import ''mbio'' compatible multibeam sonar data directly into the GRASS GIS. The program is a modified version of {{cmd|r.in.xyz}}. Instead of reading an ASCII XYZ file, ''r.in.mb'' reads an MB-System compatible list file." It can do automatic reprojection and minor hole filling. The default is to import bathymetry data, but optionally amplitude or sidescan sonar data can be loaded instead.

: '''Author:''' Bob Covill

==== r.in.onearth ====

: [http://www-pool.math.tu-berlin.de/~soeren/grass/modules/ r.in.onearth] for download and import satellite images direct from the NASA onearth WMS server into GRASS.

: '''Author:''' Soeren Gebbert

==== r.in.wms (.py) ====

: [http://les-ejk.cz/files/programs/grass/r.in.wms.tgz r.in.wms] for download and import maps direct from WMS servers into GRASS. This script is written in Python Programming language. Note GRASS 6.2+ provides a shell script version of r.in.wms, take care of which one is actually being run.

: '''Author:''' Jachym Cepicky

==== r.inund.fluv ====

: [https://svn.osgeo.org/grass/grass-addons/raster/r.inund.fluv/ r.inund.fluv]This command allows to obtain a fluvial potentially inundation map given a high-resolution DTM of the area surrounding the river and a water surface profile calculated through an 1-D hydrodinamic model.

: '''Authors:''' Roberto Marzocchi, Bianca Federici, Domenico Sguerso

==== r.isoregions ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.isoregions/r.isoregions r.isoregions] allows isoregions creation from a GRASS raster map.

: '''Authors:''' Mathieu Grelier

==== r.interp.mask ====

: [http://david.p.finlayson.googlepages.com/r.interp.mask r.interp.mask] Creates a user-specified buffer around interpolation points that can be used as a MASK to prevent or clip excessive extrapolation artifacts. This works much better than a standard convex hull around the points.

: '''Author:''' David Finlayson

==== r.li ====

: [http://www.faunalia.it/download/r_li/ r.li] is a more flexible and faster replacement of the old r.le. '''''Moved into 6.3-SVN'''''.

: '''Authors:''' Claudio Porta, Davide Spano, Serena Pallecchi, [http://www.faunalia.it Faunalia]

==== r.local_max.pl ====

: [http://les-ejk.cz/files/programs/local_max.pl Local maxima] is a Perl script for <code>r.mapcalc</code>. It detects local maxima of the image.

: '''Author:''' Jachym Cepicky

==== r.mandelbrot ====

: [http://grasslab.gisix.com/scripts/r.mandelbrot r.mandelbrot] is a shell script to calculate the Mandelbrot set.- for GRASS versions 6.X.

: '''Author:''' Peter Löwe

==== mcda====

: mcda suite is a toolset for geographics multi-criteria decision aiding and data analysis based on ELECTRE (r.mcda.electre), REGIME (r.mcda.regime) and FUZZY (r.mcda.fuzzy) algorithm. The module r.roughset is also included for geographics rough set analisys and knowledge discovery based on rough set library. It is written in C language for GRASS versions 6.X.

: '''Author:''' Gianluca Massei (g_massa@libero.it ) - Antonio Boggia

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/mcda/

==== r.mlv ====

: [http://les-ejk.cz/files/programs/grass/r.mlv.tgz r.mlv] is Mean of least variance filter for GRASS. It is an edge-preserving (or even edge-enhacing) filter, which should serve for removing additive noise from images. It is written in C language.

: '''Author:''' Jachym Cepicky

==== r.out.jpeg ====

: [http://www.geospatial.it/allegri/grass/r.out.jpeg_ r.out.jpeg] is a simple GRASS script to export georeferenced JPEG images from rasters, keeping the associated color table. It is a two-step export: first a ppm file is created, then it is converted to jpeg usgin the "convert" command from ImageMagick

: '''Author:''' Giovanni Allegri

==== r.out.gmap ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.out.gmap r.out.gmap] outputs GRASS raster map into set of image tiles
following the tiling scheme of Google Maps and Microsoft Virtual Earth. Read more in the OSGeo Journal [http://www.osgeo.org/journal Volume 5 (2009, to appear)] see also [[#r.out.kml|r.out.kml]] and [[#v.out.kml|v.out.kml]]

: '''Author:''' Tomas Cebecauer

==== r.out.gmt ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.out.gmt r.out.gmt] is a GRASS script for exporting a GRASS raster map into a [http://www.soest.hawaii.edu/gmt/ GMT] grid file. It also creates a GMT color table from the data and can generate some GMT commands for plotting a postscript file. (code is experimental, but functional) see also http://169.237.35.250/~dylan/grass_user_group/#GMT_and_GRASS-overview

: '''Authors:''' Hamish Bowman, Dylan Beaudette

==== r.out.gmt2 ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.out.gmt2 r.out.gmt2] is a modified version of Hamish's r.out.gmt. Added options for title, xlabel, ylabel, comment, and map width. Removed any settings that can be changed by gmtset for more flexibility.

: '''Author:''' Huidae Cho, Hamish Bowman, Dylan Beaudette

==== r.out.kml ====

: [https://trac.osgeo.org/grass/browser/grass-addons/raster/r.out.kml r.out.kml] is a shell script that exports a raster map into a KML file and image for Google Earth or Worldwind. See also [[#v.out.kml|v.out.kml]] and [[#r.out.gmap|r.out.gmap]].

: '''Author:''' Hamish Bowman

==== r.pack ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.pack r.pack and r.unpack] are two GRASS scripts for transfering raster maps to another computer as a single file.

: '''Author:''' Hamish Bowman

==== r.prominence ====
'''r.prominence''' calculates the average difference between a central cell and its neighbors. It approximated the terrain 'ruggedness' by looking at average differences in elevation within a given neighborhood.
: '''Author:''' Benjamin Ducke

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.prominence/

==== r.roughness ====

[http://trac.osgeo.org/grass/browser/grass-addons/raster/r.roughness/r.roughness.sh r.roughness.sh] is a shell script to calculate the surface roughness of a DEM, using r.surf.area and v.surf.rst. (for GRASS versions 6.1 and above)

[http://www.igc.usp.br/pessoais/guano/downloads/r.roughness60 r.roughness60] - for GRASS versions 6.0.X

[http://trac.osgeo.org/grass/browser/grass-addons/raster/r.roughness/r.roughness.window.area r.roughness.window.area] - calculate surface roughness as the ratio of real (surface) area and planar area, using a moving-window approach.

[http://trac.osgeo.org/grass/browser/grass-addons/raster/r.roughness/r.roughness.window.vector r.roughness.window.vector] - calculate surface roughness as vector dispersion, using a moving-window approach. Resulting maps are: Vector Strength (R) and Inverted Fisher's k parameter.

[http://trac.osgeo.org/grass/browser/grass-addons/raster/r.roughness/r.roughness.window.vector.html r.roughness.window.vector.html] - provisional help page for r.roughness.window.vector.

: '''Author:''' Carlos Henrique Grohmann

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.roughness/

==== r.roughset ====

: r.roughset is a module for geographics rough set analisys and knowledge discovery based on rough set library. It is written in C language for GRASS versions 6.X.

: '''Author:''' Gianluca Massei (g_massa@libero.it ) - Antonio Boggia

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/mcda/r.roughset/

==== r.smoothpatch ====

: [http://david.p.finlayson.googlepages.com/r.smoothpatch r.smoothpatch] creates a composite of two rasters using a distance-weighted average across the transition to smooth the edges.

: '''Author:''' David Finlayson

==== r.soils.texture ====

: r.soils.texture is a module to define soils texture from sand and clay raster file with a schema text file (now FAO,USDA and ISSS are available). It is written in C language. - for GRASS versions 6.x - For bugs and suggest: g_massa@libero.it

:'''Author:''' Gianluca Massei

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.soils.texture/

==== r.stream.angle ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.stream.angle r.stream.angle] Divide stream network into stright line segments according users input. It extends Module uses as input direction and stream netwokr map produced by r.watershed and stream.extract or custom user input. See description for details.

: '''Author:''' Jarek Jasiewicz

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.stream.angle

==== r.stream.basins ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.stream.basins r.stream.basins] delineate basins according users input. It extends r.water.outlet funcionality to extracting more than one basin at one step. Module uses as input direction map produced stream network produced by r.stream.extract, r.watershed, r.stream order or custom user input. More in tutorial on grass-wiki pages.

: '''Author:''' Jarek Jasiewicz

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.stream.basins

==== r.stream.del ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.stream.del r.stream.del] Calculates downslope length of first order streams and delete them if it length (in pixels) is lower than the treeshold. It also join false segments left by deletion into one with category of upper. It uses r.watershed direction map and r.watershed stream map as input. The module is added only for r.watershed module, r.stream.extract has deleting short streams build-in. During development of r.stream.* it will be probably abandoned due to duplicate functionality

: '''Author:''' Jarek Jasiewicz

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.stream.del

==== r.stream.distance ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.stream.distance r.stream.distance] Calculates downslope distance and downslope elevation difference between current cell and stream or outlet cells. It uses r.watershed direction map, r.watershed or r.stream.extract stream map and optionally DEM as input.

: '''Author:''' Jarek Jasiewicz

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.stream.distance

==== r.stream.extract ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.stream.extract r.stream.extract] extracts topologically clean stream networks from input elevation and optionally accumulation maps. Output is available as raster and vector and can be used as input for the other r.stream.* modules by Jarek Jasiewicz.

: '''Author:''' Markus Metz

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.stream.extract

==== r.stream.order ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.stream.order r.stream.order] orders stream network outputed by r.watershed or r.stream.extract according Sthrahler, Shreve, Horton and Hack ordering systems. It require as input stream and direction map and optionally accumulation map. It handle both SFD nad MFD modes but all data must come from the same procedure.

: '''Author:''' Jarek Jasiewicz, Markus Metz

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.stream.order

==== r.stream.pos ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.stream.pos r.stream.pos] Helper module for calculating local stream network properties and linear geostatistics. Mostly To use with R and other grass modules.

: '''Author:''' Jarek Jasiewicz

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.stream.pos

==== r.stream.stats ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.stream.stats r.stream.stats] calculate Hortonian statistics for Stahler or Horton stream network created by r.stream.order. It uses r.watershed direction map, DEM and r.stream.order's Stahler or Horton stream network as input. It outputs calculated statistics to standard output.

: '''Author:''' Jarek Jasiewicz

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.stream.stats

==== r.surf.nnbathy ====

: [http://www.sieczka.org/programy_en.html r.surf.nnbathy] interpolates a surface from a raster input using Pavel Sakov's [http://code.google.com/p/nn-c/ nn] natural neighbor interpolation library. Provides triangulation, Sibson natural neighbor interpolation and non-Sibsonian interpolation.

: '''Author:''' Maciej Sieczka

==== r.surf.volcano ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.surf.volcano r.surf.volcano] creates an artificial surface resembling a seamount or cone volcano. The user can alter the size and shape of the mountain and optionally roughen its surface. Available decay functions are polynomial, Gaussian, Lorentzian, logarithmic, and exponential.

: '''Author:''' Hamish Bowman

==== r.terracost ====

[http://www.bowdoin.edu/~ltoma/research.html r.terracost] Scalable approach for computing least-cost-path surfaces on massive grid terrains. '''Lead author''': Laura Toma

Available via SVN:
svn co https://svn.osgeo.org/grass/grass-addons/raster/r.terracost

==== r.tileset ====

: ''{{cmd|r.tileset}} moved into main archive''

==== r.traveltime ====

: [http://jesbergwetter.twoday.net/stories/4845555/ r.traveltime] computes the travel time of surface runoff to an outlet. The program starts at the basin outlet and calculates the travel time at each raster cell recursively. A drainage area related threhold considers even surface and also channel runoff. Travel times are derived by assuming kinematic wave approximation. The results can be used to derive a time-area function. This might be usefull for precipitation-runoff calculations (estimation of flood predictions) with a lumped hydrologic model (user-specified unit hydrograph).

: '''Author:''' Kristian Förster

==== r.univar.zonal ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.univar2.zonal r.univar.zonal] is similar to r.univar, but calculates statistics separately for each category(zone) present in the separate input map used to define zones (zonal statistics). The output can be like the one of r.univar or in easier to read table format and can be written to a file.

: '''Author:''' Markus Metz

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.univar2.zonal

==== r.viewshed ====

: r.viewshed is a module for extremely fast line of sight analysis (replaces the slow r.los). It is written in C language for GRASS versions 6.X/7.x.

: '''Author:''' Laura Toma, USA

Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.viewshed

Once {{trac|390}} is solved, it will substitute r.los.

==== r.xtent ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.xtent r.xtent] computes a raster map layer representing the Voronoi diagram, weighted Voronoi diagram or a more complex territorial partitioning of space around points (centers) in a vector input map, based on the XTENT formula.

:'''Author:''' Benjamin Ducke

svn co https://svn.osgeo.org/grass/grass-addons/raster/r.xtent

==== r.zc.pl ====

: [http://les-ejk.cz/files/programs/zc.pl Zero crossing] is a simple Perl script, finds the ,,zero crossings`` from the Laplacian of Gaussian filter (see above). It is really very simple, the edges don't need to be really on that pixel, where they are detected, no interpolation is performed.

: '''Author:''' Jachym Cepicky

==== GIPE ====

: The GRASS Image Processing Environment (GIPE) has USLE, Energy-balance and radiance-reflectance correction models.

: '''Author:''' Yann Chemin (unless specified otherwise).

svn co https://svn.osgeo.org/grass/grass-addons/gipe

Remark: This is progressively moved to main GRASS SVN (aka GRASS 7)

:* r.hydro.CASC2D, ported from GRASS 5.x version, is temporarily here waiting to return to main GRASS.

:* r.soiltex2prop creates porosity, Saturated Hydraulic conductivity (Ksat) and wetting front pressure head (Hf) from percentage of sand and clay after Rawls et al., 1990. This is a must for r.hydro.CASC2D.

:* i.biomass creates biomass growth map from fPAR, lightuse efficiency, water availability (or evap.fraction), Lat, doy and tsw.

:* i.dn2ref.l7, r.dn2ref.ast create top of atmosphere reflectance for Landsat 7ETM+ and ASTER. These modules also have a flag for radiance output. Updated i.dn2ref.l7 to read .met calibration file.

:* i.dn2full.l[5,7] is an attempt to get all bands of Landsat[5,7] calibrated and corrected to either reflectance or temperature, reads only the .met file.

:* i.dn2potrad.l[5,7] is an attempt to get ET potential from DN of Landsat 7 (Careful! No Atmospheric correction!).

:* i.eb.* are a set of 10+ GRASS modules that together perform the main functions of the SEBAL model (Bastiaanssen, 1995). Those functions include (but are not limited to) Soil heat flux, sensible heat flux, net radiation, evaporative fraction at satellite overpass, diurnal actual evapotranspiration, momentum roughness length, etc. These modules are also part of any Energy-Balance related processing.

:* i.evapo.potrad creates diurnal Potential evapotranspiration assuming all net radiation becomes ET, according to SEBAL model (Bastiaanssen, 1995). This module also has a flag for diurnal net radiation as required by SEBAL in i.eb.eta.

:* i.evapo.SENAY creates actual evapotranspiration following the regional method of Senay (2007).

:* i.lmf creates a Local Maximum Fitting on the temporal dimension of the multi-date input dataset, working, but more precision still to be added.

:* i.vi.mpi is the mpi version of i.vi for cluster GRASS GIS education (no speed up here!) '''Author:''' Shamim Akhter

:* i.modis.stateqa extracts State Quality Assessment information from Modis 500m (MOD09A) products.

:* i.water creates a Water Mask from NDVI and Albedo, or specifically for Modis: NDVI and Band 7.

:* i.wi creates a given Water Index (only one so far).

==== HydroFOSS ====

: HydroFOSS - a GIS embedded approach for Free & Open Source Hydrological modeling.

: '''Author:''' Massimiliano Cannata

svn co https://svn.osgeo.org/grass/grass-addons/HydroFOSS/

==== Hikereport ====

: python script that computes length, cumulative uphill and downhill, average slopes on an interactively drawn path. Based on r.profile's output.

: '''Author:''' Stefano Negri

http://tracce.wordpress.com/?attachment_id=71

=== Misc add-ons===

==== m.eigensystem ====

m.eigensystem - Computes eigen values and eigen vectors for square matrices.

: http://svn.osgeo.org/grass/grass-addons/misc/m.eigensystem/

: '''Author:''' Michael Shapiro

===Database add-ons===
==== db.join ====

: Table joining: join one table into another through common attributes

: '''Author:''' Markus Neteler. Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/database/db.join/
or
g.extension db.join

===General add-ons===

==== g.laptop.sh ====

: [http://www.nature-consult.de/dassau/g.laptop/g.laptop.sh g.laptop.sh] is an interactive shell script to extract raster and vector data from current Location into a new one. Data can be copied or extracted in current or original resolution and region extend. This script was written to extract smaller parts of a GRASS location to be able to present them on a laptop without the necessity to transfer huge data. Maps do not have to be in the same mapset.

: '''Author:''' Otto Dassau

==== Readline completion ====

: '''''Readline completion''''' for GRASS commands under the bash shell: [http://www.sorokine.info/grass-complete/ grass-complete] won't clutter the environment but needs to be installed; [http://dcalvelo.free.fr/grass/grass_rlcompleter.sh grass_rlcompleter.sh] needs almost no installation but will pollute the environment. Grass-Complete currently requires Bash version 2.05 for proper install.

: '''Author:''' Alexandre Sorokine (grass-complete), Daniel Calvelo (grass_rlcompleter.sh)

==== g.region.point ====

: [http://trac.osgeo.org/grass/browser/grass-addons/general/g.region.point g.region.point] is a shell script which resets the computational region to a square box around a given coordinate. It is intended for use within GRASS scripts to speed up processing by limiting expensive raster calculations to a small area of interest.

: '''Author:''' Hamish Bowman

==== g.linke_by_day ====

: [http://trac.osgeo.org/grass/browser/grass-addons/raster/r.sun.tools/ g.linke_by_day] is a python script for [[r.sun]] which interpolates a Linke turbidity value for a given day of the year based on monthly values edited into the script.

: '''Author:''' Hamish Bowman

==== g.xlist ====

: [http://trac.osgeo.org/grass/browser/grass-addons/general/g.xlist g.xlist] is a C implementation of g.mlist. g.xlist searches for data files matching a pattern given by wildcards or POSIX Extended Regular Expressions. POSIX regex(3) functions are required.

: '''Author:''' Huidae Cho

==== g.xremove ====

: [http://trac.osgeo.org/grass/browser/grass-addons/general/g.xremove g.xremove] is a C implementation of g.mremove. g.xremove removes data files matching a pattern given by wildcards or POSIX Extended Regular Expressions. POSIX regex(3) functions are required.

: '''Author:''' Huidae Cho

=== Imagery add-ons ===

See also

svn co https://svn.osgeo.org/grass/grass-addons/imagery

==== GIPE ====

GIPE (see also above in raster section) provides:
i.biomass, i.dn2potrad.l5, i.dn2potrad.l7, i.dn2ref.ast, i.eb.deltat, i.eb.disp, i.eb.eta, i.eb.evapfr, i.eb.g0, i.eb.h0, i.eb.h_SEBAL01, i.eb.h_SEBAL95, i.eb.h_iter, i.eb.molength, i.eb.netrad, i.eb.psi, i.eb.rah, i.eb.rohair, i.eb.ublend, i.eb.ustar, i.eb.wetdrypix, i.eb.z0m, i.eb.z0m0, i.evapo.PT, i.evapo.TSA, i.evapo.potrad, i.evapo.senay, i.evapo.time_integration, i.lmf, i.modis.stateqa, i.sattime, i.vi.grid, i.vi.mpi, i.water, i.wi

svn co https://svn.osgeo.org/grass/grass-addons/gipe/

: '''Author:''' Yann Chemin

==== i.homography ====

Rectifies an image by computing a coordinate transformation for each pixel in the image based on the control points created by i.linespoints. The approach uses homography extended for corresponding lines.

svn co https://svn.osgeo.org/grass/grass-addons/imagery/i.homography

: '''Author:''' Daniel Grasso, Bolzano, Italy, based on code written by Stefano Merler, ITC-irst, Italy

==== i.linespoints ====

An imagery command that enables the user to mark coordinate system points as well as lines on an image to be rectified and then input the coordinates of each point for creation of a coordinate transformation matrix. The transformation matrix is needed as input for the GRASS program i.homography.

svn co https://svn.osgeo.org/grass/grass-addons/imagery/i.linespoints

: '''Author:''' Daniel Grasso, Bolzano, Italy, based on i.points

==== i.landsat.toar ====

Transform calibrated digital number of Landsat products to top-of-atmosphere radiance or top-of-atmosphere reflectance and temperature (band 6 of the sensors TM and ETM+). Optionally, used to calculate the at-surface radiance or reflectance with atmospheric correction (DOS method).

svn co https://svn.osgeo.org/grass/grass-addons/imagery/i.landsat.toar

: '''Author:''' E. Jorge Tizado

==== i.points.auto ====

This module allows a search of GCP's on two raster-maps with differents levels of automation. The ''manual'' search is the default search, so it's possible to determine the GCP's manually with the mouse (like {{cmd|i.points}}). ''Semiautomated'' search: The user determines with the mouse some correspondent areas (with a discrete precision) in the two maps and the module searches itself the GCP's in these areas. ''Automated'' search: At the start of module the user has to load the maps that the algorithm uses to the search, so it is recommended to use the maps filtered with the filters DIVERSITY or STDDEV (of GRASS) with a window of 3x3 or 5x5 pixels. However, the algorithm sometimes works well with the original maps too.

Note: This code is basically an improved i.points (from 2004). Subsequent changes in i.points haven's been ported here yet.

svn co https://svn.osgeo.org/grass/grass-addons/imagery/i.points.auto

: '''Authors:''' based on i.points; additions by Ivan Michelazzi, Luca Miori (MSc theses at ITC-irst); Supervisors: Markus Neteler, Stefano Merler, ITC-irst 2003, 2004. [http://gisws.media.osaka-cu.ac.jp/grass04/viewpaper.php?id=37 PDF article]

==== i.points.reproj ====

: [http://trac.osgeo.org/grass/browser/grass-addons/imagery/i.points.reproj i.points.reproj] is a shell script that will use cs2cs to reproject the target coordinates of a group's POINTS file. By running i.rectify directly to the new target projection, a generation of resampling data loss can be avoided (versus i.rectify + r.proj). On the other hand, i.rectify does not calculate cell resolution well if the map is to be rotated ([http://intevation.de/rt/webrt?serial_num=3296 bug #3296]), in those cases i.rectify+r.proj may be the better option.

: '''Author:''' Hamish Bowman

==== i.plr.py ====

: [[I.plr.py|Probabilistic Label Relaxation]], written in Python

: '''Author:''' Georg Kaspar

==== i.pr ====

: Image classification: implements k-NN (multiclass), classification trees (multiclass), maximum likelihood (multiclass), Support Vector Machines (binary), bagging versions of all the base classifiers, AdaBoost for binary trees and support vector machines. It allows feature manipulation (normalization, principal components,...). It also implements feature selection techniques (RFE, E-RFE,...), statistical tests on variables, tools for resampling (cross-validation and bootstrap) and cost-sensitive techniques for trees and support vector machines.

: '''Author:''' Stefano Merler. Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/imagery/i.pr

==== i.spec.sam ====

: Spectral Angle mapping

: '''Author:''' Markus Neteler. Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/imagery/i.spec.sam/

==== i.spec.unmix ====

: Spectral unmixing

: '''Author:''' Markus Neteler. Available via SVN:

svn co https://svn.osgeo.org/grass/grass-addons/imagery/i.spec.unmix/

==== i.warp ====

: [http://trac.osgeo.org/grass/browser/grass-addons/imagery/i.warp i.warp] is a shell script that will use gdalwarp to rectify a raw input image using thin plate splines. The map should be imported into GRASS with r.in.gdal and GCPs set with i.points. Input is the raw image (GeoTIFF, JPEG, etc). Output is a GeoTIFF in the imagery group's target location's map projection. Requires a recent (early 2006) version of GRASS 6.1, or newer.

: '''Author:''' Hamish Bowman

=== Display add-ons ===

See also

svn co https://svn.osgeo.org/grass/grass-addons/display

==== d.edit.rast ====

: [http://trac.osgeo.org/grass/browser/grass-addons/display/d.edit.rast d.edit.rast] edits cells in an existing raster map displayed on the current monitor.

: '''Author:''' Huidae Cho

==== d.frame.quarter ====

: ('''obsolete''') [http://trac.osgeo.org/grass/browser/grass-addons/display/d.frame.split d.frame.quarter] is a shell script that will split the display into four quadrants (or sixths) using ''d.frame''. Individual frames are named ''uno, dos, tres, cuatro'', and ''full_screen''.
: Replaced by {{cmd|d.split.frame}} in main.

: '''Author:''' Hamish Bowman

==== d.frame.split ====

: ''d.frame.split moved into main archive as {{cmd|d.split.frame}}''

==== d.hyperlink ====

: [ftp://gsca.nrcan.gc.ca/outgoing/Patton/Grass/Scripts/d.hyperlink.tar.bz2 d.hyperlink] is an interactive shell script that allows the viewing of hyperlinked images from a vector's attribute table in an external image viewer. Queries can be made via SQL statements or interactive mouse-clicking. The attribute table must be pre-populated with a column containing the image to link the vector to; the user also specifies the image folder in the current MAPSET where the images are located. The script currently supports gimp, Eye of Gnome, gthumb, gpdf, and Inkscape image viewers.

: '''Author: '''Eric Patton

==== d.mark ====

: [http://trac.osgeo.org/grass/browser/grass-addons/display/d.shortcuts d.mark] is a shell script that quickly displays a marker on the display at a given coordinate.

: '''Author:''' Hamish Bowman

==== d.region.box ====

: [http://trac.osgeo.org/grass/browser/grass-addons/display/d.region.box d.region.box] is a shell script that quickly displays a box around the current region.

: '''Author:''' Hamish Bowman

==== d.stations ====

: [http://trac.osgeo.org/grass/browser/grass-addons/display/d.shortcuts d.stations] is a shell script that quickly displays vector points (or sites for GRASS 5.4 and below).

: '''Author:''' Hamish Bowman

==== d.varea ====

: [http://trac.osgeo.org/grass/browser/grass-addons/display/d.shortcuts d.varea] is a shell script that quickly displays vector areas.

: '''Author:''' Hamish Bowman

==== pd-GRASS ====

: [http://www.ornl.gov/sci/gist/software/grass/ pd-GRASS]: Parallel Display for GRASS GIS

: '''Author:''' Alex Sorokine

==== [[IconSymbols]] ====

* [[IconSymbols|Symbols]] which can be used with ''d.vect, d.graph'', and ''ps.map''.

=== Postscript add-ons ===

''See also [[ps.map scripts|ps.map samples and templates]]''.

==== ps.atlas ====

: [http://les-ejk.cz/programs/grass/ps.atlas ps.atlas] is a shell script that makes more maps on current region according to input *.psmap file. General map can be stored as vector file. The resulting *.eps maps can be automatically converted to *.pdf files.

: '''Author:''' Jachym Cepicky

==== [[AreaFillPatterns]] ====

* Hatches for ps.map's vareas

===GRASS and UMN Mapserver===

* [http://www.mail-archive.com/mapserver-users@lists.umn.edu/msg00086.html See interesting posting]

[[Category:Community]]
[[Category:Development]]
[[Category:Documentation]]
[[Category:Installation]]

GRASS SoC Ideas 2010

2010-03-14T13:52:23Z

⚠️MarisN: Feel the Power of Anonymous ;)

[[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, 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-12T13:02:34Z

⚠️MarisN: GSOC ideas for OGSF

[[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;">
'''February 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, 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 possible, this could be implemented as ''skin'' to give users choices to also get 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]] - something like a GUI front-end or replacement for {{cmd|ps.map}}

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

* Implement [[wxGUI#Graphical_modeller|graphical modeller]].

=== Raster ===

'''Willing to Mentor:''' (''your name here'')

* idea 1
* idea 2

* 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

=== Vector ===

'''Willing to Mentor:''' (''your name here'')

* idea 1
* idea 2

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

== 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 6.3 Feature Plan

2007-10-30T12:10:50Z

⚠️MarisN: /* In progress */

== GRASS 6.3.x feature plan ==
=== About feature plan ===

To make GRASS releases more often and more predictable, here is GRASS next releases feature plan. This feature plan has to be filled by developers working on GRASS 6.3.

=== TODO GRASS 6.3.0 ===
There is the release branch for 6.3.x, see details at [http://grass.itc.it/devel/cvstags.php CVS: tags and branches]. A release branch is considered as "frozen", only bugfixes can be done.

==== RC1 ====

''released 24 Oct 2007''

* <strike>annoying winGRASS vector/DBMI freeze bug</strike> (Glynn Clements)
* <strike>replace r.proj with r.proj.seg</strike>
* <strike>replace d.text with d.text.new</strike>
* <strike>Windows start script's installed on Linux (grass63.bat etc.) [http://wald.intevation.org/tracker/?group_id=21&atid=204&func=detail&aid=323 #323] and [http://wald.intevation.org/tracker/?group_id=21&atid=204&func=detail&aid=471 #471]</strike> (Glynn Clements)
* <strike>Makefile cleanups for parallel builds [http://wald.intevation.org/tracker/?func=detail&aid=359&group_id=21&atid=204 #359]</strike> (Glynn Clements)
* <strike>r.info and Total Cell count overflow [http://wald.intevation.org/tracker/?func=detail&aid=493&group_id=21&atid=204 #493]</strike> (Glynn Clements, Brad Douglas)
* <strike>Makefile cleanups for MS-Windows</strike> (Glynn Clements)

==== RC2 ====

''not released yet''

* <strike>gis.m: new nice manual pages for GEORECT, ANIMATE and PROILE tool</strike> (Michael Barton)
* <strike>gis.m/georect: fix broken msg which crashed the tool</strike> (Michael Barton)
* <strike>g.version newline fix</strike> (Hamish Bowman)
* <strike>r.stats complilation fix for Slackware</strike> (Huidae Cho)
* <strike>r.terraflow: changed to GPL</strike> (Laura Toma, Glynn Clements)
* <strike>Fix definition of US survey foot</strike> (Glynn Clements)
* <strike>r.out.tiff/db.execute manual bug for extensions</strike> (Paul Kelly)

===== Must do =====

* complete and further stabilize the native [[WinGRASS Current Status|winGRASS port]] (seems to be in a good shape now)

* g.region vect=map -a issues [http://wald.intevation.org/tracker/index.php?func=detail&aid=489&group_id=21&atid=204 #489]
: -- HB 24 Oct 2007: Is this really release critical?
: -- MS 26 Oct 2007: It was, until there was a "one row-off" bug in "g.region vect= res= -a". Fixed by Glynn in last days. A remaining issue, less important, is that "g.region vect= res= -a" needs to be run twice if the initial and target region resolution differ. This is not normal nor desired, but Glynn says it's been this way for years now. I confirm it applies to 6.2 at least too. A must-fix for GRASS 7, propably not to be fixed for legacy reasons in 6.2, and to be decided in regard to 6.3. As to me, I'm for fixing it in 6.3.

* r.out.gdal sets NoData wrong [http://wald.intevation.org/tracker/index.php?func=detail&aid=405&group_id=21&atid=204 #405]
: -- HB 24 Oct 2007: Is this really release critical? - need to find Frank's email on the subject and post it to the bug report. At least for a Byte map the no data value must live somewhere in 0-255, there is no IEEE nan for Ints.
: -- MS 26 Oct 2007: It is critical. It's a data corruption issue.
: -- HB 29 Oct 2007: IMO we just document that GDAL works like that. I don't see another good solution. I still need to look up Frank's answer..

* Update in Web-CVS: http://grass.itc.it/announces/announce_grass630.html

===== Mostly done? =====

* r.in.xyz improvements ([http://wald.intevation.org/tracker/index.php?func=detail&aid=450&group_id=21&atid=205 see GForge patch])
: -- HB 24 Oct 2007: needs testing- commit after 6.3.0 is released
:: -- not sure why not to be committed to HEAD - MN
:: -- HB 29 Oct: It can go into HEAD now, I just haven't done it yet. It should not be in the 6.3.0 release, that was my meaning.

* v.sample improvements ([http://wald.intevation.org/tracker/index.php?func=detail&aid=513&group_id=21&atid=205 see GForge patch])
: -- HB 24 Oct 2007: not ready. needs fixing for NULLs.

* v.what.vect improvements ([http://wald.intevation.org/tracker/index.php?func=detail&aid=374&group_id=21&atid=205 see GForge patch])
: -- HB 24 Oct 2007: waiting for a real world example of when this would be useful.

* use GEM for ''GRASS Addons SVN'' - status unclear
** gis.m menu part of this done (Michael)

===== Wishlist =====

* modify Makefile system to support translated HTML pages. Store translated HTML files in centralized directory with locale specific subdirs, file name is module name.
* Implement [http://freegis.org/cgi-bin/viewcvs.cgi/*checkout*/grass6/doc/vector/TODO vector improvements] as suggested by Radim
* Integrate [https://grasssvn.itc.it/grasssvn/grassaddons/trunk/grassaddons/i.points.auto/#_trunk_grassaddons_i.points.auto_ i.points.auto] (merge into i.vpoints) - see also [[Image processing]] - note that A Scianna/Palermo has modernized version
* Make sqlite the default DB? <- needs more testing, for 6.5?
* drop d.m display manager (as now almost unmaintained; there is gis.m and/or a python based GUI)
: Some people still prefer it (see posts to grass-dev) and I will fix bugs in it, but not enhance/add new modules to it without good reason. So I don't see the need to drop it before the WxPython version is ready. It's not hurting us any keeping it. --Hamish
:: We should keep plain d.mon interface but why keep d.m, if gis.m has become really good? Probably we should clearly state, that d.m is UNMAINTAINED and OBSOLETE? [[User:MarisN|MarisN]] 08:24, 16 February 2007 (CET)
* raster maps: implement SQL based [[Time series in GRASS|time series support]] (Markus has working code from Soeren; done some improvements)
* Clean up Makefile system to support extension compilation and installation outside the GRASS installation and without the full GRASS source. Much like what GEM does, but without needing the module source setup and not limited to installing within the GRASS installation dir. This could also simplify GEM on the compilation side. See also general [[Extension development]].

*'''''Updates to vector querying'''''
*v.select (query using a vector map):
**add flags -p and -g for text output instead of creating a new map. It would report which map(s) and feature(s)/cat(s) meet the query criteria.
**allow multiple maps to be selected. This would directly address Eric's question. If the output is a map, it would be the equivalent of v.patch on all queried vector elements.
**add operators "contains" and "adjacent". Contains=all vector features whose nodes are completely inside a polygon (or inside or touching the boundary). Adjacent=all vector features who share a node/point or line/boundary with the selecting feature. Because GRASS is topologically correct, adjacency information is readily available.
**maybe change option names from ainput and binput to selector and selected or queried. This would have to wait until GRASS 7, of course. I find ainput and binput not very clear where used in other vector operations either (maybe I'm just dense).

*v.what (query using coordinates):
**add flags -p and -g for current behavior (-pg could be the default if we wanted to do this before GRASS 7)
**add "output=" option to allow v.what to create a new map from the results of its query, like v.select does
**allow multiple maps for input, as with the suggestion for v.select
**allow coordinates to be read optionally as a line or area boundary (-l or -a?) instead of only as individual points.
**add operators overlap, contains, adjacent.(This also would make possible interactive vector selection with a mouse drawn box or polygon from the GUI)

*In other words, have v.select and v.what work the same except that v.select uses a vector map for querying and v.what uses a set of coordinate points.

*v.overlay (boolean combination of maps):
**drop the ainput and binput. Replace with just input.
**allow multiple maps to be entered into input, not just 2
**deprecate v.patch because v.overlay with the OR operator replaces it. (If we wanted to do this before GRASS 7, we'd have to create a new module, maybe named v.combine or something like that because this changes the default behavior of v.overlay).

=== In progress ===
* native [[WinGRASS Current Status|MS Windows port]]
* Database connection for v.out.vtk: --[[User:Huhabla|huhabla]] 20:47, 14 August 2006 (CEST)
** single column support for numerical data (int, float, double)
** GRASSRGB column support (done for ps.map)
** multiple column support for vector data
* rewrite most of the g3d modules to fulfill the grass function naming convention --[[User:Huhabla|huhabla]] 20:47, 14 August 2006 (CEST)
* adding further (organized) keywords to every grass command and script [http://grass.itc.it/pipermail/grass-dev/2006-August/025164.html] and [http://grass.itc.it/pipermail/grass-dev/2006-August/025190.html]:
** display commands
** database commands
** general commands
** imagery commands
** misc commands
** paint commands
** photo commands
** postscript commands
** raster commands
** raster3D commands
** vector commands
* continue with [[WxPython-based GUI for GRASS]]
* <strike>write (Python based?) GUI wizard to create new locations</strike> (done by Jachym and Michael, see [[WxPython-based GUI for GRASS]])
** This is done. AFAICT it works really well (IIDSSM). It will create locations using EPSG, georeferenced files, custom selection of projection parameters, and xy locations. You can also set default extents (DEFAULT_WIND).
* improve Python-SWIG interface
* less verbose commands (work in progress)
* BLAS/LAPACK updates (Brad)
* Provide interactive environment on GRASS startup [http://wald.intevation.org/tracker/index.php?func=detail&aid=521&group_id=21&atid=205 #521]

[[Category:Development]]
[[Category:Release Roadmap]]

GRASS Debugging

2007-10-17T10:56:08Z

⚠️MarisN:

The following hints assume to work on a working-copy of the GRASS CVS directory.

Additionally it is good to have set the debbugging symbols during compile-time. Do not strip the libraries or use optimization in the compile. see [http://freegis.org/cgi-bin/viewcvs.cgi/*checkout*/grass6/INSTALL?rev=HEAD&content-type=text/plain INSTALL] and [http://freegis.org/cgi-bin/viewcvs.cgi/*checkout*/grass6/doc/debugging.txt?rev=HEAD&content-type=text/plain doc/debugging.txt] in the source code for more information.

==Setting GRASS-environment variables (numbers: 1-5)==

g.gisenv set="DEBUG=1"

* A higher debug level means you see more messages.
* These messages are always present regardless of compiler settings.

== Using GDB ==

The [http://sourceware.org/gdb/ GNU Debugger] may be used to diagnose <tt>Segmentation Fault</tt>s and other weirdness.

=== Compile Time Setup ===

To add debugging information into the built binary, add ''-g'' to the CFLAGS arguments.

CFLAGS="-ggdb -Wall -Werror-implicit-function-declaration" ./configure ...

Do '''not''' use ''-O'' for optimization and do '''not''' strip the binaries with LDFLAGS="-s".

=== Using gdb on command line ===

* Running a program inside [http://en.wikipedia.org/wiki/Gdb GDB] works (installation of GDB required :-)
: (e.g. on [http://www.debian.org Debian GNU/Linux]: apt-get install gdb)

* Use the exact module name on the command line (at the GRASS prompt) without arguments. Put any command line arguments on the <tt>(gdb)</tt> command line after the word ''run''.

gdb `which v.in.ogr`
run "out=some_map dsn="PG:dbname=postgis user=me" olayer=postgislayer"

* when it crashes, type "<tt>bt full</tt>" for a full backtrace
* type "<tt>l</tt>" to list where in the source code it got to
* type "<tt>frame 2</tt>" to switch to the second level function (see the backtrace), there you can again type "<tt>l</tt>" to see where it got up to.

or you can optionally add arguments to gdb directly on the commandline:
gdb --args v.in.ogr out=bla dsn="PG:dbname=postgis user=me" olayer=postgislayer

* ''Attaching to child process'':
: use "<tt>attach <pid></tt>" to attach to an existing process (needed for DBMI debugging etc).

=== Using gdb within GNU Emacs ===

* start [http://en.wikipedia.org/wiki/Emacs GNU Emacs] within GRASS session, e.g.

emacs general/manage/cmd/remove.c

[[Image:Emacs gdb-1a.png|center]]

* create second buffer by <tt>C-x 2</tt>

[[Image:Emacs_gdb-2.png|center]]

* move cursor to the second buffer by <tt>C-x o</tt>, then <tt>M-x gdb</tt>, Enter
* type module name which you would like to debug, e.g. <tt>g.remove</tt>, Enter

* now you can use gdb inside GNU Emacs

[[Image:Emacs-gdb-3.png|center]]

=== Using DDD (gdb graphical frontend) ===
* running a program inside [http://en.wikipedia.org/wiki/Ddd DDD] works (installation of ddd and gdb required :-), (on Debian GNU/Linux: apt-get install gdb ddd)

ddd `which v.in.ogr`

http://mpa.itc.it/markus/grass61/debugging/crash_1_small.jpg

* Run (from main menu PROGRAM): "out=bla dsn="PG:dbname=postgis user=me" olayer=postgislayer"

http://mpa.itc.it/markus/grass61/debugging/ddd_1_small.jpg

* run with parameters
* when it crashes, use the UP menu item to trace back

http://mpa.itc.it/markus/grass61/debugging/ddd_2_going_up_small.jpg

* reach the line where it crashed
* set a breakpoint, then run again to stop before the crash

http://mpa.itc.it/markus/grass61/debugging/ddd_3_breakpoint_small.jpg

* right mouse button on variables permits to display them etc.

http://mpa.itc.it/markus/grass61/debugging/ddd_4_displ_vars_small.jpg

* figure out why it crashed there. This requires PATIENCE. But you will nearly save the world if you identify the problem :-)

=== Using kdbg (gdb graphical frontend) ===

* kdbg is not unlike DDD, but it's a KDE application.
* Use is similar to DDD.
* Start with (within GRASS):
kdbg `which g.module`
* Fill in command line arguments with menu item Execution->Arguments.
* Open the View->Locals window.
* Click the Run icon (or Execution->Run) and see where it breaks.
* Set pause-points by clicking a red stop-sign to the left of the "+" on a line of the source code. From there you can step through instructions.
* Explore the values of variables in the locals window.

== Using ldd ==

''ldd'' will show the shared library dependencies for a program or library. For example:

For a module:
GRASS> ldd `which v.in.ogr`
For a library:
$ ldd /usr/src/grass/grass-6.2.2/dist.i686-pc-linux-gnu/lib/libgrass_gis.so

The output looks like this:
libz.so.1 => /usr/lib/libz.so.1 (0x40077000)
libgrass_datetime.so => not found
libc.so.6 => /lib/libc.so.6 (0x4008a000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)

In the above example <tt>libgrass_datetime.so</tt> is missing causing an <tt>Illegal Instruction</tt> error in ''libgis''. A common error occurs when there are more than one versions of a support library installed, and the GRASS build is using the wrong one. ''ldd'' is good for spotting this.

=== Library search path ===

If a support library like libgdal can't be found, and you are sure it is installed, make sure the library search path is set correctly.
For example in Linux if GDAL was installed to <tt>/usr/local</tt>, add the line "<tt>/usr/local/lib</tt>" to the /etc/ld.so.conf file, and as root run <tt>ldconfig</tt> to rebuild the library links and cache.

Alternatively you can add the library path to the $LD_LIBRARY_PATH environmental variable.

== Using strace ==

* running the command through strace could give you another hint what is going wrong somewhere.

For example:
strace v.in.ogr out=your_map dsn="PG:dbname=postgis user=me" olayer=postgislayer

== Using Valgrind ==

* [http://valgrind.org Valgrind] is a tool to check for memory leaks

('''''Insert howto here''''')

Examples:

* analysis of heap usage
CMD="v.in.ascii -zt z=3 in=lidaratm2_250k.txt out=lidaratm2_250k fs=,"
valgrind --tool=massif --format=html $CMD --o

* analysis of memory leaks
: Quick addrcheck tool
valgrind -v --tool=addrcheck --leak-check=yes $CMD

: Full memcheck tool, including non-orphaned, but left over, allocated memory
valgrind --tool=memcheck --leak-check=yes --show-reachable=yes $CMD --o

* Valgrind can create PostScript output charts. To convert PostScript to PNG:
: ('pstoimg' is part of the latex2html Debian package)

pstoimg -aaliastext -flip r90 -out massif.550.png -scale 1.3 -crop a massif.550.ps

== Using Electric Fence ==

* [http://perens.com/FreeSoftware/ Electric Fence] checks for bad memory writes, ie specific malloc() over-runs and under-runs.

('''''Insert howto here''''')

Example:
CMD="gdalwarp -tps -srcnodata 255 -dstnodata 255 \
-of GTiff -rcs ${TMP}.tif ${OUTFILE}_warp"
LD_PRELOAD=libefence.so.0.0 $CMD

== Using a profiling tool ==

A profiling tool may be used to identify the bottlenecks in long running processes.

* [http://kcachegrind.sourceforge.net kcachegrind] is a visualization tool for [http://valgrind.org Valgrind]'s calltree profiling skin.
: ('''''Insert howto here''''')

* gcc / gdb profiling
: ('''''Insert howto here''''')

== Using Mudflap ==

GCC built in feature, that "instruments all risky pointer/array dereferencing operations, some standard library string/heap functions, and some other associated constructs with range/validity tests. Modules so instrumented should be immune to buffer overflows, invalid heap use, and some other classes of C/C++ programming errors. The instrumentation relies on a separate runtime library (libmudflap), which will be linked into a program if -fmudflap -lmudflap is given at link time." [http://gcc.gnu.org/wiki/Mudflap_Pointer_Debugging GCC Wiki]

* Requires GCC with mudflap support (GCC 4.x with mudflap USE flag on Gentoo, separate library "libmudflap*" in other distros);
* Add -fmudflap and -lmudflap options ('''''Is this correct way? It works...'''''):
** in include/Make/Platform.make add -lmudflap to LD_SEARCH_FLAGS;
** in include/Make/Platform.make add -fmudflap to CFLAGS1;
* Disable mudflap during compilation
export MUDFLAP_OPTIONS='-mode-nop -viol-nop'
* Compile GRASS (make clean && make). For best results use NO optimisations for compilation (-O0);
* Use GRASS.
** To disable warnings
export MUDFLAP_OPTIONS='-mode-nop -viol-nop'
** To enable warnings
export MUDFLAP_OPTIONS='-mode-check -viol-nop -check-initialization'

More information about debugging with mudflap, can be found [http://gcc.fyxm.net/summit/2003/mudflap.pdf here].

== Skimming the ChangeLog for changes ==

* use the tool [http://www.red-bean.com/cvs2cl/ cvs2cl.pl] for generating a local changelog-file
: (it can be found in the <tt>tools/</tt> directory in the GRASS 6 source code)

[[Category:Development]]

GRASS 6.3 Feature Plan

2007-10-16T08:33:01Z

⚠️MarisN: /* Wishlist */

GRASS 6.3 Feature Plan

2007-10-16T08:31:11Z

⚠️MarisN: /* Wishlist */

GRASS 6.3 Feature Plan

2007-10-16T08:29:45Z

⚠️MarisN: /* Must do */

GRASS 7 ideas collection

2007-02-16T07:29:04Z

⚠️MarisN: /* Modules */

== Raster ==

=== Library ===

* Split libgis into G_() part and Rast_() part
* Rewrite library from scratch. See [http://grass.itc.it/pipermail/grass-dev/2006-August/025025.html suggestions]
* Insert 'vertical' 2d rasters (e.g. [http://woodshole.er.usgs.gov/project-pages/longislandsound/images/Ghist_square2.jpg geophysical survey data])

=== Modules ===

* Remove r.in.arc and r.out.arc, '''if''' a [http://intevation.de/rt/webrt?serial_num=4897 related bug in r.in.gdal] is fixed. The [http://bugzilla.remotesensing.org/show_bug.cgi?id=1071 integer/floating point detection for AAIGrid driver in GDAL] was fixed after 1.3.2 release, so r.in.gdal and r.out.gdal should be enough now.

* Remove the code from r.info that makes it print projection information - we have g.region and g.proj for that. Moreover, r.info always prints a bogus '''(zone 0)''' information in non-UTM locations, which is confussing. See [http://intevation.de/rt/webrt?serial_num=3054 a bug report].

* fix the raster map history management (truncating long history, odd storage). It should work like for vector maps in GRASS 6.

* dispose '''r.resample''' and '''r.bilinear''' in favor of '''r.resamp.interp'''

* merge '''r.surf.idw''' and '''r.surf.idw2'''

* drop '''r.univar.sh'''; newly implemented '''r.univar''' features cover it

* drop '''r.univar.sh'''; newly implemented '''r.univar''' features cover it

* r.sum, r.mode, r.median, r.average, r.statistics, r.univar, r.univar2 - maybe they can be reduced to just r.statistics and r.univar? See [http://intevation.de/rt/webrt?serial_num=1848 RT #1848] and a [http://grass.itc.it/pipermail/grass-dev/2006-November/027665.html thread on the GRASS dev list]

* Dispose r.out.tiff. New C r.out.gdal should cover all it's option now (doublecheck!). See [http://intevation.de/rt/webrt?serial_num=3680 RT #3680] (starting with date Sun, Nov 26 2006 14:54:23).

* Remove remaining -v and -q flags for verbosity levels of modules.

* fix lseek() usage for Large File Support: see [http://grass.itc.it/pipermail/grass-dev/2006-December/028231.html list of affected modules]

== Vector ==
=== Library ===
* 2d 'vertical' vector data (e.g. [http://sofia.usgs.gov/publications/maps/florida_geology/Txsectionbh.jpg Geologic Cross Sections])

=== Modules ===

* rename v.mkgrid to v.grid
* merge v.select and v.overlay
* Remove [http://intevation.de/rt/webrt?serial_num=3600 doubled units in v.to.db GUI]

* Fix the [http://intevation.de/rt/webrt?serial_num=3623 Column 'cat_' already exists (duplicate name)] in v.in.ogr. Maybe by creating columns ''cat_1'', ''cat_2'' etc. each time a Grass vector is exported to shapefile and imported back to Grass?
* write Vect_map_exists() and implement in g.remove and v.digit -n (why wait for GRASS 7 ??)
* add '-d' dissolve to v.reclass
* add 'where=' to v.to.rast (why wait for GRASS 7 ??)
* implement Douglas-Peucker generalization ([http://www.ngdc.noaa.gov/mgg/shorelines/data/gshhs/version1.2/gshhs_dp.c C code file])to substitute prune tool of v.clean (why wait for GRASS 7 ??)
* Rewrite vector labeling. Needs more placement control options (may be db field value based), label overlaping prevention would be also good. May be we could borrow some ideas from MapServer?

== General ==
=== Library ===
* Add support for planetary bodies reference systems
* Add new partial differential equation (PDE) library with OpenMP support

=== Modules ===

* g.remove, g.mremove, g.rename, g.copy: don't allow for default datatype (which is currently raster) [http://intevation.de/rt/webrt?serial_num=3009].
* g.region
** [http://grass.itc.it/pipermail/grassuser/2007-February/038337.html Glynn's notes] - cleaning the print flags and new <tt>print=</tt> option

== Database ==
=== Library ===
=== Modules ===

== Imagery ==
=== Library ===

Do merge of image libraries:

* A)
** lib/imagery/: standard lib, in use (i.* except for i.points3, i.rectify3)
** imagery/i.ortho.photo/libes/: standard lib, in use (i.ortho.photo, photo.*)
* B)
** lib/image3/: never finished improvement which integrated the standard lib and the ortho lib. Seems to provide also ortho rectification for satellite data (i.points3, i.rectify3)

=== Modules ===

* merge of i.points, i.vpoints, i.points3
* merge of i.rectify and i.rectify3
* addition of new resampling algorithms such as bilinear, cubic convolution (take from r.proj?)
* add other warping methods (maybe thin splines from GDAL?)
* implement/finish linewise ortho-rectification of satellite data
* Depreciate tape functions in next major revision of GRASS and create a tape module that accomplishes tape access.

== Raster3D ==
=== Library ===
* renaming of all G3D library functions to fulfil the grass coding standard
* extent/rewrite documentation
* localisation support (why wait for GRASS 7 ??)

=== Modules ===
* report and support modules like r3.stats, r3.support
* voxel -> vector (isosurfaces ...) and vector -> voxel (lines, faces, volumes) conversion modules
* module for 3d Kriging interpolation based on vector points
* a GRASS-Python/VTK visualisation/manipulation tool

== Display ==
=== Modules ===
* d.font etc.
** Huidae Cho merged d.text.freetype and d.text into d.text.new; drop them and rename d.text.new into d.text
** merge d.font and d.font.freetype too
* d.vect
** consolidate parameter names (attrcol, wcolumn, rgb_column)

== Postscript ==
=== Modules ===
* ps.map
** remove scale parameter
** rename sizecol to sizecolumn (remove the given warning)

== Parser ==

* "Add another semantic meaning to the parser system for a type safe enumerated list" (Cedric's words commenting the bug that [http://intevation.de/rt/webrt?serial_num=2969 '''v.type''' doesn't allow for selecting input and output type in '''GUI''']

* Making GRASS modules be less verbose. Use --verbose flag and GRASS_VERBOSE environment variable. All output (G_message, G_percetn, G_warning) should go to GRASS_LOG file which could be grassdata/location/mapset/.grass.log by default.

== Data management ==

* store vertical units on per-map base, using code from [http://www.gnu.org/software/units/ units] software
* store vertical map datum on per-location base (GDAL/OGR needs the same [http://lists.maptools.org/pipermail/gdal-dev/2005-October/006857.html enhancement])
* add versioning for maps (to recover previous map versions)

== Time series ==

* Implement better [[Time series in GRASS]] support (series of satellite data etc)

== Visualization ==

...

== CLI ==

Fix the parameters and flags. Make it a concept. See proposal in GRASS 5 [http://freegis.org/cgi-bin/viewcvs.cgi/grass/documents/parameter_proposal.txt?rev=HEAD&content-type=text/vnd.viewcvs-markup documents/parameter_proposal.txt]

== GUI ==

* Multiplatform
* Fast
* Small on monitor
* Number of window reduction
* Managable from command line via d.* modules (which will have to be rewritten too)
* Facilitating easy development of custom GUI application based on GRASS

* [[GRASS and Python|Python]]?
* WxWidgets?
* Qt4

== Conceptual changes ==

* File organization in binaries:
** the grass etc dir is a mess... module should maintain arch-deps and arch-indep things in different paths -- <cite> frankie at #grass irc</cite>
** it's basically a FHS violation, i dunno if it is reported by lintian, anyway /usr/lib/grass should be used for arch-deps data, not for mixed stuff -- <cite> frankie at #grass irc</cite>

[[Category:Development]]
[[Category:Release Roadmap]]

User:MarisN

2007-02-16T07:25:02Z

⚠️MarisN:

Māris Nartišs

Author of r.lake module and troll.

Student at University of Latvia.

GRASS 6.3 Feature Plan

2007-02-16T07:24:04Z

⚠️MarisN: /* Wishlist */

== GRASS 6.3.x feature plan ==
=== About feature plan ===

To make GRASS releases more often and more predictable, here is GRASS next releases feature plan. This feature plan has to be filled by developers working on GRASS 6.3.

Basic principles:
# Add a short feature description, bug No., etc. what You want to see and what '''YOU will implement or fix''' in upcoming GRASS 6.3 to ''[[#TODO]]'' list. Sign it using four tildes <nowiki>~~~~</nowiki>!
# If You work on it, and You think it will make to next release, '''MOVE''' to ''[[#In progress]]'' section.
# When You finish and commit Your work, '''MOVE''' it to ''[[#Finished]]'' section.

'''''Warning''''' After [[GRASS_6.3_release_schedule|freeze start]], You will not be able to commit any new features till freeze end. Only bugfixes and commits related to items listed in ''In progress'' section.

=== TODO ===

==== Must do ====
* '''complete and stabilize the native [[WinGRASS Current Status|winGRASS port]]'''
* modify Makefile system to support translated HTML pages. Store translated HTML files in centralized directory with locale specific subdirs, file name is module name.

* replace r.proj with r.proj.seg; d.text with d.text.new

==== Mostly done? ====
* Create GRASS Addons SVN repository and really use GEM: ''GRASS Addons SVN'' is available now - contact Markus, see [[GRASS AddOns]] page
* Are there outstanding v.surf.idw versus v.surf.idw2 issues??

==== Wishlist ====
* Implement [http://freegis.org/cgi-bin/viewcvs.cgi/*checkout*/grass6/doc/vector/TODO vector improvements] as suggested by Radim
* Integrate [http://mpa.itc.it/markus/i_points_auto/ i.points.auto] (merge into i.vpoints) - see also [[Image processing]]
* Make sqlite the default DB?
* drop d.m display manager (as now almost unmaintained; there is gis.m and/or a python based GUI)
: Some people still prefer it (see posts to grass-dev) and I will fix bugs in it, but not enhance/add new modules to it without good reason. So I don't see the need to drop it before the WxPython version is ready. It's not hurting us any keeping it. --Hamish
:: We should keep plain d.mon interface but why keep d.m, if gis.m has become really good? Probably we should clearly state, that d.m is UNMAINTAINED and OBSOLATED? [[User:MarisN|MarisN]] 08:24, 16 February 2007 (CET)
* raster maps: implement SQL based [[Time series in GRASS|time series support]]

[[Category: Development]]

=== In progress ===
* native MS Windows port
* Database connection for v.out.vtk: --[[User:Huhabla|huhabla]] 20:47, 14 August 2006 (CEST)
** single column support for numerical data (int, float, double)
** GRASSRGB column support
** multiple column support for vector data
* rewrite most of the g3d modules to fulfil the grass function naming convention --[[User:Huhabla|huhabla]] 20:47, 14 August 2006 (CEST)
* adding further (organized) keywords to every grass command and script [http://grass.itc.it/pipermail/grass-dev/2006-August/025164.html] and [http://grass.itc.it/pipermail/grass-dev/2006-August/025190.html]:
** display commands
** database commands
** general commands
** imagery commands
** misc commands
** paint commands
** photo commands
** postscript commands
** raster commands
** raster3D commands
** vector commands
* continue with wxpython prototype
* write (Python based?) GUI wizard to create new locations (MN and terrestris.de)
* implement Python-SWIG interface
* less verbose commands

=== Finished ===
* All fixes as done for [[GRASS 6.2 Feature Plan|GRASS 6.2.x]]
* rewrite of r.to.rast3, r.to.rast3elev, v.out.vtk and r.out.vtk to fulfil the grass function naming convention --[[User:Huhabla|huhabla]] 20:47, 14 August 2006 (CEST)
* basic keyword support added [[User:Neteler|Neteler]] 15:52, 19 August 2006 (CEST)

=== User Wishes ===

''This section is not really development related...''
* Create 3D animation w nviz showing GRASS 3D coolness. [[User:MarisN|MarisN]] 12:00, 4 August 2006 (CEST)
* here are some examples to get inspired (apparently that's already possible):
** [http://skagit.meas.ncsu.edu/~helena/publwork/grasskey02/grass02talk10.html dynamic surfaces and volumes]
**[http://skagit.meas.ncsu.edu/~helena/wrriwork/cenntenial/water01dsmall.gif some water]
**[http://skagit.meas.ncsu.edu/~helena/wrriwork/balsam/fanimwalk.gif particles]
** [http://www.fhpv.unipo.sk/kagerr/pracovnici/hofierka/pv_results.html solar radiation and energy]
* Convince the users to use ParaView [http://www.paraview.org] for sophisticated animations --[[User:Huhabla|huhabla]] 20:47, 14 August 2006 (CEST)
**(Add support for Paraview in GDAL/OGR or add GDAL/OGR support in ParaView to read directly data from GRASS) see diskussion
* Or use [http://www.llnl.gov/visit/ VisIt software], it should be able to read GRASS maps directly via GDAL

[[Category:Development]]
[[Category:Release Roadmap]]

Compile and Install

2006-12-22T08:09:20Z

⚠️MarisN: /* Configure options and their meanings */

== How to do compilation and installation of GRASS 6? ==

Here we explain the procedure to compile GRASS from CVS, but it also applies to official GRASS 6 releases.

''For installation of precompiled binary packages, see the main [[Installation Guide]].''

For detailed information on compilation, please see the [http://grass.itc.it/grass61/source/INSTALL INSTALL] file in the source code.

=== Prerequisites ===

GRASS needs at least two extra libraries: PROJ and GDAL/OGR

''Note: if you want to have DBMS support in GDAL (subsequently in GRASS) you have to perform the "Optional" steps below as well.''

* [http://proj.maptools.org PROJ4] for management of projections (with proj-datumgrid-1.3.zip support)
* Optional: [http://geos.refractions.net GEOS]
* Optional: [http://www.postgresql.org PostgreSQL], [http://www.mysql.org mySQL], [http://www.unixodbc.org unixODBC], [http://www.sqlite.org SQLite] (SQLite is needed for QGIS)
* [http://www.gdal.org GDAL/OGR] for reading and writing various GIS data formats (interoperability)

You have to install these two libraries '''first'''.

It is easiest to obtain a prepackaged version of these libraries (e.g., .rpm; .deb) for your particular operating system and run the corresponding package installation (e.g., rpm -Uhv packagename.rpm; apt-get) in a terminal window. Take care to also install the development packages of these libraries (...-devel packages). If there is no prepackage version, then you will have to download the source code (see links above, source code packages usually ends in .tar.gz or .zip) and compile it (you must have a C compiler installed as part of your operating system). The Web sites show the steps to compile the libraries.

Other libraries needed to run GRASS are listed here: [http://grass.itc.it/grass63/source/REQUIREMENTS.html REQUIREMENTS]. To compile, you will also need the respective "-devel" packages.

=== Generic Compilation and installation procedure ===

* checkout the grass6 module from cvs (read http://grass.itc.it/faq/cvs_howto.html grass CVS howto instructions)
* It is wise that compilation processes are carried out as a normal user: If you want to get the source code in a place where you do not have write permissions (e.g. in /usr/local/src/cvs) just follow this:
cd /usr/local/src/cvs
su -c 'mkdir grass6'
su -c 'chown yourlogin:yourgroup grass6'
* do a checkout (co) of the repository
cvs -z3 co grass6
* in the grass6 directory, you will find the precious INSTALL file, open it with your favourite pager/editor and read it carefully!
* run configure with parameters to adapt the compile process to your own system. To see what options can be passed to it, run configure --help. The minimum set of configure parameters is (refers to GRASS 6 from CVS, not to 6.x release):
./configure ### It may (!) look like this:
./configure \
--with-cxx \
--with-sqlite \
--with-postgres-libs=/usr/include/pgsql/libpq \
--with-postgres-includes=/usr/include/pgsql \
--with-freetype \
--with-freetype-includes=/usr/include/freetype2 \
--with-motif \
--with-glw \
--with-proj-share=/usr/share/proj

You may have to explicitly state the path for certain packages (i.e., gdal). The Unix 'locate' command will come in handy for finding the path of the package you need (you may have to run locate as root ex: sudo locate gdal-config).

Please note that the paths mentioned may widely vary due to the distribution used. At the end of configuration process you should get report not much different from this:

GRASS is now configured for: i686-pc-linux-gnu

Source directory: /usr/src/grass6
Build directory: /usr/src/grass6
Installation directory: /usr/local/grass-6.1.cvs
Startup script in directory: ${exec_prefix}/bin
C compiler: gcc -g -O2
C++ compiler: c++ -g -O2
FORTRAN compiler:
Building shared libraries: yes
64bit support: no

NVIZ: yes

BLAS support: no
C++ support: yes
DWG support: no
FFMPEG support: no
FFTW support: yes
FreeType support: yes
GDAL support: yes
GLw support: no
JPEG support: yes
LAPACK support: no
Large File Support (LFS): no
Motif support: no
MySQL support: no
NLS support: no
ODBC support: no
OGR support: yes
OpenGL(R) support: yes
PNG support: yes
PostgreSQL support: yes
Readline support: no
SQLite support: no
Tcl/Tk support: yes
TIFF support: yes
X11 support: yes

* Let's compile it (takes a little while...)!
make
* At the end, you should get report not much different from this:
----------------------------------------------------------------------
Following modules are missing the 'description.html' file in src code:
----------------------------------------------------------------------
GRASS GIS compilation log
-------------------------
Started compilation: Ne kvě 28 13:18:43 CEST 2006
--
Errors in:
--
Finished compilation: Ne kvě 28 13:43:40 CEST 2006
(In case of errors please change into the directory with error and run 'make')

* If there is any error, change directory to directory with error and run "make" again. Report occuring bug to grass mailing list
* Once the installation process is finished, you're ready to install GRASS system wide.
su -c 'make install'
* enjoy GRASS:
grass61

=== What else? ===

If you want to use [http://www.qgis.org QGIS], then also compile the GRASS-GDAL/OGR plugin. This is also useful to access your GRASS-data
from other application using GDAL/OGR like [http://thuban.intevation.de thuban].
* [[Compile and install GRASS and QGIS with GDAL/OGR Plugin]] (enables QGIS to read GRASS data directly)

=== Platform Specific Notes ===

==== Debian ====

* [http://hamish.bowman.googlepages.com/debiangisfiles#compile Compiling GRASS 6.1-CVS on Debian/Stable (aka 3.1, Sarge)]

* Official [http://pkg-grass.alioth.debian.org/cgi-bin/wiki.pl DebianGIS] packaging [http://svn.debian.org/wsvn/pkg-grass/packages/grass/branches/ control files].

==== Ubuntu 6.06 ====

* [http://david.p.finlayson.googlepages.com/makegrass.sh makegrass.sh] is script designed to automate most of the download, configuration and compilation of GRASS 6.x-CVS
* [[User:Steko/Automated_CVS_compiling|Here]] is another of these scripts, it's homemade so probably you'll find the above more useful for production sites.

==== RPM SPEC files ====

... can be found in the source code, rpm/ directory, or [http://www.gdf-hannover.de/media.php?id=1&lg=en here]

==== MS-Windows/Cygwin ====

... see [http://grass.itc.it/platforms/wingrass.html here] (should be moved to the Wiki)

==== MS-Windows/native ====

For this, you need MinGW and MSys, including gcc, g++, binutils, flex, bison, make, and pdcurses, all from:
http://www.mingw.org/download.shtml

You also need this version of the XDR library:
http://wiki.qgis.org/qgiswiki/BuildingWindowsBinaryOnLinux?action=AttachFile&do=get&target=xdr-4.0-mingw2.tar.gz

The above is a stripped-down version of the Sun RPC library, which only includes the XDR [de]serialisation code, with the networking code removed.

You will first need to build and install zlib, PNG, PROJ, GDAL and the above XDR library. Then, building GRASS is similar to building it on Linux, except that you need to disable most of the optional features (including the use of shared libraries).

Aside: it might encourage more people to work on the Windows version if the GRASS site contained binary versions of the necessary libraries. Having to build XDR, PROJ, GDAL, zlib, PNG, Tcl/Tk and possibly other stuff from source before you can start to compile GRASS is a major nuisance.

... or see [http://wiki.qgis.org/qgiswiki/BuildingWindowsBinaryOnLinux here incl. QGIS compilation] (with MinGW)

==== Mac OSX ====

... see [http://grass.itc.it/platforms/macgrass.php here] for instructions

==== Zaurus====

... see [http://wiki.debian.org/?GrassGISonZaurus here] for instructions

=== Common problems and solutions ===

During compilation, error can occur if certain packages are not installed. Here a list of problems with solution:

* error: X11/Xlib.h: No such file or directory
** this suggests that you don't have the X headers installed
** Solution: Install the libx11-dev package

=== Configure options and their meanings ===

For configure there are many options and some GRASS modules are built only if some options are set. Here are listed common configuration options with short explanation.

* --prefix=/path - Sets path where GRASS will be installed. GRASS will reside in /path/grass-version.
* --enable-largefile - Enables large (>2Gb on 32bit systems) support. For current large file support status look at [[Large File Support]] page.
* --with-cxx - Enables compilation of C++ code. Required for r.terraflow module.
* --with-readline - Enables readline support. If readline is enabled, you can use its history/editing facilities when entering r.mapcalc expressions on stdin.
* --with-glw - Enables GLw support. The GLw library provides OpenGL "canvas" widgets for Athena and Motif.

That switch is unnecessary for normal compilation. It's only
required for r3.showdspf, which isn't normally built; if you
want it, you have build it manually
(e.g. "make -C raster3d/r3.showdspf").
As similar functionality is now provided by NVIZ, r3.showdspf
is deprecated.
r3.showdspf uses the Motif widget (so you also need a
Motif library, e.g. Lesstif or OpenMotif).
[http://grass.itc.it/pipermail/grassuser/2006-December/037475.html Glynn Clements at GRASS-user mailing list]

[[Category:Development]]
[[Category:Documentation]]
[[Category:Installation]]

Working with SVN

2006-12-13T07:17:39Z

⚠️MarisN:

[''I find the main grass website CVS help pages many, complex, and confusing. So trying to start over here with a more concise help page'']

== Tips for everyone ==

* You can setup default CVS options in a file called .cvsrc in your home directory.
cat << EOF >> ~/.cvsrc
-z3
diff -u
update -dP
EOF

* Explore the CVS tree and file history with the [http://freegis.org/cgi-bin/viewcvs.cgi/grass6/ WebCVS interface].

== Tips for users ==
(read-only access to the latest code)

=== Setting it up (first time) ===

* Download latest source code snapshot
wget http://grass.itc.it/grass63/source/snapshot/grass-6.3.cvs_src_snapshot_${DATE}.tar.gz
* move it somewhere on your filesystem ''without'' spaces or special characters in the path.
mv grass-6.3.cvs_src_snapshot_${DATE}.tar.gz /usr/local/src/
* decomress it
tar xzf grass-6.3.cvs_src_snapshot_${DATE}.tar.gz
* at this stage, you may want to rename the source directory to something shorter
mv grass-6.3.cvs_src_snapshot_${DATE}/ grass63/
cd grass63/
* set for anonymous connection to CVS server
CVSROOT=:pserver:grass-guest@intevation.de:/home/grass/grassrepository
export CVSROOT
* login to CVS
cvs login
password: grass
* update to the latest
cvs -z3 update -dP

=== Updating entire source tree (second time) ===
The is no need to login to CVS now, it remembers all that.

* clear away the existing rubble
make distclean
* update (You can skip the reporting of all directories by adding the -q flag (assumes -z3 and -dP were added to ~/.cvsrc)
cvs -q update
* re run ./configure and make

=== Updating just one module ===
Often you are interested in just a single bugfix or updated module. Assuming the change didn't affect libraries or the build system, you can just update and recompile the code in the module's directory.

* for example, updating just the r.cost module
cd raster/r.cost
cvs up
make

* If includes/ or module header files (*.h) have changed, you will have to run
make clean
before "<tt>make</tt>".

== Tips for users wanting to contributing code ==

=== Code Standards ===

See these files in the source code. To keep the GRASS source code manageable, all new code must conform.

* SUBMITTING
* SUBMITTING_SCRIPTS
* SUBMITTING_TCLTK

=== Legal issues ===

==== Copyright ====

* The developer may keep copyright on submitted code

* You must include copyright and licensing information in the header comments of your code so that others may know how they can use, extend, modify, and redistribute your work.

* The developer is encouraged to assign co-copyright to the GRASS Development Team. This gives the GRASS project flexibility over the source code, without this the Team must contact all former developers before allowing a license change (eg a legal hole is found in the GPL and the project needs to migrate to a new version) or confirming the original license. In a 20+ year old project, with often only a name and old email to go by, this becomes unworkable.

===== Example =====
at the top of a shell script:

#!/bin/sh
############################################################################
#
# MODULE: v.in.e00
#
# AUTHOR(S): Markus Neteler, Otto Dassau
#
# PURPOSE: Import E00 data into a GRASS vector map
# Imports single and split E00 files (.e00, .e01, .e02 ...)
#
# COPYRIGHT: (c) 2004, 2005 GDF Hannover bR, http://www.gdf-hannover.de
#
# This program is free software under the GNU General Public
# License (>=v2). Read the file COPYING that comes with GRASS
# for details.
#
#############################################################################

==== Licensing ====

* GRASS uses the GNU General Public License (the GPL).

==== Due diligence ====

* PSC RFC2

=== Code submission method ===

(Note: this applies to people without CVS write access)

'''Be sure to develop on top of the LATEST GRASS code (CVS HEAD), ''not'' on top of a stable branch.'''

You can re-check before submission with:
cvs diff -u

==== Preparing a patch ====

* create a unidiff patch against the latest development branch CVS

Be sure to create unified ("diff -u") format. "Plain" diffs (the default
format) are risky, because they will apply without warning to code which
has been substantially changed; they are also harder to read than unified.

Such diffs should be made from the top-level directory, e.g.
"cvs diff -u display/d.vect/main.c"; that way, the diff will
include the pathname rather than just "main.c".

Imagine, that You have hacked around in module r.foo. To create patch, You should use following commands:
cd /path/to/grass6
cvs diff -u raster/r.foo > r.foo.patch

==== Applying someone else patch ====

To apply patch created by someone else using "cvs diff" command, You need to use following command:
cd /path/to/grass6
patch -p0 < /path/to/r.foo.patch

==== Creating a GEM package ====

The GEM system makes it easy to prepare intergrated add-on modules or groups of add-on modules as extensions to the existing GRASS source code. Users do not need to build the entire GRASS source package to add and build GEM packages.

* link to GEM add-on docs

==== Submitting it to the Wiki Add-Ons page ====
The Add-ons page contains user contributed code which is not intended to go into the main GRASS source tree or is still experimental

* The [[GRASS AddOns]] page

==== Submitting it to the code tracker ====
Non-trival formal patches which are expected to become part of the main GRASS source tree should be uploaded to the "code patches" tracker and GRASS's Gforge site.

* http://wald.intevation.org/projects/grass/

==== Announcing it on the GRASS Development mailing list ====

Once it is uploaded to the Wiki Add-ons page or the Gforge code tracker, announce it on the [http://grass.ibiblio.org/devel/index.php#list GRASS-dev mailing list].

Final products added to the Wiki Add-Ons page should be announced on the GRASS users' mailing list.

==== Getting help ====

* IRC
* [http://grass.ibiblio.org/devel/index.php#list GRASS-dev mailing list]

== Tips for GRASS developers ==
(CVS write access, committing)

=== Becoming a GRASS developer ===

The [[PSC|GRASS Project Steering Committee]] is in charge of giving new developers write access to the CVS. This generally happens after the developer has been submitting code for long enough for the other developers to become familiar with the person and their coding ability.

=== Responsibilities ===

* [http://freegis.org/cgi-bin/viewcvs.cgi/grass6/rfc/RFC2_PSC.dox?rev=HEAD&content-type=text/vnd.viewcvs-markup RFC2: Legal aspects of code contributions]
* follow the [http://grass.itc.it/devel/index.php#submission code submission guidelines]

=== Setting it up ===

* Connection to CVS with write access: ssh, firewalls, login, etc.
** See [http://freegis.org//grass/howto_grass-sshcvs.en.html GRASS-CVS-ssh instructions]

* configuring GRASS for code development:
** Linux: please use these flags to configure GRASS, they will help you to catch most programming problems:
MYCFLAGS="-g -Wall -Werror-implicit-function-declaration -fno-common"
MYCXXFLAGS="-g -Wall"
CFLAGS="$MYCFLAGS" CXXFLAGS="$MYCXXFLAGS" ./configure ... (more flags and parameters)
** MacOSX:
** MS-Windows:

=== Commiting ===

* work against latest development branch CVS HEAD (update before committing)
* code must compile
* verify changes with 'cvs diff -u' before all commits
* cvs commit: make the cvs log message a useful synopsis of the change
* double check the change using the live WebCVS interface or [http://grass.itc.it/mailman/listinfo/grass-commit grass-commit mailing list]

Working with SVN

2006-12-13T07:14:04Z

⚠️MarisN: /* Preparing a patch */

[''I find the main grass website CVS help pages many, complex, and confusing. So trying to start over here with a more concise help page'']

== Tips for everyone ==

* You can setup default CVS options in a file called .cvsrc in your home directory.
cat << EOF >> ~/.cvsrc
-z3
diff -u
update -dP
EOF

* Explore the CVS tree and file history with the [http://freegis.org/cgi-bin/viewcvs.cgi/grass6/ WebCVS interface].

== Tips for users ==
(read-only access to the latest code)

=== Setting it up (first time) ===

* Download latest source code snapshot
wget http://grass.itc.it/grass63/source/snapshot/grass-6.3.cvs_src_snapshot_${DATE}.tar.gz
* move it somewhere on your filesystem ''without'' spaces or special characters in the path.
mv grass-6.3.cvs_src_snapshot_${DATE}.tar.gz /usr/local/src/
* decomress it
tar xzf grass-6.3.cvs_src_snapshot_${DATE}.tar.gz
* at this stage, you may want to rename the source directory to something shorter
mv grass-6.3.cvs_src_snapshot_${DATE}/ grass63/
cd grass63/
* set for anonymous connection to CVS server
CVSROOT=:pserver:grass-guest@intevation.de:/home/grass/grassrepository
export CVSROOT
* login to CVS
cvs login
password: grass
* update to the latest
cvs -z3 update -dP

=== Updating entire source tree (second time) ===
The is no need to login to CVS now, it remembers all that.

* clear away the existing rubble
make distclean
* update (You can skip the reporting of all directories by adding the -q flag (assumes -z3 and -dP were added to ~/.cvsrc)
cvs -q update
* re run ./configure and make

=== Updating just one module ===
Often you are interested in just a single bugfix or updated module. Assuming the change didn't affect libraries or the build system, you can just update and recompile the code in the module's directory.

* for example, updating just the r.cost module
cd raster/r.cost
cvs up
make

* If includes/ or module header files (*.h) have changed, you will have to run
make clean
before "<tt>make</tt>".

== Tips for users wanting to contributing code ==

=== Code Standards ===

See these files in the source code. To keep the GRASS source code manageable, all new code must conform.

* SUBMITTING
* SUBMITTING_SCRIPTS
* SUBMITTING_TCLTK

=== Legal issues ===

==== Copyright ====

* The developer may keep copyright on submitted code

* You must include copyright and licensing information in the header comments of your code so that others may know how they can use, extend, modify, and redistribute your work.

* The developer is encouraged to assign co-copyright to the GRASS Development Team. This gives the GRASS project flexibility over the source code, without this the Team must contact all former developers before allowing a license change (eg a legal hole is found in the GPL and the project needs to migrate to a new version) or confirming the original license. In a 20+ year old project, with often only a name and old email to go by, this becomes unworkable.

===== Example =====
at the top of a shell script:

#!/bin/sh
############################################################################
#
# MODULE: v.in.e00
#
# AUTHOR(S): Markus Neteler, Otto Dassau
#
# PURPOSE: Import E00 data into a GRASS vector map
# Imports single and split E00 files (.e00, .e01, .e02 ...)
#
# COPYRIGHT: (c) 2004, 2005 GDF Hannover bR, http://www.gdf-hannover.de
#
# This program is free software under the GNU General Public
# License (>=v2). Read the file COPYING that comes with GRASS
# for details.
#
#############################################################################

==== Licensing ====

* GRASS uses the GNU General Public License (the GPL).

==== Due diligence ====

* PSC RFC2

=== Code submission method ===

(Note: this applies to people without CVS write access)

'''Be sure to develop on top of the LATEST GRASS code (CVS HEAD), ''not'' on top of a stable branch.'''

You can re-check before submission with:
cvs diff -u

==== Preparing a patch ====

* create a unidiff patch against the latest development branch CVS

Be sure to create unified ("diff -u") format. "Plain" diffs (the default
format) are risky, because they will apply without warning to code which
has been substantially changed; they are also harder to read than unified.

Such diffs should be made from the top-level directory, e.g.
"cvs diff -u display/d.vect/main.c"; that way, the diff will
include the pathname rather than just "main.c".

Imagine, that You have hacked around in module r.foo. To create patch, You should use following commands:
cd /path/to/grass6
cvs diff -u raster/r.foo > r.foo.patch

==== Creating a GEM package ====

The GEM system makes it easy to prepare intergrated add-on modules or groups of add-on modules as extensions to the existing GRASS source code. Users do not need to build the entire GRASS source package to add and build GEM packages.

* link to GEM add-on docs

==== Submitting it to the Wiki Add-Ons page ====
The Add-ons page contains user contributed code which is not intended to go into the main GRASS source tree or is still experimental

* The [[GRASS AddOns]] page

==== Submitting it to the code tracker ====
Non-trival formal patches which are expected to become part of the main GRASS source tree should be uploaded to the "code patches" tracker and GRASS's Gforge site.

* http://wald.intevation.org/projects/grass/

==== Announcing it on the GRASS Development mailing list ====

Once it is uploaded to the Wiki Add-ons page or the Gforge code tracker, announce it on the [http://grass.ibiblio.org/devel/index.php#list GRASS-dev mailing list].

Final products added to the Wiki Add-Ons page should be announced on the GRASS users' mailing list.

==== Getting help ====

* IRC
* [http://grass.ibiblio.org/devel/index.php#list GRASS-dev mailing list]

== Tips for GRASS developers ==
(CVS write access, committing)

=== Becoming a GRASS developer ===

The [[PSC|GRASS Project Steering Committee]] is in charge of giving new developers write access to the CVS. This generally happens after the developer has been submitting code for long enough for the other developers to become familiar with the person and their coding ability.

=== Responsibilities ===

* [http://freegis.org/cgi-bin/viewcvs.cgi/grass6/rfc/RFC2_PSC.dox?rev=HEAD&content-type=text/vnd.viewcvs-markup RFC2: Legal aspects of code contributions]
* follow the [http://grass.itc.it/devel/index.php#submission code submission guidelines]

=== Setting it up ===

* Connection to CVS with write access: ssh, firewalls, login, etc.
** See [http://freegis.org//grass/howto_grass-sshcvs.en.html GRASS-CVS-ssh instructions]

* configuring GRASS for code development:
** Linux: please use these flags to configure GRASS, they will help you to catch most programming problems:
MYCFLAGS="-g -Wall -Werror-implicit-function-declaration -fno-common"
MYCXXFLAGS="-g -Wall"
CFLAGS="$MYCFLAGS" CXXFLAGS="$MYCXXFLAGS" ./configure ... (more flags and parameters)
** MacOSX:
** MS-Windows:

=== Commiting ===

* work against latest development branch CVS HEAD (update before committing)
* code must compile
* verify changes with 'cvs diff -u' before all commits
* cvs commit: make the cvs log message a useful synopsis of the change
* double check the change using the live WebCVS interface or [http://grass.itc.it/mailman/listinfo/grass-commit grass-commit mailing list]

Compile and Install

2006-12-09T16:19:20Z

⚠️MarisN: /* Configure options and they meaning */

== How to do compilation and installation of GRASS 6? ==

Here we explain the procedure to compile GRASS from CVS, but it also applies to official GRASS 6 releases.

''For installation of precompiled binary packages, see the main [[Installation Guide]].''

For detailed information on compilation, please see the [http://grass.itc.it/grass61/source/INSTALL INSTALL] file in the source code.

=== Prerequisites ===

GRASS needs at least two extra libraries: PROJ and GDAL/OGR

''Note: if you want to have DBMS support in GDAL (subsequently in GRASS) you have to perform the "Optional" steps below as well.''

* [http://proj.maptools.org PROJ4] for management of projections (with proj-datumgrid-1.3.zip support)
* Optional: [http://geos.refractions.net GEOS]
* Optional: [http://www.postgresql.org PostgreSQL], [http://www.mysql.org mySQL], [http://www.unixodbc.org unixODBC], [http://www.sqlite.org SQLite] (SQLite is needed for QGIS)
* [http://www.gdal.org GDAL/OGR] for reading and writing various GIS data formats (interoperability)

You have to install these two libraries '''first'''.

It is easiest to obtain a prepackaged version of these libraries (e.g., .rpm; .deb) for your particular operating system and run the corresponding package installation (e.g., rpm -Uhv packagename.rpm; apt-get) in a terminal window. Take care to also install the development packages of these libraries (...-devel packages). If there is no prepackage version, then you will have to download the source code (see links above, source code packages usually ends in .tar.gz or .zip) and compile it (you must have a C compiler installed as part of your operating system). The Web sites show the steps to compile the libraries.

Other libraries needed to run GRASS are listed here: [http://grass.itc.it/grass63/source/REQUIREMENTS.html REQUIREMENTS]. To compile, you will also need the respective "-devel" packages.

=== Generic Compilation and installation procedure ===

* checkout the grass6 module from cvs (read http://grass.itc.it/faq/cvs_howto.html grass CVS howto instructions)
* It is wise that compilation processes are carried out as a normal user: If you want to get the source code in a place where you do not have write permissions (e.g. in /usr/local/src/cvs) just follow this:
cd /usr/local/src/cvs
su -c 'mkdir grass6'
su -c 'chown yourlogin:yourgroup grass6'
* do a checkout (co) of the repository
cvs -z3 co grass6
* in the grass6 directory, you will find the precious INSTALL file, open it with your favourite pager/editor and read it carefully!
* run configure with parameters to adapt the compile process to your own system. To see what options can be passed to it, run configure --help. The minimum set of configure parameters is (refers to GRASS 6 from CVS, not to 6.x release):
./configure ### It may (!) look like this:
./configure \
--with-cxx \
--with-sqlite \
--with-postgres-libs=/usr/include/pgsql/libpq \
--with-postgres-includes=/usr/include/pgsql \
--with-freetype \
--with-freetype-includes=/usr/include/freetype2 \
--with-motif \
--with-glw \
--with-proj-share=/usr/share/proj

You may have to explicitly state the path for certain packages (i.e., gdal). The Unix 'locate' command will come in handy for finding the path of the package you need (you may have to run locate as root ex: sudo locate gdal-config).

Please note that the paths mentioned may widely vary due to the distribution used. At the end of configuration process you should get report not much different from this:

GRASS is now configured for: i686-pc-linux-gnu

Source directory: /usr/src/grass6
Build directory: /usr/src/grass6
Installation directory: /usr/local/grass-6.1.cvs
Startup script in directory: ${exec_prefix}/bin
C compiler: gcc -g -O2
C++ compiler: c++ -g -O2
FORTRAN compiler:
Building shared libraries: yes
64bit support: no

NVIZ: yes

BLAS support: no
C++ support: yes
DWG support: no
FFMPEG support: no
FFTW support: yes
FreeType support: yes
GDAL support: yes
GLw support: no
JPEG support: yes
LAPACK support: no
Large File Support (LFS): no
Motif support: no
MySQL support: no
NLS support: no
ODBC support: no
OGR support: yes
OpenGL(R) support: yes
PNG support: yes
PostgreSQL support: yes
Readline support: no
SQLite support: no
Tcl/Tk support: yes
TIFF support: yes
X11 support: yes

* Let's compile it (takes a little while...)!
make
* At the end, you should get report not much different from this:
----------------------------------------------------------------------
Following modules are missing the 'description.html' file in src code:
----------------------------------------------------------------------
GRASS GIS compilation log
-------------------------
Started compilation: Ne kvě 28 13:18:43 CEST 2006
--
Errors in:
--
Finished compilation: Ne kvě 28 13:43:40 CEST 2006
(In case of errors please change into the directory with error and run 'make')

* If there is any error, change directory to directory with error and run "make" again. Report occuring bug to grass mailing list
* Once the installation process is finished, you're ready to install GRASS system wide.
su -c 'make install'
* enjoy GRASS:
grass61

=== What else? ===

If you want to use [http://www.qgis.org QGIS], then also compile the GRASS-GDAL/OGR plugin. This is also useful to access your GRASS-data
from other application using GDAL/OGR like [http://thuban.intevation.de thuban].
* [[Compile and install GRASS and QGIS with GDAL/OGR Plugin]] (enables QGIS to read GRASS data directly)

=== Platform Specific Notes ===

==== Debian ====

* [http://hamish.bowman.googlepages.com/debiangisfiles#compile Compiling GRASS 6.1-CVS on Debian/Stable (aka 3.1, Sarge)]

* Official [http://pkg-grass.alioth.debian.org/cgi-bin/wiki.pl DebianGIS] packaging [http://svn.debian.org/wsvn/pkg-grass/packages/grass/branches/ control files].

==== Ubuntu 6.06 ====

* [http://david.p.finlayson.googlepages.com/makegrass.sh makegrass.sh] is script designed to automate most of the download, configuration and compilation of GRASS 6.x-CVS
* [[User:Steko/Automated_CVS_compiling|Here]] is another of these scripts, it's homemade so probably you'll find the above more useful for production sites.

==== RPM SPEC files ====

... can be found in the source code, rpm/ directory, or [http://www.gdf-hannover.de/media.php?id=1&lg=en here]

==== MS-Windows/Cygwin ====

... see [http://grass.itc.it/platforms/wingrass.html here] (should be moved to the Wiki)

==== MS-Windows/native ====

For this, you need MinGW and MSys, including gcc, g++, binutils, flex, bison, make, and pdcurses, all from:
http://www.mingw.org/download.shtml

You also need this version of the XDR library:
http://wiki.qgis.org/qgiswiki/BuildingWindowsBinaryOnLinux?action=AttachFile&do=get&target=xdr-4.0-mingw2.tar.gz

The above is a stripped-down version of the Sun RPC library, which only includes the XDR [de]serialisation code, with the networking code removed.

You will first need to build and install zlib, PNG, PROJ, GDAL and the above XDR library. Then, building GRASS is similar to building it on Linux, except that you need to disable most of the optional features (including the use of shared libraries).

Aside: it might encourage more people to work on the Windows version if the GRASS site contained binary versions of the necessary libraries. Having to build XDR, PROJ, GDAL, zlib, PNG, Tcl/Tk and possibly other stuff from source before you can start to compile GRASS is a major nuisance.

... or see [http://wiki.qgis.org/qgiswiki/BuildingWindowsBinaryOnLinux here incl. QGIS compilation] (with MinGW)

==== Mac OSX ====

... see [http://grass.itc.it/platforms/macgrass.php here] for instructions

==== Zaurus====

... see [http://wiki.debian.org/?GrassGISonZaurus here] for instructions

=== Common problems and solutions ===

During compilation, error can occur if certain packages are not installed. Here a list of problems with solution:

* error: X11/Xlib.h: No such file or directory
** this suggests that you don't have the X headers installed
** Solution: Install the libx11-dev package

=== Configure options and they meaning ===

For configure there are many options and some GRASS modules are built only if some options are set. Here are listed common configuration options with short explanation.

* --prefix=/path - Sets path where GRASS will be installed. GRASS will reside in /path/grass-version.
* --enable-largefile - Enables large (>2Gb on 32bit systems) support. For current large file support status look at [[Large File Support]] page.
* --with-cxx - Enables compilation of C++ code. Required for r.terraflow module.
* --with-glw - Enables GLw support. The GLw library provides OpenGL "canvas" widgets for Athena and Motif.

That switch is unnecessary for normal compilation. It's only
required for r3.showdspf, which isn't normally built; if you
want it, you have build it manually
(e.g. "make -C raster3d/r3.showdspf").
As similar functionality is now provided by NVIZ, r3.showdspf
is deprecated.
r3.showdspf uses the Motif widget (so you also need a
Motif library, e.g. Lesstif or OpenMotif).
[http://grass.itc.it/pipermail/grassuser/2006-December/037475.html Glynn Clements at GRASS-user mailing list]

[[Category:Development]]
[[Category:Documentation]]
[[Category:Installation]]

Compile and Install

2006-12-09T16:14:54Z

⚠️MarisN:

== How to do compilation and installation of GRASS 6? ==

Here we explain the procedure to compile GRASS from CVS, but it also applies to official GRASS 6 releases.

''For installation of precompiled binary packages, see the main [[Installation Guide]].''

For detailed information on compilation, please see the [http://grass.itc.it/grass61/source/INSTALL INSTALL] file in the source code.

=== Prerequisites ===

GRASS needs at least two extra libraries: PROJ and GDAL/OGR

''Note: if you want to have DBMS support in GDAL (subsequently in GRASS) you have to perform the "Optional" steps below as well.''

* [http://proj.maptools.org PROJ4] for management of projections (with proj-datumgrid-1.3.zip support)
* Optional: [http://geos.refractions.net GEOS]
* Optional: [http://www.postgresql.org PostgreSQL], [http://www.mysql.org mySQL], [http://www.unixodbc.org unixODBC], [http://www.sqlite.org SQLite] (SQLite is needed for QGIS)
* [http://www.gdal.org GDAL/OGR] for reading and writing various GIS data formats (interoperability)

You have to install these two libraries '''first'''.

It is easiest to obtain a prepackaged version of these libraries (e.g., .rpm; .deb) for your particular operating system and run the corresponding package installation (e.g., rpm -Uhv packagename.rpm; apt-get) in a terminal window. Take care to also install the development packages of these libraries (...-devel packages). If there is no prepackage version, then you will have to download the source code (see links above, source code packages usually ends in .tar.gz or .zip) and compile it (you must have a C compiler installed as part of your operating system). The Web sites show the steps to compile the libraries.

Other libraries needed to run GRASS are listed here: [http://grass.itc.it/grass63/source/REQUIREMENTS.html REQUIREMENTS]. To compile, you will also need the respective "-devel" packages.

=== Generic Compilation and installation procedure ===

* checkout the grass6 module from cvs (read http://grass.itc.it/faq/cvs_howto.html grass CVS howto instructions)
* It is wise that compilation processes are carried out as a normal user: If you want to get the source code in a place where you do not have write permissions (e.g. in /usr/local/src/cvs) just follow this:
cd /usr/local/src/cvs
su -c 'mkdir grass6'
su -c 'chown yourlogin:yourgroup grass6'
* do a checkout (co) of the repository
cvs -z3 co grass6
* in the grass6 directory, you will find the precious INSTALL file, open it with your favourite pager/editor and read it carefully!
* run configure with parameters to adapt the compile process to your own system. To see what options can be passed to it, run configure --help. The minimum set of configure parameters is (refers to GRASS 6 from CVS, not to 6.x release):
./configure ### It may (!) look like this:
./configure \
--with-cxx \
--with-sqlite \
--with-postgres-libs=/usr/include/pgsql/libpq \
--with-postgres-includes=/usr/include/pgsql \
--with-freetype \
--with-freetype-includes=/usr/include/freetype2 \
--with-motif \
--with-glw \
--with-proj-share=/usr/share/proj

You may have to explicitly state the path for certain packages (i.e., gdal). The Unix 'locate' command will come in handy for finding the path of the package you need (you may have to run locate as root ex: sudo locate gdal-config).

Please note that the paths mentioned may widely vary due to the distribution used. At the end of configuration process you should get report not much different from this:

GRASS is now configured for: i686-pc-linux-gnu

Source directory: /usr/src/grass6
Build directory: /usr/src/grass6
Installation directory: /usr/local/grass-6.1.cvs
Startup script in directory: ${exec_prefix}/bin
C compiler: gcc -g -O2
C++ compiler: c++ -g -O2
FORTRAN compiler:
Building shared libraries: yes
64bit support: no

NVIZ: yes

BLAS support: no
C++ support: yes
DWG support: no
FFMPEG support: no
FFTW support: yes
FreeType support: yes
GDAL support: yes
GLw support: no
JPEG support: yes
LAPACK support: no
Large File Support (LFS): no
Motif support: no
MySQL support: no
NLS support: no
ODBC support: no
OGR support: yes
OpenGL(R) support: yes
PNG support: yes
PostgreSQL support: yes
Readline support: no
SQLite support: no
Tcl/Tk support: yes
TIFF support: yes
X11 support: yes

* Let's compile it (takes a little while...)!
make
* At the end, you should get report not much different from this:
----------------------------------------------------------------------
Following modules are missing the 'description.html' file in src code:
----------------------------------------------------------------------
GRASS GIS compilation log
-------------------------
Started compilation: Ne kvě 28 13:18:43 CEST 2006
--
Errors in:
--
Finished compilation: Ne kvě 28 13:43:40 CEST 2006
(In case of errors please change into the directory with error and run 'make')

* If there is any error, change directory to directory with error and run "make" again. Report occuring bug to grass mailing list
* Once the installation process is finished, you're ready to install GRASS system wide.
su -c 'make install'
* enjoy GRASS:
grass61

=== What else? ===

If you want to use [http://www.qgis.org QGIS], then also compile the GRASS-GDAL/OGR plugin. This is also useful to access your GRASS-data
from other application using GDAL/OGR like [http://thuban.intevation.de thuban].
* [[Compile and install GRASS and QGIS with GDAL/OGR Plugin]] (enables QGIS to read GRASS data directly)

=== Platform Specific Notes ===

==== Debian ====

* [http://hamish.bowman.googlepages.com/debiangisfiles#compile Compiling GRASS 6.1-CVS on Debian/Stable (aka 3.1, Sarge)]

* Official [http://pkg-grass.alioth.debian.org/cgi-bin/wiki.pl DebianGIS] packaging [http://svn.debian.org/wsvn/pkg-grass/packages/grass/branches/ control files].

==== Ubuntu 6.06 ====

* [http://david.p.finlayson.googlepages.com/makegrass.sh makegrass.sh] is script designed to automate most of the download, configuration and compilation of GRASS 6.x-CVS
* [[User:Steko/Automated_CVS_compiling|Here]] is another of these scripts, it's homemade so probably you'll find the above more useful for production sites.

==== RPM SPEC files ====

... can be found in the source code, rpm/ directory, or [http://www.gdf-hannover.de/media.php?id=1&lg=en here]

==== MS-Windows/Cygwin ====

... see [http://grass.itc.it/platforms/wingrass.html here] (should be moved to the Wiki)

==== MS-Windows/native ====

For this, you need MinGW and MSys, including gcc, g++, binutils, flex, bison, make, and pdcurses, all from:
http://www.mingw.org/download.shtml

You also need this version of the XDR library:
http://wiki.qgis.org/qgiswiki/BuildingWindowsBinaryOnLinux?action=AttachFile&do=get&target=xdr-4.0-mingw2.tar.gz

The above is a stripped-down version of the Sun RPC library, which only includes the XDR [de]serialisation code, with the networking code removed.

You will first need to build and install zlib, PNG, PROJ, GDAL and the above XDR library. Then, building GRASS is similar to building it on Linux, except that you need to disable most of the optional features (including the use of shared libraries).

Aside: it might encourage more people to work on the Windows version if the GRASS site contained binary versions of the necessary libraries. Having to build XDR, PROJ, GDAL, zlib, PNG, Tcl/Tk and possibly other stuff from source before you can start to compile GRASS is a major nuisance.

... or see [http://wiki.qgis.org/qgiswiki/BuildingWindowsBinaryOnLinux here incl. QGIS compilation] (with MinGW)

==== Mac OSX ====

... see [http://grass.itc.it/platforms/macgrass.php here] for instructions

==== Zaurus====

... see [http://wiki.debian.org/?GrassGISonZaurus here] for instructions

=== Common problems and solutions ===

During compilation, error can occur if certain packages are not installed. Here a list of problems with solution:

* error: X11/Xlib.h: No such file or directory
** this suggests that you don't have the X headers installed
** Solution: Install the libx11-dev package

=== Configure options and they meaning ===

For configure there are many options and some GRASS modules are built only if some options are set. Here are listed common configuration options with short explanation.

* --prefix=/path - Sets path where GRASS will be installed. GRASS will reside in /path/grass-version.
* --with-glw - Enables GLw support. The GLw library provides OpenGL "canvas" widgets for Athena and Motif.

That switch is unnecessary for normal compilation. It's only
required for r3.showdspf, which isn't normally built; if you
want it, you have build it manually
(e.g. "make -C raster3d/r3.showdspf").
As similar functionality is now provided by NVIZ, r3.showdspf
is deprecated.
r3.showdspf uses the Motif widget (so you also need a
Motif library, e.g. Lesstif or OpenMotif).
[http://grass.itc.it/pipermail/grassuser/2006-December/037475.html Glynn Clements at GRASS-user mailing list]

[[Category:Development]]
[[Category:Documentation]]
[[Category:Installation]]

Movies

2006-12-09T15:49:32Z

⚠️MarisN:

Q: If anyone has tips on constructing high-quality MPEG-4 movies (animations) from a series of still frames, I'd be interested in hearing them.

Maris wrote:

Encode all .png files in directory to out.avi with 15 frames per second:
<pre>
mencoder "mf:///path/to/files/*.png" -mf fps=15 -o out.avi # put -ovc here, see next lines

## for DivX - libavcodec MPEG 4 (DivX5), use:
-ovc lavc -lavcopts vcodec=mpeg4:vhq:vbitrate=1800 -ffourcc MP4S
## for XviD, use:
-ovc xvid -xvidencopts bitrate=1024
## for DivX4, use:
-ovc divx4 -divx4opts q=5
</pre>

Uses mplayer's encoder. Choose one of encoding formats and append to end
of "mencoder" line. Unfortunately only way to know quality settings is by
encoding, watching result and reendocing with different params.

Notice - by default encoding with lavc will set video fourcc to FMP4, that can be decoded with ffdshow. Option -ffourcc MP4S will change it to MPS4 ("official" MS fourcc for mpeg4) and video will be playable on Windows by standart MS mpeg4 decoder. It may lead to side effects, if MS mpeg4 decoder is buggy. More info: http://www.itdp.de/mplayer-users/2005-03/msg00069.html

--------
Q: How to generate an animated GIF, FLI, or MNG?

A: for animations of 300 frames or less, animated GIF, FLI, or MNG formats are smaller files and better quality (ie frames stored as PNG not JPEG). Create with [http://www.lcdf.org/gifsicle/ gifsicle], [http://vento.pi.tu-berlin.de/fli.html ppm2fli], or for MNG use [http://www.imagemagick.org/ ImageMagick's 'convert']. With more than 300 frames the players usually have memory issues. Animated GIFs are playable in any web browser of course and also in OpenOffice.

[[Category:FAQ]]