GRASS-Wiki - User contributions [en]

GRASS GSoC Ideas 2025

2025-03-04T17:21:36Z

Ctwhite: /* New easy-to-use CLI and API for GRASS GIS */

== About ==

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

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

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

* 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 Ideas 2025

2025-03-04T17:20:40Z

Ctwhite: /* Improve GRASS user experience in Jupyter Notebook */

== About ==

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

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

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

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

NSF POSE Project 2023-2025 Timeline

2024-09-13T18:16:12Z

Ctwhite:

[[File:NSF_grant_announcement.png|500px|right|none]]

To inform GRASS community about the work done as part of the award [https://www.nsf.gov/awardsearch/showAward?AWD_ID=2303651 2303651] from the U.S. National Science Foundation (NSF) to enhance GRASS ecosystem, the following report summarizes the progress and outcomes in quarterly reports and presents the roadmap for the project.

The two main goals of the project are: 1) to facilitate the adoption of GRASS GIS as a key geoprocessing engine by a growing number of researchers and geospatial practitioners in academia, governments, and industry; and 2) to expand and diversify the developer community, especially through supporting next-generation scientists to gain expertise to maintain and innovate GRASS software.

Principal investigators and senior personnel:

* Helena Mitasova, North Carolina State University (Principal Investigator)
* Vaclav Petras, North Carolina State University (Co-Principal Investigator)
* Anna Petrasova, North Carolina State University (Co-Principal Investigator)
* C Michael Barton, Arizona State University (Co-Principal Investigator)
* Huidae Cho, New Mexico State University (Co-Principal Investigator)
* Giuseppe Amatulli, Yale (Senior Personnel)

Other personnel who is joining for the execution of the grant is listed below when relevant.

