GRASS-Wiki - User contributions [en]

PSC Meeting 2026-05-08

2026-05-07T20:27:10Z

Nila: Add RFC on C11 atomic note

== Participants ==

* TBD

== Agenda ==

The topics proposed are:

* Review action points from previous meetings:
** Community Meeting (see below)
** Was Corey added to the list of GRASS people with access to the OSGeo server?
** Status of translation, grass-gui and grass-stats mailman lists?

* [[GRASS Community Meeting San Michele 2026]]
** Wiki created, [https://grass.osgeo.org/news/2026%2004%2022%20grass%20community%20meeting%20san%20michele%202026/ event announced], [https://grass.osgeo.org/ main page carousel updated]
** Agenda
** Rooms, food, housing
** FOSSGIS e.V. request: support needed to complete and submit the request

* Releases
** [https://github.com/OSGeo/grass/releases/tag/8.5.0RC1 8.5 RC1]
*** did anyone test it?
** How are we for 8.5.0?
** [https://github.com/OSGeo/grass/discussions/7328 GitHub Discussion: What to cut from our release procedure to simplify it? #7328]

* GSoC
** Support the mentees in maximizing a good use of AI to allow mentors spend time on higher level code reviews and open-source mentoring ''by purchasing a professional subscription for the mentees''?

* Funding/Sponsoring
** New sponsoring tiers at https://grass.osgeo.org/contribute/sponsoring/
** Updates from NumFocus?

* RFC
** New planned RFC to make C11's optional feature 'atomic support' required for 8.6

* ...
* add your topic here

== Minutes ==

[[Category:PSC]]

GRASS GSoC Ideas 2026

2026-03-12T07:11:03Z

Nila: add co-mentor

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

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

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

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

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

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

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

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

=== Parallelization of existing tools ===

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

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

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

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

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

=== Support writing tests with pytest ===

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

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

=== Fix known code defects ===

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

=== Subcommand CLI for GRASS ===

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

Current state:

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


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

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

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

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

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

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

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

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

=== Title of idea ===

Description here

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

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

{{GSoC}}

GRASS GSoC Ideas 2026

2026-03-12T07:09:31Z

Nila: add training task tools

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

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

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

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

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

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

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

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

=== Parallelization of existing tools ===

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

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

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

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

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

=== Support writing tests with pytest ===

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

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

=== Fix known code defects ===

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

=== Subcommand CLI for GRASS ===

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

Current state:

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


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

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

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

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

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

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

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

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

=== Title of idea ===

Description here

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

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

{{GSoC}}

Compiling on macOS using MacPorts

2026-01-28T17:48:47Z

Nila: Update with example from version 8.4.2

== Installing GRASS GIS with MacPorts ==

MacPorts is a package management system for macOS. It makes it easy to install and update any supported software — dependencies (that can be either executables or libraries) are installed and updated automatically. It is recommended to install the MacPort base software with the package installer available at [https://guide.macports.org macports.org] where also detailed installation and usage instructions can be found. Note that Xcode is a prerequisite and that MacPorts is controlled through the Terminal with the '''port''' command.

Assuming you succeeded with the installation of the MacPorts base, the base software can be updated with:
<pre>
sudo port selfupdate
</pre>

Information on software, i.e. ''ports'', that can be installed can be retrieved with the '''info''' action, this is an example with the port '''grass''' (which is the latest version):
<pre>
port info grass

grass @8.4.2 (gis)
Sub-ports: grass-gui
Variants: debug, debugoptimized, gui, mysql57, mysql8, openblas,
openmp, postgresql12, postgresql13, postgresql14,
postgresql15, postgresql16, [+]postgresql17, python310,
python311, python312, [+]python313, universal

Description: GRASS offers powerful raster, vector, and geospatial
processing engines in a single integrated software suite.
It includes tools for terrain and ecosystem modeling,
hydrology, visualization of raster and vector data,
management and analysis of geospatial data, and the
processing of satellite and aerial imagery. It comes with
a temporal framework for advanced time series processing
and a Python API for rapid geospatial programming. GRASS
has been optimized for performance and large geospatial
data analysis. Install the port `grass-gui` to enable
graphical user interface.
Homepage: https://grass.osgeo.org

Build Dependencies: bison, flex, pkgconfig
Library Dependencies: bzip2, cairo, fftw-3, freetype, gdal, geos, liblas, libpng,
libsvm, pdal, proj, readline, sqlite3, tiff, zlib,
postgresql17, python313, py313-Pillow, py313-numpy,
py313-six
Runtime Dependencies: py313-psycopg2
Platforms: darwin
License: GPL-2+
Maintainers: Email: n_larsson yahoo com, GitHub: nilason
Policy: openmaintainer
</pre>

The ''variants'' are options for a port that can be chosen at installation. The variants marked with a '''+''', are included by default.

Installing GRASS with default variants:
<pre>
sudo port install grass
</pre>
will download, compile and install GRASS with dependencies ''postgresql17'' and ''python313''.

However, a customized installation may look like:
<pre>
sudo port install grass +python312 +postgresql16
</pre>
which will replace the default ''python313'' with ''python312''. The default variants ''postgresql16'' will in this case also be included.

'''Note:''' you need to add '''grass-gui''' port to install wxPython for GRASS graphical user interface, this in not included by default:
<pre>
sudo port install grass-gui
</pre>

To check if any of the installed ports (or dependencies) have been updated:
<pre>
sudo port selfupdate
port outdated
</pre>

To update outdated ports:
<pre>
sudo port upgrade outdated
</pre>

== Using GRASS GIS installed with MacPorts ==

A standard installation of MacPorts will install ports at:
<pre>
/opt/local/
</pre>

Installation with the port ''grass-gui'' will also install an app bundle at:
<pre>
/Applications/MacPorts/GRASS-8.4.app
</pre>

You can start GRASS GIS from terminal with command:
<pre>
grass
</pre>
or
<pre>
/opt/local/bin/grass
</pre>

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

Compile and Install With CMake

2026-01-21T15:46:04Z

Nila: /* Install according to Filesystem Hierarchy Standard (FHS) -(DWITH_FHS) */

'''Disclaimer''': As of Spring 2025, the development of GRASS GIS using CMake is ongoing. Both the functionality of the CMake build system and the content of this documentation are subject to change.

== Building With CMake ==

It is strongly recommended to perform the build process with CMake in a separate directory, as opposed to the traditional approach of running `./configure && make` in the top-level directory of the source repository using Autotools. The designated build directory may be located anywhere.

A simple configuration, which creates a build directory named "build" (with -B argument) with current directory as source directory (with -S), can look like this:

cd grass_source_dir
cmake -B build -S .

Executing the building process is made with:

cmake --build build

A custom configuration may look like:

export CFLAGS="-DGL_SILENCE_DEPRECATION"
cd grass_source_dir
cmake -B build -S . -G Ninja \
-DCMAKE_PREFIX_PATH="/opt/local" \
-DWITH_OPENMP=ON
cmake --build build -v -j8

To clean up the configuration and build files (equivalent to `make distclean`):

cd grass_source_dir
rm -rf build

Install:

cmake --install build

It is possible to run GRASS for testing purposes in build directory:

./build/output/bin/grass

== Required Software for GRASS ==

Required software to build GRASS:

* [https://www.gnu.org/software/bison/ Bison]
* [https://cmake.org CMake] (version 3.22+)
* [https://github.com/westes/flex flex]
* [https://gdal.org/en/stable/ GDAL]
* [https://www.pcre.org PCRE] (required for MSVC only, on *NIX based platforms the Regex library is part of the system)
* [https://proj.org/ PROJ]
* [https://www.python.org Python] (version 3.9+)
* [https://zlib.net zlib]

== Optional Software and Configuration Flags ==

{| class="wikitable"
|+ Optional Libraries and Configuration Flags
|-
! Software !! Flag (BOOL) !! Default
|-
| bzip2 || WITH_BZLIB || OFF
|-
| Cairo || WITH_CAIRO || ON
|-
| CBLAS || WITH_CBLAS || ON
|-
| FFTW || WITH_FFTW || ON
|-
| FreeType || WITH_FREETYPE || ON
|-
| GEOS || WITH_GEOS || ON
|-
| LAPACKE || WITH_LAPACKE || ON
|-
| libLAS || WITH_LIBLAS || OFF
|-
| libpng || WITH_LIBPNG || ON
|-
| LibTIFF || WITH_TIFF || ON
|-
| MySQL || WITH_MYSQL || OFF
|-
| NetCDF || WITH_NETCDF || OFF
|-
| ODBC || WITH_ODBC || OFF
|-
| OpenGL || WITH_OPENGL || ON
|-
| OpenMP || WITH_OPENMP || OFF
|-
| PDAL || WITH_PDAL || ON
|-
| PostgreSQL || WITH_POSTGRES || ON
|-
| Readline || WITH_READLINE || ON
|-
| SQLite || WITH_SQLITE || ON
|-
| X11 || WITH_X11 || ON/OFF*
|-
| Zstandard || WITH_ZSTD || ON
|}

{| class="wikitable"
|+ Other Configuration Flags
|-
! Description !! Flag (BOOL) !! Default
|-
| Build documentation || WITH_DOCS || ON
|-
| Install according to Filesystem Hierarchy Standard (FHS) (full support after GRASS 8.5 release) || WITH_FHS || OFF
|-
| Build GUI || WITH_GUI || ON
|-
| Large file support || WITH_LARGEFILES || ON/OFF*
|-
| Build with National Language Support (NLS) || WITH_NLS || ON/OFF*
|-
| Use Ccache || USE_CCACHE || ON
|}

*) the default setting varies by platform.

=== Configuration Options ===

==== bzip2 (-DWITH_BZLIB) ====

[https://sourceware.org/bzip2/ bzip2] is a freely available high-quality data compressor.

The library is used by: GRASS General Library (GRASS GIS Library).

==== Cairo (-DWITH_CAIRO) ====

[https://www.cairographics.org Cairo] is a 2D graphics library with support for multiple output devices.

The library is used by: GRASS Cairo Display Driver and `g.cairocomp`.

==== CBLAS (-DWITH_CBLAS) ====

[https://www.netlib.org/blas/ CBLAS] C interface to the BLAS (Basic Linear Algebra Subprograms) which are routines that provide standard building blocks for performing basic vector and matrix operations.

The library is used by: GRASS numerical math interface (GRASS Math Library).

==== FFTW (-DWITH_FFTW) ====

[https://www.fftw.org FFTW] is a C subroutine library for computing the discrete Fourier transform (DFT) in one or more dimensions, of arbitrary input size, and of both real and complex data.

The library is used by: GRASS numerical math interface (GRASS Math Library), `i.fft` and `i.ifft`.

==== FreeType (-DWITH_FREETYPE) ====

[https://freetype.org FreeType] is a freely available software library to render fonts.

The library is used by: GRASS Display Driver, GRASS Cairo Display Driver and `v.label.sa`.

==== GEOS (-DWITH_GEOS) ====

[https://libgeos.org GEOS] is a C/C++ library for computational geometry with a focus on algorithms used in geographic information systems (GIS) software.

The library is used by: `v.buffer`, `v.profile` and `v.select`.

==== LAPACKE (-DWITH_LAPACKE) ====

[https://www.netlib.org/lapack/lapacke.html LAPACKE]is the C Interface to LAPACK, the Linear Algebra PACKage.

The library is used by: GRASS Vector Library, GRASS numerical math interface (GRASS Math Library) and GRASS Raster Library

==== libLAS (-DWITH_LIBLAS) ====

[https://liblas.org libLAS] is a C/C++ library for reading and writing the very common LAS LiDAR format.

The library is used by: `r.in.lidar`, `r3.in.lidar`, `v.in.lidar`, `v.lidar.correction`, `v.lidar.edgedetection`, `v.lidar.growing` and `v.out.lidar`.

==== libpng (-DWITH_LIBPNG) ====

[http://www.libpng.org/pub/png/ libpng] provides support for Portable Network Graphics (PNG) image file format.

The library is used by: GRASS PNG Display Driver Library, `r.in.png` and `r.out.png`.

==== LibTIFF (-DWITH_TIFF) ====

[https://libtiff.gitlab.io/libtiff/ LibTIFF] provides support for the Tag Image File Format (TIFF), a widely used format for storing image data.

The library is used by: GRASS OGSF Library.

==== MySQL (-DWITH_MYSQL) ====

[https://www.mysql.com MySQL] or [https://mariadb.org MariaDB] are two forks of a relational database.

The library is used by: GRASS DataBase MySQL driver.

==== NetCDF (-DWITH_NETCDF) ====

[https://www.unidata.ucar.edu/software/netcdf/ NetCDF] (Network Common Data Form) is a set of software libraries and machine-independent data formats that support the creation, access, and sharing of array-oriented scientific data.

The library is used by: `r3.out.netcdf`.

==== ODBC (-DWITH_ODBC) ====

[https://en.wikipedia.org/wiki/Open_Database_Connectivity Open Database Connectivity] (ODBC) is a standard application programming interface (API) for accessing database management systems (DBMS).

The library is used by: GRASS DataBase ODBC driver.

==== OpenGL (-DWITH_OPENGL) ====

[https://www.opengl.org OpenGL] (Open Graphics Library) is a cross-language, cross-platform application programming interface (API) for rendering 2D and 3D vector graphics.

The library is used by: GRASS OGSF Library and GRASS Nviz Library.

==== OpenMP (-DWITH_OPENMP) ====

[https://en.wikipedia.org/wiki/OpenMP OpenMP] is an application programming interface (API) that supports multi-platform shared-memory multiprocessing programming in C, C++, and Fortran, on many platforms, instruction-set architectures and operating systems.

The library is used by: GRASS numerical math interface (GRASS Math Library), GRASS Partial differential equations Library (GPDE), GRASS Library for interpolation with regularized splines with tension (RST), `r.mfilter`,
`r.neighbors`, `r.proj`, `r.resamp.filter`, `r.resamp.interp`, `r.series`, `r.series.accumulate`, `r.slope.aspect`, `r.sun`, `r.sim`, `r.univar`, `r3.univar` and `v.surf.rst`.

==== PDAL (-DWITH_PDAL) ====

[https://pdal.io/ PDAL] is a C++ library for translating and manipulating point cloud data.

The library is used by: `r.in.pdal` and `v.in.pdal`.

==== PostgreSQL (-DWITH_POSTGRES) ====

[https://www.postgresql.org PostgreSQL] is a powerful, open source object-relational database system.

The library is used by: GRASS DataBase PostgreSQL driver, GRASS General Library (GRASS GIS Library), `v.external` and `v.out.postgis`.

==== Readline (-DWITH_READLINE) ====

[https://www.gnu.org/software/readline/ Readline] library provides a set of functions for use by applications that allow users to edit command lines as they are typed in.

The library is used by: `r.mapcalc` and `r3.mapcalc`.

==== SQLite (-DWITH_SQLITE) ====

[https://www.sqlite.org SQLite] is a C-language library that implements a small, fast, self-contained, high-reliability, full-featured, SQL database engine.

The library is used by: GRASS DataBase SQLite driver and `g.version`.

==== X11 (-DWITH_X11) ====

[https://www.x.org/wiki/ X Window System] (X11) is a windowing system for bitmap displays, common on Unix-like operating systems.

The library is used by: GRASS Nviz Library, `g.cairocomp` and `ximgview`.

==== Zstandard (-DWITH_ZSTD) ====

[https://facebook.github.io/zstd/ Zstandard] is a fast compression algorithm, providing high compression ratios. It also offers a special mode for small data, called dictionary compression.

The library is used by: GRASS General Library (GRASS GIS Library).

==== Build documentation (-DWITH_DOCS) ====

==== Install according to Filesystem Hierarchy Standard (FHS) -(DWITH_FHS) ====
Full FHS support has not yet been implemented; the release following GRASS 8.5 is expected to be the first to provide such support.

==== Build GUI (-DWITH_GUI) ====

==== Large file support (-DWITH_LARGEFILES) ====

==== Build with National Language Support (-DWITH_NLS) ====

Requires: [https://www.gnu.org/software/gettext/ Gettext]

==== Use Ccache (-DUSE_CCACHE) ====

[https://ccache.dev Ccache] is a compiler cache. It speeds up recompilation by caching previous compilations and detecting when the same compilation is being done again.

Requires: Ccache

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

Compile and Install With CMake

2026-01-21T15:41:39Z

Nila: Note on FHS support

'''Disclaimer''': As of Spring 2025, the development of GRASS GIS using CMake is ongoing. Both the functionality of the CMake build system and the content of this documentation are subject to change.

== Building With CMake ==

It is strongly recommended to perform the build process with CMake in a separate directory, as opposed to the traditional approach of running `./configure && make` in the top-level directory of the source repository using Autotools. The designated build directory may be located anywhere.

A simple configuration, which creates a build directory named "build" (with -B argument) with current directory as source directory (with -S), can look like this:

cd grass_source_dir
cmake -B build -S .

Executing the building process is made with:

cmake --build build

A custom configuration may look like:

export CFLAGS="-DGL_SILENCE_DEPRECATION"
cd grass_source_dir
cmake -B build -S . -G Ninja \
-DCMAKE_PREFIX_PATH="/opt/local" \
-DWITH_OPENMP=ON
cmake --build build -v -j8

To clean up the configuration and build files (equivalent to `make distclean`):

cd grass_source_dir
rm -rf build

Install:

cmake --install build

It is possible to run GRASS for testing purposes in build directory:

./build/output/bin/grass

== Required Software for GRASS ==

Required software to build GRASS:

* [https://www.gnu.org/software/bison/ Bison]
* [https://cmake.org CMake] (version 3.22+)
* [https://github.com/westes/flex flex]
* [https://gdal.org/en/stable/ GDAL]
* [https://www.pcre.org PCRE] (required for MSVC only, on *NIX based platforms the Regex library is part of the system)
* [https://proj.org/ PROJ]
* [https://www.python.org Python] (version 3.9+)
* [https://zlib.net zlib]

== Optional Software and Configuration Flags ==

{| class="wikitable"
|+ Optional Libraries and Configuration Flags
|-
! Software !! Flag (BOOL) !! Default
|-
| bzip2 || WITH_BZLIB || OFF
|-
| Cairo || WITH_CAIRO || ON
|-
| CBLAS || WITH_CBLAS || ON
|-
| FFTW || WITH_FFTW || ON
|-
| FreeType || WITH_FREETYPE || ON
|-
| GEOS || WITH_GEOS || ON
|-
| LAPACKE || WITH_LAPACKE || ON
|-
| libLAS || WITH_LIBLAS || OFF
|-
| libpng || WITH_LIBPNG || ON
|-
| LibTIFF || WITH_TIFF || ON
|-
| MySQL || WITH_MYSQL || OFF
|-
| NetCDF || WITH_NETCDF || OFF
|-
| ODBC || WITH_ODBC || OFF
|-
| OpenGL || WITH_OPENGL || ON
|-
| OpenMP || WITH_OPENMP || OFF
|-
| PDAL || WITH_PDAL || ON
|-
| PostgreSQL || WITH_POSTGRES || ON
|-
| Readline || WITH_READLINE || ON
|-
| SQLite || WITH_SQLITE || ON
|-
| X11 || WITH_X11 || ON/OFF*
|-
| Zstandard || WITH_ZSTD || ON
|}

{| class="wikitable"
|+ Other Configuration Flags
|-
! Description !! Flag (BOOL) !! Default
|-
| Build documentation || WITH_DOCS || ON
|-
| Install according to Filesystem Hierarchy Standard (FHS) (full support after GRASS 8.5 release) || WITH_FHS || OFF
|-
| Build GUI || WITH_GUI || ON
|-
| Large file support || WITH_LARGEFILES || ON/OFF*
|-
| Build with National Language Support (NLS) || WITH_NLS || ON/OFF*
|-
| Use Ccache || USE_CCACHE || ON
|}

*) the default setting varies by platform.

=== Configuration Options ===

==== bzip2 (-DWITH_BZLIB) ====

[https://sourceware.org/bzip2/ bzip2] is a freely available high-quality data compressor.

The library is used by: GRASS General Library (GRASS GIS Library).

==== Cairo (-DWITH_CAIRO) ====

[https://www.cairographics.org Cairo] is a 2D graphics library with support for multiple output devices.

The library is used by: GRASS Cairo Display Driver and `g.cairocomp`.

==== CBLAS (-DWITH_CBLAS) ====

[https://www.netlib.org/blas/ CBLAS] C interface to the BLAS (Basic Linear Algebra Subprograms) which are routines that provide standard building blocks for performing basic vector and matrix operations.

The library is used by: GRASS numerical math interface (GRASS Math Library).

==== FFTW (-DWITH_FFTW) ====

[https://www.fftw.org FFTW] is a C subroutine library for computing the discrete Fourier transform (DFT) in one or more dimensions, of arbitrary input size, and of both real and complex data.

The library is used by: GRASS numerical math interface (GRASS Math Library), `i.fft` and `i.ifft`.

==== FreeType (-DWITH_FREETYPE) ====

[https://freetype.org FreeType] is a freely available software library to render fonts.

The library is used by: GRASS Display Driver, GRASS Cairo Display Driver and `v.label.sa`.

==== GEOS (-DWITH_GEOS) ====

[https://libgeos.org GEOS] is a C/C++ library for computational geometry with a focus on algorithms used in geographic information systems (GIS) software.

The library is used by: `v.buffer`, `v.profile` and `v.select`.

==== LAPACKE (-DWITH_LAPACKE) ====

[https://www.netlib.org/lapack/lapacke.html LAPACKE]is the C Interface to LAPACK, the Linear Algebra PACKage.

The library is used by: GRASS Vector Library, GRASS numerical math interface (GRASS Math Library) and GRASS Raster Library

==== libLAS (-DWITH_LIBLAS) ====

[https://liblas.org libLAS] is a C/C++ library for reading and writing the very common LAS LiDAR format.

The library is used by: `r.in.lidar`, `r3.in.lidar`, `v.in.lidar`, `v.lidar.correction`, `v.lidar.edgedetection`, `v.lidar.growing` and `v.out.lidar`.

==== libpng (-DWITH_LIBPNG) ====

[http://www.libpng.org/pub/png/ libpng] provides support for Portable Network Graphics (PNG) image file format.

The library is used by: GRASS PNG Display Driver Library, `r.in.png` and `r.out.png`.

==== LibTIFF (-DWITH_TIFF) ====

[https://libtiff.gitlab.io/libtiff/ LibTIFF] provides support for the Tag Image File Format (TIFF), a widely used format for storing image data.

The library is used by: GRASS OGSF Library.

==== MySQL (-DWITH_MYSQL) ====

[https://www.mysql.com MySQL] or [https://mariadb.org MariaDB] are two forks of a relational database.

The library is used by: GRASS DataBase MySQL driver.

==== NetCDF (-DWITH_NETCDF) ====

[https://www.unidata.ucar.edu/software/netcdf/ NetCDF] (Network Common Data Form) is a set of software libraries and machine-independent data formats that support the creation, access, and sharing of array-oriented scientific data.

The library is used by: `r3.out.netcdf`.

==== ODBC (-DWITH_ODBC) ====

[https://en.wikipedia.org/wiki/Open_Database_Connectivity Open Database Connectivity] (ODBC) is a standard application programming interface (API) for accessing database management systems (DBMS).

The library is used by: GRASS DataBase ODBC driver.

==== OpenGL (-DWITH_OPENGL) ====

[https://www.opengl.org OpenGL] (Open Graphics Library) is a cross-language, cross-platform application programming interface (API) for rendering 2D and 3D vector graphics.

The library is used by: GRASS OGSF Library and GRASS Nviz Library.

==== OpenMP (-DWITH_OPENMP) ====

[https://en.wikipedia.org/wiki/OpenMP OpenMP] is an application programming interface (API) that supports multi-platform shared-memory multiprocessing programming in C, C++, and Fortran, on many platforms, instruction-set architectures and operating systems.

The library is used by: GRASS numerical math interface (GRASS Math Library), GRASS Partial differential equations Library (GPDE), GRASS Library for interpolation with regularized splines with tension (RST), `r.mfilter`,
`r.neighbors`, `r.proj`, `r.resamp.filter`, `r.resamp.interp`, `r.series`, `r.series.accumulate`, `r.slope.aspect`, `r.sun`, `r.sim`, `r.univar`, `r3.univar` and `v.surf.rst`.

==== PDAL (-DWITH_PDAL) ====

[https://pdal.io/ PDAL] is a C++ library for translating and manipulating point cloud data.

The library is used by: `r.in.pdal` and `v.in.pdal`.

==== PostgreSQL (-DWITH_POSTGRES) ====

[https://www.postgresql.org PostgreSQL] is a powerful, open source object-relational database system.

The library is used by: GRASS DataBase PostgreSQL driver, GRASS General Library (GRASS GIS Library), `v.external` and `v.out.postgis`.

==== Readline (-DWITH_READLINE) ====

[https://www.gnu.org/software/readline/ Readline] library provides a set of functions for use by applications that allow users to edit command lines as they are typed in.

The library is used by: `r.mapcalc` and `r3.mapcalc`.

==== SQLite (-DWITH_SQLITE) ====

[https://www.sqlite.org SQLite] is a C-language library that implements a small, fast, self-contained, high-reliability, full-featured, SQL database engine.

The library is used by: GRASS DataBase SQLite driver and `g.version`.

==== X11 (-DWITH_X11) ====

[https://www.x.org/wiki/ X Window System] (X11) is a windowing system for bitmap displays, common on Unix-like operating systems.

The library is used by: GRASS Nviz Library, `g.cairocomp` and `ximgview`.

==== Zstandard (-DWITH_ZSTD) ====

[https://facebook.github.io/zstd/ Zstandard] is a fast compression algorithm, providing high compression ratios. It also offers a special mode for small data, called dictionary compression.

The library is used by: GRASS General Library (GRASS GIS Library).

==== Build documentation (-DWITH_DOCS) ====

==== Install according to Filesystem Hierarchy Standard (FHS) -(DWITH_FHS) ====

==== Build GUI (-DWITH_GUI) ====

==== Large file support (-DWITH_LARGEFILES) ====

==== Build with National Language Support (-DWITH_NLS) ====

Requires: [https://www.gnu.org/software/gettext/ Gettext]

==== Use Ccache (-DUSE_CCACHE) ====

[https://ccache.dev Ccache] is a compiler cache. It speeds up recompilation by caching previous compilations and detecting when the same compilation is being done again.

Requires: Ccache

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

Talk:GRASS Developer Summit Raleigh 2025

2025-05-22T12:06:07Z

Nila: /* Nicklas Larsson | Hungarian National Museum */

{{toc|right}}

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

== Organizing Team ==

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

== Detailed Schedule ==

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

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

Room: 5101-Executive Board Room

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

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

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

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

Room: 5101-Executive Board Room

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

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

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

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

Room: 5101-Executive Board Room

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

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

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

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

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

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

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

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

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

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

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

{| class="wikitable"
! Time !! Slot !!
|-
| 8:00-9:00 || Breakfast || On site. Start the day, meet people, and plan your personal agenda for the day.
|-
| 9:00-10:00 || Morning opening sessions || GRASS project's future course.
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 10:00-11:00 || PSC meeting || Project Steering Committee meets (public).
|-
| 11:00-11:20 || Self-organized feedback session || Your topic here
|-
| 11:20-11:40 || Self-organized feedback sessions || Your topic here
|-
| 11:40-12:00 || Self-organized feedback sessions || Your topic here
|-
| 12:00-13:00 || Lunch || Walk to [https://maps.app.goo.gl/kHVHY62QxTd6wHKd9 On the Oval Culinary Creatins]. Eat, drink, and continue the discussion from the feedback sessions.
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || Dinner on your own. Corey White will organize trip to downtown. Bus 41 from Hunt library to hotel and then walk.
|}

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

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

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

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

{| class="wikitable"
! Time !! Slot !!
|-
| 8:00-9:00 || Breakfast || TBA. Start the day, meet people, and plan your personal agenda for the day.
|-
| 9:00-10:00 || Morning opening sessions || NSF POSE project evaluation, contributor community feedback.
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || Your topic here (10-minute presentation and 10-minute discussion)
|-
| 11:20-11:40 || Self-organized feedback sessions || Your topic here
|-
| 11:40-12:00 || Self-organized feedback sessions || Your topic here
|-
| 12:00-13:00 || Lunch || TBA. Eat, drink, and continue the discussion from the feedback sessions.
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || TBA.
|}

== Daily tasks for participants ==

* List all the things you are working on in the Participant reports section below. Update the list each day. Include things you work on with other people.
* If you want to discuss something with the whole group, add yourself to a Self-organized feedback sessions slot in the schedule above or tell Vaclav (Vashek) Petras.
* For people with triage access and above: If you are or will be working on an issue or on a PR which is not originally submitted by you, assign yourself to the issue or PR. (You can unassign yourself later if you change your mind.)

== Participant reports ==

Per-person reports from the meeting.

=== Giuseppe Amatulli | Yale University ===

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

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

* [https://github.com/veroandreo?tab=overview&from=2025-05-12&to=2025-05-24 GitHub contributions]
* Website footer enhancement
* Sync icons on the Tutorials website footer to those on the main website
* Fix descriptions and their display in the tutorials website
* Fix GRASS page on OSGeo website [https://www.osgeo.org/projects/grass-gis/]
** Changed logo, removed GIS from the name, fixed old links
* Social media posts
* Discussion about hyperspectral with Alen and Anna
* Expand the GRASS acronym on the home page
* Remove GIS from GRASS name on the website
* Review tutorials by Huidae and Adam Smith
* GRASS PSC admin

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

* r.runoff

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

* POSE related activities

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

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

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

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

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

* CI optimization

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

* CMake, conda, CI, Mentoring

=== Edouard Choinière ===

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

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

=== Laurent Courty ===

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

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

* r.in.pdal

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

* A tool to calculate gravity terrain corrections

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

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

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

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

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

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

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

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

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

* Tutorial: GISMentors courses updated ([https://github.com/OSGeo/grass-tutorials/pull/45 PR])
* libgis: G__usage_markdown() include tool label in metadata if defined ([https://github.com/OSGeo/grass/pull/5677 PR])
* PyGRASS: Module description property not defined always ([https://github.com/OSGeo/grass/pull/5681 PR])
* Website: OpenGeoLabs commercial support ([https://github.com/OSGeo/grass-website/pull/537 PR])
* v.select: create output also when no features found ([https://github.com/OSGeo/grass/pull/5696 PR])
* wxGUI: avoid creating nested list of errors (Graphical modeler) ([https://github.com/OSGeo/grass/pull/5700 PR])
* wxGUI/gmodeler: refactor - move ModelParamDialog to dialogs.py ([https://github.com/OSGeo/grass/pull/5715 PR])
* GUI: make Python editor dockable ([https://github.com/OSGeo/grass/pull/5733 PR])

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

Planned work: CMake build system; perhaps Conda recipe

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

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

* Helped young students in build configuration and debugging techniques.

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

=== Chung-Yuan Liang ===

* parallelize some modules, improve testing

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

* r.in.pdal

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

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

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

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

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

=== Michael Mulqueen | MassGIS ===

* depth to water, hydro from lidar, etc

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

* Worked on a new raster data analysis tool r.smooth for inclusion into GRASS core
* Discussed architecture of hyperspectral data import and per-processing tool
* Discussed testing and organizing AI modules downloading data from internet
* Prepared and gave a presentation on code preparation for translations (best practice)

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

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

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

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

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

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

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

* Documentation

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

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

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

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

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

* improve the test coverage of imagery modules.

=== Krishna Prasad Sheshadri ===

*

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

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

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

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

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

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

* Previous work: coupling R and Python scripts for computational analysis in GRASS.
* Current work: Running through GRASS commands to create visual outputs that can be added to the new GRASS 8.5 manual pages. r.mapcalc, v.surf.rst, examples with topographic parameters. AND- Working on tutorial for Windows users to install a WSL2 Linux environment running Ubuntu 22.04LTS. Creates a conda environment with wxpython, then uses WSL2 to install GRASS from unstable repo without requiring OSGeo installer. Fast, minimal install. Preserves all the goofy windows python paths that get all tangled up with grass sometimes, and isolated distro can be completely removed if needed. Once set up it does not need special network routing through vpn. (For other uses that always wanted a more native feel to their grass instance!)
* Future work: Presenting on GRASS in JUNE at CERLCON.

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

* JSON, mentoring

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

* Discussed hydroflattening method
* Discussed direct point cloud input to v.surf.rst
* Learning git procedures by updating branding (GRASS GIS to GRASS) for raster commands
Tuesday
* Continued updating branding for raster commands
* Started working on tutorial for r.hydro.flatten

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

* r.sim.water

== Guests and remote participants ==

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

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

=== Markus Neteler | mundialis ===

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

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

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

Talk:GRASS Developer Summit Raleigh 2025

2025-05-22T12:04:28Z

Nila: /* Nicklas Larsson | Hungarian National Museum */

{{toc|right}}

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

== Organizing Team ==

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

== Detailed Schedule ==

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

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

Room: 5101-Executive Board Room

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

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

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

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

Room: 5101-Executive Board Room

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

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

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

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

Room: 5101-Executive Board Room

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

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

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

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

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

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

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

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

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

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

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

{| class="wikitable"
! Time !! Slot !!
|-
| 8:00-9:00 || Breakfast || On site. Start the day, meet people, and plan your personal agenda for the day.
|-
| 9:00-10:00 || Morning opening sessions || GRASS project's future course.
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 10:00-11:00 || PSC meeting || Project Steering Committee meets (public).
|-
| 11:00-11:20 || Self-organized feedback session || Your topic here
|-
| 11:20-11:40 || Self-organized feedback sessions || Your topic here
|-
| 11:40-12:00 || Self-organized feedback sessions || Your topic here
|-
| 12:00-13:00 || Lunch || Walk to [https://maps.app.goo.gl/kHVHY62QxTd6wHKd9 On the Oval Culinary Creatins]. Eat, drink, and continue the discussion from the feedback sessions.
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || Dinner on your own. Corey White will organize trip to downtown. Bus 41 from Hunt library to hotel and then walk.
|}

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

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

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

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

{| class="wikitable"
! Time !! Slot !!
|-
| 8:00-9:00 || Breakfast || TBA. Start the day, meet people, and plan your personal agenda for the day.
|-
| 9:00-10:00 || Morning opening sessions || NSF POSE project evaluation, contributor community feedback.
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || Your topic here (10-minute presentation and 10-minute discussion)
|-
| 11:20-11:40 || Self-organized feedback sessions || Your topic here
|-
| 11:40-12:00 || Self-organized feedback sessions || Your topic here
|-
| 12:00-13:00 || Lunch || TBA. Eat, drink, and continue the discussion from the feedback sessions.
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || TBA.
|}

== Daily tasks for participants ==

* List all the things you are working on in the Participant reports section below. Update the list each day. Include things you work on with other people.
* If you want to discuss something with the whole group, add yourself to a Self-organized feedback sessions slot in the schedule above or tell Vaclav (Vashek) Petras.
* For people with triage access and above: If you are or will be working on an issue or on a PR which is not originally submitted by you, assign yourself to the issue or PR. (You can unassign yourself later if you change your mind.)

== Participant reports ==

Per-person reports from the meeting.

=== Giuseppe Amatulli | Yale University ===

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

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

* [https://github.com/veroandreo?tab=overview&from=2025-05-12&to=2025-05-24 GitHub contributions]
* Website footer enhancement
* Sync icons on the Tutorials website footer to those on the main website
* Fix descriptions and their display in the tutorials website
* Fix GRASS page on OSGeo website [https://www.osgeo.org/projects/grass-gis/]
** Changed logo, removed GIS from the name, fixed old links
* Social media posts
* Discussion about hyperspectral with Alen and Anna
* Expand the GRASS acronym on the home page
* Remove GIS from GRASS name on the website
* Review tutorials by Huidae and Adam Smith
* GRASS PSC admin

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

* r.runoff

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

* POSE related activities

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

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

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

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

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

* CI optimization

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

* CMake, conda, CI, Mentoring

=== Edouard Choinière ===

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

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

=== Laurent Courty ===

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

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

* r.in.pdal

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

* A tool to calculate gravity terrain corrections

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

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

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

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

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

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

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

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

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

* Tutorial: GISMentors courses updated ([https://github.com/OSGeo/grass-tutorials/pull/45 PR])
* libgis: G__usage_markdown() include tool label in metadata if defined ([https://github.com/OSGeo/grass/pull/5677 PR])
* PyGRASS: Module description property not defined always ([https://github.com/OSGeo/grass/pull/5681 PR])
* Website: OpenGeoLabs commercial support ([https://github.com/OSGeo/grass-website/pull/537 PR])
* v.select: create output also when no features found ([https://github.com/OSGeo/grass/pull/5696 PR])
* wxGUI: avoid creating nested list of errors (Graphical modeler) ([https://github.com/OSGeo/grass/pull/5700 PR])
* wxGUI/gmodeler: refactor - move ModelParamDialog to dialogs.py ([https://github.com/OSGeo/grass/pull/5715 PR])
* GUI: make Python editor dockable ([https://github.com/OSGeo/grass/pull/5733 PR])

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

Planned work: CMake build system; perhaps Conda recipe

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

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

* Helped young students in build configuration and debugging techniques.

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

=== Chung-Yuan Liang ===

* parallelize some modules, improve testing

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

* r.in.pdal

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

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

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

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

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

=== Michael Mulqueen | MassGIS ===

* depth to water, hydro from lidar, etc

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

* Worked on a new raster data analysis tool r.smooth for inclusion into GRASS core
* Discussed architecture of hyperspectral data import and per-processing tool
* Discussed testing and organizing AI modules downloading data from internet
* Prepared and gave a presentation on code preparation for translations (best practice)

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

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

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

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

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

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

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

* Documentation

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

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

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

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

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

* improve the test coverage of imagery modules.

=== Krishna Prasad Sheshadri ===

*

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

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

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

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

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

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

* Previous work: coupling R and Python scripts for computational analysis in GRASS.
* Current work: Running through GRASS commands to create visual outputs that can be added to the new GRASS 8.5 manual pages. r.mapcalc, v.surf.rst, examples with topographic parameters. AND- Working on tutorial for Windows users to install a WSL2 Linux environment running Ubuntu 22.04LTS. Creates a conda environment with wxpython, then uses WSL2 to install GRASS from unstable repo without requiring OSGeo installer. Fast, minimal install. Preserves all the goofy windows python paths that get all tangled up with grass sometimes, and isolated distro can be completely removed if needed. Once set up it does not need special network routing through vpn. (For other uses that always wanted a more native feel to their grass instance!)
* Future work: Presenting on GRASS in JUNE at CERLCON.

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

* JSON, mentoring

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

* Discussed hydroflattening method
* Discussed direct point cloud input to v.surf.rst
* Learning git procedures by updating branding (GRASS GIS to GRASS) for raster commands
Tuesday
* Continued updating branding for raster commands
* Started working on tutorial for r.hydro.flatten

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

* r.sim.water

== Guests and remote participants ==

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

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

=== Markus Neteler | mundialis ===

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

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

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

Compile and Install With CMake

2025-03-20T15:48:40Z

Nila: run GRASS in build dir

'''Disclaimer''': As of Spring 2025, the development of GRASS GIS using CMake is ongoing. Both the functionality of the CMake build system and the content of this documentation are subject to change.

== Building With CMake ==

It is strongly recommended to perform the build process with CMake in a separate directory, as opposed to the traditional approach of running `./configure && make` in the top-level directory of the source repository using Autotools. The designated build directory may be located anywhere.

A simple configuration, which creates a build directory named "build" (with -B argument) with current directory as source directory (with -S), can look like this:

cd grass_source_dir
cmake -B build -S .

Executing the building process is made with:

cmake --build build

A custom configuration may look like:

export CFLAGS="-DGL_SILENCE_DEPRECATION"
cd grass_source_dir
cmake -B build -S . -G Ninja \
-DCMAKE_PREFIX_PATH="/opt/local" \
-DWITH_OPENMP=ON
cmake --build build -v -j8

To clean up the configuration and build files (equivalent to `make distclean`):

cd grass_source_dir
rm -rf build

Install:

cmake --install build

It is possible to run GRASS for testing purposes in build directory:

./build/output/bin/grass

== Required Software for GRASS ==

Required software to build GRASS:

* [https://www.gnu.org/software/bison/ Bison]
* [https://cmake.org CMake] (version 3.22+)
* [https://github.com/westes/flex flex]
* [https://gdal.org/en/stable/ GDAL]
* [https://www.pcre.org PCRE] (required for MSVC only, on *NIX based platforms the Regex library is part of the system)
* [https://proj.org/ PROJ]
* [https://www.python.org Python] (version 3.9+)
* [https://zlib.net zlib]

== Optional Software and Configuration Flags ==

{| class="wikitable"
|+ Optional Libraries and Configuration Flags
|-
! Software !! Flag (BOOL) !! Default
|-
| bzip2 || WITH_BZLIB || OFF
|-
| Cairo || WITH_CAIRO || ON
|-
| CBLAS || WITH_CBLAS || ON
|-
| FFTW || WITH_FFTW || ON
|-
| FreeType || WITH_FREETYPE || ON
|-
| GEOS || WITH_GEOS || ON
|-
| LAPACKE || WITH_LAPACKE || ON
|-
| libLAS || WITH_LIBLAS || OFF
|-
| libpng || WITH_LIBPNG || ON
|-
| LibTIFF || WITH_TIFF || ON
|-
| MySQL || WITH_MYSQL || OFF
|-
| NetCDF || WITH_NETCDF || OFF
|-
| ODBC || WITH_ODBC || OFF
|-
| OpenGL || WITH_OPENGL || ON
|-
| OpenMP || WITH_OPENMP || OFF
|-
| PDAL || WITH_PDAL || ON
|-
| PostgreSQL || WITH_POSTGRES || ON
|-
| Readline || WITH_READLINE || ON
|-
| SQLite || WITH_SQLITE || ON
|-
| X11 || WITH_X11 || ON/OFF*
|-
| Zstandard || WITH_ZSTD || ON
|}

{| class="wikitable"
|+ Other Configuration Flags
|-
! Description !! Flag (BOOL) !! Default
|-
| Build documentation || WITH_DOCS || ON
|-
| Install according to Filesystem Hierarchy Standard (FHS) || WITH_FHS || OFF
|-
| Build GUI || WITH_GUI || ON
|-
| Large file support || WITH_LARGEFILES || ON/OFF*
|-
| Build with National Language Support (NLS) || WITH_NLS || ON/OFF*
|-
| Use Ccache || USE_CCACHE || ON
|}

*) the default setting varies by platform.

=== Configuration Options ===

==== bzip2 (-DWITH_BZLIB) ====

[https://sourceware.org/bzip2/ bzip2] is a freely available high-quality data compressor.

The library is used by: GRASS General Library (GRASS GIS Library).

==== Cairo (-DWITH_CAIRO) ====

[https://www.cairographics.org Cairo] is a 2D graphics library with support for multiple output devices.

The library is used by: GRASS Cairo Display Driver and `g.cairocomp`.

==== CBLAS (-DWITH_CBLAS) ====

[https://www.netlib.org/blas/ CBLAS] C interface to the BLAS (Basic Linear Algebra Subprograms) which are routines that provide standard building blocks for performing basic vector and matrix operations.

The library is used by: GRASS numerical math interface (GRASS Math Library).

==== FFTW (-DWITH_FFTW) ====

[https://www.fftw.org FFTW] is a C subroutine library for computing the discrete Fourier transform (DFT) in one or more dimensions, of arbitrary input size, and of both real and complex data.

The library is used by: GRASS numerical math interface (GRASS Math Library), `i.fft` and `i.ifft`.

==== FreeType (-DWITH_FREETYPE) ====

[https://freetype.org FreeType] is a freely available software library to render fonts.

The library is used by: GRASS Display Driver, GRASS Cairo Display Driver and `v.label.sa`.

==== GEOS (-DWITH_GEOS) ====

[https://libgeos.org GEOS] is a C/C++ library for computational geometry with a focus on algorithms used in geographic information systems (GIS) software.

The library is used by: `v.buffer`, `v.profile` and `v.select`.

==== LAPACKE (-DWITH_LAPACKE) ====

[https://www.netlib.org/lapack/lapacke.html LAPACKE]is the C Interface to LAPACK, the Linear Algebra PACKage.

The library is used by: GRASS Vector Library, GRASS numerical math interface (GRASS Math Library) and GRASS Raster Library

==== libLAS (-DWITH_LIBLAS) ====

[https://liblas.org libLAS] is a C/C++ library for reading and writing the very common LAS LiDAR format.

The library is used by: `r.in.lidar`, `r3.in.lidar`, `v.in.lidar`, `v.lidar.correction`, `v.lidar.edgedetection`, `v.lidar.growing` and `v.out.lidar`.

==== libpng (-DWITH_LIBPNG) ====

[http://www.libpng.org/pub/png/ libpng] provides support for Portable Network Graphics (PNG) image file format.

The library is used by: GRASS PNG Display Driver Library, `r.in.png` and `r.out.png`.

==== LibTIFF (-DWITH_TIFF) ====

[https://libtiff.gitlab.io/libtiff/ LibTIFF] provides support for the Tag Image File Format (TIFF), a widely used format for storing image data.

The library is used by: GRASS OGSF Library.

==== MySQL (-DWITH_MYSQL) ====

[https://www.mysql.com MySQL] or [https://mariadb.org MariaDB] are two forks of a relational database.

The library is used by: GRASS DataBase MySQL driver.

==== NetCDF (-DWITH_NETCDF) ====

[https://www.unidata.ucar.edu/software/netcdf/ NetCDF] (Network Common Data Form) is a set of software libraries and machine-independent data formats that support the creation, access, and sharing of array-oriented scientific data.

The library is used by: `r3.out.netcdf`.

==== ODBC (-DWITH_ODBC) ====

[https://en.wikipedia.org/wiki/Open_Database_Connectivity Open Database Connectivity] (ODBC) is a standard application programming interface (API) for accessing database management systems (DBMS).

The library is used by: GRASS DataBase ODBC driver.

==== OpenGL (-DWITH_OPENGL) ====

[https://www.opengl.org OpenGL] (Open Graphics Library) is a cross-language, cross-platform application programming interface (API) for rendering 2D and 3D vector graphics.

The library is used by: GRASS OGSF Library and GRASS Nviz Library.

==== OpenMP (-DWITH_OPENMP) ====

[https://en.wikipedia.org/wiki/OpenMP OpenMP] is an application programming interface (API) that supports multi-platform shared-memory multiprocessing programming in C, C++, and Fortran, on many platforms, instruction-set architectures and operating systems.

The library is used by: GRASS numerical math interface (GRASS Math Library), GRASS Partial differential equations Library (GPDE), GRASS Library for interpolation with regularized splines with tension (RST), `r.mfilter`,
`r.neighbors`, `r.proj`, `r.resamp.filter`, `r.resamp.interp`, `r.series`, `r.series.accumulate`, `r.slope.aspect`, `r.sun`, `r.sim`, `r.univar`, `r3.univar` and `v.surf.rst`.

==== PDAL (-DWITH_PDAL) ====

[https://pdal.io/ PDAL] is a C++ library for translating and manipulating point cloud data.

The library is used by: `r.in.pdal` and `v.in.pdal`.

==== PostgreSQL (-DWITH_POSTGRES) ====

[https://www.postgresql.org PostgreSQL] is a powerful, open source object-relational database system.

The library is used by: GRASS DataBase PostgreSQL driver, GRASS General Library (GRASS GIS Library), `v.external` and `v.out.postgis`.

==== Readline (-DWITH_READLINE) ====

[https://www.gnu.org/software/readline/ Readline] library provides a set of functions for use by applications that allow users to edit command lines as they are typed in.

The library is used by: `r.mapcalc` and `r3.mapcalc`.

==== SQLite (-DWITH_SQLITE) ====

[https://www.sqlite.org SQLite] is a C-language library that implements a small, fast, self-contained, high-reliability, full-featured, SQL database engine.

The library is used by: GRASS DataBase SQLite driver and `g.version`.

==== X11 (-DWITH_X11) ====

[https://www.x.org/wiki/ X Window System] (X11) is a windowing system for bitmap displays, common on Unix-like operating systems.

The library is used by: GRASS Nviz Library, `g.cairocomp` and `ximgview`.

==== Zstandard (-DWITH_ZSTD) ====

[https://facebook.github.io/zstd/ Zstandard] is a fast compression algorithm, providing high compression ratios. It also offers a special mode for small data, called dictionary compression.

The library is used by: GRASS General Library (GRASS GIS Library).

==== Build documentation (-DWITH_DOCS) ====

==== Install according to Filesystem Hierarchy Standard (FHS) -(DWITH_FHS) ====

==== Build GUI (-DWITH_GUI) ====

==== Large file support (-DWITH_LARGEFILES) ====

==== Build with National Language Support (-DWITH_NLS) ====

Requires: [https://www.gnu.org/software/gettext/ Gettext]

==== Use Ccache (-DUSE_CCACHE) ====

[https://ccache.dev Ccache] is a compiler cache. It speeds up recompilation by caching previous compilations and detecting when the same compilation is being done again.

Requires: Ccache

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

Compile and Install With CMake

2025-03-20T15:46:28Z

Nila: add install command

'''Disclaimer''': As of Spring 2025, the development of GRASS GIS using CMake is ongoing. Both the functionality of the CMake build system and the content of this documentation are subject to change.

== Building With CMake ==

It is strongly recommended to perform the build process with CMake in a separate directory, as opposed to the traditional approach of running `./configure && make` in the top-level directory of the source repository using Autotools. The designated build directory may be located anywhere.

A simple configuration, which creates a build directory named "build" (with -B argument) with current directory as source directory (with -S), can look like this:

cd grass_source_dir
cmake -B build -S .

Executing the building process is made with:

cmake --build build

A custom configuration may look like:

export CFLAGS="-DGL_SILENCE_DEPRECATION"
cd grass_source_dir
cmake -B build -S . -G Ninja \
-DCMAKE_PREFIX_PATH="/opt/local" \
-DWITH_OPENMP=ON
cmake --build build -v -j8

To clean up the configuration and build files (equivalent to `make distclean`):

cd grass_source_dir
rm -rf build

Install:

cmake --install build

== Required Software for GRASS ==

Required software to build GRASS:

* [https://www.gnu.org/software/bison/ Bison]
* [https://cmake.org CMake] (version 3.22+)
* [https://github.com/westes/flex flex]
* [https://gdal.org/en/stable/ GDAL]
* [https://www.pcre.org PCRE] (required for MSVC only, on *NIX based platforms the Regex library is part of the system)
* [https://proj.org/ PROJ]
* [https://www.python.org Python] (version 3.9+)
* [https://zlib.net zlib]

== Optional Software and Configuration Flags ==

{| class="wikitable"
|+ Optional Libraries and Configuration Flags
|-
! Software !! Flag (BOOL) !! Default
|-
| bzip2 || WITH_BZLIB || OFF
|-
| Cairo || WITH_CAIRO || ON
|-
| CBLAS || WITH_CBLAS || ON
|-
| FFTW || WITH_FFTW || ON
|-
| FreeType || WITH_FREETYPE || ON
|-
| GEOS || WITH_GEOS || ON
|-
| LAPACKE || WITH_LAPACKE || ON
|-
| libLAS || WITH_LIBLAS || OFF
|-
| libpng || WITH_LIBPNG || ON
|-
| LibTIFF || WITH_TIFF || ON
|-
| MySQL || WITH_MYSQL || OFF
|-
| NetCDF || WITH_NETCDF || OFF
|-
| ODBC || WITH_ODBC || OFF
|-
| OpenGL || WITH_OPENGL || ON
|-
| OpenMP || WITH_OPENMP || OFF
|-
| PDAL || WITH_PDAL || ON
|-
| PostgreSQL || WITH_POSTGRES || ON
|-
| Readline || WITH_READLINE || ON
|-
| SQLite || WITH_SQLITE || ON
|-
| X11 || WITH_X11 || ON/OFF*
|-
| Zstandard || WITH_ZSTD || ON
|}

{| class="wikitable"
|+ Other Configuration Flags
|-
! Description !! Flag (BOOL) !! Default
|-
| Build documentation || WITH_DOCS || ON
|-
| Install according to Filesystem Hierarchy Standard (FHS) || WITH_FHS || OFF
|-
| Build GUI || WITH_GUI || ON
|-
| Large file support || WITH_LARGEFILES || ON/OFF*
|-
| Build with National Language Support (NLS) || WITH_NLS || ON/OFF*
|-
| Use Ccache || USE_CCACHE || ON
|}

*) the default setting varies by platform.

=== Configuration Options ===

==== bzip2 (-DWITH_BZLIB) ====

[https://sourceware.org/bzip2/ bzip2] is a freely available high-quality data compressor.

The library is used by: GRASS General Library (GRASS GIS Library).

==== Cairo (-DWITH_CAIRO) ====

[https://www.cairographics.org Cairo] is a 2D graphics library with support for multiple output devices.

The library is used by: GRASS Cairo Display Driver and `g.cairocomp`.

==== CBLAS (-DWITH_CBLAS) ====

[https://www.netlib.org/blas/ CBLAS] C interface to the BLAS (Basic Linear Algebra Subprograms) which are routines that provide standard building blocks for performing basic vector and matrix operations.

The library is used by: GRASS numerical math interface (GRASS Math Library).

==== FFTW (-DWITH_FFTW) ====

[https://www.fftw.org FFTW] is a C subroutine library for computing the discrete Fourier transform (DFT) in one or more dimensions, of arbitrary input size, and of both real and complex data.

The library is used by: GRASS numerical math interface (GRASS Math Library), `i.fft` and `i.ifft`.

==== FreeType (-DWITH_FREETYPE) ====

[https://freetype.org FreeType] is a freely available software library to render fonts.

The library is used by: GRASS Display Driver, GRASS Cairo Display Driver and `v.label.sa`.

==== GEOS (-DWITH_GEOS) ====

[https://libgeos.org GEOS] is a C/C++ library for computational geometry with a focus on algorithms used in geographic information systems (GIS) software.

The library is used by: `v.buffer`, `v.profile` and `v.select`.

==== LAPACKE (-DWITH_LAPACKE) ====

[https://www.netlib.org/lapack/lapacke.html LAPACKE]is the C Interface to LAPACK, the Linear Algebra PACKage.

The library is used by: GRASS Vector Library, GRASS numerical math interface (GRASS Math Library) and GRASS Raster Library

==== libLAS (-DWITH_LIBLAS) ====

[https://liblas.org libLAS] is a C/C++ library for reading and writing the very common LAS LiDAR format.

The library is used by: `r.in.lidar`, `r3.in.lidar`, `v.in.lidar`, `v.lidar.correction`, `v.lidar.edgedetection`, `v.lidar.growing` and `v.out.lidar`.

==== libpng (-DWITH_LIBPNG) ====

[http://www.libpng.org/pub/png/ libpng] provides support for Portable Network Graphics (PNG) image file format.

The library is used by: GRASS PNG Display Driver Library, `r.in.png` and `r.out.png`.

==== LibTIFF (-DWITH_TIFF) ====

[https://libtiff.gitlab.io/libtiff/ LibTIFF] provides support for the Tag Image File Format (TIFF), a widely used format for storing image data.

The library is used by: GRASS OGSF Library.

==== MySQL (-DWITH_MYSQL) ====

[https://www.mysql.com MySQL] or [https://mariadb.org MariaDB] are two forks of a relational database.

The library is used by: GRASS DataBase MySQL driver.

==== NetCDF (-DWITH_NETCDF) ====

[https://www.unidata.ucar.edu/software/netcdf/ NetCDF] (Network Common Data Form) is a set of software libraries and machine-independent data formats that support the creation, access, and sharing of array-oriented scientific data.

The library is used by: `r3.out.netcdf`.

==== ODBC (-DWITH_ODBC) ====

[https://en.wikipedia.org/wiki/Open_Database_Connectivity Open Database Connectivity] (ODBC) is a standard application programming interface (API) for accessing database management systems (DBMS).

The library is used by: GRASS DataBase ODBC driver.

==== OpenGL (-DWITH_OPENGL) ====

[https://www.opengl.org OpenGL] (Open Graphics Library) is a cross-language, cross-platform application programming interface (API) for rendering 2D and 3D vector graphics.

The library is used by: GRASS OGSF Library and GRASS Nviz Library.

==== OpenMP (-DWITH_OPENMP) ====

[https://en.wikipedia.org/wiki/OpenMP OpenMP] is an application programming interface (API) that supports multi-platform shared-memory multiprocessing programming in C, C++, and Fortran, on many platforms, instruction-set architectures and operating systems.

The library is used by: GRASS numerical math interface (GRASS Math Library), GRASS Partial differential equations Library (GPDE), GRASS Library for interpolation with regularized splines with tension (RST), `r.mfilter`,
`r.neighbors`, `r.proj`, `r.resamp.filter`, `r.resamp.interp`, `r.series`, `r.series.accumulate`, `r.slope.aspect`, `r.sun`, `r.sim`, `r.univar`, `r3.univar` and `v.surf.rst`.

==== PDAL (-DWITH_PDAL) ====

[https://pdal.io/ PDAL] is a C++ library for translating and manipulating point cloud data.

The library is used by: `r.in.pdal` and `v.in.pdal`.

==== PostgreSQL (-DWITH_POSTGRES) ====

[https://www.postgresql.org PostgreSQL] is a powerful, open source object-relational database system.

The library is used by: GRASS DataBase PostgreSQL driver, GRASS General Library (GRASS GIS Library), `v.external` and `v.out.postgis`.

==== Readline (-DWITH_READLINE) ====

[https://www.gnu.org/software/readline/ Readline] library provides a set of functions for use by applications that allow users to edit command lines as they are typed in.

The library is used by: `r.mapcalc` and `r3.mapcalc`.

==== SQLite (-DWITH_SQLITE) ====

[https://www.sqlite.org SQLite] is a C-language library that implements a small, fast, self-contained, high-reliability, full-featured, SQL database engine.

The library is used by: GRASS DataBase SQLite driver and `g.version`.

==== X11 (-DWITH_X11) ====

[https://www.x.org/wiki/ X Window System] (X11) is a windowing system for bitmap displays, common on Unix-like operating systems.

The library is used by: GRASS Nviz Library, `g.cairocomp` and `ximgview`.

==== Zstandard (-DWITH_ZSTD) ====

[https://facebook.github.io/zstd/ Zstandard] is a fast compression algorithm, providing high compression ratios. It also offers a special mode for small data, called dictionary compression.

The library is used by: GRASS General Library (GRASS GIS Library).

==== Build documentation (-DWITH_DOCS) ====

==== Install according to Filesystem Hierarchy Standard (FHS) -(DWITH_FHS) ====

==== Build GUI (-DWITH_GUI) ====

==== Large file support (-DWITH_LARGEFILES) ====

==== Build with National Language Support (-DWITH_NLS) ====

Requires: [https://www.gnu.org/software/gettext/ Gettext]

==== Use Ccache (-DUSE_CCACHE) ====

[https://ccache.dev Ccache] is a compiler cache. It speeds up recompilation by caching previous compilations and detecting when the same compilation is being done again.

Requires: Ccache

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

Compile and Install With CMake

2025-03-20T13:54:49Z

Nila:

'''Disclaimer''': As of Spring 2025, the development of GRASS GIS using CMake is ongoing. Both the functionality of the CMake build system and the content of this documentation are subject to change.

== Building With CMake ==

It is strongly recommended to perform the build process with CMake in a separate directory, as opposed to the traditional approach of running `./configure && make` in the top-level directory of the source repository using Autotools. The designated build directory may be located anywhere.

A simple configuration, which creates a build directory named "build" (with -B argument) with current directory as source directory (with -S), can look like this:

cd grass_source_dir
cmake -B build -S .

Executing the building process is made with:

cmake --build build

A custom configuration may look like:

export CFLAGS="-DGL_SILENCE_DEPRECATION"
cd grass_source_dir
cmake -B build -S . -G Ninja \
-DCMAKE_PREFIX_PATH="/opt/local" \
-DWITH_OPENMP=ON
cmake --build build -v -j8

To clean up the configuration and build files (equivalent to `make distclean`):

cd grass_source_dir
rm -rf build

== Required Software for GRASS ==

Required software to build GRASS:

* [https://www.gnu.org/software/bison/ Bison]
* [https://cmake.org CMake] (version 3.22+)
* [https://github.com/westes/flex flex]
* [https://gdal.org/en/stable/ GDAL]
* [https://www.pcre.org PCRE] (required for MSVC only, on *NIX based platforms the Regex library is part of the system)
* [https://proj.org/ PROJ]
* [https://www.python.org Python] (version 3.9+)
* [https://zlib.net zlib]

== Optional Software and Configuration Flags ==

{| class="wikitable"
|+ Optional Libraries and Configuration Flags
|-
! Software !! Flag (BOOL) !! Default
|-
| bzip2 || WITH_BZLIB || OFF
|-
| Cairo || WITH_CAIRO || ON
|-
| CBLAS || WITH_CBLAS || ON
|-
| FFTW || WITH_FFTW || ON
|-
| FreeType || WITH_FREETYPE || ON
|-
| GEOS || WITH_GEOS || ON
|-
| LAPACKE || WITH_LAPACKE || ON
|-
| libLAS || WITH_LIBLAS || OFF
|-
| libpng || WITH_LIBPNG || ON
|-
| LibTIFF || WITH_TIFF || ON
|-
| MySQL || WITH_MYSQL || OFF
|-
| NetCDF || WITH_NETCDF || OFF
|-
| ODBC || WITH_ODBC || OFF
|-
| OpenGL || WITH_OPENGL || ON
|-
| OpenMP || WITH_OPENMP || OFF
|-
| PDAL || WITH_PDAL || ON
|-
| PostgreSQL || WITH_POSTGRES || ON
|-
| Readline || WITH_READLINE || ON
|-
| SQLite || WITH_SQLITE || ON
|-
| X11 || WITH_X11 || ON/OFF*
|-
| Zstandard || WITH_ZSTD || ON
|}

{| class="wikitable"
|+ Other Configuration Flags
|-
! Description !! Flag (BOOL) !! Default
|-
| Build documentation || WITH_DOCS || ON
|-
| Install according to Filesystem Hierarchy Standard (FHS) || WITH_FHS || OFF
|-
| Build GUI || WITH_GUI || ON
|-
| Large file support || WITH_LARGEFILES || ON/OFF*
|-
| Build with National Language Support (NLS) || WITH_NLS || ON/OFF*
|-
| Use Ccache || USE_CCACHE || ON
|}

*) the default setting varies by platform.

=== Configuration Options ===

==== bzip2 (-DWITH_BZLIB) ====

[https://sourceware.org/bzip2/ bzip2] is a freely available high-quality data compressor.

The library is used by: GRASS General Library (GRASS GIS Library).

==== Cairo (-DWITH_CAIRO) ====

[https://www.cairographics.org Cairo] is a 2D graphics library with support for multiple output devices.

The library is used by: GRASS Cairo Display Driver and `g.cairocomp`.

==== CBLAS (-DWITH_CBLAS) ====

[https://www.netlib.org/blas/ CBLAS] C interface to the BLAS (Basic Linear Algebra Subprograms) which are routines that provide standard building blocks for performing basic vector and matrix operations.

The library is used by: GRASS numerical math interface (GRASS Math Library).

==== FFTW (-DWITH_FFTW) ====

[https://www.fftw.org FFTW] is a C subroutine library for computing the discrete Fourier transform (DFT) in one or more dimensions, of arbitrary input size, and of both real and complex data.

The library is used by: GRASS numerical math interface (GRASS Math Library), `i.fft` and `i.ifft`.

==== FreeType (-DWITH_FREETYPE) ====

[https://freetype.org FreeType] is a freely available software library to render fonts.

The library is used by: GRASS Display Driver, GRASS Cairo Display Driver and `v.label.sa`.

==== GEOS (-DWITH_GEOS) ====

[https://libgeos.org GEOS] is a C/C++ library for computational geometry with a focus on algorithms used in geographic information systems (GIS) software.

The library is used by: `v.buffer`, `v.profile` and `v.select`.

==== LAPACKE (-DWITH_LAPACKE) ====

[https://www.netlib.org/lapack/lapacke.html LAPACKE]is the C Interface to LAPACK, the Linear Algebra PACKage.

The library is used by: GRASS Vector Library, GRASS numerical math interface (GRASS Math Library) and GRASS Raster Library

==== libLAS (-DWITH_LIBLAS) ====

[https://liblas.org libLAS] is a C/C++ library for reading and writing the very common LAS LiDAR format.

The library is used by: `r.in.lidar`, `r3.in.lidar`, `v.in.lidar`, `v.lidar.correction`, `v.lidar.edgedetection`, `v.lidar.growing` and `v.out.lidar`.

==== libpng (-DWITH_LIBPNG) ====

[http://www.libpng.org/pub/png/ libpng] provides support for Portable Network Graphics (PNG) image file format.

The library is used by: GRASS PNG Display Driver Library, `r.in.png` and `r.out.png`.

==== LibTIFF (-DWITH_TIFF) ====

[https://libtiff.gitlab.io/libtiff/ LibTIFF] provides support for the Tag Image File Format (TIFF), a widely used format for storing image data.

The library is used by: GRASS OGSF Library.

==== MySQL (-DWITH_MYSQL) ====

[https://www.mysql.com MySQL] or [https://mariadb.org MariaDB] are two forks of a relational database.

The library is used by: GRASS DataBase MySQL driver.

==== NetCDF (-DWITH_NETCDF) ====

[https://www.unidata.ucar.edu/software/netcdf/ NetCDF] (Network Common Data Form) is a set of software libraries and machine-independent data formats that support the creation, access, and sharing of array-oriented scientific data.

The library is used by: `r3.out.netcdf`.

==== ODBC (-DWITH_ODBC) ====

[https://en.wikipedia.org/wiki/Open_Database_Connectivity Open Database Connectivity] (ODBC) is a standard application programming interface (API) for accessing database management systems (DBMS).

The library is used by: GRASS DataBase ODBC driver.

==== OpenGL (-DWITH_OPENGL) ====

[https://www.opengl.org OpenGL] (Open Graphics Library) is a cross-language, cross-platform application programming interface (API) for rendering 2D and 3D vector graphics.

The library is used by: GRASS OGSF Library and GRASS Nviz Library.

==== OpenMP (-DWITH_OPENMP) ====

[https://en.wikipedia.org/wiki/OpenMP OpenMP] is an application programming interface (API) that supports multi-platform shared-memory multiprocessing programming in C, C++, and Fortran, on many platforms, instruction-set architectures and operating systems.

The library is used by: GRASS numerical math interface (GRASS Math Library), GRASS Partial differential equations Library (GPDE), GRASS Library for interpolation with regularized splines with tension (RST), `r.mfilter`,
`r.neighbors`, `r.proj`, `r.resamp.filter`, `r.resamp.interp`, `r.series`, `r.series.accumulate`, `r.slope.aspect`, `r.sun`, `r.sim`, `r.univar`, `r3.univar` and `v.surf.rst`.

==== PDAL (-DWITH_PDAL) ====

[https://pdal.io/ PDAL] is a C++ library for translating and manipulating point cloud data.

The library is used by: `r.in.pdal` and `v.in.pdal`.

==== PostgreSQL (-DWITH_POSTGRES) ====

[https://www.postgresql.org PostgreSQL] is a powerful, open source object-relational database system.

The library is used by: GRASS DataBase PostgreSQL driver, GRASS General Library (GRASS GIS Library), `v.external` and `v.out.postgis`.

==== Readline (-DWITH_READLINE) ====

[https://www.gnu.org/software/readline/ Readline] library provides a set of functions for use by applications that allow users to edit command lines as they are typed in.

The library is used by: `r.mapcalc` and `r3.mapcalc`.

==== SQLite (-DWITH_SQLITE) ====

[https://www.sqlite.org SQLite] is a C-language library that implements a small, fast, self-contained, high-reliability, full-featured, SQL database engine.

The library is used by: GRASS DataBase SQLite driver and `g.version`.

==== X11 (-DWITH_X11) ====

[https://www.x.org/wiki/ X Window System] (X11) is a windowing system for bitmap displays, common on Unix-like operating systems.

The library is used by: GRASS Nviz Library, `g.cairocomp` and `ximgview`.

==== Zstandard (-DWITH_ZSTD) ====

[https://facebook.github.io/zstd/ Zstandard] is a fast compression algorithm, providing high compression ratios. It also offers a special mode for small data, called dictionary compression.

The library is used by: GRASS General Library (GRASS GIS Library).

==== Build documentation (-DWITH_DOCS) ====

==== Install according to Filesystem Hierarchy Standard (FHS) -(DWITH_FHS) ====

==== Build GUI (-DWITH_GUI) ====

==== Large file support (-DWITH_LARGEFILES) ====

==== Build with National Language Support (-DWITH_NLS) ====

Requires: [https://www.gnu.org/software/gettext/ Gettext]

==== Use Ccache (-DUSE_CCACHE) ====

[https://ccache.dev Ccache] is a compiler cache. It speeds up recompilation by caching previous compilations and detecting when the same compilation is being done again.

Requires: Ccache

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

Compile and Install With CMake

2025-03-20T13:54:10Z

Nila: Initial addition of instructions for compiling with CMake

'''Disclaimer''': As of Spring 2025, the development of GRASS GIS using CMake is ongoing. Both the functionality of the CMake build system and the content of this documentation are subject to change.

== Building With CMake ==

It is strongly recommended to perform the build process with CMake in a separate directory, as opposed to the traditional approach of running `./configure && make` in the top-level directory of the source repository using Autotools. The designated build directory may be located anywhere.

A simple configuration, which creates a build directory named "build" (with -B argument) with current directory as source directory (with -S), can look like this:

cd grass_source_dir
cmake -B build -S .

Executing the building process is made with:

cmake --build build

A custom configuration may look like:

export CFLAGS="-DGL_SILENCE_DEPRECATION"
cd grass_source_dir
cmake -B build -S . -G Ninja\
-DCMAKE_PREFIX_PATH="/opt/local" \
-DWITH_OPENMP=ON
cmake --build build -v -j8

To clean up the configuration and build files (equivalent to `make distclean`):

cd grass_source_dir
rm -rf build

== Required Software for GRASS ==

Required software to build GRASS:

* [https://www.gnu.org/software/bison/ Bison]
* [https://cmake.org CMake] (version 3.22+)
* [https://github.com/westes/flex flex]
* [https://gdal.org/en/stable/ GDAL]
* [https://www.pcre.org PCRE] (required for MSVC only, on *NIX based platforms the Regex library is part of the system)
* [https://proj.org/ PROJ]
* [https://www.python.org Python] (version 3.9+)
* [https://zlib.net zlib]

== Optional Software and Configuration Flags ==

{| class="wikitable"
|+ Optional Libraries and Configuration Flags
|-
! Software !! Flag (BOOL) !! Default
|-
| bzip2 || WITH_BZLIB || OFF
|-
| Cairo || WITH_CAIRO || ON
|-
| CBLAS || WITH_CBLAS || ON
|-
| FFTW || WITH_FFTW || ON
|-
| FreeType || WITH_FREETYPE || ON
|-
| GEOS || WITH_GEOS || ON
|-
| LAPACKE || WITH_LAPACKE || ON
|-
| libLAS || WITH_LIBLAS || OFF
|-
| libpng || WITH_LIBPNG || ON
|-
| LibTIFF || WITH_TIFF || ON
|-
| MySQL || WITH_MYSQL || OFF
|-
| NetCDF || WITH_NETCDF || OFF
|-
| ODBC || WITH_ODBC || OFF
|-
| OpenGL || WITH_OPENGL || ON
|-
| OpenMP || WITH_OPENMP || OFF
|-
| PDAL || WITH_PDAL || ON
|-
| PostgreSQL || WITH_POSTGRES || ON
|-
| Readline || WITH_READLINE || ON
|-
| SQLite || WITH_SQLITE || ON
|-
| X11 || WITH_X11 || ON/OFF*
|-
| Zstandard || WITH_ZSTD || ON
|}

{| class="wikitable"
|+ Other Configuration Flags
|-
! Description !! Flag (BOOL) !! Default
|-
| Build documentation || WITH_DOCS || ON
|-
| Install according to Filesystem Hierarchy Standard (FHS) || WITH_FHS || OFF
|-
| Build GUI || WITH_GUI || ON
|-
| Large file support || WITH_LARGEFILES || ON/OFF*
|-
| Build with National Language Support (NLS) || WITH_NLS || ON/OFF*
|-
| Use Ccache || USE_CCACHE || ON
|}

*) the default setting varies by platform.

=== Configuration Options ===

==== bzip2 (-DWITH_BZLIB) ====

[https://sourceware.org/bzip2/ bzip2] is a freely available high-quality data compressor.

The library is used by: GRASS General Library (GRASS GIS Library).

==== Cairo (-DWITH_CAIRO) ====

[https://www.cairographics.org Cairo] is a 2D graphics library with support for multiple output devices.

The library is used by: GRASS Cairo Display Driver and `g.cairocomp`.

==== CBLAS (-DWITH_CBLAS) ====

[https://www.netlib.org/blas/ CBLAS] C interface to the BLAS (Basic Linear Algebra Subprograms) which are routines that provide standard building blocks for performing basic vector and matrix operations.

The library is used by: GRASS numerical math interface (GRASS Math Library).

==== FFTW (-DWITH_FFTW) ====

[https://www.fftw.org FFTW] is a C subroutine library for computing the discrete Fourier transform (DFT) in one or more dimensions, of arbitrary input size, and of both real and complex data.

The library is used by: GRASS numerical math interface (GRASS Math Library), `i.fft` and `i.ifft`.

==== FreeType (-DWITH_FREETYPE) ====

[https://freetype.org FreeType] is a freely available software library to render fonts.

The library is used by: GRASS Display Driver, GRASS Cairo Display Driver and `v.label.sa`.

==== GEOS (-DWITH_GEOS) ====

[https://libgeos.org GEOS] is a C/C++ library for computational geometry with a focus on algorithms used in geographic information systems (GIS) software.

The library is used by: `v.buffer`, `v.profile` and `v.select`.

==== LAPACKE (-DWITH_LAPACKE) ====

[https://www.netlib.org/lapack/lapacke.html LAPACKE]is the C Interface to LAPACK, the Linear Algebra PACKage.

The library is used by: GRASS Vector Library, GRASS numerical math interface (GRASS Math Library) and GRASS Raster Library

==== libLAS (-DWITH_LIBLAS) ====

[https://liblas.org libLAS] is a C/C++ library for reading and writing the very common LAS LiDAR format.

The library is used by: `r.in.lidar`, `r3.in.lidar`, `v.in.lidar`, `v.lidar.correction`, `v.lidar.edgedetection`, `v.lidar.growing` and `v.out.lidar`.

==== libpng (-DWITH_LIBPNG) ====

[http://www.libpng.org/pub/png/ libpng] provides support for Portable Network Graphics (PNG) image file format.

The library is used by: GRASS PNG Display Driver Library, `r.in.png` and `r.out.png`.

==== LibTIFF (-DWITH_TIFF) ====

[https://libtiff.gitlab.io/libtiff/ LibTIFF] provides support for the Tag Image File Format (TIFF), a widely used format for storing image data.

The library is used by: GRASS OGSF Library.

==== MySQL (-DWITH_MYSQL) ====

[https://www.mysql.com MySQL] or [https://mariadb.org MariaDB] are two forks of a relational database.

The library is used by: GRASS DataBase MySQL driver.

==== NetCDF (-DWITH_NETCDF) ====

[https://www.unidata.ucar.edu/software/netcdf/ NetCDF] (Network Common Data Form) is a set of software libraries and machine-independent data formats that support the creation, access, and sharing of array-oriented scientific data.

The library is used by: `r3.out.netcdf`.

==== ODBC (-DWITH_ODBC) ====

[https://en.wikipedia.org/wiki/Open_Database_Connectivity Open Database Connectivity] (ODBC) is a standard application programming interface (API) for accessing database management systems (DBMS).

The library is used by: GRASS DataBase ODBC driver.

==== OpenGL (-DWITH_OPENGL) ====

[https://www.opengl.org OpenGL] (Open Graphics Library) is a cross-language, cross-platform application programming interface (API) for rendering 2D and 3D vector graphics.

The library is used by: GRASS OGSF Library and GRASS Nviz Library.

==== OpenMP (-DWITH_OPENMP) ====

[https://en.wikipedia.org/wiki/OpenMP OpenMP] is an application programming interface (API) that supports multi-platform shared-memory multiprocessing programming in C, C++, and Fortran, on many platforms, instruction-set architectures and operating systems.

The library is used by: GRASS numerical math interface (GRASS Math Library), GRASS Partial differential equations Library (GPDE), GRASS Library for interpolation with regularized splines with tension (RST), `r.mfilter`,
`r.neighbors`, `r.proj`, `r.resamp.filter`, `r.resamp.interp`, `r.series`, `r.series.accumulate`, `r.slope.aspect`, `r.sun`, `r.sim`, `r.univar`, `r3.univar` and `v.surf.rst`.

==== PDAL (-DWITH_PDAL) ====

[https://pdal.io/ PDAL] is a C++ library for translating and manipulating point cloud data.

The library is used by: `r.in.pdal` and `v.in.pdal`.

==== PostgreSQL (-DWITH_POSTGRES) ====

[https://www.postgresql.org PostgreSQL] is a powerful, open source object-relational database system.

The library is used by: GRASS DataBase PostgreSQL driver, GRASS General Library (GRASS GIS Library), `v.external` and `v.out.postgis`.

==== Readline (-DWITH_READLINE) ====

[https://www.gnu.org/software/readline/ Readline] library provides a set of functions for use by applications that allow users to edit command lines as they are typed in.

The library is used by: `r.mapcalc` and `r3.mapcalc`.

==== SQLite (-DWITH_SQLITE) ====

[https://www.sqlite.org SQLite] is a C-language library that implements a small, fast, self-contained, high-reliability, full-featured, SQL database engine.

The library is used by: GRASS DataBase SQLite driver and `g.version`.

==== X11 (-DWITH_X11) ====

[https://www.x.org/wiki/ X Window System] (X11) is a windowing system for bitmap displays, common on Unix-like operating systems.

The library is used by: GRASS Nviz Library, `g.cairocomp` and `ximgview`.

==== Zstandard (-DWITH_ZSTD) ====

[https://facebook.github.io/zstd/ Zstandard] is a fast compression algorithm, providing high compression ratios. It also offers a special mode for small data, called dictionary compression.

The library is used by: GRASS General Library (GRASS GIS Library).

==== Build documentation (-DWITH_DOCS) ====

==== Install according to Filesystem Hierarchy Standard (FHS) -(DWITH_FHS) ====

==== Build GUI (-DWITH_GUI) ====

==== Large file support (-DWITH_LARGEFILES) ====

==== Build with National Language Support (-DWITH_NLS) ====

Requires: [https://www.gnu.org/software/gettext/ Gettext]

==== Use Ccache (-DUSE_CCACHE) ====

[https://ccache.dev Ccache] is a compiler cache. It speeds up recompilation by caching previous compilations and detecting when the same compilation is being done again.

Requires: Ccache

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

PSC Meeting 2025-02-14

2025-01-31T20:04:51Z

Nila: Add cmake

== Participants ==

* ...

== Agenda ==

The topics proposed are:

Communication means related:
* Further mailman transition to discourse.osgeo.org (grass-user, grass-psc, ...): plans?
* Close "Gitter" channels in favor of discourse.osgeo.org?
* Closure of grass-web? Archive https://lists.osgeo.org/mailman/listinfo/grass-web and update related web entries to point to discourse
* ...

Budget:
* [[GRASS GIS Budget 2025]]

Tutorials:
* Status of new GRASS GIS tutorials: https://grass-tutorials.osgeo.org/: who maintains it and how to get further content into it

Releases:
* Release of GRASS GIS 8.4.1: [https://github.com/OSGeo/grass/milestone/23 GH milestone]
** related [https://discourse.osgeo.org/t/re-release-planning-grass-gis-8-4-1/111926 discussion]

NSF Grant:
* Update on [[NSF POSE Project 2023-2025 Timeline|POSE]]?

Marketing related:
* report on first experiences with our paid Publer account
* rgrass maintenance shift from Roger Bivand to Steven Pawley incl. [https://github.com/OSGeo/rgrass/ new rgrass URL] -> news on website + social media
* Code signed and notarised GRASS GIS 8.4 Mac binary -> news on website + social media
* new OSGeo subdomain for GRASS GIS tutorials: https://grass-tutorials.osgeo.org/ -> news on website + social media

Other:
* CMake support: current status and discussion on how to proceed

== Minutes ==
* From previous meeting:
** ...

== Next meeting ==

...

[[Category:PSC]]

PSC Meeting 2025-02-14

2025-01-31T19:42:27Z

Nila:

== Participants ==

* ...

== Agenda ==

The topics proposed are:

Communication means related:
* Further mailman transition to discourse.osgeo.org (grass-user, grass-psc, ...): plans?
* Close "Gitter" channels in favor of discourse.osgeo.org?
* Closure of grass-web? Archive https://lists.osgeo.org/mailman/listinfo/grass-web and update related web entries to point to discourse
* ...

Budget:
* [[GRASS GIS Budget 2025]]

Tutorials:
* Status of new GRASS GIS tutorials: https://grass-tutorials.osgeo.org/: who maintains it and how to get further content into it

Releases:
* Release of GRASS GIS 8.4.1: [https://github.com/OSGeo/grass/milestone/23 GH milestone]
** related [https://discourse.osgeo.org/t/re-release-planning-grass-gis-8-4-1/111926 discussion]

NSF Grant:
* Update on [[NSF POSE Project 2023-2025 Timeline|POSE]]?

Marketing related:
* report on first experiences with our paid Publer account
* rgrass maintenance shift from Roger Bivand to Steven Pawley incl. [https://github.com/OSGeo/rgrass/ new rgrass URL] -> news on website + social media
* Code signed and notarised GRASS GIS 8.4 Mac binary -> news on website + social media
* new OSGeo subdomain for GRASS GIS tutorials: https://grass-tutorials.osgeo.org/ -> news on website + social media

Other:
* ...

== Minutes ==
* From previous meeting:
** ...

== Next meeting ==

...

[[Category:PSC]]