Lazy Load Data Points

[aswinmohanme]

Currently we get the entire data dump from the sever. This is expected to grow and considerably slows down the site.

We should load the data of the immediate surroundings first

[appunnicer13]

Any implementation to filter the whole data will result in use of more CPU and RAM from USERs device which will considerably slow down. Its always a better idea to get the data dynamically by passing latitude longitude and letting server take the load for it. But If we can get district wise data may be this will be possible, but as more people mark it here more the load is going to be

[appunnicer13]

https://www.npmjs.com/package/geolib, but this is a solution I will work on it

[appunnicer13]

What is the initial window ?

[aswinmohanme]

I don't understand

[appunnicer13]

Currently I don't load points unless they click on near me

[appunnicer13]

What should be the initial window , if I shouldn't be loading points

[aswinmohanme]

We should zoom near to the location of the user and load those points. The zoom level should not be as close as the one which shows up when we click on the locate near me

[RevathiKannanGithub]

More than district, do we have zones/divisions of districts in kerala? That might narrow down further and reduce the load time.

[appunnicer13]

Yeah that is happening automatically, I am showing points near 10km radius

[appunnicer13]

But is initial window is empty now. I will give a pull request you let me know

[appunnicer13]

Create a branch called lazy loading
I will do pull request there

[appunnicer13]

intial commit on lazy loading #12

[appunnicer13]

distance selection #17