Cluster layer goes blank
See original GitHub issueDescribe the bug
As said the Cluster Layer
goes blank when zoom out at small zoom level, the official demo can reproduce.
Change the earthquakes
demo point layer to cluster
Then zoom out.
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (3 by maintainers)
Top Results From Across the Web
Issue with clustered symbology not showing in ArcGIS ...
I'm trying to display an ArcGIS Online mapviewer (the new mapviewer) that shows locations of incidents. The incidents are spatially ...
Read more >hide clustered overlays from map when page loads
Everything is working perfectly, except that I want the map to be blank when the page first loads, and the user can choose...
Read more >Clustering visualization may be downgraded—ArcGIS Pro
Your clustered feature layer uses one or more display settings that are not supported when sharing the layer to web. The visualization of...
Read more >Failover Cluster Troubleshooting - SQL Server Always On
The first diagnostic step is to run a fresh cluster validation check. For details on validation, see Create a Failover Cluster: Validate the ......
Read more >OpenLayers event cluster feature id does not appear on layer ...
found the answer: the clustered feature (placemark) is "inside" the cluster feature, not the layer. SOLUTION 1 first way out (not most ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
My bad, you were talking about the cluster layer, yea I was able to reproduce this, will investigate
TLDR: https://github.com/mapbox/supercluster/issues/86
Ok I tracked down the issue. At low zoom levels it’s possible for
geoViewport.bounds
to return a minimum longitude that is < -180 or > 180, resulting in a bounding box where the minimum is larger than the maximum.So for example:
A simple fix for this is to clamp the longitude to between -180 and 180, as Supercluster already does for latitudes
(not sure why longitudes don’t get this fix).Update: it looks like they already fixed this: https://github.com/mapbox/supercluster/issues/86. Will bump Kepler’s package version.
IMO this is a bug in
geoViewport.getBounds
since it is an invalid coordinate, but this fix should work for now.