2023-06-05 10:00 CEST
Conversation as part of the GRASS Community Meeting in Prague 2023
Participated: Nyall Dawson (online), Markus Neteler, Vaclav Petras, Anna Petrasova, Micha Silver, Loïc Bartoletti (online), Floris Vanderhaeghe
Nyall presented an overview of GRASS-QGIS integration components and their strengths and weaknesses. (Nyall Dawson has emailed us his slides.)
To reduce maintenance burden and make it less confusing for users, the C++ plugin needs to be removed.
The goal is to remove GRASS C++ plugin. To do that, some functionality should be moved to Processing or QGIS Settings. Mapset handling unclear where to put it.
Markus points out the existence of GDAL-GRASS driver, which is maintained, used by Geoserver and planned to use in rgrass (again). Packaging could be done, but perhaps it is not worth adding another dependency when QGIS GRASS provider works fine. Moreover, the latter operates directly, doesn't depend on GDAL, which Nyall regards as an advantage.
GRASS C++ plugin often split the GRASS tools into multiple (e.g., r.slope), which in the past caused issues. That is not the case with GRASS tools available from the Processing plugin.
Micha sees many users complaining, when the tool fails, but the error message is confusing for both users and GRASS developers.
In general, the interface is being kept up-to-date, unlike e.g. SAGA, which had to become a 3rd party provider.
Addons are often requested, but are not available in Processing, see recent related QGIS issues/PRs:
There needs to be more discussion how to support addons, some ideas/questions/concerns:
g.extension
can be used to install addons.This applies to all GRASS algorithms (as for other providers). Each GRASS tool in the Processing plugin has a .txt file for converting options to whatever QGIS needs. Significant number of tools have also an associated Python file for some special cases. This complicates updating tools when they change in GRASS GIS and adding Addons.
Some ideas/questions/concerns:
Currently, GRASS calls block the QGIS GUI since grass --exec g.something
always locks the mapset. There is no reason for that, since Processing calls GRASS with grass --tmp-location
. GRASS command can be safely run in separate mapsets. Calling in the same mapsets is routinely done in GRASS, but users need to know what they are doing. Issues would arise with different computational regions, or when writing to the same raster layer or to the same sqlite database (different vector layers share same sqlite db). This could be solved, if needed. Nyall will remove the restriction so that GRASS tools can be called in the background.
Nyall is eager to continue supporting GRASS natively in QGIS.
A follow-up would be nice in e.g. 2 months. Nyall, please share your slides.
Other developers to contact: Alexander Bruy (alexbruy), Jürgen Fischer (jef-n), Loïc Bartoletti (lbartoletti)
or
or
By clicking below, you agree to our terms of service.
New to HackMD? Sign up
Syntax | Example | Reference | |
---|---|---|---|
# Header | Header | 基本排版 | |
- Unordered List |
|
||
1. Ordered List |
|
||
- [ ] Todo List |
|
||
> Blockquote | Blockquote |
||
**Bold font** | Bold font | ||
*Italics font* | Italics font | ||
~~Strikethrough~~ | |||
19^th^ | 19th | ||
H~2~O | H2O | ||
++Inserted text++ | Inserted text | ||
==Marked text== | Marked text | ||
[link text](https:// "title") | Link | ||
 | Image | ||
`Code` | Code |
在筆記中貼入程式碼 | |
```javascript var i = 0; ``` |
|
||
:smile: | ![]() |
Emoji list | |
{%youtube youtube_id %} | Externals | ||
$L^aT_eX$ | LaTeX | ||
:::info This is a alert area. ::: |
This is a alert area. |
On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?
Please give us some advice and help us improve HackMD.
Do you want to remove this version name and description?
Syncing