I've just checked in the first version of the Google Maps v3
MarkerClusterer to the utility library:
http://google-maps-utility-library-v3.googlecode.com/svn/trunk/markerclusterer/
I've tried to keep the interface the same as the v2 library so the
transition to v3 should hopefully be fairly simple.
If you're interested, have a read of the reference doc:
http://google-maps-utility-library-v3.googlecode.com/svn/trunk/markerclusterer/docs/reference.html
Check out some examples here:
http://google-maps-utility-library-v3.googlecode.com/svn/trunk/markerclusterer/docs/examples.html.
Reply back to this thread if you run into any problems/bugs.
Thanks!
Luke
Seems to work fine but I did not get the first line in the source
code:
this.extend(MarkerClusterer, google.maps.OverlayView);
Where does that extend method come from?
--
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 google-map...@googlegroups.com.
To unsubscribe from this group, send email to google-maps-js-a...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
first of all, thank you for MarketClusterer V3.
I think I found something odd / unexpected; don't know if it is a bug,
so I will give you an overview first, if needed a can then provide
further details.
When, after creating a marker, I use the addMarker() method this seems
to enlarge the the lat/lng bounds of the current viewport (the
LatLngBounds that you get from the getBounds() method of the Map
class), even if the position of each added marker is contained within.
On the contrary, if I just create each marker (with the constructor of
the Marker class) the lat/lng bounds remains exactly the same (as I
would expect).
As you can imagine this is quite an issue, in my personal case I use
this LatLngBounds as a parameter to download appropriate data from a
server DB.
Is this behavior expected?
I look forward to your comments.
Best,
Mario
On 23 Feb, 03:10, "Luke (Google Employee)" <lu...@google.com> wrote:
> Hey everyone!
>
> I've just checked in the first version of the Google Maps v3
> MarkerClusterer to the utility library:http://google-maps-utility-library-v3.googlecode.com/svn/trunk/marker...
>
> I've tried to keep the interface the same as the v2 library so the
> transition to v3 should hopefully be fairly simple.
>
> If you're interested, have a read of the reference doc:
>
> http://google-maps-utility-library-v3.googlecode.com/svn/trunk/marker...
>
> Check out some examples here:
>
> http://google-maps-utility-library-v3.googlecode.com/svn/trunk/marker....
excellent, just tried and it works smoothly, issue solved.
Thank you very much for your quick reply.
Best,
Mario
There seems to be a slight problem when you zoom the map out. The
clusters that should appear 'around the edges' in the new view don't
unless you pan the map slightly at which point they jump into view.
Same behavior in demo maps.
I see the code has a listener to spot zoom changes but this doesn't
seem to fully work?
Thanks
Mike
On Apr 12, 12:46 pm, Luke Mahé <lu...@google.com> wrote:
> Thanks for pointing that out. I've fixed the bug, I should have been
> listening to bounds_changed.
>
> - Luke
>
> On Sat, Apr 10, 2010 at 8:02 AM, Mike Wood <mikewoodconsult...@gmail.com>wrote:
>
> > Hi Luke,
>
> > There seems to be a slight problem when you zoom the map out. The
> > clusters that should appear 'around the edges' in the new view don't
> > unless you pan the map slightly at which point they jump into view.
> > Same behavior in demo maps.
>
> > I see the code has a listener to spot zoom changes but this doesn't
> > seem to fully work?
>
> > Thanks
>
> > --
> > 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
> > google-map...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > google-maps-js-a...@googlegroups.com<google-maps-js-api-v3%2Bunsu...@googlegroups.com>
PS - I created differently colored image versions of the correct
larger sizes for m4.png and m5.png so that the code works fully with
clusters of > 1000 markers (currently the demo just repeats the m3
image for 1,000 + and 10,000 +).
If you would like to use them they are here:
http://gsak.info/stats2/maps/m4.png
http://gsak.info/stats2/maps/m5.png
Mike
On Apr 12, 12:46 pm, Luke Mahé <lu...@google.com> wrote:
> Thanks for pointing that out. I've fixed the bug, I should have been
> listening to bounds_changed.
>
> - Luke
>
> On Sat, Apr 10, 2010 at 8:02 AM, Mike Wood <mikewoodconsult...@gmail.com>wrote:
>
> > Hi Luke,
>
> > There seems to be a slight problem when you zoom the map out. The
> > clusters that should appear 'around the edges' in the new view don't
> > unless you pan the map slightly at which point they jump into view.
> > Same behavior in demo maps.
>
> > I see the code has a listener to spot zoom changes but this doesn't
> > seem to fully work?
>
> > Thanks
>
> > --
> > 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
> > google-map...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > google-maps-js-a...@googlegroups.com<google-maps-js-api-v3%2Bunsu...@googlegroups.com>
To unsubscribe from this group, send email to google-maps-js-a...@googlegroups.com.
--
--