Well, finally i infer that Mapguide selection still contain a hidden bug. Here
is my simple php:
$regionGeometryData = $featureReader->GetGeometry('Geometry');
$agfReaderWriter = new MgAgfReaderWriter();
$regionGeometry = $agfReaderWriter->Read($regionGeometryData);
$queryOptions = new MgFeatureQueryOptions();
$queryOptions->SetSpatialFilter('BOUNDARY', $regionGeometry,
MgFeatureSpatialOperations::Intersects);
$layer = $map->GetLayers()->GetItem("INDEX");
$featureReader = $layer->SelectFeatures($queryOptions);
$regionGeometryData comes from SDF file. By this geometry, i try to select
another layer that is intersects with this. MGOS give me some records in layer
INDEX that is not have an intersection even far away from $regionGeometryData.
I will try to file a ticket soon for this issues..
Ary Sucaya
----- Original Message ----
From: Jason Birch <[EMAIL PROTECTED]>
To: MapGuide Users Mail List <mapguide-users@lists.osgeo.org>
Sent: Thursday, November 29, 2007 10:38:22 PM
Subject: RE: [mapguide-users] Insert Order In MySql Affect to
theMapGuideSelection?
The bounding box operations would explain why you are getting a polygon
selected even when you click outside of its boundary. Read the note at the top
of this page if you would like to confirm that this is indeed MySQL's
behaviour: http://tinyurl.com/2mk9aa
I'm not a heavy MySQL user, but I'm pretty sure that insertion order affects
the order that rows are returned in (unless you're explicitly ordering them,
and I am pretty sure that MapGuide does not). If this is the case, then in
combination with #313 this might explain why you are getting different polygons
within the multipolygon selected? Maybe I don't understand the issue properly.
If this works with multipolygon SDF files with no issues though, it is either a
problem with MySQL itself, or a problem with the MySQL FDO provider. I would
strongly encourage you to file a ticket on the FDO Trac instance (instructions
here: http://trac.osgeo.org/fdo/wiki/SubmitTicket ). For best results, please
include a description (preferably with small screenshots illustrating the
problem) and include a mysqldump of the geometry that is causing the problem
to allow the developers to easily reproduce it.
Jason
From: ary sucaya
Subject: Re: [mapguide-users] Insert Order In MySql Affect to
theMapGuideSelection?
http://trac.osgeo.org/mapguide/ticket/313 is not what i'm seeing now. That's
another problem of multipolygon. What i don't understand is why the sequence of
records insertion affect MGOS select behaviour? If MySql perform geometric
operation only on their bounding box, then 'my selection problem' will always
happens even i change the sequence of records insertion
____________________________________________________________________________________
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs_______________________________________________
mapguide-users mailing list
mapguide-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-users
