Thank you for taking the time to respond. We are at the early stages of implementing a KML solution to displaying our data so we are still trying to understand how best to implement an efficient service.
At the moment we simply have a static KML file which is called on body load and read by GeoXML. This is very cumbersome as we have over 22000 POI's. At the moment the description is either a link to an external website or a text description of the POI. The database holds a unique identifier for each record, a code to allow us to determine which users have access to the data and has a number of fields which we wish to display and a number of links for further information. We have seen so many people's different solutions but are struggling to find a concise and simple to implement answer. If you have the time a basic run through of your preffered solution (if it is relatively layman friendly) would really help in our quest. Kind regards Paul Preston --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
