Re: [gdal-announce] GDAL Support For PostGIS Out-DB Raster

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
13 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: [gdal-announce] GDAL Support For PostGIS Out-DB Raster

Even Rouault-2
Moving the discussion to gdal-dev

> Please, I wanted to find out if there is any ongoing work towards providing
> GDAL support for PostGIS Out-DB rasters. I have been in touch with both
> Postgres and QGIS and I was told that it is a limitation from GDAL.
>
> Is there any plan to implement this feature?

Yes, I should work on this in the coming weeks.

Even

--
Spatialys - Geospatial professional services
http://www.spatialys.com
_______________________________________________
gdal-dev mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/gdal-dev
Reply | Threaded
Open this post in threaded view
|

Re: [gdal-announce] GDAL Support For PostGIS Out-DB Raster

Osahon Oduware
Hi Even,

This is great news. I cannot wait for this feature to be implemented as it prevents double storage of rasters (database and filesystem).

On Wed, Mar 21, 2018 at 4:18 PM, Even Rouault <[hidden email]> wrote:
Moving the discussion to gdal-dev

> Please, I wanted to find out if there is any ongoing work towards providing
> GDAL support for PostGIS Out-DB rasters. I have been in touch with both
> Postgres and QGIS and I was told that it is a limitation from GDAL.
>
> Is there any plan to implement this feature?

Yes, I should work on this in the coming weeks.

Even

--
Spatialys - Geospatial professional services
http://www.spatialys.com


_______________________________________________
gdal-dev mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/gdal-dev
Reply | Threaded
Open this post in threaded view
|

Re: [gdal-announce] GDAL Support For PostGIS Out-DB Raster

Osahon Oduware
Hi Even,

Any update on this? I have been away for a while.

Best Regards

On Mar 21, 2018 16:32, "Osahon Oduware" <[hidden email]> wrote:
Hi Even,

This is great news. I cannot wait for this feature to be implemented as it prevents double storage of rasters (database and filesystem).

On Wed, Mar 21, 2018 at 4:18 PM, Even Rouault <[hidden email]> wrote:
Moving the discussion to gdal-dev

> Please, I wanted to find out if there is any ongoing work towards providing
> GDAL support for PostGIS Out-DB rasters. I have been in touch with both
> Postgres and QGIS and I was told that it is a limitation from GDAL.
>
> Is there any plan to implement this feature?

Yes, I should work on this in the coming weeks.

Even

--
Spatialys - Geospatial professional services
http://www.spatialys.com


_______________________________________________
gdal-dev mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/gdal-dev
Reply | Threaded
Open this post in threaded view
|

Re: [gdal-announce] GDAL Support For PostGIS Out-DB Raster

Osahon Oduware
In reply to this post by Osahon Oduware
Hi Even,

Any update on this? I have been away for a while.

Best Regards

On Mar 21, 2018 16:32, "Osahon Oduware" <[hidden email]> wrote:
Hi Even,

This is great news. I cannot wait for this feature to be implemented as it prevents double storage of rasters (database and filesystem).

On Wed, Mar 21, 2018 at 4:18 PM, Even Rouault <[hidden email]> wrote:
Moving the discussion to gdal-dev

> Please, I wanted to find out if there is any ongoing work towards providing
> GDAL support for PostGIS Out-DB rasters. I have been in touch with both
> Postgres and QGIS and I was told that it is a limitation from GDAL.
>
> Is there any plan to implement this feature?

Yes, I should work on this in the coming weeks.

Even

--
Spatialys - Geospatial professional services
http://www.spatialys.com


_______________________________________________
gdal-dev mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/gdal-dev
Reply | Threaded
Open this post in threaded view
|

Re: [gdal-announce] GDAL Support For PostGIS Out-DB Raster

Even Rouault-2
On jeudi 31 mai 2018 20:04:58 CEST Osahon Oduware wrote:
> Hi Even,
>
> Any update on this? I have been away for a while.

Yep, support for out-db raster has been added in GDAL master, and backported
to 2.3 branch as well

See outdb_resolution option in http://gdal.org/frmt_postgisraster.html

2 new functions added to PostGIS 2.5dev as well to help reading the out-db
raster directly from client-side if client and server see the same raster.

--
Spatialys - Geospatial professional services
http://www.spatialys.com
_______________________________________________
gdal-dev mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/gdal-dev
Reply | Threaded
Open this post in threaded view
|

Re: [gdal-announce] GDAL Support For PostGIS Out-DB Raster

Osahon Oduware
Hi Even,

Thanks for the prompt response. Please, I want to know what is the minimum version of GDAL, PostgreSQL and Postgis that this outdb raster functionality is currently implemented.

Best Regards

On May 31, 2018 20:13, "Even Rouault" <[hidden email]> wrote:
On jeudi 31 mai 2018 20:04:58 CEST Osahon Oduware wrote:
> Hi Even,
>
> Any update on this? I have been away for a while.

Yep, support for out-db raster has been added in GDAL master, and backported
to 2.3 branch as well

See outdb_resolution option in http://gdal.org/frmt_postgisraster.html

2 new functions added to PostGIS 2.5dev as well to help reading the out-db
raster directly from client-side if client and server see the same raster.

--
Spatialys - Geospatial professional services
http://www.spatialys.com

_______________________________________________
gdal-dev mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/gdal-dev
Reply | Threaded
Open this post in threaded view
|

Re: [gdal-announce] GDAL Support For PostGIS Out-DB Raster

Even Rouault-2
On jeudi 31 mai 2018 21:35:30 CEST Osahon Oduware wrote:
> Hi Even,
>
> Thanks for the prompt response. Please, I want to know what is the minimum
> version of GDAL,
no released version yet. Will be in 2.3.1 (end of June probably) and 2.4.0
(next year)
> PostgreSQL
irrelevant. Any PostgreSQL version supported by the PostGIS version you use is
fine
> and Postgis
will be in Postgis 2.5.0. But not strictly needed. Existing versions will work
too

> that this outdb raster
> functionality is currently implemented.
>
> Best Regards
>
> On May 31, 2018 20:13, "Even Rouault" <[hidden email]> wrote:
> > On jeudi 31 mai 2018 20:04:58 CEST Osahon Oduware wrote:
> > > Hi Even,
> > >
> > > Any update on this? I have been away for a while.
> >
> > Yep, support for out-db raster has been added in GDAL master, and
> > backported
> > to 2.3 branch as well
> >
> > See outdb_resolution option in http://gdal.org/frmt_postgisraster.html
> >
> > 2 new functions added to PostGIS 2.5dev as well to help reading the out-db
> > raster directly from client-side if client and server see the same raster.
> >
> > --
> > Spatialys - Geospatial professional services
> > http://www.spatialys.com


--
Spatialys - Geospatial professional services
http://www.spatialys.com
_______________________________________________
gdal-dev mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/gdal-dev
Reply | Threaded
Open this post in threaded view
|

Re: [gdal-announce] GDAL Support For PostGIS Out-DB Raster

Osahon Oduware
Ok, thanks a lot for the information. Great work.

On May 31, 2018 21:39, "Even Rouault" <[hidden email]> wrote:
On jeudi 31 mai 2018 21:35:30 CEST Osahon Oduware wrote:
> Hi Even,
>
> Thanks for the prompt response. Please, I want to know what is the minimum
> version of GDAL,
no released version yet. Will be in 2.3.1 (end of June probably) and 2.4.0
(next year)
> PostgreSQL
irrelevant. Any PostgreSQL version supported by the PostGIS version you use is
fine
> and Postgis
will be in Postgis 2.5.0. But not strictly needed. Existing versions will work
too

> that this outdb raster
> functionality is currently implemented.
>
> Best Regards
>
> On May 31, 2018 20:13, "Even Rouault" <[hidden email]> wrote:
> > On jeudi 31 mai 2018 20:04:58 CEST Osahon Oduware wrote:
> > > Hi Even,
> > >
> > > Any update on this? I have been away for a while.
> >
> > Yep, support for out-db raster has been added in GDAL master, and
> > backported
> > to 2.3 branch as well
> >
> > See outdb_resolution option in http://gdal.org/frmt_postgisraster.html
> >
> > 2 new functions added to PostGIS 2.5dev as well to help reading the out-db
> > raster directly from client-side if client and server see the same raster.
> >
> > --
> > Spatialys - Geospatial professional services
> > http://www.spatialys.com


--
Spatialys - Geospatial professional services
http://www.spatialys.com

_______________________________________________
gdal-dev mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/gdal-dev
Reply | Threaded
Open this post in threaded view
|

Re: [gdal-announce] GDAL Support For PostGIS Out-DB Raster

