Hi Even
On Fri, Apr 28, 2017 at 1:40 PM, Even Rouault
wrote:
>
> Heck, latest GeoServer still using such an ancient version of GDAL... Or
> perhaps the doc is not up-to-date.
>
I have this doubt as well, that is why I sent an email to the
geoserver list. Let's see what it comes out.
https://sour
On vendredi 28 avril 2017 10:13:41 CEST Paolo Corti wrote:
> Hi Even
>
> On Fri, Apr 28, 2017 at 4:13 AM, Even Rouault
>
> wrote:
> > Yes much likely this error is typical of a mismatch between SWIG 1.3 and
> > SWIG 2 or 3. It is likely that the gdal.jar in GeoServer was produced with
> > SWIG 1
Hi,
I've issued a release candidate for GDAL 2.2.0
The source is available at:
http://download.osgeo.org/gdal/2.2.0/gdal-2.2.0RC1.tar.xz
http://download.osgeo.org/gdal/2.2.0/gdal-2.2.0RC1.tar.gz
http://download.osgeo.org/gdal/2.2.0/gdal220RC1.zip
A snapshot of the Python autotest su
Hi Even
On Fri, Apr 28, 2017 at 4:13 AM, Even Rouault
wrote:
> Yes much likely this error is typical of a mismatch between SWIG 1.3 and
> SWIG 2 or 3. It is likely that the gdal.jar in GeoServer was produced with
> SWIG 1.3, so you'll need to generate the native part (libgdalconstjni.so,
> etc...
Hi Mateusz,
Thanks for your response. I would like to know how to display out-db
rasters in QGIS without the use of GDAL.
On Fri, Apr 28, 2017 at 2:57 PM, Mateusz Loskot wrote:
> On 28 April 2017 at 15:53, Osahon Oduware wrote:
> > I would like to know if out-db rasters remain unsupported by G
On 28 April 2017 at 15:53, Osahon Oduware wrote:
> I would like to know if out-db rasters remain unsupported by GDAL.
You have already got this answered by Even, see
https://lists.osgeo.org/pipermail/gdal-dev/2017-April/046512.html
> If yes, how do one solve this issue of displaying out-db raste
Hi All,
I am getting a black image when I try to display PostGIS out-db rasters. I
discovered that it has to do with GDAL support for out-db rasters as stated
in the link below for a similar issue (over 1 year back):
https://hub.qgis.org/issues/12133
The last comment by Jürgen Fischer states "...
Paolo,
> I am wondering if this could be caused by the SWIG version which I am using?
Yes much likely this error is typical of a mismatch between SWIG 1.3 and SWIG 2
or 3. It is
likely that the gdal.jar in GeoServer was produced with SWIG 1.3, so you'll
need to
generate the native part (libgd
