Rel. 2.7.1. / geocaching / import performance / aditional waypoints
Unfortunately I found some issues in the new release 2.7.1. Sorry that I had no time for testing it at the beta-release (I have been a bit offline the last weeks).
1. Slow import of pocket querys
I downloaded a ZIP-File of my founds and imported it into my category "founds".
The import has to overwrite the existing geocaches in this category, but since the new release it lasts several times longer to import. Before it was roughly about 600 geocaches in 1 minute (as far as I can remember), now i sit here with about 15 geocaches in 1 minute over 40 times slower :(.
Verified the performance with a pocket query of 66 geocaches (4,5 min) with ziped GPX and GC Live api.
Maybe the merging of informations during import (I use the setting of keeping my entered informations) needs to much time with the new database structure...
2. Editing of aditional waypoints of a geocache
If I remember correctly, it was possible to edit aditional waypoints out of the coresponding overview from the geocache details. This doesn`t work anymore. Uncomfortable workarround is to try to find the aditional waypoint on the map, click it there and choose edit.
3. Icons of aditional waypoints of a geocache
When I`m editing an aditional waypoint, the icon disappears. If I go to edit an aditional waypoint and explicit select an icon for it (there is no icon shown at the editing page), then the icon is shown on the map (till next editing).
4. Showing coordinates of aditional waypoints
In the geocache overview of the aditional waypoints, the coordinates of the aditional waypoints are not shown.
background info:
Motorola Defy+, Android 2.3.6, not rooted
overall geocaches in DB: about 8300 in different categories
category of homezone (the largest) with 2984 geocaches
database conversion took about 17 minutes
I`m looking forward for getting fixed my first class geocaching tool. Thank you for your support!
The same problem 
Ah, I overlooked that point 2 is solved for Rel. 2.7.2: http://gsfn.us/t/37d7g
and point 3 is also solved with http://gsfn.us/t/37d7k
Ah, I overlooked that point 2 is solved for Rel. 2.7.2: http://gsfn.us/t/37d7g
and point 3 is also solved with http://gsfn.us/t/37d7k
I had similar performance issues, see http://forum.locusmap.eu/viewtopic.ph....
I think, but don`t know, that it could be related to the size of the database (Locus/data/database/waypoint.db (?)) versus the amount of available ram in your phone.
I had similar performance issues, see http://forum.locusmap.eu/viewtopic.ph....
I think, but don`t know, that it could be related to the size of the database (Locus/data/database/waypoint.db (?)) versus the amount of available ram in your phone.
RAM have no effect, or at least not a huge.
anyway, point 2, 3 are already solved. On 1., I was working with peter for quite a long time and result is increased speed of import on my device from around a 70s to 40s, so you`ll see how fast it is now
ad 4., may you post a screenshot? If I tap on any waypoint attached to cache in list of waypoints, I normally see coordinates at the bottom of dialog
RAM have no effect, or at least not a huge.
anyway, point 2, 3 are already solved. On 1., I was working with peter for quite a long time and result is increased speed of import on my device from around a 70s to 40s, so you`ll see how fast it is now
ad 4., may you post a screenshot? If I tap on any waypoint attached to cache in list of waypoints, I normally see coordinates at the bottom of dialog
Well, as I explained, I reduced the size of the database from 43Mb to under 10Mb and got at least 2x speed increase (same file in less than half the time).
I couldn`t really test with different amounts of RAM, it was just a guess :)
Well, as I explained, I reduced the size of the database from 43Mb to under 10Mb and got at least 2x speed increase (same file in less than half the time).
I couldn`t really test with different amounts of RAM, it was just a guess :)
there was problem with searching for duplicites. Well, "problem" is not perfect word. Just not best way how to work with database. You`ll see in new version, it will be much faster. As well as I just increased speed of track loading to half! Uff :)
there was problem with searching for duplicites. Well, "problem" is not perfect word. Just not best way how to work with database. You`ll see in new version, it will be much faster. As well as I just increased speed of track loading to half! Uff :)
About 4: Maybe it was like this before 2.7.x, If I go in the overview of aditional waypoints of the geocache, I can not see the coordinates.
About 4: Maybe it was like this before 2.7.x, If I go in the overview of aditional waypoints of the geocache, I can not see the coordinates.
yes it was same before. So if I understand correctly, you miss visible coordinates of waypoints in this list right?
Hmm is this really useful? Do you need these coordinates for something?
yes it was same before. So if I understand correctly, you miss visible coordinates of waypoints in this list right?
Hmm is this really useful? Do you need these coordinates for something?
The performance of 2.7.2 is awesome!
The performance of 2.7.2 is awesome!
glad to hear :)
glad to hear :)
After the fixing of editing the aditional waypoints this is not very important anymore.
Sometimes when checking the coordinates of several aditional waypoints (i.e. which one was the one with E 09° 08.689`?) then it could be an advantage to see it directly. But I can click on it and see the coordinates.
After the fixing of editing the aditional waypoints this is not very important anymore.
Sometimes when checking the coordinates of several aditional waypoints (i.e. which one was the one with E 09° 08.689`?) then it could be an advantage to see it directly. But I can click on it and see the coordinates.
Yes, thank you for fixing it and the again very good perfornance!
Yes, thank you for fixing it and the again very good perfornance!
you`re welcome :). There is now not much place to improve, but in other places is. So don`t forget to push me a little ;)
you`re welcome :). There is now not much place to improve, but in other places is. So don`t forget to push me a little ;)
Replies have been locked on this page!