Metros is commented out in my code. What your looking for is rather simple
and already built in:
var geochart = new google.visualization.GeoChart(
document.getElementById('visualization'));
geochart.draw(data, {width: 556, height: 347, region:'US',
resolution: 'metros'});
Ok, well if your trying to compare the file you sent me to that then its
just a matter of changing the hi/low values to adjust to that one zip code.
If your trying to show State zip code regions like
this: http://www.zipmap.net/Michigan.htm
Then you are missing a few objects, as there were only
Nope I don't, you have to grab the hi/low values from each Google chart
state:
http://www.gstatic.com/charts/geochart/10/mapfiles/US-AL_PROVINCES.js
Just change AL to XX state Identifier.
Also just FYI, if this is ever something you want Google Charts to
incorporate or make open source for
http://www.gstatic.com/charts/geochart/10/info/mapList.js
That's all of Google charts mapped files. DC is in there, Guam is GU, not a
province but a country
http://www.gstatic.com/charts/geochart/10/mapfiles/GU_COUNTRIES.js
basically whatever subset the file is in is the ending. GU is in
I think what you did in the file I tested is fine, where each is it's own
object. However, I can't really say as I don't know what the actual final
objects are supposed to look like, so that's only something you will be
able to answer yourself once you tweak the hi/low values to the scale you
I tested your file and it loads fine, but your high/lows are way off.
Your high/low has to change based on what your trying to view:
hi: [22.0, -75.0],
lo: [18.0, -65.0]
Obviously this is skewed so you need to adjust, but I see 4 objects that I
can highlight.
--
You received
The Hi low represents the visible area on the screen you are representing.
Think of it as the 4 corners of the square on the screen.
As for how to find the high low that you are looking for there is no way
except through modifying it slowly to meet your needs.
If your purely looking for
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
Sorry I noticed you said 3 digit boundaries, however this still gives a
maximum possible of 1000 boundaries loaded at once for the US, which is
still going to get a file up into the 10MB range probably. My Texas file
with 255 counties is in the 2MB range, and if someone with a slow
connection