Osahon Oduware
In reply to this post by Even Rouault-2
Hi Even,

I want to find out if this GDAL fix will be release by the end of June. I use PostGIS version 2.3.2 at present and I will be building from source.

On Thu, May 31, 2018 at 9:39 PM, Even Rouault <[hidden email]> wrote:
On jeudi 31 mai 2018 21:35:30 CEST Osahon Oduware wrote:
> Hi Even,
>
> Thanks for the prompt response. Please, I want to know what is the minimum
> version of GDAL,
no released version yet. Will be in 2.3.1 (end of June probably) and 2.4.0
(next year)
> PostgreSQL
irrelevant. Any PostgreSQL version supported by the PostGIS version you use is
fine
> and Postgis
will be in Postgis 2.5.0. But not strictly needed. Existing versions will work
too

> that this outdb raster
> functionality is currently implemented.
>
> Best Regards
>
> On May 31, 2018 20:13, "Even Rouault" <[hidden email]> wrote:
> > On jeudi 31 mai 2018 20:04:58 CEST Osahon Oduware wrote:
> > > Hi Even,
> > >
> > > Any update on this? I have been away for a while.
> >
> > Yep, support for out-db raster has been added in GDAL master, and
> > backported
> > to 2.3 branch as well
> >
> > See outdb_resolution option in http://gdal.org/frmt_postgisraster.html
> >
> > 2 new functions added to PostGIS 2.5dev as well to help reading the out-db
> > raster directly from client-side if client and server see the same raster.
> >
> > --
> > Spatialys - Geospatial professional services
> > http://www.spatialys.com


--
Spatialys - Geospatial professional services
http://www.spatialys.com


_______________________________________________
gdal-dev mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/gdal-dev
Reply | Threaded
Open this post in threaded view
|

Re: [gdal-announce] GDAL Support For PostGIS Out-DB Raster

Even Rouault-2
On lundi 25 juin 2018 10:18:22 CEST Osahon Oduware wrote:
> Hi Even,
>
> I want to find out if this GDAL fix will be release by the end of June. I
> use PostGIS version 2.3.2 at present and I will be building from source.

Yes, this is in the release notes of the release candidate of GDAL 2.3.1 that
was published last Friday:
https://trac.osgeo.org/gdal/wiki/Release/2.3.1-News

--
Spatialys - Geospatial professional services
http://www.spatialys.com
_______________________________________________
gdal-dev mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/gdal-dev
Reply | Threaded
Open this post in threaded view
|

Re: [gdal-announce] GDAL Support For PostGIS Out-DB Raster

Osahon Oduware
Hi Even,

Thanks a lot. This is great news! I will start investigating the fix for Out-DB rasters. I will keep you posted. Great work!

On Mon, Jun 25, 2018 at 10:26 AM, Even Rouault <[hidden email]> wrote:
On lundi 25 juin 2018 10:18:22 CEST Osahon Oduware wrote:
> Hi Even,
>
> I want to find out if this GDAL fix will be release by the end of June. I
> use PostGIS version 2.3.2 at present and I will be building from source.

Yes, this is in the release notes of the release candidate of GDAL 2.3.1 that
was published last Friday:
https://trac.osgeo.org/gdal/wiki/Release/2.3.1-News

--
Spatialys - Geospatial professional services
http://www.spatialys.com


_______________________________________________
gdal-dev mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/gdal-dev
Reply | Threaded
Open this post in threaded view
|

Re: [gdal-announce] GDAL Support For PostGIS Out-DB Raster

Osahon Oduware
Hi Even,

I was trying to build GDAL 2.3.1 from source into PostgreSQL 9.6.9 that was built successfully from source, but I am getting an error when running "make -j8" (see attachment)

I ran "./configure" successfully with this statement:
./configure --prefix=/home/nagispg/local/gdal213 --with-pg=/home/nagispg/local/pgsql/bin/pg_config --with-mrsid=/home/nagispg/local/src/MrSID_DSDK-9.5.4.4703-rhel6.x86-64.gcc531/Raster_DSDK

