GRASS-Wiki - User contributions [en]

GRASS Community Meeting San Michele 2026

2026-06-08T14:53:54Z

Neteler: update arrival + activities (Markus)

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

{{toc|right}}

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

== Sponsors ==

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

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

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

== Purpose ==
The ''GRASS Community Meeting'' is a great occasion for folks to support the development by actively contributing to the project in different ways. These include source code updates, documentation (manuals, wiki, tutorials), translations, website improvements or likewise. The community meeting is also a get-together where supporters, contributors, power users and developers make decisions and tackle larger problems related to the project, discuss and collaboratively resolve bugs, plan the direction for the project and work on new features. We welcome people committed to improving the GRASS project and the interfaces to QGIS, GDAL, PostGIS, R, OGC Services and others.

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

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

== Agenda ==

Agenda is being refined.

=== Saturday, July 11 ===

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

=== Sunday, July 12 ===

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

=== Monday, July 13 ===

* FHS
* Updating the GRASS Roadmap

=== Tuesday, July 14 ===

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

=== Wednesday, July 15 ===

* Python API review
* Plan PSC elections

=== Thursday, July 16 ===

* Reducing PR backlog

=== Friday, July 17 ===

* Address issues for 8.6.0 release

=== Saturday, July 18 ===

* Website review

=== Sunday, July 19 ===

Day of departure.

== Participation ==

Please add your name here:

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;"
!width=50px|'''Number'''
!width=130px|'''Participant '''
!width=100px|'''Country'''
!width=100px|'''Arrival'''
!width=100px|'''Departure'''
!'''Topics'''
!'''Notes'''
|-
|1
| [[User:Lucadelu|Luca Delucchi]]
| Italy
|
|
|
|
|-
|2
| [[User:wenzeslaus|Vaclav Petras]]
| United States
| 11.07.
| 19.07.
| grass.tools, pytest, subcommands, reviews
|
|-
|3
| [[User:Annakrat|Anna Petrasova]]
| United States
| 11.07.
| 19.07.
| GSoC, reviews, PR backlog, tutorials
|
|-
|4
| [[User:Neteler|Markus Neteler]]
| Germany
| 06.07.
| 19.07. (?)
| documentation, website, reviews, tutorials, knowledge-transfer
|
|-
|5
| [[User:Sbl|Stefan Blumentrath]]
| Norway
| 11.07. (presumably)
| 18.07. (presumably)
| Handling Copernicus data with GRASS / actinia
|
|-
|6
| [[User:Hellik|Helmut Kudrnovsky]]
| Austria
|
|
|
|
|-
|7
| [[User:Veroandreo|Verónica Andreo]]
| Argentina
| 11.07.
| 19.07.
|
|
|-
|8
| [[User:Ctwhite|Corey White]]
| United States
| 11.07.
| 19.07.
| grass.jupyter, documentation, website, reviews, tutorials
|
|-
|9
| [[User:Echoix|Edouard Choinière]]
| Canada
| 11.07. (presumably)
| 19.07. (presumably)
| Reviews, CI, pytest, Windows GUI, i18n, undecided
|
|-
|10
| [[User:Mazingaro|Alen Mangafić]]
| Slovenia
| 13.07.
| 17.07.
| i.hyper: [https://grass.osgeo.org/grass-stable/manuals/addons/i.hyper.html Road Map] fullfilling; State of GRASS @FOSS4G 2026
|
|-
|11
| Tomaž Žagar
| Slovenia
| 13.07.
| 17.07.
| i.hyper: [https://grass.osgeo.org/grass-stable/manuals/addons/i.hyper.html Road Map] fullfilling
|
|-
|12
| Matjaž Krebs
| Slovenia
| 13.07.
| 17.07.
| i.hyper: [https://grass.osgeo.org/grass-stable/manuals/addons/i.hyper.html Road Map] fullfilling
|
|-
|}

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

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

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

=== Getting there ===

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

== Accommodation and Costs ==

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

* Travel
* Lodging

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

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

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

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

== Individual Preparation ==

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

== FAQ ==

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

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

PSC Meeting 2026-05-08

2026-05-11T15:57:42Z

Neteler: Some URLs added

== Participants ==

* Helli
* Anna
* Vashek
* Nicklas
* Paulo
* Linda
* Vero
* Huidae

== Agenda ==

The topics proposed are:

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

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

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

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

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

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

== Minutes ==

'''1. OSGeo server access'''

* A ticket was opened a month ago to request OSGeo server access for Corey: https://trac.osgeo.org/osgeo/ticket/3561
** No response has been received so far from OSGeo SAC.
** [Action] Use the same ticket or create new ones to get Nicklas and Edouard access to the server.

'''2. GRASS Community Meeting - San Michele'''

* We drafted the agenda for the event, as it will support the [https://www.fossgis.de/wiki/F%C3%B6rderantr%C3%A4ge/GRASS_GIS_Community_Meeting_2026 sponsoring request to FOSSGIS e.V.]
* [Action] Vero will meet with MarkusN to help prepare the FOSSGIS request.
* We discussed criteria for (partial) reimbursement of participants, esp. in terms of commits to the main grass repo.
* [Action] Treasurer will propose who to reimburse and how much.
* [Action] All: Let's invite contributors personally, too.

'''3. Release'''

* [https://grass.osgeo.org/news/2026_05_08_grass_8_5_0_released/ 8.5.0 is out]!
* We discussed the release procedure based on the [https://github.com/OSGeo/grass/discussions/7328 #7328], in particular, whether Release Candidates are needed, given that they are rarely tested. Bas is a notable exception, consistently providing feedback on RCs.
* The goal is to get 8.6 out approximately 6 months after 8.5, as several things are almost ready and did not make it into 8.5.
* We went through the release announcement and the list of changes on GitHub and did minor edits during the meeting.
* [Action] Update versions and dates in the roadmap.
* [Action] Update Download/Windows layout since there is no standalone installer.
* [Action] Remove all "GIS" from the Download menu.

'''4. GSoC'''

* First time under [https://numfocus.org/programs/google-summer-code NumFocus].
* GRASS was allocated 3 students. Their projects and mentors are as follows:
** '''Pytest''' — Mentors: Vashek and Corey
** '''Integrating STDS into Data Catalog''' — Mentors: Anna and Stefan (Vero and Linda are interested in following this topic)
** '''Parallelise r.proj''' — Mentor: Huidae
* The first two projects will include adding JSON output to the tools they address.
* NumFOCUS acts as the fiscal intermediary but is not heavily involved in day-to-day matters.
* Proposal to use GRASS budget to pay for AI tools for GSoC students — to be discussed further.

'''5. Funding/Sponsoring'''

* We went through the new sponsoring page.
* New tiers were suggested by NumFOCUS.
* [Action] Ping Robert Dzur to check whether they want to sponsor the meeting in San Michele.

[[Category:PSC]]

PSC Meeting 2026-05-08

2026-05-10T23:27:17Z

Neteler: /* Minutes */

== Participants ==

* Helli
* Anna
* Vashek
* Nicklas
* Paulo
* Linda
* Vero
* Huidae

== Agenda ==

The topics proposed are:

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

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

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

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

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

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

== Minutes ==

'''1. OSGeo server access'''

* A ticket was opened a month ago to request OSGeo server access for Corey: https://trac.osgeo.org/osgeo/ticket/3561
* No response has been received so far from OSGeo SAC.
* [Action] Use the same ticket or create new ones to get Nicklas and Edouard access to the server.

'''2. GRASS Community Meeting - San Michele'''

* We drafted the agenda for the event, as it will support the sponsoring request to FOSSGIS e.V.
* [Action] Vero will meet with MarkusN to help prepare the FOSSGIS request.
* We discussed criteria for (partial) reimbursement of participants, esp. in terms of commits to the main grass repo.
* [Action] Treasurer will propose who to reimburse and how much.
* [Action] All: Let's invite contributors personally, too.

'''3. Release'''

* [https://grass.osgeo.org/news/2026_05_08_grass_8_5_0_released/ 8.5.0 is out]!
* We discussed the release procedure based on the [https://github.com/OSGeo/grass/discussions/7328 #7328], in particular, whether Release Candidates are needed, given that they are rarely tested. Bas is a notable exception, consistently providing feedback on RCs.
* The goal is to get 8.6 out approximately 6 months after 8.5, as several things are almost ready and did not make it into 8.5.
* We went through the release announcement and the list of changes on GitHub and did minor edits during the meeting.
* [Action] Update versions and dates in the roadmap.
* [Action] Update Download/Windows layout since there is no standalone installer.
* [Action] Remove all "GIS" from the Download menu.

'''4. GSoC'''

* First time under NumFocus.
* GRASS was allocated 3 students. Their projects and mentors are as follows:
** '''Pytest''' — Mentors: Vashek and Corey
** '''Integrating STDS into Data Catalog''' — Mentors: Anna and Stefan (Vero and Linda are interested in following this topic)
** '''Parallelise r.proj''' — Mentor: Huidae
* The first two projects will include adding JSON output to the tools they address.
* NumFOCUS acts as the fiscal intermediary but is not heavily involved in day-to-day matters.
* Proposal to use GRASS budget to pay for AI tools for GSoC students — to be discussed further.

'''5. Funding/Sponsoring'''

* We went through the new sponsoring page.
* New tiers were suggested by NumFOCUS.
* [Action] Ping Robert Dzur to check whether they want to sponsor the meeting in San Michele.

[[Category:PSC]]

PSC Meeting 2026-05-08

2026-05-02T13:19:43Z

Neteler: /* Agenda */

== Participants ==

* TBD

== Agenda ==

The topics proposed are:

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

* [[GRASS Community Meeting San Michele 2026]]
** Wiki created, event announced
** Agenda
** Rooms, food, housing
** FOSSGIS e.V. request: support needed to complete and submit the request

* Releases
** [https://github.com/OSGeo/grass/releases/tag/8.5.0RC1 8.5 RC1]
*** did anyone test it?
** How are we for 8.5.0?

* GSoC

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

* ...
* add your topic here

== Minutes ==

[[Category:PSC]]

GRASS Community Meeting San Michele 2026

2026-04-15T09:57:45Z

Neteler: /* Participation */ +Markus Neteler

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

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

== Sponsors ==

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

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

== Purpose ==
The ''GRASS Community Meeting'' is a great occasion for folks to support the development by actively contributing to the project in different ways. These include source code updates, documentation (manuals, wiki, tutorials), translations, website improvements or likewise. The community meeting is also a get-together where supporters, contributors, power users and developers make decisions and tackle larger problems related to the project, discuss and collaboratively resolve bugs, plan the direction for the project and work on new features. We welcome people committed to improving the GRASS project and the interfaces to QGIS, GDAL, PostGIS, R, OGC Services and others.

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

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

== Agenda ==

Agenda is forthcoming.

=== Saturday, July 11 ===

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

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

Day of departure.

== Participation ==

Please add your name here:

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;"
!width=50px|'''Number'''
!width=130px|'''Participant '''
!width=100px|'''Country'''
!width=100px|'''Arrival'''
!width=100px|'''Departure'''
!'''Topics'''
!'''Notes'''
|-
|1
| [[User:Lucadelu|Luca Delucchi]]
| Italy
|
|
|
|
|-
|2
| [[User:wenzeslaus|Vaclav Petras]]
| United States
|
|
|
|
|-
|3
| [[User:Annakrat|Anna Petrasova]]
| United States
|
|
|
|
|-
|4
| [[User:Neteler|Markus Neteler]]
| Germany
|
|
|
|
|-
|5
|
|
|
|
|
|
|-
|}

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

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

=== Getting there ===

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

== Accommodation and Costs ==

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

* Travel
* Lodging

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

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

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

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

== Individual Preparation ==

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

== FAQ ==

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

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

Category:2026

2026-04-15T09:20:53Z

Neteler: Created blank page

GRASS Budget 2026

2026-04-15T09:19:54Z

Neteler: fix Category

This is proposed budget (not necessarily the actual expenses).

== Income ==

{| class="wikitable"
! Item !! USD !! EUR !! Notes
|-
| Request to OSGeo (general budget) || 2,000.00 || 1,909.48 || OSGeo Projects budget
|-
| Expected Donations || 550.00 || 525.11 || Based on average from 2020-2022, $760 2024 (Nov-Nov)
|-
| Total income || 2,000.00 || 1,909.48 ||
|}

== Expenses ==

{| class="wikitable"
! Item !! USD !! EUR !! Notes
|-
| Events, Sprints, Travel || || ||
|-
| Travel to multip-project event (e.g., sprint) || 2,200.00 || 2,100.43 || Multiple travels on a continent or one travel to a different continent
|-
| Local project sprints and meetups || 500.00 || 477.37 || Community contributions to the sprint through the budget
|-
| Subtotal || 2,200.00 || 2,100.43 ||
|-
| || || ||
|-
| Grants || || ||
|-
| Community grants || 2,000.00 || 1,909.48 || Community members (including students) can apply with a plan, PSC decides by motion
|-
| Subtotal || 2,000.00 || 1,909.48 ||
|-
| || || ||
|-
| Marketing || || ||
|-
| T-shirts, swag for users, conferences, ... || 200.00 || 190.95 || Community members can request for local or global events
|-
| Stickers and magnets (as above) || 200.00 || 190.95 || Community members can request for local or global events
|-
| Social media management service || 201.60 || 192.48 || Publer in Dec for 1 year 3 accounts
|-
| Subtotal || 601.60 || 574.37 ||
|-
| || || ||
|-
| Total expenses || 4,801.60 || 4,584.29 ||
|}

== Balance ==

{| class="wikitable"
! Item !! USD !! EUR !! Notes
|-
| Year balance (income - expenses) || -2,801.60 || -2,674.81 || If negative, it needs to be covered by additional fundraising and surplus.
|-
| Balance in Open Collective || 7,302.42 || 6,971.93 || State from December 26, 2025
|-
| Balance of persistent budget at OSGeo || 2,000.00 || 1,909.48 || 3*500 USD from GSoC 2024 + 1*500 USD from GSOC 2025
|-
| EOY balance (year balance + surplus) || 6,500.82 || 6,206.61 ||
|}

Edits: Ask the [[PSC#Members|treasurer]] about editing this page.

[[Category: Budget]]
[[Category: 2026]]

Compile and Install

2026-04-02T12:21:04Z

Neteler: +python3-pip; fix libfftw3

'''Disclaimer''': This page explains how to turn the GRASS source code into an installable binary package ("compilation") for different operating systems. If you just want to get ready-to-use binaries, go [https://grass.osgeo.org/download/ here], otherwise read on...

== How to do compilation and installation of GRASS? ==

Here we explain the procedure to compile GRASS from GitHub, but it also applies to official GRASS 8 releases.

''For installation of precompiled binary packages, see the main [[Installation Guide]].''

For detailed information on compilation, please see the [https://github.com/OSGeo/grass/blob/main/INSTALL.md INSTALL] file in the source code.

=== Prerequisites ===

==== Extra libraries ====
GRASS needs at least two extra libraries: PROJ and GDAL/OGR. It is recommended to download them as ready-to-use packages for your software platform (Linux distribution, Windows, Mac...).

Other libraries needed to run GRASS are listed on the [https://github.com/OSGeo/grass/blob/main/REQUIREMENTS.md requirements page].

To compile, you will also need the respective "-devel" packages; see below for details.

==== Download GRASS source code ====

First, [https://grass.osgeo.org/download/ download the GRASS source code].

=== Generic Compilation and installation procedure ===

* It is wise that compilation processes are carried out as a normal user: If you want to get the source code in a place where you do not have write permissions (e.g. in /usr/local/src/) just follow this:
cd /usr/local/src/
su -c 'mkdir grass8'
su -c 'chown yourlogin:yourgroup grass8'

Otherwise if you have permissions just continue as a normal user:
mkdir $HOME/src
cd $HOME/src/
git clone https://github.com/OSGeo/grass.git grass_main

* run configure with parameters to adapt the compile process to your own system. To see what options can be passed to it, run:
./configure --help | less


It may (!) look like this:

./configure \
--with-cxx \
--with-sqlite \
--with-python \
--with-geos \
--with-gdal=/usr/bin/gdal-config \
--with-cairo --with-cairo-ldflags=-lfontconfig \
--with-freetype \
--with-freetype-includes=/usr/include/freetype2 \
--with-proj --with-proj-share=/usr/share/proj

You may have to explicitly state the path for certain packages (i.e., gdal). The Unix 'locate' command will come in handy for finding the path of the package you need (you may have to run locate as root ex: sudo locate gdal-config).

Please note that the paths mentioned may widely vary due to the distribution used.
See [[Compile_and_Install#Platform_Specific_Notes|Platform Specific Notes]] below.

Depending on your needs it may be a good idea to include debugging hooks.
: See [[GRASS_Debugging#Compile_Time_Setup]].
CFLAGS="-ggdb -Wall -Werror-implicit-function-declaration" ./configure ...

At the end of configuration process you should get report not much different from this:

GRASS is now configured for: x86_64-pc-linux-gnu

Source directory: /home/user/software/grass_main
Build directory: /home/user/software/grass_main
Installation directory: ${prefix}/grass84
Startup script in directory:${exec_prefix}/bin
C compiler: gcc -O2 -march=native -std=gnu99 -fexceptions -fstack-protector -m64 -fdiagnostics-color
C++ compiler: c++ -g -Wall
Building shared libraries: yes
OpenGL platform: X11

MacOSX application: no
MacOSX architectures:
MacOSX SDK:

BLAS support: yes
BZIP2 support: no
C++ support: yes
Cairo support: yes
DWG support: no
FFTW support: yes
FreeType support: yes
GDAL support: yes
GEOS support: yes
[...]

* Let's compile it (takes a little while...)!
make -j2
* At the end, you should get report not much different from this:
----------------------------------------------------------------------
Following modules are missing the 'description.html' file in src code:
----------------------------------------------------------------------
GRASS compilation log
-------------------------
Started compilation: Mon 19 Aug 2024 10:47:57 PM CEST
--
Errors in:
No errors detected.
--
Finished compilation: Mon 19 Aug 2024 10:55:12 PM CEST
(In case of errors please change into the directory with error and run 'make')

* If there is any error, change directory to directory with error and run "make" again. Report occurring bug to GRASS mailing list
* Once the installation process is finished, you're ready to install GRASS system wide.
su -c 'make install'
* enjoy GRASS:
grass

=== What else? ===

If you want to use [https://www.qgis.org QGIS], then also compile the GRASS-GDAL/OGR plugin. This is also useful to access your GRASS-data
from other application using GDAL/OGR like [[R_statistics/ R]].
* [[Compile and install GRASS and QGIS with GDAL/OGR Plugin]] (enables QGIS to read GRASS data directly)

=== Compile and install GDAL-GRASS plugin ===

* See [[Compile and install GDAL-GRASS plugin]]

=== Platform Specific Notes ===

==== Linux ====

Linux comes in various flavours, i.e. distributions.

===== Distribution related packaging =====

Examples:

* Archlinux: https://aur.archlinux.org/packages/grass
* Centos: https://src.fedoraproject.org/rpms/grass
* Debian: https://trac.osgeo.org/grass/wiki/DebianUbuntuPackaging
* EPEL: https://src.fedoraproject.org/rpms/grass
* Fedora: https://src.fedoraproject.org/rpms/grass
* Ubuntu: https://trac.osgeo.org/grass/wiki/DebianUbuntuPackaging

===== Alpine Linux =====

<source lang="bash">
# install compiler tools and libraries
apk add build-base bzip2-dev cairo-dev fftw-dev freetype-dev g++ gcc gdal-dev geos-dev git \
gnutls-dev libc6-compat libjpeg-turbo-dev libpng-dev make openjpeg-dev openblas-dev \
postgresql-dev proj-dev python3-dev py3-numpy-dev sqlite-dev tar tiff-dev unzip vim \
wget zip zstd-dev

# install needed tools and libraries when using GRASS
apk add attr bash bison bzip2 cairo curl fftw flex freetype gdal gdal-tools gettext geos gnutls \
jsoncpp libbz2 libexecinfo libjpeg-turbo libpng libunwind musl musl-utils ncurses openjpeg \
openblas py3-numpy py3-pillow py3-six postgresql proj-datumgrid proj-util sqlite sqlite-libs \
subversion tiff zstd zstd-libs

# get source code
cd ~
wget -c https://grass.osgeo.org/grass88/source/snapshot/grass-8.4.git_src_snapshot_latest.tar.gz

# unpack
tar xvfz grass-8.4.git_src_snapshot_latest.tar.gz
rm -f grass-8.4.git_src_snapshot_latest.tar.gz

# change into source code (update path name as needed)
cd grass-8.4.git_src_snapshot_2021_05_01/

# minimal configuration
./configure \
--with-cxx \
--with-gdal=/usr/bin/gdal-config \
--with-proj --with-proj-share=/usr/share/proj \
--with-geos \
--with-sqlite \
--without-nls \
--without-wxwidgets \
--without-fftw \
--without-cairo \
--without-freetype \
--without-opengl \
--without-odbc

# compilation
nice make -j2
</source>

===== Archlinux =====
You can install GRASS for Archlinux distribution based like Archlinux, Manjaro, EndeavourOS ...

* <big>'''Easiest method : use a prebuilt package using arch4edu repository'''</big>
''"Arch4edu is a community repository for Arch Linux and Arch Linux ARM that strives to provide the latest versions of most software used by college students."''

1. Add Arch4edu repository. Follow instructions from official documentation:

https://github.com/arch4edu/arch4edu/wiki/Add-arch4edu-to-your-Archlinux

2. Refresh packages list with

pacman -Syyu

3. Install GRASS package

pacman -S grass

* <big>'''Advanced method : use AUR (Arch User Repository) package'''</big>
Up-to-date links to Archlinux GRASS PKGBUILDs are on Arch User Repository.
PKGBUILD downloads and builds automatically sources from https://grass.osgeo.org/download/software/linux/.

You can use an AUR helper like ''pamac'', ''yay'', among others ... More info through this link https://wiki.archlinux.org/title/AUR_helpers

Exemple with ''yay'':
yay -S grass

* <big>'''Expert method : compile from source code'''</big>
If you want to compile it yourself, you could follow steps below :

''(As an alternative it is recommended to download PKGBUILD from AUR and then customize to your needs)''

Install dependencies :
pacman -S bzip2 cairo fftw fontconfig freetype2 gcc-libs gdal geos glibc glu libpng libtiff libx11 libgl netcdf pdal proj python-gdal python-numpy python-pillow python-wxpython readline zlib zstd

Download and extract sources : https://grass.osgeo.org/download/software/sources/

We can now start building GRASS

export PATH=~/usr/bin:$PATH && \
./configure \
--with-freetype-includes=/usr/include/freetype2 \
--with-wxwidgets \
--with-readline \
--with-pthread \
--with-netcdf \
--with-nls \
--with-geos \
--with-postgres \
--with-pdal=/usr/include/pdal \
--with-bzlib \
--with-zstd

Now let's compile and install it

make
make install

It's done, you can enjoy GRASS in Arch, just type "grass" in the terminal to launch it or look for grass in your menu.

===== Generic procedure for Debian-based distributions (Ubuntu, ...) =====

WORK IN PROGRESS

1. Install official GRASS package

sudo apt install grass grass-dev

2. Enable source code download

# do backup first
sudo cp /etc/apt/sources.list /etc/apt/sources.list.orig
sudo sed -i '/^#\sdeb-src /s/^# *//' /etc/apt/sources.list

3. Install GRASS dependencies

sudo apt build-dep grass

4. Download GRASS source code

git clone https://github.com/osgeo/grass

5. Compile GRASS from source code

cd grass

Configure:

grass --config build | sh

Optionally install missing dependencies (can happen when official GRASS package is not compatible with GRASS main), eg.

sudo apt install libzstd-dev

Compile:

make -j2

6. Run locally or install

./bin.x86_64-pc-linux-gnu/grass --version

or

sudo make install
grass --version

===== Debian =====

* Official [https://wiki.debian.org/DebianGis DebianGIS] packaging control files, available on git server:
https://salsa.debian.org/debian-gis-team/grass

====== GRASS 8 on Debian 11 (bullseye) ======

Install needed packages for GRASS 8.4:
apt-get update && \
apt-get install bison debhelper-compat dh-python doxygen fakeroot flex graphviz \
libblas-dev libbz2-dev libcairo2-dev libfftw3-dev libfreetype6-dev \
libgdal-dev libgeos-dev libgl1-mesa-dev libglu1-mesa-dev libjpeg-dev liblapack-dev libmotif-dev \
default-libmysqlclient-dev libncurses5-dev libnetcdf-dev libpng-dev libpq-dev \
libproj-dev libreadline-dev libsqlite3-dev libtiff-dev libxmu-dev libzstd-dev \
netcdf-bin pkg-config proj-bin python3 python3-dev python3-numpy python3-pil python3-ply \
python3-six python3-wxgtk4.0 wget unixodbc-dev zlib1g-dev

Download and unpack GRASS 8.4 source code (or fetch from GitHub: https://github.com/OSGeo/grass):

wget https://grass.osgeo.org/grass84/source/grass-8.4-latest.tar.gz
tar xvfz grass-8.4-latest.tar.gz
cd grass-8.4.*

Configuration:

CFLAGS="-Wall -Werror-implicit-function-declaration -fno-common -Wextra -Wunused" \
CXXFLAGS="-Wall" \
./configure \
--prefix=/usr/local \
--with-gdal --with-proj --with-proj-share=/usr/share \
--with-glw --with-nls --with-readline \
--with-cxx --enable-largefile \
--with-freetype --with-freetype-includes=/usr/include/freetype2 \
--with-sqlite --with-cairo --with-python=/usr/bin/python-config \
--with-wxwidgets --with-geos \
--with-netcdf=/usr/bin/nc-config --with-odbc=yes \
--with-openmp=yes --with-pthread=no

Compile:

make -j2

Install:

make install

Run:

grass --version

===== Ubuntu =====

There is a dedicated page on how to [[Compile_and_Install_Ubuntu | Compile the GRASS source code & install it in Ubuntu]].

===== Linux Mint =====

The [[Compile_and_Install_Ubuntu | detailed compilation guide for Ubuntu]] may just work. However, here is a short guide for Mint:

<source lang="bash">
# Linux Mint 21+

# be sure to have an updated system
sudo apt-get update && sudo apt-get upgrade -y

# installation of required libraries and compile tools
# recommended to give Python3 precedence over Python2 (which is end-of-life since 2024)
sudo update-alternatives --install /usr/bin/python python /usr/bin/python3 1

# install compiler tools and further dependencies (tested with Linux Mint 21)
# this is a single command, please copy-paste it entirely into the terminal:
sudo apt-get install \
build-essential \
flex make bison gcc libgcc1 g++ cmake ccache \
libproj-dev proj-data proj-bin \
libgeos-dev \
libgdal-dev python3-gdal gdal-bin \
libfftw3-dev libfftw3-single3 libfftw3-double3 \
python3 python3-dev python3-pip \
python3-opengl \
python3-dateutil libgsl-dev python3-numpy \
zlib1g-dev gettext \
libbz2-dev libzstd-dev libfreetype6-dev \
libtiff5-dev libpnglite-dev libcairo2 libcairo2-dev \
sqlite3 libsqlite3-dev libpq-dev \
libboost-thread-dev libboost-program-options-dev \
git \
checkinstall \
libglu1-mesa-dev libxmu-dev \
ghostscript wget -y
</source>

'''GUI''' - update wxpython:

<source lang="bash">
# Linux Mint 21 only
sudo apt-get install wx3.0-headers libwxgtk3.0-gtk3-dev libwxbase3.0-dev libwxgtk3.0-gtk3-dev
pip3 install --user --upgrade typing-extensions
pip3 install -U -f https://extras.wxpython.org/wxPython4/extras/linux/gtk3/ubuntu-22.04 wxPython
</source>

or

<source lang="bash">
# Linux Mint 22+
sudo apt-get install wx3.2-headers libwxgtk3.2-dev libwxbase3.2-1 libgtk-3-dev python3-wxgtk4.0 \
pip3 install -U -f https://extras.wxpython.org/wxPython4/extras/linux/gtk3/ubuntu-24.04 wxPython
</source>

Next steps:
* create a subdirectory in your HOME tree for storing the GRASS source code (and later compilation)
* get source code, one of the two options:
** a) download [https://grass.osgeo.org/grass-stable/source/snapshot/ GRASS source code weekly snapshot] (e.g. take the "8.x.git snapshot"), or
*** unpack source code
** b) current source code from GitHub:
*** <code>git clone https://github.com/OSGeo/grass.git</code>
* change into the source code directory

<source lang="bash">
# in the source code directory, "configure" the source code to prepare for compilation:
./configure \
--with-cxx \
--with-proj-share=/usr/share/proj \
--with-gdal=/usr/bin/gdal-config \
--with-geos \
--with-sqlite \
--with-nls \
--with-zstd \
--with-cairo --with-cairo-ldflags=-lfontconfig \
--with-freetype=yes --with-freetype-includes="/usr/include/freetype2/" \
--with-fftw \
--with-opengl-libs=/usr/include/GL \
--without-postgres \
--without-pdal \
--without-netcdf \
--without-mysql \
--without-odbc \
--without-openmp

# compile GRASS
make -j2

# install compiled GRASS on system
sudo make install

# use GRASS! Start on command line
grass
</source>

===== Enterprise Linux =====

Enterprise Linux (EL) and derivatives (that is, Red Hat Enterprise Linux, CentOS and Scientific Linux) is a popular and robust platform for servers and computing-heavy workstations, and is therefore a good fit for GIS specific requirements.

See: https://wiki.osgeo.org/wiki/Enterprise_Linux_GIS

===== Scientific Linux =====

See Centos

===== CentOS =====

You first need to add the EPEL repository for PROJ and GDAL, see [https://fedoraproject.org/wiki/EPEL/FAQ#How_can_I_install_the_packages_from_the_EPEL_software_repository.3F here]

Preparation '''Centos 8''':
dnf install epel-release

dnf install flex bison make zlib-devel gcc-c++ gettext \
fftw-devel libtiff-devel sqlite-devel \
proj proj-devel proj-datumgrid libxml2 \
geos geos-devel git \
netcdf netcdf-devel atlas-devel \
blas-devel lapack-devel libpq-devel \
python3-devel python3-numpy \
python3-dateutil python3-imaging python3-matplotlib \
gdal gdal-libs gdal-python-tools python3-gdal gdal-devel \
wxGTK3-devel mesa-libGL-devel mesa-libGLU-devel \
libXmu-devel libX11-devel

'''GRASS 8 compilation and installation'''

[https://grass.osgeo.org/grass84/source/snapshot/ Download source code] (e.g., --> "Download latest 8.4 code)" and configure GRASS 8 (suggestion: save this as script):

./configure \
--with-cxx \
--with-proj --with-proj-share=/usr/share/proj \
--with-gdal=/usr/bin/gdal-config \
--with-sqlite \
--with-python \
--with-cairo --with-cairo-ldflags=-lfontconfig \
--with-freetype --with-freetype-includes=/usr/include/freetype2 \
--with-wxwidgets=/usr/bin/wx-config \
--with-openmp \
--with-blas --with-blas-includes=/usr/include/atlas-x86_64-base/ \
--with-lapack --with-lapack-includes=/usr/include/atlas-x86_64-base/ \
--with-fftw \
--with-geos \
--with-netcdf \
--without-ffmpeg \
--without-mysql \
--without-postgres \
--without-odbc \
--without-fftw

Compile:
make
or on a multicore system (number depends of available cores):
make -j4

For a system wide installation, run as root user:
make install
OR simply run it directly from the source code directory (substitute ARCH with i686 or x86_64):

bin.$ARCH/grass -gui

In this case, for convenience, add it to the search path:
mkdir $HOME/bin
cd $HOME/bin
# example:
ln -s $HOME/software/grass84_release/bin.x86_64-pc-linux-gnu/grass .

Now use it subsequently with
grass -gui

'''Installation grass on a HPC system with '''Centos 7''' and no root privileges:'''

This assumes that python3, fftw, proj, gdal and geos are available on the HPC system, either as modules or as installed software.

Download and prepare some dependencies (freetypes and zstd)
mkdir -p $HOME/grass/freetypes
cd $HOME/grass/freetypes
wget path/to/freetype-2.9.1.tar.gz
tar -xf freetype-2.9.1.tar.gz

mkdir $HOME/grass/zstd
cd mkdir $HOME/grass/zstd
wget path/to/v1.4.4/zstd-1.4.4.tar.gz
tar -xf zstd-1.4.4.tar.gz
make install PREFIX=./

Add the ZSTD path to your LD_LIBRARY_PATH

tee -a $HOME/.bashrc > /dev/null << EOT
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$HOME/grass/zstd/zstd-1.4.4/lib
EOT

The configure command could look like this
./configure \
-prefix=$HOME/grass \
--enable-64bit --with-fftw-includes=/path/to/fftw/include/ \
--with-fftw-libs=/path/to/fftw/lib/ \
--with-freetype-includes=$HOME/grass/freetypes/freetype-2.9.1/include/ \
--with-netcdf --with-geos --with-blas --with-lapack --with-postgres \
--with-zstd-includes=$HOME/grass/zstd/zstd-1.4.4/lib/ \
--with-zstd-libs=$HOME/grass/zstd/zstd-1.4.4/lib/ \
--with-gdal=/path/to/gdal-config # This could be the path to a gdal version compiled from source

Finally as usual:
make; make install

grass

===== Gentoo =====

./configure \
--with-freetype=yes --with-freetype-includes="/usr/include/freetype2/"

See also https://packages.gentoo.org/package/sci-geosciences/grass

===== Funtoo =====

{{MovedToTrac|FuntooLinux}}

===== Fedora =====

====== GRASS 8 on Fedora ======

'''Preparation''' for the compilation of GRASS 8+ source code (F36+):

dnf install gcc gcc-c++ bison flex ncurses-devel gettext proj-devel \
gdal gdal-devel sqlite-devel xml2 mesa-libGL-devel cairo-devel \
fftw-devel mesa-libGLU-devel libXmu-devel libX11-devel geos geos-devel \
libtiff-devel python3-devel numpy wxGTK-devel gawk git \
python3-dateutil python3-imaging python3-matplotlib-wx doxygen python3-sphinx \
libzstd-devel libzstd python3-six python3-numpy python3-wxpython4 \
proj-data PDAL-devel PDAL-libs

# optionally also: netcdf-devel postgresql-devel
# atlas-devel lapack-devel lapack-devel
# laszip laszip-devel
# proj-data-at proj-data-au proj-data-be ...

''Note 1: the optional ffmpeg-devel comes from the rpmfusion-free repository ([https://rpmfusion.org/Configuration/ configuration]).''

'''Download''' and unpack the source code:
* GRASS 8: [https://grass.osgeo.org/grass84/source/snapshot/ weekly snapshot] - [https://github.com/OSGeo/grass/releases GitHub repository]

'''Configure''': This is an example how to configure the source code on a Fedora system:

./configure \
--with-cxx \
--with-gdal=/usr/bin/gdal-config \
--with-proj --with-proj-share=/usr/share/proj \
--with-geos \
--with-pdal \
--with-sqlite \
--with-nls \
--with-wxwidgets=/usr/bin/wx-config \
--with-fftw \
--with-cairo --with-cairo-ldflags=-lfontconfig \
--with-freetype --with-freetype-includes=/usr/include/freetype2 \
--enable-largefile \
--without-odbc

''Extra 1:'' If you also want '''FFMPEG support''' - it requires 'dnf install fftw-devel' from the rpmfusion-free repository. Then add to the configuration lines above:

--with-ffmpeg --with-ffmpeg-includes="/usr/include/ffmpeg /usr/include/ffmpeg/libav* /usr/include/ffmpeg/libpostproc /usr/include/ffmpeg/libswscale" \

''Extra 2:'' For '''LAPACK/BLAS support''' (addons i.spec.unmix, v.kriging etc), install "dnf install lapack lapack-devel blas blas-devel atlas atlas-devel". Then add to the configuration lines above:
--with-blas --with-blas-includes=/usr/include/atlas-x86_64-base/ \
--with-lapack --with-lapack-includes=/usr/include/atlas-x86_64-base/ \

''Extra 3:'' For '''ZSTD support''' (Zstandard compression algorithm), first install "dnf install libzstd libzstd-devel zstd". After installing the zstd related packages, add to the configuration lines above:
--with-zstd \

Finally '''compile''' the configured source code:
make
or on multicore (number depends of available cores):
make -j4
and
make install # requires root permissions unless you become owner of /usr/local/

Then use GRASS 8 and enjoy!

grass --version

===== openSUSE =====

To build GRASS on openSUSE:

''Application:Geo'' repo to be added (see [https://software.opensuse.org//download.html?project=Application%3AGeo&package=gdal Install package Application:Geo]

<source lang="bash">
# example for Leap 42 version:
sudo zypper addrepo https://download.opensuse.org/repositories/Application:Geo/openSUSE_Leap_42.3/Application:Geo.repo
sudo zypper refresh
</source>

RPM packages to be installed:
<source lang="bash">
sudo zypper install bison flex freetype2-devel fftw3-devel gcc-c++ \
libgdal-devel libgeos-devel libjpeg-devel libpng-devel libtiff-devel \
man proj libproj-devel readline-devel netcdf-devel ncurses-devel \
mysql-devel postgresql-devel sqlite-devel unixODBC-devel \
tcl-devel tk-devel xorg-x11-Mesa-devel libXmu-devel \
python-numpy python-dateutil python-devel python-opengl \
python-wxWidgets python-xml python-dateutil wxWidgets-devel \
zlib-devel doxygen python-sphinx
</source>

Source code configuration:
<source lang="bash">
./configure \
--enable-largefile \
--with-proj-share=/usr/share/proj \
--with-cxx \
--with-lapack=yes \
--with-motif \
--with-gdal=/usr/bin/gdal-config \
--with-postgres --with-postgres-includes=/usr/include/pgsql \
--with-mysql --with-mysql-includes=/usr/include/mysql \
--with-fftw \
--with-readline \
--with-netcdf \
--with-geos \
--with-nls \
--with-sqlite \
--with-freetype \
--with-freetype-includes=/usr/include/freetype2 \
--with-wxwidgets \
--with-odbc \
--with-python
</source>

Then compile with "make [-j2]".

===== RPM SPEC files =====
* [https://build.opensuse.org/package/show?package=grass&project=Application%3AGeo OpenSuSe]
* [https://pkgs.fedoraproject.org/cgit/rpms/grass.git/tree/grass.spec Fedora]
* ...

==== macOS ====

Compiling GRASS for macOS is not fundamentally different from for other *nix systems. It is on the contrary quite similar, but what differ is the lack of a default package management system for software GRASS depends on. This leaves the mac user to either: (1) compile the dependencies one-by-one; (2) compiling with one of the third-party package management systems avaliable; or (4) a combination thereof.

If you are interested in installing a precompiled version, please check out the [https://grass.osgeo.org/download/software/mac-osx/ official download site].

To date, maybe the easiest way to compile for Mac is by using [https://github.com/nilason/grass-conda GRASS app build script] which is based on the instructions below for building using Anaconda. It will install dependencies, package and install an app bundle with just a command in Terminal.

===== Compilation and installation =====

For more up-to-date instructions please read:

* [https://github.com/nilason/grass-conda Compiling on macOS using Conda] (Intel / Apple silicon based machine M1)
* [[Compiling on macOS using Anaconda]]
* [[Compiling on macOS using Homebrew]]
* [[Compiling on macOS using MacPorts]]

===== Legacy instructions =====

The following compilation and installation instructions are rather outdated as a whole. They do, however, contain parts and snippets that still may be very instructive and useful.

* [[Compiling on MacOSX]]
* [[Compiling on MacOSX using Fink]]
* [https://web.archive.org/web/20180718005252/https://www.kyngchaos.com/software/frameworks#build_scripts build scripts for dependencies]

Troubleshooting:
* solving errors at starting GRASS: [[MacOSX GRASS errors]]

==== FreeBSD / NetBSD ====

The recommended compiler tools are GCC, GNU make, GNU coreutils (for install), and flex. All are available through the respective package managing tools (pkg_add for FreeBSD and pkgin install for NetBSD) and for recent *BSD versions most likely installed by default.

GRASS 8 should compile on FreeBSD and NetBSD.

It is highly recommended to install GDAL/OGR and PROJ first. These libraries and tools are available as [https://www.freebsd.org/ports/ ports for FreeBSD] and [https://www.pkgsrc.org/ packages for NetBSD].

Optional functionality is listed with ''./configure --help'', and related libraries and tools might need to be installed first.

You then may need to edit include/Make/Platform.make and set
ICONVLIB = -liconv

==== AIX ====

A recent [ftp://ftp.gnu.org/gnu/make/ GNU make] (>= 3.81) and GNU coreutils are required. These are available with the [https://www-03.ibm.com/systems/power/software/aix/linux/toolbox/download.html IBM AIX toolbox] or through third-party AIX software repositories, e.g. [https://www.bullfreeware.com/ bullfreeware] and [https://www.perzl.org/aix/ perzl.org]. Note that 'make' does not work, only 'gmake' works.

General instructions to compile on AIX are e.g. [https://www.perzl.org/aix/index.php?n=Main.Instructions here]

On AIX, compilation results by default in 32 bit applications and static libraries. The [https://developer.ibm.com/components/aix/ IBM documentation] explains how to build 64 bit applications and shared libraries with GCC.

'''GRASS 8: Using the IBM xlc compiler:'''

Get and install (in this order):
* [ftp://ftp.gnu.org/gnu/tar/ GNU tar]
* [ftp://ftp.gnu.org/gnu/make/ GNU make] (>= 3.81)
* [https://www.sqlite.org SQLite]
* [https://trac.osgeo.org/proj/ PROJ.4] (for ./configure parameters, see [[Talk:Compile and Install|here]])
* [https://www.gdal.org GDAL] (for ./configure parameters, see [[Talk:Compile and Install|here]])
* [https://grass.osgeo.org/grass84/source/snapshot/ GRASS 8]

The environment variables and configure command that worked:
<pre>
## AIX 5.x

export LIBPATH=/opt/freeware/lib64:/opt/freeware/lib
# make 'ar' happy
export OBJECT_MODE=64

PREFIX=$HOME/private/bin
./configure \
--prefix=$PREFIX \
--disable-shared \
--with-cxx \
--with-proj-includes=$PREFIX/include/ \
--with-proj-libs=$PREFIX/lib/ \
--with-proj-share=$PREFIX/share/proj/ \
--with-sqlite \
--with-sqlite-includes=$PREFIX/include/ \
--with-sqlite-libs=$PREFIX/lib/ \
--with-tiff=no \
--with-png=no \
--with-fftw=no \
--with-cairo=no \
--with-freetype=no
</pre>

'''GRASS 8: Using the GNU gcc compiler:'''

Get and install (in this order):
* if needed, [ftp://ftp.gnu.org/gnu/tar/ GNU tar]
* if needed (the name is often 'gmake' and not 'make') [ftp://ftp.gnu.org/gnu/make/ GNU make] (>= 3.81)
* [https://www.sqlite.org SQLite]
* [https://trac.osgeo.org/proj/ PROJ.4] (for ./configure parameters, see [[Talk:Compile and Install|here]])
* [https://www.gdal.org GDAL] (for ./configure parameters, see [[Talk:Compile and Install|here]])
* [https://grass.osgeo.org/grass84/source/snapshot/ GRASS 8]

The environment variables and configure command that worked for AIX 7.x:
<pre>
## AIX 7.x
export CC="gcc"
export CXX="g++"
PREFIX=$HOME/bin

LDFLAGS="-Wl,-bsvr4,-R,/opt/freeware/lib -L/opt/freeware/lib" CPPFLAGS="-I/opt/freeware/include" ./configure \
--prefix=$PREFIX \
--enable-shared \
--with-includes=/opt/freeware/include --with-libs=/opt/freeware/lib \
--with-cxx \
--with-proj-includes=$PREFIX/include/ \
--with-proj-libs=$PREFIX/lib/ \
--with-proj-share=$PREFIX/share/proj/ \
--with-gdal=$PREFIX/bin/gdal-config \
--with-sqlite \
--with-sqlite-libs=$PREFIX/lib --with-sqlite-includes=$PREFIX/include \
--with-png=no \
--with-tiff=no \
--with-fftw=no \
--with-cairo=no \
--with-opengl=no \
--with-freetype=no
</pre>

==== MS-Windows ====

See also [[WinGRASS Current Status]] for latest updates.

===== MS-Windows/native =====

GRASS on Windows using a standalone installer. It is still MinGW based (we are going to move this to CMake in 2024+).

Instructions to compile from source code:
* [https://trac.osgeo.org/grass/wiki/CompileOnWindows GRASS Windows Native Binary Building Guide]

===== MS-Windows/OSGeo4W =====

OSGeo4W is an installer for a broad set of open source geospatial software packages including GRASS as well as many other packages (QGIS, GDAL/OGR, and more).

* See [https://trac.osgeo.org/osgeo4w/ OSGeo4W]

===== MS-Windows/Cygwin =====

* See the [[Cygwin]] wiki pages

=== Common problems and solutions ===

During compilation, error can occur if certain packages are not installed. Here a list of problems with solution:

* error: X11/Xlib.h: No such file or directory
** this suggests that you don't have the X headers installed
** Solution: Install the libx11-dev package

* error: g.list: error while loading shared libraries: libgdal1.6.0.so.1: cannot open shared object file: No such file or directory
** this error appears in the shell right after the user clicks GUI's "Start GRASS" button. The GUI shows an error about geographic extent and gets closed afterwards.
** It happens when you launch bin.i686 executable on 64bit system. Be careful and choose the right architecture.

* error: lib/python/ctypes
** This error appears during the compilation: <code>free(): invalid pointer Aborted (core dumped)</code>
** It happens when you have multiple <code>libproj</code> versions on your system (check it with command <code>ldd PATH_TO_GRASS_INSTALL/lib/libgrass_gproj.so | grep proj</code> - when this is not your problem, you should obtain exactly one result)
** Solution: Try to reinstall <code>libproj-dev</code> and <code>proj-data</code>

=== Static compilation ===

In order to get static rather than dynamically linked binaries, configure like this:

./configure --disable-shared --enable-static

This will however break the wxGUI and GRASS 8 completely because "ctypes" wants to link against shared libs, or there is something in the static libs that "ctypes" does not like.

=== Optimization ===

GCC and other compilers support [https://gcc.gnu.org/onlinedocs/gcc-4.3.3/gcc/Optimize-Options.html#Optimize-Options optimization]

If you would like to set compiler optimisations, for a possibly faster binary, type (don't enter a ";" anywhere):

CFLAGS=-O ./configure
or,
setenv CFLAGS -O
./configure

whichever works on your shell. Use -O2 instead of -O if your compiler supports this (note: O is the letter, not zero). Using the "gcc" compiler, you can also specify processor specific flags (examples, please suggest better settings to us):

CFLAGS="-mcpu=athlon -O2" # AMD Athlon processor with code optimisations
CFLAGS="-march=amdfam10" # AMD Phenom II X4 64bit processor with gcc >=4.3
CFLAGS="-mcpu=pentium" # Intel Pentium processor
CFLAGS="-mcpu=pentium4" # Intel Pentium4 processor
CFLAGS="-O2 -msse -msse2 -mfpmath=sse -minline-all-stringops" # Intel XEON 64bit processor
CFLAGS="-mtune=nocona -m64 -minline-all-stringops" # Intel Pentium 64bit processor

To find out optional CFLAGS for your platform, enter:
gcc -dumpspecs

See also: https://gcc.gnu.org/

A real fast GRASS version (and small binaries) will be created with LDFLAGS set to "stripping" (but this disables debugging):

CFLAGS="-O2 -mcpu=<cpu_see_above> -Wall" LDFLAGS="-s" ./configure

=== Configure options and their meanings ===

For configure there are many options and some GRASS modules are built only if some options are set. Here are listed common configuration options with short explanation.

* --prefix=/path - Sets path where GRASS will be installed. GRASS will reside in /path/grass-version.
* --enable-largefile - Enables large (>2Gb on 32bit systems) support. For current large file support status look at [[Large File Support]] page.
* --with-cxx - Enables compilation of C++ code. Required for r.terraflow module.
* --with-readline - Enables readline support. If readline is enabled, you can use its history/editing facilities when entering r.mapcalc expressions on stdin.
* --with-glw - Enables GLw support. The GLw library provides OpenGL "canvas" widgets for Athena and Motif.

That switch is unnecessary for normal compilation. It's only
required for r3.showdspf, which isn't normally built; if you
want it, you have build it manually
(e.g. "make -C raster3d/r3.showdspf").
As similar functionality is now provided by NVIZ, r3.showdspf
is deprecated.
r3.showdspf uses the Motif widget (so you also need a
Motif library, e.g. Lesstif or OpenMotif).
[https://grass.itc.it/pipermail/grassuser/2006-December/037475.html Glynn Clements at GRASS-user mailing list]

=== Parallelized compilation on multi-core CPUs ===

You can dramatically accelerate the compilation of the GRASS code with the -j flag of "make" if you have a multi-core CPU system. This determines the maximum number of jobs to have running at once, so cores don't have to sit idle waiting for jobs on other cores to complete. A good rule of thumb for this value is <tt>number_of_cores * 1.5</tt>, but note that setting any higher than the actual number of cores will only affect the timing slightly. For example, on a dual-core processor:
make -j 4



== GRASS-GDAL plugin ==

* see [[Compile and install GRASS and QGIS with GDAL/OGR Plugin]]

== Addons ==

Please note that the installation of [https://grass.osgeo.org/grass-stable/manuals/addons/ GRASS addons] can be easily done with the {{cmd|g.extension}} manager. The compile instructions below are aiming at own development.

=== Compiled modules ===

This is the general way which works for C modules as well as scripts (Python or Shell/Bash modules) which has HTML documentation.

'''Requirements:'''

Either:
* a binary GRASS package, or
* source code which has been prepared with:
./configure [opionally flags]
make libs

Each of the [[GRASS_AddOns|addon]] modules should come with a Makefile. To compile it, just run:
make MODULE_TOPDIR=/path/to/grass84/

Note that the <tt>/path/to/grass84</tt> has to be absolute, not relative.

If using Bash it may be useful to set that up as an alias:
alias gmake64='make MODULE_TOPDIR=/path/to/grass84/'

Installation (perhaps requires "sudo"):
make MODULE_TOPDIR=/path/to/grass84/ install

Note: Compiled addons may require a re-compilation if you changed/updated your GRASS standard binaries.

==== If binary comes with a -dev package ====

''(work in progress, this text states how it eventually will be :)''
Nowadays one does not need to the source code, nor compiling GRASS by oneself to be able to add add-ons. On Debian, you can just install the grass-dev package and then run:
make MODULE_TOPDIR=/usr/lib/grass84/ INST_DIR=/usr/lib/grass84/

The grass-dev package essentially provides GRASS's <tt>include</tt> header files and Make configuration files.

=== Scripts ===

If the addon module is a script, it is sufficient to copy it into the (GRASS binaries) path somewhere. Alternatively, install addons into a separate GRASS addons binaries/scripts directory which is easier to maintain. It avoids getting clobbered every time you reinstall GRASS. To use these separately stored scripts, set and export the GRASS_ADDON_PATH environment variable before starting GRASS and it will automatically be added to the module search path (see the {{cmd|variables}} help page). To simplify this, do for example:

# add in $HOME/.bashrc:
GRASS_ADDON_PATH=/usr/local/grass/addons/
export GRASS_ADDON_PATH

Make sure that the script is executable, then just call it in GRASS typing the filename. Python scripts need to be called writing the extension as well, like:

GRASS (nc_spm):~ > v.krige.py

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

Compile and Install

2026-03-27T16:27:31Z

Neteler: Linux Mint 22: fix wxpython version, subversion -> git

'''Disclaimer''': This page explains how to turn the GRASS source code into an installable binary package ("compilation") for different operating systems. If you just want to get ready-to-use binaries, go [https://grass.osgeo.org/download/ here], otherwise read on...

== How to do compilation and installation of GRASS? ==

Here we explain the procedure to compile GRASS from GitHub, but it also applies to official GRASS 8 releases.

''For installation of precompiled binary packages, see the main [[Installation Guide]].''

For detailed information on compilation, please see the [https://github.com/OSGeo/grass/blob/main/INSTALL.md INSTALL] file in the source code.

=== Prerequisites ===

==== Extra libraries ====
GRASS needs at least two extra libraries: PROJ and GDAL/OGR. It is recommended to download them as ready-to-use packages for your software platform (Linux distribution, Windows, Mac...).

Other libraries needed to run GRASS are listed on the [https://github.com/OSGeo/grass/blob/main/REQUIREMENTS.md requirements page].

To compile, you will also need the respective "-devel" packages; see below for details.

==== Download GRASS source code ====

First, [https://grass.osgeo.org/download/ download the GRASS source code].

=== Generic Compilation and installation procedure ===

* It is wise that compilation processes are carried out as a normal user: If you want to get the source code in a place where you do not have write permissions (e.g. in /usr/local/src/) just follow this:
cd /usr/local/src/
su -c 'mkdir grass8'
su -c 'chown yourlogin:yourgroup grass8'

Otherwise if you have permissions just continue as a normal user:
mkdir $HOME/src
cd $HOME/src/
git clone https://github.com/OSGeo/grass.git grass_main

* run configure with parameters to adapt the compile process to your own system. To see what options can be passed to it, run:
./configure --help | less


It may (!) look like this:

./configure \
--with-cxx \
--with-sqlite \
--with-python \
--with-geos \
--with-gdal=/usr/bin/gdal-config \
--with-cairo --with-cairo-ldflags=-lfontconfig \
--with-freetype \
--with-freetype-includes=/usr/include/freetype2 \
--with-proj --with-proj-share=/usr/share/proj

You may have to explicitly state the path for certain packages (i.e., gdal). The Unix 'locate' command will come in handy for finding the path of the package you need (you may have to run locate as root ex: sudo locate gdal-config).

Please note that the paths mentioned may widely vary due to the distribution used.
See [[Compile_and_Install#Platform_Specific_Notes|Platform Specific Notes]] below.

Depending on your needs it may be a good idea to include debugging hooks.
: See [[GRASS_Debugging#Compile_Time_Setup]].
CFLAGS="-ggdb -Wall -Werror-implicit-function-declaration" ./configure ...

At the end of configuration process you should get report not much different from this:

GRASS is now configured for: x86_64-pc-linux-gnu

Source directory: /home/user/software/grass_main
Build directory: /home/user/software/grass_main
Installation directory: ${prefix}/grass84
Startup script in directory:${exec_prefix}/bin
C compiler: gcc -O2 -march=native -std=gnu99 -fexceptions -fstack-protector -m64 -fdiagnostics-color
C++ compiler: c++ -g -Wall
Building shared libraries: yes
OpenGL platform: X11

MacOSX application: no
MacOSX architectures:
MacOSX SDK:

BLAS support: yes
BZIP2 support: no
C++ support: yes
Cairo support: yes
DWG support: no
FFTW support: yes
FreeType support: yes
GDAL support: yes
GEOS support: yes
[...]

* Let's compile it (takes a little while...)!
make -j2
* At the end, you should get report not much different from this:
----------------------------------------------------------------------
Following modules are missing the 'description.html' file in src code:
----------------------------------------------------------------------
GRASS compilation log
-------------------------
Started compilation: Mon 19 Aug 2024 10:47:57 PM CEST
--
Errors in:
No errors detected.
--
Finished compilation: Mon 19 Aug 2024 10:55:12 PM CEST
(In case of errors please change into the directory with error and run 'make')

* If there is any error, change directory to directory with error and run "make" again. Report occurring bug to GRASS mailing list
* Once the installation process is finished, you're ready to install GRASS system wide.
su -c 'make install'
* enjoy GRASS:
grass

=== What else? ===

If you want to use [https://www.qgis.org QGIS], then also compile the GRASS-GDAL/OGR plugin. This is also useful to access your GRASS-data
from other application using GDAL/OGR like [[R_statistics/ R]].
* [[Compile and install GRASS and QGIS with GDAL/OGR Plugin]] (enables QGIS to read GRASS data directly)

=== Compile and install GDAL-GRASS plugin ===

* See [[Compile and install GDAL-GRASS plugin]]

=== Platform Specific Notes ===

==== Linux ====

Linux comes in various flavours, i.e. distributions.

===== Distribution related packaging =====

Examples:

* Archlinux: https://aur.archlinux.org/packages/grass
* Centos: https://src.fedoraproject.org/rpms/grass
* Debian: https://trac.osgeo.org/grass/wiki/DebianUbuntuPackaging
* EPEL: https://src.fedoraproject.org/rpms/grass
* Fedora: https://src.fedoraproject.org/rpms/grass
* Ubuntu: https://trac.osgeo.org/grass/wiki/DebianUbuntuPackaging

===== Alpine Linux =====

<source lang="bash">
# install compiler tools and libraries
apk add build-base bzip2-dev cairo-dev fftw-dev freetype-dev g++ gcc gdal-dev geos-dev git \
gnutls-dev libc6-compat libjpeg-turbo-dev libpng-dev make openjpeg-dev openblas-dev \
postgresql-dev proj-dev python3-dev py3-numpy-dev sqlite-dev tar tiff-dev unzip vim \
wget zip zstd-dev

# install needed tools and libraries when using GRASS
apk add attr bash bison bzip2 cairo curl fftw flex freetype gdal gdal-tools gettext geos gnutls \
jsoncpp libbz2 libexecinfo libjpeg-turbo libpng libunwind musl musl-utils ncurses openjpeg \
openblas py3-numpy py3-pillow py3-six postgresql proj-datumgrid proj-util sqlite sqlite-libs \
subversion tiff zstd zstd-libs

# get source code
cd ~
wget -c https://grass.osgeo.org/grass88/source/snapshot/grass-8.4.git_src_snapshot_latest.tar.gz

# unpack
tar xvfz grass-8.4.git_src_snapshot_latest.tar.gz
rm -f grass-8.4.git_src_snapshot_latest.tar.gz

# change into source code (update path name as needed)
cd grass-8.4.git_src_snapshot_2021_05_01/

# minimal configuration
./configure \
--with-cxx \
--with-gdal=/usr/bin/gdal-config \
--with-proj --with-proj-share=/usr/share/proj \
--with-geos \
--with-sqlite \
--without-nls \
--without-wxwidgets \
--without-fftw \
--without-cairo \
--without-freetype \
--without-opengl \
--without-odbc

# compilation
nice make -j2
</source>

===== Archlinux =====
You can install GRASS for Archlinux distribution based like Archlinux, Manjaro, EndeavourOS ...

* <big>'''Easiest method : use a prebuilt package using arch4edu repository'''</big>
''"Arch4edu is a community repository for Arch Linux and Arch Linux ARM that strives to provide the latest versions of most software used by college students."''

1. Add Arch4edu repository. Follow instructions from official documentation:

https://github.com/arch4edu/arch4edu/wiki/Add-arch4edu-to-your-Archlinux

2. Refresh packages list with

pacman -Syyu

3. Install GRASS package

pacman -S grass

* <big>'''Advanced method : use AUR (Arch User Repository) package'''</big>
Up-to-date links to Archlinux GRASS PKGBUILDs are on Arch User Repository.
PKGBUILD downloads and builds automatically sources from https://grass.osgeo.org/download/software/linux/.

You can use an AUR helper like ''pamac'', ''yay'', among others ... More info through this link https://wiki.archlinux.org/title/AUR_helpers

Exemple with ''yay'':
yay -S grass

* <big>'''Expert method : compile from source code'''</big>
If you want to compile it yourself, you could follow steps below :

''(As an alternative it is recommended to download PKGBUILD from AUR and then customize to your needs)''

Install dependencies :
pacman -S bzip2 cairo fftw fontconfig freetype2 gcc-libs gdal geos glibc glu libpng libtiff libx11 libgl netcdf pdal proj python-gdal python-numpy python-pillow python-wxpython readline zlib zstd

Download and extract sources : https://grass.osgeo.org/download/software/sources/

We can now start building GRASS

export PATH=~/usr/bin:$PATH && \
./configure \
--with-freetype-includes=/usr/include/freetype2 \
--with-wxwidgets \
--with-readline \
--with-pthread \
--with-netcdf \
--with-nls \
--with-geos \
--with-postgres \
--with-pdal=/usr/include/pdal \
--with-bzlib \
--with-zstd

Now let's compile and install it

make
make install

It's done, you can enjoy GRASS in Arch, just type "grass" in the terminal to launch it or look for grass in your menu.

===== Generic procedure for Debian-based distributions (Ubuntu, ...) =====

WORK IN PROGRESS

1. Install official GRASS package

sudo apt install grass grass-dev

2. Enable source code download

# do backup first
sudo cp /etc/apt/sources.list /etc/apt/sources.list.orig
sudo sed -i '/^#\sdeb-src /s/^# *//' /etc/apt/sources.list

3. Install GRASS dependencies

sudo apt build-dep grass

4. Download GRASS source code

git clone https://github.com/osgeo/grass

5. Compile GRASS from source code

cd grass

Configure:

grass --config build | sh

Optionally install missing dependencies (can happen when official GRASS package is not compatible with GRASS main), eg.

sudo apt install libzstd-dev

Compile:

make -j2

6. Run locally or install

./bin.x86_64-pc-linux-gnu/grass --version

or

sudo make install
grass --version

===== Debian =====

* Official [https://wiki.debian.org/DebianGis DebianGIS] packaging control files, available on git server:
https://salsa.debian.org/debian-gis-team/grass

====== GRASS 8 on Debian 11 (bullseye) ======

Install needed packages for GRASS 8.4:
apt-get update && \
apt-get install bison debhelper-compat dh-python doxygen fakeroot flex graphviz \
libblas-dev libbz2-dev libcairo2-dev libfftw3-dev libfreetype6-dev \
libgdal-dev libgeos-dev libgl1-mesa-dev libglu1-mesa-dev libjpeg-dev liblapack-dev libmotif-dev \
default-libmysqlclient-dev libncurses5-dev libnetcdf-dev libpng-dev libpq-dev \
libproj-dev libreadline-dev libsqlite3-dev libtiff-dev libxmu-dev libzstd-dev \
netcdf-bin pkg-config proj-bin python3 python3-dev python3-numpy python3-pil python3-ply \
python3-six python3-wxgtk4.0 wget unixodbc-dev zlib1g-dev

Download and unpack GRASS 8.4 source code (or fetch from GitHub: https://github.com/OSGeo/grass):

wget https://grass.osgeo.org/grass84/source/grass-8.4-latest.tar.gz
tar xvfz grass-8.4-latest.tar.gz
cd grass-8.4.*

Configuration:

CFLAGS="-Wall -Werror-implicit-function-declaration -fno-common -Wextra -Wunused" \
CXXFLAGS="-Wall" \
./configure \
--prefix=/usr/local \
--with-gdal --with-proj --with-proj-share=/usr/share \
--with-glw --with-nls --with-readline \
--with-cxx --enable-largefile \
--with-freetype --with-freetype-includes=/usr/include/freetype2 \
--with-sqlite --with-cairo --with-python=/usr/bin/python-config \
--with-wxwidgets --with-geos \
--with-netcdf=/usr/bin/nc-config --with-odbc=yes \
--with-openmp=yes --with-pthread=no

Compile:

make -j2

Install:

make install

Run:

grass --version

===== Ubuntu =====

There is a dedicated page on how to [[Compile_and_Install_Ubuntu | Compile the GRASS source code & install it in Ubuntu]].

===== Linux Mint =====

The [[Compile_and_Install_Ubuntu | detailed compilation guide for Ubuntu]] may just work. However, here is a short guide for Mint:

<source lang="bash">
# Linux Mint 21+

# be sure to have an updated system
sudo apt-get update && sudo apt-get upgrade -y

# installation of required libraries and compile tools
# recommended to give Python3 precedence over Python2 (which is end-of-life since 2024)
sudo update-alternatives --install /usr/bin/python python /usr/bin/python3 1

# install compiler tools and further dependencies (tested with Linux Mint 21)
# this is a single command, please copy-paste it entirely into the terminal:
sudo apt-get install \
build-essential \
flex make bison gcc libgcc1 g++ cmake ccache \
libproj-dev proj-data proj-bin \
libgeos-dev \
libgdal-dev python3-gdal gdal-bin \
python3 python3-dev \
python3-opengl \
python3-dateutil libgsl-dev python3-numpy \
libfftw3-dev \
zlib1g-dev gettext \
libbz2-dev libzstd-dev libfreetype6-dev \
libtiff5-dev libpnglite-dev libcairo2 libcairo2-dev \
sqlite3 libsqlite3-dev libpq-dev \
libfftw3-3 libfftw3-dev \
libboost-thread-dev libboost-program-options-dev \
git \
checkinstall \
libglu1-mesa-dev libxmu-dev \
ghostscript wget -y
</source>

'''GUI''' - update wxpython:

<source lang="bash">
# Linux Mint 21 only
sudo apt-get install wx3.0-headers libwxgtk3.0-gtk3-dev libwxbase3.0-dev libwxgtk3.0-gtk3-dev
pip3 install --user --upgrade typing-extensions
pip3 install -U -f https://extras.wxpython.org/wxPython4/extras/linux/gtk3/ubuntu-22.04 wxPython
</source>

or

<source lang="bash">
# Linux Mint 22+
sudo apt-get install wx3.2-headers libwxgtk3.2-dev libwxbase3.2-1 libgtk-3-dev python3-wxgtk4.0 \
pip3 install -U -f https://extras.wxpython.org/wxPython4/extras/linux/gtk3/ubuntu-24.04 wxPython
</source>

Next steps:
* create a subdirectory in your HOME tree for storing the GRASS source code (and later compilation)
* get source code, one of the two options:
** a) download [https://grass.osgeo.org/grass-stable/source/snapshot/ GRASS source code weekly snapshot] (e.g. take the "8.x.git snapshot"), or
*** unpack source code
** b) current source code from GitHub:
*** <code>git clone https://github.com/OSGeo/grass.git</code>
* change into the source code directory

<source lang="bash">
# in the source code directory, "configure" the source code to prepare for compilation:
./configure \
--with-cxx \
--with-proj-share=/usr/share/proj \
--with-gdal=/usr/bin/gdal-config \
--with-geos \
--with-sqlite \
--with-nls \
--with-zstd \
--with-cairo --with-cairo-ldflags=-lfontconfig \
--with-freetype=yes --with-freetype-includes="/usr/include/freetype2/" \
--with-fftw \
--with-opengl-libs=/usr/include/GL \
--without-postgres \
--without-pdal \
--without-netcdf \
--without-mysql \
--without-odbc \
--without-openmp

# compile GRASS
make -j2

# install compiled GRASS on system
sudo make install

# use GRASS! Start on command line
grass
</source>

===== Enterprise Linux =====

Enterprise Linux (EL) and derivatives (that is, Red Hat Enterprise Linux, CentOS and Scientific Linux) is a popular and robust platform for servers and computing-heavy workstations, and is therefore a good fit for GIS specific requirements.

See: https://wiki.osgeo.org/wiki/Enterprise_Linux_GIS

===== Scientific Linux =====

See Centos

===== CentOS =====

You first need to add the EPEL repository for PROJ and GDAL, see [https://fedoraproject.org/wiki/EPEL/FAQ#How_can_I_install_the_packages_from_the_EPEL_software_repository.3F here]

Preparation '''Centos 8''':
dnf install epel-release

dnf install flex bison make zlib-devel gcc-c++ gettext \
fftw-devel libtiff-devel sqlite-devel \
proj proj-devel proj-datumgrid libxml2 \
geos geos-devel git \
netcdf netcdf-devel atlas-devel \
blas-devel lapack-devel libpq-devel \
python3-devel python3-numpy \
python3-dateutil python3-imaging python3-matplotlib \
gdal gdal-libs gdal-python-tools python3-gdal gdal-devel \
wxGTK3-devel mesa-libGL-devel mesa-libGLU-devel \
libXmu-devel libX11-devel

'''GRASS 8 compilation and installation'''

[https://grass.osgeo.org/grass84/source/snapshot/ Download source code] (e.g., --> "Download latest 8.4 code)" and configure GRASS 8 (suggestion: save this as script):

./configure \
--with-cxx \
--with-proj --with-proj-share=/usr/share/proj \
--with-gdal=/usr/bin/gdal-config \
--with-sqlite \
--with-python \
--with-cairo --with-cairo-ldflags=-lfontconfig \
--with-freetype --with-freetype-includes=/usr/include/freetype2 \
--with-wxwidgets=/usr/bin/wx-config \
--with-openmp \
--with-blas --with-blas-includes=/usr/include/atlas-x86_64-base/ \
--with-lapack --with-lapack-includes=/usr/include/atlas-x86_64-base/ \
--with-fftw \
--with-geos \
--with-netcdf \
--without-ffmpeg \
--without-mysql \
--without-postgres \
--without-odbc \
--without-fftw

Compile:
make
or on a multicore system (number depends of available cores):
make -j4

For a system wide installation, run as root user:
make install
OR simply run it directly from the source code directory (substitute ARCH with i686 or x86_64):

bin.$ARCH/grass -gui

In this case, for convenience, add it to the search path:
mkdir $HOME/bin
cd $HOME/bin
# example:
ln -s $HOME/software/grass84_release/bin.x86_64-pc-linux-gnu/grass .

Now use it subsequently with
grass -gui

'''Installation grass on a HPC system with '''Centos 7''' and no root privileges:'''

This assumes that python3, fftw, proj, gdal and geos are available on the HPC system, either as modules or as installed software.

Download and prepare some dependencies (freetypes and zstd)
mkdir -p $HOME/grass/freetypes
cd $HOME/grass/freetypes
wget path/to/freetype-2.9.1.tar.gz
tar -xf freetype-2.9.1.tar.gz

mkdir $HOME/grass/zstd
cd mkdir $HOME/grass/zstd
wget path/to/v1.4.4/zstd-1.4.4.tar.gz
tar -xf zstd-1.4.4.tar.gz
make install PREFIX=./

Add the ZSTD path to your LD_LIBRARY_PATH

tee -a $HOME/.bashrc > /dev/null << EOT
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$HOME/grass/zstd/zstd-1.4.4/lib
EOT

The configure command could look like this
./configure \
-prefix=$HOME/grass \
--enable-64bit --with-fftw-includes=/path/to/fftw/include/ \
--with-fftw-libs=/path/to/fftw/lib/ \
--with-freetype-includes=$HOME/grass/freetypes/freetype-2.9.1/include/ \
--with-netcdf --with-geos --with-blas --with-lapack --with-postgres \
--with-zstd-includes=$HOME/grass/zstd/zstd-1.4.4/lib/ \
--with-zstd-libs=$HOME/grass/zstd/zstd-1.4.4/lib/ \
--with-gdal=/path/to/gdal-config # This could be the path to a gdal version compiled from source

Finally as usual:
make; make install

grass

===== Gentoo =====

./configure \
--with-freetype=yes --with-freetype-includes="/usr/include/freetype2/"

See also https://packages.gentoo.org/package/sci-geosciences/grass

===== Funtoo =====

{{MovedToTrac|FuntooLinux}}

===== Fedora =====

====== GRASS 8 on Fedora ======

'''Preparation''' for the compilation of GRASS 8+ source code (F36+):

dnf install gcc gcc-c++ bison flex ncurses-devel gettext proj-devel \
gdal gdal-devel sqlite-devel xml2 mesa-libGL-devel cairo-devel \
fftw-devel mesa-libGLU-devel libXmu-devel libX11-devel geos geos-devel \
libtiff-devel python3-devel numpy wxGTK-devel gawk git \
python3-dateutil python3-imaging python3-matplotlib-wx doxygen python3-sphinx \
libzstd-devel libzstd python3-six python3-numpy python3-wxpython4 \
proj-data PDAL-devel PDAL-libs

# optionally also: netcdf-devel postgresql-devel
# atlas-devel lapack-devel lapack-devel
# laszip laszip-devel
# proj-data-at proj-data-au proj-data-be ...

''Note 1: the optional ffmpeg-devel comes from the rpmfusion-free repository ([https://rpmfusion.org/Configuration/ configuration]).''

'''Download''' and unpack the source code:
* GRASS 8: [https://grass.osgeo.org/grass84/source/snapshot/ weekly snapshot] - [https://github.com/OSGeo/grass/releases GitHub repository]

'''Configure''': This is an example how to configure the source code on a Fedora system:

./configure \
--with-cxx \
--with-gdal=/usr/bin/gdal-config \
--with-proj --with-proj-share=/usr/share/proj \
--with-geos \
--with-pdal \
--with-sqlite \
--with-nls \
--with-wxwidgets=/usr/bin/wx-config \
--with-fftw \
--with-cairo --with-cairo-ldflags=-lfontconfig \
--with-freetype --with-freetype-includes=/usr/include/freetype2 \
--enable-largefile \
--without-odbc

''Extra 1:'' If you also want '''FFMPEG support''' - it requires 'dnf install fftw-devel' from the rpmfusion-free repository. Then add to the configuration lines above:

--with-ffmpeg --with-ffmpeg-includes="/usr/include/ffmpeg /usr/include/ffmpeg/libav* /usr/include/ffmpeg/libpostproc /usr/include/ffmpeg/libswscale" \

''Extra 2:'' For '''LAPACK/BLAS support''' (addons i.spec.unmix, v.kriging etc), install "dnf install lapack lapack-devel blas blas-devel atlas atlas-devel". Then add to the configuration lines above:
--with-blas --with-blas-includes=/usr/include/atlas-x86_64-base/ \
--with-lapack --with-lapack-includes=/usr/include/atlas-x86_64-base/ \

''Extra 3:'' For '''ZSTD support''' (Zstandard compression algorithm), first install "dnf install libzstd libzstd-devel zstd". After installing the zstd related packages, add to the configuration lines above:
--with-zstd \

Finally '''compile''' the configured source code:
make
or on multicore (number depends of available cores):
make -j4
and
make install # requires root permissions unless you become owner of /usr/local/

Then use GRASS 8 and enjoy!

grass --version

===== openSUSE =====

To build GRASS on openSUSE:

''Application:Geo'' repo to be added (see [https://software.opensuse.org//download.html?project=Application%3AGeo&package=gdal Install package Application:Geo]

<source lang="bash">
# example for Leap 42 version:
sudo zypper addrepo https://download.opensuse.org/repositories/Application:Geo/openSUSE_Leap_42.3/Application:Geo.repo
sudo zypper refresh
</source>

RPM packages to be installed:
<source lang="bash">
sudo zypper install bison flex freetype2-devel fftw3-devel gcc-c++ \
libgdal-devel libgeos-devel libjpeg-devel libpng-devel libtiff-devel \
man proj libproj-devel readline-devel netcdf-devel ncurses-devel \
mysql-devel postgresql-devel sqlite-devel unixODBC-devel \
tcl-devel tk-devel xorg-x11-Mesa-devel libXmu-devel \
python-numpy python-dateutil python-devel python-opengl \
python-wxWidgets python-xml python-dateutil wxWidgets-devel \
zlib-devel doxygen python-sphinx
</source>

Source code configuration:
<source lang="bash">
./configure \
--enable-largefile \
--with-proj-share=/usr/share/proj \
--with-cxx \
--with-lapack=yes \
--with-motif \
--with-gdal=/usr/bin/gdal-config \
--with-postgres --with-postgres-includes=/usr/include/pgsql \
--with-mysql --with-mysql-includes=/usr/include/mysql \
--with-fftw \
--with-readline \
--with-netcdf \
--with-geos \
--with-nls \
--with-sqlite \
--with-freetype \
--with-freetype-includes=/usr/include/freetype2 \
--with-wxwidgets \
--with-odbc \
--with-python
</source>

Then compile with "make [-j2]".

===== RPM SPEC files =====
* [https://build.opensuse.org/package/show?package=grass&project=Application%3AGeo OpenSuSe]
* [https://pkgs.fedoraproject.org/cgit/rpms/grass.git/tree/grass.spec Fedora]
* ...

==== macOS ====

Compiling GRASS for macOS is not fundamentally different from for other *nix systems. It is on the contrary quite similar, but what differ is the lack of a default package management system for software GRASS depends on. This leaves the mac user to either: (1) compile the dependencies one-by-one; (2) compiling with one of the third-party package management systems avaliable; or (4) a combination thereof.

If you are interested in installing a precompiled version, please check out the [https://grass.osgeo.org/download/software/mac-osx/ official download site].

To date, maybe the easiest way to compile for Mac is by using [https://github.com/nilason/grass-conda GRASS app build script] which is based on the instructions below for building using Anaconda. It will install dependencies, package and install an app bundle with just a command in Terminal.

===== Compilation and installation =====

For more up-to-date instructions please read:

* [https://github.com/nilason/grass-conda Compiling on macOS using Conda] (Intel / Apple silicon based machine M1)
* [[Compiling on macOS using Anaconda]]
* [[Compiling on macOS using Homebrew]]
* [[Compiling on macOS using MacPorts]]

===== Legacy instructions =====

The following compilation and installation instructions are rather outdated as a whole. They do, however, contain parts and snippets that still may be very instructive and useful.

* [[Compiling on MacOSX]]
* [[Compiling on MacOSX using Fink]]
* [https://web.archive.org/web/20180718005252/https://www.kyngchaos.com/software/frameworks#build_scripts build scripts for dependencies]

Troubleshooting:
* solving errors at starting GRASS: [[MacOSX GRASS errors]]

==== FreeBSD / NetBSD ====

The recommended compiler tools are GCC, GNU make, GNU coreutils (for install), and flex. All are available through the respective package managing tools (pkg_add for FreeBSD and pkgin install for NetBSD) and for recent *BSD versions most likely installed by default.

GRASS 8 should compile on FreeBSD and NetBSD.

It is highly recommended to install GDAL/OGR and PROJ first. These libraries and tools are available as [https://www.freebsd.org/ports/ ports for FreeBSD] and [https://www.pkgsrc.org/ packages for NetBSD].

Optional functionality is listed with ''./configure --help'', and related libraries and tools might need to be installed first.

You then may need to edit include/Make/Platform.make and set
ICONVLIB = -liconv

==== AIX ====

A recent [ftp://ftp.gnu.org/gnu/make/ GNU make] (>= 3.81) and GNU coreutils are required. These are available with the [https://www-03.ibm.com/systems/power/software/aix/linux/toolbox/download.html IBM AIX toolbox] or through third-party AIX software repositories, e.g. [https://www.bullfreeware.com/ bullfreeware] and [https://www.perzl.org/aix/ perzl.org]. Note that 'make' does not work, only 'gmake' works.

General instructions to compile on AIX are e.g. [https://www.perzl.org/aix/index.php?n=Main.Instructions here]

On AIX, compilation results by default in 32 bit applications and static libraries. The [https://developer.ibm.com/components/aix/ IBM documentation] explains how to build 64 bit applications and shared libraries with GCC.

'''GRASS 8: Using the IBM xlc compiler:'''

Get and install (in this order):
* [ftp://ftp.gnu.org/gnu/tar/ GNU tar]
* [ftp://ftp.gnu.org/gnu/make/ GNU make] (>= 3.81)
* [https://www.sqlite.org SQLite]
* [https://trac.osgeo.org/proj/ PROJ.4] (for ./configure parameters, see [[Talk:Compile and Install|here]])
* [https://www.gdal.org GDAL] (for ./configure parameters, see [[Talk:Compile and Install|here]])
* [https://grass.osgeo.org/grass84/source/snapshot/ GRASS 8]

The environment variables and configure command that worked:
<pre>
## AIX 5.x

export LIBPATH=/opt/freeware/lib64:/opt/freeware/lib
# make 'ar' happy
export OBJECT_MODE=64

PREFIX=$HOME/private/bin
./configure \
--prefix=$PREFIX \
--disable-shared \
--with-cxx \
--with-proj-includes=$PREFIX/include/ \
--with-proj-libs=$PREFIX/lib/ \
--with-proj-share=$PREFIX/share/proj/ \
--with-sqlite \
--with-sqlite-includes=$PREFIX/include/ \
--with-sqlite-libs=$PREFIX/lib/ \
--with-tiff=no \
--with-png=no \
--with-fftw=no \
--with-cairo=no \
--with-freetype=no
</pre>

'''GRASS 8: Using the GNU gcc compiler:'''

Get and install (in this order):
* if needed, [ftp://ftp.gnu.org/gnu/tar/ GNU tar]
* if needed (the name is often 'gmake' and not 'make') [ftp://ftp.gnu.org/gnu/make/ GNU make] (>= 3.81)
* [https://www.sqlite.org SQLite]
* [https://trac.osgeo.org/proj/ PROJ.4] (for ./configure parameters, see [[Talk:Compile and Install|here]])
* [https://www.gdal.org GDAL] (for ./configure parameters, see [[Talk:Compile and Install|here]])
* [https://grass.osgeo.org/grass84/source/snapshot/ GRASS 8]

The environment variables and configure command that worked for AIX 7.x:
<pre>
## AIX 7.x
export CC="gcc"
export CXX="g++"
PREFIX=$HOME/bin

LDFLAGS="-Wl,-bsvr4,-R,/opt/freeware/lib -L/opt/freeware/lib" CPPFLAGS="-I/opt/freeware/include" ./configure \
--prefix=$PREFIX \
--enable-shared \
--with-includes=/opt/freeware/include --with-libs=/opt/freeware/lib \
--with-cxx \
--with-proj-includes=$PREFIX/include/ \
--with-proj-libs=$PREFIX/lib/ \
--with-proj-share=$PREFIX/share/proj/ \
--with-gdal=$PREFIX/bin/gdal-config \
--with-sqlite \
--with-sqlite-libs=$PREFIX/lib --with-sqlite-includes=$PREFIX/include \
--with-png=no \
--with-tiff=no \
--with-fftw=no \
--with-cairo=no \
--with-opengl=no \
--with-freetype=no
</pre>

==== MS-Windows ====

See also [[WinGRASS Current Status]] for latest updates.

===== MS-Windows/native =====

GRASS on Windows using a standalone installer. It is still MinGW based (we are going to move this to CMake in 2024+).

Instructions to compile from source code:
* [https://trac.osgeo.org/grass/wiki/CompileOnWindows GRASS Windows Native Binary Building Guide]

===== MS-Windows/OSGeo4W =====

OSGeo4W is an installer for a broad set of open source geospatial software packages including GRASS as well as many other packages (QGIS, GDAL/OGR, and more).

* See [https://trac.osgeo.org/osgeo4w/ OSGeo4W]

===== MS-Windows/Cygwin =====

* See the [[Cygwin]] wiki pages

=== Common problems and solutions ===

During compilation, error can occur if certain packages are not installed. Here a list of problems with solution:

* error: X11/Xlib.h: No such file or directory
** this suggests that you don't have the X headers installed
** Solution: Install the libx11-dev package

* error: g.list: error while loading shared libraries: libgdal1.6.0.so.1: cannot open shared object file: No such file or directory
** this error appears in the shell right after the user clicks GUI's "Start GRASS" button. The GUI shows an error about geographic extent and gets closed afterwards.
** It happens when you launch bin.i686 executable on 64bit system. Be careful and choose the right architecture.

* error: lib/python/ctypes
** This error appears during the compilation: <code>free(): invalid pointer Aborted (core dumped)</code>
** It happens when you have multiple <code>libproj</code> versions on your system (check it with command <code>ldd PATH_TO_GRASS_INSTALL/lib/libgrass_gproj.so | grep proj</code> - when this is not your problem, you should obtain exactly one result)
** Solution: Try to reinstall <code>libproj-dev</code> and <code>proj-data</code>

=== Static compilation ===

In order to get static rather than dynamically linked binaries, configure like this:

./configure --disable-shared --enable-static

This will however break the wxGUI and GRASS 8 completely because "ctypes" wants to link against shared libs, or there is something in the static libs that "ctypes" does not like.

=== Optimization ===

GCC and other compilers support [https://gcc.gnu.org/onlinedocs/gcc-4.3.3/gcc/Optimize-Options.html#Optimize-Options optimization]

If you would like to set compiler optimisations, for a possibly faster binary, type (don't enter a ";" anywhere):

CFLAGS=-O ./configure
or,
setenv CFLAGS -O
./configure

whichever works on your shell. Use -O2 instead of -O if your compiler supports this (note: O is the letter, not zero). Using the "gcc" compiler, you can also specify processor specific flags (examples, please suggest better settings to us):

CFLAGS="-mcpu=athlon -O2" # AMD Athlon processor with code optimisations
CFLAGS="-march=amdfam10" # AMD Phenom II X4 64bit processor with gcc >=4.3
CFLAGS="-mcpu=pentium" # Intel Pentium processor
CFLAGS="-mcpu=pentium4" # Intel Pentium4 processor
CFLAGS="-O2 -msse -msse2 -mfpmath=sse -minline-all-stringops" # Intel XEON 64bit processor
CFLAGS="-mtune=nocona -m64 -minline-all-stringops" # Intel Pentium 64bit processor

To find out optional CFLAGS for your platform, enter:
gcc -dumpspecs

See also: https://gcc.gnu.org/

A real fast GRASS version (and small binaries) will be created with LDFLAGS set to "stripping" (but this disables debugging):

CFLAGS="-O2 -mcpu=<cpu_see_above> -Wall" LDFLAGS="-s" ./configure

=== Configure options and their meanings ===

For configure there are many options and some GRASS modules are built only if some options are set. Here are listed common configuration options with short explanation.

* --prefix=/path - Sets path where GRASS will be installed. GRASS will reside in /path/grass-version.
* --enable-largefile - Enables large (>2Gb on 32bit systems) support. For current large file support status look at [[Large File Support]] page.
* --with-cxx - Enables compilation of C++ code. Required for r.terraflow module.
* --with-readline - Enables readline support. If readline is enabled, you can use its history/editing facilities when entering r.mapcalc expressions on stdin.
* --with-glw - Enables GLw support. The GLw library provides OpenGL "canvas" widgets for Athena and Motif.

That switch is unnecessary for normal compilation. It's only
required for r3.showdspf, which isn't normally built; if you
want it, you have build it manually
(e.g. "make -C raster3d/r3.showdspf").
As similar functionality is now provided by NVIZ, r3.showdspf
is deprecated.
r3.showdspf uses the Motif widget (so you also need a
Motif library, e.g. Lesstif or OpenMotif).
[https://grass.itc.it/pipermail/grassuser/2006-December/037475.html Glynn Clements at GRASS-user mailing list]

=== Parallelized compilation on multi-core CPUs ===

You can dramatically accelerate the compilation of the GRASS code with the -j flag of "make" if you have a multi-core CPU system. This determines the maximum number of jobs to have running at once, so cores don't have to sit idle waiting for jobs on other cores to complete. A good rule of thumb for this value is <tt>number_of_cores * 1.5</tt>, but note that setting any higher than the actual number of cores will only affect the timing slightly. For example, on a dual-core processor:
make -j 4



== GRASS-GDAL plugin ==

* see [[Compile and install GRASS and QGIS with GDAL/OGR Plugin]]

== Addons ==

Please note that the installation of [https://grass.osgeo.org/grass-stable/manuals/addons/ GRASS addons] can be easily done with the {{cmd|g.extension}} manager. The compile instructions below are aiming at own development.

=== Compiled modules ===

This is the general way which works for C modules as well as scripts (Python or Shell/Bash modules) which has HTML documentation.

'''Requirements:'''

Either:
* a binary GRASS package, or
* source code which has been prepared with:
./configure [opionally flags]
make libs

Each of the [[GRASS_AddOns|addon]] modules should come with a Makefile. To compile it, just run:
make MODULE_TOPDIR=/path/to/grass84/

Note that the <tt>/path/to/grass84</tt> has to be absolute, not relative.

If using Bash it may be useful to set that up as an alias:
alias gmake64='make MODULE_TOPDIR=/path/to/grass84/'

Installation (perhaps requires "sudo"):
make MODULE_TOPDIR=/path/to/grass84/ install

Note: Compiled addons may require a re-compilation if you changed/updated your GRASS standard binaries.

==== If binary comes with a -dev package ====

''(work in progress, this text states how it eventually will be :)''
Nowadays one does not need to the source code, nor compiling GRASS by oneself to be able to add add-ons. On Debian, you can just install the grass-dev package and then run:
make MODULE_TOPDIR=/usr/lib/grass84/ INST_DIR=/usr/lib/grass84/

The grass-dev package essentially provides GRASS's <tt>include</tt> header files and Make configuration files.

=== Scripts ===

If the addon module is a script, it is sufficient to copy it into the (GRASS binaries) path somewhere. Alternatively, install addons into a separate GRASS addons binaries/scripts directory which is easier to maintain. It avoids getting clobbered every time you reinstall GRASS. To use these separately stored scripts, set and export the GRASS_ADDON_PATH environment variable before starting GRASS and it will automatically be added to the module search path (see the {{cmd|variables}} help page). To simplify this, do for example:

# add in $HOME/.bashrc:
GRASS_ADDON_PATH=/usr/local/grass/addons/
export GRASS_ADDON_PATH

Make sure that the script is executable, then just call it in GRASS typing the filename. Python scripts need to be called writing the extension as well, like:

GRASS (nc_spm):~ > v.krige.py

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

Compile and Install Ubuntu

2026-03-10T09:49:20Z

Neteler: svn -> git

<div class="boilerplate metadata" id="attention" style="-moz-border-radius:30px; border: 1px double #35824B; margin-bottom: 1.5em; padding: 1em; background-color: #f9f9f9;">
<p style="font-size: 150%; text-align: left;"><span style="color:#35824B">'''Attention'''</span> </p><span style="color:#333333">'''The following instructions describe the compilation and installation of GRASS GIS and its required dependencies completely from the source on Ubuntu based systems. Please, prefer pre-compiled packages over the manual way described below unless you know ''what'' and ''how'', you want to learn and help testing.'''</span>
</div>

== Quick instructions ==

These instructions should work fine on Ubuntu distributions:

=== Install geospatial dependencies ===

1. Install some dependencies (PROJ, GEOS, GDAL libraries) and the compiler tools <br />
(note: you need Python 3)

<source lang="bash">
# be sure to have an updated system
sudo apt update && sudo apt upgrade -y

# install PROJ
sudo apt install libproj-dev proj-data proj-bin unzip -y
</source>

<source lang="bash">
# optionally, install (selected) datum grid files
sudo apt-get install proj-data

# install GEOS
sudo apt install libgeos-dev -y

# install GDAL
sudo apt install libgdal-dev python3-gdal gdal-bin -y

## install PDAL (optional) - apparently unavailable on Ubuntu
#sudo apt install libpdal-dev pdal -y

# Python3 precedence over Python2 (which is end-of-life since 2019, so it should be the default anyway)
sudo update-alternatives --install /usr/bin/python python /usr/bin/python3 1
</source>

Install compiler stuff and further dependencies.
Note: this is a single command, please copy-paste it entirely into the terminal:

=== Install further compilation dependencies (Ubuntu 24.04) ===

For Ubuntu 24.04, including wxPython packages for GUI support:

<source lang="bash">
# this is a single command, please copy-paste it entirely into the terminal:
sudo apt-get install \
build-essential \
flex make bison gcc libgcc-s1 g++ \
python3 python3-dev \
python3-dateutil libgsl-dev python3-numpy \
zlib1g-dev gettext \
libtiff-dev libpnglite-dev \
sqlite3 libsqlite3-dev \
libboost-thread-dev libboost-program-options-dev \
systemd-resolved \
git \
checkinstall \
cmake ccache \
python3-opengl libwxbase3.2-1t64 libwxgtk3.2-dev \
python3-wxgtk4.0 \
cairo-dock libcairo2-dev \
libpq-dev \
libfreetype-dev \
libfftw3-dev libfftw3-single3 libfftw3-double3 \
libavcodec-dev \
libxmu-dev \
libavformat-dev libswscale-dev \
libglu1-mesa-dev libxmu-dev \
ghostscript
</source>

For NVIZ on Ubuntu, to also have video support (optional):
<source lang="bash">
sudo apt-get install \
ffmpeg libavutil-dev \
libffmpegthumbnailer-dev \
libavcodec-dev \
libxmu-dev \
libavformat-dev libswscale-dev -y
</source>

=== Source code download ===
Now we have all "ingredients" readily installed on our system.

'''Source code download''':

There a two ways of getting the source code: either use a) the weekly snapshot (cannot be updated, or b) the source code from the GitHub repository (you can update your local copy easily in future):

'''a) Download of the weekly source code snapshot (not recommended):'''
<source lang="bash">
# download latest GRASS GIS 8.x stable release source code:
mkdir $HOME/src/
cd $HOME/src/
wget https://grass.osgeo.org/grass84/source/snapshot/grass-8.4.git_src_snapshot_latest.tar.gz

# Unpack source code package and remove tarball archive:
tar xvfz grass-8.4.git_src_snapshot_latest.tar.gz
rm -f grass-8.4.git_src_snapshot_latest.tar.gz

# rename source code directory (yes, with the questionmarks!)
mv grass-8.4.git_src_snapshot_20??_??_?? grass-8.4.latest
cd grass-8.4.latest/
</source>

'''b) Download of the current development version from GitHub (adopt the path below accordingly)'''

Note: to find the current version number (8_x), see https://github.com/OSGeo/grass/branches:

<source lang="bash">
sudo apt-get install git
git clone https://github.com/OSGeo/grass.git grass-8.4.latest.git
cd grass-8.4.latest.git/
git checkout releasebranch_8_4
</source>

=== Compilation ===
Now we can '''compile''' the source code in order to generate the GRASS GIS binaries:

<source lang="bash">
# "configure" source code for local machine (checks for CPU type etc):
MYCFLAGS='-O2 -fPIC -fno-common -fexceptions -std=gnu99 -fstack-protector -m64'
#MYCXXFLAGS=''
MYLDFLAGS='-Wl,--no-undefined -Wl,-z,now'

LDFLAGS="$MYLDFLAGS" CFLAGS="$MYCFLAGS" CXXFLAGS="$MYCXXFLAGS" ./configure \
--with-cxx \
--enable-largefile \
--with-proj --with-proj-share=/usr/share/proj \
--with-gdal=/usr/bin/gdal-config \
--with-python \
--with-geos \
--with-sqlite \
--with-nls \
--with-zstd \
--with-cairo --with-cairo-ldflags=-lfontconfig \
--with-freetype=yes --with-freetype-includes="/usr/include/freetype2/" \
--with-wxwidgets \
--with-fftw \
--with-openmp \
--with-opengl-libs=/usr/include/GL \
--with-postgres=yes --with-postgres-includes="/usr/include/postgresql" \
--without-pdal \
--without-netcdf \
--without-mysql \
--without-odbc \
--without-ffmpeg
</source>

Now compile the source code (this will take some time as it generates binary code from the source code):
<source lang="bash">
# note: the more CPUs you have, the higher the -j number may be set to
# here: build using 4 CPU cores
make -j4
</source>

=== Installation ===

Install resulting GRASS GIS binaries into /usr/local/:
<source lang="bash">
sudo make install
</source>

Start GRASS GIS in the terminal:
<source lang="bash">
grass
</source>

'''Done & enjoy!'''

== Hints ==

* Usually, the installation of compiled code is done by using the <source lang="bash" enclose="none">make</source> tool. Alternatively, this can be done by using the ''checkinstall'' tool (i.e., <source lang="bash" enclose="none">sudo checkinstall</source> instead of <source lang="bash" enclose="none">sudo make install</source>) which eases off removal of packages. If ''checkinstall'' fails to deliver, please note some related bugs: [https://bugs.launchpad.net/ubuntu/+source/checkinstall/+bug/78455 78455] and [https://bugs.launchpad.net/ubuntu/+source/checkinstall/+bug/599163 599163]. Useful information on using ''checkinstall'': [https://help.ubuntu.com/community/CompilingEasyHowTo Compiling things on Ubuntu the Easy Way].

* In multi-core processors, the compilation performance can be boosted by using ''-j'' switches (e.g. <source lang="bash" enclose="none">make -j2</source> or <source lang="bash" enclose="none">make -j3</source> or even <source lang="bash" enclose="none">make -j4</source>) which specify the number of jobs (commands) to run simultaneously.

== Pre-compiled packages and backports ==

'''Pre-compiled packages and backports''' are available from [https://wiki.ubuntu.com/UbuntuGIS UbuntuGIS] via their [https://launchpad.net/~ubuntugis/+archive/ppa/ ppa.launchpad stable] and [https://launchpad.net/~ubuntugis/+archive/ubuntu/ubuntugis-unstable ppa.launchpad unstable] repositories. '''This is by far the simplest and fastest solution. Please prefer it over the manual way of compiling source code yourself as described below.'''

Version overview:
* jammy2 8.4
* noble 8.3
* jammy (22.04): 8.3
* focal (20.04 LTS): 8.2
* bionic (18.04 LTS): 7.8

a) Daily ready-to-install GRASS GIS builds of the stable release branch and master are available from ''ppa:grass/grass-devel'':

<source lang=bash>
sudo add-apt-repository ppa:ubuntugis/ubuntugis-unstable
sudo add-apt-repository ppa:grass/grass-devel
</source>

b) Latest packaged stable version of GRASS GIS is available from ''ppa:grass/grass-stable'':
<source lang=bash>
sudo add-apt-repository ppa:ubuntugis/ppa
sudo add-apt-repository ppa:grass/grass-stable
sudo apt-get update
sudo apt-get install grass
</source>

== Dependencies ==

=== Current stable Ubuntu version ===
First, update the system from the repositories<source lang="bash">
sudo apt-get update && sudo apt-get upgrade
</source>

Then, install ''SQLite'', ''git'' and ''dependencies'' for compiling PROJ, GEOS, GDAL/OGR, GRASS, GDAL-GRASS-PLUGIN (some additional packages may be required in this case); the following action will also install various dependencies (listed in the command line as <source lang="bash" enclose="none">The following extra packages will be installed:</source>...):<br/>

<source lang="bash">
# this is a single command, please copy-paste it entirely into the terminal:
sudo apt-get install \
build-essential \
flex make bison gcc libgcc1 g++ cmake ccache \
python python-dev \
python-opengl \
python-wxversion python-wxtools python-wxgtk3.2 \
python-dateutil libgsl-dev python-numpy \
wx3.2-headers wx-common libwxgtk3.2-dev \
libwxbase3.2-dev \
libncurses5-dev \
zlib1g-dev gettext \
libtiff5-dev libpnglite-dev \
libcairo libcairo-dev \
sqlite3 libsqlite3-dev \
libpq-dev \
libreadline6 libreadline6-dev libfreetype6-dev \
libfftw3-3 libfftw3-dev \
libboost-thread-dev libboost-program-options-dev \
resolvconf \
libjasper-dev \
git \
libav-tools libavutil-dev ffmpeg2theora \
libffmpegthumbnailer-dev \
libavcodec-dev \
libxmu-dev \
libavformat-dev libswscale-dev \
checkinstall \
libglu1-mesa-dev libxmu-dev \
ghostscript
</source>

* See the additional packages bellow and in other sections and install them. Note that some of them are [https://github.com/OSGeo/grass/blob/main/REQUIREMENTS.md required], namely PROJ, GEOS and GDAL. If you don't have special requirements, it is usually enough just to install PROJ, GEOS and GDAL from repository (rather then compile them manually).

* for mysql support, <source lang="bash" enclose="none">libmysqlclient-dev</source> is required
<source lang="bash">
sudo apt-get install libmysqlclient-dev
</source>

* for netcdf support, <source lang="bash" enclose="none">netcdf-bin</source> and <source lang="bash" enclose="none">libnetcdf-dev</source> is required
<source lang="bash">
sudo apt-get install netcdf-bin libnetcdf-dev
</source>

* for {{AddonCmd|i.spec.unmix}} Addon support, install LAPACK and BLAS:
<source lang="bash">
sudo apt-get install libblas-dev liblapack-dev
</source>

* create a directory as a simple user where all source code is going to be stored -- in this example, a directory named <source lang="bash" enclose="none">src</source> under <source lang="bash" enclose="none">/usr/local</source> is created <source lang="bash">
sudo mkdir /usr/local/src
</source>

* take over directories ownerships ('''replace''' below the terms ''userid'' and ''groupid'' with a real <source lang="bash" enclose="none">userid</source>): <source lang="bash">
sudo chown userid:groupid /usr/local/src</source>

* similarly, grant <source lang="bash" enclose="none">rwx</source> (read-write-execute) permissions for our ''userid'' and ''groupid'' onto the <source lang="bash" enclose="none">src</source> directory: <source lang="bash">
sudo chmod ug+rwx /usr/local/src</source>

== Using pre-compiled dev Packages for PROJ, GEOS and GDAL ==

=== PROJ ===

Install the <source lang="bash" enclose="none">dev</source> package:

<source lang="bash">
sudo apt-get install libproj-dev proj-data proj-bin
</source>

* In the call to <source lang="bash" enclose="none">./configure</source> for [[#GRASS|GRASS]], replace <source lang="bash" enclose="none">--with-proj-share=/usr/local/share/proj/</source> by <source lang="bash" enclose="none">--with-proj-share=/usr/share/proj/</source>

=== GEOS ===

Install the <source lang="bash" enclose="none">dev</source> package:

<source lang="bash">
# probably you also need to additionally install "libgeos-c1v5"
sudo apt-get install libgeos-dev
</source>

* In the call to <source lang="bash" enclose="none">./configure</source> for [[#GRASS|GRASS]], replace <source lang="bash" enclose="none">--with-geos=/usr/local/bin/geos-config</source> by <source lang="bash" enclose="none">--with-geos=/usr/bin/geos-config</source>

=== GDAL ===

Install the <source lang="bash" enclose="none">dev</source> package (possibly without support for datumgrid):

<source lang="bash">
sudo apt-get install libgdal-dev
</source>

For support of WMS in wxGUI install Python GDAL bindings and GDAL executables:
<source lang="bash">
sudo apt-get install python-gdal gdal-bin
</source>

* Install also the required extra packages (note the message: <source lang="bash" enclose="none">The following extra packages will be installed:</source>)
* Look out for packages to be removed by this operation -- this is most likely caused by incompatible package versions. Fix these problems in advance using commands like the following: <source lang="bash">
sudo apt-get install <package>=<required.version></source>

=== GRASS-GIS ===

[[Compile_and_Install_Ubuntu#GRASS_GIS|Jump to sub-section GRASS-GIS below]]

== Using pre-compiled dev Packages for PROJ, GEOS and GDAL from GIS.lab PPA==

Ivan Mincik has made all required packages available in his [https://launchpad.net/~imincik/+archive/ubuntu/gis PPA]:

<source lang="bash">
sudo add-apt-repository ppa:imincik/gis
sudo apt-get install libproj-dev libgdal-dev python-gdal libgeos-dev
</source>

Now you can either also install GRASS GIS from there or compile it yourself (see [[Compile_and_Install_Ubuntu#GRASS_GIS|Jump to sub-section GRASS-GIS below]])

== Compile from source ==

=== PROJ ===

* within the directory <source lang="bash" enclose="none">/usr/local/src</source> (create it if it does not exist) checkout <source lang="bash" enclose="none">proj</source> from its GitHub repository: <source lang="bash">
https://github.com/OSGeo/PROJ/
</source>

* get [http://download.osgeo.org/proj/proj-datumgrid-1.8.zip '''proj-datumgrid-1.8.zip'''] or related files from [https://trac.osgeo.org/proj proj' trac] and move it under <source lang="bash" enclose="none">proj/nad</source>
<ul><source lang="bash">
wget http://download.osgeo.org/proj/proj-datumgrid-1.8.zip
mv proj-datumgrid-1.8.zip /usr/local/src/proj/nad
cd /usr/local/src/proj/nad
</source>
</ul>

* decompress it <source lang="bash">
unzip proj-datumgrid-1.8.zip
</source>

* go back to the <source lang="bash" enclose="none">proj</source> directory <source lang="bash">
cd /usr/local/src/proj
</source>

* if required, clean previous configuration & compilation <source lang="bash">
make distclean
</source>

* simple configure, compile and install <source lang="bash">
./configure && make && sudo make install
</source>
<ul> or <source lang="bash">
./configure && make -j2 && sudo checkinstall
</source>
</ul>

* ensure that <source lang="bash" enclose="none">/usr/local/lib</source> is added to <source lang="bash" enclose="none">/etc/ld.so.conf</source> and afterwards run <source lang="bash">
sudo ldconfig
</source>

* finally, go back to the parent directory simply by instructing<source lang="bash">
cd ..
</source>

=== GEOS ===

* download '''geos-3.12.2.tar.bz2''' from [https://libgeos.org/ https://libgeos.org/] using <source lang="bash" enclose="none">wget</source> <source lang="bash">
wget https://download.osgeo.org/geos/geos-3.12.2.tar.bz2
</source>

* move to the "source-code" directory and decompress
<ul><source lang="bash">
cd /usr/local/src/
bunzip2 geos-3.12.2.tar.bz2
tar xvf geos-3.12.2.tar
</source>
</ul>

* if required, clean previous configuration & compilation <source lang="bash">
make distclean
</source>

* move to geos directory <source lang="bash">
cd geos-3.12.2
</source>

* simple configure, compile and install <source lang="bash">
./configure && make && sudo make install
</source>
<ul> or <source lang="bash">
./configure && make -j2 && sudo checkinstall
</source>
</ul>

* do not forget to execute <source lang="bash">
sudo ldconfig
</source>

=== GDAL ===

'''Note''', GDAL must be compiled '''without''' GRASS support!

* download the current stable version (see https://github.com/OSGeo/gdal/releases for latest version):
<source lang="bash">
wget https://github.com/OSGeo/gdal/releases/download/v3.9.1/gdal-3.9.1.tar.gz
</source>

Follow the instructions to compile GDAL:
https://gdal.org/development/building_from_source.html

=== GRASS GIS ===

Note the differences between different GRASS GIS version (branches) in download and cofiguration. Note also the changes required if you installed some of the dependencies from packages (rather then compiled them yourself).

To fully understand the build process, read the <code>INSTALL</code> file, which is located in GRASS' source code root directory.

''' Getting GRASS' source code '''

Select from one of the GRASS GIS versions and download the source code:

https://github.com/OSGeo/grass/releases/

''' Configure, Compile and Install'''

Enter the directory with the source code, for example:

<source lang="bash">
cd grass
</source>

* '''GRASS GIS example configuration''' (which can/should be adjusted according to specific needs):
<ul>
<source lang="bash">
CFLAGS="-O2 -Wall" LDFLAGS="-s" ./configure \
--with-nls \
--with-cxx \
--with-proj-share=/usr/local/share/proj/ \
--with-geos=/usr/local/bin/geos-config \
--with-wxwidgets \
--with-cairo \
--with-opengl-libs=/usr/include/GL \
--with-freetype=yes --with-freetype-includes="/usr/include/freetype2/" \
--with-postgres=yes --with-postgres-includes="/usr/include/postgresql" \
--with-sqlite=yes \
--with-mysql=yes --with-mysql-includes="/usr/include/mysql" \
--with-odbc=no \
--with-pdal
</source>
</ul>
<ul>
'''Note''', the above configuration uses the <code>PROJ</code> and <code>GEOS</code> packages compiled from the source. In the case that pre-compiled versions from the repository are required, remove the above corresponding lines to use the "defaults", i.e. (note the backslashe at the end of each line)
<source lang="bash">
--with-proj-share=/usr/share/proj \
--with-geos=/usr/bin/geos-config \
</source>
</ul>

* compile & install <source lang="bash">
make -j2 && sudo make install && sudo ldconfig
</source>

<ul> or <source lang="bash">
make -j2 && sudo checkinstall && sudo ldconfig
</source>
</ul>

For subsequent updates execute (not need for the first time):
<source lang="bash">
git pull
make -j2 && sudo make install && sudo ldconfig
</source>

Sometimes, it is required to clean previous configuration and compilation:
<source lang="bash">
make distclean
git pull
./configure ... # (use the configure command above)
make -j2 && sudo make install && sudo ldconfig
</source>

=== GDAL-GRASS-Plugin ===

See: https://github.com/OSGeo/gdal-grass

* get the plugin from [https://github.com/OSGeo/gdal-grass/releases GitHub]: "gdal-grass-X.Y.Z.tar.gz" using <source lang="bash" enclose="none">wget</source>
<ul><source lang="bash">
# update version number accordingly!
wget https://github.com/OSGeo/gdal-grass/archive/refs/tags/1.0.2.tar.gz -O gdal-grass-1.0.2.tar.gz
tar xvzf gdal-grass-1.0.2.tar.gz
cd gdal-grass-1.0.2
</source></ul>

* create <source lang="bash" enclose="none">/etc/ld.so.conf.d/grass.conf</source> or add in <source lang="bash" enclose="none">/etc/ld.so.conf</source> the GRASS library path:
<ul><source lang="bash">
# GRASS GIS stable library path (adapt as needed)
/usr/local/src/releasebranch_8_4/lib

# GRASS GIS development version library path (adapt as needed)
/usr/local/src/grass_master/lib
</source></ul>

* optionally, clean previous configurations/compilations<source lang="bash">
make distclean</source>

* configure -- point to GRASS installation/binaries
<ul><source lang="bash"> ./configure \
--prefix=/usr/local \
--with-gdal=/usr/local/bin/gdal-config \
--with-grass=/usr/local/grass/ \
--with-autoload="/usr/local/lib64/gdalplugins/" \
--with-ld-shared="g++ -shared"</source></ul>
</ul>

* compile & install using checkinstall<source lang="bash">
make -j2 && sudo checkinstall</source>

= Post compilation/installation control =

* For a recommended quick-check read the [https://grass.osgeo.org/wiki/Compile_and_install_GRASS_and_QGIS_with_GDAL/OGR_Plugin#Troubleshooting Troubleshooting] section at [https://grass.osgeo.org/wiki/Compile_and_install_GDAL-GRASS_plugin Compile_and_install_GDAL-GRASS_plugin]

* in case of errors in future compilation attempts, remember to remove program binaries and files created with the "configuration" from previous compilations with
make distclean

* another common mistake is compiling a module against some GRASS version and then try to run it through another GRASS version. The solution is to recompile the affected module or, in case there are multiple GRASS installations, set up properly LD_LIBRARY_PATH paths.

= Removal of GRASS =

To get rid of a GRASS binaries installation, delete (update version numbers accordingly)
* <source lang="bash" enclose="none">/usr/local/grass</source> (directory, binaries location)
* <source lang="bash" enclose="none">/usr/local/bin/grass</source> (file)
* <source lang="bash" enclose="none">/home/username/.grassrc8</source> (file)

If wanted, delete also the complete source code:
* <source lang="bash" enclose="none">/usr/local/src/grass_release</source> (directory, source code location)

To remove <code>grass</code> (or any other package) which was installed by <source lang="bash" enclose="none">checkinstall</source>, use <source lang="bash" enclose="none">dpkg</source>, e.g.<source lang="bash">
sudo dpkg -r grass # package name defined at installation is important</source>

== See also ==

* Docker: https://grass.osgeo.org/download/docker/
* [[Ubuntu Packaging]]
* [[GRASS in Debian]]

= Archived Notes =

Notes that concern the configuration and compilation of GRASS GIS and its dependencies for older versions of Ubuntu-Linux.

[[Category: Compilation]]
[[Category: Installation]]
[[Category: Ubuntu]]
[[Category: FAQ]]

Compile and Install Ubuntu

2026-03-10T09:48:27Z

Neteler: /* Current stable Ubuntu version */

<div class="boilerplate metadata" id="attention" style="-moz-border-radius:30px; border: 1px double #35824B; margin-bottom: 1.5em; padding: 1em; background-color: #f9f9f9;">
<p style="font-size: 150%; text-align: left;"><span style="color:#35824B">'''Attention'''</span> </p><span style="color:#333333">'''The following instructions describe the compilation and installation of GRASS GIS and its required dependencies completely from the source on Ubuntu based systems. Please, prefer pre-compiled packages over the manual way described below unless you know ''what'' and ''how'', you want to learn and help testing.'''</span>
</div>

== Quick instructions ==

These instructions should work fine on Ubuntu distributions:

=== Install geospatial dependencies ===

1. Install some dependencies (PROJ, GEOS, GDAL libraries) and the compiler tools <br />
(note: you need Python 3)

<source lang="bash">
# be sure to have an updated system
sudo apt update && sudo apt upgrade -y

# install PROJ
sudo apt install libproj-dev proj-data proj-bin unzip -y
</source>

<source lang="bash">
# optionally, install (selected) datum grid files
sudo apt-get install proj-data

# install GEOS
sudo apt install libgeos-dev -y

# install GDAL
sudo apt install libgdal-dev python3-gdal gdal-bin -y

## install PDAL (optional) - apparently unavailable on Ubuntu
#sudo apt install libpdal-dev pdal -y

# Python3 precedence over Python2 (which is end-of-life since 2019, so it should be the default anyway)
sudo update-alternatives --install /usr/bin/python python /usr/bin/python3 1
</source>

Install compiler stuff and further dependencies.
Note: this is a single command, please copy-paste it entirely into the terminal:

=== Install further compilation dependencies (Ubuntu 24.04) ===

For Ubuntu 24.04, including wxPython packages for GUI support:

<source lang="bash">
# this is a single command, please copy-paste it entirely into the terminal:
sudo apt-get install \
build-essential \
flex make bison gcc libgcc-s1 g++ \
python3 python3-dev \
python3-dateutil libgsl-dev python3-numpy \
zlib1g-dev gettext \
libtiff-dev libpnglite-dev \
sqlite3 libsqlite3-dev \
libboost-thread-dev libboost-program-options-dev \
systemd-resolved \
git \
checkinstall \
cmake ccache \
python3-opengl libwxbase3.2-1t64 libwxgtk3.2-dev \
python3-wxgtk4.0 \
cairo-dock libcairo2-dev \
libpq-dev \
libfreetype-dev \
libfftw3-dev libfftw3-single3 libfftw3-double3 \
libavcodec-dev \
libxmu-dev \
libavformat-dev libswscale-dev \
libglu1-mesa-dev libxmu-dev \
ghostscript
</source>

For NVIZ on Ubuntu, to also have video support (optional):
<source lang="bash">
sudo apt-get install \
ffmpeg libavutil-dev \
libffmpegthumbnailer-dev \
libavcodec-dev \
libxmu-dev \
libavformat-dev libswscale-dev -y
</source>

=== Source code download ===
Now we have all "ingredients" readily installed on our system.

'''Source code download''':

There a two ways of getting the source code: either use a) the weekly snapshot (cannot be updated, or b) the source code from the GitHub repository (you can update your local copy easily in future):

'''a) Download of the weekly source code snapshot (not recommended):'''
<source lang="bash">
# download latest GRASS GIS 8.x stable release source code:
mkdir $HOME/src/
cd $HOME/src/
wget https://grass.osgeo.org/grass84/source/snapshot/grass-8.4.git_src_snapshot_latest.tar.gz

# Unpack source code package and remove tarball archive:
tar xvfz grass-8.4.git_src_snapshot_latest.tar.gz
rm -f grass-8.4.git_src_snapshot_latest.tar.gz

# rename source code directory (yes, with the questionmarks!)
mv grass-8.4.git_src_snapshot_20??_??_?? grass-8.4.latest
cd grass-8.4.latest/
</source>

'''b) Download of the current development version from GitHub (adopt the path below accordingly)'''

Note: to find the current version number (8_x), see https://github.com/OSGeo/grass/branches:

<source lang="bash">
sudo apt-get install git
git clone https://github.com/OSGeo/grass.git grass-8.4.latest.git
cd grass-8.4.latest.git/
git checkout releasebranch_8_4
</source>

=== Compilation ===
Now we can '''compile''' the source code in order to generate the GRASS GIS binaries:

<source lang="bash">
# "configure" source code for local machine (checks for CPU type etc):
MYCFLAGS='-O2 -fPIC -fno-common -fexceptions -std=gnu99 -fstack-protector -m64'
#MYCXXFLAGS=''
MYLDFLAGS='-Wl,--no-undefined -Wl,-z,now'

LDFLAGS="$MYLDFLAGS" CFLAGS="$MYCFLAGS" CXXFLAGS="$MYCXXFLAGS" ./configure \
--with-cxx \
--enable-largefile \
--with-proj --with-proj-share=/usr/share/proj \
--with-gdal=/usr/bin/gdal-config \
--with-python \
--with-geos \
--with-sqlite \
--with-nls \
--with-zstd \
--with-cairo --with-cairo-ldflags=-lfontconfig \
--with-freetype=yes --with-freetype-includes="/usr/include/freetype2/" \
--with-wxwidgets \
--with-fftw \
--with-openmp \
--with-opengl-libs=/usr/include/GL \
--with-postgres=yes --with-postgres-includes="/usr/include/postgresql" \
--without-pdal \
--without-netcdf \
--without-mysql \
--without-odbc \
--without-ffmpeg
</source>

Now compile the source code (this will take some time as it generates binary code from the source code):
<source lang="bash">
# note: the more CPUs you have, the higher the -j number may be set to
# here: build using 4 CPU cores
make -j4
</source>

=== Installation ===

Install resulting GRASS GIS binaries into /usr/local/:
<source lang="bash">
sudo make install
</source>

Start GRASS GIS in the terminal:
<source lang="bash">
grass
</source>

'''Done & enjoy!'''

== Hints ==

* Usually, the installation of compiled code is done by using the <source lang="bash" enclose="none">make</source> tool. Alternatively, this can be done by using the ''checkinstall'' tool (i.e., <source lang="bash" enclose="none">sudo checkinstall</source> instead of <source lang="bash" enclose="none">sudo make install</source>) which eases off removal of packages. If ''checkinstall'' fails to deliver, please note some related bugs: [https://bugs.launchpad.net/ubuntu/+source/checkinstall/+bug/78455 78455] and [https://bugs.launchpad.net/ubuntu/+source/checkinstall/+bug/599163 599163]. Useful information on using ''checkinstall'': [https://help.ubuntu.com/community/CompilingEasyHowTo Compiling things on Ubuntu the Easy Way].

* In multi-core processors, the compilation performance can be boosted by using ''-j'' switches (e.g. <source lang="bash" enclose="none">make -j2</source> or <source lang="bash" enclose="none">make -j3</source> or even <source lang="bash" enclose="none">make -j4</source>) which specify the number of jobs (commands) to run simultaneously.

== Pre-compiled packages and backports ==

'''Pre-compiled packages and backports''' are available from [https://wiki.ubuntu.com/UbuntuGIS UbuntuGIS] via their [https://launchpad.net/~ubuntugis/+archive/ppa/ ppa.launchpad stable] and [https://launchpad.net/~ubuntugis/+archive/ubuntu/ubuntugis-unstable ppa.launchpad unstable] repositories. '''This is by far the simplest and fastest solution. Please prefer it over the manual way of compiling source code yourself as described below.'''

Version overview:
* jammy2 8.4
* noble 8.3
* jammy (22.04): 8.3
* focal (20.04 LTS): 8.2
* bionic (18.04 LTS): 7.8

a) Daily ready-to-install GRASS GIS builds of the stable release branch and master are available from ''ppa:grass/grass-devel'':

<source lang=bash>
sudo add-apt-repository ppa:ubuntugis/ubuntugis-unstable
sudo add-apt-repository ppa:grass/grass-devel
</source>

b) Latest packaged stable version of GRASS GIS is available from ''ppa:grass/grass-stable'':
<source lang=bash>
sudo add-apt-repository ppa:ubuntugis/ppa
sudo add-apt-repository ppa:grass/grass-stable
sudo apt-get update
sudo apt-get install grass
</source>

== Dependencies ==

=== Current stable Ubuntu version ===
First, update the system from the repositories<source lang="bash">
sudo apt-get update && sudo apt-get upgrade
</source>

Then, install ''SQLite'', ''git'' and ''dependencies'' for compiling PROJ, GEOS, GDAL/OGR, GRASS, GDAL-GRASS-PLUGIN (some additional packages may be required in this case); the following action will also install various dependencies (listed in the command line as <source lang="bash" enclose="none">The following extra packages will be installed:</source>...):<br/>

<source lang="bash">
# this is a single command, please copy-paste it entirely into the terminal:
sudo apt-get install \
build-essential \
flex make bison gcc libgcc1 g++ cmake ccache \
python python-dev \
python-opengl \
python-wxversion python-wxtools python-wxgtk3.2 \
python-dateutil libgsl-dev python-numpy \
wx3.2-headers wx-common libwxgtk3.2-dev \
libwxbase3.2-dev \
libncurses5-dev \
zlib1g-dev gettext \
libtiff5-dev libpnglite-dev \
libcairo libcairo-dev \
sqlite3 libsqlite3-dev \
libpq-dev \
libreadline6 libreadline6-dev libfreetype6-dev \
libfftw3-3 libfftw3-dev \
libboost-thread-dev libboost-program-options-dev \
resolvconf \
libjasper-dev \
git \
libav-tools libavutil-dev ffmpeg2theora \
libffmpegthumbnailer-dev \
libavcodec-dev \
libxmu-dev \
libavformat-dev libswscale-dev \
checkinstall \
libglu1-mesa-dev libxmu-dev \
ghostscript
</source>

* See the additional packages bellow and in other sections and install them. Note that some of them are [https://github.com/OSGeo/grass/blob/main/REQUIREMENTS.md required], namely PROJ, GEOS and GDAL. If you don't have special requirements, it is usually enough just to install PROJ, GEOS and GDAL from repository (rather then compile them manually).

* for mysql support, <source lang="bash" enclose="none">libmysqlclient-dev</source> is required
<source lang="bash">
sudo apt-get install libmysqlclient-dev
</source>

* for netcdf support, <source lang="bash" enclose="none">netcdf-bin</source> and <source lang="bash" enclose="none">libnetcdf-dev</source> is required
<source lang="bash">
sudo apt-get install netcdf-bin libnetcdf-dev
</source>

* for {{AddonCmd|i.spec.unmix}} Addon support, install LAPACK and BLAS:
<source lang="bash">
sudo apt-get install libblas-dev liblapack-dev
</source>

* create a directory as a simple user where all source code is going to be stored -- in this example, a directory named <source lang="bash" enclose="none">src</source> under <source lang="bash" enclose="none">/usr/local</source> is created <source lang="bash">
sudo mkdir /usr/local/src
</source>

* take over directories ownerships ('''replace''' below the terms ''userid'' and ''groupid'' with a real <source lang="bash" enclose="none">userid</source>): <source lang="bash">
sudo chown userid:groupid /usr/local/src</source>

* similarly, grant <source lang="bash" enclose="none">rwx</source> (read-write-execute) permissions for our ''userid'' and ''groupid'' onto the <source lang="bash" enclose="none">src</source> directory: <source lang="bash">
sudo chmod ug+rwx /usr/local/src</source>

== Using pre-compiled dev Packages for PROJ, GEOS and GDAL ==

=== PROJ ===

Install the <source lang="bash" enclose="none">dev</source> package:

<source lang="bash">
sudo apt-get install libproj-dev proj-data proj-bin
</source>

* In the call to <source lang="bash" enclose="none">./configure</source> for [[#GRASS|GRASS]], replace <source lang="bash" enclose="none">--with-proj-share=/usr/local/share/proj/</source> by <source lang="bash" enclose="none">--with-proj-share=/usr/share/proj/</source>

=== GEOS ===

Install the <source lang="bash" enclose="none">dev</source> package:

<source lang="bash">
# probably you also need to additionally install "libgeos-c1v5"
sudo apt-get install libgeos-dev
</source>

* In the call to <source lang="bash" enclose="none">./configure</source> for [[#GRASS|GRASS]], replace <source lang="bash" enclose="none">--with-geos=/usr/local/bin/geos-config</source> by <source lang="bash" enclose="none">--with-geos=/usr/bin/geos-config</source>

=== GDAL ===

Install the <source lang="bash" enclose="none">dev</source> package (possibly without support for datumgrid):

<source lang="bash">
sudo apt-get install libgdal-dev
</source>

For support of WMS in wxGUI install Python GDAL bindings and GDAL executables:
<source lang="bash">
sudo apt-get install python-gdal gdal-bin
</source>

* Install also the required extra packages (note the message: <source lang="bash" enclose="none">The following extra packages will be installed:</source>)
* Look out for packages to be removed by this operation -- this is most likely caused by incompatible package versions. Fix these problems in advance using commands like the following: <source lang="bash">
sudo apt-get install <package>=<required.version></source>

=== GRASS-GIS ===

[[Compile_and_Install_Ubuntu#GRASS_GIS|Jump to sub-section GRASS-GIS below]]

== Using pre-compiled dev Packages for PROJ, GEOS and GDAL from GIS.lab PPA==

Ivan Mincik has made all required packages available in his [https://launchpad.net/~imincik/+archive/ubuntu/gis PPA]:

<source lang="bash">
sudo add-apt-repository ppa:imincik/gis
sudo apt-get install libproj-dev libgdal-dev python-gdal libgeos-dev
</source>

Now you can either also install GRASS GIS from there or compile it yourself (see [[Compile_and_Install_Ubuntu#GRASS_GIS|Jump to sub-section GRASS-GIS below]])

== Compile from source ==

=== PROJ ===

* within the directory <source lang="bash" enclose="none">/usr/local/src</source> (create it if it does not exist) checkout <source lang="bash" enclose="none">proj</source> from its GitHub repository: <source lang="bash">
https://github.com/OSGeo/PROJ/
</source>

* get [http://download.osgeo.org/proj/proj-datumgrid-1.8.zip '''proj-datumgrid-1.8.zip'''] or related files from [https://trac.osgeo.org/proj proj' trac] and move it under <source lang="bash" enclose="none">proj/nad</source>
<ul><source lang="bash">
wget http://download.osgeo.org/proj/proj-datumgrid-1.8.zip
mv proj-datumgrid-1.8.zip /usr/local/src/proj/nad
cd /usr/local/src/proj/nad
</source>
</ul>

* decompress it <source lang="bash">
unzip proj-datumgrid-1.8.zip
</source>

* go back to the <source lang="bash" enclose="none">proj</source> directory <source lang="bash">
cd /usr/local/src/proj
</source>

* if required, clean previous configuration & compilation <source lang="bash">
make distclean
</source>

* simple configure, compile and install <source lang="bash">
./configure && make && sudo make install
</source>
<ul> or <source lang="bash">
./configure && make -j2 && sudo checkinstall
</source>
</ul>

* ensure that <source lang="bash" enclose="none">/usr/local/lib</source> is added to <source lang="bash" enclose="none">/etc/ld.so.conf</source> and afterwards run <source lang="bash">
sudo ldconfig
</source>

* finally, go back to the parent directory simply by instructing<source lang="bash">
cd ..
</source>

=== GEOS ===

* download '''geos-3.12.2.tar.bz2''' from [https://libgeos.org/ https://libgeos.org/] using <source lang="bash" enclose="none">wget</source> <source lang="bash">
wget https://download.osgeo.org/geos/geos-3.12.2.tar.bz2
</source>

* move to the "source-code" directory and decompress
<ul><source lang="bash">
cd /usr/local/src/
bunzip2 geos-3.12.2.tar.bz2
tar xvf geos-3.12.2.tar
</source>
</ul>

* if required, clean previous configuration & compilation <source lang="bash">
make distclean
</source>

* move to geos directory <source lang="bash">
cd geos-3.12.2
</source>

* simple configure, compile and install <source lang="bash">
./configure && make && sudo make install
</source>
<ul> or <source lang="bash">
./configure && make -j2 && sudo checkinstall
</source>
</ul>

* do not forget to execute <source lang="bash">
sudo ldconfig
</source>

=== GDAL ===

'''Note''', GDAL must be compiled '''without''' GRASS support!

* download the current stable version (see https://github.com/OSGeo/gdal/releases for latest version):
<source lang="bash">
wget https://github.com/OSGeo/gdal/releases/download/v3.9.1/gdal-3.9.1.tar.gz
</source>

Follow the instructions to compile GDAL:
https://gdal.org/development/building_from_source.html

=== GRASS GIS ===

Note the differences between different GRASS GIS version (branches) in download and cofiguration. Note also the changes required if you installed some of the dependencies from packages (rather then compiled them yourself).

To fully understand the build process, read the <code>INSTALL</code> file, which is located in GRASS' source code root directory.

''' Getting GRASS' source code '''

Select from one of the GRASS GIS versions and download the source code:

https://github.com/OSGeo/grass/releases/

''' Configure, Compile and Install'''

Enter the directory with the source code, for example:

<source lang="bash">
cd grass
</source>

* '''GRASS GIS example configuration''' (which can/should be adjusted according to specific needs):
<ul>
<source lang="bash">
CFLAGS="-O2 -Wall" LDFLAGS="-s" ./configure \
--with-nls \
--with-cxx \
--with-proj-share=/usr/local/share/proj/ \
--with-geos=/usr/local/bin/geos-config \
--with-wxwidgets \
--with-cairo \
--with-opengl-libs=/usr/include/GL \
--with-freetype=yes --with-freetype-includes="/usr/include/freetype2/" \
--with-postgres=yes --with-postgres-includes="/usr/include/postgresql" \
--with-sqlite=yes \
--with-mysql=yes --with-mysql-includes="/usr/include/mysql" \
--with-odbc=no \
--with-pdal
</source>
</ul>
<ul>
'''Note''', the above configuration uses the <code>PROJ</code> and <code>GEOS</code> packages compiled from the source. In the case that pre-compiled versions from the repository are required, remove the above corresponding lines to use the "defaults", i.e. (note the backslashe at the end of each line)
<source lang="bash">
--with-proj-share=/usr/share/proj \
--with-geos=/usr/bin/geos-config \
</source>
</ul>

* compile & install <source lang="bash">
make -j2 && sudo make install && sudo ldconfig
</source>

<ul> or <source lang="bash">
make -j2 && sudo checkinstall && sudo ldconfig
</source>
</ul>

For subsequent updates execute (not need for the first time):
<source lang="bash">
svn up
make -j2 && sudo make install && sudo ldconfig
</source>

Sometimes, it is required to clean previous configuration and compilation:
<source lang="bash">
make distclean
svn up
./configure ... # (use the configure command above)
make -j2 && sudo make install && sudo ldconfig
</source>

=== GDAL-GRASS-Plugin ===

See: https://github.com/OSGeo/gdal-grass

* get the plugin from [https://github.com/OSGeo/gdal-grass/releases GitHub]: "gdal-grass-X.Y.Z.tar.gz" using <source lang="bash" enclose="none">wget</source>
<ul><source lang="bash">
# update version number accordingly!
wget https://github.com/OSGeo/gdal-grass/archive/refs/tags/1.0.2.tar.gz -O gdal-grass-1.0.2.tar.gz
tar xvzf gdal-grass-1.0.2.tar.gz
cd gdal-grass-1.0.2
</source></ul>

* create <source lang="bash" enclose="none">/etc/ld.so.conf.d/grass.conf</source> or add in <source lang="bash" enclose="none">/etc/ld.so.conf</source> the GRASS library path:
<ul><source lang="bash">
# GRASS GIS stable library path (adapt as needed)
/usr/local/src/releasebranch_8_4/lib

# GRASS GIS development version library path (adapt as needed)
/usr/local/src/grass_master/lib
</source></ul>

* optionally, clean previous configurations/compilations<source lang="bash">
make distclean</source>

* configure -- point to GRASS installation/binaries
<ul><source lang="bash"> ./configure \
--prefix=/usr/local \
--with-gdal=/usr/local/bin/gdal-config \
--with-grass=/usr/local/grass/ \
--with-autoload="/usr/local/lib64/gdalplugins/" \
--with-ld-shared="g++ -shared"</source></ul>
</ul>

* compile & install using checkinstall<source lang="bash">
make -j2 && sudo checkinstall</source>

= Post compilation/installation control =

* For a recommended quick-check read the [https://grass.osgeo.org/wiki/Compile_and_install_GRASS_and_QGIS_with_GDAL/OGR_Plugin#Troubleshooting Troubleshooting] section at [https://grass.osgeo.org/wiki/Compile_and_install_GDAL-GRASS_plugin Compile_and_install_GDAL-GRASS_plugin]

* in case of errors in future compilation attempts, remember to remove program binaries and files created with the "configuration" from previous compilations with
make distclean

* another common mistake is compiling a module against some GRASS version and then try to run it through another GRASS version. The solution is to recompile the affected module or, in case there are multiple GRASS installations, set up properly LD_LIBRARY_PATH paths.

= Removal of GRASS =

To get rid of a GRASS binaries installation, delete (update version numbers accordingly)
* <source lang="bash" enclose="none">/usr/local/grass</source> (directory, binaries location)
* <source lang="bash" enclose="none">/usr/local/bin/grass</source> (file)
* <source lang="bash" enclose="none">/home/username/.grassrc8</source> (file)

If wanted, delete also the complete source code:
* <source lang="bash" enclose="none">/usr/local/src/grass_release</source> (directory, source code location)

To remove <code>grass</code> (or any other package) which was installed by <source lang="bash" enclose="none">checkinstall</source>, use <source lang="bash" enclose="none">dpkg</source>, e.g.<source lang="bash">
sudo dpkg -r grass # package name defined at installation is important</source>

== See also ==

* Docker: https://grass.osgeo.org/download/docker/
* [[Ubuntu Packaging]]
* [[GRASS in Debian]]

= Archived Notes =

Notes that concern the configuration and compilation of GRASS GIS and its dependencies for older versions of Ubuntu-Linux.

[[Category: Compilation]]
[[Category: Installation]]
[[Category: Ubuntu]]
[[Category: FAQ]]

Compile and Install Ubuntu

2026-03-10T09:47:56Z

Neteler: /* Pre-compiled packages and backports */

<div class="boilerplate metadata" id="attention" style="-moz-border-radius:30px; border: 1px double #35824B; margin-bottom: 1.5em; padding: 1em; background-color: #f9f9f9;">
<p style="font-size: 150%; text-align: left;"><span style="color:#35824B">'''Attention'''</span> </p><span style="color:#333333">'''The following instructions describe the compilation and installation of GRASS GIS and its required dependencies completely from the source on Ubuntu based systems. Please, prefer pre-compiled packages over the manual way described below unless you know ''what'' and ''how'', you want to learn and help testing.'''</span>
</div>

== Quick instructions ==

These instructions should work fine on Ubuntu distributions:

=== Install geospatial dependencies ===

1. Install some dependencies (PROJ, GEOS, GDAL libraries) and the compiler tools <br />
(note: you need Python 3)

<source lang="bash">
# be sure to have an updated system
sudo apt update && sudo apt upgrade -y

# install PROJ
sudo apt install libproj-dev proj-data proj-bin unzip -y
</source>

<source lang="bash">
# optionally, install (selected) datum grid files
sudo apt-get install proj-data

# install GEOS
sudo apt install libgeos-dev -y

# install GDAL
sudo apt install libgdal-dev python3-gdal gdal-bin -y

## install PDAL (optional) - apparently unavailable on Ubuntu
#sudo apt install libpdal-dev pdal -y

# Python3 precedence over Python2 (which is end-of-life since 2019, so it should be the default anyway)
sudo update-alternatives --install /usr/bin/python python /usr/bin/python3 1
</source>

Install compiler stuff and further dependencies.
Note: this is a single command, please copy-paste it entirely into the terminal:

=== Install further compilation dependencies (Ubuntu 24.04) ===

For Ubuntu 24.04, including wxPython packages for GUI support:

<source lang="bash">
# this is a single command, please copy-paste it entirely into the terminal:
sudo apt-get install \
build-essential \
flex make bison gcc libgcc-s1 g++ \
python3 python3-dev \
python3-dateutil libgsl-dev python3-numpy \
zlib1g-dev gettext \
libtiff-dev libpnglite-dev \
sqlite3 libsqlite3-dev \
libboost-thread-dev libboost-program-options-dev \
systemd-resolved \
git \
checkinstall \
cmake ccache \
python3-opengl libwxbase3.2-1t64 libwxgtk3.2-dev \
python3-wxgtk4.0 \
cairo-dock libcairo2-dev \
libpq-dev \
libfreetype-dev \
libfftw3-dev libfftw3-single3 libfftw3-double3 \
libavcodec-dev \
libxmu-dev \
libavformat-dev libswscale-dev \
libglu1-mesa-dev libxmu-dev \
ghostscript
</source>

For NVIZ on Ubuntu, to also have video support (optional):
<source lang="bash">
sudo apt-get install \
ffmpeg libavutil-dev \
libffmpegthumbnailer-dev \
libavcodec-dev \
libxmu-dev \
libavformat-dev libswscale-dev -y
</source>

=== Source code download ===
Now we have all "ingredients" readily installed on our system.

'''Source code download''':

There a two ways of getting the source code: either use a) the weekly snapshot (cannot be updated, or b) the source code from the GitHub repository (you can update your local copy easily in future):

'''a) Download of the weekly source code snapshot (not recommended):'''
<source lang="bash">
# download latest GRASS GIS 8.x stable release source code:
mkdir $HOME/src/
cd $HOME/src/
wget https://grass.osgeo.org/grass84/source/snapshot/grass-8.4.git_src_snapshot_latest.tar.gz

# Unpack source code package and remove tarball archive:
tar xvfz grass-8.4.git_src_snapshot_latest.tar.gz
rm -f grass-8.4.git_src_snapshot_latest.tar.gz

# rename source code directory (yes, with the questionmarks!)
mv grass-8.4.git_src_snapshot_20??_??_?? grass-8.4.latest
cd grass-8.4.latest/
</source>

'''b) Download of the current development version from GitHub (adopt the path below accordingly)'''

Note: to find the current version number (8_x), see https://github.com/OSGeo/grass/branches:

<source lang="bash">
sudo apt-get install git
git clone https://github.com/OSGeo/grass.git grass-8.4.latest.git
cd grass-8.4.latest.git/
git checkout releasebranch_8_4
</source>

=== Compilation ===
Now we can '''compile''' the source code in order to generate the GRASS GIS binaries:

<source lang="bash">
# "configure" source code for local machine (checks for CPU type etc):
MYCFLAGS='-O2 -fPIC -fno-common -fexceptions -std=gnu99 -fstack-protector -m64'
#MYCXXFLAGS=''
MYLDFLAGS='-Wl,--no-undefined -Wl,-z,now'

LDFLAGS="$MYLDFLAGS" CFLAGS="$MYCFLAGS" CXXFLAGS="$MYCXXFLAGS" ./configure \
--with-cxx \
--enable-largefile \
--with-proj --with-proj-share=/usr/share/proj \
--with-gdal=/usr/bin/gdal-config \
--with-python \
--with-geos \
--with-sqlite \
--with-nls \
--with-zstd \
--with-cairo --with-cairo-ldflags=-lfontconfig \
--with-freetype=yes --with-freetype-includes="/usr/include/freetype2/" \
--with-wxwidgets \
--with-fftw \
--with-openmp \
--with-opengl-libs=/usr/include/GL \
--with-postgres=yes --with-postgres-includes="/usr/include/postgresql" \
--without-pdal \
--without-netcdf \
--without-mysql \
--without-odbc \
--without-ffmpeg
</source>

Now compile the source code (this will take some time as it generates binary code from the source code):
<source lang="bash">
# note: the more CPUs you have, the higher the -j number may be set to
# here: build using 4 CPU cores
make -j4
</source>

=== Installation ===

Install resulting GRASS GIS binaries into /usr/local/:
<source lang="bash">
sudo make install
</source>

Start GRASS GIS in the terminal:
<source lang="bash">
grass
</source>

'''Done & enjoy!'''

== Hints ==

* Usually, the installation of compiled code is done by using the <source lang="bash" enclose="none">make</source> tool. Alternatively, this can be done by using the ''checkinstall'' tool (i.e., <source lang="bash" enclose="none">sudo checkinstall</source> instead of <source lang="bash" enclose="none">sudo make install</source>) which eases off removal of packages. If ''checkinstall'' fails to deliver, please note some related bugs: [https://bugs.launchpad.net/ubuntu/+source/checkinstall/+bug/78455 78455] and [https://bugs.launchpad.net/ubuntu/+source/checkinstall/+bug/599163 599163]. Useful information on using ''checkinstall'': [https://help.ubuntu.com/community/CompilingEasyHowTo Compiling things on Ubuntu the Easy Way].

* In multi-core processors, the compilation performance can be boosted by using ''-j'' switches (e.g. <source lang="bash" enclose="none">make -j2</source> or <source lang="bash" enclose="none">make -j3</source> or even <source lang="bash" enclose="none">make -j4</source>) which specify the number of jobs (commands) to run simultaneously.

== Pre-compiled packages and backports ==

'''Pre-compiled packages and backports''' are available from [https://wiki.ubuntu.com/UbuntuGIS UbuntuGIS] via their [https://launchpad.net/~ubuntugis/+archive/ppa/ ppa.launchpad stable] and [https://launchpad.net/~ubuntugis/+archive/ubuntu/ubuntugis-unstable ppa.launchpad unstable] repositories. '''This is by far the simplest and fastest solution. Please prefer it over the manual way of compiling source code yourself as described below.'''

Version overview:
* jammy2 8.4
* noble 8.3
* jammy (22.04): 8.3
* focal (20.04 LTS): 8.2
* bionic (18.04 LTS): 7.8

a) Daily ready-to-install GRASS GIS builds of the stable release branch and master are available from ''ppa:grass/grass-devel'':

<source lang=bash>
sudo add-apt-repository ppa:ubuntugis/ubuntugis-unstable
sudo add-apt-repository ppa:grass/grass-devel
</source>

b) Latest packaged stable version of GRASS GIS is available from ''ppa:grass/grass-stable'':
<source lang=bash>
sudo add-apt-repository ppa:ubuntugis/ppa
sudo add-apt-repository ppa:grass/grass-stable
sudo apt-get update
sudo apt-get install grass
</source>

== Dependencies ==

=== Current stable Ubuntu version ===
First, update the system from the repositories<source lang="bash">
sudo apt-get update && sudo apt-get upgrade
</source>

Then, install ''SQLite'', ''git'' and ''dependencies'' for compiling PROJ, GEOS, GDAL/OGR, GRASS, GDAL-GRASS-PLUGIN (some additional packages may be required in this case); the following action will also install various dependencies (listed in the command line as <source lang="bash" enclose="none">The following extra packages will be installed:</source>...):<br/>

<source lang="bash">
# this is a single command, please copy-paste it entirely into the terminal:
sudo apt-get install \
build-essential \
flex make bison gcc libgcc1 g++ cmake ccache \
python python-dev \
python-opengl \
python-wxversion python-wxtools python-wxgtk3.2 \
python-dateutil libgsl-dev python-numpy \
wx3.2-headers wx-common libwxgtk3.2-dev \
libwxbase3.2-dev \
libncurses5-dev \
zlib1g-dev gettext \
libtiff5-dev libpnglite-dev \
libcairo libcairo-dev \
sqlite3 libsqlite3-dev \
libpq-dev \
libreadline6 libreadline6-dev libfreetype6-dev \
libfftw3-3 libfftw3-dev \
libboost-thread-dev libboost-program-options-dev \
resolvconf \
libjasper-dev \
git \
libav-tools libavutil-dev ffmpeg2theora \
libffmpegthumbnailer-dev \
libavcodec-dev \
libxmu-dev \
libavformat-dev libswscale-dev \
checkinstall \
libglu1-mesa-dev libxmu-dev \
ghostscript
</source>

The following dependencies concern Ubuntu 24.04 LTS:

<source lang="bash">
# this is a single command, please copy-paste it entirely into the terminal:
sudo apt-get install \
build-essential \
flex make bison gcc libgcc-s1 g++ \
python3 python3-dev \
python3-dateutil libgsl-dev python3-numpy \
zlib1g-dev gettext \
libtiff-dev libpnglite-dev \
sqlite3 libsqlite3-dev \
libboost-thread-dev libboost-program-options-dev \
systemd-resolved \
git \
checkinstall \
cmake ccache \
python3-opengl libwxbase3.2-1t64 libwxgtk3.2-dev \
python3-wxgtk4.0 \
cairo-dock libcairo2-dev \
libpq-dev \
libfreetype-dev \
libfftw3-dev libfftw3-single3 libfftw3-double3 \
libavcodec-dev \
libxmu-dev \
libavformat-dev libswscale-dev \
libglu1-mesa-dev libxmu-dev \
ghostscript
</source>

* See the additional packages bellow and in other sections and install them. Note that some of them are [https://github.com/OSGeo/grass/blob/main/REQUIREMENTS.md required], namely PROJ, GEOS and GDAL. If you don't have special requirements, it is usually enough just to install PROJ, GEOS and GDAL from repository (rather then compile them manually).

* for mysql support, <source lang="bash" enclose="none">libmysqlclient-dev</source> is required
<source lang="bash">
sudo apt-get install libmysqlclient-dev
</source>

* for netcdf support, <source lang="bash" enclose="none">netcdf-bin</source> and <source lang="bash" enclose="none">libnetcdf-dev</source> is required
<source lang="bash">
sudo apt-get install netcdf-bin libnetcdf-dev
</source>

* for {{AddonCmd|i.spec.unmix}} Addon support, install LAPACK and BLAS:
<source lang="bash">
sudo apt-get install libblas-dev liblapack-dev
</source>

* create a directory as a simple user where all source code is going to be stored -- in this example, a directory named <source lang="bash" enclose="none">src</source> under <source lang="bash" enclose="none">/usr/local</source> is created <source lang="bash">
sudo mkdir /usr/local/src
</source>

* take over directories ownerships ('''replace''' below the terms ''userid'' and ''groupid'' with a real <source lang="bash" enclose="none">userid</source>): <source lang="bash">
sudo chown userid:groupid /usr/local/src</source>

* similarly, grant <source lang="bash" enclose="none">rwx</source> (read-write-execute) permissions for our ''userid'' and ''groupid'' onto the <source lang="bash" enclose="none">src</source> directory: <source lang="bash">
sudo chmod ug+rwx /usr/local/src</source>

== Using pre-compiled dev Packages for PROJ, GEOS and GDAL ==

=== PROJ ===

Install the <source lang="bash" enclose="none">dev</source> package:

<source lang="bash">
sudo apt-get install libproj-dev proj-data proj-bin
</source>

* In the call to <source lang="bash" enclose="none">./configure</source> for [[#GRASS|GRASS]], replace <source lang="bash" enclose="none">--with-proj-share=/usr/local/share/proj/</source> by <source lang="bash" enclose="none">--with-proj-share=/usr/share/proj/</source>

=== GEOS ===

Install the <source lang="bash" enclose="none">dev</source> package:

<source lang="bash">
# probably you also need to additionally install "libgeos-c1v5"
sudo apt-get install libgeos-dev
</source>

* In the call to <source lang="bash" enclose="none">./configure</source> for [[#GRASS|GRASS]], replace <source lang="bash" enclose="none">--with-geos=/usr/local/bin/geos-config</source> by <source lang="bash" enclose="none">--with-geos=/usr/bin/geos-config</source>

=== GDAL ===

Install the <source lang="bash" enclose="none">dev</source> package (possibly without support for datumgrid):

<source lang="bash">
sudo apt-get install libgdal-dev
</source>

For support of WMS in wxGUI install Python GDAL bindings and GDAL executables:
<source lang="bash">
sudo apt-get install python-gdal gdal-bin
</source>

* Install also the required extra packages (note the message: <source lang="bash" enclose="none">The following extra packages will be installed:</source>)
* Look out for packages to be removed by this operation -- this is most likely caused by incompatible package versions. Fix these problems in advance using commands like the following: <source lang="bash">
sudo apt-get install <package>=<required.version></source>

=== GRASS-GIS ===

[[Compile_and_Install_Ubuntu#GRASS_GIS|Jump to sub-section GRASS-GIS below]]

== Using pre-compiled dev Packages for PROJ, GEOS and GDAL from GIS.lab PPA==

Ivan Mincik has made all required packages available in his [https://launchpad.net/~imincik/+archive/ubuntu/gis PPA]:

<source lang="bash">
sudo add-apt-repository ppa:imincik/gis
sudo apt-get install libproj-dev libgdal-dev python-gdal libgeos-dev
</source>

Now you can either also install GRASS GIS from there or compile it yourself (see [[Compile_and_Install_Ubuntu#GRASS_GIS|Jump to sub-section GRASS-GIS below]])

== Compile from source ==

=== PROJ ===

* within the directory <source lang="bash" enclose="none">/usr/local/src</source> (create it if it does not exist) checkout <source lang="bash" enclose="none">proj</source> from its GitHub repository: <source lang="bash">
https://github.com/OSGeo/PROJ/
</source>

* get [http://download.osgeo.org/proj/proj-datumgrid-1.8.zip '''proj-datumgrid-1.8.zip'''] or related files from [https://trac.osgeo.org/proj proj' trac] and move it under <source lang="bash" enclose="none">proj/nad</source>
<ul><source lang="bash">
wget http://download.osgeo.org/proj/proj-datumgrid-1.8.zip
mv proj-datumgrid-1.8.zip /usr/local/src/proj/nad
cd /usr/local/src/proj/nad
</source>
</ul>

* decompress it <source lang="bash">
unzip proj-datumgrid-1.8.zip
</source>

* go back to the <source lang="bash" enclose="none">proj</source> directory <source lang="bash">
cd /usr/local/src/proj
</source>

* if required, clean previous configuration & compilation <source lang="bash">
make distclean
</source>

* simple configure, compile and install <source lang="bash">
./configure && make && sudo make install
</source>
<ul> or <source lang="bash">
./configure && make -j2 && sudo checkinstall
</source>
</ul>

* ensure that <source lang="bash" enclose="none">/usr/local/lib</source> is added to <source lang="bash" enclose="none">/etc/ld.so.conf</source> and afterwards run <source lang="bash">
sudo ldconfig
</source>

* finally, go back to the parent directory simply by instructing<source lang="bash">
cd ..
</source>

=== GEOS ===

* download '''geos-3.12.2.tar.bz2''' from [https://libgeos.org/ https://libgeos.org/] using <source lang="bash" enclose="none">wget</source> <source lang="bash">
wget https://download.osgeo.org/geos/geos-3.12.2.tar.bz2
</source>

* move to the "source-code" directory and decompress
<ul><source lang="bash">
cd /usr/local/src/
bunzip2 geos-3.12.2.tar.bz2
tar xvf geos-3.12.2.tar
</source>
</ul>

* if required, clean previous configuration & compilation <source lang="bash">
make distclean
</source>

* move to geos directory <source lang="bash">
cd geos-3.12.2
</source>

* simple configure, compile and install <source lang="bash">
./configure && make && sudo make install
</source>
<ul> or <source lang="bash">
./configure && make -j2 && sudo checkinstall
</source>
</ul>

* do not forget to execute <source lang="bash">
sudo ldconfig
</source>

=== GDAL ===

'''Note''', GDAL must be compiled '''without''' GRASS support!

* download the current stable version (see https://github.com/OSGeo/gdal/releases for latest version):
<source lang="bash">
wget https://github.com/OSGeo/gdal/releases/download/v3.9.1/gdal-3.9.1.tar.gz
</source>

Follow the instructions to compile GDAL:
https://gdal.org/development/building_from_source.html

=== GRASS GIS ===

Note the differences between different GRASS GIS version (branches) in download and cofiguration. Note also the changes required if you installed some of the dependencies from packages (rather then compiled them yourself).

To fully understand the build process, read the <code>INSTALL</code> file, which is located in GRASS' source code root directory.

''' Getting GRASS' source code '''

Select from one of the GRASS GIS versions and download the source code:

https://github.com/OSGeo/grass/releases/

''' Configure, Compile and Install'''

Enter the directory with the source code, for example:

<source lang="bash">
cd grass
</source>

* '''GRASS GIS example configuration''' (which can/should be adjusted according to specific needs):
<ul>
<source lang="bash">
CFLAGS="-O2 -Wall" LDFLAGS="-s" ./configure \
--with-nls \
--with-cxx \
--with-proj-share=/usr/local/share/proj/ \
--with-geos=/usr/local/bin/geos-config \
--with-wxwidgets \
--with-cairo \
--with-opengl-libs=/usr/include/GL \
--with-freetype=yes --with-freetype-includes="/usr/include/freetype2/" \
--with-postgres=yes --with-postgres-includes="/usr/include/postgresql" \
--with-sqlite=yes \
--with-mysql=yes --with-mysql-includes="/usr/include/mysql" \
--with-odbc=no \
--with-pdal
</source>
</ul>
<ul>
'''Note''', the above configuration uses the <code>PROJ</code> and <code>GEOS</code> packages compiled from the source. In the case that pre-compiled versions from the repository are required, remove the above corresponding lines to use the "defaults", i.e. (note the backslashe at the end of each line)
<source lang="bash">
--with-proj-share=/usr/share/proj \
--with-geos=/usr/bin/geos-config \
</source>
</ul>

* compile & install <source lang="bash">
make -j2 && sudo make install && sudo ldconfig
</source>

<ul> or <source lang="bash">
make -j2 && sudo checkinstall && sudo ldconfig
</source>
</ul>

For subsequent updates execute (not need for the first time):
<source lang="bash">
svn up
make -j2 && sudo make install && sudo ldconfig
</source>

Sometimes, it is required to clean previous configuration and compilation:
<source lang="bash">
make distclean
svn up
./configure ... # (use the configure command above)
make -j2 && sudo make install && sudo ldconfig
</source>

=== GDAL-GRASS-Plugin ===

See: https://github.com/OSGeo/gdal-grass

* get the plugin from [https://github.com/OSGeo/gdal-grass/releases GitHub]: "gdal-grass-X.Y.Z.tar.gz" using <source lang="bash" enclose="none">wget</source>
<ul><source lang="bash">
# update version number accordingly!
wget https://github.com/OSGeo/gdal-grass/archive/refs/tags/1.0.2.tar.gz -O gdal-grass-1.0.2.tar.gz
tar xvzf gdal-grass-1.0.2.tar.gz
cd gdal-grass-1.0.2
</source></ul>

* create <source lang="bash" enclose="none">/etc/ld.so.conf.d/grass.conf</source> or add in <source lang="bash" enclose="none">/etc/ld.so.conf</source> the GRASS library path:
<ul><source lang="bash">
# GRASS GIS stable library path (adapt as needed)
/usr/local/src/releasebranch_8_4/lib

# GRASS GIS development version library path (adapt as needed)
/usr/local/src/grass_master/lib
</source></ul>

* optionally, clean previous configurations/compilations<source lang="bash">
make distclean</source>

* configure -- point to GRASS installation/binaries
<ul><source lang="bash"> ./configure \
--prefix=/usr/local \
--with-gdal=/usr/local/bin/gdal-config \
--with-grass=/usr/local/grass/ \
--with-autoload="/usr/local/lib64/gdalplugins/" \
--with-ld-shared="g++ -shared"</source></ul>
</ul>

* compile & install using checkinstall<source lang="bash">
make -j2 && sudo checkinstall</source>

= Post compilation/installation control =

* For a recommended quick-check read the [https://grass.osgeo.org/wiki/Compile_and_install_GRASS_and_QGIS_with_GDAL/OGR_Plugin#Troubleshooting Troubleshooting] section at [https://grass.osgeo.org/wiki/Compile_and_install_GDAL-GRASS_plugin Compile_and_install_GDAL-GRASS_plugin]

* in case of errors in future compilation attempts, remember to remove program binaries and files created with the "configuration" from previous compilations with
make distclean

* another common mistake is compiling a module against some GRASS version and then try to run it through another GRASS version. The solution is to recompile the affected module or, in case there are multiple GRASS installations, set up properly LD_LIBRARY_PATH paths.

= Removal of GRASS =

To get rid of a GRASS binaries installation, delete (update version numbers accordingly)
* <source lang="bash" enclose="none">/usr/local/grass</source> (directory, binaries location)
* <source lang="bash" enclose="none">/usr/local/bin/grass</source> (file)
* <source lang="bash" enclose="none">/home/username/.grassrc8</source> (file)

If wanted, delete also the complete source code:
* <source lang="bash" enclose="none">/usr/local/src/grass_release</source> (directory, source code location)

To remove <code>grass</code> (or any other package) which was installed by <source lang="bash" enclose="none">checkinstall</source>, use <source lang="bash" enclose="none">dpkg</source>, e.g.<source lang="bash">
sudo dpkg -r grass # package name defined at installation is important</source>

== See also ==

* Docker: https://grass.osgeo.org/download/docker/
* [[Ubuntu Packaging]]
* [[GRASS in Debian]]

= Archived Notes =

Notes that concern the configuration and compilation of GRASS GIS and its dependencies for older versions of Ubuntu-Linux.

[[Category: Compilation]]
[[Category: Installation]]
[[Category: Ubuntu]]
[[Category: FAQ]]

Compile and Install Ubuntu

2026-03-10T09:45:08Z

Neteler: disable PDAL due to missing package

<div class="boilerplate metadata" id="attention" style="-moz-border-radius:30px; border: 1px double #35824B; margin-bottom: 1.5em; padding: 1em; background-color: #f9f9f9;">
<p style="font-size: 150%; text-align: left;"><span style="color:#35824B">'''Attention'''</span> </p><span style="color:#333333">'''The following instructions describe the compilation and installation of GRASS GIS and its required dependencies completely from the source on Ubuntu based systems. Please, prefer pre-compiled packages over the manual way described below unless you know ''what'' and ''how'', you want to learn and help testing.'''</span>
</div>

== Quick instructions ==

These instructions should work fine on Ubuntu distributions:

=== Install geospatial dependencies ===

1. Install some dependencies (PROJ, GEOS, GDAL libraries) and the compiler tools <br />
(note: you need Python 3)

<source lang="bash">
# be sure to have an updated system
sudo apt update && sudo apt upgrade -y

# install PROJ
sudo apt install libproj-dev proj-data proj-bin unzip -y
</source>

<source lang="bash">
# optionally, install (selected) datum grid files
sudo apt-get install proj-data

# install GEOS
sudo apt install libgeos-dev -y

# install GDAL
sudo apt install libgdal-dev python3-gdal gdal-bin -y

## install PDAL (optional) - apparently unavailable on Ubuntu
#sudo apt install libpdal-dev pdal -y

# Python3 precedence over Python2 (which is end-of-life since 2019, so it should be the default anyway)
sudo update-alternatives --install /usr/bin/python python /usr/bin/python3 1
</source>

Install compiler stuff and further dependencies.
Note: this is a single command, please copy-paste it entirely into the terminal:

=== Install further compilation dependencies (Ubuntu 24.04) ===

For Ubuntu 24.04, including wxPython packages for GUI support:

<source lang="bash">
# this is a single command, please copy-paste it entirely into the terminal:
sudo apt-get install \
build-essential \
flex make bison gcc libgcc-s1 g++ \
python3 python3-dev \
python3-dateutil libgsl-dev python3-numpy \
zlib1g-dev gettext \
libtiff-dev libpnglite-dev \
sqlite3 libsqlite3-dev \
libboost-thread-dev libboost-program-options-dev \
systemd-resolved \
git \
checkinstall \
cmake ccache \
python3-opengl libwxbase3.2-1t64 libwxgtk3.2-dev \
python3-wxgtk4.0 \
cairo-dock libcairo2-dev \
libpq-dev \
libfreetype-dev \
libfftw3-dev libfftw3-single3 libfftw3-double3 \
libavcodec-dev \
libxmu-dev \
libavformat-dev libswscale-dev \
libglu1-mesa-dev libxmu-dev \
ghostscript
</source>

For NVIZ on Ubuntu, to also have video support (optional):
<source lang="bash">
sudo apt-get install \
ffmpeg libavutil-dev \
libffmpegthumbnailer-dev \
libavcodec-dev \
libxmu-dev \
libavformat-dev libswscale-dev -y
</source>

=== Source code download ===
Now we have all "ingredients" readily installed on our system.

'''Source code download''':

There a two ways of getting the source code: either use a) the weekly snapshot (cannot be updated, or b) the source code from the GitHub repository (you can update your local copy easily in future):

'''a) Download of the weekly source code snapshot (not recommended):'''
<source lang="bash">
# download latest GRASS GIS 8.x stable release source code:
mkdir $HOME/src/
cd $HOME/src/
wget https://grass.osgeo.org/grass84/source/snapshot/grass-8.4.git_src_snapshot_latest.tar.gz

# Unpack source code package and remove tarball archive:
tar xvfz grass-8.4.git_src_snapshot_latest.tar.gz
rm -f grass-8.4.git_src_snapshot_latest.tar.gz

# rename source code directory (yes, with the questionmarks!)
mv grass-8.4.git_src_snapshot_20??_??_?? grass-8.4.latest
cd grass-8.4.latest/
</source>

'''b) Download of the current development version from GitHub (adopt the path below accordingly)'''

Note: to find the current version number (8_x), see https://github.com/OSGeo/grass/branches:

<source lang="bash">
sudo apt-get install git
git clone https://github.com/OSGeo/grass.git grass-8.4.latest.git
cd grass-8.4.latest.git/
git checkout releasebranch_8_4
</source>

=== Compilation ===
Now we can '''compile''' the source code in order to generate the GRASS GIS binaries:

<source lang="bash">
# "configure" source code for local machine (checks for CPU type etc):
MYCFLAGS='-O2 -fPIC -fno-common -fexceptions -std=gnu99 -fstack-protector -m64'
#MYCXXFLAGS=''
MYLDFLAGS='-Wl,--no-undefined -Wl,-z,now'

LDFLAGS="$MYLDFLAGS" CFLAGS="$MYCFLAGS" CXXFLAGS="$MYCXXFLAGS" ./configure \
--with-cxx \
--enable-largefile \
--with-proj --with-proj-share=/usr/share/proj \
--with-gdal=/usr/bin/gdal-config \
--with-python \
--with-geos \
--with-sqlite \
--with-nls \
--with-zstd \
--with-cairo --with-cairo-ldflags=-lfontconfig \
--with-freetype=yes --with-freetype-includes="/usr/include/freetype2/" \
--with-wxwidgets \
--with-fftw \
--with-openmp \
--with-opengl-libs=/usr/include/GL \
--with-postgres=yes --with-postgres-includes="/usr/include/postgresql" \
--without-pdal \
--without-netcdf \
--without-mysql \
--without-odbc \
--without-ffmpeg
</source>

Now compile the source code (this will take some time as it generates binary code from the source code):
<source lang="bash">
# note: the more CPUs you have, the higher the -j number may be set to
# here: build using 4 CPU cores
make -j4
</source>

=== Installation ===

Install resulting GRASS GIS binaries into /usr/local/:
<source lang="bash">
sudo make install
</source>

Start GRASS GIS in the terminal:
<source lang="bash">
grass
</source>

'''Done & enjoy!'''

== Hints ==

* Usually, the installation of compiled code is done by using the <source lang="bash" enclose="none">make</source> tool. Alternatively, this can be done by using the ''checkinstall'' tool (i.e., <source lang="bash" enclose="none">sudo checkinstall</source> instead of <source lang="bash" enclose="none">sudo make install</source>) which eases off removal of packages. If ''checkinstall'' fails to deliver, please note some related bugs: [https://bugs.launchpad.net/ubuntu/+source/checkinstall/+bug/78455 78455] and [https://bugs.launchpad.net/ubuntu/+source/checkinstall/+bug/599163 599163]. Useful information on using ''checkinstall'': [https://help.ubuntu.com/community/CompilingEasyHowTo Compiling things on Ubuntu the Easy Way].

* In multi-core processors, the compilation performance can be boosted by using ''-j'' switches (e.g. <source lang="bash" enclose="none">make -j2</source> or <source lang="bash" enclose="none">make -j3</source> or even <source lang="bash" enclose="none">make -j4</source>) which specify the number of jobs (commands) to run simultaneously.

== Pre-compiled packages and backports ==

'''Pre-compiled packages and backports''' are available from [https://wiki.ubuntu.com/UbuntuGIS UbuntuGIS] via their [https://launchpad.net/~ubuntugis/+archive/ppa/ ppa.launchpad stable] and [https://launchpad.net/~ubuntugis/+archive/ubuntu/ubuntugis-unstable ppa.launchpad unstable] repositories. '''This is by far the simplest and fastest solution. Please prefer it over the manual way of compiling source code yourself as described below.'''

Version overview:
* noble 8.3
* jammy (22.04): 8.3
* focal (20.04 LTS): 8.2
* bionic (18.04 LTS): 7.8
* xenial (16.04 LTS): 7.6
* trusty (14.04 LTS): 7.4

a) Daily ready-to-install GRASS GIS builds of the stable release branch and master are available from ''ppa:grass/grass-devel'':

<source lang=bash>
sudo add-apt-repository ppa:ubuntugis/ubuntugis-unstable
sudo add-apt-repository ppa:grass/grass-devel
</source>

b) Latest packaged stable version of GRASS GIS is available from ''ppa:grass/grass-stable'':
<source lang=bash>
sudo add-apt-repository ppa:ubuntugis/ppa
sudo add-apt-repository ppa:grass/grass-stable
sudo apt-get update
sudo apt-get install grass
</source>

== Dependencies ==

=== Current stable Ubuntu version ===
First, update the system from the repositories<source lang="bash">
sudo apt-get update && sudo apt-get upgrade
</source>

Then, install ''SQLite'', ''git'' and ''dependencies'' for compiling PROJ, GEOS, GDAL/OGR, GRASS, GDAL-GRASS-PLUGIN (some additional packages may be required in this case); the following action will also install various dependencies (listed in the command line as <source lang="bash" enclose="none">The following extra packages will be installed:</source>...):<br/>

<source lang="bash">
# this is a single command, please copy-paste it entirely into the terminal:
sudo apt-get install \
build-essential \
flex make bison gcc libgcc1 g++ cmake ccache \
python python-dev \
python-opengl \
python-wxversion python-wxtools python-wxgtk3.2 \
python-dateutil libgsl-dev python-numpy \
wx3.2-headers wx-common libwxgtk3.2-dev \
libwxbase3.2-dev \
libncurses5-dev \
zlib1g-dev gettext \
libtiff5-dev libpnglite-dev \
libcairo libcairo-dev \
sqlite3 libsqlite3-dev \
libpq-dev \
libreadline6 libreadline6-dev libfreetype6-dev \
libfftw3-3 libfftw3-dev \
libboost-thread-dev libboost-program-options-dev \
resolvconf \
libjasper-dev \
git \
libav-tools libavutil-dev ffmpeg2theora \
libffmpegthumbnailer-dev \
libavcodec-dev \
libxmu-dev \
libavformat-dev libswscale-dev \
checkinstall \
libglu1-mesa-dev libxmu-dev \
ghostscript
</source>

The following dependencies concern Ubuntu 24.04 LTS:

<source lang="bash">
# this is a single command, please copy-paste it entirely into the terminal:
sudo apt-get install \
build-essential \
flex make bison gcc libgcc-s1 g++ \
python3 python3-dev \
python3-dateutil libgsl-dev python3-numpy \
zlib1g-dev gettext \
libtiff-dev libpnglite-dev \
sqlite3 libsqlite3-dev \
libboost-thread-dev libboost-program-options-dev \
systemd-resolved \
git \
checkinstall \
cmake ccache \
python3-opengl libwxbase3.2-1t64 libwxgtk3.2-dev \
python3-wxgtk4.0 \
cairo-dock libcairo2-dev \
libpq-dev \
libfreetype-dev \
libfftw3-dev libfftw3-single3 libfftw3-double3 \
libavcodec-dev \
libxmu-dev \
libavformat-dev libswscale-dev \
libglu1-mesa-dev libxmu-dev \
ghostscript
</source>

* See the additional packages bellow and in other sections and install them. Note that some of them are [https://github.com/OSGeo/grass/blob/main/REQUIREMENTS.md required], namely PROJ, GEOS and GDAL. If you don't have special requirements, it is usually enough just to install PROJ, GEOS and GDAL from repository (rather then compile them manually).

* for mysql support, <source lang="bash" enclose="none">libmysqlclient-dev</source> is required
<source lang="bash">
sudo apt-get install libmysqlclient-dev
</source>

* for netcdf support, <source lang="bash" enclose="none">netcdf-bin</source> and <source lang="bash" enclose="none">libnetcdf-dev</source> is required
<source lang="bash">
sudo apt-get install netcdf-bin libnetcdf-dev
</source>

* for {{AddonCmd|i.spec.unmix}} Addon support, install LAPACK and BLAS:
<source lang="bash">
sudo apt-get install libblas-dev liblapack-dev
</source>

* create a directory as a simple user where all source code is going to be stored -- in this example, a directory named <source lang="bash" enclose="none">src</source> under <source lang="bash" enclose="none">/usr/local</source> is created <source lang="bash">
sudo mkdir /usr/local/src
</source>

* take over directories ownerships ('''replace''' below the terms ''userid'' and ''groupid'' with a real <source lang="bash" enclose="none">userid</source>): <source lang="bash">
sudo chown userid:groupid /usr/local/src</source>

* similarly, grant <source lang="bash" enclose="none">rwx</source> (read-write-execute) permissions for our ''userid'' and ''groupid'' onto the <source lang="bash" enclose="none">src</source> directory: <source lang="bash">
sudo chmod ug+rwx /usr/local/src</source>

== Using pre-compiled dev Packages for PROJ, GEOS and GDAL ==

=== PROJ ===

Install the <source lang="bash" enclose="none">dev</source> package:

<source lang="bash">
sudo apt-get install libproj-dev proj-data proj-bin
</source>

* In the call to <source lang="bash" enclose="none">./configure</source> for [[#GRASS|GRASS]], replace <source lang="bash" enclose="none">--with-proj-share=/usr/local/share/proj/</source> by <source lang="bash" enclose="none">--with-proj-share=/usr/share/proj/</source>

=== GEOS ===

Install the <source lang="bash" enclose="none">dev</source> package:

<source lang="bash">
# probably you also need to additionally install "libgeos-c1v5"
sudo apt-get install libgeos-dev
</source>

* In the call to <source lang="bash" enclose="none">./configure</source> for [[#GRASS|GRASS]], replace <source lang="bash" enclose="none">--with-geos=/usr/local/bin/geos-config</source> by <source lang="bash" enclose="none">--with-geos=/usr/bin/geos-config</source>

=== GDAL ===

Install the <source lang="bash" enclose="none">dev</source> package (possibly without support for datumgrid):

<source lang="bash">
sudo apt-get install libgdal-dev
</source>

For support of WMS in wxGUI install Python GDAL bindings and GDAL executables:
<source lang="bash">
sudo apt-get install python-gdal gdal-bin
</source>

* Install also the required extra packages (note the message: <source lang="bash" enclose="none">The following extra packages will be installed:</source>)
* Look out for packages to be removed by this operation -- this is most likely caused by incompatible package versions. Fix these problems in advance using commands like the following: <source lang="bash">
sudo apt-get install <package>=<required.version></source>

=== GRASS-GIS ===

[[Compile_and_Install_Ubuntu#GRASS_GIS|Jump to sub-section GRASS-GIS below]]

== Using pre-compiled dev Packages for PROJ, GEOS and GDAL from GIS.lab PPA==

Ivan Mincik has made all required packages available in his [https://launchpad.net/~imincik/+archive/ubuntu/gis PPA]:

<source lang="bash">
sudo add-apt-repository ppa:imincik/gis
sudo apt-get install libproj-dev libgdal-dev python-gdal libgeos-dev
</source>

Now you can either also install GRASS GIS from there or compile it yourself (see [[Compile_and_Install_Ubuntu#GRASS_GIS|Jump to sub-section GRASS-GIS below]])

== Compile from source ==

=== PROJ ===

* within the directory <source lang="bash" enclose="none">/usr/local/src</source> (create it if it does not exist) checkout <source lang="bash" enclose="none">proj</source> from its GitHub repository: <source lang="bash">
https://github.com/OSGeo/PROJ/
</source>

* get [http://download.osgeo.org/proj/proj-datumgrid-1.8.zip '''proj-datumgrid-1.8.zip'''] or related files from [https://trac.osgeo.org/proj proj' trac] and move it under <source lang="bash" enclose="none">proj/nad</source>
<ul><source lang="bash">
wget http://download.osgeo.org/proj/proj-datumgrid-1.8.zip
mv proj-datumgrid-1.8.zip /usr/local/src/proj/nad
cd /usr/local/src/proj/nad
</source>
</ul>

* decompress it <source lang="bash">
unzip proj-datumgrid-1.8.zip
</source>

* go back to the <source lang="bash" enclose="none">proj</source> directory <source lang="bash">
cd /usr/local/src/proj
</source>

* if required, clean previous configuration & compilation <source lang="bash">
make distclean
</source>

* simple configure, compile and install <source lang="bash">
./configure && make && sudo make install
</source>
<ul> or <source lang="bash">
./configure && make -j2 && sudo checkinstall
</source>
</ul>

* ensure that <source lang="bash" enclose="none">/usr/local/lib</source> is added to <source lang="bash" enclose="none">/etc/ld.so.conf</source> and afterwards run <source lang="bash">
sudo ldconfig
</source>

* finally, go back to the parent directory simply by instructing<source lang="bash">
cd ..
</source>

=== GEOS ===

* download '''geos-3.12.2.tar.bz2''' from [https://libgeos.org/ https://libgeos.org/] using <source lang="bash" enclose="none">wget</source> <source lang="bash">
wget https://download.osgeo.org/geos/geos-3.12.2.tar.bz2
</source>

* move to the "source-code" directory and decompress
<ul><source lang="bash">
cd /usr/local/src/
bunzip2 geos-3.12.2.tar.bz2
tar xvf geos-3.12.2.tar
</source>
</ul>

* if required, clean previous configuration & compilation <source lang="bash">
make distclean
</source>

* move to geos directory <source lang="bash">
cd geos-3.12.2
</source>

* simple configure, compile and install <source lang="bash">
./configure && make && sudo make install
</source>
<ul> or <source lang="bash">
./configure && make -j2 && sudo checkinstall
</source>
</ul>

* do not forget to execute <source lang="bash">
sudo ldconfig
</source>

=== GDAL ===

'''Note''', GDAL must be compiled '''without''' GRASS support!

* download the current stable version (see https://github.com/OSGeo/gdal/releases for latest version):
<source lang="bash">
wget https://github.com/OSGeo/gdal/releases/download/v3.9.1/gdal-3.9.1.tar.gz
</source>

Follow the instructions to compile GDAL:
https://gdal.org/development/building_from_source.html

=== GRASS GIS ===

Note the differences between different GRASS GIS version (branches) in download and cofiguration. Note also the changes required if you installed some of the dependencies from packages (rather then compiled them yourself).

To fully understand the build process, read the <code>INSTALL</code> file, which is located in GRASS' source code root directory.

''' Getting GRASS' source code '''

Select from one of the GRASS GIS versions and download the source code:

https://github.com/OSGeo/grass/releases/

''' Configure, Compile and Install'''

Enter the directory with the source code, for example:

<source lang="bash">
cd grass
</source>

* '''GRASS GIS example configuration''' (which can/should be adjusted according to specific needs):
<ul>
<source lang="bash">
CFLAGS="-O2 -Wall" LDFLAGS="-s" ./configure \
--with-nls \
--with-cxx \
--with-proj-share=/usr/local/share/proj/ \
--with-geos=/usr/local/bin/geos-config \
--with-wxwidgets \
--with-cairo \
--with-opengl-libs=/usr/include/GL \
--with-freetype=yes --with-freetype-includes="/usr/include/freetype2/" \
--with-postgres=yes --with-postgres-includes="/usr/include/postgresql" \
--with-sqlite=yes \
--with-mysql=yes --with-mysql-includes="/usr/include/mysql" \
--with-odbc=no \
--with-pdal
</source>
</ul>
<ul>
'''Note''', the above configuration uses the <code>PROJ</code> and <code>GEOS</code> packages compiled from the source. In the case that pre-compiled versions from the repository are required, remove the above corresponding lines to use the "defaults", i.e. (note the backslashe at the end of each line)
<source lang="bash">
--with-proj-share=/usr/share/proj \
--with-geos=/usr/bin/geos-config \
</source>
</ul>

* compile & install <source lang="bash">
make -j2 && sudo make install && sudo ldconfig
</source>

<ul> or <source lang="bash">
make -j2 && sudo checkinstall && sudo ldconfig
</source>
</ul>

For subsequent updates execute (not need for the first time):
<source lang="bash">
svn up
make -j2 && sudo make install && sudo ldconfig
</source>

Sometimes, it is required to clean previous configuration and compilation:
<source lang="bash">
make distclean
svn up
./configure ... # (use the configure command above)
make -j2 && sudo make install && sudo ldconfig
</source>

=== GDAL-GRASS-Plugin ===

See: https://github.com/OSGeo/gdal-grass

* get the plugin from [https://github.com/OSGeo/gdal-grass/releases GitHub]: "gdal-grass-X.Y.Z.tar.gz" using <source lang="bash" enclose="none">wget</source>
<ul><source lang="bash">
# update version number accordingly!
wget https://github.com/OSGeo/gdal-grass/archive/refs/tags/1.0.2.tar.gz -O gdal-grass-1.0.2.tar.gz
tar xvzf gdal-grass-1.0.2.tar.gz
cd gdal-grass-1.0.2
</source></ul>

* create <source lang="bash" enclose="none">/etc/ld.so.conf.d/grass.conf</source> or add in <source lang="bash" enclose="none">/etc/ld.so.conf</source> the GRASS library path:
<ul><source lang="bash">
# GRASS GIS stable library path (adapt as needed)
/usr/local/src/releasebranch_8_4/lib

# GRASS GIS development version library path (adapt as needed)
/usr/local/src/grass_master/lib
</source></ul>

* optionally, clean previous configurations/compilations<source lang="bash">
make distclean</source>

* configure -- point to GRASS installation/binaries
<ul><source lang="bash"> ./configure \
--prefix=/usr/local \
--with-gdal=/usr/local/bin/gdal-config \
--with-grass=/usr/local/grass/ \
--with-autoload="/usr/local/lib64/gdalplugins/" \
--with-ld-shared="g++ -shared"</source></ul>
</ul>

* compile & install using checkinstall<source lang="bash">
make -j2 && sudo checkinstall</source>

= Post compilation/installation control =

* For a recommended quick-check read the [https://grass.osgeo.org/wiki/Compile_and_install_GRASS_and_QGIS_with_GDAL/OGR_Plugin#Troubleshooting Troubleshooting] section at [https://grass.osgeo.org/wiki/Compile_and_install_GDAL-GRASS_plugin Compile_and_install_GDAL-GRASS_plugin]

* in case of errors in future compilation attempts, remember to remove program binaries and files created with the "configuration" from previous compilations with
make distclean

* another common mistake is compiling a module against some GRASS version and then try to run it through another GRASS version. The solution is to recompile the affected module or, in case there are multiple GRASS installations, set up properly LD_LIBRARY_PATH paths.

= Removal of GRASS =

To get rid of a GRASS binaries installation, delete (update version numbers accordingly)
* <source lang="bash" enclose="none">/usr/local/grass</source> (directory, binaries location)
* <source lang="bash" enclose="none">/usr/local/bin/grass</source> (file)
* <source lang="bash" enclose="none">/home/username/.grassrc8</source> (file)

If wanted, delete also the complete source code:
* <source lang="bash" enclose="none">/usr/local/src/grass_release</source> (directory, source code location)

To remove <code>grass</code> (or any other package) which was installed by <source lang="bash" enclose="none">checkinstall</source>, use <source lang="bash" enclose="none">dpkg</source>, e.g.<source lang="bash">
sudo dpkg -r grass # package name defined at installation is important</source>

== See also ==

* Docker: https://grass.osgeo.org/download/docker/
* [[Ubuntu Packaging]]
* [[GRASS in Debian]]

= Archived Notes =

Notes that concern the configuration and compilation of GRASS GIS and its dependencies for older versions of Ubuntu-Linux.

[[Category: Compilation]]
[[Category: Installation]]
[[Category: Ubuntu]]
[[Category: FAQ]]

Compile and Install Ubuntu

2026-03-10T09:43:46Z

Neteler: Update geospatial dependencies

<div class="boilerplate metadata" id="attention" style="-moz-border-radius:30px; border: 1px double #35824B; margin-bottom: 1.5em; padding: 1em; background-color: #f9f9f9;">
<p style="font-size: 150%; text-align: left;"><span style="color:#35824B">'''Attention'''</span> </p><span style="color:#333333">'''The following instructions describe the compilation and installation of GRASS GIS and its required dependencies completely from the source on Ubuntu based systems. Please, prefer pre-compiled packages over the manual way described below unless you know ''what'' and ''how'', you want to learn and help testing.'''</span>
</div>

== Quick instructions ==

These instructions should work fine on Ubuntu distributions:

=== Install geospatial dependencies ===

1. Install some dependencies (PROJ, GEOS, GDAL libraries) and the compiler tools <br />
(note: you need Python 3)

<source lang="bash">
# be sure to have an updated system
sudo apt update && sudo apt upgrade -y

# install PROJ
sudo apt install libproj-dev proj-data proj-bin unzip -y
</source>

<source lang="bash">
# optionally, install (selected) datum grid files
sudo apt-get install proj-data

# install GEOS
sudo apt install libgeos-dev -y

# install GDAL
sudo apt install libgdal-dev python3-gdal gdal-bin -y

## install PDAL (optional) - apparently unavailable on Ubuntu
#sudo apt install libpdal-dev pdal -y

# Python3 precedence over Python2 (which is end-of-life since 2019, so it should be the default anyway)
sudo update-alternatives --install /usr/bin/python python /usr/bin/python3 1
</source>

Install compiler stuff and further dependencies.
Note: this is a single command, please copy-paste it entirely into the terminal:

=== Install further compilation dependencies (Ubuntu 24.04) ===

For Ubuntu 24.04, including wxPython packages for GUI support:

<source lang="bash">
# this is a single command, please copy-paste it entirely into the terminal:
sudo apt-get install \
build-essential \
flex make bison gcc libgcc-s1 g++ \
python3 python3-dev \
python3-dateutil libgsl-dev python3-numpy \
zlib1g-dev gettext \
libtiff-dev libpnglite-dev \
sqlite3 libsqlite3-dev \
libboost-thread-dev libboost-program-options-dev \
systemd-resolved \
git \
checkinstall \
cmake ccache \
python3-opengl libwxbase3.2-1t64 libwxgtk3.2-dev \
python3-wxgtk4.0 \
cairo-dock libcairo2-dev \
libpq-dev \
libfreetype-dev \
libfftw3-dev libfftw3-single3 libfftw3-double3 \
libavcodec-dev \
libxmu-dev \
libavformat-dev libswscale-dev \
libglu1-mesa-dev libxmu-dev \
ghostscript
</source>

For NVIZ on Ubuntu, to also have video support (optional):
<source lang="bash">
sudo apt-get install \
ffmpeg libavutil-dev \
libffmpegthumbnailer-dev \
libavcodec-dev \
libxmu-dev \
libavformat-dev libswscale-dev -y
</source>

=== Source code download ===
Now we have all "ingredients" readily installed on our system.

'''Source code download''':

There a two ways of getting the source code: either use a) the weekly snapshot (cannot be updated, or b) the source code from the GitHub repository (you can update your local copy easily in future):

'''a) Download of the weekly source code snapshot (not recommended):'''
<source lang="bash">
# download latest GRASS GIS 8.x stable release source code:
mkdir $HOME/src/
cd $HOME/src/
wget https://grass.osgeo.org/grass84/source/snapshot/grass-8.4.git_src_snapshot_latest.tar.gz

# Unpack source code package and remove tarball archive:
tar xvfz grass-8.4.git_src_snapshot_latest.tar.gz
rm -f grass-8.4.git_src_snapshot_latest.tar.gz

# rename source code directory (yes, with the questionmarks!)
mv grass-8.4.git_src_snapshot_20??_??_?? grass-8.4.latest
cd grass-8.4.latest/
</source>

'''b) Download of the current development version from GitHub (adopt the path below accordingly)'''

Note: to find the current version number (8_x), see https://github.com/OSGeo/grass/branches:

<source lang="bash">
sudo apt-get install git
git clone https://github.com/OSGeo/grass.git grass-8.4.latest.git
cd grass-8.4.latest.git/
git checkout releasebranch_8_4
</source>

=== Compilation ===
Now we can '''compile''' the source code in order to generate the GRASS GIS binaries:

<source lang="bash">
# "configure" source code for local machine (checks for CPU type etc):
MYCFLAGS='-O2 -fPIC -fno-common -fexceptions -std=gnu99 -fstack-protector -m64'
#MYCXXFLAGS=''
MYLDFLAGS='-Wl,--no-undefined -Wl,-z,now'

LDFLAGS="$MYLDFLAGS" CFLAGS="$MYCFLAGS" CXXFLAGS="$MYCXXFLAGS" ./configure \
--with-cxx \
--enable-largefile \
--with-proj --with-proj-share=/usr/share/proj \
--with-gdal=/usr/bin/gdal-config \
--with-python \
--with-geos \
--with-sqlite \
--with-nls \
--with-zstd \
--with-pdal \
--with-cairo --with-cairo-ldflags=-lfontconfig \
--with-freetype=yes --with-freetype-includes="/usr/include/freetype2/" \
--with-wxwidgets \
--with-fftw \
--with-openmp \
--with-opengl-libs=/usr/include/GL \
--with-postgres=yes --with-postgres-includes="/usr/include/postgresql" \
--without-netcdf \
--without-mysql \
--without-odbc \
--without-ffmpeg
</source>

Now compile the source code (this will take some time as it generates binary code from the source code):
<source lang="bash">
# note: the more CPUs you have, the higher the -j number may be set to
# here: build using 4 CPU cores
make -j4
</source>

=== Installation ===

Install resulting GRASS GIS binaries into /usr/local/:
<source lang="bash">
sudo make install
</source>

Start GRASS GIS in the terminal:
<source lang="bash">
grass
</source>

'''Done & enjoy!'''

== Hints ==

* Usually, the installation of compiled code is done by using the <source lang="bash" enclose="none">make</source> tool. Alternatively, this can be done by using the ''checkinstall'' tool (i.e., <source lang="bash" enclose="none">sudo checkinstall</source> instead of <source lang="bash" enclose="none">sudo make install</source>) which eases off removal of packages. If ''checkinstall'' fails to deliver, please note some related bugs: [https://bugs.launchpad.net/ubuntu/+source/checkinstall/+bug/78455 78455] and [https://bugs.launchpad.net/ubuntu/+source/checkinstall/+bug/599163 599163]. Useful information on using ''checkinstall'': [https://help.ubuntu.com/community/CompilingEasyHowTo Compiling things on Ubuntu the Easy Way].

* In multi-core processors, the compilation performance can be boosted by using ''-j'' switches (e.g. <source lang="bash" enclose="none">make -j2</source> or <source lang="bash" enclose="none">make -j3</source> or even <source lang="bash" enclose="none">make -j4</source>) which specify the number of jobs (commands) to run simultaneously.

== Pre-compiled packages and backports ==

'''Pre-compiled packages and backports''' are available from [https://wiki.ubuntu.com/UbuntuGIS UbuntuGIS] via their [https://launchpad.net/~ubuntugis/+archive/ppa/ ppa.launchpad stable] and [https://launchpad.net/~ubuntugis/+archive/ubuntu/ubuntugis-unstable ppa.launchpad unstable] repositories. '''This is by far the simplest and fastest solution. Please prefer it over the manual way of compiling source code yourself as described below.'''

Version overview:
* noble 8.3
* jammy (22.04): 8.3
* focal (20.04 LTS): 8.2
* bionic (18.04 LTS): 7.8
* xenial (16.04 LTS): 7.6
* trusty (14.04 LTS): 7.4

a) Daily ready-to-install GRASS GIS builds of the stable release branch and master are available from ''ppa:grass/grass-devel'':

<source lang=bash>
sudo add-apt-repository ppa:ubuntugis/ubuntugis-unstable
sudo add-apt-repository ppa:grass/grass-devel
</source>

b) Latest packaged stable version of GRASS GIS is available from ''ppa:grass/grass-stable'':
<source lang=bash>
sudo add-apt-repository ppa:ubuntugis/ppa
sudo add-apt-repository ppa:grass/grass-stable
sudo apt-get update
sudo apt-get install grass
</source>

== Dependencies ==

=== Current stable Ubuntu version ===
First, update the system from the repositories<source lang="bash">
sudo apt-get update && sudo apt-get upgrade
</source>

Then, install ''SQLite'', ''git'' and ''dependencies'' for compiling PROJ, GEOS, GDAL/OGR, GRASS, GDAL-GRASS-PLUGIN (some additional packages may be required in this case); the following action will also install various dependencies (listed in the command line as <source lang="bash" enclose="none">The following extra packages will be installed:</source>...):<br/>

<source lang="bash">
# this is a single command, please copy-paste it entirely into the terminal:
sudo apt-get install \
build-essential \
flex make bison gcc libgcc1 g++ cmake ccache \
python python-dev \
python-opengl \
python-wxversion python-wxtools python-wxgtk3.2 \
python-dateutil libgsl-dev python-numpy \
wx3.2-headers wx-common libwxgtk3.2-dev \
libwxbase3.2-dev \
libncurses5-dev \
zlib1g-dev gettext \
libtiff5-dev libpnglite-dev \
libcairo libcairo-dev \
sqlite3 libsqlite3-dev \
libpq-dev \
libreadline6 libreadline6-dev libfreetype6-dev \
libfftw3-3 libfftw3-dev \
libboost-thread-dev libboost-program-options-dev \
resolvconf \
libjasper-dev \
git \
libav-tools libavutil-dev ffmpeg2theora \
libffmpegthumbnailer-dev \
libavcodec-dev \
libxmu-dev \
libavformat-dev libswscale-dev \
checkinstall \
libglu1-mesa-dev libxmu-dev \
ghostscript
</source>

The following dependencies concern Ubuntu 24.04 LTS:

<source lang="bash">
# this is a single command, please copy-paste it entirely into the terminal:
sudo apt-get install \
build-essential \
flex make bison gcc libgcc-s1 g++ \
python3 python3-dev \
python3-dateutil libgsl-dev python3-numpy \
zlib1g-dev gettext \
libtiff-dev libpnglite-dev \
sqlite3 libsqlite3-dev \
libboost-thread-dev libboost-program-options-dev \
systemd-resolved \
git \
checkinstall \
cmake ccache \
python3-opengl libwxbase3.2-1t64 libwxgtk3.2-dev \
python3-wxgtk4.0 \
cairo-dock libcairo2-dev \
libpq-dev \
libfreetype-dev \
libfftw3-dev libfftw3-single3 libfftw3-double3 \
libavcodec-dev \
libxmu-dev \
libavformat-dev libswscale-dev \
libglu1-mesa-dev libxmu-dev \
ghostscript
</source>

* See the additional packages bellow and in other sections and install them. Note that some of them are [https://github.com/OSGeo/grass/blob/main/REQUIREMENTS.md required], namely PROJ, GEOS and GDAL. If you don't have special requirements, it is usually enough just to install PROJ, GEOS and GDAL from repository (rather then compile them manually).

* for mysql support, <source lang="bash" enclose="none">libmysqlclient-dev</source> is required
<source lang="bash">
sudo apt-get install libmysqlclient-dev
</source>

* for netcdf support, <source lang="bash" enclose="none">netcdf-bin</source> and <source lang="bash" enclose="none">libnetcdf-dev</source> is required
<source lang="bash">
sudo apt-get install netcdf-bin libnetcdf-dev
</source>

* for {{AddonCmd|i.spec.unmix}} Addon support, install LAPACK and BLAS:
<source lang="bash">
sudo apt-get install libblas-dev liblapack-dev
</source>

* create a directory as a simple user where all source code is going to be stored -- in this example, a directory named <source lang="bash" enclose="none">src</source> under <source lang="bash" enclose="none">/usr/local</source> is created <source lang="bash">
sudo mkdir /usr/local/src
</source>

* take over directories ownerships ('''replace''' below the terms ''userid'' and ''groupid'' with a real <source lang="bash" enclose="none">userid</source>): <source lang="bash">
sudo chown userid:groupid /usr/local/src</source>

* similarly, grant <source lang="bash" enclose="none">rwx</source> (read-write-execute) permissions for our ''userid'' and ''groupid'' onto the <source lang="bash" enclose="none">src</source> directory: <source lang="bash">
sudo chmod ug+rwx /usr/local/src</source>

== Using pre-compiled dev Packages for PROJ, GEOS and GDAL ==

=== PROJ ===

Install the <source lang="bash" enclose="none">dev</source> package:

<source lang="bash">
sudo apt-get install libproj-dev proj-data proj-bin
</source>

* In the call to <source lang="bash" enclose="none">./configure</source> for [[#GRASS|GRASS]], replace <source lang="bash" enclose="none">--with-proj-share=/usr/local/share/proj/</source> by <source lang="bash" enclose="none">--with-proj-share=/usr/share/proj/</source>

=== GEOS ===

Install the <source lang="bash" enclose="none">dev</source> package:

<source lang="bash">
# probably you also need to additionally install "libgeos-c1v5"
sudo apt-get install libgeos-dev
</source>

* In the call to <source lang="bash" enclose="none">./configure</source> for [[#GRASS|GRASS]], replace <source lang="bash" enclose="none">--with-geos=/usr/local/bin/geos-config</source> by <source lang="bash" enclose="none">--with-geos=/usr/bin/geos-config</source>

=== GDAL ===

Install the <source lang="bash" enclose="none">dev</source> package (possibly without support for datumgrid):

<source lang="bash">
sudo apt-get install libgdal-dev
</source>

For support of WMS in wxGUI install Python GDAL bindings and GDAL executables:
<source lang="bash">
sudo apt-get install python-gdal gdal-bin
</source>

* Install also the required extra packages (note the message: <source lang="bash" enclose="none">The following extra packages will be installed:</source>)
* Look out for packages to be removed by this operation -- this is most likely caused by incompatible package versions. Fix these problems in advance using commands like the following: <source lang="bash">
sudo apt-get install <package>=<required.version></source>

=== GRASS-GIS ===

[[Compile_and_Install_Ubuntu#GRASS_GIS|Jump to sub-section GRASS-GIS below]]

== Using pre-compiled dev Packages for PROJ, GEOS and GDAL from GIS.lab PPA==

Ivan Mincik has made all required packages available in his [https://launchpad.net/~imincik/+archive/ubuntu/gis PPA]:

<source lang="bash">
sudo add-apt-repository ppa:imincik/gis
sudo apt-get install libproj-dev libgdal-dev python-gdal libgeos-dev
</source>

Now you can either also install GRASS GIS from there or compile it yourself (see [[Compile_and_Install_Ubuntu#GRASS_GIS|Jump to sub-section GRASS-GIS below]])

== Compile from source ==

=== PROJ ===

* within the directory <source lang="bash" enclose="none">/usr/local/src</source> (create it if it does not exist) checkout <source lang="bash" enclose="none">proj</source> from its GitHub repository: <source lang="bash">
https://github.com/OSGeo/PROJ/
</source>

* get [http://download.osgeo.org/proj/proj-datumgrid-1.8.zip '''proj-datumgrid-1.8.zip'''] or related files from [https://trac.osgeo.org/proj proj' trac] and move it under <source lang="bash" enclose="none">proj/nad</source>
<ul><source lang="bash">
wget http://download.osgeo.org/proj/proj-datumgrid-1.8.zip
mv proj-datumgrid-1.8.zip /usr/local/src/proj/nad
cd /usr/local/src/proj/nad
</source>
</ul>

* decompress it <source lang="bash">
unzip proj-datumgrid-1.8.zip
</source>

* go back to the <source lang="bash" enclose="none">proj</source> directory <source lang="bash">
cd /usr/local/src/proj
</source>

* if required, clean previous configuration & compilation <source lang="bash">
make distclean
</source>

* simple configure, compile and install <source lang="bash">
./configure && make && sudo make install
</source>
<ul> or <source lang="bash">
./configure && make -j2 && sudo checkinstall
</source>
</ul>

* ensure that <source lang="bash" enclose="none">/usr/local/lib</source> is added to <source lang="bash" enclose="none">/etc/ld.so.conf</source> and afterwards run <source lang="bash">
sudo ldconfig
</source>

* finally, go back to the parent directory simply by instructing<source lang="bash">
cd ..
</source>

=== GEOS ===

* download '''geos-3.12.2.tar.bz2''' from [https://libgeos.org/ https://libgeos.org/] using <source lang="bash" enclose="none">wget</source> <source lang="bash">
wget https://download.osgeo.org/geos/geos-3.12.2.tar.bz2
</source>

* move to the "source-code" directory and decompress
<ul><source lang="bash">
cd /usr/local/src/
bunzip2 geos-3.12.2.tar.bz2
tar xvf geos-3.12.2.tar
</source>
</ul>

* if required, clean previous configuration & compilation <source lang="bash">
make distclean
</source>

* move to geos directory <source lang="bash">
cd geos-3.12.2
</source>

* simple configure, compile and install <source lang="bash">
./configure && make && sudo make install
</source>
<ul> or <source lang="bash">
./configure && make -j2 && sudo checkinstall
</source>
</ul>

* do not forget to execute <source lang="bash">
sudo ldconfig
</source>

=== GDAL ===

'''Note''', GDAL must be compiled '''without''' GRASS support!

* download the current stable version (see https://github.com/OSGeo/gdal/releases for latest version):
<source lang="bash">
wget https://github.com/OSGeo/gdal/releases/download/v3.9.1/gdal-3.9.1.tar.gz
</source>

Follow the instructions to compile GDAL:
https://gdal.org/development/building_from_source.html

=== GRASS GIS ===

Note the differences between different GRASS GIS version (branches) in download and cofiguration. Note also the changes required if you installed some of the dependencies from packages (rather then compiled them yourself).

To fully understand the build process, read the <code>INSTALL</code> file, which is located in GRASS' source code root directory.

''' Getting GRASS' source code '''

Select from one of the GRASS GIS versions and download the source code:

https://github.com/OSGeo/grass/releases/

''' Configure, Compile and Install'''

Enter the directory with the source code, for example:

<source lang="bash">
cd grass
</source>

* '''GRASS GIS example configuration''' (which can/should be adjusted according to specific needs):
<ul>
<source lang="bash">
CFLAGS="-O2 -Wall" LDFLAGS="-s" ./configure \
--with-nls \
--with-cxx \
--with-proj-share=/usr/local/share/proj/ \
--with-geos=/usr/local/bin/geos-config \
--with-wxwidgets \
--with-cairo \
--with-opengl-libs=/usr/include/GL \
--with-freetype=yes --with-freetype-includes="/usr/include/freetype2/" \
--with-postgres=yes --with-postgres-includes="/usr/include/postgresql" \
--with-sqlite=yes \
--with-mysql=yes --with-mysql-includes="/usr/include/mysql" \
--with-odbc=no \
--with-pdal
</source>
</ul>
<ul>
'''Note''', the above configuration uses the <code>PROJ</code> and <code>GEOS</code> packages compiled from the source. In the case that pre-compiled versions from the repository are required, remove the above corresponding lines to use the "defaults", i.e. (note the backslashe at the end of each line)
<source lang="bash">
--with-proj-share=/usr/share/proj \
--with-geos=/usr/bin/geos-config \
</source>
</ul>

* compile & install <source lang="bash">
make -j2 && sudo make install && sudo ldconfig
</source>

<ul> or <source lang="bash">
make -j2 && sudo checkinstall && sudo ldconfig
</source>
</ul>

For subsequent updates execute (not need for the first time):
<source lang="bash">
svn up
make -j2 && sudo make install && sudo ldconfig
</source>

Sometimes, it is required to clean previous configuration and compilation:
<source lang="bash">
make distclean
svn up
./configure ... # (use the configure command above)
make -j2 && sudo make install && sudo ldconfig
</source>

=== GDAL-GRASS-Plugin ===

See: https://github.com/OSGeo/gdal-grass

* get the plugin from [https://github.com/OSGeo/gdal-grass/releases GitHub]: "gdal-grass-X.Y.Z.tar.gz" using <source lang="bash" enclose="none">wget</source>
<ul><source lang="bash">
# update version number accordingly!
wget https://github.com/OSGeo/gdal-grass/archive/refs/tags/1.0.2.tar.gz -O gdal-grass-1.0.2.tar.gz
tar xvzf gdal-grass-1.0.2.tar.gz
cd gdal-grass-1.0.2
</source></ul>

* create <source lang="bash" enclose="none">/etc/ld.so.conf.d/grass.conf</source> or add in <source lang="bash" enclose="none">/etc/ld.so.conf</source> the GRASS library path:
<ul><source lang="bash">
# GRASS GIS stable library path (adapt as needed)
/usr/local/src/releasebranch_8_4/lib

# GRASS GIS development version library path (adapt as needed)
/usr/local/src/grass_master/lib
</source></ul>

* optionally, clean previous configurations/compilations<source lang="bash">
make distclean</source>

* configure -- point to GRASS installation/binaries
<ul><source lang="bash"> ./configure \
--prefix=/usr/local \
--with-gdal=/usr/local/bin/gdal-config \
--with-grass=/usr/local/grass/ \
--with-autoload="/usr/local/lib64/gdalplugins/" \
--with-ld-shared="g++ -shared"</source></ul>
</ul>

* compile & install using checkinstall<source lang="bash">
make -j2 && sudo checkinstall</source>

= Post compilation/installation control =

* For a recommended quick-check read the [https://grass.osgeo.org/wiki/Compile_and_install_GRASS_and_QGIS_with_GDAL/OGR_Plugin#Troubleshooting Troubleshooting] section at [https://grass.osgeo.org/wiki/Compile_and_install_GDAL-GRASS_plugin Compile_and_install_GDAL-GRASS_plugin]

* in case of errors in future compilation attempts, remember to remove program binaries and files created with the "configuration" from previous compilations with
make distclean

* another common mistake is compiling a module against some GRASS version and then try to run it through another GRASS version. The solution is to recompile the affected module or, in case there are multiple GRASS installations, set up properly LD_LIBRARY_PATH paths.

= Removal of GRASS =

To get rid of a GRASS binaries installation, delete (update version numbers accordingly)
* <source lang="bash" enclose="none">/usr/local/grass</source> (directory, binaries location)
* <source lang="bash" enclose="none">/usr/local/bin/grass</source> (file)
* <source lang="bash" enclose="none">/home/username/.grassrc8</source> (file)

If wanted, delete also the complete source code:
* <source lang="bash" enclose="none">/usr/local/src/grass_release</source> (directory, source code location)

To remove <code>grass</code> (or any other package) which was installed by <source lang="bash" enclose="none">checkinstall</source>, use <source lang="bash" enclose="none">dpkg</source>, e.g.<source lang="bash">
sudo dpkg -r grass # package name defined at installation is important</source>

== See also ==

* Docker: https://grass.osgeo.org/download/docker/
* [[Ubuntu Packaging]]
* [[GRASS in Debian]]

= Archived Notes =

Notes that concern the configuration and compilation of GRASS GIS and its dependencies for older versions of Ubuntu-Linux.

[[Category: Compilation]]
[[Category: Installation]]
[[Category: Ubuntu]]
[[Category: FAQ]]

Compile and Install Ubuntu

2026-03-10T09:39:24Z

Neteler: Update compilation dependencies Ubuntu 24.04

<div class="boilerplate metadata" id="attention" style="-moz-border-radius:30px; border: 1px double #35824B; margin-bottom: 1.5em; padding: 1em; background-color: #f9f9f9;">
<p style="font-size: 150%; text-align: left;"><span style="color:#35824B">'''Attention'''</span> </p><span style="color:#333333">'''The following instructions describe the compilation and installation of GRASS GIS and its required dependencies completely from the source on Ubuntu based systems. Please, prefer pre-compiled packages over the manual way described below unless you know ''what'' and ''how'', you want to learn and help testing.'''</span>
</div>

== Quick instructions ==

These instructions should work fine on Ubuntu distributions:

=== Install geospatial dependencies ===

1. Install some dependencies (PROJ, GEOS, GDAL libraries) and the compiler tools <br />
(note: you need Python 3)

<source lang="bash">
# be sure to have an updated system
sudo apt update && sudo apt upgrade -y

# install PROJ
sudo apt install libproj-dev proj-data proj-bin unzip -y
</source>

<source lang="bash">
# optionally, install (selected) datum grid files
sudo apt-get install proj-data

# install GEOS
sudo apt install libgeos-dev -y

# install GDAL
sudo apt install libgdal-dev python3-gdal gdal-bin -y

# install PDAL (optional)
sudo apt install libpdal-dev pdal -y

# Python3 precedence over Python2 (which is end-of-life since 2019, so it should be the default anyway)
sudo update-alternatives --install /usr/bin/python python /usr/bin/python3 1
</source>

Install compiler stuff and further dependencies.
Note: this is a single command, please copy-paste it entirely into the terminal:

=== Install further compilation dependencies (Ubuntu 24.04) ===

For Ubuntu 24.04, including wxPython packages for GUI support:

<source lang="bash">
# this is a single command, please copy-paste it entirely into the terminal:
sudo apt-get install \
build-essential \
flex make bison gcc libgcc-s1 g++ \
python3 python3-dev \
python3-dateutil libgsl-dev python3-numpy \
zlib1g-dev gettext \
libtiff-dev libpnglite-dev \
sqlite3 libsqlite3-dev \
libboost-thread-dev libboost-program-options-dev \
systemd-resolved \
git \
checkinstall \
cmake ccache \
python3-opengl libwxbase3.2-1t64 libwxgtk3.2-dev \
python3-wxgtk4.0 \
cairo-dock libcairo2-dev \
libpq-dev \
libfreetype-dev \
libfftw3-dev libfftw3-single3 libfftw3-double3 \
libavcodec-dev \
libxmu-dev \
libavformat-dev libswscale-dev \
libglu1-mesa-dev libxmu-dev \
ghostscript
</source>

For NVIZ on Ubuntu, to also have video support (optional):
<source lang="bash">
sudo apt-get install \
ffmpeg libavutil-dev \
libffmpegthumbnailer-dev \
libavcodec-dev \
libxmu-dev \
libavformat-dev libswscale-dev -y
</source>

=== Source code download ===
Now we have all "ingredients" readily installed on our system.

'''Source code download''':

There a two ways of getting the source code: either use a) the weekly snapshot (cannot be updated, or b) the source code from the GitHub repository (you can update your local copy easily in future):

'''a) Download of the weekly source code snapshot (not recommended):'''
<source lang="bash">
# download latest GRASS GIS 8.x stable release source code:
mkdir $HOME/src/
cd $HOME/src/
wget https://grass.osgeo.org/grass84/source/snapshot/grass-8.4.git_src_snapshot_latest.tar.gz

# Unpack source code package and remove tarball archive:
tar xvfz grass-8.4.git_src_snapshot_latest.tar.gz
rm -f grass-8.4.git_src_snapshot_latest.tar.gz

# rename source code directory (yes, with the questionmarks!)
mv grass-8.4.git_src_snapshot_20??_??_?? grass-8.4.latest
cd grass-8.4.latest/
</source>

'''b) Download of the current development version from GitHub (adopt the path below accordingly)'''

Note: to find the current version number (8_x), see https://github.com/OSGeo/grass/branches:

<source lang="bash">
sudo apt-get install git
git clone https://github.com/OSGeo/grass.git grass-8.4.latest.git
cd grass-8.4.latest.git/
git checkout releasebranch_8_4
</source>

=== Compilation ===
Now we can '''compile''' the source code in order to generate the GRASS GIS binaries:

<source lang="bash">
# "configure" source code for local machine (checks for CPU type etc):
MYCFLAGS='-O2 -fPIC -fno-common -fexceptions -std=gnu99 -fstack-protector -m64'
#MYCXXFLAGS=''
MYLDFLAGS='-Wl,--no-undefined -Wl,-z,now'

LDFLAGS="$MYLDFLAGS" CFLAGS="$MYCFLAGS" CXXFLAGS="$MYCXXFLAGS" ./configure \
--with-cxx \
--enable-largefile \
--with-proj --with-proj-share=/usr/share/proj \
--with-gdal=/usr/bin/gdal-config \
--with-python \
--with-geos \
--with-sqlite \
--with-nls \
--with-zstd \
--with-pdal \
--with-cairo --with-cairo-ldflags=-lfontconfig \
--with-freetype=yes --with-freetype-includes="/usr/include/freetype2/" \
--with-wxwidgets \
--with-fftw \
--with-openmp \
--with-opengl-libs=/usr/include/GL \
--with-postgres=yes --with-postgres-includes="/usr/include/postgresql" \
--without-netcdf \
--without-mysql \
--without-odbc \
--without-ffmpeg
</source>

Now compile the source code (this will take some time as it generates binary code from the source code):
<source lang="bash">
# note: the more CPUs you have, the higher the -j number may be set to
# here: build using 4 CPU cores
make -j4
</source>

=== Installation ===

Install resulting GRASS GIS binaries into /usr/local/:
<source lang="bash">
sudo make install
</source>

Start GRASS GIS in the terminal:
<source lang="bash">
grass
</source>

'''Done & enjoy!'''

== Hints ==

* Usually, the installation of compiled code is done by using the <source lang="bash" enclose="none">make</source> tool. Alternatively, this can be done by using the ''checkinstall'' tool (i.e., <source lang="bash" enclose="none">sudo checkinstall</source> instead of <source lang="bash" enclose="none">sudo make install</source>) which eases off removal of packages. If ''checkinstall'' fails to deliver, please note some related bugs: [https://bugs.launchpad.net/ubuntu/+source/checkinstall/+bug/78455 78455] and [https://bugs.launchpad.net/ubuntu/+source/checkinstall/+bug/599163 599163]. Useful information on using ''checkinstall'': [https://help.ubuntu.com/community/CompilingEasyHowTo Compiling things on Ubuntu the Easy Way].

* In multi-core processors, the compilation performance can be boosted by using ''-j'' switches (e.g. <source lang="bash" enclose="none">make -j2</source> or <source lang="bash" enclose="none">make -j3</source> or even <source lang="bash" enclose="none">make -j4</source>) which specify the number of jobs (commands) to run simultaneously.

== Pre-compiled packages and backports ==

'''Pre-compiled packages and backports''' are available from [https://wiki.ubuntu.com/UbuntuGIS UbuntuGIS] via their [https://launchpad.net/~ubuntugis/+archive/ppa/ ppa.launchpad stable] and [https://launchpad.net/~ubuntugis/+archive/ubuntu/ubuntugis-unstable ppa.launchpad unstable] repositories. '''This is by far the simplest and fastest solution. Please prefer it over the manual way of compiling source code yourself as described below.'''

Version overview:
* noble 8.3
* jammy (22.04): 8.3
* focal (20.04 LTS): 8.2
* bionic (18.04 LTS): 7.8
* xenial (16.04 LTS): 7.6
* trusty (14.04 LTS): 7.4

a) Daily ready-to-install GRASS GIS builds of the stable release branch and master are available from ''ppa:grass/grass-devel'':

<source lang=bash>
sudo add-apt-repository ppa:ubuntugis/ubuntugis-unstable
sudo add-apt-repository ppa:grass/grass-devel
</source>

b) Latest packaged stable version of GRASS GIS is available from ''ppa:grass/grass-stable'':
<source lang=bash>
sudo add-apt-repository ppa:ubuntugis/ppa
sudo add-apt-repository ppa:grass/grass-stable
sudo apt-get update
sudo apt-get install grass
</source>

== Dependencies ==

=== Current stable Ubuntu version ===
First, update the system from the repositories<source lang="bash">
sudo apt-get update && sudo apt-get upgrade
</source>

Then, install ''SQLite'', ''git'' and ''dependencies'' for compiling PROJ, GEOS, GDAL/OGR, GRASS, GDAL-GRASS-PLUGIN (some additional packages may be required in this case); the following action will also install various dependencies (listed in the command line as <source lang="bash" enclose="none">The following extra packages will be installed:</source>...):<br/>

<source lang="bash">
# this is a single command, please copy-paste it entirely into the terminal:
sudo apt-get install \
build-essential \
flex make bison gcc libgcc1 g++ cmake ccache \
python python-dev \
python-opengl \
python-wxversion python-wxtools python-wxgtk3.2 \
python-dateutil libgsl-dev python-numpy \
wx3.2-headers wx-common libwxgtk3.2-dev \
libwxbase3.2-dev \
libncurses5-dev \
zlib1g-dev gettext \
libtiff5-dev libpnglite-dev \
libcairo libcairo-dev \
sqlite3 libsqlite3-dev \
libpq-dev \
libreadline6 libreadline6-dev libfreetype6-dev \
libfftw3-3 libfftw3-dev \
libboost-thread-dev libboost-program-options-dev \
resolvconf \
libjasper-dev \
git \
libav-tools libavutil-dev ffmpeg2theora \
libffmpegthumbnailer-dev \
libavcodec-dev \
libxmu-dev \
libavformat-dev libswscale-dev \
checkinstall \
libglu1-mesa-dev libxmu-dev \
ghostscript
</source>

The following dependencies concern Ubuntu 24.04 LTS:

<source lang="bash">
# this is a single command, please copy-paste it entirely into the terminal:
sudo apt-get install \
build-essential \
flex make bison gcc libgcc-s1 g++ \
python3 python3-dev \
python3-dateutil libgsl-dev python3-numpy \
zlib1g-dev gettext \
libtiff-dev libpnglite-dev \
sqlite3 libsqlite3-dev \
libboost-thread-dev libboost-program-options-dev \
systemd-resolved \
git \
checkinstall \
cmake ccache \
python3-opengl libwxbase3.2-1t64 libwxgtk3.2-dev \
python3-wxgtk4.0 \
cairo-dock libcairo2-dev \
libpq-dev \
libfreetype-dev \
libfftw3-dev libfftw3-single3 libfftw3-double3 \
libavcodec-dev \
libxmu-dev \
libavformat-dev libswscale-dev \
libglu1-mesa-dev libxmu-dev \
ghostscript
</source>

* See the additional packages bellow and in other sections and install them. Note that some of them are [https://github.com/OSGeo/grass/blob/main/REQUIREMENTS.md required], namely PROJ, GEOS and GDAL. If you don't have special requirements, it is usually enough just to install PROJ, GEOS and GDAL from repository (rather then compile them manually).

* for mysql support, <source lang="bash" enclose="none">libmysqlclient-dev</source> is required
<source lang="bash">
sudo apt-get install libmysqlclient-dev
</source>

* for netcdf support, <source lang="bash" enclose="none">netcdf-bin</source> and <source lang="bash" enclose="none">libnetcdf-dev</source> is required
<source lang="bash">
sudo apt-get install netcdf-bin libnetcdf-dev
</source>

* for {{AddonCmd|i.spec.unmix}} Addon support, install LAPACK and BLAS:
<source lang="bash">
sudo apt-get install libblas-dev liblapack-dev
</source>

* create a directory as a simple user where all source code is going to be stored -- in this example, a directory named <source lang="bash" enclose="none">src</source> under <source lang="bash" enclose="none">/usr/local</source> is created <source lang="bash">
sudo mkdir /usr/local/src
</source>

* take over directories ownerships ('''replace''' below the terms ''userid'' and ''groupid'' with a real <source lang="bash" enclose="none">userid</source>): <source lang="bash">
sudo chown userid:groupid /usr/local/src</source>

* similarly, grant <source lang="bash" enclose="none">rwx</source> (read-write-execute) permissions for our ''userid'' and ''groupid'' onto the <source lang="bash" enclose="none">src</source> directory: <source lang="bash">
sudo chmod ug+rwx /usr/local/src</source>

== Using pre-compiled dev Packages for PROJ, GEOS and GDAL ==

=== PROJ ===

Install the <source lang="bash" enclose="none">dev</source> package:

<source lang="bash">
sudo apt-get install libproj-dev proj-data proj-bin
</source>

* In the call to <source lang="bash" enclose="none">./configure</source> for [[#GRASS|GRASS]], replace <source lang="bash" enclose="none">--with-proj-share=/usr/local/share/proj/</source> by <source lang="bash" enclose="none">--with-proj-share=/usr/share/proj/</source>

=== GEOS ===

Install the <source lang="bash" enclose="none">dev</source> package:

<source lang="bash">
# probably you also need to additionally install "libgeos-c1v5"
sudo apt-get install libgeos-dev
</source>

* In the call to <source lang="bash" enclose="none">./configure</source> for [[#GRASS|GRASS]], replace <source lang="bash" enclose="none">--with-geos=/usr/local/bin/geos-config</source> by <source lang="bash" enclose="none">--with-geos=/usr/bin/geos-config</source>

=== GDAL ===

Install the <source lang="bash" enclose="none">dev</source> package (possibly without support for datumgrid):

<source lang="bash">
sudo apt-get install libgdal-dev
</source>

For support of WMS in wxGUI install Python GDAL bindings and GDAL executables:
<source lang="bash">
sudo apt-get install python-gdal gdal-bin
</source>

* Install also the required extra packages (note the message: <source lang="bash" enclose="none">The following extra packages will be installed:</source>)
* Look out for packages to be removed by this operation -- this is most likely caused by incompatible package versions. Fix these problems in advance using commands like the following: <source lang="bash">
sudo apt-get install <package>=<required.version></source>

=== GRASS-GIS ===

[[Compile_and_Install_Ubuntu#GRASS_GIS|Jump to sub-section GRASS-GIS below]]

== Using pre-compiled dev Packages for PROJ, GEOS and GDAL from GIS.lab PPA==

Ivan Mincik has made all required packages available in his [https://launchpad.net/~imincik/+archive/ubuntu/gis PPA]:

<source lang="bash">
sudo add-apt-repository ppa:imincik/gis
sudo apt-get install libproj-dev libgdal-dev python-gdal libgeos-dev
</source>

Now you can either also install GRASS GIS from there or compile it yourself (see [[Compile_and_Install_Ubuntu#GRASS_GIS|Jump to sub-section GRASS-GIS below]])

== Compile from source ==

=== PROJ ===

* within the directory <source lang="bash" enclose="none">/usr/local/src</source> (create it if it does not exist) checkout <source lang="bash" enclose="none">proj</source> from its GitHub repository: <source lang="bash">
https://github.com/OSGeo/PROJ/
</source>

* get [http://download.osgeo.org/proj/proj-datumgrid-1.8.zip '''proj-datumgrid-1.8.zip'''] or related files from [https://trac.osgeo.org/proj proj' trac] and move it under <source lang="bash" enclose="none">proj/nad</source>
<ul><source lang="bash">
wget http://download.osgeo.org/proj/proj-datumgrid-1.8.zip
mv proj-datumgrid-1.8.zip /usr/local/src/proj/nad
cd /usr/local/src/proj/nad
</source>
</ul>

* decompress it <source lang="bash">
unzip proj-datumgrid-1.8.zip
</source>

* go back to the <source lang="bash" enclose="none">proj</source> directory <source lang="bash">
cd /usr/local/src/proj
</source>

* if required, clean previous configuration & compilation <source lang="bash">
make distclean
</source>

* simple configure, compile and install <source lang="bash">
./configure && make && sudo make install
</source>
<ul> or <source lang="bash">
./configure && make -j2 && sudo checkinstall
</source>
</ul>

* ensure that <source lang="bash" enclose="none">/usr/local/lib</source> is added to <source lang="bash" enclose="none">/etc/ld.so.conf</source> and afterwards run <source lang="bash">
sudo ldconfig
</source>

* finally, go back to the parent directory simply by instructing<source lang="bash">
cd ..
</source>

=== GEOS ===

* download '''geos-3.12.2.tar.bz2''' from [https://libgeos.org/ https://libgeos.org/] using <source lang="bash" enclose="none">wget</source> <source lang="bash">
wget https://download.osgeo.org/geos/geos-3.12.2.tar.bz2
</source>

* move to the "source-code" directory and decompress
<ul><source lang="bash">
cd /usr/local/src/
bunzip2 geos-3.12.2.tar.bz2
tar xvf geos-3.12.2.tar
</source>
</ul>

* if required, clean previous configuration & compilation <source lang="bash">
make distclean
</source>

* move to geos directory <source lang="bash">
cd geos-3.12.2
</source>

* simple configure, compile and install <source lang="bash">
./configure && make && sudo make install
</source>
<ul> or <source lang="bash">
./configure && make -j2 && sudo checkinstall
</source>
</ul>

* do not forget to execute <source lang="bash">
sudo ldconfig
</source>

=== GDAL ===

'''Note''', GDAL must be compiled '''without''' GRASS support!

* download the current stable version (see https://github.com/OSGeo/gdal/releases for latest version):
<source lang="bash">
wget https://github.com/OSGeo/gdal/releases/download/v3.9.1/gdal-3.9.1.tar.gz
</source>

Follow the instructions to compile GDAL:
https://gdal.org/development/building_from_source.html

=== GRASS GIS ===

Note the differences between different GRASS GIS version (branches) in download and cofiguration. Note also the changes required if you installed some of the dependencies from packages (rather then compiled them yourself).

To fully understand the build process, read the <code>INSTALL</code> file, which is located in GRASS' source code root directory.

''' Getting GRASS' source code '''

Select from one of the GRASS GIS versions and download the source code:

https://github.com/OSGeo/grass/releases/

''' Configure, Compile and Install'''

Enter the directory with the source code, for example:

<source lang="bash">
cd grass
</source>

* '''GRASS GIS example configuration''' (which can/should be adjusted according to specific needs):
<ul>
<source lang="bash">
CFLAGS="-O2 -Wall" LDFLAGS="-s" ./configure \
--with-nls \
--with-cxx \
--with-proj-share=/usr/local/share/proj/ \
--with-geos=/usr/local/bin/geos-config \
--with-wxwidgets \
--with-cairo \
--with-opengl-libs=/usr/include/GL \
--with-freetype=yes --with-freetype-includes="/usr/include/freetype2/" \
--with-postgres=yes --with-postgres-includes="/usr/include/postgresql" \
--with-sqlite=yes \
--with-mysql=yes --with-mysql-includes="/usr/include/mysql" \
--with-odbc=no \
--with-pdal
</source>
</ul>
<ul>
'''Note''', the above configuration uses the <code>PROJ</code> and <code>GEOS</code> packages compiled from the source. In the case that pre-compiled versions from the repository are required, remove the above corresponding lines to use the "defaults", i.e. (note the backslashe at the end of each line)
<source lang="bash">
--with-proj-share=/usr/share/proj \
--with-geos=/usr/bin/geos-config \
</source>
</ul>

* compile & install <source lang="bash">
make -j2 && sudo make install && sudo ldconfig
</source>

<ul> or <source lang="bash">
make -j2 && sudo checkinstall && sudo ldconfig
</source>
</ul>

For subsequent updates execute (not need for the first time):
<source lang="bash">
svn up
make -j2 && sudo make install && sudo ldconfig
</source>

Sometimes, it is required to clean previous configuration and compilation:
<source lang="bash">
make distclean
svn up
./configure ... # (use the configure command above)
make -j2 && sudo make install && sudo ldconfig
</source>

=== GDAL-GRASS-Plugin ===

See: https://github.com/OSGeo/gdal-grass

* get the plugin from [https://github.com/OSGeo/gdal-grass/releases GitHub]: "gdal-grass-X.Y.Z.tar.gz" using <source lang="bash" enclose="none">wget</source>
<ul><source lang="bash">
# update version number accordingly!
wget https://github.com/OSGeo/gdal-grass/archive/refs/tags/1.0.2.tar.gz -O gdal-grass-1.0.2.tar.gz
tar xvzf gdal-grass-1.0.2.tar.gz
cd gdal-grass-1.0.2
</source></ul>

* create <source lang="bash" enclose="none">/etc/ld.so.conf.d/grass.conf</source> or add in <source lang="bash" enclose="none">/etc/ld.so.conf</source> the GRASS library path:
<ul><source lang="bash">
# GRASS GIS stable library path (adapt as needed)
/usr/local/src/releasebranch_8_4/lib

# GRASS GIS development version library path (adapt as needed)
/usr/local/src/grass_master/lib
</source></ul>

* optionally, clean previous configurations/compilations<source lang="bash">
make distclean</source>

* configure -- point to GRASS installation/binaries
<ul><source lang="bash"> ./configure \
--prefix=/usr/local \
--with-gdal=/usr/local/bin/gdal-config \
--with-grass=/usr/local/grass/ \
--with-autoload="/usr/local/lib64/gdalplugins/" \
--with-ld-shared="g++ -shared"</source></ul>
</ul>

* compile & install using checkinstall<source lang="bash">
make -j2 && sudo checkinstall</source>

= Post compilation/installation control =

* For a recommended quick-check read the [https://grass.osgeo.org/wiki/Compile_and_install_GRASS_and_QGIS_with_GDAL/OGR_Plugin#Troubleshooting Troubleshooting] section at [https://grass.osgeo.org/wiki/Compile_and_install_GDAL-GRASS_plugin Compile_and_install_GDAL-GRASS_plugin]

* in case of errors in future compilation attempts, remember to remove program binaries and files created with the "configuration" from previous compilations with
make distclean

* another common mistake is compiling a module against some GRASS version and then try to run it through another GRASS version. The solution is to recompile the affected module or, in case there are multiple GRASS installations, set up properly LD_LIBRARY_PATH paths.

= Removal of GRASS =

To get rid of a GRASS binaries installation, delete (update version numbers accordingly)
* <source lang="bash" enclose="none">/usr/local/grass</source> (directory, binaries location)
* <source lang="bash" enclose="none">/usr/local/bin/grass</source> (file)
* <source lang="bash" enclose="none">/home/username/.grassrc8</source> (file)

If wanted, delete also the complete source code:
* <source lang="bash" enclose="none">/usr/local/src/grass_release</source> (directory, source code location)

To remove <code>grass</code> (or any other package) which was installed by <source lang="bash" enclose="none">checkinstall</source>, use <source lang="bash" enclose="none">dpkg</source>, e.g.<source lang="bash">
sudo dpkg -r grass # package name defined at installation is important</source>

== See also ==

* Docker: https://grass.osgeo.org/download/docker/
* [[Ubuntu Packaging]]
* [[GRASS in Debian]]

= Archived Notes =

Notes that concern the configuration and compilation of GRASS GIS and its dependencies for older versions of Ubuntu-Linux.

[[Category: Compilation]]
[[Category: Installation]]
[[Category: Ubuntu]]
[[Category: FAQ]]

Compile and Install Ubuntu

2026-03-10T09:33:39Z

Neteler: Update to Ubuntu 24.04 version

<div class="boilerplate metadata" id="attention" style="-moz-border-radius:30px; border: 1px double #35824B; margin-bottom: 1.5em; padding: 1em; background-color: #f9f9f9;">
<p style="font-size: 150%; text-align: left;"><span style="color:#35824B">'''Attention'''</span> </p><span style="color:#333333">'''The following instructions describe the compilation and installation of GRASS GIS and its required dependencies completely from the source on Ubuntu based systems. Please, prefer pre-compiled packages over the manual way described below unless you know ''what'' and ''how'', you want to learn and help testing.'''</span>
</div>

== Quick instructions ==

These instructions should work fine on Ubuntu distributions:

=== Install geospatial dependencies ===

1. Install some dependencies (PROJ, GEOS, GDAL libraries) and the compiler tools <br />
(note: you need Python 3)

<source lang="bash">
# be sure to have an updated system
sudo apt update && sudo apt upgrade -y

# install PROJ
sudo apt install libproj-dev proj-data proj-bin unzip -y
</source>

<source lang="bash">
# optionally, install (selected) datum grid files
sudo apt-get install proj-data

# install GEOS
sudo apt install libgeos-dev -y

# install GDAL
sudo apt install libgdal-dev python3-gdal gdal-bin -y

# install PDAL (optional)
sudo apt install libpdal-dev pdal -y

# Python3 precedence over Python2 (which is end-of-life since 2019, so it should be the default anyway)
sudo update-alternatives --install /usr/bin/python python /usr/bin/python3 1
</source>

Install compiler stuff and further dependencies.
Note: this is a single command, please copy-paste it entirely into the terminal:

=== Install further compilation dependencies (Ubuntu 22.04) ===

For Ubuntu 22.04:
<source lang="bash">
sudo apt-get install \
build-essential \
flex make bison gcc libgcc1 g++ ccache \
python3 python3-dev python3-pip \
python3-opengl python3-wxgtk4.0 \
python3-dateutil libgsl-dev python3-numpy \
wx3.0-headers wx-common libwxgtk3.0-gtk3-dev \
libwxbase3.0-dev \
libncurses5-dev \
libbz2-dev \
zlib1g-dev gettext \
libtiff5-dev libpnglite-dev \
libcairo2 libcairo2-dev \
sqlite3 libsqlite3-dev \
libpq-dev libreadline-dev \
libfreetype6-dev libfftw3-3 \
libfftw3-dev libboost-thread-dev \
libboost-program-options-dev git \
libzstd-dev checkinstall \
libglu1-mesa-dev libxmu-dev \
ghostscript wget -y
</source>

For NVIZ on Ubuntu:
<source lang="bash">
sudo apt-get install \
ffmpeg libavutil-dev ffmpeg2theora \
libffmpegthumbnailer-dev \
libavcodec-dev \
libxmu-dev \
libavformat-dev libswscale-dev -y
</source>

Update wxpython:

<source lang="bash">
# be sure to pick the correct Ubuntu version
pip3 install -U -f https://extras.wxpython.org/wxPython4/extras/linux/gtk3/ubuntu-22.04 wxPython
</source>

=== Source code download ===
Now we have all "ingredients" readily installed on our system.

'''Source code download''':

There a two ways of getting the source code: either use a) the weekly snapshot (cannot be updated, or b) the source code from the GitHub repository (you can update your local copy easily in future):

'''a) Download of the weekly source code snapshot (not recommended):'''
<source lang="bash">
# download latest GRASS GIS 8.x stable release source code:
mkdir $HOME/src/
cd $HOME/src/
wget https://grass.osgeo.org/grass84/source/snapshot/grass-8.4.git_src_snapshot_latest.tar.gz

# Unpack source code package and remove tarball archive:
tar xvfz grass-8.4.git_src_snapshot_latest.tar.gz
rm -f grass-8.4.git_src_snapshot_latest.tar.gz

# rename source code directory (yes, with the questionmarks!)
mv grass-8.4.git_src_snapshot_20??_??_?? grass-8.4.latest
cd grass-8.4.latest/
</source>

'''b) Download of the current development version from GitHub (adopt the path below accordingly)'''

Note: to find the current version number (8_x), see https://github.com/OSGeo/grass/branches:

<source lang="bash">
sudo apt-get install git
git clone https://github.com/OSGeo/grass.git grass-8.4.latest.git
cd grass-8.4.latest.git/
git checkout releasebranch_8_4
</source>

=== Compilation ===
Now we can '''compile''' the source code in order to generate the GRASS GIS binaries:

<source lang="bash">
# "configure" source code for local machine (checks for CPU type etc):
MYCFLAGS='-O2 -fPIC -fno-common -fexceptions -std=gnu99 -fstack-protector -m64'
#MYCXXFLAGS=''
MYLDFLAGS='-Wl,--no-undefined -Wl,-z,now'

LDFLAGS="$MYLDFLAGS" CFLAGS="$MYCFLAGS" CXXFLAGS="$MYCXXFLAGS" ./configure \
--with-cxx \
--enable-largefile \
--with-proj --with-proj-share=/usr/share/proj \
--with-gdal=/usr/bin/gdal-config \
--with-python \
--with-geos \
--with-sqlite \
--with-nls \
--with-zstd \
--with-pdal \
--with-cairo --with-cairo-ldflags=-lfontconfig \
--with-freetype=yes --with-freetype-includes="/usr/include/freetype2/" \
--with-wxwidgets \
--with-fftw \
--with-openmp \
--with-opengl-libs=/usr/include/GL \
--with-postgres=yes --with-postgres-includes="/usr/include/postgresql" \
--without-netcdf \
--without-mysql \
--without-odbc \
--without-ffmpeg
</source>

Now compile the source code (this will take some time as it generates binary code from the source code):
<source lang="bash">
# note: the more CPUs you have, the higher the -j number may be set to
# here: build using 4 CPU cores
make -j4
</source>

=== Installation ===

Install resulting GRASS GIS binaries into /usr/local/:
<source lang="bash">
sudo make install
</source>

Start GRASS GIS in the terminal:
<source lang="bash">
grass
</source>

'''Done & enjoy!'''

== Hints ==

* Usually, the installation of compiled code is done by using the <source lang="bash" enclose="none">make</source> tool. Alternatively, this can be done by using the ''checkinstall'' tool (i.e., <source lang="bash" enclose="none">sudo checkinstall</source> instead of <source lang="bash" enclose="none">sudo make install</source>) which eases off removal of packages. If ''checkinstall'' fails to deliver, please note some related bugs: [https://bugs.launchpad.net/ubuntu/+source/checkinstall/+bug/78455 78455] and [https://bugs.launchpad.net/ubuntu/+source/checkinstall/+bug/599163 599163]. Useful information on using ''checkinstall'': [https://help.ubuntu.com/community/CompilingEasyHowTo Compiling things on Ubuntu the Easy Way].

* In multi-core processors, the compilation performance can be boosted by using ''-j'' switches (e.g. <source lang="bash" enclose="none">make -j2</source> or <source lang="bash" enclose="none">make -j3</source> or even <source lang="bash" enclose="none">make -j4</source>) which specify the number of jobs (commands) to run simultaneously.

== Pre-compiled packages and backports ==

'''Pre-compiled packages and backports''' are available from [https://wiki.ubuntu.com/UbuntuGIS UbuntuGIS] via their [https://launchpad.net/~ubuntugis/+archive/ppa/ ppa.launchpad stable] and [https://launchpad.net/~ubuntugis/+archive/ubuntu/ubuntugis-unstable ppa.launchpad unstable] repositories. '''This is by far the simplest and fastest solution. Please prefer it over the manual way of compiling source code yourself as described below.'''

Version overview:
* noble 8.3
* jammy (22.04): 8.3
* focal (20.04 LTS): 8.2
* bionic (18.04 LTS): 7.8
* xenial (16.04 LTS): 7.6
* trusty (14.04 LTS): 7.4

a) Daily ready-to-install GRASS GIS builds of the stable release branch and master are available from ''ppa:grass/grass-devel'':

<source lang=bash>
sudo add-apt-repository ppa:ubuntugis/ubuntugis-unstable
sudo add-apt-repository ppa:grass/grass-devel
</source>

b) Latest packaged stable version of GRASS GIS is available from ''ppa:grass/grass-stable'':
<source lang=bash>
sudo add-apt-repository ppa:ubuntugis/ppa
sudo add-apt-repository ppa:grass/grass-stable
sudo apt-get update
sudo apt-get install grass
</source>

== Dependencies ==

=== Current stable Ubuntu version ===
First, update the system from the repositories<source lang="bash">
sudo apt-get update && sudo apt-get upgrade
</source>

Then, install ''SQLite'', ''git'' and ''dependencies'' for compiling PROJ, GEOS, GDAL/OGR, GRASS, GDAL-GRASS-PLUGIN (some additional packages may be required in this case); the following action will also install various dependencies (listed in the command line as <source lang="bash" enclose="none">The following extra packages will be installed:</source>...):<br/>

<source lang="bash">
# this is a single command, please copy-paste it entirely into the terminal:
sudo apt-get install \
build-essential \
flex make bison gcc libgcc1 g++ cmake ccache \
python python-dev \
python-opengl \
python-wxversion python-wxtools python-wxgtk3.2 \
python-dateutil libgsl-dev python-numpy \
wx3.2-headers wx-common libwxgtk3.2-dev \
libwxbase3.2-dev \
libncurses5-dev \
zlib1g-dev gettext \
libtiff5-dev libpnglite-dev \
libcairo libcairo-dev \
sqlite3 libsqlite3-dev \
libpq-dev \
libreadline6 libreadline6-dev libfreetype6-dev \
libfftw3-3 libfftw3-dev \
libboost-thread-dev libboost-program-options-dev \
resolvconf \
libjasper-dev \
git \
libav-tools libavutil-dev ffmpeg2theora \
libffmpegthumbnailer-dev \
libavcodec-dev \
libxmu-dev \
libavformat-dev libswscale-dev \
checkinstall \
libglu1-mesa-dev libxmu-dev \
ghostscript
</source>

The following dependencies concern Ubuntu 24.04 LTS:

<source lang="bash">
# this is a single command, please copy-paste it entirely into the terminal:
sudo apt-get install \
build-essential \
flex make bison gcc libgcc-s1 g++ \
python3 python3-dev \
python3-dateutil libgsl-dev python3-numpy \
zlib1g-dev gettext \
libtiff-dev libpnglite-dev \
sqlite3 libsqlite3-dev \
libboost-thread-dev libboost-program-options-dev \
systemd-resolved \
git \
checkinstall \
cmake ccache \
python3-opengl libwxbase3.2-1t64 libwxgtk3.2-dev \
python3-wxgtk4.0 \
cairo-dock libcairo2-dev \
libpq-dev \
libfreetype-dev \
libfftw3-dev libfftw3-single3 libfftw3-double3 \
libavcodec-dev \
libxmu-dev \
libavformat-dev libswscale-dev \
libglu1-mesa-dev libxmu-dev \
ghostscript
</source>

* See the additional packages bellow and in other sections and install them. Note that some of them are [https://github.com/OSGeo/grass/blob/main/REQUIREMENTS.md required], namely PROJ, GEOS and GDAL. If you don't have special requirements, it is usually enough just to install PROJ, GEOS and GDAL from repository (rather then compile them manually).

* for mysql support, <source lang="bash" enclose="none">libmysqlclient-dev</source> is required
<source lang="bash">
sudo apt-get install libmysqlclient-dev
</source>

* for netcdf support, <source lang="bash" enclose="none">netcdf-bin</source> and <source lang="bash" enclose="none">libnetcdf-dev</source> is required
<source lang="bash">
sudo apt-get install netcdf-bin libnetcdf-dev
</source>

* for {{AddonCmd|i.spec.unmix}} Addon support, install LAPACK and BLAS:
<source lang="bash">
sudo apt-get install libblas-dev liblapack-dev
</source>

* create a directory as a simple user where all source code is going to be stored -- in this example, a directory named <source lang="bash" enclose="none">src</source> under <source lang="bash" enclose="none">/usr/local</source> is created <source lang="bash">
sudo mkdir /usr/local/src
</source>

* take over directories ownerships ('''replace''' below the terms ''userid'' and ''groupid'' with a real <source lang="bash" enclose="none">userid</source>): <source lang="bash">
sudo chown userid:groupid /usr/local/src</source>

* similarly, grant <source lang="bash" enclose="none">rwx</source> (read-write-execute) permissions for our ''userid'' and ''groupid'' onto the <source lang="bash" enclose="none">src</source> directory: <source lang="bash">
sudo chmod ug+rwx /usr/local/src</source>

== Using pre-compiled dev Packages for PROJ, GEOS and GDAL ==

=== PROJ ===

Install the <source lang="bash" enclose="none">dev</source> package:

<source lang="bash">
sudo apt-get install libproj-dev proj-data proj-bin
</source>

* In the call to <source lang="bash" enclose="none">./configure</source> for [[#GRASS|GRASS]], replace <source lang="bash" enclose="none">--with-proj-share=/usr/local/share/proj/</source> by <source lang="bash" enclose="none">--with-proj-share=/usr/share/proj/</source>

=== GEOS ===

Install the <source lang="bash" enclose="none">dev</source> package:

<source lang="bash">
# probably you also need to additionally install "libgeos-c1v5"
sudo apt-get install libgeos-dev
</source>

* In the call to <source lang="bash" enclose="none">./configure</source> for [[#GRASS|GRASS]], replace <source lang="bash" enclose="none">--with-geos=/usr/local/bin/geos-config</source> by <source lang="bash" enclose="none">--with-geos=/usr/bin/geos-config</source>

=== GDAL ===

Install the <source lang="bash" enclose="none">dev</source> package (possibly without support for datumgrid):

<source lang="bash">
sudo apt-get install libgdal-dev
</source>

For support of WMS in wxGUI install Python GDAL bindings and GDAL executables:
<source lang="bash">
sudo apt-get install python-gdal gdal-bin
</source>

* Install also the required extra packages (note the message: <source lang="bash" enclose="none">The following extra packages will be installed:</source>)
* Look out for packages to be removed by this operation -- this is most likely caused by incompatible package versions. Fix these problems in advance using commands like the following: <source lang="bash">
sudo apt-get install <package>=<required.version></source>

=== GRASS-GIS ===

[[Compile_and_Install_Ubuntu#GRASS_GIS|Jump to sub-section GRASS-GIS below]]

== Using pre-compiled dev Packages for PROJ, GEOS and GDAL from GIS.lab PPA==

Ivan Mincik has made all required packages available in his [https://launchpad.net/~imincik/+archive/ubuntu/gis PPA]:

<source lang="bash">
sudo add-apt-repository ppa:imincik/gis
sudo apt-get install libproj-dev libgdal-dev python-gdal libgeos-dev
</source>

Now you can either also install GRASS GIS from there or compile it yourself (see [[Compile_and_Install_Ubuntu#GRASS_GIS|Jump to sub-section GRASS-GIS below]])

== Compile from source ==

=== PROJ ===

* within the directory <source lang="bash" enclose="none">/usr/local/src</source> (create it if it does not exist) checkout <source lang="bash" enclose="none">proj</source> from its GitHub repository: <source lang="bash">
https://github.com/OSGeo/PROJ/
</source>

* get [http://download.osgeo.org/proj/proj-datumgrid-1.8.zip '''proj-datumgrid-1.8.zip'''] or related files from [https://trac.osgeo.org/proj proj' trac] and move it under <source lang="bash" enclose="none">proj/nad</source>
<ul><source lang="bash">
wget http://download.osgeo.org/proj/proj-datumgrid-1.8.zip
mv proj-datumgrid-1.8.zip /usr/local/src/proj/nad
cd /usr/local/src/proj/nad
</source>
</ul>

* decompress it <source lang="bash">
unzip proj-datumgrid-1.8.zip
</source>

* go back to the <source lang="bash" enclose="none">proj</source> directory <source lang="bash">
cd /usr/local/src/proj
</source>

* if required, clean previous configuration & compilation <source lang="bash">
make distclean
</source>

* simple configure, compile and install <source lang="bash">
./configure && make && sudo make install
</source>
<ul> or <source lang="bash">
./configure && make -j2 && sudo checkinstall
</source>
</ul>

* ensure that <source lang="bash" enclose="none">/usr/local/lib</source> is added to <source lang="bash" enclose="none">/etc/ld.so.conf</source> and afterwards run <source lang="bash">
sudo ldconfig
</source>

* finally, go back to the parent directory simply by instructing<source lang="bash">
cd ..
</source>

=== GEOS ===

* download '''geos-3.12.2.tar.bz2''' from [https://libgeos.org/ https://libgeos.org/] using <source lang="bash" enclose="none">wget</source> <source lang="bash">
wget https://download.osgeo.org/geos/geos-3.12.2.tar.bz2
</source>

* move to the "source-code" directory and decompress
<ul><source lang="bash">
cd /usr/local/src/
bunzip2 geos-3.12.2.tar.bz2
tar xvf geos-3.12.2.tar
</source>
</ul>

* if required, clean previous configuration & compilation <source lang="bash">
make distclean
</source>

* move to geos directory <source lang="bash">
cd geos-3.12.2
</source>

* simple configure, compile and install <source lang="bash">
./configure && make && sudo make install
</source>
<ul> or <source lang="bash">
./configure && make -j2 && sudo checkinstall
</source>
</ul>

* do not forget to execute <source lang="bash">
sudo ldconfig
</source>

=== GDAL ===

'''Note''', GDAL must be compiled '''without''' GRASS support!

* download the current stable version (see https://github.com/OSGeo/gdal/releases for latest version):
<source lang="bash">
wget https://github.com/OSGeo/gdal/releases/download/v3.9.1/gdal-3.9.1.tar.gz
</source>

Follow the instructions to compile GDAL:
https://gdal.org/development/building_from_source.html

=== GRASS GIS ===

Note the differences between different GRASS GIS version (branches) in download and cofiguration. Note also the changes required if you installed some of the dependencies from packages (rather then compiled them yourself).

To fully understand the build process, read the <code>INSTALL</code> file, which is located in GRASS' source code root directory.

''' Getting GRASS' source code '''

Select from one of the GRASS GIS versions and download the source code:

https://github.com/OSGeo/grass/releases/

''' Configure, Compile and Install'''

Enter the directory with the source code, for example:

<source lang="bash">
cd grass
</source>

* '''GRASS GIS example configuration''' (which can/should be adjusted according to specific needs):
<ul>
<source lang="bash">
CFLAGS="-O2 -Wall" LDFLAGS="-s" ./configure \
--with-nls \
--with-cxx \
--with-proj-share=/usr/local/share/proj/ \
--with-geos=/usr/local/bin/geos-config \
--with-wxwidgets \
--with-cairo \
--with-opengl-libs=/usr/include/GL \
--with-freetype=yes --with-freetype-includes="/usr/include/freetype2/" \
--with-postgres=yes --with-postgres-includes="/usr/include/postgresql" \
--with-sqlite=yes \
--with-mysql=yes --with-mysql-includes="/usr/include/mysql" \
--with-odbc=no \
--with-pdal
</source>
</ul>
<ul>
'''Note''', the above configuration uses the <code>PROJ</code> and <code>GEOS</code> packages compiled from the source. In the case that pre-compiled versions from the repository are required, remove the above corresponding lines to use the "defaults", i.e. (note the backslashe at the end of each line)
<source lang="bash">
--with-proj-share=/usr/share/proj \
--with-geos=/usr/bin/geos-config \
</source>
</ul>

* compile & install <source lang="bash">
make -j2 && sudo make install && sudo ldconfig
</source>

<ul> or <source lang="bash">
make -j2 && sudo checkinstall && sudo ldconfig
</source>
</ul>

For subsequent updates execute (not need for the first time):
<source lang="bash">
svn up
make -j2 && sudo make install && sudo ldconfig
</source>

Sometimes, it is required to clean previous configuration and compilation:
<source lang="bash">
make distclean
svn up
./configure ... # (use the configure command above)
make -j2 && sudo make install && sudo ldconfig
</source>

=== GDAL-GRASS-Plugin ===

See: https://github.com/OSGeo/gdal-grass

* get the plugin from [https://github.com/OSGeo/gdal-grass/releases GitHub]: "gdal-grass-X.Y.Z.tar.gz" using <source lang="bash" enclose="none">wget</source>
<ul><source lang="bash">
# update version number accordingly!
wget https://github.com/OSGeo/gdal-grass/archive/refs/tags/1.0.2.tar.gz -O gdal-grass-1.0.2.tar.gz
tar xvzf gdal-grass-1.0.2.tar.gz
cd gdal-grass-1.0.2
</source></ul>

* create <source lang="bash" enclose="none">/etc/ld.so.conf.d/grass.conf</source> or add in <source lang="bash" enclose="none">/etc/ld.so.conf</source> the GRASS library path:
<ul><source lang="bash">
# GRASS GIS stable library path (adapt as needed)
/usr/local/src/releasebranch_8_4/lib

# GRASS GIS development version library path (adapt as needed)
/usr/local/src/grass_master/lib
</source></ul>

* optionally, clean previous configurations/compilations<source lang="bash">
make distclean</source>

* configure -- point to GRASS installation/binaries
<ul><source lang="bash"> ./configure \
--prefix=/usr/local \
--with-gdal=/usr/local/bin/gdal-config \
--with-grass=/usr/local/grass/ \
--with-autoload="/usr/local/lib64/gdalplugins/" \
--with-ld-shared="g++ -shared"</source></ul>
</ul>

* compile & install using checkinstall<source lang="bash">
make -j2 && sudo checkinstall</source>

= Post compilation/installation control =

* For a recommended quick-check read the [https://grass.osgeo.org/wiki/Compile_and_install_GRASS_and_QGIS_with_GDAL/OGR_Plugin#Troubleshooting Troubleshooting] section at [https://grass.osgeo.org/wiki/Compile_and_install_GDAL-GRASS_plugin Compile_and_install_GDAL-GRASS_plugin]

* in case of errors in future compilation attempts, remember to remove program binaries and files created with the "configuration" from previous compilations with
make distclean

* another common mistake is compiling a module against some GRASS version and then try to run it through another GRASS version. The solution is to recompile the affected module or, in case there are multiple GRASS installations, set up properly LD_LIBRARY_PATH paths.

= Removal of GRASS =

To get rid of a GRASS binaries installation, delete (update version numbers accordingly)
* <source lang="bash" enclose="none">/usr/local/grass</source> (directory, binaries location)
* <source lang="bash" enclose="none">/usr/local/bin/grass</source> (file)
* <source lang="bash" enclose="none">/home/username/.grassrc8</source> (file)

If wanted, delete also the complete source code:
* <source lang="bash" enclose="none">/usr/local/src/grass_release</source> (directory, source code location)

To remove <code>grass</code> (or any other package) which was installed by <source lang="bash" enclose="none">checkinstall</source>, use <source lang="bash" enclose="none">dpkg</source>, e.g.<source lang="bash">
sudo dpkg -r grass # package name defined at installation is important</source>

== See also ==

* Docker: https://grass.osgeo.org/download/docker/
* [[Ubuntu Packaging]]
* [[GRASS in Debian]]

= Archived Notes =

Notes that concern the configuration and compilation of GRASS GIS and its dependencies for older versions of Ubuntu-Linux.

[[Category: Compilation]]
[[Category: Installation]]
[[Category: Ubuntu]]
[[Category: FAQ]]

PSC Meeting 2026-02-13

2026-02-13T15:12:03Z

Neteler: /* Agenda */

== Participants ==

* TBD

== Agenda ==

The topics proposed are:

* Annual budget request submitted to OSGeo
* Community Meeting - San Michele: date, planning, budget requests
* Releases
* GSoC
* [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md#ai-use-policy AI policy]
* Plan PSC elections/role changes for later this year (some of us are in PSC since Feb 2021)
* Budget
** Where are we at time?
** Fundraising efforts
* add your suggestion here...

== Minutes ==

* TBD

[[Category:PSC]]

PSC Meeting 2026-02-13

2026-02-13T15:06:20Z

Neteler: +Budget

== Participants ==

* TBD

== Agenda ==

The topics proposed are:

* Annual budget request submitted to OSGeo
* Community Meeting - San Michele: date, planning, budget requests
* Releases
* GSoC
* AI policy
* Plan PSC elections/role changes for later this year (some of us are in PSC since Feb 2021)
* Budget
** Where are we at time?
** Fundraising efforts
* add your suggestion here...

== Minutes ==

* TBD

[[Category:PSC]]

GUI

2026-01-21T15:26:06Z

Neteler: +Evolution of the GRASS GUI

=== Tcl/Tk Graphical User Interface (GUI) ===

The Tcl/Tk GUI based is the classical GRASS user interface in the versions GRASS 4.2-6.3. For details, see the [http://grass.osgeo.org/grass64/manuals/html64_user/gis.m.html GIS Manager user manual] and these [https://web.archive.org/web/20120116091437/http://grass.osgeo.org/screenshots/gui.php#tcltk screenshots].

=== wxPython GUI ===

GRASS's Tcl/Tk graphical user interface is currently undergoing a [[wxGUI|complete rewrite]] using wxPython. It is currently available for testing in GRASS 6.3 and will be the default GUI in GRASS 6.4 and GRASS 7+. See also these [https://grass.osgeo.org/learn/gallery/#user-interface screenshots].

=== Command line ===

Not really a GUI, but loved by advanced GRASS users: the command line interface. Worth learning it!

=== External GUIs: QGIS (Quantum GIS) ===

The [https://qgis.org QGIS software] gives access to key GRASS modules through a user-friendly plugin toolbox. QGIS can view GRASS maps directly alongside GIS data of many other formats. See also these [https://web.archive.org/web/20120116091437/https://grass.osgeo.org/screenshots/gui.php#qgis screenshots].

=== Overview of the GUI evolution ===

See [https://github.com/OSGeo/grass-promo/blob/main/grass-evolution/gui/README.md Evolution of the GRASS GUI]

[[Category: Documentation]]

GRASS Budget 2026

2026-01-09T14:18:25Z

Neteler: link treasurer -> PSC members

PSC

2026-01-09T14:17:26Z

Neteler: add role "Treasurer"

= GRASS Project Steering Committee (PSC) =
The Project Steering Committee plays a pivotal role in the governance and operational direction of GRASS GIS.
The PSC meets regularly to discuss organizational and financial aspects of the GRASS project and maintains the [[#PSC meeting agenda and minutes]].
The PSC is responsible for granting write access to new core developers and approving RFCs ([https://github.com/OSGeo/grass/tree/main/doc/development/rfc Request For Comments]).
The PSC has its own public [http://lists.osgeo.org/mailman/listinfo/grass-psc mailing list] where [[#Motions]] are passed.

== Members ==

* '''[https://veroandreo.gitlab.io Verónica Andreo]''', (veroandreo * gmail.com), National Research Council (CONICET) - Argentinian Space Agency (CONAE), AR - Chair
*'''[https://ecodiv.earth/about.html Paulo van Breugel]''', (p.vanbreugel * gmail com), HAS green academy, NL
*'''[https://idea.isnew.info/ Huidae Cho]''', (grass4u * gmail com), New Mexico State University, USA
*'''[https://geomatics.fsv.cvut.cz/en/employees/linda-karlovska/ Linda Karlovská]''', (linda.karlovska * seznam cz), Czech Technical University in Prague, CZ
*'''[https://www.osgeo.org/member/kudrnovsky/ Helmut Kudrnovsky]''', (hellik * web de), Environment Agency Austria, Vienna, AT
*'''Nicklas Larsson''', (n_larsson * yahoo com), Hungarian National Museum, HU
*'''[https://www.mundialis.de/neteler/ Markus Neteler]''', (neteler * osgeo org), mundialis, Bonn, DE
*'''[https://cnr.ncsu.edu/geospatial/people/vaclav-petras/ Vaclav Petráš]''', (wenzeslaus * gmail com), CGA, North Carolina State University, Raleigh NC, USA - Treasurer
*'''[https://cnr.ncsu.edu/geospatial/people/anna-petrasova Anna Petrášová]''', (kratochanna * gmail com). CGA, North Carolina State University, Raleigh NC, USA

== PSC meeting agenda and minutes ==
<div style="column-count:4">
* [[PSC Meeting 2025-11-14]]
* [[PSC Meeting 2025-08-08]]
* [[PSC Meeting 2025-05-23]]
* [[PSC Meeting 2025-05-09]]
* [[PSC Meeting 2025-02-14]]
* [[PSC Meeting 2024-11-22]]
* [[PSC Meeting 2024-11-08]]
* [[PSC Meeting 2024-08-09]]
* [[PSC Meeting 2024-06-14]]
* [[PSC Meeting 2024-05-10]]
* [https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20240209 PSC Meeting 2024-02-09]
* [https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20231110 PSC Meeting 2023-11-10]
* [https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20230811 PSC Meeting 2023-08-11]
* [https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20230512 PSC Meeting 2023-05-12]
* [https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20230210 PSC Meeting 2023-02-10]
* [https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20221111 PSC Meeting 2022-11-11]
* [https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20220812 PSC Meeting 2022-08-12]
* [https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20220513 PSC Meeting 2022-05-13]
* [https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20220211 PSC Meeting 2022-02-11]
* [https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20211112 PSC Meeting 2021-11-12]
* [https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20210729 PSC Meeting 2021-07-29]
* [https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20210511 PSC Meeting 2021-05-11]
* [https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20210203 PSC Meeting 2021-02-03]
</div>

== Motions ==

Motions are approved at meetings or on the grass-psc mailing list. Listed motions are approved unless otherwise noted.

=== 2025 ===

* Reimburse Alen Mangafic for stickers for FOSS4G Auckland 2025 (NZ) (14 Nov 2025, [[PSC Meeting 2025-11-14]])
* GitHub write access to Corey White as new core developer (20 May 2025, granted)
* Join [https://numfocus.org/ NumFOCUS] by signing Fiscal Sponsorship Agreement, signed by AP, VP, LK, VA, MN, which is the majority of PSC (5 out of 9, NumFOCUS required 5)
* Adopt new logo and branding (3 Apr 2025, [https://lists.osgeo.org/pipermail/grass-psc/2025-March/002995.html email], [https://github.com/OSGeo/grass-website/pull/506 PR])
* Use "GRASS" as the project name (26 Feb 2025, [https://lists.osgeo.org/pipermail/grass-psc/2025-February/002970.html email])

=== 2024 ===

* Approve and adopt [https://github.com/OSGeo/grass/pull/4566 C++17 Standard Support RFC] (28 Nov 2024)
* Apply for NumFOCUS membership (8 Nov 2024, [[PSC_Meeting_2024-11-08|meeting]])
* Pay Publer's business plan for one year, 3 accounts and test. Use GRASS budget sitting at OSGeo (8 Nov 2024, [[PSC_Meeting_2024-11-08|meeting]])
* Approve Linda's student grant final report and issue second payment (27 May 2024)
* Support Letter for LoC of FOSS4G 2025 Hiroshima (wording approved, 10 May 2024)
* GitHub write access to Linda Karlovska as a new core developer (granted, 26 Jan 2024)

=== 2023 ===

* Approve Linda's student grant proposal and issue first payment (27 Dec 2023)
* Github write access to Edouard Choinière as a new core developer (granted, 18 Dec 2023)
* Appoint Vaclav Petras as new treasurer (5 Dec 2023)
* Approve and adopt [https://github.com/OSGeo/grass/blob/main/doc/development/rfc/version_numbering.md RFC: Version Numbering] (5 Jun 2023)
* Approve and adopt RFC: Python Language Support (5 Jun 2023)
* Approve Linda's student grant final report (16 Mar 2023)
* Appoint Markus Neteler as new treasurer (19 Jan 2023)

=== 2022 ===

* Approve Linda's proposal for GRASS mini grant (19 Nov 2022)
* Approve final report of Caitlin Haedrich's mini grant (30 Apr 2022)
* Approve final report of Linda Kladivova's mini grant (10 Mar 2022)
* Approve mini grant for Caitlin Haedrich (6 Jan 2022)

=== 2021 ===

* Approve mini grant for Linda Kladivova (21 Dec 2021)
* [https://trac.osgeo.org/grass/wiki/RFC/7_LanguageStandardsSupport RFC 7: Language Standards Support] (approved, 29 Mar 2021)
* Approving of Veronica Andreo as GRASS GIS PSC chair (approved, 3 Feb 2021) - See [https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20210203 minutes Feb 3, 2021]
* PSC mandates will last 6 years with 1/2 of PSC elected every 3 years (approved, 3 Feb 2021)
* PSC roles and tasks will be also renewed every 3 years (approved, 3 Feb 2021)
* When a PSC member steps down, s/he might be replaced by the next person in the previous election results ranking (approved, 3 Feb 2021)

=== 2020 ===

* [https://trac.osgeo.org/grass/wiki/PSC/Election2020 Elections 2020]
* GitHub write access to Nicklas Larsson as a new core developer (granted, 24 Dec 2020)
* GitHub write access to Tomáš Zigo as a new core developer (granted, 29 Nov 2020)
* Second payment for new GRASS GIS Hugo based web site (approved, 1 Oct 2020)
* First payment for new GRASS GIS Hugo based web site (approved, 25 Feb 2020)
* Prague 2019 Community Sprint Reimbursements (approved, 14 Jan 2020)

For older motions, see [https://trac.osgeo.org/grass/wiki/PSC/Motions the list of motions] from 2006 to 2020.

== Resources ==

*[http://lists.osgeo.org/mailman/listinfo/grass-psc PSC mailing list]
*[https://github.com/OSGeo/grass/tree/main/doc/development/rfc RFCs]

== Elections ==

* [[PSC Election 2024]] (completed in Oct. 2024)
*[https://trac.osgeo.org/grass/wiki/PSC/Election2020 PSC Election 2020] (completed in Jan. 2021)
*[https://trac.osgeo.org/grass/wiki/PSC/Election2016 PSC Election 2016] (completed in Aug. 2016)
*[https://trac.osgeo.org/grass/wiki/PSC/Election2012 PSC Election 2012] (completed in Nov. 2012)
*[https://trac.osgeo.org/grass/wiki/PSC/Creation2006 PSC created in 2006]

== Former PSC members ==

Period 2020-2024:

*'''Michael Barton''', USA
*'''Martin Landa''', Czech Republic
*'''Helena Mitasova''', USA

Period 2021-2023:

*'''Moritz Lennert''', Belgium (stepped down in 2023, replaced by '''Helmut Kudrnovsky''', Austria)

Period 2016-2020:

*'''Michael Barton''', USA
*'''Margherita Di Leo''', Italy (dileomargherita * gmail com). [http://forest.jrc.ec.europa.eu/team/person/35/detail/ Home Page] European Commission, Joint Research Centre (JRC), IT
*'''Martin Landa''', Czech Republic
*'''Moritz Lennert''', Belgium
*'''Peter Löwe''', Germany (peter DOT loewe AT gmx DOT de) [https://wiki.osgeo.org/wiki/User:Peter_Loewe Home page]. TIB Hannover, DE
*'''Helena Mitasova''', USA
*'''Markus Neteler (chair)''', Italy
*'''Anna Petrášová''', USA
*'''Vaclav Petras''', USA

Period 2012-2016:

*'''Michael Barton''', USA
*'''Hamish Bowman''', New Zealand
*'''Massimiliano Cannata''', Switzerland
*'''Moritz Lennert''', Belgium
*'''Margherita Di Leo''', Italy
*'''Martin Landa''', Czech Republic
*'''Markus Metz''', Germany
*'''Helena Mitasova''', USA
*'''Scott Mitchell''', Canada
*'''Markus Neteler (chair)''', Italy

Period 2006-2012:

*'''Michael Barton, USA
*'''Dylan Beaudette''' USA
*'''Hamish Bowman, New Zealand
*'''Massimiliano Cannata, Switzerland
*'''Brad Douglas''' (rez * touchofmadness com), USA
*'''Paul Kelly''' (paul-grass stjohnspoint co uk), UK
*'''Helena Mitasova, USA
*'''Scott Mitchell, Canada
*'''Markus Neteler (chair), Italy
*'''Maciej Sieczka''' (msieczka * sieczka org) [http://www.sieczka.org Home page], PL

=== Former chair persons ===

*Period 2016-2020: '''Markus Neteler''', Germany (neteler * osgeo org) [https://www.mundialis.de/neteler/ Home page]. mundialis, Bonn, DE
*Period 2012-2016: '''Markus Neteler''', Germany (neteler * osgeo org) [https://wiki.osgeo.org/wiki/Markus_Neteler Home page]. Trento, IT
*Period 2006-2012: '''Markus Neteler''', Germany (neteler * osgeo org) [https://wiki.osgeo.org/wiki/Markus_Neteler Home page]. Trento, IT

[[Category:PSC]]

Working with GRASS without starting it explicitly

2026-01-09T14:15:11Z

Neteler: Attempt to cleanup the page (remove old GRASS 7 cruft)

GRASS GIS modules and the import of GRASS Python packages works only in a specific environmental settings (GRASS session). This settings is ensured by starting GRASS GIS application which prepares this GRASS session for you. It is possible to set up you system in the way that the GRASS session will be always active (i.e. the GRASS startup script is not running, just the environmental settings are done). People often prefer to set up the GRASS environment in their script or program and this is what this article discuss. However, it must be noted that the the generally preferred (and easy) way is to create scripts and programs as GRASS modules which means that your don't have to bother with setting up the environment since the GRASS module should be always invoked only in GRASS session.

== GRASS sessions ==

It is possible to access GRASS modules without explicitly starting a "GRASS session". GRASS libraries require certain [https://grass.osgeo.org/grass-stable/manuals/variables.html environment variables] to be set. In fact a "GRASS session" is just a set of processes (e.g. a shell and/or GUI) which have the necessary environment settings, specifically:

* '''GISBASE''' needs to be set to the top-level directory of the GRASS installation.
* '''GISRC''' needs to contain the absolute path to a file containing settings for '''GISDBASE''', '''LOCATION_NAME''' and '''MAPSET'''.
* '''PATH''' needs to include '''$GISBASE/bin''' and '''$GISBASE/scripts'''.

If the GRASS libraries are shared libraries, the loader needs to be able to find them. This normally means that '''LD_LIBRARY_PATH''' (Linux, ...), '''DYLD_LIBRARY_PATH''' (MacOSX) or '''PATH''' (Windows) need to contain '''$GISBASE/lib''', although there are other means to the same end (e.g. on Linux, putting $GISBASE/lib (with $GISBASE replaced by its actual value) into /etc/ld.so.conf then running ldconfig).

Some libraries and modules use other variables. More information for most of them is available in the file ''$GISBASE/docs/html/variables.html''. The display libraries used by ''d.*'' commands use additional variables, which are documented along with the individual drivers.

=== Batch jobs ===

You can run GRASS scripts non-interactively from outside of a GRASS session with the GRASS_BATCH_JOB environment variable. When GRASS is started with this environment variable set it will automatically run the contents of the script given in the variable, then close the GRASS session when complete. In this way full lock-checking, GRASS variables setup, and temporary file cleaning tasks are still performed.

See the [[GRASS_and_Shell#GRASS_Batch_jobs|Batch jobs]] section of the GRASS shell-help wiki page for details.

=== Starting a GRASS session and terminating it automatically ===

A GRASS session can be started and terminated automatically with the -e flag.

Since GRASS GIS 7 you can execute commands from outside by passing the command to be executed (or a script with a collection of GRASS GIS commands) to the --exec flag:

Creating a new Location based on a geodata file's projection (-c) and exit (-e) immediately:
<source lang="bash">
grass -c elevation.tiff -e /path/to/grassdata/test1/
</source>

Linking external raster data to PERMANENT Mapset:
<source lang="bash">
grass /path/to/grassdata/test1/PERMANENT/ -e --exec r.external input=basins.tiff output=basins
grass /path/to/grassdata/test1/PERMANENT/ -e --exec r.external input=elevation.tiff output=elevation
</source>

Get statistics for one raster map:
<source lang="bash">
grass /path/to/grassdata/test1/PERMANENT/ -e --exec r.univar map=elevation
</source>

==== Start a GRASS session but do not terminate it automatically ====

Compare the rasters visually:
<source lang="bash">
grass /path/to/grassdata/test1/PERMANENT/ --exec g.gui.mapswipe first=elevation second=basins
</source>

Read more in the [https://grass.osgeo.org/grass-stable/manuals/grass.html#batch-jobs-with-the-exec-interface manual].

==== Python examples ====

For details on GRASS GIS Python programming, see also [[GRASS Python Scripting Library]].

===== Python: GRASS GIS 7 with an external library: grass-session =====

The [https://github.com/zarch/grass-session "grass-session" Python library] is an easy way to control GRASS GIS from "outside"-Python. To install the current version, run:

<source lang="bash">
# see also: https://pypi.org/project/grass-session/

pip install grass-session
# for the latest development version use:
# pip install git+https://github.com/zarch/grass-session.git
</source>

Then write
<source lang="python">
#!/usr/bin/env python
# filename: test_session.py

from grass_session import Session
from grass.script import core as gcore

# create a new location from EPSG code (can also be a GeoTIFF or SHP or ... file)
with Session(gisdb="/tmp", location="mylocation",
create_opts="EPSG:4326"):
# run something in PERMANENT mapset:
print(gcore.parse_command("g.gisenv", flags="s"))
# expected output:
# {u'GISDBASE': u"'/tmp/';",
# u'LOCATION_NAME': u"'mylocation';",
# u'MAPSET': u"'PERMANENT';",}

# create a new mapset in an existing location
with Session(gisdb="/tmp", location="mylocation", mapset="test",
create_opts=""):
# do something in the test mapset.
print(gcore.parse_command("g.gisenv", flags="s"))
# expected output:
# {u'GISDBASE': u"'/tmp/';",
# u'LOCATION_NAME': u"'mylocation';",
# u'MAPSET': u"'test';",}

</source>

The grass-session library looks at the <tt>GRASSBIN</tt> environmental variable. If the variable is not set, the library tries to use the current stable release of GRASS GIS (e.g. <tt>grass84</tt> on Linux for the 8.4 release).
For instance, to execute the previous example using a custom installation of 8.5 version, write:

<source lang="bash">
# WAY 1
# set variable "on the fly" for python call
GRASSBIN="$HOME/bin/grass85 python test_session.py"

# WAY 2
export GRASSBIN="$HOME/bin/grass85"
python3 test_session.py
{'GISDBASE': "'/tmp';", 'LOCATION_NAME': "'mylocation';", 'MAPSET': "'PERMANENT';"}
{'GISDBASE': "'/tmp';", 'LOCATION_NAME': "'mylocation';", 'MAPSET': "'test';"}
</source>

See below for a solution with docker.

====== Using 'grass-session' with PyGRASS ======

If you need to use python libraries that are using ctypes, run it like this for example:

<source lang="python">
# file: test_session_ctypes.py
import grass_session
from grass.pygrass.vector import VectorTopo

print('DONE!')
</source>

The above script will raise an exception because is not possible to dynamically import the linked library in the same process.

<source lang="bash">
$ GRASSBIN=/home/pietro/.local/bin/grass python test.py
GRASSBIN: /home/pietro/.local/bin/grass
GISBASE: /home/pietro/.local/grass
Traceback (most recent call last):
File "test.py", line 3, in <module>
from grass.pygrass.vector import VectorTopo
File "/home/pietro/.local/grass/etc/python/grass/pygrass/vector/__init__.py", line 5, in <module>
import grass.lib.gis as libgis
File "/home/pietro/.local/grass/etc/python/grass/lib/gis.py", line 23, in <module>
_libs["grass_gis."] = load_library("grass_gis.")
File "/home/pietro/.local/grass/etc/python/grass/lib/ctypes_loader.py", line 62, in load_library
return self.load(path)
File "/home/pietro/.local/grass/etc/python/grass/lib/ctypes_loader.py", line 78, in load
raise ImportError(e)
ImportError: libgrass_datetime..so: cannot open shared object file: No such file or directory
</source>

But you can set the <tt>LD_LIBRARY_PATH</tt> variable before launching the program. For instance from the command line you can define:

<source lang="bash">
$ LD_LIBRARY_PATH=/home/pietro/.local/grass/lib \
GRASSBIN=/home/pietro/.local/bin/grass \
python test_session_ctypes.py
GRASSBIN: /home/pietro/.local/bin/grass
GISBASE: /home/pietro/.local/grass
DONE!
</source>

The use of the <tt>with-statement</tt> close automatically the session.
If you have to manage more complex workflow you can manually define the opening and closing actions.
For example:

<source lang="bash">
import os

# import grass_session
from grass_session import Session

# import grass python libraries
from grass.pygrass.modules.shortcuts import general as g

# set some common environmental variables, like:
os.environ.update(dict(GRASS_COMPRESS_NULLS='1',
GRASS_COMPRESSOR='ZSTD'))

# create a PERMANENT mapset
# create a Session instance
PERMANENT = Session()
PERMANENT.open(gisdb='/tmp', location='mytest',
create_opts='EPSG:4326')

# execute some command inside PERMANENT
g.mapsets(flags="l")
g.list(type="raster", flags="m")

# exit from PERMANENT
PERMANENT.close()

# create a new mapset in the same location
user = Session()
user.open(gisdb='/tmp', location='mytest', mapset='user',
create_opts='')

# execute some command inside user
g.mapsets(flags="l")
g.list(type="raster", flags="m")

# exit from user
user.close()
</source>

===== Hint: find the path to the GRASS GIS package start script =====

Hint: in order to find the '''path to the GRASS GIS package''', launch it with <tt> --config path</tt>:

<source lang="bash">
# Linux
grass --config path
/usr/bin/grass84

# Windows
C:\>grass.bat --config path
C:\OSGeo4W\apps\grass\grass84
</source>

===== Python: GRASS GIS 8 with existing location =====

See the example in the [https://grass.osgeo.org/grass-stable/manuals/libpython/script.html#module-script.setup documentation] or the script which initializes the session and lists available raster and vector maps:

<source lang="python">
#!/usr/bin/env python

import os
import subprocess
import sys

# define GRASS data settings (adapt to your needs)
grassdata = "/home/mneteler/grassdata/"
location = "nc_spm_08_grass7"
mapset = "user1"

# Python path: we ask GRASS GIS where its Python packages are
sys.path.append(
subprocess.check_output(["grass", "--config", "python_path"], text=True).strip()
)

# Import GRASS Python bindings
import grass.script as gs

# full path to new project (formerly: location)
project = "/tmp/grassproject_epsg_25832"
gs.create_project(project, epsg="25832")

# initialize project
gs.setup.init(project)
</source>

At this point we are in a running GRASS GIS session, let's verify.

<source lang="python">
# show current GRASS GIS settings
print("GRASS GIS session: tests for PROJ, GDAL, PDAL, GRASS GIS")
print(gs.parse_command("g.gisenv", flags="s"))
</source>

Now we may also import further functionality (e.g. [https://grass.osgeo.org/grass-stable/manuals/libpython/grass.pygrass.vector.html?highlight=vectortopo VectorTopo of pygrass]):

<source lang="python">
from grass.pygrass.vector import VectorTopo
</source>

and can for example retrieve the topology of a vector map (using the [https://grass.osgeo.org/download/data/#NorthCarolinaDataset North Carolina dataset]):

<source lang="python">
test_vect = VectorTopo("zipcodes_wake")
test_vect.open(mode="r")
test_vect.num_primitive_of("point")
test_vect.num_primitive_of("line")
test_vect.num_primitive_of("centroid")
test_vect.num_primitive_of("boundary")
test_vect.close()
</source>

This should report:

<source lang="python">
>>> test_vect.num_primitive_of('point')
0
>>> test_vect.num_primitive_of('line')
0
>>> test_vect.num_primitive_of('centroid')
48
>>> test_vect.num_primitive_of('boundary')
158
</source>

==== Bash examples (GNU/Linux) ====

'''''Note: see [[GRASS_and_Shell#GRASS_Batch_jobs|GRASS Batch jobs]] for a really easy approach.'''''

Below an example of a '''~/.bash_profile''' script to set the required settings in order to access GRASS commands outside of a GRASS GIS session

<source lang=bash>
# GRASS environment
export GISBASE=/usr/local/grass
export GRASS_VERSION=""
export GRASS_VERSION="8.4"
export GISBASE="/home/mundialis/src/grass-8.4.2/dist.x86_64-pc-linux-gnu/"
export GRASS_GNUPLOT="gnuplot -persist"
export GRASS_HTML_BROWSER="htmlview"
export GRASS_LD_LIBRARY_PATH="${GISBASE}/lib"
export GRASS_PAGER="more"
export GRASS_PERL="/usr/bin/perl"
export GRASS_PROJSHARE="/usr/local/share/proj"
export GRASS_PYTHON="python"
export GRASS_SH="/bin/sh"
export GRASS_SHELL_PID="$$"

#generate GISRCRC
MYGISDBASE=$HOME/grassdata
MYLOC=nc_spm_08_grass7
MYMAPSET=user1

# Set the global grassrc file to individual file name
MYGISRC="$HOME/.grassrc.$GRASS_VERSION.$$"

echo "GISDBASE: $MYGISDBASE" > "$MYGISRC"
echo "LOCATION_NAME: $MYLOC" >> "$MYGISRC"
echo "MAPSET: $MYMAPSET" >> "$MYGISRC"
echo "GRASS_GUI: text" >> "$MYGISRC"

# path to GRASS settings file
export GISRC=$MYGISRC
export GRASS_PYTHON=python
export GRASS_MESSAGE_FORMAT=plain
export GRASS_TRUECOLOR=TRUE
export GRASS_TRANSPARENT=TRUE
export GRASS_PNG_AUTO_WRITE=TRUE
export GRASS_GNUPLOT='gnuplot -persist'
export GRASS_WIDTH=640
export GRASS_HEIGHT=480
export GRASS_HTML_BROWSER=firefox
export GRASS_PAGER=cat

#For the temporal modules
export TGISDB_DRIVER=sqlite
export TGISDB_DATABASE=$MYGISDBASE/$MYLOC/PERMANENT/tgis/sqlite.db

# for fun, we can even set the shell prompt to contain a hint on GRASS GIS env being active
export PS1="[\u@\h \W G-$GRASS_VERSION]$ "

# system vars
export PATH="$GISBASE/bin:$GISBASE/scripts:$PATH"
export LD_LIBRARY_PATH="$GISBASE/lib"
export GRASS_LD_LIBRARY_PATH="$LD_LIBRARY_PATH"
export PYTHONPATH="$GISBASE/etc/python:$PYTHONPATH"
export MANPATH=$MANPATH:$GISBASE/man

# test a command
g.list rast
v.info zipcodes_wake
</source>

The above script will allow GRASS commands to be used anywhere. Furthermore, if the '''~/.Xsession''' sources the bash startup scripts, the settings aren't limited to interactive shells, but also work for e.g. M-! in XEmacs). Each interactive shell gets a separate "session" (i.e. a separate $GISRC file), while GUI programs share a common session.

Note, however, that '''~/.bash_profile''' is a personal initialization startup script and, thus, read during the login process. Any modifications to it will be read after (re-)login or explicitly sourcing it.

At the end of the ~/.bash_profile file, the following lines can be added to ensure no duplication of entries in the PATH variable.

<source lang=bash>
PATH=`awk -F: '{for(i=1;i<=NF;i++){if(!($i in a)){a[$i];printf s$i;s=":"}}}'<<<$PATH`
PYTHONPATH=`awk -F: '{for(i=1;i<=NF;i++){if(!($i in a)){a[$i];printf s$i;s=":"}}}'<<<$PYTHONPATH`
</source>

=== Important notes ===

Launching a grassXY session could still permit access on GRASS modules of the version that is set with the above script. The reason being is that grassXY scripts (e.g.: grass84) prepend the GRASS directories to '''PATH''', '''LD_LIBRARY_PATH''', etc. They won't remove any entries which are already there. A solution to this is to ''switch'' between GRASS versions by using a script like the following:

<source lang="bash">
strippath()
{
(
oldpath="$1"
newpath=
IFS=:
for dir in $oldpath ; do
case "${dir}" in
*grass*)
;;
*)
newpath="$newpath:$dir"
;;
esac
done
echo "${newpath#:}"
)
}

PATH=`strippath $PATH`

export GISBASE=$PWD/dist.i686-pc-linux-gnu
export PATH="$GISBASE/bin:$GISBASE/scripts:$PATH"
export LD_LIBRARY_PATH="$GISBASE/lib"
export PYTHONPATH="$GISBASE/etc/python"
</source>

'''Note: the above script needs to be "source"d; executing it won't work. It might also require some adjustments (e.g. the ''GISBASE'' variable).'''

Using normal grass sessions commands are recorded in '''$GISDBASE/$LOCATION_NAME/$MAPSET/.bash_history'''. While working with "pure" bash, shell entries go in '''~/.bash_history'''. Merging existing "grass-bash_history(-ies)" with the bash history log, would probably be not a good idea. Perhaps it is wise(r) to use normal GRASS sessions when working on real projects. Nevertheless, it is upon the users preferences and expertise level to decide what is best.

=== Hints and troubleshooting ===

Some hints for MS Windows users:

# The Python interpreter (python.exe) needs to be in the PATH
# Python needs to be associated with the .py extension
# PATHEXT needs to include .py if you want to be able to omit the extension

When everything works well, the installer should take care of all of these.

To manage parallel sessions on Linux, use process ID (PID) as lock file number and set the GIS_LOCK variable, for example

export GIS_LOCK=$$

in Bash.

=== References ===
* Instructions and discussion on [http://n2.nabble.com/can-I-access-mapset-outside-of-grass-by-using-python-td3405902.html#a3405902 how to access GRASS mapsets outside of a GRASS session] in the grass-user mailing list.
* removing duplicate entries in $PATH taken from [http://chunchung.blogspot.com/2007/11/remove-duplicate-paths-from-path-in.html]

== GRASS databases ==

(project file structure)

=== Minimal mapsets ===

within a functional LOCATION (see below) the minimal mapset is a subdirectory of the MAPSET's name, containing a WIND file. The WIND file can simply be copied from PERMANENT/DEFAULT_WIND. Optionally you can put a VAR file in there too to define the default database driver to use.

* You can create a new mapset when starting GRASS with the -c flag. e.g.
grass -c /path/to/location/new_mapset_name

=== Minimal locations ===

Within the GISDATABASE (which is simply a subdirectory some where), the minimum LOCATION consists of a directory giving the LOCATION its name, which in turn contains a PERMANENT subdirectory for the PERMANENT mapset. The PERMANENT mapset contains a few special files that regular mapsets don't. These are:
; PROJ_INFO: contains the location's projection information
; PROJ_UNITS: contains the location's map units definition
; DEFAULT_WIND: the default region (WINDow file). The format is identical to the WIND files created by g.region
; WIND: (optional?)

* see also {{src|demolocation}} in the GRASS source code

== See also ==
* [[GRASS_and_Shell#GRASS_Batch_jobs|GRASS Batch jobs]]

[[Category: FAQ]]
[[Category: Linking to other languages]]
[[Category: bash]]
[[Category:Scripting]]
[[Category: Python]]

PSC Meeting 2025-11-14

2025-12-13T15:37:02Z

Neteler: /* Minutes */

== Participants ==

* Anna Petrasova
* Huidae Cho
* Linda Karlovska
* Markus Neteler
* Nicklas Larsson
* Paulo van Breugel
* Vaclav Petras
* Veronica Andreo

== Agenda ==

The topics proposed are:

* Report from NumFOCUS Project Summit (VP)
* GRASS Wiki under DDOS attack, see https://discourse.osgeo.org/t/grass-wiki-under-ddos-attack/150717
* New wiki page: [[Organizing GRASS Contributor Events]]
* GRASS Meeting 2026 - Luca's proposal
* Upcoming releases:
** Release 8.4.2 (due to relevant [https://github.com/OSGeo/grass/compare/8.4.1...releasebranch_8_4 fixes]; the branch-CI is also functional again) - [https://github.com/OSGeo/grass/milestone/27 milestone]
** Release 8.5.0 - [https://github.com/OSGeo/grass/milestone/22 milestone]
* Reimburse Alen for stickers he bought to take to NZ

== Minutes ==

* Report from NumFOCUS Project Summit:
** VP participated of the NumFOCUS projects summit; there were not many other projects attending.
** There are calls for small grants (USD 10K per project per year), that we should apply for, and ideally use them for development.
** It seems we need to apply as a project, but it is not clear who submits. In any case, the person interested in the money should lead the effort. See: https://numfocus.org/programs/small-development-grants.
** We had a meeting with them on Tue 18th, but AP will ask them to move it because neither VP nor VA can attend. New date: Dec 10th, 2025.

* GRASS wiki under attack by botnet:
** MN set up countermeasures on the server, instructions to be dumped in our infrastructure shared doc
** Not everyone has access to that doc, so we shall review and discuss our shared folder and files access “policy”.

* New wiki page on organizing GRASS events:
** https://grasswiki.osgeo.org/wiki/Organizing_GRASS_Contributor_Events

* GRASS meeting San Michele 2026:
** See [https://lists.osgeo.org/pipermail/grass-psc/2025-September/003054.html Luca's proposal].
** Nicklas is not available for any of the proposed dates.
** AP and VP depend on the green card, if they get it on time, any of the dates are fine.
** Paulo: 50% with the second date.
** HC: probably the second date.
** MN and VA: any date fine for now.
** Linda: new baby coming! Congrats!

* Release 8.4.2:
** VP and MN will agree on a date soon to do the release together.
** Edouard will be invited, too.

* Release 8.5:
** It will have CMake in the source code as experimental feature to try for users who compile code themselves (but extensions won’t work for them).
** FHS won’t work with CMake yet.
** It’s a matter of communication about what’s there in the source code. Binaries will be with autotools, so addons will work.
** Blockers: there’s an issue with r.blend and something with r.patch with vrt and nprocs > 1 (the latter found by Metz, but still unreported)
** New python API, VP will call for a webinar on it by mid-dec, to show how it works and collect some feedback, too.
** JSON stuff and mkdocs is in good shape to go.
** Jupyter notebook PR needs to be reviewed, it does not work in windows, but this is not a blocker, we can mark it as experimental.
** Drop support for PROJ < 8 and GDAL < 3? Nicklas created issues to get feedback, it could be done before the release. See [https://github.com/OSGeo/grass/issues/6628 #6628] and [https://github.com/OSGeo/grass/issues/6629 #6629].

* Motion proposed and passed to reimburse Alen for the stickers. VP will contact Michael Smith, so Alen gets reimbursed.

* Plan extraordinary meeting - PSC + Luca to plan 2026 budget + community meeting when the call for OSGeo budget is out.
** VP proposal: include an item to promote GRASS in other than FOSS4G conferences.

[[Category:PSC]]

GRASS Citation Repository

2025-12-13T15:31:46Z

Neteler: Update versions

== How to cite GRASS GIS ==

Please cite GRASS when using the software in your work. Here are some choices depending on the version used and the type of citation:

* GRASS GIS Manual citations,
* Peer reviewed general GRASS GIS articles,
* Books,
* Topic oriented citations.

Please select below:

=== GRASS GIS Manual citations ===

DOI (for all versions, shows latest release on top): [https://doi.org/10.5281/zenodo.5176030 10.5281/zenodo.5176030]

* '''[https://www.fair4g.org/grass.html Overview of all DOI-based references to GRASS in scientific publications (according to CrossRef)]'''
* '''[https://scholar.google.com/citations?user=gJ0ZB0cAAAAJ Overview of all references to GRASS in scientific publications (according to Google Scholar)]'''

Software:
* GRASS Development Team, 2025. Geographic Resources Analysis Support System (GRASS) Software, Version 8.4. Open Source Geospatial Foundation. Electronic document: https://grass.osgeo.org, DOI: [https://doi.org/10.5281/zenodo.5176030 10.5281/zenodo.5176030]
* GRASS Development Team, 2020. Geographic Resources Analysis Support System (GRASS) Software, Version 7.8. Open Source Geospatial Foundation. Electronic document: https://grass.osgeo.org, DOI: [https://doi.org/10.5281/zenodo.5176030 10.5281/zenodo.5176030]
* GRASS Development Team, 2015. Geographic Resources Analysis Support System (GRASS) Software, Version 6.4. Open Source Geospatial Foundation. Electronic document: https://grass.osgeo.org, DOI: [https://doi.org/10.5281/zenodo.5176030 10.5281/zenodo.5176030]

Programmer's manual:
* GRASS Development Team, 2025. Geographic Resources Analysis Support System (GRASS 8) Programmer's Manual. Open Source Geospatial Foundation Project. Electronic document: https://grass.osgeo.org/programming8/
* GRASS Development Team, 2020. Geographic Resources Analysis Support System (GRASS 7) Programmer's Manual. Open Source Geospatial Foundation Project. Electronic document: https://grass.osgeo.org/programming7/
* GRASS Development Team, 2015. Geographic Resources Analysis Support System (GRASS 6) Programmer's Manual. Open Source Geospatial Foundation Project. Electronic document: https://grass.osgeo.org/programming6/

Related BibTeX entry:
<pre>
@Manual{GRASS_GIS_software,
title = {Geographic Resources Analysis Support System (GRASS GIS) Software, Version 8.4},
author = {{GRASS Development Team}},
organization = {Open Source Geospatial Foundation},
year = {2025},
url = {https://grass.osgeo.org},
doi = {https://doi.org/10.5281/zenodo.5176030}
}
</pre>

=== Historical manual pages ===
(Search US Army documents at https://discover.dtic.mil/products-services/)

* Predicting Database Requirements for Geographic Information Systems in the Year 2000: Long-Term Design Issues for GRASS (1992): https://apps.dtic.mil/sti/pdfs/ADA256862.pdf
* Geographic Resources Analysis Support System (GRASS) Version 4.0 User's Reference Manual (1992): https://apps.dtic.mil/sti/tr/pdf/ADA255218.pdf
* GRASS/GIS Implementation Guide (1989): https://apps.dtic.mil/sti/tr/pdf/ADA214623.pdf
* r.mapcalc: An Algebra for GIS and Image Processing (1984): https://apps.dtic.mil/sti/pdfs/ADA283923.pdf
* FORT HOOD GEOGRAPHIC INFORMATION SYSTEM: PILOT SYSTEM DEVELOPMENT AND USER INSTRUCTIONS (1983): https://apps.dtic.mil/sti/pdfs/ADA130618.pdf

=== GRASS GIS Addon Manual citations ===

Hint: when citing addons, you can simply use "grass-stable" in the URL which is auto-expanded to the latest version (e.g. grass82/). Like this the latest addon version is found.

Example:
* M. Lennert and GRASS Development Team, 2017: “Addon i.segment.stats. Geographic resources analysis support system (GRASS) software, version 7.2”, https://grass.osgeo.org/grass7/manuals/addons/i.segment.stats.html (1 June 2017)

=== Peer reviewed general GRASS GIS articles ===

* Neteler, M., Bowman, M.H., Landa, M., Metz, M., 2012. <i>GRASS GIS: A multi-purpose open source GIS</i>. Environ Model Soft 31, 124–130. ([https://dx.doi.org/10.1016/j.envsoft.2011.11.014 DOI] | [https://web.archive.org/web/20120424040115/https://gis.cri.fmach.it/uploads/neteler_grass_env_model_software.pdf PDF])
* Neteler, M., Bowman, M.H., Landa, M., Metz, M. (2012) "GRASS GIS: A multi-purpose open source GIS." Environmental Modelling & Software. Vol 31, pp. 124–130. ([https://dx.doi.org/10.1016/j.envsoft.2011.11.014 DOI] | [https://web.archive.org/web/20120424040115/https://gis.cri.fmach.it/uploads/neteler_grass_env_model_software.pdf PDF])

Related Bibtex entry:
<pre>
@article{neteler2012grass,
title={{GRASS GIS: a multi-purpose Open Source GIS}},
author={Neteler, M. and Bowman, M.H. and Landa, M. and Metz, M.},
journal={Environmental Modelling \& Software},
year={2012},
volume = {31},
pages = {124--130},
publisher={Elsevier},
doi = "10.1016/j.envsoft.2011.11.014"
}
</pre>

=== Books ===
* See https://grass.osgeo.org/learn/books/

=== Topic oriented citations ===
* see [[Citations for specific modules]]
* Citations of [[GRASS in the wild]] (add your publications here)

=== Historic citations ===

<font color="grey">
* GRASS Development Team, 2021. GRASS GIS 7 Programmer's Manual. Open Source Geospatial Foundation, USA. Electronic document: https://grass.osgeo.org/programming7/
* GRASS Development Team, 2016. GRASS 6 Programmer's Manual. Open Source Geospatial Foundation, USA. Electronic document: https://grass.osgeo.org/programming6/
* GRASS Development Team, 2012. GRASS 6.4 Users Manual. Open Source Geospatial Foundation, USA. Electronic document: https://grass.osgeo.org/grass64/manuals/
* GRASS Development Team, 2007. GRASS 6.2 Users Manual. ITC-irst, Trento, Italy. Electronic document: https://grass.osgeo.org/grass62/manuals/
* GRASS Development Team, 2002. GRASS 5.0 Users Manual. ITC-irst, Trento, Italy. Electronic document: https://grass.osgeo.org/grass57/manuals/html57_user/
* U.S. Army CERL, 1993. GRASS 4.1 Reference Manual. U.S. Army Corps of Engineers, Construction Engineering Research Laboratories, Champaign, Illinois, 1-425.
* Westervelt, J.D., Shapiro, M., Goran, W.D., Gerdes, D.P. (1992). Geographic Resources Analysis Support System (GRASS) Version 4.0 User's Reference Manual (No. CERL-ADP-N-87/22). CONSTRUCTION ENGINEERING RESEARCH LAB (ARMY) CHAMPAIGN IL. (PDF: https://apps.dtic.mil/sti/pdfs/ADA255218.pdf)
* Shapiro, M., Westervelt, J., Gerdes, D., Higgins, M., & Larson, M. (1989). GRASS 3.0 programmer's manual (No. CERL-ADP-N-89/14). CONSTRUCTION ENGINEERING RESEARCH LAB (ARMY) CHAMPAIGN IL. (PDF: https://apps.dtic.mil/sti/pdfs/ADA252461.pdf)
* ''Missing: Manuals of GRASS 1.0 and 2.0 - please submit to us!''
</font>

* Newsletter citations
** GRASSHopper CERL, https://grass.osgeo.org/about/history/
** [[Newsletter citations Vol1]] 2004
** [[Newsletter citations Vol2]] 2005
** [[Newsletter citations Vol3]] 2005
** [[Newsletter citations Vol4]] 2006

== Helpful tools and GRASS related bibliographic searches ==
* [https://grass.osgeo.org/grass-stable/manuals/addons/g.citation.html g.citation add-on module]
* Google Scholar:
** [https://scholar.google.com/scholar?q=GRASS+GIS Search for "GRASS GIS"] (activate BibTex export in "Scholar preferences")
** The virtual [https://scholar.google.com/citations?user=gJ0ZB0cAAAAJ GRASS Development Team] - GRASS GIS related papers
* [https://www.citeulike.org CiteULike] - [https://www.citeulike.org/tag/grass Search for "GRASS"]
* [https://www.scripps.edu/~cdputnam/software/bibutils/ Bibutils] bibliography conversion utilities
* [https://gbib.seul.org Gbib BibTeX editor] for GTK+Gnome
* [https://jabref.sourceforge.net/ JabRef] Multi-platform, multi-format bibliography tool
* [https://www.zotero.org/groups/gis Zotero citation manager GIS group] - with all known GRASS GIS and other GIS related references
* [[GRASS in the wild‎]]

[[Category:Citations]]
[[Category:Documentation]]
[[Category:FAQ]]

WPS

2025-12-01T19:53:41Z

Neteler: Update of various URLs and --wps-process-description XML output

'''GRASS based OGC Web Processing Service (WPS) standard implementations'''

The OGC Web Processing Service (WPS) {{wikipedia||Web Processing Service}} interface standard provides rules for standardizing how inputs and outputs (requests and responses) for invoking geospatial processing services as a web service. GRASS GIS can be used as backend in several WPS service frameworks.

== Linking to WPS server ==

A framework has been developed to make the integration of GRASS GIS in WPS server as easy as possible. The
framework is called '''wps-grass-bridge''' and is available here:
* '''wps-grass-bridge''': https://code.google.com/archive/p/wps-grass-bridge/
This framework support currently PyWPS, ZOO WPS and is used by 52North WPS server. Many GRASS GIS modules can be attached out of the box.

There are currently several '''other WPS implementations''' which use GRASS as GIS backbone:
* '''PyWPS''': https://pywps.org/
** PyWPS and wps-grass-bridge connector: https://code.google.com/archive/p/wps-grass-bridge/wikis/PyWPS_Integration.wiki
** [https://pywps.org/gallery/ Gallery] (live examples)
** PyWPS and GRASS: https://pywps-3.readthedocs.io/special/grass.html
* '''WPS by 52N''': https://52north.github.io/WPS/
** Connecting to GRASS out of the box: https://github.com/52North/WPS/tree/dev/52n-wps-grass
** Backend: https://mvnrepository.com/artifact/org.n52.wps/52n-wps-grass
** 52N-WPS-GRASS [http://geoprocessing.demo.52north.org:8080/wps/WebProcessingService?REQUEST=GetCapabilities&SERVICE=WPS&VERSION=1.0.0 Demo]
* '''ZOO project''' - Open OSW Platform: https://zoo-project.org/
** [https://zoo-project.org/code/services/ ZOO-WPS with GRASS and QGIS]
* R and WPS: [http://gsif.r-forge.r-project.org/WPS.html WPS class]

== Inside GRASS ==

In GRASS, the WPS process description can be automatically generated with the option '--wps-process-description'.
See [https://lists.osgeo.org/pipermail/grass-dev/2009-November/047133.html announcement].

Example:

r.grow --wps-process-description

<source lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<wps:ProcessDescriptions xmlns:wps="http://www.opengis.net/wps/1.0.0"
xmlns:ows="http://www.opengis.net/ows/1.1"
xmlns:xlink="http://www.w3.org/1999/xlink"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.opengis.net/wps/1.0.0
http://schemas.opengis.net/wps/1.0.0/wpsDescribeProcess_response.xsd"
service="WPS" version="1.0.0" xml:lang="en-US">
<ProcessDescription wps:processVersion="1" storeSupported="true" statusSupported="true">
<ows:Identifier>r.grow</ows:Identifier>
<ows:Title>Generates a raster map layer with contiguous areas grown by one cell.</ows:Title>
<ows:Abstract>https://grass.osgeo.org/grass-devel/manuals/r.grow.html</ows:Abstract>
<ows:Metadata xlink:title="raster" />
<ows:Metadata xlink:title="distance" />
<ows:Metadata xlink:title="proximity" />
<DataInputs>
<Input minOccurs="1" maxOccurs="1">
<ows:Identifier>input</ows:Identifier>
<ows:Title>Name of input raster map</ows:Title>
<ComplexData maximumMegabytes="2048">
<Default>
<Format>
<MimeType>image/tiff</MimeType>
</Format>
</Default>
<Supported>
<Format>
<MimeType>image/tiff</MimeType>
</Format>
<Format>
<MimeType>image/geotiff</MimeType>
</Format>
[...]
<Format>
<MimeType>application/x-netcdf</MimeType>
</Format>
</Supported>
</ComplexData>
</Input>
<Input minOccurs="0" maxOccurs="1">
<ows:Identifier>radius</ows:Identifier>
<ows:Title>Radius of buffer in raster cells</ows:Title>
<LiteralData>
<ows:DataType ows:reference="xs:float">float</ows:DataType>
<ows:AnyValue/>
<DefaultValue>1.01</DefaultValue>
</LiteralData>
</Input>
[...]
<Input minOccurs="0" maxOccurs="1">
<ows:Identifier>-m</ows:Identifier>
<ows:Title>Radius is in map units rather than cells</ows:Title>
<LiteralData>
<ows:DataType ows:reference="xs:boolean">boolean</ows:DataType>
<ows:AllowedValues>
<ows:Value>true</ows:Value>
<ows:Value>false</ows:Value>
</ows:AllowedValues>
<DefaultValue>false</DefaultValue>
</LiteralData>
</Input>
[...]
</Input>
</DataInputs>
<ProcessOutputs>
<Output>
<ows:Identifier>output</ows:Identifier>
<ows:Title>Name for output raster map</ows:Title>
<ComplexOutput>
<Default>
<Format>
<MimeType>image/tiff</MimeType>
</Format>
</Default>
<Supported>
<Format>
<MimeType>image/tiff</MimeType>
</Format>
<Format>
<MimeType>image/geotiff</MimeType>
</Format>
[...]
</Format>
<Format>
<MimeType>application/netcdf</MimeType>
</Format>
<Format>
<MimeType>application/x-netcdf</MimeType>
</Format>
</Supported>
</ComplexOutput>
</Output>
</ProcessOutputs>
</ProcessDescription>
</wps:ProcessDescriptions>
</source>

== WPS workflow idea ==

External raster maps can directly be linked into GRASS with {{cmd|r.external}} which saves time and disk space. Additionally,
there is no more need to store results in the internal GRASS format - with {{cmd|r.external.out}} the resulting maps are directly written to a GDAL supported format.

'''Preparations'''

GRASS can be used in an automated way by just defining a set of variables. See here for [[GRASS_and_Shell#Setting_the_variables|GRASS and Shell]] settings and [[GRASS_and_Python#Creating_Python_scripts_that_call_GRASS_functionality_from_outside|GRASS and Python]].

'''Data flow example'''

The script content could be looking like this:

<source lang="bash">
# register (rather than import) a GeoTIFF file in GRASS GIS:
r.external input=terra_lst1km20030314.LST_Day.tif output=modis_celsius

# define output directory for files resulting from subsequent calculations:
r.external.out directory=$HOME/gisoutput/ format="GTiff"

# perform calculations (here: extract pixels > 20 deg C)
# store output directly as GeoTIFF file, hence add the .tif extension:
r.mapcalc "warm.tif = if(modis_celsius > 20.0, modis_celsius, null() )"

# cease GDAL output connection and turn back to write standard GRASS raster files:
r.external.out -r

# use the result elsewhere
qgis $HOME/gisoutput/warm.tif
</source>

== References ==

* List of [https://scholar.google.com/scholar?hl=en&q=%2Bgrass+%2Bgis+%2Bwps&as_sdt=2001&as_ylo=&as_vis=0 GRASS-WPS articles]
* [https://www.youtube.com/watch?v=zCnax9w1bCs PyWPS GRASS GIS 7 and QGIS with WPS plugin in action]
* [https://code.google.com/archive/p/wps-grass-bridge/wikis/PyWPS_Integration.wiki PyWPS integration]

Videos:
* [https://www.youtube.com/watch?v=zCnax9w1bCs PyWPS GRASS GIS 7 and QGIS with WPS plugin in action]
* [https://www.youtube.com/watch?v=jg2pb_Xjq8Y Development of an Open Cloud GIS with GRASS GIS, PyWPS, the wps-grass-bridge and QGIS]

== Historical note: GRASSLinks as a precursor to WPS ==

* GRASSLinks was originally developed from 1994-98 by Dr. Susan Huse at the Research Program in Environmental Planning and GIS (REGIS), at the University of California, Berkeley. This is claimed to be the first fully functional online GIS package offering public domain access to environmental and geographical data.
* [http://uspest.org/glinks35/ OSU IPPC GRASSLinks 3.5beta: A web interface for GRASS GIS version 5.x]

[[Category:Development]]
[[Category:OGC]]
[[Category:Linking to other languages]]

PSC Meeting 2025-11-14

2025-11-14T11:31:42Z

Neteler: +GRASS Wiki under DDOS attack

== Agenda ==

The topics proposed are:

* Report from NumFOCUS Project Summit (VP)
* GRASS Wiki under DDOS attack, see https://discourse.osgeo.org/t/grass-wiki-under-ddos-attack/150717
* New wiki page: [[Organizing GRASS Contributor Events]]
* GRASS Meeting 2026 - Luca's proposal
* Upcoming releases:
** Release 8.4.2 (due to relevant [https://github.com/OSGeo/grass/compare/8.4.1...releasebranch_8_4 fixes]; the branch-CI is also functional again) - [https://github.com/OSGeo/grass/milestone/27 milestone]
** Release 8.5.0 - [https://github.com/OSGeo/grass/milestone/22 milestone]
* Reimburse Alen for stickers he will take to NZ

[[Category:PSC]]

PSC Meeting 2025-11-14

2025-11-11T12:39:13Z

Neteler: /* Agenda */

== Agenda ==

The topics proposed are:

* Report from NumFOCUS Project Summit (VP)
* New wiki page: [[Organizing GRASS Contributor Events]]
* GRASS Meeting 2026 - Luca's proposal
* Upcoming releases:
** Release 8.4.2 (due to relevant [https://github.com/OSGeo/grass/compare/8.4.1...releasebranch_8_4 fixes]; the branch-CI is also functional again) - [https://github.com/OSGeo/grass/milestone/27 milestone]
** Release 8.5.0 - [https://github.com/OSGeo/grass/milestone/22 milestone]
* Reimburse Alen for stickers he will take to NZ

[[Category:PSC]]

Compile and Install

2025-10-02T09:39:37Z

Neteler: Attempt to cleanup the wx package names mess in Mint

'''Disclaimer''': This page explains how to turn the GRASS source code into an installable binary package ("compilation") for different operating systems. If you just want to get ready-to-use binaries, go [https://grass.osgeo.org/download/ here], otherwise read on...

== How to do compilation and installation of GRASS? ==

Here we explain the procedure to compile GRASS from GitHub, but it also applies to official GRASS 8 releases.

''For installation of precompiled binary packages, see the main [[Installation Guide]].''

For detailed information on compilation, please see the [https://github.com/OSGeo/grass/blob/main/INSTALL.md INSTALL] file in the source code.

=== Prerequisites ===

==== Extra libraries ====
GRASS needs at least two extra libraries: PROJ and GDAL/OGR. It is recommended to download them as ready-to-use packages for your software platform (Linux distribution, Windows, Mac...).

Other libraries needed to run GRASS are listed on the [https://github.com/OSGeo/grass/blob/main/REQUIREMENTS.md requirements page].

To compile, you will also need the respective "-devel" packages; see below for details.

==== Download GRASS source code ====

First, [https://grass.osgeo.org/download/ download the GRASS source code].

=== Generic Compilation and installation procedure ===

* It is wise that compilation processes are carried out as a normal user: If you want to get the source code in a place where you do not have write permissions (e.g. in /usr/local/src/) just follow this:
cd /usr/local/src/
su -c 'mkdir grass8'
su -c 'chown yourlogin:yourgroup grass8'

Otherwise if you have permissions just continue as a normal user:
mkdir $HOME/src
cd $HOME/src/
git clone https://github.com/OSGeo/grass.git grass_main

* run configure with parameters to adapt the compile process to your own system. To see what options can be passed to it, run:
./configure --help | less


It may (!) look like this:

./configure \
--with-cxx \
--with-sqlite \
--with-python \
--with-geos \
--with-gdal=/usr/bin/gdal-config \
--with-cairo --with-cairo-ldflags=-lfontconfig \
--with-freetype \
--with-freetype-includes=/usr/include/freetype2 \
--with-proj --with-proj-share=/usr/share/proj

You may have to explicitly state the path for certain packages (i.e., gdal). The Unix 'locate' command will come in handy for finding the path of the package you need (you may have to run locate as root ex: sudo locate gdal-config).

Please note that the paths mentioned may widely vary due to the distribution used.
See [[Compile_and_Install#Platform_Specific_Notes|Platform Specific Notes]] below.

Depending on your needs it may be a good idea to include debugging hooks.
: See [[GRASS_Debugging#Compile_Time_Setup]].
CFLAGS="-ggdb -Wall -Werror-implicit-function-declaration" ./configure ...

At the end of configuration process you should get report not much different from this:

GRASS is now configured for: x86_64-pc-linux-gnu

Source directory: /home/user/software/grass_main
Build directory: /home/user/software/grass_main
Installation directory: ${prefix}/grass84
Startup script in directory:${exec_prefix}/bin
C compiler: gcc -O2 -march=native -std=gnu99 -fexceptions -fstack-protector -m64 -fdiagnostics-color
C++ compiler: c++ -g -Wall
Building shared libraries: yes
OpenGL platform: X11

MacOSX application: no
MacOSX architectures:
MacOSX SDK:

BLAS support: yes
BZIP2 support: no
C++ support: yes
Cairo support: yes
DWG support: no
FFTW support: yes
FreeType support: yes
GDAL support: yes
GEOS support: yes
[...]

* Let's compile it (takes a little while...)!
make -j2
* At the end, you should get report not much different from this:
----------------------------------------------------------------------
Following modules are missing the 'description.html' file in src code:
----------------------------------------------------------------------
GRASS compilation log
-------------------------
Started compilation: Mon 19 Aug 2024 10:47:57 PM CEST
--
Errors in:
No errors detected.
--
Finished compilation: Mon 19 Aug 2024 10:55:12 PM CEST
(In case of errors please change into the directory with error and run 'make')

* If there is any error, change directory to directory with error and run "make" again. Report occurring bug to GRASS mailing list
* Once the installation process is finished, you're ready to install GRASS system wide.
su -c 'make install'
* enjoy GRASS:
grass

=== What else? ===

If you want to use [https://www.qgis.org QGIS], then also compile the GRASS-GDAL/OGR plugin. This is also useful to access your GRASS-data
from other application using GDAL/OGR like [[R_statistics/ R]].
* [[Compile and install GRASS and QGIS with GDAL/OGR Plugin]] (enables QGIS to read GRASS data directly)

=== Compile and install GDAL-GRASS plugin ===

* See [[Compile and install GDAL-GRASS plugin]]

=== Platform Specific Notes ===

==== Linux ====

Linux comes in various flavours, i.e. distributions.

===== Distribution related packaging =====

Examples:

* Archlinux: https://aur.archlinux.org/packages/grass
* Centos: https://src.fedoraproject.org/rpms/grass
* Debian: https://trac.osgeo.org/grass/wiki/DebianUbuntuPackaging
* EPEL: https://src.fedoraproject.org/rpms/grass
* Fedora: https://src.fedoraproject.org/rpms/grass
* Ubuntu: https://trac.osgeo.org/grass/wiki/DebianUbuntuPackaging

===== Alpine Linux =====

<source lang="bash">
# install compiler tools and libraries
apk add build-base bzip2-dev cairo-dev fftw-dev freetype-dev g++ gcc gdal-dev geos-dev git \
gnutls-dev libc6-compat libjpeg-turbo-dev libpng-dev make openjpeg-dev openblas-dev \
postgresql-dev proj-dev python3-dev py3-numpy-dev sqlite-dev tar tiff-dev unzip vim \
wget zip zstd-dev

# install needed tools and libraries when using GRASS
apk add attr bash bison bzip2 cairo curl fftw flex freetype gdal gdal-tools gettext geos gnutls \
jsoncpp libbz2 libexecinfo libjpeg-turbo libpng libunwind musl musl-utils ncurses openjpeg \
openblas py3-numpy py3-pillow py3-six postgresql proj-datumgrid proj-util sqlite sqlite-libs \
subversion tiff zstd zstd-libs

# get source code
cd ~
wget -c https://grass.osgeo.org/grass88/source/snapshot/grass-8.4.git_src_snapshot_latest.tar.gz

# unpack
tar xvfz grass-8.4.git_src_snapshot_latest.tar.gz
rm -f grass-8.4.git_src_snapshot_latest.tar.gz

# change into source code (update path name as needed)
cd grass-8.4.git_src_snapshot_2021_05_01/

# minimal configuration
./configure \
--with-cxx \
--with-gdal=/usr/bin/gdal-config \
--with-proj --with-proj-share=/usr/share/proj \
--with-geos \
--with-sqlite \
--without-nls \
--without-wxwidgets \
--without-fftw \
--without-cairo \
--without-freetype \
--without-opengl \
--without-odbc

# compilation
nice make -j2
</source>

===== Archlinux =====
You can install GRASS for Archlinux distribution based like Archlinux, Manjaro, EndeavourOS ...

* <big>'''Easiest method : use a prebuilt package using arch4edu repository'''</big>
''"Arch4edu is a community repository for Arch Linux and Arch Linux ARM that strives to provide the latest versions of most software used by college students."''

1. Add Arch4edu repository. Follow instructions from official documentation:

https://github.com/arch4edu/arch4edu/wiki/Add-arch4edu-to-your-Archlinux

2. Refresh packages list with

pacman -Syyu

3. Install GRASS package

pacman -S grass

* <big>'''Advanced method : use AUR (Arch User Repository) package'''</big>
Up-to-date links to Archlinux GRASS PKGBUILDs are on Arch User Repository.
PKGBUILD downloads and builds automatically sources from https://grass.osgeo.org/download/software/linux/.

You can use an AUR helper like ''pamac'', ''yay'', among others ... More info through this link https://wiki.archlinux.org/title/AUR_helpers

Exemple with ''yay'':
yay -S grass

* <big>'''Expert method : compile from source code'''</big>
If you want to compile it yourself, you could follow steps below :

''(As an alternative it is recommended to download PKGBUILD from AUR and then customize to your needs)''

Install dependencies :
pacman -S bzip2 cairo fftw fontconfig freetype2 gcc-libs gdal geos glibc glu libpng libtiff libx11 libgl netcdf pdal proj python-gdal python-numpy python-pillow python-wxpython readline zlib zstd

Download and extract sources : https://grass.osgeo.org/download/software/sources/

We can now start building GRASS

export PATH=~/usr/bin:$PATH && \
./configure \
--with-freetype-includes=/usr/include/freetype2 \
--with-wxwidgets \
--with-readline \
--with-pthread \
--with-netcdf \
--with-nls \
--with-geos \
--with-postgres \
--with-pdal=/usr/include/pdal \
--with-bzlib \
--with-zstd

Now let's compile and install it

make
make install

It's done, you can enjoy GRASS in Arch, just type "grass" in the terminal to launch it or look for grass in your menu.

===== Generic procedure for Debian-based distributions (Ubuntu, ...) =====

WORK IN PROGRESS

1. Install official GRASS package

sudo apt install grass grass-dev

2. Enable source code download

# do backup first
sudo cp /etc/apt/sources.list /etc/apt/sources.list.orig
sudo sed -i '/^#\sdeb-src /s/^# *//' /etc/apt/sources.list

3. Install GRASS dependencies

sudo apt build-dep grass

4. Download GRASS source code

git clone https://github.com/osgeo/grass

5. Compile GRASS from source code

cd grass

Configure:

grass --config build | sh

Optionally install missing dependencies (can happen when official GRASS package is not compatible with GRASS main), eg.

sudo apt install libzstd-dev

Compile:

make -j2

6. Run locally or install

./bin.x86_64-pc-linux-gnu/grass --version

or

sudo make install
grass --version

===== Debian =====

* Official [https://wiki.debian.org/DebianGis DebianGIS] packaging control files, available on git server:
https://salsa.debian.org/debian-gis-team/grass

====== GRASS 8 on Debian 11 (bullseye) ======

Install needed packages for GRASS 8.4:
apt-get update && \
apt-get install bison debhelper-compat dh-python doxygen fakeroot flex graphviz \
libblas-dev libbz2-dev libcairo2-dev libfftw3-dev libfreetype6-dev \
libgdal-dev libgeos-dev libgl1-mesa-dev libglu1-mesa-dev libjpeg-dev liblapack-dev libmotif-dev \
default-libmysqlclient-dev libncurses5-dev libnetcdf-dev libpng-dev libpq-dev \
libproj-dev libreadline-dev libsqlite3-dev libtiff-dev libxmu-dev libzstd-dev \
netcdf-bin pkg-config proj-bin python3 python3-dev python3-numpy python3-pil python3-ply \
python3-six python3-wxgtk4.0 wget unixodbc-dev zlib1g-dev

Download and unpack GRASS 8.4 source code (or fetch from GitHub: https://github.com/OSGeo/grass):

wget https://grass.osgeo.org/grass84/source/grass-8.4-latest.tar.gz
tar xvfz grass-8.4-latest.tar.gz
cd grass-8.4.*

Configuration:

CFLAGS="-Wall -Werror-implicit-function-declaration -fno-common -Wextra -Wunused" \
CXXFLAGS="-Wall" \
./configure \
--prefix=/usr/local \
--with-gdal --with-proj --with-proj-share=/usr/share \
--with-glw --with-nls --with-readline \
--with-cxx --enable-largefile \
--with-freetype --with-freetype-includes=/usr/include/freetype2 \
--with-sqlite --with-cairo --with-python=/usr/bin/python-config \
--with-wxwidgets --with-geos \
--with-netcdf=/usr/bin/nc-config --with-odbc=yes \
--with-openmp=yes --with-pthread=no

Compile:

make -j2

Install:

make install

Run:

grass --version

===== Ubuntu =====

There is a dedicated page on how to [[Compile_and_Install_Ubuntu | Compile the GRASS source code & install it in Ubuntu]].

===== Linux Mint =====

The [[Compile_and_Install_Ubuntu | detailed compilation guide for Ubuntu]] may just work. However, here is a short guide for Mint:

<source lang="bash">
# Linux Mint 21+

# be sure to have an updated system
sudo apt-get update && sudo apt-get upgrade -y

# installation of required libraries and compile tools
# recommended to give Python3 precedence over Python2 (which is end-of-life since 2024)
sudo update-alternatives --install /usr/bin/python python /usr/bin/python3 1

# install compiler tools and further dependencies (tested with Linux Mint 21)
# this is a single command, please copy-paste it entirely into the terminal:
sudo apt-get install \
build-essential \
flex make bison gcc libgcc1 g++ cmake ccache \
libproj-dev proj-data proj-bin \
libgeos-dev \
libgdal-dev python3-gdal gdal-bin \
python3 python3-dev \
python3-opengl \
python3-dateutil libgsl-dev python3-numpy \
libfftw3-dev \
zlib1g-dev gettext \
libbz2-dev libzstd-dev libfreetype6-dev \
libtiff5-dev libpnglite-dev libcairo2 libcairo2-dev \
sqlite3 libsqlite3-dev libpq-dev \
libfftw3-3 libfftw3-dev \
libboost-thread-dev libboost-program-options-dev \
subversion \
checkinstall \
libglu1-mesa-dev libxmu-dev \
ghostscript wget -y
</source>

'''GUI''' - update wxpython:

<source lang="bash">
# Linux Mint 21 only
sudo apt-get install wx3.0-headers libwxgtk3.0-gtk3-dev libwxbase3.0-dev libwxgtk3.0-gtk3-dev
pip3 install --user --upgrade typing-extensions
pip3 install -U -f https://extras.wxpython.org/wxPython4/extras/linux/gtk3/ubuntu-22.04 wxPython
</source>

or

<source lang="bash">
# Linux Mint 22+
sudo apt-get install wx3.2-headers libwxgtk3.2-dev libwxbase3.2-1 libgtk-3-dev python3-wxgtk4.0 \
pip3 install -U -f https://extras.wxpython.org/wxPython4/extras/linux/gtk3/ubuntu-22.04 wxPython
</source>

Next steps:
* create a subdirectory in your HOME tree for storing the GRASS source code (and later compilation)
* get source code, one of the two options:
** a) download [https://grass.osgeo.org/grass84/source/snapshot/ GRASS source code weekly snapshot] (e.g. take the "8.x.git snapshot"), or
*** unpack source code
** b) current source code from GitHub:
*** <code>git clone https://github.com/OSGeo/grass.git</code>
* change into the source code directory

<source lang="bash">
# in the source code directory, "configure" the source code to prepare for compilation:
./configure \
--with-cxx \
--with-proj-share=/usr/share/proj \
--with-gdal=/usr/bin/gdal-config \
--with-geos \
--with-sqlite \
--with-nls \
--with-zstd \
--with-cairo --with-cairo-ldflags=-lfontconfig \
--with-freetype=yes --with-freetype-includes="/usr/include/freetype2/" \
--with-fftw \
--with-opengl-libs=/usr/include/GL \
--without-postgres \
--without-pdal \
--without-netcdf \
--without-mysql \
--without-odbc \
--without-openmp

# compile GRASS
make -j2

# install compiled GRASS on system
sudo make install

# use GRASS! Start on command line
grass
</source>

===== Enterprise Linux =====

Enterprise Linux (EL) and derivatives (that is, Red Hat Enterprise Linux, CentOS and Scientific Linux) is a popular and robust platform for servers and computing-heavy workstations, and is therefore a good fit for GIS specific requirements.

See: https://wiki.osgeo.org/wiki/Enterprise_Linux_GIS

===== Scientific Linux =====

See Centos

===== CentOS =====

You first need to add the EPEL repository for PROJ and GDAL, see [https://fedoraproject.org/wiki/EPEL/FAQ#How_can_I_install_the_packages_from_the_EPEL_software_repository.3F here]

Preparation '''Centos 8''':
dnf install epel-release

dnf install flex bison make zlib-devel gcc-c++ gettext \
fftw-devel libtiff-devel sqlite-devel \
proj proj-devel proj-datumgrid libxml2 \
geos geos-devel git \
netcdf netcdf-devel atlas-devel \
blas-devel lapack-devel libpq-devel \
python3-devel python3-numpy \
python3-dateutil python3-imaging python3-matplotlib \
gdal gdal-libs gdal-python-tools python3-gdal gdal-devel \
wxGTK3-devel mesa-libGL-devel mesa-libGLU-devel \
libXmu-devel libX11-devel

'''GRASS 8 compilation and installation'''

[https://grass.osgeo.org/grass84/source/snapshot/ Download source code] (e.g., --> "Download latest 8.4 code)" and configure GRASS 8 (suggestion: save this as script):

./configure \
--with-cxx \
--with-proj --with-proj-share=/usr/share/proj \
--with-gdal=/usr/bin/gdal-config \
--with-sqlite \
--with-python \
--with-cairo --with-cairo-ldflags=-lfontconfig \
--with-freetype --with-freetype-includes=/usr/include/freetype2 \
--with-wxwidgets=/usr/bin/wx-config \
--with-openmp \
--with-blas --with-blas-includes=/usr/include/atlas-x86_64-base/ \
--with-lapack --with-lapack-includes=/usr/include/atlas-x86_64-base/ \
--with-fftw \
--with-geos \
--with-netcdf \
--without-ffmpeg \
--without-mysql \
--without-postgres \
--without-odbc \
--without-fftw

Compile:
make
or on a multicore system (number depends of available cores):
make -j4

For a system wide installation, run as root user:
make install
OR simply run it directly from the source code directory (substitute ARCH with i686 or x86_64):

bin.$ARCH/grass -gui

In this case, for convenience, add it to the search path:
mkdir $HOME/bin
cd $HOME/bin
# example:
ln -s $HOME/software/grass84_release/bin.x86_64-pc-linux-gnu/grass .

Now use it subsequently with
grass -gui

'''Installation grass on a HPC system with '''Centos 7''' and no root privileges:'''

This assumes that python3, fftw, proj, gdal and geos are available on the HPC system, either as modules or as installed software.

Download and prepare some dependencies (freetypes and zstd)
mkdir -p $HOME/grass/freetypes
cd $HOME/grass/freetypes
wget path/to/freetype-2.9.1.tar.gz
tar -xf freetype-2.9.1.tar.gz

mkdir $HOME/grass/zstd
cd mkdir $HOME/grass/zstd
wget path/to/v1.4.4/zstd-1.4.4.tar.gz
tar -xf zstd-1.4.4.tar.gz
make install PREFIX=./

Add the ZSTD path to your LD_LIBRARY_PATH

tee -a $HOME/.bashrc > /dev/null << EOT
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$HOME/grass/zstd/zstd-1.4.4/lib
EOT

The configure command could look like this
./configure \
-prefix=$HOME/grass \
--enable-64bit --with-fftw-includes=/path/to/fftw/include/ \
--with-fftw-libs=/path/to/fftw/lib/ \
--with-freetype-includes=$HOME/grass/freetypes/freetype-2.9.1/include/ \
--with-netcdf --with-geos --with-blas --with-lapack --with-postgres \
--with-zstd-includes=$HOME/grass/zstd/zstd-1.4.4/lib/ \
--with-zstd-libs=$HOME/grass/zstd/zstd-1.4.4/lib/ \
--with-gdal=/path/to/gdal-config # This could be the path to a gdal version compiled from source

Finally as usual:
make; make install

grass

===== Gentoo =====

./configure \
--with-freetype=yes --with-freetype-includes="/usr/include/freetype2/"

See also https://packages.gentoo.org/package/sci-geosciences/grass

===== Funtoo =====

{{MovedToTrac|FuntooLinux}}

===== Fedora =====

====== GRASS 8 on Fedora ======

'''Preparation''' for the compilation of GRASS 8+ source code (F36+):

dnf install gcc gcc-c++ bison flex ncurses-devel gettext proj-devel \
gdal gdal-devel sqlite-devel xml2 mesa-libGL-devel cairo-devel \
fftw-devel mesa-libGLU-devel libXmu-devel libX11-devel geos geos-devel \
libtiff-devel python3-devel numpy wxGTK-devel gawk git \
python3-dateutil python3-imaging python3-matplotlib-wx doxygen python3-sphinx \
libzstd-devel libzstd python3-six python3-numpy python3-wxpython4 \
proj-data PDAL-devel PDAL-libs

# optionally also: netcdf-devel postgresql-devel
# atlas-devel lapack-devel lapack-devel
# laszip laszip-devel
# proj-data-at proj-data-au proj-data-be ...

''Note 1: the optional ffmpeg-devel comes from the rpmfusion-free repository ([https://rpmfusion.org/Configuration/ configuration]).''

'''Download''' and unpack the source code:
* GRASS 8: [https://grass.osgeo.org/grass84/source/snapshot/ weekly snapshot] - [https://github.com/OSGeo/grass/releases GitHub repository]

'''Configure''': This is an example how to configure the source code on a Fedora system:

./configure \
--with-cxx \
--with-gdal=/usr/bin/gdal-config \
--with-proj --with-proj-share=/usr/share/proj \
--with-geos \
--with-pdal \
--with-sqlite \
--with-nls \
--with-wxwidgets=/usr/bin/wx-config \
--with-fftw \
--with-cairo --with-cairo-ldflags=-lfontconfig \
--with-freetype --with-freetype-includes=/usr/include/freetype2 \
--enable-largefile \
--without-odbc

''Extra 1:'' If you also want '''FFMPEG support''' - it requires 'dnf install fftw-devel' from the rpmfusion-free repository. Then add to the configuration lines above:

--with-ffmpeg --with-ffmpeg-includes="/usr/include/ffmpeg /usr/include/ffmpeg/libav* /usr/include/ffmpeg/libpostproc /usr/include/ffmpeg/libswscale" \

''Extra 2:'' For '''LAPACK/BLAS support''' (addons i.spec.unmix, v.kriging etc), install "dnf install lapack lapack-devel blas blas-devel atlas atlas-devel". Then add to the configuration lines above:
--with-blas --with-blas-includes=/usr/include/atlas-x86_64-base/ \
--with-lapack --with-lapack-includes=/usr/include/atlas-x86_64-base/ \

''Extra 3:'' For '''ZSTD support''' (Zstandard compression algorithm), first install "dnf install libzstd libzstd-devel zstd". After installing the zstd related packages, add to the configuration lines above:
--with-zstd \

Finally '''compile''' the configured source code:
make
or on multicore (number depends of available cores):
make -j4
and
make install # requires root permissions unless you become owner of /usr/local/

Then use GRASS 8 and enjoy!

grass --version

===== openSUSE =====

To build GRASS on openSUSE:

''Application:Geo'' repo to be added (see [https://software.opensuse.org//download.html?project=Application%3AGeo&package=gdal Install package Application:Geo]

<source lang="bash">
# example for Leap 42 version:
sudo zypper addrepo https://download.opensuse.org/repositories/Application:Geo/openSUSE_Leap_42.3/Application:Geo.repo
sudo zypper refresh
</source>

RPM packages to be installed:
<source lang="bash">
sudo zypper install bison flex freetype2-devel fftw3-devel gcc-c++ \
libgdal-devel libgeos-devel libjpeg-devel libpng-devel libtiff-devel \
man proj libproj-devel readline-devel netcdf-devel ncurses-devel \
mysql-devel postgresql-devel sqlite-devel unixODBC-devel \
tcl-devel tk-devel xorg-x11-Mesa-devel libXmu-devel \
python-numpy python-dateutil python-devel python-opengl \
python-wxWidgets python-xml python-dateutil wxWidgets-devel \
zlib-devel doxygen python-sphinx
</source>

Source code configuration:
<source lang="bash">
./configure \
--enable-largefile \
--with-proj-share=/usr/share/proj \
--with-cxx \
--with-lapack=yes \
--with-motif \
--with-gdal=/usr/bin/gdal-config \
--with-postgres --with-postgres-includes=/usr/include/pgsql \
--with-mysql --with-mysql-includes=/usr/include/mysql \
--with-fftw \
--with-readline \
--with-netcdf \
--with-geos \
--with-nls \
--with-sqlite \
--with-freetype \
--with-freetype-includes=/usr/include/freetype2 \
--with-wxwidgets \
--with-odbc \
--with-python
</source>

Then compile with "make [-j2]".

===== RPM SPEC files =====
* [https://build.opensuse.org/package/show?package=grass&project=Application%3AGeo OpenSuSe]
* [https://pkgs.fedoraproject.org/cgit/rpms/grass.git/tree/grass.spec Fedora]
* ...

==== macOS ====

Compiling GRASS for macOS is not fundamentally different from for other *nix systems. It is on the contrary quite similar, but what differ is the lack of a default package management system for software GRASS depends on. This leaves the mac user to either: (1) compile the dependencies one-by-one; (2) compiling with one of the third-party package management systems avaliable; or (4) a combination thereof.

If you are interested in installing a precompiled version, please check out the [https://grass.osgeo.org/download/software/mac-osx/ official download site].

To date, maybe the easiest way to compile for Mac is by using [https://github.com/nilason/grass-conda GRASS app build script] which is based on the instructions below for building using Anaconda. It will install dependencies, package and install an app bundle with just a command in Terminal.

===== Compilation and installation =====

For more up-to-date instructions please read:

* [https://github.com/nilason/grass-conda Compiling on macOS using Conda] (Intel / Apple silicon based machine M1)
* [[Compiling on macOS using Anaconda]]
* [[Compiling on macOS using Homebrew]]
* [[Compiling on macOS using MacPorts]]

===== Legacy instructions =====

The following compilation and installation instructions are rather outdated as a whole. They do, however, contain parts and snippets that still may be very instructive and useful.

* [[Compiling on MacOSX]]
* [[Compiling on MacOSX using Fink]]
* [https://web.archive.org/web/20180718005252/https://www.kyngchaos.com/software/frameworks#build_scripts build scripts for dependencies]

Troubleshooting:
* solving errors at starting GRASS: [[MacOSX GRASS errors]]

==== FreeBSD / NetBSD ====

The recommended compiler tools are GCC, GNU make, GNU coreutils (for install), and flex. All are available through the respective package managing tools (pkg_add for FreeBSD and pkgin install for NetBSD) and for recent *BSD versions most likely installed by default.

GRASS 8 should compile on FreeBSD and NetBSD.

It is highly recommended to install GDAL/OGR and PROJ first. These libraries and tools are available as [https://www.freebsd.org/ports/ ports for FreeBSD] and [https://www.pkgsrc.org/ packages for NetBSD].

Optional functionality is listed with ''./configure --help'', and related libraries and tools might need to be installed first.

You then may need to edit include/Make/Platform.make and set
ICONVLIB = -liconv

==== AIX ====

A recent [ftp://ftp.gnu.org/gnu/make/ GNU make] (>= 3.81) and GNU coreutils are required. These are available with the [https://www-03.ibm.com/systems/power/software/aix/linux/toolbox/download.html IBM AIX toolbox] or through third-party AIX software repositories, e.g. [https://www.bullfreeware.com/ bullfreeware] and [https://www.perzl.org/aix/ perzl.org]. Note that 'make' does not work, only 'gmake' works.

General instructions to compile on AIX are e.g. [https://www.perzl.org/aix/index.php?n=Main.Instructions here]

On AIX, compilation results by default in 32 bit applications and static libraries. The [https://developer.ibm.com/components/aix/ IBM documentation] explains how to build 64 bit applications and shared libraries with GCC.

'''GRASS 8: Using the IBM xlc compiler:'''

Get and install (in this order):
* [ftp://ftp.gnu.org/gnu/tar/ GNU tar]
* [ftp://ftp.gnu.org/gnu/make/ GNU make] (>= 3.81)
* [https://www.sqlite.org SQLite]
* [https://trac.osgeo.org/proj/ PROJ.4] (for ./configure parameters, see [[Talk:Compile and Install|here]])
* [https://www.gdal.org GDAL] (for ./configure parameters, see [[Talk:Compile and Install|here]])
* [https://grass.osgeo.org/grass84/source/snapshot/ GRASS 8]

The environment variables and configure command that worked:
<pre>
## AIX 5.x

export LIBPATH=/opt/freeware/lib64:/opt/freeware/lib
# make 'ar' happy
export OBJECT_MODE=64

PREFIX=$HOME/private/bin
./configure \
--prefix=$PREFIX \
--disable-shared \
--with-cxx \
--with-proj-includes=$PREFIX/include/ \
--with-proj-libs=$PREFIX/lib/ \
--with-proj-share=$PREFIX/share/proj/ \
--with-sqlite \
--with-sqlite-includes=$PREFIX/include/ \
--with-sqlite-libs=$PREFIX/lib/ \
--with-tiff=no \
--with-png=no \
--with-fftw=no \
--with-cairo=no \
--with-freetype=no
</pre>

'''GRASS 8: Using the GNU gcc compiler:'''

Get and install (in this order):
* if needed, [ftp://ftp.gnu.org/gnu/tar/ GNU tar]
* if needed (the name is often 'gmake' and not 'make') [ftp://ftp.gnu.org/gnu/make/ GNU make] (>= 3.81)
* [https://www.sqlite.org SQLite]
* [https://trac.osgeo.org/proj/ PROJ.4] (for ./configure parameters, see [[Talk:Compile and Install|here]])
* [https://www.gdal.org GDAL] (for ./configure parameters, see [[Talk:Compile and Install|here]])
* [https://grass.osgeo.org/grass84/source/snapshot/ GRASS 8]

The environment variables and configure command that worked for AIX 7.x:
<pre>
## AIX 7.x
export CC="gcc"
export CXX="g++"
PREFIX=$HOME/bin

LDFLAGS="-Wl,-bsvr4,-R,/opt/freeware/lib -L/opt/freeware/lib" CPPFLAGS="-I/opt/freeware/include" ./configure \
--prefix=$PREFIX \
--enable-shared \
--with-includes=/opt/freeware/include --with-libs=/opt/freeware/lib \
--with-cxx \
--with-proj-includes=$PREFIX/include/ \
--with-proj-libs=$PREFIX/lib/ \
--with-proj-share=$PREFIX/share/proj/ \
--with-gdal=$PREFIX/bin/gdal-config \
--with-sqlite \
--with-sqlite-libs=$PREFIX/lib --with-sqlite-includes=$PREFIX/include \
--with-png=no \
--with-tiff=no \
--with-fftw=no \
--with-cairo=no \
--with-opengl=no \
--with-freetype=no
</pre>

==== MS-Windows ====

See also [[WinGRASS Current Status]] for latest updates.

===== MS-Windows/native =====

GRASS on Windows using a standalone installer. It is still MinGW based (we are going to move this to CMake in 2024+).

Instructions to compile from source code:
* [https://trac.osgeo.org/grass/wiki/CompileOnWindows GRASS Windows Native Binary Building Guide]

===== MS-Windows/OSGeo4W =====

OSGeo4W is an installer for a broad set of open source geospatial software packages including GRASS as well as many other packages (QGIS, GDAL/OGR, and more).

* See [https://trac.osgeo.org/osgeo4w/ OSGeo4W]

===== MS-Windows/Cygwin =====

* See the [[Cygwin]] wiki pages

=== Common problems and solutions ===

During compilation, error can occur if certain packages are not installed. Here a list of problems with solution:

* error: X11/Xlib.h: No such file or directory
** this suggests that you don't have the X headers installed
** Solution: Install the libx11-dev package

* error: g.list: error while loading shared libraries: libgdal1.6.0.so.1: cannot open shared object file: No such file or directory
** this error appears in the shell right after the user clicks GUI's "Start GRASS" button. The GUI shows an error about geographic extent and gets closed afterwards.
** It happens when you launch bin.i686 executable on 64bit system. Be careful and choose the right architecture.

* error: lib/python/ctypes
** This error appears during the compilation: <code>free(): invalid pointer Aborted (core dumped)</code>
** It happens when you have multiple <code>libproj</code> versions on your system (check it with command <code>ldd PATH_TO_GRASS_INSTALL/lib/libgrass_gproj.so | grep proj</code> - when this is not your problem, you should obtain exactly one result)
** Solution: Try to reinstall <code>libproj-dev</code> and <code>proj-data</code>

=== Static compilation ===

In order to get static rather than dynamically linked binaries, configure like this:

./configure --disable-shared --enable-static

This will however break the wxGUI and GRASS 8 completely because "ctypes" wants to link against shared libs, or there is something in the static libs that "ctypes" does not like.

=== Optimization ===

GCC and other compilers support [https://gcc.gnu.org/onlinedocs/gcc-4.3.3/gcc/Optimize-Options.html#Optimize-Options optimization]

If you would like to set compiler optimisations, for a possibly faster binary, type (don't enter a ";" anywhere):

CFLAGS=-O ./configure
or,
setenv CFLAGS -O
./configure

whichever works on your shell. Use -O2 instead of -O if your compiler supports this (note: O is the letter, not zero). Using the "gcc" compiler, you can also specify processor specific flags (examples, please suggest better settings to us):

CFLAGS="-mcpu=athlon -O2" # AMD Athlon processor with code optimisations
CFLAGS="-march=amdfam10" # AMD Phenom II X4 64bit processor with gcc >=4.3
CFLAGS="-mcpu=pentium" # Intel Pentium processor
CFLAGS="-mcpu=pentium4" # Intel Pentium4 processor
CFLAGS="-O2 -msse -msse2 -mfpmath=sse -minline-all-stringops" # Intel XEON 64bit processor
CFLAGS="-mtune=nocona -m64 -minline-all-stringops" # Intel Pentium 64bit processor

To find out optional CFLAGS for your platform, enter:
gcc -dumpspecs

See also: https://gcc.gnu.org/

A real fast GRASS version (and small binaries) will be created with LDFLAGS set to "stripping" (but this disables debugging):

CFLAGS="-O2 -mcpu=<cpu_see_above> -Wall" LDFLAGS="-s" ./configure

=== Configure options and their meanings ===

For configure there are many options and some GRASS modules are built only if some options are set. Here are listed common configuration options with short explanation.

* --prefix=/path - Sets path where GRASS will be installed. GRASS will reside in /path/grass-version.
* --enable-largefile - Enables large (>2Gb on 32bit systems) support. For current large file support status look at [[Large File Support]] page.
* --with-cxx - Enables compilation of C++ code. Required for r.terraflow module.
* --with-readline - Enables readline support. If readline is enabled, you can use its history/editing facilities when entering r.mapcalc expressions on stdin.
* --with-glw - Enables GLw support. The GLw library provides OpenGL "canvas" widgets for Athena and Motif.

That switch is unnecessary for normal compilation. It's only
required for r3.showdspf, which isn't normally built; if you
want it, you have build it manually
(e.g. "make -C raster3d/r3.showdspf").
As similar functionality is now provided by NVIZ, r3.showdspf
is deprecated.
r3.showdspf uses the Motif widget (so you also need a
Motif library, e.g. Lesstif or OpenMotif).
[https://grass.itc.it/pipermail/grassuser/2006-December/037475.html Glynn Clements at GRASS-user mailing list]

=== Parallelized compilation on multi-core CPUs ===

You can dramatically accelerate the compilation of the GRASS code with the -j flag of "make" if you have a multi-core CPU system. This determines the maximum number of jobs to have running at once, so cores don't have to sit idle waiting for jobs on other cores to complete. A good rule of thumb for this value is <tt>number_of_cores * 1.5</tt>, but note that setting any higher than the actual number of cores will only affect the timing slightly. For example, on a dual-core processor:
make -j 4



== GRASS-GDAL plugin ==

* see [[Compile and install GRASS and QGIS with GDAL/OGR Plugin]]

== Addons ==

Please note that the installation of [https://grass.osgeo.org/grass-stable/manuals/addons/ GRASS addons] can be easily done with the {{cmd|g.extension}} manager. The compile instructions below are aiming at own development.

=== Compiled modules ===

This is the general way which works for C modules as well as scripts (Python or Shell/Bash modules) which has HTML documentation.

'''Requirements:'''

Either:
* a binary GRASS package, or
* source code which has been prepared with:
./configure [opionally flags]
make libs

Each of the [[GRASS_AddOns|addon]] modules should come with a Makefile. To compile it, just run:
make MODULE_TOPDIR=/path/to/grass84/

Note that the <tt>/path/to/grass84</tt> has to be absolute, not relative.

If using Bash it may be useful to set that up as an alias:
alias gmake64='make MODULE_TOPDIR=/path/to/grass84/'

Installation (perhaps requires "sudo"):
make MODULE_TOPDIR=/path/to/grass84/ install

Note: Compiled addons may require a re-compilation if you changed/updated your GRASS standard binaries.

==== If binary comes with a -dev package ====

''(work in progress, this text states how it eventually will be :)''
Nowadays one does not need to the source code, nor compiling GRASS by oneself to be able to add add-ons. On Debian, you can just install the grass-dev package and then run:
make MODULE_TOPDIR=/usr/lib/grass84/ INST_DIR=/usr/lib/grass84/

The grass-dev package essentially provides GRASS's <tt>include</tt> header files and Make configuration files.

=== Scripts ===

If the addon module is a script, it is sufficient to copy it into the (GRASS binaries) path somewhere. Alternatively, install addons into a separate GRASS addons binaries/scripts directory which is easier to maintain. It avoids getting clobbered every time you reinstall GRASS. To use these separately stored scripts, set and export the GRASS_ADDON_PATH environment variable before starting GRASS and it will automatically be added to the module search path (see the {{cmd|variables}} help page). To simplify this, do for example:

# add in $HOME/.bashrc:
GRASS_ADDON_PATH=/usr/local/grass/addons/
export GRASS_ADDON_PATH

Make sure that the script is executable, then just call it in GRASS typing the filename. Python scripts need to be called writing the extension as well, like:

GRASS (nc_spm):~ > v.krige.py

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

PostGIS

2025-09-23T07:54:01Z

Neteler: remove version from GRASS (avoid "7")

When accessing [http://www.postgis.net PostGIS] data in GRASS you can
* [[#Import into GRASS|import]] PostGIS (simple features) data into GRASS topological format or,
* [[#Link to GRASS|link]] PostGIS data as GRASS vector maps

See also [[Working with external data in GRASS|working with external data in GRASS]].
__TOC__
== Help pages ==

* {{cmd|vectorintro|desc=Vector data processing in GRASS GIS}} help page
* {{cmd|databaseintro|desc=Database management in GRASS GIS}} help page
* {{cmd|sql|desc=SQL support in GRASS GIS}} help page

* {{cmd|grass-pg|desc=PostgreSQL DB driver in GRASS}} help page
* {{cmd|grass-odbc|desc=ODBC DB driver in GRASS}} help page

== Import into GRASS ==

# {{cmd|v.in.ogr}} - imports geometry data from PostGIS into native GRASS vector format, attributes are stored using default DB settings (see {{cmd|db.connect}} for details)
# {{cmd|v.clean}} - clean up data after import

''Note 1:'' There is a fundamental difference between the PostGIS format which is
non-topological (OGC simple feature-based) and the internal GRASS format which is topological and
which, thus, does not really allow for overlapping polygons. You can
digitize them, but they are not really useful...

''Note 2:'' GRASS also allows reading and writing topological PostGIS data (see [http://www.postgis.org/documentation/manual-2.0/Topology.html PostGIS Topology] for details).

{{YouTube|JoqIkL2VRVc|desc=Importing PostGIS layers into GRASS}}

== Link to GRASS ==

* input maps: {{cmd|v.external}}
**GRASS supports also write access to the map links, see [[Working with external data in GRASS#Vector data|working with external data in GRASS]] for details
* output maps: {{cmd|v.external.out}}

You can register a PostGIS table in GRASS using {{cmd|v.external}}. The command below creates a link to the table 'lakes' located in database 'pgis_nc'.

# list available PG tables
v.external input="PG:host=myserver user=myuser dbname=pgis_nc" -l

# link PG table into GRASS GIS as vector map
v.external input="PG:host=myserver user=myuser dbname=pgis_nc" layer=lakes

The command creates in the current mapset new vector map 'lakes', the module also builds pseudo-topology for this map,

To link a PostGIS table from non-public schema

v.external input=PG:<connection sting> layer=<schema>.<layer> output=<layer>

''Important note:'' In GRASS 6 the created links area ''read-only''. GRASS also allows to modify linked layers directly via OGR or PostGIS data provider, see [[Working with external data in GRASS#Vector data|working with external data in GRASS]] for details.

{{YouTube|eB3_SmE3E9Q|desc=Link PostGIS layers as GRASS vector maps}}

== Export to PostGIS ==

To export GRASS vector map layer as PostGIS table use {{cmd|v.out.ogr}}, eg.

v.out.ogr in=lakes@PERMANENT output=PG:dbname=pgis_nc format=PostgreSQL type=area

In GRASS also specialized module {{cmd|v.out.postgis}} exists which allows to export GRASS vector data as simple features (similarly to {{cmd|v.out.ogr}}) or in topological format (see [[PostGIS Topology]] for defails).

Note that exporting data can be quite time-consuming task, especially when input vector map attributes are stored in DBF format. It's recommended to store attribute data in {{cmd|grass-sqlite|desc=SQLite format}} rather then in old-fashioned {{cmd|grass-dbf|desc=DBF format}}.

{{YouTube|DTMmmcVpJKk|desc=Creating model which exports all GRASS vector maps from given mapset to PostGIS database}}
{{YouTube|uStN3F6ZZoc|desc=Creating model which exports all GRASS vector maps from given mapset to PostGIS database (including schema)

1) create schema with name of input mapset

2) copy vector maps from selected mapset to the current and stores their attributes in SQLite database

3) exports GRASS vector maps to the selected PostGIS database
}}

See also [[wxGUI Graphical Modeler]].

== Direct access to PostGIS data ==

''Important note:'' Direct read/write access is available only in GRASS.

=== Direct read access ===

GRASS allows to access PostGIS data directly via virtual mapset called 'OGR'. In this case parameter <tt>map</tt> or <tt>input</tt> is used for OGR data source and <tt>layer</tt> for table. In the command bellow is accessed PostGIS table 'lakes' from database 'pgis_nc'.

v.info map=PG:dbname=pgis_nc@OGR layer=lakes

To access table from non-public schema (or schemas which are not in the search path), type

<pre>
v.info map=PG:<OGR data source> layer=<schema>.<table>
</pre>

When accessing external data directly you don't need to create a map link by {{cmd|v.external}}. The major drawback of direct read access is that the pseudo-topology is built each time when accessing the data. From this point of view the direct access is useful when accessing data once or few times, otherwise is better to link the data by {{cmd|v.external}}.

=== Direct write access ===

GRASS allows to write output vector map directly via OGR library. For defining output vector data format is designed {{cmd|v.external.out}} module. For example

v.external.out input=PG:dbname=pgis_nc format=PostgreSQL

causes that output vector data are written in PostGIS format in the database 'pgis_nc'. GRASS also creates automatically for every PostGIS table a new vector map in the current mapset as the link to the PostGIS table.

PostGIS data can be accessed by the map link or directly as described in the section above. For example

v.extract input=lakes out=reservoir where="FTYPE = 'RESERVOIR'"

v.info map=reservoir
# or
v.info map=PG:dbname=pgis_nc@OGR layer=reservoir

To switch back to GRASS native format enter

v.external.out -r

== See also ==

* [[Working with external data in GRASS]]
* [[PostGIS Topology]]

== External links ==

* [http://www.surfaces.co.il/?p=645 Tutorial by Micha Silver]
* [http://www.postgis.org PostGIS]
* [http://gdal.org/ogr OGR library]
* [http://www.dimensionaledge.com/main/postgis/viewshed-analysis-in-postgis-using-plr-and-grass/ Viewshed analysis in PostGIS using PL/R and GRASS] (blog post by Mark Wynter)
* [https://strk.kbt.io/projects/rttopo/ RT Topology Library]

[[Category: FAQ]]
[[Category: Vector]]

Working with external data in GRASS

2025-09-23T07:43:24Z

Neteler: remove version from GRASS (avoid "7")

This page explains how to effectively work with external raster and vector data in GRASS. See also [[PostGIS]] and [[PostGIS Topology]].
__TOC__
== Raster data ==

External raster data can be linked via {{cmd|r.external}}. List of supported formats can be determined by

{{cmd|r.external}} -f

To link file-based data formats, eg. GeoTiff

{{cmd|r.external}} input=ncrast/urban.tif output=urban

=== Raster data processing workflow when keeping data external ===

External raster maps can directly be linked into GRASS with {{cmd|r.external}} which saves time and disk space. Additionally, there is no more a need to store results in the internal GRASS format - with {{cmd|r.external.out}} the resulting maps are directly written to a GDAL supported format.

'''Preparations'''

GRASS can be used in an automated way by just defining a set of variables. See here for [[GRASS_and_Shell#Setting_the_variables|GRASS and Shell]] settings and [[GRASS_and_Python#Creating_Python_scripts_that_call_GRASS_functionality_from_outside|GRASS and Python]].

'''Data flow example'''

The script content could be looking like this:

<source lang="bash">
# register (rather than import) a GeoTIFF file in GRASS GIS:
r.external input=terra_lst1km20030314.LST_Day.tif output=modis_celsius

# define output directory for files resulting from subsequent calculations:
r.external.out directory=$HOME/gisoutput/ format="GTiff"

# perform calculations (here: extract pixels > 20 deg C)
# store output directly as GeoTIFF file, hence add the .tif extension:
r.mapcalc "warm.tif = if(modis_celsius > 20.0, modis_celsius, null() )"

# cease GDAL output connection and turn back to write standard GRASS raster files:
r.external.out -r

# use the result elsewhere
qgis $HOME/gisoutput/warm.tif
</source>

== Vector data ==

See trac {{twiki|Grass7/VectorLib/OGRInterface|OGR interface}} and {{twiki|Grass7/VectorLib/PostGISEditing| PG interface}} page for development issues.

=== Link external data ===

External vector data can be linked via {{cmd|v.external}} using [http://gdal.org/ogr OGR library] or ''GRASS-PostGIS data driver'' (<tt>format=PostgreSQL</tt>). List of supported formats can be determined by

{{cmd|v.external}} -f

To link ''file-based data formats'', eg. [http://gdal.osgeo.org/ogr/drv_shapefile.html ESRI Shapefile] using OGR library

{{cmd|v.external}} input=ncshape/ layer=railroads

Assuming that <tt>railroads.shp</tt> is located in directory <tt>ncshape</tt>.

To link ''database-based data formats'', eg. [http://gdal.osgeo.org/ogr/drv_pg.html PostGIS] using GRASS-PostGIS data driver

{{cmd|v.external}} input=PG:dbname=pgis_nc -l

PostGIS database <pgis_nc> contains 55 feature table(s):
...
bridges
...

{{cmd|v.external}} input=PG:dbname=pgis_nc layer=bridges output=b

Assuming that PostGIS layer named <tt>bridges</tt> is located in database <tt>pgis_nc</tt>. This layer is linked to GRASS mapset as vector map with name <tt>b</tt>. {{cmd|v.external}} also builds pseudo-topology over simple features which enables GRASS to access linked vector data on level 2. Note that data are stored as simple features, so no full topology support can be build based on this data.

By default PostGIS feature tables are linked using built-in '''GRASS-PostGIS data driver''' - it means that PostGIS geometry data are accessed by GRASS directly without any abstract level (like OGR library). When GRASS is built without PostgreSQL support or environmental variable <tt>GRASS_VECTOR_OGR</tt> exists, then GRASS will access PostGIS data using [http://www.gdal.org/drv_pg.html OGR-PostgreSQL] driver.

=== Direct access to external data ===

External data can be accessed using OGR library via ''virtual'' mapset <tt>OGR</tt>.

{{cmd|v.info}} map=PG:dbname=pgis_nc@OGR layer=bridges

Direct access using GRASS-PostGIS data driver is not currently possible.

=== Create new OGR layers using GRASS modules ===

==== v.extract showcase ====

GRASS also supports write access to the external data using OGR or GRASS-PostGIS data driver. Showcase bellow:

{{cmd|v.external}} input=PG:dbname=pgis_nc layer=bridges output=b

{{cmd|v.out.ascii}} input=b where="cat < 10" --q

375171.4992779|317756.72097616|1
374247.5192779|317487.13697616|2
380230.2292779|316900.97897616|3
379191.4162779|316419.09697616|4
388958.8222779|316332.04697616|5
375875.2662779|316319.89597616|6
376393.5282779|316155.96797616|7
380647.5282779|316022.61797616|8
376739.6982779|315970.62597616|9

{{cmd|v.external.out}} input=PG:dbname=pgis_nc format=PostgreSQL

{{cmd|v.extract}} input=b output=b_9 where="cat < 10"

{{cmd|v.external}} input=PG:dbname=pgis_nc -l

PostGIS database <pgis_nc> contains 56 feature table(s):
b_9
bridges
...

Example of direct access to external data without creating a link (only OGR data driver)

{{cmd|v.out.ascii}} input=PG:dbname=pgis_nc@OGR layer=b_9

375171.4992779|317756.72097616|1
374247.5192779|317487.13697616|2
380230.2292779|316900.97897616|3
379191.4162779|316419.09697616|4
388958.8222779|316332.04697616|5
375875.2662779|316319.89597616|6
376393.5282779|316155.96797616|7
380647.5282779|316022.61797616|8
376739.6982779|315970.62597616|9

==== Create new empty OGR/PostGIS layer ====

Check connection settings:

(for GRASS-OGR data driver)

{{cmd|v.external.out}} -p

dsn: /path/to/shapefiles
format: ESRI Shapefile

(for GRASS-PostGIS data driver)

{{cmd|v.external.out}} -p

conninfo: dbname=pgis_nc
format: PostGIS

New OGR/PostGIS layer can be created using {{cmd|v.edit}}, note that you need to specify feature type for newly created OGR/PostGIS layer (point, line or boundary).

{{cmd|v.edit}} map=pmap tool=create type=point

Check created OGR layer (direct access, OGR data driver only):

{{cmd|v.info}} -t map=PG:dbname=pgis_nc@OGR layer=pmap

...
points=0
...

Check created OGR/PostGIS layer (link):

{{cmd|v.external}} input=PG:dbname=pgis_nc layer=pmap

{{cmd|v.info}} -t map=pmap

Adding new point feature:

cat point.txt

P 1 1
375171.4992779 317756.72097616
1 1

{{cmd|v.edit}} -n map=pmap tool=add input=point.txt
{{cmd|v.info}} -t map=pmap

...
points=1
...

==== v.select speed test ====

Testing data:

* DBF input (attributes only)

{{cmd|g.mapset}} user1
{{cmd|db.connect}} -p

driver:dbf
database:$GISDBASE/$LOCATION_NAME/$MAPSET/dbf/

{{cmd|g.copy}} vect=bridges,b --o
{{cmd|g.copy}} vect=urbanarea,u --o

* SQLite input (attributes only)

{{cmd|g.mapset}} sqlite
{{cmd|db.connect}} -p

driver:sqlite
database:$GISDBASE/$LOCATION_NAME/$MAPSET/sqlite.db

{{cmd|g.copy}} vect=bridges,b --o
{{cmd|g.copy}} vect=urbanarea,u --o

* Export data to PostGIS database (from mapset 'sqlite')

{{cmd|v.out.ogr}} input=b input=PG:dbname=pgis_nc format=PostgreSQL olayer=bridges --o
{{cmd|v.out.ogr}} input=u input=PG:dbname=pgis_nc format=PostgreSQL olayer=urbanarea --o

* PostGIS input (geometry + attributes) - OGR data driver

{{cmd|g.mapset}} pg_ogr
export GRASS_VECTOR_OGR=1
{{cmd|v.external}} input=PG:dbname=pgis_nc layer=bridges output=b --o
{{cmd|v.external}} input=PG:dbname=pgis_nc layer=urbanarea output=u --o

* PostGIS input (geometry + attributes) - GRASS-PostGIS data driver

{{cmd|g.mapset}} pg
{{cmd|v.external}} input=PG:dbname=pgis_nc layer=bridges output=b --o
{{cmd|v.external}} input=PG:dbname=pgis_nc layer=urbanarea output=u --o

Writing output directly using OGR library (mapset 'pg_ogr'):

{{cmd|v.external.out}} -p

dsn: PG:dbname=pgis_nc
format: PostgreSQL

Writing output directly using PostGIS data driver (mapset 'pg'):

{{cmd|v.external.out}} -p

conninfo: dbname=pgis_nc
format: PostgreSQL

* DBF input

time {{cmd|v.select}} ain=b@user1 atype=point bin=u@user1 btype=area out=b_u ope=overlap --o

real 0m6.059s
user 0m4.780s
sys 0m0.588s

* SQLite input

time {{cmd|v.select}} ain=b@sqlite atype=point bin=u@sqlite btype=area out=b_u ope=overlap --o

real 0m2.239s
user 0m1.084s
sys 0m0.524s

* PostGIS input

time {{cmd|v.select}} ain=b atype=point bin=u btype=area out=b_u ope=overlap --o

real 0m20.609s
user 0m7.920s
sys 0m1.644s

''Note:'' Main reason of worse speed is random access used by v.select which is quite costly for OGR layers.

Time consumption for native output:

real 0m1.631s
user 0m0.860s
sys 0m0.768s

=== Digitize OGR layer using wxGUI ===

[[Image:wxgui-digitize-postgis.png|center|thumb|640px|Example of digitizing PostGIS layer (linked via {{cmd|v.external}}) in wxGUI]]

{{YouTube|7XKMGTcje-Q|desc=wxGUI - create and edit new OGR layer}}

{{YouTube|cyy-1HPQR5Y|desc=wxGUI - create and edit new PostGIS layer}}

== Using wxGUI ==

From ''menu''

File -> Link external formats

[[Image:wxgui-link-menu.png|center|frame|Link external data - Layer Manager menu]]

or from ''toolbar'' in Layer Manager.

[[Image:wxgui-link-tooltip.png|center|frame|Link external data - Layer Manager toolbar (1)]]
[[Image:wxgui-link-tool.png|center|frame|Link external data - Layer Manager toolbar (2)]]
[[Image:wxgui-v.external.png|center|thumb|400px|wxGUI {{cmd|v.external}} dialog]]
[[Image:wxgui-v.external.out.png|center|thumb|400px|wxGUI {{cmd|v.external.out}} dialog]]

== See also ==

* [[PostGIS]]
* [[PostGIS Topology]]

[[Category:Vector]]
[[Category:FAQ]]

Working with external data in GRASS 7

2025-09-23T07:41:29Z

Neteler: Neteler moved page Working with external data in GRASS 7 to Working with external data in GRASS: remove GRASS version from title

#REDIRECT [[Working with external data in GRASS]]

Working with external data in GRASS

2025-09-23T07:41:29Z

Neteler: Neteler moved page Working with external data in GRASS 7 to Working with external data in GRASS: remove GRASS version from title

This page explains how to effectively work with external raster and vector data in GRASS 7. See also [[PostGIS]] and [[PostGIS Topology]].
__TOC__
== Raster data ==

External raster data can be linked via {{cmd|r.external}}. List of supported formats can be determined by

{{cmd|r.external}} -f

To link file-based data formats, eg. GeoTiff

{{cmd|r.external}} input=ncrast/urban.tif output=urban

=== Raster data processing workflow when keeping data external ===

External raster maps can directly be linked into GRASS with {{cmd|r.external}} which saves time and disk space. Additionally, there is no more a need to store results in the internal GRASS format - with {{cmd|r.external.out}} the resulting maps are directly written to a GDAL supported format.

'''Preparations'''

GRASS can be used in an automated way by just defining a set of variables. See here for [[GRASS_and_Shell#Setting_the_variables|GRASS and Shell]] settings and [[GRASS_and_Python#Creating_Python_scripts_that_call_GRASS_functionality_from_outside|GRASS and Python]].

'''Data flow example'''

The script content could be looking like this:

<source lang="bash">
# register (rather than import) a GeoTIFF file in GRASS GIS:
r.external input=terra_lst1km20030314.LST_Day.tif output=modis_celsius

# define output directory for files resulting from subsequent calculations:
r.external.out directory=$HOME/gisoutput/ format="GTiff"

# perform calculations (here: extract pixels > 20 deg C)
# store output directly as GeoTIFF file, hence add the .tif extension:
r.mapcalc "warm.tif = if(modis_celsius > 20.0, modis_celsius, null() )"

# cease GDAL output connection and turn back to write standard GRASS raster files:
r.external.out -r

# use the result elsewhere
qgis $HOME/gisoutput/warm.tif
</source>

== Vector data ==

See trac {{twiki|Grass7/VectorLib/OGRInterface|OGR interface}} and {{twiki|Grass7/VectorLib/PostGISEditing| PG interface}} page for development issues.

=== Link external data ===

External vector data can be linked via {{cmd|v.external}} using [http://gdal.org/ogr OGR library] or ''GRASS-PostGIS data driver'' (<tt>format=PostgreSQL</tt>). List of supported formats can be determined by

{{cmd|v.external}} -f

To link ''file-based data formats'', eg. [http://gdal.osgeo.org/ogr/drv_shapefile.html ESRI Shapefile] using OGR library

{{cmd|v.external}} input=ncshape/ layer=railroads

Assuming that <tt>railroads.shp</tt> is located in directory <tt>ncshape</tt>.

To link ''database-based data formats'', eg. [http://gdal.osgeo.org/ogr/drv_pg.html PostGIS] using GRASS-PostGIS data driver

{{cmd|v.external}} input=PG:dbname=pgis_nc -l

PostGIS database <pgis_nc> contains 55 feature table(s):
...
bridges
...

{{cmd|v.external}} input=PG:dbname=pgis_nc layer=bridges output=b

Assuming that PostGIS layer named <tt>bridges</tt> is located in database <tt>pgis_nc</tt>. This layer is linked to GRASS mapset as vector map with name <tt>b</tt>. {{cmd|v.external}} also builds pseudo-topology over simple features which enables GRASS to access linked vector data on level 2. Note that data are stored as simple features, so no full topology support can be build based on this data.

By default PostGIS feature tables are linked using built-in '''GRASS-PostGIS data driver''' - it means that PostGIS geometry data are accessed by GRASS directly without any abstract level (like OGR library). When GRASS is built without PostgreSQL support or environmental variable <tt>GRASS_VECTOR_OGR</tt> exists, then GRASS will access PostGIS data using [http://www.gdal.org/drv_pg.html OGR-PostgreSQL] driver.

=== Direct access to external data ===

External data can be accessed using OGR library via ''virtual'' mapset <tt>OGR</tt>.

{{cmd|v.info}} map=PG:dbname=pgis_nc@OGR layer=bridges

Direct access using GRASS-PostGIS data driver is not currently possible.

=== Create new OGR layers using GRASS modules ===

==== v.extract showcase ====

GRASS 7 also supports write access to the external data using OGR or GRASS-PostGIS data driver. Showcase bellow:

{{cmd|v.external}} input=PG:dbname=pgis_nc layer=bridges output=b

{{cmd|v.out.ascii}} input=b where="cat < 10" --q

375171.4992779|317756.72097616|1
374247.5192779|317487.13697616|2
380230.2292779|316900.97897616|3
379191.4162779|316419.09697616|4
388958.8222779|316332.04697616|5
375875.2662779|316319.89597616|6
376393.5282779|316155.96797616|7
380647.5282779|316022.61797616|8
376739.6982779|315970.62597616|9

{{cmd|v.external.out}} input=PG:dbname=pgis_nc format=PostgreSQL

{{cmd|v.extract}} input=b output=b_9 where="cat < 10"

{{cmd|v.external}} input=PG:dbname=pgis_nc -l

PostGIS database <pgis_nc> contains 56 feature table(s):
b_9
bridges
...

Example of direct access to external data without creating a link (only OGR data driver)

{{cmd|v.out.ascii}} input=PG:dbname=pgis_nc@OGR layer=b_9

375171.4992779|317756.72097616|1
374247.5192779|317487.13697616|2
380230.2292779|316900.97897616|3
379191.4162779|316419.09697616|4
388958.8222779|316332.04697616|5
375875.2662779|316319.89597616|6
376393.5282779|316155.96797616|7
380647.5282779|316022.61797616|8
376739.6982779|315970.62597616|9

==== Create new empty OGR/PostGIS layer ====

Check connection settings:

(for GRASS-OGR data driver)

{{cmd|v.external.out}} -p

dsn: /path/to/shapefiles
format: ESRI Shapefile

(for GRASS-PostGIS data driver)

{{cmd|v.external.out}} -p

conninfo: dbname=pgis_nc
format: PostGIS

New OGR/PostGIS layer can be created using {{cmd|v.edit}}, note that you need to specify feature type for newly created OGR/PostGIS layer (point, line or boundary).

{{cmd|v.edit}} map=pmap tool=create type=point

Check created OGR layer (direct access, OGR data driver only):

{{cmd|v.info}} -t map=PG:dbname=pgis_nc@OGR layer=pmap

...
points=0
...

Check created OGR/PostGIS layer (link):

{{cmd|v.external}} input=PG:dbname=pgis_nc layer=pmap

{{cmd|v.info}} -t map=pmap

Adding new point feature:

cat point.txt

P 1 1
375171.4992779 317756.72097616
1 1

{{cmd|v.edit}} -n map=pmap tool=add input=point.txt
{{cmd|v.info}} -t map=pmap

...
points=1
...

==== v.select speed test ====

Testing data:

* DBF input (attributes only)

{{cmd|g.mapset}} user1
{{cmd|db.connect}} -p

driver:dbf
database:$GISDBASE/$LOCATION_NAME/$MAPSET/dbf/

{{cmd|g.copy}} vect=bridges,b --o
{{cmd|g.copy}} vect=urbanarea,u --o

* SQLite input (attributes only)

{{cmd|g.mapset}} sqlite
{{cmd|db.connect}} -p

driver:sqlite
database:$GISDBASE/$LOCATION_NAME/$MAPSET/sqlite.db

{{cmd|g.copy}} vect=bridges,b --o
{{cmd|g.copy}} vect=urbanarea,u --o

* Export data to PostGIS database (from mapset 'sqlite')

{{cmd|v.out.ogr}} input=b input=PG:dbname=pgis_nc format=PostgreSQL olayer=bridges --o
{{cmd|v.out.ogr}} input=u input=PG:dbname=pgis_nc format=PostgreSQL olayer=urbanarea --o

* PostGIS input (geometry + attributes) - OGR data driver

{{cmd|g.mapset}} pg_ogr
export GRASS_VECTOR_OGR=1
{{cmd|v.external}} input=PG:dbname=pgis_nc layer=bridges output=b --o
{{cmd|v.external}} input=PG:dbname=pgis_nc layer=urbanarea output=u --o

* PostGIS input (geometry + attributes) - GRASS-PostGIS data driver

{{cmd|g.mapset}} pg
{{cmd|v.external}} input=PG:dbname=pgis_nc layer=bridges output=b --o
{{cmd|v.external}} input=PG:dbname=pgis_nc layer=urbanarea output=u --o

Writing output directly using OGR library (mapset 'pg_ogr'):

{{cmd|v.external.out}} -p

dsn: PG:dbname=pgis_nc
format: PostgreSQL

Writing output directly using PostGIS data driver (mapset 'pg'):

{{cmd|v.external.out}} -p

conninfo: dbname=pgis_nc
format: PostgreSQL

* DBF input

time {{cmd|v.select}} ain=b@user1 atype=point bin=u@user1 btype=area out=b_u ope=overlap --o

real 0m6.059s
user 0m4.780s
sys 0m0.588s

* SQLite input

time {{cmd|v.select}} ain=b@sqlite atype=point bin=u@sqlite btype=area out=b_u ope=overlap --o

real 0m2.239s
user 0m1.084s
sys 0m0.524s

* PostGIS input

time {{cmd|v.select}} ain=b atype=point bin=u btype=area out=b_u ope=overlap --o

real 0m20.609s
user 0m7.920s
sys 0m1.644s

''Note:'' Main reason of worse speed is random access used by v.select which is quite costly for OGR layers.

Time consumption for native output:

real 0m1.631s
user 0m0.860s
sys 0m0.768s

=== Digitize OGR layer using wxGUI ===

[[Image:wxgui-digitize-postgis.png|center|thumb|640px|Example of digitizing PostGIS layer (linked via {{cmd|v.external}}) in wxGUI]]

{{YouTube|7XKMGTcje-Q|desc=wxGUI - create and edit new OGR layer}}

{{YouTube|cyy-1HPQR5Y|desc=wxGUI - create and edit new PostGIS layer}}

== Using wxGUI ==

From ''menu''

File -> Link external formats

[[Image:wxgui-link-menu.png|center|frame|Link external data - Layer Manager menu]]

or from ''toolbar'' in Layer Manager.

[[Image:wxgui-link-tooltip.png|center|frame|Link external data - Layer Manager toolbar (1)]]
[[Image:wxgui-link-tool.png|center|frame|Link external data - Layer Manager toolbar (2)]]
[[Image:wxgui-v.external.png|center|thumb|400px|wxGUI {{cmd|v.external}} dialog]]
[[Image:wxgui-v.external.out.png|center|thumb|400px|wxGUI {{cmd|v.external.out}} dialog]]

== See also ==

* [[PostGIS]]
* [[PostGIS Topology]]

[[Category:Vector]]
[[Category:FAQ]]
[[Category:GRASS 7]]

GRASS Citation Repository

2025-08-21T08:05:28Z

Neteler: /* GRASS GIS Manual citations */

== How to cite GRASS GIS ==

Please cite GRASS when using the software in your work. Here are some choices depending on the version used and the type of citation:

* GRASS GIS Manual citations,
* Peer reviewed general GRASS GIS articles,
* Books,
* Topic oriented citations.

Please select below:

=== GRASS GIS Manual citations ===

DOI (for all versions, shows latest release on top): [https://doi.org/10.5281/zenodo.5176030 10.5281/zenodo.5176030]

'''[https://www.fair4g.org/grass.html Overview of all DOI-based references to GRASS in scientific publications (according to CrossRef)]'''

Software:
* GRASS Development Team, 2022. Geographic Resources Analysis Support System (GRASS) Software, Version 8.2. Open Source Geospatial Foundation. Electronic document: https://grass.osgeo.org, DOI: [https://doi.org/10.5281/zenodo.5176030 10.5281/zenodo.5176030]
* GRASS Development Team, 2017. Geographic Resources Analysis Support System (GRASS) Software, Version 7.2. Open Source Geospatial Foundation. Electronic document: https://grass.osgeo.org, DOI: [https://doi.org/10.5281/zenodo.5176030 10.5281/zenodo.5176030]
* GRASS Development Team, 2016. Geographic Resources Analysis Support System (GRASS) Software, Version 7.0. Open Source Geospatial Foundation. Electronic document: https://grass.osgeo.org, DOI: [https://doi.org/10.5281/zenodo.5176030 10.5281/zenodo.5176030]
* GRASS Development Team, 2015. Geographic Resources Analysis Support System (GRASS) Software, Version 6.4. Open Source Geospatial Foundation. Electronic document: https://grass.osgeo.org, DOI: [https://doi.org/10.5281/zenodo.5176030 10.5281/zenodo.5176030]

Programmer's manual:
* GRASS Development Team, 2024. Geographic Resources Analysis Support System (GRASS 8) Programmer's Manual. Open Source Geospatial Foundation Project. Electronic document: https://grass.osgeo.org/programming8/
* GRASS Development Team, 2017. Geographic Resources Analysis Support System (GRASS 7) Programmer's Manual. Open Source Geospatial Foundation Project. Electronic document: https://grass.osgeo.org/programming7/
* GRASS Development Team, 2015. Geographic Resources Analysis Support System (GRASS 6) Programmer's Manual. Open Source Geospatial Foundation Project. Electronic document: https://grass.osgeo.org/programming6/

Related BibTeX entry:
<pre>
@Manual{GRASS_GIS_software,
title = {Geographic Resources Analysis Support System (GRASS GIS) Software, Version 8.2},
author = {{GRASS Development Team}},
organization = {Open Source Geospatial Foundation},
year = {2022},
url = {https://grass.osgeo.org},
doi = {https://doi.org/10.5281/zenodo.5176030}
}
</pre>

=== Historical manual pages ===
(Search US Army documents at https://discover.dtic.mil/products-services/)

* Predicting Database Requirements for Geographic Information Systems in the Year 2000: Long-Term Design Issues for GRASS (1992): https://apps.dtic.mil/sti/pdfs/ADA256862.pdf
* Geographic Resources Analysis Support System (GRASS) Version 4.0 User's Reference Manual (1992): https://apps.dtic.mil/sti/tr/pdf/ADA255218.pdf
* GRASS/GIS Implementation Guide (1989): https://apps.dtic.mil/sti/tr/pdf/ADA214623.pdf
* r.mapcalc: An Algebra for GIS and Image Processing (1984): https://apps.dtic.mil/sti/pdfs/ADA283923.pdf
* FORT HOOD GEOGRAPHIC INFORMATION SYSTEM: PILOT SYSTEM DEVELOPMENT AND USER INSTRUCTIONS (1983): https://apps.dtic.mil/sti/pdfs/ADA130618.pdf

=== GRASS GIS Addon Manual citations ===

Hint: when citing addons, you can simply use "grass-stable" in the URL which is auto-expanded to the latest version (e.g. grass82/). Like this the latest addon version is found.

Example:
* M. Lennert and GRASS Development Team, 2017: “Addon i.segment.stats. Geographic resources analysis support system (GRASS) software, version 7.2”, https://grass.osgeo.org/grass7/manuals/addons/i.segment.stats.html (1 June 2017)

=== Peer reviewed general GRASS GIS articles ===

* Neteler, M., Bowman, M.H., Landa, M., Metz, M., 2012. <i>GRASS GIS: A multi-purpose open source GIS</i>. Environ Model Soft 31, 124–130. ([https://dx.doi.org/10.1016/j.envsoft.2011.11.014 DOI] | [https://web.archive.org/web/20120424040115/https://gis.cri.fmach.it/uploads/neteler_grass_env_model_software.pdf PDF])
* Neteler, M., Bowman, M.H., Landa, M., Metz, M. (2012) "GRASS GIS: A multi-purpose open source GIS." Environmental Modelling & Software. Vol 31, pp. 124–130. ([https://dx.doi.org/10.1016/j.envsoft.2011.11.014 DOI] | [https://web.archive.org/web/20120424040115/https://gis.cri.fmach.it/uploads/neteler_grass_env_model_software.pdf PDF])

Related Bibtex entry:
<pre>
@article{neteler2012grass,
title={{GRASS GIS: a multi-purpose Open Source GIS}},
author={Neteler, M. and Bowman, M.H. and Landa, M. and Metz, M.},
journal={Environmental Modelling \& Software},
year={2012},
volume = {31},
pages = {124--130},
publisher={Elsevier},
doi = "10.1016/j.envsoft.2011.11.014"
}
</pre>

=== Books ===
* See https://grass.osgeo.org/learn/books/

=== Topic oriented citations ===
* see [[Citations for specific modules]]
* Citations of [[GRASS in the wild]] (add your publications here)

=== Historic citations ===

<font color="grey">
* GRASS Development Team, 2021. GRASS GIS 7 Programmer's Manual. Open Source Geospatial Foundation, USA. Electronic document: https://grass.osgeo.org/programming7/
* GRASS Development Team, 2016. GRASS 6 Programmer's Manual. Open Source Geospatial Foundation, USA. Electronic document: https://grass.osgeo.org/programming6/
* GRASS Development Team, 2012. GRASS 6.4 Users Manual. Open Source Geospatial Foundation, USA. Electronic document: https://grass.osgeo.org/grass64/manuals/
* GRASS Development Team, 2007. GRASS 6.2 Users Manual. ITC-irst, Trento, Italy. Electronic document: https://grass.osgeo.org/grass62/manuals/
* GRASS Development Team, 2002. GRASS 5.0 Users Manual. ITC-irst, Trento, Italy. Electronic document: https://grass.osgeo.org/grass57/manuals/html57_user/
* U.S. Army CERL, 1993. GRASS 4.1 Reference Manual. U.S. Army Corps of Engineers, Construction Engineering Research Laboratories, Champaign, Illinois, 1-425.
* Westervelt, J.D., Shapiro, M., Goran, W.D., Gerdes, D.P. (1992). Geographic Resources Analysis Support System (GRASS) Version 4.0 User's Reference Manual (No. CERL-ADP-N-87/22). CONSTRUCTION ENGINEERING RESEARCH LAB (ARMY) CHAMPAIGN IL. (PDF: https://apps.dtic.mil/sti/pdfs/ADA255218.pdf)
* Shapiro, M., Westervelt, J., Gerdes, D., Higgins, M., & Larson, M. (1989). GRASS 3.0 programmer's manual (No. CERL-ADP-N-89/14). CONSTRUCTION ENGINEERING RESEARCH LAB (ARMY) CHAMPAIGN IL. (PDF: https://apps.dtic.mil/sti/pdfs/ADA252461.pdf)
* ''Missing: Manuals of GRASS 1.0 and 2.0 - please submit to us!''
</font>

* Newsletter citations
** GRASSHopper CERL, https://grass.osgeo.org/about/history/
** [[Newsletter citations Vol1]] 2004
** [[Newsletter citations Vol2]] 2005
** [[Newsletter citations Vol3]] 2005
** [[Newsletter citations Vol4]] 2006

== Helpful tools and GRASS related bibliographic searches ==
* [https://grass.osgeo.org/grass-stable/manuals/addons/g.citation.html g.citation add-on module]
* Google Scholar:
** [https://scholar.google.com/scholar?q=GRASS+GIS Search for "GRASS GIS"] (activate BibTex export in "Scholar preferences")
** The virtual [https://scholar.google.com/citations?user=gJ0ZB0cAAAAJ GRASS Development Team] - GRASS GIS related papers
* [https://www.citeulike.org CiteULike] - [https://www.citeulike.org/tag/grass Search for "GRASS"]
* [https://www.scripps.edu/~cdputnam/software/bibutils/ Bibutils] bibliography conversion utilities
* [https://gbib.seul.org Gbib BibTeX editor] for GTK+Gnome
* [https://jabref.sourceforge.net/ JabRef] Multi-platform, multi-format bibliography tool
* [https://www.zotero.org/groups/gis Zotero citation manager GIS group] - with all known GRASS GIS and other GIS related references
* [[GRASS in the wild‎]]

[[Category:Citations]]
[[Category:Documentation]]
[[Category:FAQ]]

PSC Meeting 2025-08-08

2025-08-10T21:19:23Z

Neteler: add missing :Category:PSC

== Participants ==

* Anna Petrasova
* Helmut Kudrnovsky
* Huidae Cho
* Linda Karlovska
* Nicklas Larsson
* Paulo van Breugel
* Vaclav Petras
* Veronica Andreo

== Agenda ==

The topics proposed are:

* GRASS presence on different events
* Release 8.5
* New docs status
* Website rebranding status
* Mailing list removal? Question from Vicky in chat
* Decide on the Workspace topic and whether the solution suggested [https://github.com/OSGeo/grass/discussions/5916#discussioncomment-14045240 here] can be implemented. This would help to finalize and merge this [https://github.com/OSGeo/grass/pull/3113 PR].
* Discussion on the [https://github.com/OSGeo/grass/discussions/5909 workflow proposal]. Perhaps we need a File Browser pane?

== Minutes ==

* GRASS presence on different events
** FOSS4G EU: Alen presented the state of GRASS talk.
** FOSS4G NA (Nov 3-5)
*** Workshop: GRASS Addon Development with Python, Corey & Caitlin.
*** Talk: GRASS Meets Longest Flow Paths, Shortest Compute Times, Huidae.
*** Talk: State of GRASS, Corey.
** FOSS4G 2025 NZ:
*** Alen and Luca will attend and present the state of GRASS talk (Corey as co-author as he wrote the original abstract).
** FOSS4G.be: Moritz will present a state of GRASS talk

* GRASS 8.5 Release postponed to fall
** Waiting for JSON stuff from GSoC, which needs to be reviewed before release.
** Fix r.mapcalc issues regarding parallelization.
** Mac binaries: There's an issue with code signing. Needs to be solved before the release.
** Release scripts are in addons, and they run in a Docker image. Still several steps need to be manual and they are different depending on the type of release, i.e., major, minor, micro or RC.
** Jupyter notebook integration into GUI. Some things need to be defined/solved first:
*** Where to start the Jupyter server?
*** Where to store the notebooks: current working directory, let users choose, outside projects, within mapsets, provide a good default?
*** What happens when users do not have the dependencies installed?
*** It should work in Windows (both OSGeo4W and standalone installer).
** FHS should be ready for 8.6

* New docs:
** They are up and running, but there's still something missing on the automatic upload part (currently a personal GH token of MN is used which expires every 3 months).
** There’s the question of whether we need to have docs updated all the time or only when we release. In that sense, this is not a blocker for the release, but a nice-to-have.
** For this release, we do not remove the HTML files, which are mostly used locally in the GUI or when called with g.manual from the terminal.
** Addon docs with new format: they work online.

* GSoC:
** The student and mentors are working hard on adding JSON output to C tools.
** They are obsoleting the -g flag and moving to the format option.
** More clean-up should be done before GRASS 9 + Python tools.

* CMake:
** We need 3 steps: FHS ([https://github.com/OSGeo/grass/pull/5630 PR WIP]), GUI (Nicklas has a follow-up PR, but will need help with this), extensions (nothing done so far).
** MSVC binaries are built fine, but they don’t work out of the box because of missing environment variables; Can make them work by manually setting environment variables though; g.gui fails with Python exceptions

* Vicky's questions in the [https://matrix.to/#/!BOjyJgENYOLyXbRKxO:gitter.im/$xIdFsIr_HiEm6ASHtQCEt7GQkIrz_5zlLKOr-UpZLgo?via=gitter.im&via=matrix.org&via=osgeo.org GRASS chat]:
** We need to understand what they want to remove, and why; grass-user and grass-dev archives must not be removed, and neither must other list archives.
** Anna sends an email to Vicky.

* Workspace discussion:
** We agreed on having them within mapsets, but being asked if we want to save them or not - the opposite view is to save them automatically with a timer or so
* Anna proposed to remove the lock to delete maps in different mapsets from the GUI - check if this is independent from the owners of mapsets.

[[Category:PSC]]

PSC Meeting 2025-08-08

2025-08-10T21:17:24Z

Neteler: explain personal GH token use in automatic manual upload

Compile and Install

2025-07-10T10:43:31Z

Neteler: /* Linux Mint */ + libgtk-3-dev

'''Disclaimer''': This page explains how to turn the GRASS source code into an installable binary package ("compilation") for different operating systems. If you just want to get ready-to-use binaries, go [https://grass.osgeo.org/download/ here], otherwise read on...

== How to do compilation and installation of GRASS? ==

Here we explain the procedure to compile GRASS from GitHub, but it also applies to official GRASS 8 releases.

''For installation of precompiled binary packages, see the main [[Installation Guide]].''

For detailed information on compilation, please see the [https://github.com/OSGeo/grass/blob/main/INSTALL.md INSTALL] file in the source code.

=== Prerequisites ===

==== Extra libraries ====
GRASS needs at least two extra libraries: PROJ and GDAL/OGR. It is recommended to download them as ready-to-use packages for your software platform (Linux distribution, Windows, Mac...).

Other libraries needed to run GRASS are listed on the [https://github.com/OSGeo/grass/blob/main/REQUIREMENTS.md requirements page].

To compile, you will also need the respective "-devel" packages; see below for details.

==== Download GRASS source code ====

First, [https://grass.osgeo.org/download/ download the GRASS source code].

=== Generic Compilation and installation procedure ===

* It is wise that compilation processes are carried out as a normal user: If you want to get the source code in a place where you do not have write permissions (e.g. in /usr/local/src/) just follow this:
cd /usr/local/src/
su -c 'mkdir grass8'
su -c 'chown yourlogin:yourgroup grass8'

Otherwise if you have permissions just continue as a normal user:
mkdir $HOME/src
cd $HOME/src/
git clone https://github.com/OSGeo/grass.git grass_main

* run configure with parameters to adapt the compile process to your own system. To see what options can be passed to it, run:
./configure --help | less


It may (!) look like this:

./configure \
--with-cxx \
--with-sqlite \
--with-python \
--with-geos \
--with-gdal=/usr/bin/gdal-config \
--with-cairo --with-cairo-ldflags=-lfontconfig \
--with-freetype \
--with-freetype-includes=/usr/include/freetype2 \
--with-proj --with-proj-share=/usr/share/proj

You may have to explicitly state the path for certain packages (i.e., gdal). The Unix 'locate' command will come in handy for finding the path of the package you need (you may have to run locate as root ex: sudo locate gdal-config).

Please note that the paths mentioned may widely vary due to the distribution used.
See [[Compile_and_Install#Platform_Specific_Notes|Platform Specific Notes]] below.

Depending on your needs it may be a good idea to include debugging hooks.
: See [[GRASS_Debugging#Compile_Time_Setup]].
CFLAGS="-ggdb -Wall -Werror-implicit-function-declaration" ./configure ...

At the end of configuration process you should get report not much different from this:

GRASS is now configured for: x86_64-pc-linux-gnu

Source directory: /home/user/software/grass_main
Build directory: /home/user/software/grass_main
Installation directory: ${prefix}/grass84
Startup script in directory:${exec_prefix}/bin
C compiler: gcc -O2 -march=native -std=gnu99 -fexceptions -fstack-protector -m64 -fdiagnostics-color
C++ compiler: c++ -g -Wall
Building shared libraries: yes
OpenGL platform: X11

MacOSX application: no
MacOSX architectures:
MacOSX SDK:

BLAS support: yes
BZIP2 support: no
C++ support: yes
Cairo support: yes
DWG support: no
FFTW support: yes
FreeType support: yes
GDAL support: yes
GEOS support: yes
[...]

* Let's compile it (takes a little while...)!
make -j2
* At the end, you should get report not much different from this:
----------------------------------------------------------------------
Following modules are missing the 'description.html' file in src code:
----------------------------------------------------------------------
GRASS compilation log
-------------------------
Started compilation: Mon 19 Aug 2024 10:47:57 PM CEST
--
Errors in:
No errors detected.
--
Finished compilation: Mon 19 Aug 2024 10:55:12 PM CEST
(In case of errors please change into the directory with error and run 'make')

* If there is any error, change directory to directory with error and run "make" again. Report occurring bug to GRASS mailing list
* Once the installation process is finished, you're ready to install GRASS system wide.
su -c 'make install'
* enjoy GRASS:
grass

=== What else? ===

If you want to use [https://www.qgis.org QGIS], then also compile the GRASS-GDAL/OGR plugin. This is also useful to access your GRASS-data
from other application using GDAL/OGR like [[R_statistics/ R]].
* [[Compile and install GRASS and QGIS with GDAL/OGR Plugin]] (enables QGIS to read GRASS data directly)

=== Compile and install GDAL-GRASS plugin ===

* See [[Compile and install GDAL-GRASS plugin]]

=== Platform Specific Notes ===

==== Linux ====

Linux comes in various flavours, i.e. distributions.

===== Distribution related packaging =====

Examples:

* Archlinux: https://aur.archlinux.org/packages/grass
* Centos: https://src.fedoraproject.org/rpms/grass
* Debian: https://trac.osgeo.org/grass/wiki/DebianUbuntuPackaging
* EPEL: https://src.fedoraproject.org/rpms/grass
* Fedora: https://src.fedoraproject.org/rpms/grass
* Ubuntu: https://trac.osgeo.org/grass/wiki/DebianUbuntuPackaging

===== Alpine Linux =====

<source lang="bash">
# install compiler tools and libraries
apk add build-base bzip2-dev cairo-dev fftw-dev freetype-dev g++ gcc gdal-dev geos-dev git \
gnutls-dev libc6-compat libjpeg-turbo-dev libpng-dev make openjpeg-dev openblas-dev \
postgresql-dev proj-dev python3-dev py3-numpy-dev sqlite-dev tar tiff-dev unzip vim \
wget zip zstd-dev

# install needed tools and libraries when using GRASS
apk add attr bash bison bzip2 cairo curl fftw flex freetype gdal gdal-tools gettext geos gnutls \
jsoncpp libbz2 libexecinfo libjpeg-turbo libpng libunwind musl musl-utils ncurses openjpeg \
openblas py3-numpy py3-pillow py3-six postgresql proj-datumgrid proj-util sqlite sqlite-libs \
subversion tiff zstd zstd-libs

# get source code
cd ~
wget -c https://grass.osgeo.org/grass88/source/snapshot/grass-8.4.git_src_snapshot_latest.tar.gz

# unpack
tar xvfz grass-8.4.git_src_snapshot_latest.tar.gz
rm -f grass-8.4.git_src_snapshot_latest.tar.gz

# change into source code (update path name as needed)
cd grass-8.4.git_src_snapshot_2021_05_01/

# minimal configuration
./configure \
--with-cxx \
--with-gdal=/usr/bin/gdal-config \
--with-proj --with-proj-share=/usr/share/proj \
--with-geos \
--with-sqlite \
--without-nls \
--without-wxwidgets \
--without-fftw \
--without-cairo \
--without-freetype \
--without-opengl \
--without-odbc

# compilation
nice make -j2
</source>

===== Archlinux =====
You can install GRASS for Archlinux distribution based like Archlinux, Manjaro, EndeavourOS ...

* <big>'''Easiest method : use a prebuilt package using arch4edu repository'''</big>
''"Arch4edu is a community repository for Arch Linux and Arch Linux ARM that strives to provide the latest versions of most software used by college students."''

1. Add Arch4edu repository. Follow instructions from official documentation:

https://github.com/arch4edu/arch4edu/wiki/Add-arch4edu-to-your-Archlinux

2. Refresh packages list with

pacman -Syyu

3. Install GRASS package

pacman -S grass

* <big>'''Advanced method : use AUR (Arch User Repository) package'''</big>
Up-to-date links to Archlinux GRASS PKGBUILDs are on Arch User Repository.
PKGBUILD downloads and builds automatically sources from https://grass.osgeo.org/download/software/linux/.

You can use an AUR helper like ''pamac'', ''yay'', among others ... More info through this link https://wiki.archlinux.org/title/AUR_helpers

Exemple with ''yay'':
yay -S grass

* <big>'''Expert method : compile from source code'''</big>
If you want to compile it yourself, you could follow steps below :

''(As an alternative it is recommended to download PKGBUILD from AUR and then customize to your needs)''

Install dependencies :
pacman -S bzip2 cairo fftw fontconfig freetype2 gcc-libs gdal geos glibc glu libpng libtiff libx11 libgl netcdf pdal proj python-gdal python-numpy python-pillow python-wxpython readline zlib zstd

Download and extract sources : https://grass.osgeo.org/download/software/sources/

We can now start building GRASS

export PATH=~/usr/bin:$PATH && \
./configure \
--with-freetype-includes=/usr/include/freetype2 \
--with-wxwidgets \
--with-readline \
--with-pthread \
--with-netcdf \
--with-nls \
--with-geos \
--with-postgres \
--with-pdal=/usr/include/pdal \
--with-bzlib \
--with-zstd

Now let's compile and install it

make
make install

It's done, you can enjoy GRASS in Arch, just type "grass" in the terminal to launch it or look for grass in your menu.

===== Generic procedure for Debian-based distributions (Ubuntu, ...) =====

WORK IN PROGRESS

1. Install official GRASS package

sudo apt install grass grass-dev

2. Enable source code download

# do backup first
sudo cp /etc/apt/sources.list /etc/apt/sources.list.orig
sudo sed -i '/^#\sdeb-src /s/^# *//' /etc/apt/sources.list

3. Install GRASS dependencies

sudo apt build-dep grass

4. Download GRASS source code

git clone https://github.com/osgeo/grass

5. Compile GRASS from source code

cd grass

Configure:

grass --config build | sh

Optionally install missing dependencies (can happen when official GRASS package is not compatible with GRASS main), eg.

sudo apt install libzstd-dev

Compile:

make -j2

6. Run locally or install

./bin.x86_64-pc-linux-gnu/grass --version

or

sudo make install
grass --version

===== Debian =====

* Official [https://wiki.debian.org/DebianGis DebianGIS] packaging control files, available on git server:
https://salsa.debian.org/debian-gis-team/grass

====== GRASS 8 on Debian 11 (bullseye) ======

Install needed packages for GRASS 8.4:
apt-get update && \
apt-get install bison debhelper-compat dh-python doxygen fakeroot flex graphviz \
libblas-dev libbz2-dev libcairo2-dev libfftw3-dev libfreetype6-dev \
libgdal-dev libgeos-dev libgl1-mesa-dev libglu1-mesa-dev libjpeg-dev liblapack-dev libmotif-dev \
default-libmysqlclient-dev libncurses5-dev libnetcdf-dev libpng-dev libpq-dev \
libproj-dev libreadline-dev libsqlite3-dev libtiff-dev libxmu-dev libzstd-dev \
netcdf-bin pkg-config proj-bin python3 python3-dev python3-numpy python3-pil python3-ply \
python3-six python3-wxgtk4.0 wget unixodbc-dev zlib1g-dev

Download and unpack GRASS 8.4 source code (or fetch from GitHub: https://github.com/OSGeo/grass):

wget https://grass.osgeo.org/grass84/source/grass-8.4-latest.tar.gz
tar xvfz grass-8.4-latest.tar.gz
cd grass-8.4.*

Configuration:

CFLAGS="-Wall -Werror-implicit-function-declaration -fno-common -Wextra -Wunused" \
CXXFLAGS="-Wall" \
./configure \
--prefix=/usr/local \
--with-gdal --with-proj --with-proj-share=/usr/share \
--with-glw --with-nls --with-readline \
--with-cxx --enable-largefile \
--with-freetype --with-freetype-includes=/usr/include/freetype2 \
--with-sqlite --with-cairo --with-python=/usr/bin/python-config \
--with-wxwidgets --with-geos \
--with-netcdf=/usr/bin/nc-config --with-odbc=yes \
--with-openmp=yes --with-pthread=no

Compile:

make -j2

Install:

make install

Run:

grass --version

===== Ubuntu =====

There is a dedicated page on how to [[Compile_and_Install_Ubuntu | Compile the GRASS source code & install it in Ubuntu]].

===== Linux Mint =====

The [[Compile_and_Install_Ubuntu | detailed compilation guide for Ubuntu]] may just work. However, here is a short guide for Mint:

<source lang="bash">
# Linux Mint 21+

# be sure to have an updated system
sudo apt-get update && sudo apt-get upgrade -y

# installation of required libraries and compile tools
# recommended to give Python3 precedence over Python2 (which is end-of-life since 2024)
sudo update-alternatives --install /usr/bin/python python /usr/bin/python3 1

# install compiler tools and further dependencies (tested with Linux Mint 21)
# this is a single command, please copy-paste it entirely into the terminal:
sudo apt-get install \
build-essential \
flex make bison gcc libgcc1 g++ cmake ccache \
libproj-dev proj-data proj-bin \
libgeos-dev \
libgdal-dev python3-gdal gdal-bin \
python3 python3-dev \
python3-opengl \
python3-wxgtk4.0 \
python3-dateutil libgsl-dev python3-numpy \
wx3.2-headers libwxgtk3.2-dev libwxbase3.2-1 libfftw3-dev libgtk-3-dev\
libncurses5-dev zlib1g-dev gettext \
libbz2-dev libzstd-dev libfreetype6-dev \
libtiff5-dev libpnglite-dev libcairo libcairo-dev \
sqlite3 libsqlite3-dev libpq-dev \
libfftw3-3 libfftw3-dev \
libboost-thread-dev libboost-program-options-dev \
subversion \
checkinstall \
libglu1-mesa-dev libxmu-dev \
ghostscript wget -y
</source>

'''GUI''' - update wxpython:

<source lang="bash">
pip3 install -U -f https://extras.wxpython.org/wxPython4/extras/linux/gtk3/ubuntu-22.04 wxPython
</source>

Next steps:
* create a subdirectory in your HOME tree for storing the GRASS source code (and later compilation)
* get source code, one of the two options:
** a) download [https://grass.osgeo.org/grass84/source/snapshot/ GRASS source code weekly snapshot] (e.g. take the "8.x.git snapshot"), or
*** unpack source code
** b) current source code from GitHub:
*** <code>git clone https://github.com/OSGeo/grass.git</code>
* change into the source code directory

<source lang="bash">
# in the source code directory, "configure" the source code to prepare for compilation:
./configure \
--with-cxx \
--with-proj-share=/usr/share/proj \
--with-gdal=/usr/bin/gdal-config \
--with-geos \
--with-sqlite \
--with-nls \
--with-zstd \
--with-cairo --with-cairo-ldflags=-lfontconfig \
--with-freetype=yes --with-freetype-includes="/usr/include/freetype2/" \
--with-fftw \
--with-opengl-libs=/usr/include/GL \
--without-postgres \
--without-pdal \
--without-netcdf \
--without-mysql \
--without-odbc \
--without-openmp

# compile GRASS
make -j2

# install compiled GRASS on system
sudo make install

# use GRASS! Start on command line
grass
</source>

===== Enterprise Linux =====

Enterprise Linux (EL) and derivatives (that is, Red Hat Enterprise Linux, CentOS and Scientific Linux) is a popular and robust platform for servers and computing-heavy workstations, and is therefore a good fit for GIS specific requirements.

See: https://wiki.osgeo.org/wiki/Enterprise_Linux_GIS

===== Scientific Linux =====

See Centos

===== CentOS =====

You first need to add the EPEL repository for PROJ and GDAL, see [https://fedoraproject.org/wiki/EPEL/FAQ#How_can_I_install_the_packages_from_the_EPEL_software_repository.3F here]

Preparation '''Centos 8''':
dnf install epel-release

dnf install flex bison make zlib-devel gcc-c++ gettext \
fftw-devel libtiff-devel sqlite-devel \
proj proj-devel proj-datumgrid libxml2 \
geos geos-devel git \
netcdf netcdf-devel atlas-devel \
blas-devel lapack-devel libpq-devel \
python3-devel python3-numpy \
python3-dateutil python3-imaging python3-matplotlib \
gdal gdal-libs gdal-python-tools python3-gdal gdal-devel \
wxGTK3-devel mesa-libGL-devel mesa-libGLU-devel \
libXmu-devel libX11-devel

'''GRASS 8 compilation and installation'''

[https://grass.osgeo.org/grass84/source/snapshot/ Download source code] (e.g., --> "Download latest 8.4 code)" and configure GRASS 8 (suggestion: save this as script):

./configure \
--with-cxx \
--with-proj --with-proj-share=/usr/share/proj \
--with-gdal=/usr/bin/gdal-config \
--with-sqlite \
--with-python \
--with-cairo --with-cairo-ldflags=-lfontconfig \
--with-freetype --with-freetype-includes=/usr/include/freetype2 \
--with-wxwidgets=/usr/bin/wx-config \
--with-openmp \
--with-blas --with-blas-includes=/usr/include/atlas-x86_64-base/ \
--with-lapack --with-lapack-includes=/usr/include/atlas-x86_64-base/ \
--with-fftw \
--with-geos \
--with-netcdf \
--without-ffmpeg \
--without-mysql \
--without-postgres \
--without-odbc \
--without-fftw

Compile:
make
or on a multicore system (number depends of available cores):
make -j4

For a system wide installation, run as root user:
make install
OR simply run it directly from the source code directory (substitute ARCH with i686 or x86_64):

bin.$ARCH/grass -gui

In this case, for convenience, add it to the search path:
mkdir $HOME/bin
cd $HOME/bin
# example:
ln -s $HOME/software/grass84_release/bin.x86_64-pc-linux-gnu/grass .

Now use it subsequently with
grass -gui

'''Installation grass on a HPC system with '''Centos 7''' and no root privileges:'''

This assumes that python3, fftw, proj, gdal and geos are available on the HPC system, either as modules or as installed software.

Download and prepare some dependencies (freetypes and zstd)
mkdir -p $HOME/grass/freetypes
cd $HOME/grass/freetypes
wget path/to/freetype-2.9.1.tar.gz
tar -xf freetype-2.9.1.tar.gz

mkdir $HOME/grass/zstd
cd mkdir $HOME/grass/zstd
wget path/to/v1.4.4/zstd-1.4.4.tar.gz
tar -xf zstd-1.4.4.tar.gz
make install PREFIX=./

Add the ZSTD path to your LD_LIBRARY_PATH

tee -a $HOME/.bashrc > /dev/null << EOT
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$HOME/grass/zstd/zstd-1.4.4/lib
EOT

The configure command could look like this
./configure \
-prefix=$HOME/grass \
--enable-64bit --with-fftw-includes=/path/to/fftw/include/ \
--with-fftw-libs=/path/to/fftw/lib/ \
--with-freetype-includes=$HOME/grass/freetypes/freetype-2.9.1/include/ \
--with-netcdf --with-geos --with-blas --with-lapack --with-postgres \
--with-zstd-includes=$HOME/grass/zstd/zstd-1.4.4/lib/ \
--with-zstd-libs=$HOME/grass/zstd/zstd-1.4.4/lib/ \
--with-gdal=/path/to/gdal-config # This could be the path to a gdal version compiled from source

Finally as usual:
make; make install

grass

===== Gentoo =====

./configure \
--with-freetype=yes --with-freetype-includes="/usr/include/freetype2/"

See also https://packages.gentoo.org/package/sci-geosciences/grass

===== Funtoo =====

{{MovedToTrac|FuntooLinux}}

===== Fedora =====

====== GRASS 8 on Fedora ======

'''Preparation''' for the compilation of GRASS 8+ source code (F36+):

dnf install gcc gcc-c++ bison flex ncurses-devel gettext proj-devel \
gdal gdal-devel sqlite-devel xml2 mesa-libGL-devel cairo-devel \
fftw-devel mesa-libGLU-devel libXmu-devel libX11-devel geos geos-devel \
libtiff-devel python3-devel numpy wxGTK-devel gawk git \
python3-dateutil python3-imaging python3-matplotlib-wx doxygen python3-sphinx \
libzstd-devel libzstd python3-six python3-numpy python3-wxpython4 \
proj-data PDAL-devel PDAL-libs

# optionally also: netcdf-devel postgresql-devel
# atlas-devel lapack-devel lapack-devel
# laszip laszip-devel
# proj-data-at proj-data-au proj-data-be ...

''Note 1: the optional ffmpeg-devel comes from the rpmfusion-free repository ([https://rpmfusion.org/Configuration/ configuration]).''

'''Download''' and unpack the source code:
* GRASS 8: [https://grass.osgeo.org/grass84/source/snapshot/ weekly snapshot] - [https://github.com/OSGeo/grass/releases GitHub repository]

'''Configure''': This is an example how to configure the source code on a Fedora system:

./configure \
--with-cxx \
--with-gdal=/usr/bin/gdal-config \
--with-proj --with-proj-share=/usr/share/proj \
--with-geos \
--with-pdal \
--with-sqlite \
--with-nls \
--with-wxwidgets=/usr/bin/wx-config \
--with-fftw \
--with-cairo --with-cairo-ldflags=-lfontconfig \
--with-freetype --with-freetype-includes=/usr/include/freetype2 \
--enable-largefile \
--without-odbc

''Extra 1:'' If you also want '''FFMPEG support''' - it requires 'dnf install fftw-devel' from the rpmfusion-free repository. Then add to the configuration lines above:

--with-ffmpeg --with-ffmpeg-includes="/usr/include/ffmpeg /usr/include/ffmpeg/libav* /usr/include/ffmpeg/libpostproc /usr/include/ffmpeg/libswscale" \

''Extra 2:'' For '''LAPACK/BLAS support''' (addons i.spec.unmix, v.kriging etc), install "dnf install lapack lapack-devel blas blas-devel atlas atlas-devel". Then add to the configuration lines above:
--with-blas --with-blas-includes=/usr/include/atlas-x86_64-base/ \
--with-lapack --with-lapack-includes=/usr/include/atlas-x86_64-base/ \

''Extra 3:'' For '''ZSTD support''' (Zstandard compression algorithm), first install "dnf install libzstd libzstd-devel zstd". After installing the zstd related packages, add to the configuration lines above:
--with-zstd \

Finally '''compile''' the configured source code:
make
or on multicore (number depends of available cores):
make -j4
and
make install # requires root permissions unless you become owner of /usr/local/

Then use GRASS 8 and enjoy!

grass --version

===== openSUSE =====

To build GRASS on openSUSE:

''Application:Geo'' repo to be added (see [https://software.opensuse.org//download.html?project=Application%3AGeo&package=gdal Install package Application:Geo]

<source lang="bash">
# example for Leap 42 version:
sudo zypper addrepo https://download.opensuse.org/repositories/Application:Geo/openSUSE_Leap_42.3/Application:Geo.repo
sudo zypper refresh
</source>

RPM packages to be installed:
<source lang="bash">
sudo zypper install bison flex freetype2-devel fftw3-devel gcc-c++ \
libgdal-devel libgeos-devel libjpeg-devel libpng-devel libtiff-devel \
man proj libproj-devel readline-devel netcdf-devel ncurses-devel \
mysql-devel postgresql-devel sqlite-devel unixODBC-devel \
tcl-devel tk-devel xorg-x11-Mesa-devel libXmu-devel \
python-numpy python-dateutil python-devel python-opengl \
python-wxWidgets python-xml python-dateutil wxWidgets-devel \
zlib-devel doxygen python-sphinx
</source>

Source code configuration:
<source lang="bash">
./configure \
--enable-largefile \
--with-proj-share=/usr/share/proj \
--with-cxx \
--with-lapack=yes \
--with-motif \
--with-gdal=/usr/bin/gdal-config \
--with-postgres --with-postgres-includes=/usr/include/pgsql \
--with-mysql --with-mysql-includes=/usr/include/mysql \
--with-fftw \
--with-readline \
--with-netcdf \
--with-geos \
--with-nls \
--with-sqlite \
--with-freetype \
--with-freetype-includes=/usr/include/freetype2 \
--with-wxwidgets \
--with-odbc \
--with-python
</source>

Then compile with "make [-j2]".

===== RPM SPEC files =====
* [https://build.opensuse.org/package/show?package=grass&project=Application%3AGeo OpenSuSe]
* [https://pkgs.fedoraproject.org/cgit/rpms/grass.git/tree/grass.spec Fedora]
* ...

==== macOS ====

Compiling GRASS for macOS is not fundamentally different from for other *nix systems. It is on the contrary quite similar, but what differ is the lack of a default package management system for software GRASS depends on. This leaves the mac user to either: (1) compile the dependencies one-by-one; (2) compiling with one of the third-party package management systems avaliable; or (4) a combination thereof.

If you are interested in installing a precompiled version, please check out the [https://grass.osgeo.org/download/software/mac-osx/ official download site].

To date, maybe the easiest way to compile for Mac is by using [https://github.com/nilason/grass-conda GRASS app build script] which is based on the instructions below for building using Anaconda. It will install dependencies, package and install an app bundle with just a command in Terminal.

===== Compilation and installation =====

For more up-to-date instructions please read:

* [https://github.com/nilason/grass-conda Compiling on macOS using Conda] (Intel / Apple silicon based machine M1)
* [[Compiling on macOS using Anaconda]]
* [[Compiling on macOS using Homebrew]]
* [[Compiling on macOS using MacPorts]]

===== Legacy instructions =====

The following compilation and installation instructions are rather outdated as a whole. They do, however, contain parts and snippets that still may be very instructive and useful.

* [[Compiling on MacOSX]]
* [[Compiling on MacOSX using Fink]]
* [https://web.archive.org/web/20180718005252/https://www.kyngchaos.com/software/frameworks#build_scripts build scripts for dependencies]

Troubleshooting:
* solving errors at starting GRASS: [[MacOSX GRASS errors]]

==== FreeBSD / NetBSD ====

The recommended compiler tools are GCC, GNU make, GNU coreutils (for install), and flex. All are available through the respective package managing tools (pkg_add for FreeBSD and pkgin install for NetBSD) and for recent *BSD versions most likely installed by default.

GRASS 8 should compile on FreeBSD and NetBSD.

It is highly recommended to install GDAL/OGR and PROJ first. These libraries and tools are available as [https://www.freebsd.org/ports/ ports for FreeBSD] and [https://www.pkgsrc.org/ packages for NetBSD].

Optional functionality is listed with ''./configure --help'', and related libraries and tools might need to be installed first.

You then may need to edit include/Make/Platform.make and set
ICONVLIB = -liconv

==== AIX ====

A recent [ftp://ftp.gnu.org/gnu/make/ GNU make] (>= 3.81) and GNU coreutils are required. These are available with the [https://www-03.ibm.com/systems/power/software/aix/linux/toolbox/download.html IBM AIX toolbox] or through third-party AIX software repositories, e.g. [https://www.bullfreeware.com/ bullfreeware] and [https://www.perzl.org/aix/ perzl.org]. Note that 'make' does not work, only 'gmake' works.

General instructions to compile on AIX are e.g. [https://www.perzl.org/aix/index.php?n=Main.Instructions here]

On AIX, compilation results by default in 32 bit applications and static libraries. The [https://developer.ibm.com/components/aix/ IBM documentation] explains how to build 64 bit applications and shared libraries with GCC.

'''GRASS 8: Using the IBM xlc compiler:'''

Get and install (in this order):
* [ftp://ftp.gnu.org/gnu/tar/ GNU tar]
* [ftp://ftp.gnu.org/gnu/make/ GNU make] (>= 3.81)
* [https://www.sqlite.org SQLite]
* [https://trac.osgeo.org/proj/ PROJ.4] (for ./configure parameters, see [[Talk:Compile and Install|here]])
* [https://www.gdal.org GDAL] (for ./configure parameters, see [[Talk:Compile and Install|here]])
* [https://grass.osgeo.org/grass84/source/snapshot/ GRASS 8]

The environment variables and configure command that worked:
<pre>
## AIX 5.x

export LIBPATH=/opt/freeware/lib64:/opt/freeware/lib
# make 'ar' happy
export OBJECT_MODE=64

PREFIX=$HOME/private/bin
./configure \
--prefix=$PREFIX \
--disable-shared \
--with-cxx \
--with-proj-includes=$PREFIX/include/ \
--with-proj-libs=$PREFIX/lib/ \
--with-proj-share=$PREFIX/share/proj/ \
--with-sqlite \
--with-sqlite-includes=$PREFIX/include/ \
--with-sqlite-libs=$PREFIX/lib/ \
--with-tiff=no \
--with-png=no \
--with-fftw=no \
--with-cairo=no \
--with-freetype=no
</pre>

'''GRASS 8: Using the GNU gcc compiler:'''

Get and install (in this order):
* if needed, [ftp://ftp.gnu.org/gnu/tar/ GNU tar]
* if needed (the name is often 'gmake' and not 'make') [ftp://ftp.gnu.org/gnu/make/ GNU make] (>= 3.81)
* [https://www.sqlite.org SQLite]
* [https://trac.osgeo.org/proj/ PROJ.4] (for ./configure parameters, see [[Talk:Compile and Install|here]])
* [https://www.gdal.org GDAL] (for ./configure parameters, see [[Talk:Compile and Install|here]])
* [https://grass.osgeo.org/grass84/source/snapshot/ GRASS 8]

The environment variables and configure command that worked for AIX 7.x:
<pre>
## AIX 7.x
export CC="gcc"
export CXX="g++"
PREFIX=$HOME/bin

LDFLAGS="-Wl,-bsvr4,-R,/opt/freeware/lib -L/opt/freeware/lib" CPPFLAGS="-I/opt/freeware/include" ./configure \
--prefix=$PREFIX \
--enable-shared \
--with-includes=/opt/freeware/include --with-libs=/opt/freeware/lib \
--with-cxx \
--with-proj-includes=$PREFIX/include/ \
--with-proj-libs=$PREFIX/lib/ \
--with-proj-share=$PREFIX/share/proj/ \
--with-gdal=$PREFIX/bin/gdal-config \
--with-sqlite \
--with-sqlite-libs=$PREFIX/lib --with-sqlite-includes=$PREFIX/include \
--with-png=no \
--with-tiff=no \
--with-fftw=no \
--with-cairo=no \
--with-opengl=no \
--with-freetype=no
</pre>

==== MS-Windows ====

See also [[WinGRASS Current Status]] for latest updates.

===== MS-Windows/native =====

GRASS on Windows using a standalone installer. It is still MinGW based (we are going to move this to CMake in 2024+).

Instructions to compile from source code:
* [https://trac.osgeo.org/grass/wiki/CompileOnWindows GRASS Windows Native Binary Building Guide]

===== MS-Windows/OSGeo4W =====

OSGeo4W is an installer for a broad set of open source geospatial software packages including GRASS as well as many other packages (QGIS, GDAL/OGR, and more).

* See [https://trac.osgeo.org/osgeo4w/ OSGeo4W]

===== MS-Windows/Cygwin =====

* See the [[Cygwin]] wiki pages

=== Common problems and solutions ===

During compilation, error can occur if certain packages are not installed. Here a list of problems with solution:

* error: X11/Xlib.h: No such file or directory
** this suggests that you don't have the X headers installed
** Solution: Install the libx11-dev package

* error: g.list: error while loading shared libraries: libgdal1.6.0.so.1: cannot open shared object file: No such file or directory
** this error appears in the shell right after the user clicks GUI's "Start GRASS" button. The GUI shows an error about geographic extent and gets closed afterwards.
** It happens when you launch bin.i686 executable on 64bit system. Be careful and choose the right architecture.

* error: lib/python/ctypes
** This error appears during the compilation: <code>free(): invalid pointer Aborted (core dumped)</code>
** It happens when you have multiple <code>libproj</code> versions on your system (check it with command <code>ldd PATH_TO_GRASS_INSTALL/lib/libgrass_gproj.so | grep proj</code> - when this is not your problem, you should obtain exactly one result)
** Solution: Try to reinstall <code>libproj-dev</code> and <code>proj-data</code>

=== Static compilation ===

In order to get static rather than dynamically linked binaries, configure like this:

./configure --disable-shared --enable-static

This will however break the wxGUI and GRASS 8 completely because "ctypes" wants to link against shared libs, or there is something in the static libs that "ctypes" does not like.

=== Optimization ===

GCC and other compilers support [https://gcc.gnu.org/onlinedocs/gcc-4.3.3/gcc/Optimize-Options.html#Optimize-Options optimization]

If you would like to set compiler optimisations, for a possibly faster binary, type (don't enter a ";" anywhere):

CFLAGS=-O ./configure
or,
setenv CFLAGS -O
./configure

whichever works on your shell. Use -O2 instead of -O if your compiler supports this (note: O is the letter, not zero). Using the "gcc" compiler, you can also specify processor specific flags (examples, please suggest better settings to us):

CFLAGS="-mcpu=athlon -O2" # AMD Athlon processor with code optimisations
CFLAGS="-march=amdfam10" # AMD Phenom II X4 64bit processor with gcc >=4.3
CFLAGS="-mcpu=pentium" # Intel Pentium processor
CFLAGS="-mcpu=pentium4" # Intel Pentium4 processor
CFLAGS="-O2 -msse -msse2 -mfpmath=sse -minline-all-stringops" # Intel XEON 64bit processor
CFLAGS="-mtune=nocona -m64 -minline-all-stringops" # Intel Pentium 64bit processor

To find out optional CFLAGS for your platform, enter:
gcc -dumpspecs

See also: https://gcc.gnu.org/

A real fast GRASS version (and small binaries) will be created with LDFLAGS set to "stripping" (but this disables debugging):

CFLAGS="-O2 -mcpu=<cpu_see_above> -Wall" LDFLAGS="-s" ./configure

=== Configure options and their meanings ===

For configure there are many options and some GRASS modules are built only if some options are set. Here are listed common configuration options with short explanation.

* --prefix=/path - Sets path where GRASS will be installed. GRASS will reside in /path/grass-version.
* --enable-largefile - Enables large (>2Gb on 32bit systems) support. For current large file support status look at [[Large File Support]] page.
* --with-cxx - Enables compilation of C++ code. Required for r.terraflow module.
* --with-readline - Enables readline support. If readline is enabled, you can use its history/editing facilities when entering r.mapcalc expressions on stdin.
* --with-glw - Enables GLw support. The GLw library provides OpenGL "canvas" widgets for Athena and Motif.

That switch is unnecessary for normal compilation. It's only
required for r3.showdspf, which isn't normally built; if you
want it, you have build it manually
(e.g. "make -C raster3d/r3.showdspf").
As similar functionality is now provided by NVIZ, r3.showdspf
is deprecated.
r3.showdspf uses the Motif widget (so you also need a
Motif library, e.g. Lesstif or OpenMotif).
[https://grass.itc.it/pipermail/grassuser/2006-December/037475.html Glynn Clements at GRASS-user mailing list]

=== Parallelized compilation on multi-core CPUs ===

You can dramatically accelerate the compilation of the GRASS code with the -j flag of "make" if you have a multi-core CPU system. This determines the maximum number of jobs to have running at once, so cores don't have to sit idle waiting for jobs on other cores to complete. A good rule of thumb for this value is <tt>number_of_cores * 1.5</tt>, but note that setting any higher than the actual number of cores will only affect the timing slightly. For example, on a dual-core processor:
make -j 4



== GRASS-GDAL plugin ==

* see [[Compile and install GRASS and QGIS with GDAL/OGR Plugin]]

== Addons ==

Please note that the installation of [https://grass.osgeo.org/grass-stable/manuals/addons/ GRASS addons] can be easily done with the {{cmd|g.extension}} manager. The compile instructions below are aiming at own development.

=== Compiled modules ===

This is the general way which works for C modules as well as scripts (Python or Shell/Bash modules) which has HTML documentation.

'''Requirements:'''

Either:
* a binary GRASS package, or
* source code which has been prepared with:
./configure [opionally flags]
make libs

Each of the [[GRASS_AddOns|addon]] modules should come with a Makefile. To compile it, just run:
make MODULE_TOPDIR=/path/to/grass84/

Note that the <tt>/path/to/grass84</tt> has to be absolute, not relative.

If using Bash it may be useful to set that up as an alias:
alias gmake64='make MODULE_TOPDIR=/path/to/grass84/'

Installation (perhaps requires "sudo"):
make MODULE_TOPDIR=/path/to/grass84/ install

Note: Compiled addons may require a re-compilation if you changed/updated your GRASS standard binaries.

==== If binary comes with a -dev package ====

''(work in progress, this text states how it eventually will be :)''
Nowadays one does not need to the source code, nor compiling GRASS by oneself to be able to add add-ons. On Debian, you can just install the grass-dev package and then run:
make MODULE_TOPDIR=/usr/lib/grass84/ INST_DIR=/usr/lib/grass84/

The grass-dev package essentially provides GRASS's <tt>include</tt> header files and Make configuration files.

=== Scripts ===

If the addon module is a script, it is sufficient to copy it into the (GRASS binaries) path somewhere. Alternatively, install addons into a separate GRASS addons binaries/scripts directory which is easier to maintain. It avoids getting clobbered every time you reinstall GRASS. To use these separately stored scripts, set and export the GRASS_ADDON_PATH environment variable before starting GRASS and it will automatically be added to the module search path (see the {{cmd|variables}} help page). To simplify this, do for example:

# add in $HOME/.bashrc:
GRASS_ADDON_PATH=/usr/local/grass/addons/
export GRASS_ADDON_PATH

Make sure that the script is executable, then just call it in GRASS typing the filename. Python scripts need to be called writing the extension as well, like:

GRASS (nc_spm):~ > v.krige.py

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

Compile and Install

2025-07-10T10:10:14Z

Neteler: Linux Mint: update packages

'''Disclaimer''': This page explains how to turn the GRASS source code into an installable binary package ("compilation") for different operating systems. If you just want to get ready-to-use binaries, go [https://grass.osgeo.org/download/ here], otherwise read on...

== How to do compilation and installation of GRASS? ==

Here we explain the procedure to compile GRASS from GitHub, but it also applies to official GRASS 8 releases.

''For installation of precompiled binary packages, see the main [[Installation Guide]].''

For detailed information on compilation, please see the [https://github.com/OSGeo/grass/blob/main/INSTALL.md INSTALL] file in the source code.

=== Prerequisites ===

==== Extra libraries ====
GRASS needs at least two extra libraries: PROJ and GDAL/OGR. It is recommended to download them as ready-to-use packages for your software platform (Linux distribution, Windows, Mac...).

Other libraries needed to run GRASS are listed on the [https://github.com/OSGeo/grass/blob/main/REQUIREMENTS.md requirements page].

To compile, you will also need the respective "-devel" packages; see below for details.

==== Download GRASS source code ====

First, [https://grass.osgeo.org/download/ download the GRASS source code].

=== Generic Compilation and installation procedure ===

* It is wise that compilation processes are carried out as a normal user: If you want to get the source code in a place where you do not have write permissions (e.g. in /usr/local/src/) just follow this:
cd /usr/local/src/
su -c 'mkdir grass8'
su -c 'chown yourlogin:yourgroup grass8'

Otherwise if you have permissions just continue as a normal user:
mkdir $HOME/src
cd $HOME/src/
git clone https://github.com/OSGeo/grass.git grass_main

* run configure with parameters to adapt the compile process to your own system. To see what options can be passed to it, run:
./configure --help | less


It may (!) look like this:

./configure \
--with-cxx \
--with-sqlite \
--with-python \
--with-geos \
--with-gdal=/usr/bin/gdal-config \
--with-cairo --with-cairo-ldflags=-lfontconfig \
--with-freetype \
--with-freetype-includes=/usr/include/freetype2 \
--with-proj --with-proj-share=/usr/share/proj

You may have to explicitly state the path for certain packages (i.e., gdal). The Unix 'locate' command will come in handy for finding the path of the package you need (you may have to run locate as root ex: sudo locate gdal-config).

Please note that the paths mentioned may widely vary due to the distribution used.
See [[Compile_and_Install#Platform_Specific_Notes|Platform Specific Notes]] below.

Depending on your needs it may be a good idea to include debugging hooks.
: See [[GRASS_Debugging#Compile_Time_Setup]].
CFLAGS="-ggdb -Wall -Werror-implicit-function-declaration" ./configure ...

At the end of configuration process you should get report not much different from this:

GRASS is now configured for: x86_64-pc-linux-gnu

Source directory: /home/user/software/grass_main
Build directory: /home/user/software/grass_main
Installation directory: ${prefix}/grass84
Startup script in directory:${exec_prefix}/bin
C compiler: gcc -O2 -march=native -std=gnu99 -fexceptions -fstack-protector -m64 -fdiagnostics-color
C++ compiler: c++ -g -Wall
Building shared libraries: yes
OpenGL platform: X11

MacOSX application: no
MacOSX architectures:
MacOSX SDK:

BLAS support: yes
BZIP2 support: no
C++ support: yes
Cairo support: yes
DWG support: no
FFTW support: yes
FreeType support: yes
GDAL support: yes
GEOS support: yes
[...]

* Let's compile it (takes a little while...)!
make -j2
* At the end, you should get report not much different from this:
----------------------------------------------------------------------
Following modules are missing the 'description.html' file in src code:
----------------------------------------------------------------------
GRASS compilation log
-------------------------
Started compilation: Mon 19 Aug 2024 10:47:57 PM CEST
--
Errors in:
No errors detected.
--
Finished compilation: Mon 19 Aug 2024 10:55:12 PM CEST
(In case of errors please change into the directory with error and run 'make')

* If there is any error, change directory to directory with error and run "make" again. Report occurring bug to GRASS mailing list
* Once the installation process is finished, you're ready to install GRASS system wide.
su -c 'make install'
* enjoy GRASS:
grass

=== What else? ===

If you want to use [https://www.qgis.org QGIS], then also compile the GRASS-GDAL/OGR plugin. This is also useful to access your GRASS-data
from other application using GDAL/OGR like [[R_statistics/ R]].
* [[Compile and install GRASS and QGIS with GDAL/OGR Plugin]] (enables QGIS to read GRASS data directly)

=== Compile and install GDAL-GRASS plugin ===

* See [[Compile and install GDAL-GRASS plugin]]

=== Platform Specific Notes ===

==== Linux ====

Linux comes in various flavours, i.e. distributions.

===== Distribution related packaging =====

Examples:

* Archlinux: https://aur.archlinux.org/packages/grass
* Centos: https://src.fedoraproject.org/rpms/grass
* Debian: https://trac.osgeo.org/grass/wiki/DebianUbuntuPackaging
* EPEL: https://src.fedoraproject.org/rpms/grass
* Fedora: https://src.fedoraproject.org/rpms/grass
* Ubuntu: https://trac.osgeo.org/grass/wiki/DebianUbuntuPackaging

===== Alpine Linux =====

<source lang="bash">
# install compiler tools and libraries
apk add build-base bzip2-dev cairo-dev fftw-dev freetype-dev g++ gcc gdal-dev geos-dev git \
gnutls-dev libc6-compat libjpeg-turbo-dev libpng-dev make openjpeg-dev openblas-dev \
postgresql-dev proj-dev python3-dev py3-numpy-dev sqlite-dev tar tiff-dev unzip vim \
wget zip zstd-dev

# install needed tools and libraries when using GRASS
apk add attr bash bison bzip2 cairo curl fftw flex freetype gdal gdal-tools gettext geos gnutls \
jsoncpp libbz2 libexecinfo libjpeg-turbo libpng libunwind musl musl-utils ncurses openjpeg \
openblas py3-numpy py3-pillow py3-six postgresql proj-datumgrid proj-util sqlite sqlite-libs \
subversion tiff zstd zstd-libs

# get source code
cd ~
wget -c https://grass.osgeo.org/grass88/source/snapshot/grass-8.4.git_src_snapshot_latest.tar.gz

# unpack
tar xvfz grass-8.4.git_src_snapshot_latest.tar.gz
rm -f grass-8.4.git_src_snapshot_latest.tar.gz

# change into source code (update path name as needed)
cd grass-8.4.git_src_snapshot_2021_05_01/

# minimal configuration
./configure \
--with-cxx \
--with-gdal=/usr/bin/gdal-config \
--with-proj --with-proj-share=/usr/share/proj \
--with-geos \
--with-sqlite \
--without-nls \
--without-wxwidgets \
--without-fftw \
--without-cairo \
--without-freetype \
--without-opengl \
--without-odbc

# compilation
nice make -j2
</source>

===== Archlinux =====
You can install GRASS for Archlinux distribution based like Archlinux, Manjaro, EndeavourOS ...

* <big>'''Easiest method : use a prebuilt package using arch4edu repository'''</big>
''"Arch4edu is a community repository for Arch Linux and Arch Linux ARM that strives to provide the latest versions of most software used by college students."''

1. Add Arch4edu repository. Follow instructions from official documentation:

https://github.com/arch4edu/arch4edu/wiki/Add-arch4edu-to-your-Archlinux

2. Refresh packages list with

pacman -Syyu

3. Install GRASS package

pacman -S grass

* <big>'''Advanced method : use AUR (Arch User Repository) package'''</big>
Up-to-date links to Archlinux GRASS PKGBUILDs are on Arch User Repository.
PKGBUILD downloads and builds automatically sources from https://grass.osgeo.org/download/software/linux/.

You can use an AUR helper like ''pamac'', ''yay'', among others ... More info through this link https://wiki.archlinux.org/title/AUR_helpers

Exemple with ''yay'':
yay -S grass

* <big>'''Expert method : compile from source code'''</big>
If you want to compile it yourself, you could follow steps below :

''(As an alternative it is recommended to download PKGBUILD from AUR and then customize to your needs)''

Install dependencies :
pacman -S bzip2 cairo fftw fontconfig freetype2 gcc-libs gdal geos glibc glu libpng libtiff libx11 libgl netcdf pdal proj python-gdal python-numpy python-pillow python-wxpython readline zlib zstd

Download and extract sources : https://grass.osgeo.org/download/software/sources/

We can now start building GRASS

export PATH=~/usr/bin:$PATH && \
./configure \
--with-freetype-includes=/usr/include/freetype2 \
--with-wxwidgets \
--with-readline \
--with-pthread \
--with-netcdf \
--with-nls \
--with-geos \
--with-postgres \
--with-pdal=/usr/include/pdal \
--with-bzlib \
--with-zstd

Now let's compile and install it

make
make install

It's done, you can enjoy GRASS in Arch, just type "grass" in the terminal to launch it or look for grass in your menu.

===== Generic procedure for Debian-based distributions (Ubuntu, ...) =====

WORK IN PROGRESS

1. Install official GRASS package

sudo apt install grass grass-dev

2. Enable source code download

# do backup first
sudo cp /etc/apt/sources.list /etc/apt/sources.list.orig
sudo sed -i '/^#\sdeb-src /s/^# *//' /etc/apt/sources.list

3. Install GRASS dependencies

sudo apt build-dep grass

4. Download GRASS source code

git clone https://github.com/osgeo/grass

5. Compile GRASS from source code

cd grass

Configure:

grass --config build | sh

Optionally install missing dependencies (can happen when official GRASS package is not compatible with GRASS main), eg.

sudo apt install libzstd-dev

Compile:

make -j2

6. Run locally or install

./bin.x86_64-pc-linux-gnu/grass --version

or

sudo make install
grass --version

===== Debian =====

* Official [https://wiki.debian.org/DebianGis DebianGIS] packaging control files, available on git server:
https://salsa.debian.org/debian-gis-team/grass

====== GRASS 8 on Debian 11 (bullseye) ======

Install needed packages for GRASS 8.4:
apt-get update && \
apt-get install bison debhelper-compat dh-python doxygen fakeroot flex graphviz \
libblas-dev libbz2-dev libcairo2-dev libfftw3-dev libfreetype6-dev \
libgdal-dev libgeos-dev libgl1-mesa-dev libglu1-mesa-dev libjpeg-dev liblapack-dev libmotif-dev \
default-libmysqlclient-dev libncurses5-dev libnetcdf-dev libpng-dev libpq-dev \
libproj-dev libreadline-dev libsqlite3-dev libtiff-dev libxmu-dev libzstd-dev \
netcdf-bin pkg-config proj-bin python3 python3-dev python3-numpy python3-pil python3-ply \
python3-six python3-wxgtk4.0 wget unixodbc-dev zlib1g-dev

Download and unpack GRASS 8.4 source code (or fetch from GitHub: https://github.com/OSGeo/grass):

wget https://grass.osgeo.org/grass84/source/grass-8.4-latest.tar.gz
tar xvfz grass-8.4-latest.tar.gz
cd grass-8.4.*

Configuration:

CFLAGS="-Wall -Werror-implicit-function-declaration -fno-common -Wextra -Wunused" \
CXXFLAGS="-Wall" \
./configure \
--prefix=/usr/local \
--with-gdal --with-proj --with-proj-share=/usr/share \
--with-glw --with-nls --with-readline \
--with-cxx --enable-largefile \
--with-freetype --with-freetype-includes=/usr/include/freetype2 \
--with-sqlite --with-cairo --with-python=/usr/bin/python-config \
--with-wxwidgets --with-geos \
--with-netcdf=/usr/bin/nc-config --with-odbc=yes \
--with-openmp=yes --with-pthread=no

Compile:

make -j2

Install:

make install

Run:

grass --version

===== Ubuntu =====

There is a dedicated page on how to [[Compile_and_Install_Ubuntu | Compile the GRASS source code & install it in Ubuntu]].

===== Linux Mint =====

The [[Compile_and_Install_Ubuntu | detailed compilation guide for Ubuntu]] may just work. However, here is a short guide for Mint:

<source lang="bash">
# Linux Mint 21+

# be sure to have an updated system
sudo apt-get update && sudo apt-get upgrade -y

# installation of required libraries and compile tools
# recommended to give Python3 precedence over Python2 (which is end-of-life since 2024)
sudo update-alternatives --install /usr/bin/python python /usr/bin/python3 1

# install compiler tools and further dependencies (tested with Linux Mint 21)
# this is a single command, please copy-paste it entirely into the terminal:
sudo apt-get install \
build-essential \
flex make bison gcc libgcc1 g++ cmake ccache \
libproj-dev proj-data proj-bin \
libgeos-dev \
libgdal-dev python3-gdal gdal-bin \
python3 python3-dev \
python3-opengl \
python3-wxgtk4.0 \
python3-dateutil libgsl-dev python3-numpy \
wx3.2-headers libwxgtk3.2-dev libwxbase3.2-1 libfftw3-dev
libncurses5-dev zlib1g-dev gettext \
libbz2-dev libzstd-dev libfreetype6-dev \
libtiff5-dev libpnglite-dev libcairo libcairo-dev \
sqlite3 libsqlite3-dev libpq-dev \
libfftw3-3 libfftw3-dev \
libboost-thread-dev libboost-program-options-dev \
subversion \
checkinstall \
libglu1-mesa-dev libxmu-dev \
ghostscript wget -y
</source>

'''GUI''' - update wxpython:

<source lang="bash">
pip3 install -U -f https://extras.wxpython.org/wxPython4/extras/linux/gtk3/ubuntu-22.04 wxPython
</source>

Next steps:
* create a subdirectory in your HOME tree for storing the GRASS source code (and later compilation)
* get source code, one of the two options:
** a) download [https://grass.osgeo.org/grass84/source/snapshot/ GRASS source code weekly snapshot] (e.g. take the "8.x.git snapshot"), or
*** unpack source code
** b) current source code from GitHub:
*** <code>git clone https://github.com/OSGeo/grass.git</code>
* change into the source code directory

<source lang="bash">
# in the source code directory, "configure" the source code to prepare for compilation:
./configure \
--with-cxx \
--with-proj-share=/usr/share/proj \
--with-gdal=/usr/bin/gdal-config \
--with-geos \
--with-sqlite \
--with-nls \
--with-zstd \
--with-cairo --with-cairo-ldflags=-lfontconfig \
--with-freetype=yes --with-freetype-includes="/usr/include/freetype2/" \
--with-fftw \
--with-opengl-libs=/usr/include/GL \
--without-postgres \
--without-pdal \
--without-netcdf \
--without-mysql \
--without-odbc \
--without-openmp

# compile GRASS
make -j2

# install compiled GRASS on system
sudo make install

# use GRASS! Start on command line
grass
</source>

===== Enterprise Linux =====

Enterprise Linux (EL) and derivatives (that is, Red Hat Enterprise Linux, CentOS and Scientific Linux) is a popular and robust platform for servers and computing-heavy workstations, and is therefore a good fit for GIS specific requirements.

See: https://wiki.osgeo.org/wiki/Enterprise_Linux_GIS

===== Scientific Linux =====

See Centos

===== CentOS =====

You first need to add the EPEL repository for PROJ and GDAL, see [https://fedoraproject.org/wiki/EPEL/FAQ#How_can_I_install_the_packages_from_the_EPEL_software_repository.3F here]

Preparation '''Centos 8''':
dnf install epel-release

dnf install flex bison make zlib-devel gcc-c++ gettext \
fftw-devel libtiff-devel sqlite-devel \
proj proj-devel proj-datumgrid libxml2 \
geos geos-devel git \
netcdf netcdf-devel atlas-devel \
blas-devel lapack-devel libpq-devel \
python3-devel python3-numpy \
python3-dateutil python3-imaging python3-matplotlib \
gdal gdal-libs gdal-python-tools python3-gdal gdal-devel \
wxGTK3-devel mesa-libGL-devel mesa-libGLU-devel \
libXmu-devel libX11-devel

'''GRASS 8 compilation and installation'''

[https://grass.osgeo.org/grass84/source/snapshot/ Download source code] (e.g., --> "Download latest 8.4 code)" and configure GRASS 8 (suggestion: save this as script):

./configure \
--with-cxx \
--with-proj --with-proj-share=/usr/share/proj \
--with-gdal=/usr/bin/gdal-config \
--with-sqlite \
--with-python \
--with-cairo --with-cairo-ldflags=-lfontconfig \
--with-freetype --with-freetype-includes=/usr/include/freetype2 \
--with-wxwidgets=/usr/bin/wx-config \
--with-openmp \
--with-blas --with-blas-includes=/usr/include/atlas-x86_64-base/ \
--with-lapack --with-lapack-includes=/usr/include/atlas-x86_64-base/ \
--with-fftw \
--with-geos \
--with-netcdf \
--without-ffmpeg \
--without-mysql \
--without-postgres \
--without-odbc \
--without-fftw

Compile:
make
or on a multicore system (number depends of available cores):
make -j4

For a system wide installation, run as root user:
make install
OR simply run it directly from the source code directory (substitute ARCH with i686 or x86_64):

bin.$ARCH/grass -gui

In this case, for convenience, add it to the search path:
mkdir $HOME/bin
cd $HOME/bin
# example:
ln -s $HOME/software/grass84_release/bin.x86_64-pc-linux-gnu/grass .

Now use it subsequently with
grass -gui

'''Installation grass on a HPC system with '''Centos 7''' and no root privileges:'''

This assumes that python3, fftw, proj, gdal and geos are available on the HPC system, either as modules or as installed software.

Download and prepare some dependencies (freetypes and zstd)
mkdir -p $HOME/grass/freetypes
cd $HOME/grass/freetypes
wget path/to/freetype-2.9.1.tar.gz
tar -xf freetype-2.9.1.tar.gz

mkdir $HOME/grass/zstd
cd mkdir $HOME/grass/zstd
wget path/to/v1.4.4/zstd-1.4.4.tar.gz
tar -xf zstd-1.4.4.tar.gz
make install PREFIX=./

Add the ZSTD path to your LD_LIBRARY_PATH

tee -a $HOME/.bashrc > /dev/null << EOT
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$HOME/grass/zstd/zstd-1.4.4/lib
EOT

The configure command could look like this
./configure \
-prefix=$HOME/grass \
--enable-64bit --with-fftw-includes=/path/to/fftw/include/ \
--with-fftw-libs=/path/to/fftw/lib/ \
--with-freetype-includes=$HOME/grass/freetypes/freetype-2.9.1/include/ \
--with-netcdf --with-geos --with-blas --with-lapack --with-postgres \
--with-zstd-includes=$HOME/grass/zstd/zstd-1.4.4/lib/ \
--with-zstd-libs=$HOME/grass/zstd/zstd-1.4.4/lib/ \
--with-gdal=/path/to/gdal-config # This could be the path to a gdal version compiled from source

Finally as usual:
make; make install

grass

===== Gentoo =====

./configure \
--with-freetype=yes --with-freetype-includes="/usr/include/freetype2/"

See also https://packages.gentoo.org/package/sci-geosciences/grass

===== Funtoo =====

{{MovedToTrac|FuntooLinux}}

===== Fedora =====

====== GRASS 8 on Fedora ======

'''Preparation''' for the compilation of GRASS 8+ source code (F36+):

dnf install gcc gcc-c++ bison flex ncurses-devel gettext proj-devel \
gdal gdal-devel sqlite-devel xml2 mesa-libGL-devel cairo-devel \
fftw-devel mesa-libGLU-devel libXmu-devel libX11-devel geos geos-devel \
libtiff-devel python3-devel numpy wxGTK-devel gawk git \
python3-dateutil python3-imaging python3-matplotlib-wx doxygen python3-sphinx \
libzstd-devel libzstd python3-six python3-numpy python3-wxpython4 \
proj-data PDAL-devel PDAL-libs

# optionally also: netcdf-devel postgresql-devel
# atlas-devel lapack-devel lapack-devel
# laszip laszip-devel
# proj-data-at proj-data-au proj-data-be ...

''Note 1: the optional ffmpeg-devel comes from the rpmfusion-free repository ([https://rpmfusion.org/Configuration/ configuration]).''

'''Download''' and unpack the source code:
* GRASS 8: [https://grass.osgeo.org/grass84/source/snapshot/ weekly snapshot] - [https://github.com/OSGeo/grass/releases GitHub repository]

'''Configure''': This is an example how to configure the source code on a Fedora system:

./configure \
--with-cxx \
--with-gdal=/usr/bin/gdal-config \
--with-proj --with-proj-share=/usr/share/proj \
--with-geos \
--with-pdal \
--with-sqlite \
--with-nls \
--with-wxwidgets=/usr/bin/wx-config \
--with-fftw \
--with-cairo --with-cairo-ldflags=-lfontconfig \
--with-freetype --with-freetype-includes=/usr/include/freetype2 \
--enable-largefile \
--without-odbc

''Extra 1:'' If you also want '''FFMPEG support''' - it requires 'dnf install fftw-devel' from the rpmfusion-free repository. Then add to the configuration lines above:

--with-ffmpeg --with-ffmpeg-includes="/usr/include/ffmpeg /usr/include/ffmpeg/libav* /usr/include/ffmpeg/libpostproc /usr/include/ffmpeg/libswscale" \

''Extra 2:'' For '''LAPACK/BLAS support''' (addons i.spec.unmix, v.kriging etc), install "dnf install lapack lapack-devel blas blas-devel atlas atlas-devel". Then add to the configuration lines above:
--with-blas --with-blas-includes=/usr/include/atlas-x86_64-base/ \
--with-lapack --with-lapack-includes=/usr/include/atlas-x86_64-base/ \

''Extra 3:'' For '''ZSTD support''' (Zstandard compression algorithm), first install "dnf install libzstd libzstd-devel zstd". After installing the zstd related packages, add to the configuration lines above:
--with-zstd \

Finally '''compile''' the configured source code:
make
or on multicore (number depends of available cores):
make -j4
and
make install # requires root permissions unless you become owner of /usr/local/

Then use GRASS 8 and enjoy!

grass --version

===== openSUSE =====

To build GRASS on openSUSE:

''Application:Geo'' repo to be added (see [https://software.opensuse.org//download.html?project=Application%3AGeo&package=gdal Install package Application:Geo]

<source lang="bash">
# example for Leap 42 version:
sudo zypper addrepo https://download.opensuse.org/repositories/Application:Geo/openSUSE_Leap_42.3/Application:Geo.repo
sudo zypper refresh
</source>

RPM packages to be installed:
<source lang="bash">
sudo zypper install bison flex freetype2-devel fftw3-devel gcc-c++ \
libgdal-devel libgeos-devel libjpeg-devel libpng-devel libtiff-devel \
man proj libproj-devel readline-devel netcdf-devel ncurses-devel \
mysql-devel postgresql-devel sqlite-devel unixODBC-devel \
tcl-devel tk-devel xorg-x11-Mesa-devel libXmu-devel \
python-numpy python-dateutil python-devel python-opengl \
python-wxWidgets python-xml python-dateutil wxWidgets-devel \
zlib-devel doxygen python-sphinx
</source>

Source code configuration:
<source lang="bash">
./configure \
--enable-largefile \
--with-proj-share=/usr/share/proj \
--with-cxx \
--with-lapack=yes \
--with-motif \
--with-gdal=/usr/bin/gdal-config \
--with-postgres --with-postgres-includes=/usr/include/pgsql \
--with-mysql --with-mysql-includes=/usr/include/mysql \
--with-fftw \
--with-readline \
--with-netcdf \
--with-geos \
--with-nls \
--with-sqlite \
--with-freetype \
--with-freetype-includes=/usr/include/freetype2 \
--with-wxwidgets \
--with-odbc \
--with-python
</source>

Then compile with "make [-j2]".

===== RPM SPEC files =====
* [https://build.opensuse.org/package/show?package=grass&project=Application%3AGeo OpenSuSe]
* [https://pkgs.fedoraproject.org/cgit/rpms/grass.git/tree/grass.spec Fedora]
* ...

==== macOS ====

Compiling GRASS for macOS is not fundamentally different from for other *nix systems. It is on the contrary quite similar, but what differ is the lack of a default package management system for software GRASS depends on. This leaves the mac user to either: (1) compile the dependencies one-by-one; (2) compiling with one of the third-party package management systems avaliable; or (4) a combination thereof.

If you are interested in installing a precompiled version, please check out the [https://grass.osgeo.org/download/software/mac-osx/ official download site].

To date, maybe the easiest way to compile for Mac is by using [https://github.com/nilason/grass-conda GRASS app build script] which is based on the instructions below for building using Anaconda. It will install dependencies, package and install an app bundle with just a command in Terminal.

===== Compilation and installation =====

For more up-to-date instructions please read:

* [https://github.com/nilason/grass-conda Compiling on macOS using Conda] (Intel / Apple silicon based machine M1)
* [[Compiling on macOS using Anaconda]]
* [[Compiling on macOS using Homebrew]]
* [[Compiling on macOS using MacPorts]]

===== Legacy instructions =====

The following compilation and installation instructions are rather outdated as a whole. They do, however, contain parts and snippets that still may be very instructive and useful.

* [[Compiling on MacOSX]]
* [[Compiling on MacOSX using Fink]]
* [https://web.archive.org/web/20180718005252/https://www.kyngchaos.com/software/frameworks#build_scripts build scripts for dependencies]

Troubleshooting:
* solving errors at starting GRASS: [[MacOSX GRASS errors]]

==== FreeBSD / NetBSD ====

The recommended compiler tools are GCC, GNU make, GNU coreutils (for install), and flex. All are available through the respective package managing tools (pkg_add for FreeBSD and pkgin install for NetBSD) and for recent *BSD versions most likely installed by default.

GRASS 8 should compile on FreeBSD and NetBSD.

It is highly recommended to install GDAL/OGR and PROJ first. These libraries and tools are available as [https://www.freebsd.org/ports/ ports for FreeBSD] and [https://www.pkgsrc.org/ packages for NetBSD].

Optional functionality is listed with ''./configure --help'', and related libraries and tools might need to be installed first.

You then may need to edit include/Make/Platform.make and set
ICONVLIB = -liconv

==== AIX ====

A recent [ftp://ftp.gnu.org/gnu/make/ GNU make] (>= 3.81) and GNU coreutils are required. These are available with the [https://www-03.ibm.com/systems/power/software/aix/linux/toolbox/download.html IBM AIX toolbox] or through third-party AIX software repositories, e.g. [https://www.bullfreeware.com/ bullfreeware] and [https://www.perzl.org/aix/ perzl.org]. Note that 'make' does not work, only 'gmake' works.

General instructions to compile on AIX are e.g. [https://www.perzl.org/aix/index.php?n=Main.Instructions here]

On AIX, compilation results by default in 32 bit applications and static libraries. The [https://developer.ibm.com/components/aix/ IBM documentation] explains how to build 64 bit applications and shared libraries with GCC.

'''GRASS 8: Using the IBM xlc compiler:'''

Get and install (in this order):
* [ftp://ftp.gnu.org/gnu/tar/ GNU tar]
* [ftp://ftp.gnu.org/gnu/make/ GNU make] (>= 3.81)
* [https://www.sqlite.org SQLite]
* [https://trac.osgeo.org/proj/ PROJ.4] (for ./configure parameters, see [[Talk:Compile and Install|here]])
* [https://www.gdal.org GDAL] (for ./configure parameters, see [[Talk:Compile and Install|here]])
* [https://grass.osgeo.org/grass84/source/snapshot/ GRASS 8]

The environment variables and configure command that worked:
<pre>
## AIX 5.x

export LIBPATH=/opt/freeware/lib64:/opt/freeware/lib
# make 'ar' happy
export OBJECT_MODE=64

PREFIX=$HOME/private/bin
./configure \
--prefix=$PREFIX \
--disable-shared \
--with-cxx \
--with-proj-includes=$PREFIX/include/ \
--with-proj-libs=$PREFIX/lib/ \
--with-proj-share=$PREFIX/share/proj/ \
--with-sqlite \
--with-sqlite-includes=$PREFIX/include/ \
--with-sqlite-libs=$PREFIX/lib/ \
--with-tiff=no \
--with-png=no \
--with-fftw=no \
--with-cairo=no \
--with-freetype=no
</pre>

'''GRASS 8: Using the GNU gcc compiler:'''

Get and install (in this order):
* if needed, [ftp://ftp.gnu.org/gnu/tar/ GNU tar]
* if needed (the name is often 'gmake' and not 'make') [ftp://ftp.gnu.org/gnu/make/ GNU make] (>= 3.81)
* [https://www.sqlite.org SQLite]
* [https://trac.osgeo.org/proj/ PROJ.4] (for ./configure parameters, see [[Talk:Compile and Install|here]])
* [https://www.gdal.org GDAL] (for ./configure parameters, see [[Talk:Compile and Install|here]])
* [https://grass.osgeo.org/grass84/source/snapshot/ GRASS 8]

The environment variables and configure command that worked for AIX 7.x:
<pre>
## AIX 7.x
export CC="gcc"
export CXX="g++"
PREFIX=$HOME/bin

LDFLAGS="-Wl,-bsvr4,-R,/opt/freeware/lib -L/opt/freeware/lib" CPPFLAGS="-I/opt/freeware/include" ./configure \
--prefix=$PREFIX \
--enable-shared \
--with-includes=/opt/freeware/include --with-libs=/opt/freeware/lib \
--with-cxx \
--with-proj-includes=$PREFIX/include/ \
--with-proj-libs=$PREFIX/lib/ \
--with-proj-share=$PREFIX/share/proj/ \
--with-gdal=$PREFIX/bin/gdal-config \
--with-sqlite \
--with-sqlite-libs=$PREFIX/lib --with-sqlite-includes=$PREFIX/include \
--with-png=no \
--with-tiff=no \
--with-fftw=no \
--with-cairo=no \
--with-opengl=no \
--with-freetype=no
</pre>

==== MS-Windows ====

See also [[WinGRASS Current Status]] for latest updates.

===== MS-Windows/native =====

GRASS on Windows using a standalone installer. It is still MinGW based (we are going to move this to CMake in 2024+).

Instructions to compile from source code:
* [https://trac.osgeo.org/grass/wiki/CompileOnWindows GRASS Windows Native Binary Building Guide]

===== MS-Windows/OSGeo4W =====

OSGeo4W is an installer for a broad set of open source geospatial software packages including GRASS as well as many other packages (QGIS, GDAL/OGR, and more).

* See [https://trac.osgeo.org/osgeo4w/ OSGeo4W]

===== MS-Windows/Cygwin =====

* See the [[Cygwin]] wiki pages

=== Common problems and solutions ===

During compilation, error can occur if certain packages are not installed. Here a list of problems with solution:

* error: X11/Xlib.h: No such file or directory
** this suggests that you don't have the X headers installed
** Solution: Install the libx11-dev package

* error: g.list: error while loading shared libraries: libgdal1.6.0.so.1: cannot open shared object file: No such file or directory
** this error appears in the shell right after the user clicks GUI's "Start GRASS" button. The GUI shows an error about geographic extent and gets closed afterwards.
** It happens when you launch bin.i686 executable on 64bit system. Be careful and choose the right architecture.

* error: lib/python/ctypes
** This error appears during the compilation: <code>free(): invalid pointer Aborted (core dumped)</code>
** It happens when you have multiple <code>libproj</code> versions on your system (check it with command <code>ldd PATH_TO_GRASS_INSTALL/lib/libgrass_gproj.so | grep proj</code> - when this is not your problem, you should obtain exactly one result)
** Solution: Try to reinstall <code>libproj-dev</code> and <code>proj-data</code>

=== Static compilation ===

In order to get static rather than dynamically linked binaries, configure like this:

./configure --disable-shared --enable-static

This will however break the wxGUI and GRASS 8 completely because "ctypes" wants to link against shared libs, or there is something in the static libs that "ctypes" does not like.

=== Optimization ===

GCC and other compilers support [https://gcc.gnu.org/onlinedocs/gcc-4.3.3/gcc/Optimize-Options.html#Optimize-Options optimization]

If you would like to set compiler optimisations, for a possibly faster binary, type (don't enter a ";" anywhere):

CFLAGS=-O ./configure
or,
setenv CFLAGS -O
./configure

whichever works on your shell. Use -O2 instead of -O if your compiler supports this (note: O is the letter, not zero). Using the "gcc" compiler, you can also specify processor specific flags (examples, please suggest better settings to us):

CFLAGS="-mcpu=athlon -O2" # AMD Athlon processor with code optimisations
CFLAGS="-march=amdfam10" # AMD Phenom II X4 64bit processor with gcc >=4.3
CFLAGS="-mcpu=pentium" # Intel Pentium processor
CFLAGS="-mcpu=pentium4" # Intel Pentium4 processor
CFLAGS="-O2 -msse -msse2 -mfpmath=sse -minline-all-stringops" # Intel XEON 64bit processor
CFLAGS="-mtune=nocona -m64 -minline-all-stringops" # Intel Pentium 64bit processor

To find out optional CFLAGS for your platform, enter:
gcc -dumpspecs

See also: https://gcc.gnu.org/

A real fast GRASS version (and small binaries) will be created with LDFLAGS set to "stripping" (but this disables debugging):

CFLAGS="-O2 -mcpu=<cpu_see_above> -Wall" LDFLAGS="-s" ./configure

=== Configure options and their meanings ===

For configure there are many options and some GRASS modules are built only if some options are set. Here are listed common configuration options with short explanation.

* --prefix=/path - Sets path where GRASS will be installed. GRASS will reside in /path/grass-version.
* --enable-largefile - Enables large (>2Gb on 32bit systems) support. For current large file support status look at [[Large File Support]] page.
* --with-cxx - Enables compilation of C++ code. Required for r.terraflow module.
* --with-readline - Enables readline support. If readline is enabled, you can use its history/editing facilities when entering r.mapcalc expressions on stdin.
* --with-glw - Enables GLw support. The GLw library provides OpenGL "canvas" widgets for Athena and Motif.

That switch is unnecessary for normal compilation. It's only
required for r3.showdspf, which isn't normally built; if you
want it, you have build it manually
(e.g. "make -C raster3d/r3.showdspf").
As similar functionality is now provided by NVIZ, r3.showdspf
is deprecated.
r3.showdspf uses the Motif widget (so you also need a
Motif library, e.g. Lesstif or OpenMotif).
[https://grass.itc.it/pipermail/grassuser/2006-December/037475.html Glynn Clements at GRASS-user mailing list]

=== Parallelized compilation on multi-core CPUs ===

You can dramatically accelerate the compilation of the GRASS code with the -j flag of "make" if you have a multi-core CPU system. This determines the maximum number of jobs to have running at once, so cores don't have to sit idle waiting for jobs on other cores to complete. A good rule of thumb for this value is <tt>number_of_cores * 1.5</tt>, but note that setting any higher than the actual number of cores will only affect the timing slightly. For example, on a dual-core processor:
make -j 4



== GRASS-GDAL plugin ==

* see [[Compile and install GRASS and QGIS with GDAL/OGR Plugin]]

== Addons ==

Please note that the installation of [https://grass.osgeo.org/grass-stable/manuals/addons/ GRASS addons] can be easily done with the {{cmd|g.extension}} manager. The compile instructions below are aiming at own development.

=== Compiled modules ===

This is the general way which works for C modules as well as scripts (Python or Shell/Bash modules) which has HTML documentation.

'''Requirements:'''

Either:
* a binary GRASS package, or
* source code which has been prepared with:
./configure [opionally flags]
make libs

Each of the [[GRASS_AddOns|addon]] modules should come with a Makefile. To compile it, just run:
make MODULE_TOPDIR=/path/to/grass84/

Note that the <tt>/path/to/grass84</tt> has to be absolute, not relative.

If using Bash it may be useful to set that up as an alias:
alias gmake64='make MODULE_TOPDIR=/path/to/grass84/'

Installation (perhaps requires "sudo"):
make MODULE_TOPDIR=/path/to/grass84/ install

Note: Compiled addons may require a re-compilation if you changed/updated your GRASS standard binaries.

==== If binary comes with a -dev package ====

''(work in progress, this text states how it eventually will be :)''
Nowadays one does not need to the source code, nor compiling GRASS by oneself to be able to add add-ons. On Debian, you can just install the grass-dev package and then run:
make MODULE_TOPDIR=/usr/lib/grass84/ INST_DIR=/usr/lib/grass84/

The grass-dev package essentially provides GRASS's <tt>include</tt> header files and Make configuration files.

=== Scripts ===

If the addon module is a script, it is sufficient to copy it into the (GRASS binaries) path somewhere. Alternatively, install addons into a separate GRASS addons binaries/scripts directory which is easier to maintain. It avoids getting clobbered every time you reinstall GRASS. To use these separately stored scripts, set and export the GRASS_ADDON_PATH environment variable before starting GRASS and it will automatically be added to the module search path (see the {{cmd|variables}} help page). To simplify this, do for example:

# add in $HOME/.bashrc:
GRASS_ADDON_PATH=/usr/local/grass/addons/
export GRASS_ADDON_PATH

Make sure that the script is executable, then just call it in GRASS typing the filename. Python scripts need to be called writing the extension as well, like:

GRASS (nc_spm):~ > v.krige.py

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

Temporal data processing

2025-07-02T08:51:36Z

Neteler: /* References */

== Introduction ==

TGRASS is the temporal enabled GRASS GIS.
TGRASS is completely metadata based, i.e. it does not change any data but simply handles the organization of raster, vector, raster3D maps actually stored in a GRASS GIS mapset by registering in an additional internal database. This is done specifically for managing temporal and spatial extent including temporal topology.

Manual overview: https://grass.osgeo.org/grass-stable/manuals/temporalintro.html

== Terminology Overview ==

* Space time raster datasets ('''strds''') are designed to manage raster map time series. Modules that process strds have the naming prefix ''t.rast''.
* Space time 3D raster datasets ('''str3ds''') are designed to manage 3D raster map time series. Modules that process str3ds have the naming prefix ''t.rast3d''.
* Space time vector datasets ('''stvds''') are designed to manage vector map time series. Modules that process stvds have the naming prefix ''t.vect''.

== Workflow overview ==

# create an empty space time datasets: strds, str3ds, or stvds ({{cmd|t.create}})
# register the GRASS GIS maps ({{cmd|t.register}})
# check the generated space time datasets ({{cmd|t.list}}, {{cmd|t.info}})
# do your analysis: {{cmd|t.rast.aggregate}}, {{cmd|t.info}}, {{cmd|t.rast.univar}}, {{cmd|t.vect.univar}}, ... so many more!

== Example workflow for a Chlorophyll-a MODIS time series ==

The following examples are based on a series of MODIS L3 Chlorophyll-a product that is freely available at the [http://oceancolor.gsfc.nasa.gov/cgi/l3?sen=A&per=MO&prd=CHL_chlor_a ocean color] site. So, say we download the SMI 8-day composite product at 4.6 km resolution for the period 2003-2013. That is a 506 set of images, 46 per year. Data comes as compressed HDF4 files. Chlorophyll products file names look like this:

<code>A20030012003008.L3m_8D_CHL_chlor_a_4km</code>

where,

A: MODIS/Aqua
2003: Year at start
001: Julian day at start
2003: Year at end
008: Julian day at end
L3m: Level 3 data, mapped (Projection: Plate carrée)
8D: 8 day composition
CHL: Chlorophyll a concentration product
chlor_a: algorithm used 10^(a0 + a1*X + a2*X^2 + a3*X^3 + a4*X^4)
4km: 4.6km pixel size (8640x4320 image, 2.5 minute resolution)

We now decompress files and check metadata

<source lang="bash">
# Go to where the data is and decompress
find -iname '*.bz2' -exec bzip2 -d {} \;
# Check file meta-data (GDAL utilities)
gdalinfo A20030012003008.L3m_8D_CHL_chlor_a_4km
</source>

Next step is to import all 506 images into GRASS. You can use {{cmd|r.in.gdal}} or {{cmd|r.external}} for that.
Note that global Cl-a images as downloaded from [http://oceancolor.gsfc.nasa.gov/cgi/l3?sen=A&per=MO&prd=CHL_chlor_a ocean color] site are ~150 mb each (disk space issues!). Here, 3 different options:

* import global images (506 images, 150 Mb each) with r.in.gdal, resize to study area and remove global files
* set projection and extension, and resize to study area with gdal_translate, and import already resized images with r.in.gdal
* import global images (506 images, 150 Mb each) with r.external, resize to study area and remove global files, as showed below:

<source lang="bash">
# define region extension
g.region -p n=-38 s=-55 w=-70 e=-56

suffix=_tmp
for map in *chlor* ; do
r.external input=$map output=${map}${suffix} -o
r.mapcalc expression="$map = ${map}${suffix}"
g.remove type=raster name=${map}${suffix}
done
</source>

Once we have maps inside GRASS GIS database we can start the temporal processing. If this is the first time you'll use temporal modules,
you need to run

<source lang="bash">
t.connect -d
</source>

to set the default temporal GIS database connection for the current mapset. If the connection is not initially set with {{cmd|t.connect}}, any temporal module that you try to run for the first time will first set the connection to the temporal database for you. The default TGIS database of type ''sqlite3'' is located in the PERMANENT mapset directory. Temporal GIS content from all created mapsets will be stored there.

=== Creating a STRDS and registering maps ===

'''Creating a STRDS'''

First step is to '''create a space time dataset''' by means of {{cmd|t.create}}. As an example, let us create a strds for the Chlorophyll-a (Cl-a) time series. We need to define the name and semantic type of the new space time dataset, its title and a description. By default a raster dataset is created with absolute time (Gregorian calendar). We can change that according to our needs with type and temporaltype options.

<source lang="bash">
t.create type=strds temporaltype=absolute output=cla \
title="Chlorophyll-a concentration" \
description="MODIS L3 Chlorophyll-a concentration for Argentinian sea" \
semantictype=mean
</source>

'''Registering maps'''

Then, we '''register the maps''' in the strds using {{cmd|t.register}}. This module assigns timestamps to raster, 3D raster and vector maps and register them in the temporal database and into space time datasets. Existing timestamps can be read and used by t.register. Note that this is a metadata based registration, nothing is imported into GRASS GIS since the maps are already present in the location (hence, no duplication occurs).

This module (and TGRASS in general) supports '''absolute time''' and '''relative time'''. The ''absolute'' temporal type refers to a fixed date or interval in the Gregorian calendar, while the ''relative'' temporal type refers to data without fixed time stamps (e.g., sequential maps used to calculate multi-decadal averages). Refer to the [http://www.geostat-course.org/system/files/Presentation_0.pdf TGRASS overview slides] for background.

Maps can be registered by command line argument (i.e., a list of comma separated map names) or using an input file. The start time, end time and a temporal increment can be provided either by command line or in the input file. End time and increment are mutually exclusive. Maps can be registered in several space time datasets using the same timestamp. For a more detailed explanation and examples on how to register maps in stds, see also [https://grasswiki.osgeo.org/wiki/Temporal_data_processing/maps_registration maps registration] wiki page.

Start time and end time with absolute time must be provided using the format yyyy-mm-dd HH:MM:SS +HHMM. It is also supported to specify the date yyyy-mm-dd only. In case of relative time, the temporal unit (years, months, days, hours, minutes or seconds) must be provided. The relative start time, end time and the increment are integers (see also {{cmd|t.register}}).

<source lang="bash">
# note: with -i we create intervals (start and end time) spanning the given increment, and starting from start.
t.register -i type=raster input=cla \
maps=`g.list raster pattern="*_chlor_*" separator=comma` \
start="2003-01-01" \
increment="8 days"
</source>

'''Dealing with weekly data'''

While the former would have been the simplest solution, our 8-day products have a problem: in this example the last image of each year is not a product of an 8-day composition, but 4 or 5-day. Then, when using the increment parameter, dates (and consequently, intervals) are not set properly.
The solution is to create a list of maps, with their respective start and end date. As the filenames contain information regarding year and DOY (day of year), we can use the following Python script to '''read filenames and transform DOY to calendar dates''' (Thanks Soeren!).

<source lang="python">
# Script to extract the input file for t.register from map names
# run in python
# modify to your needs

from os import walk
f = []
for (dirpath, dirnames, filenames) in walk("/path/to/the/maps"):
f.extend(filenames)
break
# to order the list
f.sort()

input_list=[]

import datetime
for map_name in f:
start_year = int(map_name[1:5])
start_day = int(map_name[5:8])
end_year = int(map_name[8:12])
end_day = int(map_name[12:15])
start = datetime.datetime(start_year, 1, 1) + datetime.timedelta(start_day - 1)
end = datetime.datetime(int(end_year), 1, 1) + datetime.timedelta(end_day)
map_list = map_name + '|' + str(start) + '|' + str(end)
print map_list
input_list.append(map_list)

print input_list

txt = '\n' .join(input_list)
f = open("input_list_cla.txt","w")
f.write(txt)
f.close()
</source>

Using the number of characters in the filenames and the datetime library in Python, you can convert DOY in the filenames into start_time and end_time as in the file you need to pass to {{cmd|t.register}}:

A20030012003008.L3m_8D_CHL_chlor_a_4km_arg|2003-01-01 00:00:00|2003-01-09 00:00:00
A20030092003016.L3m_8D_CHL_chlor_a_4km_arg|2003-01-09 00:00:00|2003-01-17 00:00:00
A20030172003024.L3m_8D_CHL_chlor_a_4km_arg|2003-01-17 00:00:00|2003-01-25 00:00:00
...
A20133452013352.L3m_8D_CHL_chlor_a_4km_arg|2013-12-11 00:00:00|2013-12-19 00:00:00
A20133532013360.L3m_8D_CHL_chlor_a_4km_arg|2013-12-19 00:00:00|2013-12-27 00:00:00
A20133612013365.L3m_8D_CHL_chlor_a_4km_arg|2013-12-27 00:00:00|2014-01-01 00:00:00

and then, the command would be:

<source lang="bash">
t.register --o type=raster input=cla file=input_list_cla.txt
</source>

As we are providing start and end time along with map names, we don't need to use the -i flag, neither set start nor increment options because that information is already contained in the file.

'''Assign a color table'''

We can also set a color table for all maps in the strds with {{cmd|t.rast.colors}}:

<source lang="bash">
# using a predetermined color table
t.rast.colors input=cla color=bcyr
#using your dedicated color table
t.rast.colors input=cla rules=path/to/your/color_table
</source>

Further examples of '''extracting timestamps from map names''' can be found here: [https://grasswiki.osgeo.org/wiki/Temporal_data_processing/maps_registration maps registration] wiki page.

=== Getting some basic info and statistics ===

We now check the space time data sets we have in our mapset with {{cmd|t.list}}:

<source lang="bash">
t.list type=strds
</source>

and get information about our recently created strds. See {{cmd|t.info}} for additional uses.

<source lang="bash">
t.info type=strds input=cla
</source>

+-------------------- Space Time Raster Dataset -----------------------------+
| |
+-------------------- Basic information -------------------------------------+
| Id: ........................ cla@clorofila
| Name: ...................... cla
| Mapset: .................... clorofila
| Creator: ................... veroandreo
| Temporal type: ............. absolute
| Creation time: ............. 2014-04-29 14:23:00.579342
| Modification time:.......... 2014-05-12 09:15:08.917309
| Semantic type:.............. mean
+-------------------- Absolute time -----------------------------------------+
| Start time:................. 2003-01-01 00:00:00
| End time:................... 2014-01-01 00:00:00
| Granularity:................ 1 day
| Temporal type of maps:...... interval
+-------------------- Spatial extent ----------------------------------------+
| North:...................... -38.0
| South:...................... -55.0
| East:.. .................... -55.0
| West:....................... -70.0
| Top:........................ 0.0
| Bottom:..................... 0.0
+-------------------- Metadata information ----------------------------------+
| Raster register table:...... raster_map_register_91ba57d5f0924f4fa0bd7176a1b39b2f
| North-South resolution min:. 0.041667
| North-South resolution max:. 0.041667
| East-west resolution min:... 0.041667
| East-west resolution max:... 0.041667
| Minimum value min:.......... 0.02925
| Minimum value max:.......... 0.26472
| Maximum value min:.......... 5.2104
| Maximum value max:.......... 99.953934
| Aggregation type:........... None
| Number of registered maps:.. 506
|
| Title:
| Chlorophyll-a
| Description:
| Concentracion de Clorofila a
| Command history:
| # 2014-04-29 14:23:00
| t.create type="strds" temporaltype="absolute"
| output="cla" title="Chlorophyll-a"
| description="Concentracion de Clorofila a" --o
| # 2014-04-29 14:23:23
| t.register --o type="rast" input="cla"
| file="input_list_cla.txt"
|
+----------------------------------------------------------------------------+

Now, we get univariate statistics from the non-null cells for each registered raster map of the strds. For that matter we use {{cmd|t.rast.univar}} which, by default, returns the name of the map, the start and end date of dataset and the following values: ''mean, minimum and maximum vale, mean_of_abs, standard deviation, variance, coeff_var, number of null cells, total number of cell''.

<source lang="bash">
t.rast.univar input=cla
</source>

Or, you can send the output to a text file using

<source lang="bash">
t.rast.univar input=cla separator=comma output=stats_cla.csv
</source>

This file "stats_cla.csv" you can now open in a spreadsheet or statistical software for inspection and plotting.

=== Listing maps and selections ===

The module {{cmd|t.rast.list}} allows you to list all the maps registered in a strds or a selection of them and, provides options for different listing methods, sorting of the list, information to print and so on. The ''where'' option in t.rast.list allows to perform different selections of maps to list. The ''columns'' that can be used to perform these selections are: ''id, name, creator, mapset, temporal_type, creation_time, start_time, end_time, north, south, west, east, nsres, ewres, cols, rows, number_of_cells, min and max''. (Note that for vector time series, i.e. stvds, the columns in {{cmd|t.vect.list}} differ from those for strds. You can check that with <code>t.vect.list --help</code>).

<source lang="bash">
t.rast.list input=cla method=gran granule="1 month"
# this will give one image every one month, 3 months, 1 year, or the granule you choose

t.rast.list input=cla order=min columns=id,name,start_time,min where="min <= '0.05'"
# this will order by minimum value all the maps in the strds that have a minimum value lower than or equal to 0.05

t.rast.list input=cla order=max columns=name,start_time,max where="max > '10.0'"
# maps ordered by maximum value in which maximum value is higher than 10.

t.rast.list input=cla where="start_time >= '2003-01' and start_time <= '2003-06'"
# all the maps in the first 6 month of the time series

t.rast.list input=cla where="strftime('%m', start_time)='01'"
# all the maps from January

t.rast.list input=cla where="strftime('%m-%d', start_time)='01-01'"
# all the maps from January, 1st

t.rast.list input=cla where="strftime('%w', start_time)='1'"
# all Mondays in the time series (Sunday is 0)
</source>

If you have monthly (instead of 8-day products) data and you want to list all January maps, then you can do:

<source lang="bash">
t.rast.list input=cla where="start_time=datetime(start_time, 'start of year', ' 0 month')"
</source>

Note: '''Do not forget to use single quotes around date''', neither in {{cmd|t.rast.list}} nor in any other of the t.* modules offering the ''where'' option, because the clause will be ignored (i.e.: no selection performed) and no warning nor error will be printed.

=== Visualization ===

There are different visualization options for strds.

* {{cmd|g.gui.timeline}} allows to compare temporal datasets by displaying their temporal extents in a plot.

<source lang="bash">
# only temporal extent
g.gui.timeline inputs=cla
# temporal and spatio-temporal extent
g.gui.timeline -3 inputs=cla
</source>

[[Image:Cla strds.png|center|thumb|560px|Temporal and spatio-temporal extent of cla strds.]]

* {{cmd|g.gui.tplot}} allows to see the values of one or more temporal datasets for a queried point defined by a coordinate pair.

Steps to use this module are:

# Select strds
# Select pair of coordinates (east,north) or mark a point in the map
# Hit Draw
# Customize plot as desired
# Save

[[Image:Output gguitplot.png|center|thumb|800px|Time series plot (Chlorophyll vs Time) for a certain coordinate pair in the study area]]

* {{cmd|g.gui.animation}} is the tool for animating a series of raster and vector maps or a space time raster or vector dataset.

<source lang="bash">
g.gui.animation strds=cla_monthly_average
</source>

[[Image:Grass70 temporal chlorophyll anim small.gif|framed|center|Monthly mean chlorophyll-a concentration]]

=== Aggregation ===

For aggregations of data with different methods and different granularities, there are two very useful commands:

* {{cmd|t.rast.series}} that applies different aggregation methods from {{cmd|r.series}} on all or a subset of raster maps in a strds, and

* {{cmd|t.rast.aggregate}} that temporally aggregates the maps in a strds by a user defined granularity.

With these modules it is very simple to get maps of basic statistical parameters for different temporal granules, and this permits the analysis of the spatio-temporal variability of the variable of interest.

Some examples:

<source lang="bash">
# yearly aggregation
t.rast.aggregate input=cla output=cla_yearly_average basename=cla_yearly_average \
granularity="1 years" method=average sampling=starts suffix=gran

# yearly aggregation with corresponding methods (output: 7 strds with 11 maps each)
for method in average median mode minimum maximum stddev range ; do
t.rast.aggregate input=cla output=cla_yearly_${method} \
basename=cla_yearly_${method} granularity="1 years" \
method=${method} sampling=starts suffix=gran
done
</source>

With the where parameter, as exemplified before, we can select for example all 8-day products which start_time is 01 (January) over the years. Like this we can get the so-known '''climatologies'''.

<source lang="bash">
t.rast.series input=cla method=average where="strftime('%m', start_time)='01'" output=january_average
</source>

We could also get long term averages for specific periods in a time series, e.g. January 5-year mean:

<source lang="bash">
t.rast.series input=cla \
where="start_time >= '2005-01-01' AND start_time <= '2009-12-01' AND strftime('%m', start_time)='01'" \
method=average output=jan_cla_mean_2000_2004

# say we take a 15 years period (2000-2014) of monthly data and we want monthly 5-year averages
YEAR_START=(2000 2005 2010)
YEAR_END=(2004 2009 2014)
count=${#YEAR_START[@]}

for i in `seq 1 $count` ; do
echo ${YEAR_START[$i-1]} ${YEAR_END[$i-1]}
for MONTH in `seq -w 1 12` ; do
t.rast.series input=cla \
where="start_time >= '"${YEAR_START[$i-1]}"-01-01' AND start_time <= '"${YEAR_END[$i-1]}"-12-01' AND strftime('%m', start_time)='"${MONTH}"'" \
method=average output=cla_${YEAR_START[$i-1]}_${YEAR_END[$i-1]}_month_${MONTH} --o
done
done
</source>

Generalizing a bit, to obtain monthly climatologies from a time series, we can:

<source lang="bash">
# monthly climatologies
for MONTH in `seq -w 1 12` ; do
for METHOD in average median stddev minimum maximum ; do
t.rast.series input=cla method=${METHOD} where="strftime('%m', start_time)='${MONTH}'" output=${METHOD}_${MONTH}
done
done

# seasonal climatologies
for i in "01 02 03" "04 05 06" "07 08 09" "10 11 12" ; do
set -- $i ; echo $1 $2 $3
for m in average median stddev minimum maximum ; do
t.rast.series input=cla method=${m} output=${m}_${1} \
where="strftime('%m',start_time)='"${1}"' or strftime('%m',start_time)='"${2}"' or strftime('%m', start_time)='"${3}"'"
done
done
</source>

Using the climatologies previously obtained, we'll now estimate monthly anomalies in the mean, max and min Cl-a concentration. First, we need to monthly aggregate data, and then do the difference between the monthly climatology and each respective monthly aggregate. We'll do the aggregation for the average, minimum and maximum of Cl-a concentration (from 506 input maps in cla strds, we'll get 132 maps in each monthly aggregated new strds).

<source lang="bash">
# monthly aggregates (132 maps)
for method in average minimum maximum ; do
t.rast.aggregate input=cla output=cla_monthly_${method} \
basename=cla_monthly_${method} \
granularity="1 months" method=${method} \
sampling=contains suffix=gran
done

# January anomalies in mean, min and max Cl-a
t.rast.list -u input=cla_monthly_average where="start_time=datetime(start_time, 'start of year', '0 month')" columns=name

for m in average minimum maximum ; do
for i in 1 13 25 37 49 61 73 85 97 109 121 ; do # these numbers correspond to all January monthly aggregates
r.mapcalc expression="Jan_${m}_anomaly_${i}=cla_monthly_${m}_${i}-01_${m}"
done
done
</source>

You can also use {{cmd|t.rast.list}} for looping, the same way you use {{cmd|g.list}}:

<source lang="bash">
for map in `t.rast.list -u input=cla_monthly_average where="strftime('%m', start_time)='01'" columns=name` ; do
r.mapcalc expression="anomaly_${map}=${map}-01_average"
done
</source>

Generalizing, we can estimate all monthly anomalies from mean like:

<source lang="bash">
for i in `seq -w 1 12` ; do
for map in `t.rast.list -u input=cla_monthly_average columns=name where="strftime('%m', start_time)='"${i}"'"` ; do
r.mapcalc expression="anomaly_${map}=${map}-average_${i}"
done
done
</source>

Say we now need to know the date of the maximum value of Cl-a concentration over all the study period and/or on a yearly basis:

<source lang="bash">
# map index for the overall maximum Cl-a value
t.rast.series input=cla method=max_raster output=cla_max_index

# map index for the yearly maximum Cl-a value
t.rast.aggregate input=cla granularity="1 year" method=max_raster output=yearly_max_index basename=yearly_max_index suffix=gran
</source>

The outputs show (pixelwise) the map index in which the maximum value of Cl-a occurs (from 1 to 506 and from 1 to 46, for the whole time series and on a yearly basis, respectively). For relative time this is maybe enough, but you may then want to reclassify data to get DOY, for example. In that case, you may use {{cmd|r.reclass}}.

If you already have monthly data, you can get climatologies quite simply as follows:

<source lang="bash">
# January averages
t.rast.series input=cla_monthly method=average where="start_time=datetime(start_time, 'start of year', '0 month')" output=jan_average
</source>

=== Spatio-temporal algebra with STRDS ===

The module {{cmd|t.rast.mapcalc}} allows us to perform spatio-temporal mapcalc expressions on temporally sampled maps of strds. There are spatial and temporal operators available for the "expression" string. Spatial operators, functions and internal variables are those used in {{cmd|r.mapcalc}}. Temporal internal variables supported for both relative and absolute time include: td(), start_time() and end_time(). There are also several very useful internal variables supported especially for absolute time of the current sample interval or instance, e.g.: start_doy(), start_year(), start_month() and so on (see {{cmd|t.rast.mapcalc}} manual for further details and examples).

Some examples now. Say we did some analysis and decided that we will only consider values higher than 0.05. Then, we need to set all values below that threshold to null.

<source lang="bash">
t.rast.mapcalc input=cla expression="if(cla < 0.05, null(), cla)" output=cla_corrected basename=cla_corrected
</source>

or we may also want to take negative erroneous values to the knowm minimum of the strds, so:

<source lang="bash">
t.rast.series input=cla method=minimum output=min_cla
t.rast.mapcalc input=cla expression="if(cla < 0.0, min_cla, cla)" output=cla_corrected basename=cla_corrected
</source>

We may also need to reclassify all maps in the strds according to a certain threshold, e.g.: a certain level of Cl-a that indicates bloom conditions, in order to get bloom frequency afterwards:

<source lang="bash">
# reclassify
t.rast.mapcalc -n input=cla output=cla_bloom basename=cla_bloom expression="if(cla > 0.75, 1, null())"
# bloom frequency
t.rast.series input=cla_bloom output=bloom_freq method=count
</source>

Do you remember we wanted to get the DOY of maximum Cl-a value before? Well, here's another way of doing it...

<source lang="bash">
# overall maximum value
t.rast.series input=cla method=maximum output=max_cla
# new strds with DOY of overall maximum
t.rast.mapcalc -n inputs=cla output=date_max_cla expression="if(cla == max_cla,start_doy(),null())" basename=date_max_cla
# map with DOY of overall maximum
t.rast.series input=date_max_cla method=maximum output=max_cla_date
# remove date_max_cla strds (we were only interested in the resulting aggregated map)
t.remove -rf inputs=date_max_cla
</source>

There's also a {{cmd|t.rast.algebra}} module that allows for temporal and spatial operations on strds by means of temporal raster algebra. The module expects an expression in the following form: "result = expression".

The statement structure is similar to r.mapcalc, the result is the name of a new strds that will contain the result of the calculation given as expression. Expressions can be any valid or nested combination of temporal operations and spatial overlay or buffer functions that are provided by the temporal algebra. See the manual for further details and explanations.

We'll use this module to estimate the rate of change (slope) between every pair of maps in the "cla" strds. The result will be a new strds consisting of maps with the slope value between every consecutive pair of maps in the original strds:

<source lang="bash">
# we set 8 as fixed denominator, because products are 8-day compositions
t.rast.algebra expression="slope_cla = (cla[1]-cla[0])/8.0" basename=slope_cla
</source>

We can then use any of the aggregation modules that we saw before to get the maximum or minimumm rate of change for different granularities.

===== Some known issues with t.rast.mapcalc =====

It has been observed that if the names of inputs and output space time datasets (partially) match each other, t.rast.mapcalc may not work properly (especially when several input strds are used). This is because the module uses a simple search and replace approach to substitute the input strds with the corresponding map names. Eventualy, choosing a specific order for the input strds in the input parameter may reduce the risk of wrong substitution. Therefore, especially in operations involving several strds (with partially matching names) as inputs, '''it is recommended to use {{cmd|t.rast.algebra}} that correctly recognizes spatio-temporal datasets''' rather than t.rast.mapcalc.

=== Subseting and something else ===

{{cmd|t.rast.extract}} is another really useful module within temporal GRASS. It allows to extract a subset of a strds and store it in a different strds. The "where" condition is used to do the subset, but you can also specify a r.mapcalc sub-expression that performs operations on all maps of the selected subset. If no r.mapcalc expression is defined, the selected maps are simply registered in the new output strds.

Say we need to know in how many maps of the strds minimum values are below a certain threshold, and not only that, but we also want to know how many pixels per map meet that condition. Then, we can do

<source lang="bash">
t.rast.extract input=cla where="min <= '0.05'" output=cla_less_05 basename=cla_less_05 expression="if(cla < 0.05, 1, null())"
</source>

to extract those maps with a minimum value lower than 0.05, and in the same step put 1 in every cell meeting the criterium and null everywhere else. To get a count of maps and pixels meeting the condition we may use:

<source lang="bash">
# univariate stistics to get the count per map
t.rast.univar input=cla_less_05
# count map of cells with min value < 0.05
t.rast.series input=cla_less_05 output=count_cla_less_05 method=count
</source>

=== Importing / Exporting STRDS ===

Say we now need to do some processing in R (e.g.: run [http://menugget.blogspot.com.ar/2012/10/dineof-data-interpolating-empirical.html DINEOF] to fill gaps in data), so we need to export our strds, hence we use {{cmd|t.rast.export}}.

<source lang="bash">
t.rast.export input=cla output=cla4R compression=gzip
</source>

After we have done our analysis we can import the whole strds back to GRASS again, exporting it from R with read/write.tgrass from [http://cran.r-project.org/web/packages/spacetime/index.html spacetime] R package and using {{cmd|t.rast.import}} in GRASS.

<source lang="bash">
t.rast.import input=cla_from_R.tar.gz output=cla_from_R basename=new_map directory=/tmp
</source>

For a full example of how to handle raster time series between GRASS and R, please visit the [https://grasswiki.osgeo.org/wiki/Temporal_data_processing/raster_time_series_grass_R_statistics time series GRASS-R Statistics] wiki. The example is based on North Carolina climate location [http://courses.ncsu.edu/mea592/common/media/02/nc_climate_spm_2000_2012.zip] and includes the following steps:

# Exporting the strds out of GRASS
# Importing into R
# Re-formating the data
# Running [http://modb.oce.ulg.ac.be/mediawiki/index.php/DINEOF DINEOF]
# Re-constructing the raster time series
# Exporting out of R, and
# Importing the gap-filled new strds into GRASS.

=== Neighborhood analysis ===

{{cmd|t.rast.neighbors}} performs a neighborhood analysis for each map in a space time raster dataset. This module supports a subset of the options already available in r.neighbors. Both, size of the neighborhood and aggregation method can be chosen. As an example, we'll estimate mean Cl-a concentration in a 3x3 neighborhood for every map in the strds.

<source lang="bash">
t.rast.neighbors input=cla output=cla_smoth base=cla_smooth method=average size=3
</source>

=== Filling and reconstructing time series data with gaps ===

==== Harmonic ANalysis of Time Series - HANTS ====

{{AddonCmd|r.hants}} is an add-on not strictly within the temporal modules, but really useful when working with time series data, particularly with gappy data. Here's a simple example for generating a list of temporally ordered maps to use as input in '''r.hants''', running HANTS and getting a map of dominant frequencies, afterwards. See the manual for further information on parameter setting and explanations.

<source lang="bash">
# use t.rast.list to create a list of temporally ordered maps
t.rast.list input=cla order=start_time columns=name -u > map_list.csv

# a HANTS run using the list of maps
r.hants -l file=map_list.csv nf=5 fet=0.1 dod=11 base_period=46 suffix=_hants amplitude=amp_hants phase=pha_hants

# dominant frequency map (0 means the dominant freq is 1, 1 that dominant freq is 2, and so on...)
r.series input=`g.list type=raster pattern="amp_hants*" separator=comma` output=dominant_freq_hants method=max_raster
</source>

==== Local Weighted Regression - LWR ====

Another very useful add-on for the reconstruction of gappy time series, such as those from remote sensing imagery, is {{AddonCmd|r.series.lwr}}. This module performs a local weighted regression (LWR) of the input maps in order to estimate missing values and identify (and remove) outliers. See the manual for further information and explanations.

<source lang="bash">
# use same list as before
t.rast.list input=cla order=start_time columns=name -u > map_list.csv

# run r.series.lwr
r.series.lwr file=map_list.csv suffix=_lwr order=2 weight=tricube range=0.0,65.0 dod=16 fet=0.1 -l
</source>

==== Estimate Mean Absolute Error (MAE) ====

One of the measures used to assess how close forecasts or predictions might be to the observed values is the
[https://en.wikipedia.org/wiki/Mean_absolute_error mean absolute error]. We will use it to evaluate the performance of HANTS and LWR.

First, we will rebuild our time series with the corresponding output maps of r.hants and r.series.lwr. Here, only showed for LWR.

<source lang="bash">
# re-build time series
t.create type=strds temporaltype=absolute output=cla_lwr \
title="LWR output for Chl-a" \
description="MODIS Aqua L3 Chl-a 8-day 4km 2010-2013. Reconstruction with r.series.lwr"

# create list with filenames to parse
g.list type=raster pattern="*lwr" output=names_list

# parse filenames, convert YYYY-DOY to YYYY-MM-DD and write file to use in t.register
for mapname in `cat names_list` ; do
year_start=`echo ${mapname:1:4}`
doy_start=`echo ${mapname:5:3}`
year_end=`echo ${mapname:8:4}`
doy_end=`echo ${mapname:12:3}`
# convert YYYY-DOY to YYYY-MM-DD
#BEWARE: leading zeros make bash assume the number is in base 8 system, not base 10!
doy_start=`echo "$doy_start" | sed 's/^0*//'`
doy_end=`echo "$doy_end" | sed 's/^0*//'`
START_DATE=`date -d "${year_start}-01-01 +$(( ${doy_start} - 1 ))days" +%Y-%m-%d`
END_DATE=`date -d "${year_end}-01-01 +$(( ${doy_end} ))days" +%Y-%m-%d`
# print mapname, start and end date
echo "$mapname|$START_DATE|$END_DATE" >> map_list_start_and_end_time.txt
done

# register maps in strds
t.register input=cla_lwr type=raster file=map_list_start_and_end_time.txt
</source>

Now, we will estimate the MAE and use it to compare both methods. Again, only the example for LWR is showed.

<source lang="bash">
# obtain a strds of the absolute differences between predicted and observed Chl-a values
t.rast.algebra -n \
basename=lwr_minus_orig suffix=gran \
expression="abs_lwr_minus_orig = abs(cla_lwr - cla)"

# sum of the absolute differences (numerator) and count of non-null maps per pixel (denominator)
t.rast.series input=abs_lwr_minus_orig output=sum_abs_lwr_minus_orig method=sum
t.rast.series input=abs_lwr_minus_orig output=count_abs_lwr_minus_orig method=count

# MAE for LWR
r.mapcalc expression="mae_lwr = sum_abs_lwr_minus_orig / count_abs_lwr_minus_orig"

# remove intermediate strds and maps
t.remove -rf abs_lwr_minus_orig
g.remove -f type=raster name=sum_abs_lwr_minus_orig,count_abs_lwr_minus_orig
</source>

Let's now compare the predictions generated by both methods, HANTS and LWR, and the corresponding mean absolute error maps.

{|
|-
| [[Image:cla_vs_cla_hants.png|center|thumb|560px|Original Chl-a time series vs HANTS output.]] || [[Image:cla_vs_cla_lwr.png|center|thumb|560px|Original Chl-a time series vs LWR output.)]]
|-
| [[Image:mae_hants_map.png|center|thumb|560px|MAE of HANTS predictions.]] || [[Image:mae_lwr_map.png|center|thumb|560px|MAE of LWR predictions.]]
|}

=== Extract strds values for points in a vector ===

Let's say we need to extract values of the strds to check the behaviour of HANTS at given locations and compare it with the original values. We can graphically do that with {{cmd|g.gui.tplot}}, but if you need to take data outside GRASS, say, read it into R and do some other analysis (See [http://grasswiki.osgeo.org/wiki/R_statistics/rgrass7#Reading_in_data R_Statistics wiki page]) you may use {{cmd|v.what.strds}}. This module retrieves raster values from a given strds to the attribute table of a point vector map.

<source lang="bash">
# original data
v.what.strds input=points_cla strds=cla output=points_cla_out
v.db.select map=points_cla_out file=ts_points_cla.csv

# HANTS' reconstructed data (several runs)
for i in `seq 1 13` ; do
v.what.strds --overwrite input=points_cla strds=cla_hants_${i} output=points_hants_${i}_out
v.db.select map=points_cla file=ts_points_hants_${i}.csv
done
</source>

Another option would be to use {{cmd|t.rast.what}} that samples a space time raster dataset at specific vector point coordinates and writes the output to stdout or text file using different layouts. This module doesn't write the vector's attribute table.

<source lang="bash">
t.rast.what points=points strds=cla output=cla_points.csv null_value=NA separator=comma
</source>

=== Some other modules and addons useful in the time series context ===

* {{cmd|t.rast.accumulate}} and {{cmd|t.rast.accdetect}} to compute and detect cyclic accumulations in raster time series.
* {{AddonCmd|t.rast.what.aggr}} to sample a strds with a vector point map and get aggregated values of desired granularity either in stdout or in the vector's attribute table.
* {{AddonCmd|t.rast.out.xyz}} to export a strds to a CSV file.
* {{AddonCmd|t.rast.null}} to manage NULL-values of a strds.
* {{AddonCmd|v.strds.stats}} to calculate univariate statistics from a strds based on a vector map.
* {{AddonCmd|r.seasons}} to extract seasons from a time series.
* {{AddonCmd|r.bioclim}} to calculate bio-climatic indices.
* {{AddonCmd|r.change.info}} for landscape change assessment.
* {{AddonCmd|r.quantile.ref}} to determine the corresponding quantile for an input value from a reference raster time series.
* {{AddonCmd|r.regression.series}} and {{AddonCmd|r.mregression.series}} to perform univariate and multivariate linear regression among raster time series, respectively.
* {{AddonCmd|r.series.diversity}} to estimate diversity indices in raster time series.
* {{AddonCmd|r.series.decompose}} to decompose raster time series.
* {{AddonCmd|r.series.filter}} to apply Savitzky-Golay or median filters to raster time series.

== FAQ ==

=== Best practice data organization ===

When it comes to time series, thousands of maps are often involved. In order to keep control, here some suggestions:

* separate original data from derived aggregates: store them in separate mapsets
* for specific projects, maintain them in individual mapsets. You can access the STDS stored in other mapsets (same location) through
t.some.module input=my_strds@the_other_mapset output=result ...
as long as mapsets are indeed accessible, i.e.: in the mapset's search path (See {{cmd|g.mapsets}}).

=== Best practice multi user management ===

GRASS GIS supports multi-user data management and allows several users to work in the same location within their own mapsets. Data can be read from other mapsets but not edited there. The same principle applies to space time datasets (STDS), i.e. in case of having a collection of maps corresponding to a time series in a dedicated mapset, you need to also create the STDS therein (See {{cmd|t.create}} and {{cmd|t.register}}), so it is visible to other users in other mapsets when they use {{cmd|t.list}}, for example.

=== Use of ''where'' parameter (ticket [https://trac.osgeo.org/grass/ticket/2270 #2270]) ===

Pay attention when using the "where" option in t.* modules. In some occasions it may not yield the expected results. Given the backend database chosen for TGRASS implementation, you may not be selecting all maps you think if you forget to set time along with date in the where clause. For example, let's say we need to select maps from 2005-03-01 until 2005-05-31 included. You would think the following command would do the job:

<source lang="bash">
t.rast.list daily_temp where="start_time > '2005-03-01' and start_time <= '2005-05-31'"
</source>

but, no... The last map in the list is:

temp_0516|pruebas|2005-05-30 00:00:00|2005-05-31 00:00:00

which would be equivalent to:

<source lang="bash">
t.rast.list daily_temp where="start_time > '2005-03-01' and start_time < '2005-05-31'"
</source>

This is a product of sqlite. Therefore, if you need the last date included in your selection (map from 2005-05-31 in our example), you need to set time too.

<source lang="bash">
t.rast.list daily_temp where="start_time > '2005-03-01' and start_time <= '2005-05-31 00:00:00'" | tail -n1
temp_0517|pruebas|2005-05-31 00:00:00|2005-06-01 00:00:00
</source>

=== Aggregation with defined granularity ===

''Q: I need to aggregate a strds with a granularity of 1 year, but shifting the start day one month in each run, i.e.: changing the start_time to 2003-02-01, 2003-03-01, 2003-04-01 and so on... My question is: if i recursively change start_time with the 'where' parameter, will the module t.rast.aggregate "aggregate" to the next february, march, april (what i'd wish) or just till the end of 2003?''

A: If you specify a granularity of a year, then the start time to perform the aggregation will always be shifted to the 1st January of the current year and the end time the 1st January of the next year (eg. 2002-01-01 - 2003-01-01). If you wish to aggregate a full year but shifting one month forward then simply use a granularity of 12 months.

=== Listing maps with specific start month ===

''Q: I have a strds with 506 maps that correspond to 8-day composite products. I need to sequentially list all maps which "start_month" is January, February and so on... to use them as input in {{cmd|r.series}} (or {{cmd|t.rast.series}}). How can I achieve that?''

A: You can use the [https://www.sqlite.org/lang_datefunc.html datetime functionality of SQLite] to perform this task, this should work for January:

<source lang="bash">
t.rast.list input=cla_null_mayor65 \
where='start_time >= datetime(start_time, "start of year") and start_time <= datetime(start_time, "start of year", "1 month")'
</source>

=== Aggregation of seasonal data ===

''Q: How can I calculate average seasonal temperature starting from a daily temperatures temporal dataset?''

A: Use {{cmd|t.rast.aggregate.ds}}, the input is the daily strds, the sampling stds should have seasonal intervals. Then use average as method. The output will have seasonal aggregated temperatures. For a detailed workflow see: [https://grasswiki.osgeo.org/wiki/Temporal_data_processing/seasonal_aggregation seasonal aggregation example].

=== Aggregation of seasonal data using time ranges ===

A way to aggregate seasons from daily data without granularity but by using time ranges is shown here. The issue is to include for the season calculation also a month from the previous year. This can be addressed with some datetime calculations in SQLite:

<source lang="bash">
# We assume to have daily temperature data in DB "temp_daily_average"

# loop over seasons, generate aggregates:
### 'start_time' and 'end_time' are columns in TGRASS

for year in `seq 2004 2014` ; do

# we consider also a month of the previous year
for month in "12 01 02" "03 04 05" "06 07 08" "09 10 11" ; do
set -- $month ; echo $1 $2 $3

prevyear=$year
if [ $1 -eq 12 ] ; then
prevyear=`expr $year - 1`
fi

# prepare query strings in SQLite
MYSTART=`echo "SELECT strftime(datetime('${prevyear}-${1}-01'));" | sqlite3`
MYEND=`echo "SELECT strftime(datetime('${prevyear}-${1}-01','+3 month'));" | sqlite3`

# Debugging only, to see what it does:
echo "---- Querying ${prevyear}-${1}-01 ... ${year}-${3}-end:"
# we use start_time and end_time to get the proper time range
t.rast.list input=temp_daily_average@modis_lst_reconstructed_europe_daily \
where="start_time >= '$MYSTART' AND end_time <= '$MYEND'" > list_${prevyear}_${1}_${3}.csv

head -n 3 list_${prevyear}_${1}_${3}.csv
echo "..."
tail -n 3 list_${prevyear}_${1}_${3}.csv
echo "======="
rm -f list_${prevyear}_${1}_${3}.csv

# calculate aggregates:
method="average" # median mode minimum maximum stddev

t.rast.series input=temp_daily_average@modis_lst_reconstructed_europe_daily \
where="start_time >= '$MYSTART' AND end_time <= '$MYEND'" \
output=temp_${method}_${prevyear}_${1}
done
done
</source>

Much simpler '''alternative''' (which runs in parallel on multi-cores):
<source lang="bash">
t.rast.aggregate input=A output=B basename=b where="start_time >= '2004-03-01 00:00:00'" granularity="3 months"
</source>

=== How to count consecutive days that meet a certain condition? ===

This example was kindly contributed by Thomas Leppelt and shows how to obtain the number of consecutive days with temperature below 0 per week.

<source lang="bash">
# Set the computational region and resolution
g.region -p n=-30 s=-50 e=-50 w=-70 res=1

# We create maps for 100 days
for map in `seq 1 100` ; do
# generate synthetic maps as a seeding random values for temperatures
r.mapcalc -s expression="daily_temp_${map} = rand(-20,20)" --o
echo daily_temp_${map} >> map_list.txt
done

t.create type=strds temporaltype=absolute \
output=temperature_daily \
title="Daily Temperature" \
description="Test dataset with daily temperature"

t.register -i type=raster input=temperature_daily \
file=map_list.txt start="2014-03-07" increment="1 days" --o

# check general information of the daily strds
t.info type=strds input=temperature_daily

# Create weekly mask to which we will add 1 or 0 according to temperature in the days within it (each map in this week mask will have a value of 7)
t.rast.aggregate input=temperature_daily output=weekly_mask basename=mask_week granularity="1 weeks" method=count

# Calculate consecutive days with negative temperatures
t.rast.algebra base=neg_temp_days expression="consecutive_days = weekly_mask {+,contains,l} if(temperature_daily < 0 && temperature_daily[-1] < 0 || temperature_daily[1] < 0 && temperature_daily < 0, 1, 0)"
</source>

== Online tutorials and courses ==

* [https://web.archive.org/web/20160119125858/www.geostat-course.org/topic_gebbert/ The temporal GRASS GIS framework: Introduction and application] by Sören Gebbert (2012)
* CZ: [https://web.archive.org/web/20180316200749/https://training.gismentors.eu/grass-gis-pokrocily/tgrass/index.html Úvod do časoprostorových analýz] (Introduction to space-time analysis) by Martin Landa (2015)
* [https://gismentors.github.io/grass-gis-workshop-jena/units/21.html Sentinel spatio-temporal processing] by Martin Landa (2020)
* [https://github.com/veroandreo/tgrass_workshop_foss4g_eu TGRASS: temporal data processing with GRASS GIS] FOSS4G-EU workshop by Veronica Andreo, Luca Delucchi and Markus Neteler (2017)

== References ==
* Gebbert, S., Pebesma, E. 2014. ''TGRASS: A temporal GIS for field based environmental modeling''. Environmental Modelling & Software 53, 1-12 ([https://doi.org/10.1016/j.envsoft.2013.11.001 DOI]) - [https://ifgi.uni-muenster.de/~epebe_01/tgrass.pdf preprint PDF]
* Gebbert, S., Pebesma, E. 2017. ''The GRASS GIS temporal framework''. International Journal of Geographical Information Science 31, 1273-1292 ([https://doi.org/10.1080/13658816.2017.1306862 DOI]) - [https://figshare.com/articles/journal_contribution/The_GRASS_GIS_temporal_framework/4834013/1/files/8024429.pdf PDF]
* Gebbert, S., Leppelt, T., Pebesma, E., 2019. ''A topology based spatio-temporal map algebra for big data analysis''. Data 4, 86. ([https://doi.org/10.3390/data4020086 DOI]) - [https://www.mdpi.com/2306-5729/4/2/86/pdf?version=1560849201 PDF]. Content:
** Object oriented code design
** Code examples
*** Registration of existing raster layers
*** Temporal aggregation of a raster time series
*** Sampling a raster time series at vector points
*** Spatio-temporal intersection of trajectories
*** Benchmark Python code

== See also ==
* Introduction: [http://www.slideshare.net/Luis_de_Sousa/presentation-soeren GRASS as a Temporal GIS] by Sören Gebbert (slides)
* [https://archive.org/details/TheTemporalGrassGisFrameworkIntroductionAndApplication# The temporal GRASS GIS framework: Introduction and application] Video of Sören Gebbert's presentation in [http://www.geostat-course.org/Muenster_2012 GEOSTAT course] 2012
* [https://grass.osgeo.org/grass-stable/manuals/temporalintro.html Introduction to temporal modules] (GRASS GIS manual)
* [https://grass.osgeo.org/grass-stable/manuals/temporal.html Available temporal modules] (GRASS GIS manual)
* [https://trac.osgeo.org/grass/wiki/Grass7/TemporalExtension Temporal Extension] (background info in trac)
* [[GRASS GSoC 2013 Temporal GIS Algebra for raster and vector data in GRASS]]

[[Category: Documentation]]
[[Category: Tutorial]]
[[Category: Temporal]]

Temporal data processing

2025-07-02T08:49:47Z

Neteler: /* References */

== Introduction ==

TGRASS is the temporal enabled GRASS GIS.
TGRASS is completely metadata based, i.e. it does not change any data but simply handles the organization of raster, vector, raster3D maps actually stored in a GRASS GIS mapset by registering in an additional internal database. This is done specifically for managing temporal and spatial extent including temporal topology.

Manual overview: https://grass.osgeo.org/grass-stable/manuals/temporalintro.html

== Terminology Overview ==

* Space time raster datasets ('''strds''') are designed to manage raster map time series. Modules that process strds have the naming prefix ''t.rast''.
* Space time 3D raster datasets ('''str3ds''') are designed to manage 3D raster map time series. Modules that process str3ds have the naming prefix ''t.rast3d''.
* Space time vector datasets ('''stvds''') are designed to manage vector map time series. Modules that process stvds have the naming prefix ''t.vect''.

== Workflow overview ==

# create an empty space time datasets: strds, str3ds, or stvds ({{cmd|t.create}})
# register the GRASS GIS maps ({{cmd|t.register}})
# check the generated space time datasets ({{cmd|t.list}}, {{cmd|t.info}})
# do your analysis: {{cmd|t.rast.aggregate}}, {{cmd|t.info}}, {{cmd|t.rast.univar}}, {{cmd|t.vect.univar}}, ... so many more!

== Example workflow for a Chlorophyll-a MODIS time series ==

The following examples are based on a series of MODIS L3 Chlorophyll-a product that is freely available at the [http://oceancolor.gsfc.nasa.gov/cgi/l3?sen=A&per=MO&prd=CHL_chlor_a ocean color] site. So, say we download the SMI 8-day composite product at 4.6 km resolution for the period 2003-2013. That is a 506 set of images, 46 per year. Data comes as compressed HDF4 files. Chlorophyll products file names look like this:

<code>A20030012003008.L3m_8D_CHL_chlor_a_4km</code>

where,

A: MODIS/Aqua
2003: Year at start
001: Julian day at start
2003: Year at end
008: Julian day at end
L3m: Level 3 data, mapped (Projection: Plate carrée)
8D: 8 day composition
CHL: Chlorophyll a concentration product
chlor_a: algorithm used 10^(a0 + a1*X + a2*X^2 + a3*X^3 + a4*X^4)
4km: 4.6km pixel size (8640x4320 image, 2.5 minute resolution)

We now decompress files and check metadata

<source lang="bash">
# Go to where the data is and decompress
find -iname '*.bz2' -exec bzip2 -d {} \;
# Check file meta-data (GDAL utilities)
gdalinfo A20030012003008.L3m_8D_CHL_chlor_a_4km
</source>

Next step is to import all 506 images into GRASS. You can use {{cmd|r.in.gdal}} or {{cmd|r.external}} for that.
Note that global Cl-a images as downloaded from [http://oceancolor.gsfc.nasa.gov/cgi/l3?sen=A&per=MO&prd=CHL_chlor_a ocean color] site are ~150 mb each (disk space issues!). Here, 3 different options:

* import global images (506 images, 150 Mb each) with r.in.gdal, resize to study area and remove global files
* set projection and extension, and resize to study area with gdal_translate, and import already resized images with r.in.gdal
* import global images (506 images, 150 Mb each) with r.external, resize to study area and remove global files, as showed below:

<source lang="bash">
# define region extension
g.region -p n=-38 s=-55 w=-70 e=-56

suffix=_tmp
for map in *chlor* ; do
r.external input=$map output=${map}${suffix} -o
r.mapcalc expression="$map = ${map}${suffix}"
g.remove type=raster name=${map}${suffix}
done
</source>

Once we have maps inside GRASS GIS database we can start the temporal processing. If this is the first time you'll use temporal modules,
you need to run

<source lang="bash">
t.connect -d
</source>

to set the default temporal GIS database connection for the current mapset. If the connection is not initially set with {{cmd|t.connect}}, any temporal module that you try to run for the first time will first set the connection to the temporal database for you. The default TGIS database of type ''sqlite3'' is located in the PERMANENT mapset directory. Temporal GIS content from all created mapsets will be stored there.

=== Creating a STRDS and registering maps ===

'''Creating a STRDS'''

First step is to '''create a space time dataset''' by means of {{cmd|t.create}}. As an example, let us create a strds for the Chlorophyll-a (Cl-a) time series. We need to define the name and semantic type of the new space time dataset, its title and a description. By default a raster dataset is created with absolute time (Gregorian calendar). We can change that according to our needs with type and temporaltype options.

<source lang="bash">
t.create type=strds temporaltype=absolute output=cla \
title="Chlorophyll-a concentration" \
description="MODIS L3 Chlorophyll-a concentration for Argentinian sea" \
semantictype=mean
</source>

'''Registering maps'''

Then, we '''register the maps''' in the strds using {{cmd|t.register}}. This module assigns timestamps to raster, 3D raster and vector maps and register them in the temporal database and into space time datasets. Existing timestamps can be read and used by t.register. Note that this is a metadata based registration, nothing is imported into GRASS GIS since the maps are already present in the location (hence, no duplication occurs).

This module (and TGRASS in general) supports '''absolute time''' and '''relative time'''. The ''absolute'' temporal type refers to a fixed date or interval in the Gregorian calendar, while the ''relative'' temporal type refers to data without fixed time stamps (e.g., sequential maps used to calculate multi-decadal averages). Refer to the [http://www.geostat-course.org/system/files/Presentation_0.pdf TGRASS overview slides] for background.

Maps can be registered by command line argument (i.e., a list of comma separated map names) or using an input file. The start time, end time and a temporal increment can be provided either by command line or in the input file. End time and increment are mutually exclusive. Maps can be registered in several space time datasets using the same timestamp. For a more detailed explanation and examples on how to register maps in stds, see also [https://grasswiki.osgeo.org/wiki/Temporal_data_processing/maps_registration maps registration] wiki page.

Start time and end time with absolute time must be provided using the format yyyy-mm-dd HH:MM:SS +HHMM. It is also supported to specify the date yyyy-mm-dd only. In case of relative time, the temporal unit (years, months, days, hours, minutes or seconds) must be provided. The relative start time, end time and the increment are integers (see also {{cmd|t.register}}).

<source lang="bash">
# note: with -i we create intervals (start and end time) spanning the given increment, and starting from start.
t.register -i type=raster input=cla \
maps=`g.list raster pattern="*_chlor_*" separator=comma` \
start="2003-01-01" \
increment="8 days"
</source>

'''Dealing with weekly data'''

While the former would have been the simplest solution, our 8-day products have a problem: in this example the last image of each year is not a product of an 8-day composition, but 4 or 5-day. Then, when using the increment parameter, dates (and consequently, intervals) are not set properly.
The solution is to create a list of maps, with their respective start and end date. As the filenames contain information regarding year and DOY (day of year), we can use the following Python script to '''read filenames and transform DOY to calendar dates''' (Thanks Soeren!).

<source lang="python">
# Script to extract the input file for t.register from map names
# run in python
# modify to your needs

from os import walk
f = []
for (dirpath, dirnames, filenames) in walk("/path/to/the/maps"):
f.extend(filenames)
break
# to order the list
f.sort()

input_list=[]

import datetime
for map_name in f:
start_year = int(map_name[1:5])
start_day = int(map_name[5:8])
end_year = int(map_name[8:12])
end_day = int(map_name[12:15])
start = datetime.datetime(start_year, 1, 1) + datetime.timedelta(start_day - 1)
end = datetime.datetime(int(end_year), 1, 1) + datetime.timedelta(end_day)
map_list = map_name + '|' + str(start) + '|' + str(end)
print map_list
input_list.append(map_list)

print input_list

txt = '\n' .join(input_list)
f = open("input_list_cla.txt","w")
f.write(txt)
f.close()
</source>

Using the number of characters in the filenames and the datetime library in Python, you can convert DOY in the filenames into start_time and end_time as in the file you need to pass to {{cmd|t.register}}:

A20030012003008.L3m_8D_CHL_chlor_a_4km_arg|2003-01-01 00:00:00|2003-01-09 00:00:00
A20030092003016.L3m_8D_CHL_chlor_a_4km_arg|2003-01-09 00:00:00|2003-01-17 00:00:00
A20030172003024.L3m_8D_CHL_chlor_a_4km_arg|2003-01-17 00:00:00|2003-01-25 00:00:00
...
A20133452013352.L3m_8D_CHL_chlor_a_4km_arg|2013-12-11 00:00:00|2013-12-19 00:00:00
A20133532013360.L3m_8D_CHL_chlor_a_4km_arg|2013-12-19 00:00:00|2013-12-27 00:00:00
A20133612013365.L3m_8D_CHL_chlor_a_4km_arg|2013-12-27 00:00:00|2014-01-01 00:00:00

and then, the command would be:

<source lang="bash">
t.register --o type=raster input=cla file=input_list_cla.txt
</source>

As we are providing start and end time along with map names, we don't need to use the -i flag, neither set start nor increment options because that information is already contained in the file.

'''Assign a color table'''

We can also set a color table for all maps in the strds with {{cmd|t.rast.colors}}:

<source lang="bash">
# using a predetermined color table
t.rast.colors input=cla color=bcyr
#using your dedicated color table
t.rast.colors input=cla rules=path/to/your/color_table
</source>

Further examples of '''extracting timestamps from map names''' can be found here: [https://grasswiki.osgeo.org/wiki/Temporal_data_processing/maps_registration maps registration] wiki page.

=== Getting some basic info and statistics ===

We now check the space time data sets we have in our mapset with {{cmd|t.list}}:

<source lang="bash">
t.list type=strds
</source>

and get information about our recently created strds. See {{cmd|t.info}} for additional uses.

<source lang="bash">
t.info type=strds input=cla
</source>

+-------------------- Space Time Raster Dataset -----------------------------+
| |
+-------------------- Basic information -------------------------------------+
| Id: ........................ cla@clorofila
| Name: ...................... cla
| Mapset: .................... clorofila
| Creator: ................... veroandreo
| Temporal type: ............. absolute
| Creation time: ............. 2014-04-29 14:23:00.579342
| Modification time:.......... 2014-05-12 09:15:08.917309
| Semantic type:.............. mean
+-------------------- Absolute time -----------------------------------------+
| Start time:................. 2003-01-01 00:00:00
| End time:................... 2014-01-01 00:00:00
| Granularity:................ 1 day
| Temporal type of maps:...... interval
+-------------------- Spatial extent ----------------------------------------+
| North:...................... -38.0
| South:...................... -55.0
| East:.. .................... -55.0
| West:....................... -70.0
| Top:........................ 0.0
| Bottom:..................... 0.0
+-------------------- Metadata information ----------------------------------+
| Raster register table:...... raster_map_register_91ba57d5f0924f4fa0bd7176a1b39b2f
| North-South resolution min:. 0.041667
| North-South resolution max:. 0.041667
| East-west resolution min:... 0.041667
| East-west resolution max:... 0.041667
| Minimum value min:.......... 0.02925
| Minimum value max:.......... 0.26472
| Maximum value min:.......... 5.2104
| Maximum value max:.......... 99.953934
| Aggregation type:........... None
| Number of registered maps:.. 506
|
| Title:
| Chlorophyll-a
| Description:
| Concentracion de Clorofila a
| Command history:
| # 2014-04-29 14:23:00
| t.create type="strds" temporaltype="absolute"
| output="cla" title="Chlorophyll-a"
| description="Concentracion de Clorofila a" --o
| # 2014-04-29 14:23:23
| t.register --o type="rast" input="cla"
| file="input_list_cla.txt"
|
+----------------------------------------------------------------------------+

Now, we get univariate statistics from the non-null cells for each registered raster map of the strds. For that matter we use {{cmd|t.rast.univar}} which, by default, returns the name of the map, the start and end date of dataset and the following values: ''mean, minimum and maximum vale, mean_of_abs, standard deviation, variance, coeff_var, number of null cells, total number of cell''.

<source lang="bash">
t.rast.univar input=cla
</source>

Or, you can send the output to a text file using

<source lang="bash">
t.rast.univar input=cla separator=comma output=stats_cla.csv
</source>

This file "stats_cla.csv" you can now open in a spreadsheet or statistical software for inspection and plotting.

=== Listing maps and selections ===

The module {{cmd|t.rast.list}} allows you to list all the maps registered in a strds or a selection of them and, provides options for different listing methods, sorting of the list, information to print and so on. The ''where'' option in t.rast.list allows to perform different selections of maps to list. The ''columns'' that can be used to perform these selections are: ''id, name, creator, mapset, temporal_type, creation_time, start_time, end_time, north, south, west, east, nsres, ewres, cols, rows, number_of_cells, min and max''. (Note that for vector time series, i.e. stvds, the columns in {{cmd|t.vect.list}} differ from those for strds. You can check that with <code>t.vect.list --help</code>).

<source lang="bash">
t.rast.list input=cla method=gran granule="1 month"
# this will give one image every one month, 3 months, 1 year, or the granule you choose

t.rast.list input=cla order=min columns=id,name,start_time,min where="min <= '0.05'"
# this will order by minimum value all the maps in the strds that have a minimum value lower than or equal to 0.05

t.rast.list input=cla order=max columns=name,start_time,max where="max > '10.0'"
# maps ordered by maximum value in which maximum value is higher than 10.

t.rast.list input=cla where="start_time >= '2003-01' and start_time <= '2003-06'"
# all the maps in the first 6 month of the time series

t.rast.list input=cla where="strftime('%m', start_time)='01'"
# all the maps from January

t.rast.list input=cla where="strftime('%m-%d', start_time)='01-01'"
# all the maps from January, 1st

t.rast.list input=cla where="strftime('%w', start_time)='1'"
# all Mondays in the time series (Sunday is 0)
</source>

If you have monthly (instead of 8-day products) data and you want to list all January maps, then you can do:

<source lang="bash">
t.rast.list input=cla where="start_time=datetime(start_time, 'start of year', ' 0 month')"
</source>

Note: '''Do not forget to use single quotes around date''', neither in {{cmd|t.rast.list}} nor in any other of the t.* modules offering the ''where'' option, because the clause will be ignored (i.e.: no selection performed) and no warning nor error will be printed.

=== Visualization ===

There are different visualization options for strds.

* {{cmd|g.gui.timeline}} allows to compare temporal datasets by displaying their temporal extents in a plot.

<source lang="bash">
# only temporal extent
g.gui.timeline inputs=cla
# temporal and spatio-temporal extent
g.gui.timeline -3 inputs=cla
</source>

[[Image:Cla strds.png|center|thumb|560px|Temporal and spatio-temporal extent of cla strds.]]

* {{cmd|g.gui.tplot}} allows to see the values of one or more temporal datasets for a queried point defined by a coordinate pair.

Steps to use this module are:

# Select strds
# Select pair of coordinates (east,north) or mark a point in the map
# Hit Draw
# Customize plot as desired
# Save

[[Image:Output gguitplot.png|center|thumb|800px|Time series plot (Chlorophyll vs Time) for a certain coordinate pair in the study area]]

* {{cmd|g.gui.animation}} is the tool for animating a series of raster and vector maps or a space time raster or vector dataset.

<source lang="bash">
g.gui.animation strds=cla_monthly_average
</source>

[[Image:Grass70 temporal chlorophyll anim small.gif|framed|center|Monthly mean chlorophyll-a concentration]]

=== Aggregation ===

For aggregations of data with different methods and different granularities, there are two very useful commands:

* {{cmd|t.rast.series}} that applies different aggregation methods from {{cmd|r.series}} on all or a subset of raster maps in a strds, and

* {{cmd|t.rast.aggregate}} that temporally aggregates the maps in a strds by a user defined granularity.

With these modules it is very simple to get maps of basic statistical parameters for different temporal granules, and this permits the analysis of the spatio-temporal variability of the variable of interest.

Some examples:

<source lang="bash">
# yearly aggregation
t.rast.aggregate input=cla output=cla_yearly_average basename=cla_yearly_average \
granularity="1 years" method=average sampling=starts suffix=gran

# yearly aggregation with corresponding methods (output: 7 strds with 11 maps each)
for method in average median mode minimum maximum stddev range ; do
t.rast.aggregate input=cla output=cla_yearly_${method} \
basename=cla_yearly_${method} granularity="1 years" \
method=${method} sampling=starts suffix=gran
done
</source>

With the where parameter, as exemplified before, we can select for example all 8-day products which start_time is 01 (January) over the years. Like this we can get the so-known '''climatologies'''.

<source lang="bash">
t.rast.series input=cla method=average where="strftime('%m', start_time)='01'" output=january_average
</source>

We could also get long term averages for specific periods in a time series, e.g. January 5-year mean:

<source lang="bash">
t.rast.series input=cla \
where="start_time >= '2005-01-01' AND start_time <= '2009-12-01' AND strftime('%m', start_time)='01'" \
method=average output=jan_cla_mean_2000_2004

# say we take a 15 years period (2000-2014) of monthly data and we want monthly 5-year averages
YEAR_START=(2000 2005 2010)
YEAR_END=(2004 2009 2014)
count=${#YEAR_START[@]}

for i in `seq 1 $count` ; do
echo ${YEAR_START[$i-1]} ${YEAR_END[$i-1]}
for MONTH in `seq -w 1 12` ; do
t.rast.series input=cla \
where="start_time >= '"${YEAR_START[$i-1]}"-01-01' AND start_time <= '"${YEAR_END[$i-1]}"-12-01' AND strftime('%m', start_time)='"${MONTH}"'" \
method=average output=cla_${YEAR_START[$i-1]}_${YEAR_END[$i-1]}_month_${MONTH} --o
done
done
</source>

Generalizing a bit, to obtain monthly climatologies from a time series, we can:

<source lang="bash">
# monthly climatologies
for MONTH in `seq -w 1 12` ; do
for METHOD in average median stddev minimum maximum ; do
t.rast.series input=cla method=${METHOD} where="strftime('%m', start_time)='${MONTH}'" output=${METHOD}_${MONTH}
done
done

# seasonal climatologies
for i in "01 02 03" "04 05 06" "07 08 09" "10 11 12" ; do
set -- $i ; echo $1 $2 $3
for m in average median stddev minimum maximum ; do
t.rast.series input=cla method=${m} output=${m}_${1} \
where="strftime('%m',start_time)='"${1}"' or strftime('%m',start_time)='"${2}"' or strftime('%m', start_time)='"${3}"'"
done
done
</source>

Using the climatologies previously obtained, we'll now estimate monthly anomalies in the mean, max and min Cl-a concentration. First, we need to monthly aggregate data, and then do the difference between the monthly climatology and each respective monthly aggregate. We'll do the aggregation for the average, minimum and maximum of Cl-a concentration (from 506 input maps in cla strds, we'll get 132 maps in each monthly aggregated new strds).

<source lang="bash">
# monthly aggregates (132 maps)
for method in average minimum maximum ; do
t.rast.aggregate input=cla output=cla_monthly_${method} \
basename=cla_monthly_${method} \
granularity="1 months" method=${method} \
sampling=contains suffix=gran
done

# January anomalies in mean, min and max Cl-a
t.rast.list -u input=cla_monthly_average where="start_time=datetime(start_time, 'start of year', '0 month')" columns=name

for m in average minimum maximum ; do
for i in 1 13 25 37 49 61 73 85 97 109 121 ; do # these numbers correspond to all January monthly aggregates
r.mapcalc expression="Jan_${m}_anomaly_${i}=cla_monthly_${m}_${i}-01_${m}"
done
done
</source>

You can also use {{cmd|t.rast.list}} for looping, the same way you use {{cmd|g.list}}:

<source lang="bash">
for map in `t.rast.list -u input=cla_monthly_average where="strftime('%m', start_time)='01'" columns=name` ; do
r.mapcalc expression="anomaly_${map}=${map}-01_average"
done
</source>

Generalizing, we can estimate all monthly anomalies from mean like:

<source lang="bash">
for i in `seq -w 1 12` ; do
for map in `t.rast.list -u input=cla_monthly_average columns=name where="strftime('%m', start_time)='"${i}"'"` ; do
r.mapcalc expression="anomaly_${map}=${map}-average_${i}"
done
done
</source>

Say we now need to know the date of the maximum value of Cl-a concentration over all the study period and/or on a yearly basis:

<source lang="bash">
# map index for the overall maximum Cl-a value
t.rast.series input=cla method=max_raster output=cla_max_index

# map index for the yearly maximum Cl-a value
t.rast.aggregate input=cla granularity="1 year" method=max_raster output=yearly_max_index basename=yearly_max_index suffix=gran
</source>

The outputs show (pixelwise) the map index in which the maximum value of Cl-a occurs (from 1 to 506 and from 1 to 46, for the whole time series and on a yearly basis, respectively). For relative time this is maybe enough, but you may then want to reclassify data to get DOY, for example. In that case, you may use {{cmd|r.reclass}}.

If you already have monthly data, you can get climatologies quite simply as follows:

<source lang="bash">
# January averages
t.rast.series input=cla_monthly method=average where="start_time=datetime(start_time, 'start of year', '0 month')" output=jan_average
</source>

=== Spatio-temporal algebra with STRDS ===

The module {{cmd|t.rast.mapcalc}} allows us to perform spatio-temporal mapcalc expressions on temporally sampled maps of strds. There are spatial and temporal operators available for the "expression" string. Spatial operators, functions and internal variables are those used in {{cmd|r.mapcalc}}. Temporal internal variables supported for both relative and absolute time include: td(), start_time() and end_time(). There are also several very useful internal variables supported especially for absolute time of the current sample interval or instance, e.g.: start_doy(), start_year(), start_month() and so on (see {{cmd|t.rast.mapcalc}} manual for further details and examples).

Some examples now. Say we did some analysis and decided that we will only consider values higher than 0.05. Then, we need to set all values below that threshold to null.

<source lang="bash">
t.rast.mapcalc input=cla expression="if(cla < 0.05, null(), cla)" output=cla_corrected basename=cla_corrected
</source>

or we may also want to take negative erroneous values to the knowm minimum of the strds, so:

<source lang="bash">
t.rast.series input=cla method=minimum output=min_cla
t.rast.mapcalc input=cla expression="if(cla < 0.0, min_cla, cla)" output=cla_corrected basename=cla_corrected
</source>

We may also need to reclassify all maps in the strds according to a certain threshold, e.g.: a certain level of Cl-a that indicates bloom conditions, in order to get bloom frequency afterwards:

<source lang="bash">
# reclassify
t.rast.mapcalc -n input=cla output=cla_bloom basename=cla_bloom expression="if(cla > 0.75, 1, null())"
# bloom frequency
t.rast.series input=cla_bloom output=bloom_freq method=count
</source>

Do you remember we wanted to get the DOY of maximum Cl-a value before? Well, here's another way of doing it...

<source lang="bash">
# overall maximum value
t.rast.series input=cla method=maximum output=max_cla
# new strds with DOY of overall maximum
t.rast.mapcalc -n inputs=cla output=date_max_cla expression="if(cla == max_cla,start_doy(),null())" basename=date_max_cla
# map with DOY of overall maximum
t.rast.series input=date_max_cla method=maximum output=max_cla_date
# remove date_max_cla strds (we were only interested in the resulting aggregated map)
t.remove -rf inputs=date_max_cla
</source>

There's also a {{cmd|t.rast.algebra}} module that allows for temporal and spatial operations on strds by means of temporal raster algebra. The module expects an expression in the following form: "result = expression".

The statement structure is similar to r.mapcalc, the result is the name of a new strds that will contain the result of the calculation given as expression. Expressions can be any valid or nested combination of temporal operations and spatial overlay or buffer functions that are provided by the temporal algebra. See the manual for further details and explanations.

We'll use this module to estimate the rate of change (slope) between every pair of maps in the "cla" strds. The result will be a new strds consisting of maps with the slope value between every consecutive pair of maps in the original strds:

<source lang="bash">
# we set 8 as fixed denominator, because products are 8-day compositions
t.rast.algebra expression="slope_cla = (cla[1]-cla[0])/8.0" basename=slope_cla
</source>

We can then use any of the aggregation modules that we saw before to get the maximum or minimumm rate of change for different granularities.

===== Some known issues with t.rast.mapcalc =====

It has been observed that if the names of inputs and output space time datasets (partially) match each other, t.rast.mapcalc may not work properly (especially when several input strds are used). This is because the module uses a simple search and replace approach to substitute the input strds with the corresponding map names. Eventualy, choosing a specific order for the input strds in the input parameter may reduce the risk of wrong substitution. Therefore, especially in operations involving several strds (with partially matching names) as inputs, '''it is recommended to use {{cmd|t.rast.algebra}} that correctly recognizes spatio-temporal datasets''' rather than t.rast.mapcalc.

=== Subseting and something else ===

{{cmd|t.rast.extract}} is another really useful module within temporal GRASS. It allows to extract a subset of a strds and store it in a different strds. The "where" condition is used to do the subset, but you can also specify a r.mapcalc sub-expression that performs operations on all maps of the selected subset. If no r.mapcalc expression is defined, the selected maps are simply registered in the new output strds.

Say we need to know in how many maps of the strds minimum values are below a certain threshold, and not only that, but we also want to know how many pixels per map meet that condition. Then, we can do

<source lang="bash">
t.rast.extract input=cla where="min <= '0.05'" output=cla_less_05 basename=cla_less_05 expression="if(cla < 0.05, 1, null())"
</source>

to extract those maps with a minimum value lower than 0.05, and in the same step put 1 in every cell meeting the criterium and null everywhere else. To get a count of maps and pixels meeting the condition we may use:

<source lang="bash">
# univariate stistics to get the count per map
t.rast.univar input=cla_less_05
# count map of cells with min value < 0.05
t.rast.series input=cla_less_05 output=count_cla_less_05 method=count
</source>

=== Importing / Exporting STRDS ===

Say we now need to do some processing in R (e.g.: run [http://menugget.blogspot.com.ar/2012/10/dineof-data-interpolating-empirical.html DINEOF] to fill gaps in data), so we need to export our strds, hence we use {{cmd|t.rast.export}}.

<source lang="bash">
t.rast.export input=cla output=cla4R compression=gzip
</source>

After we have done our analysis we can import the whole strds back to GRASS again, exporting it from R with read/write.tgrass from [http://cran.r-project.org/web/packages/spacetime/index.html spacetime] R package and using {{cmd|t.rast.import}} in GRASS.

<source lang="bash">
t.rast.import input=cla_from_R.tar.gz output=cla_from_R basename=new_map directory=/tmp
</source>

For a full example of how to handle raster time series between GRASS and R, please visit the [https://grasswiki.osgeo.org/wiki/Temporal_data_processing/raster_time_series_grass_R_statistics time series GRASS-R Statistics] wiki. The example is based on North Carolina climate location [http://courses.ncsu.edu/mea592/common/media/02/nc_climate_spm_2000_2012.zip] and includes the following steps:

# Exporting the strds out of GRASS
# Importing into R
# Re-formating the data
# Running [http://modb.oce.ulg.ac.be/mediawiki/index.php/DINEOF DINEOF]
# Re-constructing the raster time series
# Exporting out of R, and
# Importing the gap-filled new strds into GRASS.

=== Neighborhood analysis ===

{{cmd|t.rast.neighbors}} performs a neighborhood analysis for each map in a space time raster dataset. This module supports a subset of the options already available in r.neighbors. Both, size of the neighborhood and aggregation method can be chosen. As an example, we'll estimate mean Cl-a concentration in a 3x3 neighborhood for every map in the strds.

<source lang="bash">
t.rast.neighbors input=cla output=cla_smoth base=cla_smooth method=average size=3
</source>

=== Filling and reconstructing time series data with gaps ===

==== Harmonic ANalysis of Time Series - HANTS ====

{{AddonCmd|r.hants}} is an add-on not strictly within the temporal modules, but really useful when working with time series data, particularly with gappy data. Here's a simple example for generating a list of temporally ordered maps to use as input in '''r.hants''', running HANTS and getting a map of dominant frequencies, afterwards. See the manual for further information on parameter setting and explanations.

<source lang="bash">
# use t.rast.list to create a list of temporally ordered maps
t.rast.list input=cla order=start_time columns=name -u > map_list.csv

# a HANTS run using the list of maps
r.hants -l file=map_list.csv nf=5 fet=0.1 dod=11 base_period=46 suffix=_hants amplitude=amp_hants phase=pha_hants

# dominant frequency map (0 means the dominant freq is 1, 1 that dominant freq is 2, and so on...)
r.series input=`g.list type=raster pattern="amp_hants*" separator=comma` output=dominant_freq_hants method=max_raster
</source>

==== Local Weighted Regression - LWR ====

Another very useful add-on for the reconstruction of gappy time series, such as those from remote sensing imagery, is {{AddonCmd|r.series.lwr}}. This module performs a local weighted regression (LWR) of the input maps in order to estimate missing values and identify (and remove) outliers. See the manual for further information and explanations.

<source lang="bash">
# use same list as before
t.rast.list input=cla order=start_time columns=name -u > map_list.csv

# run r.series.lwr
r.series.lwr file=map_list.csv suffix=_lwr order=2 weight=tricube range=0.0,65.0 dod=16 fet=0.1 -l
</source>

==== Estimate Mean Absolute Error (MAE) ====

One of the measures used to assess how close forecasts or predictions might be to the observed values is the
[https://en.wikipedia.org/wiki/Mean_absolute_error mean absolute error]. We will use it to evaluate the performance of HANTS and LWR.

First, we will rebuild our time series with the corresponding output maps of r.hants and r.series.lwr. Here, only showed for LWR.

<source lang="bash">
# re-build time series
t.create type=strds temporaltype=absolute output=cla_lwr \
title="LWR output for Chl-a" \
description="MODIS Aqua L3 Chl-a 8-day 4km 2010-2013. Reconstruction with r.series.lwr"

# create list with filenames to parse
g.list type=raster pattern="*lwr" output=names_list

# parse filenames, convert YYYY-DOY to YYYY-MM-DD and write file to use in t.register
for mapname in `cat names_list` ; do
year_start=`echo ${mapname:1:4}`
doy_start=`echo ${mapname:5:3}`
year_end=`echo ${mapname:8:4}`
doy_end=`echo ${mapname:12:3}`
# convert YYYY-DOY to YYYY-MM-DD
#BEWARE: leading zeros make bash assume the number is in base 8 system, not base 10!
doy_start=`echo "$doy_start" | sed 's/^0*//'`
doy_end=`echo "$doy_end" | sed 's/^0*//'`
START_DATE=`date -d "${year_start}-01-01 +$(( ${doy_start} - 1 ))days" +%Y-%m-%d`
END_DATE=`date -d "${year_end}-01-01 +$(( ${doy_end} ))days" +%Y-%m-%d`
# print mapname, start and end date
echo "$mapname|$START_DATE|$END_DATE" >> map_list_start_and_end_time.txt
done

# register maps in strds
t.register input=cla_lwr type=raster file=map_list_start_and_end_time.txt
</source>

Now, we will estimate the MAE and use it to compare both methods. Again, only the example for LWR is showed.

<source lang="bash">
# obtain a strds of the absolute differences between predicted and observed Chl-a values
t.rast.algebra -n \
basename=lwr_minus_orig suffix=gran \
expression="abs_lwr_minus_orig = abs(cla_lwr - cla)"

# sum of the absolute differences (numerator) and count of non-null maps per pixel (denominator)
t.rast.series input=abs_lwr_minus_orig output=sum_abs_lwr_minus_orig method=sum
t.rast.series input=abs_lwr_minus_orig output=count_abs_lwr_minus_orig method=count

# MAE for LWR
r.mapcalc expression="mae_lwr = sum_abs_lwr_minus_orig / count_abs_lwr_minus_orig"

# remove intermediate strds and maps
t.remove -rf abs_lwr_minus_orig
g.remove -f type=raster name=sum_abs_lwr_minus_orig,count_abs_lwr_minus_orig
</source>

Let's now compare the predictions generated by both methods, HANTS and LWR, and the corresponding mean absolute error maps.

{|
|-
| [[Image:cla_vs_cla_hants.png|center|thumb|560px|Original Chl-a time series vs HANTS output.]] || [[Image:cla_vs_cla_lwr.png|center|thumb|560px|Original Chl-a time series vs LWR output.)]]
|-
| [[Image:mae_hants_map.png|center|thumb|560px|MAE of HANTS predictions.]] || [[Image:mae_lwr_map.png|center|thumb|560px|MAE of LWR predictions.]]
|}

=== Extract strds values for points in a vector ===

Let's say we need to extract values of the strds to check the behaviour of HANTS at given locations and compare it with the original values. We can graphically do that with {{cmd|g.gui.tplot}}, but if you need to take data outside GRASS, say, read it into R and do some other analysis (See [http://grasswiki.osgeo.org/wiki/R_statistics/rgrass7#Reading_in_data R_Statistics wiki page]) you may use {{cmd|v.what.strds}}. This module retrieves raster values from a given strds to the attribute table of a point vector map.

<source lang="bash">
# original data
v.what.strds input=points_cla strds=cla output=points_cla_out
v.db.select map=points_cla_out file=ts_points_cla.csv

# HANTS' reconstructed data (several runs)
for i in `seq 1 13` ; do
v.what.strds --overwrite input=points_cla strds=cla_hants_${i} output=points_hants_${i}_out
v.db.select map=points_cla file=ts_points_hants_${i}.csv
done
</source>

Another option would be to use {{cmd|t.rast.what}} that samples a space time raster dataset at specific vector point coordinates and writes the output to stdout or text file using different layouts. This module doesn't write the vector's attribute table.

<source lang="bash">
t.rast.what points=points strds=cla output=cla_points.csv null_value=NA separator=comma
</source>

=== Some other modules and addons useful in the time series context ===

* {{cmd|t.rast.accumulate}} and {{cmd|t.rast.accdetect}} to compute and detect cyclic accumulations in raster time series.
* {{AddonCmd|t.rast.what.aggr}} to sample a strds with a vector point map and get aggregated values of desired granularity either in stdout or in the vector's attribute table.
* {{AddonCmd|t.rast.out.xyz}} to export a strds to a CSV file.
* {{AddonCmd|t.rast.null}} to manage NULL-values of a strds.
* {{AddonCmd|v.strds.stats}} to calculate univariate statistics from a strds based on a vector map.
* {{AddonCmd|r.seasons}} to extract seasons from a time series.
* {{AddonCmd|r.bioclim}} to calculate bio-climatic indices.
* {{AddonCmd|r.change.info}} for landscape change assessment.
* {{AddonCmd|r.quantile.ref}} to determine the corresponding quantile for an input value from a reference raster time series.
* {{AddonCmd|r.regression.series}} and {{AddonCmd|r.mregression.series}} to perform univariate and multivariate linear regression among raster time series, respectively.
* {{AddonCmd|r.series.diversity}} to estimate diversity indices in raster time series.
* {{AddonCmd|r.series.decompose}} to decompose raster time series.
* {{AddonCmd|r.series.filter}} to apply Savitzky-Golay or median filters to raster time series.

== FAQ ==

=== Best practice data organization ===

When it comes to time series, thousands of maps are often involved. In order to keep control, here some suggestions:

* separate original data from derived aggregates: store them in separate mapsets
* for specific projects, maintain them in individual mapsets. You can access the STDS stored in other mapsets (same location) through
t.some.module input=my_strds@the_other_mapset output=result ...
as long as mapsets are indeed accessible, i.e.: in the mapset's search path (See {{cmd|g.mapsets}}).

=== Best practice multi user management ===

GRASS GIS supports multi-user data management and allows several users to work in the same location within their own mapsets. Data can be read from other mapsets but not edited there. The same principle applies to space time datasets (STDS), i.e. in case of having a collection of maps corresponding to a time series in a dedicated mapset, you need to also create the STDS therein (See {{cmd|t.create}} and {{cmd|t.register}}), so it is visible to other users in other mapsets when they use {{cmd|t.list}}, for example.

=== Use of ''where'' parameter (ticket [https://trac.osgeo.org/grass/ticket/2270 #2270]) ===

Pay attention when using the "where" option in t.* modules. In some occasions it may not yield the expected results. Given the backend database chosen for TGRASS implementation, you may not be selecting all maps you think if you forget to set time along with date in the where clause. For example, let's say we need to select maps from 2005-03-01 until 2005-05-31 included. You would think the following command would do the job:

<source lang="bash">
t.rast.list daily_temp where="start_time > '2005-03-01' and start_time <= '2005-05-31'"
</source>

but, no... The last map in the list is:

temp_0516|pruebas|2005-05-30 00:00:00|2005-05-31 00:00:00

which would be equivalent to:

<source lang="bash">
t.rast.list daily_temp where="start_time > '2005-03-01' and start_time < '2005-05-31'"
</source>

This is a product of sqlite. Therefore, if you need the last date included in your selection (map from 2005-05-31 in our example), you need to set time too.

<source lang="bash">
t.rast.list daily_temp where="start_time > '2005-03-01' and start_time <= '2005-05-31 00:00:00'" | tail -n1
temp_0517|pruebas|2005-05-31 00:00:00|2005-06-01 00:00:00
</source>

=== Aggregation with defined granularity ===

''Q: I need to aggregate a strds with a granularity of 1 year, but shifting the start day one month in each run, i.e.: changing the start_time to 2003-02-01, 2003-03-01, 2003-04-01 and so on... My question is: if i recursively change start_time with the 'where' parameter, will the module t.rast.aggregate "aggregate" to the next february, march, april (what i'd wish) or just till the end of 2003?''

A: If you specify a granularity of a year, then the start time to perform the aggregation will always be shifted to the 1st January of the current year and the end time the 1st January of the next year (eg. 2002-01-01 - 2003-01-01). If you wish to aggregate a full year but shifting one month forward then simply use a granularity of 12 months.

=== Listing maps with specific start month ===

''Q: I have a strds with 506 maps that correspond to 8-day composite products. I need to sequentially list all maps which "start_month" is January, February and so on... to use them as input in {{cmd|r.series}} (or {{cmd|t.rast.series}}). How can I achieve that?''

A: You can use the [https://www.sqlite.org/lang_datefunc.html datetime functionality of SQLite] to perform this task, this should work for January:

<source lang="bash">
t.rast.list input=cla_null_mayor65 \
where='start_time >= datetime(start_time, "start of year") and start_time <= datetime(start_time, "start of year", "1 month")'
</source>

=== Aggregation of seasonal data ===

''Q: How can I calculate average seasonal temperature starting from a daily temperatures temporal dataset?''

A: Use {{cmd|t.rast.aggregate.ds}}, the input is the daily strds, the sampling stds should have seasonal intervals. Then use average as method. The output will have seasonal aggregated temperatures. For a detailed workflow see: [https://grasswiki.osgeo.org/wiki/Temporal_data_processing/seasonal_aggregation seasonal aggregation example].

=== Aggregation of seasonal data using time ranges ===

A way to aggregate seasons from daily data without granularity but by using time ranges is shown here. The issue is to include for the season calculation also a month from the previous year. This can be addressed with some datetime calculations in SQLite:

<source lang="bash">
# We assume to have daily temperature data in DB "temp_daily_average"

# loop over seasons, generate aggregates:
### 'start_time' and 'end_time' are columns in TGRASS

for year in `seq 2004 2014` ; do

# we consider also a month of the previous year
for month in "12 01 02" "03 04 05" "06 07 08" "09 10 11" ; do
set -- $month ; echo $1 $2 $3

prevyear=$year
if [ $1 -eq 12 ] ; then
prevyear=`expr $year - 1`
fi

# prepare query strings in SQLite
MYSTART=`echo "SELECT strftime(datetime('${prevyear}-${1}-01'));" | sqlite3`
MYEND=`echo "SELECT strftime(datetime('${prevyear}-${1}-01','+3 month'));" | sqlite3`

# Debugging only, to see what it does:
echo "---- Querying ${prevyear}-${1}-01 ... ${year}-${3}-end:"
# we use start_time and end_time to get the proper time range
t.rast.list input=temp_daily_average@modis_lst_reconstructed_europe_daily \
where="start_time >= '$MYSTART' AND end_time <= '$MYEND'" > list_${prevyear}_${1}_${3}.csv

head -n 3 list_${prevyear}_${1}_${3}.csv
echo "..."
tail -n 3 list_${prevyear}_${1}_${3}.csv
echo "======="
rm -f list_${prevyear}_${1}_${3}.csv

# calculate aggregates:
method="average" # median mode minimum maximum stddev

t.rast.series input=temp_daily_average@modis_lst_reconstructed_europe_daily \
where="start_time >= '$MYSTART' AND end_time <= '$MYEND'" \
output=temp_${method}_${prevyear}_${1}
done
done
</source>

Much simpler '''alternative''' (which runs in parallel on multi-cores):
<source lang="bash">
t.rast.aggregate input=A output=B basename=b where="start_time >= '2004-03-01 00:00:00'" granularity="3 months"
</source>

=== How to count consecutive days that meet a certain condition? ===

This example was kindly contributed by Thomas Leppelt and shows how to obtain the number of consecutive days with temperature below 0 per week.

<source lang="bash">
# Set the computational region and resolution
g.region -p n=-30 s=-50 e=-50 w=-70 res=1

# We create maps for 100 days
for map in `seq 1 100` ; do
# generate synthetic maps as a seeding random values for temperatures
r.mapcalc -s expression="daily_temp_${map} = rand(-20,20)" --o
echo daily_temp_${map} >> map_list.txt
done

t.create type=strds temporaltype=absolute \
output=temperature_daily \
title="Daily Temperature" \
description="Test dataset with daily temperature"

t.register -i type=raster input=temperature_daily \
file=map_list.txt start="2014-03-07" increment="1 days" --o

# check general information of the daily strds
t.info type=strds input=temperature_daily

# Create weekly mask to which we will add 1 or 0 according to temperature in the days within it (each map in this week mask will have a value of 7)
t.rast.aggregate input=temperature_daily output=weekly_mask basename=mask_week granularity="1 weeks" method=count

# Calculate consecutive days with negative temperatures
t.rast.algebra base=neg_temp_days expression="consecutive_days = weekly_mask {+,contains,l} if(temperature_daily < 0 && temperature_daily[-1] < 0 || temperature_daily[1] < 0 && temperature_daily < 0, 1, 0)"
</source>

== Online tutorials and courses ==

* [https://web.archive.org/web/20160119125858/www.geostat-course.org/topic_gebbert/ The temporal GRASS GIS framework: Introduction and application] by Sören Gebbert (2012)
* CZ: [https://web.archive.org/web/20180316200749/https://training.gismentors.eu/grass-gis-pokrocily/tgrass/index.html Úvod do časoprostorových analýz] (Introduction to space-time analysis) by Martin Landa (2015)
* [https://gismentors.github.io/grass-gis-workshop-jena/units/21.html Sentinel spatio-temporal processing] by Martin Landa (2020)
* [https://github.com/veroandreo/tgrass_workshop_foss4g_eu TGRASS: temporal data processing with GRASS GIS] FOSS4G-EU workshop by Veronica Andreo, Luca Delucchi and Markus Neteler (2017)

== References ==
* Gebbert, S., Pebesma, E. 2014. ''TGRASS: A temporal GIS for field based environmental modeling''. Environmental Modelling & Software 53, 1-12 ([https://doi.org/10.1016/j.envsoft.2013.11.001 DOI]) - [https://ifgi.uni-muenster.de/~epebe_01/tgrass.pdf preprint PDF]
* Gebbert, S., Pebesma, E. 2017. ''The GRASS GIS temporal framework''. International Journal of Geographical Information Science 31, 1273-1292 ([https://doi.org/10.1080/13658816.2017.1306862 DOI]) - [https://figshare.com/articles/journal_contribution/The_GRASS_GIS_temporal_framework/4834013/1/files/8024429.pdf PDF]
* Gebbert, S., Leppelt, T., Pebesma, E., 2019. ''A topology based spatio-temporal map algebra for big data analysis''. Data 4, 86. ([https://doi.org/10.3390/data4020086 DOI]) - [https://www.mdpi.com/2306-5729/4/2/86/pdf?version=1560849201 PDF]

== See also ==
* Introduction: [http://www.slideshare.net/Luis_de_Sousa/presentation-soeren GRASS as a Temporal GIS] by Sören Gebbert (slides)
* [https://archive.org/details/TheTemporalGrassGisFrameworkIntroductionAndApplication# The temporal GRASS GIS framework: Introduction and application] Video of Sören Gebbert's presentation in [http://www.geostat-course.org/Muenster_2012 GEOSTAT course] 2012
* [https://grass.osgeo.org/grass-stable/manuals/temporalintro.html Introduction to temporal modules] (GRASS GIS manual)
* [https://grass.osgeo.org/grass-stable/manuals/temporal.html Available temporal modules] (GRASS GIS manual)
* [https://trac.osgeo.org/grass/wiki/Grass7/TemporalExtension Temporal Extension] (background info in trac)
* [[GRASS GSoC 2013 Temporal GIS Algebra for raster and vector data in GRASS]]

[[Category: Documentation]]
[[Category: Tutorial]]
[[Category: Temporal]]

Temporal data processing

2025-07-02T08:43:17Z

Neteler: Cleanup

== Introduction ==

TGRASS is the temporal enabled GRASS GIS.
TGRASS is completely metadata based, i.e. it does not change any data but simply handles the organization of raster, vector, raster3D maps actually stored in a GRASS GIS mapset by registering in an additional internal database. This is done specifically for managing temporal and spatial extent including temporal topology.

Manual overview: https://grass.osgeo.org/grass-stable/manuals/temporalintro.html

== Terminology Overview ==

* Space time raster datasets ('''strds''') are designed to manage raster map time series. Modules that process strds have the naming prefix ''t.rast''.
* Space time 3D raster datasets ('''str3ds''') are designed to manage 3D raster map time series. Modules that process str3ds have the naming prefix ''t.rast3d''.
* Space time vector datasets ('''stvds''') are designed to manage vector map time series. Modules that process stvds have the naming prefix ''t.vect''.

== Workflow overview ==

# create an empty space time datasets: strds, str3ds, or stvds ({{cmd|t.create}})
# register the GRASS GIS maps ({{cmd|t.register}})
# check the generated space time datasets ({{cmd|t.list}}, {{cmd|t.info}})
# do your analysis: {{cmd|t.rast.aggregate}}, {{cmd|t.info}}, {{cmd|t.rast.univar}}, {{cmd|t.vect.univar}}, ... so many more!

== Example workflow for a Chlorophyll-a MODIS time series ==

The following examples are based on a series of MODIS L3 Chlorophyll-a product that is freely available at the [http://oceancolor.gsfc.nasa.gov/cgi/l3?sen=A&per=MO&prd=CHL_chlor_a ocean color] site. So, say we download the SMI 8-day composite product at 4.6 km resolution for the period 2003-2013. That is a 506 set of images, 46 per year. Data comes as compressed HDF4 files. Chlorophyll products file names look like this:

<code>A20030012003008.L3m_8D_CHL_chlor_a_4km</code>

where,

A: MODIS/Aqua
2003: Year at start
001: Julian day at start
2003: Year at end
008: Julian day at end
L3m: Level 3 data, mapped (Projection: Plate carrée)
8D: 8 day composition
CHL: Chlorophyll a concentration product
chlor_a: algorithm used 10^(a0 + a1*X + a2*X^2 + a3*X^3 + a4*X^4)
4km: 4.6km pixel size (8640x4320 image, 2.5 minute resolution)

We now decompress files and check metadata

<source lang="bash">
# Go to where the data is and decompress
find -iname '*.bz2' -exec bzip2 -d {} \;
# Check file meta-data (GDAL utilities)
gdalinfo A20030012003008.L3m_8D_CHL_chlor_a_4km
</source>

Next step is to import all 506 images into GRASS. You can use {{cmd|r.in.gdal}} or {{cmd|r.external}} for that.
Note that global Cl-a images as downloaded from [http://oceancolor.gsfc.nasa.gov/cgi/l3?sen=A&per=MO&prd=CHL_chlor_a ocean color] site are ~150 mb each (disk space issues!). Here, 3 different options:

* import global images (506 images, 150 Mb each) with r.in.gdal, resize to study area and remove global files
* set projection and extension, and resize to study area with gdal_translate, and import already resized images with r.in.gdal
* import global images (506 images, 150 Mb each) with r.external, resize to study area and remove global files, as showed below:

<source lang="bash">
# define region extension
g.region -p n=-38 s=-55 w=-70 e=-56

suffix=_tmp
for map in *chlor* ; do
r.external input=$map output=${map}${suffix} -o
r.mapcalc expression="$map = ${map}${suffix}"
g.remove type=raster name=${map}${suffix}
done
</source>

Once we have maps inside GRASS GIS database we can start the temporal processing. If this is the first time you'll use temporal modules,
you need to run

<source lang="bash">
t.connect -d
</source>

to set the default temporal GIS database connection for the current mapset. If the connection is not initially set with {{cmd|t.connect}}, any temporal module that you try to run for the first time will first set the connection to the temporal database for you. The default TGIS database of type ''sqlite3'' is located in the PERMANENT mapset directory. Temporal GIS content from all created mapsets will be stored there.

=== Creating a STRDS and registering maps ===

'''Creating a STRDS'''

First step is to '''create a space time dataset''' by means of {{cmd|t.create}}. As an example, let us create a strds for the Chlorophyll-a (Cl-a) time series. We need to define the name and semantic type of the new space time dataset, its title and a description. By default a raster dataset is created with absolute time (Gregorian calendar). We can change that according to our needs with type and temporaltype options.

<source lang="bash">
t.create type=strds temporaltype=absolute output=cla \
title="Chlorophyll-a concentration" \
description="MODIS L3 Chlorophyll-a concentration for Argentinian sea" \
semantictype=mean
</source>

'''Registering maps'''

Then, we '''register the maps''' in the strds using {{cmd|t.register}}. This module assigns timestamps to raster, 3D raster and vector maps and register them in the temporal database and into space time datasets. Existing timestamps can be read and used by t.register. Note that this is a metadata based registration, nothing is imported into GRASS GIS since the maps are already present in the location (hence, no duplication occurs).

This module (and TGRASS in general) supports '''absolute time''' and '''relative time'''. The ''absolute'' temporal type refers to a fixed date or interval in the Gregorian calendar, while the ''relative'' temporal type refers to data without fixed time stamps (e.g., sequential maps used to calculate multi-decadal averages). Refer to the [http://www.geostat-course.org/system/files/Presentation_0.pdf TGRASS overview slides] for background.

Maps can be registered by command line argument (i.e., a list of comma separated map names) or using an input file. The start time, end time and a temporal increment can be provided either by command line or in the input file. End time and increment are mutually exclusive. Maps can be registered in several space time datasets using the same timestamp. For a more detailed explanation and examples on how to register maps in stds, see also [https://grasswiki.osgeo.org/wiki/Temporal_data_processing/maps_registration maps registration] wiki page.

Start time and end time with absolute time must be provided using the format yyyy-mm-dd HH:MM:SS +HHMM. It is also supported to specify the date yyyy-mm-dd only. In case of relative time, the temporal unit (years, months, days, hours, minutes or seconds) must be provided. The relative start time, end time and the increment are integers (see also {{cmd|t.register}}).

<source lang="bash">
# note: with -i we create intervals (start and end time) spanning the given increment, and starting from start.
t.register -i type=raster input=cla \
maps=`g.list raster pattern="*_chlor_*" separator=comma` \
start="2003-01-01" \
increment="8 days"
</source>

'''Dealing with weekly data'''

While the former would have been the simplest solution, our 8-day products have a problem: in this example the last image of each year is not a product of an 8-day composition, but 4 or 5-day. Then, when using the increment parameter, dates (and consequently, intervals) are not set properly.
The solution is to create a list of maps, with their respective start and end date. As the filenames contain information regarding year and DOY (day of year), we can use the following Python script to '''read filenames and transform DOY to calendar dates''' (Thanks Soeren!).

<source lang="python">
# Script to extract the input file for t.register from map names
# run in python
# modify to your needs

from os import walk
f = []
for (dirpath, dirnames, filenames) in walk("/path/to/the/maps"):
f.extend(filenames)
break
# to order the list
f.sort()

input_list=[]

import datetime
for map_name in f:
start_year = int(map_name[1:5])
start_day = int(map_name[5:8])
end_year = int(map_name[8:12])
end_day = int(map_name[12:15])
start = datetime.datetime(start_year, 1, 1) + datetime.timedelta(start_day - 1)
end = datetime.datetime(int(end_year), 1, 1) + datetime.timedelta(end_day)
map_list = map_name + '|' + str(start) + '|' + str(end)
print map_list
input_list.append(map_list)

print input_list

txt = '\n' .join(input_list)
f = open("input_list_cla.txt","w")
f.write(txt)
f.close()
</source>

Using the number of characters in the filenames and the datetime library in Python, you can convert DOY in the filenames into start_time and end_time as in the file you need to pass to {{cmd|t.register}}:

A20030012003008.L3m_8D_CHL_chlor_a_4km_arg|2003-01-01 00:00:00|2003-01-09 00:00:00
A20030092003016.L3m_8D_CHL_chlor_a_4km_arg|2003-01-09 00:00:00|2003-01-17 00:00:00
A20030172003024.L3m_8D_CHL_chlor_a_4km_arg|2003-01-17 00:00:00|2003-01-25 00:00:00
...
A20133452013352.L3m_8D_CHL_chlor_a_4km_arg|2013-12-11 00:00:00|2013-12-19 00:00:00
A20133532013360.L3m_8D_CHL_chlor_a_4km_arg|2013-12-19 00:00:00|2013-12-27 00:00:00
A20133612013365.L3m_8D_CHL_chlor_a_4km_arg|2013-12-27 00:00:00|2014-01-01 00:00:00

and then, the command would be:

<source lang="bash">
t.register --o type=raster input=cla file=input_list_cla.txt
</source>

As we are providing start and end time along with map names, we don't need to use the -i flag, neither set start nor increment options because that information is already contained in the file.

'''Assign a color table'''

We can also set a color table for all maps in the strds with {{cmd|t.rast.colors}}:

<source lang="bash">
# using a predetermined color table
t.rast.colors input=cla color=bcyr
#using your dedicated color table
t.rast.colors input=cla rules=path/to/your/color_table
</source>

Further examples of '''extracting timestamps from map names''' can be found here: [https://grasswiki.osgeo.org/wiki/Temporal_data_processing/maps_registration maps registration] wiki page.

=== Getting some basic info and statistics ===

We now check the space time data sets we have in our mapset with {{cmd|t.list}}:

<source lang="bash">
t.list type=strds
</source>

and get information about our recently created strds. See {{cmd|t.info}} for additional uses.

<source lang="bash">
t.info type=strds input=cla
</source>

+-------------------- Space Time Raster Dataset -----------------------------+
| |
+-------------------- Basic information -------------------------------------+
| Id: ........................ cla@clorofila
| Name: ...................... cla
| Mapset: .................... clorofila
| Creator: ................... veroandreo
| Temporal type: ............. absolute
| Creation time: ............. 2014-04-29 14:23:00.579342
| Modification time:.......... 2014-05-12 09:15:08.917309
| Semantic type:.............. mean
+-------------------- Absolute time -----------------------------------------+
| Start time:................. 2003-01-01 00:00:00
| End time:................... 2014-01-01 00:00:00
| Granularity:................ 1 day
| Temporal type of maps:...... interval
+-------------------- Spatial extent ----------------------------------------+
| North:...................... -38.0
| South:...................... -55.0
| East:.. .................... -55.0
| West:....................... -70.0
| Top:........................ 0.0
| Bottom:..................... 0.0
+-------------------- Metadata information ----------------------------------+
| Raster register table:...... raster_map_register_91ba57d5f0924f4fa0bd7176a1b39b2f
| North-South resolution min:. 0.041667
| North-South resolution max:. 0.041667
| East-west resolution min:... 0.041667
| East-west resolution max:... 0.041667
| Minimum value min:.......... 0.02925
| Minimum value max:.......... 0.26472
| Maximum value min:.......... 5.2104
| Maximum value max:.......... 99.953934
| Aggregation type:........... None
| Number of registered maps:.. 506
|
| Title:
| Chlorophyll-a
| Description:
| Concentracion de Clorofila a
| Command history:
| # 2014-04-29 14:23:00
| t.create type="strds" temporaltype="absolute"
| output="cla" title="Chlorophyll-a"
| description="Concentracion de Clorofila a" --o
| # 2014-04-29 14:23:23
| t.register --o type="rast" input="cla"
| file="input_list_cla.txt"
|
+----------------------------------------------------------------------------+

Now, we get univariate statistics from the non-null cells for each registered raster map of the strds. For that matter we use {{cmd|t.rast.univar}} which, by default, returns the name of the map, the start and end date of dataset and the following values: ''mean, minimum and maximum vale, mean_of_abs, standard deviation, variance, coeff_var, number of null cells, total number of cell''.

<source lang="bash">
t.rast.univar input=cla
</source>

Or, you can send the output to a text file using

<source lang="bash">
t.rast.univar input=cla separator=comma output=stats_cla.csv
</source>

This file "stats_cla.csv" you can now open in a spreadsheet or statistical software for inspection and plotting.

=== Listing maps and selections ===

The module {{cmd|t.rast.list}} allows you to list all the maps registered in a strds or a selection of them and, provides options for different listing methods, sorting of the list, information to print and so on. The ''where'' option in t.rast.list allows to perform different selections of maps to list. The ''columns'' that can be used to perform these selections are: ''id, name, creator, mapset, temporal_type, creation_time, start_time, end_time, north, south, west, east, nsres, ewres, cols, rows, number_of_cells, min and max''. (Note that for vector time series, i.e. stvds, the columns in {{cmd|t.vect.list}} differ from those for strds. You can check that with <code>t.vect.list --help</code>).

<source lang="bash">
t.rast.list input=cla method=gran granule="1 month"
# this will give one image every one month, 3 months, 1 year, or the granule you choose

t.rast.list input=cla order=min columns=id,name,start_time,min where="min <= '0.05'"
# this will order by minimum value all the maps in the strds that have a minimum value lower than or equal to 0.05

t.rast.list input=cla order=max columns=name,start_time,max where="max > '10.0'"
# maps ordered by maximum value in which maximum value is higher than 10.

t.rast.list input=cla where="start_time >= '2003-01' and start_time <= '2003-06'"
# all the maps in the first 6 month of the time series

t.rast.list input=cla where="strftime('%m', start_time)='01'"
# all the maps from January

t.rast.list input=cla where="strftime('%m-%d', start_time)='01-01'"
# all the maps from January, 1st

t.rast.list input=cla where="strftime('%w', start_time)='1'"
# all Mondays in the time series (Sunday is 0)
</source>

If you have monthly (instead of 8-day products) data and you want to list all January maps, then you can do:

<source lang="bash">
t.rast.list input=cla where="start_time=datetime(start_time, 'start of year', ' 0 month')"
</source>

Note: '''Do not forget to use single quotes around date''', neither in {{cmd|t.rast.list}} nor in any other of the t.* modules offering the ''where'' option, because the clause will be ignored (i.e.: no selection performed) and no warning nor error will be printed.

=== Visualization ===

There are different visualization options for strds.

* {{cmd|g.gui.timeline}} allows to compare temporal datasets by displaying their temporal extents in a plot.

<source lang="bash">
# only temporal extent
g.gui.timeline inputs=cla
# temporal and spatio-temporal extent
g.gui.timeline -3 inputs=cla
</source>

[[Image:Cla strds.png|center|thumb|560px|Temporal and spatio-temporal extent of cla strds.]]

* {{cmd|g.gui.tplot}} allows to see the values of one or more temporal datasets for a queried point defined by a coordinate pair.

Steps to use this module are:

# Select strds
# Select pair of coordinates (east,north) or mark a point in the map
# Hit Draw
# Customize plot as desired
# Save

[[Image:Output gguitplot.png|center|thumb|800px|Time series plot (Chlorophyll vs Time) for a certain coordinate pair in the study area]]

* {{cmd|g.gui.animation}} is the tool for animating a series of raster and vector maps or a space time raster or vector dataset.

<source lang="bash">
g.gui.animation strds=cla_monthly_average
</source>

[[Image:Grass70 temporal chlorophyll anim small.gif|framed|center|Monthly mean chlorophyll-a concentration]]

=== Aggregation ===

For aggregations of data with different methods and different granularities, there are two very useful commands:

* {{cmd|t.rast.series}} that applies different aggregation methods from {{cmd|r.series}} on all or a subset of raster maps in a strds, and

* {{cmd|t.rast.aggregate}} that temporally aggregates the maps in a strds by a user defined granularity.

With these modules it is very simple to get maps of basic statistical parameters for different temporal granules, and this permits the analysis of the spatio-temporal variability of the variable of interest.

Some examples:

<source lang="bash">
# yearly aggregation
t.rast.aggregate input=cla output=cla_yearly_average basename=cla_yearly_average \
granularity="1 years" method=average sampling=starts suffix=gran

# yearly aggregation with corresponding methods (output: 7 strds with 11 maps each)
for method in average median mode minimum maximum stddev range ; do
t.rast.aggregate input=cla output=cla_yearly_${method} \
basename=cla_yearly_${method} granularity="1 years" \
method=${method} sampling=starts suffix=gran
done
</source>

With the where parameter, as exemplified before, we can select for example all 8-day products which start_time is 01 (January) over the years. Like this we can get the so-known '''climatologies'''.

<source lang="bash">
t.rast.series input=cla method=average where="strftime('%m', start_time)='01'" output=january_average
</source>

We could also get long term averages for specific periods in a time series, e.g. January 5-year mean:

<source lang="bash">
t.rast.series input=cla \
where="start_time >= '2005-01-01' AND start_time <= '2009-12-01' AND strftime('%m', start_time)='01'" \
method=average output=jan_cla_mean_2000_2004

# say we take a 15 years period (2000-2014) of monthly data and we want monthly 5-year averages
YEAR_START=(2000 2005 2010)
YEAR_END=(2004 2009 2014)
count=${#YEAR_START[@]}

for i in `seq 1 $count` ; do
echo ${YEAR_START[$i-1]} ${YEAR_END[$i-1]}
for MONTH in `seq -w 1 12` ; do
t.rast.series input=cla \
where="start_time >= '"${YEAR_START[$i-1]}"-01-01' AND start_time <= '"${YEAR_END[$i-1]}"-12-01' AND strftime('%m', start_time)='"${MONTH}"'" \
method=average output=cla_${YEAR_START[$i-1]}_${YEAR_END[$i-1]}_month_${MONTH} --o
done
done
</source>

Generalizing a bit, to obtain monthly climatologies from a time series, we can:

<source lang="bash">
# monthly climatologies
for MONTH in `seq -w 1 12` ; do
for METHOD in average median stddev minimum maximum ; do
t.rast.series input=cla method=${METHOD} where="strftime('%m', start_time)='${MONTH}'" output=${METHOD}_${MONTH}
done
done

# seasonal climatologies
for i in "01 02 03" "04 05 06" "07 08 09" "10 11 12" ; do
set -- $i ; echo $1 $2 $3
for m in average median stddev minimum maximum ; do
t.rast.series input=cla method=${m} output=${m}_${1} \
where="strftime('%m',start_time)='"${1}"' or strftime('%m',start_time)='"${2}"' or strftime('%m', start_time)='"${3}"'"
done
done
</source>

Using the climatologies previously obtained, we'll now estimate monthly anomalies in the mean, max and min Cl-a concentration. First, we need to monthly aggregate data, and then do the difference between the monthly climatology and each respective monthly aggregate. We'll do the aggregation for the average, minimum and maximum of Cl-a concentration (from 506 input maps in cla strds, we'll get 132 maps in each monthly aggregated new strds).

<source lang="bash">
# monthly aggregates (132 maps)
for method in average minimum maximum ; do
t.rast.aggregate input=cla output=cla_monthly_${method} \
basename=cla_monthly_${method} \
granularity="1 months" method=${method} \
sampling=contains suffix=gran
done

# January anomalies in mean, min and max Cl-a
t.rast.list -u input=cla_monthly_average where="start_time=datetime(start_time, 'start of year', '0 month')" columns=name

for m in average minimum maximum ; do
for i in 1 13 25 37 49 61 73 85 97 109 121 ; do # these numbers correspond to all January monthly aggregates
r.mapcalc expression="Jan_${m}_anomaly_${i}=cla_monthly_${m}_${i}-01_${m}"
done
done
</source>

You can also use {{cmd|t.rast.list}} for looping, the same way you use {{cmd|g.list}}:

<source lang="bash">
for map in `t.rast.list -u input=cla_monthly_average where="strftime('%m', start_time)='01'" columns=name` ; do
r.mapcalc expression="anomaly_${map}=${map}-01_average"
done
</source>

Generalizing, we can estimate all monthly anomalies from mean like:

<source lang="bash">
for i in `seq -w 1 12` ; do
for map in `t.rast.list -u input=cla_monthly_average columns=name where="strftime('%m', start_time)='"${i}"'"` ; do
r.mapcalc expression="anomaly_${map}=${map}-average_${i}"
done
done
</source>

Say we now need to know the date of the maximum value of Cl-a concentration over all the study period and/or on a yearly basis:

<source lang="bash">
# map index for the overall maximum Cl-a value
t.rast.series input=cla method=max_raster output=cla_max_index

# map index for the yearly maximum Cl-a value
t.rast.aggregate input=cla granularity="1 year" method=max_raster output=yearly_max_index basename=yearly_max_index suffix=gran
</source>

The outputs show (pixelwise) the map index in which the maximum value of Cl-a occurs (from 1 to 506 and from 1 to 46, for the whole time series and on a yearly basis, respectively). For relative time this is maybe enough, but you may then want to reclassify data to get DOY, for example. In that case, you may use {{cmd|r.reclass}}.

If you already have monthly data, you can get climatologies quite simply as follows:

<source lang="bash">
# January averages
t.rast.series input=cla_monthly method=average where="start_time=datetime(start_time, 'start of year', '0 month')" output=jan_average
</source>

=== Spatio-temporal algebra with STRDS ===

The module {{cmd|t.rast.mapcalc}} allows us to perform spatio-temporal mapcalc expressions on temporally sampled maps of strds. There are spatial and temporal operators available for the "expression" string. Spatial operators, functions and internal variables are those used in {{cmd|r.mapcalc}}. Temporal internal variables supported for both relative and absolute time include: td(), start_time() and end_time(). There are also several very useful internal variables supported especially for absolute time of the current sample interval or instance, e.g.: start_doy(), start_year(), start_month() and so on (see {{cmd|t.rast.mapcalc}} manual for further details and examples).

Some examples now. Say we did some analysis and decided that we will only consider values higher than 0.05. Then, we need to set all values below that threshold to null.

<source lang="bash">
t.rast.mapcalc input=cla expression="if(cla < 0.05, null(), cla)" output=cla_corrected basename=cla_corrected
</source>

or we may also want to take negative erroneous values to the knowm minimum of the strds, so:

<source lang="bash">
t.rast.series input=cla method=minimum output=min_cla
t.rast.mapcalc input=cla expression="if(cla < 0.0, min_cla, cla)" output=cla_corrected basename=cla_corrected
</source>

We may also need to reclassify all maps in the strds according to a certain threshold, e.g.: a certain level of Cl-a that indicates bloom conditions, in order to get bloom frequency afterwards:

<source lang="bash">
# reclassify
t.rast.mapcalc -n input=cla output=cla_bloom basename=cla_bloom expression="if(cla > 0.75, 1, null())"
# bloom frequency
t.rast.series input=cla_bloom output=bloom_freq method=count
</source>

Do you remember we wanted to get the DOY of maximum Cl-a value before? Well, here's another way of doing it...

<source lang="bash">
# overall maximum value
t.rast.series input=cla method=maximum output=max_cla
# new strds with DOY of overall maximum
t.rast.mapcalc -n inputs=cla output=date_max_cla expression="if(cla == max_cla,start_doy(),null())" basename=date_max_cla
# map with DOY of overall maximum
t.rast.series input=date_max_cla method=maximum output=max_cla_date
# remove date_max_cla strds (we were only interested in the resulting aggregated map)
t.remove -rf inputs=date_max_cla
</source>

There's also a {{cmd|t.rast.algebra}} module that allows for temporal and spatial operations on strds by means of temporal raster algebra. The module expects an expression in the following form: "result = expression".

The statement structure is similar to r.mapcalc, the result is the name of a new strds that will contain the result of the calculation given as expression. Expressions can be any valid or nested combination of temporal operations and spatial overlay or buffer functions that are provided by the temporal algebra. See the manual for further details and explanations.

We'll use this module to estimate the rate of change (slope) between every pair of maps in the "cla" strds. The result will be a new strds consisting of maps with the slope value between every consecutive pair of maps in the original strds:

<source lang="bash">
# we set 8 as fixed denominator, because products are 8-day compositions
t.rast.algebra expression="slope_cla = (cla[1]-cla[0])/8.0" basename=slope_cla
</source>

We can then use any of the aggregation modules that we saw before to get the maximum or minimumm rate of change for different granularities.

===== Some known issues with t.rast.mapcalc =====

It has been observed that if the names of inputs and output space time datasets (partially) match each other, t.rast.mapcalc may not work properly (especially when several input strds are used). This is because the module uses a simple search and replace approach to substitute the input strds with the corresponding map names. Eventualy, choosing a specific order for the input strds in the input parameter may reduce the risk of wrong substitution. Therefore, especially in operations involving several strds (with partially matching names) as inputs, '''it is recommended to use {{cmd|t.rast.algebra}} that correctly recognizes spatio-temporal datasets''' rather than t.rast.mapcalc.

=== Subseting and something else ===

{{cmd|t.rast.extract}} is another really useful module within temporal GRASS. It allows to extract a subset of a strds and store it in a different strds. The "where" condition is used to do the subset, but you can also specify a r.mapcalc sub-expression that performs operations on all maps of the selected subset. If no r.mapcalc expression is defined, the selected maps are simply registered in the new output strds.

Say we need to know in how many maps of the strds minimum values are below a certain threshold, and not only that, but we also want to know how many pixels per map meet that condition. Then, we can do

<source lang="bash">
t.rast.extract input=cla where="min <= '0.05'" output=cla_less_05 basename=cla_less_05 expression="if(cla < 0.05, 1, null())"
</source>

to extract those maps with a minimum value lower than 0.05, and in the same step put 1 in every cell meeting the criterium and null everywhere else. To get a count of maps and pixels meeting the condition we may use:

<source lang="bash">
# univariate stistics to get the count per map
t.rast.univar input=cla_less_05
# count map of cells with min value < 0.05
t.rast.series input=cla_less_05 output=count_cla_less_05 method=count
</source>

=== Importing / Exporting STRDS ===

Say we now need to do some processing in R (e.g.: run [http://menugget.blogspot.com.ar/2012/10/dineof-data-interpolating-empirical.html DINEOF] to fill gaps in data), so we need to export our strds, hence we use {{cmd|t.rast.export}}.

<source lang="bash">
t.rast.export input=cla output=cla4R compression=gzip
</source>

After we have done our analysis we can import the whole strds back to GRASS again, exporting it from R with read/write.tgrass from [http://cran.r-project.org/web/packages/spacetime/index.html spacetime] R package and using {{cmd|t.rast.import}} in GRASS.

<source lang="bash">
t.rast.import input=cla_from_R.tar.gz output=cla_from_R basename=new_map directory=/tmp
</source>

For a full example of how to handle raster time series between GRASS and R, please visit the [https://grasswiki.osgeo.org/wiki/Temporal_data_processing/raster_time_series_grass_R_statistics time series GRASS-R Statistics] wiki. The example is based on North Carolina climate location [http://courses.ncsu.edu/mea592/common/media/02/nc_climate_spm_2000_2012.zip] and includes the following steps:

# Exporting the strds out of GRASS
# Importing into R
# Re-formating the data
# Running [http://modb.oce.ulg.ac.be/mediawiki/index.php/DINEOF DINEOF]
# Re-constructing the raster time series
# Exporting out of R, and
# Importing the gap-filled new strds into GRASS.

=== Neighborhood analysis ===

{{cmd|t.rast.neighbors}} performs a neighborhood analysis for each map in a space time raster dataset. This module supports a subset of the options already available in r.neighbors. Both, size of the neighborhood and aggregation method can be chosen. As an example, we'll estimate mean Cl-a concentration in a 3x3 neighborhood for every map in the strds.

<source lang="bash">
t.rast.neighbors input=cla output=cla_smoth base=cla_smooth method=average size=3
</source>

=== Filling and reconstructing time series data with gaps ===

==== Harmonic ANalysis of Time Series - HANTS ====

{{AddonCmd|r.hants}} is an add-on not strictly within the temporal modules, but really useful when working with time series data, particularly with gappy data. Here's a simple example for generating a list of temporally ordered maps to use as input in '''r.hants''', running HANTS and getting a map of dominant frequencies, afterwards. See the manual for further information on parameter setting and explanations.

<source lang="bash">
# use t.rast.list to create a list of temporally ordered maps
t.rast.list input=cla order=start_time columns=name -u > map_list.csv

# a HANTS run using the list of maps
r.hants -l file=map_list.csv nf=5 fet=0.1 dod=11 base_period=46 suffix=_hants amplitude=amp_hants phase=pha_hants

# dominant frequency map (0 means the dominant freq is 1, 1 that dominant freq is 2, and so on...)
r.series input=`g.list type=raster pattern="amp_hants*" separator=comma` output=dominant_freq_hants method=max_raster
</source>

==== Local Weighted Regression - LWR ====

Another very useful add-on for the reconstruction of gappy time series, such as those from remote sensing imagery, is {{AddonCmd|r.series.lwr}}. This module performs a local weighted regression (LWR) of the input maps in order to estimate missing values and identify (and remove) outliers. See the manual for further information and explanations.

<source lang="bash">
# use same list as before
t.rast.list input=cla order=start_time columns=name -u > map_list.csv

# run r.series.lwr
r.series.lwr file=map_list.csv suffix=_lwr order=2 weight=tricube range=0.0,65.0 dod=16 fet=0.1 -l
</source>

==== Estimate Mean Absolute Error (MAE) ====

One of the measures used to assess how close forecasts or predictions might be to the observed values is the
[https://en.wikipedia.org/wiki/Mean_absolute_error mean absolute error]. We will use it to evaluate the performance of HANTS and LWR.

First, we will rebuild our time series with the corresponding output maps of r.hants and r.series.lwr. Here, only showed for LWR.

<source lang="bash">
# re-build time series
t.create type=strds temporaltype=absolute output=cla_lwr \
title="LWR output for Chl-a" \
description="MODIS Aqua L3 Chl-a 8-day 4km 2010-2013. Reconstruction with r.series.lwr"

# create list with filenames to parse
g.list type=raster pattern="*lwr" output=names_list

# parse filenames, convert YYYY-DOY to YYYY-MM-DD and write file to use in t.register
for mapname in `cat names_list` ; do
year_start=`echo ${mapname:1:4}`
doy_start=`echo ${mapname:5:3}`
year_end=`echo ${mapname:8:4}`
doy_end=`echo ${mapname:12:3}`
# convert YYYY-DOY to YYYY-MM-DD
#BEWARE: leading zeros make bash assume the number is in base 8 system, not base 10!
doy_start=`echo "$doy_start" | sed 's/^0*//'`
doy_end=`echo "$doy_end" | sed 's/^0*//'`
START_DATE=`date -d "${year_start}-01-01 +$(( ${doy_start} - 1 ))days" +%Y-%m-%d`
END_DATE=`date -d "${year_end}-01-01 +$(( ${doy_end} ))days" +%Y-%m-%d`
# print mapname, start and end date
echo "$mapname|$START_DATE|$END_DATE" >> map_list_start_and_end_time.txt
done

# register maps in strds
t.register input=cla_lwr type=raster file=map_list_start_and_end_time.txt
</source>

Now, we will estimate the MAE and use it to compare both methods. Again, only the example for LWR is showed.

<source lang="bash">
# obtain a strds of the absolute differences between predicted and observed Chl-a values
t.rast.algebra -n \
basename=lwr_minus_orig suffix=gran \
expression="abs_lwr_minus_orig = abs(cla_lwr - cla)"

# sum of the absolute differences (numerator) and count of non-null maps per pixel (denominator)
t.rast.series input=abs_lwr_minus_orig output=sum_abs_lwr_minus_orig method=sum
t.rast.series input=abs_lwr_minus_orig output=count_abs_lwr_minus_orig method=count

# MAE for LWR
r.mapcalc expression="mae_lwr = sum_abs_lwr_minus_orig / count_abs_lwr_minus_orig"

# remove intermediate strds and maps
t.remove -rf abs_lwr_minus_orig
g.remove -f type=raster name=sum_abs_lwr_minus_orig,count_abs_lwr_minus_orig
</source>

Let's now compare the predictions generated by both methods, HANTS and LWR, and the corresponding mean absolute error maps.

{|
|-
| [[Image:cla_vs_cla_hants.png|center|thumb|560px|Original Chl-a time series vs HANTS output.]] || [[Image:cla_vs_cla_lwr.png|center|thumb|560px|Original Chl-a time series vs LWR output.)]]
|-
| [[Image:mae_hants_map.png|center|thumb|560px|MAE of HANTS predictions.]] || [[Image:mae_lwr_map.png|center|thumb|560px|MAE of LWR predictions.]]
|}

=== Extract strds values for points in a vector ===

Let's say we need to extract values of the strds to check the behaviour of HANTS at given locations and compare it with the original values. We can graphically do that with {{cmd|g.gui.tplot}}, but if you need to take data outside GRASS, say, read it into R and do some other analysis (See [http://grasswiki.osgeo.org/wiki/R_statistics/rgrass7#Reading_in_data R_Statistics wiki page]) you may use {{cmd|v.what.strds}}. This module retrieves raster values from a given strds to the attribute table of a point vector map.

<source lang="bash">
# original data
v.what.strds input=points_cla strds=cla output=points_cla_out
v.db.select map=points_cla_out file=ts_points_cla.csv

# HANTS' reconstructed data (several runs)
for i in `seq 1 13` ; do
v.what.strds --overwrite input=points_cla strds=cla_hants_${i} output=points_hants_${i}_out
v.db.select map=points_cla file=ts_points_hants_${i}.csv
done
</source>

Another option would be to use {{cmd|t.rast.what}} that samples a space time raster dataset at specific vector point coordinates and writes the output to stdout or text file using different layouts. This module doesn't write the vector's attribute table.

<source lang="bash">
t.rast.what points=points strds=cla output=cla_points.csv null_value=NA separator=comma
</source>

=== Some other modules and addons useful in the time series context ===

* {{cmd|t.rast.accumulate}} and {{cmd|t.rast.accdetect}} to compute and detect cyclic accumulations in raster time series.
* {{AddonCmd|t.rast.what.aggr}} to sample a strds with a vector point map and get aggregated values of desired granularity either in stdout or in the vector's attribute table.
* {{AddonCmd|t.rast.out.xyz}} to export a strds to a CSV file.
* {{AddonCmd|t.rast.null}} to manage NULL-values of a strds.
* {{AddonCmd|v.strds.stats}} to calculate univariate statistics from a strds based on a vector map.
* {{AddonCmd|r.seasons}} to extract seasons from a time series.
* {{AddonCmd|r.bioclim}} to calculate bio-climatic indices.
* {{AddonCmd|r.change.info}} for landscape change assessment.
* {{AddonCmd|r.quantile.ref}} to determine the corresponding quantile for an input value from a reference raster time series.
* {{AddonCmd|r.regression.series}} and {{AddonCmd|r.mregression.series}} to perform univariate and multivariate linear regression among raster time series, respectively.
* {{AddonCmd|r.series.diversity}} to estimate diversity indices in raster time series.
* {{AddonCmd|r.series.decompose}} to decompose raster time series.
* {{AddonCmd|r.series.filter}} to apply Savitzky-Golay or median filters to raster time series.

== FAQ ==

=== Best practice data organization ===

When it comes to time series, thousands of maps are often involved. In order to keep control, here some suggestions:

* separate original data from derived aggregates: store them in separate mapsets
* for specific projects, maintain them in individual mapsets. You can access the STDS stored in other mapsets (same location) through
t.some.module input=my_strds@the_other_mapset output=result ...
as long as mapsets are indeed accessible, i.e.: in the mapset's search path (See {{cmd|g.mapsets}}).

=== Best practice multi user management ===

GRASS GIS supports multi-user data management and allows several users to work in the same location within their own mapsets. Data can be read from other mapsets but not edited there. The same principle applies to space time datasets (STDS), i.e. in case of having a collection of maps corresponding to a time series in a dedicated mapset, you need to also create the STDS therein (See {{cmd|t.create}} and {{cmd|t.register}}), so it is visible to other users in other mapsets when they use {{cmd|t.list}}, for example.

=== Use of ''where'' parameter (ticket [https://trac.osgeo.org/grass/ticket/2270 #2270]) ===

Pay attention when using the "where" option in t.* modules. In some occasions it may not yield the expected results. Given the backend database chosen for TGRASS implementation, you may not be selecting all maps you think if you forget to set time along with date in the where clause. For example, let's say we need to select maps from 2005-03-01 until 2005-05-31 included. You would think the following command would do the job:

<source lang="bash">
t.rast.list daily_temp where="start_time > '2005-03-01' and start_time <= '2005-05-31'"
</source>

but, no... The last map in the list is:

temp_0516|pruebas|2005-05-30 00:00:00|2005-05-31 00:00:00

which would be equivalent to:

<source lang="bash">
t.rast.list daily_temp where="start_time > '2005-03-01' and start_time < '2005-05-31'"
</source>

This is a product of sqlite. Therefore, if you need the last date included in your selection (map from 2005-05-31 in our example), you need to set time too.

<source lang="bash">
t.rast.list daily_temp where="start_time > '2005-03-01' and start_time <= '2005-05-31 00:00:00'" | tail -n1
temp_0517|pruebas|2005-05-31 00:00:00|2005-06-01 00:00:00
</source>

=== Aggregation with defined granularity ===

''Q: I need to aggregate a strds with a granularity of 1 year, but shifting the start day one month in each run, i.e.: changing the start_time to 2003-02-01, 2003-03-01, 2003-04-01 and so on... My question is: if i recursively change start_time with the 'where' parameter, will the module t.rast.aggregate "aggregate" to the next february, march, april (what i'd wish) or just till the end of 2003?''

A: If you specify a granularity of a year, then the start time to perform the aggregation will always be shifted to the 1st January of the current year and the end time the 1st January of the next year (eg. 2002-01-01 - 2003-01-01). If you wish to aggregate a full year but shifting one month forward then simply use a granularity of 12 months.

=== Listing maps with specific start month ===

''Q: I have a strds with 506 maps that correspond to 8-day composite products. I need to sequentially list all maps which "start_month" is January, February and so on... to use them as input in {{cmd|r.series}} (or {{cmd|t.rast.series}}). How can I achieve that?''

A: You can use the [https://www.sqlite.org/lang_datefunc.html datetime functionality of SQLite] to perform this task, this should work for January:

<source lang="bash">
t.rast.list input=cla_null_mayor65 \
where='start_time >= datetime(start_time, "start of year") and start_time <= datetime(start_time, "start of year", "1 month")'
</source>

=== Aggregation of seasonal data ===

''Q: How can I calculate average seasonal temperature starting from a daily temperatures temporal dataset?''

A: Use {{cmd|t.rast.aggregate.ds}}, the input is the daily strds, the sampling stds should have seasonal intervals. Then use average as method. The output will have seasonal aggregated temperatures. For a detailed workflow see: [https://grasswiki.osgeo.org/wiki/Temporal_data_processing/seasonal_aggregation seasonal aggregation example].

=== Aggregation of seasonal data using time ranges ===

A way to aggregate seasons from daily data without granularity but by using time ranges is shown here. The issue is to include for the season calculation also a month from the previous year. This can be addressed with some datetime calculations in SQLite:

<source lang="bash">
# We assume to have daily temperature data in DB "temp_daily_average"

# loop over seasons, generate aggregates:
### 'start_time' and 'end_time' are columns in TGRASS

for year in `seq 2004 2014` ; do

# we consider also a month of the previous year
for month in "12 01 02" "03 04 05" "06 07 08" "09 10 11" ; do
set -- $month ; echo $1 $2 $3

prevyear=$year
if [ $1 -eq 12 ] ; then
prevyear=`expr $year - 1`
fi

# prepare query strings in SQLite
MYSTART=`echo "SELECT strftime(datetime('${prevyear}-${1}-01'));" | sqlite3`
MYEND=`echo "SELECT strftime(datetime('${prevyear}-${1}-01','+3 month'));" | sqlite3`

# Debugging only, to see what it does:
echo "---- Querying ${prevyear}-${1}-01 ... ${year}-${3}-end:"
# we use start_time and end_time to get the proper time range
t.rast.list input=temp_daily_average@modis_lst_reconstructed_europe_daily \
where="start_time >= '$MYSTART' AND end_time <= '$MYEND'" > list_${prevyear}_${1}_${3}.csv

head -n 3 list_${prevyear}_${1}_${3}.csv
echo "..."
tail -n 3 list_${prevyear}_${1}_${3}.csv
echo "======="
rm -f list_${prevyear}_${1}_${3}.csv

# calculate aggregates:
method="average" # median mode minimum maximum stddev

t.rast.series input=temp_daily_average@modis_lst_reconstructed_europe_daily \
where="start_time >= '$MYSTART' AND end_time <= '$MYEND'" \
output=temp_${method}_${prevyear}_${1}
done
done
</source>

Much simpler '''alternative''' (which runs in parallel on multi-cores):
<source lang="bash">
t.rast.aggregate input=A output=B basename=b where="start_time >= '2004-03-01 00:00:00'" granularity="3 months"
</source>

=== How to count consecutive days that meet a certain condition? ===

This example was kindly contributed by Thomas Leppelt and shows how to obtain the number of consecutive days with temperature below 0 per week.

<source lang="bash">
# Set the computational region and resolution
g.region -p n=-30 s=-50 e=-50 w=-70 res=1

# We create maps for 100 days
for map in `seq 1 100` ; do
# generate synthetic maps as a seeding random values for temperatures
r.mapcalc -s expression="daily_temp_${map} = rand(-20,20)" --o
echo daily_temp_${map} >> map_list.txt
done

t.create type=strds temporaltype=absolute \
output=temperature_daily \
title="Daily Temperature" \
description="Test dataset with daily temperature"

t.register -i type=raster input=temperature_daily \
file=map_list.txt start="2014-03-07" increment="1 days" --o

# check general information of the daily strds
t.info type=strds input=temperature_daily

# Create weekly mask to which we will add 1 or 0 according to temperature in the days within it (each map in this week mask will have a value of 7)
t.rast.aggregate input=temperature_daily output=weekly_mask basename=mask_week granularity="1 weeks" method=count

# Calculate consecutive days with negative temperatures
t.rast.algebra base=neg_temp_days expression="consecutive_days = weekly_mask {+,contains,l} if(temperature_daily < 0 && temperature_daily[-1] < 0 || temperature_daily[1] < 0 && temperature_daily < 0, 1, 0)"
</source>

== Online tutorials and courses ==

* [https://web.archive.org/web/20160119125858/www.geostat-course.org/topic_gebbert/ The temporal GRASS GIS framework: Introduction and application] by Sören Gebbert (2012)
* CZ: [https://web.archive.org/web/20180316200749/https://training.gismentors.eu/grass-gis-pokrocily/tgrass/index.html Úvod do časoprostorových analýz] (Introduction to space-time analysis) by Martin Landa (2015)
* [https://gismentors.github.io/grass-gis-workshop-jena/units/21.html Sentinel spatio-temporal processing] by Martin Landa (2020)
* [https://github.com/veroandreo/tgrass_workshop_foss4g_eu TGRASS: temporal data processing with GRASS GIS] FOSS4G-EU workshop by Veronica Andreo, Luca Delucchi and Markus Neteler (2017)

== References ==
* Gebbert, S., Pebesma, E. 2014. ''TGRASS: A temporal GIS for field based environmental modeling''. Environmental Modelling & Software 53, 1-12 ([http://dx.doi.org/10.1016/j.envsoft.2013.11.001 DOI]) - [http://ifgi.uni-muenster.de/~epebe_01/tgrass.pdf preprint PDF]
* Gebbert, S., Pebesma, E. 2017. ''The GRASS GIS temporal framework''. International Journal of Geographical Information Science 31, 1273-1292 ([http://dx.doi.org/10.1080/13658816.2017.1306862 DOI]) - [https://figshare.com/articles/journal_contribution/The_GRASS_GIS_temporal_framework/4834013/1/files/8024429.pdf PDF]
* Gebbert, S., Leppelt, T., Pebesma, E., 2019. ''A topology based spatio-temporal map algebra for big data analysis''. Data 4, 86. ([https://doi.org/10.3390/data4020086 DOI]) - [https://www.mdpi.com/2306-5729/4/2/86/pdf?version=1560849201 PDF]

== See also ==
* Introduction: [http://www.slideshare.net/Luis_de_Sousa/presentation-soeren GRASS as a Temporal GIS] by Sören Gebbert (slides)
* [https://archive.org/details/TheTemporalGrassGisFrameworkIntroductionAndApplication# The temporal GRASS GIS framework: Introduction and application] Video of Sören Gebbert's presentation in [http://www.geostat-course.org/Muenster_2012 GEOSTAT course] 2012
* [https://grass.osgeo.org/grass-stable/manuals/temporalintro.html Introduction to temporal modules] (GRASS GIS manual)
* [https://grass.osgeo.org/grass-stable/manuals/temporal.html Available temporal modules] (GRASS GIS manual)
* [https://trac.osgeo.org/grass/wiki/Grass7/TemporalExtension Temporal Extension] (background info in trac)
* [[GRASS GSoC 2013 Temporal GIS Algebra for raster and vector data in GRASS]]

[[Category: Documentation]]
[[Category: Tutorial]]
[[Category: Temporal]]

GRASS messages translation

2025-06-22T16:09:22Z

Neteler: /* Add Weblate generated translation badge to README files */ Adding new translators

== GRASS messages translation project ==

Many users prefer to use software in their mother tongue which is mostly not English. This requires that all GRASS software messages have to be translated to languages other than English. The GRASS Development Team is seeking translators. Please subscribe to the dedicated mailing list at

GRASS translations mailing list
http://lists.osgeo.org/mailman/listinfo/grass-translations

Translation related issues may be discussed there. This is an opportunity for non-programmers to contribute as messages can be easily translated. No programming skills required!

* Join the [[GRASS_Translation_Team#Members_of_Translation_Team|team]]

=== Wanted languages ===

Simple Chinese, Swahili, Hindi, Greek, Tamil, Russian, Telugu, Português, ... Please join us!

== Weblate translation platform ==

Weblate is a web-based translation tool with tight version control integration. It features a simple and clean user interface, propagation of translations across components, quality checks and automatic linking to source files.

(Note that we migrated from Transifex to [https://weblate.osgeo.org/projects/grass-gis/ Weblate] in 2023. All messages on Transifex have been transferred to Weblate.)

=== How to translate ===
'''''NOTE: THIS IS FOR TRANSLATOR'''''

* For terminology, please refer to the [[GRASS Translation Glossary]].

Register yourself on the [https://weblate.osgeo.org/projects/grass-gis/ Weblate website] using the [https://www.osgeo.org/community/getting-started-osgeo/osgeo_userid/ OSGeo-ID], and start to translate (grasswxpy is the GUI translation and it should be the first translated).

=== Using the machine translation tool ===

Using the machine translation tool: We have added the DeepL.com API which helps for selected languages to come to speed with translations.

Usage: login to Weblate. Then you see a button "Automatic suggestion". Use "Clone Translation" to copy over the suggested translation, edit as needed and save it.

[[File:Weblate with machine translation DeepL.png|thumb|800px|center|alt=Weblate with machine translation DeepL.com API|Weblate with machine translation DeepL.com API]]

=== Automated upload of your translation work to the GRASS GIS project in GitHub ===

Every 24 hours the new translations are automatically pushed to https://github.com/OSGeo/grass/pulls.
One of the maintainers will take care to merge them into the code so that it becomes part of the next release.

=== Files to be edited ===

==== GRASS GIS 8 translations ====
In GRASS GIS 8, we have only 3 types of .po files per language (the files are stored in the source code, in directory locale/po/):



<center>
[[Image:Weblate grassgis widget.png|center|link=https://weblate.osgeo.org/projects/grass-gis/]]
(click to see the GRASS GIS Weblate pages)
</center>

* <tt>grasslibs_LANG.po</tt>: messages from libraries
* <tt>grassmods_LANG.po</tt>: messages from commands ("modules")
* <tt>grasswxpy_LANG.po</tt>: messages from wxgrass/wxPython graphical user interface

where "LANG" in the above file names is a two character code which indicates the language. It is based on the Alpha-2 code of [http://www.loc.gov/standards/iso639-2/php/English_list.php ISO 639-1] (right column). Example: <tt>grasswxpy_pl.po</tt> for Polish.

'''We highly recommend to use our Weblate server: https://weblate.osgeo.org/projects/grass-gis/'''!

==== Add support for a new language ====

Go to any component, e.g. grasslibs - https://weblate.osgeo.org/projects/grass-gis/grasslibs/

Then click on the <code>+</code> button to add a language. You have to do it for each component.

==== Adding Weblate generated translation badge to README files ====

We may consider to add a translation status badge, pointing to [https://weblate.osgeo.org/projects/grass-gis/ Weblate], to the server README.md on GitHub:

<syntaxhighlight lang="markdown">
[![Translation status](https://weblate.osgeo.org/widgets/grass-gis/-/svg-badge.svg)](https://weblate.osgeo.org/engage/grass-gis/?utm_source=widget)
</syntaxhighlight>

Yet a TODO.

==== Adding new translators: giving credit ====

New translators need to be added here:
https://github.com/OSGeo/grass/blob/main/translators.csv

=== Weblate: technical background on the installation ===

'''How it works:''' when a developer makes a GRASS GIS repo commit on GitHub, GitHub then calls the [https://github.com/OSGeo/grass/pull/3065#issuecomment-1716446226 webhook] on Weblate which triggers a refresh of Weblate's git fork of the GRASS GIS repo (check at https://github.com/osgeoweblate/grass/tree/weblate-grass-gis-grasslibs).

For pushing translations back to GitHub, there is a setting in Weblate for that which defaults to 24 hrs (accumulates translations over a day). Then a pull request with the translations will be opened in the GRASS GIS GitHub repo.

For technical background on the OSGeo Weblate installation, see https://wiki.osgeo.org/wiki/SAC:Weblate .

For GRASS GIS related Weblate troubleshooting, see the discussion in this OSGeo-SAC ticket: https://trac.osgeo.org/osgeo/ticket/2981

'''Weblate Troubleshooting:'''

In case the Weblate's git copy of the GRASS GIS repo does no longer update due to
a conflict or whatever reason:

Log into Weblate (requires administrator rights) and check on <https://weblate.osgeo.org/projects/grass-gis/#repository>
click on the "Manage" -> "Repository Maintenance". Therein choose "Update" button,
"Update with merge without fast-forward". If successful, this will create
another pull request in the GRASS GIS repo (trigger with "Push" button).

=== Continuing an existing translation ===

The file(s) are there but partially outdated? Read on.

First '''announce''' on the [http://lists.osgeo.org/mailman/listinfo/grass-translations GRASS translations mailing list] that you plan to continue the translation of a certain language. Why? Because sometimes people silently translate already and we need these efforts to be coordinated to avoid doing it twice...

Then get these four .po files for your language and start. If a file is missing, just ask on the list to get it generated or see next section. To get these .po files (the files are in the directory locale/po/):

* either [https://github.com/OSGeo/grass/tree/master/locale/po/ download current .po files] directly from SVN (click on file name to download),
* or [https://grass.osgeo.org/download/0 download source code package] from GitHub,
* or download the recent [https://grass.osgeo.org/grass78/source/snapshot/ source code snapshot],
* or ask on the [https://lists.osgeo.org/mailman/listinfo/grass-translations GRASS translations mailing list] for these files.

Then edit the files with a .po file editor (poEDIT or kbabel or..., see below). Take care to maintain layout and special characters. And '''submit often''' - if you wait for weeks, the messages may already be outdated and your time wasted. Just keep in touch on the [https://lists.osgeo.org/mailman/listinfo/grass-translations GRASS translations mailing list]!

=== Starting a new translation ===

The language you want isn't yet there? Read on.

Briefly, the steps to create new messages files are (if you find this too complicated, ask on the [https://lists.osgeo.org/mailman/listinfo/grass-translations GRASS translations mailing list] to get these files done for you!):

# Get the latest source code development version from either the SVN repository or as SVN snapshot (see [https://grass.osgeo.org/download/ Download]).
# run: './configure --with-nls [... other parameters]' to configure the GRASS source code
# run: 'cd locale' to change into the translation directory
# run: 'make pot' to create grass*.pot template files (to extract original messages)
# run: copy these file from templates/ into po/; rename them to contain the two characters language code (see Alpha-2 code of [http://www.loc.gov/standards/iso639-2/php/English_list.php ISO 639-1]) and to .po extension; update the file headers either manually or with your .po editing software
(Example: Polish language):
mv ./templates/grasslibs.pot ./po/grasslibs_pl.po
mv ./templates/grassmods.pot ./po/grassmods_pl.po
mv ./templates/grassnviz.pot ./po/grassnviz_pl.po
mv ./templates/grasstcl.pot ./po/grasstcl_pl.po
mv ./templates/grasswxpy.pot ./po/grasswxpy_pl.po

Now translate the messages in these po/*.po files (using poEDIT or other editor, see below)

From time to time messages need to be updated from the originals. This is usually done by the GRASS translation manager.

=== Create a new project ===

'''''NOTE: CORE DEVELOPERS ONLY!'''''

TODO 2023: improve this section!

A project should be done for each stable release, only an Organization Administrators can create a project. From the dashboard in the left bottom corner there is "'''New project'''" button. Fill all the field in the form. More info in [https://docs.weblate.org/en/latest/ Weblate documentation]

Once the new project is created you need to upload the resources (the pot file to translate).
To create the pot files you can execute
make pot

inside the '''locale''' folder. Now you can load in the Resource section, after you added them you can link the pot file with an online version to get updates. To do this click on "'''Auto update resources'''" bottom (read also the [https://docs.weblate.org/en/latest/ Weblate documentation].

At this point you need to load the translated po files, for each language and file you have to upload the translation po file. Some errors could appear, resolution of this problems is a TODO

=== Get the translated po files ===

'''''NOTE: THIS IS FOR DEVELOPERS OR POWER USERS'''''

== Testing different languages in GRASS GIS ==

Testing different languages requires that the respective language environment and, if needed, fonts are installed.
Check what languages are currently installed on your system with:
locale -a

To change to a certain language environment (locale), do the following steps (here, example for Unix style environment):

1. Define/check language settings:
echo $LANG
echo $LANGUAGE
echo $LC_MESSAGES

2. Change it (example for to Japanese):
a) bash shell:
export LANG=ja_JP.UTF-8
export LANGUAGE=ja_JP.UTF-8
export LC_MESSAGES=ja_JP.UTF-8

b) (t)csh shell:
setenv LANG ja_JP.UTF-8
setenv LANGUAGE ja_JP.UTF-8
setenv LC_MESSAGES ja_JP.UTF-8

Now launch GRASS in this terminal. If you launch it from an icon, you have to change the LOCALE in the computer setup program instead.

Other common languages useful for testing are <tt>de_DE</tt> for German, <tt>fr_FR</tt> for French, or "C" for none (effectively <tt>en_US</tt>, which for GRASS is the base language).

=== Creating startup scripts for different languages ===

GRASS in English language, save as "grass78eng" (executable flag set, store in path):
#!/bin/sh
export LANG=en_US
export LANGUAGE=en_US
export LC_MESSAGES=en_US
exec grass78 "$@"

GRASS in Japanese language, save as "grass78ja" (executable flag set, store in path):
#!/bin/sh
export LANG=ja_JA.UTF-8
export LANGUAGE=ja_JA.UTF-8
export LC_MESSAGES=ja_JA.UTF-8
grass78 "$@"

== Coordination among translators ==

If several translators work on the same language files, obviously some coordination is needed. Please announce work via the "translations" mailing list at https://lists.osgeo.org/mailman/listinfo/grass-translations

Also the translation manager is listening there to the upload the changed files into the GRASS source code repository.

== Best practices ==

* Italiano: [https://tp.linux.it/buona_traduzione.html Regole per la buona traduzione]

== Installation of language packages ==

Example: Chinese

* Debian, Fedora, Ubuntu, ...: the locales should be already present
** list all valid locales on the system: localectl list-locales
** show current settings: localectl status
** set new locale: localectl set-locale LANG=zh_CN.utf8 LC_MESSAGES=zh_CN.utf8

== Reduction of similar messages ==

Please re-use existing messages:
* https://trac.osgeo.org/grass/wiki/MessageStandardization

== Updating messages in the source code ==

Generally, to support i18N multiple languages, message strings in GRASS must be modified by adding so-called [https://www.gnu.org/software/gettext/ gettext macros] <tt>'''_('''"..."''')'''</tt>.

=== C programming language ===

Change from
fprintf ( ..., "...\n", ...);
to either
fprintf ( ..., _("...\n"), ...);
or usually (while omitting \n)
G_message ( _("..."), ...);

=== Python programming language ===

In Python, the macro is used like this:
<source lang="python">
grass.message(_('Raster map <{name}> unpacked'.format(name=map_name)))
</source>

=== Important hints ===

Beware:
* G_message should be used for messages - information about the process for user while fprintf(stdout...) for data output.
* G_message output is not expected to be send to pipe or file.
* fprintf(stdout...) output is usually send to pipe or file.

Programming details are available in the file locale/[https://github.com/OSGeo/grass/blob/master/locale/README README].

Important:
* [https://trac.osgeo.org/grass/wiki/MessageStandardization Message Standardization]: How should Errors/Warnings/Messages be formatted, Macros etc

== See also ==

* Alpha-2 code of [http://www.loc.gov/standards/iso639-2/php/English_list.php ISO 639-1] (right column)

[[Category: Development]]
[[Category: Documentation]]
[[Category: FAQ]]
[[Category: Translation]]

GRASS messages translation

2025-06-20T15:15:54Z

Neteler: + Add translation badge to README files

== GRASS messages translation project ==

Many users prefer to use software in their mother tongue which is mostly not English. This requires that all GRASS software messages have to be translated to languages other than English. The GRASS Development Team is seeking translators. Please subscribe to the dedicated mailing list at

GRASS translations mailing list
http://lists.osgeo.org/mailman/listinfo/grass-translations

Translation related issues may be discussed there. This is an opportunity for non-programmers to contribute as messages can be easily translated. No programming skills required!

* Join the [[GRASS_Translation_Team#Members_of_Translation_Team|team]]

=== Wanted languages ===

Simple Chinese, Swahili, Hindi, Greek, Tamil, Russian, Telugu, Português, ... Please join us!

== Weblate translation platform ==

Weblate is a web-based translation tool with tight version control integration. It features a simple and clean user interface, propagation of translations across components, quality checks and automatic linking to source files.

(Note that we migrated from Transifex to [https://weblate.osgeo.org/projects/grass-gis/ Weblate] in 2023. All messages on Transifex have been transferred to Weblate.)

=== How to translate ===
'''''NOTE: THIS IS FOR TRANSLATOR'''''

* For terminology, please refer to the [[GRASS Translation Glossary]].

Register yourself on the [https://weblate.osgeo.org/projects/grass-gis/ Weblate website] using the [https://www.osgeo.org/community/getting-started-osgeo/osgeo_userid/ OSGeo-ID], and start to translate (grasswxpy is the GUI translation and it should be the first translated).

=== Using the machine translation tool ===

Using the machine translation tool: We have added the DeepL.com API which helps for selected languages to come to speed with translations.

Usage: login to Weblate. Then you see a button "Automatic suggestion". Use "Clone Translation" to copy over the suggested translation, edit as needed and save it.

[[File:Weblate with machine translation DeepL.png|thumb|800px|center|alt=Weblate with machine translation DeepL.com API|Weblate with machine translation DeepL.com API]]

=== Automated upload of your translation work to the GRASS GIS project in GitHub ===

Every 24 hours the new translations are automatically pushed to https://github.com/OSGeo/grass/pulls.
One of the maintainers will take care to merge them into the code so that it becomes part of the next release.

=== Files to be edited ===

==== GRASS GIS 8 translations ====
In GRASS GIS 8, we have only 3 types of .po files per language (the files are stored in the source code, in directory locale/po/):



<center>
[[Image:Weblate grassgis widget.png|center|link=https://weblate.osgeo.org/projects/grass-gis/]]
(click to see the GRASS GIS Weblate pages)
</center>

* <tt>grasslibs_LANG.po</tt>: messages from libraries
* <tt>grassmods_LANG.po</tt>: messages from commands ("modules")
* <tt>grasswxpy_LANG.po</tt>: messages from wxgrass/wxPython graphical user interface

where "LANG" in the above file names is a two character code which indicates the language. It is based on the Alpha-2 code of [http://www.loc.gov/standards/iso639-2/php/English_list.php ISO 639-1] (right column). Example: <tt>grasswxpy_pl.po</tt> for Polish.

'''We highly recommend to use our Weblate server: https://weblate.osgeo.org/projects/grass-gis/'''!

==== Add support for a new language ====

Go to any component, e.g. grasslibs - https://weblate.osgeo.org/projects/grass-gis/grasslibs/

Then click on the <code>+</code> button to add a language. You have to do it for each component.

==== Add Weblate generated translation badge to README files ====

We may consider to add a translation status badge, pointing to [https://weblate.osgeo.org/projects/grass-gis/ Weblate], to the server README.md on GitHub:

<syntaxhighlight lang="markdown">
[![Translation status](https://weblate.osgeo.org/widgets/grass-gis/-/svg-badge.svg)](https://weblate.osgeo.org/engage/grass-gis/?utm_source=widget)
</syntaxhighlight>

Yet a TODO.

=== Weblate: technical background on the installation ===

'''How it works:''' when a developer makes a GRASS GIS repo commit on GitHub, GitHub then calls the [https://github.com/OSGeo/grass/pull/3065#issuecomment-1716446226 webhook] on Weblate which triggers a refresh of Weblate's git fork of the GRASS GIS repo (check at https://github.com/osgeoweblate/grass/tree/weblate-grass-gis-grasslibs).

For pushing translations back to GitHub, there is a setting in Weblate for that which defaults to 24 hrs (accumulates translations over a day). Then a pull request with the translations will be opened in the GRASS GIS GitHub repo.

For technical background on the OSGeo Weblate installation, see https://wiki.osgeo.org/wiki/SAC:Weblate .

For GRASS GIS related Weblate troubleshooting, see the discussion in this OSGeo-SAC ticket: https://trac.osgeo.org/osgeo/ticket/2981

'''Weblate Troubleshooting:'''

In case the Weblate's git copy of the GRASS GIS repo does no longer update due to
a conflict or whatever reason:

Log into Weblate (requires administrator rights) and check on <https://weblate.osgeo.org/projects/grass-gis/#repository>
click on the "Manage" -> "Repository Maintenance". Therein choose "Update" button,
"Update with merge without fast-forward". If successful, this will create
another pull request in the GRASS GIS repo (trigger with "Push" button).

=== Continuing an existing translation ===

The file(s) are there but partially outdated? Read on.

First '''announce''' on the [http://lists.osgeo.org/mailman/listinfo/grass-translations GRASS translations mailing list] that you plan to continue the translation of a certain language. Why? Because sometimes people silently translate already and we need these efforts to be coordinated to avoid doing it twice...

Then get these four .po files for your language and start. If a file is missing, just ask on the list to get it generated or see next section. To get these .po files (the files are in the directory locale/po/):

* either [https://github.com/OSGeo/grass/tree/master/locale/po/ download current .po files] directly from SVN (click on file name to download),
* or [https://grass.osgeo.org/download/0 download source code package] from GitHub,
* or download the recent [https://grass.osgeo.org/grass78/source/snapshot/ source code snapshot],
* or ask on the [https://lists.osgeo.org/mailman/listinfo/grass-translations GRASS translations mailing list] for these files.

Then edit the files with a .po file editor (poEDIT or kbabel or..., see below). Take care to maintain layout and special characters. And '''submit often''' - if you wait for weeks, the messages may already be outdated and your time wasted. Just keep in touch on the [https://lists.osgeo.org/mailman/listinfo/grass-translations GRASS translations mailing list]!

=== Starting a new translation ===

The language you want isn't yet there? Read on.

Briefly, the steps to create new messages files are (if you find this too complicated, ask on the [https://lists.osgeo.org/mailman/listinfo/grass-translations GRASS translations mailing list] to get these files done for you!):

# Get the latest source code development version from either the SVN repository or as SVN snapshot (see [https://grass.osgeo.org/download/ Download]).
# run: './configure --with-nls [... other parameters]' to configure the GRASS source code
# run: 'cd locale' to change into the translation directory
# run: 'make pot' to create grass*.pot template files (to extract original messages)
# run: copy these file from templates/ into po/; rename them to contain the two characters language code (see Alpha-2 code of [http://www.loc.gov/standards/iso639-2/php/English_list.php ISO 639-1]) and to .po extension; update the file headers either manually or with your .po editing software
(Example: Polish language):
mv ./templates/grasslibs.pot ./po/grasslibs_pl.po
mv ./templates/grassmods.pot ./po/grassmods_pl.po
mv ./templates/grassnviz.pot ./po/grassnviz_pl.po
mv ./templates/grasstcl.pot ./po/grasstcl_pl.po
mv ./templates/grasswxpy.pot ./po/grasswxpy_pl.po

Now translate the messages in these po/*.po files (using poEDIT or other editor, see below)

From time to time messages need to be updated from the originals. This is usually done by the GRASS translation manager.

=== Create a new project ===

'''''NOTE: CORE DEVELOPERS ONLY!'''''

TODO 2023: improve this section!

A project should be done for each stable release, only an Organization Administrators can create a project. From the dashboard in the left bottom corner there is "'''New project'''" button. Fill all the field in the form. More info in [https://docs.weblate.org/en/latest/ Weblate documentation]

Once the new project is created you need to upload the resources (the pot file to translate).
To create the pot files you can execute
make pot

inside the '''locale''' folder. Now you can load in the Resource section, after you added them you can link the pot file with an online version to get updates. To do this click on "'''Auto update resources'''" bottom (read also the [https://docs.weblate.org/en/latest/ Weblate documentation].

At this point you need to load the translated po files, for each language and file you have to upload the translation po file. Some errors could appear, resolution of this problems is a TODO

=== Get the translated po files ===

'''''NOTE: THIS IS FOR DEVELOPERS OR POWER USERS'''''

== Testing different languages in GRASS GIS ==

Testing different languages requires that the respective language environment and, if needed, fonts are installed.
Check what languages are currently installed on your system with:
locale -a

To change to a certain language environment (locale), do the following steps (here, example for Unix style environment):

1. Define/check language settings:
echo $LANG
echo $LANGUAGE
echo $LC_MESSAGES

2. Change it (example for to Japanese):
a) bash shell:
export LANG=ja_JP.UTF-8
export LANGUAGE=ja_JP.UTF-8
export LC_MESSAGES=ja_JP.UTF-8

b) (t)csh shell:
setenv LANG ja_JP.UTF-8
setenv LANGUAGE ja_JP.UTF-8
setenv LC_MESSAGES ja_JP.UTF-8

Now launch GRASS in this terminal. If you launch it from an icon, you have to change the LOCALE in the computer setup program instead.

Other common languages useful for testing are <tt>de_DE</tt> for German, <tt>fr_FR</tt> for French, or "C" for none (effectively <tt>en_US</tt>, which for GRASS is the base language).

=== Creating startup scripts for different languages ===

GRASS in English language, save as "grass78eng" (executable flag set, store in path):
#!/bin/sh
export LANG=en_US
export LANGUAGE=en_US
export LC_MESSAGES=en_US
exec grass78 "$@"

GRASS in Japanese language, save as "grass78ja" (executable flag set, store in path):
#!/bin/sh
export LANG=ja_JA.UTF-8
export LANGUAGE=ja_JA.UTF-8
export LC_MESSAGES=ja_JA.UTF-8
grass78 "$@"

== Coordination among translators ==

If several translators work on the same language files, obviously some coordination is needed. Please announce work via the "translations" mailing list at https://lists.osgeo.org/mailman/listinfo/grass-translations

Also the translation manager is listening there to the upload the changed files into the GRASS source code repository.

== Best practices ==

* Italiano: [https://tp.linux.it/buona_traduzione.html Regole per la buona traduzione]

== Installation of language packages ==

Example: Chinese

* Debian, Fedora, Ubuntu, ...: the locales should be already present
** list all valid locales on the system: localectl list-locales
** show current settings: localectl status
** set new locale: localectl set-locale LANG=zh_CN.utf8 LC_MESSAGES=zh_CN.utf8

== Reduction of similar messages ==

Please re-use existing messages:
* https://trac.osgeo.org/grass/wiki/MessageStandardization

== Updating messages in the source code ==

Generally, to support i18N multiple languages, message strings in GRASS must be modified by adding so-called [https://www.gnu.org/software/gettext/ gettext macros] <tt>'''_('''"..."''')'''</tt>.

=== C programming language ===

Change from
fprintf ( ..., "...\n", ...);
to either
fprintf ( ..., _("...\n"), ...);
or usually (while omitting \n)
G_message ( _("..."), ...);

=== Python programming language ===

In Python, the macro is used like this:
<source lang="python">
grass.message(_('Raster map <{name}> unpacked'.format(name=map_name)))
</source>

=== Important hints ===

Beware:
* G_message should be used for messages - information about the process for user while fprintf(stdout...) for data output.
* G_message output is not expected to be send to pipe or file.
* fprintf(stdout...) output is usually send to pipe or file.

Programming details are available in the file locale/[https://github.com/OSGeo/grass/blob/master/locale/README README].

Important:
* [https://trac.osgeo.org/grass/wiki/MessageStandardization Message Standardization]: How should Errors/Warnings/Messages be formatted, Macros etc

== See also ==

* Alpha-2 code of [http://www.loc.gov/standards/iso639-2/php/English_list.php ISO 639-1] (right column)

[[Category: Development]]
[[Category: Documentation]]
[[Category: FAQ]]
[[Category: Translation]]

PSC Meeting 2025-05-09

2025-06-17T16:57:35Z

Neteler: added :Category:PSC

== Participants ==

* Anna Petrasova
* Helmut Kudrnovsky
* Huidae Cho
* Linda Karlovska
* Markus Neteler
* Paulo van Breugel
* Vaclav Petras
* Veronica Andreo

== Agenda ==

The topics proposed are:

* Hosting of GRASS server at OSL, Oregon State University. See: https://osuosl.org/blog/osl-future/.
* Financial Sponsoring via NumFocus. Status update.
* Conda update
* [[GRASS Developer Summit Raleigh 2025]], NC.
** Remote participation?
** Schedule
* Status of new docs: https://grass.osgeo.org/grass-devel/manuals/
* Status of doc and macOS uploads.
* Status of new branding.
** The main logo on wiki needs server-side update. Current file is https://grasswiki.osgeo.org/w/skins/common/images/grasslogo_wiki.png?3fa1b. (Also, this goes to mapping relation with OSGeo SAC.)
*** 7th May 2025: markusN has updated the logo on the wiki
* Wiki status
** The Main Page needs a major update and, more importantly, a ''complete change of approach''
** Ohloh_Project Widget is broken: [[Widget:Ohloh_Project]] used in [[Software requirements specification]]
*** 7th May 2025: markusN has been updated from https://www.mediawiki.org/wiki/Extension:Widgets, error messages here disappeared but the widget is not rendered yet. More time to be spent.
*** VP: Consider if we actually want Widget:Ohloh_Project or Widgets.
** There is no favicon.
*** 7th May 2025: markusN has added the favicon on the wiki
* Website
** we have [https://github.com/OSGeo/grass-website/issues/513 notable SEO issues] on the website which penalize our search engine ranking.
* GSoC.
* Shall we consider applying to Outreachy, too? See: https://lists.osgeo.org/pipermail/qgis-psc/2025-March/010525.html.

== Minutes ==

* From previous meeting:
** mailman migration to discourse:
*** The '''grass-user mailing list''' has been migrated to Discourse.
*** We will close the '''grass-web mailing list''' that receives spam mostly. Markus will put it into read-only mode, after an announcement to the list.
*** Anna will remove grass-web references from the website
*** We should add a “Contact us” something to the website → improve website footer
*** We decided to change the '''grass-stats mailing list''' and '''grass-translation mailing list''' mailing lists to read-only mode to reduce channel confusion. Markus will do this as he has permission, after an announcement has been sent to the list explaining the alternative(s).
*** For now, we keep the '''grass-psc mailing list''' list on mailman, but we are considering merging it to GRASS developer in Discourse, as subscribers are pretty much the same (that is, close down the mailing list). We also keep grass-announce on mailman.
** tutorials contributing guide: a [https://github.com/OSGeo/grass-tutorials/pull/16 PR] is there, but it seems useless. Vero volunteers to work on it; we are still trying to figure out the workflow (i.e., what to commit and so on).

* Hosting of GRASS server at [https://wiki.osgeo.org/wiki/OSL OSL - Oregon University] using OSGeo infrastructure hosted there.
** OSL funding is at risk. We have no action item as OSGeo will handle this, but we will keep an eye on it in case we need to take action.
** News: Seems the next year is again funded ([https://osuosl.org/blog/osl-future-update/ OSL blog]).

* NumFOCUS status update: The main reason to go with them is that they provide invoices when someone donates to the project, while OSGeo is not willing/legally able to do so, and we are missing some funding/sponsoring opportunities because of that. Also, NumFOCUS brings new funding options.
** Contract draft: edits concerning the PSC description were included.
** OSGeo cannot remain our fiscal host; it will become NumFOCUS; but we can still use the OSGeo money via reimbursements as usual.
** Once the agreement is signed, we’ll meet with their Finance department and go through NumFOCUS onboarding.

* Conda
** Huidae built a Linux conda package, but without FHS (Filesystem Hierarchy Standard)
** The Windows conda package is not stable, probably a CMake issue
** There are 2 open issues: conda for Linux and Windows, CMake for Windows
** HC will resume work on it next week
** Instructions to test: https://github.com/OSGeo/grass/issues/5067

* GRASS Developer Summit at Raleigh ([https://grasswiki.osgeo.org/wiki/Talk:GRASS_Developer_Summit_Raleigh_2025 agenda schedule])
** Remote participation? We decided async work is better according to previous years experiences, but we could define a time slot for a call with folks contributing remotely.
** There will be a PSC meeting during the summit: Friday 23, 5pm CET, 11am ET. Calendar invite sent.

* New docs:
** They are up and looking great: https://grass.osgeo.org/grass-devel/manuals/
** Automatic upload from CI to the web server is WIP, needs GHA.
** Only some Python examples do not work, but that should be solvable.
** Corey is working on syncing branding among the website, docs, and tutorials

* JSON: theoretically we want 3 types: <code>format=json</code> (WIP), <code>--json</code> (implemented), <code>--json-interface-description</code> (not yet implemented)

* Releases:
** 8.4.2 in [https://github.com/OSGeo/grass/milestone/27 some weeks]

* New branding:
** Wiki:
*** logo and favicon were updated by MN
*** svg file in the corner? To be checked by MN -> done
*** review the Wiki landing page and redo it
**** highlight PSC and Events categories because that’s the current usage, and remove other links that are already on the website
*** Ohloh/OpenHub Project Widget is broken: let’s remove it -> done
*** Ideas on what to do with all the content we have on the media wiki:
**** obsolete everything and then select what to keep,
**** go topic by topic
**** obsolete everything that was not edited in the last 3 years, maybe with a bot extension?
**** To be discussed further

* Website SEO issues:
** Our search engine ranking is partially penalized at time. See: https://github.com/OSGeo/grass-website/issues/513
** TODO: a volunteer to fix the issues noted in the ticket

* Website analytics:
** There's the [https://2022.foss4g.org/matomo/ GFOSS.it Matomo] instance, but we do not have much control over it, only MN has a user account, via Luca D.
** OSGeo-SAC related [https://trac.osgeo.org/osgeo/ticket/2830 ticket] to install Matomo. Anna will revive it and Vashek will ask Howard.
** Corey offered to sponsor it as OpenPlains
** The paid option is around USD 500 yearly

* GSoC:
** We got only one student this year, he'll work on the JSON project.

[[Category:PSC]]

GRASS messages translation

2025-06-03T16:02:34Z

Neteler: /* Files to be edited */ Add support for a new language

== GRASS messages translation project ==

Many users prefer to use software in their mother tongue which is mostly not English. This requires that all GRASS software messages have to be translated to languages other than English. The GRASS Development Team is seeking translators. Please subscribe to the dedicated mailing list at

GRASS translations mailing list
http://lists.osgeo.org/mailman/listinfo/grass-translations

Translation related issues may be discussed there. This is an opportunity for non-programmers to contribute as messages can be easily translated. No programming skills required!

* Join the [[GRASS_Translation_Team#Members_of_Translation_Team|team]]

=== Wanted languages ===

Simple Chinese, Swahili, Hindi, Greek, Tamil, Russian, Telugu, Português, ... Please join us!

== Weblate translation platform ==

Weblate is a web-based translation tool with tight version control integration. It features a simple and clean user interface, propagation of translations across components, quality checks and automatic linking to source files.

(Note that we migrated from Transifex to [https://weblate.osgeo.org/projects/grass-gis/ Weblate] in 2023. All messages on Transifex have been transferred to Weblate.)

=== How to translate ===
'''''NOTE: THIS IS FOR TRANSLATOR'''''

* For terminology, please refer to the [[GRASS Translation Glossary]].

Register yourself on the [https://weblate.osgeo.org/projects/grass-gis/ Weblate website] using the [https://www.osgeo.org/community/getting-started-osgeo/osgeo_userid/ OSGeo-ID], and start to translate (grasswxpy is the GUI translation and it should be the first translated).

=== Using the machine translation tool ===

Using the machine translation tool: We have added the DeepL.com API which helps for selected languages to come to speed with translations.

Usage: login to Weblate. Then you see a button "Automatic suggestion". Use "Clone Translation" to copy over the suggested translation, edit as needed and save it.

[[File:Weblate with machine translation DeepL.png|thumb|800px|center|alt=Weblate with machine translation DeepL.com API|Weblate with machine translation DeepL.com API]]

=== Automated upload of your translation work to the GRASS GIS project in GitHub ===

Every 24 hours the new translations are automatically pushed to https://github.com/OSGeo/grass/pulls.
One of the maintainers will take care to merge them into the code so that it becomes part of the next release.

=== Files to be edited ===

==== GRASS GIS 8 translations ====
In GRASS GIS 8, we have only 3 types of .po files per language (the files are stored in the source code, in directory locale/po/):



<center>
[[Image:Weblate grassgis widget.png|center|link=https://weblate.osgeo.org/projects/grass-gis/]]
(click to see the GRASS GIS Weblate pages)
</center>

* <tt>grasslibs_LANG.po</tt>: messages from libraries
* <tt>grassmods_LANG.po</tt>: messages from commands ("modules")
* <tt>grasswxpy_LANG.po</tt>: messages from wxgrass/wxPython graphical user interface

where "LANG" in the above file names is a two character code which indicates the language. It is based on the Alpha-2 code of [http://www.loc.gov/standards/iso639-2/php/English_list.php ISO 639-1] (right column). Example: <tt>grasswxpy_pl.po</tt> for Polish.

'''We highly recommend to use our Weblate server: https://weblate.osgeo.org/projects/grass-gis/'''!

==== Add support for a new language ====

Go to any component, e.g. grasslibs - https://weblate.osgeo.org/projects/grass-gis/grasslibs/

Then click on the <code>+</code> button to add a language. You have to do it for each component.

=== Weblate: technical background on the installation ===

'''How it works:''' when a developer makes a GRASS GIS repo commit on GitHub, GitHub then calls the [https://github.com/OSGeo/grass/pull/3065#issuecomment-1716446226 webhook] on Weblate which triggers a refresh of Weblate's git fork of the GRASS GIS repo (check at https://github.com/osgeoweblate/grass/tree/weblate-grass-gis-grasslibs).

For pushing translations back to GitHub, there is a setting in Weblate for that which defaults to 24 hrs (accumulates translations over a day). Then a pull request with the translations will be opened in the GRASS GIS GitHub repo.

For technical background on the OSGeo Weblate installation, see https://wiki.osgeo.org/wiki/SAC:Weblate .

For GRASS GIS related Weblate troubleshooting, see the discussion in this OSGeo-SAC ticket: https://trac.osgeo.org/osgeo/ticket/2981

'''Weblate Troubleshooting:'''

In case the Weblate's git copy of the GRASS GIS repo does no longer update due to
a conflict or whatever reason:

Log into Weblate (requires administrator rights) and check on <https://weblate.osgeo.org/projects/grass-gis/#repository>
click on the "Manage" -> "Repository Maintenance". Therein choose "Update" button,
"Update with merge without fast-forward". If successful, this will create
another pull request in the GRASS GIS repo (trigger with "Push" button).

=== Continuing an existing translation ===

The file(s) are there but partially outdated? Read on.

First '''announce''' on the [http://lists.osgeo.org/mailman/listinfo/grass-translations GRASS translations mailing list] that you plan to continue the translation of a certain language. Why? Because sometimes people silently translate already and we need these efforts to be coordinated to avoid doing it twice...

Then get these four .po files for your language and start. If a file is missing, just ask on the list to get it generated or see next section. To get these .po files (the files are in the directory locale/po/):

* either [https://github.com/OSGeo/grass/tree/master/locale/po/ download current .po files] directly from SVN (click on file name to download),
* or [https://grass.osgeo.org/download/0 download source code package] from GitHub,
* or download the recent [https://grass.osgeo.org/grass78/source/snapshot/ source code snapshot],
* or ask on the [https://lists.osgeo.org/mailman/listinfo/grass-translations GRASS translations mailing list] for these files.

Then edit the files with a .po file editor (poEDIT or kbabel or..., see below). Take care to maintain layout and special characters. And '''submit often''' - if you wait for weeks, the messages may already be outdated and your time wasted. Just keep in touch on the [https://lists.osgeo.org/mailman/listinfo/grass-translations GRASS translations mailing list]!

=== Starting a new translation ===

The language you want isn't yet there? Read on.

Briefly, the steps to create new messages files are (if you find this too complicated, ask on the [https://lists.osgeo.org/mailman/listinfo/grass-translations GRASS translations mailing list] to get these files done for you!):

# Get the latest source code development version from either the SVN repository or as SVN snapshot (see [https://grass.osgeo.org/download/ Download]).
# run: './configure --with-nls [... other parameters]' to configure the GRASS source code
# run: 'cd locale' to change into the translation directory
# run: 'make pot' to create grass*.pot template files (to extract original messages)
# run: copy these file from templates/ into po/; rename them to contain the two characters language code (see Alpha-2 code of [http://www.loc.gov/standards/iso639-2/php/English_list.php ISO 639-1]) and to .po extension; update the file headers either manually or with your .po editing software
(Example: Polish language):
mv ./templates/grasslibs.pot ./po/grasslibs_pl.po
mv ./templates/grassmods.pot ./po/grassmods_pl.po
mv ./templates/grassnviz.pot ./po/grassnviz_pl.po
mv ./templates/grasstcl.pot ./po/grasstcl_pl.po
mv ./templates/grasswxpy.pot ./po/grasswxpy_pl.po

Now translate the messages in these po/*.po files (using poEDIT or other editor, see below)

From time to time messages need to be updated from the originals. This is usually done by the GRASS translation manager.

=== Create a new project ===

'''''NOTE: CORE DEVELOPERS ONLY!'''''

TODO 2023: improve this section!

A project should be done for each stable release, only an Organization Administrators can create a project. From the dashboard in the left bottom corner there is "'''New project'''" button. Fill all the field in the form. More info in [https://docs.weblate.org/en/latest/ Weblate documentation]

Once the new project is created you need to upload the resources (the pot file to translate).
To create the pot files you can execute
make pot

inside the '''locale''' folder. Now you can load in the Resource section, after you added them you can link the pot file with an online version to get updates. To do this click on "'''Auto update resources'''" bottom (read also the [https://docs.weblate.org/en/latest/ Weblate documentation].

At this point you need to load the translated po files, for each language and file you have to upload the translation po file. Some errors could appear, resolution of this problems is a TODO

=== Get the translated po files ===

'''''NOTE: THIS IS FOR DEVELOPERS OR POWER USERS'''''

== Testing different languages in GRASS GIS ==

Testing different languages requires that the respective language environment and, if needed, fonts are installed.
Check what languages are currently installed on your system with:
locale -a

To change to a certain language environment (locale), do the following steps (here, example for Unix style environment):

1. Define/check language settings:
echo $LANG
echo $LANGUAGE
echo $LC_MESSAGES

2. Change it (example for to Japanese):
a) bash shell:
export LANG=ja_JP.UTF-8
export LANGUAGE=ja_JP.UTF-8
export LC_MESSAGES=ja_JP.UTF-8

b) (t)csh shell:
setenv LANG ja_JP.UTF-8
setenv LANGUAGE ja_JP.UTF-8
setenv LC_MESSAGES ja_JP.UTF-8

Now launch GRASS in this terminal. If you launch it from an icon, you have to change the LOCALE in the computer setup program instead.

Other common languages useful for testing are <tt>de_DE</tt> for German, <tt>fr_FR</tt> for French, or "C" for none (effectively <tt>en_US</tt>, which for GRASS is the base language).

=== Creating startup scripts for different languages ===

GRASS in English language, save as "grass78eng" (executable flag set, store in path):
#!/bin/sh
export LANG=en_US
export LANGUAGE=en_US
export LC_MESSAGES=en_US
exec grass78 "$@"

GRASS in Japanese language, save as "grass78ja" (executable flag set, store in path):
#!/bin/sh
export LANG=ja_JA.UTF-8
export LANGUAGE=ja_JA.UTF-8
export LC_MESSAGES=ja_JA.UTF-8
grass78 "$@"

== Coordination among translators ==

If several translators work on the same language files, obviously some coordination is needed. Please announce work via the "translations" mailing list at https://lists.osgeo.org/mailman/listinfo/grass-translations

Also the translation manager is listening there to the upload the changed files into the GRASS source code repository.

== Best practices ==

* Italiano: [https://tp.linux.it/buona_traduzione.html Regole per la buona traduzione]

== Installation of language packages ==

Example: Chinese

* Debian, Fedora, Ubuntu, ...: the locales should be already present
** list all valid locales on the system: localectl list-locales
** show current settings: localectl status
** set new locale: localectl set-locale LANG=zh_CN.utf8 LC_MESSAGES=zh_CN.utf8

== Reduction of similar messages ==

Please re-use existing messages:
* https://trac.osgeo.org/grass/wiki/MessageStandardization

== Updating messages in the source code ==

Generally, to support i18N multiple languages, message strings in GRASS must be modified by adding so-called [https://www.gnu.org/software/gettext/ gettext macros] <tt>'''_('''"..."''')'''</tt>.

=== C programming language ===

Change from
fprintf ( ..., "...\n", ...);
to either
fprintf ( ..., _("...\n"), ...);
or usually (while omitting \n)
G_message ( _("..."), ...);

=== Python programming language ===

In Python, the macro is used like this:
<source lang="python">
grass.message(_('Raster map <{name}> unpacked'.format(name=map_name)))
</source>

=== Important hints ===

Beware:
* G_message should be used for messages - information about the process for user while fprintf(stdout...) for data output.
* G_message output is not expected to be send to pipe or file.
* fprintf(stdout...) output is usually send to pipe or file.

Programming details are available in the file locale/[https://github.com/OSGeo/grass/blob/master/locale/README README].

Important:
* [https://trac.osgeo.org/grass/wiki/MessageStandardization Message Standardization]: How should Errors/Warnings/Messages be formatted, Macros etc

== See also ==

* Alpha-2 code of [http://www.loc.gov/standards/iso639-2/php/English_list.php ISO 639-1] (right column)

[[Category: Development]]
[[Category: Documentation]]
[[Category: FAQ]]
[[Category: Translation]]

Talk:GRASS Developer Summit Raleigh 2025

2025-05-28T13:13:17Z

Neteler: /* Markus Neteler | mundialis */

{{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 || GRASS roadmap and future (Vaclav Petras)
|-
| 11:20-11:40 || Self-organized feedback sessions || GRASS tools: core and additional functionality (MartinL)
|-
| 11:40-12:00 || Self-organized feedback sessions || Jupyter integration into GUI (Linda Karlovska)
|-
| 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-26 GitHub contributions]
* Enhanced the GRASS website footer.
* Sync icons on the Tutorials website footer to those on the main website.
* Fixed description tags and their display on the tutorials website.
* Fixed typos in Get Started tutorials.
* Fixed GRASS page on OSGeo website [https://www.osgeo.org/projects/grass-gis/]
** Changed logo, removed GIS from the name, fixed old links.
* Posted on social media.
* Discussion about hyperspectral with Alen and Anna.
* Expanded the GRASS acronym on the home page.
* Removed GIS from GRASS name on the website.
* Reviewed tutorials by Huidae, Michael Barton and Adam Smith.
* Added external tutorials by Huidae and the one from FOSS4G 2024.
* Enhanced and added 7 time series tutorials that were on hold from 2024.
* Added lightbox class in get-started tutorials and others so images can be clicked on.
* GRASS PSC admin stuff.
* Participated of the PSC meeting.
* Talked 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 on Thu: 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.

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

=== 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])
* g.proj: upgrade to format=proj4 style text output ([https://github.com/OSGeo/grass/pull/5722 PR])
* g.proj: upgrade to format=wkt style text output ([https://github.com/OSGeo/grass/pull/5727 PR])
* g.proj: upgrade to format=shellstyle text output ([https://github.com/OSGeo/grass/pull/5728 PR])

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

On Friday I presented the Jupyter Notebook integration options and led the discussion on how to address it in GRASS (the level of integration, own kernel or not etc.)

=== 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
* Presentation 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
* i.hyper.import module: added option to generate RGB, CIR, SWIR or custom composite during import
* i.hyper.preproc module: implementing Savitzky-Golay filter with options for polynomial order, derivative order and window width
Thursday May 22 - 24
* i.hyper.import module: adding options for handling invalid bands, null values and clamping negative values
* i.hyper.export module: exporting hyperspectral 3D rasters as stacked GeoTiff
* commition to personal, public repo
* drafting future plans:
** i.hyper.preproc PCA, KPCA, continuum removal an wavelet transformation
** i.hyper.import PRISMA and Hyperion support
** i.hyper.export: HDF5, Zarr and IMG spport
** i.hyper.explore: new submodule for spectra visualization
* Submission of the details of the "State of GRASS" talk for FOSS4GE 2025.

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

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

[https://github.com/marisn?tab=overview&from=2025-05-19&to=2025-05-24 GitHub activity]
* 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
* Fixed initialization of private variables in OpenMP threads in r.univar
* 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 multiple 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 (without project)
* Feedback session different Python APIs to access tools
* Feedback session on roadmap and future of GRASS
* Discussed pygrass access to tools with Martin Landa and Ondřej Pešek (e.g. <code>raster = Tools(group="raster"); raster.slope_aspect(...)</code>)
* Discussed LLMs with Neel Ghoshal, Riya, Pratikshya Regmi
* Discussed session setup 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
* Discussed parallelization with Māris Nartišs, Chung-Yuan Liang, Anna Petrasova
* 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 NumPy and xarray integrations with Laurent Courty
* Discussed r.horizon parallelization with Chung-Yuan Liang and Anna Petrasova
* Discussed Jupyter integration into GUI with Linda Karlovska
* Answered user, coding, and setup questions for Neel Ghoshal, Abdullah Azzam, Gregory Power, and Alen Mangafić
* Participated in the hybrid PSC meeting (presented differences between OSGeo project and NumFOCUS project)
* Drafted modifications of subprocess calling for tools in Python API
* Prototype for running tools from Python with NumPy arrays

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

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

=== Andy Kiley | NC DEQ ===

* Hydrology day guest discussing stream mapping

=== Nick Brady | Natrx ===

* Lightning talk speaker presenting usage of GRASS in distributed environment for coastal erosion assessments

GRASS-Wiki

2025-05-21T13:33:14Z

Neteler: /* Relevant Categories */

__NOTOC__

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

= Welcome to the GRASS Wiki =

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

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

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

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

== Governance ==

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

== Latest Events & Planning ==

* [[GRASS_Developer_Summit_Raleigh_2025|GRASS Developer Summit in Raleigh 2025]]
* [[GRASS_GSoC_Ideas_2025|Google Summer of Code 2025]]

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

Talk:GRASS Developer Summit Raleigh 2025

2025-05-19T13:59:16Z

Neteler: /* Markus Neteler | mundialis */ +github

Main Page color test

2025-05-16T07:49:35Z

Neteler:

== Testing colors for use in GRASS-Wiki ==

background color test page:
or/yelw: 239:223:164 #EFDFA4
liyel: 240:232:196 #F0E8C4
green: 206:218:151 #CEDA97
pukgrn: 226:234:183 #E2EAB7
aqblue: 214:228:214 #D6E4D6
prpblu: 214:213:217 #D6D5D9
greyblu: 218:218:219 #DADADB
grblu2: 224:233:221 #E0E9DD
ligrey: 220:220:220 #DCDCDC

old liblue: #f8f8ff

== Main ==

__NOTOC__
{| width="100%"
|-
| width="68%" style="vertical-align:top" |
<div style="margin:0; margin-right:10px; border:1px solid #dfdfdf; background-color:#D6D5D9;">

<div style="padding:0.3em 1em 0.7em 1em;">

[[Image:grasslogo_vector_small.png|right]]

=== Welcome to the GRASS GIS Users Wiki ===

The [http://grass.osgeo.org Geographic Resources Analysis Support System], commonly referred to as '''GRASS''', is a Geographic Information System ([http://en.wikipedia.org/wiki/Geographic_information_system GIS]) used for geospatial data management and analysis, image processing, graphics/maps production, spatial modeling, and visualization. GRASS is currently used in academic and commercial settings around the world, as well as by many governmental agencies and environmental consulting companies. GRASS GIS is an [http://www.osgeo.org Open Source Geospatial Foundation] project. This WIKI offers the official user community platform of the GRASS GIS project. For analysis examples, see the [http://grass.osgeo.org/screenshots/index.php GRASS GIS Gallery].

On this Wiki, you can get and contribute to GRASS related information, documents and add-ons programs. To edit here, you need to register and login first (see top right link).
</div>
</div>

<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#FFF5E5;">

'''What's hot: [[GRASS SoC Ideas 2009]]'''
</div>

<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#DADADB;">

==== User Documentation and Support ====
* [[GRASS Help|GRASS Help and Getting Started]]
* [[GRASS Documents|In depth GRASS Documentation]]
* [[Installation Guide]] for precompiled binaries
* [[Faq|FAQ]]
* [[wxGUI]] - Graphical User Interface based on wxPython
</div>

<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#E0E9DD;">

==== Community ====
* [[GRASS Community]]: Getting in touch
* [[Applications|Research applications]]: What people are doing with GRASS
* [[GRASS migration hints|Migrating to GRASS]]
* [[GRASS Blogger]]
* Get involved: [[Project jobs]]
* [http://grass.osgeo.org/wiki/Special:Recentchanges?feed=rss RSS feed] of recent changes of this Wiki
</div>

<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#EFDFA4;">
or/yelw: 239:223:164 #EFDFA4
</div>

<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#F0E8C4;">
liyel: 240:232:196 #F0E8C4
</div>

<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#CEDA97;">
green: 206:218:151 #CEDA97
</div>

<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#E2EAB7;">
pukgrn: 226:234:183 #E2EAB7
</div>

<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#D6D5D9;">
prpblu: 214:213:217 #D6D5D9
</div>

<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#DADADB;">
greyblu: 218:218:219 #DADADB
</div>

<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#D6E4D6;">
aqblue: 214:228:214 #D6E4D6
</div>

<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#E0E9DD;">
grblu2: 224:233:221 #E0E9DD
</div>

<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#f8f8ff;">
old liblue: #f8f8ff
</div>

<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#dcdcdc;">
ligrey: #dcdcdc
</div>

<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #4da948; padding:0em 1em 1em 1em; background-color:#dcdcdc;">
ligrey: #dcdcdc (border #4da948)
</div>

<div>Have a look at the GRASS GIS users worldwide [http://grass.osgeo.org/community/ GRASS GIS User Online]. If you operate a GRASS GIS installation, you are welcome to enter your user data there.
</div>

<div><p>''[[GRASS-Wiki:Language policy|Translate this Wiki]]''</p></div>


| width="38%" style="vertical-align:top" |
<div style="margin:0; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#f8f8ff;">
[[Image:OSGeo 220pix.png|center|220px]]
<center>OSGeo Foundation Project</center>
</div>

<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#EFDFA4;">
* [http://grass.osgeo.org/screenshots/index.php GRASS GIS Gallery]
* [http://trac.osgeo.org SVN/trac] Source Code Repository
* [http://grass.osgeo.org/community/support.php Mailing lists] and [http://grass.osgeo.org/community/support.php#irc IRC]
* [http://trac.osgeo.org/grass/ Report errors]
* [https://svn.osgeo.org/grass/grass/branches/releasebranch_6_3/COPYING Licensed under GNU GPL]
</div>

<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#CEDA97;">

==== Download ====
* [http://grass.osgeo.org/download/ Source code and binaries]
* '''[[GRASS AddOns]]'''
* [[Promotional material]]
* [[Sample datasets]]
* [[Global datasets]]
</div>

<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#F0E8C4;">

==== Development ====
* [http://trac.osgeo.org/grass/wiki GRASS-trac]: the development Wiki, bugtracker, source code browser
* [[Development|GRASS Development]] intro
* [[Release Roadmap]]
* [[GRASS 7 ideas collection]]
* [[GRASS SoC Ideas|Google Summer of Code ideas collection]]
* [[Compile and Install]] of Source Code
* [http://trac.osgeo.org/grass/wiki/HowToContribute How to contribute to GRASS development] (getting write access and such)
</div>

<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#E2EAB7;">
Project Metrics provided by [http://www.ohloh.net/projects/3666 Ohloh].
{{#ohloh: account=3666}}
</div>
|}

==== See also ====

The official GRASS-GIS colors described in the [http://grasswiki.osgeo.org/wiki/GRASS_Logo GRASS Logo] page

[[Category: Colors]]

Main Page color test

2025-05-16T07:49:04Z

Neteler: /* See also */

Raspberry Pi

2025-05-16T07:47:21Z

Neteler: /* See also */

[[Image:Grass7 RaspberryPI.png|500px|right|thumb|GRASS running in the LXDE desktop environment on a Raspberry Pi]]

__TOC__

= GRASS on the Raspberry Pi =

The {{wikipedia|Raspberry_Pi}} is a small computer about the size of a deck of cards. It runs on a low power ARM processor similar to one used in a smart phone or tablet. Technically it's a ARM v6 SoC chip originally designed for use in a set-top TV box, meaning the general purpose CPU is rather slow, but it can handle full screen 1080p graphics without problems. It is designed for tinkering and is very cheap: US$25-35 depending on the model.

The Pi runs Linux and a popular distribution for it is [http://www.raspbian.org/ Raspian], an ARM v6 rebuild of {{wikipedia|Debian}}'s "testing" line, which supplies builds for ARM v4 and ARM v7 but not the v6. Running the official Debian build for v4 will work, but not take full advantage of the chip.

== Installing ==

Since GRASS is a standard package in Debian, installation on a running Pi system is very easy. At a terminal prompt type:
sudo apt-get install grass grass-doc grass-dev

This will also bring in all of the user documentation and the development environment needed to install GRASS [[AddOns]].

GRASS will work fine on very slow hardware with limited RAM, especially for raster maps. It was after all originally designed in the 1980s when computers were much less capable than they are today. To keep RAM use low keep your region rows x columns small, and vector features to a minimum. Typical use with the older (and smaller) [[Sample_datasets|Spearfish dataset]] should work very smoothly. The GUI can be computationally expensive, so you might consider changing the default GUI to the more lightweight Tcl/Tk version(s), or setting the default to text mode with the {{Cmd|g.gui}} module. For example:
<font color="DarkBlue">GRASS></font> g.gui text
<text> is now the default GUI

== Compiling ==

If you are interested in working on GRASS development or trying out experimental features in GRASS 7, Yann Chemin has [http://article.gmane.org/gmane.comp.gis.grass.devel/52126 put together some instructions on how to compile GRASS 7 on the RPi]. This was done on an older Model B unit with 256MB RAM; newer revisions of the board come with 512MB RAM.

If you simply want to compile and build your own [[AddOns|add-on modules]] for GRASS 6.4, all you need to do is install the <tt>grass-dev</tt> package and you're ready to go; you don't need the full GRASS source code for that. (although it is useful for reference)

How-to download, configure, compile, and install GRASS 7.svn on the RPi:

* Use [http://www.raspbian.org/ Raspbian] as your SD card image
* Start the Raspberry Pi with that SD card
* You will be presented with a text-based start menu:
:- Extend the File system to the fill the SD card
:- Overclock to 900MHz (needs 1V power more) or more (1GHz possible)
:- Set up ssh server if you want to connect remotely
:- Go ahead to load the Debian LXDE interface

* Once you are through all that and it has booted to the {{wikipedia|LXDE}} desktop, open a terminal, and enter these commands to update your Raspian OS and install the standard GRASS 6.4 packages with all required dependencies:
sudo apt-get update
sudo apt-get dist-upgrade --assume-yes
sudo apt-get install grass-dev

Next fetch the latest GRASS development source code:
sudo apt-get install subversion
svn checkout <nowiki>https://svn.osgeo.org/grass/grass/trunk</nowiki> grass7_trunk

* cd into <tt>grass7_trunk</tt>

* Download and install the required build dependencies (like libcairo-dev for wxgui, etc). If you have the deb-src lines active in your /etc/apt/sources.list file, this is easily done with a single command:
sudo apt-get build-dep grass

* Lower the job priority of the build Terminal session so that the rest of the RPi will still be usable during the build:
renice +17 -p $$

* Get your config options right, here's a working example but you should adjust to suit your needs:
CFLAGS="-ggdb -march=native -Wall -Werror-implicit-function-declaration" \
./configure \
--with-tcltk-includes=/usr/include/tcl8.5 --with-cairo \
--with-motif --with-python=/usr/bin/python2.7-config \
--with-readline --with-cxx --with-odbc --with-sqlite \
--with-freetype --with-freetype-includes=/usr/include/freetype2 \
--without-postgres --with-proj-share=/usr/share/proj \
--with-wxwidgets=/usr/lib/wx/config/gtk2-unicode-release-2.8 \
--with-geos \
2>&1 | tee config_log.txt

: For help with the configure options run this command:
./configure --help | less

If you are building without GUI support (text only mode) you can leave off Motif, Tcl/Tk, wxWidgets, and possibly Freetype (although that allows for background graphics rendering).

* Run <tt>make</tt> to build it. (The first time it will take loong !)
make

* And finally install to <tt>/usr/local/</tt>:
sudo make install

== Field deployment ==

Since the RPi Model B rev2 only uses 3 watts of power (and the Model A only uses 1.5 watts), and due to its small footprint, low cost & easy drop-in replacability, it's ideal for use as a field datalogger run from a battery in harsh environments where you'd be loathe to leave an expensive laptop. Since it uses a standard Linux toolchain with easy access to 30000 prebuilt software packages, and encourages Python as a primary programming language, it is easy for anyone with general UNIX experience to set up with the aid of a wealth of help available on the Internet; no specialist skills working with exotic embedded hardware is needed.

=== Rugged/waterproof case ===

The RPi does not come with a case, you'll have to put something together yourself.

The classic DIY field gear solution to this is to get a small Pelican Case, and drill some holes in the side where you mount some waterproof bulkhead connector fittings with silicone sealant, or install pass-through cable glands. Make the power button a red light-up one with a {{wikipedia|molly_guard}} to make it look professional. :o)

* [https://www.google.com/search?q=rugged+case+raspberry+pi Here's a web search for "rugged cases" for the RPi]
: ... but since it already has mounting holes on the PCB you could just mount it with rubber offsets to a backing plate cut to the interior size of your waterproof case.

Heat dissipation should not be a major issue in most deployments.

=== Connecting with a GPS ===

==== Software ====

Install the <tt>gpsd</tt> Raspian package. This can also feed time into <tt>ntpd</tt>, the standard UNIX time keeping deamon, with micro-second accuracy; this can be important as the RPi does not have a built-in real time clock. (see RPi forums for how to connect to a RTC via the GPIO pins)

==== Hardware ====

For NMEA you can plug in a RS-232 or TTL level serial connection to the GPIO dual-inline header pin block on the board.

You can plug a GPS which communicates via USB directly into one of the RPi's USB ports, but if the GPS uses the USB port for more than just communication (i.e. to power or recharge it) you'll want to use a powered USB hub.

AdaFruit technologies (and probably many others) sells a bare-board GPS kit for the RPi.

=== Using as an automated datalogger ===

You can use the RPi connected to monitoring devices to automatically poll and collect data via the GPIO pins on a regular schedule via standed UNIX {{wikipedia|cron}} jobs.

GRASS can be run non-interactively in text mode, without the GUI (see [[GRASS_and_Shell#GRASS_Batch_jobs|GRASS Batch Jobs]]), and so beyond a simple datalogger your remote RPi can perform full data processing, creation of finished real-time maps, data plots, and finished auto-generated PDF reports, then serve these via FTP or a web page running in the background. An ethernet connection, USB WiFi dongle or VHF radio packet modem can be connected to either push the data back to your home base, or stay online ready for queries.

To save power, pair with a low power {{wikipedia|Arduino}} board (like the ''Ultra Mini 8'') with a timer on it. You can have the system boot, perform a measurement, and send off the results, before shutting itself back down for another hour of <1mA sleep. In this way a small solar panel and a 6v or 12v sealed lead-acid battery (plus a 5v regulator) can keep the unit running indefinetly.

* AdaFruit technologies (and probably many others) sells a kit with a solar panel and a rechargable cellphone-style Li-Ion battery for the RPi.

=== Using as a field entry device ===

It will work, but maybe the task is more suited for a jailbroken Android Tablet dual-booting into Linux? See also the [http://f-droid.org Android build of gvSIG mini], another OSGeo project.

* [http://www.raspberrypi.org/archives/3621 See this blog post] for instructions on using a daylight readable e-Ink display (in this case a Kindle) as a small monitor which is actually usable in sunshine.

== Tips ==

Due to low RAM, avoid running other software when using the wxGUI, especially when launching it.

== See also ==

* [http://grassold.osgeo.org/screenshots/platforms.php Historical screenshots of portable-GRASS running on iPAQ and handheld computers]
* The [http://www.raspberrypi.org/ Raspberry Pi Foundation] is a non-profit education-focused group in the UK which designs and produces the RPi.

[[Category: Hardware]]
[[Category: Android]]
[[Category: Installation‏‎]]
[[Category: Tutorial]]