ersteinmal ein dickes Dank für die Realisierung dieses Feature und ein dickes Lob für die Umsetzung und das Handling.
Ich habe das heute erst ausprobieren können und bin total begeistert und werde bestimmt noch viel Spaß und viele weitere Ideen damit haben.
Run.GPS Atlas format does not use additional compression - it stores the compressed PNG files. The size of the Atlas file is the size of all single files plus the size of the index (which is very small). This means that there is no smaller format possible, unless you use additional compression, which may spare you another max 5% size but would make everything much slower. Or you leave part of the data away (by recomputing the map tiles), but that was no option for us.
The OruxMaps format is a format that uses many files, not just one as the .ratlas format. (Or did you mean OruxMaps Sqlite?)
I cannot confirm your tests. Before this "atlas-container" my OSM-Maps
needed 626 MB Space on a 4GB/Fat32 sd-card - by 221 MB file size!
The "Atlas-container" has a size of 221MB on the sd-card (filesize and space).
Performance-tests are outstanding. Seems to work fast enough.
I downloaded and created an atlas of whole switzerland. But the file ratlas files gets way too big: 14GB! I created with the same configuration an atlas for orux-maps and there the size is 2.6GB.. so ratlas is 5.4 times bigger! I think this is not really efficient and not usable as you said it was one of the reason to create you own format.
what are your comments on this?
24.10.2010 19:00:16 UTCgeändert am 24.10.2010 19:07:25 UTC
Performance-Test
Hi,
I did a performance test on the new Atlas file format:
Prerequisites:
- MDA Compact V (= HTC Touch Diamond 2) with Windows Mobile 6.2,
- sandisc micro-sd 8 gb,
- netbook with WinXP
sd-encryption on Windows Mobile is switched on.
I created an atlas-file from all osm-files downloaded using RunGPS on my MDA.
file size of atlas file is about 350 mb.
first attempt: copied atlas file via active-sync to sd-card (this creates an encrypted file on sd-card (Windows Mobile encryption))
result: access time to map was 4 to 7 times slower than the standard osm-files
second attempt: copied atlas file via a card reader (so the file is not encrypted)
result: access time to map was almost equal to standard osm-files (ratio 1 to 1.2)
summary: if You use atlas file, make sure that it will not be encrypted by the device
hope that helps...
P.S.: I had to fix some minor bugs (regarding fileseparatorchar and 0 Byte files) in the RunGPSAtlasFile.java provided on http://www.rungps.net/wiki/RunGPSAtlasFormat. Is there anyone who wants to get a diff-file or the changed source file?
We're currently working on the problem. For us the problem currently is that we do not get the crash ...
Could somebody please describe from map source (OpenStreetMap, Google, ..) you're trying to download and what geographic region you're downloading? Which zoom levels did you select for download?
wäre super mit diesem Format..
Bekomme diesselbe Fehlermeldung wie OpenBiker. Wenn ich die erzeugten Files dennoch herunterlade, wird nichts angezeigt...