Then I try to run "Make -j8" and I get an error extracted below (see attachment for more detailed error):
/bin/ld: warning: libpq.so.5, needed by /home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so, not found (try using -rpath or -rpath-link)
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `lo_open'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQputCopyEnd'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQresultErrorMessage'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQstatus'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQsetNoticeProcessor'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQnfields'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQgetvalue'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQclear'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQgetlength'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQfmod'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQftablecol'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQconnectdb'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQcmdStatus'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQftable'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQntuples'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQexecParams'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQfname'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQfinish'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `lo_close'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQerrorMessage'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `lo_read'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQputCopyData'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `lo_write'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQgetResult'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQgetisnull'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQescapeStringConn'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQexec'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `lo_creat'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQsetClientEncoding'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQftype'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQresultStatus'
collect2: error: ld returned 1 exit status
make[1]: *** [gdalserver] Error 1

Please, could you point me to the likely cause of this error. I look forward to hearing from you.


On Mon, Jun 25, 2018 at 12:43 PM, Osahon Oduware <[hidden email]> wrote:
Hi Even,

Thanks a lot. This is great news! I will start investigating the fix for Out-DB rasters. I will keep you posted. Great work!

On Mon, Jun 25, 2018 at 10:26 AM, Even Rouault <[hidden email]> wrote:
On lundi 25 juin 2018 10:18:22 CEST Osahon Oduware wrote:
> Hi Even,
>
> I want to find out if this GDAL fix will be release by the end of June. I
> use PostGIS version 2.3.2 at present and I will be building from source.

Yes, this is in the release notes of the release candidate of GDAL 2.3.1 that
was published last Friday:
https://trac.osgeo.org/gdal/wiki/Release/2.3.1-News

--
Spatialys - Geospatial professional services
http://www.spatialys.com



_______________________________________________
gdal-dev mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/gdal-dev

Error.txt (12K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [gdal-announce] GDAL Support For PostGIS Out-DB Raster

Osahon Oduware
Hi All,

Can anyone help with the error in my previous mail?

On Jun 26, 2018 12:39 PM, "Osahon Oduware" <[hidden email]> wrote:
Hi Even,

I was trying to build GDAL 2.3.1 from source into PostgreSQL 9.6.9 that was built successfully from source, but I am getting an error when running "make -j8" (see attachment)

I ran "./configure" successfully with this statement:
./configure --prefix=/home/nagispg/local/gdal213 --with-pg=/home/nagispg/local/pgsql/bin/pg_config --with-mrsid=/home/nagispg/local/src/MrSID_DSDK-9.5.4.4703-rhel6.x86-64.gcc531/Raster_DSDK

Then I try to run "Make -j8" and I get an error extracted below (see attachment for more detailed error):
/bin/ld: warning: libpq.so.5, needed by /home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so, not found (try using -rpath or -rpath-link)
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `lo_open'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQputCopyEnd'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQresultErrorMessage'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQstatus'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQsetNoticeProcessor'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQnfields'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQgetvalue'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQclear'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQgetlength'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQfmod'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQftablecol'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQconnectdb'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQcmdStatus'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQftable'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQntuples'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQexecParams'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQfname'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQfinish'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `lo_close'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQerrorMessage'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `lo_read'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQputCopyData'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `lo_write'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQgetResult'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQgetisnull'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQescapeStringConn'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQexec'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `lo_creat'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQsetClientEncoding'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQftype'
/home/nagispg/local/src/gdal-2.3.1/.libs/libgdal.so: undefined reference to `PQresultStatus'
collect2: error: ld returned 1 exit status
make[1]: *** [gdalserver] Error 1

Please, could you point me to the likely cause of this error. I look forward to hearing from you.


On Mon, Jun 25, 2018 at 12:43 PM, Osahon Oduware <[hidden email]> wrote:
Hi Even,

Thanks a lot. This is great news! I will start investigating the fix for Out-DB rasters. I will keep you posted. Great work!

On Mon, Jun 25, 2018 at 10:26 AM, Even Rouault <[hidden email]> wrote:
On lundi 25 juin 2018 10:18:22 CEST Osahon Oduware wrote:
> Hi Even,
>
> I want to find out if this GDAL fix will be release by the end of June. I
> use PostGIS version 2.3.2 at present and I will be building from source.

Yes, this is in the release notes of the release candidate of GDAL 2.3.1 that
was published last Friday:
https://trac.osgeo.org/gdal/wiki/Release/2.3.1-News

--
Spatialys - Geospatial professional services
http://www.spatialys.com



_______________________________________________
gdal-dev mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/gdal-dev