On Jan 12, 6:54 pm, Chris Apolzon <[email protected]> wrote:
> I'm wondering if I can speed up my map by passing a pre-encoded
> polyline into the polyline constructor instead of letting google
> encode it. I haven't seen anything in the v3 documentation about
> forcing the use of an encoded polyline, is there a workaround to allow
> this to happen? I'd be fine abandoning the polyline class if
> necessary.
I have several large poly demos running at:
http://www/polyarc.us/polycluster
for both API V2 & API V3.
The compression algorithm is different than the one used by Google.
It is pixel based for full precision at deep zoom levels. Point
reduction is done on the fly. "zoom strings" are not required nor
useful resulting in a reduction in the size of the poly definition
package. It also eliminates a lot of confusion.
It works in any browser supporting either CANVAS or SVG. I am still
trying to make VML (the rendering engine used by Internet Explorer)
work, but, thanks to Ben, I have an example I ought to be able to
adapt.
--
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.
