-
Notifications
You must be signed in to change notification settings - Fork 24
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
Pin aggregation #24
Comments
Library options seem to be Leaflet.markercluster and PruneCluster. The former seems to be the de facto standard, but the latter seems to look and perform nicer. |
TIL about PruneCluster. It does look and perform better. And they both need to be imported anyways so it's new overhead regardless. Seems like the best choice. I wonder if we could also prune for all untracked data/data outside Oakland, and set it in a pruned pin fixed on a position on the screen, maybe by dataset type.. |
Don't want to stretch you thin, @brlodi , but any chance you could tackle this, too, since you're working with the pins and logos anyway? |
Yeah I can take a look. I found another seemingly more lightweight plugin that merely does the spiderification, so we might consider that too since I don't think the numbered clusters do as good of a job at indicating scale as a tight cluster of pins do (I'd be more in favor if we could tailor the boundaries to some sort of subdivision of Oakland instead of the automatically calculated ones the libraries use, but that seems like a lot of work). It resembles the Google Maps implementation of spiderification. |
What's the plugin? |
Should aggregate a collection of pins in the same location into one pin that, when clicked, shows the separate pins living there. Should have a little icon that shows the that there are a number of pins living there. This will help clear up the UI.
The text was updated successfully, but these errors were encountered: