GRASS-Wiki - User contributions [en]

Talk:GRASS Community Meeting San Michele 2026

2026-07-16T12:53:22Z

Annakrat: /* July 16 */

{{toc|right}}

Quick links: [[GRASS Community Meeting San Michele 2026|Meeting page]] | [[#Reports|Reports]] | [[GRASS_Community_Meeting_Prague_2024#Sponsors|Sponsors]]

== Organizing Team ==

* Initial planning: Luca Delucchi, Vaclav Petras, Veronica Andreo, Markus Neteler, Anna Petrasova
* Budget: Luca Delucchi, Vaclav Petras, Markus Neteler, Veronica Andreo
* Raising support: Vaclav Petras, Markus Neteler, Veronica Andreo
* Reimbursements:
* Venue: Luca Delucchi
* Meals: Luca Delucchi
* Agenda: Veronica Andreo, Anna Petrasova
* Wiki page: Anna Petrasova, Luca Delucchi, Vaclav Petras
* Virtual participant support:
* Promotion, invitations, and social media: Vaclav Petras, Veronica Andreo
* Photography: Veronica Andreo

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

== Reports ==

Per-person reports from the meeting (one <code>=== Name ===</code> section per participant.)

=== Markus Neteler ===

==== Jul 12 ====
* work on generating an auto-generated GRASS addons index covering all addons found with GitHub topic "[https://github.com/topics/grass-gis-addons grass-gis-addons]"
** part 1: add missing markdown manual files to all addons missing them (addons found on GitHub outside of "grass-addons": currently 71)
** part 2: developing of a script doing the git clone/compilation/manual page generation steps [https://github.com/OSGeo/grass-addons/pull/1782 PR#1782]
*** yet unsubmitted

==== Jul 13 ====
* cleanup of some old stale tickets
* work on SBOM implementation [https://github.com/OSGeo/grass/issues/7215 issue 7215]

==== Jul 14 ====
* work on SBOM implementation [https://github.com/OSGeo/grass/issues/7215 issue 7215]
** Discussed sbom formatting (SPDX vs CycloneDX) and changes that need to made for compliance.
** Draft [https://github.com/OSGeo/grass/pull/7698 PR#7698] (CycloneDX SBOM)
* work on SPDX header cleanup [https://github.com/OSGeo/grass/issues/4190 issue 4190]
** Draft [https://github.com/OSGeo/grass/pull/7716 PR#7716]

==== Jul 15 ====
* continuation of work on SPDX header cleanup, learned a lot about agents
* re-gained ssh access (thanks, strk and Regina!)
** to grass.osgeo.org - fixes for new website deployment method
** to grasswiki.osgeo.org - check for captcha removal

==== Jul 16 ====
* Update [[Sponsors]] to numFOCUS
* fix ssh access to grass.osgeo.org for Corey (new website pages deployment)

=== Veronica Andreo ===

* Review grass-tutorials PRs [https://github.com/OSGeo/grass-tutorials/pull/116 #116], [https://github.com/OSGeo/grass-tutorials/pull/130 130], [https://github.com/OSGeo/grass-tutorials/pull/133 #133],[https://github.com/OSGeo/grass-tutorials/pull/135 #135], [https://github.com/OSGeo/grass-tutorials/pull/136 #136].
* Review grass-website PRs [https://github.com/OSGeo/grass-website/pull/169 169], [https://github.com/OSGeo/grass-website/pull/611 611], [https://github.com/OSGeo/grass-website/pull/613 613], [https://github.com/OSGeo/grass-website/pull/645 645].
* PRs and issues clean-up in tutorials and website.
* Fix conda submenu [https://github.com/OSGeo/grass-website/pull/643 643].
* Participated of the discussion on STDS integration into GUI with Anna and Stefan.
* Assisted Luca with local organization issues.
* Compiled list of voters for upcoming PSC elections in line with PSC criteria defined on [[PSC_Meeting_2024-06-14]].
** Went through grass, grass-addons, grass-promo, grass-website, grass-tutorials, rgrass and got contributors with at least one merged PR during the current and previous PSC mandates, i.e., as far as 2016.
** Check attendants to community meetings in the same period.
** Check contributions to QGIS related to GRASS in the same period.
** Processed all lists and compiled a file with unique names and emails.
* Pictures and social media posting.
* Managed to compile GRASS-dev in WSL.
* Tested [https://github.com/OSGeo/grass/pull/7707 grass#7077].
* Tested and reviewed [https://github.com/OSGeo/grass-addons/pull/641 grass-addons#641], [https://github.com/OSGeo/grass-addons/pull/1005 grass-addons#1005], [https://github.com/OSGeo/grass-addons/pull/1010 grass-addons#1010], [https://github.com/OSGeo/grass-addons/pull/1790 grass-addons#1790].

=== Corey White ===
'''12-07-2026'''

GRASS Website migration to Bootstrap 5 and sass-dart
* Addressing [https://github.com/OSGeo/grass-website/issues/600 Issue #600]
Current state
# [https://github.com/OSGeo/grass-website/pull/599 PR#599 (grass-website)] - Approved (pending PR#635 and PR#1783)
# [https://github.com/OSGeo/grass-website/pull/552 PR#552 (grass-website)] (devcontainer) - Closed (superseded by #599)
# PR B (grass-website)(bootstrap5-migration) - Pushed to fork, not opened. I'll open after #599 merges
# PR C (grass-website) (brand-tokens-single-source) - Pushed to fork, not opened. I'll open after PR B merges
# [https://github.com/OSGeo/grass-website/pull/635 PR#635 (grass-website)] - Build production site in CI and publish it as a release artifact
# [https://github.com/OSGeo/grass-addons/pull/1783 PR#1783 (grass-addons)] - Updates deploy website CRON job from the CI-built release artifact

'''13-07-2026'''
# [https://github.com/OSGeo/grass/pull/3826 PR#3826 (grass) v.ppa] - Split code into smaller lib functions, fix issues with original implementation, and updated tests.
# [https://github.com/OSGeo/grass/pull/7298 Reviewed PR#7298] - grass.script: add create_mapset function
# Got t.stac tutorial reviewed by Vero
# [https://github.com/OSGeo/grass-website/pull/635 PR#635 (grass-website)] - '''(Merged)''' Build production site in CI and publish it as a release artifact
# [https://github.com/OSGeo/grass-website/pull/637 PR#637 (grass-website)] - '''(Merged)''' Fix production build: inline Renovate-managed toolchain versions
# [https://github.com/OSGeo/grass-website/pull/639 PR#637 grass-website)] - '''(Merged)''' Add Renovate's helper preset to pin GitHub Actions to the full length SHA

'''14-07-2026'''
# [https://github.com/OSGeo/grass-website/pull/643 PR#643 (grass-website)] - '''(Reviewed/Merged)''' Menu entries: Use uppercase for Conda submenu
# [https://github.com/OSGeo/grass-addons/pull/1783 PR#1783 (grass-addons)] - '''(Approved)''' Updates deploy website CRON job from the CI-built release artifact
# [https://github.com/OSGeo/grass-website/pull/644 PR#644 (grass-website)] - '''(Approved)''' Migrate markup to Bootstrap 5 and drop jQuery
# [https://github.com/OSGeo/grass-website/pull/645 PR#645 (grass-website)] - '''(In-Review)''' Single-source brand tokens; remove orphaned style.css (issue #600)
# [https://github.com/OSGeo/grass-website/pull/646 PR#645 (grass-website)] - '''(In-Review)''' Split production artifact workflow into build and deploy jobs
# [https://github.com/OSGeo/grass-addons/pull/1641 PR#1641 (grass-addons)] - '''(Merged)''' t.stac: fixed issue with download and import asset potentially overwhelming network.
# [https://github.com/OSGeo/grass/pull/3826 PR#3826 (grass) v.ppa] - '''(In-Review)''' Split code into smaller lib functions, fix issues with original implementation, updated tests, and images to docs
# Discussed sbom formatting (SPDX vs CycloneDX) and changes that need to made for compliance.

'''15-07-2026'''
# [https://github.com/OSGeo/grass-addons/pull/1788 PR#1788 (grass-addons)] - '''(Draft)''' Create new r.soils.rosetta addon.
# [https://github.com/OSGeo/grass-addons/pull/1336 PR#1336 (grass-addons)] - '''(Closed)''' Update python script shebang line to python3
# [https://github.com/OSGeo/grass/pull/7298 PR#7298 (grass)] - '''(Reviewed/Approved)''' grass.script: add create_mapset function
# [https://github.com/OpenPlainsInc/grass-obsidian (grass-obsidian)] - '''(Published)''' Opened up the OpenPlains grass-obsidian plugin that allows you to review your grass project from your obsidian notes.
# [https://github.com/OSGeo/grass-website/pull/646 PR#645 (grass-website)] - '''(Merged)''' Split production artifact workflow into build and deploy jobs
# [https://github.com/OSGeo/grass-website/pull/599 PR#599 (grass-website)] - '''(Merged)''' Hugo dart scss
# [https://github.com/OSGeo/grass-website/pull/644 PR#644 (grass-website)] - '''(Merged)''' Migrate markup to Bootstrap 5 and drop jQuery
# [https://github.com/OSGeo/grass-website/pull/645 PR#645 (grass-website)] - '''(Merged)''' Single-source brand tokens; remove orphaned style.css (issue #600)
# [https://github.com/OSGeo/grass-addons/pull/1783 PR#1783 (grass-addons)] - '''(Merged)''' Updates deploy website CRON job from the CI-built release artifact
# [https://github.com/OSGeo/grass-website/issues/636 Issue#636 (grass-website] - '''(Closed)''' Add zizmor to the checks run
# [https://github.com/OSGeo/grass/pull/7703 PR#7703 (grass)] - '''(Open)''' python: Use argument lists instead of shell=True for subprocess
# [https://github.com/OSGeo/grass/pull/7713 PR#7713 (grass)] - '''(Open)''' checks: Mark justified partial-path subprocess calls as nosec B607
# [https://github.com/OSGeo/grass/pull/7698 PR#7698 (grass)] - '''(Reviewed)'''CI: add CycloneDX SBOM generation for releases
# [https://github.com/OSGeo/grass-website/pull/583 PR#583 (grass-website)] '''(Closed)''' Update brand download dropdowns to Bootstrap 5 namespaced attributes

'''15-07-2026'''
# [https://github.com/OSGeo/grass-website/issues/600 (grass-website)] '''(Closed)''' Migrating to Bootstrap v5 from v3
# Load photos to Google Photos
# [https://github.com/OSGeo/grass-website/pull/169 PR#169 (grass-website)] '''(Review)''' GRASS community map
# [https://github.com/OSGeo/grass-website/pull/659 PR#659 (grass-website)] '''(Open)''' ci: npm security updates
# Got setup with Google Search Console for GRASS to track SEO
# Debugging loss of access to osgeo server.
# [https://github.com/OSGeo/grass-addons/pull/1788 PR#1788 (grass-addons)] - '''(Open)''' Create new r.soils.rosetta addon. Add first implication of r.soils.rosetta and updated r.in.ssurgo to produce the correct raster outputs for clay, sand, and bulk density.
# [https://github.com/OSGeo/grass/pull/7713 PR#7713 (grass)] - '''(Open)''' checks: Mark justified partial-path subprocess calls as nosec B607
# Created osgeo-skills proposal

=== Anna Petrasova ===
==== Jul 12 ====
* Review of [https://github.com/OSGeo/grass/pull/7659 #7659], [https://github.com/OSGeo/grass/pull/7599 #7599]
* Finish v.geometry tool: [https://github.com/OSGeo/grass/pull/7329 #7329]
* Working on markdown to man page conversion to remove old html pages:
** [https://github.com/OSGeo/grass/pull/7540 #7540] - merged
** [https://github.com/OSGeo/grass/pull/7674 #7674]
* Review website [https://github.com/OSGeo/grass-website/pull/599 #599]

==== Jul 13 ====

* Discussion with Vero and Stefan on GSoC project implementation
* Fixed bug in temporal library: [https://github.com/OSGeo/grass/pull/7681 #7681]
* t.info tests [https://github.com/OSGeo/grass/pull/7682 #7682]
* Review Jupyter GUI integration [https://github.com/OSGeo/grass/pull/5901 #5901]
* Discussion between me, Linda, Alen and Vashek about data catalog and regions

==== Jul 14 ====

* Fixing v.class causing flaky test [https://github.com/OSGeo/grass/pull/7692 #7692]
* Call with Saket and Stefan about the GSoC project
* Review [https://github.com/OSGeo/grass/pull/7608 #7608], [https://github.com/OSGeo/grass/pull/5901 #5901]
* Adding new icons for #7608.
* Cmake fixes [https://github.com/OSGeo/grass/pull/7720 #7720]

==== July 15 ====
* temporal fixes [https://github.com/OSGeo/grass/pull/7717 #7717]
* over 10 PRs reviewed
* fix temporal with 3.14 [https://github.com/OSGeo/grass/pull/7724 #7724]

==== July 16 ====
* review 7599, 7444
* reviewing GSoC r.param.scale and r.proj PRs
* fixing v.proj bug
* load C libraries in a notebook [https://github.com/OSGeo/grass/pull/7733 #7733]

=== Edouard Choinière ===
==== 2026-07-11 ====
* Discussion with Corey White on trying to build docs with Zensical, and dropping Sphinx for [https://zensical.org/docs/setup/extensions/mkdocstrings/ mkdocstrings]
* Discussion with Vaclav Petras on Windows builds and Fable:
** The nsis installer had a change to do (as debugged last year by me in [https://github.com/OSGeo/grass/issues/5663 #5663]), but we don't know how to do it well. We suggested to let Anthropic's Fable try to do it before it stopped being included in the Claude subscription.
** For us to try out the fixed nsis installer script, Fable should be able to create the installer in CI. It is being tried in [https://github.com/echoix/grass/pull/664 echoix#664]/[https://github.com/wenzeslaus/grass/pull/12 wenzeslaus#12]
** Also suggested to use Fable to attempt to solve issues in a pending Sphinx PR that we were stuck for too long, (Stcuk PR: [https://github.com/OSGeo/grass/pull/7526 #7526], result: [https://github.com/wenzeslaus/grass/pull/11 wenzeslaus#11])
==== 2026-07-12 ====
* Got PRs merged: [https://github.com/OSGeo/grass/pull/7660 #7660], [https://github.com/OSGeo/grass/pull/7659 #7659],
* Created follow-up PR for sscanf: [https://github.com/OSGeo/grass/pull/7673 #7673]
* Discussed with Stefan Blumentrath:
** temporal init, choice of his PR or another contributor
** Discussed AI findings on various files accumulated in the last weeks: most are valid and should be filed.
* Reviewed PRs: [https://github.com/OSGeo/grass-addons/pull/641 grass-addons#641], [https://github.com/OSGeo/grass/pull/7635 #7635], [https://github.com/OSGeo/grass/pull/7671 #7671], [https://github.com/OSGeo/grass/pull/7669 #7669]
* Video call on FHS
* First review of Fable windows installer in CI on [https://github.com/echoix/grass/pull/664 echoix#664]

==== 2026-07-13 ====
* Reviewed PRs: [https://github.com/OSGeo/grass/pull/7663 #7663], [https://github.com/OSGeo/grass-website/pull/635 grass-website#635], [https://github.com/OSGeo/grass/pull/7337 #7337], [https://github.com/OSGeo/grass/pull/7672 #7672], [https://github.com/OSGeo/grass/pull/7684 #7684], [https://github.com/OSGeo/grass/pull/7687 #7687]
* Worked on the last sscanf CodeQL alert, for [https://github.com/OSGeo/grass/pull/7673 #7673]
* Tested out windows standalone installer built in CI [https://github.com/echoix/grass/pull/664 echoix#664]. Almost works, as it installs, but it doesn't start because of a path error. Wrote some notes about windows compilation in CI in relation to addons in Vashek's google doc.
* Wrote notes on the windows build script having two versions, where OSGeo4W uses a different one than the one we use in CI for our tests, and they diverged
* Submitted PR of AI findings for tests of g.md2man [https://github.com/OSGeo/grass/pull/7679 #7679]
* Configured CI required checks to not wait for successful checks during the code sprint, with the new rights given to me. Discussed with Vashek on what approach we'd want for the 4 ubuntu job configurations.
** Commented on an issue closed today [https://github.com/OSGeo/grass/issues/1313 #1313] about cppcheck: cppcheck could be useful to cover a bit more configuration combinations, but as discussed, only being to compile would only get us so far without testing.
* Discussion with Vashek on AI policy and approach to use with AI, low-quality contributors; Approach on renovate updates; Wishes on release cadence
* Multiple reviews and pair brainstorming on grass-website with Corey White, including [https://github.com/OSGeo/grass-website/pull/635 grass-website#635], [https://github.com/OSGeo/grass-website/pull/637 grass-website#637], [https://github.com/OSGeo/grass-website/pull/639 grass-website#639], [https://github.com/OSGeo/grass-website/pull/634 grass-website#634], [https://github.com/OSGeo/grass-website/pull/640 grass-website#640]
* Worked on CMake formatting, moving forward the PR a contributor opened for Gersemi, PR [https://github.com/OSGeo/grass/pull/7663 #7663], discussed weird finding with Vashek, lead to issue [https://github.com/OSGeo/grass/issues/7686 #7686]. To be continued the next day.
* Opened PR [https://github.com/OSGeo/grass/pull/7685 #7685] (merged), [https://github.com/OSGeo/grass/pull/7683 #7683] (needs more work/investigation), [https://github.com/OSGeo/grass/pull/7680 #7680] (merged)
* Opened issue to add zizmor to grass-website tools used to check, either local or CI [https://github.com/OSGeo/grass-website/issues/636 grass-website#636]

==== 2026-07-14 ====
* (Early night) Merge PR that updates minimum Python version to 3.11, needed to change the required checks in order to do so. [https://github.com/OSGeo/grass/pull/7684 #7684].
** In the morning, update PRs which were most probably ready, and needed the check passing, like [https://github.com/OSGeo/grass/pull/7329 #7329], [https://github.com/OSGeo/grass/pull/7635 #7635], [https://github.com/OSGeo/grass/pull/7687 #7687]
* Review and/or merge [https://github.com/OSGeo/grass-website/pull/642 grass-website#642], [https://github.com/OSGeo/grass/pull/7674 #7674], [https://github.com/OSGeo/grass/pull/7689 #7689], [https://github.com/OSGeo/grass/pull/7688 #7688], [https://github.com/OSGeo/grass/pull/7690 #7690], [https://github.com/OSGeo/grass/pull/7699 #7699], [https://github.com/OSGeo/grass/pull/7697 #7697], [https://github.com/OSGeo/grass/pull/7713 #7713], [https://github.com/OSGeo/grass/pull/7702 #7702], [https://github.com/OSGeo/grass/pull/7678 #7678], [https://github.com/OSGeo/grass-addons/pull/1786 grass-addons#1786]
* Long review and analysis of [https://github.com/OSGeo/grass-website/pull/646 grass-website#646], coming from a discussion earlier on that using a single workflow to build, but split the deploy part in order to run separately.
* Work on CMake formatting tool: Finally ended up replacing [https://github.com/OSGeo/grass/pull/7663 #7663] with [https://github.com/OSGeo/grass/pull/7696 #7696]. Will close issue [https://github.com/OSGeo/grass/issues/7346 #7346] and [https://github.com/OSGeo/grass/issues/7686 #7686]. Opened issues with the tool's repo [https://github.com/BlankSpruce/gersemi/issues/123], [https://github.com/BlankSpruce/gersemi/issues/124], and [https://github.com/BlankSpruce/gersemi/issues/122] (the previous day).
* Help Stefan Blumentrath's son get started with finding simple ruff rules to fix.
* Work with Antonio Galea on making windows standalone installer + addons work without the old server. The installer now works. [https://github.com/echoix/grass/pull/664 echoix#664]
* Reviewing PR by navigating types in dynamic gui code [https://github.com/OSGeo/grass/pull/7693 #7693]
* More precise discussion with team on what renovate grouping strategy to use.
* Discussion with Vashek on python version support policy.
* Created PR [https://github.com/OSGeo/grass/pull/7718 #7718] (merged)

==== 2026-07-15 ====
* Merged [https://github.com/OSGeo/grass/pull/7699 #7699]
* Review issue [https://github.com/OSGeo/grass/issues/7646 #7646]
* Created PR [https://github.com/OSGeo/grass/pull/7722 #7722] (merged), [https://github.com/OSGeo/grass/pull/7723 #7723]
* Review PR [https://github.com/OSGeo/grass/pull/7687 #7687], [https://github.com/OSGeo/grass-website/pull/646 grass-website#646], [https://github.com/OSGeo/grass-addons/pull/1769 grass-addons#1769], [https://github.com/OSGeo/grass-addons/pull/1785 grass-addons#1785], [https://github.com/OSGeo/grass/pull/7676 #7676], [https://github.com/OSGeo/grass-website/pull/645 grass-website#645], [https://github.com/OSGeo/grass/pull/5656 #5656], [https://github.com/OSGeo/grass-addons/pull/1791 grass-addons#1791]
* Try to get [https://github.com/OSGeo/grass/pull/7635 #7635] merged (update after other PR fixed test).
* Finished editing [https://github.com/OSGeo/grass/pull/7693 #7693]
* Worked again on CMake formatting, creating stubs for unrecognized functions [https://github.com/OSGeo/grass/pull/7696 #7696]
* Create draft rulesets for the grass-website repo.
* Debugged [https://github.com/OSGeo/grass/pull/7683 #7683] for codecov to work on macOS runners configured to build grass
* Discussion with Anna on the viability of MkDocs, alternatives, and how the attempt on using Zensical turned out. Zensical is missing at least tag listing pages.

==== 2026-07-16 ====
* Applied the fixes for [https://github.com/OSGeo/grass/pull/7683 #7683] to work.

=== Vaclav Petras ===

==== 2026-07-12 ====

* Reviews and discussion on FHS (video call, [https://github.com/OSGeo/grass/pull/5630 5630], [https://github.com/wenzeslaus/grass/pull/10 my fork PR 10])
* Test reviews: [https://github.com/OSGeo/grass/pull/7675 #7675]
* Windows distribution reviews: [https://github.com/OSGeo/grass/issues/5663 #5663]
* Sphinx reviews: [https://github.com/OSGeo/grass/pull/7526 #7526]
* RegionManager discussion ([https://github.com/OSGeo/grass/pull/7599 7599])
* Parson allocation review: [https://github.com/OSGeo/grass/pull/7208 7208]

==== 2026-07-13 ====

* Reduce Sphinx warnings

==== 2026-07-14 ====

* Update RFC for updating Python versions which also sets up precedence for RFC amendments.
* Review v.class undefined behavior PR
* Reduce Sphinx warnings
* Port old in-package grass.pygrass unit tests to pytest

=== Stefan Blumentrath ===
==== 2026-07-12 ====
Opened PRs: [https://github.com/OSGeo/grass/pull/7672 #7672]

Reviewed: [https://github.com/OSGeo/grass/pull/7670 #7670], [https://github.com/OSGeo/grass/pull/7671 #7671]

Closed PRs: [https://github.com/OSGeo/grass/pull/7644 #7644]

==== 2026-07-13 ====

Discussed options for handling STDS in the GUI

Opened PRs: [https://github.com/OSGeo/grass/pull/7678 #7678]

Reviewed PRs: [https://github.com/OSGeo/grass/pull/7670 #7670]

Merged PRs: [https://github.com/OSGeo/grass/pull/7672 #7672]

Closed PRs: [https://github.com/OSGeo/grass/pull/7671 #7671]

==== 2026-07-14 ====

Opened PRs: [https://github.com/OSGeo/grass/pull/7707 #7707]

Reviewed PRs: [https://github.com/OSGeo/grass/pull/7670 #7670]

==== 2026-07-15 ====

Reviewed PRs: [https://github.com/OSGeo/grass/pull/7682 #7682], [https://github.com/OSGeo/grass/pull/7714 #7714], [https://github.com/OSGeo/grass/pull/7670 #7670]

Closed PRs: [https://github.com/OSGeo/grass/pull/7707 #7707]

==== 2026-07-16 ====

Closed PRs: [https://github.com/OSGeo/grass/pull/7693 #7693]

Reviewed PRs: [https://github.com/OSGeo/grass/pull/7693 #7693],[https://github.com/OSGeo/grass/pull/7731 #7731], [https://github.com/OSGeo/grass/pull/7732 #7732], [https://github.com/OSGeo/grass/pull/2448 #2448]

=== Luca Delucchi ===

* All the local organizing (Thank you, Luca!)

==== Website ====

* [https://github.com/OSGeo/grass-website/pull/169 Community map]

==== Addons ====
* [https://github.com/OSGeo/grass-addons/pull/1010/ t.rast.aggregate.seasons] new addon
* [https://github.com/OSGeo/grass-addons/pull/1005 t.rast.climatologies] new addon
* [https://github.com/OSGeo/grass-addons/pull/641 t.rast.vi] new addon
* [https://github.com/OSGeo/grass-addons/pull/1695 r.learn.predict] fix map history

=== Antonio Galea ===

==== Jul 14 ====
* support with the development of the (broken) winGRASS server replacement with a GitHub actions based Windows installer in CI on [https://github.com/echoix/grass/pull/664 echoix#664]

=== Tomaž Žagar ===
==== 2026-07-14 ====

* i.hyper addon: enhancement/bugfix when importing EnMAP example data: https://github.com/mazingaro/grass-addons/issues/12
* i,hyper addon: fixed radiance import: https://github.com/mazingaro/grass-addons/issues/16
* started to work on: https://github.com/mazingaro/grass-addons/issues/6

==== 2026-07-15 ====
* Continued to work on: https://github.com/mazingaro/grass-addons/issues/6
** first implemented it as Python addon - then switched to C addon as proposed for "better" integration (compilation when installing addon with g.extension) with https://github.com/YannChemin/libsixsv
** included https://github.com/YannChemin/i.hyper.atcorr to https://github.com/mazingaro/grass-addons/tree/i.hyper/src/imagery/i.hyper/i.hyper.atcorr
** added i.hyper.history handling to https://github.com/mazingaro/grass-addons/commit/97957ebf7723a2866a13926ded57d104a546036a
** testing and wondering

=== Matjaž Krebs ===
==== 2026-07-13 ====
* i.hyper addon: Started working on new importer module for emit data
==== 2026-07-14 ====
* i.hyper addon: working on importer module for emit data. Implementing and troubleshooting.
* i.hyper addon: working on i.hyper.export bug for exporting 3D raster cube from WGS 4326

=== Alen Mangafić ===
==== 2026-07-14 ====

* i.hyper addon: improved EnMAP import handling and related bugfixes: https://github.com/mazingaro/grass-addons/commit/0a30d9505, https://github.com/mazingaro/grass-addons/commit/36bf3e686
* i.hyper addon: improved metadata copying/validation and fixed i.hyper.preproc import behavior: https://github.com/mazingaro/grass-addons/commit/d4313f162, https://github.com/mazingaro/grass-addons/commit/a52012289, https://github.com/mazingaro/grass-addons/commit/ce6cdd25d, https://github.com/mazingaro/grass-addons/commit/6d994e853
* i.hyper addon: implemented spectral resampling and merged it into i.hyper: https://github.com/mazingaro/grass-addons/commit/38a8e073b, https://github.com/mazingaro/grass-addons/commit/c992bc90f
* helped Matjaž Krebs to survive the day
==== 2026-07-15 ====

* SPDX License AI monkey business TBA

=== Christian Braun ===

* grass: [https://github.com/OSGeo/grass/pull/7725 grass #7725] — wxGUI: fixed orphaned drag image windows when dragging layers in the layer tree on macOS, and addressed the review comments on the TOC drag fix.
* grass-addons: added [https://docs.pytest.org pytest] test coverage and small fixes to several addons:
** [https://github.com/OSGeo/grass-addons/pull/1784 grass-addons #1784] — ''r.clip'': added a pytest test suite (merged).
** [https://github.com/OSGeo/grass-addons/pull/1786 grass-addons #1786] — ''r.centroids'': added a pytest test suite (merged).
** [https://github.com/OSGeo/grass-addons/pull/1787 grass-addons #1787] — ''v.median'': fixed the stdout output and added a pytest test suite.
* actinia: discussed with Markus about a GeoNode-Addon to connect actinia as a processing backend. First architecting and design work has been done.

Talk:GRASS Community Meeting San Michele 2026

2026-07-16T11:56:18Z

Annakrat: /* July 16 */

{{toc|right}}

Quick links: [[GRASS Community Meeting San Michele 2026|Meeting page]] | [[#Reports|Reports]] | [[GRASS_Community_Meeting_Prague_2024#Sponsors|Sponsors]]

== Organizing Team ==

* Initial planning: Luca Delucchi, Vaclav Petras, Veronica Andreo, Markus Neteler, Anna Petrasova
* Budget: Luca Delucchi, Vaclav Petras, Markus Neteler, Veronica Andreo
* Raising support: Vaclav Petras, Markus Neteler, Veronica Andreo
* Reimbursements:
* Venue: Luca Delucchi
* Meals: Luca Delucchi
* Agenda: Veronica Andreo, Anna Petrasova
* Wiki page: Anna Petrasova, Luca Delucchi, Vaclav Petras
* Virtual participant support:
* Promotion, invitations, and social media: Vaclav Petras, Veronica Andreo
* Photography: Veronica Andreo

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

== Reports ==

Per-person reports from the meeting (one <code>=== Name ===</code> section per participant.)

=== Markus Neteler ===

==== Jul 12 ====
* work on generating an auto-generated GRASS addons index covering all addons found with GitHub topic "[https://github.com/topics/grass-gis-addons grass-gis-addons]"
** part 1: add missing markdown manual files to all addons missing them (addons found on GitHub outside of "grass-addons": currently 71)
** part 2: developing of a script doing the git clone/compilation/manual page generation steps [https://github.com/OSGeo/grass-addons/pull/1782 PR#1782]
*** yet unsubmitted

==== Jul 13 ====
* cleanup of some old stale tickets
* work on SBOM implementation [https://github.com/OSGeo/grass/issues/7215 issue 7215]

==== Jul 14 ====
* work on SBOM implementation [https://github.com/OSGeo/grass/issues/7215 issue 7215]
** Discussed sbom formatting (SPDX vs CycloneDX) and changes that need to made for compliance.
** Draft [https://github.com/OSGeo/grass/pull/7698 PR#7698] (CycloneDX SBOM)
* work on SPDX header cleanup [https://github.com/OSGeo/grass/issues/4190 issue 4190]
** Draft [https://github.com/OSGeo/grass/pull/7716 PR#7716]

==== Jul 15 ====
* continuation of work on SPDX header cleanup, learned a lot about agents
* re-gained ssh access (thanks, strk and Regina!)
** to grass.osgeo.org - fixes for new website deployment method
** to grasswiki.osgeo.org - check for captcha removal

==== Jul 16 ====
* Update [[Sponsors]] to numFOCUS
* fix ssh access to grass.osgeo.org for Corey (new website pages deployment)

=== Veronica Andreo ===

* Review grass-tutorials PRs [https://github.com/OSGeo/grass-tutorials/pull/116 #116], [https://github.com/OSGeo/grass-tutorials/pull/130 130], [https://github.com/OSGeo/grass-tutorials/pull/133 #133],[https://github.com/OSGeo/grass-tutorials/pull/135 #135], [https://github.com/OSGeo/grass-tutorials/pull/136 #136].
* Review grass-website PRs [https://github.com/OSGeo/grass-website/pull/169 169], [https://github.com/OSGeo/grass-website/pull/611 611], [https://github.com/OSGeo/grass-website/pull/613 613], [https://github.com/OSGeo/grass-website/pull/645 645].
* PRs and issues clean-up in tutorials and website.
* Fix conda submenu [https://github.com/OSGeo/grass-website/pull/643 643].
* Participated of the discussion on STDS integration into GUI with Anna and Stefan.
* Assisted Luca with local organization issues.
* Compiled list of voters for upcoming PSC elections in line with PSC criteria defined on [[PSC_Meeting_2024-06-14]].
** Went through grass, grass-addons, grass-promo, grass-website, grass-tutorials, rgrass and got contributors with at least one merged PR during the current and previous PSC mandates, i.e., as far as 2016.
** Check attendants to community meetings in the same period.
** Check contributions to QGIS related to GRASS in the same period.
** Processed all lists and compiled a file with unique names and emails.
* Pictures and social media posting.
* Managed to compile GRASS-dev in WSL.
* Tested [https://github.com/OSGeo/grass/pull/7707 grass#7077].
* Tested and reviewed [https://github.com/OSGeo/grass-addons/pull/641 grass-addons#641], [https://github.com/OSGeo/grass-addons/pull/1005 grass-addons#1005], [https://github.com/OSGeo/grass-addons/pull/1010 grass-addons#1010].

=== Corey White ===
'''12-07-2026'''

GRASS Website migration to Bootstrap 5 and sass-dart
* Addressing [https://github.com/OSGeo/grass-website/issues/600 Issue #600]
Current state
# [https://github.com/OSGeo/grass-website/pull/599 PR#599 (grass-website)] - Approved (pending PR#635 and PR#1783)
# [https://github.com/OSGeo/grass-website/pull/552 PR#552 (grass-website)] (devcontainer) - Closed (superseded by #599)
# PR B (grass-website)(bootstrap5-migration) - Pushed to fork, not opened. I'll open after #599 merges
# PR C (grass-website) (brand-tokens-single-source) - Pushed to fork, not opened. I'll open after PR B merges
# [https://github.com/OSGeo/grass-website/pull/635 PR#635 (grass-website)] - Build production site in CI and publish it as a release artifact
# [https://github.com/OSGeo/grass-addons/pull/1783 PR#1783 (grass-addons)] - Updates deploy website CRON job from the CI-built release artifact

'''13-07-2026'''
# [https://github.com/OSGeo/grass/pull/3826 PR#3826 (grass) v.ppa] - Split code into smaller lib functions, fix issues with original implementation, and updated tests.
# [https://github.com/OSGeo/grass/pull/7298 Reviewed PR#7298] - grass.script: add create_mapset function
# Got t.stac tutorial reviewed by Vero
# [https://github.com/OSGeo/grass-website/pull/635 PR#635 (grass-website)] - '''(Merged)''' Build production site in CI and publish it as a release artifact
# [https://github.com/OSGeo/grass-website/pull/637 PR#637 (grass-website)] - '''(Merged)''' Fix production build: inline Renovate-managed toolchain versions
# [https://github.com/OSGeo/grass-website/pull/639 PR#637 grass-website)] - '''(Merged)''' Add Renovate's helper preset to pin GitHub Actions to the full length SHA

'''14-07-2026'''
# [https://github.com/OSGeo/grass-website/pull/643 PR#643 (grass-website)] - '''(Reviewed/Merged)''' Menu entries: Use uppercase for Conda submenu
# [https://github.com/OSGeo/grass-addons/pull/1783 PR#1783 (grass-addons)] - '''(Approved)''' Updates deploy website CRON job from the CI-built release artifact
# [https://github.com/OSGeo/grass-website/pull/644 PR#644 (grass-website)] - '''(Approved)''' Migrate markup to Bootstrap 5 and drop jQuery
# [https://github.com/OSGeo/grass-website/pull/645 PR#645 (grass-website)] - '''(In-Review)''' Single-source brand tokens; remove orphaned style.css (issue #600)
# [https://github.com/OSGeo/grass-website/pull/646 PR#645 (grass-website)] - '''(In-Review)''' Split production artifact workflow into build and deploy jobs
# [https://github.com/OSGeo/grass-addons/pull/1641 PR#1641 (grass-addons)] - '''(Merged)''' t.stac: fixed issue with download and import asset potentially overwhelming network.
# [https://github.com/OSGeo/grass/pull/3826 PR#3826 (grass) v.ppa] - '''(In-Review)''' Split code into smaller lib functions, fix issues with original implementation, updated tests, and images to docs
# Discussed sbom formatting (SPDX vs CycloneDX) and changes that need to made for compliance.

'''15-07-2026'''
# [https://github.com/OSGeo/grass-addons/pull/1788 PR#1788 (grass-addons)] - '''(Draft)''' Create new r.soils.rosetta addon.
# [https://github.com/OSGeo/grass-addons/pull/1336 PR#1336 (grass-addons)] - '''(Closed)''' Update python script shebang line to python3
# [https://github.com/OSGeo/grass/pull/7298 PR#7298 (grass)] - '''(Reviewed/Approved)''' grass.script: add create_mapset function
# [https://github.com/OpenPlainsInc/grass-obsidian (grass-obsidian)] - '''(Published)''' Opened up the OpenPlains grass-obsidian plugin that allows you to review your grass project from your obsidian notes.
# [https://github.com/OSGeo/grass-website/pull/646 PR#645 (grass-website)] - '''(Merged)''' Split production artifact workflow into build and deploy jobs
# [https://github.com/OSGeo/grass-website/pull/599 PR#599 (grass-website)] - '''(Merged)''' Hugo dart scss
# [https://github.com/OSGeo/grass-website/pull/644 PR#644 (grass-website)] - '''(Merged)''' Migrate markup to Bootstrap 5 and drop jQuery
# [https://github.com/OSGeo/grass-website/pull/645 PR#645 (grass-website)] - '''(Merged)''' Single-source brand tokens; remove orphaned style.css (issue #600)
# [https://github.com/OSGeo/grass-addons/pull/1783 PR#1783 (grass-addons)] - '''(Merged)''' Updates deploy website CRON job from the CI-built release artifact
# [https://github.com/OSGeo/grass-website/issues/636 Issue#636 (grass-website] - '''(Closed)''' Add zizmor to the checks run
# [https://github.com/OSGeo/grass/pull/7703 PR#7703 (grass)] - '''(Open)''' python: Use argument lists instead of shell=True for subprocess
# [https://github.com/OSGeo/grass/pull/7713 PR#7713 (grass)] - '''(Open)''' checks: Mark justified partial-path subprocess calls as nosec B607
# [https://github.com/OSGeo/grass/pull/7698 PR#7698 (grass)] - '''(Reviewed)'''CI: add CycloneDX SBOM generation for releases
# [https://github.com/OSGeo/grass-website/pull/583 PR#583 (grass-website)] '''(Closed)''' Update brand download dropdowns to Bootstrap 5 namespaced attributes

'''15-07-2026'''
# [https://github.com/OSGeo/grass-website/issues/600 (grass-website)] '''(Closed)''' Migrating to Bootstrap v5 from v3
# Load photos to Google Photos
# [https://github.com/OSGeo/grass-website/pull/169 PR#169 (grass-website)] '''(Review)''' GRASS community map

=== Anna Petrasova ===
==== Jul 12 ====
* Review of [https://github.com/OSGeo/grass/pull/7659 #7659], [https://github.com/OSGeo/grass/pull/7599 #7599]
* Finish v.geometry tool: [https://github.com/OSGeo/grass/pull/7329 #7329]
* Working on markdown to man page conversion to remove old html pages:
** [https://github.com/OSGeo/grass/pull/7540 #7540] - merged
** [https://github.com/OSGeo/grass/pull/7674 #7674]
* Review website [https://github.com/OSGeo/grass-website/pull/599 #599]

==== Jul 13 ====

* Discussion with Vero and Stefan on GSoC project implementation
* Fixed bug in temporal library: [https://github.com/OSGeo/grass/pull/7681 #7681]
* t.info tests [https://github.com/OSGeo/grass/pull/7682 #7682]
* Review Jupyter GUI integration [https://github.com/OSGeo/grass/pull/5901 #5901]
* Discussion between me, Linda, Alen and Vashek about data catalog and regions

==== Jul 14 ====

* Fixing v.class causing flaky test [https://github.com/OSGeo/grass/pull/7692 #7692]
* Call with Saket and Stefan about the GSoC project
* Review [https://github.com/OSGeo/grass/pull/7608 #7608], [https://github.com/OSGeo/grass/pull/5901 #5901]
* Adding new icons for #7608.
* Cmake fixes [https://github.com/OSGeo/grass/pull/7720 #7720]

==== July 15 ====
* temporal fixes [https://github.com/OSGeo/grass/pull/7717 #7717]
* over 10 PRs reviewed
* fix temporal with 3.14 [https://github.com/OSGeo/grass/pull/7724 #7724]

==== July 16 ====
* review 7599, 7444
* reviewing GSoC r.param.scale and r.proj PRs
* fixing v.proj bug

=== Edouard Choinière ===
==== 2026-07-11 ====
* Discussion with Corey White on trying to build docs with Zensical, and dropping Sphinx for [https://zensical.org/docs/setup/extensions/mkdocstrings/ mkdocstrings]
* Discussion with Vaclav Petras on Windows builds and Fable:
** The nsis installer had a change to do (as debugged last year by me in [https://github.com/OSGeo/grass/issues/5663 #5663]), but we don't know how to do it well. We suggested to let Anthropic's Fable try to do it before it stopped being included in the Claude subscription.
** For us to try out the fixed nsis installer script, Fable should be able to create the installer in CI. It is being tried in [https://github.com/echoix/grass/pull/664 echoix#664]/[https://github.com/wenzeslaus/grass/pull/12 wenzeslaus#12]
** Also suggested to use Fable to attempt to solve issues in a pending Sphinx PR that we were stuck for too long, (Stcuk PR: [https://github.com/OSGeo/grass/pull/7526 #7526], result: [https://github.com/wenzeslaus/grass/pull/11 wenzeslaus#11])
==== 2026-07-12 ====
* Got PRs merged: [https://github.com/OSGeo/grass/pull/7660 #7660], [https://github.com/OSGeo/grass/pull/7659 #7659],
* Created follow-up PR for sscanf: [https://github.com/OSGeo/grass/pull/7673 #7673]
* Discussed with Stefan Blumentrath:
** temporal init, choice of his PR or another contributor
** Discussed AI findings on various files accumulated in the last weeks: most are valid and should be filed.
* Reviewed PRs: [https://github.com/OSGeo/grass-addons/pull/641 grass-addons#641], [https://github.com/OSGeo/grass/pull/7635 #7635], [https://github.com/OSGeo/grass/pull/7671 #7671], [https://github.com/OSGeo/grass/pull/7669 #7669]
* Video call on FHS
* First review of Fable windows installer in CI on [https://github.com/echoix/grass/pull/664 echoix#664]

==== 2026-07-13 ====
* Reviewed PRs: [https://github.com/OSGeo/grass/pull/7663 #7663], [https://github.com/OSGeo/grass-website/pull/635 grass-website#635], [https://github.com/OSGeo/grass/pull/7337 #7337], [https://github.com/OSGeo/grass/pull/7672 #7672], [https://github.com/OSGeo/grass/pull/7684 #7684], [https://github.com/OSGeo/grass/pull/7687 #7687]
* Worked on the last sscanf CodeQL alert, for [https://github.com/OSGeo/grass/pull/7673 #7673]
* Tested out windows standalone installer built in CI [https://github.com/echoix/grass/pull/664 echoix#664]. Almost works, as it installs, but it doesn't start because of a path error. Wrote some notes about windows compilation in CI in relation to addons in Vashek's google doc.
* Wrote notes on the windows build script having two versions, where OSGeo4W uses a different one than the one we use in CI for our tests, and they diverged
* Submitted PR of AI findings for tests of g.md2man [https://github.com/OSGeo/grass/pull/7679 #7679]
* Configured CI required checks to not wait for successful checks during the code sprint, with the new rights given to me. Discussed with Vashek on what approach we'd want for the 4 ubuntu job configurations.
** Commented on an issue closed today [https://github.com/OSGeo/grass/issues/1313 #1313] about cppcheck: cppcheck could be useful to cover a bit more configuration combinations, but as discussed, only being to compile would only get us so far without testing.
* Discussion with Vashek on AI policy and approach to use with AI, low-quality contributors; Approach on renovate updates; Wishes on release cadence
* Multiple reviews and pair brainstorming on grass-website with Corey White, including [https://github.com/OSGeo/grass-website/pull/635 grass-website#635], [https://github.com/OSGeo/grass-website/pull/637 grass-website#637], [https://github.com/OSGeo/grass-website/pull/639 grass-website#639], [https://github.com/OSGeo/grass-website/pull/634 grass-website#634], [https://github.com/OSGeo/grass-website/pull/640 grass-website#640]
* Worked on CMake formatting, moving forward the PR a contributor opened for Gersemi, PR [https://github.com/OSGeo/grass/pull/7663 #7663], discussed weird finding with Vashek, lead to issue [https://github.com/OSGeo/grass/issues/7686 #7686]. To be continued the next day.
* Opened PR [https://github.com/OSGeo/grass/pull/7685 #7685] (merged), [https://github.com/OSGeo/grass/pull/7683 #7683] (needs more work/investigation), [https://github.com/OSGeo/grass/pull/7680 #7680] (merged)
* Opened issue to add zizmor to grass-website tools used to check, either local or CI [https://github.com/OSGeo/grass-website/issues/636 grass-website#636]

==== 2026-07-14 ====
* (Early night) Merge PR that updates minimum Python version to 3.11, needed to change the required checks in order to do so. [https://github.com/OSGeo/grass/pull/7684 #7684].
** In the morning, update PRs which were most probably ready, and needed the check passing, like [https://github.com/OSGeo/grass/pull/7329 #7329], [https://github.com/OSGeo/grass/pull/7635 #7635], [https://github.com/OSGeo/grass/pull/7687 #7687]
* Review and/or merge [https://github.com/OSGeo/grass-website/pull/642 grass-website#642], [https://github.com/OSGeo/grass/pull/7674 #7674], [https://github.com/OSGeo/grass/pull/7689 #7689], [https://github.com/OSGeo/grass/pull/7688 #7688], [https://github.com/OSGeo/grass/pull/7690 #7690], [https://github.com/OSGeo/grass/pull/7699 #7699], [https://github.com/OSGeo/grass/pull/7697 #7697], [https://github.com/OSGeo/grass/pull/7713 #7713], [https://github.com/OSGeo/grass/pull/7702 #7702], [https://github.com/OSGeo/grass/pull/7678 #7678], [https://github.com/OSGeo/grass-addons/pull/1786 grass-addons#1786]
* Long review and analysis of [https://github.com/OSGeo/grass-website/pull/646 grass-website#646], coming from a discussion earlier on that using a single workflow to build, but split the deploy part in order to run separately.
* Work on CMake formatting tool: Finally ended up replacing [https://github.com/OSGeo/grass/pull/7663 #7663] with [https://github.com/OSGeo/grass/pull/7696 #7696]. Will close issue [https://github.com/OSGeo/grass/issues/7346 #7346] and [https://github.com/OSGeo/grass/issues/7686 #7686]. Opened issues with the tool's repo [https://github.com/BlankSpruce/gersemi/issues/123], [https://github.com/BlankSpruce/gersemi/issues/124], and [https://github.com/BlankSpruce/gersemi/issues/122] (the previous day).
* Help Stefan Blumentrath's son get started with finding simple ruff rules to fix.
* Work with Antonio Galea on making windows standalone installer + addons work without the old server. The installer now works. [https://github.com/echoix/grass/pull/664 echoix#664]
* Reviewing PR by navigating types in dynamic gui code [https://github.com/OSGeo/grass/pull/7693 #7693]
* More precise discussion with team on what renovate grouping strategy to use.
* Discussion with Vashek on python version support policy.
* Created PR [https://github.com/OSGeo/grass/pull/7718 #7718] (merged)

==== 2026-07-15 ====
* Merged [https://github.com/OSGeo/grass/pull/7699 #7699]
* Review issue [https://github.com/OSGeo/grass/issues/7646 #7646]
* Created PR [https://github.com/OSGeo/grass/pull/7722 #7722] (merged), [https://github.com/OSGeo/grass/pull/7723 #7723]
* Review PR [https://github.com/OSGeo/grass/pull/7687 #7687], [https://github.com/OSGeo/grass-website/pull/646 grass-website#646], [https://github.com/OSGeo/grass-addons/pull/1769 grass-addons#1769], [https://github.com/OSGeo/grass-addons/pull/1785 grass-addons#1785], [https://github.com/OSGeo/grass/pull/7676 #7676], [https://github.com/OSGeo/grass-website/pull/645 grass-website#645], [https://github.com/OSGeo/grass/pull/5656 #5656], [https://github.com/OSGeo/grass-addons/pull/1791 grass-addons#1791]
* Try to get [https://github.com/OSGeo/grass/pull/7635 #7635] merged (update after other PR fixed test).
* Finished editing [https://github.com/OSGeo/grass/pull/7693 #7693]
* Worked again on CMake formatting, creating stubs for unrecognized functions [https://github.com/OSGeo/grass/pull/7696 #7696]
* Create draft rulesets for the grass-website repo.
* Debugged [https://github.com/OSGeo/grass/pull/7683 #7683] for codecov to work on macOS runners configured to build grass
* Discussion with Anna on the viability of MkDocs, alternatives, and how the attempt on using Zensical turned out. Zensical is missing at least tag listing pages.

==== 2026-07-16 ====
* Applied the fixes for [https://github.com/OSGeo/grass/pull/7683 #7683] to work.

=== Vaclav Petras ===

==== 2026-07-12 ====

* Reviews and discussion on FHS (video call, [https://github.com/OSGeo/grass/pull/5630 5630], [https://github.com/wenzeslaus/grass/pull/10 my fork PR 10])
* Test reviews: [https://github.com/OSGeo/grass/pull/7675 #7675]
* Windows distribution reviews: [https://github.com/OSGeo/grass/issues/5663 #5663]
* Sphinx reviews: [https://github.com/OSGeo/grass/pull/7526 #7526]
* RegionManager discussion ([https://github.com/OSGeo/grass/pull/7599 7599])
* Parson allocation review: [https://github.com/OSGeo/grass/pull/7208 7208]

==== 2026-07-13 ====

* Reduce Sphinx warnings

==== 2026-07-14 ====

* Update RFC for updating Python versions which also sets up precedence for RFC amendments.
* Review v.class undefined behavior PR
* Reduce Sphinx warnings
* Port old in-package grass.pygrass unit tests to pytest

=== Stefan Blumentrath ===
==== 2026-07-12 ====
Opened PRs: [https://github.com/OSGeo/grass/pull/7672 #7672]

Reviewed: [https://github.com/OSGeo/grass/pull/7670 #7670], [https://github.com/OSGeo/grass/pull/7671 #7671]

Closed PRs: [https://github.com/OSGeo/grass/pull/7644 #7644]

==== 2026-07-13 ====

Discussed options for handling STDS in the GUI

Opened PRs: [https://github.com/OSGeo/grass/pull/7678 #7678]

Reviewed PRs: [https://github.com/OSGeo/grass/pull/7670 #7670]

Merged PRs: [https://github.com/OSGeo/grass/pull/7672 #7672]

Closed PRs: [https://github.com/OSGeo/grass/pull/7671 #7671]

==== 2026-07-14 ====

Opened PRs: [https://github.com/OSGeo/grass/pull/7707 #7707]

Reviewed PRs: [https://github.com/OSGeo/grass/pull/7670 #7670]

==== 2026-07-15 ====

Reviewed PRs: [https://github.com/OSGeo/grass/pull/7682 #7682], [https://github.com/OSGeo/grass/pull/7714 #7714], [https://github.com/OSGeo/grass/pull/7670 #7670]

Closed PRs: [https://github.com/OSGeo/grass/pull/7707 #7707]

=== Luca Delucchi ===

* All the local organizing (Thank you, Luca!)

==== Website ====

* [https://github.com/OSGeo/grass-website/pull/169 Community map]

==== Addons ====
* [https://github.com/OSGeo/grass-addons/pull/1010/ t.rast.aggregate.seasons] new addon
* [https://github.com/OSGeo/grass-addons/pull/1005 t.rast.climatologies] new addon
* [https://github.com/OSGeo/grass-addons/pull/641 t.rast.vi] new addon
* [https://github.com/OSGeo/grass-addons/pull/1695 r.learn.predict] fix map history

=== Antonio Galea ===

==== Jul 14 ====
* support with the development of the (broken) winGRASS server replacement with a GitHub actions based Windows installer in CI on [https://github.com/echoix/grass/pull/664 echoix#664]

=== Tomaž Žagar ===
==== 2026-07-14 ====

* i.hyper addon: enhancement/bugfix when importing EnMAP example data: https://github.com/mazingaro/grass-addons/issues/12
* i,hyper addon: fixed radiance import: https://github.com/mazingaro/grass-addons/issues/16
* started to work on: https://github.com/mazingaro/grass-addons/issues/6

==== 2026-07-15 ====
* Continued to work on: https://github.com/mazingaro/grass-addons/issues/6
** first implemented it as Python addon - then switched to C addon as proposed for "better" integration (compilation when installing addon with g.extension) with https://github.com/YannChemin/libsixsv
** included https://github.com/YannChemin/i.hyper.atcorr to https://github.com/mazingaro/grass-addons/tree/i.hyper/src/imagery/i.hyper/i.hyper.atcorr
** added i.hyper.history handling to https://github.com/mazingaro/grass-addons/commit/97957ebf7723a2866a13926ded57d104a546036a
** testing and wondering

=== Matjaž Krebs ===
==== 2026-07-13 ====
* i.hyper addon: Started working on new importer module for emit data
==== 2026-07-14 ====
* i.hyper addon: working on importer module for emit data. Implementing and troubleshooting.
* i.hyper addon: working on i.hyper.export bug for exporting 3D raster cube from WGS 4326

=== Alen Mangafić ===
==== 2026-07-14 ====

* i.hyper addon: improved EnMAP import handling and related bugfixes: https://github.com/mazingaro/grass-addons/commit/0a30d9505, https://github.com/mazingaro/grass-addons/commit/36bf3e686
* i.hyper addon: improved metadata copying/validation and fixed i.hyper.preproc import behavior: https://github.com/mazingaro/grass-addons/commit/d4313f162, https://github.com/mazingaro/grass-addons/commit/a52012289, https://github.com/mazingaro/grass-addons/commit/ce6cdd25d, https://github.com/mazingaro/grass-addons/commit/6d994e853
* i.hyper addon: implemented spectral resampling and merged it into i.hyper: https://github.com/mazingaro/grass-addons/commit/38a8e073b, https://github.com/mazingaro/grass-addons/commit/c992bc90f
* helped Matjaž Krebs to survive the day
==== 2026-07-15 ====

* SPDX License AI monkey business TBA

=== Christian Braun ===

* grass: [https://github.com/OSGeo/grass/pull/7725 grass #7725] — wxGUI: fixed orphaned drag image windows when dragging layers in the layer tree on macOS, and addressed the review comments on the TOC drag fix.
* grass-addons: added [https://docs.pytest.org pytest] test coverage and small fixes to several addons:
** [https://github.com/OSGeo/grass-addons/pull/1784 grass-addons #1784] — ''r.clip'': added a pytest test suite (merged).
** [https://github.com/OSGeo/grass-addons/pull/1786 grass-addons #1786] — ''r.centroids'': added a pytest test suite (merged).
** [https://github.com/OSGeo/grass-addons/pull/1787 grass-addons #1787] — ''v.median'': fixed the stdout output and added a pytest test suite.
* actinia: discussed with Markus about a GeoNode-Addon to connect actinia as a processing backend. First architecting and design work has been done.

Talk:GRASS Community Meeting San Michele 2026

2026-07-16T06:17:56Z

Annakrat: /* Anna Petrasova */

{{toc|right}}

Quick links: [[GRASS Community Meeting San Michele 2026|Meeting page]] | [[#Reports|Reports]] | [[GRASS_Community_Meeting_Prague_2024#Sponsors|Sponsors]]

== Organizing Team ==

* Initial planning: Luca Delucchi, Vaclav Petras, Veronica Andreo, Markus Neteler, Anna Petrasova
* Budget: Luca Delucchi, Vaclav Petras, Markus Neteler, Veronica Andreo
* Raising support: Vaclav Petras, Markus Neteler, Veronica Andreo
* Reimbursements:
* Venue: Luca Delucchi
* Meals: Luca Delucchi
* Agenda: Veronica Andreo, Anna Petrasova
* Wiki page: Anna Petrasova, Luca Delucchi, Vaclav Petras
* Virtual participant support:
* Promotion, invitations, and social media: Vaclav Petras, Veronica Andreo
* Photography: Veronica Andreo

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

== Reports ==

Per-person reports from the meeting (one <code>=== Name ===</code> section per participant.)

=== Markus Neteler ===

==== Jul 12 ====
* work on generating an auto-generated GRASS addons index covering all addons found with GitHub topic "[https://github.com/topics/grass-gis-addons grass-gis-addons]"
** part 1: add missing markdown manual files to all addons missing them (addons found on GitHub outside of "grass-addons": currently 71)
** part 2: developing of a script doing the git clone/compilation/manual page generation steps [https://github.com/OSGeo/grass-addons/pull/1782 PR#1782]
*** yet unsubmitted

==== Jul 13 ====
* cleanup of some old stale tickets
* work on SBOM implementation [https://github.com/OSGeo/grass/issues/7215 issue 7215]

==== Jul 14 ====
* work on SBOM implementation [https://github.com/OSGeo/grass/issues/7215 issue 7215]
** Discussed sbom formatting (SPDX vs CycloneDX) and changes that need to made for compliance.
** Draft [https://github.com/OSGeo/grass/pull/7698 PR#7698] (CycloneDX SBOM)
* work on SPDX header cleanup [https://github.com/OSGeo/grass/issues/4190 issue 4190]
** Draft [https://github.com/OSGeo/grass/pull/7716 PR#7716]

==== Jul 15 ====
* continuation of work on SPDX header cleanup, learned a lot about agents
* re-gained ssh access (thanks, strk and Regina!)
** to grass.osgeo.org - fixes for new website deployment method
** to grasswiki.osgeo.org - check for captcha removal

=== Veronica Andreo ===

* Review grass-tutorials PRs [https://github.com/OSGeo/grass-tutorials/pull/116 #116], [https://github.com/OSGeo/grass-tutorials/pull/130 130], [https://github.com/OSGeo/grass-tutorials/pull/133 #133],[https://github.com/OSGeo/grass-tutorials/pull/135 #135], [https://github.com/OSGeo/grass-tutorials/pull/136 #136].
* Review grass-website PRs [https://github.com/OSGeo/grass-website/pull/169 169], [https://github.com/OSGeo/grass-website/pull/611 611], [https://github.com/OSGeo/grass-website/pull/613 613], [https://github.com/OSGeo/grass-website/pull/645 645].
* PRs and issues clean-up in tutorials and website.
* Fix conda submenu [https://github.com/OSGeo/grass-website/pull/643 643].
* Participated of the discussion on STDS integration into GUI with Anna and Stefan.
* Assisted Luca with local organization issues.
* Compiled list of voters for upcoming PSC elections in line with PSC criteria defined on [[PSC_Meeting_2024-06-14]].
** Went through grass, grass-addons, grass-promo, grass-website, grass-tutorials, rgrass and got contributors with at least one merged PR during the current and previous PSC mandates, i.e., as far as 2016.
** Check attendants to community meetings in the same period.
** Check contributions to QGIS related to GRASS in the same period.
** Processed all lists and compiled a file with unique names and emails.
* Pictures and social media posting.
* Managed to compile GRASS-dev in LSW.
* Tested [https://github.com/OSGeo/grass/pull/7707 grass-#7077].

=== Corey White ===
'''12-07-2026'''

GRASS Website migration to Bootstrap 5 and sass-dart
* Addressing [https://github.com/OSGeo/grass-website/issues/600 Issue #600]
Current state
# [https://github.com/OSGeo/grass-website/pull/599 PR#599 (grass-website)] - Approved (pending PR#635 and PR#1783)
# [https://github.com/OSGeo/grass-website/pull/552 PR#552 (grass-website)] (devcontainer) - Closed (superseded by #599)
# PR B (grass-website)(bootstrap5-migration) - Pushed to fork, not opened. I'll open after #599 merges
# PR C (grass-website) (brand-tokens-single-source) - Pushed to fork, not opened. I'll open after PR B merges
# [https://github.com/OSGeo/grass-website/pull/635 PR#635 (grass-website)] - Build production site in CI and publish it as a release artifact
# [https://github.com/OSGeo/grass-addons/pull/1783 PR#1783 (grass-addons)] - Updates deploy website CRON job from the CI-built release artifact

'''13-07-2026'''
# [https://github.com/OSGeo/grass/pull/3826 PR#3826 (grass) v.ppa] - Split code into smaller lib functions, fix issues with original implementation, and updated tests.
# [https://github.com/OSGeo/grass/pull/7298 Reviewed PR#7298] - grass.script: add create_mapset function
# Got t.stac tutorial reviewed by Vero
# [https://github.com/OSGeo/grass-website/pull/635 PR#635 (grass-website)] - '''(Merged)''' Build production site in CI and publish it as a release artifact
# [https://github.com/OSGeo/grass-website/pull/637 PR#637 (grass-website)] - '''(Merged)''' Fix production build: inline Renovate-managed toolchain versions
# [https://github.com/OSGeo/grass-website/pull/639 PR#637 grass-website)] - '''(Merged)''' Add Renovate's helper preset to pin GitHub Actions to the full length SHA

'''14-07-2026'''
# [https://github.com/OSGeo/grass-website/pull/643 PR#643 (grass-website)] - '''(Reviewed/Merged)''' Menu entries: Use uppercase for Conda submenu
# [https://github.com/OSGeo/grass-addons/pull/1783 PR#1783 (grass-addons)] - '''(Approved)''' Updates deploy website CRON job from the CI-built release artifact
# [https://github.com/OSGeo/grass-website/pull/644 PR#644 (grass-website)] - '''(Approved)''' Migrate markup to Bootstrap 5 and drop jQuery
# [https://github.com/OSGeo/grass-website/pull/645 PR#645 (grass-website)] - '''(In-Review)''' Single-source brand tokens; remove orphaned style.css (issue #600)
# [https://github.com/OSGeo/grass-website/pull/646 PR#645 (grass-website)] - '''(In-Review)''' Split production artifact workflow into build and deploy jobs
# [https://github.com/OSGeo/grass-addons/pull/1641 PR#1641 (grass-addons)] - '''(Merged)''' t.stac: fixed issue with download and import asset potentially overwhelming network.
# [https://github.com/OSGeo/grass/pull/3826 PR#3826 (grass) v.ppa] - '''(In-Review)''' Split code into smaller lib functions, fix issues with original implementation, updated tests, and images to docs
# Discussed sbom formatting (SPDX vs CycloneDX) and changes that need to made for compliance.

'''15-07-2026'''
# [https://github.com/OSGeo/grass-addons/pull/1788 PR#1788 (grass-addons)] - '''(Draft)''' Create new r.soils.rosetta addon.
# [https://github.com/OSGeo/grass-addons/pull/1336 PR#1336 (grass-addons)] - '''(Closed)''' Update python script shebang line to python3
# [https://github.com/OSGeo/grass/pull/7298 PR#7298 (grass)] - '''(Reviewed/Approved)''' grass.script: add create_mapset function
# [https://github.com/OpenPlainsInc/grass-obsidian (grass-obsidian)] - '''(Published)''' Opened up the OpenPlains grass-obsidian plugin that allows you to review your grass project from your obsidian notes.
# [https://github.com/OSGeo/grass-website/pull/646 PR#645 (grass-website)] - '''(Merged)''' Split production artifact workflow into build and deploy jobs
# [https://github.com/OSGeo/grass-website/pull/599 PR#599 (grass-website)] - '''(Merged)''' Hugo dart scss
# [https://github.com/OSGeo/grass-website/pull/644 PR#644 (grass-website)] - '''(Merged)''' Migrate markup to Bootstrap 5 and drop jQuery
# [https://github.com/OSGeo/grass-website/pull/645 PR#645 (grass-website)] - '''(Merged)''' Single-source brand tokens; remove orphaned style.css (issue #600)
# [https://github.com/OSGeo/grass-addons/pull/1783 PR#1783 (grass-addons)] - '''(Merged)''' Updates deploy website CRON job from the CI-built release artifact
# [https://github.com/OSGeo/grass-website/issues/636 Issue#636 (grass-website] - '''(Closed)''' Add zizmor to the checks run
# [https://github.com/OSGeo/grass/pull/7703 PR#7703 (grass)] - '''(Open)''' python: Use argument lists instead of shell=True for subprocess
# [https://github.com/OSGeo/grass/pull/7713 PR#7713 (grass)] - '''(Open)''' checks: Mark justified partial-path subprocess calls as nosec B607
# [https://github.com/OSGeo/grass/pull/7698 PR#7698 (grass)] - '''(Reviewed)'''CI: add CycloneDX SBOM generation for releases
# [https://github.com/OSGeo/grass-website/pull/583 PR#583 (grass-website)] '''(Closed)''' Update brand download dropdowns to Bootstrap 5 namespaced attributes

=== Anna Petrasova ===
==== Jul 12 ====
* Review of [https://github.com/OSGeo/grass/pull/7659 #7659], [https://github.com/OSGeo/grass/pull/7599 #7599]
* Finish v.geometry tool: [https://github.com/OSGeo/grass/pull/7329 #7329]
* Working on markdown to man page conversion to remove old html pages:
** [https://github.com/OSGeo/grass/pull/7540 #7540] - merged
** [https://github.com/OSGeo/grass/pull/7674 #7674]
* Review website [https://github.com/OSGeo/grass-website/pull/599 #599]

==== Jul 13 ====

* Discussion with Vero and Stefan on GSoC project implementation
* Fixed bug in temporal library: [https://github.com/OSGeo/grass/pull/7681 #7681]
* t.info tests [https://github.com/OSGeo/grass/pull/7682 #7682]
* Review Jupyter GUI integration [https://github.com/OSGeo/grass/pull/5901 #5901]
* Discussion between me, Linda, Alen and Vashek about data catalog and regions

==== Jul 14 ====

* Fixing v.class causing flaky test [https://github.com/OSGeo/grass/pull/7692 #7692]
* Call with Saket and Stefan about the GSoC project
* Review [https://github.com/OSGeo/grass/pull/7608 #7608], [https://github.com/OSGeo/grass/pull/5901 #5901]
* Adding new icons for #7608.
* Cmake fixes [https://github.com/OSGeo/grass/pull/7720 #7720]

==== July 15 ====
* temporal fixes [https://github.com/OSGeo/grass/pull/7717 #7717]
* over 10 PRs reviewed
* fix temporal with 3.14 [https://github.com/OSGeo/grass/pull/7724 #7724]

==== July 16 ====

=== Edouard Choinière ===
==== 2026-07-11 ====
* Discussion with Corey White on trying to build docs with Zensical, and dropping Sphinx for [https://zensical.org/docs/setup/extensions/mkdocstrings/ mkdocstrings]
* Discussion with Vaclav Petras on Windows builds and Fable:
** The nsis installer had a change to do (as debugged last year by me in [https://github.com/OSGeo/grass/issues/5663 #5663]), but we don't know how to do it well. We suggested to let Anthropic's Fable try to do it before it stopped being included in the Claude subscription.
** For us to try out the fixed nsis installer script, Fable should be able to create the installer in CI. It is being tried in [https://github.com/echoix/grass/pull/664 echoix#664]/[https://github.com/wenzeslaus/grass/pull/12 wenzeslaus#12]
** Also suggested to use Fable to attempt to solve issues in a pending Sphinx PR that we were stuck for too long, (Stcuk PR: [https://github.com/OSGeo/grass/pull/7526 #7526], result: [https://github.com/wenzeslaus/grass/pull/11 wenzeslaus#11])
==== 2026-07-12 ====
* Got PRs merged: [https://github.com/OSGeo/grass/pull/7660 #7660], [https://github.com/OSGeo/grass/pull/7659 #7659],
* Created follow-up PR for sscanf: [https://github.com/OSGeo/grass/pull/7673 #7673]
* Discussed with Stefan Blumentrath:
** temporal init, choice of his PR or another contributor
** Discussed AI findings on various files accumulated in the last weeks: most are valid and should be filed.
* Reviewed PRs: [https://github.com/OSGeo/grass-addons/pull/641 grass-addons#641], [https://github.com/OSGeo/grass/pull/7635 #7635], [https://github.com/OSGeo/grass/pull/7671 #7671], [https://github.com/OSGeo/grass/pull/7669 #7669]
* Video call on FHS
* First review of Fable windows installer in CI on [https://github.com/echoix/grass/pull/664 echoix#664]

==== 2026-07-13 ====
* Reviewed PRs: [https://github.com/OSGeo/grass/pull/7663 #7663], [https://github.com/OSGeo/grass-website/pull/635 grass-website#635], [https://github.com/OSGeo/grass/pull/7337 #7337], [https://github.com/OSGeo/grass/pull/7672 #7672], [https://github.com/OSGeo/grass/pull/7684 #7684], [https://github.com/OSGeo/grass/pull/7687 #7687]
* Worked on the last sscanf CodeQL alert, for [https://github.com/OSGeo/grass/pull/7673 #7673]
* Tested out windows standalone installer built in CI [https://github.com/echoix/grass/pull/664 echoix#664]. Almost works, as it installs, but it doesn't start because of a path error. Wrote some notes about windows compilation in CI in relation to addons in Vashek's google doc.
* Wrote notes on the windows build script having two versions, where OSGeo4W uses a different one than the one we use in CI for our tests, and they diverged
* Submitted PR of AI findings for tests of g.md2man [https://github.com/OSGeo/grass/pull/7679 #7679]
* Configured CI required checks to not wait for successful checks during the code sprint, with the new rights given to me. Discussed with Vashek on what approach we'd want for the 4 ubuntu job configurations.
** Commented on an issue closed today [https://github.com/OSGeo/grass/issues/1313 #1313] about cppcheck: cppcheck could be useful to cover a bit more configuration combinations, but as discussed, only being to compile would only get us so far without testing.
* Discussion with Vashek on AI policy and approach to use with AI, low-quality contributors; Approach on renovate updates; Wishes on release cadence
* Multiple reviews and pair brainstorming on grass-website with Corey White, including [https://github.com/OSGeo/grass-website/pull/635 grass-website#635], [https://github.com/OSGeo/grass-website/pull/637 grass-website#637], [https://github.com/OSGeo/grass-website/pull/639 grass-website#639], [https://github.com/OSGeo/grass-website/pull/634 grass-website#634], [https://github.com/OSGeo/grass-website/pull/640 grass-website#640]
* Worked on CMake formatting, moving forward the PR a contributor opened for Gersemi, PR [https://github.com/OSGeo/grass/pull/7663 #7663], discussed weird finding with Vashek, lead to issue [https://github.com/OSGeo/grass/issues/7686 #7686]. To be continued the next day.
* Opened PR [https://github.com/OSGeo/grass/pull/7685 #7685] (merged), [https://github.com/OSGeo/grass/pull/7683 #7683] (needs more work/investigation), [https://github.com/OSGeo/grass/pull/7680 #7680] (merged)
* Opened issue to add zizmor to grass-website tools used to check, either local or CI [https://github.com/OSGeo/grass-website/issues/636 grass-website#636]

==== 2026-07-14 ====
* (Early night) Merge PR that updates minimum Python version to 3.11, needed to change the required checks in order to do so. [https://github.com/OSGeo/grass/pull/7684 #7684].
** In the morning, update PRs which were most probably ready, and needed the check passing, like [https://github.com/OSGeo/grass/pull/7329 #7329], [https://github.com/OSGeo/grass/pull/7635 #7635], [https://github.com/OSGeo/grass/pull/7687 #7687]
* Review and/or merge [https://github.com/OSGeo/grass-website/pull/642 grass-website#642], [https://github.com/OSGeo/grass/pull/7674 #7674], [https://github.com/OSGeo/grass/pull/7689 #7689], [https://github.com/OSGeo/grass/pull/7688 #7688], [https://github.com/OSGeo/grass/pull/7690 #7690], [https://github.com/OSGeo/grass/pull/7699 #7699], [https://github.com/OSGeo/grass/pull/7697 #7697], [https://github.com/OSGeo/grass/pull/7713 #7713], [https://github.com/OSGeo/grass/pull/7702 #7702], [https://github.com/OSGeo/grass/pull/7678 #7678], [https://github.com/OSGeo/grass-addons/pull/1786 grass-addons#1786]
* Long review and analysis of [https://github.com/OSGeo/grass-website/pull/646 grass-website#646], coming from a discussion earlier on that using a single workflow to build, but split the deploy part in order to run separately.
* Work on CMake formatting tool: Finally ended up replacing [https://github.com/OSGeo/grass/pull/7663 #7663] with [https://github.com/OSGeo/grass/pull/7696 #7696]. Will close issue [https://github.com/OSGeo/grass/issues/7346 #7346] and [https://github.com/OSGeo/grass/issues/7686 #7686]. Opened issues with the tool's repo [https://github.com/BlankSpruce/gersemi/issues/123], [https://github.com/BlankSpruce/gersemi/issues/124], and [https://github.com/BlankSpruce/gersemi/issues/122] (the previous day).
* Help Stefan Blumentrath's son get started with finding simple ruff rules to fix.
* Work with Antonio Galea on making windows standalone installer + addons work without the old server. The installer now works. [https://github.com/echoix/grass/pull/664 echoix#664]
* Reviewing PR by navigating types in dynamic gui code [https://github.com/OSGeo/grass/pull/7693 #7693]
* More precise discussion with team on what renovate grouping strategy to use.
* Discussion with Vashek on python version support policy.
* Created PR [https://github.com/OSGeo/grass/pull/7718 #7718] (merged)

==== 2026-07-15 ====
* Merged [https://github.com/OSGeo/grass/pull/7699 #7699]
* Review issue [https://github.com/OSGeo/grass/issues/7646 #7646]
* Created PR [https://github.com/OSGeo/grass/pull/7722 #7722] (merged), [https://github.com/OSGeo/grass/pull/7723 #7723]
* Review PR [https://github.com/OSGeo/grass/pull/7687 #7687], [https://github.com/OSGeo/grass-website/pull/646 grass-website#646], [https://github.com/OSGeo/grass-addons/pull/1769 grass-addons#1769], [https://github.com/OSGeo/grass-addons/pull/1785 grass-addons#1785], [https://github.com/OSGeo/grass/pull/7676 #7676], [https://github.com/OSGeo/grass-website/pull/645 grass-website#645]
* Try to get [https://github.com/OSGeo/grass/pull/7635 #7635] merged (update after other PR fixed test).
* Finished editing [https://github.com/OSGeo/grass/pull/7693 #7693]

=== Vaclav Petras ===

==== 2026-07-12 ====

* Reviews and discussion on FHS (video call, [https://github.com/OSGeo/grass/pull/5630 5630], [https://github.com/wenzeslaus/grass/pull/10 my fork PR 10])
* Test reviews: [https://github.com/OSGeo/grass/pull/7675 #7675]
* Windows distribution reviews: [https://github.com/OSGeo/grass/issues/5663 #5663]
* Sphinx reviews: [https://github.com/OSGeo/grass/pull/7526 #7526]
* RegionManager discussion ([https://github.com/OSGeo/grass/pull/7599 7599])
* Parson allocation review: [https://github.com/OSGeo/grass/pull/7208 7208]

==== 2026-07-13 ====

* Reduce Sphinx warnings

==== 2026-07-14 ====

* Update RFC for updating Python versions which also sets up precedence for RFC amendments.
* Review v.class undefined behavior PR
* Reduce Sphinx warnings
* Port old in-package grass.pygrass unit tests to pytest

=== Stefan Blumentrath ===
==== 2026-07-12 ====
Opened PRs: [https://github.com/OSGeo/grass/pull/7672 #7672]

Reviewed: [https://github.com/OSGeo/grass/pull/7670 #7670], [https://github.com/OSGeo/grass/pull/7671 #7671]

Closed PRs: [https://github.com/OSGeo/grass/pull/7644 #7644]

==== 2026-07-13 ====

Discussed options for handling STDS in the GUI

Opened PRs: [https://github.com/OSGeo/grass/pull/7678 #7678]

Reviewed PRs: [https://github.com/OSGeo/grass/pull/7670 #7670]

Merged PRs: [https://github.com/OSGeo/grass/pull/7672 #7672]

Closed PRs: [https://github.com/OSGeo/grass/pull/7671 #7671]

==== 2026-07-14 ====

Opened PRs: [https://github.com/OSGeo/grass/pull/7707 #7707]

Reviewed PRs: [https://github.com/OSGeo/grass/pull/7670 #7670]

==== 2026-07-15 ====

Reviewed PRs: [https://github.com/OSGeo/grass/pull/7682 #7682], [https://github.com/OSGeo/grass/pull/7714 #7714], [https://github.com/OSGeo/grass/pull/7670 #7670]

Closed PRs: [https://github.com/OSGeo/grass/pull/7707 #7707]

=== Luca Delucchi ===

* All the local organizing (Thank you, Luca!)

==== Website ====

* [https://github.com/OSGeo/grass-website/pull/169 Community map]

==== Addons ====
* [https://github.com/OSGeo/grass-addons/pull/1010/ t.rast.aggregate.seasons] new addon
* [https://github.com/OSGeo/grass-addons/pull/1005 t.rast.climatologies] new addon
* [https://github.com/OSGeo/grass-addons/pull/641 t.rast.vi] new addon
* [https://github.com/OSGeo/grass-addons/pull/1695 r.learn.predict] fix map history

=== Antonio Galea ===

==== Jul 14 ====
* support with the development of the (broken) winGRASS server replacement with a GitHub actions based Windows installer in CI on [https://github.com/echoix/grass/pull/664 echoix#664]

=== Tomaž Žagar ===
==== 2026-07-14 ====

* i.hyper addon: enhancement/bugfix when importing EnMAP example data: https://github.com/mazingaro/grass-addons/issues/12
* i,hyper addon: fixed radiance import: https://github.com/mazingaro/grass-addons/issues/16
* started to work on: https://github.com/mazingaro/grass-addons/issues/6

=== Matjaž Krebs ===
==== 2026-07-13 ====
* i.hyper addon: Started working on new importer module for emit data
==== 2026-07-14 ====
* i.hyper addon: working on importer module for emit data. Implementing and troubleshooting.
* i.hyper addon: working on i.hyper.export bug for exporting 3D raster cube from WGS 4326

=== Alen Mangafić ===
==== 2026-07-14 ====

* i.hyper addon: improved EnMAP import handling and related bugfixes: https://github.com/mazingaro/grass-addons/commit/0a30d9505, https://github.com/mazingaro/grass-addons/commit/36bf3e686
* i.hyper addon: improved metadata copying/validation and fixed i.hyper.preproc import behavior: https://github.com/mazingaro/grass-addons/commit/d4313f162, https://github.com/mazingaro/grass-addons/commit/a52012289, https://github.com/mazingaro/grass-addons/commit/ce6cdd25d, https://github.com/mazingaro/grass-addons/commit/6d994e853
* i.hyper addon: implemented spectral resampling and merged it into i.hyper: https://github.com/mazingaro/grass-addons/commit/38a8e073b, https://github.com/mazingaro/grass-addons/commit/c992bc90f
* helped Matjaž Krebs to survive the day
==== 2026-07-15 ====

* SPDX License AI monkey business TBA

Talk:GRASS Community Meeting San Michele 2026

2026-07-15T07:50:19Z

Annakrat: /* Anna Petrasova */

Talk:GRASS Community Meeting San Michele 2026

2026-07-15T06:18:39Z

Annakrat: /* Anna Petrasova */

Talk:GRASS Community Meeting San Michele 2026

2026-07-15T06:18:12Z

Annakrat: /* Jul 12 */

Talk:GRASS Community Meeting San Michele 2026

2026-07-14T16:54:07Z

Annakrat: /* Jul 14 */

Talk:GRASS Community Meeting San Michele 2026

2026-07-14T15:11:57Z

Annakrat: /* Jul 14 */

Talk:GRASS Community Meeting San Michele 2026

2026-07-14T13:49:05Z

Annakrat: /* Jul 14 */

GRASS Community Meeting San Michele 2026

2026-07-14T13:47:52Z

Annakrat: /* Tuesday, July 14 */

[[File:Sanmichele.png|frameless|center|1000px|San Michele all'Adige]]

{{toc|right}}

The ''GRASS Community Meeting'' for contributors and developers will be happening from '''July 11 - 19, 2026''' in [https://www.openstreetmap.org/relation/46990#map=12/46.1349/11.1947 San Michele all'Adige, Trentino, Italy].

== Sponsors ==

Sponsors make the event possible. Learn more about [https://grass.osgeo.org/contribute/sponsoring/ Sponsoring].

* [https://bhinc.com/ Bohannan Huston, Inc.]: 2,500 USD
[[File:Bohannan_Huston_Inc_Logo.png|none|left|400px|alt=Logo of Bohannan Huston, Inc.|Bohannan Huston, Inc.]]

* [https://www.osgeo.org/ OSGeo]: 2500 USD (see [https://wiki.osgeo.org/w/index.php?title=GRASS_Community_Meeting_2026:_Budget budget]]).

[[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.fossgis.de/ FOSSGIS e.V.]: 4500 EUR (approved budget contribution, [https://www.fossgis.de/wiki/F%C3%B6rderantr%C3%A4ge/GRASS_GIS_Community_Meeting_2026 request]).

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

* U.S. National Science Foundation, award 2303651 (planning and time of 3 participants).

* In-kind contributions:
** mundialis GmbH & Co. KG - personnel time (personnel time)
** Geodetic institute of Slovenia (GI) - personnel time: SPHERE (basic research project No. J7-70247) financed by Slovenian Research and Innovation Agency
* Personal time and/or financial contributions:
** Edouard Choinière, Helmut Kudrnovsky, Markus Neteler, Vaclav Petras, Anna Petrasova, Corey White, Veronica Andreo
** In addition to the above contributions, many participants made special efforts to keep costs down.

== Purpose ==
The ''GRASS Community Meeting'' is a great occasion for folks to support the development by actively contributing to the project in different ways. These include source code updates, documentation (manuals, wiki, tutorials), translations, website improvements 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 project and the interfaces to QGIS, GDAL, PostGIS, R, OGC Services and others.

The focus is on GRASS maintenance, and interaction with other projects. Many maintenance tasks, infrastructure changes, and planning of large changes especially benefits from maintainers being in one place and time zone. While the specific topics highly depend on the participants, we will prioritize topics which require highly synchronous collaboration, such as the CMake build system transition and API transitions. The [https://grass.osgeo.org/news/2025_05_27_grass_dev_summit_report/ 2025 event report] gives an overview of what was achieved last year.

We do require participants to work on GRASS or connections to other projects. However, we leave them the freedom to work on what they think is the best contribution to the project given their skills and time available.

== Agenda ==

Agenda is being refined.

=== Saturday, July 11 ===

Day of arrival. Contact organizers (Luca, see FAQ below) if you are interested in individualized program or helping with organization.

=== Sunday, July 12 ===

* Hybrid meeting about 8.6.0 with Filesystem Hierarchy Standard and Jupyter in GUI updates

=== Monday, July 13 ===

* Filesystem Hierarchy Standard ([https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard FHS])
* New '''Windows build server''' needed for addon provisioning and to get rid of "windows-2022 build and tests" (<code>ERROR: Cannot open URL <http://wingrass.fsv.cvut.cz/grass85/addons/grass-8.5.1dev/r.stream.distance.zip>: HTTP Error 404: Not Found</code>)
* Call with remote participants on GUI topics ([https://github.com/OSGeo/grass/issues/7614 #7614] and others)

=== Tuesday, July 14 ===

* [[GSoC]] Space-time dataset integration call
* GeoAI
* Updating the GRASS Roadmap

=== Wednesday, July 15 ===

* Python API review
* Plan [[PSC]] elections

=== Thursday, July 16 ===

* Reducing PR backlog

=== Friday, July 17 ===

* Address issues for the upcoming [https://github.com/OSGeo/grass/milestone/29 8.6.0 release]
* Presentation of i.hyper @ 11.00h.

=== Saturday, July 18 ===

* Website review: fix the serious bootstrap mixup and broken sitemap bugs

=== Sunday, July 19 ===

Day of departure.

== Participation ==

Please add your name here:

{|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:Lucadelu|Luca Delucchi]]
| Italy
|
|
|
|
|-
|2
| [[User:wenzeslaus|Vaclav Petras]]
| United States
| 11.07.
| 19.07.
| grass.tools, pytest, subcommands, reviews
|
|-
|3
| [[User:Annakrat|Anna Petrasova]]
| United States
| 11.07.
| 19.07.
| GSoC, reviews, PR backlog, tutorials
|
|-
|4
| [[User:Neteler|Markus Neteler]]
| Germany
| 06.07.
| 18.07.
| documentation, website, state of GRASS support in QGIS 3.x/4.x, knowledge-transfer
|
|-
|5
| [[User:Sbl|Stefan Blumentrath]]
| Norway
| 11.07. (presumably)
| 18.07. (presumably)
| Handling Copernicus data with GRASS / actinia
|
|-
|6
| [[User:Hellik|Helmut Kudrnovsky]]
| Austria
|
|
|
|
|-
|7
| [[User:Veroandreo|Verónica Andreo]]
| Argentina
| 11.07.
| 19.07.
|
|
|-
|8
| [[User:Ctwhite|Corey White]]
| United States
| 11.07.
| 19.07.
| grass.jupyter, documentation, website, reviews, tutorials
|
|-
|9
| [[User:Echoix|Edouard Choinière]]
| Canada
| 11.07. (presumably)
| 19.07. (presumably)
| Reviews, CI, pytest, Windows GUI, i18n, undecided
|
|-
|10
| [[User:Mazingaro|Alen Mangafić]]
| Slovenia
| 13.07.
| 17.07.
| i.hyper: [https://grass.osgeo.org/grass-stable/manuals/addons/i.hyper.html Road Map] fulfilling; State of GRASS @FOSS4G 2026
|
|-
|11
| Tomaž Žagar
| Slovenia
| 13.07.
| 17.07.
| i.hyper: [https://grass.osgeo.org/grass-stable/manuals/addons/i.hyper.html Road Map] fulfilling
|
|-
|12
| Matjaž Krebs
| Slovenia
| 13.07.
| 17.07.
| i.hyper: [https://grass.osgeo.org/grass-stable/manuals/addons/i.hyper.html Road Map] fulfilling
|
|-
|13
| Christian Braun
| Luxembourg
| 13.07.
| 16.07.
| Reviews, documentation
|
|-
|}

Registration is free; participants cover their own travel and lodging (see below), often with employer support — thank you. Ideally we'd reimburse everyone, and every [https://numfocus.org/donate-to-grass donation] or [https://grass.osgeo.org/contribute/sponsoring/ employer sponsorship] of the project helps us get closer.

== Venue ==
The meeting will be hosted at [https://fmach.it/ Fondazione Edmund Mach] (FEM) in San Michele all'Adige, Trentino, Italy — about 15 km north of Trento. FEM is a research and education center with on-site facilities that allow participants to work, sleep, and eat in the same location.

[https://maps.app.goo.gl/5YEuEts6qXvky7HD9 Map]

=== Getting there ===

San Michele all'Adige is reachable by train on the Trento–Bolzano line (Trento or Mezzocorona station), with frequent connections from Trento (~15 minutes) and Verona (~1 hour). The nearest airports are Verona (VRN), Venice Marco Polo (VCE) and Treviso (TSF), Milan Bergamo (BGY), Malpensa (MXP), and Linate (LIN), Bologna (BLQ), and Innsbruck (INN) in Austria. Trento is also the host city of FOSS4G Italy 2026 (July 9–11), making it convenient to combine both events.

From Trento main train station you need to move to Ferrovia Trento-Malè (FTM) train station (few minutes by walk, https://www.openstreetmap.org/#map=17/46.072739/11.120814) and there take a train to Grumo/San Michele all'Adige. Train timetable is [https://www.trentinotrasporti.it/images/allegati/ferrovia/ftm/FTM%20est2026%20-%20ANDATA.pdf here], the opposite way is [https://www.trentinotrasporti.it/images/allegati/ferrovia/ftm/FTM%20est2026%20-%20RITORNO.pdf this one]

Another possibility is to arrive with the main train (Ferrovie dello Stato) in Mezzocorona and here you can walk to San Michele (around 20 minutes by walk) or take the small train Trento-Malè from Mezzocorona Ferrovia station (in front of main train station https://www.openstreetmap.org/#map=18/46.206633/11.128024) and stop in Grumo/San Michele (you need to look for the [https://www.trentinotrasporti.it/images/allegati/ferrovia/ftm/FTM%20est2026%20-%20RITORNO.pdf way back schedule])

== Accommodation and Costs ==

''Registration is free''. However, participants should plan for the following costs:

* Travel
* Lodging

Participants can stay on-site at the FEM convitto (dormitory), keeping the community together for the full duration of the meeting:

* €35 per person per night
* Double and triple rooms (triples include a small kitchen)
* A mandatory on-site supervisor is required at €200 per night (flat fee, shared across the group)
* Family members are welcome to stay in the dormitory as well
* [https://cif.fmach.it/content/download/2701/78358/file/brochure_convitto.pdf Brochure]
* For '''lodging booking''' options: see [https://grasscommunitymeeting2026.eventbrite.it/ Eventbrite]

For anyone preferring alternative lodging, hotels and B&Bs are available in San Michele and nearby Trento.

Lunches on weekdays can be taken at the FEM canteen (mensa), located on the same campus. Details and pricing are being finalized.

== Individual Preparation ==

* Bring your own computer
* Bring {{wikipedia|AC power plugs and sockets|power adapter}} if needed (Italy: 230V, 50Hz, {{wikipedia|Europlug|Type C}}, {{wikipedia|Schuko|Type F}}, and {{wikipedia|AC power plugs and sockets: L|Type L}} sockets are common)
* Install git and the compiler tools, and come with a working GRASS development environment if possible. See [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md here] for details.

== FAQ ==

* ''Is this a conference?''
** Talks or presentations may be included, but the purpose is to work together on the project. Among conference formats, the closest comparison would be a participatory workshop.
* ''Is this a hackathon?''
** While there is plenty of intensive coding, the meeting is not competitive. We meet to collaborate.
* ''Is the GRASS Community Meeting for developers only?''
** No, the meeting is open to all users, supporters, contributors, power users, and developers ''who want to make a meaningful contribution to the project''.
* ''What skills do I need?''
** Coding skills are not required. Contributions to documentation, tutorials, translations, website, and testing are all valuable. Practical help during the meeting, such as coordinating meals, photography, or reporting, is a real contribution too.
* ''Can I attend remotely?''
** The meeting is in-person, but everyone is welcome to use the same week for focused work on the project from wherever they are.
* ''What language is used during the meeting?''
** English is the working language, but you may hear several other languages spoken at the event.
* ''How was it last time?''
** Splendid! See [[GRASS Developer Summit Raleigh 2025]]!
* ''Where can I get help and more information about the community meeting?''
** Contact local organizer [[User:Lucadelu|Luca Delucchi]] (<tt><lucadeluge at gmail com></tt>) or [[User:wenzeslaus|Vaclav Petras]] (<tt><wenzeslaus at gmail com></tt>) for budget questions.
* ''What if I can't spend time on this?''
** Can you spend money instead? [https://numfocus.org/donate-to-grass Donate to GRASS through NumFOCUS] to help keep the project going.

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2026]]

Talk:GRASS Community Meeting San Michele 2026

2026-07-14T09:08:59Z

Annakrat: /* Anna Petrasova */

GRASS Community Meeting San Michele 2026

2026-07-14T06:30:45Z

Annakrat: /* Agenda */

[[File:Sanmichele.png|frameless|center|1000px|San Michele all'Adige]]

{{toc|right}}

The ''GRASS Community Meeting'' for contributors and developers will be happening from '''July 11 - 19, 2026''' in [https://www.openstreetmap.org/relation/46990#map=12/46.1349/11.1947 San Michele all'Adige, Trentino, Italy].

== Sponsors ==

Sponsors make the event possible. Learn more about [https://grass.osgeo.org/contribute/sponsoring/ Sponsoring].

* [https://bhinc.com/ Bohannan Huston, Inc.]: 2,500 USD
[[File:Bohannan_Huston_Inc_Logo.png|none|left|400px|alt=Logo of Bohannan Huston, Inc.|Bohannan Huston, Inc.]]

* [https://www.osgeo.org/ OSGeo]: 2500 USD (see [https://wiki.osgeo.org/w/index.php?title=GRASS_Community_Meeting_2026:_Budget budget]]).

[[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.fossgis.de/ FOSSGIS e.V.]: 4500 EUR (approved budget contribution, [https://www.fossgis.de/wiki/F%C3%B6rderantr%C3%A4ge/GRASS_GIS_Community_Meeting_2026 request]).

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

* U.S. National Science Foundation, award 2303651 (planning and time of 3 participants).

* In-kind contributions:
** mundialis GmbH & Co. KG - personnel time (personnel time)
* Personal time and/or financial contributions:
** Edouard Choinière, Helmut Kudrnovsky, Markus Neteler, Vaclav Petras, Anna Petrasova, Corey White, Veronica Andreo
** In addition to the above contributions, many participants made special efforts to keep costs down.

== Purpose ==
The ''GRASS Community Meeting'' is a great occasion for folks to support the development by actively contributing to the project in different ways. These include source code updates, documentation (manuals, wiki, tutorials), translations, website improvements 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 project and the interfaces to QGIS, GDAL, PostGIS, R, OGC Services and others.

The focus is on GRASS maintenance, and interaction with other projects. Many maintenance tasks, infrastructure changes, and planning of large changes especially benefits from maintainers being in one place and time zone. While the specific topics highly depend on the participants, we will prioritize topics which require highly synchronous collaboration, such as the CMake build system transition and API transitions. The [https://grass.osgeo.org/news/2025_05_27_grass_dev_summit_report/ 2025 event report] gives an overview of what was achieved last year.

We do require participants to work on GRASS or connections to other projects. However, we leave them the freedom to work on what they think is the best contribution to the project given their skills and time available.

== Agenda ==

Agenda is being refined.

=== Saturday, July 11 ===

Day of arrival. Contact organizers (Luca, see FAQ below) if you are interested in individualized program or helping with organization.

=== Sunday, July 12 ===

* Hybrid meeting about 8.6.0 with Filesystem Hierarchy Standard and Jupyter in GUI updates

=== Monday, July 13 ===

* Filesystem Hierarchy Standard ([https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard FHS])
* New '''Windows build server''' needed for addon provisioning and to get rid of "windows-2022 build and tests" (<code>ERROR: Cannot open URL <http://wingrass.fsv.cvut.cz/grass85/addons/grass-8.5.1dev/r.stream.distance.zip>: HTTP Error 404: Not Found</code>)
* Call with remote participants on GUI topics ([https://github.com/OSGeo/grass/issues/7614 #7614] and others)

=== Tuesday, July 14 ===

* [[GSoC]] ([https://ncsu.zoom.us/j/91637696963?pwd=7GFdlbLPvCsxzkggmwHt6QarJELMcq.1 zoom link])
* GeoAI
* Updating the GRASS Roadmap

=== Wednesday, July 15 ===

* Python API review
* Plan [[PSC]] elections

=== Thursday, July 16 ===

* Reducing PR backlog

=== Friday, July 17 ===

* Address issues for the upcoming [https://github.com/OSGeo/grass/milestone/29 8.6.0 release]

=== Saturday, July 18 ===

* Website review: fix the serious bootstrap mixup and broken sitemap bugs

=== Sunday, July 19 ===

Day of departure.

== Participation ==

Please add your name here:

{|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:Lucadelu|Luca Delucchi]]
| Italy
|
|
|
|
|-
|2
| [[User:wenzeslaus|Vaclav Petras]]
| United States
| 11.07.
| 19.07.
| grass.tools, pytest, subcommands, reviews
|
|-
|3
| [[User:Annakrat|Anna Petrasova]]
| United States
| 11.07.
| 19.07.
| GSoC, reviews, PR backlog, tutorials
|
|-
|4
| [[User:Neteler|Markus Neteler]]
| Germany
| 06.07.
| 18.07.
| documentation, website, state of GRASS support in QGIS 3.x/4.x, knowledge-transfer
|
|-
|5
| [[User:Sbl|Stefan Blumentrath]]
| Norway
| 11.07. (presumably)
| 18.07. (presumably)
| Handling Copernicus data with GRASS / actinia
|
|-
|6
| [[User:Hellik|Helmut Kudrnovsky]]
| Austria
|
|
|
|
|-
|7
| [[User:Veroandreo|Verónica Andreo]]
| Argentina
| 11.07.
| 19.07.
|
|
|-
|8
| [[User:Ctwhite|Corey White]]
| United States
| 11.07.
| 19.07.
| grass.jupyter, documentation, website, reviews, tutorials
|
|-
|9
| [[User:Echoix|Edouard Choinière]]
| Canada
| 11.07. (presumably)
| 19.07. (presumably)
| Reviews, CI, pytest, Windows GUI, i18n, undecided
|
|-
|10
| [[User:Mazingaro|Alen Mangafić]]
| Slovenia
| 13.07.
| 17.07.
| i.hyper: [https://grass.osgeo.org/grass-stable/manuals/addons/i.hyper.html Road Map] fulfilling; State of GRASS @FOSS4G 2026
|
|-
|11
| Tomaž Žagar
| Slovenia
| 13.07.
| 17.07.
| i.hyper: [https://grass.osgeo.org/grass-stable/manuals/addons/i.hyper.html Road Map] fulfilling
|
|-
|12
| Matjaž Krebs
| Slovenia
| 13.07.
| 17.07.
| i.hyper: [https://grass.osgeo.org/grass-stable/manuals/addons/i.hyper.html Road Map] fulfilling
|
|-
|13
| Christian Braun
| Luxembourg
| 13.07.
| 16.07.
| Reviews, documentation
|
|-
|}

Registration is free; participants cover their own travel and lodging (see below), often with employer support — thank you. Ideally we'd reimburse everyone, and every [https://numfocus.org/donate-to-grass donation] or [https://grass.osgeo.org/contribute/sponsoring/ employer sponsorship] of the project helps us get closer.

== Venue ==
The meeting will be hosted at [https://fmach.it/ Fondazione Edmund Mach] (FEM) in San Michele all'Adige, Trentino, Italy — about 15 km north of Trento. FEM is a research and education center with on-site facilities that allow participants to work, sleep, and eat in the same location.

[https://maps.app.goo.gl/5YEuEts6qXvky7HD9 Map]

=== Getting there ===

San Michele all'Adige is reachable by train on the Trento–Bolzano line (Trento or Mezzocorona station), with frequent connections from Trento (~15 minutes) and Verona (~1 hour). The nearest airports are Verona (VRN), Venice Marco Polo (VCE) and Treviso (TSF), Milan Bergamo (BGY), Malpensa (MXP), and Linate (LIN), Bologna (BLQ), and Innsbruck (INN) in Austria. Trento is also the host city of FOSS4G Italy 2026 (July 9–11), making it convenient to combine both events.

From Trento main train station you need to move to Ferrovia Trento-Malè (FTM) train station (few minutes by walk, https://www.openstreetmap.org/#map=17/46.072739/11.120814) and there take a train to Grumo/San Michele all'Adige. Train timetable is [https://www.trentinotrasporti.it/images/allegati/ferrovia/ftm/FTM%20est2026%20-%20ANDATA.pdf here], the opposite way is [https://www.trentinotrasporti.it/images/allegati/ferrovia/ftm/FTM%20est2026%20-%20RITORNO.pdf this one]

Another possibility is to arrive with the main train (Ferrovie dello Stato) in Mezzocorona and here you can walk to San Michele (around 20 minutes by walk) or take the small train Trento-Malè from Mezzocorona Ferrovia station (in front of main train station https://www.openstreetmap.org/#map=18/46.206633/11.128024) and stop in Grumo/San Michele (you need to look for the [https://www.trentinotrasporti.it/images/allegati/ferrovia/ftm/FTM%20est2026%20-%20RITORNO.pdf way back schedule])

== Accommodation and Costs ==

''Registration is free''. However, participants should plan for the following costs:

* Travel
* Lodging

Participants can stay on-site at the FEM convitto (dormitory), keeping the community together for the full duration of the meeting:

* €35 per person per night
* Double and triple rooms (triples include a small kitchen)
* A mandatory on-site supervisor is required at €200 per night (flat fee, shared across the group)
* Family members are welcome to stay in the dormitory as well
* [https://cif.fmach.it/content/download/2701/78358/file/brochure_convitto.pdf Brochure]
* For '''lodging booking''' options: see [https://grasscommunitymeeting2026.eventbrite.it/ Eventbrite]

For anyone preferring alternative lodging, hotels and B&Bs are available in San Michele and nearby Trento.

Lunches on weekdays can be taken at the FEM canteen (mensa), located on the same campus. Details and pricing are being finalized.

== Individual Preparation ==

* Bring your own computer
* Bring {{wikipedia|AC power plugs and sockets|power adapter}} if needed (Italy: 230V, 50Hz, {{wikipedia|Europlug|Type C}}, {{wikipedia|Schuko|Type F}}, and {{wikipedia|AC power plugs and sockets: L|Type L}} sockets are common)
* Install git and the compiler tools, and come with a working GRASS development environment if possible. See [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md here] for details.

== FAQ ==

* ''Is this a conference?''
** Talks or presentations may be included, but the purpose is to work together on the project. Among conference formats, the closest comparison would be a participatory workshop.
* ''Is this a hackathon?''
** While there is plenty of intensive coding, the meeting is not competitive. We meet to collaborate.
* ''Is the GRASS Community Meeting for developers only?''
** No, the meeting is open to all users, supporters, contributors, power users, and developers ''who want to make a meaningful contribution to the project''.
* ''What skills do I need?''
** Coding skills are not required. Contributions to documentation, tutorials, translations, website, and testing are all valuable. Practical help during the meeting, such as coordinating meals, photography, or reporting, is a real contribution too.
* ''Can I attend remotely?''
** The meeting is in-person, but everyone is welcome to use the same week for focused work on the project from wherever they are.
* ''What language is used during the meeting?''
** English is the working language, but you may hear several other languages spoken at the event.
* ''How was it last time?''
** Splendid! See [[GRASS Developer Summit Raleigh 2025]]!
* ''Where can I get help and more information about the community meeting?''
** Contact local organizer [[User:Lucadelu|Luca Delucchi]] (<tt><lucadeluge at gmail com></tt>) or [[User:wenzeslaus|Vaclav Petras]] (<tt><wenzeslaus at gmail com></tt>) for budget questions.
* ''What if I can't spend time on this?''
** Can you spend money instead? [https://numfocus.org/donate-to-grass Donate to GRASS through NumFOCUS] to help keep the project going.

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2026]]

GRASS Community Meeting San Michele 2026

2026-07-13T16:09:37Z

Annakrat: /* Tuesday, July 14 */

[[File:Sanmichele.png|frameless|center|1000px|San Michele all'Adige]]

{{toc|right}}

The ''GRASS Community Meeting'' for contributors and developers will be happening from '''July 11 - 19, 2026''' in [https://www.openstreetmap.org/relation/46990#map=12/46.1349/11.1947 San Michele all'Adige, Trentino, Italy].

== Sponsors ==

Sponsors make the event possible. Learn more about [https://grass.osgeo.org/contribute/sponsoring/ Sponsoring].

* [https://bhinc.com/ Bohannan Huston, Inc.]: 2,500 USD
[[File:Bohannan_Huston_Inc_Logo.png|none|left|400px|alt=Logo of Bohannan Huston, Inc.|Bohannan Huston, Inc.]]

* [https://www.osgeo.org/ OSGeo]: 2500 USD (see [https://wiki.osgeo.org/w/index.php?title=GRASS_Community_Meeting_2026:_Budget budget]]).

[[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.fossgis.de/ FOSSGIS e.V.]: 4500 EUR (approved budget contribution, [https://www.fossgis.de/wiki/F%C3%B6rderantr%C3%A4ge/GRASS_GIS_Community_Meeting_2026 request]).

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

* U.S. National Science Foundation, award 2303651 (planning and time of 3 participants).

* In-kind contributions:
** mundialis GmbH & Co. KG - personnel time (personnel time)
* Personal time and/or financial contributions:
** Edouard Choinière, Helmut Kudrnovsky, Markus Neteler, Vaclav Petras, Anna Petrasova, Corey White, Veronica Andreo
** In addition to the above contributions, many participants made special efforts to keep costs down.

== Purpose ==
The ''GRASS Community Meeting'' is a great occasion for folks to support the development by actively contributing to the project in different ways. These include source code updates, documentation (manuals, wiki, tutorials), translations, website improvements 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 project and the interfaces to QGIS, GDAL, PostGIS, R, OGC Services and others.

The focus is on GRASS maintenance, and interaction with other projects. Many maintenance tasks, infrastructure changes, and planning of large changes especially benefits from maintainers being in one place and time zone. While the specific topics highly depend on the participants, we will prioritize topics which require highly synchronous collaboration, such as the CMake build system transition and API transitions. The [https://grass.osgeo.org/news/2025_05_27_grass_dev_summit_report/ 2025 event report] gives an overview of what was achieved last year.

We do require participants to work on GRASS or connections to other projects. However, we leave them the freedom to work on what they think is the best contribution to the project given their skills and time available.

== Agenda ==

Agenda is being refined.

=== Saturday, July 11 ===

Day of arrival. Contact organizers (Luca, see FAQ below) if you are interested in individualized program or helping with organization.

=== Sunday, July 12 ===

* Hybrid meeting about 8.6.0 with Filesystem Hierarchy Standard and Jupyter in GUI updates

=== Monday, July 13 ===

* Filesystem Hierarchy Standard ([https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard FHS])
* Updating the GRASS Roadmap
* New '''Windows build server''' needed for addon provisioning and to get rid of "windows-2022 build and tests" (<code>ERROR: Cannot open URL <http://wingrass.fsv.cvut.cz/grass85/addons/grass-8.5.1dev/r.stream.distance.zip>: HTTP Error 404: Not Found</code>)
* Call with remote participants on GUI topics ([https://github.com/OSGeo/grass/issues/7614 #7614] and others)

=== Tuesday, July 14 ===

* [[GSoC]] ([https://ncsu.zoom.us/j/91637696963?pwd=7GFdlbLPvCsxzkggmwHt6QarJELMcq.1 zoom link])
* GeoAI

=== Wednesday, July 15 ===

* Python API review
* Plan [[PSC]] elections

=== Thursday, July 16 ===

* Reducing PR backlog

=== Friday, July 17 ===

* Address issues for the upcoming [https://github.com/OSGeo/grass/milestone/29 8.6.0 release]

=== Saturday, July 18 ===

* Website review: fix the serious bootstrap mixup and broken sitemap bugs

=== Sunday, July 19 ===

Day of departure.

== Participation ==

Please add your name here:

{|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:Lucadelu|Luca Delucchi]]
| Italy
|
|
|
|
|-
|2
| [[User:wenzeslaus|Vaclav Petras]]
| United States
| 11.07.
| 19.07.
| grass.tools, pytest, subcommands, reviews
|
|-
|3
| [[User:Annakrat|Anna Petrasova]]
| United States
| 11.07.
| 19.07.
| GSoC, reviews, PR backlog, tutorials
|
|-
|4
| [[User:Neteler|Markus Neteler]]
| Germany
| 06.07.
| 18.07.
| documentation, website, state of GRASS support in QGIS 3.x/4.x, knowledge-transfer
|
|-
|5
| [[User:Sbl|Stefan Blumentrath]]
| Norway
| 11.07. (presumably)
| 18.07. (presumably)
| Handling Copernicus data with GRASS / actinia
|
|-
|6
| [[User:Hellik|Helmut Kudrnovsky]]
| Austria
|
|
|
|
|-
|7
| [[User:Veroandreo|Verónica Andreo]]
| Argentina
| 11.07.
| 19.07.
|
|
|-
|8
| [[User:Ctwhite|Corey White]]
| United States
| 11.07.
| 19.07.
| grass.jupyter, documentation, website, reviews, tutorials
|
|-
|9
| [[User:Echoix|Edouard Choinière]]
| Canada
| 11.07. (presumably)
| 19.07. (presumably)
| Reviews, CI, pytest, Windows GUI, i18n, undecided
|
|-
|10
| [[User:Mazingaro|Alen Mangafić]]
| Slovenia
| 13.07.
| 17.07.
| i.hyper: [https://grass.osgeo.org/grass-stable/manuals/addons/i.hyper.html Road Map] fulfilling; State of GRASS @FOSS4G 2026
|
|-
|11
| Tomaž Žagar
| Slovenia
| 13.07.
| 17.07.
| i.hyper: [https://grass.osgeo.org/grass-stable/manuals/addons/i.hyper.html Road Map] fulfilling
|
|-
|12
| Matjaž Krebs
| Slovenia
| 13.07.
| 17.07.
| i.hyper: [https://grass.osgeo.org/grass-stable/manuals/addons/i.hyper.html Road Map] fulfilling
|
|-
|13
| Christian Braun
| Luxembourg
| 13.07.
| 16.07.
| Reviews, documentation
|
|-
|}

Registration is free; participants cover their own travel and lodging (see below), often with employer support — thank you. Ideally we'd reimburse everyone, and every [https://numfocus.org/donate-to-grass donation] or [https://grass.osgeo.org/contribute/sponsoring/ employer sponsorship] of the project helps us get closer.

== Venue ==
The meeting will be hosted at [https://fmach.it/ Fondazione Edmund Mach] (FEM) in San Michele all'Adige, Trentino, Italy — about 15 km north of Trento. FEM is a research and education center with on-site facilities that allow participants to work, sleep, and eat in the same location.

[https://maps.app.goo.gl/5YEuEts6qXvky7HD9 Map]

=== Getting there ===

San Michele all'Adige is reachable by train on the Trento–Bolzano line (Trento or Mezzocorona station), with frequent connections from Trento (~15 minutes) and Verona (~1 hour). The nearest airports are Verona (VRN), Venice Marco Polo (VCE) and Treviso (TSF), Milan Bergamo (BGY), Malpensa (MXP), and Linate (LIN), Bologna (BLQ), and Innsbruck (INN) in Austria. Trento is also the host city of FOSS4G Italy 2026 (July 9–11), making it convenient to combine both events.

From Trento main train station you need to move to Ferrovia Trento-Malè (FTM) train station (few minutes by walk, https://www.openstreetmap.org/#map=17/46.072739/11.120814) and there take a train to Grumo/San Michele all'Adige. Train timetable is [https://www.trentinotrasporti.it/images/allegati/ferrovia/ftm/FTM%20est2026%20-%20ANDATA.pdf here], the opposite way is [https://www.trentinotrasporti.it/images/allegati/ferrovia/ftm/FTM%20est2026%20-%20RITORNO.pdf this one]

Another possibility is to arrive with the main train (Ferrovie dello Stato) in Mezzocorona and here you can walk to San Michele (around 20 minutes by walk) or take the small train Trento-Malè from Mezzocorona Ferrovia station (in front of main train station https://www.openstreetmap.org/#map=18/46.206633/11.128024) and stop in Grumo/San Michele (you need to look for the [https://www.trentinotrasporti.it/images/allegati/ferrovia/ftm/FTM%20est2026%20-%20RITORNO.pdf way back schedule])

== Accommodation and Costs ==

''Registration is free''. However, participants should plan for the following costs:

* Travel
* Lodging

Participants can stay on-site at the FEM convitto (dormitory), keeping the community together for the full duration of the meeting:

* €35 per person per night
* Double and triple rooms (triples include a small kitchen)
* A mandatory on-site supervisor is required at €200 per night (flat fee, shared across the group)
* Family members are welcome to stay in the dormitory as well
* [https://cif.fmach.it/content/download/2701/78358/file/brochure_convitto.pdf Brochure]
* For '''lodging booking''' options: see [https://grasscommunitymeeting2026.eventbrite.it/ Eventbrite]

For anyone preferring alternative lodging, hotels and B&Bs are available in San Michele and nearby Trento.

Lunches on weekdays can be taken at the FEM canteen (mensa), located on the same campus. Details and pricing are being finalized.

== Individual Preparation ==

* Bring your own computer
* Bring {{wikipedia|AC power plugs and sockets|power adapter}} if needed (Italy: 230V, 50Hz, {{wikipedia|Europlug|Type C}}, {{wikipedia|Schuko|Type F}}, and {{wikipedia|AC power plugs and sockets: L|Type L}} sockets are common)
* Install git and the compiler tools, and come with a working GRASS development environment if possible. See [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md here] for details.

== FAQ ==

* ''Is this a conference?''
** Talks or presentations may be included, but the purpose is to work together on the project. Among conference formats, the closest comparison would be a participatory workshop.
* ''Is this a hackathon?''
** While there is plenty of intensive coding, the meeting is not competitive. We meet to collaborate.
* ''Is the GRASS Community Meeting for developers only?''
** No, the meeting is open to all users, supporters, contributors, power users, and developers ''who want to make a meaningful contribution to the project''.
* ''What skills do I need?''
** Coding skills are not required. Contributions to documentation, tutorials, translations, website, and testing are all valuable. Practical help during the meeting, such as coordinating meals, photography, or reporting, is a real contribution too.
* ''Can I attend remotely?''
** The meeting is in-person, but everyone is welcome to use the same week for focused work on the project from wherever they are.
* ''What language is used during the meeting?''
** English is the working language, but you may hear several other languages spoken at the event.
* ''How was it last time?''
** Splendid! See [[GRASS Developer Summit Raleigh 2025]]!
* ''Where can I get help and more information about the community meeting?''
** Contact local organizer [[User:Lucadelu|Luca Delucchi]] (<tt><lucadeluge at gmail com></tt>) or [[User:wenzeslaus|Vaclav Petras]] (<tt><wenzeslaus at gmail com></tt>) for budget questions.
* ''What if I can't spend time on this?''
** Can you spend money instead? [https://numfocus.org/donate-to-grass Donate to GRASS through NumFOCUS] to help keep the project going.

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2026]]

GRASS Community Meeting San Michele 2026

2026-07-13T16:08:41Z

Annakrat: /* Monday, July 13 */

[[File:Sanmichele.png|frameless|center|1000px|San Michele all'Adige]]

{{toc|right}}

The ''GRASS Community Meeting'' for contributors and developers will be happening from '''July 11 - 19, 2026''' in [https://www.openstreetmap.org/relation/46990#map=12/46.1349/11.1947 San Michele all'Adige, Trentino, Italy].

== Sponsors ==

Sponsors make the event possible. Learn more about [https://grass.osgeo.org/contribute/sponsoring/ Sponsoring].

* [https://bhinc.com/ Bohannan Huston, Inc.]: 2,500 USD
[[File:Bohannan_Huston_Inc_Logo.png|none|left|400px|alt=Logo of Bohannan Huston, Inc.|Bohannan Huston, Inc.]]

* [https://www.osgeo.org/ OSGeo]: 2500 USD (see [https://wiki.osgeo.org/w/index.php?title=GRASS_Community_Meeting_2026:_Budget budget]]).

[[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.fossgis.de/ FOSSGIS e.V.]: 4500 EUR (approved budget contribution, [https://www.fossgis.de/wiki/F%C3%B6rderantr%C3%A4ge/GRASS_GIS_Community_Meeting_2026 request]).

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

* U.S. National Science Foundation, award 2303651 (planning and time of 3 participants).

* In-kind contributions:
** mundialis GmbH & Co. KG - personnel time (personnel time)
* Personal time and/or financial contributions:
** Edouard Choinière, Helmut Kudrnovsky, Markus Neteler, Vaclav Petras, Anna Petrasova, Corey White, Veronica Andreo
** In addition to the above contributions, many participants made special efforts to keep costs down.

== Purpose ==
The ''GRASS Community Meeting'' is a great occasion for folks to support the development by actively contributing to the project in different ways. These include source code updates, documentation (manuals, wiki, tutorials), translations, website improvements 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 project and the interfaces to QGIS, GDAL, PostGIS, R, OGC Services and others.

The focus is on GRASS maintenance, and interaction with other projects. Many maintenance tasks, infrastructure changes, and planning of large changes especially benefits from maintainers being in one place and time zone. While the specific topics highly depend on the participants, we will prioritize topics which require highly synchronous collaboration, such as the CMake build system transition and API transitions. The [https://grass.osgeo.org/news/2025_05_27_grass_dev_summit_report/ 2025 event report] gives an overview of what was achieved last year.

We do require participants to work on GRASS or connections to other projects. However, we leave them the freedom to work on what they think is the best contribution to the project given their skills and time available.

== Agenda ==

Agenda is being refined.

=== Saturday, July 11 ===

Day of arrival. Contact organizers (Luca, see FAQ below) if you are interested in individualized program or helping with organization.

=== Sunday, July 12 ===

* Hybrid meeting about 8.6.0 with Filesystem Hierarchy Standard and Jupyter in GUI updates

=== Monday, July 13 ===

* Filesystem Hierarchy Standard ([https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard FHS])
* Updating the GRASS Roadmap
* New '''Windows build server''' needed for addon provisioning and to get rid of "windows-2022 build and tests" (<code>ERROR: Cannot open URL <http://wingrass.fsv.cvut.cz/grass85/addons/grass-8.5.1dev/r.stream.distance.zip>: HTTP Error 404: Not Found</code>)
* Call with remote participants on GUI topics ([https://github.com/OSGeo/grass/issues/7614 #7614] and others)

=== Tuesday, July 14 ===

* [[GSoC]] (may be moved to different day)
* GeoAI

=== Wednesday, July 15 ===

* Python API review
* Plan [[PSC]] elections

=== Thursday, July 16 ===

* Reducing PR backlog

=== Friday, July 17 ===

* Address issues for the upcoming [https://github.com/OSGeo/grass/milestone/29 8.6.0 release]

=== Saturday, July 18 ===

* Website review: fix the serious bootstrap mixup and broken sitemap bugs

=== Sunday, July 19 ===

Day of departure.

== Participation ==

Please add your name here:

{|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:Lucadelu|Luca Delucchi]]
| Italy
|
|
|
|
|-
|2
| [[User:wenzeslaus|Vaclav Petras]]
| United States
| 11.07.
| 19.07.
| grass.tools, pytest, subcommands, reviews
|
|-
|3
| [[User:Annakrat|Anna Petrasova]]
| United States
| 11.07.
| 19.07.
| GSoC, reviews, PR backlog, tutorials
|
|-
|4
| [[User:Neteler|Markus Neteler]]
| Germany
| 06.07.
| 18.07.
| documentation, website, state of GRASS support in QGIS 3.x/4.x, knowledge-transfer
|
|-
|5
| [[User:Sbl|Stefan Blumentrath]]
| Norway
| 11.07. (presumably)
| 18.07. (presumably)
| Handling Copernicus data with GRASS / actinia
|
|-
|6
| [[User:Hellik|Helmut Kudrnovsky]]
| Austria
|
|
|
|
|-
|7
| [[User:Veroandreo|Verónica Andreo]]
| Argentina
| 11.07.
| 19.07.
|
|
|-
|8
| [[User:Ctwhite|Corey White]]
| United States
| 11.07.
| 19.07.
| grass.jupyter, documentation, website, reviews, tutorials
|
|-
|9
| [[User:Echoix|Edouard Choinière]]
| Canada
| 11.07. (presumably)
| 19.07. (presumably)
| Reviews, CI, pytest, Windows GUI, i18n, undecided
|
|-
|10
| [[User:Mazingaro|Alen Mangafić]]
| Slovenia
| 13.07.
| 17.07.
| i.hyper: [https://grass.osgeo.org/grass-stable/manuals/addons/i.hyper.html Road Map] fulfilling; State of GRASS @FOSS4G 2026
|
|-
|11
| Tomaž Žagar
| Slovenia
| 13.07.
| 17.07.
| i.hyper: [https://grass.osgeo.org/grass-stable/manuals/addons/i.hyper.html Road Map] fulfilling
|
|-
|12
| Matjaž Krebs
| Slovenia
| 13.07.
| 17.07.
| i.hyper: [https://grass.osgeo.org/grass-stable/manuals/addons/i.hyper.html Road Map] fulfilling
|
|-
|13
| Christian Braun
| Luxembourg
| 13.07.
| 16.07.
| Reviews, documentation
|
|-
|}

Registration is free; participants cover their own travel and lodging (see below), often with employer support — thank you. Ideally we'd reimburse everyone, and every [https://numfocus.org/donate-to-grass donation] or [https://grass.osgeo.org/contribute/sponsoring/ employer sponsorship] of the project helps us get closer.

== Venue ==
The meeting will be hosted at [https://fmach.it/ Fondazione Edmund Mach] (FEM) in San Michele all'Adige, Trentino, Italy — about 15 km north of Trento. FEM is a research and education center with on-site facilities that allow participants to work, sleep, and eat in the same location.

[https://maps.app.goo.gl/5YEuEts6qXvky7HD9 Map]

=== Getting there ===

San Michele all'Adige is reachable by train on the Trento–Bolzano line (Trento or Mezzocorona station), with frequent connections from Trento (~15 minutes) and Verona (~1 hour). The nearest airports are Verona (VRN), Venice Marco Polo (VCE) and Treviso (TSF), Milan Bergamo (BGY), Malpensa (MXP), and Linate (LIN), Bologna (BLQ), and Innsbruck (INN) in Austria. Trento is also the host city of FOSS4G Italy 2026 (July 9–11), making it convenient to combine both events.

From Trento main train station you need to move to Ferrovia Trento-Malè (FTM) train station (few minutes by walk, https://www.openstreetmap.org/#map=17/46.072739/11.120814) and there take a train to Grumo/San Michele all'Adige. Train timetable is [https://www.trentinotrasporti.it/images/allegati/ferrovia/ftm/FTM%20est2026%20-%20ANDATA.pdf here], the opposite way is [https://www.trentinotrasporti.it/images/allegati/ferrovia/ftm/FTM%20est2026%20-%20RITORNO.pdf this one]

Another possibility is to arrive with the main train (Ferrovie dello Stato) in Mezzocorona and here you can walk to San Michele (around 20 minutes by walk) or take the small train Trento-Malè from Mezzocorona Ferrovia station (in front of main train station https://www.openstreetmap.org/#map=18/46.206633/11.128024) and stop in Grumo/San Michele (you need to look for the [https://www.trentinotrasporti.it/images/allegati/ferrovia/ftm/FTM%20est2026%20-%20RITORNO.pdf way back schedule])

== Accommodation and Costs ==

''Registration is free''. However, participants should plan for the following costs:

* Travel
* Lodging

Participants can stay on-site at the FEM convitto (dormitory), keeping the community together for the full duration of the meeting:

* €35 per person per night
* Double and triple rooms (triples include a small kitchen)
* A mandatory on-site supervisor is required at €200 per night (flat fee, shared across the group)
* Family members are welcome to stay in the dormitory as well
* [https://cif.fmach.it/content/download/2701/78358/file/brochure_convitto.pdf Brochure]
* For '''lodging booking''' options: see [https://grasscommunitymeeting2026.eventbrite.it/ Eventbrite]

For anyone preferring alternative lodging, hotels and B&Bs are available in San Michele and nearby Trento.

Lunches on weekdays can be taken at the FEM canteen (mensa), located on the same campus. Details and pricing are being finalized.

== Individual Preparation ==

* Bring your own computer
* Bring {{wikipedia|AC power plugs and sockets|power adapter}} if needed (Italy: 230V, 50Hz, {{wikipedia|Europlug|Type C}}, {{wikipedia|Schuko|Type F}}, and {{wikipedia|AC power plugs and sockets: L|Type L}} sockets are common)
* Install git and the compiler tools, and come with a working GRASS development environment if possible. See [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md here] for details.

== FAQ ==

* ''Is this a conference?''
** Talks or presentations may be included, but the purpose is to work together on the project. Among conference formats, the closest comparison would be a participatory workshop.
* ''Is this a hackathon?''
** While there is plenty of intensive coding, the meeting is not competitive. We meet to collaborate.
* ''Is the GRASS Community Meeting for developers only?''
** No, the meeting is open to all users, supporters, contributors, power users, and developers ''who want to make a meaningful contribution to the project''.
* ''What skills do I need?''
** Coding skills are not required. Contributions to documentation, tutorials, translations, website, and testing are all valuable. Practical help during the meeting, such as coordinating meals, photography, or reporting, is a real contribution too.
* ''Can I attend remotely?''
** The meeting is in-person, but everyone is welcome to use the same week for focused work on the project from wherever they are.
* ''What language is used during the meeting?''
** English is the working language, but you may hear several other languages spoken at the event.
* ''How was it last time?''
** Splendid! See [[GRASS Developer Summit Raleigh 2025]]!
* ''Where can I get help and more information about the community meeting?''
** Contact local organizer [[User:Lucadelu|Luca Delucchi]] (<tt><lucadeluge at gmail com></tt>) or [[User:wenzeslaus|Vaclav Petras]] (<tt><wenzeslaus at gmail com></tt>) for budget questions.
* ''What if I can't spend time on this?''
** Can you spend money instead? [https://numfocus.org/donate-to-grass Donate to GRASS through NumFOCUS] to help keep the project going.

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2026]]

Talk:GRASS Community Meeting San Michele 2026

2026-07-13T15:39:39Z

Annakrat: /* Jul 13 */

GRASS Community Meeting San Michele 2026

2026-07-13T13:31:01Z

Annakrat: /* Monday, July 13 */

[[File:Sanmichele.png|frameless|center|1000px|San Michele all'Adige]]

{{toc|right}}

The ''GRASS Community Meeting'' for contributors and developers will be happening from '''July 11 - 19, 2026''' in [https://www.openstreetmap.org/relation/46990#map=12/46.1349/11.1947 San Michele all'Adige, Trentino, Italy].

== Sponsors ==

Sponsors make the event possible. Learn more about [https://grass.osgeo.org/contribute/sponsoring/ Sponsoring].

* [https://bhinc.com/ Bohannan Huston, Inc.]: 2,500 USD
[[File:Bohannan_Huston_Inc_Logo.png|none|left|400px|alt=Logo of Bohannan Huston, Inc.|Bohannan Huston, Inc.]]

* [https://www.osgeo.org/ OSGeo]: 2500 USD (see [https://wiki.osgeo.org/w/index.php?title=GRASS_Community_Meeting_2026:_Budget budget]]).

[[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.fossgis.de/ FOSSGIS e.V.]: 4500 EUR (approved budget contribution, [https://www.fossgis.de/wiki/F%C3%B6rderantr%C3%A4ge/GRASS_GIS_Community_Meeting_2026 request]).

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

* U.S. National Science Foundation, award 2303651 (planning and time of 3 participants).

* In-kind contributions:
** mundialis GmbH & Co. KG - personnel time (personnel time)
* Personal time and/or financial contributions:
** Edouard Choinière, Helmut Kudrnovsky, Markus Neteler, Vaclav Petras, Anna Petrasova, Corey White, Veronica Andreo
** In addition to the above contributions, many participants made special efforts to keep costs down.

== Purpose ==
The ''GRASS Community Meeting'' is a great occasion for folks to support the development by actively contributing to the project in different ways. These include source code updates, documentation (manuals, wiki, tutorials), translations, website improvements 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 project and the interfaces to QGIS, GDAL, PostGIS, R, OGC Services and others.

The focus is on GRASS maintenance, and interaction with other projects. Many maintenance tasks, infrastructure changes, and planning of large changes especially benefits from maintainers being in one place and time zone. While the specific topics highly depend on the participants, we will prioritize topics which require highly synchronous collaboration, such as the CMake build system transition and API transitions. The [https://grass.osgeo.org/news/2025_05_27_grass_dev_summit_report/ 2025 event report] gives an overview of what was achieved last year.

We do require participants to work on GRASS or connections to other projects. However, we leave them the freedom to work on what they think is the best contribution to the project given their skills and time available.

== Agenda ==

Agenda is being refined.

=== Saturday, July 11 ===

Day of arrival. Contact organizers (Luca, see FAQ below) if you are interested in individualized program or helping with organization.

=== Sunday, July 12 ===

* Hybrid meeting about 8.6.0 with Filesystem Hierarchy Standard and Jupyter in GUI updates

=== Monday, July 13 ===

* Filesystem Hierarchy Standard ([https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard FHS])
* Updating the GRASS Roadmap
* New '''Windows build server''' needed for addon provisioning and to get rid of "windows-2022 build and tests" (<code>ERROR: Cannot open URL <http://wingrass.fsv.cvut.cz/grass85/addons/grass-8.5.1dev/r.stream.distance.zip>: HTTP Error 404: Not Found</code>)
* Call with remote participants on GUI topics ([https://github.com/OSGeo/grass/issues/7614 #7614] and others): [https://ncsu.zoom.us/j/91637696963?pwd=7GFdlbLPvCsxzkggmwHt6QarJELMcq.1 zoom link]

=== Tuesday, July 14 ===

* [[GSoC]] (may be moved to different day)
* GeoAI

=== Wednesday, July 15 ===

* Python API review
* Plan [[PSC]] elections

=== Thursday, July 16 ===

* Reducing PR backlog

=== Friday, July 17 ===

* Address issues for the upcoming [https://github.com/OSGeo/grass/milestone/29 8.6.0 release]

=== Saturday, July 18 ===

* Website review: fix the serious bootstrap mixup and broken sitemap bugs

=== Sunday, July 19 ===

Day of departure.

== Participation ==

Please add your name here:

{|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:Lucadelu|Luca Delucchi]]
| Italy
|
|
|
|
|-
|2
| [[User:wenzeslaus|Vaclav Petras]]
| United States
| 11.07.
| 19.07.
| grass.tools, pytest, subcommands, reviews
|
|-
|3
| [[User:Annakrat|Anna Petrasova]]
| United States
| 11.07.
| 19.07.
| GSoC, reviews, PR backlog, tutorials
|
|-
|4
| [[User:Neteler|Markus Neteler]]
| Germany
| 06.07.
| 18.07.
| documentation, website, state of GRASS support in QGIS 3.x/4.x, knowledge-transfer
|
|-
|5
| [[User:Sbl|Stefan Blumentrath]]
| Norway
| 11.07. (presumably)
| 18.07. (presumably)
| Handling Copernicus data with GRASS / actinia
|
|-
|6
| [[User:Hellik|Helmut Kudrnovsky]]
| Austria
|
|
|
|
|-
|7
| [[User:Veroandreo|Verónica Andreo]]
| Argentina
| 11.07.
| 19.07.
|
|
|-
|8
| [[User:Ctwhite|Corey White]]
| United States
| 11.07.
| 19.07.
| grass.jupyter, documentation, website, reviews, tutorials
|
|-
|9
| [[User:Echoix|Edouard Choinière]]
| Canada
| 11.07. (presumably)
| 19.07. (presumably)
| Reviews, CI, pytest, Windows GUI, i18n, undecided
|
|-
|10
| [[User:Mazingaro|Alen Mangafić]]
| Slovenia
| 13.07.
| 17.07.
| i.hyper: [https://grass.osgeo.org/grass-stable/manuals/addons/i.hyper.html Road Map] fulfilling; State of GRASS @FOSS4G 2026
|
|-
|11
| Tomaž Žagar
| Slovenia
| 13.07.
| 17.07.
| i.hyper: [https://grass.osgeo.org/grass-stable/manuals/addons/i.hyper.html Road Map] fulfilling
|
|-
|12
| Matjaž Krebs
| Slovenia
| 13.07.
| 17.07.
| i.hyper: [https://grass.osgeo.org/grass-stable/manuals/addons/i.hyper.html Road Map] fulfilling
|
|-
|13
| Christian Braun
| Luxembourg
| 13.07.
| 16.07.
| Reviews, documentation
|
|-
|}

Registration is free; participants cover their own travel and lodging (see below), often with employer support — thank you. Ideally we'd reimburse everyone, and every [https://numfocus.org/donate-to-grass donation] or [https://grass.osgeo.org/contribute/sponsoring/ employer sponsorship] of the project helps us get closer.

== Venue ==
The meeting will be hosted at [https://fmach.it/ Fondazione Edmund Mach] (FEM) in San Michele all'Adige, Trentino, Italy — about 15 km north of Trento. FEM is a research and education center with on-site facilities that allow participants to work, sleep, and eat in the same location.

[https://maps.app.goo.gl/5YEuEts6qXvky7HD9 Map]

=== Getting there ===

San Michele all'Adige is reachable by train on the Trento–Bolzano line (Trento or Mezzocorona station), with frequent connections from Trento (~15 minutes) and Verona (~1 hour). The nearest airports are Verona (VRN), Venice Marco Polo (VCE) and Treviso (TSF), Milan Bergamo (BGY), Malpensa (MXP), and Linate (LIN), Bologna (BLQ), and Innsbruck (INN) in Austria. Trento is also the host city of FOSS4G Italy 2026 (July 9–11), making it convenient to combine both events.

From Trento main train station you need to move to Ferrovia Trento-Malè (FTM) train station (few minutes by walk, https://www.openstreetmap.org/#map=17/46.072739/11.120814) and there take a train to Grumo/San Michele all'Adige. Train timetable is [https://www.trentinotrasporti.it/images/allegati/ferrovia/ftm/FTM%20est2026%20-%20ANDATA.pdf here], the opposite way is [https://www.trentinotrasporti.it/images/allegati/ferrovia/ftm/FTM%20est2026%20-%20RITORNO.pdf this one]

Another possibility is to arrive with the main train (Ferrovie dello Stato) in Mezzocorona and here you can walk to San Michele (around 20 minutes by walk) or take the small train Trento-Malè from Mezzocorona Ferrovia station (in front of main train station https://www.openstreetmap.org/#map=18/46.206633/11.128024) and stop in Grumo/San Michele (you need to look for the [https://www.trentinotrasporti.it/images/allegati/ferrovia/ftm/FTM%20est2026%20-%20RITORNO.pdf way back schedule])

== Accommodation and Costs ==

''Registration is free''. However, participants should plan for the following costs:

* Travel
* Lodging

Participants can stay on-site at the FEM convitto (dormitory), keeping the community together for the full duration of the meeting:

* €35 per person per night
* Double and triple rooms (triples include a small kitchen)
* A mandatory on-site supervisor is required at €200 per night (flat fee, shared across the group)
* Family members are welcome to stay in the dormitory as well
* [https://cif.fmach.it/content/download/2701/78358/file/brochure_convitto.pdf Brochure]
* For '''lodging booking''' options: see [https://grasscommunitymeeting2026.eventbrite.it/ Eventbrite]

For anyone preferring alternative lodging, hotels and B&Bs are available in San Michele and nearby Trento.

Lunches on weekdays can be taken at the FEM canteen (mensa), located on the same campus. Details and pricing are being finalized.

== Individual Preparation ==

* Bring your own computer
* Bring {{wikipedia|AC power plugs and sockets|power adapter}} if needed (Italy: 230V, 50Hz, {{wikipedia|Europlug|Type C}}, {{wikipedia|Schuko|Type F}}, and {{wikipedia|AC power plugs and sockets: L|Type L}} sockets are common)
* Install git and the compiler tools, and come with a working GRASS development environment if possible. See [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md here] for details.

== FAQ ==

* ''Is this a conference?''
** Talks or presentations may be included, but the purpose is to work together on the project. Among conference formats, the closest comparison would be a participatory workshop.
* ''Is this a hackathon?''
** While there is plenty of intensive coding, the meeting is not competitive. We meet to collaborate.
* ''Is the GRASS Community Meeting for developers only?''
** No, the meeting is open to all users, supporters, contributors, power users, and developers ''who want to make a meaningful contribution to the project''.
* ''What skills do I need?''
** Coding skills are not required. Contributions to documentation, tutorials, translations, website, and testing are all valuable. Practical help during the meeting, such as coordinating meals, photography, or reporting, is a real contribution too.
* ''Can I attend remotely?''
** The meeting is in-person, but everyone is welcome to use the same week for focused work on the project from wherever they are.
* ''What language is used during the meeting?''
** English is the working language, but you may hear several other languages spoken at the event.
* ''How was it last time?''
** Splendid! See [[GRASS Developer Summit Raleigh 2025]]!
* ''Where can I get help and more information about the community meeting?''
** Contact local organizer [[User:Lucadelu|Luca Delucchi]] (<tt><lucadeluge at gmail com></tt>) or [[User:wenzeslaus|Vaclav Petras]] (<tt><wenzeslaus at gmail com></tt>) for budget questions.
* ''What if I can't spend time on this?''
** Can you spend money instead? [https://numfocus.org/donate-to-grass Donate to GRASS through NumFOCUS] to help keep the project going.

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2026]]

GRASS Community Meeting San Michele 2026

2026-07-13T13:27:55Z

Annakrat: /* Monday, July 13 */

[[File:Sanmichele.png|frameless|center|1000px|San Michele all'Adige]]

{{toc|right}}

The ''GRASS Community Meeting'' for contributors and developers will be happening from '''July 11 - 19, 2026''' in [https://www.openstreetmap.org/relation/46990#map=12/46.1349/11.1947 San Michele all'Adige, Trentino, Italy].

== Sponsors ==

Sponsors make the event possible. Learn more about [https://grass.osgeo.org/contribute/sponsoring/ Sponsoring].

* [https://bhinc.com/ Bohannan Huston, Inc.]: 2,500 USD
[[File:Bohannan_Huston_Inc_Logo.png|none|left|400px|alt=Logo of Bohannan Huston, Inc.|Bohannan Huston, Inc.]]

* [https://www.osgeo.org/ OSGeo]: 2500 USD (see [https://wiki.osgeo.org/w/index.php?title=GRASS_Community_Meeting_2026:_Budget budget]]).

[[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.fossgis.de/ FOSSGIS e.V.]: 4500 EUR (approved budget contribution, [https://www.fossgis.de/wiki/F%C3%B6rderantr%C3%A4ge/GRASS_GIS_Community_Meeting_2026 request]).

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

* U.S. National Science Foundation, award 2303651 (planning and time of 3 participants).

* In-kind contributions:
** mundialis GmbH & Co. KG - personnel time (personnel time)
* Personal time and/or financial contributions:
** Edouard Choinière, Helmut Kudrnovsky, Markus Neteler, Vaclav Petras, Anna Petrasova, Corey White, Veronica Andreo
** In addition to the above contributions, many participants made special efforts to keep costs down.

== Purpose ==
The ''GRASS Community Meeting'' is a great occasion for folks to support the development by actively contributing to the project in different ways. These include source code updates, documentation (manuals, wiki, tutorials), translations, website improvements 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 project and the interfaces to QGIS, GDAL, PostGIS, R, OGC Services and others.

The focus is on GRASS maintenance, and interaction with other projects. Many maintenance tasks, infrastructure changes, and planning of large changes especially benefits from maintainers being in one place and time zone. While the specific topics highly depend on the participants, we will prioritize topics which require highly synchronous collaboration, such as the CMake build system transition and API transitions. The [https://grass.osgeo.org/news/2025_05_27_grass_dev_summit_report/ 2025 event report] gives an overview of what was achieved last year.

We do require participants to work on GRASS or connections to other projects. However, we leave them the freedom to work on what they think is the best contribution to the project given their skills and time available.

== Agenda ==

Agenda is being refined.

=== Saturday, July 11 ===

Day of arrival. Contact organizers (Luca, see FAQ below) if you are interested in individualized program or helping with organization.

=== Sunday, July 12 ===

* Hybrid meeting about 8.6.0 with Filesystem Hierarchy Standard and Jupyter in GUI updates

=== Monday, July 13 ===

* Filesystem Hierarchy Standard ([https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard FHS])
* Updating the GRASS Roadmap
* New '''Windows build server''' needed for addon provisioning and to get rid of "windows-2022 build and tests" (<code>ERROR: Cannot open URL <http://wingrass.fsv.cvut.cz/grass85/addons/grass-8.5.1dev/r.stream.distance.zip>: HTTP Error 404: Not Found</code>)
* Call with remote participants on GUI topics: [https://ncsu.zoom.us/j/91637696963?pwd=7GFdlbLPvCsxzkggmwHt6QarJELMcq.1 zoom link]

=== Tuesday, July 14 ===

* [[GSoC]] (may be moved to different day)
* GeoAI

=== Wednesday, July 15 ===

* Python API review
* Plan [[PSC]] elections

=== Thursday, July 16 ===

* Reducing PR backlog

=== Friday, July 17 ===

* Address issues for the upcoming [https://github.com/OSGeo/grass/milestone/29 8.6.0 release]

=== Saturday, July 18 ===

* Website review: fix the serious bootstrap mixup and broken sitemap bugs

=== Sunday, July 19 ===

Day of departure.

== Participation ==

Please add your name here:

{|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:Lucadelu|Luca Delucchi]]
| Italy
|
|
|
|
|-
|2
| [[User:wenzeslaus|Vaclav Petras]]
| United States
| 11.07.
| 19.07.
| grass.tools, pytest, subcommands, reviews
|
|-
|3
| [[User:Annakrat|Anna Petrasova]]
| United States
| 11.07.
| 19.07.
| GSoC, reviews, PR backlog, tutorials
|
|-
|4
| [[User:Neteler|Markus Neteler]]
| Germany
| 06.07.
| 18.07.
| documentation, website, state of GRASS support in QGIS 3.x/4.x, knowledge-transfer
|
|-
|5
| [[User:Sbl|Stefan Blumentrath]]
| Norway
| 11.07. (presumably)
| 18.07. (presumably)
| Handling Copernicus data with GRASS / actinia
|
|-
|6
| [[User:Hellik|Helmut Kudrnovsky]]
| Austria
|
|
|
|
|-
|7
| [[User:Veroandreo|Verónica Andreo]]
| Argentina
| 11.07.
| 19.07.
|
|
|-
|8
| [[User:Ctwhite|Corey White]]
| United States
| 11.07.
| 19.07.
| grass.jupyter, documentation, website, reviews, tutorials
|
|-
|9
| [[User:Echoix|Edouard Choinière]]
| Canada
| 11.07. (presumably)
| 19.07. (presumably)
| Reviews, CI, pytest, Windows GUI, i18n, undecided
|
|-
|10
| [[User:Mazingaro|Alen Mangafić]]
| Slovenia
| 13.07.
| 17.07.
| i.hyper: [https://grass.osgeo.org/grass-stable/manuals/addons/i.hyper.html Road Map] fulfilling; State of GRASS @FOSS4G 2026
|
|-
|11
| Tomaž Žagar
| Slovenia
| 13.07.
| 17.07.
| i.hyper: [https://grass.osgeo.org/grass-stable/manuals/addons/i.hyper.html Road Map] fulfilling
|
|-
|12
| Matjaž Krebs
| Slovenia
| 13.07.
| 17.07.
| i.hyper: [https://grass.osgeo.org/grass-stable/manuals/addons/i.hyper.html Road Map] fulfilling
|
|-
|13
| Christian Braun
| Luxembourg
| 13.07.
| 16.07.
| Reviews, documentation
|
|-
|}

Registration is free; participants cover their own travel and lodging (see below), often with employer support — thank you. Ideally we'd reimburse everyone, and every [https://numfocus.org/donate-to-grass donation] or [https://grass.osgeo.org/contribute/sponsoring/ employer sponsorship] of the project helps us get closer.

== Venue ==
The meeting will be hosted at [https://fmach.it/ Fondazione Edmund Mach] (FEM) in San Michele all'Adige, Trentino, Italy — about 15 km north of Trento. FEM is a research and education center with on-site facilities that allow participants to work, sleep, and eat in the same location.

[https://maps.app.goo.gl/5YEuEts6qXvky7HD9 Map]

=== Getting there ===

San Michele all'Adige is reachable by train on the Trento–Bolzano line (Trento or Mezzocorona station), with frequent connections from Trento (~15 minutes) and Verona (~1 hour). The nearest airports are Verona (VRN), Venice Marco Polo (VCE) and Treviso (TSF), Milan Bergamo (BGY), Malpensa (MXP), and Linate (LIN), Bologna (BLQ), and Innsbruck (INN) in Austria. Trento is also the host city of FOSS4G Italy 2026 (July 9–11), making it convenient to combine both events.

From Trento main train station you need to move to Ferrovia Trento-Malè (FTM) train station (few minutes by walk, https://www.openstreetmap.org/#map=17/46.072739/11.120814) and there take a train to Grumo/San Michele all'Adige. Train timetable is [https://www.trentinotrasporti.it/images/allegati/ferrovia/ftm/FTM%20est2026%20-%20ANDATA.pdf here], the opposite way is [https://www.trentinotrasporti.it/images/allegati/ferrovia/ftm/FTM%20est2026%20-%20RITORNO.pdf this one]

Another possibility is to arrive with the main train (Ferrovie dello Stato) in Mezzocorona and here you can walk to San Michele (around 20 minutes by walk) or take the small train Trento-Malè from Mezzocorona Ferrovia station (in front of main train station https://www.openstreetmap.org/#map=18/46.206633/11.128024) and stop in Grumo/San Michele (you need to look for the [https://www.trentinotrasporti.it/images/allegati/ferrovia/ftm/FTM%20est2026%20-%20RITORNO.pdf way back schedule])

== Accommodation and Costs ==

''Registration is free''. However, participants should plan for the following costs:

* Travel
* Lodging

Participants can stay on-site at the FEM convitto (dormitory), keeping the community together for the full duration of the meeting:

* €35 per person per night
* Double and triple rooms (triples include a small kitchen)
* A mandatory on-site supervisor is required at €200 per night (flat fee, shared across the group)
* Family members are welcome to stay in the dormitory as well
* [https://cif.fmach.it/content/download/2701/78358/file/brochure_convitto.pdf Brochure]
* For '''lodging booking''' options: see [https://grasscommunitymeeting2026.eventbrite.it/ Eventbrite]

For anyone preferring alternative lodging, hotels and B&Bs are available in San Michele and nearby Trento.

Lunches on weekdays can be taken at the FEM canteen (mensa), located on the same campus. Details and pricing are being finalized.

== Individual Preparation ==

* Bring your own computer
* Bring {{wikipedia|AC power plugs and sockets|power adapter}} if needed (Italy: 230V, 50Hz, {{wikipedia|Europlug|Type C}}, {{wikipedia|Schuko|Type F}}, and {{wikipedia|AC power plugs and sockets: L|Type L}} sockets are common)
* Install git and the compiler tools, and come with a working GRASS development environment if possible. See [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md here] for details.

== FAQ ==

* ''Is this a conference?''
** Talks or presentations may be included, but the purpose is to work together on the project. Among conference formats, the closest comparison would be a participatory workshop.
* ''Is this a hackathon?''
** While there is plenty of intensive coding, the meeting is not competitive. We meet to collaborate.
* ''Is the GRASS Community Meeting for developers only?''
** No, the meeting is open to all users, supporters, contributors, power users, and developers ''who want to make a meaningful contribution to the project''.
* ''What skills do I need?''
** Coding skills are not required. Contributions to documentation, tutorials, translations, website, and testing are all valuable. Practical help during the meeting, such as coordinating meals, photography, or reporting, is a real contribution too.
* ''Can I attend remotely?''
** The meeting is in-person, but everyone is welcome to use the same week for focused work on the project from wherever they are.
* ''What language is used during the meeting?''
** English is the working language, but you may hear several other languages spoken at the event.
* ''How was it last time?''
** Splendid! See [[GRASS Developer Summit Raleigh 2025]]!
* ''Where can I get help and more information about the community meeting?''
** Contact local organizer [[User:Lucadelu|Luca Delucchi]] (<tt><lucadeluge at gmail com></tt>) or [[User:wenzeslaus|Vaclav Petras]] (<tt><wenzeslaus at gmail com></tt>) for budget questions.
* ''What if I can't spend time on this?''
** Can you spend money instead? [https://numfocus.org/donate-to-grass Donate to GRASS through NumFOCUS] to help keep the project going.

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2026]]

Talk:GRASS Community Meeting San Michele 2026

2026-07-13T13:18:22Z

Annakrat: /* Jul 13 */

Talk:GRASS Community Meeting San Michele 2026

2026-07-13T13:04:21Z

Annakrat: /* Jul 13 */

Talk:GRASS Community Meeting San Michele 2026

2026-07-13T09:53:26Z

Annakrat: /* Anna Petrasova */

Talk:GRASS Community Meeting San Michele 2026

2026-07-12T13:57:36Z

Annakrat: /* Reports */

Talk:GRASS Community Meeting San Michele 2026

2026-07-12T10:08:44Z

Annakrat: /* Anna Petrasova */

Talk:GRASS Community Meeting San Michele 2026

2026-07-12T08:52:08Z

Annakrat: /* Anna Petrasova */

GRASS Community Meeting San Michele 2026

2026-07-12T07:39:10Z

Annakrat: /* Sponsors */

[[File:Sanmichele.png|frameless|center|1000px|San Michele all'Adige]]

{{toc|right}}

The ''GRASS Community Meeting'' for contributors and developers will be happening from '''July 11 - 19, 2026''' in [https://www.openstreetmap.org/relation/46990#map=12/46.1349/11.1947 San Michele all'Adige, Trentino, Italy].

== Sponsors ==

Sponsors make the event possible. Learn more about [https://grass.osgeo.org/contribute/sponsoring/ Sponsoring].

* [https://bhinc.com/ Bohannan Huston, Inc.]: 2,500 USD
[[File:Bohannan_Huston_Inc_Logo.png|none|left|400px|alt=Logo of Bohannan Huston, Inc.|Bohannan Huston, Inc.]]

* [https://www.osgeo.org/ OSGeo]: 2500 USD (see [https://wiki.osgeo.org/w/index.php?title=GRASS_Community_Meeting_2026:_Budget budget]]).

[[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.fossgis.de/ FOSSGIS e.V.]: 4500 EUR (approved budget contribution, [https://www.fossgis.de/wiki/F%C3%B6rderantr%C3%A4ge/GRASS_GIS_Community_Meeting_2026 request]).

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

* U.S. National Science Foundation, award 2303651 (planning and time of 3 participants).

* In-kind contributions:
** mundialis GmbH & Co. KG - personnel time (personnel time)
* Personal time and/or financial contributions:
** Edouard Choinière, Helmut Kudrnovsky, Markus Neteler, Vaclav Petras, Anna Petrasova, Corey White, Veronica Andreo
** In addition to the above contributions, many participants made special efforts to keep costs down.

== Purpose ==
The ''GRASS Community Meeting'' is a great occasion for folks to support the development by actively contributing to the project in different ways. These include source code updates, documentation (manuals, wiki, tutorials), translations, website improvements 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 project and the interfaces to QGIS, GDAL, PostGIS, R, OGC Services and others.

The focus is on GRASS maintenance, and interaction with other projects. Many maintenance tasks, infrastructure changes, and planning of large changes especially benefits from maintainers being in one place and time zone. While the specific topics highly depend on the participants, we will prioritize topics which require highly synchronous collaboration, such as the CMake build system transition and API transitions. The [https://grass.osgeo.org/news/2025_05_27_grass_dev_summit_report/ 2025 event report] gives an overview of what was achieved last year.

We do require participants to work on GRASS or connections to other projects. However, we leave them the freedom to work on what they think is the best contribution to the project given their skills and time available.

== Agenda ==

Agenda is being refined.

=== Saturday, July 11 ===

Day of arrival. Contact organizers (Luca, see FAQ below) if you are interested in individualized program or helping with organization.

=== Sunday, July 12 ===

* Hybrid meeting about 8.6.0 with Filesystem Hierarchy Standard and Jupyter in GUI updates

=== Monday, July 13 ===

* Filesystem Hierarchy Standard ([https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard FHS])
* Updating the GRASS Roadmap
* New '''Windows build server''' needed for addon provisioning and to get rid of "windows-2022 build and tests" (<code>ERROR: Cannot open URL <http://wingrass.fsv.cvut.cz/grass85/addons/grass-8.5.1dev/r.stream.distance.zip>: HTTP Error 404: Not Found</code>)

=== Tuesday, July 14 ===

* [[GSoC]] (may be moved to different day)
* GeoAI

=== Wednesday, July 15 ===

* Python API review
* Plan [[PSC]] elections

=== Thursday, July 16 ===

* Reducing PR backlog

=== Friday, July 17 ===

* Address issues for the upcoming [https://github.com/OSGeo/grass/milestone/29 8.6.0 release]

=== Saturday, July 18 ===

* Website review: fix the serious bootstrap mixup and broken sitemap bugs

=== Sunday, July 19 ===

Day of departure.

== Participation ==

Please add your name here:

{|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:Lucadelu|Luca Delucchi]]
| Italy
|
|
|
|
|-
|2
| [[User:wenzeslaus|Vaclav Petras]]
| United States
| 11.07.
| 19.07.
| grass.tools, pytest, subcommands, reviews
|
|-
|3
| [[User:Annakrat|Anna Petrasova]]
| United States
| 11.07.
| 19.07.
| GSoC, reviews, PR backlog, tutorials
|
|-
|4
| [[User:Neteler|Markus Neteler]]
| Germany
| 06.07.
| 18.07.
| documentation, website, state of GRASS support in QGIS 3.x/4.x, knowledge-transfer
|
|-
|5
| [[User:Sbl|Stefan Blumentrath]]
| Norway
| 11.07. (presumably)
| 18.07. (presumably)
| Handling Copernicus data with GRASS / actinia
|
|-
|6
| [[User:Hellik|Helmut Kudrnovsky]]
| Austria
|
|
|
|
|-
|7
| [[User:Veroandreo|Verónica Andreo]]
| Argentina
| 11.07.
| 19.07.
|
|
|-
|8
| [[User:Ctwhite|Corey White]]
| United States
| 11.07.
| 19.07.
| grass.jupyter, documentation, website, reviews, tutorials
|
|-
|9
| [[User:Echoix|Edouard Choinière]]
| Canada
| 11.07. (presumably)
| 19.07. (presumably)
| Reviews, CI, pytest, Windows GUI, i18n, undecided
|
|-
|10
| [[User:Mazingaro|Alen Mangafić]]
| Slovenia
| 13.07.
| 17.07.
| i.hyper: [https://grass.osgeo.org/grass-stable/manuals/addons/i.hyper.html Road Map] fulfilling; State of GRASS @FOSS4G 2026
|
|-
|11
| Tomaž Žagar
| Slovenia
| 13.07.
| 17.07.
| i.hyper: [https://grass.osgeo.org/grass-stable/manuals/addons/i.hyper.html Road Map] fulfilling
|
|-
|12
| Matjaž Krebs
| Slovenia
| 13.07.
| 17.07.
| i.hyper: [https://grass.osgeo.org/grass-stable/manuals/addons/i.hyper.html Road Map] fulfilling
|
|-
|}

Registration is free; participants cover their own travel and lodging (see below), often with employer support — thank you. Ideally we'd reimburse everyone, and every [https://numfocus.org/donate-to-grass donation] or [https://grass.osgeo.org/contribute/sponsoring/ employer sponsorship] of the project helps us get closer.

== Venue ==
The meeting will be hosted at [https://fmach.it/ Fondazione Edmund Mach] (FEM) in San Michele all'Adige, Trentino, Italy — about 15 km north of Trento. FEM is a research and education center with on-site facilities that allow participants to work, sleep, and eat in the same location.

[https://maps.app.goo.gl/5YEuEts6qXvky7HD9 Map]

=== Getting there ===

San Michele all'Adige is reachable by train on the Trento–Bolzano line (Trento or Mezzocorona station), with frequent connections from Trento (~15 minutes) and Verona (~1 hour). The nearest airports are Verona (VRN), Venice Marco Polo (VCE) and Treviso (TSF), Milan Bergamo (BGY), Malpensa (MXP), and Linate (LIN), Bologna (BLQ), and Innsbruck (INN) in Austria. Trento is also the host city of FOSS4G Italy 2026 (July 9–11), making it convenient to combine both events.

From Trento main train station you need to move to Ferrovia Trento-Malè (FTM) train station (few minutes by walk, https://www.openstreetmap.org/#map=17/46.072739/11.120814) and there take a train to Grumo/San Michele all'Adige. Train timetable is [https://www.trentinotrasporti.it/images/allegati/ferrovia/ftm/FTM%20est2026%20-%20ANDATA.pdf here], the opposite way is [https://www.trentinotrasporti.it/images/allegati/ferrovia/ftm/FTM%20est2026%20-%20RITORNO.pdf this one]

Another possibility is to arrive with the main train (Ferrovie dello Stato) in Mezzocorona and here you can walk to San Michele (around 20 minutes by walk) or take the small train Trento-Malè from Mezzocorona Ferrovia station (in front of main train station https://www.openstreetmap.org/#map=18/46.206633/11.128024) and stop in Grumo/San Michele (you need to look for the [https://www.trentinotrasporti.it/images/allegati/ferrovia/ftm/FTM%20est2026%20-%20RITORNO.pdf way back schedule])

== Accommodation and Costs ==

''Registration is free''. However, participants should plan for the following costs:

* Travel
* Lodging

Participants can stay on-site at the FEM convitto (dormitory), keeping the community together for the full duration of the meeting:

* €35 per person per night
* Double and triple rooms (triples include a small kitchen)
* A mandatory on-site supervisor is required at €200 per night (flat fee, shared across the group)
* Family members are welcome to stay in the dormitory as well
* [https://cif.fmach.it/content/download/2701/78358/file/brochure_convitto.pdf Brochure]
* For '''lodging booking''' options: see [https://grasscommunitymeeting2026.eventbrite.it/ Eventbrite]

For anyone preferring alternative lodging, hotels and B&Bs are available in San Michele and nearby Trento.

Lunches on weekdays can be taken at the FEM canteen (mensa), located on the same campus. Details and pricing are being finalized.

== Individual Preparation ==

* Bring your own computer
* Bring {{wikipedia|AC power plugs and sockets|power adapter}} if needed (Italy: 230V, 50Hz, {{wikipedia|Europlug|Type C}}, {{wikipedia|Schuko|Type F}}, and {{wikipedia|AC power plugs and sockets: L|Type L}} sockets are common)
* Install git and the compiler tools, and come with a working GRASS development environment if possible. See [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md here] for details.

== FAQ ==

* ''Is this a conference?''
** Talks or presentations may be included, but the purpose is to work together on the project. Among conference formats, the closest comparison would be a participatory workshop.
* ''Is this a hackathon?''
** While there is plenty of intensive coding, the meeting is not competitive. We meet to collaborate.
* ''Is the GRASS Community Meeting for developers only?''
** No, the meeting is open to all users, supporters, contributors, power users, and developers ''who want to make a meaningful contribution to the project''.
* ''What skills do I need?''
** Coding skills are not required. Contributions to documentation, tutorials, translations, website, and testing are all valuable. Practical help during the meeting, such as coordinating meals, photography, or reporting, is a real contribution too.
* ''Can I attend remotely?''
** The meeting is in-person, but everyone is welcome to use the same week for focused work on the project from wherever they are.
* ''What language is used during the meeting?''
** English is the working language, but you may hear several other languages spoken at the event.
* ''How was it last time?''
** Splendid! See [[GRASS Developer Summit Raleigh 2025]]!
* ''Where can I get help and more information about the community meeting?''
** Contact local organizer [[User:Lucadelu|Luca Delucchi]] (<tt><lucadeluge at gmail com></tt>) or [[User:wenzeslaus|Vaclav Petras]] (<tt><wenzeslaus at gmail com></tt>) for budget questions.
* ''What if I can't spend time on this?''
** Can you spend money instead? [https://numfocus.org/donate-to-grass Donate to GRASS through NumFOCUS] to help keep the project going.

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2026]]

GRASS Community Meeting San Michele 2026

2026-07-12T07:36:57Z

Annakrat: /* Sponsors */

[[File:Sanmichele.png|frameless|center|1000px|San Michele all'Adige]]

{{toc|right}}

The ''GRASS Community Meeting'' for contributors and developers will be happening from '''July 11 - 19, 2026''' in [https://www.openstreetmap.org/relation/46990#map=12/46.1349/11.1947 San Michele all'Adige, Trentino, Italy].

== Sponsors ==

Sponsors make the event possible. Learn more about [https://grass.osgeo.org/contribute/sponsoring/ Sponsoring].

* [https://www.osgeo.org/ OSGeo]: 2500 USD (see [https://wiki.osgeo.org/w/index.php?title=GRASS_Community_Meeting_2026:_Budget budget]]).

[[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.fossgis.de/ FOSSGIS e.V.]: 4500 EUR (approved budget contribution, [https://www.fossgis.de/wiki/F%C3%B6rderantr%C3%A4ge/GRASS_GIS_Community_Meeting_2026 request]).

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

* U.S. National Science Foundation, award 2303651 (planning and time of 3 participants).

* In-kind contributions:
** mundialis GmbH & Co. KG - personnel time (personnel time)
* Personal time and/or financial contributions:
** Edouard Choinière, Helmut Kudrnovsky, Markus Neteler, Vaclav Petras, Anna Petrasova, Corey White, Veronica Andreo
** In addition to the above contributions, many participants made special efforts to keep costs down.

== Purpose ==
The ''GRASS Community Meeting'' is a great occasion for folks to support the development by actively contributing to the project in different ways. These include source code updates, documentation (manuals, wiki, tutorials), translations, website improvements 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 project and the interfaces to QGIS, GDAL, PostGIS, R, OGC Services and others.

The focus is on GRASS maintenance, and interaction with other projects. Many maintenance tasks, infrastructure changes, and planning of large changes especially benefits from maintainers being in one place and time zone. While the specific topics highly depend on the participants, we will prioritize topics which require highly synchronous collaboration, such as the CMake build system transition and API transitions. The [https://grass.osgeo.org/news/2025_05_27_grass_dev_summit_report/ 2025 event report] gives an overview of what was achieved last year.

We do require participants to work on GRASS or connections to other projects. However, we leave them the freedom to work on what they think is the best contribution to the project given their skills and time available.

== Agenda ==

Agenda is being refined.

=== Saturday, July 11 ===

Day of arrival. Contact organizers (Luca, see FAQ below) if you are interested in individualized program or helping with organization.

=== Sunday, July 12 ===

* Hybrid meeting about 8.6.0 with Filesystem Hierarchy Standard and Jupyter in GUI updates

=== Monday, July 13 ===

* Filesystem Hierarchy Standard ([https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard FHS])
* Updating the GRASS Roadmap
* New '''Windows build server''' needed for addon provisioning and to get rid of "windows-2022 build and tests" (<code>ERROR: Cannot open URL <http://wingrass.fsv.cvut.cz/grass85/addons/grass-8.5.1dev/r.stream.distance.zip>: HTTP Error 404: Not Found</code>)

=== Tuesday, July 14 ===

* [[GSoC]] (may be moved to different day)
* GeoAI

=== Wednesday, July 15 ===

* Python API review
* Plan [[PSC]] elections

=== Thursday, July 16 ===

* Reducing PR backlog

=== Friday, July 17 ===

* Address issues for the upcoming [https://github.com/OSGeo/grass/milestone/29 8.6.0 release]

=== Saturday, July 18 ===

* Website review: fix the serious bootstrap mixup and broken sitemap bugs

=== Sunday, July 19 ===

Day of departure.

== Participation ==

Please add your name here:

{|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:Lucadelu|Luca Delucchi]]
| Italy
|
|
|
|
|-
|2
| [[User:wenzeslaus|Vaclav Petras]]
| United States
| 11.07.
| 19.07.
| grass.tools, pytest, subcommands, reviews
|
|-
|3
| [[User:Annakrat|Anna Petrasova]]
| United States
| 11.07.
| 19.07.
| GSoC, reviews, PR backlog, tutorials
|
|-
|4
| [[User:Neteler|Markus Neteler]]
| Germany
| 06.07.
| 18.07.
| documentation, website, state of GRASS support in QGIS 3.x/4.x, knowledge-transfer
|
|-
|5
| [[User:Sbl|Stefan Blumentrath]]
| Norway
| 11.07. (presumably)
| 18.07. (presumably)
| Handling Copernicus data with GRASS / actinia
|
|-
|6
| [[User:Hellik|Helmut Kudrnovsky]]
| Austria
|
|
|
|
|-
|7
| [[User:Veroandreo|Verónica Andreo]]
| Argentina
| 11.07.
| 19.07.
|
|
|-
|8
| [[User:Ctwhite|Corey White]]
| United States
| 11.07.
| 19.07.
| grass.jupyter, documentation, website, reviews, tutorials
|
|-
|9
| [[User:Echoix|Edouard Choinière]]
| Canada
| 11.07. (presumably)
| 19.07. (presumably)
| Reviews, CI, pytest, Windows GUI, i18n, undecided
|
|-
|10
| [[User:Mazingaro|Alen Mangafić]]
| Slovenia
| 13.07.
| 17.07.
| i.hyper: [https://grass.osgeo.org/grass-stable/manuals/addons/i.hyper.html Road Map] fulfilling; State of GRASS @FOSS4G 2026
|
|-
|11
| Tomaž Žagar
| Slovenia
| 13.07.
| 17.07.
| i.hyper: [https://grass.osgeo.org/grass-stable/manuals/addons/i.hyper.html Road Map] fulfilling
|
|-
|12
| Matjaž Krebs
| Slovenia
| 13.07.
| 17.07.
| i.hyper: [https://grass.osgeo.org/grass-stable/manuals/addons/i.hyper.html Road Map] fulfilling
|
|-
|}

Registration is free; participants cover their own travel and lodging (see below), often with employer support — thank you. Ideally we'd reimburse everyone, and every [https://numfocus.org/donate-to-grass donation] or [https://grass.osgeo.org/contribute/sponsoring/ employer sponsorship] of the project helps us get closer.

== Venue ==
The meeting will be hosted at [https://fmach.it/ Fondazione Edmund Mach] (FEM) in San Michele all'Adige, Trentino, Italy — about 15 km north of Trento. FEM is a research and education center with on-site facilities that allow participants to work, sleep, and eat in the same location.

[https://maps.app.goo.gl/5YEuEts6qXvky7HD9 Map]

=== Getting there ===

San Michele all'Adige is reachable by train on the Trento–Bolzano line (Trento or Mezzocorona station), with frequent connections from Trento (~15 minutes) and Verona (~1 hour). The nearest airports are Verona (VRN), Venice Marco Polo (VCE) and Treviso (TSF), Milan Bergamo (BGY), Malpensa (MXP), and Linate (LIN), Bologna (BLQ), and Innsbruck (INN) in Austria. Trento is also the host city of FOSS4G Italy 2026 (July 9–11), making it convenient to combine both events.

From Trento main train station you need to move to Ferrovia Trento-Malè (FTM) train station (few minutes by walk, https://www.openstreetmap.org/#map=17/46.072739/11.120814) and there take a train to Grumo/San Michele all'Adige. Train timetable is [https://www.trentinotrasporti.it/images/allegati/ferrovia/ftm/FTM%20est2026%20-%20ANDATA.pdf here], the opposite way is [https://www.trentinotrasporti.it/images/allegati/ferrovia/ftm/FTM%20est2026%20-%20RITORNO.pdf this one]

Another possibility is to arrive with the main train (Ferrovie dello Stato) in Mezzocorona and here you can walk to San Michele (around 20 minutes by walk) or take the small train Trento-Malè from Mezzocorona Ferrovia station (in front of main train station https://www.openstreetmap.org/#map=18/46.206633/11.128024) and stop in Grumo/San Michele (you need to look for the [https://www.trentinotrasporti.it/images/allegati/ferrovia/ftm/FTM%20est2026%20-%20RITORNO.pdf way back schedule])

== Accommodation and Costs ==

''Registration is free''. However, participants should plan for the following costs:

* Travel
* Lodging

Participants can stay on-site at the FEM convitto (dormitory), keeping the community together for the full duration of the meeting:

* €35 per person per night
* Double and triple rooms (triples include a small kitchen)
* A mandatory on-site supervisor is required at €200 per night (flat fee, shared across the group)
* Family members are welcome to stay in the dormitory as well
* [https://cif.fmach.it/content/download/2701/78358/file/brochure_convitto.pdf Brochure]
* For '''lodging booking''' options: see [https://grasscommunitymeeting2026.eventbrite.it/ Eventbrite]

For anyone preferring alternative lodging, hotels and B&Bs are available in San Michele and nearby Trento.

Lunches on weekdays can be taken at the FEM canteen (mensa), located on the same campus. Details and pricing are being finalized.

== Individual Preparation ==

* Bring your own computer
* Bring {{wikipedia|AC power plugs and sockets|power adapter}} if needed (Italy: 230V, 50Hz, {{wikipedia|Europlug|Type C}}, {{wikipedia|Schuko|Type F}}, and {{wikipedia|AC power plugs and sockets: L|Type L}} sockets are common)
* Install git and the compiler tools, and come with a working GRASS development environment if possible. See [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md here] for details.

== FAQ ==

* ''Is this a conference?''
** Talks or presentations may be included, but the purpose is to work together on the project. Among conference formats, the closest comparison would be a participatory workshop.
* ''Is this a hackathon?''
** While there is plenty of intensive coding, the meeting is not competitive. We meet to collaborate.
* ''Is the GRASS Community Meeting for developers only?''
** No, the meeting is open to all users, supporters, contributors, power users, and developers ''who want to make a meaningful contribution to the project''.
* ''What skills do I need?''
** Coding skills are not required. Contributions to documentation, tutorials, translations, website, and testing are all valuable. Practical help during the meeting, such as coordinating meals, photography, or reporting, is a real contribution too.
* ''Can I attend remotely?''
** The meeting is in-person, but everyone is welcome to use the same week for focused work on the project from wherever they are.
* ''What language is used during the meeting?''
** English is the working language, but you may hear several other languages spoken at the event.
* ''How was it last time?''
** Splendid! See [[GRASS Developer Summit Raleigh 2025]]!
* ''Where can I get help and more information about the community meeting?''
** Contact local organizer [[User:Lucadelu|Luca Delucchi]] (<tt><lucadeluge at gmail com></tt>) or [[User:wenzeslaus|Vaclav Petras]] (<tt><wenzeslaus at gmail com></tt>) for budget questions.
* ''What if I can't spend time on this?''
** Can you spend money instead? [https://numfocus.org/donate-to-grass Donate to GRASS through NumFOCUS] to help keep the project going.

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2026]]

Talk:GRASS Community Meeting San Michele 2026

2026-07-12T07:16:39Z

Annakrat: Initial reports page

GRASS GIS Jupyter notebooks

2026-05-15T17:15:44Z

Annakrat: Remove outdated information

A Jupyter Notebook is a web application that allows you to create and share documents that contain scripts and code, equations, visualizations and explanatory text, combined.

== Get started ==
Read [https://grass.osgeo.org/grass-stable/manuals/jupyter_intro.html GRASS Jupyter Notebooks Introduction].
Try [https://grass-tutorials.osgeo.org/content/tutorials/get_started/fast_track_grass_and_python.html Get started with GRASS & Python in Jupyter Notebooks] official tutorial. Browse additional [https://grass-tutorials.osgeo.org/ tutorials].

== List of selected GRASS Jupyter notebooks ==
Note that the following list is community contributed and the notebooks may contain outdated information and old GRASS API usage. For up-to-date notebooks, see GRASS official [https://grass-tutorials.osgeo.org/ tutorial page].

'''Intro notebooks:'''
* [https://github.com/OSGeo/grass/blob/main/doc/notebooks Official notebooks in OSGeo/grass repo] ([https://mybinder.org/v2/gh/OSGeo/grass/main?urlpath=lab%2Ftree%2Fdoc%2Fnotebooks%2Fjupyter_example.ipynb jupyter_example.ipynb on Binder])
* [https://github.com/ncsu-geoforall-lab/grass-gis-workshop-foss4g-2022 Unleash the power of GRASS GIS with Jupyter (FOSS4G 2022 workshop)]
* [https://github.com/ncsu-geoforall-lab/grass-gis-workshop-FOSS4G-2021 GRASS GIS: From Beginner to Power User (FOSS4G 2021 workshop)]
* [https://github.com/wenzeslaus/try-grass-in-jupyter-with-bash wenzeslaus/try-grass-in-jupyter-with-bash] (experimental)
* NSF platform: https://wholetale.org/
** GRASS GIS Introduction, by Anna Petrasova: https://dashboard.wholetale.org/run/63d832bab4a0197e9a9ecdad?tab=files

'''Windows related:'''
* [https://github.com/ncsu-geoforall-lab/GIS714-assignments/blob/main/GRASS_GIS_Foundations/JupyterOnWindows_standalone_Tutorial.ipynb GRASS GIS Jupyter Notebooks on Windows standalone installer tutorial]
* [https://github.com/ncsu-geoforall-lab/GIS714-assignments/blob/main/GRASS_GIS_Foundations/JupyterOnWindows_OSGeo4W_Tutorial.ipynb GRASS GIS Jupyter Notebooks on Windows with OSGeo4W]

'''Mac related:'''
* [https://github.com/ncsu-geoforall-lab/GIS714-assignments/blob/main/GRASS_GIS_Foundations/JupyterOnMac_Tutorial.ipynb GRASS GIS Jupyter Notebooks on Mac]

'''Workbook Collections:'''
* [https://github.com/wenzeslaus/geospatial-modeling-course-jupyter/tree/master/notebooks 14 Jupyter Notebooks for learning geospatial analysis and modeling with GRASS GIS] (Python and command line versions)

'''Species Distribution Modeling:'''
* NSF platform: https://wholetale.org/
** Using satellite data for Species Distribution Modeling with GRASS GIS and R, by Veronica Andreo https://dashboard.wholetale.org/run/64388157b3b74e434bd8f1ac?tab=files

'''Image processing/OBIA:'''
* [https://github.com/veroandreo/foss4g2022_grass4rs GRASS GIS for remote sensing data processing and analysis]
* [https://github.com/neteler/jupyter_sentinel2_grass_gis GRASS GIS 8 and processing of multitemporal EO data]
* [https://github.com/tgrippa/Opensource_OBIA_processing_chain An open-source semi-automated processing chain for urban OBIA classification]

'''Python and PyGRASS:'''
* [https://github.com/zarch/workshop-pygrass Workshop on PyGRASS using IPython notebook]
* [https://github.com/wenzeslaus/foss4g-2022-developing-custom-grass-tools Developing custom GRASS tools (FOSS4G 2022 workshop)]
* [https://github.com/wenzeslaus/python-grass-addon How to write a Python GRASS GIS 7 addon (FOSS4G Europe 2015 workshop)]
* [https://github.com/lucadelu/docker-stacks/tree/geospatial/geospatial-notebook Jupyter Notebook Geospatial Python Stack]

'''R and GRASS GIS:'''
* [https://gist.github.com/joergsteinkamp/43fb13a82aeab9b5c0dcc4433f97f1a6 Simple Opensource GIS examples with GRASS GIS and R]

'''Wildfire Modeling:'''
* [https://github.com/acoiman/wildfire_modeling Wildfire Modeling in Yosemite National Park]

[[Category: Documentation]]
[[Category: Python]]

FUTURES tutorial

2026-05-14T16:46:33Z

Annakrat: small updates

[https://grass.osgeo.org/grass-stable/manuals/addons/r.futures.html r.futures.*] is an implementation of FUTure Urban-Regional Environment Simulation (FUTURES)
which is a model for multilevel simulations of emerging urban-rural landscape structure.
FUTURES produces regional projections of landscape patterns using coupled submodels that integrate nonstationary
drivers of land change: per capita demand (DEMAND submodel), site suitability (POTENTIAL submodel),
and the spatial structure of conversion events (PGA submodel).

This tutorial shows how to prepare data and run the model. You can download [http://fatra.cnr.ncsu.edu/futures/FUTURES_triangle.zip sample dataset] and simulate urban growth
in [https://en.wikipedia.org/wiki/Research_Triangle The Triangle], region in the Piedmont of North Carolina in the United States with rapidly growing cities Raleigh, Durham and Chapel Hill.

= Prerequisites =

This tutorial requires basic knowledge of GRASS GIS. If you haven't used GRASS GIS before, you may want to first go through some of the introductory tutorials or alternative workshops linked from the [[#See also|See also section]].

= Software =
Required software includes:
* GRASS GIS
* addons
** {{AddonCmd|r.futures.simulation}}
** {{AddonCmd|r.futures.potential}}
** {{AddonCmd|r.futures.demand}}
** {{AddonCmd|r.futures.devpressure}}
** {{AddonCmd|r.sample.category}}
* R (≥ 3.0.2) - needed for {{AddonCmd|r.futures.potential}}
* SciPy - useful for {{AddonCmd|r.futures.demand}}

= Input data used in this tutorial =
Download [http://fatra.cnr.ncsu.edu/futures/FUTURES_triangle.zip sample dataset] containing:
* digital elevation model ([http://nationalmap.gov/elevation.html NED])
* [http://www.mrlc.gov/ NLCD] 2001, 2011
* NLCD 1992/2001 Retrofit Land Cover Change Product
* transportation network ([http://www.census.gov/geo/maps-data/data/tiger-line.html TIGER])
* county boundaries ([http://www.census.gov/geo/maps-data/data/tiger-line.html TIGER])
* protected areas ([http://www.conservationgateway.org/ConservationByGeography/NorthAmerica/UnitedStates/edc/reportsdata/terrestrial/secured/Pages/default.aspx Secured Lands])
* cities above 20000 (USGS)
* county population past estimates and future projections ([https://www.osbm.nc.gov/demog/county-projections NC OSBM]) per county (nonspatial)

= Workflow =
Download sample data and unzip it. Create <tt>grassdata</tt> directory on your disk (or use the one you already have) and move there Location <tt>futures_ncspm</tt>.
Launch GRASS GIS and select your <tt>grassdata</tt> directory, Location <tt>futures_ncspm</tt> and Mapset <tt>practice1</tt>.

Install addons:
<source lang="bash">
g.extension r.futures
g.extension r.sample.category
</source>

Close GUI and restart it:
<source lang="bash">
g.gui
</source>

To install the required R packages, go to the command line terminal which was started with GRASS GIS and R:

<source lang="bash">
R
</source>

This starts the R command line where you need to execute the following code (and go through any dialogs about installation if R shows them):

<source lang="R">
install.packages(c("MuMIn", "lme4", "optparse", "rgrass7"))
</source>

== Initial steps and data preparation ==
First we will set computational region of our analyses to an extent covering our study area and so that the cells are aligned with one of our landuse rasters:
<source lang="bash">g.region raster=landuse_2011 -p</source>

We will derive urbanized areas from NLCD dataset for year 1992, 2001 and 2011
by extracting categories category 21 - 24 into a new binary map where developed is 1,
undeveloped 0 and NULL (no data) is area unsuitable for development (water, wetlands, protected areas).
First we will convert protected areas from vector to raster and set
NULLs to zeros (for simpler raster algebra expression in the next step):

<source lang="bash">
v.to.rast input=protected_areas output=protected_areas use=val
r.null map=protected_areas null=0
</source>

And then create rasters of developed/undeveloped areas using raster algebra:

<source lang="bash" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
r.mapcalc "urban_1992 = if(landuse_1992 >= 21 && landuse_1992 <= 24, 1, if(landuse_1992 == 11 || landuse_1992 >= 90 || protected_areas, null(), 0))"
r.mapcalc "urban_2001 = if(landuse_2001 >= 21 && landuse_2001 <= 24, 1, if(landuse_2001 == 11 || landuse_2001 >= 90 || protected_areas, null(), 0))"
r.mapcalc "urban_2011 = if(landuse_2011 >= 21 && landuse_2011 <= 24, 1, if(landuse_2011 == 11 || landuse_2011 >= 90 || protected_areas, null(), 0))"
</source>

We will convert vector counties to raster with the values of the FIPS attribute which links to population file:

<source lang="bash">
v.to.rast input=counties type=area use=attr attribute_column=FIPS output=counties
</source>

If we need to run FUTURES only for smaller number of counties, we can extract them based on the identifier:

<source lang="bash" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
v.to.rast input=counties type=area where="FIPS in (37183, 37101)" use=attr attribute_column=FIPS output=counties_subset
</source>

Before further steps, we will set our working directory so that the input population files and text files
we are going to create are saved in one directory and easily accessible.
You can do that from menu ''Settings'' → ''GRASS working environment'' → ''Change working directory''.
Select (or create) a directory and move there the downloaded files <tt>population_projection.csv</tt> and <tt>population_trend.csv</tt>.

== Potential submodel ==
Module {{AddonCmd|r.futures.potential}} implements POTENTIAL submodel as a part of FUTURES land change model. POTENTIAL is implemented using a set of coefficients that relate a selection of site suitability factors to the probability of a place becoming developed. This is implemented using the parameter table in combination with maps of those site suitability factors (mapped predictors). The coefficients are obtained by conducting multilevel logistic regression in R with package lme4 where the coefficients may vary by county. The best model is selected automatically using dredge function from package [https://cran.r-project.org/web/packages/MuMIn/index.html MuMIn].

First, we will derive couple of predictors.
=== Predictors ===
==== Slope ====
We will derive slope in degrees from digital elevation model using {{cmd|r.slope.aspect}} module:
<source lang="bash">r.slope.aspect elevation=elevation_30m slope=slope</source>

==== Distance from lakes/rivers ====
First we will extract [http://www.mrlc.gov/nlcd11_leg.php category ''Open Water''] from 2011 NLCD dataset:
<source lang="bash">
r.mapcalc "water = if(landuse_2011 == 11, 1, null())"
</source>

Then we compute the distance to water with module {{cmd|r.grow.distance}} and set color table to shades of blue:
<source lang="bash">
r.grow.distance input=water distance=dist_to_water
r.colors -n map=dist_to_water color=blues
</source>

==== Distance from protected areas ====
We will use raster protected of protected areas we already created, but we will set NULL values to zero.
We compute the distance to protected areas with module {{cmd|r.grow.distance}} and set color table from green to red:
<source lang="bash">
r.null map=protected_areas setnull=0
r.grow.distance input=protected_areas distance=dist_to_protected
r.colors map=dist_to_protected color=gyr
</source>

==== Forests ====
We will smooth the transition between forest and other land use, see NLCD [http://www.mrlc.gov/nlcd11_leg.php category ''Open Water'']:
<source lang="bash">
r.mapcalc "forest = if(landuse_2011 >= 41 && landuse_2011 <= 43, 1, 0)"
r.neighbors -c input=forest output=forest_smooth size=15 method=average
r.colors map=forest_smooth color=ndvi
</source>

==== Travel time to cities ====
Here we will compute travel time to cities (> population 20000)
as cumulative cost distance where cost is defined as travel time on roads.
First we specify the speed on different types of roads.
We copy the roads raster into our mapset so that we can change it
by adding a new attribute field <tt>speed</tt>. Then we assign speed values (km/h) based on the type of road:

<source lang="bash">
g.copy vector=roads,myroads
v.db.addcolumn map=myroads columns="speed double precision"
v.db.update map=myroads column=speed value=50 where="MTFCC = 'S1400'"
v.db.update map=myroads column=speed value=100 where="MTFCC IN ('S1100', 'S1200')"
</source>

Now we rasterize the selected road types using the speed values from the attribute table as raster values.

<source lang="bash" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
v.to.rast input=myroads type=line where="MTFCC IN ('S1100', 'S1200', 'S1400')" output=roads_speed use=attr attribute_column=speed
</source>

We set the rest of the area to low speed and recompute the speed as time to travel through a 30m cell in minutes:

<source lang="bash">
r.null map=roads_speed null=5
r.mapcalc "roads_travel_time = 1.8 / roads_speed"
</source>

Finally we compute the travel time to larger cities using {{cmd|r.cost}}:

<source lang="bash">
r.cost input=roads_travel_time output=travel_time_cities start_points=cities_20000 memory=3000
r.colors map=travel_time_cities color=byr
</source>

==== Road density ====
We will rasterize roads and use moving window analysis ({{cmd|r.neighbors}}) to compute road density:

<source lang="bash">
v.to.rast input=roads output=roads use=val
r.null map=roads null=0
r.neighbors -c input=roads output=road_dens size=25 method=average nprocs=4
</source>

==== Distance to interchanges ====

We will consider TIGER roads of type <tt>Ramp</tt> as interchanges, rasterize them and compute euclidean distance to them:

<source lang="bash">
v.to.rast input=roads type=line where="MTFCC = 'S1630'" output=interchanges use=val
r.grow.distance -m input=interchanges distance=dist_interchanges
</source>

=== Development pressure ===

We compute development pressure with {{AddonCmd|r.futures.devpressure}}. Development pressure is a predictor based on number of neighboring developed cells within search distance, weighted by distance. The development pressure variable plays a special role in the model, allowing for a feedback between predicted change and change in subsequent steps.

<source lang="bash" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
r.futures.devpressure -n input=urban_2011 output=devpressure_1 method=gravity size=10 gamma=1 scaling_factor=1
r.futures.devpressure -n input=urban_2011 output=devpressure_0_5 method=gravity size=30 gamma=0.5 scaling_factor=0.1
</source>

When gamma increases, development influence decreases more rapidly with distance.
Size is half the size of the moving window. When gamma is low, local development influences more distant places.
We will derive 2 layers with different gamma and size parameters for the potential statistical model.

=== Rescaling variables ===

First we will look at the ranges of our predictor variables by running a short Python code snippet in Python tab in GUI:

<source lang="python" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
for name in ['slope', 'dist_to_water', 'dist_to_protected', 'forest_smooth', 'travel_time_cities', 'road_dens', 'dist_interchanges', 'devpressure_0_5', 'devpressure_1']:
minmax = grass.raster_info(name)
print name, minmax['min'], minmax['max']
</source>

We will rescale some of our input variables:

<source lang="bash">
r.mapcalc "dist_to_water_km = dist_to_water / 1000"
r.mapcalc "dist_to_protected_km = dist_to_protected / 1000"
r.mapcalc "dist_interchanges_km = dist_interchanges / 1000"
r.mapcalc "road_dens_perc = road_dens * 100"
r.mapcalc "forest_smooth_perc = forest_smooth * 100"
</source>

=== Sampling ===
To sample only in the analyzed counties, we will clip development layer:

<source lang="bash">
r.mapcalc "urban_2011_clip = if(counties, urban_2011)"
</source>

To estimate the number of sampling points, we can use {{cmd|r.report}} to report number of developed/undeveloped cells and their ratio.

<source lang="bash">
r.report map=urban_2011 units=h,c,p
</source>

We will sample the predictors and the response variable with 10000 random points in undeveloped areas and 2000 points in developed area:

<source lang="bash" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
r.sample.category input=urban_2011_clip output=sampling sampled=counties,devpressure_0_5,devpressure_1,slope,road_dens_perc,forest_smooth_perc,dist_to_water_km,dist_to_protected_km,dist_interchanges_km,travel_time_cities npoints=10000,2000
</source>

The attribute table can be exported as CSV file (not necessary step):

<source lang="bash" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
v.db.select map=sampling columns=urban_2011_clip,counties,devpressure_0_5,devpressure_1,slope,road_dens_perc,forest_smooth_perc,dist_to_water_km,dist_to_protected_km,dist_interchanges_km,travel_time_cities separator=comma file=samples.csv
</source>

=== Development potential ===
Now we find best model for predicting urbanization using {{AddonCmd|r.futures.potential}} which wraps an R script.

We can play with different combinations of predictors, for example:

<source lang="bash" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
r.futures.potential input=sampling output=potential.csv columns=devpressure_0_5,slope,road_dens_perc,forest_smooth_perc,dist_to_water_km,travel_time_cities developed_column=urban_2011_clip subregions_column=counties
r.futures.potential input=sampling output=potential.csv columns=devpressure_1,road_dens_perc,dist_to_water_km,dist_to_protected_km,travel_time_cities developed_column=urban_2011_clip subregions_column=counties
</source>

Or we can run R [http://www.inside-r.org/packages/cran/MuMIn/docs/dredge dredge] function to find "best" model. We can specify minimum and maximum number of predictors the final model should use.
<source lang="bash" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
r.futures.potential -d input=sampling output=potential.csv columns=devpressure_1,slope,road_dens_perc,forest_smooth_perc,dist_to_water_km,dist_to_protected_km,dist_interchanges_km,travel_time_cities developed_column=urban_2011_clip subregions_column=counties min_variables=4 max_variables=7
</source>

You can then open the output file <tt>potential.csv</tt>, which is a CSV file with tabs as separators.

For this tutorial, the final potential is created with:
<source lang="bash" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
r.futures.potential input=sampling output=potential.csv columns=devpressure_1,slope,forest_smooth_perc,dist_interchanges_km,travel_time_cities developed_column=urban_2011_clip subregions_column=counties --o
</source>

== Demand submodel ==
First we will mask out roads so that they don't influence into per capita land demand relation.
<source lang="bash">
v.to.rast input=roads type=line output=roads_mask use=val
r.mask roads_mask -i
</source>

We will use {{AddonCmd|r.futures.demand}} which derives the population vs. development relation. The relation can be linear/logarithmic/logarithmic2/exponential/exponential approach.
Look for examples of the different relations in the manual.

* linear: y = A + Bx
* logarithmic: y = A + Bln(x)
* logarithmic2: y = A + B * ln(x - C)        (requires SciPy)
* exponential: y = Ae^(BX)
* exp_approach: y = (1 - e^(-A(x - B))) + C        (requires SciPy)

The format of the input population CSV files is described in the manual. It is important to have synchronized categories of subregions and the column headers of the CSV files (in our case FIPS number). How to simply generate the list of years (for which demand is computed) is described in {{AddonCmd|r.futures.demand}} manual, for example run this in Python console:

<source lang="python">
','.join([str(i) for i in range(2011, 2036)])
</source>

Then we can create the DEMAND file:
<source lang="bash" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
r.futures.demand development=urban_1992,urban_2001,urban_2011 subregions=counties observed_population=population_trend.csv projected_population=population_projection.csv simulation_times=2011,2012,2013,2014,2015,2016,2017,2018,2019,2020,2021,2022,2023,2024,2025,2026,2027,2028,2029,2030,2031,2032,2033,2034,2035 plot=plot_demand.pdf demand=demand.csv separator=comma
</source>

In your current working directory, you should find files <tt>plot_demand.png</tt> and <tt>demand.csv</tt>.

If you have SciPy installed, you can experiment with other methods for fitting the functions:
<source lang="bash">
r.futures.demand ... method=logarithmic2
r.futures.demand ... method=exp_approach
</source>
If necessary, you can create a set of demand files produced by fitting each method separately and
then pick for each county the method which seems best and manually create a new demand file.

When you are finished, remove the mask as it is not needed for the next steps.
<source lang="bash">
r.mask -r
</source>

== Patch calibration ==
Patch calibration can be a very time consuming computation.
First we derive patches of new development by comparing historical and latest development.
We can run this on the entire area and keep only patches with minimum size 2 cells (1800 = 2 x 30 x 30 m).

<source lang="bash">
r.futures.calib development_start=urban_1992 development_end=urban_2011 subregions=counties patch_sizes=patches.txt patch_threshold=1800 -l
</source>
We obtained a file <tt>patches.txt</tt> (used later in the PGA) - a patch size distribution file - containing sizes of all found patches.

We can look at the distribution of the patch sizes:

<source lang="python">
from matplotlib import pyplot as plt
with open('patches.txt') as f:
patches = [int(patch) for patch in f.readlines()]
plt.hist(patches, 2000)
plt.xlim(0,50)
plt.show()
</source>

At this point, we start the calibration to get best parameters of patch shape
(for this tutorial, this step can be skipped and the suggested parameters are used).
First we select only one county to

<source lang="bash">
v.to.rast input=counties type=area where="FIPS == 37183" use=attr attribute_column=FIPS output=calib_county
g.region raster=calib_county zoom=calib_county
</source>

<source lang="bash"
style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
r.futures.calib development_start=urban_1992 development_end=urban_2011 subregions=calib_county patch_sizes=patches.txt calibration_results=calib.csv patch_threshold=1800 repeat=5 compactness_mean=0.1,0.3,0.5,0.7,0.9 compactness_range=0.1,0.05 discount_factor=0.1,0.3,0.5,0.7,0.9 predictors=slope,forest_smooth_perc,dist_interchanges_km,travel_time_cities demand=demand.csv devpot_params=potential.csv num_neighbors=4 seed_search=probability development_pressure=devpressure_1 development_pressure_approach=gravity n_dev_neighbourhood=10 gamma=1 scaling_factor=1 --o
</source>

== FUTURES simulation ==
We will switch back to our previous region:
<source lang="bash">
g.region raster=landuse_2011 -p
</source>

Now we have all the inputs necessary for running {{AddonCmd|r.futures.simulation}}:

The entire command is here:
<source lang="bash" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
r.futures.simulation subregions=counties developed=urban_2011 predictors=slope,forest_smooth_perc,dist_interchanges_km,travel_time_cities devpot_params=potential.csv development_pressure=devpressure_1 n_dev_neighbourhood=10 development_pressure_approach=gravity gamma=1 scaling_factor=1 demand=demand.csv discount_factor=0.3 compactness_mean=0.2 compactness_range=0.1 patch_sizes=patches.txt num_neighbors=4 seed_search=probability random_seed=1 output=final output_series=final
</source>

=== Quick description ===
The command parameters and their values:
* raster map of counties with their categories
<code>
... subregions=counties ...
</code>

* raster of developed (1), undeveloped (0) and NULLs for undevelopable areas
<code>
... developed=urban_2011 ...
</code>

* predictors selected with {{AddonCmd|r.futures.potential}} and their coefficients in a <tt>potential.csv</tt> file. The order of predictors must match the order in the file and the categories of the counties must match raster <tt>counties</tt>.
<code>
... predictors=slope,forest_smooth_perc,dist_interchanges_km,travel_time_cities devpot_params=potential.csv ...
</code>

* initial development pressure computed by {{AddonCmd|r.futures.devpressure}}, it's important to set here the same parameters
<code>
... development_pressure=devpressure_1 n_dev_neighbourhood=10 development_pressure_approach=gravity gamma=1 scaling_factor=1 ...
</code>

* per capita land demand computed by {{AddonCmd|r.futures.demand}}, the categories of the counties must match raster <tt>counties</tt>.
<code>
... demand=demand.csv ...
</code>

* patch parameters from the calibration step
<code>
... discount_factor=0.3 compactness_mean=0.4 compactness_range=0.08 patch_sizes=patches.txt ...
</code>

* recommended parameters for patch growing algorithm
<code>
... num_neighbors=4 seed_search=probability ...
</code>

* set random seed for repeatable results or set flag <tt>-s</tt> to generate seed automatically
<code>
... random_seed=1 ...
</code>

* specify final output map and optionally basename for intermediate raster maps
<code>
output=final output_series=final
</code>

=== Scenarios ===

Scenarios involving policies that encourage infill versus sprawl can be explored using the <tt>incentive_power</tt> parameter,
which uses a power function to transform the evenness of the probability gradient in POTENTIAL.

The default value is 1. You can change the power to a number between 0.25 and 4 to test urban sprawl/infill scenarios.
Higher power leads to infill behavior, lower power to urban sprawl.

= Postprocessing =

Follow a [[Creating_animation_from_FUTURES_output_in_GRASS_GIS| tutorial how to make an animation from the results]].

= See also =

* [[From GRASS GIS novice to power user (workshop at FOSS4G Boston 2017)]]
* [[Unleash the power of GRASS GIS at US-IALE 2017]]
* [[Workshop on urban growth modeling with FUTURES]]
* [[R statistics|GRASS GIS and R]]
* [[GRASS Location Wizard]]

[[Category: Tutorial]]
[[Category: FUTURES]]
[[Category: Urban]]

FUTURES tutorial

2026-05-14T16:41:45Z

Annakrat: /* Travel time to cities */

[https://grass.osgeo.org/grass-stable/manuals/addons/r.futures.html r.futures.*] is an implementation of FUTure Urban-Regional Environment Simulation (FUTURES)
which is a model for multilevel simulations of emerging urban-rural landscape structure.
FUTURES produces regional projections of landscape patterns using coupled submodels that integrate nonstationary
drivers of land change: per capita demand (DEMAND submodel), site suitability (POTENTIAL submodel),
and the spatial structure of conversion events (PGA submodel).

This tutorial shows how to prepare data and run the model. You can download [http://fatra.cnr.ncsu.edu/futures/FUTURES_triangle.zip sample dataset] and simulate urban growth
in [https://en.wikipedia.org/wiki/Research_Triangle The Triangle], region in the Piedmont of North Carolina in the United States with rapidly growing cities Raleigh, Durham and Chapel Hill.

= Prerequisites =

This tutorial requires basic knowledge of GRASS GIS. If you haven't used GRASS GIS before, you may want to first go through some of the introductory tutorials or alternative workshops linked from the [[#See also|See also section]].

= Software =
Required software includes:
* GRASS GIS 7
* addons
** {{AddonCmd|r.futures.pga}}
** {{AddonCmd|r.futures.potential}}
** {{AddonCmd|r.futures.demand}}
** {{AddonCmd|r.futures.devpressure}}
** {{AddonCmd|r.sample.category}}
* R (≥ 3.0.2) - needed for {{AddonCmd|r.futures.potential}}
* SciPy - useful for {{AddonCmd|r.futures.demand}}

= Input data used in this tutorial =
Download [http://fatra.cnr.ncsu.edu/futures/FUTURES_triangle.zip sample dataset] containing:
* digital elevation model ([http://nationalmap.gov/elevation.html NED])
* [http://www.mrlc.gov/ NLCD] 2001, 2011
* NLCD 1992/2001 Retrofit Land Cover Change Product
* transportation network ([http://www.census.gov/geo/maps-data/data/tiger-line.html TIGER])
* county boundaries ([http://www.census.gov/geo/maps-data/data/tiger-line.html TIGER])
* protected areas ([http://www.conservationgateway.org/ConservationByGeography/NorthAmerica/UnitedStates/edc/reportsdata/terrestrial/secured/Pages/default.aspx Secured Lands])
* cities above 20000 (USGS)
* county population past estimates and future projections ([https://www.osbm.nc.gov/demog/county-projections NC OSBM]) per county (nonspatial)

= Workflow =
Download sample data and unzip it. Create <tt>grassdata</tt> directory on your disk (or use the one you already have) and move there Location <tt>futures_ncspm</tt>.
Launch GRASS GIS and select your <tt>grassdata</tt> directory, Location <tt>futures_ncspm</tt> and Mapset <tt>practice1</tt>.

Install addons:
<source lang="bash">
g.extension r.futures
g.extension r.sample.category
</source>

Close GUI and restart it:
<source lang="bash">
g.gui
</source>

To install the required R packages, go to the command line terminal which was started with GRASS GIS and R:

<source lang="bash">
R
</source>

This starts the R command line where you need to execute the following code (and go through any dialogs about installation if R shows them):

<source lang="R">
install.packages(c("MuMIn", "lme4", "optparse", "rgrass7"))
</source>

== Initial steps and data preparation ==
First we will set computational region of our analyses to an extent covering our study area and so that the cells are aligned with one of our landuse rasters:
<source lang="bash">g.region raster=landuse_2011 -p</source>

We will derive urbanized areas from NLCD dataset for year 1992, 2001 and 2011
by extracting categories category 21 - 24 into a new binary map where developed is 1,
undeveloped 0 and NULL (no data) is area unsuitable for development (water, wetlands, protected areas).
First we will convert protected areas from vector to raster and set
NULLs to zeros (for simpler raster algebra expression in the next step):

<source lang="bash">
v.to.rast input=protected_areas output=protected_areas use=val
r.null map=protected_areas null=0
</source>

And then create rasters of developed/undeveloped areas using raster algebra:

<source lang="bash" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
r.mapcalc "urban_1992 = if(landuse_1992 >= 21 && landuse_1992 <= 24, 1, if(landuse_1992 == 11 || landuse_1992 >= 90 || protected_areas, null(), 0))"
r.mapcalc "urban_2001 = if(landuse_2001 >= 21 && landuse_2001 <= 24, 1, if(landuse_2001 == 11 || landuse_2001 >= 90 || protected_areas, null(), 0))"
r.mapcalc "urban_2011 = if(landuse_2011 >= 21 && landuse_2011 <= 24, 1, if(landuse_2011 == 11 || landuse_2011 >= 90 || protected_areas, null(), 0))"
</source>

We will convert vector counties to raster with the values of the FIPS attribute which links to population file:

<source lang="bash">
v.to.rast input=counties type=area use=attr attribute_column=FIPS output=counties
</source>

If we need to run FUTURES only for smaller number of counties, we can extract them based on the identifier:

<source lang="bash" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
v.to.rast input=counties type=area where="FIPS in (37183, 37101)" use=attr attribute_column=FIPS output=counties_subset
</source>

Before further steps, we will set our working directory so that the input population files and text files
we are going to create are saved in one directory and easily accessible.
You can do that from menu ''Settings'' → ''GRASS working environment'' → ''Change working directory''.
Select (or create) a directory and move there the downloaded files <tt>population_projection.csv</tt> and <tt>population_trend.csv</tt>.

== Potential submodel ==
Module {{AddonCmd|r.futures.potential}} implements POTENTIAL submodel as a part of FUTURES land change model. POTENTIAL is implemented using a set of coefficients that relate a selection of site suitability factors to the probability of a place becoming developed. This is implemented using the parameter table in combination with maps of those site suitability factors (mapped predictors). The coefficients are obtained by conducting multilevel logistic regression in R with package lme4 where the coefficients may vary by county. The best model is selected automatically using dredge function from package [https://cran.r-project.org/web/packages/MuMIn/index.html MuMIn].

First, we will derive couple of predictors.
=== Predictors ===
==== Slope ====
We will derive slope in degrees from digital elevation model using {{cmd|r.slope.aspect}} module:
<source lang="bash">r.slope.aspect elevation=elevation_30m slope=slope</source>

==== Distance from lakes/rivers ====
First we will extract [http://www.mrlc.gov/nlcd11_leg.php category ''Open Water''] from 2011 NLCD dataset:
<source lang="bash">
r.mapcalc "water = if(landuse_2011 == 11, 1, null())"
</source>

Then we compute the distance to water with module {{cmd|r.grow.distance}} and set color table to shades of blue:
<source lang="bash">
r.grow.distance input=water distance=dist_to_water
r.colors -n map=dist_to_water color=blues
</source>

==== Distance from protected areas ====
We will use raster protected of protected areas we already created, but we will set NULL values to zero.
We compute the distance to protected areas with module {{cmd|r.grow.distance}} and set color table from green to red:
<source lang="bash">
r.null map=protected_areas setnull=0
r.grow.distance input=protected_areas distance=dist_to_protected
r.colors map=dist_to_protected color=gyr
</source>

==== Forests ====
We will smooth the transition between forest and other land use, see NLCD [http://www.mrlc.gov/nlcd11_leg.php category ''Open Water'']:
<source lang="bash">
r.mapcalc "forest = if(landuse_2011 >= 41 && landuse_2011 <= 43, 1, 0)"
r.neighbors -c input=forest output=forest_smooth size=15 method=average
r.colors map=forest_smooth color=ndvi
</source>

==== Travel time to cities ====
Here we will compute travel time to cities (> population 20000)
as cumulative cost distance where cost is defined as travel time on roads.
First we specify the speed on different types of roads.
We copy the roads raster into our mapset so that we can change it
by adding a new attribute field <tt>speed</tt>. Then we assign speed values (km/h) based on the type of road:

<source lang="bash">
g.copy vector=roads,myroads
v.db.addcolumn map=myroads columns="speed double precision"
v.db.update map=myroads column=speed value=50 where="MTFCC = 'S1400'"
v.db.update map=myroads column=speed value=100 where="MTFCC IN ('S1100', 'S1200')"
</source>

Now we rasterize the selected road types using the speed values from the attribute table as raster values.

<source lang="bash" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
v.to.rast input=myroads type=line where="MTFCC IN ('S1100', 'S1200', 'S1400')" output=roads_speed use=attr attribute_column=speed
</source>

We set the rest of the area to low speed and recompute the speed as time to travel through a 30m cell in minutes:

<source lang="bash">
r.null map=roads_speed null=5
r.mapcalc "roads_travel_time = 1.8 / roads_speed"
</source>

Finally we compute the travel time to larger cities using {{cmd|r.cost}}:

<source lang="bash">
r.cost input=roads_travel_time output=travel_time_cities start_points=cities_20000 memory=3000
r.colors map=travel_time_cities color=byr
</source>

==== Road density ====
We will rasterize roads and use moving window analysis ({{cmd|r.neighbors}}) to compute road density:

<source lang="bash">
v.to.rast input=roads output=roads use=val
r.null map=roads null=0
r.neighbors -c input=roads output=road_dens size=25 method=average
</source>

==== Distance to interchanges ====

We will consider TIGER roads of type <tt>Ramp</tt> as interchanges, rasterize them and compute euclidean distance to them:

<source lang="bash">
v.to.rast input=roads type=line where="MTFCC = 'S1630'" output=interchanges use=val
r.grow.distance -m input=interchanges distance=dist_interchanges
</source>

=== Development pressure ===

We compute development pressure with {{AddonCmd|r.futures.devpressure}}. Development pressure is a predictor based on number of neighboring developed cells within search distance, weighted by distance. The development pressure variable plays a special role in the model, allowing for a feedback between predicted change and change in subsequent steps.

<source lang="bash" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
r.futures.devpressure -n input=urban_2011 output=devpressure_1 method=gravity size=10 gamma=1 scaling_factor=1
r.futures.devpressure -n input=urban_2011 output=devpressure_0_5 method=gravity size=30 gamma=0.5 scaling_factor=0.1
</source>

When gamma increases, development influence decreases more rapidly with distance.
Size is half the size of the moving window. When gamma is low, local development influences more distant places.
We will derive 2 layers with different gamma and size parameters for the potential statistical model.

=== Rescaling variables ===

First we will look at the ranges of our predictor variables by running a short Python code snippet in Python tab in GUI:

<source lang="python" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
for name in ['slope', 'dist_to_water', 'dist_to_protected', 'forest_smooth', 'travel_time_cities', 'road_dens', 'dist_interchanges', 'devpressure_0_5', 'devpressure_1']:
minmax = grass.raster_info(name)
print name, minmax['min'], minmax['max']
</source>

We will rescale some of our input variables:

<source lang="bash">
r.mapcalc "dist_to_water_km = dist_to_water / 1000"
r.mapcalc "dist_to_protected_km = dist_to_protected / 1000"
r.mapcalc "dist_interchanges_km = dist_interchanges / 1000"
r.mapcalc "road_dens_perc = road_dens * 100"
r.mapcalc "forest_smooth_perc = forest_smooth * 100"
</source>

=== Sampling ===
To sample only in the analyzed counties, we will clip development layer:

<source lang="bash">
r.mapcalc "urban_2011_clip = if(counties, urban_2011)"
</source>

To estimate the number of sampling points, we can use {{cmd|r.report}} to report number of developed/undeveloped cells and their ratio.

<source lang="bash">
r.report map=urban_2011 units=h,c,p
</source>

We will sample the predictors and the response variable with 10000 random points in undeveloped areas and 2000 points in developed area:

<source lang="bash" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
r.sample.category input=urban_2011_clip output=sampling sampled=counties,devpressure_0_5,devpressure_1,slope,road_dens_perc,forest_smooth_perc,dist_to_water_km,dist_to_protected_km,dist_interchanges_km,travel_time_cities npoints=10000,2000
</source>

The attribute table can be exported as CSV file (not necessary step):

<source lang="bash" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
v.db.select map=sampling columns=urban_2011_clip,counties,devpressure_0_5,devpressure_1,slope,road_dens_perc,forest_smooth_perc,dist_to_water_km,dist_to_protected_km,dist_interchanges_km,travel_time_cities separator=comma file=samples.csv
</source>

=== Development potential ===
Now we find best model for predicting urbanization using {{AddonCmd|r.futures.potential}} which wraps an R script.

We can play with different combinations of predictors, for example:

<source lang="bash" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
r.futures.potential input=sampling output=potential.csv columns=devpressure_0_5,slope,road_dens_perc,forest_smooth_perc,dist_to_water_km,travel_time_cities developed_column=urban_2011_clip subregions_column=counties
r.futures.potential input=sampling output=potential.csv columns=devpressure_1,road_dens_perc,dist_to_water_km,dist_to_protected_km,travel_time_cities developed_column=urban_2011_clip subregions_column=counties
</source>

Or we can run R [http://www.inside-r.org/packages/cran/MuMIn/docs/dredge dredge] function to find "best" model. We can specify minimum and maximum number of predictors the final model should use.
<source lang="bash" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
r.futures.potential -d input=sampling output=potential.csv columns=devpressure_1,slope,road_dens_perc,forest_smooth_perc,dist_to_water_km,dist_to_protected_km,dist_interchanges_km,travel_time_cities developed_column=urban_2011_clip subregions_column=counties min_variables=4 max_variables=7
</source>

You can then open the output file <tt>potential.csv</tt>, which is a CSV file with tabs as separators.

For this tutorial, the final potential is created with:
<source lang="bash" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
r.futures.potential input=sampling output=potential.csv columns=devpressure_1,slope,forest_smooth_perc,dist_interchanges_km,travel_time_cities developed_column=urban_2011_clip subregions_column=counties --o
</source>

== Demand submodel ==
First we will mask out roads so that they don't influence into per capita land demand relation.
<source lang="bash">
v.to.rast input=roads type=line output=roads_mask use=val
r.mask roads_mask -i
</source>

We will use {{AddonCmd|r.futures.demand}} which derives the population vs. development relation. The relation can be linear/logarithmic/logarithmic2/exponential/exponential approach.
Look for examples of the different relations in the manual.

* linear: y = A + Bx
* logarithmic: y = A + Bln(x)
* logarithmic2: y = A + B * ln(x - C)        (requires SciPy)
* exponential: y = Ae^(BX)
* exp_approach: y = (1 - e^(-A(x - B))) + C        (requires SciPy)

The format of the input population CSV files is described in the manual. It is important to have synchronized categories of subregions and the column headers of the CSV files (in our case FIPS number). How to simply generate the list of years (for which demand is computed) is described in {{AddonCmd|r.futures.demand}} manual, for example run this in Python console:

<source lang="python">
','.join([str(i) for i in range(2011, 2036)])
</source>

Then we can create the DEMAND file:
<source lang="bash" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
r.futures.demand development=urban_1992,urban_2001,urban_2011 subregions=counties observed_population=population_trend.csv projected_population=population_projection.csv simulation_times=2011,2012,2013,2014,2015,2016,2017,2018,2019,2020,2021,2022,2023,2024,2025,2026,2027,2028,2029,2030,2031,2032,2033,2034,2035 plot=plot_demand.pdf demand=demand.csv separator=comma
</source>

In your current working directory, you should find files <tt>plot_demand.png</tt> and <tt>demand.csv</tt>.

If you have SciPy installed, you can experiment with other methods for fitting the functions:
<source lang="bash">
r.futures.demand ... method=logarithmic2
r.futures.demand ... method=exp_approach
</source>
If necessary, you can create a set of demand files produced by fitting each method separately and
then pick for each county the method which seems best and manually create a new demand file.

When you are finished, remove the mask as it is not needed for the next steps.
<source lang="bash">
r.mask -r
</source>

== Patch calibration ==
Patch calibration can be a very time consuming computation.
First we derive patches of new development by comparing historical and latest development.
We can run this on the entire area and keep only patches with minimum size 2 cells (1800 = 2 x 30 x 30 m).

<source lang="bash">
r.futures.calib development_start=urban_1992 development_end=urban_2011 subregions=counties patch_sizes=patches.txt patch_threshold=1800 -l
</source>
We obtained a file <tt>patches.txt</tt> (used later in the PGA) - a patch size distribution file - containing sizes of all found patches.

We can look at the distribution of the patch sizes:

<source lang="python">
from matplotlib import pyplot as plt
with open('patches.txt') as f:
patches = [int(patch) for patch in f.readlines()]
plt.hist(patches, 2000)
plt.xlim(0,50)
plt.show()
</source>

At this point, we start the calibration to get best parameters of patch shape
(for this tutorial, this step can be skipped and the suggested parameters are used).
First we select only one county to

<source lang="bash">
v.to.rast input=counties type=area where="FIPS == 37183" use=attr attribute_column=FIPS output=calib_county
g.region raster=calib_county zoom=calib_county
</source>

<source lang="bash"
style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
r.futures.calib development_start=urban_1992 development_end=urban_2011 subregions=calib_county patch_sizes=patches.txt calibration_results=calib.csv patch_threshold=1800 repeat=5 compactness_mean=0.1,0.3,0.5,0.7,0.9 compactness_range=0.1,0.05 discount_factor=0.1,0.3,0.5,0.7,0.9 predictors=slope,forest_smooth_perc,dist_interchanges_km,travel_time_cities demand=demand.csv devpot_params=potential.csv num_neighbors=4 seed_search=2 development_pressure=devpressure_1 development_pressure_approach=gravity n_dev_neighbourhood=10 gamma=1 scaling_factor=1 --o
</source>

== FUTURES simulation ==
We will switch back to our previous region:
<source lang="bash">
g.region raster=landuse_2011 -p
</source>

Now we have all the inputs necessary for running {{AddonCmd|r.futures.pga}}:

The entire command is here:
<source lang="bash" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
r.futures.pga subregions=counties developed=urban_2011 predictors=slope,forest_smooth_perc,dist_interchanges_km,travel_time_cities devpot_params=potential.csv development_pressure=devpressure_1 n_dev_neighbourhood=10 development_pressure_approach=gravity gamma=1 scaling_factor=1 demand=demand.csv discount_factor=0.3 compactness_mean=0.2 compactness_range=0.1 patch_sizes=patches.txt num_neighbors=4 seed_search=2 random_seed=1 output=final output_series=final
</source>

=== Quick description ===
The command parameters and their values:
* raster map of counties with their categories
<code>
... subregions=counties ...
</code>

* raster of developed (1), undeveloped (0) and NULLs for undevelopable areas
<code>
... developed=urban_2011 ...
</code>

* predictors selected with {{AddonCmd|r.futures.potential}} and their coefficients in a <tt>potential.csv</tt> file. The order of predictors must match the order in the file and the categories of the counties must match raster <tt>counties</tt>.
<code>
... predictors=slope,forest_smooth_perc,dist_interchanges_km,travel_time_cities devpot_params=potential.csv ...
</code>

* initial development pressure computed by {{AddonCmd|r.futures.devpressure}}, it's important to set here the same parameters
<code>
... development_pressure=devpressure_1 n_dev_neighbourhood=10 development_pressure_approach=gravity gamma=1 scaling_factor=1 ...
</code>

* per capita land demand computed by {{AddonCmd|r.futures.demand}}, the categories of the counties must match raster <tt>counties</tt>.
<code>
... demand=demand.csv ...
</code>

* patch parameters from the calibration step
<code>
... discount_factor=0.3 compactness_mean=0.4 compactness_range=0.08 patch_sizes=patches.txt ...
</code>

* recommended parameters for patch growing algorithm
<code>
... num_neighbors=4 seed_search=2 ...
</code>

* set random seed for repeatable results or set flag <tt>-s</tt> to generate seed automatically
<code>
... random_seed=1 ...
</code>

* specify final output map and optionally basename for intermediate raster maps
<code>
output=final output_series=final
</code>

=== Scenarios ===

Scenarios involving policies that encourage infill versus sprawl can be explored using the <tt>incentive_power</tt> parameter,
which uses a power function to transform the evenness of the probability gradient in POTENTIAL.

The default value is 1. You can change the power to a number between 0.25 and 4 to test urban sprawl/infill scenarios.
Higher power leads to infill behavior, lower power to urban sprawl.

= Postprocessing =

Follow a [[Creating_animation_from_FUTURES_output_in_GRASS_GIS| tutorial how to make an animation from the results]].

= See also =

* [[From GRASS GIS novice to power user (workshop at FOSS4G Boston 2017)]]
* [[Unleash the power of GRASS GIS at US-IALE 2017]]
* [[Workshop on urban growth modeling with FUTURES]]
* [[R statistics|GRASS GIS and R]]
* [[GRASS Location Wizard]]

[[Category: Tutorial]]
[[Category: FUTURES]]
[[Category: Urban]]

GRASS Community Meeting San Michele 2026

2026-05-08T16:32:10Z

Annakrat: /* Agenda */

[[File:Sanmichele.png|frameless|center|1000px|San Michele all'Adige]]

{{toc|right}}

The ''GRASS Community Meeting'' for contributors and developers will be happening from '''July 11 - 19, 2026''' in [https://www.openstreetmap.org/relation/46990#map=12/46.1349/11.1947 San Michele all'Adige, Trentino, Italy].

== Sponsors ==

Sponsors make the event possible. Learn more about [https://grass.osgeo.org/contribute/sponsoring/ Sponsoring].

* [https://www.osgeo.org/ OSGeo]: 2500 USD (see [https://wiki.osgeo.org/w/index.php?title=GRASS_Community_Meeting_2026:_Budget budget]]).

[[File:Osgeo logo.png|none|left|alt=Light and dark green logo of OSGeo saying Your Open Source Compass|Open Source Geospatial Foundation]]

== Purpose ==
The ''GRASS Community Meeting'' is a great occasion for folks to support the development by actively contributing to the project in different ways. These include source code updates, documentation (manuals, wiki, tutorials), translations, website improvements 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 project and the interfaces to QGIS, GDAL, PostGIS, R, OGC Services and others.

The focus is on GRASS maintenance, and interaction with other projects. Many maintenance tasks, infrastructure changes, and planning of large changes especially benefits from maintainers being in one place and time zone. While the specific topics highly depend on the participants, we will prioritize topics which require highly synchronous collaboration, such as the CMake build system transition and API transitions. The [https://grass.osgeo.org/news/2025_05_27_grass_dev_summit_report/ 2025 event report] gives an overview of what was achieved last year.

We do require participants to work on GRASS or connections to other projects. However, we leave them the freedom to work on what they think is the best contribution to the project given their skills and time available.

== Agenda ==

Agenda is being refined.

=== Saturday, July 11 ===

Day of arrival. Contact organizers if you are interested in individualized program or helping with organization.

=== Sunday, July 12 ===

* Hybrid meeting about 8.6.0 with FHS and Jupyter in GUI updates

=== Monday, July 13 ===

* FHS
* Updating the GRASS Roadmap

=== Tuesday, July 14 ===

* GSoC (may be moved to different day)
* GeoAI

=== Wednesday, July 15 ===

* Python API review
* Plan PSC elections

=== Thursday, July 16 ===

* Reducing PR backlog

=== Friday, July 17 ===

* Address issues for 8.6.0 release

=== Saturday, July 18 ===

* Website review

=== Sunday, July 19 ===

Day of departure.

== Participation ==

Please add your name here:

{|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:Lucadelu|Luca Delucchi]]
| Italy
|
|
|
|
|-
|2
| [[User:wenzeslaus|Vaclav Petras]]
| United States
| 11.07.
| 19.07.
| grass.tools, pytest, subcommands, reviews
|
|-
|3
| [[User:Annakrat|Anna Petrasova]]
| United States
| 11.07.
| 19.07.
| GSoC, reviews, PR backlog, tutorials
|
|-
|4
| [[User:Neteler|Markus Neteler]]
| Germany
|
|
|
|
|-
|5
| [[User:Sbl|Stefan Blumentrath]]
| Norway
| 11.07. (presumably)
| 18.07. (presumably)
| Handling Copernicus data with GRASS / actinia
|
|-
|6
| [[User:Hellik|Helmut Kudrnovsky]]
| Austria
|
|
|
|
|-
|7
| [[User:Veroandreo|Verónica Andreo]]
| Argentina
| 11.07.
| 19.07.
|
|
|-
|8
| [[User:Ctwhite|Corey White]]
| United States
| 11.07.
| 19.07.
| grass.jupyter, documentation, website, reviews, tutorials
|
|-
|}

Registration is free; participants cover their own travel and lodging, often with employer support — thank you. Ideally we'd reimburse everyone, and every [https://numfocus.org/donate-to-grass donation] or [https://grass.osgeo.org/contribute/sponsoring/ employer sponsorship] of the project helps us get closer.

== Venue ==
The meeting will be hosted at [https://fmach.it/ Fondazione Edmund Mach] (FEM) in San Michele all'Adige, Trentino, Italy — about 15 km north of Trento. FEM is a research and education center with on-site facilities that allow participants to work, sleep, and eat in the same location.

[https://maps.app.goo.gl/5YEuEts6qXvky7HD9 Map]

=== Getting there ===

San Michele all'Adige is reachable by train on the Trento–Bolzano line (San Michele all'Adige–Mezzocorona station), with frequent connections from Trento (~15 minutes) and Verona (~1 hour). The nearest airports are Verona (VRN), Venice Marco Polo (VCE) and Treviso (TSF), Milan Bergamo (BGY), Malpensa (MXP), and Linate (LIN), Bologna (BLQ), and Innsbruck (INN) in Austria. Trento is also the host city of FOSS4G Italy 2026 (July 9–11), making it convenient to combine both events.

== Accommodation and Costs ==

''Registration is free''. However, participants should plan for the following costs:

* Travel
* Lodging

Participants can stay on-site at the FEM convitto (dormitory), keeping the community together for the full duration of the meeting:

* €35 per person per night
* Double and triple rooms (triples include a small kitchen)
* A mandatory on-site supervisor is required at €200 per night (flat fee, shared across the group)
* Family members are welcome to stay in the dormitory as well
* [https://cif.fmach.it/content/download/2701/78358/file/brochure_convitto.pdf Brochure]
* Details to be communicated soon.

For anyone preferring alternative lodging, hotels and B&Bs are available in San Michele and nearby Trento.

Lunches on weekdays can be taken at the FEM canteen (mensa), located on the same campus. Details and pricing are being finalized.

== Individual Preparation ==

* Bring your own computer
* Bring {{wikipedia|AC power plugs and sockets|power adapter}} if needed (Italy: 230V, 50Hz, {{wikipedia|Europlug|Type C}}, {{wikipedia|Schuko|Type F}}, and {{wikipedia|AC power plugs and sockets: L|Type L}} sockets are common)
* Install git and the compiler tools, and come with a working GRASS development environment if possible. See [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md here] for details.

== FAQ ==

* ''Is this a conference?''
** Talks or presentations may be included, but the purpose is to work together on the project. Among conference formats, the closest comparison would be a participatory workshop.
* ''Is this a hackathon?''
** While there is plenty of intensive coding, the meeting is not competitive. We meet to collaborate.
* ''Is the GRASS Community Meeting for developers only?''
** No, the meeting is open to all users, supporters, contributors, power users, and developers ''who want to make a meaningful contribution to the project''.
* ''What skills do I need?''
** Coding skills are not required. Contributions to documentation, tutorials, translations, website, and testing are all valuable. Practical help during the meeting, such as coordinating meals, photography, or reporting, is a real contribution too.
* ''Can I attend remotely?''
** The meeting is in-person, but everyone is welcome to use the same week for focused work on the project from wherever they are.
* ''What language is used during the meeting?''
** English is the working language, but you may hear several other languages spoken at the event.
* ''How was it last time?''
** Splendid! See [[GRASS Developer Summit Raleigh 2025]]!
* ''Where can I get help and more information about the community meeting?''
** Contact local organizer [[User:Lucadelu|Luca Delucchi]] (<tt><lucadeluge at gmail com></tt>) or [[User:wenzeslaus|Vaclav Petras]] (<tt><wenzeslaus at gmail com></tt>) for budget questions.
* ''What if I can't spend time on this?''
** Can you spend money instead? [https://numfocus.org/donate-to-grass Donate to GRASS through NumFOCUS] to help keep the project going.

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2026]]

GRASS Community Meeting San Michele 2026

2026-05-05T13:23:32Z

Annakrat: /* Participation */

GRASS GSoC Ideas 2026

2026-05-04T02:31:41Z

Annakrat: Add template for accepted ideas

== About ==
Important: While we are still an OSGeo project, we changed our fiscal sponsor to [https://numfocus.org/ NumFOCUS].

''As a result, GRASS participates in GSoC under the [https://numfocus.org/ NumFOCUS] umbrella organization.''

Read more about our governance [https://grass.osgeo.org/about/governance/ on GRASS website].

* [https://numfocus.org/programs/google-summer-code The NumFOCUS GSoC main page]
* [https://github.com/numfocus/gsoc/blob/master/CONTRIBUTING-contributors.md NumFOCUS guidelines for contributors].
* [https://summerofcode.withgoogle.com/ Official GSoC page at Google]

== Accepted ideas ==
=== Idea title ===
* Student:
* Mentors:
* [[GRASS_GSoC_2025_Add_JSON_output_to_different_tools_in_C|Example of Wiki page]]

== AI Tool Usage Policy ==
We acknowledge that applicants may use AI tools (like ChatGPT, Copilot, etc.) to assist with proposal writing and coding. However:

* Your proposal should reflect your own understanding and voice. AI-generated "slop" (overly generic or regurgitated content) is easy to spot and will hurt your application.
* We evaluate applications primarily on GitHub contributions and communication with the GRASS community, not just proposal polish.
* Show us you understand the project through high-quality pull requests on GitHub.
* Disclose AI usage: If you use AI tools in your proposal or code contributions, please disclose the extent to which you used them (e.g., for brainstorming, proofreading, code suggestions, etc.).

== Ideas ==
If you are a student you can suggest a new idea or pick up an existing one. In any case write about it to [https://discourse.osgeo.org/c/grass/developer/61 OSGeo Discourse forum for GRASS developers], [https://github.com/OSGeo/grass/discussions GitHub Discussions], or [https://gitter.im/grassgis/community Gitter].

You are invited as well to have a close look at ideas from previous years ([https://trac.osgeo.org/grass/wiki/GSoC/2014 2014], [https://trac.osgeo.org/grass/wiki/GSoC/2015 2015], [https://trac.osgeo.org/grass/wiki/GSoC/2016 2016],
[https://trac.osgeo.org/grass/wiki/GSoC/2017 2017],
[https://trac.osgeo.org/grass/wiki/GSoC/2018 2018],
[https://trac.osgeo.org/grass/wiki/GSoC/2019 2019],
[https://trac.osgeo.org/grass/wiki/GSoC/2020 2020],
[https://trac.osgeo.org/grass/wiki/GSoC/2021 2021],
[https://trac.osgeo.org/grass/wiki/GSoC/2022 2022],
[https://trac.osgeo.org/grass/wiki/GSoC/2023 2023])
which have not yet been implemented.
You can also look at accepted GRASS GSoC [https://trac.osgeo.org/grass/wiki/GSoC projects from previous years] for an idea of scope.''

=== Parallelization of existing tools ===

There are several tools that would benefit from parallelization with OpenMP, e.g. r.texture, r.fill.stats, r/v.surf.idw, r.viewshed, v.to.rast, r.grow.distance, v.surf.bspline, r.proj, ...
For overview of current state, see [[Raster_Parallelization_with_OpenMP]].

* Requirements: familiarity with C, OpenMP
* Mentor: Huidae Cho
* Co-mentor: Vaclav Petras, Anna Petrasova
* Project length: Large (350 hours)
* Rating: difficult
* Expected Outcomes: parallelized 2-5 tools, depending on complexity
* Test of skills (one or more):
** Address https://github.com/OSGeo/grass/issues/5776 (carefully read the existing conversation in the issue and linked PR)
** Pick a tool and develop prototype implementation of the parallelization.

=== Improve GRASS user experience in Jupyter Notebook ===
[[File:Jupyter_interactive_viewshed.png|500px|thumb|right|InteractiveMap in grass.jupyter library]]
Python package [https://grass.osgeo.org/grass-stable/manuals/libpython/grass.jupyter.html grass.jupyter] was developed during [https://trac.osgeo.org/grass/wiki/GSoC/2021/JupyterAndGRASS GSoC 2021] to simplify running GRASS from Jupyter Notebooks and displaying data. This project could focus on adding features such as better symbology handling and adding legend to InteractiveMap and better integration with matplotlib.

* Requirements: Python
* Mentor: Anna Petrasova
* Co-mentor: Vaclav Petras, Helena Mitasova, Corey White
* Project length: Large (350 hours)
* Rating: easy to medium
* Expected Outcomes: improved user experience when using GRASS through notebooks
* Test of skills: write a test for [https://github.com/OSGeo/grass/tree/main/python/grass/jupyter grass.jupyter library] using python unittest or pytest, more info [https://grass.osgeo.org/grass-devel/manuals/libpython/gunittest_testing.html here] or rewrite some of the functions in grass.jupyter library using the new [https://grass.osgeo.org/grass-devel/manuals/python_intro.html#running-tools Tools API].

=== Add JSON output to different tools ===
There are several tools in GRASS that would benefit from a JSON-formatted output.
Besides adding the JSON output, the work would also include adding tests and basic documentation.
* Requirements: C, Python
* Mentor: Vaclav Petras
* Co-mentor: Anna Petrasova, Corey White
* Project length: Large (350 hours)
* Rating: easy to medium
* Expected Outcomes: 10-20 tools (depending on project length and complexity of the tool) tools with well tested JSON output
* Note: A lot of work on JSON was already done, but there is more! Some of the remaining tools require more design. There are also Python tools (not just C which was the focus previously) and then also the grass-addons repo. Some tools also don't have any machine readable output right now and should. Also current tools which use other tools should use the new JSON as opposed to what they are using now. Preparing a well-reasoned list of tasks is a part of the application.
* Test of skills (pick one or more):
** https://github.com/OSGeo/grass/issues/6968
** https://github.com/OSGeo/grass/issues/6969
** https://github.com/OSGeo/grass/issues/6970

=== Support writing tests with pytest ===

* The current testing framework, ''[https://grass.osgeo.org/grass-stable/manuals/libpython/gunittest.html grass.gunittest]'', was written before migration to Git/GitHub and when long free runs in 3rd party services were unthinkable. Additionally, some no longer relevant goals were prioritized, such as independence on the current code, detailed custom HTML reports, success tracking over time, and high specialization towards GRASS-specifics.
* ''grass.gunittest'' is based on Python ''unittest'' package and many projects since then migrated to //pytest//, e.g., GDAL and Numpy. While ''unittest'' is inspired by Java's JUnit, ''pytest'' is designed to support writing small, readable tests, and uses plain `assert` statements instead of many different assert methods.
* Using ''pytest'' should lead to tests which feel more like Python scripts and to minimum of testing-specific code.
* An example issue of ''grass.gunittest'' is that it doesn't work well with tests of the main GRASS executable (prominence of `grass ... --exec` is yet another new thing which changed since ''grass.gunittest'' was designed).
* Two main things needed:
** Create general comparison functions from the ''grass.gunittest'' assert methods so that they can be used with pytest.
** Current grass.script.setup.init function and grass.script.core.create_location function don't work well in the context of a pytest test function. More
* Additional things needed:
** Fixture for pytest to set up and tear down a GRASS session in a temporary mapset.

* Requirements: Python
* Project length: Large (350 hours)
* Mentor: Vaclav Petras
* Co-mentor: Stefan Blumentrath
* Proposed by: Vaclav Petras
* Rating: easy to medium
* Expected Outcomes: Convenient way of writing tests with pytest
* Test of skills: Fix failing tests and/or write new tests (more is better). Alternatively, addressing a smaller problem in the testing framework is a good task, too.

=== Fix known code defects ===

* Fix code defects (security or code quality) such as those reported by Coverity Scan.
* Mentors: Vaclav Petras
* Co-mentors: Nicklas Larsson
* Proposed by: Vaclav Petras
* Project length: Large (350 hours)
* Rating: medium
* Requirements:
** Language: C
** Proposal: Define milestones which will be used during the evaluation.
* Expected outcomes:
** Reduction of issues by 70-100%.
** New tests for changed code if missing.
* Test and training tasks (complete more than one): Fix e.g., [https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html GCC Static Analysis], [https://clang.llvm.org/docs/ClangStaticAnalyzer.html Clang Static Analyzer] or [https://cppcheck.sourceforge.io Cppcheck] issues.

=== Subcommand CLI for GRASS ===

* Make running of GRASS tools in command line as easy as possible.
** `grass run r.slope.aspect elevation=elevation.tiff slope=slope.tiff aspect=aspect.tiff`
* Project length: Large (350 hours)
* Rating: medium
* Requirements:
** Language: Python
** Proposal: Student needs to show sufficient understanding of data and project handling in GRASS. Furthermore, the proposal needs to present, at least, concrete formulation of ideas, identification of missing and existing parts, and new subcommands.
* Mentors: Vaclav Petras
* Co-mentors: Stefan Blumentrath, Corey White
* Proposed by: Vaclav Petras
* Expected outcomes:
** A subcommand which runs a GRASS tool on GeoTiff and GeoPackage in one step.
** A complete parity with the existing CLI.
** An underlying Python API which will be used to implement the CLI.
* Test and training tasks (complete one or more): Add a subcommand, sub-subcommand, or an option to the experimental interface (with tests).
** Add `--region` to set a temporary computational region for the execution, e.g. `--region="raster=raster_name"`.
** Add `--import-raster=some/file.tiff` which imports (r.import) a raster file (same for vector and similarly for export).
** Add `--link-raster=some/file.tiff` which links (r.external) a raster file (same for vector and similarly for r.external.out).

Current state:

# Reveals the existing subcommands
PYTHONPATH=$(grass --config python-path) python -m grass.app --help
# Allows running subset of commands
grass run --help


=== GUI: Add space-time datasets support in Data Catalog ===
[[File:GUI_data_tab.png|400px|thumb|right|Data catalog]]
Currently GRASS Data Catalog shows only raster and vector maps. The goal of this project is to add support for space-time datasets. It is mainly space-time raster datasets. In the next phase of the project support for other types of space-time datasets (vector and 3D raster) could be added. Besides displaying space-time datasets in the layer tree, it is also about adding the equivalent functionality currently available for raster and vector layers from the context menu.

* Requirements: familiar with Python
* Project length: Large (350 hours)
* Mentor: Martin Landa
* Co-mentor: Anna Petrasova
* Proposed by: Martin Landa
* Rating: medium
* Expected Outcomes: 175 hours basic support for space-time raster datasets; 350 extended support also for other space-time datasets types (vector, 3D raster)
* Test of skills:
** suggest/implement solution for completing https://github.com/OSGeo/grass/issues/2599

=== Searchable metadata in Space Time Datasets ===
The temporal framework in GRASS was initially developed almost 15 years ago. Spatio-temporal data has become more widely available since then and new standards emerged like e.g. ''[https://docs.ogc.org/cs/25-004/25-004.html STAC]'' with ''[https://github.com/stac-extensions/stac-extensions.github.io extensions]'', or the ''[https://cfconventions.org/ CF-conventions]''. The aim of this project is to extend the metadata model in the temporal framework to improve discoverability of map datasets registered in TGIS and to allow users to embed extended metadata with the registered maps in a Space Time Dataset in a searchable way. Ideally, the new model is able to account for the standards mentioned above.

See also: https://github.com/OSGeo/grass/issues/1938

* Requirements: Python, SQL, JSON
* Project length: Large (350 hours)
* Mentor: Stefan Blumentrath
* Co-mentor: ???
* Proposed by: Stefan Blumentrath
* Rating: medium
* Expected Outcomes:
** an updated TGIS database model (version 4) that:
*** is oriented on relevant metadata standards (STAC, CF-Convention, ...)
*** allows to use metadata in temporal_where to select relevant elements of Space time datasets
** updated tool to create space time datasets (t.create) in the TGIS database with extended metadata
** updated tool to register map datasets (t.register) in the TGIS database with extended metadata
** Conversion tool for database Upgrades (v3 to v4)
** a new tool to update / modify metadata in the TGIS database
** Storage of timeseries metadata for both C-based and temporal Tools

* Test of skills (e.g.):
** address one or more sub-tasks from https://github.com/OSGeo/grass/issues/3427 (add append-mode to selected new tool(s))
** suggest/implement solution for https://github.com/OSGeo/grass/issues/3394 (more complex task)
** suggest/implement solution for https://github.com/OSGeo/grass/issues/7041

=== Add {your research idea} to GRASS ===

* In general, you can propose any topic, but you can specifically propose integrating your research or research idea into GRASS.
* Requirements:
** Language:
*** Depends on the project, often Python, sometimes C.
*** Adding your latest ecological analysis
** Proposal:
*** Discuss relevance to GRASS.
*** Describe technical steps needed for integration.
*** Describe whether it is an addition of a tool (module) or a change in one of the libraries. If it is a tool, specify if it should be included in the core grass repository or in grass-addons repository and why.
*** Specify what research was done and what needs to be accomplished in order to have usable product at the end of summer.
*** Specify who will provide the research expertise.
* Project length: Large (350 hours)
* Rating: from low to hard
* Mentors:
** GRASS project will provide technical mentors, but it is up to the applicant to ensure the research part is mentored well. An exception may be granted to applicants which can demonstrate that the research is finished or that they have enough expertise themselves.
** Possible technical mentors: Vaclav Petras, Anna Petrasova
** Research mentors: Bring in an expert from your field, e.g., your academic advisor or project principal investigator (if needed).
* Proposed by: Vaclav Petras
* Expected outcome: Working feature which is integrated and merged at the end of the project.
* Test and training tasks:
** Create a test in Python for an existing tool in the grass-addons repository or in the core grass repository.

=== Title of idea ===

Description here

* Requirements:
* Project length: (175 or 350 hours)
* Mentor:
* Proposed by:
* Rating:
* Expected Outcomes:
* Test of skills:
* Other:

== Tips for students ==
* Follow official [https://github.com/numfocus/gsoc/blob/master/CONTRIBUTING-contributors.md NumFOCUS guidelines].
* Include "GRASS" in the title of our idea to easily distinguish ideas and projects inside NumFOCUS.
* If you have your own ideas we encourage you to propose them. Explain them on the [https://discourse.osgeo.org/c/grass/developer/61 on our Discourse].
* Follow some good practices in your ideas and proposals:
** Stress why the project would be useful.
** Show that you know how you will proceed. That is, make sure that you can demonstrate that the proposal is feasible in the given time frame.
** Be specific in the implementation (or at least as specific as you can).
** Explain what the final product will look like and how it will work. You can add drawings or mock-ups.
** Explain how the idea relates to existing GRASS functions, features, and needs.
** Do not include steps such as "install GRASS", "compile GRASS libraries (on my machine)", "read about the API". You should do this before applying to GSoC.
* Compile GRASS from source and prepare environment for development:
** Read [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md CONTRIBUTING file].
* Prove your worth by being active on the [https://discourse.osgeo.org/c/grass/developer/61 GRASS Discourse] or other channels ([https://github.com/OSGeo/grass/discussions GitHub Discussions], fix some [https://github.com/OSGeo/grass/issues bugs], and/or implement some (smaller) features, or write some (simpler) GRASS module, and post it to mailing list. There's no better way to demonstrate your willingness and abilities. Do this before start you apply to GSoC.
* Also note that fixing existing bugs and/or implementing enhancements will be a part of student evaluation.

{{GSoC}}

GRASS GSoC Ideas 2026

2026-05-04T02:30:26Z

Annakrat: Add template for accepted ideas

== About ==
Important: While we are still an OSGeo project, we changed our fiscal sponsor to [https://numfocus.org/ NumFOCUS].

''As a result, GRASS participates in GSoC under the [https://numfocus.org/ NumFOCUS] umbrella organization.''

Read more about our governance [https://grass.osgeo.org/about/governance/ on GRASS website].

* [https://numfocus.org/programs/google-summer-code The NumFOCUS GSoC main page]
* [https://github.com/numfocus/gsoc/blob/master/CONTRIBUTING-contributors.md NumFOCUS guidelines for contributors].
* [https://summerofcode.withgoogle.com/ Official GSoC page at Google]

== AI Tool Usage Policy ==
We acknowledge that applicants may use AI tools (like ChatGPT, Copilot, etc.) to assist with proposal writing and coding. However:

* Your proposal should reflect your own understanding and voice. AI-generated "slop" (overly generic or regurgitated content) is easy to spot and will hurt your application.
* We evaluate applications primarily on GitHub contributions and communication with the GRASS community, not just proposal polish.
* Show us you understand the project through high-quality pull requests on GitHub.
* Disclose AI usage: If you use AI tools in your proposal or code contributions, please disclose the extent to which you used them (e.g., for brainstorming, proofreading, code suggestions, etc.).

== Ideas ==
If you are a student you can suggest a new idea or pick up an existing one. In any case write about it to [https://discourse.osgeo.org/c/grass/developer/61 OSGeo Discourse forum for GRASS developers], [https://github.com/OSGeo/grass/discussions GitHub Discussions], or [https://gitter.im/grassgis/community Gitter].

You are invited as well to have a close look at ideas from previous years ([https://trac.osgeo.org/grass/wiki/GSoC/2014 2014], [https://trac.osgeo.org/grass/wiki/GSoC/2015 2015], [https://trac.osgeo.org/grass/wiki/GSoC/2016 2016],
[https://trac.osgeo.org/grass/wiki/GSoC/2017 2017],
[https://trac.osgeo.org/grass/wiki/GSoC/2018 2018],
[https://trac.osgeo.org/grass/wiki/GSoC/2019 2019],
[https://trac.osgeo.org/grass/wiki/GSoC/2020 2020],
[https://trac.osgeo.org/grass/wiki/GSoC/2021 2021],
[https://trac.osgeo.org/grass/wiki/GSoC/2022 2022],
[https://trac.osgeo.org/grass/wiki/GSoC/2023 2023])
which have not yet been implemented.
You can also look at accepted GRASS GSoC [https://trac.osgeo.org/grass/wiki/GSoC projects from previous years] for an idea of scope.''

=== Parallelization of existing tools ===

There are several tools that would benefit from parallelization with OpenMP, e.g. r.texture, r.fill.stats, r/v.surf.idw, r.viewshed, v.to.rast, r.grow.distance, v.surf.bspline, r.proj, ...
For overview of current state, see [[Raster_Parallelization_with_OpenMP]].

* Requirements: familiarity with C, OpenMP
* Mentor: Huidae Cho
* Co-mentor: Vaclav Petras, Anna Petrasova
* Project length: Large (350 hours)
* Rating: difficult
* Expected Outcomes: parallelized 2-5 tools, depending on complexity
* Test of skills (one or more):
** Address https://github.com/OSGeo/grass/issues/5776 (carefully read the existing conversation in the issue and linked PR)
** Pick a tool and develop prototype implementation of the parallelization.

=== Improve GRASS user experience in Jupyter Notebook ===
[[File:Jupyter_interactive_viewshed.png|500px|thumb|right|InteractiveMap in grass.jupyter library]]
Python package [https://grass.osgeo.org/grass-stable/manuals/libpython/grass.jupyter.html grass.jupyter] was developed during [https://trac.osgeo.org/grass/wiki/GSoC/2021/JupyterAndGRASS GSoC 2021] to simplify running GRASS from Jupyter Notebooks and displaying data. This project could focus on adding features such as better symbology handling and adding legend to InteractiveMap and better integration with matplotlib.

* Requirements: Python
* Mentor: Anna Petrasova
* Co-mentor: Vaclav Petras, Helena Mitasova, Corey White
* Project length: Large (350 hours)
* Rating: easy to medium
* Expected Outcomes: improved user experience when using GRASS through notebooks
* Test of skills: write a test for [https://github.com/OSGeo/grass/tree/main/python/grass/jupyter grass.jupyter library] using python unittest or pytest, more info [https://grass.osgeo.org/grass-devel/manuals/libpython/gunittest_testing.html here] or rewrite some of the functions in grass.jupyter library using the new [https://grass.osgeo.org/grass-devel/manuals/python_intro.html#running-tools Tools API].

=== Add JSON output to different tools ===
There are several tools in GRASS that would benefit from a JSON-formatted output.
Besides adding the JSON output, the work would also include adding tests and basic documentation.
* Requirements: C, Python
* Mentor: Vaclav Petras
* Co-mentor: Anna Petrasova, Corey White
* Project length: Large (350 hours)
* Rating: easy to medium
* Expected Outcomes: 10-20 tools (depending on project length and complexity of the tool) tools with well tested JSON output
* Note: A lot of work on JSON was already done, but there is more! Some of the remaining tools require more design. There are also Python tools (not just C which was the focus previously) and then also the grass-addons repo. Some tools also don't have any machine readable output right now and should. Also current tools which use other tools should use the new JSON as opposed to what they are using now. Preparing a well-reasoned list of tasks is a part of the application.
* Test of skills (pick one or more):
** https://github.com/OSGeo/grass/issues/6968
** https://github.com/OSGeo/grass/issues/6969
** https://github.com/OSGeo/grass/issues/6970

=== Support writing tests with pytest ===

* The current testing framework, ''[https://grass.osgeo.org/grass-stable/manuals/libpython/gunittest.html grass.gunittest]'', was written before migration to Git/GitHub and when long free runs in 3rd party services were unthinkable. Additionally, some no longer relevant goals were prioritized, such as independence on the current code, detailed custom HTML reports, success tracking over time, and high specialization towards GRASS-specifics.
* ''grass.gunittest'' is based on Python ''unittest'' package and many projects since then migrated to //pytest//, e.g., GDAL and Numpy. While ''unittest'' is inspired by Java's JUnit, ''pytest'' is designed to support writing small, readable tests, and uses plain `assert` statements instead of many different assert methods.
* Using ''pytest'' should lead to tests which feel more like Python scripts and to minimum of testing-specific code.
* An example issue of ''grass.gunittest'' is that it doesn't work well with tests of the main GRASS executable (prominence of `grass ... --exec` is yet another new thing which changed since ''grass.gunittest'' was designed).
* Two main things needed:
** Create general comparison functions from the ''grass.gunittest'' assert methods so that they can be used with pytest.
** Current grass.script.setup.init function and grass.script.core.create_location function don't work well in the context of a pytest test function. More
* Additional things needed:
** Fixture for pytest to set up and tear down a GRASS session in a temporary mapset.

* Requirements: Python
* Project length: Large (350 hours)
* Mentor: Vaclav Petras
* Co-mentor: Stefan Blumentrath
* Proposed by: Vaclav Petras
* Rating: easy to medium
* Expected Outcomes: Convenient way of writing tests with pytest
* Test of skills: Fix failing tests and/or write new tests (more is better). Alternatively, addressing a smaller problem in the testing framework is a good task, too.

=== Fix known code defects ===

* Fix code defects (security or code quality) such as those reported by Coverity Scan.
* Mentors: Vaclav Petras
* Co-mentors: Nicklas Larsson
* Proposed by: Vaclav Petras
* Project length: Large (350 hours)
* Rating: medium
* Requirements:
** Language: C
** Proposal: Define milestones which will be used during the evaluation.
* Expected outcomes:
** Reduction of issues by 70-100%.
** New tests for changed code if missing.
* Test and training tasks (complete more than one): Fix e.g., [https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html GCC Static Analysis], [https://clang.llvm.org/docs/ClangStaticAnalyzer.html Clang Static Analyzer] or [https://cppcheck.sourceforge.io Cppcheck] issues.

=== Subcommand CLI for GRASS ===

* Make running of GRASS tools in command line as easy as possible.
** `grass run r.slope.aspect elevation=elevation.tiff slope=slope.tiff aspect=aspect.tiff`
* Project length: Large (350 hours)
* Rating: medium
* Requirements:
** Language: Python
** Proposal: Student needs to show sufficient understanding of data and project handling in GRASS. Furthermore, the proposal needs to present, at least, concrete formulation of ideas, identification of missing and existing parts, and new subcommands.
* Mentors: Vaclav Petras
* Co-mentors: Stefan Blumentrath, Corey White
* Proposed by: Vaclav Petras
* Expected outcomes:
** A subcommand which runs a GRASS tool on GeoTiff and GeoPackage in one step.
** A complete parity with the existing CLI.
** An underlying Python API which will be used to implement the CLI.
* Test and training tasks (complete one or more): Add a subcommand, sub-subcommand, or an option to the experimental interface (with tests).
** Add `--region` to set a temporary computational region for the execution, e.g. `--region="raster=raster_name"`.
** Add `--import-raster=some/file.tiff` which imports (r.import) a raster file (same for vector and similarly for export).
** Add `--link-raster=some/file.tiff` which links (r.external) a raster file (same for vector and similarly for r.external.out).

Current state:

# Reveals the existing subcommands
PYTHONPATH=$(grass --config python-path) python -m grass.app --help
# Allows running subset of commands
grass run --help


=== GUI: Add space-time datasets support in Data Catalog ===
[[File:GUI_data_tab.png|400px|thumb|right|Data catalog]]
Currently GRASS Data Catalog shows only raster and vector maps. The goal of this project is to add support for space-time datasets. It is mainly space-time raster datasets. In the next phase of the project support for other types of space-time datasets (vector and 3D raster) could be added. Besides displaying space-time datasets in the layer tree, it is also about adding the equivalent functionality currently available for raster and vector layers from the context menu.

* Requirements: familiar with Python
* Project length: Large (350 hours)
* Mentor: Martin Landa
* Co-mentor: Anna Petrasova
* Proposed by: Martin Landa
* Rating: medium
* Expected Outcomes: 175 hours basic support for space-time raster datasets; 350 extended support also for other space-time datasets types (vector, 3D raster)
* Test of skills:
** suggest/implement solution for completing https://github.com/OSGeo/grass/issues/2599

=== Searchable metadata in Space Time Datasets ===
The temporal framework in GRASS was initially developed almost 15 years ago. Spatio-temporal data has become more widely available since then and new standards emerged like e.g. ''[https://docs.ogc.org/cs/25-004/25-004.html STAC]'' with ''[https://github.com/stac-extensions/stac-extensions.github.io extensions]'', or the ''[https://cfconventions.org/ CF-conventions]''. The aim of this project is to extend the metadata model in the temporal framework to improve discoverability of map datasets registered in TGIS and to allow users to embed extended metadata with the registered maps in a Space Time Dataset in a searchable way. Ideally, the new model is able to account for the standards mentioned above.

See also: https://github.com/OSGeo/grass/issues/1938

* Requirements: Python, SQL, JSON
* Project length: Large (350 hours)
* Mentor: Stefan Blumentrath
* Co-mentor: ???
* Proposed by: Stefan Blumentrath
* Rating: medium
* Expected Outcomes:
** an updated TGIS database model (version 4) that:
*** is oriented on relevant metadata standards (STAC, CF-Convention, ...)
*** allows to use metadata in temporal_where to select relevant elements of Space time datasets
** updated tool to create space time datasets (t.create) in the TGIS database with extended metadata
** updated tool to register map datasets (t.register) in the TGIS database with extended metadata
** Conversion tool for database Upgrades (v3 to v4)
** a new tool to update / modify metadata in the TGIS database
** Storage of timeseries metadata for both C-based and temporal Tools

* Test of skills (e.g.):
** address one or more sub-tasks from https://github.com/OSGeo/grass/issues/3427 (add append-mode to selected new tool(s))
** suggest/implement solution for https://github.com/OSGeo/grass/issues/3394 (more complex task)
** suggest/implement solution for https://github.com/OSGeo/grass/issues/7041

=== Add {your research idea} to GRASS ===

* In general, you can propose any topic, but you can specifically propose integrating your research or research idea into GRASS.
* Requirements:
** Language:
*** Depends on the project, often Python, sometimes C.
*** Adding your latest ecological analysis
** Proposal:
*** Discuss relevance to GRASS.
*** Describe technical steps needed for integration.
*** Describe whether it is an addition of a tool (module) or a change in one of the libraries. If it is a tool, specify if it should be included in the core grass repository or in grass-addons repository and why.
*** Specify what research was done and what needs to be accomplished in order to have usable product at the end of summer.
*** Specify who will provide the research expertise.
* Project length: Large (350 hours)
* Rating: from low to hard
* Mentors:
** GRASS project will provide technical mentors, but it is up to the applicant to ensure the research part is mentored well. An exception may be granted to applicants which can demonstrate that the research is finished or that they have enough expertise themselves.
** Possible technical mentors: Vaclav Petras, Anna Petrasova
** Research mentors: Bring in an expert from your field, e.g., your academic advisor or project principal investigator (if needed).
* Proposed by: Vaclav Petras
* Expected outcome: Working feature which is integrated and merged at the end of the project.
* Test and training tasks:
** Create a test in Python for an existing tool in the grass-addons repository or in the core grass repository.

=== Title of idea ===

Description here

* Requirements:
* Project length: (175 or 350 hours)
* Mentor:
* Proposed by:
* Rating:
* Expected Outcomes:
* Test of skills:
* Other:

== Tips for students ==
* Follow official [https://github.com/numfocus/gsoc/blob/master/CONTRIBUTING-contributors.md NumFOCUS guidelines].
* Include "GRASS" in the title of our idea to easily distinguish ideas and projects inside NumFOCUS.
* If you have your own ideas we encourage you to propose them. Explain them on the [https://discourse.osgeo.org/c/grass/developer/61 on our Discourse].
* Follow some good practices in your ideas and proposals:
** Stress why the project would be useful.
** Show that you know how you will proceed. That is, make sure that you can demonstrate that the proposal is feasible in the given time frame.
** Be specific in the implementation (or at least as specific as you can).
** Explain what the final product will look like and how it will work. You can add drawings or mock-ups.
** Explain how the idea relates to existing GRASS functions, features, and needs.
** Do not include steps such as "install GRASS", "compile GRASS libraries (on my machine)", "read about the API". You should do this before applying to GSoC.
* Compile GRASS from source and prepare environment for development:
** Read [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md CONTRIBUTING file].
* Prove your worth by being active on the [https://discourse.osgeo.org/c/grass/developer/61 GRASS Discourse] or other channels ([https://github.com/OSGeo/grass/discussions GitHub Discussions], fix some [https://github.com/OSGeo/grass/issues bugs], and/or implement some (smaller) features, or write some (simpler) GRASS module, and post it to mailing list. There's no better way to demonstrate your willingness and abilities. Do this before start you apply to GSoC.
* Also note that fixing existing bugs and/or implementing enhancements will be a part of student evaluation.

{{GSoC}}

GRASS GSoC Ideas 2026

2026-05-04T02:30:17Z

Annakrat: Add template for accepted ideas

== About ==
Important: While we are still an OSGeo project, we changed our fiscal sponsor to [https://numfocus.org/ NumFOCUS].

''As a result, GRASS participates in GSoC under the [https://numfocus.org/ NumFOCUS] umbrella organization.''

Read more about our governance [https://grass.osgeo.org/about/governance/ on GRASS website].

* [https://numfocus.org/programs/google-summer-code The NumFOCUS GSoC main page]
* [https://github.com/numfocus/gsoc/blob/master/CONTRIBUTING-contributors.md NumFOCUS guidelines for contributors].
* [https://summerofcode.withgoogle.com/ Official GSoC page at Google]

== Accepted ideas ==
=== Accepted idea title ===
* Student:
* Mentors:
* [[GRASS_GSoC_2025_Add_JSON_output_to_different_tools_in_C|Example of Wiki page]]

== AI Tool Usage Policy ==
We acknowledge that applicants may use AI tools (like ChatGPT, Copilot, etc.) to assist with proposal writing and coding. However:

* Your proposal should reflect your own understanding and voice. AI-generated "slop" (overly generic or regurgitated content) is easy to spot and will hurt your application.
* We evaluate applications primarily on GitHub contributions and communication with the GRASS community, not just proposal polish.
* Show us you understand the project through high-quality pull requests on GitHub.
* Disclose AI usage: If you use AI tools in your proposal or code contributions, please disclose the extent to which you used them (e.g., for brainstorming, proofreading, code suggestions, etc.).

== Ideas ==
If you are a student you can suggest a new idea or pick up an existing one. In any case write about it to [https://discourse.osgeo.org/c/grass/developer/61 OSGeo Discourse forum for GRASS developers], [https://github.com/OSGeo/grass/discussions GitHub Discussions], or [https://gitter.im/grassgis/community Gitter].

You are invited as well to have a close look at ideas from previous years ([https://trac.osgeo.org/grass/wiki/GSoC/2014 2014], [https://trac.osgeo.org/grass/wiki/GSoC/2015 2015], [https://trac.osgeo.org/grass/wiki/GSoC/2016 2016],
[https://trac.osgeo.org/grass/wiki/GSoC/2017 2017],
[https://trac.osgeo.org/grass/wiki/GSoC/2018 2018],
[https://trac.osgeo.org/grass/wiki/GSoC/2019 2019],
[https://trac.osgeo.org/grass/wiki/GSoC/2020 2020],
[https://trac.osgeo.org/grass/wiki/GSoC/2021 2021],
[https://trac.osgeo.org/grass/wiki/GSoC/2022 2022],
[https://trac.osgeo.org/grass/wiki/GSoC/2023 2023])
which have not yet been implemented.
You can also look at accepted GRASS GSoC [https://trac.osgeo.org/grass/wiki/GSoC projects from previous years] for an idea of scope.''

=== Parallelization of existing tools ===

There are several tools that would benefit from parallelization with OpenMP, e.g. r.texture, r.fill.stats, r/v.surf.idw, r.viewshed, v.to.rast, r.grow.distance, v.surf.bspline, r.proj, ...
For overview of current state, see [[Raster_Parallelization_with_OpenMP]].

* Requirements: familiarity with C, OpenMP
* Mentor: Huidae Cho
* Co-mentor: Vaclav Petras, Anna Petrasova
* Project length: Large (350 hours)
* Rating: difficult
* Expected Outcomes: parallelized 2-5 tools, depending on complexity
* Test of skills (one or more):
** Address https://github.com/OSGeo/grass/issues/5776 (carefully read the existing conversation in the issue and linked PR)
** Pick a tool and develop prototype implementation of the parallelization.

=== Improve GRASS user experience in Jupyter Notebook ===
[[File:Jupyter_interactive_viewshed.png|500px|thumb|right|InteractiveMap in grass.jupyter library]]
Python package [https://grass.osgeo.org/grass-stable/manuals/libpython/grass.jupyter.html grass.jupyter] was developed during [https://trac.osgeo.org/grass/wiki/GSoC/2021/JupyterAndGRASS GSoC 2021] to simplify running GRASS from Jupyter Notebooks and displaying data. This project could focus on adding features such as better symbology handling and adding legend to InteractiveMap and better integration with matplotlib.

* Requirements: Python
* Mentor: Anna Petrasova
* Co-mentor: Vaclav Petras, Helena Mitasova, Corey White
* Project length: Large (350 hours)
* Rating: easy to medium
* Expected Outcomes: improved user experience when using GRASS through notebooks
* Test of skills: write a test for [https://github.com/OSGeo/grass/tree/main/python/grass/jupyter grass.jupyter library] using python unittest or pytest, more info [https://grass.osgeo.org/grass-devel/manuals/libpython/gunittest_testing.html here] or rewrite some of the functions in grass.jupyter library using the new [https://grass.osgeo.org/grass-devel/manuals/python_intro.html#running-tools Tools API].

=== Add JSON output to different tools ===
There are several tools in GRASS that would benefit from a JSON-formatted output.
Besides adding the JSON output, the work would also include adding tests and basic documentation.
* Requirements: C, Python
* Mentor: Vaclav Petras
* Co-mentor: Anna Petrasova, Corey White
* Project length: Large (350 hours)
* Rating: easy to medium
* Expected Outcomes: 10-20 tools (depending on project length and complexity of the tool) tools with well tested JSON output
* Note: A lot of work on JSON was already done, but there is more! Some of the remaining tools require more design. There are also Python tools (not just C which was the focus previously) and then also the grass-addons repo. Some tools also don't have any machine readable output right now and should. Also current tools which use other tools should use the new JSON as opposed to what they are using now. Preparing a well-reasoned list of tasks is a part of the application.
* Test of skills (pick one or more):
** https://github.com/OSGeo/grass/issues/6968
** https://github.com/OSGeo/grass/issues/6969
** https://github.com/OSGeo/grass/issues/6970

=== Support writing tests with pytest ===

* The current testing framework, ''[https://grass.osgeo.org/grass-stable/manuals/libpython/gunittest.html grass.gunittest]'', was written before migration to Git/GitHub and when long free runs in 3rd party services were unthinkable. Additionally, some no longer relevant goals were prioritized, such as independence on the current code, detailed custom HTML reports, success tracking over time, and high specialization towards GRASS-specifics.
* ''grass.gunittest'' is based on Python ''unittest'' package and many projects since then migrated to //pytest//, e.g., GDAL and Numpy. While ''unittest'' is inspired by Java's JUnit, ''pytest'' is designed to support writing small, readable tests, and uses plain `assert` statements instead of many different assert methods.
* Using ''pytest'' should lead to tests which feel more like Python scripts and to minimum of testing-specific code.
* An example issue of ''grass.gunittest'' is that it doesn't work well with tests of the main GRASS executable (prominence of `grass ... --exec` is yet another new thing which changed since ''grass.gunittest'' was designed).
* Two main things needed:
** Create general comparison functions from the ''grass.gunittest'' assert methods so that they can be used with pytest.
** Current grass.script.setup.init function and grass.script.core.create_location function don't work well in the context of a pytest test function. More
* Additional things needed:
** Fixture for pytest to set up and tear down a GRASS session in a temporary mapset.

* Requirements: Python
* Project length: Large (350 hours)
* Mentor: Vaclav Petras
* Co-mentor: Stefan Blumentrath
* Proposed by: Vaclav Petras
* Rating: easy to medium
* Expected Outcomes: Convenient way of writing tests with pytest
* Test of skills: Fix failing tests and/or write new tests (more is better). Alternatively, addressing a smaller problem in the testing framework is a good task, too.

=== Fix known code defects ===

* Fix code defects (security or code quality) such as those reported by Coverity Scan.
* Mentors: Vaclav Petras
* Co-mentors: Nicklas Larsson
* Proposed by: Vaclav Petras
* Project length: Large (350 hours)
* Rating: medium
* Requirements:
** Language: C
** Proposal: Define milestones which will be used during the evaluation.
* Expected outcomes:
** Reduction of issues by 70-100%.
** New tests for changed code if missing.
* Test and training tasks (complete more than one): Fix e.g., [https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html GCC Static Analysis], [https://clang.llvm.org/docs/ClangStaticAnalyzer.html Clang Static Analyzer] or [https://cppcheck.sourceforge.io Cppcheck] issues.

=== Subcommand CLI for GRASS ===

* Make running of GRASS tools in command line as easy as possible.
** `grass run r.slope.aspect elevation=elevation.tiff slope=slope.tiff aspect=aspect.tiff`
* Project length: Large (350 hours)
* Rating: medium
* Requirements:
** Language: Python
** Proposal: Student needs to show sufficient understanding of data and project handling in GRASS. Furthermore, the proposal needs to present, at least, concrete formulation of ideas, identification of missing and existing parts, and new subcommands.
* Mentors: Vaclav Petras
* Co-mentors: Stefan Blumentrath, Corey White
* Proposed by: Vaclav Petras
* Expected outcomes:
** A subcommand which runs a GRASS tool on GeoTiff and GeoPackage in one step.
** A complete parity with the existing CLI.
** An underlying Python API which will be used to implement the CLI.
* Test and training tasks (complete one or more): Add a subcommand, sub-subcommand, or an option to the experimental interface (with tests).
** Add `--region` to set a temporary computational region for the execution, e.g. `--region="raster=raster_name"`.
** Add `--import-raster=some/file.tiff` which imports (r.import) a raster file (same for vector and similarly for export).
** Add `--link-raster=some/file.tiff` which links (r.external) a raster file (same for vector and similarly for r.external.out).

Current state:

# Reveals the existing subcommands
PYTHONPATH=$(grass --config python-path) python -m grass.app --help
# Allows running subset of commands
grass run --help


=== GUI: Add space-time datasets support in Data Catalog ===
[[File:GUI_data_tab.png|400px|thumb|right|Data catalog]]
Currently GRASS Data Catalog shows only raster and vector maps. The goal of this project is to add support for space-time datasets. It is mainly space-time raster datasets. In the next phase of the project support for other types of space-time datasets (vector and 3D raster) could be added. Besides displaying space-time datasets in the layer tree, it is also about adding the equivalent functionality currently available for raster and vector layers from the context menu.

* Requirements: familiar with Python
* Project length: Large (350 hours)
* Mentor: Martin Landa
* Co-mentor: Anna Petrasova
* Proposed by: Martin Landa
* Rating: medium
* Expected Outcomes: 175 hours basic support for space-time raster datasets; 350 extended support also for other space-time datasets types (vector, 3D raster)
* Test of skills:
** suggest/implement solution for completing https://github.com/OSGeo/grass/issues/2599

=== Searchable metadata in Space Time Datasets ===
The temporal framework in GRASS was initially developed almost 15 years ago. Spatio-temporal data has become more widely available since then and new standards emerged like e.g. ''[https://docs.ogc.org/cs/25-004/25-004.html STAC]'' with ''[https://github.com/stac-extensions/stac-extensions.github.io extensions]'', or the ''[https://cfconventions.org/ CF-conventions]''. The aim of this project is to extend the metadata model in the temporal framework to improve discoverability of map datasets registered in TGIS and to allow users to embed extended metadata with the registered maps in a Space Time Dataset in a searchable way. Ideally, the new model is able to account for the standards mentioned above.

See also: https://github.com/OSGeo/grass/issues/1938

* Requirements: Python, SQL, JSON
* Project length: Large (350 hours)
* Mentor: Stefan Blumentrath
* Co-mentor: ???
* Proposed by: Stefan Blumentrath
* Rating: medium
* Expected Outcomes:
** an updated TGIS database model (version 4) that:
*** is oriented on relevant metadata standards (STAC, CF-Convention, ...)
*** allows to use metadata in temporal_where to select relevant elements of Space time datasets
** updated tool to create space time datasets (t.create) in the TGIS database with extended metadata
** updated tool to register map datasets (t.register) in the TGIS database with extended metadata
** Conversion tool for database Upgrades (v3 to v4)
** a new tool to update / modify metadata in the TGIS database
** Storage of timeseries metadata for both C-based and temporal Tools

* Test of skills (e.g.):
** address one or more sub-tasks from https://github.com/OSGeo/grass/issues/3427 (add append-mode to selected new tool(s))
** suggest/implement solution for https://github.com/OSGeo/grass/issues/3394 (more complex task)
** suggest/implement solution for https://github.com/OSGeo/grass/issues/7041

=== Add {your research idea} to GRASS ===

* In general, you can propose any topic, but you can specifically propose integrating your research or research idea into GRASS.
* Requirements:
** Language:
*** Depends on the project, often Python, sometimes C.
*** Adding your latest ecological analysis
** Proposal:
*** Discuss relevance to GRASS.
*** Describe technical steps needed for integration.
*** Describe whether it is an addition of a tool (module) or a change in one of the libraries. If it is a tool, specify if it should be included in the core grass repository or in grass-addons repository and why.
*** Specify what research was done and what needs to be accomplished in order to have usable product at the end of summer.
*** Specify who will provide the research expertise.
* Project length: Large (350 hours)
* Rating: from low to hard
* Mentors:
** GRASS project will provide technical mentors, but it is up to the applicant to ensure the research part is mentored well. An exception may be granted to applicants which can demonstrate that the research is finished or that they have enough expertise themselves.
** Possible technical mentors: Vaclav Petras, Anna Petrasova
** Research mentors: Bring in an expert from your field, e.g., your academic advisor or project principal investigator (if needed).
* Proposed by: Vaclav Petras
* Expected outcome: Working feature which is integrated and merged at the end of the project.
* Test and training tasks:
** Create a test in Python for an existing tool in the grass-addons repository or in the core grass repository.

=== Title of idea ===

Description here

* Requirements:
* Project length: (175 or 350 hours)
* Mentor:
* Proposed by:
* Rating:
* Expected Outcomes:
* Test of skills:
* Other:

== Tips for students ==
* Follow official [https://github.com/numfocus/gsoc/blob/master/CONTRIBUTING-contributors.md NumFOCUS guidelines].
* Include "GRASS" in the title of our idea to easily distinguish ideas and projects inside NumFOCUS.
* If you have your own ideas we encourage you to propose them. Explain them on the [https://discourse.osgeo.org/c/grass/developer/61 on our Discourse].
* Follow some good practices in your ideas and proposals:
** Stress why the project would be useful.
** Show that you know how you will proceed. That is, make sure that you can demonstrate that the proposal is feasible in the given time frame.
** Be specific in the implementation (or at least as specific as you can).
** Explain what the final product will look like and how it will work. You can add drawings or mock-ups.
** Explain how the idea relates to existing GRASS functions, features, and needs.
** Do not include steps such as "install GRASS", "compile GRASS libraries (on my machine)", "read about the API". You should do this before applying to GSoC.
* Compile GRASS from source and prepare environment for development:
** Read [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md CONTRIBUTING file].
* Prove your worth by being active on the [https://discourse.osgeo.org/c/grass/developer/61 GRASS Discourse] or other channels ([https://github.com/OSGeo/grass/discussions GitHub Discussions], fix some [https://github.com/OSGeo/grass/issues bugs], and/or implement some (smaller) features, or write some (simpler) GRASS module, and post it to mailing list. There's no better way to demonstrate your willingness and abilities. Do this before start you apply to GSoC.
* Also note that fixing existing bugs and/or implementing enhancements will be a part of student evaluation.

{{GSoC}}

GRASS Community Meeting San Michele 2026

2026-04-15T18:29:41Z

Annakrat:

{{toc|right}}
The ''GRASS Community Meeting'' for contributors and developers will be happening from '''July 11 - 19, 2026''' in [https://www.openstreetmap.org/relation/46990#map=12/46.1349/11.1947 San Michele all'Adige, Trentino, Italy].

[[File:Sanmichele.png|frameless|center|1000px|San Michele all'Adige]]

== Sponsors ==

* [https://www.osgeo.org/ OSGeo]: 2500 USD (see [https://wiki.osgeo.org/w/index.php?title=GRASS_Community_Meeting_2026:_Budget budget]]).

[[File:Osgeo logo.png|none|left|alt=Light and dark green logo of OSGeo saying Your Open Source Compass|Open Source Geospatial Foundation]]

== Purpose ==
The ''GRASS Community Meeting'' is a great occasion for folks to support the development by actively contributing to the project in different ways. These include source code updates, documentation (manuals, wiki, tutorials), translations, website improvements 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 project and the interfaces to QGIS, GDAL, PostGIS, R, OGC Services and others.

The focus is on GRASS maintenance, and interaction with other projects. Many maintenance tasks, infrastructure changes, and planning of large changes especially benefits from maintainers being in one place and time zone. While the specific topics highly depend on the participants, we will prioritize topics which require highly synchronous collaboration, such as the CMake build system transition and API transitions. The [https://grass.osgeo.org/news/2025_05_27_grass_dev_summit_report/ 2025 event report] gives an overview of what was achieved last year.

We do require participants to work on GRASS or connections to other projects. However, we leave them the freedom to work on what they think is the best contribution to the project given their skills and time available.

== Agenda ==

Agenda is forthcoming.

=== Saturday, July 11 ===

Day of arrival. Contact organizers if you are interested in individualized program or helping with organization.

=== Sunday, July 12 ===
=== Monday, July 13 ===
=== Tuesday, July 14 ===
=== Wednesday, July 15 ===
=== Thursday, July 16 ===
=== Friday, July 17 ===
=== Saturday, July 18 ===
=== Sunday, July 19 ===

Day of departure.

== Participation ==

Please add your name here:

{|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:Lucadelu|Luca Delucchi]]
| Italy
|
|
|
|
|-
|2
| [[User:wenzeslaus|Vaclav Petras]]
| United States
|
|
|
|
|-
|3
| [[User:Annakrat|Anna Petrasova]]
| United States
|
|
|
|
|-
|4
| [[User:Neteler|Markus Neteler]]
| Germany
|
|
|
|
|-
|5
|
|
|
|
|
|
|-
|}

== Venue ==
The meeting will be hosted at [https://fmach.it/ Fondazione Edmund Mach] (FEM) in San Michele all'Adige, Trentino, Italy — about 15 km north of Trento. FEM is a research and education center with on-site facilities that allow participants to work, sleep, and eat in the same location.

[https://maps.app.goo.gl/5YEuEts6qXvky7HD9 Map]

=== Getting there ===

San Michele all'Adige is reachable by train on the Trento–Bolzano line (San Michele all'Adige–Mezzocorona station), with frequent connections from Trento (~15 minutes) and Verona (~1 hour). The nearest airports are Verona (VRN), Venice Marco Polo (VCE) and Treviso (TSF), Milan Bergamo (BGY), Malpensa (MXP), and Linate (LIN), Bologna (BLQ), and Innsbruck (INN) in Austria. Trento is also the host city of FOSS4G Italy 2026 (July 9–11), making it convenient to combine both events.

== Accommodation and Costs ==

''Participation is free of charge''. However, participants should plan for the following costs:

* Travel
* Lodging

Participants can stay on-site at the FEM convitto (dormitory), keeping the community together for the full duration of the meeting:

* €35 per person per night
* Double and triple rooms (triples include a small kitchen)
* A mandatory on-site supervisor is required at €200 per night (flat fee, shared across the group)
* Family members are welcome to stay in the dormitory as well
* [https://cif.fmach.it/content/download/2701/78358/file/brochure_convitto.pdf Brochure]

For anyone preferring alternative lodging, hotels and B&Bs are available in San Michele and nearby Trento.

Lunches on weekdays can be taken at the FEM canteen (mensa), located on the same campus. Details and pricing are being finalized.

== Individual Preparation ==

* Bring your own computer
* Bring {{wikipedia|AC power plugs and sockets|power adapter}} if needed (Italy: 230V, 50Hz, {{wikipedia|Europlug|Type C}}, {{wikipedia|Schuko|Type F}}, and {{wikipedia|AC power plugs and sockets: L|Type L}} sockets are common)
* Install git and the compiler tools, and come with a working GRASS development environment if possible. See [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md here] for details.

== FAQ ==

* ''How was it last time?''
** Splendid! See [[GRASS Developer Summit Raleigh 2025]]!
* ''Is the GRASS Community Meeting for developers only?''
** No, the meeting is open to all users, supporters, contributors, power users and developers ''who want to make a meaningful contribution to the project''.
* ''Where can I get help and more information about the community meeting?''
** Contact local organizer [[User:Lucadelu|Luca Delucchi]] (<tt><lucadeluge at gmail com></tt>) or [[User:wenzeslaus|Vaclav Petras]] (<tt><wenzeslaus at gmail com></tt>) for budget questions.

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2026]]

GRASS-Wiki

2026-04-15T03:40:27Z

Annakrat: /* Governance */

__NOTOC__

[[Image:grasslogo_vector_small.png|110x123 px|right|link=https://grass.osgeo.org]]

== Welcome to the GRASS Wiki ==

This wiki is used by the GRASS community mainly for '''governance''', '''event planning''', and '''community coordination'''.

Looking for how to use GRASS? Visit our main website and learning resources:

* [https://grass.osgeo.org/ Main GRASS Website]
* [https://grass.osgeo.org/grass-stable/manuals/index.html Documentation & Manuals]
* [https://grass-tutorials.osgeo.org/ Tutorials & Learning Resources]
* [https://grass.osgeo.org/download/ Download GRASS]
* [https://github.com/OSGeo/grass GitHub Repository]

'''Support GRASS development: [https://grass.osgeo.org/contribute/sponsoring/ Donate here]'''

== Governance ==

* [[PSC|Project Steering Committee (PSC)]]
* [[PSC#PSC_meeting_agenda_and_minutes|Meeting Minutes]]
* [[GRASS_Budget_2026|2026 Budget]]

== Latest Events & Planning ==

* [[GRASS Community Meeting San Michele 2026]]
* [[GRASS_GSoC_Ideas_2026|Google Summer of Code 2026]]
* [[Local GRASS Meetup at NC State Center for Geospatial Analytics 2025]]

== Relevant Categories ==
* [[:Category:GSoC|GSoC]]
* [[:Category:Code_Sprint|Code sprints]]
* [[:Category:Workshops|Workshops]]
* [[:Category:Conferences|Conferences]]
* [[:Category:Installation|Installation]]
* [[:Category:Budget|Budget]]
* [[Special:Categories|Further categories]]

GRASS-Wiki

2026-04-15T03:40:07Z

Annakrat: /* Governance */

__NOTOC__

[[Image:grasslogo_vector_small.png|110x123 px|right|link=https://grass.osgeo.org]]

== Welcome to the GRASS Wiki ==

This wiki is used by the GRASS community mainly for '''governance''', '''event planning''', and '''community coordination'''.

Looking for how to use GRASS? Visit our main website and learning resources:

* [https://grass.osgeo.org/ Main GRASS Website]
* [https://grass.osgeo.org/grass-stable/manuals/index.html Documentation & Manuals]
* [https://grass-tutorials.osgeo.org/ Tutorials & Learning Resources]
* [https://grass.osgeo.org/download/ Download GRASS]
* [https://github.com/OSGeo/grass GitHub Repository]

'''Support GRASS development: [https://grass.osgeo.org/contribute/sponsoring/ Donate here]'''

== Governance ==

* [[PSC|Project Steering Committee (PSC)]]
* [[PSC#PSC_meeting_agenda_and_minutes|Meeting Minutes]]
* [[GRASS_GIS_Budget_2026|2026 Budget]]

== Latest Events & Planning ==

* [[GRASS Community Meeting San Michele 2026]]
* [[GRASS_GSoC_Ideas_2026|Google Summer of Code 2026]]
* [[Local GRASS Meetup at NC State Center for Geospatial Analytics 2025]]

== Relevant Categories ==
* [[:Category:GSoC|GSoC]]
* [[:Category:Code_Sprint|Code sprints]]
* [[:Category:Workshops|Workshops]]
* [[:Category:Conferences|Conferences]]
* [[:Category:Installation|Installation]]
* [[:Category:Budget|Budget]]
* [[Special:Categories|Further categories]]

GRASS-Wiki

2026-04-15T03:38:50Z

Annakrat: /* Latest Events & Planning */

__NOTOC__

[[Image:grasslogo_vector_small.png|110x123 px|right|link=https://grass.osgeo.org]]

== Welcome to the GRASS Wiki ==

This wiki is used by the GRASS community mainly for '''governance''', '''event planning''', and '''community coordination'''.

Looking for how to use GRASS? Visit our main website and learning resources:

* [https://grass.osgeo.org/ Main GRASS Website]
* [https://grass.osgeo.org/grass-stable/manuals/index.html Documentation & Manuals]
* [https://grass-tutorials.osgeo.org/ Tutorials & Learning Resources]
* [https://grass.osgeo.org/download/ Download GRASS]
* [https://github.com/OSGeo/grass GitHub Repository]

'''Support GRASS development: [https://grass.osgeo.org/contribute/sponsoring/ Donate here]'''

== Governance ==

* [[PSC|Project Steering Committee (PSC)]]
* [[PSC#PSC_meeting_agenda_and_minutes|Meeting Minutes]]
* [[GRASS_GIS_Budget_2025|2025 Budget]]

== Latest Events & Planning ==

* [[GRASS Community Meeting San Michele 2026]]
* [[GRASS_GSoC_Ideas_2026|Google Summer of Code 2026]]
* [[Local GRASS Meetup at NC State Center for Geospatial Analytics 2025]]

== Relevant Categories ==
* [[:Category:GSoC|GSoC]]
* [[:Category:Code_Sprint|Code sprints]]
* [[:Category:Workshops|Workshops]]
* [[:Category:Conferences|Conferences]]
* [[:Category:Installation|Installation]]
* [[:Category:Budget|Budget]]
* [[Special:Categories|Further categories]]

GRASS Community Meeting San Michele 2026

2026-04-15T03:36:11Z

Annakrat: /* Participation */

{{toc|right}}
The ''GRASS Community Meeting'' for contributors and developers will be happening from '''July 11 to June 19, 2026''' in [https://www.openstreetmap.org/relation/46990#map=12/46.1349/11.1947 San Michele all'Adige, Trentino, Italy].

[[File:Sanmichele.png|frameless|center|1000px|San Michele all'Adige]]

== Sponsors ==

* [https://www.osgeo.org/ OSGeo]: 2500 USD (see [https://wiki.osgeo.org/w/index.php?title=GRASS_Community_Meeting_2026:_Budget budget]]).

[[File:Osgeo logo.png|none|left|alt=Light and dark green logo of OSGeo saying Your Open Source Compass|Open Source Geospatial Foundation]]

== Purpose ==
The ''GRASS Community Meeting'' is a great occasion for folks to support the development by actively contributing to the project in different ways. These include source code updates, documentation (manuals, wiki, tutorials), translations, website improvements 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 project and the interfaces to QGIS, GDAL, PostGIS, R, OGC Services and others.

The focus is on GRASS maintenance, and interaction with other projects. Many maintenance tasks, infrastructure changes, and planning of large changes especially benefits from maintainers being in one place and time zone. While the specific topics highly depend on the participants, we will prioritize topics which require highly synchronous collaboration, such as the CMake build system transition and API transitions. The [https://grass.osgeo.org/news/2025_05_27_grass_dev_summit_report/ 2025 event report] gives an overview of what was achieved last year.

We do require participants to work on GRASS or connections to other projects. However, we leave them the freedom to work on what they think is the best contribution to the project given their skills and time available.

== Agenda ==

Agenda is forthcoming.

=== Saturday, July 11 ===

Day of arrival. Contact organizers if you are interested in individualized program or helping with organization.

=== Sunday, July 12 ===
=== Monday, July 13 ===
=== Tuesday, July 14 ===
=== Wednesday, July 15 ===
=== Thursday, July 16 ===
=== Friday, July 17 ===
=== Saturday, July 18 ===
=== Sunday, July 19 ===

Day of departure.

== Participation ==

Please add your name here:

{|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:Lucadelu|Luca Delucchi]]
| Italy
|
|
|
|
|-
|2
| [[User:wenzeslaus|Vaclav Petras]]
| United States
|
|
|
|
|-
|3
| [[User:Annakrat|Anna Petrasova]]
| United States
|
|
|
|
|-
|4
|
|
|
|
|
|
|-
|}

== Venue ==
The meeting will be hosted at [https://fmach.it/ Fondazione Edmund Mach] (FEM) in San Michele all'Adige, Trentino, Italy — about 15 km north of Trento. FEM is a research and education center with on-site facilities that allow participants to work, sleep, and eat in the same location.

[https://maps.app.goo.gl/5YEuEts6qXvky7HD9 Map]

=== Getting there ===

San Michele all'Adige is reachable by train on the Trento–Bolzano line (San Michele all'Adige–Mezzocorona station), with frequent connections from Trento (~15 minutes) and Verona (~1 hour). The nearest airports are Verona (VRN), Venice Marco Polo (VCE) and Treviso (TSF), Milan Bergamo (BGY), Malpensa (MXP), and Linate (LIN), Bologna (BLQ), and Innsbruck (INN) in Austria. Trento is also the host city of FOSS4G Italy 2026 (July 9–11), making it convenient to combine both events.

== Accommodation and Costs ==

''Participation is free of charge''. However, participants should plan for the following costs:

* Travel
* Lodging

Participants can stay on-site at the FEM convitto (dormitory), keeping the community together for the full duration of the meeting:

* €35 per person per night
* Double and triple rooms (triples include a small kitchen)
* A mandatory on-site supervisor is required at €200 per night (flat fee, shared across the group)
* Family members are welcome to stay in the dormitory as well
* [https://cif.fmach.it/content/download/2701/78358/file/brochure_convitto.pdf Brochure]

For anyone preferring alternative lodging, hotels and B&Bs are available in San Michele and nearby Trento.

Lunches on weekdays can be taken at the FEM canteen (mensa), located on the same campus. Details and pricing are being finalized.

== Individual Preparation ==

* Bring your own computer
* Bring {{wikipedia|AC power plugs and sockets|power adapter}} if needed (Italy: 230V, 50Hz, {{wikipedia|Europlug|Type C}}, {{wikipedia|Schuko|Type F}}, and {{wikipedia|AC power plugs and sockets: L|Type L}} sockets are common)
* Install git and the compiler tools, and come with a working GRASS development environment if possible. See [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md here] for details.

== FAQ ==

* ''How was it last time?''
** Splendid! See [[GRASS Developer Summit Raleigh 2025]]!
* ''Is the GRASS Community Meeting for developers only?''
** No, the meeting is open to all users, supporters, contributors, power users and developers ''who want to make a meaningful contribution to the project''.
* ''Where can I get help and more information about the community meeting?''
** Contact local organizer [[User:Lucadelu|Luca Delucchi]] (<tt><lucadeluge at gmail com></tt>) or [[User:wenzeslaus|Vaclav Petras]] (<tt><wenzeslaus at gmail com></tt>) for budget questions.

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2026]]

GRASS Community Meeting San Michele 2026

2026-04-15T03:34:08Z

Annakrat: add image

{{toc|right}}
The ''GRASS Community Meeting'' for contributors and developers will be happening from '''July 11 to June 19, 2026''' in [https://www.openstreetmap.org/relation/46990#map=12/46.1349/11.1947 San Michele all'Adige, Trentino, Italy].

[[File:Sanmichele.png|frameless|center|1000px|San Michele all'Adige]]

== Sponsors ==

* [https://www.osgeo.org/ OSGeo]: 2500 USD (see [https://wiki.osgeo.org/w/index.php?title=GRASS_Community_Meeting_2026:_Budget budget]]).

[[File:Osgeo logo.png|none|left|alt=Light and dark green logo of OSGeo saying Your Open Source Compass|Open Source Geospatial Foundation]]

== Purpose ==
The ''GRASS Community Meeting'' is a great occasion for folks to support the development by actively contributing to the project in different ways. These include source code updates, documentation (manuals, wiki, tutorials), translations, website improvements 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 project and the interfaces to QGIS, GDAL, PostGIS, R, OGC Services and others.

The focus is on GRASS maintenance, and interaction with other projects. Many maintenance tasks, infrastructure changes, and planning of large changes especially benefits from maintainers being in one place and time zone. While the specific topics highly depend on the participants, we will prioritize topics which require highly synchronous collaboration, such as the CMake build system transition and API transitions. The [https://grass.osgeo.org/news/2025_05_27_grass_dev_summit_report/ 2025 event report] gives an overview of what was achieved last year.

We do require participants to work on GRASS or connections to other projects. However, we leave them the freedom to work on what they think is the best contribution to the project given their skills and time available.

== Agenda ==

Agenda is forthcoming.

=== Saturday, July 11 ===

Day of arrival. Contact organizers if you are interested in individualized program or helping with organization.

=== Sunday, July 12 ===
=== Monday, July 13 ===
=== Tuesday, July 14 ===
=== Wednesday, July 15 ===
=== Thursday, July 16 ===
=== Friday, July 17 ===
=== Saturday, July 18 ===
=== Sunday, July 19 ===

Day of departure.

== Participation ==

Please add your name here:

{|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:wenzeslaus|Vaclav Petras]]
| United States
|
|
|
|
|-
|2
| [[User:Annakrat|Anna Petrasova]]
| United States
|
|
|
|
|-
|3
|
|
|
|
|
|
|-
|}

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

== Venue ==
The meeting will be hosted at [https://fmach.it/ Fondazione Edmund Mach] (FEM) in San Michele all'Adige, Trentino, Italy — about 15 km north of Trento. FEM is a research and education center with on-site facilities that allow participants to work, sleep, and eat in the same location.

[https://maps.app.goo.gl/5YEuEts6qXvky7HD9 Map]

=== Getting there ===

San Michele all'Adige is reachable by train on the Trento–Bolzano line (San Michele all'Adige–Mezzocorona station), with frequent connections from Trento (~15 minutes) and Verona (~1 hour). The nearest airports are Verona (VRN), Venice Marco Polo (VCE) and Treviso (TSF), Milan Bergamo (BGY), Malpensa (MXP), and Linate (LIN), Bologna (BLQ), and Innsbruck (INN) in Austria. Trento is also the host city of FOSS4G Italy 2026 (July 9–11), making it convenient to combine both events.

== Accommodation and Costs ==

''Participation is free of charge''. However, participants should plan for the following costs:

* Travel
* Lodging

Participants can stay on-site at the FEM convitto (dormitory), keeping the community together for the full duration of the meeting:

* €35 per person per night
* Double and triple rooms (triples include a small kitchen)
* A mandatory on-site supervisor is required at €200 per night (flat fee, shared across the group)
* Family members are welcome to stay in the dormitory as well
* [https://cif.fmach.it/content/download/2701/78358/file/brochure_convitto.pdf Brochure]

For anyone preferring alternative lodging, hotels and B&Bs are available in San Michele and nearby Trento.

Lunches on weekdays can be taken at the FEM canteen (mensa), located on the same campus. Details and pricing are being finalized.

== Individual Preparation ==

* Bring your own computer
* Bring {{wikipedia|AC power plugs and sockets|power adapter}} if needed (Italy: 230V, 50Hz, {{wikipedia|Europlug|Type C}}, {{wikipedia|Schuko|Type F}}, and {{wikipedia|AC power plugs and sockets: L|Type L}} sockets are common)
* Install git and the compiler tools, and come with a working GRASS development environment if possible. See [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md here] for details.

== FAQ ==

* ''How was it last time?''
** Splendid! See [[GRASS Developer Summit Raleigh 2025]]!
* ''Is the GRASS Community Meeting for developers only?''
** No, the meeting is open to all users, supporters, contributors, power users and developers ''who want to make a meaningful contribution to the project''.
* ''Where can I get help and more information about the community meeting?''
** Contact local organizer [[User:Lucadelu|Luca Delucchi]] (<tt><lucadeluge at gmail com></tt>) or [[User:wenzeslaus|Vaclav Petras]] (<tt><wenzeslaus at gmail com></tt>) for budget questions.

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2026]]

File:Sanmichele.png

2026-04-15T03:28:00Z

Annakrat: Images capturing San Michele all'Adige for community meeting promo. Source is personal photos.

== Summary ==
Images capturing San Michele all'Adige for community meeting promo. Source is personal photos.

GRASS Community Meeting San Michele 2026

2026-04-15T02:59:24Z

Annakrat: wrong year

{{toc|right}}
The ''GRASS Community Meeting'' for contributors and developers will be happening from '''July 11 to June 19, 2026''' in [https://www.openstreetmap.org/relation/46990#map=12/46.1349/11.1947 San Michele all'Adige, Trentino, Italy].

== Sponsors ==

* [https://www.osgeo.org/ OSGeo]: 2500 USD (see [https://wiki.osgeo.org/w/index.php?title=GRASS_Community_Meeting_2026:_Budget budget]]).

[[File:Osgeo logo.png|none|left|alt=Light and dark green logo of OSGeo saying Your Open Source Compass|Open Source Geospatial Foundation]]

== Purpose ==
The ''GRASS Community Meeting'' is a great occasion for folks to support the development by actively contributing to the project in different ways. These include source code updates, documentation (manuals, wiki, tutorials), translations, website improvements 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 project and the interfaces to QGIS, GDAL, PostGIS, R, OGC Services and others.

The focus is on GRASS maintenance, and interaction with other projects. Many maintenance tasks, infrastructure changes, and planning of large changes especially benefits from maintainers being in one place and time zone. While the specific topics highly depend on the participants, we will prioritize topics which require highly synchronous collaboration, such as the CMake build system transition and API transitions. The [https://grass.osgeo.org/news/2025_05_27_grass_dev_summit_report/ 2025 event report] gives an overview of what was achieved last year.

We do require participants to work on GRASS or connections to other projects. However, we leave them the freedom to work on what they think is the best contribution to the project given their skills and time available.

== Agenda ==

Agenda is forthcoming.

=== Saturday, July 11 ===

Day of arrival. Contact organizers if you are interested in individualized program or helping with organization.

=== Sunday, July 12 ===
=== Monday, July 13 ===
=== Tuesday, July 14 ===
=== Wednesday, July 15 ===
=== Thursday, July 16 ===
=== Friday, July 17 ===
=== Saturday, July 18 ===
=== Sunday, July 19 ===

Day of departure.

== Participation ==

Please add your name here:

{|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:wenzeslaus|Vaclav Petras]]
| United States
|
|
|
|
|-
|2
| [[User:Annakrat|Anna Petrasova]]
| United States
|
|
|
|
|-
|3
|
|
|
|
|
|
|-
|}

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

== Venue ==
The meeting will be hosted at [https://fmach.it/ Fondazione Edmund Mach] (FEM) in San Michele all'Adige, Trentino, Italy — about 15 km north of Trento. FEM is a research and education center with on-site facilities that allow participants to work, sleep, and eat in the same location.

[https://maps.app.goo.gl/5YEuEts6qXvky7HD9 Map]

=== Getting there ===

San Michele all'Adige is reachable by train on the Trento–Bolzano line (San Michele all'Adige–Mezzocorona station), with frequent connections from Trento (~15 minutes) and Verona (~1 hour). The nearest airports are Verona (VRN), Venice Marco Polo (VCE) and Treviso (TSF), Milan Bergamo (BGY), Malpensa (MXP), and Linate (LIN), Bologna (BLQ), and Innsbruck (INN) in Austria. Trento is also the host city of FOSS4G Italy 2026 (July 9–11), making it convenient to combine both events.

== Accommodation and Costs ==

''Participation is free of charge''. However, participants should plan for the following costs:

* Travel
* Lodging

Participants can stay on-site at the FEM convitto (dormitory), keeping the community together for the full duration of the meeting:

* €35 per person per night
* Double and triple rooms (triples include a small kitchen)
* A mandatory on-site supervisor is required at €200 per night (flat fee, shared across the group)
* Family members are welcome to stay in the dormitory as well
* [https://cif.fmach.it/content/download/2701/78358/file/brochure_convitto.pdf Brochure]

For anyone preferring alternative lodging, hotels and B&Bs are available in San Michele and nearby Trento.

Lunches on weekdays can be taken at the FEM canteen (mensa), located on the same campus. Details and pricing are being finalized.

== Individual Preparation ==

* Bring your own computer
* Bring {{wikipedia|AC power plugs and sockets|power adapter}} if needed (Italy: 230V, 50Hz, {{wikipedia|Europlug|Type C}}, {{wikipedia|Schuko|Type F}}, and {{wikipedia|AC power plugs and sockets: L|Type L}} sockets are common)
* Install git and the compiler tools, and come with a working GRASS development environment if possible. See [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md here] for details.

== FAQ ==

* ''How was it last time?''
** Splendid! See [[GRASS Developer Summit Raleigh 2025]]!
* ''Is the GRASS Community Meeting for developers only?''
** No, the meeting is open to all users, supporters, contributors, power users and developers ''who want to make a meaningful contribution to the project''.
* ''Where can I get help and more information about the community meeting?''
** Contact local organizer [[User:Lucadelu|Luca Delucchi]] (<tt><lucadeluge at gmail com></tt>) or [[User:wenzeslaus|Vaclav Petras]] (<tt><wenzeslaus at gmail com></tt>) for budget questions.

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2026]]

GRASS Community Meeting San Michele 2026

2026-04-15T02:58:58Z

Annakrat: Initial page

{{toc|right}}
The ''GRASS Community Meeting'' for contributors and developers will be happening from '''July 11 to June 19, 2026''' in [https://www.openstreetmap.org/relation/46990#map=12/46.1349/11.1947 San Michele all'Adige, Trentino, Italy].

== Sponsors ==

* [https://www.osgeo.org/ OSGeo]: 2500 USD (see [https://wiki.osgeo.org/w/index.php?title=GRASS_Community_Meeting_2026:_Budget budget]]).

[[File:Osgeo logo.png|none|left|alt=Light and dark green logo of OSGeo saying Your Open Source Compass|Open Source Geospatial Foundation]]

== Purpose ==
The ''GRASS Community Meeting'' is a great occasion for folks to support the development by actively contributing to the project in different ways. These include source code updates, documentation (manuals, wiki, tutorials), translations, website improvements 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 project and the interfaces to QGIS, GDAL, PostGIS, R, OGC Services and others.

The focus is on GRASS maintenance, and interaction with other projects. Many maintenance tasks, infrastructure changes, and planning of large changes especially benefits from maintainers being in one place and time zone. While the specific topics highly depend on the participants, we will prioritize topics which require highly synchronous collaboration, such as the CMake build system transition and API transitions. The [https://grass.osgeo.org/news/2025_05_27_grass_dev_summit_report/ 2025 event report] gives an overview of what was achieved last year.

We do require participants to work on GRASS or connections to other projects. However, we leave them the freedom to work on what they think is the best contribution to the project given their skills and time available.

== Agenda ==

Agenda is forthcoming.

=== Saturday, July 11 ===

Day of arrival. Contact organizers if you are interested in individualized program or helping with organization.

=== Sunday, July 12 ===
=== Monday, July 13 ===
=== Tuesday, July 14 ===
=== Wednesday, July 15 ===
=== Thursday, July 16 ===
=== Friday, July 17 ===
=== Saturday, July 18 ===
=== Sunday, July 19 ===

Day of departure.

== Participation ==

Please add your name here:

{|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:wenzeslaus|Vaclav Petras]]
| United States
|
|
|
|
|-
|2
| [[User:Annakrat|Anna Petrasova]]
| United States
|
|
|
|
|-
|3
|
|
|
|
|
|
|-
|}

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

== Venue ==
The meeting will be hosted at [https://fmach.it/ Fondazione Edmund Mach] (FEM) in San Michele all'Adige, Trentino, Italy — about 15 km north of Trento. FEM is a research and education center with on-site facilities that allow participants to work, sleep, and eat in the same location.

[https://maps.app.goo.gl/5YEuEts6qXvky7HD9 Map]

=== Getting there ===

San Michele all'Adige is reachable by train on the Trento–Bolzano line (San Michele all'Adige–Mezzocorona station), with frequent connections from Trento (~15 minutes) and Verona (~1 hour). The nearest airports are Verona (VRN), Venice Marco Polo (VCE) and Treviso (TSF), Milan Bergamo (BGY), Malpensa (MXP), and Linate (LIN), Bologna (BLQ), and Innsbruck (INN) in Austria. Trento is also the host city of FOSS4G Italy 2026 (July 9–11), making it convenient to combine both events.

== Accommodation and Costs ==

''Participation is free of charge''. However, participants should plan for the following costs:

* Travel
* Lodging

Participants can stay on-site at the FEM convitto (dormitory), keeping the community together for the full duration of the meeting:

* €35 per person per night
* Double and triple rooms (triples include a small kitchen)
* A mandatory on-site supervisor is required at €200 per night (flat fee, shared across the group)
* Family members are welcome to stay in the dormitory as well
* [https://cif.fmach.it/content/download/2701/78358/file/brochure_convitto.pdf Brochure]

For anyone preferring alternative lodging, hotels and B&Bs are available in San Michele and nearby Trento.

Lunches on weekdays can be taken at the FEM canteen (mensa), located on the same campus. Details and pricing are being finalized.

== Individual Preparation ==

* Bring your own computer
* Bring {{wikipedia|AC power plugs and sockets|power adapter}} if needed (Italy: 230V, 50Hz, {{wikipedia|Europlug|Type C}}, {{wikipedia|Schuko|Type F}}, and {{wikipedia|AC power plugs and sockets: L|Type L}} sockets are common)
* Install git and the compiler tools, and come with a working GRASS development environment if possible. See [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md here] for details.

== FAQ ==

* ''How was it last time?''
** Splendid! See [[GRASS Developer Summit Raleigh 2025]]!
* ''Is the GRASS Community Meeting for developers only?''
** No, the meeting is open to all users, supporters, contributors, power users and developers ''who want to make a meaningful contribution to the project''.
* ''Where can I get help and more information about the community meeting?''
** Contact local organizer [[User:Lucadelu|Luca Delucchi]] (<tt><lucadeluge at gmail com></tt>) or [[User:wenzeslaus|Vaclav Petras]] (<tt><wenzeslaus at gmail com></tt>) for budget questions.

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2024]]

PSC Meeting 2026-02-13

2026-02-19T19:01:49Z

Annakrat: /* Minutes */ add link, remove one level of bullet points

== Participants ==

* Anna
* Vashek
* Nicklas
* Markus
* Paulo
* Linda
* Helli
* Huidae
* Vero
* Luca (guest)

== Agenda ==

The topics proposed are:

* Annual budget request submitted to OSGeo
* Community Meeting - San Michele: date, planning, budget requests
* Releases
* GSoC
* [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md#ai-use-policy AI policy]
* Plan PSC elections/role changes for later this year (some of us have been in PSC since Feb 2021)
* Budget
** Where are we at time?
** Fundraising efforts

== Minutes ==

1. Budget
* OSGeo:
** The annual budget request was submitted. See https://wiki.osgeo.org/wiki/GRASS_Budget_2026. OSGeo has allocated $1,600 of the $2,000 originally requested. Budget for swags should be requested from the Marketing Committee, which is why they cut 400 USD.
* Numfocus
** Their interface for money is not as transparent as OpenCollective; there’s no public view of the contributors or the money we have in their bucket
** We've been with them for a year now, and they are still not our fiscal hosts in Redbubble and OpenCollective. They are also going through a transition.

2. Community Meeting - San Michele
* OSGeo allocated 2500 USD, originally requested 5500 USD. See: https://wiki.osgeo.org/wiki/GRASS_Community_Meeting_2026:_Budget.
* By the beginning of March, Luca will meet FEM director, and we should then have an idea if we can stay at Convito in San Michele, so everything happens in San Michele, or if not, we search for university options in Trento, i.e., working rooms and housing.
* [Action] Create a wiki for the event.
* [Action] FOSSGIS e.V. request: will be handled by MN based on the one from [https://www.fossgis.de/wiki/Förderanträge/GRASS_GIS_Community_Meeting_2024 2024]

3. Annual report 2025
* Published as a [https://grass.osgeo.org/news/2025_12_31_annual_report/ news item] on the website
* It also served to meet the OSGeo requirement for budget request
* Nice new writing style with mentions to people actually doing things, as well as funding

4. Releases
* MN, NL, and Edouard had a branching session
* New 8.5 branch: https://github.com/OSGeo/grass/tree/releasebranch_8_5
* Waiting for Martin Landa to create the branch on Windows server
* Jupyter integration should be ready soon and will be backported to 8.5, to be part of the release.
* CMake is mostly functional, even for addons (those that were added), but documentation cannot yet be built with CMake.
* NL requested us to test CMake: https://grasswiki.osgeo.org/wiki/Compile_and_Install_With_CMake
* HC: Fixing issues in CMake for Windows.
* FHS is not ready yet; there's a big PR waiting for after the release.
* Conda: HC is working on a conda package for Windows.
* Documentation: Materials for Mkdocs style is retiring, we should transition to a supported theme. Just maybe not for the 8.5 release.

5. GSoC
* First year we participate under Numfocus if they are accepted
* We don’t know how many students we’ll get; it’s not clear how it works with Numfocus (is there a GSoC liaison/responsible person as in OSGeo?)

6. GRASS website
* There's a new version of packages and dependencies soon to be deployed
* Build to be moved to github-actions. Then the artifact has to be uploaded to OSGeo server (limitation: it needs a token that expires yearly).
* Corey to be added to the list of GRASS people with access to the OSGeo server
** [Action] VP will invite him, then create the SAC ticket needed
* conda missing from the download page, [https://github.com/OSGeo/grass-website/issues/601 issue] created
* download logos were broken for > half a year (?) and nobody realized this, [https://github.com/OSGeo/grass-website/issues/602 issue] created

7. AI policy
* Included in the main repo: https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md#ai-use-policy
* Simple - straightforward criteria that people might actually read, sort of guarantee/reference to close bad/meaningless PRs.
* Anna wrote it in response to the huge amount of PRs we are getting lately that are clearly created with AI, with no further understanding of GRASS.
* Many PRs are about tests, but they are not meaningful tests. It would be interesting to have instructions to create tests, so that contributors can train AI with instructions and create better tests.
** Corey is preparing instructions for Copilot, so it has context for code writing/reviewing.

8. PSC elections
* Some PSC members have been in PSC since Feb 2021, and as we decided back then, [https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20210203#Electiondebrief mandates should last max 6 years].
* [Action] Start planning by July, during the Community Meeting.

9. Mailman
* Move translation, grass-gui and grass-stats lists to read-only mode; make a last post saying we are closing it, and ask SAC to do so (keeping their archives).

[[Category:PSC]]

GRASS GSoC Ideas 2026

2026-02-03T18:15:31Z

Annakrat: /* Ideas */ make all project sizes large

== About ==
Important: While we are still an OSGeo project, we changed our fiscal sponsor to [https://numfocus.org/ NumFOCUS].

''As a result, GRASS participates in GSoC under the [https://numfocus.org/ NumFOCUS] umbrella organization.''

Read more about our governance [https://grass.osgeo.org/about/governance/ on GRASS website].

* [https://numfocus.org/programs/google-summer-code The NumFOCUS GSoC main page]
* [https://github.com/numfocus/gsoc/blob/master/CONTRIBUTING-contributors.md NumFOCUS guidelines for contributors].
* [https://summerofcode.withgoogle.com/ Official GSoC page at Google]

== AI Tool Usage Policy ==
We acknowledge that applicants may use AI tools (like ChatGPT, Copilot, etc.) to assist with proposal writing and coding. However:

* Your proposal should reflect your own understanding and voice. AI-generated "slop" (overly generic or regurgitated content) is easy to spot and will hurt your application.
* We evaluate applications primarily on GitHub contributions and communication with the GRASS community, not just proposal polish.
* Show us you understand the project through high-quality pull requests on GitHub.
* Disclose AI usage: If you use AI tools in your proposal or code contributions, please disclose the extent to which you used them (e.g., for brainstorming, proofreading, code suggestions, etc.).

== Ideas ==
If you are a student you can suggest a new idea or pick up an existing one. In any case write about it to [https://discourse.osgeo.org/c/grass/developer/61 OSGeo Discourse forum for GRASS developers], [https://github.com/OSGeo/grass/discussions GitHub Discussions], or [https://gitter.im/grassgis/community Gitter].

You are invited as well to have a close look at ideas from previous years ([https://trac.osgeo.org/grass/wiki/GSoC/2014 2014], [https://trac.osgeo.org/grass/wiki/GSoC/2015 2015], [https://trac.osgeo.org/grass/wiki/GSoC/2016 2016],
[https://trac.osgeo.org/grass/wiki/GSoC/2017 2017],
[https://trac.osgeo.org/grass/wiki/GSoC/2018 2018],
[https://trac.osgeo.org/grass/wiki/GSoC/2019 2019],
[https://trac.osgeo.org/grass/wiki/GSoC/2020 2020],
[https://trac.osgeo.org/grass/wiki/GSoC/2021 2021],
[https://trac.osgeo.org/grass/wiki/GSoC/2022 2022],
[https://trac.osgeo.org/grass/wiki/GSoC/2023 2023])
which have not yet been implemented.
You can also look at accepted GRASS GSoC [https://trac.osgeo.org/grass/wiki/GSoC projects from previous years] for an idea of scope.''

=== Parallelization of existing tools ===

There are several tools that would benefit from parallelization with OpenMP, e.g. r.texture, r.fill.stats, r/v.surf.idw, r.viewshed, v.to.rast, r.grow.distance, v.surf.bspline, r.proj, ...
For overview of current state, see [[Raster_Parallelization_with_OpenMP]].

* Requirements: familiarity with C, OpenMP
* Mentor: Huidae Cho
* Co-mentor: Vaclav Petras, Anna Petrasova
* Project length: Large (350 hours)
* Rating: difficult
* Expected Outcomes: parallelized 2-5 tools, depending on complexity
* Test of skills (one or more):
** Address https://github.com/OSGeo/grass/issues/5776 (carefully read the existing conversation in the issue and linked PR)
** Pick a tool and develop prototype implementation of the parallelization.

=== Improve GRASS user experience in Jupyter Notebook ===
[[File:Jupyter_interactive_viewshed.png|500px|thumb|right|InteractiveMap in grass.jupyter library]]
Python package [https://grass.osgeo.org/grass-stable/manuals/libpython/grass.jupyter.html grass.jupyter] was developed during [https://trac.osgeo.org/grass/wiki/GSoC/2021/JupyterAndGRASS GSoC 2021] to simplify running GRASS from Jupyter Notebooks and displaying data. This project could focus on adding features such as better symbology handling and adding legend to InteractiveMap and better integration with matplotlib.

* Requirements: Python
* Mentor: Anna Petrasova
* Co-mentor: Vaclav Petras, Helena Mitasova, Corey White
* Project length: Large (350 hours)
* Rating: easy to medium
* Expected Outcomes: improved user experience when using GRASS through notebooks
* Test of skills: write a test for [https://github.com/OSGeo/grass/tree/main/python/grass/jupyter grass.jupyter library] using python unittest or pytest, more info [https://grass.osgeo.org/grass-devel/manuals/libpython/gunittest_testing.html here] or rewrite some of the functions in grass.jupyter library using the new [https://grass.osgeo.org/grass-devel/manuals/python_intro.html#running-tools Tools API].

=== Add JSON output to different tools ===
There are several tools in GRASS that would benefit from a JSON-formatted output.
Besides adding the JSON output, the work would also include adding tests and basic documentation.
* Requirements: C, Python
* Mentor: Vaclav Petras
* Co-mentor: Anna Petrasova, Corey White
* Project length: Large (350 hours)
* Rating: easy to medium
* Expected Outcomes: 10-20 tools (depending on project length and complexity of the tool) tools with well tested JSON output
* Test of skills (pick one or more):
** https://github.com/OSGeo/grass/issues/6968
** https://github.com/OSGeo/grass/issues/6969
** https://github.com/OSGeo/grass/issues/6970

=== Support writing tests with pytest ===

* The current testing framework, ''[https://grass.osgeo.org/grass-stable/manuals/libpython/gunittest.html grass.gunittest]'', was written before migration to Git/GitHub and when long free runs in 3rd party services were unthinkable. Additionally, some no longer relevant goals were prioritized, such as independence on the current code, detailed custom HTML reports, success tracking over time, and high specialization towards GRASS-specifics.
* ''grass.gunittest'' is based on Python ''unittest'' package and many projects since then migrated to //pytest//, e.g., GDAL and Numpy. While ''unittest'' is inspired by Java's JUnit, ''pytest'' is designed to support writing small, readable tests, and uses plain `assert` statements instead of many different assert methods.
* Using ''pytest'' should lead to tests which feel more like Python scripts and to minimum of testing-specific code.
* An example issue of ''grass.gunittest'' is that it doesn't work well with tests of the main GRASS executable (prominence of `grass ... --exec` is yet another new thing which changed since ''grass.gunittest'' was designed).
* Two main things needed:
** Create general comparison functions from the ''grass.gunittest'' assert methods so that they can be used with pytest.
** Current grass.script.setup.init function and grass.script.core.create_location function don't work well in the context of a pytest test function. More
* Additional things needed:
** Fixture for pytest to set up and tear down a GRASS session in a temporary mapset.

* Requirements: Python
* Project length: Large (350 hours)
* Mentor: Vaclav Petras
* Co-mentor: Stefan Blumentrath
* Proposed by: Vaclav Petras
* Rating: easy to medium
* Expected Outcomes: Convenient way of writing tests with pytest
* Test of skills: Fix failing tests and/or write new tests (more is better). Alternatively, addressing a smaller problem in the testing framework is a good task, too.

=== Fix known code defects ===

* Fix code defects (security or code quality) such as those reported by Coverity Scan.
* Mentors: Vaclav Petras
* Co-mentors: ?
* Proposed by: Vaclav Petras
* Project length: Large (350 hours)
* Rating: medium
* Requirements:
** Language: C
** Proposal: Define milestones which will be used during the evaluation.
* Expected outcomes:
** Reduction of issues by 70-100%.
** New tests for changed code if missing.
* Test and training tasks (complete more than one): Fix cppcheck issue.

=== Subcommand CLI for GRASS ===

* Make running of GRASS tools in command line as easy as possible.
** `grass run r.slope.aspect elevation=elevation.tiff slope=slope.tiff aspect=aspect.tiff`
* Project length: Large (350 hours)
* Rating: medium
* Requirements:
** Language: Python
** Proposal: Student needs to show sufficient understanding of data and project handling in GRASS. Furthermore, the proposal needs to present, at least, concrete formulation of ideas, identification of missing and existing parts, and new subcommands.
* Mentors: Vaclav Petras
* Co-mentors: Stefan Blumentrath, Corey White
* Proposed by: Vaclav Petras
* Expected outcomes:
** A subcommand which runs a GRASS tool on GeoTiff and GeoPackage in one step.
** A complete parity with the existing CLI.
** An underlying Python API which will be used to implement the CLI.
* Test and training tasks (complete one or more): Add a subcommand, sub-subcommand, or an option to the experimental interface (with tests).
** Add `--region` to set a temporary computational region for the execution, e.g. `--region="raster=raster_name"`.
** Add `--import-raster=some/file.tiff` which imports (r.import) a raster file (same for vector and similarly for export).
** Add `--link-raster=some/file.tiff` which links (r.external) a raster file (same for vector and similarly for r.external.out).

Current state:

# Reveals the existing subcommands
PYTHONPATH=$(grass --config python-path) python -m grass.app --help
# Allows running subset of commands
grass run --help



=== GUI: Add space-time datasets support in Data Catalog ===
[[File:GUI_data_tab.png|400px|thumb|right|Data catalog]]
Currently GRASS Data Catalog shows only raster and vector maps. The goal of this project is to add support for space-time datasets. It is mainly space-time raster datasets. In the next phase of the project support for other types of space-time datasets (vector and 3D raster) could be added. Besides displaying space-time datasets in the layer tree, it is also about adding the equivalent functionality currently available for raster and vector layers from the context menu.

* Requirements: familiar with Python
* Project length: Large (350 hours)
* Mentor: Martin Landa
* Co-mentor: Anna Petrasova
* Proposed by: Martin Landa
* Rating: medium
* Expected Outcomes: 175 hours basic support for space-time raster datasets; 350 extended support also for other space-time datasets types (vector, 3D raster)
* Test of skills:
** suggest/implement solution for completing https://github.com/OSGeo/grass/issues/2599

=== Add {your research idea} to GRASS ===

* In general, you can propose any topic, but you can specifically propose integrating your research or research idea into GRASS.
* Requirements:
** Language:
*** Depends on the project, often Python, sometimes C.
*** Adding your latest ecological analysis
** Proposal:
*** Discuss relevance to GRASS.
*** Describe technical steps needed for integration.
*** Describe whether it is an addition of a tool (module) or a change in one of the libraries. If it is a tool, specify if it should be included in the core grass repository or in grass-addons repository and why.
*** Specify what research was done and what needs to be accomplished in order to have usable product at the end of summer.
*** Specify who will provide the research expertise.
* Project length: Large (350 hours)
* Rating: from low to hard
* Mentors:
** GRASS project will provide technical mentors, but it is up to the applicant to ensure the research part is mentored well. An exception may be granted to applicants which can demonstrate that the research is finished or that they have enough expertise themselves.
** Possible technical mentors: Vaclav Petras, Anna Petrasova
** Research mentors: Bring in an expert from your field, e.g., your academic advisor or project principal investigator (if needed).
* Proposed by: Vaclav Petras
* Expected outcome: Working feature which is integrated and merged at the end of the project.
* Test and training tasks:
** Create a test in Python for an existing tool in the grass-addons repository or in the core grass repository.

=== Title of idea ===

Description here

* Requirements:
* Project length: (175 or 350 hours)
* Mentor:
* Proposed by:
* Rating:
* Expected Outcomes:
* Test of skills:
* Other:

== Tips for students ==
* Follow official [https://github.com/numfocus/gsoc/blob/master/CONTRIBUTING-contributors.md NumFOCUS guidelines].
* Include "GRASS" in the title of our idea to easily distinguish ideas and projects inside NumFOCUS.
* If you have your own ideas we encourage you to propose them. Explain them on the [https://discourse.osgeo.org/c/grass/developer/61 on our Discourse].
* Follow some good practices in your ideas and proposals:
** Stress why the project would be useful.
** Show that you know how you will proceed. That is, make sure that you can demonstrate that the proposal is feasible in the given time frame.
** Be specific in the implementation (or at least as specific as you can).
** Explain what the final product will look like and how it will work. You can add drawings or mock-ups.
** Explain how the idea relates to existing GRASS functions, features, and needs.
** Do not include steps such as "install GRASS", "compile GRASS libraries (on my machine)", "read about the API". You should do this before applying to GSoC.
* Compile GRASS from source and prepare environment for development:
** Read [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md CONTRIBUTING file].
* Prove your worth by being active on the [https://discourse.osgeo.org/c/grass/developer/61 GRASS Discourse] or other channels ([https://github.com/OSGeo/grass/discussions GitHub Discussions], fix some [https://github.com/OSGeo/grass/issues bugs], and/or implement some (smaller) features, or write some (simpler) GRASS module, and post it to mailing list. There's no better way to demonstrate your willingness and abilities. Do this before start you apply to GSoC.
* Also note that fixing existing bugs and/or implementing enhancements will be a part of student evaluation.

{{GSoC}}

GRASS GSoC Ideas 2026

2026-01-29T17:58:06Z

Annakrat: /* Improve GRASS user experience in Jupyter Notebook */

== About ==
Important: While we are still an OSGeo project, we changed our fiscal sponsor to [https://numfocus.org/ NumFOCUS].

''As a result, GRASS participates in GSoC under the [https://numfocus.org/ NumFOCUS] umbrella organization.''

Read more about our governance [https://grass.osgeo.org/about/governance/ on GRASS website].

* [https://numfocus.org/programs/google-summer-code The NumFOCUS GSoC main page]
* [https://github.com/numfocus/gsoc/blob/master/CONTRIBUTING-contributors.md NumFOCUS guidelines for contributors].
* [https://summerofcode.withgoogle.com/ Official GSoC page at Google]

== AI Tool Usage Policy ==
We acknowledge that applicants may use AI tools (like ChatGPT, Copilot, etc.) to assist with proposal writing and coding. However:

* Your proposal should reflect your own understanding and voice. AI-generated "slop" (overly generic or regurgitated content) is easy to spot and will hurt your application.
* We evaluate applications primarily on GitHub contributions and communication with the GRASS community, not just proposal polish.
* Show us you understand the project through high-quality pull requests on GitHub.
* Disclose AI usage: If you use AI tools in your proposal or code contributions, please disclose the extent to which you used them (e.g., for brainstorming, proofreading, code suggestions, etc.).

== Ideas ==
If you are a student you can suggest a new idea or pick up an existing one. In any case write about it to [https://discourse.osgeo.org/c/grass/developer/61 OSGeo Discourse forum for GRASS developers], [https://github.com/OSGeo/grass/discussions GitHub Discussions], or [https://gitter.im/grassgis/community Gitter].

You are invited as well to have a close look at ideas from previous years ([https://trac.osgeo.org/grass/wiki/GSoC/2014 2014], [https://trac.osgeo.org/grass/wiki/GSoC/2015 2015], [https://trac.osgeo.org/grass/wiki/GSoC/2016 2016],
[https://trac.osgeo.org/grass/wiki/GSoC/2017 2017],
[https://trac.osgeo.org/grass/wiki/GSoC/2018 2018],
[https://trac.osgeo.org/grass/wiki/GSoC/2019 2019],
[https://trac.osgeo.org/grass/wiki/GSoC/2020 2020],
[https://trac.osgeo.org/grass/wiki/GSoC/2021 2021],
[https://trac.osgeo.org/grass/wiki/GSoC/2022 2022],
[https://trac.osgeo.org/grass/wiki/GSoC/2023 2023])
which have not yet been implemented.
You can also look at accepted GRASS GSoC [https://trac.osgeo.org/grass/wiki/GSoC projects from previous years] for an idea of scope.''

=== Parallelization of existing tools ===

There are several tools that would benefit from parallelization with OpenMP, e.g. r.texture, r.fill.stats, r/v.surf.idw, r.viewshed, v.to.rast, r.grow.distance, v.surf.bspline, r.proj, ...
For overview of current state, see [[Raster_Parallelization_with_OpenMP]].

* Requirements: familiarity with C, OpenMP
* Mentor: Huidae Cho
* Co-mentor: Vaclav Petras, Anna Petrasova
* Project length: 175 or 350 hours (take your pick)
* Rating: difficult
* Expected Outcomes: parallelized 2-5 tools, depending on complexity
* Test of skills (one or more):
** Address https://github.com/OSGeo/grass/issues/5776 (carefully read the existing conversation in the issue and linked PR)
** Pick a tool and develop prototype implementation of the parallelization.

=== Improve GRASS user experience in Jupyter Notebook ===
[[File:Jupyter_interactive_viewshed.png|500px|thumb|right|InteractiveMap in grass.jupyter library]]
Python package [https://grass.osgeo.org/grass-stable/manuals/libpython/grass.jupyter.html grass.jupyter] was developed during [https://trac.osgeo.org/grass/wiki/GSoC/2021/JupyterAndGRASS GSoC 2021] to simplify running GRASS from Jupyter Notebooks and displaying data. This project could focus on adding features such as better symbology handling and adding legend to InteractiveMap and better integration with matplotlib.

* Requirements: Python
* Mentor: Anna Petrasova
* Co-mentor: Vaclav Petras, Helena Mitasova, Corey White
* Project length: 175 or 350 hours (take your pick)
* Rating: easy to medium
* Expected Outcomes: improved user experience when using GRASS through notebooks
* Test of skills: write a test for [https://github.com/OSGeo/grass/tree/main/python/grass/jupyter grass.jupyter library] using python unittest or pytest, more info [https://grass.osgeo.org/grass-devel/manuals/libpython/gunittest_testing.html here] or rewrite some of the functions in grass.jupyter library using the new [https://grass.osgeo.org/grass-devel/manuals/python_intro.html#running-tools Tools API].

=== Add JSON output to different tools ===
There are several tools in GRASS that would benefit from a JSON-formatted output.
Besides adding the JSON output, the work would also include adding tests and basic documentation.
* Requirements: C, Python
* Mentor: Vaclav Petras
* Co-mentor: Anna Petrasova, Corey White
* Project length: 175 or 350 hours (take your pick)
* Rating: easy to medium
* Expected Outcomes: 10-20 tools (depending on project length and complexity of the tool) tools with well tested JSON output
* Test of skills (pick one or more):
** https://github.com/OSGeo/grass/issues/6968
** https://github.com/OSGeo/grass/issues/6969
** https://github.com/OSGeo/grass/issues/6970

=== Support writing tests with pytest ===

* The current testing framework, ''[https://grass.osgeo.org/grass-stable/manuals/libpython/gunittest.html grass.gunittest]'', was written before migration to Git/GitHub and when long free runs in 3rd party services were unthinkable. Additionally, some no longer relevant goals were prioritized, such as independence on the current code, detailed custom HTML reports, success tracking over time, and high specialization towards GRASS-specifics.
* ''grass.gunittest'' is based on Python ''unittest'' package and many projects since then migrated to //pytest//, e.g., GDAL and Numpy. While ''unittest'' is inspired by Java's JUnit, ''pytest'' is designed to support writing small, readable tests, and uses plain `assert` statements instead of many different assert methods.
* Using ''pytest'' should lead to tests which feel more like Python scripts and to minimum of testing-specific code.
* An example issue of ''grass.gunittest'' is that it doesn't work well with tests of the main GRASS executable (prominence of `grass ... --exec` is yet another new thing which changed since ''grass.gunittest'' was designed).
* Two main things needed:
** Create general comparison functions from the ''grass.gunittest'' assert methods so that they can be used with pytest.
** Current grass.script.setup.init function and grass.script.core.create_location function don't work well in the context of a pytest test function. More
* Additional things needed:
** Fixture for pytest to set up and tear down a GRASS session in a temporary mapset.

* Requirements: Python
* Project length: 175 or 350 hours (take your pick)
* Mentor: Vaclav Petras
* Co-mentor: Stefan Blumentrath
* Proposed by: Vaclav Petras
* Rating: easy to medium
* Expected Outcomes: Convenient way of writing tests with pytest
* Test of skills: Fix failing tests and/or write new tests (more is better). Alternatively, addressing a smaller problem in the testing framework is a good task, too.

=== Fix known code defects ===

* Fix code defects (security or code quality) such as those reported by Coverity Scan.
* Mentors: Vaclav Petras
* Co-mentors: ?
* Proposed by: Vaclav Petras
* Project length: 175 or 350 hours (flexible)
* Rating: medium
* Requirements:
** Language: C
** Proposal: Define milestones which will be used during the evaluation.
* Expected outcomes:
** Reduction of issues by 70-100%.
** New tests for changed code if missing.
* Test and training tasks (complete more than one): Fix cppcheck issue.

=== Subcommand CLI for GRASS ===

* Make running of GRASS tools in command line as easy as possible.
** `grass run r.slope.aspect elevation=elevation.tiff slope=slope.tiff aspect=aspect.tiff`
* Project length: 350 hours
* Rating: medium
* Requirements:
** Language: Python
** Proposal: Student needs to show sufficient understanding of data and project handling in GRASS. Furthermore, the proposal needs to present, at least, concrete formulation of ideas, identification of missing and existing parts, and new subcommands.
* Mentors: Vaclav Petras
* Co-mentors: Stefan Blumentrath, Corey White
* Proposed by: Vaclav Petras
* Expected outcomes:
** A subcommand which runs a GRASS tool on GeoTiff and GeoPackage in one step.
** A complete parity with the existing CLI.
** An underlying Python API which will be used to implement the CLI.
* Test and training tasks (complete one or more): Add a subcommand, sub-subcommand, or an option to the experimental interface (with tests).
** Add `--region` to set a temporary computational region for the execution, e.g. `--region="raster=raster_name"`.
** Add `--import-raster=some/file.tiff` which imports (r.import) a raster file (same for vector and similarly for export).
** Add `--link-raster=some/file.tiff` which links (r.external) a raster file (same for vector and similarly for r.external.out).

Current state:

# Reveals the existing subcommands
PYTHONPATH=$(grass --config python-path) python -m grass.app --help
# Allows running subset of commands
grass run --help



=== GUI: Add space-time datasets support in Data Catalog ===
[[File:GUI_data_tab.png|400px|thumb|right|Data catalog]]
Currently GRASS Data Catalog shows only raster and vector maps. The goal of this project is to add support for space-time datasets. It is mainly space-time raster datasets. In the next phase of the project support for other types of space-time datasets (vector and 3D raster) could be added. Besides displaying space-time datasets in the layer tree, it is also about adding the equivalent functionality currently available for raster and vector layers from the context menu.

* Requirements: familiar with Python
* Project length: 175 or 350 hours
* Mentor: Martin Landa
* Co-mentor: Anna Petrasova
* Proposed by: Martin Landa
* Rating: medium
* Expected Outcomes: 175 hours basic support for space-time raster datasets; 350 extended support also for other space-time datasets types (vector, 3D raster)
* Test of skills:
** suggest/implement solution for completing https://github.com/OSGeo/grass/issues/2599

=== Add {your research idea} to GRASS ===

* In general, you can propose any topic, but you can specifically propose integrating your research or research idea into GRASS.
* Requirements:
** Language:
*** Depends on the project, often Python, sometimes C.
*** Adding your latest ecological analysis
** Proposal:
*** Discuss relevance to GRASS.
*** Describe technical steps needed for integration.
*** Describe whether it is an addition of a tool (module) or a change in one of the libraries. If it is a tool, specify if it should be included in the core grass repository or in grass-addons repository and why.
*** Specify what research was done and what needs to be accomplished in order to have usable product at the end of summer.
*** Specify who will provide the research expertise.
* Project length: 175 or 350 hours (take your pick)
* Rating: from low to hard
* Mentors:
** GRASS project will provide technical mentors, but it is up to the applicant to ensure the research part is mentored well. An exception may be granted to applicants which can demonstrate that the research is finished or that they have enough expertise themselves.
** Possible technical mentors: Vaclav Petras, Anna Petrasova
** Research mentors: Bring in an expert from your field, e.g., your academic advisor or project principal investigator (if needed).
* Proposed by: Vaclav Petras
* Expected outcome: Working feature which is integrated and merged at the end of the project.
* Test and training tasks:
** Create a test in Python for an existing tool in the grass-addons repository or in the core grass repository.

=== Title of idea ===

Description here

* Requirements:
* Project length: (175 or 350 hours)
* Mentor:
* Proposed by:
* Rating:
* Expected Outcomes:
* Test of skills:
* Other:

== Tips for students ==
* Follow official [https://github.com/numfocus/gsoc/blob/master/CONTRIBUTING-contributors.md NumFOCUS guidelines].
* Include "GRASS" in the title of our idea to easily distinguish ideas and projects inside NumFOCUS.
* If you have your own ideas we encourage you to propose them. Explain them on the [https://discourse.osgeo.org/c/grass/developer/61 on our Discourse].
* Follow some good practices in your ideas and proposals:
** Stress why the project would be useful.
** Show that you know how you will proceed. That is, make sure that you can demonstrate that the proposal is feasible in the given time frame.
** Be specific in the implementation (or at least as specific as you can).
** Explain what the final product will look like and how it will work. You can add drawings or mock-ups.
** Explain how the idea relates to existing GRASS functions, features, and needs.
** Do not include steps such as "install GRASS", "compile GRASS libraries (on my machine)", "read about the API". You should do this before applying to GSoC.
* Compile GRASS from source and prepare environment for development:
** Read [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md CONTRIBUTING file].
* Prove your worth by being active on the [https://discourse.osgeo.org/c/grass/developer/61 GRASS Discourse] or other channels ([https://github.com/OSGeo/grass/discussions GitHub Discussions], fix some [https://github.com/OSGeo/grass/issues bugs], and/or implement some (smaller) features, or write some (simpler) GRASS module, and post it to mailing list. There's no better way to demonstrate your willingness and abilities. Do this before start you apply to GSoC.
* Also note that fixing existing bugs and/or implementing enhancements will be a part of student evaluation.

{{GSoC}}

GRASS GSoC Ideas 2026

2026-01-26T04:26:15Z

Annakrat: /* Improve GRASS user experience in Jupyter Notebook */

== About ==
Important: While we are still an OSGeo project, we changed our fiscal sponsor to [https://numfocus.org/ NumFOCUS].

''As a result, GRASS participates in GSoC under the [https://numfocus.org/ NumFOCUS] umbrella organization.''

Read more about our governance [https://grass.osgeo.org/about/governance/ on GRASS website].

* [https://numfocus.org/programs/google-summer-code The NumFOCUS GSoC main page]
* [https://github.com/numfocus/gsoc/blob/master/CONTRIBUTING-contributors.md NumFOCUS guidelines for contributors].
* [https://summerofcode.withgoogle.com/ Official GSoC page at Google]

== AI Tool Usage Policy ==
We acknowledge that applicants may use AI tools (like ChatGPT, Copilot, etc.) to assist with proposal writing and coding. However:

* Your proposal should reflect your own understanding and voice. AI-generated "slop" (overly generic or regurgitated content) is easy to spot and will hurt your application.
* We evaluate applications primarily on GitHub contributions and communication with the GRASS community, not just proposal polish.
* Show us you understand the project through high-quality pull requests on GitHub.
* Disclose AI usage: If you use AI tools in your proposal or code contributions, please disclose the extent to which you used them (e.g., for brainstorming, proofreading, code suggestions, etc.).

== Ideas ==
If you are a student you can suggest a new idea or pick up an existing one. In any case write about it to [https://discourse.osgeo.org/c/grass/developer/61 OSGeo Discourse forum for GRASS developers], [https://github.com/OSGeo/grass/discussions GitHub Discussions], or [https://gitter.im/grassgis/community Gitter].

You are invited as well to have a close look at ideas from previous years ([https://trac.osgeo.org/grass/wiki/GSoC/2014 2014], [https://trac.osgeo.org/grass/wiki/GSoC/2015 2015], [https://trac.osgeo.org/grass/wiki/GSoC/2016 2016],
[https://trac.osgeo.org/grass/wiki/GSoC/2017 2017],
[https://trac.osgeo.org/grass/wiki/GSoC/2018 2018],
[https://trac.osgeo.org/grass/wiki/GSoC/2019 2019],
[https://trac.osgeo.org/grass/wiki/GSoC/2020 2020],
[https://trac.osgeo.org/grass/wiki/GSoC/2021 2021],
[https://trac.osgeo.org/grass/wiki/GSoC/2022 2022],
[https://trac.osgeo.org/grass/wiki/GSoC/2023 2023])
which have not yet been implemented.
You can also look at accepted GRASS GSoC [https://trac.osgeo.org/grass/wiki/GSoC projects from previous years] for an idea of scope.''

=== Parallelization of existing tools ===

There are several tools that would benefit from parallelization with OpenMP, e.g. r.texture, r.fill.stats, r/v.surf.idw, r.viewshed, v.to.rast, r.grow.distance, v.surf.bspline, r.proj, ...
For overview of current state, see [[Raster_Parallelization_with_OpenMP]].

* Requirements: familiarity with C, OpenMP
* Mentor: Huidae Cho
* Co-mentor: Vaclav Petras, Anna Petrasova
* Project length: 175 or 350 hours (take your pick)
* Rating: difficult
* Expected Outcomes: parallelized 2-5 tools, depending on complexity
* Test of skills (one or more):
** Address https://github.com/OSGeo/grass/issues/5776 (carefully read the existing conversation in the issue and linked PR)
** Pick a tool and develop prototype implementation of the parallelization.

=== Improve GRASS user experience in Jupyter Notebook ===
[[File:Jupyter_interactive_viewshed.png|500px|thumb|right|InteractiveMap in grass.jupyter library]]
Python package [https://grass.osgeo.org/grass-stable/manuals/libpython/grass.jupyter.html grass.jupyter] was developed during [https://trac.osgeo.org/grass/wiki/GSoC/2021/JupyterAndGRASS GSoC 2021] to simplify running GRASS from Jupyter Notebooks and displaying data. This project could focus on adding features such as better symbology handling and adding legend to InteractiveMap and better integration with matplotlib.

* Requirements: Python
* Mentor: Anna Petrasova
* Co-mentor: Vaclav Petras, Helena Mitasova, Corey White
* Project length: 175 or 350 hours (take your pick)
* Rating: easy to medium
* Expected Outcomes: improved user experience when using GRASS through notebooks
* Test of skills: write a test for [https://github.com/OSGeo/grass/tree/main/python/grass/jupyter grass.jupyter library] using python unittest or pytest, more info [https://grass.osgeo.org/grass-devel/manuals/libpython/gunittest_testing.html here].

=== Add JSON output to different tools ===
There are several tools in GRASS that would benefit from a JSON-formatted output.
Besides adding the JSON output, the work would also include adding tests and basic documentation.
* Requirements: C, Python
* Mentor: Vaclav Petras
* Co-mentor: Anna Petrasova, Corey White
* Project length: 175 or 350 hours (take your pick)
* Rating: easy to medium
* Expected Outcomes: 10-20 tools (depending on project length and complexity of the tool) tools with well tested JSON output
* Test of skills (pick one or more):
** https://github.com/OSGeo/grass/issues/6968
** https://github.com/OSGeo/grass/issues/6969
** https://github.com/OSGeo/grass/issues/6970

=== Support writing tests with pytest ===

* The current testing framework, ''[https://grass.osgeo.org/grass-stable/manuals/libpython/gunittest.html grass.gunittest]'', was written before migration to Git/GitHub and when long free runs in 3rd party services were unthinkable. Additionally, some no longer relevant goals were prioritized, such as independence on the current code, detailed custom HTML reports, success tracking over time, and high specialization towards GRASS-specifics.
* ''grass.gunittest'' is based on Python ''unittest'' package and many projects since then migrated to //pytest//, e.g., GDAL and Numpy. While ''unittest'' is inspired by Java's JUnit, ''pytest'' is designed to support writing small, readable tests, and uses plain `assert` statements instead of many different assert methods.
* Using ''pytest'' should lead to tests which feel more like Python scripts and to minimum of testing-specific code.
* An example issue of ''grass.gunittest'' is that it doesn't work well with tests of the main GRASS executable (prominence of `grass ... --exec` is yet another new thing which changed since ''grass.gunittest'' was designed).
* Two main things needed:
** Create general comparison functions from the ''grass.gunittest'' assert methods so that they can be used with pytest.
** Current grass.script.setup.init function and grass.script.core.create_location function don't work well in the context of a pytest test function. More
* Additional things needed:
** Fixture for pytest to set up and tear down a GRASS session in a temporary mapset.

* Requirements: Python
* Project length: 175 or 350 hours (take your pick)
* Mentor: Vaclav Petras
* Co-mentor: Stefan Blumentrath
* Proposed by: Vaclav Petras
* Rating: easy to medium
* Expected Outcomes: Convenient way of writing tests with pytest
* Test of skills: Fix failing tests and/or write new tests (more is better). Alternatively, addressing a smaller problem in the testing framework is a good task, too.

=== Fix known code defects ===

* Fix code defects (security or code quality) such as those reported by Coverity Scan.
* Mentors: Vaclav Petras
* Co-mentors: ?
* Proposed by: Vaclav Petras
* Project length: 175 or 350 hours (flexible)
* Rating: medium
* Requirements:
** Language: C
** Proposal: Define milestones which will be used during the evaluation.
* Expected outcomes:
** Reduction of issues by 70-100%.
** New tests for changed code if missing.
* Test and training tasks (complete more than one): Fix cppcheck issue.

=== Subcommand CLI for GRASS ===

* Make running of GRASS tools in command line as easy as possible.
** `grass run r.slope.aspect elevation=elevation.tiff slope=slope.tiff aspect=aspect.tiff`
* Project length: 350 hours
* Rating: medium
* Requirements:
** Language: Python
** Proposal: Student needs to show sufficient understanding of data and project handling in GRASS. Furthermore, the proposal needs to present, at least, concrete formulation of ideas, identification of missing and existing parts, and new subcommands.
* Mentors: Vaclav Petras
* Co-mentors: Stefan Blumentrath, Corey White
* Proposed by: Vaclav Petras
* Expected outcomes:
** A subcommand which runs a GRASS tool on GeoTiff and GeoPackage in one step.
** A complete parity with the existing CLI.
** An underlying Python API which will be used to implement the CLI.
* Test and training tasks (complete one or more): Add a subcommand, sub-subcommand, or an option to the experimental interface (with tests).
** Add `--region` to set a temporary computational region for the execution, e.g. `--region="raster=raster_name"`.
** Add `--import-raster=some/file.tiff` which imports (r.import) a raster file (same for vector and similarly for export).
** Add `--link-raster=some/file.tiff` which links (r.external) a raster file (same for vector and similarly for r.external.out).

Current state:

# Reveals the existing subcommands
PYTHONPATH=$(grass --config python-path) python -m grass.app --help
# Allows running subset of commands
grass run --help



=== GUI: Add space-time datasets support in Data Catalog ===
[[File:GUI_data_tab.png|400px|thumb|right|Data catalog]]
Currently GRASS Data Catalog shows only raster and vector maps. The goal of this project is to add support for space-time datasets. It is mainly space-time raster datasets. In the next phase of the project support for other types of space-time datasets (vector and 3D raster) could be added. Besides displaying space-time datasets in the layer tree, it is also about adding the equivalent functionality currently available for raster and vector layers from the context menu.

* Requirements: familiar with Python
* Project length: 175 or 350 hours
* Mentor: Martin Landa
* Co-mentor: Anna Petrasova
* Proposed by: Martin Landa
* Rating: medium
* Expected Outcomes: 175 hours basic support for space-time raster datasets; 350 extended support also for other space-time datasets types (vector, 3D raster)
* Test of skills:
** suggest/implement solution for completing https://github.com/OSGeo/grass/issues/2599

=== Add {your research idea} to GRASS ===

* In general, you can propose any topic, but you can specifically propose integrating your research or research idea into GRASS.
* Requirements:
** Language:
*** Depends on the project, often Python, sometimes C.
*** Adding your latest ecological analysis
** Proposal:
*** Discuss relevance to GRASS.
*** Describe technical steps needed for integration.
*** Describe whether it is an addition of a tool (module) or a change in one of the libraries. If it is a tool, specify if it should be included in the core grass repository or in grass-addons repository and why.
*** Specify what research was done and what needs to be accomplished in order to have usable product at the end of summer.
*** Specify who will provide the research expertise.
* Project length: 175 or 350 hours (take your pick)
* Rating: from low to hard
* Mentors:
** GRASS project will provide technical mentors, but it is up to the applicant to ensure the research part is mentored well. An exception may be granted to applicants which can demonstrate that the research is finished or that they have enough expertise themselves.
** Possible technical mentors: Vaclav Petras, Anna Petrasova
** Research mentors: Bring in an expert from your field, e.g., your academic advisor or project principal investigator (if needed).
* Proposed by: Vaclav Petras
* Expected outcome: Working feature which is integrated and merged at the end of the project.
* Test and training tasks:
** Create a test in Python for an existing tool in the grass-addons repository or in the core grass repository.

=== Title of idea ===

Description here

* Requirements:
* Project length: (175 or 350 hours)
* Mentor:
* Proposed by:
* Rating:
* Expected Outcomes:
* Test of skills:
* Other:

== Tips for students ==
* Follow official [https://github.com/numfocus/gsoc/blob/master/CONTRIBUTING-contributors.md NumFOCUS guidelines].
* Include "GRASS" in the title of our idea to easily distinguish ideas and projects inside NumFOCUS.
* If you have your own ideas we encourage you to propose them. Explain them on the [https://discourse.osgeo.org/c/grass/developer/61 on our Discourse].
* Follow some good practices in your ideas and proposals:
** Stress why the project would be useful.
** Show that you know how you will proceed. That is, make sure that you can demonstrate that the proposal is feasible in the given time frame.
** Be specific in the implementation (or at least as specific as you can).
** Explain what the final product will look like and how it will work. You can add drawings or mock-ups.
** Explain how the idea relates to existing GRASS functions, features, and needs.
** Do not include steps such as "install GRASS", "compile GRASS libraries (on my machine)", "read about the API". You should do this before applying to GSoC.
* Compile GRASS from source and prepare environment for development:
** Read [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md CONTRIBUTING file].
* Prove your worth by being active on the [https://discourse.osgeo.org/c/grass/developer/61 GRASS Discourse] or other channels ([https://github.com/OSGeo/grass/discussions GitHub Discussions], fix some [https://github.com/OSGeo/grass/issues bugs], and/or implement some (smaller) features, or write some (simpler) GRASS module, and post it to mailing list. There's no better way to demonstrate your willingness and abilities. Do this before start you apply to GSoC.
* Also note that fixing existing bugs and/or implementing enhancements will be a part of student evaluation.

{{GSoC}}

GRASS GSoC Ideas 2026

2026-01-26T04:15:24Z

Annakrat: /* Parallelization of existing tools */

== About ==
Important: While we are still an OSGeo project, we changed our fiscal sponsor to [https://numfocus.org/ NumFOCUS].

''As a result, GRASS participates in GSoC under the [https://numfocus.org/ NumFOCUS] umbrella organization.''

Read more about our governance [https://grass.osgeo.org/about/governance/ on GRASS website].

* [https://numfocus.org/programs/google-summer-code The NumFOCUS GSoC main page]
* [https://github.com/numfocus/gsoc/blob/master/CONTRIBUTING-contributors.md NumFOCUS guidelines for contributors].
* [https://summerofcode.withgoogle.com/ Official GSoC page at Google]

== AI Tool Usage Policy ==
We acknowledge that applicants may use AI tools (like ChatGPT, Copilot, etc.) to assist with proposal writing and coding. However:

* Your proposal should reflect your own understanding and voice. AI-generated "slop" (overly generic or regurgitated content) is easy to spot and will hurt your application.
* We evaluate applications primarily on GitHub contributions and communication with the GRASS community, not just proposal polish.
* Show us you understand the project through high-quality pull requests on GitHub.
* Disclose AI usage: If you use AI tools in your proposal or code contributions, please disclose the extent to which you used them (e.g., for brainstorming, proofreading, code suggestions, etc.).

== Ideas ==
If you are a student you can suggest a new idea or pick up an existing one. In any case write about it to [https://discourse.osgeo.org/c/grass/developer/61 OSGeo Discourse forum for GRASS developers], [https://github.com/OSGeo/grass/discussions GitHub Discussions], or [https://gitter.im/grassgis/community Gitter].

You are invited as well to have a close look at ideas from previous years ([https://trac.osgeo.org/grass/wiki/GSoC/2014 2014], [https://trac.osgeo.org/grass/wiki/GSoC/2015 2015], [https://trac.osgeo.org/grass/wiki/GSoC/2016 2016],
[https://trac.osgeo.org/grass/wiki/GSoC/2017 2017],
[https://trac.osgeo.org/grass/wiki/GSoC/2018 2018],
[https://trac.osgeo.org/grass/wiki/GSoC/2019 2019],
[https://trac.osgeo.org/grass/wiki/GSoC/2020 2020],
[https://trac.osgeo.org/grass/wiki/GSoC/2021 2021],
[https://trac.osgeo.org/grass/wiki/GSoC/2022 2022],
[https://trac.osgeo.org/grass/wiki/GSoC/2023 2023])
which have not yet been implemented.
You can also look at accepted GRASS GSoC [https://trac.osgeo.org/grass/wiki/GSoC projects from previous years] for an idea of scope.''

=== Parallelization of existing tools ===

There are several tools that would benefit from parallelization with OpenMP, e.g. r.texture, r.fill.stats, r/v.surf.idw, r.viewshed, v.to.rast, r.grow.distance, v.surf.bspline, r.proj, ...
For overview of current state, see [[Raster_Parallelization_with_OpenMP]].

* Requirements: familiarity with C, OpenMP
* Mentor: Huidae Cho
* Co-mentor: Vaclav Petras, Anna Petrasova
* Project length: 175 or 350 hours (take your pick)
* Rating: difficult
* Expected Outcomes: parallelized 2-5 tools, depending on complexity
* Test of skills (one or more):
** Address https://github.com/OSGeo/grass/issues/5776 (carefully read the existing conversation in the issue and linked PR)
** Pick a tool and develop prototype implementation of the parallelization.

=== Improve GRASS user experience in Jupyter Notebook ===
[[File:Jupyter_interactive_viewshed.png|500px|thumb|right|InteractiveMap in grass.jupyter library]]
Python package [https://grass.osgeo.org/grass-stable/manuals/libpython/grass.jupyter.html grass.jupyter] was developed during [https://trac.osgeo.org/grass/wiki/GSoC/2021/JupyterAndGRASS GSoC 2021] to simplify running GRASS from Jupyter Notebooks and displaying data. This project could focus on adding features such as increasing interactivity of displayed data using ipyleaflet, adding API for managing projects and subprojects (i.e., locations/mapsets), creating GUI for commands, ...

* Requirements: Python
* Mentor: Anna Petrasova
* Co-mentor: Vaclav Petras, Helena Mitasova, Corey White
* Project length: 175 or 350 hours (take your pick)
* Rating: easy to medium
* Expected Outcomes: improved user experience when using GRASS through notebooks
* Test of skills: https://github.com/OSGeo/grass/issues/3276, or write a test for [https://github.com/OSGeo/grass/tree/main/python/grass/jupyter grass.jupyter library] using python unittest or pytest, more info [https://grass.osgeo.org/grass-devel/manuals/libpython/gunittest_testing.html here].

=== Add JSON output to different tools ===
There are several tools in GRASS that would benefit from a JSON-formatted output.
Besides adding the JSON output, the work would also include adding tests and basic documentation.
* Requirements: C, Python
* Mentor: Vaclav Petras
* Co-mentor: Anna Petrasova, Corey White
* Project length: 175 or 350 hours (take your pick)
* Rating: easy to medium
* Expected Outcomes: 10-20 tools (depending on project length and complexity of the tool) tools with well tested JSON output
* Test of skills (pick one or more):
** https://github.com/OSGeo/grass/issues/6968
** https://github.com/OSGeo/grass/issues/6969
** https://github.com/OSGeo/grass/issues/6970

=== Support writing tests with pytest ===

* The current testing framework, ''[https://grass.osgeo.org/grass-stable/manuals/libpython/gunittest.html grass.gunittest]'', was written before migration to Git/GitHub and when long free runs in 3rd party services were unthinkable. Additionally, some no longer relevant goals were prioritized, such as independence on the current code, detailed custom HTML reports, success tracking over time, and high specialization towards GRASS-specifics.
* ''grass.gunittest'' is based on Python ''unittest'' package and many projects since then migrated to //pytest//, e.g., GDAL and Numpy. While ''unittest'' is inspired by Java's JUnit, ''pytest'' is designed to support writing small, readable tests, and uses plain `assert` statements instead of many different assert methods.
* Using ''pytest'' should lead to tests which feel more like Python scripts and to minimum of testing-specific code.
* An example issue of ''grass.gunittest'' is that it doesn't work well with tests of the main GRASS executable (prominence of `grass ... --exec` is yet another new thing which changed since ''grass.gunittest'' was designed).
* Two main things needed:
** Create general comparison functions from the ''grass.gunittest'' assert methods so that they can be used with pytest.
** Current grass.script.setup.init function and grass.script.core.create_location function don't work well in the context of a pytest test function. More
* Additional things needed:
** Fixture for pytest to set up and tear down a GRASS session in a temporary mapset.

* Requirements: Python
* Project length: 175 or 350 hours (take your pick)
* Mentor: Vaclav Petras
* Co-mentor: Stefan Blumentrath
* Proposed by: Vaclav Petras
* Rating: easy to medium
* Expected Outcomes: Convenient way of writing tests with pytest
* Test of skills: Fix failing tests and/or write new tests (more is better). Alternatively, addressing a smaller problem in the testing framework is a good task, too.

=== Fix known code defects ===

* Fix code defects (security or code quality) such as those reported by Coverity Scan.
* Mentors: Vaclav Petras
* Co-mentors: ?
* Proposed by: Vaclav Petras
* Project length: 175 or 350 hours (flexible)
* Rating: medium
* Requirements:
** Language: C
** Proposal: Define milestones which will be used during the evaluation.
* Expected outcomes:
** Reduction of issues by 70-100%.
** New tests for changed code if missing.
* Test and training tasks (complete more than one): Fix cppcheck issue.

=== Subcommand CLI for GRASS ===

* Make running of GRASS tools in command line as easy as possible.
** `grass run r.slope.aspect elevation=elevation.tiff slope=slope.tiff aspect=aspect.tiff`
* Project length: 350 hours
* Rating: medium
* Requirements:
** Language: Python
** Proposal: Student needs to show sufficient understanding of data and project handling in GRASS. Furthermore, the proposal needs to present, at least, concrete formulation of ideas, identification of missing and existing parts, and new subcommands.
* Mentors: Vaclav Petras
* Co-mentors: Stefan Blumentrath, Corey White
* Proposed by: Vaclav Petras
* Expected outcomes:
** A subcommand which runs a GRASS tool on GeoTiff and GeoPackage in one step.
** A complete parity with the existing CLI.
** An underlying Python API which will be used to implement the CLI.
* Test and training tasks (complete one or more): Add a subcommand, sub-subcommand, or an option to the experimental interface (with tests).
** Add `--region` to set a temporary computational region for the execution, e.g. `--region="raster=raster_name"`.
** Add `--import-raster=some/file.tiff` which imports (r.import) a raster file (same for vector and similarly for export).
** Add `--link-raster=some/file.tiff` which links (r.external) a raster file (same for vector and similarly for r.external.out).

Current state:

# Reveals the existing subcommands
PYTHONPATH=$(grass --config python-path) python -m grass.app --help
# Allows running subset of commands
grass run --help



=== GUI: Add space-time datasets support in Data Catalog ===
[[File:GUI_data_tab.png|400px|thumb|right|Data catalog]]
Currently GRASS Data Catalog shows only raster and vector maps. The goal of this project is to add support for space-time datasets. It is mainly space-time raster datasets. In the next phase of the project support for other types of space-time datasets (vector and 3D raster) could be added. Besides displaying space-time datasets in the layer tree, it is also about adding the equivalent functionality currently available for raster and vector layers from the context menu.

* Requirements: familiar with Python
* Project length: 175 or 350 hours
* Mentor: Martin Landa
* Co-mentor: Anna Petrasova
* Proposed by: Martin Landa
* Rating: medium
* Expected Outcomes: 175 hours basic support for space-time raster datasets; 350 extended support also for other space-time datasets types (vector, 3D raster)
* Test of skills:
** suggest/implement solution for completing https://github.com/OSGeo/grass/issues/2599

=== Add {your research idea} to GRASS ===

* In general, you can propose any topic, but you can specifically propose integrating your research or research idea into GRASS.
* Requirements:
** Language:
*** Depends on the project, often Python, sometimes C.
*** Adding your latest ecological analysis
** Proposal:
*** Discuss relevance to GRASS.
*** Describe technical steps needed for integration.
*** Describe whether it is an addition of a tool (module) or a change in one of the libraries. If it is a tool, specify if it should be included in the core grass repository or in grass-addons repository and why.
*** Specify what research was done and what needs to be accomplished in order to have usable product at the end of summer.
*** Specify who will provide the research expertise.
* Project length: 175 or 350 hours (take your pick)
* Rating: from low to hard
* Mentors:
** GRASS project will provide technical mentors, but it is up to the applicant to ensure the research part is mentored well. An exception may be granted to applicants which can demonstrate that the research is finished or that they have enough expertise themselves.
** Possible technical mentors: Vaclav Petras, Anna Petrasova
** Research mentors: Bring in an expert from your field, e.g., your academic advisor or project principal investigator (if needed).
* Proposed by: Vaclav Petras
* Expected outcome: Working feature which is integrated and merged at the end of the project.
* Test and training tasks:
** Create a test in Python for an existing tool in the grass-addons repository or in the core grass repository.

=== Title of idea ===

Description here

* Requirements:
* Project length: (175 or 350 hours)
* Mentor:
* Proposed by:
* Rating:
* Expected Outcomes:
* Test of skills:
* Other:

== Tips for students ==
* Follow official [https://github.com/numfocus/gsoc/blob/master/CONTRIBUTING-contributors.md NumFOCUS guidelines].
* Include "GRASS" in the title of our idea to easily distinguish ideas and projects inside NumFOCUS.
* If you have your own ideas we encourage you to propose them. Explain them on the [https://discourse.osgeo.org/c/grass/developer/61 on our Discourse].
* Follow some good practices in your ideas and proposals:
** Stress why the project would be useful.
** Show that you know how you will proceed. That is, make sure that you can demonstrate that the proposal is feasible in the given time frame.
** Be specific in the implementation (or at least as specific as you can).
** Explain what the final product will look like and how it will work. You can add drawings or mock-ups.
** Explain how the idea relates to existing GRASS functions, features, and needs.
** Do not include steps such as "install GRASS", "compile GRASS libraries (on my machine)", "read about the API". You should do this before applying to GSoC.
* Compile GRASS from source and prepare environment for development:
** Read [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md CONTRIBUTING file].
* Prove your worth by being active on the [https://discourse.osgeo.org/c/grass/developer/61 GRASS Discourse] or other channels ([https://github.com/OSGeo/grass/discussions GitHub Discussions], fix some [https://github.com/OSGeo/grass/issues bugs], and/or implement some (smaller) features, or write some (simpler) GRASS module, and post it to mailing list. There's no better way to demonstrate your willingness and abilities. Do this before start you apply to GSoC.
* Also note that fixing existing bugs and/or implementing enhancements will be a part of student evaluation.

{{GSoC}}

GRASS GSoC Ideas 2026

2026-01-26T03:52:07Z

Annakrat: /* Add JSON output to different tools in C */

== About ==
Important: While we are still an OSGeo project, we changed our fiscal sponsor to [https://numfocus.org/ NumFOCUS].

''As a result, GRASS participates in GSoC under the [https://numfocus.org/ NumFOCUS] umbrella organization.''

Read more about our governance [https://grass.osgeo.org/about/governance/ on GRASS website].

* [https://numfocus.org/programs/google-summer-code The NumFOCUS GSoC main page]
* [https://github.com/numfocus/gsoc/blob/master/CONTRIBUTING-contributors.md NumFOCUS guidelines for contributors].
* [https://summerofcode.withgoogle.com/ Official GSoC page at Google]

== AI Tool Usage Policy ==
We acknowledge that applicants may use AI tools (like ChatGPT, Copilot, etc.) to assist with proposal writing and coding. However:

* Your proposal should reflect your own understanding and voice. AI-generated "slop" (overly generic or regurgitated content) is easy to spot and will hurt your application.
* We evaluate applications primarily on GitHub contributions and communication with the GRASS community, not just proposal polish.
* Show us you understand the project through high-quality pull requests on GitHub.
* Disclose AI usage: If you use AI tools in your proposal or code contributions, please disclose the extent to which you used them (e.g., for brainstorming, proofreading, code suggestions, etc.).

== Ideas ==
If you are a student you can suggest a new idea or pick up an existing one. In any case write about it to [https://discourse.osgeo.org/c/grass/developer/61 OSGeo Discourse forum for GRASS developers], [https://github.com/OSGeo/grass/discussions GitHub Discussions], or [https://gitter.im/grassgis/community Gitter].

You are invited as well to have a close look at ideas from previous years ([https://trac.osgeo.org/grass/wiki/GSoC/2014 2014], [https://trac.osgeo.org/grass/wiki/GSoC/2015 2015], [https://trac.osgeo.org/grass/wiki/GSoC/2016 2016],
[https://trac.osgeo.org/grass/wiki/GSoC/2017 2017],
[https://trac.osgeo.org/grass/wiki/GSoC/2018 2018],
[https://trac.osgeo.org/grass/wiki/GSoC/2019 2019],
[https://trac.osgeo.org/grass/wiki/GSoC/2020 2020],
[https://trac.osgeo.org/grass/wiki/GSoC/2021 2021],
[https://trac.osgeo.org/grass/wiki/GSoC/2022 2022],
[https://trac.osgeo.org/grass/wiki/GSoC/2023 2023])
which have not yet been implemented.
You can also look at accepted GRASS GSoC [https://trac.osgeo.org/grass/wiki/GSoC projects from previous years] for an idea of scope.''

=== Parallelization of existing tools ===

There are several tools that would benefit from parallelization with OpenMP, e.g. r.texture, r.horizon, r.fill.stats, r/v.surf.idw, r.viewshed, v.to.rast, r.grow.distance, v.surf.bspline, ...
For overview of current state, see [[Raster_Parallelization_with_OpenMP]].

* Requirements: familiarity with C, OpenMP
* Mentor: Huidae Cho
* Co-mentor: Vaclav Petras, Anna Petrasova
* Project length: 175 or 350 hours (take your pick)
* Rating: medium
* Expected Outcomes: parallelized module or modules, depending on complexity

=== Improve GRASS user experience in Jupyter Notebook ===
[[File:Jupyter_interactive_viewshed.png|500px|thumb|right|InteractiveMap in grass.jupyter library]]
Python package [https://grass.osgeo.org/grass-stable/manuals/libpython/grass.jupyter.html grass.jupyter] was developed during [https://trac.osgeo.org/grass/wiki/GSoC/2021/JupyterAndGRASS GSoC 2021] to simplify running GRASS from Jupyter Notebooks and displaying data. This project could focus on adding features such as increasing interactivity of displayed data using ipyleaflet, adding API for managing projects and subprojects (i.e., locations/mapsets), creating GUI for commands, ...

* Requirements: Python
* Mentor: Anna Petrasova
* Co-mentor: Vaclav Petras, Helena Mitasova, Corey White
* Project length: 175 or 350 hours (take your pick)
* Rating: easy to medium
* Expected Outcomes: improved user experience when using GRASS through notebooks
* Test of skills: https://github.com/OSGeo/grass/issues/3276, or write a test for [https://github.com/OSGeo/grass/tree/main/python/grass/jupyter grass.jupyter library] using python unittest or pytest, more info [https://grass.osgeo.org/grass-devel/manuals/libpython/gunittest_testing.html here].

=== Add JSON output to different tools ===
There are several tools in GRASS that would benefit from a JSON-formatted output.
Besides adding the JSON output, the work would also include adding tests and basic documentation.
* Requirements: C, Python
* Mentor: Vaclav Petras
* Co-mentor: Anna Petrasova, Corey White
* Project length: 175 or 350 hours (take your pick)
* Rating: easy to medium
* Expected Outcomes: 10-20 tools (depending on project length and complexity of the tool) tools with well tested JSON output
* Test of skills (pick one or more):
** https://github.com/OSGeo/grass/issues/6968
** https://github.com/OSGeo/grass/issues/6969
** https://github.com/OSGeo/grass/issues/6970

=== Support writing tests with pytest ===

* The current testing framework, ''[https://grass.osgeo.org/grass-stable/manuals/libpython/gunittest.html grass.gunittest]'', was written before migration to Git/GitHub and when long free runs in 3rd party services were unthinkable. Additionally, some no longer relevant goals were prioritized, such as independence on the current code, detailed custom HTML reports, success tracking over time, and high specialization towards GRASS-specifics.
* ''grass.gunittest'' is based on Python ''unittest'' package and many projects since then migrated to //pytest//, e.g., GDAL and Numpy. While ''unittest'' is inspired by Java's JUnit, ''pytest'' is designed to support writing small, readable tests, and uses plain `assert` statements instead of many different assert methods.
* Using ''pytest'' should lead to tests which feel more like Python scripts and to minimum of testing-specific code.
* An example issue of ''grass.gunittest'' is that it doesn't work well with tests of the main GRASS executable (prominence of `grass ... --exec` is yet another new thing which changed since ''grass.gunittest'' was designed).
* Two main things needed:
** Create general comparison functions from the ''grass.gunittest'' assert methods so that they can be used with pytest.
** Current grass.script.setup.init function and grass.script.core.create_location function don't work well in the context of a pytest test function. More
* Additional things needed:
** Fixture for pytest to set up and tear down a GRASS session in a temporary mapset.

* Requirements: Python
* Project length: 175 or 350 hours (take your pick)
* Mentor: Vaclav Petras
* Co-mentor: Stefan Blumentrath
* Proposed by: Vaclav Petras
* Rating: easy to medium
* Expected Outcomes: Convenient way of writing tests with pytest
* Test of skills: Fix failing tests and/or write new tests (more is better). Alternatively, addressing a smaller problem in the testing framework is a good task, too.

=== Fix known code defects ===

* Fix code defects (security or code quality) such as those reported by Coverity Scan.
* Mentors: Vaclav Petras
* Co-mentors: ?
* Proposed by: Vaclav Petras
* Project length: 175 or 350 hours (flexible)
* Rating: medium
* Requirements:
** Language: C
** Proposal: Define milestones which will be used during the evaluation.
* Expected outcomes:
** Reduction of issues by 70-100%.
** New tests for changed code if missing.
* Test and training tasks (complete more than one): Fix cppcheck issue.

=== Subcommand CLI for GRASS ===

* Make running of GRASS tools in command line as easy as possible.
** `grass run r.slope.aspect elevation=elevation.tiff slope=slope.tiff aspect=aspect.tiff`
* Project length: 350 hours
* Rating: medium
* Requirements:
** Language: Python
** Proposal: Student needs to show sufficient understanding of data and project handling in GRASS. Furthermore, the proposal needs to present, at least, concrete formulation of ideas, identification of missing and existing parts, and new subcommands.
* Mentors: Vaclav Petras
* Co-mentors: Stefan Blumentrath, Corey White
* Proposed by: Vaclav Petras
* Expected outcomes:
** A subcommand which runs a GRASS tool on GeoTiff and GeoPackage in one step.
** A complete parity with the existing CLI.
** An underlying Python API which will be used to implement the CLI.
* Test and training tasks (complete one or more): Add a subcommand, sub-subcommand, or an option to the experimental interface (with tests).
** Add `--region` to set a temporary computational region for the execution, e.g. `--region="raster=raster_name"`.
** Add `--import-raster=some/file.tiff` which imports (r.import) a raster file (same for vector and similarly for export).
** Add `--link-raster=some/file.tiff` which links (r.external) a raster file (same for vector and similarly for r.external.out).

Current state:

# Reveals the existing subcommands
PYTHONPATH=$(grass --config python-path) python -m grass.app --help
# Allows running subset of commands
grass run --help



=== GUI: Add space-time datasets support in Data Catalog ===
[[File:GUI_data_tab.png|400px|thumb|right|Data catalog]]
Currently GRASS Data Catalog shows only raster and vector maps. The goal of this project is to add support for space-time datasets. It is mainly space-time raster datasets. In the next phase of the project support for other types of space-time datasets (vector and 3D raster) could be added. Besides displaying space-time datasets in the layer tree, it is also about adding the equivalent functionality currently available for raster and vector layers from the context menu.

* Requirements: familiar with Python
* Project length: 175 or 350 hours
* Mentor: Martin Landa
* Co-mentor: Anna Petrasova
* Proposed by: Martin Landa
* Rating: medium
* Expected Outcomes: 175 hours basic support for space-time raster datasets; 350 extended support also for other space-time datasets types (vector, 3D raster)
* Test of skills:
** suggest/implement solution for completing https://github.com/OSGeo/grass/issues/2599

=== Add {your research idea} to GRASS ===

* In general, you can propose any topic, but you can specifically propose integrating your research or research idea into GRASS.
* Requirements:
** Language:
*** Depends on the project, often Python, sometimes C.
*** Adding your latest ecological analysis
** Proposal:
*** Discuss relevance to GRASS.
*** Describe technical steps needed for integration.
*** Describe whether it is an addition of a tool (module) or a change in one of the libraries. If it is a tool, specify if it should be included in the core grass repository or in grass-addons repository and why.
*** Specify what research was done and what needs to be accomplished in order to have usable product at the end of summer.
*** Specify who will provide the research expertise.
* Project length: 175 or 350 hours (take your pick)
* Rating: from low to hard
* Mentors:
** GRASS project will provide technical mentors, but it is up to the applicant to ensure the research part is mentored well. An exception may be granted to applicants which can demonstrate that the research is finished or that they have enough expertise themselves.
** Possible technical mentors: Vaclav Petras, Anna Petrasova
** Research mentors: Bring in an expert from your field, e.g., your academic advisor or project principal investigator (if needed).
* Proposed by: Vaclav Petras
* Expected outcome: Working feature which is integrated and merged at the end of the project.
* Test and training tasks:
** Create a test in Python for an existing tool in the grass-addons repository or in the core grass repository.

=== Title of idea ===

Description here

* Requirements:
* Project length: (175 or 350 hours)
* Mentor:
* Proposed by:
* Rating:
* Expected Outcomes:
* Test of skills:
* Other:

== Tips for students ==
* Follow official [https://github.com/numfocus/gsoc/blob/master/CONTRIBUTING-contributors.md NumFOCUS guidelines].
* Include "GRASS" in the title of our idea to easily distinguish ideas and projects inside NumFOCUS.
* If you have your own ideas we encourage you to propose them. Explain them on the [https://discourse.osgeo.org/c/grass/developer/61 on our Discourse].
* Follow some good practices in your ideas and proposals:
** Stress why the project would be useful.
** Show that you know how you will proceed. That is, make sure that you can demonstrate that the proposal is feasible in the given time frame.
** Be specific in the implementation (or at least as specific as you can).
** Explain what the final product will look like and how it will work. You can add drawings or mock-ups.
** Explain how the idea relates to existing GRASS functions, features, and needs.
** Do not include steps such as "install GRASS", "compile GRASS libraries (on my machine)", "read about the API". You should do this before applying to GSoC.
* Compile GRASS from source and prepare environment for development:
** Read [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md CONTRIBUTING file].
* Prove your worth by being active on the [https://discourse.osgeo.org/c/grass/developer/61 GRASS Discourse] or other channels ([https://github.com/OSGeo/grass/discussions GitHub Discussions], fix some [https://github.com/OSGeo/grass/issues bugs], and/or implement some (smaller) features, or write some (simpler) GRASS module, and post it to mailing list. There's no better way to demonstrate your willingness and abilities. Do this before start you apply to GSoC.
* Also note that fixing existing bugs and/or implementing enhancements will be a part of student evaluation.

{{GSoC}}

GRASS GSoC Ideas 2026

2026-01-21T20:15:14Z

Annakrat: /* AI Tool Usage Policy */

== About ==
Important: While we are still an OSGeo project, we changed our fiscal sponsor to [https://numfocus.org/ NumFOCUS].

''As a result, GRASS participates in GSoC under the [https://numfocus.org/ NumFOCUS] umbrella organization.''

Read more about our governance [https://grass.osgeo.org/about/governance/ on GRASS website].

* [https://numfocus.org/programs/google-summer-code The NumFOCUS GSoC main page]
* [https://github.com/numfocus/gsoc/blob/master/CONTRIBUTING-contributors.md NumFOCUS guidelines for contributors].
* [https://summerofcode.withgoogle.com/ Official GSoC page at Google]

== AI Tool Usage Policy ==
We acknowledge that applicants may use AI tools (like ChatGPT, Copilot, etc.) to assist with proposal writing and coding. However:

* Your proposal should reflect your own understanding and voice. AI-generated "slop" (overly generic or regurgitated content) is easy to spot and will hurt your application.
* We evaluate applications primarily on GitHub contributions and communication with the GRASS community, not just proposal polish.
* Show us you understand the project through high-quality pull requests on GitHub.
* Disclose AI usage: If you use AI tools in your proposal or code contributions, please disclose the extent to which you used them (e.g., for brainstorming, proofreading, code suggestions, etc.).

== Ideas ==
If you are a student you can suggest a new idea or pick up an existing one. In any case write about it to [https://discourse.osgeo.org/c/grass/developer/61 OSGeo Discourse forum for GRASS developers], [https://github.com/OSGeo/grass/discussions GitHub Discussions], or [https://gitter.im/grassgis/community Gitter].

You are invited as well to have a close look at ideas from previous years ([https://trac.osgeo.org/grass/wiki/GSoC/2014 2014], [https://trac.osgeo.org/grass/wiki/GSoC/2015 2015], [https://trac.osgeo.org/grass/wiki/GSoC/2016 2016],
[https://trac.osgeo.org/grass/wiki/GSoC/2017 2017],
[https://trac.osgeo.org/grass/wiki/GSoC/2018 2018],
[https://trac.osgeo.org/grass/wiki/GSoC/2019 2019],
[https://trac.osgeo.org/grass/wiki/GSoC/2020 2020],
[https://trac.osgeo.org/grass/wiki/GSoC/2021 2021],
[https://trac.osgeo.org/grass/wiki/GSoC/2022 2022],
[https://trac.osgeo.org/grass/wiki/GSoC/2023 2023])
which have not yet been implemented.
You can also look at accepted GRASS GSoC [https://trac.osgeo.org/grass/wiki/GSoC projects from previous years] for an idea of scope.''

=== Parallelization of existing tools ===

There are several tools that would benefit from parallelization with OpenMP, e.g. r.texture, r.horizon, r.fill.stats, r/v.surf.idw, r.viewshed, v.to.rast, r.grow.distance, v.surf.bspline, ...
For overview of current state, see [[Raster_Parallelization_with_OpenMP]].

* Requirements: familiarity with C, OpenMP
* Mentor: Huidae Cho
* Co-mentor: Vaclav Petras, Anna Petrasova
* Project length: 175 or 350 hours (take your pick)
* Rating: medium
* Expected Outcomes: parallelized module or modules, depending on complexity

=== Improve GRASS user experience in Jupyter Notebook ===
[[File:Jupyter_interactive_viewshed.png|500px|thumb|right|InteractiveMap in grass.jupyter library]]
Python package [https://grass.osgeo.org/grass-stable/manuals/libpython/grass.jupyter.html grass.jupyter] was developed during [https://trac.osgeo.org/grass/wiki/GSoC/2021/JupyterAndGRASS GSoC 2021] to simplify running GRASS from Jupyter Notebooks and displaying data. This project could focus on adding features such as increasing interactivity of displayed data using ipyleaflet, adding API for managing projects and subprojects (i.e., locations/mapsets), creating GUI for commands, ...

* Requirements: Python
* Mentor: Anna Petrasova
* Co-mentor: Vaclav Petras, Helena Mitasova, Corey White
* Project length: 175 or 350 hours (take your pick)
* Rating: easy to medium
* Expected Outcomes: improved user experience when using GRASS through notebooks
* Test of skills: https://github.com/OSGeo/grass/issues/3276, or write a test for [https://github.com/OSGeo/grass/tree/main/python/grass/jupyter grass.jupyter library] using python unittest or pytest, more info [https://grass.osgeo.org/grass-devel/manuals/libpython/gunittest_testing.html here].

=== Add JSON output to different tools in C ===
There are several tools in GRASS that would benefit from a JSON-formatted output, see [https://github.com/OSGeo/grass/issues/3020 this issue for a list of tools]. Besides adding the JSON output, the work would also include adding tests and basic documentation.
* Requirements: C, Python for tests
* Mentor: Vaclav Petras
* Co-mentor: Anna Petrasova, Corey White
* Project length: 175 or 350 hours (take your pick)
* Rating: easy to medium
* Expected Outcomes: one or more (depending on project length and complexity of the tool) tools with well tested JSON output
* Test of skills: Address https://github.com/OSGeo/grass/issues/1044 for r.surf.fractal

=== Support writing tests with pytest ===

* The current testing framework, ''[https://grass.osgeo.org/grass-stable/manuals/libpython/gunittest.html grass.gunittest]'', was written before migration to Git/GitHub and when long free runs in 3rd party services were unthinkable. Additionally, some no longer relevant goals were prioritized, such as independence on the current code, detailed custom HTML reports, success tracking over time, and high specialization towards GRASS-specifics.
* ''grass.gunittest'' is based on Python ''unittest'' package and many projects since then migrated to //pytest//, e.g., GDAL and Numpy. While ''unittest'' is inspired by Java's JUnit, ''pytest'' is designed to support writing small, readable tests, and uses plain `assert` statements instead of many different assert methods.
* Using ''pytest'' should lead to tests which feel more like Python scripts and to minimum of testing-specific code.
* An example issue of ''grass.gunittest'' is that it doesn't work well with tests of the main GRASS executable (prominence of `grass ... --exec` is yet another new thing which changed since ''grass.gunittest'' was designed).
* Two main things needed:
** Create general comparison functions from the ''grass.gunittest'' assert methods so that they can be used with pytest.
** Current grass.script.setup.init function and grass.script.core.create_location function don't work well in the context of a pytest test function. More
* Additional things needed:
** Fixture for pytest to set up and tear down a GRASS session in a temporary mapset.

* Requirements: Python
* Project length: 175 or 350 hours (take your pick)
* Mentor: Vaclav Petras
* Co-mentor: Stefan Blumentrath
* Proposed by: Vaclav Petras
* Rating: easy to medium
* Expected Outcomes: Convenient way of writing tests with pytest
* Test of skills: Fix failing tests and/or write new tests (more is better). Alternatively, addressing a smaller problem in the testing framework is a good task, too.

=== New easy-to-use CLI and API for GRASS GIS ===

* Make running of GRASS GIS modules as easy as it is to run GDAL commands.
** `grass run r.slope.aspect elevation=elevation.tiff slope=slope.tiff aspect=aspect.tiff`
** CLI like GDAL has.
** No GRASS Database, Location, Mapset to deal with.
** No import, export from user perspective.
** Reasonable defaults for things like region.
** CLI and API still allows user to specify any of the above.
* Idea page with details: wiki:GSoC/2021/EasyToUseCliAndApiIdea
* Project length: 350 hours
* Rating: medium
* Requirements:
** Language: Python
** Proposal: Student needs to show sufficient understanding of the GRASS GIS Database structure and significantly extend on text below in terms of more concrete formulation of ideas and identification of missing and existing parts.
* Mentors: Vaclav Petras
* Co-mentors: Stefan Blumentrath, Corey White
* Proposed by: Vaclav Petras
* Expected outcomes: New subcommand which easily runs a GRASS module on GeoTiff and GeoPackage.
* Test and training tasks:
** Solve one of the tickets linked at the idea page.
** Add features to `grass` executable interface:
*** Make it possible to associate `*.gxw` files with `grass` executable (#1204) or at least add `--gui-workspace` or preferably just recognize it in the command line (distinguish it from database/location/mapset).
** Extend `--exec` functionality:
*** Add `--region` to set a temporary computational region for the execution, e.g. `--region="raster=raster_name"`
*** Add `--import-raster=some/file.tiff` which imports (r.import) a raster file (same for vector and similarly for export).
*** Add `--link-raster=some/file.tiff` which links (r.external) a raster file (same for vector and similarly for r.external.out).



=== GUI: Add space-time datasets support in Data Catalog ===
[[File:GUI_data_tab.png|400px|thumb|right|Data catalog]]
Currently GRASS Data Catalog shows only raster and vector maps. The goal of this project is to add support for space-time datasets. It is mainly space-time raster datasets. In the next phase of the project support for other types of space-time datasets (vector and 3D raster) could be added. Besides displaying space-time datasets in the layer tree, it is also about adding the equivalent functionality currently available for raster and vector layers from the context menu.

* Requirements: familiar with Python
* Project length: 175 or 350 hours
* Mentor: Martin Landa
* Co-mentor: Anna Petrasova
* Proposed by: Martin Landa
* Rating: medium
* Expected Outcomes: 175 hours basic support for space-time raster datasets; 350 extended support also for other space-time datasets types (vector, 3D raster)
* Test of skills:
** suggest/implement solution for completing https://github.com/OSGeo/grass/issues/2599

=== Add {your research idea} to GRASS GIS ===

* In general, you can propose any topic, but you can specifically propose integrating your research or research idea into GRASS GIS.
* Requirements:
** Language:
*** Depends on the project, often Python, sometimes C.
*** Adding your latest ecological analysis
** Proposal:
*** Discuss relevance to GRASS GIS.
*** Describe technical steps needed for integration.
*** Describe whether it is an addition of a tool (module) or a change in one of the libraries. If it is a tool, specify if it should be included in the core grass repository or in grass-addons repository and why.
*** Specify what research was done and what needs to be accomplished in order to have usable product at the end of summer.
*** Specify who will provide the research expertise.
* Project length: 175 or 350 hours (take your pick)
* Rating: from low to hard
* Mentors:
** GRASS GIS project will provide technical mentors, but it is up to the applicant to ensure the research part is mentored well. An exception may be granted to applicants which can demonstrate that the research is finished or that they have enough expertise themselves.
** Possible technical mentors: Vaclav Petras, Anna Petrasova
** Research mentors: Bring in an expert from your field, e.g., your academic advisor or project principal investigator (if needed).
* Proposed by: Vaclav Petras
* Expected outcome: Working feature which is integrated and merged at the end of the project.
* Test and training tasks:
** Create a test in Python for an existing tool in the grass-addons repository or in the core grass repository.

=== Title of idea ===

Description here

* Requirements:
* Project length: (175 or 350 hours)
* Mentor:
* Proposed by:
* Rating:
* Expected Outcomes:
* Test of skills:
* Other:

== Tips for students ==
* Follow official [https://github.com/numfocus/gsoc/blob/master/CONTRIBUTING-contributors.md NumFOCUS guidelines].
* Include "GRASS" in the title of our idea to easily distinguish ideas and projects inside NumFOCUS.
* If you have your own ideas we encourage you to propose them. Explain them on the [https://discourse.osgeo.org/c/grass/developer/61 on our Discourse].
* Follow some good practices in your ideas and proposals:
** Stress why the project would be useful.
** Show that you know how you will proceed. That is, make sure that you can demonstrate that the proposal is feasible in the given time frame.
** Be specific in the implementation (or at least as specific as you can).
** Explain what the final product will look like and how it will work. You can add drawings or mock-ups.
** Explain how the idea relates to existing GRASS functions, features, and needs.
** Do not include steps such as "install GRASS", "compile GRASS libraries (on my machine)", "read about the API". You should do this before applying to GSoC.
* Compile GRASS from source and prepare environment for development:
** Read [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md CONTRIBUTING file].
* Prove your worth by being active on the [https://discourse.osgeo.org/c/grass/developer/61 GRASS Discourse] or other channels ([https://github.com/OSGeo/grass/discussions GitHub Discussions], fix some [https://github.com/OSGeo/grass/issues bugs], and/or implement some (smaller) features, or write some (simpler) GRASS module, and post it to mailing list. There's no better way to demonstrate your willingness and abilities. Do this before start you apply to GSoC.
* Also note that fixing existing bugs and/or implementing enhancements will be a part of student evaluation.

{{GSoC}}