On Dec 18, 10:14 am, "ralf.w" <[email protected]> wrote:
> One problem with GPolygon overlays is: you can't display polygons with
> holes (and there are some in the dataset).
Actually, it can be done by building a zero width bridge in both
directions between the outer & inner polys.
> Maybe I should try it with GPolygon.fromEncoded in the next example
> (to display holes) but I guess even better is to use image overlays
> (e.g. Polygonzo) for large Polygon data.
Actually, PolyGonzo uses the same built-in browser drawing
capabilities (VML / SVG / CANVAS) used for GPolyline / GPolygon by the
API. Some of its speed advantages can be achieved by realizing you do
not have to use "new GLatLon()" to build the array of points. You can
use an array of {x:,Lx,y:,Ly} objects with significantly less
overhead:
www.polyarc.us/polyfix
GPolys are dynamic but slow. Tiles are fast but static. Tiles are
cacheable both locally & at the server. Tiles can be displayed by
relatively simple mobile phone devices without (VMS / SVG / CANVAS)
capabilities. "Sparse Tile Layer Overlays" are a compromise between
GPoly flexibility & tile speed.
> I'm only wondering if I then have the same possibilities in my map
> (e.g. tooltips, mouseover- and clickeffects ....) as when I use the
> normal GPolygon overlay?
Clickable tiles require auxilliary click / rollover structures. John
Coryat has posted a demo for clickable markers / points.
For arbitrary shapes, look at:
www.polyarc.us/polybuilder
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
