Rough, yeah. I'll have to look into the best way to throw out inaccurate values. Otherwise the application tends to look a bit ugly (inertial navigation). For instance, if I walk by a window while my application is estimating movements on its own and happens to get a gps signal for a moment or two, then all of a sudden I get one or two inaccurate dots come on the screen and my estimated movement for where the droid is will start at that new GPS location.
At first I thought perhaps I would throw away a couple of initial values, but it doesn't seem as though there is a consistent number of bad results before receiving a good one. I'll see if there is a way to wait for a fine grained result related to triggering the onLocationChanged segment. Perhaps I can even put up a range zone around my estimated value, and as long as its close I can throw away any GPS that fall outside that range. That's my current thoughts. Thanks for the input Mike. ~ JFrog "Debugging something is twice as hard as coding it up the first time. Therefore, if we code something up as cleverly as possible, we are by definition not smart enough to debug it" -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en To unsubscribe from this group, send email to android-developers+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
