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
{{ message }}
This repository has been archived by the owner on May 27, 2024. It is now read-only.
Now that the new POI system is being used heavily by the layers widget (thanks to the collapsible groups), several new poi queries are requested upon initialization of the web app.
This causes additional data transfer and some extra time to the load time of the app - and could possibly be significant in e.g. certain mobile devices where bandwidth is scarce.
The following screenshots show the before and after network inspector for the POI API queries:
Expected behavior:
Some possibilities for improvements:
Investigate enabling CACHING for API endpoint
Add a bounding box to the POI API and update the frontend to only load the data for the visible area. NOTE: this will cause additional ajax queries for active layers upon map pan.
The text was updated successfully, but these errors were encountered:
Summary:
Now that the new POI system is being used heavily by the layers widget (thanks to the collapsible groups), several new poi queries are requested upon initialization of the web app.
This causes additional data transfer and some extra time to the load time of the app - and could possibly be significant in e.g. certain mobile devices where bandwidth is scarce.
The following screenshots show the before and after network inspector for the POI API queries:
Expected behavior:
Some possibilities for improvements:
The text was updated successfully, but these errors were encountered: