PATRIK27 / osmdroid

Automatically exported from code.google.com/p/osmdroid
0 stars 0 forks source link

Allow users to specify tile location #234

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
The sdcard tile location is hard-coded. There should be a possibility for users 
to specify a different location.

Original issue reported on code.google.com by neilboyd on 28 Jun 2011 at 5:29

GoogleCodeExporter commented 8 years ago
See also issue 174.

Original comment by neilboyd on 28 Jun 2011 at 5:29

GoogleCodeExporter commented 8 years ago
Issue 299 has been merged into this issue.

Original comment by neilboyd on 19 Jan 2012 at 12:28

GoogleCodeExporter commented 8 years ago
Issue 301 has been merged into this issue.

Original comment by neilboyd on 20 Jan 2012 at 9:13

GoogleCodeExporter commented 8 years ago
See also issue 310.

Original comment by neilboyd on 13 Feb 2012 at 6:28

GoogleCodeExporter commented 8 years ago
Issue 336 has been merged into this issue.

Original comment by neilboyd on 9 Apr 2012 at 2:34

GoogleCodeExporter commented 8 years ago
I have implemented a fix for this and used it in my app for quite a while now. 
Basically I have removed some of the configuration data from 
OpenStreetMapConstants and moved it to a separate default configuration class, 
that can be overwritten/supplied by a 3rd party application.

Unfortunately this patch covers quite a number of classes, because the 
configuration and constants are used a lot across the package. Nevertheless I 
found it quite useful to give the app and potentially the user more control.

Original comment by osei...@gmail.com on 28 May 2012 at 5:14

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
Previous patch had issues.

Original comment by osei...@gmail.com on 28 May 2012 at 6:52

Attachments:

GoogleCodeExporter commented 8 years ago
Issue 174 has been merged into this issue.

Original comment by neilboyd on 3 Jun 2012 at 7:33

GoogleCodeExporter commented 8 years ago
I managed to patch, but how do you use it? how do I specify the path for the 
SDcard cached tiles?

Original comment by pip...@gmail.com on 22 Jun 2012 at 9:41

GoogleCodeExporter commented 8 years ago
OK. I figured it out by looking at the following file: 
OsmDroidDefaultConfiguration.java

create your copy (e.g MyOsmDroidDefaultConfiguration )

then you use it in your tike provider as:

final MapTileProviderBasic tileProvider = new 
MapTileProviderBasic(getApplicationContext(),MyOsmDroidDefaultConfiguration.getI
nstance());

I used getExternalCacheDir();
for the base path! according to DOCs this will ensure my tiles will be deleted 
once my app is uninstalled.

In my opinion this patch is a must! If i find some issues will report here.

Original comment by pip...@gmail.com on 22 Jun 2012 at 10:37

GoogleCodeExporter commented 8 years ago
Sorry, I should have provided an example implementation...

Original comment by osei...@gmail.com on 22 Jun 2012 at 11:27

GoogleCodeExporter commented 8 years ago
Are any news for this issue?

Original comment by devemu...@gmail.com on 4 Apr 2013 at 6:24

GoogleCodeExporter commented 8 years ago
just apply the patch. auto using SVN client or manual, i did it manual and it 
took not much time. see my commetn #11 for idea how to use it.

Original comment by pip...@gmail.com on 4 Apr 2013 at 9:34

GoogleCodeExporter commented 8 years ago
Actually I have already implemented a more simple solution for my projects. I 
was wondering if there would be an official solution some time.

In case anyone interests I just modified MapTileFileArchiveProvider and 
OpenStreetMapTileProviderConstants which are the only place OSMDROID_PATH used.
I added a new public static variable at MapTileFileArchiveProvider which I use 
at findArchiveFiles method and I set it at my projects start.
Also I set the TILE_PATH_BASE at OpenStreetMapTileProviderConstants to use that 
variable.

Original comment by devemu...@gmail.com on 4 Apr 2013 at 9:56

GoogleCodeExporter commented 8 years ago

Original comment by neilboyd on 20 Sep 2013 at 4:36

GoogleCodeExporter commented 8 years ago
Are any news for this issue?

Original comment by moshkov.konstantin on 31 May 2014 at 8:39

GoogleCodeExporter commented 8 years ago
I don't think the lib is under active development and after looking into the 
details it seems all too messy for me to bother ;)

Original comment by pip...@gmail.com on 31 May 2014 at 9:57

GoogleCodeExporter commented 8 years ago
Yes, there's a lot of news but we just didn't want you to know, Konstantin...

How come noone understands phrase on the right of comment box: 

"Each comment triggers notification emails. So, please do not post "+1 Me too!".
Instead, click the star icon."

Asking "are there any news" all the time is pointless. And irritating (for 
people who keep getting spam on their mailboxes).

1 - you can easily patch it yourself, just modify and build the lib by yourself 
- it takes like 10 minutes.
2 - if you even bother to read, you would know that project was moved to 
github, so asking here won't do anything

https://github.com/osmdroid/osmdroid

Original comment by scana...@gmail.com on 31 May 2014 at 10:15

GoogleCodeExporter commented 8 years ago
See github issue 96
https://github.com/osmdroid/osmdroid/issues/96

Original comment by neilboyd on 26 Apr 2015 at 8:05