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
When you search and there are multiple locations in the results, we omit things like comments and scores and whatnot. That resulted in faster loading.
But we still have "zoom limits" because eventually even that lesser amount of data takes a while load, given enough of it. What if instead of zoom limits, we had another "level" of location data that returned even less info. Like, once you zoom out past X, then instead of showing the location type and the list of machines, instead it just returned the venue name and the number of machines?
I think all this would occur with Started GET "/map_location_data? ... ?
Given that some of our searches are for particular machines, those would still need to query for spots that have that one machine.
I guess the main "slow down", though, is not so much querying and returning the data as it is loading all the divs. So, if we wanted a scenario that returned every single location in America, we would probably have to exclude the sidebar that has all the locations and instead just load map markers.
Thinking out loud here. Just trying to imagine a scenario where we don't have these max zoom limits (or they are less strict).
The text was updated successfully, but these errors were encountered:
When you search and there are multiple locations in the results, we omit things like comments and scores and whatnot. That resulted in faster loading.
But we still have "zoom limits" because eventually even that lesser amount of data takes a while load, given enough of it. What if instead of zoom limits, we had another "level" of location data that returned even less info. Like, once you zoom out past X, then instead of showing the location type and the list of machines, instead it just returned the venue name and the number of machines?
I think all this would occur with
Started GET "/map_location_data?
... ?Given that some of our searches are for particular machines, those would still need to query for spots that have that one machine.
I guess the main "slow down", though, is not so much querying and returning the data as it is loading all the divs. So, if we wanted a scenario that returned every single location in America, we would probably have to exclude the sidebar that has all the locations and instead just load map markers.
Thinking out loud here. Just trying to imagine a scenario where we don't have these max zoom limits (or they are less strict).
The text was updated successfully, but these errors were encountered: