The reason that tiles are a better solution is that lots of polygons
make your map sluggish. Depending on the complexity of the boundaries,
about 50 polygons is about as much as some browsers can cope with.
Also consider the size of the data that needs to be passed to your
client in order to describe the zip codes. If you've already got the
boundary data in your database, take a look at the filesize of that data
and consider how long it would take to send that to the client over a 1
megabit broadband connection.
Using a tileserver avoids both those problems.
--
Mike Williams
--
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.