== Y1 1st quarter report ==
=== Project Announcements and Communication ===
* Announcement on [https://grass.osgeo.org/news/2023_09_06_nsf_grant_awarded/ GRASS website].
* Info session to explain the POSE Project ([https://lists.osgeo.org/pipermail/grass-user/2023-September/083423.html Announcement on GRASS user mailing list], 2 sessions for different time zones).
* Collected statistics from GitHub, X and others and set up automated collection for GitHub.

=== Conference Presentations ===
* [https://petrasovaa.github.io/FUTURES-CONUS-talk/foss4gNA2023.html#/ Parallelization Tips for Geoprocessing with GRASS GIS] by Anna Petrasova at FOSS4GNA, October 2023.
* [https://wenzeslaus.github.io/grass-gis-talks/foss4gna2023.html#/ GRASS GIS: Not What You Think] by Vaclav Petras at FOSS4GNA, October 2023.
* [https://docs.google.com/presentation/d/1D-Fh1cLSPINyeXdVaxlakrE9IjB8kK5lIw3D12yX1bk Computational Notebooks for Reproducible Geospatial Computation in Research and Education] by Caitlin Haedrich at FOSS4GNA, October 2023.
* [https://github.com/HuidaeCho/grass-gis-talk-foss4g-asia-2023 State of GRASS GIS: 40 Years Strong and Counting] by Huidae Cho at FOSS4G Asia, November 2023.

=== Training and Workshops ===
* [https://github.com/ncsu-geoforall-lab/grass-gis-workshop-foss4gna-2023 Unlock the power of GRASS GIS] by Anna Petrasova and Caitlin Haedrich at FOSS4GNA, October 2023.
* [https://github.com/ncsu-geoforall-lab/develop-tools-with-grass-foss4gna-2023 Develop Geospatial Workflows and Custom Tools with GRASS GIS] by Vaclav Petras and Corey White at FOSS4GNA, October 2023.
* [https://github.com/ncsu-geoforall-lab/grass-workshop-gis-week-2023 Big Data Computing with GRASS GIS] by Anna Petrasova and Vaclav Petras at NC State GIS week, November 2023.
* [https://github.com/ncsu-geoforall-lab/grass-gis-on-hpc-henry2/blob/8564c72e9b8929c9ef4d25ada1ef36b569991221/docs/tutorial.md GIS Week Workshop: High Performance Computing for Geospatial Analysis (GRASS GIS part)] by Vaclav Petras (main lecture lead by Andrew Petersen from NCSU OIT) at NC State GIS week, November 2023.
* [https://spatial-ecology.net/docs/build/html/index.html Geocomputation and Machine Learning for Environmental Applications] training course [https://spatial-ecology.net/course-geocomputation-machine-learning-for-environmental-applications-intermediate-level-2024/ announced]. GRASS GIS part led by Giuseppe Amatulli is free of charge thanks to the support by NSF.

=== Community Sprint Participation ===
Anna Petrasova and Vaclav Petras remotely participated in [https://wiki.osgeo.org/wiki/OSGeo_Community_Sprint_2023 OSGeo 2023 code sprint] doing PR reviews and maintenance of GRASS GIS code, documentation, and website.

=== Mentoring Program ===
* Started a development-oriented mentoring program [https://grass.osgeo.org/news/2023_10_11_mentoring_program_announced/ announced] with details available on a [https://grasswiki.osgeo.org/wiki/Mentoring_Program wiki page].
* Program now has 4 participants (from 12 responses) supported by email and video calls.
* Program already resulted in improvements to GRASS GIS core and addons:
** merged PR: [https://github.com/OSGeo/grass/pull/3206 grass.script: ensure memmap content is flushed before writing to a raster]
** radar addon toolset PR: [https://github.com/OSGeo/grass-addons/pull/949 Add i.saocom and i.sar toolsets]
Mentoring Program is a new effort started and so-far performed only by the POSE team.

=== Student Grants Program ===
Student grants [https://grass.osgeo.org/news/2023_11_09_student_grants_announced/ announced] with topics at a [https://grasswiki.osgeo.org/wiki/GRASS_GIS_Student_Grants wiki page]. Student Grants Program is an existing effort which the POSE team participates in.

=== Working Groups ===

Four [https://grasswiki.osgeo.org/wiki/Working_Groups working groups] created (scope, wiki page, coordinator, and a list of people for each).

=== Citations ===

* GRASS GIS Google Scholar [https://scholar.google.com/citations?user=gJ0ZB0cAAAAJ account] updated with more complete records.
* A [https://forms.gle/cDEvMJu7d6nvxLKn9 form] was created to collect new and missing records.
* Profile link added to GRASS website [https://grass.osgeo.org/contribute/ Contribute] and [https://grass.osgeo.org/about/citation/ Citation] page.

== Y1 2nd quarter report ==
=== NSF I-Corps program ===
Corey White, Vaclav Petras, and Anna Petrasova participated in a 4-week long intensive mandatory training that draws on the methods, customer discovery, and curriculum of the [https://new.nsf.gov/funding/initiatives/i-corps NSF Innovation Corps] and applies them to open-source projects.

The program included conducting 70+ 30-minute interviews with both GRASS users and non-users to better shape the future path of GRASS GIS and the POSE project. So far, the interviews focused on educators, companies, researchers, influencers and it focused more on non-users than users.

Next steps, include processing the collected qualitative data, developing possible future directions for sustainability of the project, discussing these with the Project Steering Committee, the core team of developers, and the broader community.

=== Mentoring Program ===
The development oriented [https://grass.osgeo.org/news/2023_10_11_mentoring_program_announced/ mentoring program] welcomed 5 new participants from various institutions including universities, USGS, US Army Corps of Engineers, and local municipalities. The discussed topics covered developing workflows for topography and network analysis, environmental modeling, and geophysics. Participants were supported by email and video calls.

=== Conference Presentations ===
* [https://agu.confex.com/agu/fm23/meetingapp.cgi/Paper/1342418 Modeling vegetated stream buffer impacts on water depth and discharge at the watershed scale with GRASS GIS and Jupyter Notebooks] by Caitlin Haedrich at AGU, December 2023.
* [https://agu.confex.com/agu/fm23/meetingapp.cgi/Paper/1420596 OpenPlains: A Web-Based Platform to Democratize Geospatial Participatory Modeling on the Cloud] by Corey White at AGU, December 2023.

=== Presentations and Workshops ===
* [https://github.com/ncsu-geoforall-lab/grass-gis-workshop-vanderbilt-2024 Intro to GRASS GIS] by Vaclav Petras and Anna Petrasova was remotely delivered to geographers at Vanderbilt University in February 2024. The workshop was developed in Jupyter Lab and run using [https://wholetale.org WholeTale] online platform.
* [https://github.com/tomorrownow/intro-to-geoprocessing-workshop Introduction to GRASS GIS Geospatial Processing] by Corey White at [https://smathhacks.ncssm.edu/ SMathHacks hackathon], March 2nd (supported also by Veronica Andreo and Vaclav Petras). SMathHacks is the annual 36-hour hackathon hosted by the NC School of Science and Math, open to all North Carolina students. Students collaborate to build innovative software projects, explore new technologies, and have fun along the way. The workshop was delivered in person with students using [https://colab.research.google.com/ Google Colab].

=== Student Grant Program ===
Linda Karlovska participates in the [https://grasswiki.osgeo.org/wiki/GRASS_GIS_Student_Grants Student Grant program] with her project [https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/EasyCommandHistoryNavigation Easy command history navigation through the History browser panel] mentored by Anna Petrasova (POSE team) and Martin Landa (FCE CTU). Student Grants Program is an existing effort which the POSE team participates in by mentoring.

=== Code Security ===
Vaclav Petras mentors four students who create code security improvements in their NCSU class ''CSC 472: Cybersecurity Practicum''. So far, the students created two PRs which were successfully merged:
* [https://github.com/OSGeo/grass/pull/3444 grass.script: Change insecure mktemp to NamedTemporaryFile #3444]
* [https://github.com/OSGeo/grass/pull/3451 utils: fixed shell vulnerability in mkrest.py #3451]

Two other PRs are open and more work is underway to do first steps for new approach to a more secure code.

=== Localized Basic Datasets ===
* NCSU and ASU teams worked on localized versions of GRASS basic data set following the [https://grass.osgeo.org/sampledata/north_carolina/nc_basic_spm_grass7.zip North Carolina basic data set example], preparing Flagstaff, Arizona and Nepal draft version with basic layers

== Y1 3rd quarter report ==

=== Mentoring Activities ===
The mentoring program form received 2 new responses and mentors were actively working with 3 mentees.
It resulted in fixes in [https://github.com/OSGeo/grass-addons/pull/1042 v.transects] and [https://github.com/OSGeo/grass-addons/pull/1077 r.accumulate].

Linda Kladivova finished her project developing [https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/EasyCommandHistoryNavigation History browser] in the GRASS GUI as part of the GRASS Student Grant Program. Mentor's time was covered by POSE.

GRASS GIS has [https://grass.osgeo.org/news/2024_05_27_gsoc_2024_students/ 3 students this year for Google Summer of Code]. Time spent managing GSoC for GRASS GIS was covered by POSE.

The topics covered by GSoC projects are:
* [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_2024_EODAG_Support Add EODAG support to GRASS GIS]
* [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_2024_Improve_user_experience_in_Jupyter_Notebooks Improve GRASS user experience in Jupyter Notebook]
* [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_2024_Add_JSON_output Add JSON output to different GRASS tools in C]

=== Presentations, Workshops, Event Planning ===
* [https://github.com/ncsu-geoforall-lab/tngic-2024 GRASS 101: From GUI Clicks to Writing Scripts (TNGIC 2024)] by Veronica Andreo and Caitlin Haedrich
* [https://github.com/ncsu-geoforall-lab/csdms-grass-2024 Coastal evolution analysis and inundation modeling with GRASS GIS (CSDMS Workshop 2024)] by Caitlin Haedrich and Pratikshya Regmi, see also [https://cnr.ncsu.edu/geospatial/news/2024/06/03/students-teach-grass-gis-for-coastal-hazard-analysis/ blog post with images]

* Organization of [[GRASS Community Meeting Prague 2024]] and budget planning by Vaclav Petras

=== CMake transition ===
Ongoing work on [https://github.com/OSGeo/grass/pull/3621 CMake compilation] was partially covered by POSE.

=== Code Quality and Security ===

Code quality improvements in Python code:
* [https://github.com/OSGeo/grass/pull/3541 PR addressing Flake8 E501] (long lines in 158 files not fixable by automated tools)
* [https://github.com/OSGeo/grass/pull/3535 PR addressing Flake8 E401] (unused imports)

Vaclav Petras mentored a team of four students who create code security improvements in their NCSU class ''CSC 472: Cybersecurity Practicum''. The team created 12 PRs which were successfully merged, 7 additional experimental PRs (not merged) and 2 PRs which are still open at this time. Specifically, the team achieved the following:

* With the involvement and help from the other contributors, the team introduced Bandit and Coverity Scan as additional code scanning tools for Python and C, respectively.
* The team analyzed issues reported CodeQL, Bandit, and Coverity Scan and reported on relevance of different issues to the project (report privately shared with the GRASS Development Team).
* Vulnerability Triage Guide (also privately shared with the GRASS Development Team).
* The team also developed a [https://github.com/OSGeo/grass/security/policy security policy] for the project.
* The vulnerability reporting and security advisories were enabled based on the team recommendations.
* The team fixed several specific security issues in the code:
** [https://github.com/OSGeo/grass/pull/3469 packaging: Use subprocess instead of os.popen for change log creation #3469] (merged)
** [https://github.com/OSGeo/grass/pull/3549 lib raster: fixed security vulnerabilities and weaknesses #3549] (merged)
** [https://github.com/OSGeo/grass/pull/3451 utils: fixed shell vulnerability in mkrest.py #3451] (merged)
** [https://github.com/OSGeo/grass/pull/3444 grass.script: Change insecure mktemp to NamedTemporaryFile #3444] (merged)
** [https://github.com/OSGeo/grass/pull/3551 lib/psdriver: Fix issues with wrong type of arguments to printf #3551] (PR open)
** [https://github.com/OSGeo/grass/pull/3452 g.region/r.to.rast3elev: fixed scanf error to recognize EOF as a possible return value #3452] (PR open)

=== Documentation ===
* Documentation and Education Working Group met and planned the development of new tutorials. Veronica Andreo met other GRASS developers and contributors to coordinate further tutorials development.
* Development of new [https://github.com/ncsu-geoforall-lab/tutorials tutorials] in progress, topics include:
** Getting started with GRASS GIS
** GRASS GIS in Google Colab
** GRASS GIS and Python
** GRASS GIS and R
** GRASS R and Python comparison
** Making plots in GRASS GIS
* New [https://github.com/OSGeo/grass/blob/main/doc/development/style_guide.md GRASS Programming Style Guide]
* [https://github.com/petrasovaa/cookiecutter-grass-addon New addon template powered by Cookiecutter]
* Analysis of options names and functionality in plotting tools:
** [https://github.com/OSGeo/grass-addons/issues/1071 Addons for plotting: Standardize parameters and flags]

=== Communication and outreach ===

* Creation of 4 news post in the [https://grass.osgeo.org/news/ GRASS website]
* Social media:
** [https://twitter.com/GRASSGIS Twitter]: 9 new posts/threads
** [https://fosstodon.org/@grassgis Fosstodon]: 9 new posts/threads

=== Other sustainability activities ===
* [https://github.com/OSGeo/grass/blob/main/CODE_OF_CONDUCT.md Code of Conduct added to the main repository]
* [https://github.com/OSGeo/grass/blob/main/.github/ISSUE_TEMPLATE/bug_report.md revised Issue template]
* New [https://github.com/OSGeo/grass/pull/3673 RFC for a Release Policy]
* Revised [https://github.com/OSGeo/grass/pull/2815 RFC for Release Procedure]
* WIP: GRASS GIS Roadmap
* [https://github.com/OSGeo/grass-website/issues/414 GRASS website: ongoing restructuring]
* [[PSC]] page moved from trac wiki to media wiki

== Y1 4th quarter report ==

=== Mentoring Activities ===
The mentoring program form received 3 new responses and mentors were actively working with 3 mentees.
Results include parallelization of r.texture, r.horizon, improved grass.benchmarking library and a new tutorial on lidar data.

GSoC successfully completed their projects:
* [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_2024_EODAG_Support Add EODAG support to GRASS GIS]
* [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_2024_Improve_user_experience_in_Jupyter_Notebooks Improve GRASS user experience in Jupyter Notebook]
* [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_2024_Add_JSON_output Add JSON output to different GRASS tools in C]

Time spent by mentoring was covered by NSF.

=== Presentations, Workshops, Event Planning ===

* [https://veroandreo.github.io/grass_foss4geu_2024/ Let's combine GRASS, Python and R: Satellite time series data for species distribution modeling]. Workshop by Veronica Andreo. FOSS4G Europe 2024, Tartu.
* [https://veroandreo.github.io/grass-gis-talks/foss4gEU2024.html#/ Status of GRASS GIS project]. Talk by Veronica Andreo. FOSS4G Europe 2024, Tartu.
* [https://veroandreo.github.io/grass-gis-talks/useR2024.html#/ Boost Spatial Data Science Workflows with GRASS GIS and R]. Talk by Veronica Andreo. useR Conference 2024, Salzburg.
* [https://ncsu-geoforall-lab.github.io/usdoi-webinar/notebooks/grass_jupyter.html Geoprocessing with GRASS GIS and Jupyter Notebooks]. Webinar by Corey White. U.S. DOI, August 2024, NCSU.
* [[GRASS Community Meeting Prague 2024]]

* Planning GRASS Dev summit 2025 at NCSU

* Planning AGU (4 abstract submitted), AGU booth for GRASS GIS reserved and payed

* Submitted workshop, talk and keynote to FOSS4G 2024 - Brazil.

=== CMake transition ===
Ongoing work on [https://github.com/OSGeo/grass/pull/3621 CMake compilation] was partially covered by POSE.

=== Code Quality and Security ===

* Code quality improvements in Python code:
** [https://github.com/OSGeo/grass/pull/3763 Flake8 W605 Invalid escape sequence #3763]
** [https://github.com/OSGeo/grass/pull/3926 Flake8 E741 Do not use variables named 'I', 'O', or 'l' in wxGUI code #3926]
** [https://github.com/OSGeo/grass/pull/3928 Flake8 E741 for the rest of code base #3928]
** [https://github.com/OSGeo/grass/pull/4200 grass.temporal: Flake8 F841 Local variable assigned to but never used #4200]
** [https://github.com/OSGeo/grass/pull/4113 grass.pygrass: Remove unused arg in ctypes.CFUNCTYPE #4113]
** [https://github.com/OSGeo/grass/pull/4206 t.rast.to.vect: Fix passing column parameter to r.to.vect, fix flake8 F841 #4206]

* Code quality and security improvements in C and C++ code are in 36 PRs with fixes for more than 25 tools, specifically in:
** raster: r.path, r.out.mpeg, r.out.png, r.in.xyz, r.terraflow, r.statistics, r.spreadpath, r.sim.water, r.sim.erosion, r.object.geometry, r.coin
** imagery: i.atcorr, i.aster.toar, i.ortho.photo, i.landsat.acca, i.segment, i.smap
** display: d.linegraph, d.legend.vect, d.histogram, d.labels
** raster 3D: r3.in.v5d, r3.info, r3.mapcalc
** other: lib/gis, lib/vector/diglib, g.findfile, g.setproj, ps.map, lib/cdhc

Changes by author: [https://github.com/OSGeo/grass/pulls?q=author%3AShubhamDesai+is%3Apr+is%3Aclosed+merged%3A2024-06-01..2024-08-31+base%3Amain+sort%3Aupdated-desc+ ShubhamDesai], [https://github.com/OSGeo/grass/pulls?q=author%3Amshukuno+is%3Apr+is%3Aclosed+merged%3A2024-06-01..2024-08-31+base%3Amain+sort%3Aupdated-desc+ Makiko Shukunobe], [https://github.com/OSGeo/grass/pulls?q=author%3Aymdatta+is%3Apr+is%3Aclosed+merged%3A2024-06-01..2024-08-31+base%3Amain+sort%3Aupdated-desc+ ymdatta]

Several reviewers, not supported by the NSF POSE project, played crucial role not only in reviewing, but also in determining the right fixes.

Fixed issues were reported by Flake8, Coverity Scan, and Cppcheck.

=== Documentation ===

* Veronica Andreo met some GRASS developers and contributors to follow up on tutorials development.
* 7 new [https://github.com/ncsu-geoforall-lab/tutorials tutorials] on time series:
** Management and visualization
** Aggregation
** Algebra
** Accumulation
** Gap filling
** Querying raster time series with vectors
** Subset, import and export
* Tutorial on how to set up Jupyter and GRASS in Windows
* New [https://github.com/OSGeo/grass-tutorials repository] under OSGeo organization to host the upcoming quarto based website for GRASS tutorials
* PR template created - [https://github.com/OSGeo/grass/community GitHub Community Standards] all checked complete

=== Communication and outreach ===

* Creation of 4 news posts in the [https://grass.osgeo.org/news/ GRASS website]
* Social media:
** [https://twitter.com/GRASSGIS Twitter]: 25 new posts
** [https://fosstodon.org/@grassgis Fosstodon]: 25 new posts
* New GRASS GIS LinkedIn page at: [https://www.linkedin.com/company/grass-gis/ https://www.linkedin.com/company/grass-gis/]
* Requested transition of [https://discourse.osgeo.org/t/osgeo-3255-migrate-grass-dev-mailing-list-to-discourse/49796 grass-dev mailing list to discourse.osgeo.org]
* Set up GRASS GIS swag shop on Redbubble

=== Governance ===
* [https://grass.osgeo.org/about/roadmap/ Roadmap] and [https://grass.osgeo.org/about/governance/ Governance] pages added to the website
* PSC elections:
** Documented criteria to define people entitled to vote
** Documented procedure to compile the list of voters
** Elections [https://www.mail-archive.com/grass-user@lists.osgeo.org/msg41102.html announcement] sent out

== Y2 1st quarter report ==

=== Presentations, Workshops, Event Planning ===
FOSS4GNA 2024 in St. Louis, Missouri:

* Vaclav Petras. State of GRASS GIS. FOSS4G NA St. Louis, September 9-11, 2024 ([https://wenzeslaus.github.io/grass-gis-talks/foss4gna2024.html slides])
* Huidae Cho. Evolution of GRASS GIS. FOSS4G NA St. Louis, September 9-11, 2024 ([https://htmlpreview.github.io/?https://github.com/HuidaeCho/grass-talks/blob/main/foss4g-na-2024.html slides])
* Huidae Cho. An OpenMP Algorithm for Delineating a Large Number of Watersheds. FOSS4G NA St. Louis, September 9-11, 2024
* Corey T. White. Developing Web-Applications with GRASS GIS. Workshop. FOSS4G NA St. Louis, September 9-11, 2024
* Corey T. White. GRASS GIS as a Geospatial Computational Engine. FOSS4G NA St. Louis, September 9-11, 2024

== Roadmap ==
;Mentoring program (fall 2023 - summer 2025)
:Free developer-oriented mentoring program to support researchers and software developers to integrate GRASS GIS into their workflows and contribute to GRASS GIS.

; Streamline contributor onboarding (spring 2024 - fall 2024)
: Includes updating and creating guidelines for code and non-code contributions.

; Streamline user onboarding (spring 2024 - fall 2024)
: Includes modernizing tool documentation, developing tutorials.
: Creating sample datasets for localized tutorials.
: Developing online training materials for big data processing.

; Training sessions (fall 2023 - summer 2025)
: Local training sessions (at universities and conferences) introducing GRASS GIS to students and researchers.
: Training program for big data processing delivered online.

; Engaging industry partners (January - August 2024)
: Identify and engage industry partners to gather feedback and to start industry partnership program.

; Conferences
: Presence (talks, workshops, networking) at FOSS4GNA 2023, FOSS4G Asia 2023, AGU 2023, CSDMD 2024, FOSS4G Europe 2024, FOSS4G 2024, AGU 2024

; Community sprints
: Virtual or in-person participation in OSGeo community sprints, GRASS GIS community sprints

; Software distribution (January 2024 - December 2024)
: Transition to CMake build system
: Develop conda package

;Simplify maintenance of GRASS integrations with QGIS and R (2024-2025)
: Virtual meetings with QGIS and R developers and GRASS GIS developers (spring 2024).
: Identify and implement improvements to the integration.

;Improve code quality, security, and quality assurance
: Code quality (Flake8, Pylint, Cppcheck), first half of 2024.
: Security (CodeQL), second half of 2024.
: Quality assurance (better pytest integration), second half of 2024.

; In-person developer summit (spring/summer 2025)
: Hosted by NC State University, Raleigh, NC, USA.
: Identify additional challenges for adoption of GRASS GIS as geoprocessing engine.
: Long-term planning beyond the POSE project.

== Acknowledgements ==

The funding is provided by the U.S. National Science Foundation, award 2303651.
[[File:NSF Official logo.png|frameless|left]]

[[Category: Community]]
[[Category: Conferences‏‎]]
[[Category: 2023]]
[[Category: 2024]]
[[Category: 2025]]

NSF POSE Project 2023-2025 Timeline

2024-08-26T17:32:33Z

Ctwhite:

[[File:NSF_grant_announcement.png|500px|right|none]]

To inform GRASS community about the work done as part of the award [https://www.nsf.gov/awardsearch/showAward?AWD_ID=2303651 2303651] from the U.S. National Science Foundation (NSF) to enhance GRASS ecosystem, the following report summarizes the progress and outcomes in quarterly reports and presents the roadmap for the project.

The two main goals of the project are: 1) to facilitate the adoption of GRASS GIS as a key geoprocessing engine by a growing number of researchers and geospatial practitioners in academia, governments, and industry; and 2) to expand and diversify the developer community, especially through supporting next-generation scientists to gain expertise to maintain and innovate GRASS software.

Principal investigators and senior personnel:

* Helena Mitasova, North Carolina State University (Principal Investigator)
* Vaclav Petras, North Carolina State University (Co-Principal Investigator)
* Anna Petrasova, North Carolina State University (Co-Principal Investigator)
* C Michael Barton, Arizona State University (Co-Principal Investigator)
* Huidae Cho, New Mexico State University (Co-Principal Investigator)
* Giuseppe Amatulli, Yale (Senior Personnel)

Other personnel who is joining for the execution of the grant is listed below when relevant.

== 1st quarter report ==
=== Project Announcements and Communication ===
* Announcement on [https://grass.osgeo.org/news/2023_09_06_nsf_grant_awarded/ GRASS website].
* Info session to explain the POSE Project ([https://lists.osgeo.org/pipermail/grass-user/2023-September/083423.html Announcement on GRASS user mailing list], 2 sessions for different time zones).
* Collected statistics from GitHub, X and others and set up automated collection for GitHub.

=== Conference Presentations ===
* [https://petrasovaa.github.io/FUTURES-CONUS-talk/foss4gNA2023.html#/ Parallelization Tips for Geoprocessing with GRASS GIS] by Anna Petrasova at FOSS4GNA, October 2023.
* [https://wenzeslaus.github.io/grass-gis-talks/foss4gna2023.html#/ GRASS GIS: Not What You Think] by Vaclav Petras at FOSS4GNA, October 2023.
* [https://docs.google.com/presentation/d/1D-Fh1cLSPINyeXdVaxlakrE9IjB8kK5lIw3D12yX1bk Computational Notebooks for Reproducible Geospatial Computation in Research and Education] by Caitlin Haedrich at FOSS4GNA, October 2023.
* [https://github.com/HuidaeCho/grass-gis-talk-foss4g-asia-2023 State of GRASS GIS: 40 Years Strong and Counting] by Huidae Cho at FOSS4G Asia, November 2023.

=== Training and Workshops ===
* [https://github.com/ncsu-geoforall-lab/grass-gis-workshop-foss4gna-2023 Unlock the power of GRASS GIS] by Anna Petrasova and Caitlin Haedrich at FOSS4GNA, October 2023.
* [https://github.com/ncsu-geoforall-lab/develop-tools-with-grass-foss4gna-2023 Develop Geospatial Workflows and Custom Tools with GRASS GIS] by Vaclav Petras and Corey White at FOSS4GNA, October 2023.
* [https://github.com/ncsu-geoforall-lab/grass-workshop-gis-week-2023 Big Data Computing with GRASS GIS] by Anna Petrasova and Vaclav Petras at NC State GIS week, November 2023.
* [https://github.com/ncsu-geoforall-lab/grass-gis-on-hpc-henry2/blob/8564c72e9b8929c9ef4d25ada1ef36b569991221/docs/tutorial.md GIS Week Workshop: High Performance Computing for Geospatial Analysis (GRASS GIS part)] by Vaclav Petras (main lecture lead by Andrew Petersen from NCSU OIT) at NC State GIS week, November 2023.
* [https://spatial-ecology.net/docs/build/html/index.html Geocomputation and Machine Learning for Environmental Applications] training course [https://spatial-ecology.net/course-geocomputation-machine-learning-for-environmental-applications-intermediate-level-2024/ announced]. GRASS GIS part led by Giuseppe Amatulli is free of charge thanks to the support by NSF.

=== Community Sprint Participation ===
Anna Petrasova and Vaclav Petras remotely participated in [https://wiki.osgeo.org/wiki/OSGeo_Community_Sprint_2023 OSGeo 2023 code sprint] doing PR reviews and maintenance of GRASS GIS code, documentation, and website.

=== Mentoring Program ===
* Started a development-oriented mentoring program [https://grass.osgeo.org/news/2023_10_11_mentoring_program_announced/ announced] with details available on a [https://grasswiki.osgeo.org/wiki/Mentoring_Program wiki page].
* Program now has 4 participants (from 12 responses) supported by email and video calls.
* Program already resulted in improvements to GRASS GIS core and addons:
** merged PR: [https://github.com/OSGeo/grass/pull/3206 grass.script: ensure memmap content is flushed before writing to a raster]
** radar addon toolset PR: [https://github.com/OSGeo/grass-addons/pull/949 Add i.saocom and i.sar toolsets]
Mentoring Program is a new effort started and so-far performed only by the POSE team.

=== Student Grants Program ===
Student grants [https://grass.osgeo.org/news/2023_11_09_student_grants_announced/ announced] with topics at a [https://grasswiki.osgeo.org/wiki/GRASS_GIS_Student_Grants wiki page]. Student Grants Program is an existing effort which the POSE team participates in.

=== Working Groups ===

Four [https://grasswiki.osgeo.org/wiki/Working_Groups working groups] created (scope, wiki page, coordinator, and a list of people for each).

=== Citations ===

* GRASS GIS Google Scholar [https://scholar.google.com/citations?user=gJ0ZB0cAAAAJ account] updated with more complete records.
* A [https://forms.gle/cDEvMJu7d6nvxLKn9 form] was created to collect new and missing records.
* Profile link added to GRASS website [https://grass.osgeo.org/contribute/ Contribute] and [https://grass.osgeo.org/about/citation/ Citation] page.

== 2nd quarter report ==
=== NSF I-Corps program ===
Corey White, Vaclav Petras, and Anna Petrasova participated in a 4-week long intensive mandatory training that draws on the methods, customer discovery, and curriculum of the [https://new.nsf.gov/funding/initiatives/i-corps NSF Innovation Corps] and applies them to open-source projects.

The program included conducting 70+ 30-minute interviews with both GRASS users and non-users to better shape the future path of GRASS GIS and the POSE project. So far, the interviews focused on educators, companies, researchers, influencers and it focused more on non-users than users.

Next steps, include processing the collected qualitative data, developing possible future directions for sustainability of the project, discussing these with the Project Steering Committee, the core team of developers, and the broader community.

=== Mentoring Program ===
The development oriented [https://grass.osgeo.org/news/2023_10_11_mentoring_program_announced/ mentoring program] welcomed 5 new participants from various institutions including universities, USGS, US Army Corps of Engineers, and local municipalities. The discussed topics covered developing workflows for topography and network analysis, environmental modeling, and geophysics. Participants were supported by email and video calls.

=== Conference Presentations ===
* [https://agu.confex.com/agu/fm23/meetingapp.cgi/Paper/1342418 Modeling vegetated stream buffer impacts on water depth and discharge at the watershed scale with GRASS GIS and Jupyter Notebooks] by Caitlin Haedrich at AGU, December 2023.
* [https://agu.confex.com/agu/fm23/meetingapp.cgi/Paper/1420596 OpenPlains: A Web-Based Platform to Democratize Geospatial Participatory Modeling on the Cloud] by Corey White at AGU, December 2023.

=== Presentations and Workshops ===
* [https://github.com/ncsu-geoforall-lab/grass-gis-workshop-vanderbilt-2024 Intro to GRASS GIS] by Vaclav Petras and Anna Petrasova was remotely delivered to geographers at Vanderbilt University in February 2024. The workshop was developed in Jupyter Lab and run using [https://wholetale.org WholeTale] online platform.
* [https://github.com/tomorrownow/intro-to-geoprocessing-workshop Introduction to GRASS GIS Geospatial Processing] by Corey White at [https://smathhacks.ncssm.edu/ SMathHacks hackathon], March 2nd (supported also by Veronica Andreo and Vaclav Petras). SMathHacks is the annual 36-hour hackathon hosted by the NC School of Science and Math, open to all North Carolina students. Students collaborate to build innovative software projects, explore new technologies, and have fun along the way. The workshop was delivered in person with students using [https://colab.research.google.com/ Google Colab].

=== Student Grant Program ===
Linda Karlovska participates in the [https://grasswiki.osgeo.org/wiki/GRASS_GIS_Student_Grants Student Grant program] with her project [https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/EasyCommandHistoryNavigation Easy command history navigation through the History browser panel] mentored by Anna Petrasova (POSE team) and Martin Landa (FCE CTU). Student Grants Program is an existing effort which the POSE team participates in by mentoring.

=== Code Security ===
Vaclav Petras mentors four students who create code security improvements in their NCSU class ''CSC 472: Cybersecurity Practicum''. So far, the students created two PRs which were successfully merged:
* [https://github.com/OSGeo/grass/pull/3444 grass.script: Change insecure mktemp to NamedTemporaryFile #3444]
* [https://github.com/OSGeo/grass/pull/3451 utils: fixed shell vulnerability in mkrest.py #3451]

Two other PRs are open and more work is underway to do first steps for new approach to a more secure code.

=== Localized Basic Datasets ===
* NCSU and ASU teams worked on localized versions of GRASS basic data set following the [https://grass.osgeo.org/sampledata/north_carolina/nc_basic_spm_grass7.zip North Carolina basic data set example], preparing Flagstaff, Arizona and Nepal draft version with basic layers

== 3rd quarter report ==

=== Mentoring Activities ===
The mentoring program form received 2 new responses and mentors were actively working with 3 mentees.
It resulted in fixes in [https://github.com/OSGeo/grass-addons/pull/1042 v.transects] and [https://github.com/OSGeo/grass-addons/pull/1077 r.accumulate].

Linda Kladivova finished her project developing [https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/EasyCommandHistoryNavigation History browser] in the GRASS GUI as part of the GRASS Student Grant Program. Mentor's time was covered by POSE.

GRASS GIS has [https://grass.osgeo.org/news/2024_05_27_gsoc_2024_students/ 3 students this year for Google Summer of Code]. Time spent managing GSoC for GRASS GIS was covered by POSE.

The topics covered by GSoC projects are:
* [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_2024_EODAG_Support Add EODAG support to GRASS GIS]
* [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_2024_Improve_user_experience_in_Jupyter_Notebooks Improve GRASS user experience in Jupyter Notebook]
* [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_2024_Add_JSON_output Add JSON output to different GRASS tools in C]

=== Presentations, Workshops, Event Planning ===
* [https://github.com/ncsu-geoforall-lab/tngic-2024 GRASS 101: From GUI Clicks to Writing Scripts (TNGIC 2024)] by Veronica Andreo and Caitlin Haedrich
* [https://github.com/ncsu-geoforall-lab/csdms-grass-2024 Coastal evolution analysis and inundation modeling with GRASS GIS (CSDMS Workshop 2024)] by Caitlin Haedrich and Pratikshya Regmi, see also [https://cnr.ncsu.edu/geospatial/news/2024/06/03/students-teach-grass-gis-for-coastal-hazard-analysis/ blog post with images]

* Organization of [[GRASS Community Meeting Prague 2024]] and budget planning by Vaclav Petras

=== CMake transition ===
Ongoing work on [https://github.com/OSGeo/grass/pull/3621 CMake compilation] was partially covered by POSE.

=== Code Quality and Security ===

Code quality improvements in Python code:
* [https://github.com/OSGeo/grass/pull/3541 PR addressing Flake8 E501] (long lines in 158 files not fixable by automated tools)
* [https://github.com/OSGeo/grass/pull/3535 PR addressing Flake8 E401] (unused imports)

Vaclav Petras mentored a team of four students who create code security improvements in their NCSU class ''CSC 472: Cybersecurity Practicum''. The team created 12 PRs which were successfully merged, 7 additional experimental PRs (not merged) and 2 PRs which are still open at this time. Specifically, the team achieved the following:

* With the involvement and help from the other contributors, the team introduced Bandit and Coverity Scan as additional code scanning tools for Python and C, respectively.
* The team analyzed issues reported CodeQL, Bandit, and Coverity Scan and reported on relevance of different issues to the project (report privately shared with the GRASS Development Team).
* Vulnerability Triage Guide (also privately shared with the GRASS Development Team).
* The team also developed a [https://github.com/OSGeo/grass/security/policy security policy] for the project.
* The vulnerability reporting and security advisories were enabled based on the team recommendations.
* The team fixed several specific security issues in the code:
** [https://github.com/OSGeo/grass/pull/3469 packaging: Use subprocess instead of os.popen for change log creation #3469] (merged)
** [https://github.com/OSGeo/grass/pull/3549 lib raster: fixed security vulnerabilities and weaknesses #3549] (merged)
** [https://github.com/OSGeo/grass/pull/3451 utils: fixed shell vulnerability in mkrest.py #3451] (merged)
** [https://github.com/OSGeo/grass/pull/3444 grass.script: Change insecure mktemp to NamedTemporaryFile #3444] (merged)
** [https://github.com/OSGeo/grass/pull/3551 lib/psdriver: Fix issues with wrong type of arguments to printf #3551] (PR open)
** [https://github.com/OSGeo/grass/pull/3452 g.region/r.to.rast3elev: fixed scanf error to recognize EOF as a possible return value #3452] (PR open)

=== Documentation ===
* Documentation and Education Working Group met and planned the development of new tutorials. Veronica Andreo met other GRASS developers and contributors to coordinate further tutorials development.
* Development of new [https://github.com/ncsu-geoforall-lab/tutorials tutorials] in progress, topics include:
** Getting started with GRASS GIS
** GRASS GIS in Google Colab
** GRASS GIS and Python
** GRASS GIS and R
** GRASS R and Python comparison
** Making plots in GRASS GIS
* New [https://github.com/OSGeo/grass/blob/main/doc/development/style_guide.md GRASS Programming Style Guide]
* [https://github.com/petrasovaa/cookiecutter-grass-addon New addon template powered by Cookiecutter]
* Analysis of options names and functionality in plotting tools:
** [https://github.com/OSGeo/grass-addons/issues/1071 Addons for plotting: Standardize parameters and flags]

=== Communication and outreach ===

* Creation of 4 news post in the [https://grass.osgeo.org/news/ GRASS website]
* Social media:
** [https://twitter.com/GRASSGIS Twitter]: 9 new posts/threads
** [https://fosstodon.org/@grassgis Fosstodon]: 9 new posts/threads

=== Other sustainability activities ===
* [https://github.com/OSGeo/grass/blob/main/CODE_OF_CONDUCT.md Code of Conduct added to the main repository]
* [https://github.com/OSGeo/grass/blob/main/.github/ISSUE_TEMPLATE/bug_report.md revised Issue template]
* New [https://github.com/OSGeo/grass/pull/3673 RFC for a Release Policy]
* Revised [https://github.com/OSGeo/grass/pull/2815 RFC for Release Procedure]
* WIP: GRASS GIS Roadmap
* [https://github.com/OSGeo/grass-website/issues/414 GRASS website: ongoing restructuring]
* [[PSC]] page moved from trac wiki to media wiki

== 4th quarter report ==

=== Mentoring Activities ===
The mentoring program form received 3 new responses and mentors were actively working with 3 mentees.
Results include parallelization of r.texture, r.horizon, improved grass.benchmarking library and a new tutorial on lidar data.

GSoC successfully completed their projects:
* [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_2024_EODAG_Support Add EODAG support to GRASS GIS]
* [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_2024_Improve_user_experience_in_Jupyter_Notebooks Improve GRASS user experience in Jupyter Notebook]
* [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_2024_Add_JSON_output Add JSON output to different GRASS tools in C]

Time spent by mentoring was covered by NSF.

=== Presentations, Workshops, Event Planning ===

* [https://veroandreo.github.io/grass_foss4geu_2024/ Let's combine GRASS, Python and R: Satellite time series data for species distribution modeling]. Workshop by Veronica Andreo. FOSS4G Europe 2024, Tartu.
* [https://veroandreo.github.io/grass-gis-talks/foss4gEU2024.html#/ Status of GRASS GIS project]. Talk by Veronica Andreo. FOSS4G Europe 2024, Tartu.
* [https://veroandreo.github.io/grass-gis-talks/useR2024.html#/ Boost Spatial Data Science Workflows with GRASS GIS and R]. Talk by Veronica Andreo. useR Conference 2024, Salzburg.
* [https://ncsu-geoforall-lab.github.io/usdoi-webinar/notebooks/grass_jupyter.html Geoprocessing with GRASS GIS and Jupyter Notebooks]. Webinar by Corey White. U.S. DOI, August 2024, NCSU.
* [[GRASS Community Meeting Prague 2024]]

* Planning GRASS Dev summit 2025 at NCSU

* Planning AGU (4 abstract submitted), AGU booth for GRASS GIS reserved and payed

=== CMake transition ===
Ongoing work on [https://github.com/OSGeo/grass/pull/3621 CMake compilation] was partially covered by POSE.

=== Code Quality and Security ===

* Code quality improvements in Python code:
** [https://github.com/OSGeo/grass/pull/3763 Flake8 W605 Invalid escape sequence #3763]
** [https://github.com/OSGeo/grass/pull/3926 Flake8 E741 Do not use variables named 'I', 'O', or 'l' in wxGUI code #3926]
** [https://github.com/OSGeo/grass/pull/3928 Flake8 E741 for the rest of code base #3928]
** [https://github.com/OSGeo/grass/pull/4200 grass.temporal: Flake8 F841 Local variable assigned to but never used #4200]
** [https://github.com/OSGeo/grass/pull/4113 grass.pygrass: Remove unused arg in ctypes.CFUNCTYPE #4113]
** [https://github.com/OSGeo/grass/pull/4206 t.rast.to.vect: Fix passing column parameter to r.to.vect, fix flake8 F841 #4206]

* Code quality and security improvements in C and C++ code are in 36 PRs with fixes for more than 25 tools, specifically in:
** raster: r.path, r.out.mpeg, r.out.png, r.in.xyz, r.terraflow, r.statistics, r.spreadpath, r.sim.water, r.sim.erosion, r.object.geometry, r.coin
** imagery: i.atcorr, i.aster.toar, i.ortho.photo, i.landsat.acca, i.segment, i.smap
** display: d.linegraph, d.legend.vect, d.histogram, d.labels
** raster 3D: r3.in.v5d, r3.info, r3.mapcalc
** other: lib/gis, lib/vector/diglib, g.findfile, g.setproj, ps.map, lib/cdhc

Changes by author: [https://github.com/OSGeo/grass/pulls?q=author%3AShubhamDesai+is%3Apr+is%3Aclosed+merged%3A2024-06-01..2024-08-31+base%3Amain+sort%3Aupdated-desc+ ShubhamDesai], [https://github.com/OSGeo/grass/pulls?q=author%3Amshukuno+is%3Apr+is%3Aclosed+merged%3A2024-06-01..2024-08-31+base%3Amain+sort%3Aupdated-desc+ Makiko Shukunobe], [https://github.com/OSGeo/grass/pulls?q=author%3Aymdatta+is%3Apr+is%3Aclosed+merged%3A2024-06-01..2024-08-31+base%3Amain+sort%3Aupdated-desc+ ymdatta]

Fixed issues were reported by Flake8, Coverity Scan, and Cppcheck.

=== Documentation ===

* Veronica Andreo met some GRASS developers and contributors to follow up on tutorials development.
* 7 new [https://github.com/ncsu-geoforall-lab/tutorials tutorials] on time series:
** Management and visualization
** Aggregation
** Algebra
** Accumulation
** Gap filling
** Querying raster time series with vectors
** Subset, import and export
* Tutorial on how to set up Jupyter and GRASS in Windows
* PR template created - [https://github.com/OSGeo/grass/community GitHub Community Standards] all checked complete

=== Communication and outreach ===

* Creation of 4 news post in the [https://grass.osgeo.org/news/ GRASS website]
* Social media:
** [https://twitter.com/GRASSGIS Twitter]: 25 new posts
** [https://fosstodon.org/@grassgis Fosstodon]: 25 new posts
* Requested transition of [https://discourse.osgeo.org/t/osgeo-3255-migrate-grass-dev-mailing-list-to-discourse/49796 grass-dev mailing list to discourse.osgeo.org]
* Set up GRASS GIS swag shop on Redbubble

=== Governance ===
* Roadmap
* PSC elections:
** Documented criteria to define people entitled to vote
** Documented procedure to compile the list of voters
** Elections announcement sent out

== Roadmap ==
;Mentoring program (fall 2023 - summer 2025)
:Free developer-oriented mentoring program to support researchers and software developers to integrate GRASS GIS into their workflows and contribute to GRASS GIS.

; Streamline contributor onboarding (spring 2024 - fall 2024)
: Includes updating and creating guidelines for code and non-code contributions.

; Streamline user onboarding (spring 2024 - fall 2024)
: Includes modernizing tool documentation, developing tutorials.
: Creating sample datasets for localized tutorials.
: Developing online training materials for big data processing.

; Training sessions (fall 2023 - summer 2025)
: Local training sessions (at universities and conferences) introducing GRASS GIS to students and researchers.
: Training program for big data processing delivered online.

; Engaging industry partners (January - August 2024)
: Identify and engage industry partners to gather feedback and to start industry partnership program.

; Conferences
: Presence (talks, workshops, networking) at FOSS4GNA 2023, FOSS4G Asia 2023, AGU 2023, CSDMD 2024, FOSS4G Europe 2024, FOSS4G 2024, AGU 2024

; Community sprints
: Virtual or in-person participation in OSGeo community sprints, GRASS GIS community sprints

; Software distribution (January 2024 - December 2024)
: Transition to CMake build system
: Develop conda package

;Simplify maintenance of GRASS integrations with QGIS and R (2024-2025)
: Virtual meetings with QGIS and R developers and GRASS GIS developers (spring 2024).
: Identify and implement improvements to the integration.

;Improve code quality, security, and quality assurance
: Code quality (Flake8, Pylint, Cppcheck), first half of 2024.
: Security (CodeQL), second half of 2024.
: Quality assurance (better pytest integration), second half of 2024.

; In-person developer summit (spring/summer 2025)
: Hosted by NC State University, Raleigh, NC, USA.
: Identify additional challenges for adoption of GRASS GIS as geoprocessing engine.
: Long-term planning beyond the POSE project.

== Acknowledgements ==

The funding is provided by the U.S. National Science Foundation, award 2303651.
[[File:NSF Official logo.png|frameless|left]]

[[Category: Community]]
[[Category: Conferences‏‎]]
[[Category: 2023]]
[[Category: 2024]]
[[Category: 2025]]

Talk:GRASS Community Meeting Prague 2024

2024-07-09T19:55:42Z

Ctwhite:

{{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)
* Participated in the roadmap discussion session.
* Participated in the documentation discussion session.
* Lead website discussion session.

=== 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])
* Unit tests for [https://github.com/OSGeo/grass/tree/main/raster/r.out.gdal r.out.gdal] ([https://github.com/OSGeo/grass/pull/3903 PR #3903])
* 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, sparked by [https://www.linkedin.com/feed/update/urn:li:activity:7208372306924994560?commentUrn=urn%3Ali%3Acomment%3A%28activity%3A7208372306924994560%2C7208521495923306496%29&dashCommentUrn=urn%3Ali%3Afsd_comment%3A%287208521495923306496%2Curn%3Ali%3Aactivity%3A7208372306924994560%29 Tom Hengl's remarks]:
** 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 [https://grass.osgeo.org/grass83/manuals/libpython/pygrass.modules.grid.html GridModule] class 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
* Worked with Markus to create a repo for addon template https://github.com/OSGeo/grass-addon-cookiecutter

=== 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 - 45 PRs), especially for tool parallelization, JSON outputs, code quality
* Participated in discussions: project roadmap, interfacing with QGIS, website, parallelization (including default number of cores used), continuous integration (CI), and testing
* PRs for contributor documentation, release notes, and automation (8 PRs)
* Work on RC1 (version updates, release notes, coordination)
* Reviews of social media post co-authored with the NC State European Center (venue).
* Venue organizing and hosting

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

* i.atcorr: bug fixing, refactoring, speeding up ([https://github.com/OSGeo/grass/pull/3911 PR #3911], [https://github.com/OSGeo/grass/pull/3886 PR #3886], [https://github.com/OSGeo/grass/pull/3806 PR #3806])
* g.gui.gmodeler: bug fixing, refactoring ([https://github.com/OSGeo/grass/pull/3881 PR #3881], [https://github.com/OSGeo/grass/pull/3865 PR #3865], [https://github.com/OSGeo/grass/pull/3816 PR #3816])
* work on docs, general code cleaning, refactoring, style ([https://github.com/OSGeo/grass/pulls?q=+is%3Apr+author%3Apesekon2+created%3A%3E%3D2024-06-13+ list of PRs])
* PR reviews

=== Martin Landa ===

* work on docs migration from HTML to Markdown: [https://github.com/OSGeo/grass/pull/3849 #3849]
* GRASS_CONFIG_DIR (together with Ivan Mincik): [https://github.com/OSGeo/grass/pull/3899 #3899]
* PR reviews

=== Ivan Mincik ===

* GRASS GIS in Geospatial NIX
* GRASS_CONFIG_DIR (together with Martin Landa): [https://github.com/OSGeo/grass/pull/3899 #3899]

=== Linda Karlovska ===

* work on the History panel - new mechanism for command ordering, optimization of node refreshes, bigger refactoring: [https://github.com/OSGeo/grass/pull/3896 #3896]

Talk:GRASS Community Meeting Prague 2024

2024-06-15T10:22:31Z

Ctwhite:

{{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])

=== Veronica Andreo ===

* Discuss tutorial topics with Alen
* Reviewed PRs: i.eodag, a couple related to the temporal framework
* 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.

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

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