Hi Regina,
Thanks so much for the quick response, that did the trick!
-Shane
On Tue, May 2, 2017 at 1:53 PM Regina Obe wrote:
> Shane,
>
>
>
> I've ticketed this issue here: https://trac.osgeo.org/postgis/ticket/3750
>
> Most of these issues related to restore were fixed in PostGIS 2.3, but
>
Shane,
I've ticketed this issue here: https://trac.osgeo.org/postgis/ticket/3750
Most of these issues related to restore were fixed in PostGIS 2.3, but looks
like you found a missed spot.
To fix, you should have a folder in your postgresql install share/extension
with a file called postg
Disregard what I said. I see that the SQL statements I thought mistakenly were
coming from DbManager are generated by GDAL (looking at the GDAL postgis raster
code).
So the change would need to be done in GDAL driver. I think having a PostGIS
function GDAL can count on calling that would
Just to add the bug regarding raster2pgsql will be fixed in upcoming 2.3.3
And the work-around is to use –Y with –s as detailed in the ticket.
https://trac.osgeo.org/postgis/ticket/3738
Regarding the QGIS issue with GDAL not supporting out-db. I've been thinking
that the easier fix
Was a solution to this problem ever discovered? I'm running into exactly
the same problem (backup from PostGIS 2.1 with raster tables can't be
restored to PostGIS 2.3).
HINT: No operator matches the given name and argument type(s). You might
need to add explicit type casts.
QUERY: SELECT $1 @ $2
I think that raster2pgsql is indeed a mature tool, but it is the out-db
feature of postgis
which is maybe not widely used, and so the bugs takes more time to appear
because
of the fewer users.
2017-05-02 12:18 GMT+02:00 :
> Hello Tumasgiu Rossini,
>
>
>
> thank you very much for your fast and com
Hello Tumasgiu Rossini,
thank you very much for your fast and comprehensive response. I was not aware
of that bug yet but found so many references to raster2pgsql that I just
assumed that it was a mature tool already.
(And noted that I gave wrong parameter in the subject line of my mail, should
Hi,
To answer your first question :
the combination of the -s and -R options actually transforms out-db raster
into in-db,
it is a recent known bug, see
https://lists.osgeo.org/pipermail/postgis-users/2017-April/042003.html
for more information.
For the latter question,
Qgis uses gdal to fetch ra
Dear users,
I hope that somebody can tell me if I found a bug or simply don't use the
command correctly.
Given:
* A directory with four GeoTIFF files
* PostgreSQL 9.6.1, compiled by Visual C++ build 1800, 64-bit
* POSTGIS="2.3.1 r15264" GEOS="3.6.0-CAPI-1.10.0 r4265" SFCGAL="1.