Just be sure to check whatever you use against IE before you release it. I had a client side solution working great for county polygons under FF and Chrome, but as soon as I tried it under IE, it took forever to load. I ended up having to use a TileOverlay to make it usable in IE. Another possibility if IE is too slow... is to shrink up your dataset, use some sort of point minimization routine based on zoom level and only supply to the client polygons which are inside of the current view.
-- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" 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-js-api-v3?hl=en.
