This object is in archive!
Manual Import of Geocaches from GSAK Addon does not work with Locus 3.40.1
Solved
Hi
With the actual version 3.40.1 of Locus Map Pro, the manual import of geocaches from a GSAK DB with the GSAK DB addon does not work anymore (Samsung Galaxy S7 with Android 8.0.0).
If one now tries to import geocaches from the GSAK DB, the "Läd" dialogue is show as before, there are also geocaches read from the DB but at the end, the dialogue where to import the POIs is missing.
With the prevoius Locus Version this worked fine, the only change I made is to upgrade to 3.40 and 3.40.1
Since this is a very useful feature of Locus Map for Geocachers, I ask you to fix this issue as soon as possible.
Best regardsmarujave
The same problem 
Hello marujave,
I have only one small GSAK database and no matter what I do, even if I have a map screen center directly on the place where are stored some geocaches, add-on always returns an empty list of caches.
Do you have any sample database I may try with this add-on, that for sure worked correctly before? It looks to me like a problem in the add-on itself anyway if it worked for you before, there may be something in the Locus Map itself. Thanks
Hello marujave,
I have only one small GSAK database and no matter what I do, even if I have a map screen center directly on the place where are stored some geocaches, add-on always returns an empty list of caches.
Do you have any sample database I may try with this add-on, that for sure worked correctly before? It looks to me like a problem in the add-on itself anyway if it worked for you before, there may be something in the Locus Map itself. Thanks
Hi Menion
I've created a GSAK DB with 847 caches around Berne (capital of Switzerland).
I will do some tests with the DB and if it behaves the same as my original DB, I will send it to you.
What's the easiest way to send it to you? (don't like to attacht it here to this public forum).
Best regards
marujave
Hi Menion
I've created a GSAK DB with 847 caches around Berne (capital of Switzerland).
I will do some tests with the DB and if it behaves the same as my original DB, I will send it to you.
What's the easiest way to send it to you? (don't like to attacht it here to this public forum).
Best regards
marujave
Hello,
perfect, send it please on my email jiri.mlavec@asamm.com , thanks.
Hello,
perfect, send it please on my email jiri.mlavec@asamm.com , thanks.
Hi Menion
I did now some tests with the smaller DB and found that the problem has to do with the number of caches that are imported.
With 847 caches, the problem was not observed. I've now crated a bigger DB with 2671 caches. With this DB, the problem does not occur if only 1000 caches are imported. If more are imported, (I don't know exaclty how many more) the problem described above can be observed.
I hope, you will be able to reproduce and find the issue with this GSAK DB.
Best regards
marujave
Hi Menion
I did now some tests with the smaller DB and found that the problem has to do with the number of caches that are imported.
With 847 caches, the problem was not observed. I've now crated a bigger DB with 2671 caches. With this DB, the problem does not occur if only 1000 caches are imported. If more are imported, (I don't know exaclty how many more) the problem described above can be observed.
I hope, you will be able to reproduce and find the issue with this GSAK DB.
Best regards
marujave
Hello marujave,
thank you very much for the database. It helped. The issue found and fixed.
The new version is planned most probably on Monday.
Menion
Hello marujave,
thank you very much for the database. It helped. The issue found and fixed.
The new version is planned most probably on Monday.
Menion
Hi Menion
Thank you for the quick fix!
Best regards
marujave
Hi Menion
Thank you for the quick fix!
Best regards
marujave
Replies have been locked on this page!