I would just like to point out that zip code boundaries change on a ( quarterly I think) basis in the US. On top of this zip codes cross both county and state lines, so you could never emulate something like what I did with breaking down counties into states. I also thought about going deeper into zipcodes, but this stopped me.
The only way something like this would work in the current GeoChart would be to load all of one states zip code boundaries, with the zip code objects being the final items in the list. Each item in the list in the JS file overwrites previous items, so you could have views with other states as 1 object as GeoCharts already do, but the zip code boundaries that do overlap the state lines would lay on top of the state boundary lines from the state objects. This however, only solves one of the problems, and you still need to get updated zip code boundary files whenever they are updated. You won't be able to load all 10000+ zip code boundaries in the GeoChart as it is currently. The Visualization team will need to modify the code to increase the timeout for loading a mapfile to be more then the 8 seconds it is now, otherwise it will simply throw an error every time and say the map doesn't exist. -- You received this message because you are subscribed to the Google Groups "Google Visualization API" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-visualization-api+unsubscr...@googlegroups.com. To post to this group, send email to google-visualization-api@googlegroups.com. Visit this group at http://groups.google.com/group/google-visualization-api. For more options, visit https://groups.google.com/d/optout.
