There will probably be a GDAL 2.3.1 release with this
fix at end of june / july. And assuming OSGeo4W
catches this, this will be available to QGIS
--
Spatialys - Geospatial professional services
http://www.spatialys.com
___
QGIS-Developer mailing
Anyone know of the approximate timeframe for a commit to GDAL master and 2.3
branch will be available in a QGIS release?
Thanks Jakob
-
Jakob Lanstorp
--
Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html
___
Il 19/05/2018 11:40, Even Rouault ha scritto:
>> e.g. https://issues.qgis.org/issues/18054
>
>
>
> Cannot reproduce. Perhaps another issue
so possibly better close it.
>> https://issues.qgis.org/issues/8073
>
>
>
> That one was exactly what I fixed. Closed
thanks a lot Even
All the best
On vendredi 18 mai 2018 13:08:56 CEST Paolo Cavallini wrote:
> Il 17/05/2018 19:25, Even Rouault ha scritto:
> > Jakob,
> >
> >
> >
> > This is a limitation of the GDAL PostgisRaster client driver that I'm
> > currently working on. The enhancement to support out-of-db rasters in
> > the driver
Il 17/05/2018 19:25, Even Rouault ha scritto:
> Jakob,
>
>
>
> This is a limitation of the GDAL PostgisRaster client driver that I'm
> currently working on. The enhancement to support out-of-db rasters in
> the driver should land in GDAL master in a few hours.
Good news, thanks Even. There
Jakob,
This is a limitation of the GDAL PostgisRaster client driver that I'm
currently working on. The enhancement to support out-of-db rasters
in the driver should land in GDAL master in a few hours.
Even
--
Spatialys - Geospatial professional services
http://www.spatialys.com
I load a geotiff with raster2pgsql with the -R param for having an out of db
stored raster in PostGIS.
The raster renders in QGIS through the DB Manager as a black box with no
values. Running a raster layer statistics in QGIS returns 0 for all values.
I have tried loading the raster as a in-db
