cllocation and tracking

[zero_]

i've a gps tracker that now works great, except when iphone lost gps connection.
When the connection is lost the track make one or more point to a random location (as you can see in this image:



In which way i can discard this bad values?

I've think to do in this way:
before save my data i can do a sum of my integer values of current latitude and longitude and compare with integer values of my old latutude and longitude; if the difference is > somevalue i discard my data.

It will be a good thing?
There's some other nice tricks to do this?

Thank's

[smithdale87]

I think your approach will be good.

[zero_]

maybe i've found my fault:

in

locationManager:didFailWithError:

when i receive a kCLErrorNetwork or any other error except kCLErrorDenied i perform a stopupdatinglocation and a startupdatinglocation.

Now i've comment that two line and the app works good also when there's no gps signal, i make some other test tomorrow and post here the result.

[sunmom]

I M NEWER TO THIS
PLEASE HELP ME

[JamesJesst]

V interesting post. Thanks for this and your update, nice lateral solution to a problem I had been experiencing too. I'm not building a 'GPS-tracker' app like yours, but I do want to store CLLocation objects in an array so that I can use them later (not for map annotations). At the moment I just stick them in a NSMutableArray and php POST them to MySQL on a remote server.

However, my experience has not been a great one. Walking around town with the app activated creates a massive number of objects into that array that (I fear) may be crashing my app (there are no leaks, or at least none when on simulator). I'm wondering if you came up with a more elegant solution to this that you'd be prepared to share?

Many thanks

[zero_]

Originally Posted by JamesJesst

V interesting post. Thanks for this and your update, nice lateral solution to a problem I had been experiencing too. I'm not building a 'GPS-tracker' app like yours, but I do want to store CLLocation objects in an array so that I can use them later (not for map annotations). At the moment I just stick them in a NSMutableArray and php POST them to MySQL on a remote server.

However, my experience has not been a great one. Walking around town with the app activated creates a massive number of objects into that array that (I fear) may be crashing my app (there are no leaks, or at least none when on simulator). I'm wondering if you came up with a more elegant solution to this that you'd be prepared to share?

Many thanks

Hi James,

for some data i'm also storing all the values in a nsmutablearray. No leak problem also with 3hours of data collectios.
Maybe you can set a distance filter and collect datas in you array only when distance il > SOMEVALUES.

[JamesJesst]

Originally Posted by zero_

Hi James,

for some data i'm also storing all the values in a nsmutablearray. No leak problem also with 3hours of data collectios.
Maybe you can set a distance filter and collect datas in you array only when distance il > SOMEVALUES.

Hey - thanks for your quick response. Yeah, I am moderating the number of objects I'm storing; meantime you are managing to store 3 hours worth of CLLocation objects into that array without melting your app? OK, then I suspect my problem lies elsewhere - just having real difficulty working out where. The instruments say there are no leaks, and the whole thing works fine if it runs for just a couple of minutes or so.

Of course it may be that there is a POST limit to MySQL which, of course, will be easily solved by locally persisting using Core Data. Anyway, back to the drawing board, thanks anyway!

[sarunw]

Can I ask how do you keep location data (Core data or using archive) ?

[zero_]

hi sarunw,

in this specific app i use .csv file, i'm now working for a migration to .plist (but application works great also with .csv files)