search

gerhardol / apply-routes

Automatically exported from code.google.com/p/apply-routes
0 stars 0 forks source link

Caching of MapProvider tiles #1

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Currently tiles are only cached in memory.

It would be nice to cache them on disk. One problem with this is that (due
to the nature of trying to capture a bitmap from a dynamic website) tiles
sometimes have the wrong contents. We would need a way to clear just one
tile (or all the visible tiles) from the cache. Clicking the refresh button
tells the provider to drop *all* of its cached tiles - it would be a shame
to drop a months cache for one invalid tile.

Original issue reported on code.google.com by mark...@gmail.com on 11 Jun 2009 at 1:32

GoogleCodeExporter commented 9 years ago 
I think this is not necessary. 
If I understand right how this plugin works, maps are loaded through web 
browser. So 
web browser should be caching map tiles already.

Original comment by dob...@gmail.com on 11 Jun 2009 at 7:30

GoogleCodeExporter commented 9 years ago 
You're right, the browser *does* cache the tiles. But without the in-memory 
caching 
its still very slow (compared with fetching tiles direct from a server via 
GET). And 
it seems like (at least for the google tiles) the browser doesnt cache them 
from one 
session to the next. Also, the intial setup time for each map service is 
relatively 
long; if you're just revisiting one of your normal running areas, this could 
often be 
skipped entirely.

There is, however, another issue, which I forgot to mention in the enhancement 
request, which is that google's TOS dont allow the tiles to be saved anyway.

But still, several people have asked for this, and some of the maps do allow it 
(all 
the OpenLayers maps, for example).

Original comment by mark...@gmail.com on 11 Jun 2009 at 1:35