New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GetFeatureInfo wrong on MultiPolygons with Spatialite/OGR #4420
Comments
MapServer doesn't handle SpatialLite any differently than other data sources and MULTIPOLYGONS work fine in those instances. For example, try converting your SpatialLite database to a shapefile or whatever. Does it work then? If yes then it's more likely an OGR issue and not a MapServer issue. The best test would be to convert to a shapefile and then access the shapefile via OGR in MapServer. Steve |
I've investigated the problem and it seems to be due to a GEOS behavior. If we use TOLERANCE=0 for the given layer queryByPoint doesn't hit any shapes, because the point to polygon intersection test always return false. |
…n degenerated cases (#4420) "backported" from master branch
Hi, |
…n degenerated cases (MapServer#4420)
…n degenerated cases (MapServer#4420) "backported" from master branch
Spatialite DB accessed with the OGR driver don't resolve correctly the Multipolygons dataset.
It report always wrongly
"Search returned no results. No matching record(s) found"
I tested the spatialite ogr with a Polygon dataset and it return correctly from a GetFeatureInfo request,
so I guess the problem is on the MultiPolygon type.
No test do on MultiLinestrings.
The text was updated successfully, but these errors were encountered: