On Jan 28, 9:05 am, qFox <[email protected]> wrote: > What you're looking at is a custom tile layer. Google requests images > as tiles from your server and displays them over their own maptiles. > It is then up to your server to actually create those images properly > to display whatever you like. When you go to the 'radar' example you > can clearly see the tiles being loaded, one square at a time, because > the "radar" server is much slower than google's server. The tiles are > created by the server somehow to reflect the weather conditions on > those area's. > > Setting up a custom tile layer is not very hard on the client side > (but still a bit advanced) and is quite some work on the server side, > depending on what you're trying to accomplish. > > Have a look at the GTileLayerOverlay examples.
Using tiles for time sensitive images runs the risk of adjacent tiles from different observation times. Also, obtaining tiles through a third party (Iowa State) adds delay & reduces reliability. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
