Teleporting point
Hi. I just discovered very strange bug.
Lest start from my observations. When Im on my bike, and the road is very very bumpy, my HTC Desire Z is resetting itself. And after returning to normal state, and starting Locus, im getting back to record the last recorded track. After a while Im discovering that my track has got ~8000km length. WTF? I had this situation a few times. Im attaching a KML file of this track. It looks like, the last point before restart is recorded as S 00.00000° | E 000.00104°. After trying to edit the track, im fully successful. I just need to find this magic point and delete it. After that I have the valid track back. Uhh.
https://dl.dropbox.com/u/4747589/Mega...
IT IS VERY POSSIBLE, that this bug is occuring not only after restarting the device or force close the Locus. This bug needs more testing.
Shit. I jusy found more complicated example.
The track has about 26000km. And I think the bug happend a few times during recording of this track, thats why. Anyway, it looks like Locus cant see these teleportaion points. And it behaves strangely. I cant jump to every point of the track, just to eg. 14001, 14501, 15001. And the track is straight, not curvy. So I cant see the magical points. But when Im exporting such a track to KML, The track is in the right place, and the track is curvy as normal. Of course there are this magical jumps to S 00.00000° | E 000.00104° which are invalid.
The same problem 
thanks for report. I did one check on wrong points, that check time and distance between previous and new points. Check next test or market version and let me know if this happen again. I`ll not check your attached track for now, we`ll see in next version ...
thanks for report. I did one check on wrong points, that check time and distance between previous and new points. Check next test or market version and let me know if this happen again. I`ll not check your attached track for now, we`ll see in next version ...
Great, but... will I be able to repair my invalid track? Why during edit mode of the track, I can only jump every 500 points? Too many points on the screen? Too long distances on the screen?
Great, but... will I be able to repair my invalid track? Why during edit mode of the track, I can only jump every 500 points? Too many points on the screen? Too long distances on the screen?
repair invalid tracks: sorry, no. You have to fix them on yourself. About "every 500th, etc ...". It`s quite simple. Display map on screen in some high zoom level and you`ll see all points. Zoom out, map will be slower and slower because more points is visible on screen. Locus anyway since some zoom level begin to optimize track and display only every Xth point. Thanks to this, you may display quite a lot of tracks and Locus remain still quite stable.
So if you want to find any specific point, I suggest to zoom in a little and then move between points by arrows in left panel
repair invalid tracks: sorry, no. You have to fix them on yourself. About "every 500th, etc ...". It`s quite simple. Display map on screen in some high zoom level and you`ll see all points. Zoom out, map will be slower and slower because more points is visible on screen. Locus anyway since some zoom level begin to optimize track and display only every Xth point. Thanks to this, you may display quite a lot of tracks and Locus remain still quite stable.
So if you want to find any specific point, I suggest to zoom in a little and then move between points by arrows in left panel
there is still something wrong:
Im pretty sure it was introduced in the newest version. I didnt experienced anything like that for a long time, until now.
https://dl.dropbox.com/u/4747589/Tysi...
there is still something wrong:
Im pretty sure it was introduced in the newest version. I didnt experienced anything like that for a long time, until now.
https://dl.dropbox.com/u/4747589/Tysi...
this bug is still in version 2.6.1
this bug is still in version 2.6.1
hmm hard work. You know that it`s not directly bug in Locus, but rather problem of you GPS right? Locus already have a few check, to prevent some issues. How this one happen? Anyway if this is one point in one of 100 recorded tracks, it`s not a general issue and "Delete" feature on specific point, do it`s work fast and easy :)
hmm hard work. You know that it`s not directly bug in Locus, but rather problem of you GPS right? Locus already have a few check, to prevent some issues. How this one happen? Anyway if this is one point in one of 100 recorded tracks, it`s not a general issue and "Delete" feature on specific point, do it`s work fast and easy :)
this is occuring only after the unnormal exit of the app ( end of the batteries, restart, force close and so on). did you make some kind of check after the Locus is being started and it detects that the recording was not finished? maybe add some area around N 0 and E 0 to be "illegal" after the restart? or check for too long jumps? this one is several km long. delete point is almost alright, but not when the track is bigger then 1mb :/
this is occuring only after the unnormal exit of the app ( end of the batteries, restart, force close and so on). did you make some kind of check after the Locus is being started and it detects that the recording was not finished? maybe add some area around N 0 and E 0 to be "illegal" after the restart? or check for too long jumps? this one is several km long. delete point is almost alright, but not when the track is bigger then 1mb :/
there is many checks. On too big distance compare to previous point, on invalid (zero) coordinates, on invalid altitude & accuracy points etc. It`s quite mystery that these points come through all these checkings ...
1MB limit is really bad. I`m currently trying to figure out how to create better database system for storing tracks and no success. Unfortunately I`m not too much skilled with database systems ... because you may simply insert, delete, edit point of track in locus, I have problems how to keep in simple database correct order. Because Android 4.0 have increased limit on 2M for this query, I have strong feeling to keep it as is now and just add some automatic separating into two or more tracks :/
there is many checks. On too big distance compare to previous point, on invalid (zero) coordinates, on invalid altitude & accuracy points etc. It`s quite mystery that these points come through all these checkings ...
1MB limit is really bad. I`m currently trying to figure out how to create better database system for storing tracks and no success. Unfortunately I`m not too much skilled with database systems ... because you may simply insert, delete, edit point of track in locus, I have problems how to keep in simple database correct order. Because Android 4.0 have increased limit on 2M for this query, I have strong feeling to keep it as is now and just add some automatic separating into two or more tracks :/
I know this "bug" is problematic, because its hard to recreate:/
I know this "bug" is problematic, because its hard to recreate:/
it is so good that this issue stopped so many months ago:) thanks
it is so good that this issue stopped so many months ago:) thanks
hmm perfect. Many problems is solved "automatically" when something other change. Here was big change in database structure, so it probably also fixed this one. Perfect :)
hmm perfect. Many problems is solved "automatically" when something other change. Here was big change in database structure, so it probably also fixed this one. Perfect :)
Replies have been locked on this page!