[GRASS-dev] Export from GRASS to Postgres

[Martin Landa]

[please don't send me private mails, keep the communication on ML,
please don't ignore it!]

2013/4/5 suprakash maitra <suprakashmaitra at yahoo.com>:

> [root at lab35 grass-6.4.2]#./configure
> --with-postgres-includes=/opt/PostgreSQL/9.1/include
> --with-postgres-libs=/opt/PostgreSQL/9.1/lib
> --with-freetype-includes=/usr/include/freetype2
> --with-freetype-libs=/usr/lib --with-cxx --with-python --with-fftw
> --with-freetype --with-gdal=/usr/local/bin/gdal-config --with-postgres
>
> GRASS is installed and configured with postgres

As I noted *earlier*, v.out.ogr is using OGR library to export data to
PostgreSQL/PostGIS. So it's not related to this problem.

> then
> [root at lab35 gdal-1.8.1]#./configure
> --with-grass=/usr/local/grass-6.4.2/dist.i686-pc-linux-gnu
> --with-libgrass=/usr/local/grass-6.4.2/dist.i686-pc-linux-gnu/lib
> --with-pg=/opt/PostgreSQL/9.1/bin/pg_config
>
> gdal is configured with grass and postgres

You don't need to compile GDAL with GRASS support, unless you want use
OGR GRASS driver [1]. None of r.[in|out].gdal and v.[in|out].ogr
modules do not use this driver.

> after that I have got the output with the command:
>
>
> $ ogrinfo --formats | grep PostgreSQL
>   -> "PostgreSQL" (read/write)
>
> Even then the format "PostgreSQL" is not supported.

Are you sure that you compile GRASS against the same GDAL/OGR version.
It could be that you have more GDAL/OGR installations on your machine.

Martin

[1] http://gdal.org/ogr/drv_grass.html

--
Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa