On Oct 24, 6:57 am, William <[EMAIL PROTECTED]> wrote: > On Oct 23, 11:50 pm, MapSavage <[EMAIL PROTECTED]> wrote: > > > What do I have to do to get the same thing here? > > I think you should first work on implementing a simple application > that consumes this demo webservice, to see if it is actually going to > produce the maps you want on your own site and fit into your > application workflow. If this works then you would need to look at > the server-side tile processing. > > I can make a REST API with POST method so you can pass all the data > from your server and get back a google layer identifier. This > identifier would be used when the server constructs your google map > page. I'll send you a simple PHP example of this.
Eliminating the use of proxies with a JSON interface might appeal to some developers. Google's "mapsdt" service uses a very clever scheme to avoid proxies. Each tile URL contains a reference to a KML / KMZ file plus the usual (x,y,z) tile parameters. Presumably, the first reference to the KML / KMZ file causes tiles to be rendered and cached. Subsequent occurrances operate out of the cache. If it could also apply different colors "on the fly" it might improve an extremely useful service. Colors could be defined in a table or in the URL parameters. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
