Why not eliminate the KML step and just use PHP/MySQL? A PHP while loop will echo the MySQL data into the Javascript code for the polygons, generating a KML file seems like a wasted step.
On Mar 10, 3:32 pm, Dommer <[email protected]> wrote: > I know that Pamela fox can't be all things to all people, and thanks > to her for trying! > > I'm interested in designing an application that can display specific > polygons that are elicited by user search queries based on address or > account number. I will be using mysql to store the information, and > PHP to recall specific information that is searched for and which will > generate KML information from the mysql data. What I don't know > though is how to pull this off. > > Pamela Fox's tutorials about using php/mysql/kml works great for > points, and even for her line example. But what about polygons? > > It seems like you should be able to store the polygon information in > mysql native polygon geometry attribute, and then call it up as WKT. > But how can you transmute that WKT information into the data within > the KML-producing php script? Can you even use the geometry/polygon > type to store the correct information? > > I know there's interest out there, has anyone done this successfully? > > I'd love to see some examples, or if anyone has any ideas on where to > begin here, I could really use some pointers. > > Thanks! > > Dominic --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
