Clusters overlapping, fractal children patterns
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2.4k
- Forks
- 304
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I've been tinkering around with supercluster and deck.gl to visualize large datasets. I'm using synthetic dataset of a 600 by 600 grid to test performance and wanted to better visualize/understand the individual clusters. I was hoping to get fairly disjoint clusters at any radius I selected, but for the most part( other than a radius of 70), the clusters frequently overlap and exhibit interesting fractal patterns.
The images I'm displaying below show children points and polygon overlay of each cluster generated by supercluster(at the specified zoom level). Each picture has a different radius value ranging 20, 40, 70, 80, and 100 units. (The children are fetched via getLeaves(id, Inifinity) per cluster;
I'm interested in knowing if the fractal patterns clusters exhibit is expected/usual using supercluster(or perhaps my synthetic data is causing issues with the underlying algorithm). And also if is any parameter tuning that can be done to mitigate the effect.
If a codesandbox is desired I can try to get it set up, the only issue being the data usually causes the website to be unresponsive so I can try to generate a smaller set that exhibits the same behavior.
Thanks
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the overlapping clusters with supercluster and the synthetic 600-by-600 grid described in the issue, varying radius values from 20 to 100. Inspect how cluster polygons, getLeaves(id, Infinity), and the clustering parameters relate; done means establishing whether the fractal patterns are expected and identifying any documented parameter guidance or reproducible defect.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- data-visualization
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100