Jon, Thanks for your quick reply. I see what you're saying about having one record per item: but like most people, I'm dealing with the database output that is given to me by shp2mysql, and with little control over what I've got. Because I know others are using a similar system for displaying in google maps, I thought someone might have an idea. Do you have a suggestion about another group that would deal with KML creation using PhP that would be dealing with the same GEOMETRY objects in Mysql?
I'm also curious as to what you mean about holes.... Like donut shaped polygons? My dataset doesn't have any of those, so I wouldn't have encountered them, but I could see how that would similarly be a problem. Again, thanks for your reply - I didn't mean to go too far off topic, and I apologize. Dominic On Apr 17, 10:38 am, "Maps.Huge.Info (Google Maps API Guru)" <[email protected]> wrote: > The simple answer is to prepare your database to use one polygon per > record and drop the multipolygon problem. It's easier to deal with > polygons if you know there is only a single boundary in each. > > There is also the problem of holes, you probably have that as well. > > This isn't a PHP problem, but one of programming so you can solve it > with some thought. This also isn't an API problem, so you might want > to post your question on a PHP forum for better results. > > -John Coryat > > http://maps.huge.info > > http://www.usnaviguide.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Maps-API?hl=en -~----------~----~----~----~------~----~------~--~---
