Lagging of map in full screen due to large parsing of data

[ananyaarun]

Description

In some layers, (like osm ) layer loading takes a lot of time (looks like the browser is hanging ) due to huge data being parsed.
A quick fix would be to allow layer loading only at zoom levels by indicating zoom-in in brackets along with the layer name.
But a more stable fix is necessary.

cc- @jywarren

[ananyaarun]

This was fixed temporarily by adding a zoom-in next to layer name in #202
reference - #202 (review)

[jywarren]

I think this can even be a permanent solution! But it might vary by region - some areas with /much/ more data than others, you know? I'm so glad you are working on this. Other layers will also need optimization! Also - this idea that some layers are only enabled at some range of zoom levels is (as you prob know) another part of the layer standardization project. That layers could in their basic options have minZoom and maxZoom bounds. That could be a way to accomplish this too.

…

On Fri, Jun 14, 2019 at 2:35 AM Ananya Arun ***@***.***> wrote: This was fixed temporarily by adding a zoom-in next to layer name in #202 <#202> reference - #202 (review) <#202 (review)> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#208?email_source=notifications&email_token=AAAF6JZP3LJULL5SSPV6X43P2M3YZA5CNFSM4HYE4FNKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXV3P4A#issuecomment-501987312>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAF6J3ZL3O5GJP7TXPHPZTP2M3YZANCNFSM4HYE4FNA> .

[ananyaarun]

Sure @jywarren makes sense :)

[sagarpreet-chadha]

So restricting heavy data fetching layer to higher zoom level only?

[jywarren]

Yes, so adding to the #135 metadata that each layer could optionally provide, would be a zoom range that it'd be enabled!