New Topic

Locus Map - help desk Topic Problem Locus Map (Android)

This object is in archive!

Category Locus Map (Android)

Comments 12

Subscribers 5

Votes 1

Import percentage

R5O.nl shared this problem ago

Solved

I was just importing a big zip file with a lot of caches; in itself the procedure went fine and I end up with one folder with around 65000 caches (something for the weekend...). Using latest Locus Pro. It is a procedure of some 15 minutes on eg Nexus9 or Nexus5X (both latest Android 7.1.2). Locus loads the file, analyses it and I choose to import into an empty folder. That runs and after a short while it shows the counter for the amount of loaded caches and also a percentage. After some 1000s of caches loaded it reports a double name and I select to overwrite (and for all from there on). It continues importing and the percentage increases. Then at around 50% it quickly says something like 'succeeded' and stops. I now have the nagging feeling that either the percentage was wrong or I did not import all caches. I tried on 2 devices. What could it be...

The same problem 0

Replies (1)

Michal Stupka ●

Hi,

that looks strange, for sure. And what about the count of caches in the folder - how many of the it indicates? 65 000? or 32500?

regards

Michal

URL

R5O.nl ●

It now indicates 65000 caches. After import. I do not know whether that is indeed the amount contained in the zipfile. I can share the file with you, over private mail. Tnx.

URL

Michal Stupka ●

OK, please send it to michal.stupka@asamm.com

URL

Libor Poutnik Striz ●

65000 is quite a lot. Could it hit the 16bit unsigned integer count limit, if there is one ? ( 65536 )

URL

R5O.nl ●

65536: That is a smart remark indeed! Maybe this is the case, and together with some double names (as I wrote in my original post) we could end up with around 65000 effectively loaded. BTW, this morning I shared the big zipfile with MichalS. Hopefully it arrived well.

URL

Michal Stupka ●

Hi, the file has arrived safe and sound and after a few attempts (I didn't have time to check it all the way through and OS often stopped Locus when it went to standby) I successfully imported it. The file contains 65487 caches and all of them successfully imported. However, I missed the point when Locus showed 50% during import... Anyway - such a big database is nonsense - work with it is quite annoying as Locus has to handle enormous amount of data at once and is lagging all the time you open the cache folder.

URL

R5O.nl ●

OK, thanks for checking. I totally agree that having such a big db is waaay overdone and causes lagging in Locus when starting and when scrolling the map. However, quite impressive that Locus crunches through and is able to handle it. This is the kind of cache DB that go around and I use it for viewing purposes or a quick cache when I am occasionally in a far away place. As for the percentage: that starts showing after a while and increases along while importing. I reckon there is a small calculation error there in Locus. I will make a screenshot for you. I consider this cosmetics, now we assessed that the full file is imported. Thanks for attending!

URL

R5O.nl ●

Here some screenshots with the percentages that are way too low, considering the file contains some 65000 points.

Files:

URL

R5O.nl ●

And some more, when the import is almost ready. See the low percentage.

Or does the file still contain a lot more points?...

BTW, Locus crashed while collecting these screenshots. I will report that in a separate topic. I have the logcat :)

Files:

URL

c.s.g. ●

Hi,

or it has something to do with this topic.

c.s.g.

URL

R5O.nl ●

Yep, sounds like the same. Tnx.

URL

Michal Stupka ●

There definitely is a bug in counting % of imported points. I simulated it too. Menion has been informed...

URL