I see your point. When using a database I usually write a php or perl script to create kml files. So perhaps an excel file would be appropriate (easier to work with for than mysql on my webserver), and when its time to create a new JSON or xml, I'll just save it as a .csv or .txt and convert it to JSON/xml via php or perl. Does this make sense? This would be more stable than dealing with all the markup manually.
Still very interested in linking markers together through JSON and javascript. Thanks again! Shad On Aug 4, 8:33 am, Rossko <[email protected]> wrote: > > Thanks very much, and you guessed it...the data will be edited/ > > maintained by hand. And sometimes it will be a hand that has little > > experience in coding. > > Whether XML or JSON, it'll be ridiculously easy to break the data file > completely with something as simple as an apostrophe or ampersand in a > placename (see every alternate post in this forum with titles like "my > map just stopped working"). > > I'd strongly recommend some kind of user-interface that can take care > of encodings etc. for them, even if the project doesn't warrant a > database system. -- 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.
