On Mar 15, 6:28 pm, Marcelo <[email protected]> wrote:
> If that level of accuracy is good enough for your map, then I would
> definetly use them.
But, to its credit, the API does not support encoded polys. For fewer
than one hundred points, the space savings is insignificant. The
useless "zoom string" adds 50% to the payload. The CPU overhead is
always greater.
I have added an example of 27,000 polys with over 1 million vertices
WITHOUT ZOOM STRINGS.
See "Other US Highways"
http://www.polyarc.us
It is slow because of its size but it runs without crashing.
--
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.
