New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integration with a server-side clustering implementation #151
Comments
This is definitely needed. I can see two separate features that would allow this to happen.
This is sounding more like a fork of the markercluster package the more I think about it. |
I'm going to say this is outside of the scope of L.MarkerCluster. |
Any progress on this? |
Yes, I've also been looking into solutions for this but not really found any. This site (ddproperty.com/en/property-map-search) appears to perform server-side clustering of 100,000+ markers, and it appears to use something similar to Leaflet, or maybe a forked version of it or something. Hoping to find out how they achieved it. |
You can use supercluster, which can load in server side, same functionality as ddproperty.com/en/property-map-search, I am using with node js :) |
hi,
this is just a rough idea and i'm not sure if i will have the resources for implementing this. so please take it mainly as a collection of ideas rather than an actual request to make this happen :)
i have developed Geocluster, a server-side clustering implementation for Drupal that integrates with Leaflet: http://drupal.org/project/geocluster
the clustering works quite well and scales up to 100,000 using mysql and beyond 1,000,000 items using a apache solr implementation of the Geohash-based clustering algorithm.
obviously, the visualization part of my implementation is very rough and leaves a lot of room for improvements :) i think, Leaflet.markercluster has implemented this quite nicely. i'm wondering, if one could extend markercluster to support a hybrid approach: the server provides a clustered result as geojson and the js clustering library would visualize it the same way as markercluster does. the only difference is that sub-requests to the server are issued, if necessary for expanding clusters.
let me know if you are interested adding capabilities of integrating a server-side clustering implementation / your thoughts on implementation-details. here's a link to some discussion on that topic we had in the geocluster issue queue on drupal.org http://drupal.org/node/1914704
regards,
dasjo
The text was updated successfully, but these errors were encountered: