[QGIS-Developer] Plugin [1242] QuickPrint approval notification.
Plugin QuickPrint approval by pcav. The plugin version "[1242] QuickPrint 3.5.1" is now approved Link: http://plugins.qgis.org/plugins/QuickPrint/ ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
[QGIS-Developer] Plugin [591] Dissolve with stats approval notification.
Plugin Dissolve with stats approval by pcav. The plugin version "[591] Dissolve with stats 0.6" is now approved Link: http://plugins.qgis.org/plugins/DissolveWithStats/ ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
[QGIS-Developer] Cannot save raster data in formats like NetCDF
Hi list, I wish to report a bug I've discovered when using QGIS Desktop. Unfortunately, I cannot login to the bugtracker (never received an activation email), so I'm reporting the bug on this list. Saving raster data in formats like NetCDF is broken for me in operations like "Clip Raster to Extent", because GDAL is run with the wrong output format. I can reproduce that by: - opening e.g. "Clip Raster to Extent" dialog - setting "Input layer" and "Clipping extent" - setting "Clipped (extent)" to a (non-existing) NetCDF file Expected Result: The output format parameter of the shown GDAL command is "-of NetCDF". Actual Result: The output format parameter of the shown GDAL command is "-of GMT". When run, GDAL exits with an error, telling it does not know format 'GMT'. As a workaround, I'm just running the (corrected) GDAL command in my terminal. I'm using QGIS 3.6.1 and GDAL 2.3.2 on Arch Linux. Greetings, Felix ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
[QGIS-Developer] Bug in QgsPathResolver ?
Hi devs,
I have a strange behavior with QgsPathResolver that prevent layer to be loaded
if a QgsProject read config file from relative path:
The problem has been reduced to the following behavior (pyQgis):
```
# Init a QgsPathResolver as with a relative path
pr = QgsPathResolver('./geography/data/france_parts.qgs')
pr.readPath('./france_parts/france_parts.shp')
# Output -> '/geography/data/france_parts/france_parts.shp'
# Note the leading '/'
```
Worst:
```
pr = QgsPathResolver('../geography/data/france_parts.qgs')
pr.readPath('./france_parts/france_parts.shp')
# Output -> '/../geography/data/france_parts/france_parts.shp'
# which is a meaningless path
```
The side effect is that if you do:
```
prj = QgsProject()
prj.read("./geography/data/france_parts.qgs")
```
then you get the error:
```
Qgis OGR: Cannot open /geography/data/france_parts/france_parts.shp.()
Qgis : 1 unavailable layers found:
Qgis : * ./france_parts/france_parts.shp
```
This is with Qgis 3.6.1
Can anybody confirm that this behavior is a bug ? I will submit a PR if this
is the case.
Thanks,
Cheers
David
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] [GRASS-dev] [GRASS-user] Nice opportunity to show off GRASS functionality and topological vector format ?
* Nikos Alexandris [2019-04-19 13:46:18 +0200]: * Markus Metz [2019-04-18 18:38:28 +0200]: On Tue, Apr 16, 2019 at 11:07 AM Moritz Lennert < mlenn...@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. And here an entry in gis.se: https://gis.stackexchange.com/a/319333/5256. Nikos Markus M APPLICATION DEADLINE: SUNDAY, 21 APRIL 23:59 GMT Moritz ___ grass-user mailing list grass-u...@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user ___ grass-user mailing list grass-u...@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user -- Nikos Alexandris | Remote Sensing & Geomatics GPG Key Fingerprint 6F9D4506F3CA28380974D31A9053534B693C4FB3 ___ grass-dev mailing list grass-...@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev -- Nikos Alexandris | Remote Sensing & Geomatics GPG Key Fingerprint 6F9D4506F3CA28380974D31A9053534B693C4FB3 ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] [GRASS-user] Nice opportunity to show off GRASS functionality and topological vector format ?
* Markus Metz [2019-04-18 18:38:28 +0200]: On Tue, Apr 16, 2019 at 11:07 AM Moritz Lennert < mlenn...@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-u...@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user ___ grass-user mailing list grass-u...@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user -- Nikos Alexandris | Remote Sensing & Geomatics GPG Key Fingerprint 6F9D4506F3CA28380974D31A9053534B693C4FB3 ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] Can I backport bugfix with UI updates and fixing QGIS Server regression
Hi devs, I have cherry-picked the changes I have tested it without regressions or issues. Now I need some review to merge and fix 2 issues. https://github.com/qgis/QGIS/pull/9692 Regards, René-Luc Le 17/04/2019 à 14:18, René-Luc Dhont a écrit : Hi devs, Thanks Paolo for your agreement. I'd like to fix the QGIS Sever regression before friday and the version 3.4.7 released. So I'd like to have other point of view about backporting : [needs-docs][layouts] Add checkbox to disable raster tiling for PDF/SVG exports https://github.com/qgis/QGIS/pull/9016 and finalizing Fix regression server print selection pdf release 3.4 https://github.com/qgis/QGIS/pull/9692 Thanks. René-Luc Le 12/04/2019 à 12:06, Paolo Cavallini a écrit : Hi René, On 12/04/19 12:05, René-Luc Dhont wrote: I would like to know if I can backport all the commits made by Nyall to fix issue 19500 even if it updates the User Interface ? +1 from my side, but obviously Nyall has the final word on this. Thanks. ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
