Map refresh issues and overlapping sources

[SabrinaAnderson]

When a lot of sources are displayed on the page like in the case of the usage types irrigation and municipal, the map takes a long time to reload whenever the user zooms in and out or attempts to pan over the map for both the existing supplies and the strategy supplies themes. I got the message that the web page was not responding a couple of times when looking at data types regional water planning cycle and usage types. Data type Regional Planning Cycle = 'F' is a good example of this. I can zoom in, but when we try to move around the map when zoomed in, the application takes a while to respond.

It is also difficult to click on sources that overlap each other. For example, when the user selects Regional Planning Cycle = Region C as the data type and then selects the existing supplies theme in the interactive map, 'SULPHUR INDIRECT REUSE' and 'SULPHUR RUN-OF-RIVER' both display on the map, but they have the same line feature and overlap each other. The user can hover over the line and only the indirect reuse source name displays. Another example is when the user selects County = 'Terry' as the data type and then selects the existing supplies theme in the interactive map, the aquifer sources 'Ogallala | Terry' and 'Edwards-Trinity-High Plains Aquifer | Terry' both completely cover the county and when the user hovers over the aquifer shape, the 'Edwards-Trinity-High Plains Aquifer | Terry' source name is the only one that displays.

A suggestion that we had would be to allow the user to turn on and off source type features in the map by dividing the sources into groundwater, surface water, and reuse. This would not help in the case of the aquifer overlap, but would allow the user to see the supply data more easily and speed up the refresh time when the user moves around the map. Please let us know if you have any other suggestions that will help resolve this issue.

[adambreznicky]

source layer performance can be improved by converting the single geojson layer into a UTF Grid & Tile Raster layer. The 2 working simultaneously will render much faster but requires reworking the queries and the popup.
i will begin working on this as a priority just as soon as i get back to focusing on this app.

[adambreznicky]

after spending time to convert from the single geojson layer into a utf grid & tile raster layer, performance was not too much better. only better in 'some cases' and was much more inconsistent. it also caused other timing and layer draw issues - the time required to iron out these issues is not worth the mild performance benefits.

alternative solution: host the sources layer within the app's cache.db dbase rather than carto. may be another rabbit hole of fixes though considering api updates, sqlite3 acceptance of long geometry strings, etc. this is a luxury update so this is put off until time is plentiful.

[SabrinaAnderson]

I understand. Thank you for looking into it.