Open GoogleCodeExporter opened 8 years ago
I had the same problem but I change to
osmdroid-android-3.0.8-20120208.220818-1.jar
and it seems to work fine, when zoom in some maps tiles are updated and some
parts of the map remain as it is and I think this is because the tiles
crosponding to the partsof the map(not updated) are not downloaded because in
mobile atlas
Original comment by 07n...@gmail.com
on 20 Apr 2012 at 8:12
I have attached a quick and dirty patch to solve the problem. Basically I had
to disable the ScaleTileLooper in class MapTileProviderBase.
In my project I have both online and offline maps, so I switch the behavior
with a setter:
MapTileProviderArray provider = new MapTileProviderArray(MBTILESRENDER, null,
new MapTileModuleProviderBase[] { moduleProvider });
provider.setUseScaleTileLooper(false);
...
Original comment by markgabb...@gmail.com
on 16 May 2012 at 10:31
Attachments:
Is this different to issue 290 and issue 289?
Original comment by neilboyd
on 17 May 2012 at 2:16
It looks the same as both issue 290 and issue 289. The patch does improve
things a bit, as it gets rid of some overhead on zooming in/out. And yet,
missing tiles are still there, especially on zoom out (library v.4.1). The
problem seems to be a timeout of some kind. The slower the loading, the more
missing tiles there is. I tested it on a customized version of GEMFFileArchive
(which supports overzoom and caches overzoomed tiles). The original
GEMFFileArchive is obviously faster and I get less missing tiles, but still
occasionally do. And by the way, the tiles are in TileOverlay.
Does it give any clue as to where the timeout is happening?
Original comment by daniel.k...@gmail.com
on 10 May 2014 at 3:43
I finally solved the problem by following the advice from issue 251 - by
setting TileRequestCompleteHandler for provider for tile overlay to MapView's
one. Like so:
myGemfTileProvider.setTileRequestCompleteHandler(mMapView.getTileRequestComplete
Handler());
Original comment by daniel.k...@gmail.com
on 10 May 2014 at 4:12
@daniel.klimov I would appreciate it if you could create a new issue in github
which can replace all the related issues. Then we can consolidate all the
relevant information and close the rest.
Original comment by neilboyd
on 13 May 2014 at 7:43
Original issue reported on code.google.com by
sam.w...@gmail.com
on 5 Apr 2012 at 8:47