Skip to content
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

Points with the same lat/long do not cluster #7

Closed
demoend opened this issue Nov 15, 2012 · 2 comments
Closed

Points with the same lat/long do not cluster #7

demoend opened this issue Nov 15, 2012 · 2 comments

Comments

@demoend
Copy link

demoend commented Nov 15, 2012

I think you are on the right track with your AD cluster map view, I appreciate your effort and desire to share you code with others. But it only works well to a point for me.

Using the sample project, if I change some of the point data in the CDToilets.json file to have the same lat/long then those points will not cluster. This was at maximum zoom. Looks like they are just on top of each other and I cannot pick the point underneath the top one.

Example: If I stand in one spot for a while and snap 10 photos, I most likely will have photos with the same lat/long. Some photos may be so close that they should always bee seen as one point. The user then will need to click on the blue arrow in the callout to drill down to the exact photo they are interested in. The Apple photo app does this same type of thing.

@Ecco
Copy link
Contributor

Ecco commented Dec 16, 2012

This is an interesting use case, but I'm not sure it has anything to do with clustering actually.

The aim of clustering is to remove reduce the number of visible annotation for a nicer and faster UI.

Here it's actually your annotations themselves that aren't properly built. Your model objects aren't correct: instead of adding one annotation per photo, you should add one annotation per "photo list", where a photo list is defined as a group of photos sharing the same coordinates (or nearly the same coordinates).

That being said, your use case is pretty common I guess, so it might make sense to work something out.

@PatrickNLT
Copy link

We're keeping only one open issue on this subject: #8.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants