GRASS-Wiki - User contributions [en]

Talk:GRASS Community Meeting Prague 2023

2023-06-04T22:02:17Z

⚠️Hellik: /* Helmut Kudrnovsky */

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

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

=== 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
Initialize second file/function: ''r.optram.soilmoisture.py''
# createSoilMoisture() - creates new GRASS raster

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

=== 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!)
* 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

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

=== Floris Vanderhaeghe ===

* Explore reading straight from the GRASS database into R (https://github.com/rsbivand/rgrass/issues/75)
* Help arranging a meeting with Nyall Dawson for the QGIS GRASS interfase
* Participate in a two-hour meeting with Roger Bivand, Vero Andreo, Vaclav, Anna, Helmut, Micha, ..... about rgrass development

=== 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]
* Other minor revisions

Talk:GRASS Community Meeting Prague 2023

2023-06-04T17:14:06Z

⚠️Hellik: /* Helmut Kudrnovsky */

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

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

=== 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
Initialize second file/function: ''r.optram.soilmoisture.py''
# createSoilMoisture() - creates new GRASS raster

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

=== 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!)
* 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

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

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

=== Floris Vanderhaeghe ===

* Explore reading straight from the GRASS database into R (https://github.com/rsbivand/rgrass/issues/75)
* Help arranging a meeting with Nyall Dawson for the QGIS GRASS interfase
* Participate in a two-hour meeting with Roger Bivand, Vero Andreo, Vaclav, Anna, Helmut, Micha, ..... about rgrass development

Talk:GRASS Community Meeting Prague 2023

2023-06-03T10:42:58Z

⚠️Hellik: /* Helmut Kudrnovsky */

Talk:GRASS Community Meeting Prague 2023

2023-06-03T09:02:46Z

⚠️Hellik: /* Reports */

Talk:GRASS Community Meeting Prague 2023

2023-06-03T09:02:14Z

⚠️Hellik: /* Reports */

GRASS Community Meeting Prague 2023

2023-05-11T19:13:07Z

⚠️Hellik: /* In person */

{{toc|right}}
The GRASS GIS team is organizing the ''GRASS GIS Community Meeting with contributors, power users and developers'' from '''June 2 to June 6, 2023''' to celebrate GRASS GIS '''40th birthday''' (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 :/
|
|-
|}

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

== Broadcast & Video ==

During the event :)

== Photos ==

Also during the event :)

== FAQ ==

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

== 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-04T18:51:33Z

⚠️Hellik: /* In person */

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

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

== Purpose ==

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

For the detailed agenda, see below.

== Sponsors ==

We welcome '''financial contributions''' to support the meeting and we are looking for sponsors to cover costs such as meals or to help reducing 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 ===

Will be specified later.

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

* Arrival

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

* 10:00 meeting starts in the room B-868

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

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

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

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

