Size of installed offline vector database is not correct in details.
Solved
In details screen for the installed vector databases the size of the respective database is displayed but size does not match actual size as reported by the system file manager when navigating to the data directory when the 3 database files are stored.
Android app info also reports a much higher occupied storage (19GB) as the sum of database sizes (15GB)
The same problem 
Hello Frank,
Locus Map considers the map and the file with offline points as a single "map". They belong together.
So in your case, in the UI is the sum of 4.28GB of the map file and also 858MB of the "osm.db" database file. "osm.poi" is a format not used by the Locus Map app.
Now we are close, not identical to what you see in the app.
I'm checking this on my device and what I see is identical to yours. It looks like a problem in Android conversion.
First screen is from PC where values are in bytes
Second screen is also from the Android device, where values seem to be simply divided by 1.000.000 to convert to MB. "Funny".
So from my point of view, values in Locus Map are correct.
Hello Frank,
Locus Map considers the map and the file with offline points as a single "map". They belong together.
So in your case, in the UI is the sum of 4.28GB of the map file and also 858MB of the "osm.db" database file. "osm.poi" is a format not used by the Locus Map app.
Now we are close, not identical to what you see in the app.
I'm checking this on my device and what I see is identical to yours. It looks like a problem in Android conversion.
First screen is from PC where values are in bytes
Second screen is also from the Android device, where values seem to be simply divided by 1.000.000 to convert to MB. "Funny".
So from my point of view, values in Locus Map are correct.
Hi Menion,
Thanks for the explanation. I considered the three (!) files belonging together and they summed up to more than the reported 4.9GB. I'm also familiar about the problem what is 1GB/MB... (1024 vs 1000) euch explains 4.28gb+858MB=>4896MB
According to your explanation Locus does not use osm.poi but then I wonder why it is stored in data directory maintained by Locus wasting 1.2GB of space? Wouldn't it be better only keeping files which are actually used?
In other words: only install used files resp. delete unused/unsupported files would be better approach.
Bye
Frank
Hi Menion,
Thanks for the explanation. I considered the three (!) files belonging together and they summed up to more than the reported 4.9GB. I'm also familiar about the problem what is 1GB/MB... (1024 vs 1000) euch explains 4.28gb+858MB=>4896MB
According to your explanation Locus does not use osm.poi but then I wonder why it is stored in data directory maintained by Locus wasting 1.2GB of space? Wouldn't it be better only keeping files which are actually used?
In other words: only install used files resp. delete unused/unsupported files would be better approach.
Bye
Frank
Hello,
sure it would, but OAM maps are not managed by us. You had to somehow download and install them and what exactly happens during this process is not Locus Map business (if I simplify it). We offer our own internal LoMaps (available in the Locus Store).
Anyway, on the OAM web page is an option to download map directly to Locus Map, have you tried this? I hope that the guys behind OAM do not pack a useless database file into the provided zip.
Hello,
sure it would, but OAM maps are not managed by us. You had to somehow download and install them and what exactly happens during this process is not Locus Map business (if I simplify it). We offer our own internal LoMaps (available in the Locus Store).
Anyway, on the OAM web page is an option to download map directly to Locus Map, have you tried this? I hope that the guys behind OAM do not pack a useless database file into the provided zip.
Hi,
I exactly used this service and it seems that they add the additional database although it is not used in Locus. If I get you right then it's completely up to OAM which files are installed as Locus does not perform any checks for used external install triggers and installs anything, right?
Then I would ask the OAM guys to remove unnecessary osm.poi file for Locus install.
Thanks for the explanations!
Hi,
I exactly used this service and it seems that they add the additional database although it is not used in Locus. If I get you right then it's completely up to OAM which files are installed as Locus does not perform any checks for used external install triggers and installs anything, right?
Then I would ask the OAM guys to remove unnecessary osm.poi file for Locus install.
Thanks for the explanations!
Yes, you must report this to OAM
Yes, you must report this to OAM
This is correct as freischneider confirmed. What OAM guys use is the very generic system I've created that may be used for anything, not just maps.
And because of this, Locus Map does not check any downloaded content.
This is correct as freischneider confirmed. What OAM guys use is the very generic system I've created that may be used for anything, not just maps.
And because of this, Locus Map does not check any downloaded content.
Replies have been locked on this page!