Re: [QGIS-Developer] Raster calculator turns lowest row of pixels into nodata

2020-02-11 Thread Rahkonen Jukka (MML)
: Rahkonen Jukka (MML) Kopio: qgis-developer@lists.osgeo.org Aihe: Re: [QGIS-Developer] Raster calculator turns lowest row of pixels into nodata che you check master version, AFAIR, alessandro pasotti fixed this basing on a issue report by Jorge Rocha Luigi Pirelli

[QGIS-Developer] Raster calculator turns lowest row of pixels into nodata

2020-02-10 Thread Rahkonen Jukka (MML)
Hi, See https://gis.stackexchange.com/questions/349531/qgis-zonal-statistics-and-no-data/349559 It seems that raster calculator turns the lowest pixel row of the image that covers the whole world in EPSG:4326 into nodata with value -3.4e+38 which gives troubles afterwards. The original image

[QGIS-Developer] Does QGIS utilize the statistics of cloud optimized GeoTIFF?

2020-01-08 Thread Rahkonen Jukka (MML)
Hi, QGIS is setting the default contrast stretch reasonably If I read a GeoTIFF file from a local file. Statistics are included in the image through the GDAL tags Tag 42112: 0 -10.126687384969 -71.313484191895 9.6992444829123 11.53 However, if I open the same file through http the

[QGIS-Developer] Can't edot OGC API Features connection

2019-11-01 Thread Rahkonen Jukka (MML)
Hi, It seems to me that if I edit the settings of the OGC API Features connection the changes do not have any effect but I must delete and re-create the connection instead. Also, I see a message "The download limit has been reached. You may want to check the 'Only request features overlapping

[QGIS-Developer] Geopackage slow when metadata shows generic geometries

2019-10-11 Thread Rahkonen Jukka (MML)
Hi, Have a look at this question https://gis.stackexchange.com/questions/338478/reading-geopackage-with-large-features-is-very-slow I guess that quite few QGIS users know that such GeoPackages could be made to open much faster. Perhaps QGIS could give a warning and suggest to update the

[QGIS-Developer] OpenLayers 6 and only WGS 84 API

2019-09-05 Thread Rahkonen Jukka (MML)
Hi, I followed the recording from FOSS4G 2019 about the new features in OL 6 https://media.ccc.de/v/bucharest-337-openlayers-6-there-and-back-again. At time 16:35 there is a slide that states "Use only geographic coordinates (WGS 84) in the API". I wonder if such change would make it difficult