On Jan 6, 2:07 pm, Vladimir Agafonkin <[email protected]> wrote:
> Thanks for the answer bratliff,
>
> Sounds really interesting. How the click/rollover support is possible
> technically? I thought that you can only do that by manually going
> through all the points with a sophisticated algorithm on click/
> mouseover/out which is very slow.
Visible polys are already broken into tiles. A typical tile contains
fewer than one thousand points with one hundred points per tile being
much more typical.
The search can be confined to just one tile using a "fast winding
number" algorithm:
http://softsurfer.com/Archive/algorithm_0103/algorithm_0103.htm
Otherwise, a discrete event listener is required for every poly for
every tile for every monitored condition (click / mousemove /
mouseover / mouseout / etc.)
For polys not yet rendered, I plan to use an auxilliary grid structure
with intersecting X & Y slices several pixels wide. A hit occurs if
the same poly resides in both the corresponding X slice & the
corresponding Y slice.
--
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.
