thanks Mike and Bratliff for the explanation of the cross-domain javascript issue.
However in this kind of application, where polygons need to be coloured with dynamic data and symbology, there is often a workflow (like a wizard) through many html pages before a report or map can be generated. So the application isn't a full AJAX system, it's more a traditional website. A good example is the US Census Bureau American FactFinder. The Census Bureau has terabytes of data that could be displayed on a map. So they offer a wizard for the user to browse the available data, choose symbology, data classes etc, and finally create a report or a map. The wizard starts with this screen: http://tinyurl.com/69m4fl After lots of data selection screens the user will be given a map. If the map contains all the 3000 counties can a VERY long time to render, for example this Median Age map of all counties: http://tinyurl.com/6lb88n The map is slow because it is using older ESRI technology to render the map image. Here's a simple example of the same thing done much faster in google maps: http://tinyurl.com/6lb88n The tile server can be on another domain because the request is for images not javascript or JSON. All that's required is that the dynamic tile url contains a reference to the map layer that was created for the original map request. This map layer was specified in terms of data, symbology, and data classification scheme. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
