On Sep 5, 4:18 pm, KirAsh4 <[email protected]> wrote:
> For this test, yes I did. As I was adding the waypoints in the
> encoder, before hitting 'add point', I would copy and paste the
> values. Eventually (and now that I know what my mistake was), I'll
> continue to use the encoder. In fact, I did try to use that other
> one, but I couldn't figure out why the 'levels' value is so different
> from what the Goggle version was returning.
>
> Eventually, once all the necessary polylines are in, I'll be feeding
> the map some 3,000 addresses and use GClientGeocoder() and the
> MarkerManager to populate the map. Still need to learn the proper
> use of the zoomFactor and numLevels in GPolyline.fromEncoded() before
> I move on to the next bit though. Just can't seem to get the hang of
> it. Slowly learning the API and the various bits and pieces of it.
Google's utility & Mark McClure's utility use different zoom level
quantizations. Google assigns the same symbol to a group of four zoom
levels. Mark McClure assigns a different symbol to each zoom level.
If "zoom strings" actually did have a useful purpose, Mark McClure's
approach would be better.
The API does adequate thinning on the fly. Unfortunately, the
"fromEncoded" methods will not work without a "zoom string". "Zoom
strings" are both confusing & a relic of the past. I agree, encoded
polys do reduce transmission time but "zoom strings" inflate the size
of each packet by 50% with no tangible benefit.
Sorry to keep beating the same dead horse. In V3, Google has a chance
to abandon "zoom strings".
Some V3 examples of very large polys (41,000 vertices / 110,000
vertices) without "zoom strings":
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
-~----------~----~----~----~------~----~------~--~---
