[GRASS-dev] [GRASS-user] Nice opportunity to show off GRASS functionality and topological vector format ?

[Nikos Alexandris]

* Markus Metz <markus.metz.giswork at gmail.com> [2019-04-18 18:38:28 +0200]:

>On Tue, Apr 16, 2019 at 11:07 AM Moritz Lennert <
>mlennert at club.worldonline.be> wrote:
>>
>> Hi,
>>
>> If anyone has some time and wants to show off some GRASS GIS power:
>>
>> https://www.ecmwf.int/en/learning/workshops/ecmwf-summer-weather-code-2019
>>
>> "The Summer of Weather Code(ESoWC) programme by the European Centre for
>> Medium-Range Weather Forecasts (ECMWF) is a collabrative online
>> programme to promote the development of weather-related open-source
>> software."
>>
>> More specificially:
>>
>> https://github.com/esowc/challenges_2019
>>
>> And even more, I think this challenge is a fairly low hanging fruit
>> using GRASS GIS tools:
>>
>> https://github.com/esowc/challenges_2019/issues/3
>
>I agree, this reads like a low-hanging fruit. I could submit an abstract
>until Sunday 21 April with a fairly detailed workflow, but I will most
>probably not have the time to write such a tool: apparently they would like
>to have a custom QGIS plugin.

Panos literally implemented Nyal Dawson's excellent recommendation(s)
[0, 1, 2] and exposing a GRASS GIS module/add-on is easy. An example is
the QGIS plugin [3] for the `r.estimap.recreation` plugin [4].

[0] https://lists.osgeo.org/pipermail/qgis-developer/2019-February/056155.html
[1] https://lists.osgeo.org/pipermail/qgis-developer/2019-February/056285.html
[2] https://github.com/qgis/QGIS/pull/9202
[3] https://gitlab.com/natcapes/natcapes_qgis
[4] https://gitlab.com/natcapes/r.estimap.recreation

This makes the process as easy as never before, as far as I understand.
In my humble view, this should be further adopted and advertised.

On/Off-topic (Cc-ing also the qgis-developer mailing list):

I left from the `r.estimap.recreation` project leaving behind one
remaining issue-to-solve: https://issues.qgis.org/issues/21322.

This issue concerns only the interface and does not affect the
core work of exposing a GRASS GIS add-on inside QGIS' Processing
Framework. Nevertheless, in my humble view, this issue is important to
the GRASS GIS community and having an up-to-date documentation will save
our time from figuring out how the interface related api works.

Nikos

>
>Markus M
>>
>>
>> APPLICATION DEADLINE: SUNDAY, 21 APRIL 23:59 GMT
>>
>>
>> Moritz
>> _______________________________________________
>> grass-user mailing list
>> grass-user at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/grass-user

>_______________________________________________
>grass-user mailing list
>grass-user at lists.osgeo.org
>https://lists.osgeo.org/mailman/listinfo/grass-user


-- 
Nikos Alexandris | Remote Sensing & Geomatics
GPG Key Fingerprint 6F9D4506F3CA28380974D31A9053534B693C4FB3