Simply execute the Union-method before applying your spatial filter: geometry = geometry.Union(geometry);
That's the way I workaround curve polygons for SQL Server 2008. In case of a MgCurvePolygon the resulting geometry is a segmented MgPolygon. I don't know if this is a bug in the library as I would expect also a MgCurvePolygon as the result but it does a good job for workaround all types of curve geometries in SQL Server 2008. Maybe this is an OGC conform behaviour of the Union-method. Don't know! Curve geometries should be supported in SQL Server 2012 but I am not aware if the FDO Provider for SQL Server already supports these features. Haven't tried it yet! Gunter -- View this message in context: http://osgeo-org.1560.n6.nabble.com/Getting-error-Geometry-Conversion-error-when-doing-SpatialFilter-in-MgCurvePolygon-tp5014745p5016513.html Sent from the MapGuide Users mailing list archive at Nabble.com. _______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
