[fdo-internals] Disable GEOS support explicitly

[Kenneth, GEOGRAF A/S]

If you remove GEOS from the OGR Provider, it will perform all 
intersection checks as BBOX overlap only.
This will cause bad behavior with both selection and tooltip.

This can be fixed by using the FDO geometry operations instead of the 
OGR which rely on GEOS.

Regards, Kenneth, GEOGRAF A/S



Mateusz Loskot skrev:
> Traian Stanev wrote:
>   
>> The OGR provider likely benefits from OGR having Geos compiled with
>> it. However, the default build for the provider could probably get
>> away without Geos.
>>     
>
> Traian,
>
> Yes, this is what I've been wondering about.
> Although, if we want GEOS support we have to specify in manual/readme
> what version/line is required by GDAL we currently use.
>
> The user having problems I reported compiles GDAL 1.3 and this version
> uses GEOS C++ API. However, he seems to have installed newer version of
> GEOS that includes significant reoragnization of C++ API (new namespaces
> layout).
> Some time ago, GDAL moved to use GEOS C API. This introduced
> requirement of GEOS 2.2.0 or newer.
>
> IOW, we have indirect requirements connection between FDO and GEOS
> version through GDAL version.
>
> Cheers
>   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/fdo-internals/attachments/20071212/18a7c804/attachment.html