It is likely (incorrectly) treating the remaining rings of the polygon as holes and the intersection check fails for them. This instersection check is done by the FDO provider, so it would be the SHP FDO provider that is doing intersection wrong. One thing you could try - convert your SHP to SDF and see if it still fails. SDF uses the same code for intersection, but may be the geometry will be converted to the right kind of multi-polygon during the conversion step. I know... this sounds more like a cooking recipe than a fix, but it may help.
Traian From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ryan Northcott Sent: Tuesday, October 30, 2007 4:35 PM To: MapGuide Users Mail List Subject: Re: [mapguide-users] Fluctuating Cursor Accuracy I've noticed this as well, and it appears to be just the way the mapframe reads your x,y location. So the further zoomed out your scale is, the harder to precision grab the x,y. Now for the fun stuff. I create shapefiles out of ArcView 3.2 that are multi-part polygons. (So two or more seperate polygons for one feature), and it would appear, that you can't select, or Task-panel click on the multi-part polygons other than the first one in the feature, to get a selection. For example, a multi-part polygon with a 0.25 Acre triangle corner polygon on the other side of a road, and a 100 Acre square polygon, if the the 0.25 acre sized polygon has it's vertices index first, you can only hit that small polygon in order to pull the attributes of the feature. Clicking on the Larger 100 Acres polygon doesn't create a hit. On 10/30/07, IT-Joe Marvin <[EMAIL PROTECTED]> wrote: When using an AJAX map, cursor is not always aligned properly. For example, if I go to select a polygon, sometimes the polygon on the tail or middle of the cursor is selected, instead of the point of the cursor. It seems to vary each time I load the page, sometimes it is correct, other times it is not. This is very confusing to users who think they are clicking on one polygon and actually clicking on another. Has anyone else encountered this problem, or even better, found a fix? Thanks _______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
_______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
