On Sep 9, 1:02 pm, KirAsh4 <[email protected]> wrote:
> LOL. I never thought of it that way (it probably being a good idea to
> ignore) ... But I have started to use Mark's encoder. I do still
> want to figure out what the three options do together though. the
> API's documentation does say that they work together, but ... what
> exactly they do is still a mystery to me.
>
> Oh well, for now it works, and I'm going to move on to the next step
> in the project.
>
> Thanks!
I believe the word Andrew is objecting to is in your subject line. In
the US, it is roughly comparable to "Pest" which is an appropriate
description for Internet Explorer.
I agree, "zoom strings" are totally confusing, even counter productive
because of the extra bulk added to the package. The mistake was made
a couple of years ago for V2. I am trying to make enough noise to be
sure it does not happen again for V3. Very large polys (110,000
vertices) can be constructed without "zoom strings"
See:
www.polyarc.us/polycluster
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
