You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've seen this happen, and, generally, the changing numbers of properties depending on the zoom level was confusing to people in our workshop. There may be room for a smarter rewrite of this feature to avoid this problem entirely.
However, what I think is happening is that the FE is briefly using both the point and polygon layers of the pmtiles as it switches zoom levels, which is basically doubling the number of observations when toggling between zoom levels. There's probably an easy way to avoid this.
When Zooming on Vacant Property Map (using mouse), the total property count varied above 35K (47K, 52K, 67k)
Steps to reproduce the behavior:
Would expect count NOT to exceed ~35,227 when looking at the entire map range for Philadelphia.
macOS 10.15
Chrome
Tried to reproduce at 3:27PM 2024-11-20 and could not, property range came in at 35,227 as expected.
The text was updated successfully, but these errors were encountered: