<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
If you remove GEOS from the OGR Provider, it will perform all
intersection checks as BBOX overlap only.<br>
This will cause bad behavior with both selection and tooltip.<br>
<br>
This can be fixed by using the FDO geometry operations instead of the
OGR which rely on GEOS.<br>
<pre class="moz-signature" cols="72">Regards, Kenneth, GEOGRAF A/S
</pre>
<br>
<br>
Mateusz Loskot skrev:
<blockquote cite="mid:475F3A67.6090600@loskot.net" type="cite">
<pre wrap="">Traian Stanev wrote:
</pre>
<blockquote type="cite">
<pre wrap="">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.
</pre>
</blockquote>
<pre wrap=""><!---->
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
</pre>
</blockquote>
</body>
</html>