If you do try that, you will need a build of GDAL/OGR compiled with Geos support. I am not sure how the one that comes with the FDO binary distribution is built. We could probably remove this requirement by changing OgrFeatureReader::ReadNext() to perform the intersects using FdoSpatialUtility rather than OGR's OGRGeometry::Intersects.
Traian From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kenneth, GEOGRAF A/S Sent: Wednesday, April 16, 2008 4:41 PM To: MapGuide Users Mail List Subject: Re: [mapguide-users] Precision when selecting polygons You can try the OGR provider, which also supports MySQL. I am positive that the BBOX problem is solved there, but I am unsure about the performance aspect. There may be other hidden problems, but it might be easier than migrating data. Regards, Kenneth, GEOGRAF A/S Dave Wilson skrev: If you are using MGOS 2.0 then you can theme on the joined columns. You can't in the 1.2 version. A join between an SHP and a table in MySQL should work in 2.0 and allow selection since the selection is based on the SHP. The searching should also work on the join since theming and searching are both filters. The selection problem is specific to MySQL so having all your data in MySQL won't work. Dave -----Original Message----- From: [EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]> [mailto:[EMAIL PROTECTED] On Behalf Of Krunoslav Sent: Wednesday, April 16, 2008 12:21 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mapguide-users] Precision when selecting polygons Dave Wilson-3 wrote: MySQL only does Envelope operations. For example when selecting MapGuide might do an Intersect spatial operation; however, MySQL (at least version 5 and earlier) only does Envelope Intersects so you won't always get the results you expect depending on how the polygons sit next to each other. This is a known issue with MySQL. I'm not sure if they have resolved this in later versions. Thank you for your answer. Since I have all data in mysql tables, I created new Geometry column, converted my SHP to mysql with shp2mysql tool, so I have everything in same table. It seemed perfect, but obviously it won't work this way. Since I have to use styling which is related to property in one column, I also tried to use SHP <-> MySQL join, without geometry data in mysql. I can get properties from mysql table, but layer isn't themed, I don't know why, all parcels are the same color, even if mapguide studio can "pull" properties from the table. Same procedure works fine when everything (converted SHP) is in mysql, but there is problem as mentioned above. So, is there any solution for this or should I give up from using mysql? Anyway, before starting on a project: I have few shp files and data tables in Excel (which I can easely convert to mysql tables). What would you recommend for next things to work? 1. Properly selecting polygons 2. Searching (regarding to some property from table) 3. Themes (also regarding to one column in table). What database to use and how to join this together? Sorry for my bad english and thank you in advance. -- View this message in context: http://www.nabble.com/Precision-when-selecting-polygons-tp16718926s16610p16728445.html Sent from the MapGuide Users mailing list archive at Nabble.com. _______________________________________________ mapguide-users mailing list [email protected]<mailto:[email protected]> http://lists.osgeo.org/mailman/listinfo/mapguide-users _______________________________________________ mapguide-users mailing list [email protected]<mailto:[email protected]> http://lists.osgeo.org/mailman/listinfo/mapguide-users
_______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
