Opened 15 years ago

Closed 14 years ago

#3100 closed defect (worksforme)

Error TopologyException when using Personal geodatabase data source

Reported by: heijo Owned by: warmerdam
Priority: high Milestone:
Component: OGR Support Version: 5.2
Severity: critical Keywords: OGR msOGRFileNextShape TopologyException
Cc: dmorissette, jmckenna

Description

Data source: Personal geodatabase (.mdb file), connect through OGR

Issue: Some time when interactive with map (zoom, pan), this fatal error show: msOGRFileNextShape(): OGR error. TopologyException: side location conflict...

Maybe the mapping engine takes notice of the consistency of the geometries!

Change History (7)

comment:1 by dmorissette, 15 years ago

Cc: dmorissette added
Owner: changed from dmorissette to warmerdam

Frank summed up this issue fairly well on the mapserver-users list. As Frank wrote, we would need a testcase (sample data, mapfile, etc.) to reproduce the issue otherwise we can't help:

I believe this error is coming from GEOS and likely occurs when the geometries
from the file are translated into GEOS format in order to do a spatial
comparison test against the map view within OGR.

This likely is due to a linestring or polygon being invalid - perhaps due
to self-intersection.

Actually, I'm surprised that things would dip into the GEOS geometry
comparisons. MapServer is careful to only set rectangular spatial filters
and OGR is supposed to short circuit this case to avoid GEOS.  I'm not really
sure why you end up in GEOS.  Are you doing any other fancy stuff that
might end up in GEOS?

If you could boil this down to something similar I could use to reproduce
the problem, I would be willing to have Chaitanya look into it.  It would
need to be filed as a GDAL ticket.

comment:2 by dmorissette, 15 years ago

Milestone: 5.2.1 release5.6.0 release

comment:3 by jmckenna, 15 years ago

Cc: jmckenna added

comment:4 by warmerdam, 14 years ago

I believe we need some very specific details to reproduce this, including a file, map and a specific url that demonstrates the problem - ideally with a known build such as from MS4W or OSGeo4W.

For the reasons expressed on list, I do think this may indicate a real MapServer issue (complex geos operations getting invoked when I would not expect) so I'd like to try and address this in time for 5.6 release if we can get information on reproducing it.

comment:5 by warmerdam, 14 years ago

Milestone: 5.6 release
Status: newassigned

Removing milestone. I'd still like to address this for 5.6 if I can, but there is no point in holding up a release for a bug that I still can't reproduce.

comment:6 by heijo, 14 years ago

Oh, I don't think it needs a case test or something like this. Try do the below Oliver Wesp-2's post:

Hi, 
we recently struggled with exactely the same kind of errors 
(TopologyException) when reading S57 data through ogr. We discovered 
that the problem only occured when gdal/ogr was build against GEOS. We 
rebuild without GEOS support and the TopologyExceptions dissapeard. 
Best regards, 
Oliver

Hope to see this bug is gone in next MapServer's version :) Thank you!

comment:7 by warmerdam, 14 years ago

Resolution: worksforme
Status: assignedclosed

Closing as no test case appears to be forthcoming.

Note: See TracTickets for help on using tickets.