On Sep 1, 12:39 pm, Papa Bear <papabear.newy...@gmail.com> wrote:
> I think better efficiency could be gained by
>
> 1) down sampling my set of pointys
> 2) encoding the points - A BIG WIN - especially when zoomed out.
But, with just five decimal places of accuracy, a big loss if zoomed
in. The API does automatic point reduction. "Zoom strings" are a
relic of the past. Encoded strings have to be decoded which adds
overhead. Encoding is useful for reduced transmission time or reduced
URL length for static maps but not much else.
> 3) better browser support for small vector drawing. Only Firefox (I
> think) use the native hardware (forget what its called - you guys
> probably know). IE8, Safari and Chrome are all visibly slower. I
> would think (except for IE) those guys could get that working.
I have several CANVAS demos:
www.polyarc.us/polycluster/others
one with 110,000 points. Every browser (Firefox, Safari, Opera,
Chrome, iPhone) except Internet Explorer is supported. It is a V3
subclass of OverlayView but a V2 subclass of GOverlay could be added.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google Maps API" group.
To post to this group, send email to Google-Maps-API@googlegroups.com
To unsubscribe from this group, send email to
google-maps-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/Google-Maps-API?hl=en
-~----------~----~----~----~------~----~------~--~---
