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

Previous (big) circles not disposed properly upon zoom in #11

Closed
michaltrunek opened this issue Jun 25, 2021 · 3 comments
Closed

Previous (big) circles not disposed properly upon zoom in #11

michaltrunek opened this issue Jun 25, 2021 · 3 comments

Comments

@michaltrunek
Copy link

Upon zooming in (fast) or clicking on regions, the previous big circles with number of trees in regions are disappearing very slowly most of the time. The big circle is zoomed in and is covering big part of the screen and at the same time we are already loading another/detailed regions with tree numbers. This doesn't look nice for a user. We should dispose/dismiss the previous circle more effectively.

Details:
Mobile and Desktop devices

slow_circles.mov
@dadiorchen
Copy link
Collaborator

This is an interesting issue, I'm happy you are interested in this, the thing is, I thought this is a feature intentionally provided by leaflet, the old/big/previous circle remains there is for (in some view) better user experience, if you use google map, you will find, when you zoom in the satellite map, the previously loaded map will stay there for a while, till the new map get loaded, I guess this will make the user more comfortable comparing to hide the old one immediately.
Back to our case, we have implemented our own tile server (just like google satellite map) but currently, we have some performance problems with it, so the newest map gets loaded slowly.
Actually, I have no answer for a better solution to it, it would be great you want to do some research, feel free to do some experiments on it.

@dadiorchen dadiorchen transferred this issue from Greenstand/treetracker-web-map-client Oct 29, 2021
@keyy123
Copy link
Contributor

keyy123 commented Dec 8, 2022

Should we mark this issue as closed/moved/transferred? 🤔

@dadiorchen
Copy link
Collaborator

Yes, we will migrate to beta, so let's close this

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