Limit amount of data for Blitzortung.org direct data.

[wuan]

The app gets unresponsive during high activity

[d3xter]

Does https://github.com/wuan/bo-android/blob/improve_ui_performance/ resolve the unresponsiveness?

[wuan]

Unfortunately this is a problem of the map view. We should add map features dynamically depending on the current view. Having a lot (several thousands to ten thousand, depending on the performance of the device) of map features by default degrades performance.

[d3xter]

Oh ok.

Does #154 help when we use it for StrikeShapes too?

[wuan]

Ah, there was a problem during test. Your changes may have improved things. I just enabled the detailed strike mode for our tests, because direct Blitzortung.org access is too slow. There is a new icon on the right, which can be used to switch between raster end single strike mode.

[wuan]

Unfortunately I do not see any strike on the map now. The raster display is working.

[d3xter]

StrikeShapes are drawn now. But strangely, sometimes there are white strikes and after the next data-retrieval the white ones are gone.

And there are no yellow strikes anymore

[wuan]

That is a problem with the timestamp related expiry, already fixed locally

[wuan]

It is faster than before, but still lags above 20k strikes. We could use raster display for overview and strikes at higher zoom levels, where we reduce the features on the map depending on the current view.

[d3xter]

Its working now.

I've disabled the drawing of the StrikeShape completly and its still laggy. so its not the drawing part, but rather the moving/resizing of all the strikes thats lagging

[d3xter]

I've tested 1.6_Beta3 yesterday with 120min TimeRange and about 60k Lightnings.

It was very slow when moving the map, but no more "App unresponsive" messages