Dear Colleagues, Patrick,
thanks, this is a VERY relevant issue, and might be the future concept for
GIS, of sorts (=more data volumes).
While I have no direct answer to your architecture question (sorry),
I have a sample dataset and application on the topic and can share it with
people as they se
Hello,
the issue is not with the performance drawing the raster, it is with the
system only being able to have a certain number of file based rasters
loaded in a project before it will crash.
On 22/11/19 11:08 AM, Alexandre Neto wrote:
AFAIK,
WMST creates pyramids in cache as needed, hence
AFAIK,
WMST creates pyramids in cache as needed, hence it may do a better balance
between disk usage and performance. You can control the number of pyramid
layers you create and the compression format of it to save some space. But
having raster files with 4000x4000 pixels with no pyramids will mak
Building pyramids gobbles up heaps of disk space. I tried pyramids on
157 MB layer, which created an extra file 1.6 GiB.
I can't see the WMTS building lots of temporary file pyramids using up disk
On 18/11/19 10:50 PM, Alexandre Neto wrote:
Hi Patrick,
Sorry for asking, did you create pyramid
Hi Patrick,
Sorry for asking, did you create pyramids (overlays) for your raster
"tiles"?
See more information about pyramids on QGIS official documentation:
https://docs.qgis.org/3.4/en/docs/user_manual/working_with_raster/raster_properties.html#pyramids-properties
To create pyramids on many f
