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

Add documentation on cluster behavior + syntax #2985

Closed
mollymerp opened this issue Aug 11, 2016 · 5 comments
Closed

Add documentation on cluster behavior + syntax #2985

mollymerp opened this issue Aug 11, 2016 · 5 comments
Assignees

Comments

@mollymerp
Copy link
Contributor

Right now the only things I could find on our clustering functionality were in the examples and in the style reference for GeoJSONSource.

We should document things like the point_count property more explicitly.

Also, I was trying to figure out if there's a way to set a minimum for the number of points in a clusterRadius that should be grouped in a cluster (i.e. if you only want clusters for areas w more than 3 points) and I did not have time to fully check.

@mourner do you have any thoughts?

@mourner
Copy link
Member

mourner commented Aug 11, 2016

@mollymerp I don't think we need the minClusterPoints option, but it would be possible to add on the supercluster library level. We should definitely improve docs about clustering.

@YunjieLi
Copy link
Contributor

I also find the point_count a little cryptic, like for a single point in a cluster=true source, its point_count is null instead of 0 (like if I need to filter them out).

@stevage
Copy link
Contributor

stevage commented Aug 16, 2017

So, what properties get generated exactly? cluster (boolean), point_count (integer), any others?

(Are there any other examples of properties generated by Mapbox-G? I wonder if they should be $cluster, $point_count etc to reduce the chance of namespace collisions...)

@tuukka
Copy link

tuukka commented Feb 18, 2018

I'm seeing cluster, cluster_id, point_count, point_count_abbreviated.

@mourner
Copy link
Member

mourner commented Jul 24, 2018

Fixed in #7000

@mourner mourner closed this as completed Jul 24, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants