GRASS-Wiki - User contributions [en]

Installation Guide

2026-04-15T23:58:04Z

Ltb25: /* Variant B) Advanced installation */

== General ==
:''Note: For compilation of GRASS GIS source code, see [[Compile and Install]]''
This page explains the installation of GRASS binaries.

GRASS GIS requires a workstation running either some flavor of UNIX conforming to POSIX standards like Linux, Mac OS X, Solaris, IRIX, or BSD or MS-Windows. It is also possible to run GRASS in MS Windows by using UNIX translation software such as [[Cygwin]] or natively with MingGW. Ideally, you should have at least 500 Mb for data and 512 Mb RAM. The source code package needs around 270 MB uncompressed. The resulting binaries may need between 20 MB and 180 MB depending on your platform. During a full compilation you may need temporarily up to 150MB including the source code.

The [https://grass.osgeo.org/download/ Software Download Section] of the main GRASS web site contains the latest binaries and source code for all supported platforms. That site also has general directions for installing GRASS manually. However, installation is slightly different on each operating system. Here you can find user-contributed pointers for installing GRASS on specific platforms. In particular, many operating systems have package management utilities that can greatly simplify GRASS installation.

== MS Windows ==

:''The official download page [https://grass.osgeo.org/download/windows/ GRASS GIS for MS-Windows]''

There are two main flavours:
* '''OSGeo4W installer''', for a broad set of open source geospatial software packages including GRASS GIS as well as many other packages (QGIS, GDAL/OGR, and more). Advantages include: 1) Whenever you run the OSGeo4W installer again, it updates the existing installation. 2) The OSGeo4W installer simplifies the installation of GDAL, which is needed for some GRASS tasks.
* '''Standalone winGRASS installer''': install GRASS GIS for Windows with the required support packages. Note that if the version of the winGRASS installer does not include the GDAL package, it may be necessary to install it separately for certain GRASS tasks. The OSGeo4W installer is helpful for installing GDAL on Windows.

=== OSGeo4W installer ===

OSGeo4W is an installer for a broad set of open source geospatial software packages including GRASS GIS as well as many other packages (QGIS, GDAL/OGR, and more). Advantages include: 1) Whenever you run the OSGeo4W installer again, it updates the existing installation. 2) The OSGeo4W installer simplifies the installation of GDAL which is needed for some GRASS tasks.

* Install using [https://trac.osgeo.org/osgeo4w/ OSGeo4W installer] which installs all dependencies as well (PROJ, GDAL, GEOS, Python, etc.)

==== Launch the OSGeo4W installer ====

Save and run the downloaded installer as an ''administrator'' (consider keeping it for convenient future updates).

To ensure you are running the OSGeo4W installer as an administrator, it is recommended to right-click on the installer and select ''Run as administrator ''(rather than opening/running it directly, e.g. left-clicking or double-clicking).

(This is because with Windows 11 the ''desktop'', ''download'', and ''documents'' directories are located in a standard user account directory, e.g. C:\User\username, that is created by default and ''do not have administrator privileges'' - even on personal, single-user laptops when the user is also the administrator.)

"The installer must be run on a computer with internet access, as the installer downloads individual packages as needed." This means it may be necessary "to enable your software firewall to allow the installer to have outbound access." For example, pausing vpn security features before starting the installation (and for long enough for the duration of the installation).

You can select either the grass (stable) or grass-daily (development) packages to install.

[[Image:Osgeo4w_1.png|center|thumb|500px|Install with "Administrator" rights]]

==== Variant A) Express installation ====

The "Express Desktop Install" mode installs the stable version of GRASS. The OSGeo4W Quick Start guidance recommends running the "Express Installation" over a 'full install in Advanced mode'.

[[Image:Osgeo4w_2_express.png|center|thumb|500px|Use "Express installation" to select stable version]]

For a GRASS GIS installation, select both GRASS and GDAL.

[[Image:Osgeo4w_3_express.png|center|thumb|500px|The options you see with the current version of the OSGeo4W installer may differ from those in the image above - the important thing is to select both GRASS and GDAL for installation]]

.

The Express Installation will make a directory called OSGeo4W on the C drive and install the packages there.

If there is a problem with the OSGeo4W installation, reading the generated log file is useful for identifying and resolving the issue(s).

Commonly installed Python packages include:

* python3-gdal
* python3-matplotlib
* python3-wx
* python3-numpy
* python3-pillow
* python3-pip
* python3-ply
* python3-pyopengl
* python3-psycopg2
* python3-six
* python3-pywin32

The "Advanced Install" mode can be used after an initial "Express Install" to install additional useful packages (e.g. python3-pandas, msys).

==== Variant B) Advanced installation ====

Use the "Advanced Install Mode" to customise the installation of the stable version or to install the development version of GRASS. Remember, the OSGeo4W installer should be run as an administrator (right-click to select the Run as administrator option), and internet security features/settings need to allow the installer internet access.

If installing GRASS and GDAL using the Advanced Installation mode, do not attempt a full install (i.e., all options selected). Be selective, knowing that the OSGeo4W installer will alert you if key dependencies are missed and suggest they be added before proceeding with the installation.

[[Image:Osgeo4w_2_advanced.png|center|thumb|500px|Use "Advanced installation" to select development version]]

[[Image:Osgeo4w_3_advanced.png|center|thumb|500px| Please note that this image was from a former version of the OSGeo4W installer and GRASS (7.9), so it will look a little different for you now.]]

Unlike the Express mode, the Advanced Installation mode allows you to specify the directory for installation of the OSGeo4W packages, but the installation will fail if there is a space in the name/path (e.g., Program Files).

If you plan to use the OSGeo4W installer for future updates on Windows, keep the directory you selected for the installation in mind as the Express mode default is OSGeo4W on the C: drive.

If there is a problem with the OSGeo4W installation of GRASS, reading the generated log file is useful for identifying and resolving the issue(s).

=== winGRASS standalone installer ===

* Native winGRASS package installer is available [https://grass.osgeo.org/grass-stable/binary/mswindows/native/ here].

=== QGIS with winGRASS installer ===
* QGIS including native winGRASS packages are provided [https://www.qgis.org/wiki/Download here].

== GNU/Linux ==

:''The official page [https://grass.osgeo.org/download/linux/ GRASS GIS Download for GNU/Linux]''

=== Debian ===

A binary version of GRASS is available from the apt repository. As root type:

apt-get install grass grass-doc

This is the easiest way to install GRASS on Debian. If you choose to install a binary version manually from the main web site, be sure to follow the instructions for making symlinks found as a note to the [[https://grass.osgeo.org/grass-stable/binary/linux/snapshot/ GRASS GIS stable weekly snapshot]] release.

==== DebianGIS ====

There is also the wonderful [https://wiki.debian.org/DebianGis DebianGIS] project which has a more recent GRASS version with its related packages. Read here for more [[GRASS in Debian |details]]

==== Compiling GRASS from source ====

* See [[Compile and Install]] of Source Code

=== Installation on Fedora ===

The [https://src.fedoraproject.org/rpms/grass Fedora project] provides RPM-packages for stable releases prepared to install on Fedora systems:

<source lang="bash">
sudo dnf install grass grass-gui
</source>

=== Mageia ===

* [https://madb.mageia.org/package/show/name/grass/ Mageia] provides PROJ/GDAL/GRASS RPMs:

urpmi grass

=== openSUSE ===

* [https://build.opensuse.org/package/show/Application:Geo/grass openSUSE] provides GRASS and related RPM-packages:

<source lang="bash">
sudo zypper refresh
sudo zypper install grass
</source>

Alternatively, one can use the '''One-Click installer''':
https://software.opensuse.org/package/grass

=== Red Hat Enterprise Linux (RHEL, CentOS and EPEL) ===

* [https://src.fedoraproject.org/rpms/grass Fedora] offers GRASS and related binaries for CentOS and EPEL

<source lang="bash">
dnf install grass
</source>

=== Ubuntu ===

GRASS Binaries are available from apt/synaptic. From a terminal type:

sudo apt-get install grass grass-doc

or alternatively, search for and install these packages from Synaptic. This is the easy way to get GRASS on your system. Even if you choose to install binaries from another source, you may want to install this version just so that all (most) dependencies are installed as painlessly as possible.

To get the latest version of GRASS on Ubuntu, compile the code from source. See the [[Compile and Install]] section for a shell script that makes this easy.

== MacOS ==

Precompiled GRASS GIS packages for macOS can be found [https://grass.osgeo.org/download/mac here]. These are distributed as zipped *.dmg packages. Opening the dmg prompts the user to simply drag and drop the app into the Applications folder. In fact, they '''must''' be installed into the Applications folder and may not run properly in other locations.

A brief introduction to how to install via [https://www.macports.org MacPorts]: [[Compiling on macOS using MacPorts]].

== Raspberry Pi ==

:''See the main page [[Raspberry Pi]].''

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

Installation Guide

2026-04-15T23:50:05Z

Ltb25: /* MS Windows */

== General ==
:''Note: For compilation of GRASS GIS source code, see [[Compile and Install]]''
This page explains the installation of GRASS binaries.

GRASS GIS requires a workstation running either some flavor of UNIX conforming to POSIX standards like Linux, Mac OS X, Solaris, IRIX, or BSD or MS-Windows. It is also possible to run GRASS in MS Windows by using UNIX translation software such as [[Cygwin]] or natively with MingGW. Ideally, you should have at least 500 Mb for data and 512 Mb RAM. The source code package needs around 270 MB uncompressed. The resulting binaries may need between 20 MB and 180 MB depending on your platform. During a full compilation you may need temporarily up to 150MB including the source code.

The [https://grass.osgeo.org/download/ Software Download Section] of the main GRASS web site contains the latest binaries and source code for all supported platforms. That site also has general directions for installing GRASS manually. However, installation is slightly different on each operating system. Here you can find user-contributed pointers for installing GRASS on specific platforms. In particular, many operating systems have package management utilities that can greatly simplify GRASS installation.

== MS Windows ==

:''The official download page [https://grass.osgeo.org/download/windows/ GRASS GIS for MS-Windows]''

There are two main flavours:
* '''OSGeo4W installer''', for a broad set of open source geospatial software packages including GRASS GIS as well as many other packages (QGIS, GDAL/OGR, and more). Advantages include: 1) Whenever you run the OSGeo4W installer again, it updates the existing installation. 2) The OSGeo4W installer simplifies the installation of GDAL, which is needed for some GRASS tasks.
* '''Standalone winGRASS installer''': install GRASS GIS for Windows with the required support packages. Note that if the version of the winGRASS installer does not include the GDAL package, it may be necessary to install it separately for certain GRASS tasks. The OSGeo4W installer is helpful for installing GDAL on Windows.

=== OSGeo4W installer ===

OSGeo4W is an installer for a broad set of open source geospatial software packages including GRASS GIS as well as many other packages (QGIS, GDAL/OGR, and more). Advantages include: 1) Whenever you run the OSGeo4W installer again, it updates the existing installation. 2) The OSGeo4W installer simplifies the installation of GDAL which is needed for some GRASS tasks.

* Install using [https://trac.osgeo.org/osgeo4w/ OSGeo4W installer] which installs all dependencies as well (PROJ, GDAL, GEOS, Python, etc.)

==== Launch the OSGeo4W installer ====

Save and run the downloaded installer as an ''administrator'' (consider keeping it for convenient future updates).

To ensure you are running the OSGeo4W installer as an administrator, it is recommended to right-click on the installer and select ''Run as administrator ''(rather than opening/running it directly, e.g. left-clicking or double-clicking).

(This is because with Windows 11 the ''desktop'', ''download'', and ''documents'' directories are located in a standard user account directory, e.g. C:\User\username, that is created by default and ''do not have administrator privileges'' - even on personal, single-user laptops when the user is also the administrator.)

"The installer must be run on a computer with internet access, as the installer downloads individual packages as needed." This means it may be necessary "to enable your software firewall to allow the installer to have outbound access." For example, pausing vpn security features before starting the installation (and for long enough for the duration of the installation).

You can select either the grass (stable) or grass-daily (development) packages to install.

[[Image:Osgeo4w_1.png|center|thumb|500px|Install with "Administrator" rights]]

==== Variant A) Express installation ====

The "Express Desktop Install" mode installs the stable version of GRASS. The OSGeo4W Quick Start guidance recommends running the "Express Installation" over a 'full install in Advanced mode'.

[[Image:Osgeo4w_2_express.png|center|thumb|500px|Use "Express installation" to select stable version]]

For a GRASS GIS installation, select both GRASS and GDAL.

[[Image:Osgeo4w_3_express.png|center|thumb|500px|The options you see with the current version of the OSGeo4W installer may differ from those in the image above - the important thing is to select both GRASS and GDAL for installation]]

.

The Express Installation will make a directory called OSGeo4W on the C drive and install the packages there.

If there is a problem with the OSGeo4W installation, reading the generated log file is useful for identifying and resolving the issue(s).

Commonly installed Python packages include:

* python3-gdal
* python3-matplotlib
* python3-wx
* python3-numpy
* python3-pillow
* python3-pip
* python3-ply
* python3-pyopengl
* python3-psycopg2
* python3-six
* python3-pywin32

The "Advanced Install" mode can be used after an initial "Express Install" to install additional useful packages (e.g. python3-pandas, msys).

==== Variant B) Advanced installation ====

Use the "Advanced Install Mode" to customise the installation of the stable version or to install the development version of GRASS. Remember, the OSGeo4W installer should be run as an administrator (right-click to select the Run as administrator option), and internet security features/settings need to allow the installer internet access.

If installing GRASS and GDAL using the Advanced Installation mode, do not attempt a full install (i.e., all options selected). Be selective, knowing that the OSGeo4W installer will alert you if key dependencies are missed and suggest they be added before proceeding with the installation.

[[Image:Osgeo4w_2_advanced.png|center|thumb|500px|Use "Advanced installation" to select development version]]

[[Image:Osgeo4w_3_advanced.png|center|thumb|500px]]

Unlike the Express mode, the Advanced Installation mode allows you to specify the directory for installation of the OSGeo4W packages, but the installation will fail if there is a space in the name/path (e.g., Program Files).

If you plan to use the OSGeo4W installer for future updates on Windows, keep the directory you selected for the installation in mind as the Express mode default is OSGeo4W on the C: drive.

If there is a problem with the OSGeo4W installation of GRASS, reading the generated log file is useful for identifying and resolving the issue(s).

=== winGRASS standalone installer ===

* Native winGRASS package installer is available [https://grass.osgeo.org/grass-stable/binary/mswindows/native/ here].

=== QGIS with winGRASS installer ===
* QGIS including native winGRASS packages are provided [https://www.qgis.org/wiki/Download here].

== GNU/Linux ==

:''The official page [https://grass.osgeo.org/download/linux/ GRASS GIS Download for GNU/Linux]''

=== Debian ===

A binary version of GRASS is available from the apt repository. As root type:

apt-get install grass grass-doc

This is the easiest way to install GRASS on Debian. If you choose to install a binary version manually from the main web site, be sure to follow the instructions for making symlinks found as a note to the [[https://grass.osgeo.org/grass-stable/binary/linux/snapshot/ GRASS GIS stable weekly snapshot]] release.

==== DebianGIS ====

There is also the wonderful [https://wiki.debian.org/DebianGis DebianGIS] project which has a more recent GRASS version with its related packages. Read here for more [[GRASS in Debian |details]]

==== Compiling GRASS from source ====

* See [[Compile and Install]] of Source Code

=== Installation on Fedora ===

The [https://src.fedoraproject.org/rpms/grass Fedora project] provides RPM-packages for stable releases prepared to install on Fedora systems:

<source lang="bash">
sudo dnf install grass grass-gui
</source>

=== Mageia ===

* [https://madb.mageia.org/package/show/name/grass/ Mageia] provides PROJ/GDAL/GRASS RPMs:

urpmi grass

=== openSUSE ===

* [https://build.opensuse.org/package/show/Application:Geo/grass openSUSE] provides GRASS and related RPM-packages:

<source lang="bash">
sudo zypper refresh
sudo zypper install grass
</source>

Alternatively, one can use the '''One-Click installer''':
https://software.opensuse.org/package/grass

=== Red Hat Enterprise Linux (RHEL, CentOS and EPEL) ===

* [https://src.fedoraproject.org/rpms/grass Fedora] offers GRASS and related binaries for CentOS and EPEL

<source lang="bash">
dnf install grass
</source>

=== Ubuntu ===

GRASS Binaries are available from apt/synaptic. From a terminal type:

sudo apt-get install grass grass-doc

or alternatively, search for and install these packages from Synaptic. This is the easy way to get GRASS on your system. Even if you choose to install binaries from another source, you may want to install this version just so that all (most) dependencies are installed as painlessly as possible.

To get the latest version of GRASS on Ubuntu, compile the code from source. See the [[Compile and Install]] section for a shell script that makes this easy.

== MacOS ==

Precompiled GRASS GIS packages for macOS can be found [https://grass.osgeo.org/download/mac here]. These are distributed as zipped *.dmg packages. Opening the dmg prompts the user to simply drag and drop the app into the Applications folder. In fact, they '''must''' be installed into the Applications folder and may not run properly in other locations.

A brief introduction to how to install via [https://www.macports.org MacPorts]: [[Compiling on macOS using MacPorts]].

== Raspberry Pi ==

:''See the main page [[Raspberry Pi]].''

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

Installation Guide

2026-04-15T23:28:42Z

Ltb25: /* MS Windows */

== General ==
:''Note: For compilation of GRASS GIS source code, see [[Compile and Install]]''
This page explains the installation of GRASS binaries.

GRASS GIS requires a workstation running either some flavor of UNIX conforming to POSIX standards like Linux, Mac OS X, Solaris, IRIX, or BSD or MS-Windows. It is also possible to run GRASS in MS Windows by using UNIX translation software such as [[Cygwin]] or natively with MingGW. Ideally, you should have at least 500 Mb for data and 512 Mb RAM. The source code package needs around 270 MB uncompressed. The resulting binaries may need between 20 MB and 180 MB depending on your platform. During a full compilation you may need temporarily up to 150MB including the source code.

The [https://grass.osgeo.org/download/ Software Download Section] of the main GRASS web site contains the latest binaries and source code for all supported platforms. That site also has general directions for installing GRASS manually. However, installation is slightly different on each operating system. Here you can find user-contributed pointers for installing GRASS on specific platforms. In particular, many operating systems have package management utilities that can greatly simplify GRASS installation.

== MS Windows ==

:''The official download page [https://grass.osgeo.org/download/windows/ GRASS GIS for MS-Windows]''

There are two main flavours:
* '''OSGeo4W installer''', for a broad set of open source geospatial software packages including GRASS GIS as well as many other packages (QGIS, GDAL/OGR, and more). Advantages include: 1) Whenever you run the OSGeo4W installer again, it updates the existing installation. 2) The OSGeo4W installer simplifies the installation of GDAL which is needed for some GRASS modules.
* '''Standalone winGRASS installer''': install GRASS GIS for Windows with the required support packages. Note that if the version of the winGRASS installer does not include the GDAL package, it may be necessary to install it separately for certain GRASS tasks. The OSGeo4W installer is helpful for installing GDAL on Windows.

=== OSGeo4W installer ===

OSGeo4W is an installer for a broad set of open source geospatial software packages including GRASS GIS as well as many other packages (QGIS, GDAL/OGR, and more). Advantages include: 1) Whenever you run the OSGeo4W installer again, it updates the existing installation. 2) The OSGeo4W installer simplifies the installation of GDAL which is needed for some GRASS modules.

* Install using [https://trac.osgeo.org/osgeo4w/ OSGeo4W installer] which installs all dependencies as well (PROJ, GDAL, GEOS, Python, etc.)

==== Launch the OSGeo4W installer ====

Save and run the downloaded installer as an ''administrator'' (consider keeping it for convenient future updates).

To ensure you are running the OSGeo4W installer as an administrator, it is recommended to right-click on the installer and select ''Run as administrator ''(rather than opening/running it directly, e.g. left-clicking or double-clicking).

(This is because with Windows 11 the ''desktop'', ''download'', and ''documents'' directories are located in a standard user account directory, e.g. C:\User\username, that is created by default and ''do not have administrator privileges'' - even on personal, single-user laptops when the user is also the administrator.)

"The installer must be run on a computer with internet access as the installer downloads individual packages as needed." This means it may be necessary "to enable your software firewall to allow the installer to have outbound access." For example, pausing vpn security features before starting the installation (and for long enough for the duration of the installation).

You can select either the grass (stable) or grass-daily (development) packages to install.

[[Image:Osgeo4w_1.png|center|thumb|500px|Install with "Administrator" rights]]

==== Variant A) Express installation ====

The "Express Desktop Install" mode installs the stable version of GRASS. The OSGeo4W Quick Start guidance recommends running the "Express Installation" over a 'full install in Advanced mode'.

[[Image:Osgeo4w_2_express.png|center|thumb|500px|Use "Express installation" to select stable version]]

[[Image:Osgeo4w_3_express.png|center|thumb|500px]]

For just GRASS GIS installation, select both GRASS and GDAL options.

The Express Installation will make a directory called OSGeo4W on the C drive and install the packages there. (Note that the options in the 'OSGeo4W Setup - Express Package Selection' box you see with the current version of the OSGeo4W installer you are using may differ from those in the image above.)

If there is a problem with the OSGeo4W installation of GRASS (either Express or Advanced), reading the generated log file is useful for identifying and resolving the issue(s).

Commonly installed Python packages include:

* python3-gdal
* python3-matplotlib
* python3-wx
* python3-numpy
* python3-pillow
* python3-pip
* python3-ply
* python3-pyopengl
* python3-psycopg2
* python3-six
* python3-pywin32

The "Advanced Install" mode can be used to install additional useful packages (e.g. python3-pandas, msys) for use with the stable GRASS version installed using the "Express Install" mode.

==== Variant B) Advanced installation ====

Use "Advanced Install Mode" to customise the installation of the stable version or to install the development version.

The "Advanced Installation" mode allows more customisation. If you chose to install GRASS and GDAL using the Advanced Installation, do not install everything; be selective. The OSGeo4W installer will let you know if there are key dependencies that were not selected and allow you to select them before proceeding with the installation in the Advanced mode. Remember, the OSGeo4W installer should be run as an administrator (right-click to select the Run as administrator option).

[[Image:Osgeo4w_2_advanced.png|center|thumb|500px|Use "Advanced installation" to select development version]]

[[Image:Osgeo4w_3_advanced.png|center|thumb|500px]]

Unlike the Express mode, the Advanced Installation mode allows you to specify the directory for installation of the OSGeo4W packages, but the installation will fail if there is a space in the name/path (e.g., Program Files). Keep the directory of the installation in mind if you plan to use the OSGeo4W installer for updates.

If there is a problem with the OSGeo4W installation of GRASS (either Express or Advanced), reading the generated log file is useful for identifying and resolving the issue(s).

=== winGRASS standalone installer ===

* Native winGRASS package installer is available [https://grass.osgeo.org/grass-stable/binary/mswindows/native/ here].

=== QGIS with winGRASS installer ===
* QGIS including native winGRASS packages are provided [https://www.qgis.org/wiki/Download here].

== GNU/Linux ==

:''The official page [https://grass.osgeo.org/download/linux/ GRASS GIS Download for GNU/Linux]''

=== Debian ===

A binary version of GRASS is available from the apt repository. As root type:

apt-get install grass grass-doc

This is the easiest way to install GRASS on Debian. If you choose to install a binary version manually from the main web site, be sure to follow the instructions for making symlinks found as a note to the [[https://grass.osgeo.org/grass-stable/binary/linux/snapshot/ GRASS GIS stable weekly snapshot]] release.

==== DebianGIS ====

There is also the wonderful [https://wiki.debian.org/DebianGis DebianGIS] project which has a more recent GRASS version with its related packages. Read here for more [[GRASS in Debian |details]]

==== Compiling GRASS from source ====

* See [[Compile and Install]] of Source Code

=== Installation on Fedora ===

The [https://src.fedoraproject.org/rpms/grass Fedora project] provides RPM-packages for stable releases prepared to install on Fedora systems:

<source lang="bash">
sudo dnf install grass grass-gui
</source>

=== Mageia ===

* [https://madb.mageia.org/package/show/name/grass/ Mageia] provides PROJ/GDAL/GRASS RPMs:

urpmi grass

=== openSUSE ===

* [https://build.opensuse.org/package/show/Application:Geo/grass openSUSE] provides GRASS and related RPM-packages:

<source lang="bash">
sudo zypper refresh
sudo zypper install grass
</source>

Alternatively, one can use the '''One-Click installer''':
https://software.opensuse.org/package/grass

=== Red Hat Enterprise Linux (RHEL, CentOS and EPEL) ===

* [https://src.fedoraproject.org/rpms/grass Fedora] offers GRASS and related binaries for CentOS and EPEL

<source lang="bash">
dnf install grass
</source>

=== Ubuntu ===

GRASS Binaries are available from apt/synaptic. From a terminal type:

sudo apt-get install grass grass-doc

or alternatively, search for and install these packages from Synaptic. This is the easy way to get GRASS on your system. Even if you choose to install binaries from another source, you may want to install this version just so that all (most) dependencies are installed as painlessly as possible.

To get the latest version of GRASS on Ubuntu, compile the code from source. See the [[Compile and Install]] section for a shell script that makes this easy.

== MacOS ==

Precompiled GRASS GIS packages for macOS can be found [https://grass.osgeo.org/download/mac here]. These are distributed as zipped *.dmg packages. Opening the dmg prompts the user to simply drag and drop the app into the Applications folder. In fact, they '''must''' be installed into the Applications folder and may not run properly in other locations.

A brief introduction to how to install via [https://www.macports.org MacPorts]: [[Compiling on macOS using MacPorts]].

== Raspberry Pi ==

:''See the main page [[Raspberry Pi]].''

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

Installation Guide

2026-04-08T15:38:56Z

Ltb25: /* Launch the OSGeo4W installer */

== General ==
:''Note: For compilation of GRASS GIS source code, see [[Compile and Install]]''
This page explains the installation of GRASS binaries.

GRASS GIS requires a workstation running either some flavor of UNIX conforming to POSIX standards like Linux, Mac OS X, Solaris, IRIX, or BSD or MS-Windows. It is also possible to run GRASS in MS Windows by using UNIX translation software such as [[Cygwin]] or natively with MingGW. Ideally, you should have at least 500 Mb for data and 512 Mb RAM. The source code package needs around 270 MB uncompressed. The resulting binaries may need between 20 MB and 180 MB depending on your platform. During a full compilation you may need temporarily up to 150MB including the source code.

The [https://grass.osgeo.org/download/ Software Download Section] of the main GRASS web site contains the latest binaries and source code for all supported platforms. That site also has general directions for installing GRASS manually. However, installation is slightly different on each operating system. Here you can find user-contributed pointers for installing GRASS on specific platforms. In particular, many operating systems have package management utilities that can greatly simplify GRASS installation.

== MS Windows ==

:''The official download page [https://grass.osgeo.org/download/windows/ GRASS GIS for MS-Windows]''

There are two main flavours:
* '''OSGeo4W installer''', for a broad set of open source geospatial software packages including GRASS GIS as well as many other packages (QGIS, GDAL/OGR, and more). Advantage: whenever you run again the OSGeo4W installer, it updates the existing installation.
* '''Standalone winGRASS installer''': install GRASS GIS with the required support packages.

=== OSGeo4W installer ===

OSGeo4W is an installer for a broad set of open source geospatial software packages including GRASS GIS as well as many other packages (QGIS, GDAL/OGR, and more). Advantage: whenever you run again the OSGeo4W installer, it updates the existing installation.

* Install using [https://trac.osgeo.org/osgeo4w/ OSGeo4W installer] which installs all dependencies as well (PROJ, GDAL, GEOS, Python, etc.)

==== Launch the OSGeo4W installer ====

Save the downloaded installer (consider keeping it for future updates) and run it as an ''administrator''.

(Note that with Windows 11 the ''desktop'', ''download'', and ''documents'' directories are located in a standard user account directory, e.g. C:\User\username, that is created by default and ''do not have administrator privileges'' - even on personal, single-user laptops when the user is also the administrator. To run the installer as an administrator from a location in a standard user account directory, right-click on the installer and select Run as administrator.)

You can select either the grass (stable) or grass-daily (development) packages to install.

[[Image:Osgeo4w_1.png|center|thumb|500px|Install with "Administrator" rights]]

==== Variant A) Express installation ====

Use "Express Desktop Install" mode to select stable version.

[[Image:Osgeo4w_2_express.png|center|thumb|500px|Use "Express installation" to select stable version]]

[[Image:Osgeo4w_3_express.png|center|thumb|500px]]

Common installed Python packages:

* python3-gdal
* python3-matplotlib
* python3-wx
* python3-numpy
* python3-pillow
* python3-pip
* python3-ply
* python3-pyopengl
* python3-psycopg2
* python3-six
* python3-pywin32

Additional useful packages (e.g. python3-pandas, msys) can be installed in "Advanced Install" mode.

==== Variant B) Advanced installation ====

Use "Advanced Install Mode" to select development version.

[[Image:Osgeo4w_2_advanced.png|center|thumb|500px|Use "Advanced installation" to select development version]]

[[Image:Osgeo4w_3_advanced.png|center|thumb|500px]]

=== winGRASS standalone installer ===

* Native winGRASS package installer is available [https://grass.osgeo.org/grass-stable/binary/mswindows/native/ here].

=== QGIS with winGRASS installer ===
* QGIS including native winGRASS packages are provided [https://www.qgis.org/wiki/Download here].

== GNU/Linux ==

:''The official page [https://grass.osgeo.org/download/linux/ GRASS GIS Download for GNU/Linux]''

=== Debian ===

A binary version of GRASS is available from the apt repository. As root type:

apt-get install grass grass-doc

This is the easiest way to install GRASS on Debian. If you choose to install a binary version manually from the main web site, be sure to follow the instructions for making symlinks found as a note to the [[https://grass.osgeo.org/grass-stable/binary/linux/snapshot/ GRASS GIS stable weekly snapshot]] release.

==== DebianGIS ====

There is also the wonderful [https://wiki.debian.org/DebianGis DebianGIS] project which has a more recent GRASS version with its related packages. Read here for more [[GRASS in Debian |details]]

==== Compiling GRASS from source ====

* See [[Compile and Install]] of Source Code

=== Installation on Fedora ===

The [https://src.fedoraproject.org/rpms/grass Fedora project] provides RPM-packages for stable releases prepared to install on Fedora systems:

<source lang="bash">
sudo dnf install grass grass-gui
</source>

=== Mageia ===

* [https://madb.mageia.org/package/show/name/grass/ Mageia] provides PROJ/GDAL/GRASS RPMs:

urpmi grass

=== openSUSE ===

* [https://build.opensuse.org/package/show/Application:Geo/grass openSUSE] provides GRASS and related RPM-packages:

<source lang="bash">
sudo zypper refresh
sudo zypper install grass
</source>

Alternatively, one can use the '''One-Click installer''':
https://software.opensuse.org/package/grass

=== Red Hat Enterprise Linux (RHEL, CentOS and EPEL) ===

* [https://src.fedoraproject.org/rpms/grass Fedora] offers GRASS and related binaries for CentOS and EPEL

<source lang="bash">
dnf install grass
</source>

=== Ubuntu ===

GRASS Binaries are available from apt/synaptic. From a terminal type:

sudo apt-get install grass grass-doc

or alternatively, search for and install these packages from Synaptic. This is the easy way to get GRASS on your system. Even if you choose to install binaries from another source, you may want to install this version just so that all (most) dependencies are installed as painlessly as possible.

To get the latest version of GRASS on Ubuntu, compile the code from source. See the [[Compile and Install]] section for a shell script that makes this easy.

== MacOS ==

Precompiled GRASS GIS packages for macOS can be found [https://grass.osgeo.org/download/mac here]. These are distributed as zipped *.dmg packages. Opening the dmg prompts the user to simply drag and drop the app into the Applications folder. In fact, they '''must''' be installed into the Applications folder and may not run properly in other locations.

A brief introduction to how to install via [https://www.macports.org MacPorts]: [[Compiling on macOS using MacPorts]].

== Raspberry Pi ==

:''See the main page [[Raspberry Pi]].''

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

Installation Guide

2026-04-08T15:36:52Z

Ltb25: /* Launch the OSGeo4W installer */

== General ==
:''Note: For compilation of GRASS GIS source code, see [[Compile and Install]]''
This page explains the installation of GRASS binaries.

GRASS GIS requires a workstation running either some flavor of UNIX conforming to POSIX standards like Linux, Mac OS X, Solaris, IRIX, or BSD or MS-Windows. It is also possible to run GRASS in MS Windows by using UNIX translation software such as [[Cygwin]] or natively with MingGW. Ideally, you should have at least 500 Mb for data and 512 Mb RAM. The source code package needs around 270 MB uncompressed. The resulting binaries may need between 20 MB and 180 MB depending on your platform. During a full compilation you may need temporarily up to 150MB including the source code.

The [https://grass.osgeo.org/download/ Software Download Section] of the main GRASS web site contains the latest binaries and source code for all supported platforms. That site also has general directions for installing GRASS manually. However, installation is slightly different on each operating system. Here you can find user-contributed pointers for installing GRASS on specific platforms. In particular, many operating systems have package management utilities that can greatly simplify GRASS installation.

== MS Windows ==

:''The official download page [https://grass.osgeo.org/download/windows/ GRASS GIS for MS-Windows]''

There are two main flavours:
* '''OSGeo4W installer''', for a broad set of open source geospatial software packages including GRASS GIS as well as many other packages (QGIS, GDAL/OGR, and more). Advantage: whenever you run again the OSGeo4W installer, it updates the existing installation.
* '''Standalone winGRASS installer''': install GRASS GIS with the required support packages.

=== OSGeo4W installer ===

OSGeo4W is an installer for a broad set of open source geospatial software packages including GRASS GIS as well as many other packages (QGIS, GDAL/OGR, and more). Advantage: whenever you run again the OSGeo4W installer, it updates the existing installation.

* Install using [https://trac.osgeo.org/osgeo4w/ OSGeo4W installer] which installs all dependencies as well (PROJ, GDAL, GEOS, Python, etc.)

==== Launch the OSGeo4W installer ====

Save the downloaded installer (consider keeping it for future updates) and run it as an ''administrator''.

(Note that with Windows 11 the ''desktop'', ''download'', and ''documents'' directories are located in a standard user account directory, e.g. C:\User\username, that is created by default and do not have administrator privileges'' - even on personal, single-user laptops when the user is also the administrator. To run the installer as an administrator from a location in a standard user account directory, right-click on the installer and select Run as administrator.)

You can select either the grass (stable) or grass-daily (development) packages to install.

[[Image:Osgeo4w_1.png|center|thumb|500px|Install with "Administrator" rights]]

==== Variant A) Express installation ====

Use "Express Desktop Install" mode to select stable version.

[[Image:Osgeo4w_2_express.png|center|thumb|500px|Use "Express installation" to select stable version]]

[[Image:Osgeo4w_3_express.png|center|thumb|500px]]

Common installed Python packages:

* python3-gdal
* python3-matplotlib
* python3-wx
* python3-numpy
* python3-pillow
* python3-pip
* python3-ply
* python3-pyopengl
* python3-psycopg2
* python3-six
* python3-pywin32

Additional useful packages (e.g. python3-pandas, msys) can be installed in "Advanced Install" mode.

==== Variant B) Advanced installation ====

Use "Advanced Install Mode" to select development version.

[[Image:Osgeo4w_2_advanced.png|center|thumb|500px|Use "Advanced installation" to select development version]]

[[Image:Osgeo4w_3_advanced.png|center|thumb|500px]]

=== winGRASS standalone installer ===

* Native winGRASS package installer is available [https://grass.osgeo.org/grass-stable/binary/mswindows/native/ here].

=== QGIS with winGRASS installer ===
* QGIS including native winGRASS packages are provided [https://www.qgis.org/wiki/Download here].

== GNU/Linux ==

:''The official page [https://grass.osgeo.org/download/linux/ GRASS GIS Download for GNU/Linux]''

=== Debian ===

A binary version of GRASS is available from the apt repository. As root type:

apt-get install grass grass-doc

This is the easiest way to install GRASS on Debian. If you choose to install a binary version manually from the main web site, be sure to follow the instructions for making symlinks found as a note to the [[https://grass.osgeo.org/grass-stable/binary/linux/snapshot/ GRASS GIS stable weekly snapshot]] release.

==== DebianGIS ====

There is also the wonderful [https://wiki.debian.org/DebianGis DebianGIS] project which has a more recent GRASS version with its related packages. Read here for more [[GRASS in Debian |details]]

==== Compiling GRASS from source ====

* See [[Compile and Install]] of Source Code

=== Installation on Fedora ===

The [https://src.fedoraproject.org/rpms/grass Fedora project] provides RPM-packages for stable releases prepared to install on Fedora systems:

<source lang="bash">
sudo dnf install grass grass-gui
</source>

=== Mageia ===

* [https://madb.mageia.org/package/show/name/grass/ Mageia] provides PROJ/GDAL/GRASS RPMs:

urpmi grass

=== openSUSE ===

* [https://build.opensuse.org/package/show/Application:Geo/grass openSUSE] provides GRASS and related RPM-packages:

<source lang="bash">
sudo zypper refresh
sudo zypper install grass
</source>

Alternatively, one can use the '''One-Click installer''':
https://software.opensuse.org/package/grass

=== Red Hat Enterprise Linux (RHEL, CentOS and EPEL) ===

* [https://src.fedoraproject.org/rpms/grass Fedora] offers GRASS and related binaries for CentOS and EPEL

<source lang="bash">
dnf install grass
</source>

=== Ubuntu ===

GRASS Binaries are available from apt/synaptic. From a terminal type:

sudo apt-get install grass grass-doc

or alternatively, search for and install these packages from Synaptic. This is the easy way to get GRASS on your system. Even if you choose to install binaries from another source, you may want to install this version just so that all (most) dependencies are installed as painlessly as possible.

To get the latest version of GRASS on Ubuntu, compile the code from source. See the [[Compile and Install]] section for a shell script that makes this easy.

== MacOS ==

Precompiled GRASS GIS packages for macOS can be found [https://grass.osgeo.org/download/mac here]. These are distributed as zipped *.dmg packages. Opening the dmg prompts the user to simply drag and drop the app into the Applications folder. In fact, they '''must''' be installed into the Applications folder and may not run properly in other locations.

A brief introduction to how to install via [https://www.macports.org MacPorts]: [[Compiling on macOS using MacPorts]].

== Raspberry Pi ==

:''See the main page [[Raspberry Pi]].''

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

Installation Guide

2026-04-08T15:36:02Z

Ltb25: /* Launch the OSGeo4W installer */

== General ==
:''Note: For compilation of GRASS GIS source code, see [[Compile and Install]]''
This page explains the installation of GRASS binaries.

GRASS GIS requires a workstation running either some flavor of UNIX conforming to POSIX standards like Linux, Mac OS X, Solaris, IRIX, or BSD or MS-Windows. It is also possible to run GRASS in MS Windows by using UNIX translation software such as [[Cygwin]] or natively with MingGW. Ideally, you should have at least 500 Mb for data and 512 Mb RAM. The source code package needs around 270 MB uncompressed. The resulting binaries may need between 20 MB and 180 MB depending on your platform. During a full compilation you may need temporarily up to 150MB including the source code.

The [https://grass.osgeo.org/download/ Software Download Section] of the main GRASS web site contains the latest binaries and source code for all supported platforms. That site also has general directions for installing GRASS manually. However, installation is slightly different on each operating system. Here you can find user-contributed pointers for installing GRASS on specific platforms. In particular, many operating systems have package management utilities that can greatly simplify GRASS installation.

== MS Windows ==

:''The official download page [https://grass.osgeo.org/download/windows/ GRASS GIS for MS-Windows]''

There are two main flavours:
* '''OSGeo4W installer''', for a broad set of open source geospatial software packages including GRASS GIS as well as many other packages (QGIS, GDAL/OGR, and more). Advantage: whenever you run again the OSGeo4W installer, it updates the existing installation.
* '''Standalone winGRASS installer''': install GRASS GIS with the required support packages.

=== OSGeo4W installer ===

OSGeo4W is an installer for a broad set of open source geospatial software packages including GRASS GIS as well as many other packages (QGIS, GDAL/OGR, and more). Advantage: whenever you run again the OSGeo4W installer, it updates the existing installation.

* Install using [https://trac.osgeo.org/osgeo4w/ OSGeo4W installer] which installs all dependencies as well (PROJ, GDAL, GEOS, Python, etc.)

==== Launch the OSGeo4W installer ====

Save the downloaded installer (consider keeping it for future updates) and run it as an ''administrator''.

(Note that with Windows 11 the ''desktop'', ''download'', and ''documents'' directories are located in a standard user account directory, e.g. C:\User\username, that is created by default which does not have administrator privileges'' - even on personal, single-user laptops when the user is also the administrator. To run the installer as an administrator from a location in a standard user account directory, right-click on the installer and select Run as administrator.)

You can select either the grass (stable) or grass-daily (development) packages to install.

[[Image:Osgeo4w_1.png|center|thumb|500px|Install with "Administrator" rights]]

==== Variant A) Express installation ====

Use "Express Desktop Install" mode to select stable version.

[[Image:Osgeo4w_2_express.png|center|thumb|500px|Use "Express installation" to select stable version]]

[[Image:Osgeo4w_3_express.png|center|thumb|500px]]

Common installed Python packages:

* python3-gdal
* python3-matplotlib
* python3-wx
* python3-numpy
* python3-pillow
* python3-pip
* python3-ply
* python3-pyopengl
* python3-psycopg2
* python3-six
* python3-pywin32

Additional useful packages (e.g. python3-pandas, msys) can be installed in "Advanced Install" mode.

==== Variant B) Advanced installation ====

Use "Advanced Install Mode" to select development version.

[[Image:Osgeo4w_2_advanced.png|center|thumb|500px|Use "Advanced installation" to select development version]]

[[Image:Osgeo4w_3_advanced.png|center|thumb|500px]]

=== winGRASS standalone installer ===

* Native winGRASS package installer is available [https://grass.osgeo.org/grass-stable/binary/mswindows/native/ here].

=== QGIS with winGRASS installer ===
* QGIS including native winGRASS packages are provided [https://www.qgis.org/wiki/Download here].

== GNU/Linux ==

:''The official page [https://grass.osgeo.org/download/linux/ GRASS GIS Download for GNU/Linux]''

=== Debian ===

A binary version of GRASS is available from the apt repository. As root type:

apt-get install grass grass-doc

This is the easiest way to install GRASS on Debian. If you choose to install a binary version manually from the main web site, be sure to follow the instructions for making symlinks found as a note to the [[https://grass.osgeo.org/grass-stable/binary/linux/snapshot/ GRASS GIS stable weekly snapshot]] release.

==== DebianGIS ====

There is also the wonderful [https://wiki.debian.org/DebianGis DebianGIS] project which has a more recent GRASS version with its related packages. Read here for more [[GRASS in Debian |details]]

==== Compiling GRASS from source ====

* See [[Compile and Install]] of Source Code

=== Installation on Fedora ===

The [https://src.fedoraproject.org/rpms/grass Fedora project] provides RPM-packages for stable releases prepared to install on Fedora systems:

<source lang="bash">
sudo dnf install grass grass-gui
</source>

=== Mageia ===

* [https://madb.mageia.org/package/show/name/grass/ Mageia] provides PROJ/GDAL/GRASS RPMs:

urpmi grass

=== openSUSE ===

* [https://build.opensuse.org/package/show/Application:Geo/grass openSUSE] provides GRASS and related RPM-packages:

<source lang="bash">
sudo zypper refresh
sudo zypper install grass
</source>

Alternatively, one can use the '''One-Click installer''':
https://software.opensuse.org/package/grass

=== Red Hat Enterprise Linux (RHEL, CentOS and EPEL) ===

* [https://src.fedoraproject.org/rpms/grass Fedora] offers GRASS and related binaries for CentOS and EPEL

<source lang="bash">
dnf install grass
</source>

=== Ubuntu ===

GRASS Binaries are available from apt/synaptic. From a terminal type:

sudo apt-get install grass grass-doc

or alternatively, search for and install these packages from Synaptic. This is the easy way to get GRASS on your system. Even if you choose to install binaries from another source, you may want to install this version just so that all (most) dependencies are installed as painlessly as possible.

To get the latest version of GRASS on Ubuntu, compile the code from source. See the [[Compile and Install]] section for a shell script that makes this easy.

== MacOS ==

Precompiled GRASS GIS packages for macOS can be found [https://grass.osgeo.org/download/mac here]. These are distributed as zipped *.dmg packages. Opening the dmg prompts the user to simply drag and drop the app into the Applications folder. In fact, they '''must''' be installed into the Applications folder and may not run properly in other locations.

A brief introduction to how to install via [https://www.macports.org MacPorts]: [[Compiling on macOS using MacPorts]].

== Raspberry Pi ==

:''See the main page [[Raspberry Pi]].''

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

Installation Guide

2026-04-08T03:42:47Z

Ltb25: /* Launch the OSGeo4W installer */

== General ==
:''Note: For compilation of GRASS GIS source code, see [[Compile and Install]]''
This page explains the installation of GRASS binaries.

GRASS GIS requires a workstation running either some flavor of UNIX conforming to POSIX standards like Linux, Mac OS X, Solaris, IRIX, or BSD or MS-Windows. It is also possible to run GRASS in MS Windows by using UNIX translation software such as [[Cygwin]] or natively with MingGW. Ideally, you should have at least 500 Mb for data and 512 Mb RAM. The source code package needs around 270 MB uncompressed. The resulting binaries may need between 20 MB and 180 MB depending on your platform. During a full compilation you may need temporarily up to 150MB including the source code.

The [https://grass.osgeo.org/download/ Software Download Section] of the main GRASS web site contains the latest binaries and source code for all supported platforms. That site also has general directions for installing GRASS manually. However, installation is slightly different on each operating system. Here you can find user-contributed pointers for installing GRASS on specific platforms. In particular, many operating systems have package management utilities that can greatly simplify GRASS installation.

== MS Windows ==

:''The official download page [https://grass.osgeo.org/download/windows/ GRASS GIS for MS-Windows]''

There are two main flavours:
* '''OSGeo4W installer''', for a broad set of open source geospatial software packages including GRASS GIS as well as many other packages (QGIS, GDAL/OGR, and more). Advantage: whenever you run again the OSGeo4W installer, it updates the existing installation.
* '''Standalone winGRASS installer''': install GRASS GIS with the required support packages.

=== OSGeo4W installer ===

OSGeo4W is an installer for a broad set of open source geospatial software packages including GRASS GIS as well as many other packages (QGIS, GDAL/OGR, and more). Advantage: whenever you run again the OSGeo4W installer, it updates the existing installation.

* Install using [https://trac.osgeo.org/osgeo4w/ OSGeo4W installer] which installs all dependencies as well (PROJ, GDAL, GEOS, Python, etc.)

==== Launch the OSGeo4W installer ====

Save the downloaded installer (consider keeping it for future updates) and run it as an ''administrator''.

(Note that with Windows 11 the ''desktop'', ''download'', and ''documents'' directories are located in a standard user account directory, e.g. C:\User\username, that is created by default and ''do not have administrator privileges'' by default - even on personal, single-user laptops. Make sure to use an administrator rather than standard user account when running the installer)

You can select either the grass (stable) or grass-daily (development) packages to install.

[[Image:Osgeo4w_1.png|center|thumb|500px|Install with "Administrator" rights]]

==== Variant A) Express installation ====

Use "Express Desktop Install" mode to select stable version.

[[Image:Osgeo4w_2_express.png|center|thumb|500px|Use "Express installation" to select stable version]]

[[Image:Osgeo4w_3_express.png|center|thumb|500px]]

Common installed Python packages:

* python3-gdal
* python3-matplotlib
* python3-wx
* python3-numpy
* python3-pillow
* python3-pip
* python3-ply
* python3-pyopengl
* python3-psycopg2
* python3-six
* python3-pywin32

Additional useful packages (e.g. python3-pandas, msys) can be installed in "Advanced Install" mode.

==== Variant B) Advanced installation ====

Use "Advanced Install Mode" to select development version.

[[Image:Osgeo4w_2_advanced.png|center|thumb|500px|Use "Advanced installation" to select development version]]

[[Image:Osgeo4w_3_advanced.png|center|thumb|500px]]

=== winGRASS standalone installer ===

* Native winGRASS package installer is available [https://grass.osgeo.org/grass-stable/binary/mswindows/native/ here].

=== QGIS with winGRASS installer ===
* QGIS including native winGRASS packages are provided [https://www.qgis.org/wiki/Download here].

== GNU/Linux ==

:''The official page [https://grass.osgeo.org/download/linux/ GRASS GIS Download for GNU/Linux]''

=== Debian ===

A binary version of GRASS is available from the apt repository. As root type:

apt-get install grass grass-doc

This is the easiest way to install GRASS on Debian. If you choose to install a binary version manually from the main web site, be sure to follow the instructions for making symlinks found as a note to the [[https://grass.osgeo.org/grass-stable/binary/linux/snapshot/ GRASS GIS stable weekly snapshot]] release.

==== DebianGIS ====

There is also the wonderful [https://wiki.debian.org/DebianGis DebianGIS] project which has a more recent GRASS version with its related packages. Read here for more [[GRASS in Debian |details]]

==== Compiling GRASS from source ====

* See [[Compile and Install]] of Source Code

=== Installation on Fedora ===

The [https://src.fedoraproject.org/rpms/grass Fedora project] provides RPM-packages for stable releases prepared to install on Fedora systems:

<source lang="bash">
sudo dnf install grass grass-gui
</source>

=== Mageia ===

* [https://madb.mageia.org/package/show/name/grass/ Mageia] provides PROJ/GDAL/GRASS RPMs:

urpmi grass

=== openSUSE ===

* [https://build.opensuse.org/package/show/Application:Geo/grass openSUSE] provides GRASS and related RPM-packages:

<source lang="bash">
sudo zypper refresh
sudo zypper install grass
</source>

Alternatively, one can use the '''One-Click installer''':
https://software.opensuse.org/package/grass

=== Red Hat Enterprise Linux (RHEL, CentOS and EPEL) ===

* [https://src.fedoraproject.org/rpms/grass Fedora] offers GRASS and related binaries for CentOS and EPEL

<source lang="bash">
dnf install grass
</source>

=== Ubuntu ===

GRASS Binaries are available from apt/synaptic. From a terminal type:

sudo apt-get install grass grass-doc

or alternatively, search for and install these packages from Synaptic. This is the easy way to get GRASS on your system. Even if you choose to install binaries from another source, you may want to install this version just so that all (most) dependencies are installed as painlessly as possible.

To get the latest version of GRASS on Ubuntu, compile the code from source. See the [[Compile and Install]] section for a shell script that makes this easy.

== MacOS ==

Precompiled GRASS GIS packages for macOS can be found [https://grass.osgeo.org/download/mac here]. These are distributed as zipped *.dmg packages. Opening the dmg prompts the user to simply drag and drop the app into the Applications folder. In fact, they '''must''' be installed into the Applications folder and may not run properly in other locations.

A brief introduction to how to install via [https://www.macports.org MacPorts]: [[Compiling on macOS using MacPorts]].

== Raspberry Pi ==

:''See the main page [[Raspberry Pi]].''

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

Installation Guide

2026-04-08T03:32:44Z

Ltb25: /* Launch the OSGeo4W installer */

== General ==
:''Note: For compilation of GRASS GIS source code, see [[Compile and Install]]''
This page explains the installation of GRASS binaries.

GRASS GIS requires a workstation running either some flavor of UNIX conforming to POSIX standards like Linux, Mac OS X, Solaris, IRIX, or BSD or MS-Windows. It is also possible to run GRASS in MS Windows by using UNIX translation software such as [[Cygwin]] or natively with MingGW. Ideally, you should have at least 500 Mb for data and 512 Mb RAM. The source code package needs around 270 MB uncompressed. The resulting binaries may need between 20 MB and 180 MB depending on your platform. During a full compilation you may need temporarily up to 150MB including the source code.

The [https://grass.osgeo.org/download/ Software Download Section] of the main GRASS web site contains the latest binaries and source code for all supported platforms. That site also has general directions for installing GRASS manually. However, installation is slightly different on each operating system. Here you can find user-contributed pointers for installing GRASS on specific platforms. In particular, many operating systems have package management utilities that can greatly simplify GRASS installation.

== MS Windows ==

:''The official download page [https://grass.osgeo.org/download/windows/ GRASS GIS for MS-Windows]''

There are two main flavours:
* '''OSGeo4W installer''', for a broad set of open source geospatial software packages including GRASS GIS as well as many other packages (QGIS, GDAL/OGR, and more). Advantage: whenever you run again the OSGeo4W installer, it updates the existing installation.
* '''Standalone winGRASS installer''': install GRASS GIS with the required support packages.

=== OSGeo4W installer ===

OSGeo4W is an installer for a broad set of open source geospatial software packages including GRASS GIS as well as many other packages (QGIS, GDAL/OGR, and more). Advantage: whenever you run again the OSGeo4W installer, it updates the existing installation.

* Install using [https://trac.osgeo.org/osgeo4w/ OSGeo4W installer] which installs all dependencies as well (PROJ, GDAL, GEOS, Python, etc.)

==== Launch the OSGeo4W installer ====

Save the downloaded installer (consider keeping it for future updates) and run it as an ''administrator''.

(Note that with Windows 11 the ''desktop'', ''download'', and ''documents'' directories are located in a standard user account directory, e.g. C:\User\username, that is created by default and ''do not have administrator privileges'' by default - even on personal, single-user laptops. To run the installer, move it to an Administrator-Only directory, e.g. C:\Program Files, or adjust the User Account Control (UAC) settings to Administrator for the user's account it is in, first)

You can select either the grass (stable) or grass-daily (development) packages to install.

[[Image:Osgeo4w_1.png|center|thumb|500px|Install with "Administrator" rights]]

==== Variant A) Express installation ====

Use "Express Desktop Install" mode to select stable version.

[[Image:Osgeo4w_2_express.png|center|thumb|500px|Use "Express installation" to select stable version]]

[[Image:Osgeo4w_3_express.png|center|thumb|500px]]

Common installed Python packages:

* python3-gdal
* python3-matplotlib
* python3-wx
* python3-numpy
* python3-pillow
* python3-pip
* python3-ply
* python3-pyopengl
* python3-psycopg2
* python3-six
* python3-pywin32

Additional useful packages (e.g. python3-pandas, msys) can be installed in "Advanced Install" mode.

==== Variant B) Advanced installation ====

Use "Advanced Install Mode" to select development version.

[[Image:Osgeo4w_2_advanced.png|center|thumb|500px|Use "Advanced installation" to select development version]]

[[Image:Osgeo4w_3_advanced.png|center|thumb|500px]]

=== winGRASS standalone installer ===

* Native winGRASS package installer is available [https://grass.osgeo.org/grass-stable/binary/mswindows/native/ here].

=== QGIS with winGRASS installer ===
* QGIS including native winGRASS packages are provided [https://www.qgis.org/wiki/Download here].

== GNU/Linux ==

:''The official page [https://grass.osgeo.org/download/linux/ GRASS GIS Download for GNU/Linux]''

=== Debian ===

A binary version of GRASS is available from the apt repository. As root type:

apt-get install grass grass-doc

This is the easiest way to install GRASS on Debian. If you choose to install a binary version manually from the main web site, be sure to follow the instructions for making symlinks found as a note to the [[https://grass.osgeo.org/grass-stable/binary/linux/snapshot/ GRASS GIS stable weekly snapshot]] release.

==== DebianGIS ====

There is also the wonderful [https://wiki.debian.org/DebianGis DebianGIS] project which has a more recent GRASS version with its related packages. Read here for more [[GRASS in Debian |details]]

==== Compiling GRASS from source ====

* See [[Compile and Install]] of Source Code

=== Installation on Fedora ===

The [https://src.fedoraproject.org/rpms/grass Fedora project] provides RPM-packages for stable releases prepared to install on Fedora systems:

<source lang="bash">
sudo dnf install grass grass-gui
</source>

=== Mageia ===

* [https://madb.mageia.org/package/show/name/grass/ Mageia] provides PROJ/GDAL/GRASS RPMs:

urpmi grass

=== openSUSE ===

* [https://build.opensuse.org/package/show/Application:Geo/grass openSUSE] provides GRASS and related RPM-packages:

<source lang="bash">
sudo zypper refresh
sudo zypper install grass
</source>

Alternatively, one can use the '''One-Click installer''':
https://software.opensuse.org/package/grass

=== Red Hat Enterprise Linux (RHEL, CentOS and EPEL) ===

* [https://src.fedoraproject.org/rpms/grass Fedora] offers GRASS and related binaries for CentOS and EPEL

<source lang="bash">
dnf install grass
</source>

=== Ubuntu ===

GRASS Binaries are available from apt/synaptic. From a terminal type:

sudo apt-get install grass grass-doc

or alternatively, search for and install these packages from Synaptic. This is the easy way to get GRASS on your system. Even if you choose to install binaries from another source, you may want to install this version just so that all (most) dependencies are installed as painlessly as possible.

To get the latest version of GRASS on Ubuntu, compile the code from source. See the [[Compile and Install]] section for a shell script that makes this easy.

== MacOS ==

Precompiled GRASS GIS packages for macOS can be found [https://grass.osgeo.org/download/mac here]. These are distributed as zipped *.dmg packages. Opening the dmg prompts the user to simply drag and drop the app into the Applications folder. In fact, they '''must''' be installed into the Applications folder and may not run properly in other locations.

A brief introduction to how to install via [https://www.macports.org MacPorts]: [[Compiling on macOS using MacPorts]].

== Raspberry Pi ==

:''See the main page [[Raspberry Pi]].''

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

Installation Guide

2026-04-08T03:31:31Z

Ltb25: /* OSGeo4W installer */

== General ==
:''Note: For compilation of GRASS GIS source code, see [[Compile and Install]]''
This page explains the installation of GRASS binaries.

GRASS GIS requires a workstation running either some flavor of UNIX conforming to POSIX standards like Linux, Mac OS X, Solaris, IRIX, or BSD or MS-Windows. It is also possible to run GRASS in MS Windows by using UNIX translation software such as [[Cygwin]] or natively with MingGW. Ideally, you should have at least 500 Mb for data and 512 Mb RAM. The source code package needs around 270 MB uncompressed. The resulting binaries may need between 20 MB and 180 MB depending on your platform. During a full compilation you may need temporarily up to 150MB including the source code.

The [https://grass.osgeo.org/download/ Software Download Section] of the main GRASS web site contains the latest binaries and source code for all supported platforms. That site also has general directions for installing GRASS manually. However, installation is slightly different on each operating system. Here you can find user-contributed pointers for installing GRASS on specific platforms. In particular, many operating systems have package management utilities that can greatly simplify GRASS installation.

== MS Windows ==

:''The official download page [https://grass.osgeo.org/download/windows/ GRASS GIS for MS-Windows]''

There are two main flavours:
* '''OSGeo4W installer''', for a broad set of open source geospatial software packages including GRASS GIS as well as many other packages (QGIS, GDAL/OGR, and more). Advantage: whenever you run again the OSGeo4W installer, it updates the existing installation.
* '''Standalone winGRASS installer''': install GRASS GIS with the required support packages.

=== OSGeo4W installer ===

OSGeo4W is an installer for a broad set of open source geospatial software packages including GRASS GIS as well as many other packages (QGIS, GDAL/OGR, and more). Advantage: whenever you run again the OSGeo4W installer, it updates the existing installation.

* Install using [https://trac.osgeo.org/osgeo4w/ OSGeo4W installer] which installs all dependencies as well (PROJ, GDAL, GEOS, Python, etc.)

==== Launch the OSGeo4W installer ====

Save the downloaded installer (consider keeping it for future updates) and run it as an ''administrator''.

(Note that with Windows 11 the ''desktop'', ''download'', and ''documents''directories are located in a standard user account directory, e.g. C:\User\username, that is created by default and ''do not have administrator privileges'' by default - even on personal, single-user laptops. To run the installer, move it to an Administrator-Only directory, e.g. C:\Program Files, or adjust the User Account Control (UAC) settings to Administrator for the user's account it is in, first)

You can select either the grass (stable) or grass-daily (development) packages to install.

[[Image:Osgeo4w_1.png|center|thumb|500px|Install with "Administrator" rights]]

==== Variant A) Express installation ====

Use "Express Desktop Install" mode to select stable version.

[[Image:Osgeo4w_2_express.png|center|thumb|500px|Use "Express installation" to select stable version]]

[[Image:Osgeo4w_3_express.png|center|thumb|500px]]

Common installed Python packages:

* python3-gdal
* python3-matplotlib
* python3-wx
* python3-numpy
* python3-pillow
* python3-pip
* python3-ply
* python3-pyopengl
* python3-psycopg2
* python3-six
* python3-pywin32

Additional useful packages (e.g. python3-pandas, msys) can be installed in "Advanced Install" mode.

==== Variant B) Advanced installation ====

Use "Advanced Install Mode" to select development version.

[[Image:Osgeo4w_2_advanced.png|center|thumb|500px|Use "Advanced installation" to select development version]]

[[Image:Osgeo4w_3_advanced.png|center|thumb|500px]]

=== winGRASS standalone installer ===

* Native winGRASS package installer is available [https://grass.osgeo.org/grass-stable/binary/mswindows/native/ here].

=== QGIS with winGRASS installer ===
* QGIS including native winGRASS packages are provided [https://www.qgis.org/wiki/Download here].

== GNU/Linux ==

:''The official page [https://grass.osgeo.org/download/linux/ GRASS GIS Download for GNU/Linux]''

=== Debian ===

A binary version of GRASS is available from the apt repository. As root type:

apt-get install grass grass-doc

This is the easiest way to install GRASS on Debian. If you choose to install a binary version manually from the main web site, be sure to follow the instructions for making symlinks found as a note to the [[https://grass.osgeo.org/grass-stable/binary/linux/snapshot/ GRASS GIS stable weekly snapshot]] release.

==== DebianGIS ====

There is also the wonderful [https://wiki.debian.org/DebianGis DebianGIS] project which has a more recent GRASS version with its related packages. Read here for more [[GRASS in Debian |details]]

==== Compiling GRASS from source ====

* See [[Compile and Install]] of Source Code

=== Installation on Fedora ===

The [https://src.fedoraproject.org/rpms/grass Fedora project] provides RPM-packages for stable releases prepared to install on Fedora systems:

<source lang="bash">
sudo dnf install grass grass-gui
</source>

=== Mageia ===

* [https://madb.mageia.org/package/show/name/grass/ Mageia] provides PROJ/GDAL/GRASS RPMs:

urpmi grass

=== openSUSE ===

* [https://build.opensuse.org/package/show/Application:Geo/grass openSUSE] provides GRASS and related RPM-packages:

<source lang="bash">
sudo zypper refresh
sudo zypper install grass
</source>

Alternatively, one can use the '''One-Click installer''':
https://software.opensuse.org/package/grass

=== Red Hat Enterprise Linux (RHEL, CentOS and EPEL) ===

* [https://src.fedoraproject.org/rpms/grass Fedora] offers GRASS and related binaries for CentOS and EPEL

<source lang="bash">
dnf install grass
</source>

=== Ubuntu ===

GRASS Binaries are available from apt/synaptic. From a terminal type:

sudo apt-get install grass grass-doc

or alternatively, search for and install these packages from Synaptic. This is the easy way to get GRASS on your system. Even if you choose to install binaries from another source, you may want to install this version just so that all (most) dependencies are installed as painlessly as possible.

To get the latest version of GRASS on Ubuntu, compile the code from source. See the [[Compile and Install]] section for a shell script that makes this easy.

== MacOS ==

Precompiled GRASS GIS packages for macOS can be found [https://grass.osgeo.org/download/mac here]. These are distributed as zipped *.dmg packages. Opening the dmg prompts the user to simply drag and drop the app into the Applications folder. In fact, they '''must''' be installed into the Applications folder and may not run properly in other locations.

A brief introduction to how to install via [https://www.macports.org MacPorts]: [[Compiling on macOS using MacPorts]].

== Raspberry Pi ==

:''See the main page [[Raspberry Pi]].''

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

GIS Concepts

2025-06-24T23:06:54Z

Ltb25: /* Background material */

== Geodesy and Cartography ==
=== Background material ===

* [http://oceanservice.noaa.gov/education/kits/geodesy/welcome.html An introduction to Geodesy] from NOAA (currently unavailable)
* [http://en.wikipedia.org/wiki/Geodesy Wikipedia's Geodesy entry]
* [http://en.wikipedia.org/wiki/GIS Wikipedia's GIS entry]
* [http://www.nga.mil/portal/site/maritime/ Bowditch's American Practical Navigator] - (especially chapter 2)
* [http://earth-info.nima.mil/GandG/publications/ NGA Geodesy and Geophysics publications]
* [http://www.ordnancesurvey.co.uk/oswebsite/gps/information/coordinatesystemsinfo/guidecontents/index.html UK Ordnance Survey primer on coordinate system concepts] ([http://www.ordnancesurvey.co.uk/gps/docs/A_Guide_to_Coordinate_Systems_in_Great_Britain.pdf PDF])
* Clifford J Mugnier's [https://www.asprs.org/asprs-publications/grids-and-datums Grids and Datums column from PE&RS] containing detailed descriptions of many national projections & datums

=== Map projections ===

* [http://www.mapref.org/ MapRef] - The Collection of Map Projections and Reference Systems for Europe
* [http://www.remotesensing.org/geotiff/proj_list/ Projections Transform Lists] (PROJ4)
* [http://www.dmap.co.uk/utmworld.htm UTM Zones]

EPSG:
* [http://www.epsg.org EPSG projection codes]
* [http://www.epsg-registry.org/ EPSG database search]
* [http://spatialreference.org/ Spatialreference community portal]

Projection galleries:
* [http://www.progonos.com/furuti/MapProj/CartIndex/cartIndex.html Map projection concepts] by Carlos Furuti
* [http://www.csiss.org/map-projections/index.html Map projection gallery] by Paul Anderson ([http://www.galleryofmapprojections.com/ old link])


=== Map datums ===

An extra calculation is needed when re-projecting maps and data between
two different co-ordinate systems (in addition to the re-projection) if
the two co-ordinate systems are based on different models of the
curvature of the earth. E.g. OSGB36 uses the Airy ellipsoid and WGS84 uses the WGS84 ellipsoid, which have slightly different sizes and shapes. The error is not large - generally a few hundred metres at most on the ground.
The datum transformation parameters describe this adjustment
mathematically.

As the transformation between any two datums is approximate and varies by location, different sets of parameters are often offered to give improved accuracy in different regions of a country. In general there is no one "correct" set of transformation parameters - indeed the accuracy changes over time due to tectonic movements in the Earth.

* [http://sourceforge.net/mailarchive/forum.php?thread_name=1190060064.27461.57.camel%40blackpad&forum_name=jump-pilot-devel A brief history of map datums] for the layman
* [http://www.colorado.edu/geography/gcraft/notes/datum/datum.html An introduction to geodetic datums] by Peter Dana
* [http://home.online.no/~sigurdhu/WGS84_Eng.html How WGS 84 defines the Earth]
* A discussion of [http://www.linz.govt.nz/geodetic/conversion-coordinates/geodetic-datum-conversion/nzgd1949-nzgd2000/index.aspx 3-term, 7-term, and NTv2 grid datum transformations] by Land Information New Zealand
: (besides the web page have a look at the PDF fact sheet and guide linked therein)

* Vertical datum files: http://download.osgeo.org/proj/vdatum/

==How GRASS deals with geodetics==

As far as GRASS is concerned, an ellipsoid and a spheroid are the same thing, and ellipsoid is the prefered name.

As far as GRASS is concerned, a datum is made up of an ellipsoid and an origin.
Setting a datum is optional, but highly recommended.

GRASS uses the [https://proj.org PROJ] library.

=== Modules controling a location's map projection ===
* {{cmd|g.proj}} help page

=== Modules for reprojecting GIS maps and data ===

* {{cmd|r.proj}} for reprojecting raster maps
* {{cmd|v.proj}} for reprojecting vector maps
* {{cmd|m.proj}} for reprojecting a list of coordinate pairs

=== Modules for georectifying images ===

* {{cmd|r.region}} for resetting a raster map's bounds information
* gis.m GIS manager GeoReferencing tool (File menu)
* {{cmd|i.points}} and {{cmd|i.vpoints}} for setting GCPs
* {{cmd|i.rectify}} for georectifying imagery
* [http://www.gdal.org gdalwarp] (use with gdal_translate, see the i.warp script in the wiki [[GRASS_AddOns#Imagery_add-ons|AddOns]] page)

;[[Georeferencing]]

==GIS Data types==

===Raster Data===

Data which occurs in a regularly spaced grid. e.g. a satellite image or digital terrain map. 
Region settings determine the spatial extent and resolution of the grid.

;{{cmd|rasterintro}}

[[GRASS Raster Mask]]

[[GRASS raster semantics]]

===3D Raster Data (Voxel)===

A stack of 2D raster maps.

;{{cmd|raster3dintro}}

===Vector Data===

Data which occurs as a series of coordinates. e.g. a GPS position or coastline map. May be a point, line, area, etc in either 2D or 3D space. Generally independent of region settings.

;{{cmd|vectorintro}}
[[Vectordata]]

=== Imagery Data ===
Pixelated photographic or satellite images, often imported from a
[http://en.wikipedia.org/wiki/GeoTIFF GeoTIFF] or PNG image file.

As far as the GIS is concerned this is just another raster map, but there are several modules specially tailored for rectification and processing common imagery types. e.g. ortho-photos or multi-channel [[LANDSAT]] data.

* {{cmd|imageryintro}}

* The GRASS [[Image processing]] wiki page

=== Old GRASS GIS 5 / 6 Site Data===
Old versions of GRASS (5 and earlier) treated point data separate to line and polygon data. GRASS 6 classes all vector data features the same. Convert old sites file data into GRASS 6 vector format with the GRASS 6 {{cmd|v.in.sites}} or
{{cmd|v.in.sites.all}} modules.

==Conversions between data types==

The following table is intended to catalog transformations from one type of data to another: 
''[table is currently incomplete!]''

{| border="1"
| From / To
!{{cmd|rasterintro}}
!{{cmd|raster3dintro}}
!{{cmd|vectorintro}}
|-
! Raster
| r.mapcalc
| r.to.rast3
| r.to.vect, v.sample, r.volume
|-
! 3D Raster
| r3.to.rast, r3.cross.rast
| r3.mapcalc
|
|-
! Vector
| v.to.rast, v.surf.rst, v.surf.idw
| v.vol.rst, v.vol.idw, v.to.rast3
| v.clean
|-
! Data
| r.in.*
| r3.in.*
| v.in.*
|}

==How a GRASS project is organized==

GRASS data is stored in a three level structure, the database, location and mapset. These can be found in a series of nested directories on the user's computer. All three must exist and are set at GRASS startup time.

===The Database===

The directory in which all GIS data is to be stored.

e.g. <tt>~/grassdata/</tt>

===The Location===

A ''location'' is a GRASS project consisting of an area, projection definition (or unprojected), a grouping of mapsets, all with the same projection settings. A location is a subdirectory of the GRASS ''database''.

e.g. world_lat_lon, utm_zone_59, or west_coast

A ''location'' contains one or many ''mapsets''.

===The Mapset===

A ''mapset'' contains map(s), it is a subdirectory of a ''location''.
Conceptually, if several mapsets are used in a location, they may be assigned to different users (each has one or several own mapsets to work in and cannot modify thos of other users), and/or it they are used to organize a project (''location'') by subareas or subprojects.
There are no specific organizational limitations.

There is always a PERMANENT mapset which is readable from all other mapsets within the same location. Read access to maps in other mapsets is managed with the 'g.mapsets' command or by adding the "@" symbol and mapset name (e.g. <tt>map@othermapset</tt>).

==Raster GIS Analysis==

===Simple Raster Math===

Sometimes when analyzing the relationship between two or more raster data sets, a relatively simple mathematical approach is best. One example using the {{cmd|r.mapcalc}} tool would be to look at changes between two raster data sets. By subtracting the values in these two data sets you can assume that resulting cells with a positive value have a positive change and those with a negative value have negative change. If the cell values have a zero value then there would be no change.

GRASS comes bundled with the {{cmd|r.mapcalc}} command line tool as well as a GUI interface for the tool accessible using the {{cmd|r.mapcalculator}} command. This GUI allows the user to easily assign raster maps to the variables used in the formulas and easily create mathematical strings that will result in a new raster data set containing the results.

[[Category:Community]]
[[Category:Raster]]
[[Category:Vector]]

Talk:GRASS Developer Summit Raleigh 2025

2025-05-26T14:36:57Z

Ltb25: /* Laura Belica | NC State University */

{{toc|right}}

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

== Organizing Team ==

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

== Detailed Schedule ==

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

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

Room: 5101-Executive Board Room

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

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

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

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

Room: 5101-Executive Board Room

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

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

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

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

Room: 5101-Executive Board Room

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

== Daily tasks for participants ==

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

== Participant reports ==

Per-person reports from the meeting.

=== Giuseppe Amatulli | Yale University ===

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

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

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

=== Abdullah Azzam | New Mexico State University ===
Monday 5/19
* Created first PR; fixed broken links on the website [https://github.com/OSGeo/grass-website/pull/538 #538]

Tuesday 5/20
*Started working on a new addon and switched to cookiecutter python template from the C implementation.
* Helped Andres compile OpenMP in Mac.

Wednesday 5/21
*Drafted the addon and discussed the changes with Dr. Cho and Anna.

Thursday 5/22
* Pushed a new GRASS Addon ''r.curvenumber'' [https://github.com/OSGeo/grass-addons/pull/1403 #1403]

Friday 5/23
*Addressed the fixes and issues in ''r.curvenumber'' and discussed another addon with Dr. Cho

Saturday 5/24
*Discussed and developed another addon ''r.scs.runoff'' with Anna.

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

* POSE related activities

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

*my focus was on developing a draft/test tutorial (in Quarto) for a standard basic hydrological study workflow [extraction of nested as well as disconnected study streams and watersheds informed by ground-truthed stream CHIP and outlet point data and estimating stream segment length, watershed area, mean slope, etc.]. The tutorial includes the crucial pre-work of how to figure out the most appropriate project/location and extent for elevation data import [e.g., if region of interest is much smaller than tile extent and/or spans multiple tiles] as well as considerations of some of the downstream impacts of resolution, extent, region etc. when additional datasets with different resolutions and extents (e.g., roads, land cover, sampling points) may be incorporated later.

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

23 May
* tested workflow

24 May
* worked on tutorial qmd
* explored different alternatives for transforming aspect for computation of mean watershed aspect within GRASS and with R and Python

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

* CI optimization

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

* CMake, conda, CI, Mentoring

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

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

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

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

Friday 5/23
* CMake and Conda Testing on Linux
* CMake Testing on Windows
* CI: Discussion with Edouard
* Mentoring: Chung-Yuan, Abdullah

Saturday 5/24
* [https://github.com/OSGeo/grass/pull/5771 MSVC: Use the same M_PI_4 value to avoid redefinition warnings]
* CMake Testing on Windows
* Mentoring: Abdullah

=== Edouard Choinière ===

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

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

=== Laurent Courty ===

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

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

* r.in.pdal

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

* A tool to calculate gravity terrain corrections

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

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

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

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

* Plan: developing ([https://github.com/baharmon/r.earthworks r.earthworks]) addon & tutorials
* Log: [https://github.com/baharmon?tab=overview&from=2025-05-19&to=2025-05-24 GitHub activity]
* Activities: published r.earthworks to addons repo, discussed modernizing colors, & started map algebra tutorials
* Unfinished: develop map algebra tutorials, open issue about modernizing color, start discussion on citations, open issue about v.to.rast bug, etc...

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

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

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

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

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

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

Planned work: CMake build system; perhaps Conda recipe

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

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

* Helped young students in build configuration and debugging techniques.

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

=== Chung-Yuan Liang ===

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

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

* r.in.pdal

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

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

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

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

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

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

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

=== Michael Mulqueen | MassGIS ===

* depth to water, hydro from lidar, etc

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

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

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

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

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

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

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

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

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

* Documentation
* Investigate [https://pixi.sh/latest/ Pixi] to manage installation and build procedures.
* Learned more about GRASS's vector format and modules
** Need a deeper explanation on how the different vector subtypes behave
** Need a cleaner output of v.clean so users can inspect error types
** Documentation could use a comparison of GRASS's topological model and components with that of OGC's Simple Features

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

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

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

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

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

* improve the test coverage of imagery modules.

=== Krishna Prasad Sheshadri ===

*

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

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

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

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

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

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

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

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

* JSON, mentoring

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

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

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

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

* r.sim.water

== Guests and remote participants ==

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

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

=== Markus Neteler | mundialis ===

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

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

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

Talk:GRASS Developer Summit Raleigh 2025

2025-05-26T14:04:42Z

Ltb25: /* Laura Belica | NC State University */

{{toc|right}}

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

== Organizing Team ==

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

== Detailed Schedule ==

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

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

Room: 5101-Executive Board Room

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

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

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

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

Room: 5101-Executive Board Room

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

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

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

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

Room: 5101-Executive Board Room

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

== Daily tasks for participants ==

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

== Participant reports ==

Per-person reports from the meeting.

=== Giuseppe Amatulli | Yale University ===

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

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

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

=== Abdullah Azzam | New Mexico State University ===
Monday 5/19
* Created first PR; fixed broken links on the website [https://github.com/OSGeo/grass-website/pull/538 #538]

Tuesday 5/20
*Started working on a new addon and switched to cookiecutter python template from the C implementation.
* Helped Andres compile OpenMP in Mac.

Wednesday 5/21
*Drafted the addon and discussed the changes with Dr. Cho and Anna.

Thursday 5/22
* Pushed a new GRASS Addon ''r.curvenumber'' [https://github.com/OSGeo/grass-addons/pull/1403 #1403]

Friday 5/23
*Addressed the fixes and issues in ''r.curvenumber'' and discussed another addon with Dr. Cho

Saturday 5/24
*Discussed and developed another addon ''r.scs.runoff'' with Anna.

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

24 May
* worked on tutorial qmd

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

* CI optimization

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

* CMake, conda, CI, Mentoring

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

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

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

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

Friday 5/23
* CMake and Conda Testing on Linux
* CMake Testing on Windows
* CI: Discussion with Edouard
* Mentoring: Chung-Yuan, Abdullah

Saturday 5/24
* [https://github.com/OSGeo/grass/pull/5771 MSVC: Use the same M_PI_4 value to avoid redefinition warnings]
* CMake Testing on Windows
* Mentoring: Abdullah

=== Edouard Choinière ===

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

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

=== Laurent Courty ===

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

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

* r.in.pdal

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

* A tool to calculate gravity terrain corrections

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

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

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

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

* Plan: developing ([https://github.com/baharmon/r.earthworks r.earthworks]) addon & tutorials
* Log: [https://github.com/baharmon?tab=overview&from=2025-05-19&to=2025-05-24 GitHub activity]
* Activities: published r.earthworks to addons repo, discussed modernizing colors, & started map algebra tutorials
* Unfinished: develop map algebra tutorials, open issue about modernizing color, start discussion on citations, open issue about v.to.rast bug, etc...

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

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

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

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

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

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

Planned work: CMake build system; perhaps Conda recipe

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

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

* Helped young students in build configuration and debugging techniques.

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

=== Chung-Yuan Liang ===

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

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

* r.in.pdal

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

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

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

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

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

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

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

=== Michael Mulqueen | MassGIS ===

* depth to water, hydro from lidar, etc

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

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

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

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

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

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

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

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

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

* Documentation
* Investigate [https://pixi.sh/latest/ Pixi] to manage installation and build procedures.
* Learned more about GRASS's vector format and modules
** Need a deeper explanation on how the different vector subtypes behave
** Need a cleaner output of v.clean so users can inspect error types
** Documentation could use a comparison of GRASS's topological model and components with that of OGC's Simple Features

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

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

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

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

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

* improve the test coverage of imagery modules.

=== Krishna Prasad Sheshadri ===

*

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

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

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

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

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

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

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

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

* JSON, mentoring

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

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

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

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

* r.sim.water

== Guests and remote participants ==

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

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

=== Markus Neteler | mundialis ===

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

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

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

Talk:GRASS Developer Summit Raleigh 2025

2025-05-19T21:50:43Z

Ltb25: /* Laura Belica | NC State University */

Talk:GRASS Developer Summit Raleigh 2025

2025-05-19T21:48:26Z

Ltb25: /* Laura Belica | NC State University */

Talk:GRASS Developer Summit Raleigh 2025

2025-05-19T21:34:08Z

Ltb25: /* Laura Belica | NC State University */

Talk:GRASS Developer Summit Raleigh 2025

2025-05-19T21:23:45Z

Ltb25: