cluster.setPixel(10); seems to have done the trick as far as fixing
the rendering issues. I've also simplified the map quite a bit if you
still need that.
One thing I did add was a "Remove Polycluster" button for testing
purposes but I can't get it to work. I create an empty array as so
(shorttrip being the path I want to delete):
var empty_array = {};
empty_array.shorttrip = [];
and then I do cluster.load(empty_array);
You had mentioned I just needed to reload the cluster with an empty
array but I'm obviously doing something incorrectly.
Thanks again Berry, I appreciate you taking the time to look at all
this stuff.
On Oct 9, 10:11 am, bratliff <[email protected]> wrote:
> On Oct 8, 6:38 pm, Tim G <[email protected]> wrote:
>
> > Berry,
>
> > Here you go, as simple as it gets (hopefully!). I set the stroke to
> > 300px. Typically I'd use a ~300px stroke when you're zoomed in pretty
> > close. Zooming in further, I'd just remove the poly so you get a
> > clear map view. Zooming out, I'd make the stroke more narrow,
> > eliminating the issue in most cases.
>
> >http://www.dgcoursereview.com/google_simple/beta_cluster_simple.php
>
> > I did notice the issues started to show up at 129px. At 128px you
> > could zoom in to any level without issue. 129px started to show
> > rendering issues.
>
> I have a "stop-gap" fix. Set the tile size to 1024 pixels by adding
> the following statement:
>
> cluster.setPixel(10);
>
> It is still a PolyCluster bug. I am working on correcting it.
--
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.