==== 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'''
!width=75px|'''T-Shirt'''
!'''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
| XL
|
|-
|2
| Micha Silver
| Israel
| June 2
| June 6
| Addon to derive soil moisture from Sentinel 2
| XXL
|
|-
|3
|[https://www.osgeo.org/member/kudrnovsky/ Helmut Kudrnovsky]
| Austria
| June 2 (18:37) by train
| June 4 (18:24) by train
|
| L
|
|-
|4
|[[User:Neteler|Markus Neteler]]
| Germany
| June 2
| June 6 (12:43)
| see [[Talk:GRASS_Community_Meeting_Prague_2023#Markus_Neteler|my list in "Discussion" page]]
| L
|
|-
|5
|[[User:pesekon2|Ondřej Pešek]]
| Czech Republic
| June 2 (17:17)
| June 6 (12:43)
| Python 3.12-connected issues, gmodeler
| M
|
|-
|6
| [[User:helena|Helena Mitasova]]
| United States
| June 2
| June 6
|
| S
|
|-
|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
| M
|
|-
|8
| [[User:Annakrat|Anna Petrasova]]
| United States
| June 1
| June 7
| parallelization, grass.jupyter
| S
|
|-
|9
| [[User:Ctwhite|Corey White]]
| United States
| June 2 (10:55)
| June 7
| Connections with other tools, OpenPlains, JSON outputs
| XL
|
|-
|10
| [[User:MarisN|Maris Nartiss]]
| Latvia
| June 2
| June 6
|
| XL
|-
|11
| [[User:Aaronsms|Aaron Saw Min Sern]]
| Singapore
| June 1
| June 7
| Support CMake transition, r.mapcalc parallelization
| XS (or S)
| Possibly attending virtually (TBC)
|-
|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.
| M
|
|-
|13
| [[User:Chaedrich|Caitlin Haedrich]]
| United States
| June 1
| June 7
| grass.jupyter
| S
|
|-
|14
| [[User:Lindakladivova|Linda Kladivová]]
| Czech Republic
| June 2
| June 6
|
| M
|
|-
|15
| Carmen Tawalika
| Germany
| June 2
| June 6
| Happy to assist with general topics like documentation + automation, in doubt something related to actinia
| M
|
|-
|}

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'''
!'''Notes'''
|-
|1
|[[User:Baharmon|Brendan Harmon]]
| United States
| Update integration with QGIS
|
|-
|2
|[[User:veroandreo|Veronica Andreo]]
| Argentina
| See [https://grasswiki.osgeo.org/wiki/Talk:GRASS_Community_Meeting_Prague_2023#Vero discussion tab]
|
|-
|}

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

== Broadcast & Video ==

During the event :)

== Photos ==

Also during the event :)

== FAQ ==

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

== 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-03-21T18:38:08Z

⚠️Hellik: /* In person */

2018-12-23T19:37:53Z

2018-09-23T20:35:40Z

⚠️Hellik: /* Startup */

'''This page refers to the usage of R within a GRASS GIS 7 session and the use of GRASS GIS 7 within an R session.''' (see also [[R_statistics/spgrass6]])

== Terminology ==

Using R in conjunction with GRASS GIS can have two meanings:

* Using '''R within GRASS GIS session''', i.e. you start R (or RStudio) from the GRASS GIS command line. You may like this variant if you are primarily a GIS user.
* Using '''GRASS GIS within a R session''', i.e. you connect to a GRASS GIS location/mapset from within R (or RStudio). You may like this variant if you are primarily a R user.



'''References''': see "Overview" in [[R_statistics]]

== Installation ==

See [[R_statistics/Installation]]

== R within GRASS ==

Using '''R within GRASS GIS session''', i.e. you start R (or RStudio) from the GRASS GIS command line.

=== Startup ===

* First start a GRASS GIS session. Then, at the GRASS command line start ''R'' (for a 'rstudio' session, see below)
: ''In this example we will use the [http://grass.osgeo.org/download/sample-data/ North Carolina sample dataset].''

Reset the region settings to the defaults
<source lang="bash">
GRASS 7.0.1svn (nc_spm_08_grass7):~ > g.region -d
</source>

Launch R from the GRASS prompt
<source lang="bash">
GRASS 7.0.1svn (nc_spm_08_grass7):~ > R
</source>

Load the ''rgrass7'' library:
<source lang="rsplus">
library(rgrass7)
</source>

If you plan to follow the example using the North Carolina sample dataset, load the ''rgdal'' library:
<source lang="rsplus">
library(rgdal)
</source>

Get the GRASS environment (mapset, region, map projection, etc.); you can display the metadata for your location by printing G:
<source lang="rsplus">
G <- gmeta()
gisdbase /home/neteler/grassdata
location nc_spm_08_grass7
mapset user1
rows 620
columns 1630
north 320000
south 10000
west 120000
east 935000
nsres 500
ewres 500
projection +proj=lcc +lat_1=36.16666666666666 +lat_2=34.33333333333334
+lat_0=33.75 +lon_0=-79 +x_0=609601.22 +y_0=0 +no_defs +a=6378137
+rf=298.257222101 +towgs84=0.000,0.000,0.000 +to_meter=1
</source>

=== Listing of existing maps ===

List available vector maps:
<source lang="rsplus">
execGRASS("g.list", parameters = list(type = "vector"))
</source>

List selected vector maps (wildcard):
<source lang="rsplus">
execGRASS("g.list", parameters = list(type = "vector", pattern = "precip*"))
</source>

Save selected vector maps into R vector:
<source lang="rsplus">
my_vmaps <- execGRASS("g.list", parameters = list(type = "vector", pattern = "precip*"))
attributes(my_vmaps)
attributes(my_vmaps)$resOut
</source>

List available raster maps:
<source lang="rsplus">
execGRASS("g.list", parameters = list(type = "raster"))
</source>

List selected raster maps (wildcard):
<source lang="rsplus">
execGRASS("g.list", parameters = list(type = "raster", pattern = "lsat7_2002*"))
</source>

=== Reading in data from GRASS ===

==== Example 1 ====

Read in two GRASS raster maps (the maps "geology_30m" and "elevation" from the North Carolina sample data location) into the R current session as a new object "ncdata" (containing then two SpatialGridDataFrames as well as metadata):
<source lang="rsplus">
# the cat parameter indicates which raster values to be returned as factors
# - geology_30m is a categorical map (i.e., it comes with classes)
# - elevation is a continuous surface
ncdata <- readRAST(c("geology_30m", "elevation"), cat=c(TRUE, FALSE))
</source>
(A warning may appear since in the "geology_30m" map two labels are not unique - as found in the original data.)

We can verify the new R object:
<source lang="rsplus">
str(ncdata)
Formal class 'SpatialGridDataFrame' [package "sp"] with 4 slots
..@ data :'data.frame': 16616 obs. of 2 variables:
</source>

and also check the data structure in more detail:
<source lang="rsplus">
str(ncdata@data)
'data.frame': 16616 obs. of 2 variables:
$ geology_30m: Factor w/ 12 levels "CZfg_217","CZlg_262",..: NA NA NA NA NA NA NA NA NA NA ...
$ elevation : num NA NA NA NA NA NA NA NA NA NA ...
</source>

The metadata are now accessed and available, but are not (yet) used to structure the ''sp'' class objects, in this case a SpatialGridDataFrame object filled with data from two North Carolina layers. Here is a plot of the elevation data:
<source lang="rsplus">
image(ncdata, "elevation", col = terrain.colors(20))
</source>

Add a title to the plot:
<source lang="rsplus">
title("North Carolina elevation")
</source>

[[Image:ncdata.png|center]]

In addition, we can show what is going on inside the objects read into R:
<source lang="rsplus">
str(G)
List of 26
$ DEBUG : chr "0"
$ LOCATION_NAME: chr "nc_spm_08_grass7"
$ GISDBASE : chr "/home/veroandreo/grassdata"
$ MAPSET : chr "PERMANENT"
$ GUI : chr "wxpython"
$ projection : chr "99"
$ zone : chr "0"
$ n : num 228500
$ s : num 215000
$ w : num 630000
$ e : num 645000
$ t : num 1
$ b : num 0
$ nsres : num 27.5
$ nsres3 : num 10
$ ewres : num 37.5
$ ewres3 : num 10
$ tbres : num 1
$ rows : int 491
$ rows3 : int 1350
$ cols : int 400
$ cols3 : int 1500
$ depths : int 1
$ cells : chr "196400"
$ cells3 : chr "2025000"
$ proj4 : chr "+proj=lcc +lat_1=36.16666666666666 +lat_2=34.33333333333334 +lat_0=33.75 +lon_0=-79 +x_0=609601.22 +y_0=0 +no_defs +a=6378137 +"| __truncated__
- attr(*, "class")= chr "gmeta"

summary(ncdata)
Object of class SpatialGridDataFrame
Coordinates:
min max
[1,] 630000 645000
[2,] 215000 228500
Is projected: TRUE
proj4string :
[+proj=lcc +lat_1=36.16666666666666 +lat_2=34.33333333333334
+lat_0=33.75 +lon_0=-79 +x_0=609601.22 +y_0=0 +no_defs +a=6378137
+rf=298.257222101 +towgs84=0.000,0.000,0.000 +to_meter=1]
Grid attributes:
cellcentre.offset cellsize cells.dim
1 630018.8 37.50000 400
2 215013.7 27.49491 491
Data attributes:
geology_30m elevation
CZfg_217:70381 Min. : 55.92
CZig_270:66861 1st Qu.: 94.78
CZbg_405:24561 Median :108.88
CZlg_262:19287 Mean :110.38
CZam_862: 6017 3rd Qu.:126.78
CZbg_910: 4351 Max. :156.25
(Other) : 4942
</source>

==== Example 2 ====

Here an example for a single map transfer from GRASS GIS to R:

<source lang="rsplus">
library(rgrass7)
execGRASS("g.region", raster = "elevation", flags = "p")
ncdata <- readRAST("elevation", cat=FALSE)
summary(ncdata)
spplot(ncdata, col = terrain.colors(20))
</source>

=== Summarizing data ===

We can create a table of cell counts:
<source lang="rsplus">
table(ncdata$geology_30m)
</source>
{| class="wikitable" border="1"
!CZfg_217
!CZlg_262
!CZig_270
!CZbg_405
!CZve_583
!CZam_720
!CZg_766
!CZam_862
!CZbg_910
!Km_921
!CZbg_945
!CZam_946
!CZam_948
|-
|70381
|19287
|66861
|24561
|2089
|467
|691
|6017
|4351
|1211
|1
|398
|85
|}

And compare with the equivalent GRASS module:
<source lang="rsplus">
execGRASS("r.stats", flags=c("c", "l"), parameters=list(input="geology_30m"), ignore.stderr=TRUE)
</source>
<pre>
217 CZfg 70381
262 CZlg 19287
270 CZig 66861
405 CZbg 24561
583 CZve 2089
720 CZam 467
766 CZg 691
862 CZam 6017
910 CZbg 4351
921 Km 1211
945 CZbg 1
946 CZam 398
948 CZam 85
</pre>

Create a box plot of geologic types at different elevations:
<source lang="rsplus">
boxplot(ncdata$elevation ~ ncdata$geology_30m, medlwd = 1)
</source>

[[Image:boxplot_geo.png|center]]

=== Querying maps ===

Sometimes you may want to query GRASS GIS maps from your R session.

As an example, here the transfer of raster pixel values at the position of vector points:

<source lang="rsplus">
# set the computational region first to the raster map:
execGRASS("g.region", raster = "elev_state_500m", flags = "p")

# query raster map at vector points, transfer result into R
goutput <- execGRASS("r.what", map="elev_state_500m", points="geodetic_pts", separator=",", intern=TRUE)
str(goutput)
chr [1:29939] "571530.81289275,265739.968425953,,187.8082200648" ...

# parse it
con <- textConnection(goutput)
go1 <- read.csv(con, header=FALSE)
str(go1)
'data.frame': 29939 obs. of 4 variables:
$ V1: num 571531 571359 571976 572391 573011 ...
$ V2: num 265740 265987 267049 267513 269615 ...
$ V3: logi NA NA NA NA NA NA ...
$ V4: Factor w/ 22738 levels "-0.0048115728",..: 6859 6642 6749 6411 6356 6904 7506 7224 6908 7167 ...
summary(go1)
V1 V2 V3 V4
Min. :121862 Min. : 7991 Mode:logical 0 : 723
1st Qu.:462706 1st Qu.:162508 NA's:29939 * : 293
Median :610328 Median :204502 0.3048 : 47
Mean :588514 Mean :200038 0.6096 : 44
3rd Qu.:717610 3rd Qu.:247633 1.524 : 42
Max. :946743 Max. :327186 0.9144 : 23
(Other):28767
</source>

=== Exporting data back to GRASS ===

Finally, a SpatialGridDataFrame object is written back to a GRASS raster map:

First prepare some data: (square root of elevation)
<source lang="rsplus">
ncdata$sqdem <- sqrt(ncdata$elevation)
</source>

Export data from ''R'' back into a GRASS raster map:
<source lang="rsplus">
writeRAST(ncdata, "sqdemNC", zcol="sqdem", ignore.stderr=TRUE)
</source>

Check that it imported into GRASS ok:
<source lang="rsplus">
execGRASS("r.info", parameters=list(map="sqdemNC"))
</source>

<pre>
+----------------------------------------------------------------------------+
| Map: sqdemNC Date: Sun Jul 19 13:06:34 2015 |
| Mapset: PERMANENT Login of Creator: veroandreo |
| Location: nc_spm_08_grass7 |
| DataBase: /home/veroandreo/grassdata |
| Title: ( sqdemNC ) |
| Timestamp: none |
|----------------------------------------------------------------------------|
| |
| Type of Map: raster Number of Categories: 0 |
| Data Type: DCELL |
| Rows: 491 |
| Columns: 400 |
| Total Cells: 196400 |
| Projection: Lambert Conformal Conic |
| N: 228500 S: 215000.0002 Res: 27.49490794 |
| E: 645000 W: 630000 Res: 37.5 |
| Range of data: min = 7.47818253045085 max = 12.5000787351036 |
| |
| Data Description: |
| generated by r.in.bin |
| |
| Comments: |
| |
+----------------------------------------------------------------------------+
</pre>

=== Using RStudio in a GRASS GIS session ===

If you are most used to run R through RStudio, but still want to have all GRASS data available for performing
any analyses without loosing the possibility of still using GRASS command line, you can run:

<source lang="bash">
GRASS> rstudio &
</source>

or, if you already are working on a certain RStudio project:

<source lang="bash">
GRASS> rstudio /path/to/project/folder/ &
</source>

Then, you load rgrass7 library in your RStudio project
<source lang="rsplus">
library(rgrass7)
</source>

and you are ready to go.

[[File:Grass7_rstudio.png|thumb|500px|center|RStudio used in GRASS GIS 7 session]]

== GRASS within R ==

Using '''GRASS GIS within a R session''', i.e. you connect to a GRASS GIS location/mapset from within R (or RStudio).

=== Startup ===

In the first place, find out the path to the GRASS GIS library. This can be easily done with the following command (still outside of R; or through a system() call inside of R):

<source lang="bash">
# OSGeo4W users:
grass74 --config path

# Linux, Mac OSX users:
grass70 --config path
</source>

It may report something like:
<source lang="bash">
# OSGeo4W users:
C:\OSGEO4~1\apps\grass\grass-7.4.1

# Linux, Mac OSX users:
/usr/local/grass-7.0.1
</source>

To call GRASS GIS 7 functionality from R, start R and use the initGRASS() function to define the GRASS settings:

<source lang="rsplus">
## MS-Windows users (example for a OSGeo4W 64bit installation):
library(rgrass7)
# initialisation and the use of North Carolina sample dataset
initGRASS(gisBase = "C:/OSGeo4W64/apps/grass/grass-7.4.1",
gisDbase = "C:/Users/marissa/GRASSdata/",
location = "nc_spm_08_grass7", mapset = "user1", SG="elevation")

## Linux, Mac OSX users:
library(rgrass7)
# initialisation and the use of North Carolina sample dataset
initGRASS(gisBase = "/usr/local/grass-7.0.1", home = tempdir(),
gisDbase = "/home/veroandreo/grassdata/",
location = "nc_spm_08_grass7", mapset = "user1", SG="elevation")
</source>

Note: the optional SG parameter is a 'SpatialGrid' object to define the ‘DEFAULT_WIND’ of the temporary location.

<source lang="rsplus">
# set computational region to default (optional)
system("g.region -dp")
# verify metadata
gmeta()

# get two raster maps into R space
ncdata <- readRAST(c("geology_30m", "elevation"), cat=c(TRUE, FALSE))

# calculate object summaries
summary(ncdata$geology_30m)
CZfg_217 CZlg_262 CZig_270 CZbg_405 CZve_583 CZam_720 CZg_766 CZam_862
292 78 277 102 8 1 2 25
CZbg_910 Km_921 CZam_946 NA's
18 5 2 1009790
</source>

== R in GRASS in batch mode ==

Run the following script with

<source lang="bash">
R CMD BATCH batch.R
</source>

<source lang="rsplus">
library(rgrass7)
# initialisation and the use of north carolina dataset
initGRASS(gisBase = "/home/veroandreo/software/grass-7.0.svn/dist.x86_64-unknown-linux-gnu",
home = tempdir(),
gisDbase = "/home/veroandreo/grassdata/",
location = "nc_spm_08_grass7", mapset = "user1", SG="elevation",
override = TRUE)
# set region to default
system("g.region -dp")
# verify
gmeta()
# read data into R
ncdata <- readRAST(c("geology_30m", "elevation"), cat=c(TRUE, FALSE))
# summary of geology map
summary(ncdata$geology_30m)
proc.time()
</source>

The result is (shorted here):
<source lang="bash">
cat batch.Rout
</source>

<source lang="rsplus">
R version 3.2.1 (2015-06-18) -- "World-Famous Astronaut"
Copyright (C) 2015 The R Foundation for Statistical Computing
Platform: x86_64-redhat-linux-gnu (64-bit)
...
> library(rgrass7)
Loading required package: sp
Loading required package: XML
GRASS GIS interface loaded with GRASS version: (GRASS not running)
> # initialisation and the use of north carolina dataset
> initGRASS(gisBase = "/home/veroandreo/software/grass-7.0.svn/dist.x86_64-unknown-linux-gnu", home = tempdir(),
+ gisDbase = "/home/veroandreo/grassdata/",
+ location = "nc_spm_08_grass7", mapset = "user1", SG="elevation",
+ override = TRUE)
gisdbase /home/veroandreo/grassdata/
location nc_spm_08_grass7
mapset user1
rows 620
columns 1630
north 320000
south 10000
west 120000
east 935000
nsres 500
ewres 500
projection +proj=lcc +lat_1=36.16666666666666 +lat_2=34.33333333333334
+lat_0=33.75 +lon_0=-79 +x_0=609601.22 +y_0=0 +no_defs +a=6378137
+rf=298.257222101 +towgs84=0.000,0.000,0.000 +to_meter=1

> system("g.region -dp")
projection: 99 (Lambert Conformal Conic)
zone: 0
datum: nad83
ellipsoid: a=6378137 es=0.006694380022900787
north: 320000
south: 10000
west: 120000
east: 935000
nsres: 500
ewres: 500
rows: 620
cols: 1630
cells: 1010600
> gmeta()
gisdbase /home/veroandreo/grassdata/
location nc_spm_08_grass7
mapset user1
rows 620
columns 1630
north 320000
south 10000
...
> ncdata <- readRAST(c("geology_30m", "elevation"), cat=c(TRUE, FALSE))
...
> summary(ncdata$geology_30m)
CZfg_217 CZlg_262 CZig_270 CZbg_405 CZve_583 CZam_720 CZg_766 CZam_862
292 78 277 102 8 1 2 25
CZbg_910 Km_921 CZam_946 NA's
18 5 2 1009790
> proc.time()
user system elapsed
8.061 2.016 10.048
</source>

== Troubleshooting ==

=== Running out of disk space ===

Linux: A common issue is that /tmp/ is used for temporary files albeit being often a small partition. To change that to a larger directory, you may add to your <tt>$HOME/.bashrc</tt> the entry:

<source lang="bash">
# change TMP directory of R (note: of course also another directory than suggested here is fine)
mkdir -p $HOME/tmp
export TMP=$HOME/tmp
</source>

The drawback is that on modern Linux systems the /tmp/ is a fast RAM disk (based on tempfs) while HOME directories are often on slower spinning disks (unless you have a SSD drive). At least you no longer run out of disk space easily.

[[Category:FAQ]]
[[Category:Linking to other languages]]
[[Category:R]]
[[Category:Statistics]]

R statistics/rgrass

2018-09-23T20:34:09Z

⚠️Hellik: /* Startup */

'''This page refers to the usage of R within a GRASS GIS 7 session and the use of GRASS GIS 7 within an R session.''' (see also [[R_statistics/spgrass6]])

== Terminology ==

Using R in conjunction with GRASS GIS can have two meanings:

* Using '''R within GRASS GIS session''', i.e. you start R (or RStudio) from the GRASS GIS command line. You may like this variant if you are primarily a GIS user.
* Using '''GRASS GIS within a R session''', i.e. you connect to a GRASS GIS location/mapset from within R (or RStudio). You may like this variant if you are primarily a R user.



'''References''': see "Overview" in [[R_statistics]]

== Installation ==

See [[R_statistics/Installation]]

== R within GRASS ==

Using '''R within GRASS GIS session''', i.e. you start R (or RStudio) from the GRASS GIS command line.

=== Startup ===

* First start a GRASS GIS session. Then, at the GRASS command line start ''R'' (for a 'rstudio' session, see below)
: ''In this example we will use the [http://grass.osgeo.org/download/sample-data/ North Carolina sample dataset].''

Reset the region settings to the defaults
<source lang="bash">
GRASS 7.0.1svn (nc_spm_08_grass7):~ > g.region -d
</source>

Launch R from the GRASS prompt
<source lang="bash">
GRASS 7.0.1svn (nc_spm_08_grass7):~ > R
</source>

Load the ''rgrass7'' library:
<source lang="rsplus">
library(rgrass7)
</source>

If you plan to follow the example using the North Carolina sample dataset, load the ''rgdal'' library:
<source lang="rsplus">
library(rgdal)
</source>

Get the GRASS environment (mapset, region, map projection, etc.); you can display the metadata for your location by printing G:
<source lang="rsplus">
G <- gmeta()
gisdbase /home/neteler/grassdata
location nc_spm_08_grass7
mapset user1
rows 620
columns 1630
north 320000
south 10000
west 120000
east 935000
nsres 500
ewres 500
projection +proj=lcc +lat_1=36.16666666666666 +lat_2=34.33333333333334
+lat_0=33.75 +lon_0=-79 +x_0=609601.22 +y_0=0 +no_defs +a=6378137
+rf=298.257222101 +towgs84=0.000,0.000,0.000 +to_meter=1
</source>

=== Listing of existing maps ===

List available vector maps:
<source lang="rsplus">
execGRASS("g.list", parameters = list(type = "vector"))
</source>

List selected vector maps (wildcard):
<source lang="rsplus">
execGRASS("g.list", parameters = list(type = "vector", pattern = "precip*"))
</source>

Save selected vector maps into R vector:
<source lang="rsplus">
my_vmaps <- execGRASS("g.list", parameters = list(type = "vector", pattern = "precip*"))
attributes(my_vmaps)
attributes(my_vmaps)$resOut
</source>

List available raster maps:
<source lang="rsplus">
execGRASS("g.list", parameters = list(type = "raster"))
</source>

List selected raster maps (wildcard):
<source lang="rsplus">
execGRASS("g.list", parameters = list(type = "raster", pattern = "lsat7_2002*"))
</source>

=== Reading in data from GRASS ===

==== Example 1 ====

Read in two GRASS raster maps (the maps "geology_30m" and "elevation" from the North Carolina sample data location) into the R current session as a new object "ncdata" (containing then two SpatialGridDataFrames as well as metadata):
<source lang="rsplus">
# the cat parameter indicates which raster values to be returned as factors
# - geology_30m is a categorical map (i.e., it comes with classes)
# - elevation is a continuous surface
ncdata <- readRAST(c("geology_30m", "elevation"), cat=c(TRUE, FALSE))
</source>
(A warning may appear since in the "geology_30m" map two labels are not unique - as found in the original data.)

We can verify the new R object:
<source lang="rsplus">
str(ncdata)
Formal class 'SpatialGridDataFrame' [package "sp"] with 4 slots
..@ data :'data.frame': 16616 obs. of 2 variables:
</source>

and also check the data structure in more detail:
<source lang="rsplus">
str(ncdata@data)
'data.frame': 16616 obs. of 2 variables:
$ geology_30m: Factor w/ 12 levels "CZfg_217","CZlg_262",..: NA NA NA NA NA NA NA NA NA NA ...
$ elevation : num NA NA NA NA NA NA NA NA NA NA ...
</source>

The metadata are now accessed and available, but are not (yet) used to structure the ''sp'' class objects, in this case a SpatialGridDataFrame object filled with data from two North Carolina layers. Here is a plot of the elevation data:
<source lang="rsplus">
image(ncdata, "elevation", col = terrain.colors(20))
</source>

Add a title to the plot:
<source lang="rsplus">
title("North Carolina elevation")
</source>

[[Image:ncdata.png|center]]

In addition, we can show what is going on inside the objects read into R:
<source lang="rsplus">
str(G)
List of 26
$ DEBUG : chr "0"
$ LOCATION_NAME: chr "nc_spm_08_grass7"
$ GISDBASE : chr "/home/veroandreo/grassdata"
$ MAPSET : chr "PERMANENT"
$ GUI : chr "wxpython"
$ projection : chr "99"
$ zone : chr "0"
$ n : num 228500
$ s : num 215000
$ w : num 630000
$ e : num 645000
$ t : num 1
$ b : num 0
$ nsres : num 27.5
$ nsres3 : num 10
$ ewres : num 37.5
$ ewres3 : num 10
$ tbres : num 1
$ rows : int 491
$ rows3 : int 1350
$ cols : int 400
$ cols3 : int 1500
$ depths : int 1
$ cells : chr "196400"
$ cells3 : chr "2025000"
$ proj4 : chr "+proj=lcc +lat_1=36.16666666666666 +lat_2=34.33333333333334 +lat_0=33.75 +lon_0=-79 +x_0=609601.22 +y_0=0 +no_defs +a=6378137 +"| __truncated__
- attr(*, "class")= chr "gmeta"

summary(ncdata)
Object of class SpatialGridDataFrame
Coordinates:
min max
[1,] 630000 645000
[2,] 215000 228500
Is projected: TRUE
proj4string :
[+proj=lcc +lat_1=36.16666666666666 +lat_2=34.33333333333334
+lat_0=33.75 +lon_0=-79 +x_0=609601.22 +y_0=0 +no_defs +a=6378137
+rf=298.257222101 +towgs84=0.000,0.000,0.000 +to_meter=1]
Grid attributes:
cellcentre.offset cellsize cells.dim
1 630018.8 37.50000 400
2 215013.7 27.49491 491
Data attributes:
geology_30m elevation
CZfg_217:70381 Min. : 55.92
CZig_270:66861 1st Qu.: 94.78
CZbg_405:24561 Median :108.88
CZlg_262:19287 Mean :110.38
CZam_862: 6017 3rd Qu.:126.78
CZbg_910: 4351 Max. :156.25
(Other) : 4942
</source>

==== Example 2 ====

Here an example for a single map transfer from GRASS GIS to R:

<source lang="rsplus">
library(rgrass7)
execGRASS("g.region", raster = "elevation", flags = "p")
ncdata <- readRAST("elevation", cat=FALSE)
summary(ncdata)
spplot(ncdata, col = terrain.colors(20))
</source>

=== Summarizing data ===

We can create a table of cell counts:
<source lang="rsplus">
table(ncdata$geology_30m)
</source>
{| class="wikitable" border="1"
!CZfg_217
!CZlg_262
!CZig_270
!CZbg_405
!CZve_583
!CZam_720
!CZg_766
!CZam_862
!CZbg_910
!Km_921
!CZbg_945
!CZam_946
!CZam_948
|-
|70381
|19287
|66861
|24561
|2089
|467
|691
|6017
|4351
|1211
|1
|398
|85
|}

And compare with the equivalent GRASS module:
<source lang="rsplus">
execGRASS("r.stats", flags=c("c", "l"), parameters=list(input="geology_30m"), ignore.stderr=TRUE)
</source>
<pre>
217 CZfg 70381
262 CZlg 19287
270 CZig 66861
405 CZbg 24561
583 CZve 2089
720 CZam 467
766 CZg 691
862 CZam 6017
910 CZbg 4351
921 Km 1211
945 CZbg 1
946 CZam 398
948 CZam 85
</pre>

Create a box plot of geologic types at different elevations:
<source lang="rsplus">
boxplot(ncdata$elevation ~ ncdata$geology_30m, medlwd = 1)
</source>

[[Image:boxplot_geo.png|center]]

=== Querying maps ===

Sometimes you may want to query GRASS GIS maps from your R session.

As an example, here the transfer of raster pixel values at the position of vector points:

<source lang="rsplus">
# set the computational region first to the raster map:
execGRASS("g.region", raster = "elev_state_500m", flags = "p")

# query raster map at vector points, transfer result into R
goutput <- execGRASS("r.what", map="elev_state_500m", points="geodetic_pts", separator=",", intern=TRUE)
str(goutput)
chr [1:29939] "571530.81289275,265739.968425953,,187.8082200648" ...

# parse it
con <- textConnection(goutput)
go1 <- read.csv(con, header=FALSE)
str(go1)
'data.frame': 29939 obs. of 4 variables:
$ V1: num 571531 571359 571976 572391 573011 ...
$ V2: num 265740 265987 267049 267513 269615 ...
$ V3: logi NA NA NA NA NA NA ...
$ V4: Factor w/ 22738 levels "-0.0048115728",..: 6859 6642 6749 6411 6356 6904 7506 7224 6908 7167 ...
summary(go1)
V1 V2 V3 V4
Min. :121862 Min. : 7991 Mode:logical 0 : 723
1st Qu.:462706 1st Qu.:162508 NA's:29939 * : 293
Median :610328 Median :204502 0.3048 : 47
Mean :588514 Mean :200038 0.6096 : 44
3rd Qu.:717610 3rd Qu.:247633 1.524 : 42
Max. :946743 Max. :327186 0.9144 : 23
(Other):28767
</source>

=== Exporting data back to GRASS ===

Finally, a SpatialGridDataFrame object is written back to a GRASS raster map:

First prepare some data: (square root of elevation)
<source lang="rsplus">
ncdata$sqdem <- sqrt(ncdata$elevation)
</source>

Export data from ''R'' back into a GRASS raster map:
<source lang="rsplus">
writeRAST(ncdata, "sqdemNC", zcol="sqdem", ignore.stderr=TRUE)
</source>

Check that it imported into GRASS ok:
<source lang="rsplus">
execGRASS("r.info", parameters=list(map="sqdemNC"))
</source>

<pre>
+----------------------------------------------------------------------------+
| Map: sqdemNC Date: Sun Jul 19 13:06:34 2015 |
| Mapset: PERMANENT Login of Creator: veroandreo |
| Location: nc_spm_08_grass7 |
| DataBase: /home/veroandreo/grassdata |
| Title: ( sqdemNC ) |
| Timestamp: none |
|----------------------------------------------------------------------------|
| |
| Type of Map: raster Number of Categories: 0 |
| Data Type: DCELL |
| Rows: 491 |
| Columns: 400 |
| Total Cells: 196400 |
| Projection: Lambert Conformal Conic |
| N: 228500 S: 215000.0002 Res: 27.49490794 |
| E: 645000 W: 630000 Res: 37.5 |
| Range of data: min = 7.47818253045085 max = 12.5000787351036 |
| |
| Data Description: |
| generated by r.in.bin |
| |
| Comments: |
| |
+----------------------------------------------------------------------------+
</pre>

=== Using RStudio in a GRASS GIS session ===

If you are most used to run R through RStudio, but still want to have all GRASS data available for performing
any analyses without loosing the possibility of still using GRASS command line, you can run:

<source lang="bash">
GRASS> rstudio &
</source>

or, if you already are working on a certain RStudio project:

<source lang="bash">
GRASS> rstudio /path/to/project/folder/ &
</source>

Then, you load rgrass7 library in your RStudio project
<source lang="rsplus">
library(rgrass7)
</source>

and you are ready to go.

[[File:Grass7_rstudio.png|thumb|500px|center|RStudio used in GRASS GIS 7 session]]

== GRASS within R ==

Using '''GRASS GIS within a R session''', i.e. you connect to a GRASS GIS location/mapset from within R (or RStudio).

=== Startup ===

In the first place, find out the path to the GRASS GIS library. This can be easily done with the following command (still outside of R; or through a system() call inside of R):

<source lang="bash">
# OSGeo4W users:
grass74 --config path

# Linux, Mac OSX users:
grass70 --config path
</source>

It may report something like:
<source lang="bash">
/usr/local/grass-7.0.1
</source>

To call GRASS GIS 7 functionality from R, start R and use the initGRASS() function to define the GRASS settings:

<source lang="rsplus">
## MS-Windows users (example for a OSGeo4W 64bit installation):
library(rgrass7)
# initialisation and the use of North Carolina sample dataset
initGRASS(gisBase = "C:/OSGeo4W64/apps/grass/grass-7.4.1",
gisDbase = "C:/Users/marissa/GRASSdata/",
location = "nc_spm_08_grass7", mapset = "user1", SG="elevation")

## Linux, Mac OSX users:
library(rgrass7)
# initialisation and the use of North Carolina sample dataset
initGRASS(gisBase = "/usr/local/grass-7.0.1", home = tempdir(),
gisDbase = "/home/veroandreo/grassdata/",
location = "nc_spm_08_grass7", mapset = "user1", SG="elevation")
</source>

Note: the optional SG parameter is a 'SpatialGrid' object to define the ‘DEFAULT_WIND’ of the temporary location.

<source lang="rsplus">
# set computational region to default (optional)
system("g.region -dp")
# verify metadata
gmeta()

# get two raster maps into R space
ncdata <- readRAST(c("geology_30m", "elevation"), cat=c(TRUE, FALSE))

# calculate object summaries
summary(ncdata$geology_30m)
CZfg_217 CZlg_262 CZig_270 CZbg_405 CZve_583 CZam_720 CZg_766 CZam_862
292 78 277 102 8 1 2 25
CZbg_910 Km_921 CZam_946 NA's
18 5 2 1009790
</source>

== R in GRASS in batch mode ==

Run the following script with

<source lang="bash">
R CMD BATCH batch.R
</source>

<source lang="rsplus">
library(rgrass7)
# initialisation and the use of north carolina dataset
initGRASS(gisBase = "/home/veroandreo/software/grass-7.0.svn/dist.x86_64-unknown-linux-gnu",
home = tempdir(),
gisDbase = "/home/veroandreo/grassdata/",
location = "nc_spm_08_grass7", mapset = "user1", SG="elevation",
override = TRUE)
# set region to default
system("g.region -dp")
# verify
gmeta()
# read data into R
ncdata <- readRAST(c("geology_30m", "elevation"), cat=c(TRUE, FALSE))
# summary of geology map
summary(ncdata$geology_30m)
proc.time()
</source>

The result is (shorted here):
<source lang="bash">
cat batch.Rout
</source>

<source lang="rsplus">
R version 3.2.1 (2015-06-18) -- "World-Famous Astronaut"
Copyright (C) 2015 The R Foundation for Statistical Computing
Platform: x86_64-redhat-linux-gnu (64-bit)
...
> library(rgrass7)
Loading required package: sp
Loading required package: XML
GRASS GIS interface loaded with GRASS version: (GRASS not running)
> # initialisation and the use of north carolina dataset
> initGRASS(gisBase = "/home/veroandreo/software/grass-7.0.svn/dist.x86_64-unknown-linux-gnu", home = tempdir(),
+ gisDbase = "/home/veroandreo/grassdata/",
+ location = "nc_spm_08_grass7", mapset = "user1", SG="elevation",
+ override = TRUE)
gisdbase /home/veroandreo/grassdata/
location nc_spm_08_grass7
mapset user1
rows 620
columns 1630
north 320000
south 10000
west 120000
east 935000
nsres 500
ewres 500
projection +proj=lcc +lat_1=36.16666666666666 +lat_2=34.33333333333334
+lat_0=33.75 +lon_0=-79 +x_0=609601.22 +y_0=0 +no_defs +a=6378137
+rf=298.257222101 +towgs84=0.000,0.000,0.000 +to_meter=1

> system("g.region -dp")
projection: 99 (Lambert Conformal Conic)
zone: 0
datum: nad83
ellipsoid: a=6378137 es=0.006694380022900787
north: 320000
south: 10000
west: 120000
east: 935000
nsres: 500
ewres: 500
rows: 620
cols: 1630
cells: 1010600
> gmeta()
gisdbase /home/veroandreo/grassdata/
location nc_spm_08_grass7
mapset user1
rows 620
columns 1630
north 320000
south 10000
...
> ncdata <- readRAST(c("geology_30m", "elevation"), cat=c(TRUE, FALSE))
...
> summary(ncdata$geology_30m)
CZfg_217 CZlg_262 CZig_270 CZbg_405 CZve_583 CZam_720 CZg_766 CZam_862
292 78 277 102 8 1 2 25
CZbg_910 Km_921 CZam_946 NA's
18 5 2 1009790
> proc.time()
user system elapsed
8.061 2.016 10.048
</source>

== Troubleshooting ==

=== Running out of disk space ===

Linux: A common issue is that /tmp/ is used for temporary files albeit being often a small partition. To change that to a larger directory, you may add to your <tt>$HOME/.bashrc</tt> the entry:

<source lang="bash">
# change TMP directory of R (note: of course also another directory than suggested here is fine)
mkdir -p $HOME/tmp
export TMP=$HOME/tmp
</source>

The drawback is that on modern Linux systems the /tmp/ is a fast RAM disk (based on tempfs) while HOME directories are often on slower spinning disks (unless you have a SSD drive). At least you no longer run out of disk space easily.

[[Category:FAQ]]
[[Category:Linking to other languages]]
[[Category:R]]
[[Category:Statistics]]

R statistics/rgrass

2018-09-23T20:32:05Z

WinGRASS errors

2018-02-17T23:01:11Z

⚠️Hellik: /* GRASS GIS installation (OSGeo4W or standalone) fails with a sqlite3 error */

Due to the varieties of MS-Windows versions existing, a series of problems with the [[WinGRASS Installation]] have been identified (and solved):

== The GRASS GIS exits when started with g.list CalledModuleError and -1073741511 return code ==

If GRASS GIS graphical user interface fails to start with error which ends like this:

grass.exceptions.CalledModuleError: Module run None ['g.list', '--q', '-m', 'type=raster'] ended with error
Process ended with non-zero return code -1073741511. See errors in the (error) output.

you can try to run the following command manually from the command line (the "black" system command line which was started with GRASS GIS).

g.list -m type=raster

If you run the command, you might get the following error:

The procedure entry point sqlite3_vfs_register could not be located in the dynamic link library sqlite3.dll.

The issue is caused by different <tt>sqlite3.dll</tt> files accessible "on path" to all application. In case of GRASS GIS, some incompatible sqlite3 DLL is picked up by the system rather than using the correct one shipped with GRASS GIS.

Solution: search for all <tt>sqlite3.dll</tt> files on your computer and <strike>remove</strike> rename them one by one while trying at the same time to start GRASS GIS successfully. Note that removing some of the other <tt>sqlite3.dll</tt> files may break the applications which use them (say, while this is possible it has never actually been reported by any user). So, it is a good idea to just rename the DLL file in case you discover that another application needs that particular sqlite3 DLL and you have to reverse the process.

== Legend and scale bar do not show any text ==
If you add legend (<tt>d.legend</tt>) or scale bar (<tt>d.barscale</tt>) to the Map Display and you see only the colors or the bar but no text:

1. Try to run this command within a GRASS session:
g.mkfontcap -o

Redraw, the text should appear.

2. Alternatively, in the menu go to ''Settings'' > ''Preferences'', then select ''Map Display'' tab. Use ''Set font'' button to set ''Default font for GRASS displays''. From the list choose <tt>arial</tt> or another font you wish to use.

== The GRASS GIS (winGRASS) exits immediately after I start it complaining about MSVCR DLL ==

'''''Problem: WinGRASS complains about a missing MSVCR71.dll, MSCVP100.dll or similar on startup or exits immediately.'''''

First note that GRASS GIS 6.4.3 and later '''suggest to install the needed "Important Microsoft runtime libraries" already during the installation process'' (on the same install wizard page offering to download sample datasets), so you should make sure that you check this option during installation. If you are sure about that or the step ended with error (e.g. when proxy settings were not recognized), follow the instructions below.

=== Solution A ===

You may need to install Microsoft's .NET Framework. You can [http://msdn.microsoft.com/en-us/netframework/aa569263 download it here].

If it still asks for MSVCP100.dll, [http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=5555 download it here].

=== Solution B ===

If the above ''Solution A'' does not help, or ends with an error, or if it says that you already have everything, you can reproduce steps which the installer is doing:
# You do not need to uninstall GRASS GIS to fix it. But be sure to close any GRASS windows you have still open.
# Download [http://download.osgeo.org/osgeo4w/x86/release/msvcrt/msvcrt-1.0.1-12.tar.bz2 msvcrt-1.0.1-12.tar.bz2 archive]
# Uncompress the archive. Note that it is <tt>tar.bz2</tt>, so to uncompress it use [http://www.7-zip.org 7-Zip] or Winzip or something else that can handle it. It will unzip 3 folders. Keep those 3 folders together (it doesn't matter where).
# Open the "bin" folder (it is in one of the 3 folders from above) and run the following programs (just double click on them) in the indicated order, following the directions in each wizard:
#* <tt>vcredist_2005_x86.exe</tt> (first screen might be in German, just click left button ("Ja"); then it switches to English)
#* <tt>vcredist_2008_x86.exe</tt>
#* <tt>vcredist_2010_x86.exe</tt>
# Once you installed each of these programs, copy the following files (they are in the same "bin" folder) to the <tt>"extrabin"</tt> folder in the GRASS GIS installation directory (the one you chose during the installation):
#* <tt>msvcp60.dll, msvcp70.dll, msvcp71.dll, msvcr71.dll, msvcrt.dll</tt> So: paste them into e.g. <tt>C:\Program Files (x86)\GRASS GIS 7.0.0beta3\extrabin\</tt> (assuming you used the default install location).
# Try GRASS GIS again! It should be running now. If not make sure that you have tried all the steps and try again. If this still does not help, please write to the [http://lists.osgeo.org/pipermail/grass-user/ grass-user] mailing list.

== Error message "ImportError: cannot import name MAXREPEAT" ==

A system-wide Python installation (2.7.2, independent of GRASS) may cause the trouble. Replacing this system-wide Python installation with version 2.7.4 (or newer 2.7.x), instead of 2.7.2, solves the problem.

A variant of the problem is also seen with "import re" appearing in the error message. The solution is the same: upgrade the system-wide installed version.

Note that you can also try to remove the system-wide installation but this has a higher risk of breaking some (part) other applciation which depends on the system-wide Python.

== Error message "The ordinal 63 could not be located in the dynamic link libexpat.dll." ==

You have likely an old "libexpat.dll" in your directory %WINDIR%\system32 (or %WINDIR%\sysWOW64). Try to rename that file (or delete after backup). Then winGRASS should work.

== Error message "The ordinal 32 could not be located in the dynamic link library proj.dll." ==

You have likely an old "proj.dll" in your directory %WINDIR%\system32 (or %WINDIR%\sysWOW64). Try to rename that file (or delete after backup). Then winGRASS should work.

== The winGRASS user interface shows up in the wrong language for me! ==

MSys users should be setting the LANG, LC_MESSAGES etc. variables in ~/.bash_profile (etc) if they want it set to a specific locale other than the default locale of the system.

== ''This'' and ''that'' is not functioning in my winGRASS installation! ==

May happen, we are working on it :) Please visit the [http://trac.osgeo.org/grass/wiki/CompileOnWindows#Errata Errata page] and the [[WinGRASS_Current_Status#Known_Issues|WinGRASS Current Status]] page

== Error message "This application has failed to start because libintl3.dll was not found". (or libiconv2.dll and/or regex2.dll) ==

Reinstalling of the "msys" package in the OSGeo4W installer will bring it back.

== Error message "libfreetype-6.dll not installed" (similar wording) ==

You may need to install "libfreetype-6.dll" on your system. For this, launch the OSGeo4W Network Installer > Advanced Install, type freetype in the search box and do the freetype packages installation.

== The startup fails with a GISDBASE not defined error ==

Maybe there is junk in the GRASS session configuration file. To see if this is true and to remove the issue. Rename configuration and a new one will be created next time you run GRASS GIS. Follow these steps:

* Find where <tt>%APPDATA%</tt> directory is; usually it is <tt>C:\Users\<username>\AppData</tt>.
** Note that <tt>%APPDATA%</tt> is a hidden folder
* Find the GRASS session configuration file.
** <tt>%APPDATA%\GRASS6\grassrc6</tt> for GRASS GIS 6
** <tt>%APPDATA%\GRASS7\rc</tt> for GRASS GIS 7
* Rename session configuration file, e.g. to <tt>grassrc6.old</tt> or <tt>rc.old</tt>
* Now restart GRASS GIS and the error should be gone (if it was caused by bad configuration file).

== The startup fails with a IOerror: [Errno 2] No such file or directory : 'nul' ==

'''Q:''' At startup, I get
nul=open <os.devnull, 'w'>
IOerror: [Errno 2] No such file or directory : 'nul'

'''A:''' Apparently, it's possible for the service implementing the null device ('nul' pseudo-file) to be stopped or to malfunction.

The status can be checked via the control panel. Start the Device Manager (Control Panel > Hardware and Sound > Device Manager), select View > Show hidden devices, then under Non-Plug and Play Drivers, there should be an entry for "Null".

The corresponding registry key is
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Null

The Start and Type values should both be 1.

== ERROR: G_realloc: unable to allocate xxx bytes of memory at ... ==

'''Q:''' When processing a large dataset, I get something like

Current region rows: rrrrr, cols: ccccc
ERROR: G_realloc: unable to allocate XXX bytes of memory at ...

'''A:''' In general GRASS GIS 7 is able to manage huge datasets in the multi-GB size. For hints, see [[Large raster data processing]]

== Error message "Process ended with non-zero return code -1073741571" ==

This error message may indicate that the [[Computational region]] region is containing too many pixels.

Background: according to [http://stackoverflow.com/a/26311584/452464 StackOverflow] this number "''is the signed integer representation of Microsoft's 'stack overflow/stack exhaustion' error code 0xC00000FD.''"

To verify:
g.region -p

The mount of "cells" main exceed that being manageable by your computer: in case if this error message the number of rows/columns is likely too high. Either reduce the extent or lower the resolution.

== startup of winGRASS and wxGUI very slow/freezed ==

'''Q:''' The startup, location wizzard and wxGUI of winGRASS is very slow, how come?

'''A:''' Some firewall/anti-virus software may be very restrictive regarding new winGRASS version; just update the rules of the firewall/anti-virus software; as all winGRASS release packages are tested for malicious code/virus, they are considered to be secure when originating from the GRASS GIS Web site hosted at OSGeo.

== GRASS GIS installation (OSGeo4W or standalone) fails with a sqlite3 error ==

If the installation fails with an error that an entry point in the sqlite3 dll can't be found, then it is very likely that there is another SQLite library in %PATH% on that windows machine.

First steps are:

* typing in a wondows console: where "$path:sqlite3*"
* search in C:\Windows in the explorer for sqlite3*

Windows operating systems don't install natively a SQLite dll in any directory available in %PATH%.

If one of results of the steps above are positive, another software installed the dll in a directory available in %PATH%.

For a successful installation, following steps should be done:

* rename the found dll (e.g. in C:\Windows\System32\sqlite3.dll) to something like xxxsqlite3.dll
* check if installation of winGRASS (OSGeo4W or standalone) works
* if it works, then the software which installed the dll in %PATH% will be broken
* start other installed software on that machine step by step and see which one is now broken
* if the broken software is found, move xxxsqlite3.dll to the installation directory of that software (e.g. e.g. c:\Programs\YourSoftwareBreakingGrass) and rename it back
to sqlite3.dll

== See also ==

* [[WinGRASS Current Status#Known_Issues|Known Issues in winGRASS]]
* [[MacOSX GRASS errors]]

[[Category: FAQ]]
[[Category: winGRASS]]