GRASS-Wiki - User contributions [en]

Talk:GRASS Developer Summit Raleigh 2025

2025-05-24T18:13:13Z

Cyliang: /* Chung-Yuan Liang */

{{toc|right}}

Quick links: [[GRASS Developer Summit Raleigh 2025|Meeting page]] | [[#Participant_reports|Reports]] | [[GRASS_Developer_Summit_Raleigh_2025#Sponsors|Sponsors]]

== Organizing Team ==

* Initial planning: Vaclav Petras, Anna Petrasova, Veronica Andreo, Corey White, Lois Utt, Sarah White, Doug Newcomb, Huidae Cho, Veronica Andreo ([[GRASS_Developer_Summit_Raleigh_2025#Organizing_Committee|Organizing Committee]])
* Budget: Vaclav Petras, Lois Utt, Anna Petrasova
* Raising support: Helena Mitasova, Vaclav Petras, Anna Petrasova, Michael Barton, Giuseppe Amatulli ([[NSF POSE Project 2023-2025 Timeline|NSF POSE project]] proposal authors)
* Travel: Lois Utt
* Venue: Vaclav Petras, Lois Utt
* Meals: Lois Utt, Sarah White, Vaclav Petras, Corey White, Anna Petrasova
* Agenda: Vaclav Petras, Huidae Cho, Anna Petrasova
* Wiki page: Vaclav Petras, Anna Petrasova
* Swag: Sarah White, Vaclav Petras, Anna Petrasova, Corey White
* Promotion, invitations, and social media: Vaclav Petras, Sarah White, Corey White, John Vogler
* Lightning talks organization: Vaclav Petras, Zachary Arcaro, John Vogler
* Lightning talk speakers: Vaclav Petras (welcome), Markus Metz and Markus Neteler (talk presented by Vaclav Petras), Anna Petrasova, Veronica Andreo, Robert Dzur, Nick Brady, Huidae Cho, Gregory Power, Doug Newcomb, Caitlin Haedrich
* Photography: Caitlin Haedrich, Māris Nartišs, Pratikshya Regmi
* Portrait photography: Riya, Caitlin Haedrich, Natalie Trso

== Detailed Schedule ==

=== Day 1, Monday, May 19 ===

Location: Talley Student Union, 2610 Cates Ave ([https://www.google.com/maps/place/Talley+Student+Union/data=!4m2!3m1!1s0x0:0x38989377c96adef0?sa=X&ved=1t:2428&ictx=111 map])

Room: 5101-Executive Board Room

Highlighted topic: ''Contributing to GRASS. Getting started. Is it easy to contribute?''

{| class="wikitable"
! Time !! Slot !!
|-
| 8:30-9:00 || Breakfast || Catered breakfast on site. Meet people, and plan your personal agenda for the day.
|-
| 9:00-10:00 || Morning opening sessions || What to expect from the event, contributing to GRASS using Git and GitHub, making your first contribution.
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || i.hyper: Integrating Hyperspectral Imagery Processing into GRASS - Alen Mangafić
|-
| 11:20-11:40 || Self-organized feedback sessions ||
|-
| 11:40-12:00 || Self-organized feedback sessions || Project Image - Vaclav Petras
|-
| 12:00-13:00 || Lunch || Catered food on site.
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || We will walk to [https://www.trophybrewing.com/brewing-pizza Trophy Brewing & Pizza] ([https://maps.app.goo.gl/ggnZ7EvXbWqDUmvP9 directions], 30 min walk from Talley)
|}

=== Day 2, Tuesday, May 20 ===

Location: Talley Student Union, 2610 Cates Ave ([https://www.google.com/maps/place/Talley+Student+Union/data=!4m2!3m1!1s0x0:0x38989377c96adef0?sa=X&ved=1t:2428&ictx=111 map])

Room: 5101-Executive Board Room

Highlighted topics: ''Hydrology and Interfacing with R and QGIS (gathering user feedback, testing, discussing with developers, developing action items)''

{| class="wikitable"
! Time !! Slot !!
|-
| 8:30-9:00 || Breakfast || Breakfast on site. Start the day, meet people, and plan your personal agenda for the day.
|-
| 9:00-10:00 || Morning opening sessions || Introduction to writing GRASS tools, program for the day.
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || fasterRaster R package - Adam Smith
|-
| 11:20-11:40 || Self-organized feedback sessions || Hydography90m + Geocomputation Courses - Giuseppe
|-
| 11:40-12:00 || Self-organized feedback sessions || Flood modelling with grass and itzi ([https://itzi.org]) - Laurent Courty
|-
| 12:00-13:00 || Lunch || [https://maps.app.goo.gl/womSkce9DrE8CTnR8 Case dining hall]
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || [https://maps.app.goo.gl/CQiWoCAQNt1ymZkb7 Served in Jordan Hall at the Center for Geospatial Analytics], evaluate the day's accomplishments, plan and prioritize for the next few days.
|}

=== Day 3, Wednesday, May 21 ===

Location: Talley Student Union, 2610 Cates Ave ([https://www.google.com/maps/place/Talley+Student+Union/data=!4m2!3m1!1s0x0:0x38989377c96adef0?sa=X&ved=1t:2428&ictx=111 map])

Room: 5101-Executive Board Room

Highlighted topic: ''Non-coding contributions, natural language translation, and internationalization.''

{| class="wikitable"
! Time !! Slot !!
|-
| 7:00-9:00 || Breakfast || [https://maps.app.goo.gl/eZ8VK8Mx6TjMt9NP8 Case dining hall]
|-
| 9:00-10:00 || Morning opening sessions || Introduction to non-coding contributions, tutorials, contributing examples, natural language translation and internationalization (procedures, glossaries, code customization, translation).
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || Easier access to GRASS tools - Vaclav Petras
|-
| 11:20-11:40 || Self-organized feedback sessions ||
|-
| 11:40-12:00 || Self-organized feedback sessions || GRASS backend for xarray and temporal framework global variables ([https://github.com/OSGeo/grass/issues/629]) - Laurent Courty
|-
| 12:00-13:00 || Lunch || Served on site. Eat, drink, and continue the discussion from the feedback sessions.
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || [https://maps.app.goo.gl/1E39eySMVaxYJUUS8 Picnic at Pullen Park, shelter #3. In case of bad weather, dinner at the Center for Geospatial Analytics.
|}

=== Day 4, Thursday, May 22 ===

Location: Center for Geospatial Analytics, Jordan Hall, 2800 Faucette Drive ([https://www.google.com/maps/search/Jordan+Hall/@35.7816832,-78.6772765,18z/data=!3m1!4b1?entry=ttu&g_ep=EgoyMDI1MDQyMC4wIKXMDSoJLDEwMjExNDUzSAFQAw%3D%3D map])

Room: 5103 (straight from the two elevators, at the end of the hallway)

Highlighted topic: ''Project vision and computational engine use case.''

{| class="wikitable"
! Time !! Slot !!
|-
| 8:00-9:00 || Breakfast || On site. Start the day, meet people, and plan your personal agenda for the day.
|-
| 9:00-10:00 || Morning opening sessions || Project vision and the computational engine use case (missing features, documentation, user groups).
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || NSF POSE I-Corps Interviews - Corey White
|-
| 11:20-11:40 || Self-organized feedback session || YAIT - Yet Another Interface to Tools - Vaclav Petras
|-
| 11:40-12:00 || Self-organized feedback session || Modernizing Color Tables (Brendan)
|-
| 12:00-13:00 || Lunch || On site. Eat, drink, and continue the discussion from the feedback sessions.
|-
| 13:00-16:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 16:00-17:00 || Lightning talks || Fast-paced talks, showcasing applications of GRASS, room 5111.
|-
| 18:00 || Reception || Connect with researchers, government professionals, and industry collaborators, rooms 5111 and 5119.
|}

=== Day 5, Friday, May 23 ===

Location: James B. Hunt Jr. Library, 1070 Partners Way - Centennial Campus ([https://www.google.com/maps/place/James+B.+Hunt+Jr.+Library/@35.7693736,-78.679167,17z/data=!3m1!5s0x89acf5759f5a31df:0xc547454a0151c440!4m10!1m2!2m1!1shunt+library!3m6!1s0x89acf5759f591f41:0xbe0266269ce37f59!8m2!3d35.7693215!4d-78.6764409!15sCgxodW50IGxpYnJhcnlaDiIMaHVudCBsaWJyYXJ5kgESdW5pdmVyc2l0eV9saWJyYXJ54AEA!16s%2Fm%2F0r4wjf_?entry=ttu&g_ep=EgoyMDI1MDQyMC4wIKXMDSoJLDEwMjExNDUzSAFQAw%3D%3D map])

Room: Faculty Research Commons - 5100 ([https://www.lib.ncsu.edu/hunt/map floor plan])

Highlighted topic: ''GRASS project's future course.''

{| class="wikitable"
! Time !! Slot !!
|-
| 7:45-8:15 || Breakfast || '''Hotel Aloft (2nd floor).''' Search for Lois!
|-
| 9:00-10:00 || Morning opening sessions || GRASS project's future course.
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-12:00 || PSC meeting || Project Steering Committee meets (public).
|-
| 11:00-11:20 || Self-organized feedback session || Your topic here
|-
| 11:20-11:40 || Self-organized feedback sessions || Your topic here
|-
| 11:40-12:00 || Self-organized feedback sessions || Rescheduled for Saturday

|-
| 12:00-13:00 || Lunch || Walk to [https://maps.app.goo.gl/kHVHY62QxTd6wHKd9 On the Oval Culinary Creations]. Eat, drink, and continue the discussion from the feedback sessions.
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || Dinner on your own. Corey White will organize trip to downtown. Bus 41 from Hunt library to hotel and then walk.
|}

=== Day 6, Saturday, May 24 ===

Location: James B. Hunt Jr. Library, 1070 Partners Way - Centennial Campus ([https://www.google.com/maps/place/James+B.+Hunt+Jr.+Library/@35.7693736,-78.679167,17z/data=!3m1!5s0x89acf5759f5a31df:0xc547454a0151c440!4m10!1m2!2m1!1shunt+library!3m6!1s0x89acf5759f591f41:0xbe0266269ce37f59!8m2!3d35.7693215!4d-78.6764409!15sCgxodW50IGxpYnJhcnlaDiIMaHVudCBsaWJyYXJ5kgESdW5pdmVyc2l0eV9saWJyYXJ54AEA!16s%2Fm%2F0r4wjf_?entry=ttu&g_ep=EgoyMDI1MDQyMC4wIKXMDSoJLDEwMjExNDUzSAFQAw%3D%3D map])

'''Take bus 41 at 8.30 from Aloft.'''

Room: Faculty Research Commons - 5100 ([https://www.lib.ncsu.edu/hunt/map floor plan])

Highlighted topics: ''NSF POSE project evaluation.''

{| class="wikitable"
! Time !! Slot !!
|-
| 8:30-10:00 || Breakfast || We will have breakfast (yogurt, granola, pastries) at [https://maps.app.goo.gl/EwzNxeovv4rTivjK9 Lake Raleigh]. Feel free to bring your own coffee.
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || Your topic here (10-minute presentation and 10-minute discussion)
|-
| 11:20-11:40 || Self-organized feedback sessions || Your topic here
|-
| 11:40-12:00 || Self-organized feedback sessions || GRASS tools: core and additional functionality (MartinL)
|-
| 12:00-13:00 || Lunch || Pizza. Eat, drink, and continue the discussion from the feedback sessions.
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || Player's Retreat.
|}

== Daily tasks for participants ==

* List all the things you are working on in the Participant reports section below. Update the list each day. Include things you work on with other people.
* If you want to discuss something with the whole group, add yourself to a Self-organized feedback sessions slot in the schedule above or tell Vaclav (Vashek) Petras.
* For people with triage access and above: 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.)

== Participant reports ==

Per-person reports from the meeting.

=== Giuseppe Amatulli | Yale University ===

* Testing r.watershed and r.stream.* for handling large datasets
* Running r.flowaccumulation at global level using water direction from hydrography90m
* Preparing the grass tutorial material for the https://www.geomorphometry2025.org/ conference

=== Veronica Andreo | CONICET - Instituto Gulich ===

* [https://github.com/veroandreo?tab=overview&from=2025-05-12&to=2025-05-24 GitHub contributions]
* Enhanced the website footer.
* Sync icons on the Tutorials website footer to those on the main website.
* Fix descriptions and their display on the tutorials website.
* Fix GRASS page on OSGeo website [https://www.osgeo.org/projects/grass-gis/]
** Changed logo, removed GIS from the name, fixed old links.
* Social media posts.
* Discussion about hyperspectral with Alen and Anna.
* Expand the GRASS acronym on the home page.
* Remove GIS from GRASS name on the website.
* Review tutorials by Huidae and Adam Smith.
* Add external tutorials by Huidae and the one from FOSS4G 2024.
* Started adding the time series tutorials.
* Add lightbox class in get-started tutorials so images can be clicked on.
* GRASS PSC admin stuff.
* Participated of the PSC meeting.
* Talk to Tonis Kardi from FOSS4G EU LOC to have a "State of GRASS" talk in the program. Alen will be presenting.
* Gave a lightning talk: GRASS-fed species distribution models.
* Discussed with Brendan, Corey and Mimi about tutorials.

=== Abdullah Azzam | New Mexico State University ===

* Created first PR; fixed broken links on the website [https://github.com/OSGeo/grass-website/pull/538 #538]
* Pushed a new GRASS Addon ''r.curvenumber'' [https://github.com/OSGeo/grass-addons/pull/1403 #1403]

=== Michael Barton | Arizona State University ===

* POSE related activities

=== Laura Belica | NC State University ===

* have been working on developing a workflow-tool tutorial template that facilitates GRASS learners who tend to 'jump in' or have a 'choose your own adventure' approach to learning GRASS (i.e., want to use their data for their study area for their objective from the start). The structure of the tutorial template is a concise, basic, general description/instructions of the workflow with optional links to pertinent explanatory/deeper dive content (e.g., plain language explainers of the tool, options, defaults, etc.) in a variety of formats (e.g., captioned images, short tool demo videos (30 sec to 2 min)) in addition to the more comprehensive resources available (e.g. documentation, examples, tutorials). The main motivation for this approach is to help new and occasional GRASS users avoid some of the common pitfalls and to learn how to find workarounds for some of the unanticipated challenges they may encounter with their specific datasets or use cases so that they can learn as they go. Another motivation for this approach is to facilitate the translation, extension, and updating of workflow tutorials by the community over time (e.g., providing audio and closed captioning for one of the tool-demo videos in another language, replacing an outdated GUI demo with one for the current release, or incorporating a new add-on as an option in the workflow).

* my focus this week is on developing a draft/test tutorial (in Quarto) for a standard hydrological modelling workflow that begins with the crucial pre-work of how to figure out the appropriate project/location, etc. as well as considerations of some of the downstream impacts of resolution, extent, region etc. It may not be ready for sharing by the end of the week, but suggestions and advice are welcomed in advance.

19 May
* discussed a novice user issue with 'moving' vector data from one location to another with Vero and learned a neat GUI option
* revised and added workflow tutorial text

=== Shonil Sateesh Bhide | NC State University ===

* CI optimization

=== Huidae Cho | New Mexico State University ===

* CMake, conda, CI, Mentoring

Monday 5/19
* [https://github.com/OSGeo/grass/pull/5680 CMake: Recognize conda installation path at runtime]: Replaced by [https://github.com/HuidaeCho/grass-conda/blob/master/recipe/post-link.sh conda post-link.sh]
* CMake and Conda Testing on Linux
* CMake Testing on Windows
* Mentoring: Chung-Yuan, Abdullah

Tuesday 5/20
* [https://github.com/OSGeo/grass/pull/5712 CMake: Define custom complex types for MSVC LAPACKE]
* [https://github.com/OSGeo/grass/pull/5713 CMake: Fix build output directories for MSVC]
* CMake and Conda Testing on Linux
* CMake Testing on Windows

Wednesday 5/21
* Translation Talk
* Translation Discussion with Edouard
* Flow Direction Meeting with Ondrej, Ondrej's Student, Martin, and Markus Metz
* CMake and Conda Testing on Linux
* CMake Testing on Windows
* Mentoring: Chung-Yuan, Abdullah

Thursday 5/22
* [https://github.com/OSGeo/grass/pull/5740 CMake: Fix the parameter is incorrect: . error for MSVC]
* Lightning Talk
* CMake and Conda Testing on Linux
* CMake Testing on Windows
* CI: Discussion with Edouard
* Mentoring: Chung-Yuan, Abdullah

=== Edouard Choinière ===

* Quick ideas, way too much for a week: Helping others (may take a reasonable part of the time), managing CI, setting up localization template updating workflow, backporting tool? Pytest/coverage improvements? Discuss and design other projects, to work on during the year. Open to change on other priorities once there, anything that is useful. Maybe make a little progress on high dpi GUI, especially on Windows.

* Weekend before sprint:
** Clear up Renovate PRs to not use CI time during the sprint, reviewing and merging: [https://github.com/OSGeo/grass/pull/5664 #5664], [https://github.com/OSGeo/grass/pull/5665 #5665], [https://github.com/OSGeo/grass/pull/5666 #5666], [https://github.com/OSGeo/grass/pull/5667 #5667], [https://github.com/OSGeo/grass/pull/5668 #5668]
** PR to avoid some CI run time for the sprint: [https://github.com/OSGeo/grass/pull/5670 #5670]
** Reviewed open PRs for PRs that were mergeable before the sprint, updated outdated PRs to avoid having it needing CI time during sprint. Only ended up merging [https://github.com/OSGeo/grass/pull/5658 #5658], but another reviewed one that might still need changes: [https://github.com/OSGeo/grass/pull/5628 #5628]
* Monday May 19, 2025:
** PR got merged: [https://github.com/OSGeo/grass/pull/5670 #5670],[https://github.com/OSGeo/grass/pull/5550 #5550]
** Reviewed PRs: [https://github.com/OSGeo/grass/pull/5671 #5671], [https://github.com/OSGeo/grass/pull/5672 #5672]
** Discussions:
*** Shonil Sateesh Bhid & Shuham on their CI & pytest work and project.
*** Māris Nartišs about a potential issue and improvement for it. Will be discussed in the security reporting tab, also allowing to test the security vulnerability reporting process. + Research on existing solutions
** Reviewed: [https://github.com/OSGeo/grass/pull/5682 #5682], [https://github.com/OSGeo/grass/pull/5660 #5660],
** Reviewed, edited and merged: [https://github.com/OSGeo/grass/pull/3672 #3672]
** Discussed/helped user for: [https://github.com/OSGeo/grass/pull/5678 #5678] and [https://github.com/OSGeo/grass/pull/5684 #5684]
** Long discussion and vision planning for windows scripting with Vaclav, concerning [https://github.com/OSGeo/grass/pull/5624 #5624]. Tested alternatives and tried the consequences of that PR. This older PR finally got merged.
** Created PRs for NSIS installer: [https://github.com/OSGeo/grass/pull/5685 #5685] and also [https://github.com/OSGeo/grass/pull/5686 #5686], which should address [https://github.com/OSGeo/grass/issues/5663 #5663]. Still needs to test it.
** Agreed on convention for titles with Vaclav, unblocking [https://github.com/OSGeo/grass/pull/5341 #5341]
** Found a name with Ondrej and finally merged older PRs of an external contributor [https://github.com/OSGeo/grass/pull/5473 #5473] and [https://github.com/OSGeo/grass/pull/5474 #5474]
* Thursday May 20, 2025:
** Reviewed: [https://github.com/OSGeo/grass/pull/5695 #5695]
** Merged PRs: [https://github.com/OSGeo/grass/pull/5673 #5673], [https://github.com/OSGeo/grass/pull/5691 #5691], [https://github.com/OSGeo/grass/pull/5690 #5690], [https://github.com/OSGeo/grass/pull/5684 #5684],
** Discussed with author of [https://github.com/OSGeo/grass/pull/5660 #5660] and [https://github.com/OSGeo/grass/issues/5659 #5659] about rgb/hsl bug and tests for help.
** Worked with Corey to adjust markdown links for new markdownlint rule, finishing up [https://github.com/OSGeo/grass/pull/5669 #5669]
** Created PRs: [https://github.com/OSGeo/grass/pull/5692 #5692], [https://github.com/OSGeo/grass/pull/5694 #5694], [https://github.com/OSGeo/grass/pull/5689 #5689]
* Wednesday May 21, 2025:
** Created a new set of GitHub rulesets for the required checks, applied with Vaclav. One of them is separated in order to increase velocity during the sprint
** Reviewed the branch protection rules for grass-addons repo with Vaclav. Creating rulesets will be possible after the sprint with the info collected.
** Reviewed the security reporting settings and secret scanning settings with Vaclav for the main grass repo.
** Got shown by Huidae Cho how to update the translation files, and reviewed Weblate settings. No settings changed, but a backup stored for 30 days was kept.
** Created a first implementation of a translation file update workflow
** Tested out the two NSIS installer PRs, the first one, for installing the VC runtime earlier doesn't work as expected, and after more research I don't know enough to fix it. The second PR with High-DPI improvement was correct and got merged [https://github.com/OSGeo/grass/pull/5685 #5685]
** Helped a student set up a grass installation on WSL with conda.
** PRs created: [https://github.com/OSGeo/grass/pull/5736 #5736], [https://github.com/OSGeo/grass/pull/5734 #5734]
** My PRs that got merged: [https://github.com/OSGeo/grass/pull/5685 #5685], [https://github.com/OSGeo/grass/pull/5341 #5341], [https://github.com/OSGeo/grass/pull/5689 #5689]
** Reviewed and merged multiple PRs, restarting failed required checks of the previous night.

=== Laurent Courty ===

* Objectives: An xarray backend for GRASS STRDS. Fixing related issues
* May 20
** Presented itzi
** Uploaded arm64 wheels to PyPI for MacOS and Linux ([https://pypi.org/project/itzi/#files])
** Discussed with other developers about issue #629
* May 21
** Uploaded xarray-grass to PyPI
** Added CI tests to xarray-grass
** Discussed with the group about the xarray-grass backend
** Discussed with the group about solving mapset switching in the temporal framework (issue #629)
** Created PR #5735 to address issue #629
* May 22
** Fix bug in PR #5735

=== Robert S. Dzur | Bohannan Huston, Inc. ===

* r.in.pdal

=== David W. Farris | East Carolina University ===

* A tool to calculate gravity terrain corrections

=== Neel Ghoshal | NC State University ===
• LLM for helping users find tools 
5/19 
• Learnt how to PR (#5674) 
• Setup GRASS on system 
• Found small issue with compilation document 
• Discussed about the possible use case of LLM for helping users find tools 
5/20 
• Learnt about cookie cutter 
• Set up wsl on system 
• Compiled GRASS 
• Listed data sources for LLM training 
5/21 
• Extracted tool information from Markdown files 
• Started off with data cleaning 
5/22 
• Worked on LLM setup 
5/23 
• Ran and finetuned a basic test LLM model for extracted data 

=== Caitlin Haedrich | NC State University ===

* Event photographs, food coordination
* git/github mentoring
* GRASS mentoring
* Lightning Talk preparation
* Preparing workshop for [https://www.geomorphometry2025.org/ Geomorphometry2025]

=== Brendan Harmon | Louisiana State University ===

* Developing ([https://github.com/baharmon/r.earthworks r.earthworks]) addon & tutorials
* [https://github.com/baharmon?tab=overview&from=2025-05-19&to=2025-05-24 GitHub activity]

=== Linda Karlovska | Czech Technical University in Prague ===

* Fix uninitialized variables in DOutFile() method: ([https://github.com/OSGeo/grass/pull/5650 PR])
* Update figures related to GUI: ([https://github.com/OSGeo/grass/pull/5651 PR])

Working on integration of the Jupyter notebooks to GUI (work for the whole week :-))

=== Martin Landa | Czech Technical University in Prague ===

* Tutorial: GISMentors courses updated ([https://github.com/OSGeo/grass-tutorials/pull/45 PR])
* libgis: G__usage_markdown() include tool label in metadata if defined ([https://github.com/OSGeo/grass/pull/5677 PR])
* PyGRASS: Module description property not defined always ([https://github.com/OSGeo/grass/pull/5681 PR])
* Website: OpenGeoLabs commercial support ([https://github.com/OSGeo/grass-website/pull/537 PR])
* v.select: create output also when no features found ([https://github.com/OSGeo/grass/pull/5696 PR])
* wxGUI: avoid creating nested list of errors (Graphical modeler) ([https://github.com/OSGeo/grass/pull/5700 PR])
* wxGUI/gmodeler: refactor - move ModelParamDialog to dialogs.py ([https://github.com/OSGeo/grass/pull/5715 PR])
* GUI: make Python editor dockable ([https://github.com/OSGeo/grass/pull/5733 PR])
* r.relief: module label changed to description ([https://github.com/OSGeo/grass/pull/5741 PR])
* GUI: propagate previously defined where option value ([https://github.com/OSGeo/grass/pull/5747 PR])
* GUI: always show 'Close dialog on finish' option ([https://github.com/OSGeo/grass/pull/5751 PR])
* GUI: do not remove parameter value on dialog update event ([https://github.com/OSGeo/grass/pull/5760 PR])
* documentation: add miscellaneous tools too full index (markdown) ([https://github.com/OSGeo/grass/pull/5761 PR])

=== Nicklas Larsson | Hungarian National Museum ===

Planned work: CMake build system; perhaps Conda recipe

[https://github.com/nilason?tab=overview&from=2025-05-19&to=2025-05-24 GitHub activity]

* Preparation for CMake build conforming to Filesystem Hierarchy Standard (FHS), resolving resource paths for both the current and FHS in code. In collaboration with Huidae Cho and with important input from Vaclav Petras ([https://github.com/OSGeo/grass/pull/5630 PR5630])

* Helped young students in build configuration and debugging techniques.

* Discussion with several participants on solutions to publish a GRASS package to Conda-forge.

=== Chung-Yuan Liang ===

* r.horizon
** [https://github.com/OSGeo/grass/pull/4213 PR4213]
** Discussed with Vashek, Anna, and Huidae regarding parallelization performance.
* r.mapcalc
** [https://github.com/OSGeo/grass/pull/5742 PR5742]
** Parallelized a part of r.mapcalc.
** Discussed with Anna and Huidae how to improve the parallelization.
** More work is needed for better efficiency for threads > 4.
* r.univar
** [https://github.com/OSGeo/grass/pull/5748 PR5748], [https://github.com/OSGeo/grass/pull/5750 PR5750]
** Created a test for large data and parallel computations.
** Applied Kahan sum to avoid accumulations of floating point errors.
** Update reference numbers in other testing scripts that use r.univar.
* Discussing how to improve I/O and memory buffers for raster data in the parallelization aspect.

=== Andres Lucero | Bohannan Huston Inc ===

* r.in.pdal

=== Alen Mangafić | Geodetic Institute of Slovenia ===
Monday May 19
* Presentationf of i.hyper, add-on which offers hyperspectral data support in GRASS.
* Architecture of the multi-module addon
Tuesday May 20
* i.hyper.import module: importing EnMAP imagery as 3D raster map
* i.hyper.preproc module: draft
Wednesday May 21
* fixing the i.hyper.import module
* i.hyper.preproc module: implementing Savitzky-Golay filter

=== Helena Mitasova | NC State University ===

* standardized data set and related tutorials
* documentation for interpolation tools
* collaborate/coordinate/discuss hydrology tools (analytics, simulations, soil properties inputs)
* assist with wiki cleanup if needed

Monday May 19
* investigated issues with v.surf.rst documentation in source code, tested and identified fixes needed
* discussed coupling GRASS with Blender versus potree for 3D object rendering with Brendan, Anna and Caitlin (for TL activities and other applications)
* discussed soil data for runoff estimation and other hydro topics, to be worked on on day 2

Tuesday May 20
* worked with Corey on fixing v.surf.rst documentation, discussed ideas for improvements and for documentation / tutorial for cross-valiadation
* discussed suggestions for graphics and examples to be inculded in v.surf.rst docs with Michelle
* discussed new developments in hydrology tools
* experimented with basic/standardized versus specialized data sets for documentation and tutorials

Wednesday May 21
* explored existing tutorials, emailed Paulo about finishing the one on interpolation
* tested NM basic data set with GIS582 class assignment (very cool)
* discussed design of Jnotebooks that would work with various localized data with Caitlin

Thursday May 22
* discussed needed capabilities for a more advanced color ramp processing tool with Brendan
* added further ideas to basic dataset document after talking to Vero - we just need standardized names for the localized tutorials to work
* discussed infiltration fix pull request for r.sim.water with Anna - more work is needed

=== Michael Mulqueen | MassGIS ===

* depth to water, hydro from lidar, etc

=== Māris Nartišs ===

* Taking photos of the event
* Introduced a new GRASS core module r.smooth.edgepreserve
* Discussed architecture of hyperspectral data import and per-processing tool
* Discussed testing and organizing AI modules downloading data from internet
* Prepared and gave a presentation on code preparation for translations (best practice)
* Debugging translation file updating with Edouard
* Changed default multiprocessor setting to always use maximum number of available threads
* Unified max process setting handling in all modules that use default parser parameter
* Discovered and supervised fixing a bug in r.univar parallelization code
* Discussed requirements for raster data reading parallelization (GRASS 9)
* Discussed future features to be implemented (long term view)

=== Ondřej Pešek | Czech Technical University in Prague ===

* [https://github.com/pesekon2?tab=overview&from=2025-05-19&to=2025-05-24 GitHub activity]
* Refactoring, fixing, improving, discussing g.gui.gmodeler
* Discussing hyperspectral with Alen Mangafic
* Discussing jupyter in single GUI with Linda Karlovska
* PyGRASS
* Docs
* CQ
* Reviewing PRs, PR archeology

=== Vaclav (Vashek) Petras | NC State University ===

* [https://github.com/wenzeslaus?tab=overview&from=2025-05-19&to=2025-05-24 GitHub activity]
* My focus: Getting feedback and ideas for computational engine use case, APIs, funding.
* Summit organizing
* Implementing rebranding on GitHub (repos, teams)
* Feedback session on project image
* Feedback session on easier access to tools
* Discussed LLMs with Neel Ghoshal, Riya
* Discussed session setupp Martin Landa
* Discussed conda with Nicklas Larsson
* Discussed hyperspectral with Alen Mangafić, Veronica Andreo, and Anna Petrasova
* Discussed code for new smoothing tool, integer overflows, translations with Māris Nartišs
* Compared setup of GRASS session and project in fasterRaster, QGIS, and GRASS itself with Adam Smith
* Discussed potential of Pixi for packaging or compilation with Gregory Power
* Discussed itzi model distribution issues with Laurent Courty
* Discussed r.horizon parallelization with Chung-Yuan Liang and Anna Petrasova
* Answered coding and setup questions for Neel Ghoshal, Abdullah Azzam, and Alen Mangafić

=== Anna Petrasova | NC State University ===

* [https://github.com/petrasovaa?tab=overview&from=2025-05-19&to=2025-05-24 GitHub activity]
* plan: mentoring, documentation
* Monday
** discussing hyperspectral implementation with Alen
** helping mentee David Farris implementing his gravity correction addon
* Tuesday
** delivered intro to creating an addon, documentation
** mentoring Alen, Abdullah
** discussing bug in i.his.rgb with Jayneel
** reviews
* Wednesday
** discuss and demonstrate tutorials page
** mentoring Alen, Jayneel
** call with GSoC student
* Thursday
** lightning talk
** discussing openmp implementations for r.horizon, r.mapcalc, default thread number
* Friday
** grass repo README
** reviews

=== Gregory Power | Town of Cary ===

* Documentation

=== Pratikshya Regmi | NC State University ===

* Event photographs and videos
* Opened a pull request to change GRASS GIS to GRASS on the documentation (this was my first contribution to GRASS)
* Worked on preparing the mock document for LLM RAG
* Wrote a tutorial to Visualize Contour Lines with a Color Gradient with Folium.
* Finished mockup document and testing on LLM.

=== Riya | Indian Institute of Technology, Roorkee ===

* I am currently thinking of developing an AI Agent for the grass jupyter library which will help the users with mathematical calculations done in GIS.

=== Jayneel Shah | NC State University ===

* improve the test coverage of imagery modules.

=== Krishna Prasad Sheshadri ===

*

=== Adam Smith | Missouri Botanical Garden ===

Overall: R package fasterRaster (fielding bug reports, adding features)

Monday:
* Assessed scope of fasterRaster issue [https://github.com/adamlilith/fasterRaster/issues/83 83]

Tuesday:
* Created a PR for fasterRaster tutorial on GRASS tutorials page.
* Improved handling of addons, including autodetect and installing when needed, enabling easier creation of addon-dependent methods.
* Presented *fasterRaster* package to group.

Wednesday:
* Created fasterRaster methods for neighborhood matrices, terrain ruggedness index, and multivariate environmental similarity

=== Michelle (Mimi) Stephens | ERDC ===

* Previous work: coupling R and Python scripts for computational analysis in GRASS.
* Current work: Running through GRASS commands to create visual outputs that can be added to the new GRASS 8.5 manual pages - r.mapcalc, v.surf.rst, examples with topographic parameters, LinkedIn requests.
* Tutorial for Windows users to install a WSL2 Linux environment. Creates a conda environment with wxpython, installs GRASS without requiring OSGeo installer. Fast, simple, and minimal install. Resolves various issues encountered in government due to automatic Windows updates, cyber security, vpn routing, user preference, and isolated distro can be completely removed if needed. -> Motivation for WSL2 - wanted more hands-on practice with Unix command line tools for HPC; Docker not allowed, but miniforge and Apptainer are on ERDC's HPC; able to install grass via command line (only on internet-capable HPC systems); AND - For other users that always wanted a more native feel to their grass instance!
* Future work: Presenting on GRASS in JUNE at CERLCON.

=== Corey White | NC State University ===

* JSON, mentoring

=== Doug Newcomb | Semi Retired Cartographer ===

* Discussed hydroflattening method
* Discussed direct point cloud input to v.surf.rst
* Learning git procedures by updating branding (GRASS GIS to GRASS) for raster commands
Tuesday
* Continued updating branding for raster commands
* Started working on tutorial for r.hydro.flatten
Wednesday
* Finalized Data set for for r.hydro.flatten
* Worked on Lightning Talk for Thursday
Thursday
* Continued work on r.hydro.flatten tutorial
* Gave lightning talk on r.hydro.flatten
Friday
* Worked with Rob Dzur on r.hydro.flatten workflow.
* Explored the possibility of using r.resample.bspline for areas with high standard deviation ranges.

* Worked with Rob Dzur on identifying workflow for implimenting USGS GMI, https://www.usgs.gov/ngp-standards-and-specifications/elevation-derived-hydrography-data-acquisition-specifications-16 , in GRASS and connected Rob with USGS contact for GMI.

=== Natalie Trso | Balance Geo LLC ===

* r.sim.water

== Guests and remote participants ==

=== Luís de Sousa | University of Lisbon ===

* Review outstanding PRs
* Prepare GRASS sessions for the OpenGeoHub Summer School

=== Markus Neteler | mundialis ===

* Support full automation of new GRASS manual pages deployment on server (upload artifacts from GitHub to OSGeo servers (grass and download))
* Source code license documentation: Using SPDX License IDs ({{GH-Issues|4190}})
* Support Wiki cleanup
* [https://github.com/neteler?tab=overview&from=2025-05-19&to=2025-05-24 GitHub contributions]

=== Nishant Bansal | Indian Institute of Technology, Varanasi ===

* Review the previous work on JSON during last year’s GSoC, including enhancements and the addition of JSON output support to other modules.

Talk:GRASS Community Meeting Prague 2024

2024-06-19T12:58:18Z

Cyliang: /* Chung-Yuan Liang */

{{toc|right}}

Quick links: [[GRASS Community Meeting Prague 2024|Meeting page]] | [[#Reports|Reports]] | [[GRASS_Community_Meeting_Prague_2024#Sponsors|Sponsors]]

== Organizing Team ==

* Initial planning: Vaclav Petras, Veronica Andreo, Markus Neteler, Anna Petrasova, Martin Landa, Helmut Kudrnovsky, Helena Mitasova
* Budget: Vaclav Petras, Anna Petrasova, Markus Neteler, Veronica Andreo, Helena Mitasova
* Raising support: Vaclav Petras, Veronica Andreo, Markus Neteler, Helmut Kudrnovsky, Anna Petrasova
* Reimbursements: Vaclav Petras
* Venue: Vaclav Petras
* Meals: Caitlin Haedrich, Alen Mangafić, Martin Landa, Anna Petrasova, Vaclav Petras, Ondrej Pesek, Veronica Andreo
* Agenda: Veronica Andreo, Anna Petrasova
* Wiki page: Vaclav Petras, Veronica Andreo, Martin Landa
* Virtual participant support: Veronica Andreo
* T-shirts, hoodies, stickers: Vaclav Petras, Veronica Andreo
* Promotion, invitations, and social media: Caitlin Haedrich, Veronica Andreo, Vaclav Petras
* Photography: Caitlin Haedrich, Helmut Kudrnovsky

== Tasks for participants ==

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

== Reports ==

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

=== Floris Vanderhaeghe ===

* Make maintenance pull requests [https://github.com/rsbivand/rgrass/pull/90 PR #90] and [https://github.com/rsbivand/rgrass/pull/91 PR #91] to support future contributors of the [https://github.com/rsbivand/rgrass R package rgrass].
* Test the standalone GDAL-GRASS driver in R and create issues [https://github.com/OSGeo/gdal-grass/issues/46 #46], [https://github.com/OSGeo/gdal-grass/issues/47 #47], [https://github.com/OSGeo/gdal-grass/issues/48 #48] and [https://github.com/OSGeo/gdal-grass/issues/49 #49] in its code repository, with help of Markus Neteler.
* Implement the GDAL-GRASS driver in the <code>read_VECT()</code> function of [https://github.com/rsbivand/rgrass R package rgrass], as well as some associated enhancements. See [https://github.com/rsbivand/rgrass/pull/93 PR #93].
* Make an [https://github.com/rsbivand/rgrass/issues/92 issue], with the help of Helmut Kudrnovsky and Veronica Andreo, about launching R in the OSGeo4W shell independently of GRASS GIS.
* Help sorting out a few issues in the [https://github.com/rsbivand/rgrass repository of R package rgrass].
* Point at the PROJJSON specification in support of GRASS GIS issue [https://github.com/OSGeo/grass/issues/3020 #3020].
* Participate in the GRASS GIS roadmap discussion on Saturday.
* Participate in the discussion on interfacing GRASS GIS from QGIS. See [https://github.com/OSGeo/grass/discussions/3898 meeting minutes].

=== Markus Neteler ===

* cleanup labels in GitHub repo
* replace --tmp-location with --tmp-project (pull requests [https://github.com/OSGeo/grass/pull/3825 PR #3825], [https://github.com/OSGeo/grass/pull/3822 PR #3822])
* docker: remove "grass-session" pip approach, replace to new build-in Python API (pull request [https://github.com/OSGeo/grass/pull/3819 PR #3819])
* Participated in the PSC meeting to define elections date and other elections related issues. See [[PSC_Meeting_2024-06-14]].
* Discussion about our Dockerfiles
* Simplified examples for working with GRASS 8.4+ in Python (update [https://gis.stackexchange.com/a/457875/687 Stackexchange posts])
* Participated of the roadmap discussion session
* cleanup of many pull request titles to be recognized by https://github.com/OSGeo/grass/blob/main/utils/release.yml
* Complete OpenSSF Best Practices badge questionnaire to 100%: https://www.bestpractices.dev/en/projects/2470
* backport plenty of pull requests to GRASS GIS 8.4 release branch
* lib/gis: modernize getl2() https://github.com/OSGeo/grass/pull/3850
* social media outreach: suggest use of Publer.io to easier feed our channels (discuss with Vero and Caitlin)
* work on 8.4.0RC1, together with Vaclav, see https://github.com/OSGeo/grass/releases
* Participation in QGIS-GRASS session with Nyall Dawson
* Worked with Vero on the highlights for the 8.4.0RC1 release notes.
* Updated hugo version on the website, see also [https://github.com/OSGeo/grass-website/pull/438 PR]

=== Veronica Andreo ===

* Discuss tutorial topics with Alen
* Reviewed and tested contributions by the Google Summer of Code student working on EODAG integration.
* Reviewed other PRs: temporal framework, tutorial on GRASS usage within Jupyter on Windows, t.stac, among others.
* Participated in the PSC meeting to define elections date and other elections related issues. See [[PSC_Meeting_2024-06-14]].
* Compiled the raw list of contributors since Dec 2020, to create the list of voters, as discussed in PSC meeting.
* Set up a swag shop in RedBubble and added designs with color and white logos. Yet not published as payment details need to be configured with OSGeo treasurer.
* Participated of the roadmap discussion session - Roadmap will be published in the website.
* Participated of the documentation discussion session.
* Participated of the call with Nyall Dawson about improving GRASS-QGIS integration.
* Worked with Markus on the highlights for the RC1 release notes.
* Assisted Caitlin with social media posting, review posts and setting up Publer and Buffer services suggested by Markus to streamline posting in various channels.
* Discussed and tested gdal-grass driver implementation by Floris.
* Went through grass-website issues, closed some, pinged in others and changed hugo version in the website [https://github.com/OSGeo/grass-website/pull/438 PR].
* Reviewed PR and tested the upcoming t.stac tool.

=== Alen Mangafić ===
* Discuss tutorial with Veronica and Vaclav.
* Setting up the environment for the tutorial with Ondřej and Corey, resulting in a process to build a Docker container with the main branch and it's kernel connection to Jupyter Lab.
* Writing a Jupyter Lab framework which works. Helped by Vaclav with locating the "GISENV" location bug.
* Data preparation: correction the point clouds to match correct Global Encoding value of a LAS 1.4 file with PDRF 6 - 10 is 17 (16 + 1); CRS definition.
* Testing and drafting the workflow in GUI.
* Found a and reported a bug about how r.in.pdal handles the number of returns ([https://github.com/OSGeo/grass/issues/3827 #3827]).
* Built a micromamba python environment for grass scripting with point cloud visualization with help of Edouard.
* Writing the tutorial.

=== Corey White ===

* Discussed and reviewed PRs for Google Summer of Code json and jupyter notebook projects.
* Helped setting up Docker environment for GRASS GIS and Jupyter Lab.
* Working on t.stac.* addon. (PR https://github.com/OSGeo/grass-addons/pull/802)
* Opened PR for new point pattern analysis tool v.paa (https://github.com/OSGeo/grass/pull/3826)

=== Luís de Sousa ===

* Debugging [https://github.com/OSGeo/grass/issues/2187 issue #2187] ([https://github.com/OSGeo/grass/pull/3869 PR #3869])
* Unit tests for [https://github.com/OSGeo/grass/tree/main/vector/v.out.ogr v.out.ogr] ([https://github.com/OSGeo/grass/pull/3848 PR #3848])
* Updates to add-ons documentation ([https://github.com/OSGeo/grass-addons/pull/1105 PR #1105])
* Review to Unit Test documentation ([https://github.com/OSGeo/grass/issues/3887 issue #3887])
* Discussion on parallel computation:
** several approaches exist (documented in the [https://github.com/ncsu-geoforall-lab/opengeohub-2023 OpenGeoHub 2023 workshop]) but not all accessible to non-programmers;
** most modules obvious to be parallelised have [https://grass.osgeo.org/grass83/manuals/keywords.html#parallel already been so];
** patching of results is an issue (high overhead), although in the GridModule a virtual raster could be an option.

=== Anna Petrasova ===
* Participated in the PSC meeting to define elections date and other elections related issues. See [[PSC_Meeting_2024-06-14]].
* Discussed and reviewed PR for Google Summer of Code jupyter notebook projects.
* Reviewing v.surf.rst PR (Cross-validation OpenMP support, PR #3590)
* Tasked Caitlin to show layer controller in grass.jupyter.InteractiveMap by default, defined implementation, reviewed her PR (#3880)
* Solving conflict and reviewing PR #2481
* Testing and reviewing r.texture PR #3857, running benchmarks on laptop and desktop.
* Participated in QGIS discussion, put together meeting minutes: https://github.com/OSGeo/grass/discussions/3898
* Participated in the roadmap discussion session.
* Participated in the documentation discussion session.
* Restructured CONTRIBUTING.md by moving out Github workflow into separate file
* Led GSoC students presentations.
* Participated in discussion about parallelization with Luis and Vashek, Caitlin and others

=== Chung-Yuan Liang ===
* Refactored r.texture and updated tests (PR [https://github.com/OSGeo/grass/pull/3785 #3785], [https://github.com/OSGeo/grass/pull/3786 #3786]).
* Parallelized r.texture and provided benchmarks.
* Revised v.surf.rst PR (Cross-validation OpenMP support, PR [https://github.com/OSGeo/grass/pull/3590 #3590]).
* Enabled Python benchmark module to plot speedup and efficiency (PR [https://github.com/OSGeo/grass/pull/3835 #3835]).
* Parallelized r.horizon and provided benchmarks. (PR [https://github.com/OSGeo/grass/pull/3890 #3890])
* Discussed details of parallelizing modules with Vashek and Anna.

=== Caitlin Haedrich ===
* Discussed GRASS, Jupyter and Windows with Heli
* Wrote tutorial for using OSGeo4W to set up Jupyter Lab in Notebooks - [https://github.com/ncsu-geoforall-lab/tutorials/pull/3 PR]
* Set up Publer account for social media management, compared with Buffer
* Took pictures and posted 2x daily to social media
* Added Layer Control by default to grass.jupyter.InteractiveMap() - [https://github.com/OSGeo/grass/pull/3880 PR]
* Reviewed all GRASS GIS online profiled and compiled list that need updating (report in progress)

=== Edouard Choinière ===
* Discussion with Vaclav Petras on current state of python packaging, build, and testing framework and coverage, Windows porting improvements, and future plans. Planning for the week. Lead to PRs addressing Windows blockers: [https://github.com/OSGeo/grass/pull/3850 #3850] and [https://github.com/OSGeo/grass/pull/3853 #3853], which I tested on my fork combined with my changes highlighting the bugs.
* Reviewing of PRs, managing CI during the sprint (restarting transient failures, finding inefficiencies, queueing jobs before and after active periods).
* Maintaining code quality CI and pre-commit. Example: Flake8 fails with Python 3.12 in pre-commit, as it is way outdated, harming contributions of the sprint's participants. Bumping to a new version has other failures and dependent changes needed. Related PRs include: [https://github.com/OSGeo/grass/pull/3808 #3808], [https://github.com/OSGeo/grass/pull/3831 #3831], [https://github.com/OSGeo/grass/pull/3833 #3833], [https://github.com/OSGeo/grass/pull/3840 #3840], [https://github.com/OSGeo/grass/pull/3814 #3814], [https://github.com/OSGeo/grass/pull/3799 #3799], [https://github.com/OSGeo/grass/pull/3834 #3834], [https://github.com/OSGeo/grass/pull/3815 #3815], [https://github.com/OSGeo/grass/pull/3820 #3820], [https://github.com/OSGeo/grass/pull/3818, #3818], [https://github.com/OSGeo/grass/pull/3813 #3813], [https://github.com/OSGeo/grass/pull/3855 #3855], [https://github.com/OSGeo/grass/pull/3817 #3817], [https://github.com/OSGeo/grass/pull/3812 #3812], [https://github.com/OSGeo/grass/pull/3859 #3859], [https://github.com/OSGeo/grass/pull/3860 #3860], [https://github.com/OSGeo/grass/pull/3861 #3861], [https://github.com/OSGeo/grass/pull/3841 #3841]
* Help Markus debugging Dockerfile builds. Reviewed docker-related PRs, improved docker builds, upgrade base images. (PRs: [https://github.com/OSGeo/grass/pull/3802 #3802], [https://github.com/OSGeo/grass/pull/3807 #3807], [https://github.com/OSGeo/grass/pull/3810 #3810], [https://github.com/OSGeo/grass/pull/3828 #3828], [https://github.com/OSGeo/grass/pull/3819 #3819], [https://github.com/OSGeo/grass/pull/3830 #3830], [https://github.com/OSGeo/grass/pull/3797 #3797], [https://github.com/OSGeo/grass/pull/3787 #3787], [https://github.com/OSGeo/grass/pull/3773 #3773], [https://github.com/OSGeo/grass/pull/3822 #3822], [https://github.com/OSGeo/grass/pull/3728 #3728])
* Helped multiple times Alen Mangafić with usage and building custom Docker images with different versions of PDAL.
* Designing and drafting the integration of docker build caching to improve build times whilst keeping risk of using cached old dependencies. [https://github.com/OSGeo/grass/pull/3821 #3821]
* With Vaclav Petras: reviewing backportable PRs, and designing the requirements and it's implementation of a automated backport solution with GitHub actions. Prioritized to work on the implementation after the sprint, as other features affecting productivity during the sprint should be worked on. Edit: implementation started on [https://github.com/echoix/grass/tree/backport-automation a branch of my fork]
* With Vaclav Petras: Discussing release notes generation improvements, deciding on new labels and classification, adjusting and improving titles regexes. Designed a process to validate PR that PR titles are classified correctly automatically, to greatly simplify future releases. This lead to Vaclav creating the validation function in [https://github.com/OSGeo/grass/pull/3824 PR #3824]. Implementation of validation workflow on PR creation and title changes will follow. PRs related to these decisions also include: [https://github.com/OSGeo/grass/pull/3823 #3823], [https://github.com/OSGeo/grass/pull/3829 #3829]
* Clarifying our supported languages standard support with Vaclav Petras and when changes should be made, leading to reduction of C/C++ CI usage in [https://github.com/OSGeo/grass/pull/3846 #3846]. Postponed checking of newer C++23 until Ubuntu 24.04 builds with newest GCC toolchain are included in CI.
* Helping Alen Mangafić with a local build to run alongside jupyter and conda environment.
* Reviewing Chung-Yuan Liang's PR, then assisting him multiple times with git operations, argparse, and unittest-related problems when programming. Sample of resulting PRs: [https://github.com/OSGeo/grass/pull/3835 #3835]
* Review and ajust repository's configuration to prevent some noticed problems, including pull request title/commit details (with Markus) and ruleset permissions related to branch creation (with Vaclav).
* PR title validation workflow implemented: [https://github.com/OSGeo/grass/pull/3877 #3877]
* Debug and investigate pytest timeout failures of [https://github.com/OSGeo/grass/pull/3879 #3879] that that same PR was supposed to prevent. The most probable explanation requires changing the multiprocessing startup method from fork to spawn, that also requires the code to be pickle-able. Alternative solution to avoid this requires changes of blocked and unmerged PRs that I worked to unblock. Unblocking these is also required to run pytest on macOS and Windows, and for a future python 3.14 on Linux too.
* Finish debugging porting Travis CI to Ubuntu 22.04 (Jammy) to unblock other PRs. Needed to fix some errors from -Wdeprecated-non-prototype to make Travis pass with the new -Werror flag. PR: [https://github.com/OSGeo/grass/pull/3002 #3002]
* Windows test failures due to external web content used for g.extension tests not being available for 8.5 on winGRASS yet. [https://github.com/OSGeo/grass/issues/3893 #3893]

=== Vaclav Petras ===

* PR reviews (a lot)
* Work on RC1 (release notes, automatic generators)
* Venue organizing and hosting
* Review of media posts

Talk:GRASS Community Meeting Prague 2024

2024-06-16T11:12:59Z

Cyliang:

{{toc|right}}

Quick links: [[GRASS Community Meeting Prague 2024|Meeting page]] | [[#Reports|Reports]] | [[GRASS_Community_Meeting_Prague_2024#Sponsor_us!|Sponsors]]

== Organizing Team ==

* Initial planning: Martin Landa, Vaclav Petras, Veronica Andreo, Markus Neteler, Anna Petrasova, Helmut Kudrnovsky, Helena Mitasova
* Budget: Vaclav Petras, Anna Petrasova, Markus Neteler, Veronica Andreo, Helena Mitasova
* Wiki page: Vaclav Petras, Veronica Andreo, Martin Landa

== Tasks for participants ==

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

== Reports ==

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

=== Floris Vanderhaeghe ===

* Help sorting out a few issues in the [https://github.com/rsbivand/rgrass repository of R package rgrass].
* Make maintenance pull requests [https://github.com/rsbivand/rgrass/pull/90 PR #90] and [https://github.com/rsbivand/rgrass/pull/91 PR #91] to support future contributors of the R package rgrass.

=== Markus Neteler ===

* cleanup labels in GitHub repo
* replace --tmp-location with --tmp-project (pull requests [https://github.com/OSGeo/grass/pull/3825 PR #3825], [https://github.com/OSGeo/grass/pull/3822 PR #3822])
* docker: remove "grass-session" pip approach, replace to new build-in Python API (pull request [https://github.com/OSGeo/grass/pull/3819 PR #3819])
* Participated in the PSC meeting to define elections date and other elections related issues. See [[PSC_Meeting_2024-06-14]].
* Discussion about our Dockerfiles
* Simplified examples for working with GRASS 8.4+ in Python (update [https://gis.stackexchange.com/a/457875/687 Stackexchange posts])
* Participated of the roadmap discussion session
* cleanup of many pull request titles to be recognized by https://github.com/OSGeo/grass/blob/main/utils/release.yml
* Complete OpenSSF Best Practices badge questionnaire to 100%: https://www.bestpractices.dev/en/projects/2470
* backport plenty of pull requests to GRASS GIS 8.4 release branch
* social media outreach: suggest use of Publer.io to easier feed our channels (discuss with Vero and Caitlin)

=== Veronica Andreo ===

* Discuss tutorial topics with Alen
* Reviewed PRs: i.eodag, a couple related to the temporal framework, tutorial on GRASS usage within Jupyter on Windows.
* Participated in the PSC meeting to define elections date and other elections related issues. See [[PSC_Meeting_2024-06-14]].
* Compiled the raw list of contributors since Dec 2020, to create the list of voters.
* Set up a swag shop in RedBubble and added designs with color and white logos. Yet not published as payment details need to be configured with OSGeo treasurer.
* Participated of the roadmap discussion session - Roadmap will be published in the website.

=== Alen Mangafić ===
* Discuss tutorial with Veronica and Vaclav.
* Setting up the environment for the tutorial with Ondřej and Corey, resulting in a process to build a Docker container with the main branch and it's kernel connection to Jupyter Lab.
* Writing a Jupyter Lab framework which works. Helped by Vaclav with locating the "GISENV" location bug.
* Data preparation: correction the point clouds to match correct Global Encoding value of a LAS 1.4 file with PDRF 6 - 10 is 17 (16 + 1); CRS definition.
* Testing and drafting the workflow in GUI.
* Found a and reported a bug about how r.in.pdal handles the number of returns ([https://github.com/OSGeo/grass/issues/3827 #3827]).

=== Corey White ===

* Discussed and reviewed PRs for Google Summer of Code json and jupyter notebook projects.
* Helped setting up Docker environment for GRASS GIS and Jupyter Lab.
* Working on t.stac.* addon. (PR https://github.com/OSGeo/grass-addons/pull/802)
* Opened PR for new point pattern analysis tool v.paa (https://github.com/OSGeo/grass/pull/3826)

=== Luís de Sousa ===

* Debugging [https://github.com/OSGeo/grass/issues/2187 issue #2187]
* Unit tests for [https://github.com/OSGeo/grass/tree/main/vector/v.out.ogr v.out.ogr]

=== Anna Petrasova ===
* Participated in the PSC meeting to define elections date and other elections related issues. See [[PSC_Meeting_2024-06-14]].
* Discussed and reviewed PR for Google Summer of Code jupyter notebook projects.
* Reviewing v.surf.rst PR (Cross-validation OpenMP support, PR #3590)
* Tasked Caitlin to show layer controller in grass.jupyter.InteractiveMap by default, defined implementation
* Solving conflict and reviewing PR #2481

=== Chung-Yuan Liang ===
* Refactored r.texture and updated tests (PR #3785, #3786).
* Parallelized r.texture and provided benchmarks.
* Revised v.surf.rst PR (Cross-validation OpenMP support, PR #3590).
* Enabled Python benchmark module to plot speedup or efficiency.

GRASS GSoC Ideas 2024

2024-05-10T15:40:34Z

Cyliang: /* Parallelization of existing tools in GRASS GIS */

== About ==

* [https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2024_Ideas The OSGeo GSoC 2024 main page]
* [https://summerofcode.withgoogle.com/ Official GSoC page at Google]

== Accepted ideas ==
=== Add JSON output to different GRASS tools in C ===
* Student: Kriti Birda
* Mentors: Corey White and Vaclav Petras
* Wiki page

=== Add EODAG support to GRASS GIS ===
* Student: Hamed Ashraf
* Mentors: Luca Delucchi, Veronica Andreo, Stefan Blumentrath
* [https://wiki.osgeo.org/wiki/GRASS_GSoC_2024_EODAG_Support Wiki page]

=== Parallelization of existing tools in GRASS GIS ===
* Student: Chung-Yuan Liang
* Mentors: Huidae Cho, Vaclav Petras, Maris Nartiss
* [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_2024_Parallelize_Tools Wiki page]

=== Improve GRASS user experience in Jupyter Notebook ===
* Student: Riya Saxena
* Mentors: Anna Petrasova, Corey White
* Wiki page

== 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://lists.osgeo.org/listinfo/grass-dev grass-dev mailing list],[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.''

Include "GRASS GIS" in the title of our idea to easily distinguish ideas and projects inside OSGeo.

=== 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
* Test of skills: suggest/implement solution for https://github.com/OSGeo/grass/issues/2644

=== 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 adding parallelization for rendering, increasing interactivity of displayed data using ipyleaflet (e.g., capture mouse clicks to show information about vector line, pixel), adding API for managing projects and subprojects (i.e., locations/mapsets), simplifing display of attribute data, ...

* Requirements: Python
* Mentor: Anna Petrasova
* Co-mentor: Vaclav Petras, Helena Mitasova
* 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
* 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).

=== STAC (SpatioTemporal Asset Catalog) Integration ===

Create new import and export capabilities for GRASS GIS which allow users to easily ingest data from STAC catalogs and export locations and mapsets as STAC specs for data discovery within STAC browsers.

* Requirements: familiar with python, STAC specs
* Mentor: Corey White
* Co-mentor: Vaclav Petras, Anna Petrasova
* Project length: 175 or 350 hours (take your pick)
* Rating: medium
* Expected Outcomes: completion of t.in.stac and t.out.stac
* Test of skills:
** suggest or implement solution for implementing t.out.stac using the prototype STAC spec https://github.com/tomorrownow/grass-stac-extension
** suggest/implement solution for completing https://github.com/OSGeo/grass-addons/pull/802

=== Add EODAG support to GRASS GIS ===

[https://eodag.readthedocs.io/en/stable/ EODAG] is a Python library useful to download several satellite datasets from different providers (i.e., USGS, Copernicus, AWS, Planetary Computer, etc.). GRASS has various modules to download satellite data like i.sentinel.download, i.landsat.download, i.modis.download. However, they all use different libraries, some of them no longer maintained. Hence, implementing the use of EODAG as back-end for those tools would be very useful not only in terms of maintenance but also in terms of less code repetition. It would also open the possibility for new tools or a master tool to download other datasets directly from GRASS.

* Requirements: familiar with Python
* Project length: 175 or 350 hours
* Mentor: Luca Delucchi
* Co-mentor: Veronica Andreo
* Proposed by: Luca Delucchi
* Rating: medium
* Expected Outcomes: 175 hours EODAG core library to be able to download products; 350 library + application at least to i.sentinel.download but hopefully also to i.landsat.download
* Test of skills: https://github.com/OSGeo/grass-addons/issues/1033

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

* If you have your own ideas we encourage you to propose them. Explain them on the [https://lists.osgeo.org/listinfo/grass-dev grass-dev mailing list].
* If you like some idea here or from previous yeas, write about it on [https://lists.osgeo.org/listinfo/grass-dev grass-dev mailing list] and any ideas of your own which could improve it.
* 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 GIS 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 GIS from source and prepare environment for development:
** Read [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md CONTRIBUTING file] and [https://grasswiki.osgeo.org/wiki/Compile_and_Install compilation instructions].
** If you get stuck with the setup, feel free to consult the [https://lists.osgeo.org/listinfo/grass-user grass-user mailing list].
** Familiarize yourself with wiki:Submitting rules.
* Prove your worth by being active on the GRASS mailing lists ([https://lists.osgeo.org/listinfo/grass-user grass-user], [https://lists.osgeo.org/listinfo/grass-dev grass-dev]) or other channels ([https://github.com/OSGeo/grass/discussions GitHub Discussions], [https://gitter.im/grassgis/community Gitter]), 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.

* Every year GRASS GIS hopes to participate and participates in GSoC as part of the [https://www.osgeo.org/ OSGeo Foundation]'s GSoC program umbrella. See the official OSGeo template for application details and other important information at the [https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students OSGeo Recommendations for Students].

{{GSoC}}

GRASS GSoC 2024 Parallelize Tools

2024-05-10T15:36:49Z

Cyliang: Created page with "Accepted Google Summer of Code 2024 project. {| {{table}} |Student Name: || Chung-Yuan Liang, [https://www.purdue.edu/ Purdue University, West Lafayette, USA] |- |Organization: || [http://www.osgeo.org OSGeo - Open Source Geospatial Foundation] |- | Mentor Name: || Huidae Cho, Vaclav Petras, Maris Nartiss |- | Title: || '''Parallelization of existing tools in GRASS GIS''' |- |} ;Abstract ::This project aims to parallelize geospatial tools/algorithms to..."

Accepted Google Summer of Code 2024 project.

{| {{table}}
|Student Name: || [[User:cyliang|Chung-Yuan Liang]], [https://www.purdue.edu/ Purdue University, West Lafayette, USA]
|-
|Organization: || [http://www.osgeo.org OSGeo - Open Source Geospatial Foundation]
|-
| Mentor Name: || Huidae Cho, Vaclav Petras, Maris Nartiss
|-
| Title: || '''Parallelization of existing tools in GRASS GIS'''
|-
|}

;Abstract
::This project aims to parallelize geospatial tools/algorithms to enhance our abilities to utilize and analyze large-scale geospatial and remote sensing data. Although many geographic information system (GIS) tools are widely used, they haven’t been parallelized yet. The serial computation, while functional for modest datasets, significantly restricts the processing time and scalability necessary for handling increasingly larger geospatial datasets. Leveraging the potential of modern computing hardware, we can parallelize tools to mitigate these limitations. Several tools could benefit from parallelization, such as r.texture, r.horizon, r.fill.stats, r/v.surf.idw, r.viewshed, v.to.rast, r.to.vect, r.grow.distance, etc. These tools can be speeded up by parallelization with OpenMP and MPI. Moreover, CUDA can be used for these tools to compute raster and image processing on GPU.
__TOC__
== Application ==