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 , 15 years ago
Cc: | added |
---|---|
Owner: | changed from | to
comment:2 by , 15 years ago
Milestone: | 5.2.1 release → 5.6.0 release |
---|
comment:3 by , 15 years ago
Cc: | added |
---|
comment:4 by , 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 , 14 years ago
Milestone: | 5.6 release |
---|---|
Status: | new → assigned |
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 , 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 , 14 years ago
Resolution: | → worksforme |
---|---|
Status: | assigned → closed |
Closing as no test case appears to be forthcoming.
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: