On Jul 17, 4:40 am, bratliff <[email protected]> wrote: > I forgot to mention another case. Two consecutive vertices may both > be "off-tile" but their connecting line may intersect the visible > tile. Both "off-tile" vertices will have to be moved into range along > their connecting line. Again, it is a lot of work but by doing it > once & caching the result, it does not have to be duplicated.
thanks bratliff for the detailed explanations of the tile clipping process, it's very interesting stuff. I've done this sort of thing with conventional GIS, for example when shading land/ocean, if using an entire continent boundary with millions of coordinates, then it's much higher performance to tesselate the polygon. It's amazing that it's now possible with javascript because I'm used to doing this stuff with optimized C code on a dedicated workstation. Now it can be done in javascript on an iPhone! Today I'll try these problem polylines with PolyCluster to compare with google.maps.Polyline. ... -- 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.
