[gdal-dev] gdal 3.11 vector pipeline with postgres problems

Daniel Baston dbaston at gmail.com
Sat Apr 26 13:18:07 PDT 2025


Hi Rich,

This is a bug -- the "read" step does not exclusively pass GDAL_OF_VECTOR
to GDALOpen, so it attempts to read raster layers from the input. I've made
one possible fix at https://github.com/OSGeo/gdal/pull/12203.

Dan

On Sat, Apr 26, 2025 at 2:14 PM Richard Greenwood via gdal-dev <
gdal-dev at lists.osgeo.org> wrote:

> Below works:
> *$ gdal vector info PG:"$PGCONN" -l "roads"*
>
> And this works:
> *$ gdal vector convert PG:"$PGCONN" -l "roads" junk*
>
> But below fails (I'm using pipeline because I need an intermediate step
> once I get this to work). I do not have the postgis_raster extension in
> this database.
>
>
>
>
> *$ gdal vector pipeline read PG:"$PGCONN" -l "roads" ! write junkERROR 1:
> Error browsing database for PostGIS Raster tables: ERROR 1: Error browsing
> database for PostGIS Raster tables: Usage: gdal vector pipeline [OPTIONS]
> <PIPELINE>Try 'gdal vector pipeline --help' for help.*
>
> I created the postgis_raster extension and ran the same pipeline:
>
> *$ gdal vector pipeline read PG:"$PGCONN" -l "roads" ! write junkERROR 1:
> read: Cannot find source layer 'roads'*
>
> It seems like requiring the postgis_raster extension is a bug.
> What about the *Cannot find source layer*? I fiddled with specifying the
> schema, different quoting, etc.
>
> Thanks
> --
> Richard W. Greenwood
>
> _______________________________________________
> gdal-dev mailing list
> gdal-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/gdal-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20250426/9c4e0442/attachment.htm>


More information about the gdal-dev mailing list