RE: [mapguide-users] Postgis & OGR provide

2009-01-27 Thread Traian Stanev


PostGIS support was not dropped from the provider. The default build of the OGR 
provider now dynamically links to the GDAL/OGR dlls, unlike before when I did a 
static link against my own build of OGR, with PostGIS support enabled.

If your GDAL build has PostGIS support, it *should* also work in the OGR 
provider. However, I don't think the pre-built GDAL dll that comes with FDO is 
compiled with PostGIS support.

Traian


-Original Message-
From: mapguide-users-boun...@lists.osgeo.org 
[mailto:mapguide-users-boun...@lists.osgeo.org] On Behalf Of Gabriele Monfardini
Sent: Tuesday, January 27, 2009 2:43 PM
To: MapGuide Users Mail List
Subject: Re: [mapguide-users] Postgis & OGR provide

We've made some investigations on this issue.

It appears that in latest precompilated Windows binaries OGR support
for Postgresql (that has to be enabled at compile time) was dropped in
favor of the new Postgis provider.
Probably this also happens in OGR provider compiled under GNU/Linux.
Error messages don't help much to understand.
Maybe you can check your OGR provider dynamic libraries with ldd to
find unresolved symbols.

Postgis provider seems to need a fairly recent version of Postgresql
header in order to work (it works in Windows against Postgresql
8.2.10, it does not against Postgresql 8.1.15)
We're trying to compile the Postgis provider under Debian etch
(stable), using newer packages from lenny (testing) when needed.

The problem is that compiling flags force build to go until the end
even if some symbols are unresolved. And this is how we've find that
the new postgis provider needs a recent postgresql version.

If you find something new please report me.

Gabriele




On Wed, Jan 21, 2009 at 01:24, shad0wsong  wrote:
>
> I'm having the exact same problem, except im running CentOS 4 (RHEL4
> compatible)
>
> The exception im getting is a "Connection Failed" with no more details than
> that.
>
> Has anyone resolved this issue?
>
> Thank you!
>
>
> Gabriele Monfardini wrote:
>>
>> Hi all,
>>
>> We're having problems using PostGIS and OGR provider.
>>
>> We've built MGOS 2.0.1 and fdo-3.3.0 in Ubuntu 7.10 without errors,
>> but neither PostGIS provider, neither OGR provider works correctly.
>> They always throw some exceptions when I try to connect to any
>> PostgreSQL + PostGIS db.
>>
>> Under MGOS 1.2 OGR provider works fine with the same data.
>>
>> Does anyone use PostGIS with MGOS 2.0.1 and fdo-3.3.0? With which
>> provider? Using the binary or compiling all from the source?
>>
>>
>> Thanks,
>>
>> Gabriele
>> ___
>> mapguide-users mailing list
>> mapguide-users@lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/mapguide-users
>>
>>
>
> --
> View this message in context: 
> http://n2.nabble.com/Postgis---OGR-provider-tp1816487p2189744.html
> Sent from the MapGuide Users mailing list archive at Nabble.com.
>
> ___
> mapguide-users mailing list
> mapguide-users@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-users
>
___
mapguide-users mailing list
mapguide-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-users
___
mapguide-users mailing list
mapguide-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-users


Re: [mapguide-users] Postgis & OGR provide

2009-01-27 Thread Gabriele Monfardini
We've made some investigations on this issue.

It appears that in latest precompilated Windows binaries OGR support
for Postgresql (that has to be enabled at compile time) was dropped in
favor of the new Postgis provider.
Probably this also happens in OGR provider compiled under GNU/Linux.
Error messages don't help much to understand.
Maybe you can check your OGR provider dynamic libraries with ldd to
find unresolved symbols.

Postgis provider seems to need a fairly recent version of Postgresql
header in order to work (it works in Windows against Postgresql
8.2.10, it does not against Postgresql 8.1.15)
We're trying to compile the Postgis provider under Debian etch
(stable), using newer packages from lenny (testing) when needed.

The problem is that compiling flags force build to go until the end
even if some symbols are unresolved. And this is how we've find that
the new postgis provider needs a recent postgresql version.

If you find something new please report me.

Gabriele




On Wed, Jan 21, 2009 at 01:24, shad0wsong  wrote:
>
> I'm having the exact same problem, except im running CentOS 4 (RHEL4
> compatible)
>
> The exception im getting is a "Connection Failed" with no more details than
> that.
>
> Has anyone resolved this issue?
>
> Thank you!
>
>
> Gabriele Monfardini wrote:
>>
>> Hi all,
>>
>> We're having problems using PostGIS and OGR provider.
>>
>> We've built MGOS 2.0.1 and fdo-3.3.0 in Ubuntu 7.10 without errors,
>> but neither PostGIS provider, neither OGR provider works correctly.
>> They always throw some exceptions when I try to connect to any
>> PostgreSQL + PostGIS db.
>>
>> Under MGOS 1.2 OGR provider works fine with the same data.
>>
>> Does anyone use PostGIS with MGOS 2.0.1 and fdo-3.3.0? With which
>> provider? Using the binary or compiling all from the source?
>>
>>
>> Thanks,
>>
>> Gabriele
>> ___
>> mapguide-users mailing list
>> mapguide-users@lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/mapguide-users
>>
>>
>
> --
> View this message in context: 
> http://n2.nabble.com/Postgis---OGR-provider-tp1816487p2189744.html
> Sent from the MapGuide Users mailing list archive at Nabble.com.
>
> ___
> mapguide-users mailing list
> mapguide-users@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-users
>
___
mapguide-users mailing list
mapguide-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-users