Limit Cluster Legend to Integers

[PeterKnoop]

When using Clustering in the Map Viewer, it defaults to displaying a count of features. Since counts are inherently integers, the legend should also be limited to integer values.

If the range of the values being clustered contains fewer than 5 distinct integers, then it should reduce the number of legend items to maintain each being an integer.

If the range needs breaks, then those breaks should also be integers; adjusting the number of items in the legend to accommodate the range.

For example, if you happen be viewing an extent where the count of features ranges from 2 to 3, then the legend should only have two values in it: 2 and 3. It should not display fractional values, as it currently does:

It is confusing to indicate fractional counts, as it is impossible to have a fractional count. Furthermore, there are no symbols on the map that are not 2 or 3, so it overly complicates the legend to have those fractional values presented. 

[RussRoberts]

Yup what we would need to do in this case when you get down to this scale with clusters is drop the number of classes from 5 down to 2 or 3. This could be jarring for some users for viewing the legend while panning and zooming but would have symbols represented the whole number values. 

[PeterKnoop]

@RussRoberts as the legend values are already potentially changing when you pan/zoom, I would suppose that this would not be any more jarring than what the user is currently experiencing. I might suggest that the number of legend values changing provides a stronger visual cue to the user that the legend can update on the fly as they pan/zoom.

[DevinEPA]

Hi, was this ever resolved or was a workaround found? I'm dealing with the same issue.

[MappyIan]

This is such a sensible idea, I'm amazed it hasn't been implemented.  It seems totally bonkers that the cluster legend shows fractional values given that cluster values will only ever be integers.  Dropping the number of cluster classes (as mentioned by @RussRoberts) is the most sensible way of achieving this and I don't believe it will be any more jarring for the user than the legend updating under pan/zoom as mentioned by @PeterKnoop.  Dropping the number of classes would remove the situation below, which is really not very good:

I fully support this idea and hope that it will be implemented in the future.

There's a very similar/duplicate idea here: https://community.esri.com/t5/arcgis-online-ideas/aggregated-feature-representation-in-web-map/idc-p...