View Single Post
gnuite's Avatar
Posts: 1,245 | Thanked: 421 times | Joined on Dec 2005
#10
Originally Posted by Ray View Post
Using a database container doesn't automatically mean no wasted space;-)
It still depends on the data organisation, the access methods, and other things.
Ray is right. No data structure, especially flat ones (i.e. disk-based), are without some amount of overhead. In Maemo Mapper v2.0's case, the overhead is in storing the "keys" that are used to find and access a given image in what is otherwise a sparsely populated matrix. This overhead, however, is significantly less than that of the internal fragmentation of typically formatted memory cards.

Originally Posted by Ray View Post
For a memory-limited device as the 770, it could also make sense
to store the tiles in an optimized database AND have them zipped beforehand.
The images will be stored in the database as they are retrieved (from Google Maps, Virtual Earth, etc.). This is usually in either PNG or JPG format, neither of which reacts at all to zip compression, because they themselves are already heavily compressed.