Caching SuperCluster Index
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- web-dev
Research direction
Start from the Supercluster construction and the .load(geoJsonData.features) entry point shown in the issue. Determine whether the generated index can be persisted and reused across instances, and define how cached data should handle the clustering options and input records. Done means large datasets can reuse a valid index instead of rebuilding it with load().
Written by the indexing model from the issue text.
Description
Hi, is it possible to cache index generated by SuperCluster so that I can use it next time instead of calling new Supercluster({}).load() Again?
The code below takes time for large records. I am trying to get over this issue.
superclusterIndex = new Supercluster({
map: (props) => props,
radius: MapConfig.clusterRadius,
maxZoom: ClusterZoomLevel.maxZoom,
}).load(geoJsonData.features);
- Dominant language
- JavaScript
- Stars
- 2.4k
- Forks
- 303
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from mapbox/supercluster
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mapbox/supercluster#265 ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
mapbox/supercluster#254 · 2 comments ·
-
Missing points when bounds are scoped to the extent of pointsMay be free again A pull request for this issue was closed without being merged. Openquestion
Difficulty 4/5 3-5 days Newbie friendliness 38/100
mapbox/supercluster#234 · 1 comment ·
-
Nested geoJson properties are copied by referencePossibly taken @mrkwanzaa claimed this 1337 days ago. Openenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 50/100
mapbox/supercluster#215 ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
mapbox/supercluster#211 · 2 comments ·
All issues in mapbox/supercluster
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Query Log shows "Upstream" for CNAME cloaking, schedule, NXDOMAIN hijack and response IP blocksOpenbug good first issue query-log web
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
ferrous-networking/ferrous-dns#326 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Ylianst/MeshCentral#8294 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
yunaremaia/jsonl-cli#1 · 1 comment ·