Show loading feedback when fetching eco benefits

[opentreemap]

Show loading feedback when fetching eco benefits

[ahinz]

We got this down to about 5 seconds for even a largest maps in a worst case time... do we still need to add a spinner?

[dboyer]

I don't think so.

[steventlamb]

@jwalgran should we close this?

[jwalgran]

Labeled as a question. I do think a spinner is a good idea, but I moved it to Long Term Issues because Deb gave it a thumbs down.

[maurizi]

Just noting that I watched someone else using OpenTreeMap for the first time yesterday (Ivan) and they were confused when nothing seemed to have happened after attempting a search.

[RickMohr]

I vote for a spinner. Currently searches on latreemap take over 10 seconds.

[RobinIsTheBird]

@RickMohr what search took > 10 seconds? On staging, all my searches are blindingly fast.

[RickMohr]

I don't remember exactly but I just tried an advanced search on the production latreemap unchecking Dispay > Trees and it took 8 seconds

[RobinIsTheBird]

Specifically, unchecking trees does take around 8 seconds.

Another reason to have a spinner is that sometimes the results are impossible to see, so you don't actually know when your search is done.

We should solicit @lederer's input on the "searching" feedback. Seems to me that you should have the ability to cancel the search or adjust it, or zoom/pan the map or whatever, before a search completes.

[lederer]

Can we try this…

On search, disable the search button and lower its opacity to, say, .2. Also lower the opacity of any content that will be updated by the search results (eg, ecobenefits, tree count, planting sites count).

When the search completes, update the content, reenable the search button, and restore the opacity of all elements.

[RickMohr]

We now show a "Loading Ecobenefits" message.

[maurizi]

We only show the "Loading Ecobenefits" message on page load, not when a search happens.
We're partway there, but there is more work to do.