GPS-Sport ForenRun.GPS SoftwareMemory leak
Bitte einloggen, um neue Kommentare zu erstellen Foren durchsuchen
Erste Seite<Seite1von1>Letzte Seite
admin 01.12.2009 13:19:43 UTC



Regarding your proposal: it's a good thought to create one bigger data structure that contains all PNGs of one level, but many users of Run.GPS download the tiles on their PCs and then copy to and fro. The cluster size issue is bad, but using the standard OSM tiles file structure has many advantages ...
actuar 01.12.2009 10:05:01 UTC geändert am 01.12.2009 11:56:20 UTC

Clear for everyone

1) on FAT32 drive it can only be 4177918 clusters (files). On zoom level 18 it means that it can saves maximum 819 locations at all zoom levels (divide that number with aprox 5200); on FAT16 drive it can only be 65000 clusters (files): so there no point using them: http://www.ntfs.com/ntfs_vs_fat.htm

2-3) Everything gets clear now: using this software http://www.amberhome.de/pdatm_faq.html
everybody can clear see the number and size of downloaded tiles.

ONLY one thing: the microSD drives come formatted with FAT32 with 32K cluster size. One can only changes to 1 K cluster size (it really saves 30 times the needed memory because of the small .pngs). Now the real problem it's the number of tiles: max 4 milion which it's not so much..

/// already did what i said and it works great: the speed decreased only to 11% from copying a 700MB file into the new 1KB cluster size///

PROPOSAL: maybe you can propose another software and modify your masterpiece so that it automatically combine .pngs into clusters: example. all 15* folders with png to be combined into a single png.

admin 01.12.2009 07:59:42 UTC



1) Well I'm not an expert on that issue. But if you have it running on FAT32 currently, the cluster size should be smaller than 16kb. Right? See http://support.microsoft.com/kb/140365

2) The data structure is a "quad tree". Every tile is divided into 4 tiles when you go to a higher zoom level.

3) The built-in download in Run.GPS is rather simple ... you can use the PDATileManager instead: http://www.gps-sport.net/forums/thread/958-10/
actuar 30.11.2009 18:16:35 UTC

Am i right?

First of all, thks for such a quick and clear answer. Pls tell me if I've got it right:

1) about the MEMORY: although the .png can be only 103 bytes (for no image at all) it takes 32kb to store it on disk. Obviously then why it takes 40 time more on disk to store 40000 .png; so there's no bug just real numbers. Does it makes a difference if I'll format the disk on FAT16 (taking only 16kb size on disk)?

2) Can you describe me a formula of how many .png will be downloaded depending on the zoom factor? so that everybody to calculate their own needs?! I suppose it will be something like 2^k.

3) If we can adjust the zoom factor, can we also adjust the maximum area were we can automatic download all the needed data? Now it's set on 15km on diameter... Say I want to go in a new place and download quickly everything that's around that location.

admin 30.11.2009 16:12:42 UTC



I suggest the following:
1) delete all osm files
2) edit the "maps.xml" file (/sdcard/My documents/Run.GPS)
3) replace the maximum zoom factor (18) with a smaller zoom factor (17) - 17 is usually enough

>>> so you will have much less files
actuar 30.11.2009 13:27:22 UTC

Memory

Hallo,

using osm maps (downloading 30 Mb of them, more then 40 000 files) it looks like run.gps will allocate more then 1.3 GB on my SDMC drive. On a 4 Gb drive, I've been writing only 2.4 Gb, but the WM 6.1 will get no more memory left. Of course run.gps will be unable to write nothing when on training. Is this a bug on WM edition, or do you know that the proggrame will use so much data?
Erste Seite<Seite1von1>Letzte Seite
© 2024 | Impressum | Allgemeine Geschäftsbedingungen | Nutzungsbedigungen | Datenschutzerklärung | Widerruf und Rücksendung | Batterieentsorgung