-
Notifications
You must be signed in to change notification settings - Fork 0
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
Performance #24
Comments
i have noticed this too - it is probably the vtl. One strategy is to narrow the zoom level to not display at the national level... kinda a bummer. |
or we could have hexbins show at the high level and switch to the point vtl on the way down past some zoom level |
Also, where is the survey tool hosted? I want to see what it looks like in production. |
the rgoss branch should be the branch in production. |
there are three hexbin levels, it looks like you are displaying one of the higher resolution layers, if you display a different resolution at different zoom levels it might be best. i think @rgoss might have some ideas for how to play around with that. |
for v0.0.1 we will drop support for VTL in CM3 |
The issue is caused by a data race condition from the VTL using the same load queue as the base map. Without modifying dependency packages, a solution is to force trigger load on mouse movement (see link below). Issue should be resolve when re-adding VLT. |
If the map is zoomed in, and then zoomed out, the part of the map outside of the zoomed in section will not load. This is likely tied to the VTL layer, I don't think I see the problem without it. There's no error thrown in console. Could be due to my laptop not having the sufficient computing capacity to both host the development server and compute the graph on the front end.
The text was updated successfully, but these errors were encountered: