GRASS-Wiki - User contributions [en]

GRASS GSoC Ideas 2024

2024-02-09T16:49:20Z

⚠️Ctwhite: Add GRASS STAC integration idea

== About ==

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

== Ideas ==
If you are a student you can suggest a new idea or pick up an existing one. In any case write about it to [https://lists.osgeo.org/listinfo/grass-dev grass-dev mailing list],[https://github.com/OSGeo/grass/discussions GitHub Discussions], or [https://gitter.im/grassgis/community Gitter].

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

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

=== Parallelization of existing tools ===

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

* Requirements: familiarity with C, OpenMP
* Mentor: Huidae Cho
* Co-mentor: Vaclav Petras, Anna Petrasova
* Project length: 175 or 350 hours (take your pick)
* Rating: medium
* Expected Outcomes: parallelized module or modules, depending on complexity
* Test of skills: suggest/implement solution for https://github.com/OSGeo/grass/issues/2644

=== Improve GRASS user experience in Jupyter Notebook ===
[[File:Jupyter_interactive_viewshed.png|500px|thumb|right|InteractiveMap in grass.jupyter library]]
Python package [https://grass.osgeo.org/grass-stable/manuals/libpython/grass.jupyter.html grass.jupyter] was developed during [https://trac.osgeo.org/grass/wiki/GSoC/2021/JupyterAndGRASS GSoC 2021] to simplify running GRASS from Jupyter Notebooks and displaying data. This project could focus on adding features such as adding parallelization for rendering, increasing interactivity of displayed data using ipyleaflet (e.g., capture mouse clicks to show information about vector line, pixel), adding API for managing projects and subprojects (i.e., locations/mapsets), simplifing display of attribute data, ...

* Requirements: Python
* Mentor: Anna Petrasova
* Co-mentor: Vaclav Petras, Helena Mitasova
* Project length: 175 or 350 hours (take your pick)
* Rating: easy to medium
* Expected Outcomes: improved user experience when using GRASS through notebooks
* Test of skills: https://github.com/OSGeo/grass/issues/3276, or write a test for [https://github.com/OSGeo/grass/tree/main/python/grass/jupyter grass.jupyter library] using python unittest or pytest, more info [https://grass.osgeo.org/grass-devel/manuals/libpython/gunittest_testing.html here].

=== Add JSON output to different tools in C ===
There are several tools in GRASS that would benefit from a JSON-formatted output, see [https://github.com/OSGeo/grass/issues/3020 this issue for a list of tools]. Besides adding the JSON output, the work would also include adding tests and basic documentation.
* Requirements: C, Python for tests
* Mentor: Vaclav Petras
* Co-mentor: Anna Petrasova, Corey White
* Project length: 175 or 350 hours (take your pick)
* Rating: easy to medium
* Expected Outcomes: one or more (depending on project length and complexity of the tool) tools with well tested JSON output
* Test of skills: Address https://github.com/OSGeo/grass/issues/1044 for r.surf.fractal

=== Support writing tests with pytest ===

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

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

=== New easy-to-use CLI and API for GRASS GIS ===

* Make running of GRASS GIS modules as easy as it is to run GDAL commands.
** `grass run r.slope.aspect elevation=elevation.tiff slope=slope.tiff aspect=aspect.tiff`
** CLI like GDAL has.
** No GRASS Database, Location, Mapset to deal with.
** No import, export from user perspective.
** Reasonable defaults for things like region.
** CLI and API still allows user to specify any of the above.
* Idea page with details: wiki:GSoC/2021/EasyToUseCliAndApiIdea
* Project length: 350 hours
* Rating: medium
* Requirements:
** Language: Python
** Proposal: Student needs to show sufficient understanding of the GRASS GIS Database structure and significantly extend on text below in terms of more concrete formulation of ideas and identification of missing and existing parts.
* Mentors: Vaclav Petras
* Co-mentors: Stefan Blumentrath
* Proposed by: Vaclav Petras
* Expected outcomes: New subcommand which easily runs a GRASS module on GeoTiff and GeoPackage.
* Test and training tasks:
** Solve one of the tickets linked at the idea page.
** Add features to `grass` executable interface:
*** Make it possible to associate `*.gxw` files with `grass` executable (#1204) or at least add `--gui-workspace` or preferably just recognize it in the command line (distinguish it from database/location/mapset).
** Extend `--exec` functionality:
*** Add `--region` to set a temporary computational region for the execution, e.g. `--region="raster=raster_name"`
*** Add `--import-raster=some/file.tiff` which imports (r.import) a raster file (same for vector and similarly for export).
*** Add `--link-raster=some/file.tiff` which links (r.external) a raster file (same for vector and similarly for r.external.out).

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

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

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

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

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

=== Title of idea ===

Description here

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

== Tips for students ==

* If you have your own ideas we encourage you to propose them. Explain them on the [https://lists.osgeo.org/listinfo/grass-dev grass-dev mailing list].
* If you like some idea here or from previous yeas, write about it on [https://lists.osgeo.org/listinfo/grass-dev grass-dev mailing list] and any ideas of your own which could improve it.
* Follow some good practices in your ideas and proposals:
** Stress why the project would be useful.
** Show that you know how you will proceed. That is, make sure that you can demonstrate that the proposal is feasible in the given time frame.
** Be specific in the implementation (or at least as specific as you can).
** Explain what the final product will look like and how it will work. You can add drawings or mock-ups.
** Explain how the idea relates to existing GRASS GIS functions, features, and needs.
** Do not include steps such as "install GRASS", "compile GRASS libraries (on my machine)", "read about the API". You should do this before applying to GSoC.
* Compile GRASS GIS from source and prepare environment for development:
** Read [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md CONTRIBUTING file] and [https://grasswiki.osgeo.org/wiki/Compile_and_Install compilation instructions].
** If you get stuck with the setup, feel free to consult the [https://lists.osgeo.org/listinfo/grass-user grass-user mailing list].
** Familiarize yourself with wiki:Submitting rules.
* Prove your worth by being active on the GRASS mailing lists ([https://lists.osgeo.org/listinfo/grass-user grass-user], [https://lists.osgeo.org/listinfo/grass-dev grass-dev]) or other channels ([https://github.com/OSGeo/grass/discussions GitHub Discussions], [https://gitter.im/grassgis/community Gitter]), fix some [https://github.com/OSGeo/grass/issues bugs], and/or implement some (smaller) features, or write some (simpler) GRASS module, and post it to mailing list. There's no better way to demonstrate your willingness and abilities. Do this before start you apply to GSoC.
* Also note that fixing existing bugs and/or implementing enhancements will be a part of student evaluation.

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

GRASS Community Meeting Prague 2023

2023-04-04T20:35:55Z

⚠️Ctwhite: /* In person */

{{toc|right}}
The GRASS GIS team is organizing the ''GRASS GIS Community Meeting with contributors, power users and developers'' from '''June 2 to June 6, 2023''' to celebrate GRASS GIS '''40th birthday'''.

<gallery mode="slideshow">
Image:grass-sprint-prague.jpg|Prague 2013
Image:Grass_sprint2018_bonn_fotowall.jpg|Bonn 2018
</gallery>

== Purpose ==

GRASS GIS Community Meeting is a great occasion for folks to support the development by actively contributing to the source code, documentation (manuals, wiki, tutorials), translations, website 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 GIS project and the interfaces to QGIS, GDAL, PostGIS, R statistics, OGC Services and willing to '''celebrate with us the 40th GRASS GIS birthday!!'''

For the detailed agenda, see below.

== Sponsors ==

We welcome '''financial contributions''' to support the meeting and we are looking for sponsors to cover costs such as meals or to help reducing travelling and accommodation expenses for GRASS developers with far arrival. If you are interested in sponsoring the GRASS Community Meeting, please read about

:::'''sponsoring the GRASS GIS project''' at '''[https://grass.osgeo.org/contribute/sponsoring/ https://grass.osgeo.org/contribute/sponsoring/]'''

Note that it is also possible to buy a round of beers for the developers with a quick click using the Open Collective "Contribute Money" button https://opencollective.com/osgeo/projects/grass

Any surplus at the end of the event will be turned over to the GRASS GIS project.

This GRASS Community Meeting is a great occasion for you to support the development of GRASS. With your contribution you'll enable more developers to meet. Community meetings are important opportunities for developers to discuss, fix bugs, plan the direction for the project and work on new features. Please see below for the detailed agenda. The developers and contributors are donating their valuable time, so it would be great if in-kind funding can be made available from within the community to cover out-of-pocket expenses. All of the work that takes place at the community meeting will be directly contributed back into the GRASS project to the benefit of everyone who uses it.

=== Thanks to our sponsors ===

We are grateful for the support which we have received to organize this GRASS Community Meeting:

TBD

== Timing ==

'''When''': June 2-6, 2023

Of course you are invited to join or leave the meeting whenever you want.

== Venue ==

[[Image:logo_cvut.jpg|130px|left]]
Department of Geomatics 
[https://www.fsv.cvut.cz/?lang=en Faculty of Civil Engineering] 
[https://www.cvut.cz/en Czech Technical University in Prague], {{wikipedia|Czech Republic}} 
Thákurova 7/2077, Prague 
Room B868 
[https://en.mapy.cz/s/debazefuse Map] 

Prague has an international [http://www.prg.aero/en/ airport] and is also reachable by train, bus or car.

== Accommodation and Costs ==

Participants should plan for the following costs:

* The participation is free of charge
* Travel to Prague, variable depending on where you come from
* Accommodation and meals (with the donated sponsorship money we will try to cover some expenses of the participants)
'''Please note''': The currency in Czech Republic is {{wikipedia|Czech crown}} (CZK, koruna, Kč). 100 Czech crowns are about 4 Euros (see [https://www.cnb.cz/cs/financni-trhy/devizovy-trh/kurzy-devizoveho-trhu/kurzy-devizoveho-trhu/ current rates]).

Please let us know your time of arrival and departure, so we can book accommodations and organize the logistics.

Financial support: (partial) travel grants can be payed upon request thanks to our sponsors!

== Agenda - What we plan to do ==

'''Note:''' The program is generally open for your ideas. Please write an email to the [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developer list] to discuss your contribution.

During the meeting we will work on GRASS GIS on these tasks (please add more!):

* We will update and revise the [https://github.com/qgis/QGIS/tree/master/python/plugins/grassprovider GRASS GIS Integration with QGIS] to simplify maintenance.
* Furthermore, we will migrate the compilation technology to CMake to significantly improve the Windows builds including PDAL support and become binary compatible with OSGeo4W.
* The extensive GRASS documentation will be converted from HTML to Markdown to facilitate future collaboration.
* Pictures, examples and workflows will be added to the documentation where they are still missing.
* Software maintenance processes are automated and documented to reduce the burden on maintainers and thus improve the sustainability of the project.

This means that there are tasks from both the programming and documentation areas to appeal to a wide range of interested parties.

Further details about the action items you '''find [[Talk:GRASS Community Meeting Prague 2023|here]]''' and below. Topics cover non-technical, semi-technical, and technical issues.

=== Timeline ===

Will be specified later.

==== Friday, 2 June ====

==== Saturday, 3 June ====

==== Sunday, 4 June ====

==== Monday, 5 June ====

==== Tuesday, 6 June ====

== Participation ==

We are planning for an attendance of 20 people (i.e., coding places) but of course you are welcome to join us and bring new ideas with you: we'll make more places available. Please add your name here or contact [[User:Landa|Martin Landa]] <tt><landa.martin at gmail.com></tt>:

=== In person ===

{|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'''
!width=75px|'''T-Shirt'''
!'''Notes'''
|-
|1
|[[User:Landa|Martin Landa]]
| Czech Republic
| June 2
| June 6
|
| XL
|
|-
|2
| Micha Silver
| Israel
| June 2
| June 6
| Addon to derive soil moisture from Sentinel 2
| XXL
|
|-
|3
|[https://www.osgeo.org/member/kudrnovsky/ Helmut Kudrnovsky]
| Austria
| June 2
| June 4
|
| L
|
|-
|4
|[[User:Neteler|Markus Neteler]]
| Germany
| June 2
| June 6 (12:43)
| see [[Talk:GRASS_Community_Meeting_Prague_2023#Markus_Neteler|my list in "Discussion" page]]
| L
|
|-
|5
|[[User:pesekon2|Ondřej Pešek]]
| Czech Republic
| June 2
| June 6
|
| M
|
|-
|6
| [[User:helena|Helena Mitasova]]
| United States
| June 2
| June 6
|
| S
|
|-
|7
| [[User:wenzeslaus|Vaclav Petras]]
| United States
| June 1
| June 7
| Support CMake transition, revise connection with QGIS and other tools
| M
|
|-
|8
| [[User:Annakrat|Anna Petrasova]]
| United States
| June 1
| June 7
| parallelization, grass.jupyter
| S
|
|-
|9
| [[User:Ctwhite|Corey White]]
| United States
| June 1
| June 7
| Connections with other tools, OpenPlains, JSON outputs
| XL
|
|-
|10
| [[User:MarisN|Maris Nartiss]]
| Latvia
| June 2
| June 6
|
| XL
|-
|}

=== Via chat or hangout ===

Join our [https://app.gitter.im/#/room/#grassgis_community:gitter.im Gitter chatroom]

TBD: Google Meet / Zoom / ???

Participating virtually:

{|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'''
!'''Topics'''
!'''Notes'''
|-
|1
|[[User:Baharmon|Brendan Harmon]]
| United States
| Update integration with QGIS
|
|-
|}

==== Timing of hangout meetings ====

TBD

=== Collaborative document scratching ===

TBD

== Individual Preparation ==

* Bring your own computer
* Bring {{wikipedia|AC adapter|power connector adapter}} if needed (Czech Republic: 230V, 50Hz, {{wikipedia|File:Euro-Flachstecker_2.jpg|Type C Europlugs}} are common and also {{wikipedia|File:French_plug_and_socket.jpg|Type E}})
* Install subversion and the compiler tools, and come with a working GRASS development environment if possible.

== Broadcast & Video ==

During the event :)

== Photos ==

Also during the event :)

== FAQ ==

* '''How was it last time?'''
** Very nice, see [[GRASS_GIS at OSGeo Virtual Community Sprint 2020]]!
* ''Is the GRASS Community Meeting just a coding event?''
** It is mainly a coding and documentation event. It is a working session for people who are already participants in the GRASS project and/or are committed to improving the GRASS project.
** On demand we can do some presentations of current working GRASS implementation and new upcoming features to spread the idea of Open Source GIS software.
* ''Is the GRASS Community Meeting for developers only?''
** No: anybody can help, with testing, checking out bugs and fixes, documentation and more.
* ''Where can I get help and more information about the community meeting?''
** Contact [[User:Landa|Martin Landa]] <tt><landa.martin at gmail.com></tt>

== Press Release ==

TBD: After the event :-)

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2023]]

GRASS Community Meeting Prague 2023

2023-04-04T20:34:10Z

⚠️Ctwhite: /* In person */

{{toc|right}}
The GRASS GIS team is organizing the ''GRASS GIS Community Meeting with contributors, power users and developers'' from '''June 2 to June 6, 2023''' to celebrate GRASS GIS '''40th birthday'''.

<gallery mode="slideshow">
Image:grass-sprint-prague.jpg|Prague 2013
Image:Grass_sprint2018_bonn_fotowall.jpg|Bonn 2018
</gallery>

== Purpose ==

GRASS GIS Community Meeting is a great occasion for folks to support the development by actively contributing to the source code, documentation (manuals, wiki, tutorials), translations, website 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 GIS project and the interfaces to QGIS, GDAL, PostGIS, R statistics, OGC Services and willing to '''celebrate with us the 40th GRASS GIS birthday!!'''

For the detailed agenda, see below.

== Sponsors ==

We welcome '''financial contributions''' to support the meeting and we are looking for sponsors to cover costs such as meals or to help reducing travelling and accommodation expenses for GRASS developers with far arrival. If you are interested in sponsoring the GRASS Community Meeting, please read about

:::'''sponsoring the GRASS GIS project''' at '''[https://grass.osgeo.org/contribute/sponsoring/ https://grass.osgeo.org/contribute/sponsoring/]'''

Note that it is also possible to buy a round of beers for the developers with a quick click using the Open Collective "Contribute Money" button https://opencollective.com/osgeo/projects/grass

Any surplus at the end of the event will be turned over to the GRASS GIS project.

This GRASS Community Meeting is a great occasion for you to support the development of GRASS. With your contribution you'll enable more developers to meet. Community meetings are important opportunities for developers to discuss, fix bugs, plan the direction for the project and work on new features. Please see below for the detailed agenda. The developers and contributors are donating their valuable time, so it would be great if in-kind funding can be made available from within the community to cover out-of-pocket expenses. All of the work that takes place at the community meeting will be directly contributed back into the GRASS project to the benefit of everyone who uses it.

=== Thanks to our sponsors ===

We are grateful for the support which we have received to organize this GRASS Community Meeting:

TBD

== Timing ==

'''When''': June 2-6, 2023

Of course you are invited to join or leave the meeting whenever you want.

== Venue ==

[[Image:logo_cvut.jpg|130px|left]]
Department of Geomatics 
[https://www.fsv.cvut.cz/?lang=en Faculty of Civil Engineering] 
[https://www.cvut.cz/en Czech Technical University in Prague], {{wikipedia|Czech Republic}} 
Thákurova 7/2077, Prague 
Room B868 
[https://en.mapy.cz/s/debazefuse Map] 

Prague has an international [http://www.prg.aero/en/ airport] and is also reachable by train, bus or car.

== Accommodation and Costs ==

Participants should plan for the following costs:

* The participation is free of charge
* Travel to Prague, variable depending on where you come from
* Accommodation and meals (with the donated sponsorship money we will try to cover some expenses of the participants)
'''Please note''': The currency in Czech Republic is {{wikipedia|Czech crown}} (CZK, koruna, Kč). 100 Czech crowns are about 4 Euros (see [https://www.cnb.cz/cs/financni-trhy/devizovy-trh/kurzy-devizoveho-trhu/kurzy-devizoveho-trhu/ current rates]).

Please let us know your time of arrival and departure, so we can book accommodations and organize the logistics.

Financial support: (partial) travel grants can be payed upon request thanks to our sponsors!

== Agenda - What we plan to do ==

'''Note:''' The program is generally open for your ideas. Please write an email to the [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developer list] to discuss your contribution.

During the meeting we will work on GRASS GIS on these tasks (please add more!):

* We will update and revise the [https://github.com/qgis/QGIS/tree/master/python/plugins/grassprovider GRASS GIS Integration with QGIS] to simplify maintenance.
* Furthermore, we will migrate the compilation technology to CMake to significantly improve the Windows builds including PDAL support and become binary compatible with OSGeo4W.
* The extensive GRASS documentation will be converted from HTML to Markdown to facilitate future collaboration.
* Pictures, examples and workflows will be added to the documentation where they are still missing.
* Software maintenance processes are automated and documented to reduce the burden on maintainers and thus improve the sustainability of the project.

This means that there are tasks from both the programming and documentation areas to appeal to a wide range of interested parties.

Further details about the action items you '''find [[Talk:GRASS Community Meeting Prague 2023|here]]''' and below. Topics cover non-technical, semi-technical, and technical issues.

=== Timeline ===

Will be specified later.

==== Friday, 2 June ====

==== Saturday, 3 June ====

==== Sunday, 4 June ====

==== Monday, 5 June ====

==== Tuesday, 6 June ====

== Participation ==

We are planning for an attendance of 20 people (i.e., coding places) but of course you are welcome to join us and bring new ideas with you: we'll make more places available. Please add your name here or contact [[User:Landa|Martin Landa]] <tt><landa.martin at gmail.com></tt>:

=== In person ===

{|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'''
!width=75px|'''T-Shirt'''
!'''Notes'''
|-
|1
|[[User:Landa|Martin Landa]]
| Czech Republic
| June 2
| June 6
|
| XL
|
|-
|2
| Micha Silver
| Israel
| June 2
| June 6
| Addon to derive soil moisture from Sentinel 2
| XXL
|
|-
|3
|[https://www.osgeo.org/member/kudrnovsky/ Helmut Kudrnovsky]
| Austria
| June 2
| June 4
|
| L
|
|-
|4
|[[User:Neteler|Markus Neteler]]
| Germany
| June 2
| June 6 (12:43)
| see [[Talk:GRASS_Community_Meeting_Prague_2023#Markus_Neteler|my list in "Discussion" page]]
| L
|
|-
|5
|[[User:pesekon2|Ondřej Pešek]]
| Czech Republic
| June 2
| June 6
|
| M
|
|-
|6
| [[User:helena|Helena Mitasova]]
| United States
| June 2
| June 6
|
| S
|
|-
|7
| [[User:wenzeslaus|Vaclav Petras]]
| United States
| June 1
| June 7
| Support CMake transition, revise connection with QGIS and other tools
| M
|
|-
|8
| [[User:Annakrat|Anna Petrasova]]
| United States
| June 1
| June 7
| parallelization, grass.jupyter
| S
|
|-
|9
| [[User:Ctwhite|Corey White]]
| United States
| June 1
| June 7
|
| XL
|
|-
|10
| [[User:MarisN|Maris Nartiss]]
| Latvia
| June 2
| June 6
|
| XL
|-
|}

=== Via chat or hangout ===

Join our [https://app.gitter.im/#/room/#grassgis_community:gitter.im Gitter chatroom]

TBD: Google Meet / Zoom / ???

Participating virtually:

{|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'''
!'''Topics'''
!'''Notes'''
|-
|1
|[[User:Baharmon|Brendan Harmon]]
| United States
| Update integration with QGIS
|
|-
|}

==== Timing of hangout meetings ====

TBD

=== Collaborative document scratching ===

TBD

== Individual Preparation ==

* Bring your own computer
* Bring {{wikipedia|AC adapter|power connector adapter}} if needed (Czech Republic: 230V, 50Hz, {{wikipedia|File:Euro-Flachstecker_2.jpg|Type C Europlugs}} are common and also {{wikipedia|File:French_plug_and_socket.jpg|Type E}})
* Install subversion and the compiler tools, and come with a working GRASS development environment if possible.

== Broadcast & Video ==

During the event :)

== Photos ==

Also during the event :)

== FAQ ==

* '''How was it last time?'''
** Very nice, see [[GRASS_GIS at OSGeo Virtual Community Sprint 2020]]!
* ''Is the GRASS Community Meeting just a coding event?''
** It is mainly a coding and documentation event. It is a working session for people who are already participants in the GRASS project and/or are committed to improving the GRASS project.
** On demand we can do some presentations of current working GRASS implementation and new upcoming features to spread the idea of Open Source GIS software.
* ''Is the GRASS Community Meeting for developers only?''
** No: anybody can help, with testing, checking out bugs and fixes, documentation and more.
* ''Where can I get help and more information about the community meeting?''
** Contact [[User:Landa|Martin Landa]] <tt><landa.martin at gmail.com></tt>

== Press Release ==

TBD: After the event :-)

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2023]]

GRASS Community Meeting Prague 2023

2023-04-03T14:07:40Z

⚠️Ctwhite: /* In person */

{{toc|right}}
The GRASS GIS team is organizing the ''GRASS GIS Community Meeting with contributors, power users and developers'' from '''June 2 to June 6, 2023''' to celebrate GRASS GIS '''40th birthday'''.

<gallery mode="slideshow">
Image:grass-sprint-prague.jpg|Prague 2013
Image:Grass_sprint2018_bonn_fotowall.jpg|Bonn 2018
</gallery>

== Purpose ==

GRASS GIS Community Meeting is a great occasion for folks to support the development by actively contributing to the source code, documentation (manuals, wiki, tutorials), translations, website 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 GIS project and the interfaces to QGIS, GDAL, PostGIS, R statistics, OGC Services and willing to '''celebrate with us the 40th GRASS GIS birthday!!'''

For the detailed agenda, see below.

== Sponsors ==

We welcome '''financial contributions''' to support the meeting and we are looking for sponsors to cover costs such as meals or to help reducing travelling and accommodation expenses for GRASS developers with far arrival. If you are interested in sponsoring the GRASS Community Meeting, please read about

:::'''sponsoring the GRASS GIS project''' at '''[https://grass.osgeo.org/contribute/sponsoring/ https://grass.osgeo.org/contribute/sponsoring/]'''

Note that it is also possible to buy a round of beers for the developers with a quick click using the Open Collective "Contribute Money" button https://opencollective.com/osgeo/projects/grass

Any surplus at the end of the event will be turned over to the GRASS GIS project.

This GRASS Community Meeting is a great occasion for you to support the development of GRASS. With your contribution you'll enable more developers to meet. Community meetings are important opportunities for developers to discuss, fix bugs, plan the direction for the project and work on new features. Please see below for the detailed agenda. The developers and contributors are donating their valuable time, so it would be great if in-kind funding can be made available from within the community to cover out-of-pocket expenses. All of the work that takes place at the community meeting will be directly contributed back into the GRASS project to the benefit of everyone who uses it.

=== Thanks to our sponsors ===

We are grateful for the support which we have received to organize this GRASS Community Meeting:

TBD

== Timing ==

'''When''': June 2-6, 2023

Of course you are invited to join or leave the meeting whenever you want.

== Venue ==

[[Image:logo_cvut.jpg|130px|left]]
Department of Geomatics 
[https://www.fsv.cvut.cz/?lang=en Faculty of Civil Engineering] 
[https://www.cvut.cz/en Czech Technical University in Prague], {{wikipedia|Czech Republic}} 
Thákurova 7/2077, Prague 
Room B868 
[https://en.mapy.cz/s/debazefuse Map] 

Prague has an international [http://www.prg.aero/en/ airport] and is also reachable by train, bus or car.

== Accommodation and Costs ==

Participants should plan for the following costs:

* The participation is free of charge
* Travel to Prague, variable depending on where you come from
* Accommodation and meals (with the donated sponsorship money we will try to cover some expenses of the participants)
'''Please note''': The currency in Czech Republic is {{wikipedia|Czech crown}} (CZK, koruna, Kč). 100 Czech crowns are about 4 Euros (see [https://www.cnb.cz/cs/financni-trhy/devizovy-trh/kurzy-devizoveho-trhu/kurzy-devizoveho-trhu/ current rates]).

Please let us know your time of arrival and departure, so we can book accommodations and organize the logistics.

Financial support: (partial) travel grants can be payed upon request thanks to our sponsors!

== Agenda - What we plan to do ==

'''Note:''' The program is generally open for your ideas. Please write an email to the [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developer list] to discuss your contribution.

During the meeting we will work on GRASS GIS on these tasks (please add more!):

* We will update and revise the [https://github.com/qgis/QGIS/tree/master/python/plugins/grassprovider GRASS GIS Integration with QGIS] to simplify maintenance.
* Furthermore, we will migrate the compilation technology to CMake to significantly improve the Windows builds including PDAL support and become binary compatible with OSGeo4W.
* The extensive GRASS documentation will be converted from HTML to Markdown to facilitate future collaboration.
* Pictures, examples and workflows will be added to the documentation where they are still missing.
* Software maintenance processes are automated and documented to reduce the burden on maintainers and thus improve the sustainability of the project.

This means that there are tasks from both the programming and documentation areas to appeal to a wide range of interested parties.

Further details about the action items you '''find [[Talk:GRASS Community Meeting Prague 2023|here]]''' and below. Topics cover non-technical, semi-technical, and technical issues.

=== Timeline ===

Will be specified later.

==== Friday, 2 June ====

==== Saturday, 3 June ====

==== Sunday, 4 June ====

==== Monday, 5 June ====

==== Tuesday, 6 June ====

== Participation ==

We are planning for an attendance of 20 people (i.e., coding places) but of course you are welcome to join us and bring new ideas with you: we'll make more places available. Please add your name here or contact [[User:Landa|Martin Landa]] <tt><landa.martin at gmail.com></tt>:

=== In person ===

{|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'''
!width=75px|'''T-Shirt'''
!'''Notes'''
|-
|1
|[[User:Landa|Martin Landa]]
| Czech Republic
| June 2
| June 6
|
| XL
|
|-
|2
| Micha Silver
| Israel
| June 2
| June 6
| Addon to derive soil moisture from Sentinel 2
| XXL
|
|-
|3
|[https://www.osgeo.org/member/kudrnovsky/ Helmut Kudrnovsky]
| Austria
| June 2
| June 4
|
| L
|
|-
|4
|[[User:Neteler|Markus Neteler]]
| Germany
| June 2
| June 6 (12:43)
| see [[Talk:GRASS_Community_Meeting_Prague_2023#Markus_Neteler|my list in "Discussion" page]]
| L
|
|-
|5
|[[User:pesekon2|Ondřej Pešek]]
| Czech Republic
| June 2
| June 6
|
| M
|
|-
|6
| [[User:helena|Helena Mitasova]]
| United States
| June 2
| June 6
|
| S
|
|-
|7
| [[User:wenzeslaus|Vaclav Petras]]
| United States
| June 2
| June 6
|
| M
|
|-
|8
| [[User:Annakrat|Anna Petrasova]]
| United States
| June 2
| June 6
|
| S
|
|-
|9
| [[User:Ctwhite|Corey White]]
| United States
| June 2
| June 6
|
| XL
|
|-
|}

=== Via chat or hangout ===

Join our [https://app.gitter.im/#/room/#grassgis_community:gitter.im Gitter chatroom]

TBD: Google Meet / Zoom / ???

Participating virtually:

==== Timing of hangout meetings ====

TBD

=== Collaborative document scratching ===

TBD

== Individual Preparation ==

* Bring your own computer
* Bring {{wikipedia|AC adapter|power connector adapter}} if needed (Czech Republic: 230V, 50Hz, {{wikipedia|File:Euro-Flachstecker_2.jpg|Type C Europlugs}} are common and also {{wikipedia|File:French_plug_and_socket.jpg|Type E}})
* Install subversion and the compiler tools, and come with a working GRASS development environment if possible.

== Broadcast & Video ==

During the event :)

== Photos ==

Also during the event :)

== FAQ ==

* '''How was it last time?'''
** Very nice, see [[GRASS_GIS at OSGeo Virtual Community Sprint 2020]]!
* ''Is the GRASS Community Meeting just a coding event?''
** It is mainly a coding and documentation event. It is a working session for people who are already participants in the GRASS project and/or are committed to improving the GRASS project.
** On demand we can do some presentations of current working GRASS implementation and new upcoming features to spread the idea of Open Source GIS software.
* ''Is the GRASS Community Meeting for developers only?''
** No: anybody can help, with testing, checking out bugs and fixes, documentation and more.
* ''Where can I get help and more information about the community meeting?''
** Contact [[User:Landa|Martin Landa]] <tt><landa.martin at gmail.com></tt>

== Press Release ==

TBD: After the event :-)

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2023]]

GRASS GIS at OSGeo Community Sprint 2022

2022-08-27T10:04:47Z

⚠️Ctwhite: /* */

{{toc|right}}

[https://wiki.osgeo.org/wiki/OSGeo_Community_Sprint_2022 ''OSGeo Community Sprint 2022''], Florence, Aug 27-28, 2022.

<center>
[[File:GRASS_GIS_Code_Sprint_2018.png|320px]]
</center>

== Introduction ==

Participation is free of charge and anyone involved or interested in getting involved in OSGeo community projects is welcome.

This year we will try to offer the format '''an hour with the developer''', where we ask seasoned community members to donate time for welcoming new members and introduce them to different projects or guide them through the setup of the development environment or translation tools and get started on the Foss4G journey.

You can choose to contribute to one or more projects. The sky is the limit. There’s always plenty to do – and it’s not all about programming. Translation, documentation, feedback, discussions, and testing are very important for projects! Conference registration is not a prerequisite for participation in the code sprint.

=== When ===

The code sprint will be held on 27-28 of August.

=== Where ===

The codesprint will be hosted at the University of Florence.

* onsite: Centro Didattico Morgagni UniFi in Viale Morgagni 42 -- 44 Firenze ([https://umap.openstreetmap.fr/it/map/foss4g-2022-sites_776000#16/43.7978/11.2472 map]).
* online: https://gitter.im/grassgis/sprint

== Goals ==

=== Command Line Improvements ===
* Finish issues [https://github.com/OSGeo/grass/issues/942 #942] [https://github.com/OSGeo/grass/issues/753 #753] [https://github.com/OSGeo/grass/issues/964 #964] - A unified colorful prompt across all shells
** I need help with windows for testing if color works as expected
** Get clarification on whether issue #970 is up for grabs
** Discuss with Vaclav about introducing sub commands into grass.py, and maybe get it started.

=== Discuss naming and presentation of GRASS GIS data hierarchy ===
* Kladivova, Petrasova, Petras, Landa (2022, not published): ''GRASS GIS was conceived from its very beginning as a powerful geospatial computing tool that emphasized data integrity to deliver accurate results. To achieve consistent results when working with data from different sources, GRASS GIS requires the data to be imported into GRASS data storage and reprojected into a common coordinate reference system (CRS) predetermined by the user for each project. Within each project, called location, data are further organized into subprojects, called mapsets, used for managing different subregions or analyses. Additionally, mapsets have distinct processing settings such as computational extent and resolution. The directory with one or more locations is referred to as GRASS database and is typically named grassdata.''
* location and mapset -> project and subproject
* GRASS database (GISDBASE, database directory) -> not needed as a prominent concept; a path, directory (folder) which happens to have one or more projects
* More than just a rename, but different presentation.
* g.project.switch (or g.switch.project) - change current project or subproject
* g.search.path - manage visibility of data in other subprojects
* g.mapset and g.mapsets kept for backwards compatibility
* grass.script.setup.init - add project and subproject keyword arguments; keep location and mapset
* Workspace file (.gxw) -> automatically created in each subproject with the last used GUI state, but still needs to be available as now for things like 3D animations and g.print.ws
* PERMANENT
** permanent versus temporary confusion
** alternative names: default, base, main (if common files are moved to location, there is no need for a specific name at all)
** also as a default subproject (mapset)? Path to project (location) would translate to project/{default}, e.g., project/PERMANENT

=== Tools versus Modules ===

* Modular: A component added to a modular system
* Tools: A things which does things

=== NC sample data on the website ===

* Rename https://grass.osgeo.org/download/data/#NorthCarolinaDataset: take out <tt>_grass7</tt> to not confuse G8 users

=== New semantic versioning and GitHub milestones ===

* rename label 8.4 to 8.3?

=== Marketing ===

* Best practice (recommendations) how to make a presentation on GRASS GIS
** existing good material (e.g., reveal.js slides)
** what should be mentioned
** adversise the mailing list and new communication platform
** ... add more.
* add link to Anna's presentation on parallelization --> and blogpost
* add link to Vashek's presentation on code style --> and blogpost

=== Parallel processing ===

* r.mapcalc.tiled/r.*.tiled: set default window to non-square for faster row-based computation
* develop a script which tests a combination of nprocs/memory settings to guide the user what to use on the particular machine
* add link to Anna's presentation on parallelization

=== Tests ===

* Document how to write test (or prominently say where this is already documented)

=== Sponsorship ===

* add different levels
* explain better what it is a good idea to donate money (what is the value gained for the donor)

=== GitHub maintenance ===

* use a project board (?) - discuss

=== Message Translation ===

* how to backport translations (weblate pull requests)

=== Student grants ===

* define content of new round

=== Web site ===

* Add roadmap, with iframe pointing to milestones in GitHub?

=== Juyper notebooks ===

* fix timeseries plot which runs into an endless loop in t.rast.series - SQLite locking mess

=== JSON Ouput ===
Update GRASS modules to support json exports.
* g.mapsets
* g.mapset
* g.location
* r.describe
* t.vect.list
* g.region
* r.univar
* r.what
* r.info
* r.stats
* r.report
* r.coin

=== ===

=== ===

=== ===

== Reports ==

=== Saturday ===

==== You ====

* ...

=== Sunday ===

==== You ====

* ...

=== See also ===

* https://wiki.osgeo.org/wiki/FOSS4G_2022/Community_sprint

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2022]]

MacOSX GRASS errors

2019-10-30T20:00:27Z

⚠️Ctwhite: /* When using g.extension after updating to MacOSX Mojave and Xcode 10, I get "fatal error: 'stdio.h' file not found" */

Here some problems reported by users along with solutions:

== Starting GRASS GIS on MacOSX, I get "image not found" ==

A) You may be lacking the installation of one or several "frameworks" (e.g. GDAL). Get them from here:

http://grass.osgeo.org/download/software/mac-osx/
--> Install the required framework packages first

B) You are hit by the SIP - System Integrity Protection - security measure which prevents some software from being installed properly. Please see the internet for suggestions how to deal with that. Alternative: use "[[Compiling on MacOSX using homebrew|homebrew]]" to install GRASS GIS.

== Starting GRASS GIS on MacOSX, I get "bad cpu type in executable" ==

It looks like a macports problem (maybe ''homebrew'' also uses /opt/local?) with their Python. A guess is that their python is 64bit-only, and GRASS is trying to run python 32bit because it couldn't find a 64bit wxpython because 64bit wxpython isn't existing yet in the stable release. 
Work-around: Edit the file ".bash_profile" in your HOME directory and add therein:

export GRASS_PYTHON=/usr/bin/python2.6
export GRASS_PYTHONWX=/usr/bin/pythonw2.6

== When using g.extension, I get "fatal error: grass/gis.h: No such file or directory" ==

Hint: g.extension should indeed work. The main key is that you need to install the Xcode command line tools. This can be done either from the Xcode app (free from app store), or by downloading the command line tools installer separately (from an Apple developer account).

== When using g.extension after updating to MacOSX Mojave and Xcode 10, I get "fatal error: 'stdio.h' file not found" ==

Note: Updating to MacOSX Mojave and Xcode 10 moves the location of the c header files preventing some GRASS extensions from compiling.

Solution: Install the package file located at the below path to add c header files in /usr/include:

/Library/Developer/CommandLineTools/Packages/macOS_SDK_headers_for_macOS_10.14.pkg

'''Update'''

Fix this issue by updating ''/Applications/GRASS-7.6.app/Contents/Resources/include/Make/Platform.make''

By replacing all references to /Developer/SDKs/MacOSX10.9.sdk with the updated sdk path /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk

'''Variables to Update'''

CFLAGS = -g -O2 -arch x86_64 -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk
CXXFLAGS = -arch x86_64 -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk
INCLUDE_DIRS = -I/Applications/GRASS-7.6.app/Contents/Resources/include
LINK_FLAGS = -arch x86_64 -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk -L/Applications/GRASS-7.6.app/Contents/Resources/lib -Xlinker -rpath -Xlinker ${prefix}/lib -Xlinker -rpath -Xlinker ${RUN_GISBASE}/lib

MACOSX_SDK = -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk

== Starting GRASS GIS on MacOSX, I get "AppleScript Error. Terminal got an error: Can't get window 1. (-1728)" ==

Note: Normally when Terminal is activated (running or not), it starts a new window if there is none open, but I've seen cases where it does not when you start Terminal when it was NOT running.

Solution: Try starting Terminal first, then start GRASS.

== Starting GRASS GIS on MacOSX, I get "ERROR: unknown locale: UTF-8" ==

You need to add these two lines

export LC_ALL=en_US.UTF-8
export LANG=en_US.UTF-8

to the file ".bash_profile" in your HOME directory. You can use any text editor to create/edit the file $HOME/.bash_profile (the same: ~/.bash_profile) and copy-paste the these two lines. Just be sure to save it as ".bash_profile" in your home directory.

== d.legend does not show numbers ==

Problem: d.legend and other text is not shown in the display!

Solution: You need to rescan the fonts available on your system:

g.mkfontcap -o

== 3D view error on MacOS (black screen) ==

Problem: 3D view error on MacOS (black screen)

Solution: compile GRASS GIS using [[Compiling on MacOSX using homebrew|homebrew]] libraries. The trick was to set --with-opengl=aqua, so it uses the opengl librarie from the system. Using --with-opengl=x11 results in the black screen.

== See also ==

* MacOSX GRASS Support forum: http://grassmac.wikidot.com/forum:start
* http://www.kyngchaos.com/software/support/faq
* [[WinGRASS errors]]

[[Category: FAQ]]
[[Category: Installation‏‎]]

MacOSX GRASS errors

2019-10-30T19:58:24Z

⚠️Ctwhite: /* When using g.extension after updating to MacOSX Mojave and Xcode 10, I get "fatal error: 'stdio.h' file not found" */

MacOSX GRASS errors

2019-10-30T19:56:02Z

⚠️Ctwhite: /* When using g.extension after updating to MacOSX Mojave and Xcode 10, I get "fatal error: 'stdio.h' file not found" */

Here some problems reported by users along with solutions:

== Starting GRASS GIS on MacOSX, I get "image not found" ==

A) You may be lacking the installation of one or several "frameworks" (e.g. GDAL). Get them from here:

http://grass.osgeo.org/download/software/mac-osx/
--> Install the required framework packages first

B) You are hit by the SIP - System Integrity Protection - security measure which prevents some software from being installed properly. Please see the internet for suggestions how to deal with that. Alternative: use "[[Compiling on MacOSX using homebrew|homebrew]]" to install GRASS GIS.

== Starting GRASS GIS on MacOSX, I get "bad cpu type in executable" ==

It looks like a macports problem (maybe ''homebrew'' also uses /opt/local?) with their Python. A guess is that their python is 64bit-only, and GRASS is trying to run python 32bit because it couldn't find a 64bit wxpython because 64bit wxpython isn't existing yet in the stable release. 
Work-around: Edit the file ".bash_profile" in your HOME directory and add therein:

export GRASS_PYTHON=/usr/bin/python2.6
export GRASS_PYTHONWX=/usr/bin/pythonw2.6

== When using g.extension, I get "fatal error: grass/gis.h: No such file or directory" ==

Hint: g.extension should indeed work. The main key is that you need to install the Xcode command line tools. This can be done either from the Xcode app (free from app store), or by downloading the command line tools installer separately (from an Apple developer account).

== When using g.extension after updating to MacOSX Mojave and Xcode 10, I get "fatal error: 'stdio.h' file not found" ==

Note: Updating to MacOSX Mojave and Xcode 10 moves the location of the c header files preventing some GRASS extensions from compiling.

Solution: Install the package file located at the below path to add c header files in /usr/include:

/Library/Developer/CommandLineTools/Packages/macOS_SDK_headers_for_macOS_10.14.pkg

'''Update'''

Fix this issue by updating ''/Applications/GRASS-7.6.app/Contents/Resources/include/Make/Platform.make''

By replacing all references to /Developer/SDKs/MacOSX10.9.sdk with the updated sdk path /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk

'''Variables to Update'''

```
CFLAGS = -g -O2 -arch x86_64 -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk

CXXFLAGS = -arch x86_64 -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk

INCLUDE_DIRS = -I/Applications/GRASS-7.6.app/Contents/Resources/include

LINK_FLAGS = -arch x86_64 -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk -L/Applications/GRASS-7.6.app/Contents/Resources/lib -Xlinker -rpath -Xlinker ${prefix}/lib -Xlinker -rpath -Xlinker ${RUN_GISBASE}/lib

MACOSX_SDK = -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk
```

== Starting GRASS GIS on MacOSX, I get "AppleScript Error. Terminal got an error: Can't get window 1. (-1728)" ==

Note: Normally when Terminal is activated (running or not), it starts a new window if there is none open, but I've seen cases where it does not when you start Terminal when it was NOT running.

Solution: Try starting Terminal first, then start GRASS.

== Starting GRASS GIS on MacOSX, I get "ERROR: unknown locale: UTF-8" ==

You need to add these two lines

export LC_ALL=en_US.UTF-8
export LANG=en_US.UTF-8

to the file ".bash_profile" in your HOME directory. You can use any text editor to create/edit the file $HOME/.bash_profile (the same: ~/.bash_profile) and copy-paste the these two lines. Just be sure to save it as ".bash_profile" in your home directory.

== d.legend does not show numbers ==

Problem: d.legend and other text is not shown in the display!

Solution: You need to rescan the fonts available on your system:

g.mkfontcap -o

== 3D view error on MacOS (black screen) ==

Problem: 3D view error on MacOS (black screen)

Solution: compile GRASS GIS using [[Compiling on MacOSX using homebrew|homebrew]] libraries. The trick was to set --with-opengl=aqua, so it uses the opengl librarie from the system. Using --with-opengl=x11 results in the black screen.

== See also ==

* MacOSX GRASS Support forum: http://grassmac.wikidot.com/forum:start
* http://www.kyngchaos.com/software/support/faq
* [[WinGRASS errors]]

[[Category: FAQ]]
[[Category: Installation‏‎]]

MacOSX GRASS errors

2019-10-30T19:53:56Z

⚠️Ctwhite: /* When using g.extension after updating to MacOSX Mojave and Xcode 10, I get "fatal error: 'stdio.h' file not found" */

Here some problems reported by users along with solutions:

== Starting GRASS GIS on MacOSX, I get "image not found" ==

A) You may be lacking the installation of one or several "frameworks" (e.g. GDAL). Get them from here:

http://grass.osgeo.org/download/software/mac-osx/
--> Install the required framework packages first

B) You are hit by the SIP - System Integrity Protection - security measure which prevents some software from being installed properly. Please see the internet for suggestions how to deal with that. Alternative: use "[[Compiling on MacOSX using homebrew|homebrew]]" to install GRASS GIS.

== Starting GRASS GIS on MacOSX, I get "bad cpu type in executable" ==

It looks like a macports problem (maybe ''homebrew'' also uses /opt/local?) with their Python. A guess is that their python is 64bit-only, and GRASS is trying to run python 32bit because it couldn't find a 64bit wxpython because 64bit wxpython isn't existing yet in the stable release. 
Work-around: Edit the file ".bash_profile" in your HOME directory and add therein:

export GRASS_PYTHON=/usr/bin/python2.6
export GRASS_PYTHONWX=/usr/bin/pythonw2.6

== When using g.extension, I get "fatal error: grass/gis.h: No such file or directory" ==

Hint: g.extension should indeed work. The main key is that you need to install the Xcode command line tools. This can be done either from the Xcode app (free from app store), or by downloading the command line tools installer separately (from an Apple developer account).

== When using g.extension after updating to MacOSX Mojave and Xcode 10, I get "fatal error: 'stdio.h' file not found" ==

Note: Updating to MacOSX Mojave and Xcode 10 moves the location of the c header files preventing some GRASS extensions from compiling.

Solution: Install the package file located at the below path to add c header files in /usr/include:

/Library/Developer/CommandLineTools/Packages/macOS_SDK_headers_for_macOS_10.14.pkg

'''Update'''

Fix this issue by updating ''/Applications/GRASS-7.6.app/Contents/Resources/include/Make/Platform.make''

By replacing all references to /Developer/SDKs/MacOSX10.9.sdk with the updated sdk path /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk

'''Variables to Update'''

```CFLAGS = -g -O2 -arch x86_64 -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk
CXXFLAGS = -arch x86_64 -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk
INCLUDE_DIRS = -I/Applications/GRASS-7.6.app/Contents/Resources/include
LINK_FLAGS = -arch x86_64 -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk -L/Applications/GRASS-7.6.app/Contents/Resources/lib -Xlinker -rpath -Xlinker ${prefix}/lib -Xlinker -rpath -Xlinker ${RUN_GISBASE}/lib

MACOSX_SDK = -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk
```

== Starting GRASS GIS on MacOSX, I get "AppleScript Error. Terminal got an error: Can't get window 1. (-1728)" ==

Note: Normally when Terminal is activated (running or not), it starts a new window if there is none open, but I've seen cases where it does not when you start Terminal when it was NOT running.

Solution: Try starting Terminal first, then start GRASS.

== Starting GRASS GIS on MacOSX, I get "ERROR: unknown locale: UTF-8" ==

You need to add these two lines

export LC_ALL=en_US.UTF-8
export LANG=en_US.UTF-8

to the file ".bash_profile" in your HOME directory. You can use any text editor to create/edit the file $HOME/.bash_profile (the same: ~/.bash_profile) and copy-paste the these two lines. Just be sure to save it as ".bash_profile" in your home directory.

== d.legend does not show numbers ==

Problem: d.legend and other text is not shown in the display!

Solution: You need to rescan the fonts available on your system:

g.mkfontcap -o

== 3D view error on MacOS (black screen) ==

Problem: 3D view error on MacOS (black screen)

Solution: compile GRASS GIS using [[Compiling on MacOSX using homebrew|homebrew]] libraries. The trick was to set --with-opengl=aqua, so it uses the opengl librarie from the system. Using --with-opengl=x11 results in the black screen.

== See also ==

* MacOSX GRASS Support forum: http://grassmac.wikidot.com/forum:start
* http://www.kyngchaos.com/software/support/faq
* [[WinGRASS errors]]

[[Category: FAQ]]
[[Category: Installation‏‎]]

MacOSX GRASS errors

2019-10-30T19:53:25Z

⚠️Ctwhite: /* When using g.extension after updating to MacOSX Mojave and Xcode 10, I get "fatal error: 'stdio.h' file not found" */

Here some problems reported by users along with solutions:

== Starting GRASS GIS on MacOSX, I get "image not found" ==

A) You may be lacking the installation of one or several "frameworks" (e.g. GDAL). Get them from here:

http://grass.osgeo.org/download/software/mac-osx/
--> Install the required framework packages first

B) You are hit by the SIP - System Integrity Protection - security measure which prevents some software from being installed properly. Please see the internet for suggestions how to deal with that. Alternative: use "[[Compiling on MacOSX using homebrew|homebrew]]" to install GRASS GIS.

== Starting GRASS GIS on MacOSX, I get "bad cpu type in executable" ==

It looks like a macports problem (maybe ''homebrew'' also uses /opt/local?) with their Python. A guess is that their python is 64bit-only, and GRASS is trying to run python 32bit because it couldn't find a 64bit wxpython because 64bit wxpython isn't existing yet in the stable release. 
Work-around: Edit the file ".bash_profile" in your HOME directory and add therein:

export GRASS_PYTHON=/usr/bin/python2.6
export GRASS_PYTHONWX=/usr/bin/pythonw2.6

== When using g.extension, I get "fatal error: grass/gis.h: No such file or directory" ==

Hint: g.extension should indeed work. The main key is that you need to install the Xcode command line tools. This can be done either from the Xcode app (free from app store), or by downloading the command line tools installer separately (from an Apple developer account).

== When using g.extension after updating to MacOSX Mojave and Xcode 10, I get "fatal error: 'stdio.h' file not found" ==

Note: Updating to MacOSX Mojave and Xcode 10 moves the location of the c header files preventing some GRASS extensions from compiling.

Solution: Install the package file located at the below path to add c header files in /usr/include:

/Library/Developer/CommandLineTools/Packages/macOS_SDK_headers_for_macOS_10.14.pkg

'''Update'''

Fix this issue by updating ''/Applications/GRASS-7.6.app/Contents/Resources/include/Make/Platform.make''

By replacing all references to /Developer/SDKs/MacOSX10.9.sdk with the updated sdk path /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk

'''Variables to Update'''
CFLAGS = -g -O2 -arch x86_64 -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk
CXXFLAGS = -arch x86_64 -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk
INCLUDE_DIRS = -I/Applications/GRASS-7.6.app/Contents/Resources/include
LINK_FLAGS = -arch x86_64 -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk -L/Applications/GRASS-7.6.app/Contents/Resources/lib -Xlinker -rpath -Xlinker ${prefix}/lib -Xlinker -rpath -Xlinker ${RUN_GISBASE}/lib

MACOSX_SDK = -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk

== Starting GRASS GIS on MacOSX, I get "AppleScript Error. Terminal got an error: Can't get window 1. (-1728)" ==

Note: Normally when Terminal is activated (running or not), it starts a new window if there is none open, but I've seen cases where it does not when you start Terminal when it was NOT running.

Solution: Try starting Terminal first, then start GRASS.

== Starting GRASS GIS on MacOSX, I get "ERROR: unknown locale: UTF-8" ==

You need to add these two lines

export LC_ALL=en_US.UTF-8
export LANG=en_US.UTF-8

to the file ".bash_profile" in your HOME directory. You can use any text editor to create/edit the file $HOME/.bash_profile (the same: ~/.bash_profile) and copy-paste the these two lines. Just be sure to save it as ".bash_profile" in your home directory.

== d.legend does not show numbers ==

Problem: d.legend and other text is not shown in the display!

Solution: You need to rescan the fonts available on your system:

g.mkfontcap -o

== 3D view error on MacOS (black screen) ==

Problem: 3D view error on MacOS (black screen)

Solution: compile GRASS GIS using [[Compiling on MacOSX using homebrew|homebrew]] libraries. The trick was to set --with-opengl=aqua, so it uses the opengl librarie from the system. Using --with-opengl=x11 results in the black screen.

== See also ==

* MacOSX GRASS Support forum: http://grassmac.wikidot.com/forum:start
* http://www.kyngchaos.com/software/support/faq
* [[WinGRASS errors]]

[[Category: FAQ]]
[[Category: Installation‏‎]]

MacOSX GRASS errors

2019-03-04T15:17:37Z

⚠️Ctwhite: When using g.extension after updating to MacOSX Mojave and Xcode 10, I get "fatel error: 'stdio.h' file not found"

Here some problems reported by users along with solutions:

== Starting GRASS GIS on MacOSX, I get "image not found" ==

A) You may be lacking the installation of one or several "frameworks" (e.g. GDAL). Get them from here:

http://grass.osgeo.org/download/software/mac-osx/
--> Install the required framework packages first

B) You are hit by the SIP - System Integrity Protection - security measure which prevents some software from being installed properly. Please see the internet for suggestions how to deal with that. Alternative: use "[[Compiling on MacOSX using homebrew|homebrew]]" to install GRASS GIS.

== Starting GRASS GIS on MacOSX, I get "bad cpu type in executable" ==

It looks like a macports problem (maybe ''homebrew'' also uses /opt/local?) with their Python. A guess is that their python is 64bit-only, and GRASS is trying to run python 32bit because it couldn't find a 64bit wxpython because 64bit wxpython isn't existing yet in the stable release. 
Work-around: Edit the file ".bash_profile" in your HOME directory and add therein:

export GRASS_PYTHON=/usr/bin/python2.6
export GRASS_PYTHONWX=/usr/bin/pythonw2.6

== When using g.extension, I get "fatal error: grass/gis.h: No such file or directory" ==

Hint: g.extension should indeed work. The main key is that you need to install the Xcode command line tools. This can be done either from the Xcode app (free from app store), or by downloading the command line tools installer separately (from an Apple developer account).

== When using g.extension after updating to MacOSX Mojave and Xcode 10, I get "fatel error: 'stdio.h' file not found" ==

Note: Updating to MacOSX Mojave and Xcode 10 moves the location of the c header files preventing some GRASS extensions from compiling.

Solution: Install the package file located at the below path to add c header files in /usr/include:

/Library/Developer/CommandLineTools/Packages/macOS_SDK_headers_for_macOS_10.14.pkg

== Starting GRASS GIS on MacOSX, I get "AppleScript Error. Terminal got an error: Can't get window 1. (-1728)" ==

Note: Normally when Terminal is activated (running or not), it starts a new window if there is none open, but I've seen cases where it does not when you start Terminal when it was NOT running.

Solution: Try starting Terminal first, then start GRASS.

== Starting GRASS GIS on MacOSX, I get "ERROR: unknown locale: UTF-8" ==

You need to add these two lines

export LC_ALL=en_US.UTF-8
export LANG=en_US.UTF-8

to the file ".bash_profile" in your HOME directory. You can use any text editor to create/edit the file $HOME/.bash_profile (the same: ~/.bash_profile) and copy-paste the these two lines. Just be sure to save it as ".bash_profile" in your home directory.

== d.legend does not show numbers ==

Problem: d.legend and other text is not shown in the display!

Solution: You need to rescan the fonts available on your system:

g.mkfontcap -o

== 3D view error on MacOS (black screen) ==

Problem: 3D view error on MacOS (black screen)

Solution: compile GRASS GIS using [[Compiling on MacOSX using homebrew|homebrew]] libraries. The trick was to set --with-opengl=aqua, so it uses the opengl librarie from the system. Using --with-opengl=x11 results in the black screen.

== See also ==

* MacOSX GRASS Support forum: http://grassmac.wikidot.com/forum:start
* http://www.kyngchaos.com/software/support/faq
* [[WinGRASS errors]]

[[Category: FAQ]]
[[Category: Installation‏‎]]