You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[X ] Question
[ ] Bug
[ ] Improvement
[ ] Build system related
[ ] Performance
[ ] Documentation
Description and/or steps/code to reproduce the problem
We have an implementation using a 3rd party tile source. I've been looking into optimizing this, and noticed that the tile caching doesn't work as I expected. If I open a map fragment, the tiles are downloaded and stored to cache. However, in navigating away from the map fragment and returning to it with the exact same map tiles displayed, the tiles are not found in cache and are downloaded from the source all over again.
Drilling into this, I noticed that the call to mapView.setTileSource(myTileSource) will in turn call mTileProvider.setTileSource(aTileSource).
So as far as I can tell, the cache is cleared whenever the custom tilesource is set. I assume this is why the same map tiles are downloaded every time the exact same map is opened? How can I avoid this, I have to set the tilesource at some point? Or have I misunderstood how the tile cache is supposed to work?
Version of osmdroid the issue relates to:
6.1.2
The text was updated successfully, but these errors were encountered:
Issue Type
[X ] Question
[ ] Bug
[ ] Improvement
[ ] Build system related
[ ] Performance
[ ] Documentation
Description and/or steps/code to reproduce the problem
We have an implementation using a 3rd party tile source. I've been looking into optimizing this, and noticed that the tile caching doesn't work as I expected. If I open a map fragment, the tiles are downloaded and stored to cache. However, in navigating away from the map fragment and returning to it with the exact same map tiles displayed, the tiles are not found in cache and are downloaded from the source all over again.
Drilling into this, I noticed that the call to
mapView.setTileSource(myTileSource)
will in turn callmTileProvider.setTileSource(aTileSource)
.From MapTileProviderBase.java:
So as far as I can tell, the cache is cleared whenever the custom tilesource is set. I assume this is why the same map tiles are downloaded every time the exact same map is opened? How can I avoid this, I have to set the tilesource at some point? Or have I misunderstood how the tile cache is supposed to work?
Version of osmdroid the issue relates to:
6.1.2
The text was updated successfully, but these errors were encountered: