Re: [Qgis-developer] PostGIS Rasters

Hi, Back end-repo is from here: https://download.postgresql.org/pub/repos/yum/9.6/redhat/rhel-7-x86_64/pgdg-centos96-9.6-3.noarch.rpm The front end is windows: QGIS-OSGeo4W-2.18.6-1-Setup-x86_64.exe Output from ver is: Microsoft Windows [Version 6.1.7601] On Tue, Apr 11, 2017 at 9:59 AM,

Re: [Qgis-developer] Qgis-developer Digest, Vol 138, Issue 36

> Date: Tue, 11 Apr 2017 04:41:32 -0700 (MST) > From: Tom Chadwin > > Yes, I mean that all models are made up of discrete algorithms, and those > algorithms will only really work as intended if chained together as in the > model. Nevertheless, the algorithms will appear

Re: [Qgis-developer] PostGIS Rasters

Hi Robert Just a little of topic question. Your centos install for Postgres etc, is that only using Postgres Yum repo? Your QGIS frontend, is that also Centos? Pieter On Tue, Apr 11, 2017 at 6:27 PM, Robert Hewlett wrote: > Hi, > > Quick test results. Attached are the

Re: [Qgis-developer] PostGIS Rasters

Hi Rob, Thanks for testing. Good to know that pyramids now work fine with postgis raster. It was a while back since I last tested. If you can log the SQL queries on the server by increasing the logging level, than it you can prove which tables QGIS is querying. Andreas On 2017-04-11 15:29,

Re: [Qgis-developer] PostGIS Rasters

Hi, I am using 2.18.5. and the performance seems okay to good. The ortho data in the DB are tiled and have overviews built. When working with the data within QGIS it seems that the overviews are 'in play'. I will see if I can write some SQL to prove one way or the other. The test vm on the

Re: [Qgis-developer] Set processing input default value to layer custom property

11.04.2017, 14:41, Tom Chadwin kirjoitti: Yes, I mean that all models are made up of discrete algorithms, and those algorithms will only really work as intended if chained together as in the model. Nevertheless, the algorithms will appear in the Processing toolbox, so users could try to use them

Re: [Qgis-developer] Are there plans to create a unique "Add layer" tool?

Hi Alexandre this is indeed great! Is the gdoc as it is now helpful enough for you to design a possible implementation? Or, if not, what other inputs / comments would be necessary? Cheers Stéphane Le lundi 10 avril 2017, Alexandre Neto a écrit : > Hello all, > > At

Re: [Qgis-developer] Set processing input default value to layer custom property

Yes, I mean that all models are made up of discrete algorithms, and those algorithms will only really work as intended if chained together as in the model. Nevertheless, the algorithms will appear in the Processing toolbox, so users could try to use them in isolation, and have difficulty forming

Re: [Qgis-developer] PostGIS Rasters

Hi Andreas, The QGIS performance reading rasters from Postgis is not so bad, if pyramids are available on the database. QGIS takes advantage of the pyramids, if they exist. Check [1]. Regards, Jorge [1]

Re: [Qgis-developer] Set processing input default value to layer custom property

11.04.2017, 11:50, Tom Chadwin kirjoitti: Hi Ari What a great idea. Thank you. I guess the one downside is that it means the main algorithm will not function on its own, so you have to rely on documentation to inform the user not to try to use it without your preprocessor? By main algorithm

Re: [Qgis-developer] Set processing input default value to layer custom property

Hi Ari What a great idea. Thank you. I guess the one downside is that it means the main algorithm will not function on its own, so you have to rely on documentation to inform the user not to try to use it without your preprocessor? Thanks again Tom - Buy Pie Spy: Adventures in British

Re: [Qgis-developer] Set processing input default value to layer custom property

I have a small processing model where one of the algorithms is Rasterize from GDAL. I needed to set the target resolution to be the same as the one in one of the input rasters to the model. The problem was thus the same as yours. My solution was to write a very simple processor, which takes