Hi David, thanks for your respond
I already solved the problem here
The problem's my mistake in a code at the smoothing formula, i use the
wrong value
Anyway, anybody here know about high pass filter?
Thanks
On Mon, Mar 26, 2012 at 5:51 PM, David Griffiths davi...@cordic.com wrote:
Sorry, my
As well as multiplying twice by 1.0E6 (instead of multiplying and then
dividing), another error is
​smoothingCoor[i] = smoothingCoor [i] +alpha * (coor[i] -
smoothingCoor[i]);
This should be
smoothingCoor[i] = (smoothingCoor [i] * (1.0 - alpha)) + alpha * (coor[i]
- smoothingCoor[i]);
Sorry, my mistake.
The line
smoothingCoor[i] = smoothingCoor [i] +alpha * (coor[i] - smoothingCoor[i]);
is correct as it stands. However my comment on your nearing smoothing not
taking into account the 359 degrees problem is correct.
Two other problems with the code you have posted: I
Hi jinja, thanks for the help
I already tried with the fixed point but it still get me the wrong value
Are there something filtering that we can use to filter latitude and
longitude ? (except kalman filter)
Sory for my bad english
On Fri, Mar 16, 2012 at 12:17 AM, Jinja neiljmar...@gmail.com
Hi, thanks for all the input
Right now i still don't have any solution for get the best latitude and
longitude
I want to use kalman filter at the first, but after read some paper and
articles kalman filter is need the value from accelorometer
Unfortunately my requirement for this application is
Hi Concave,
Okay, I see that you need to keep the values as x1E6 now. However, you are
still multiplying by 1E6 twice, you only need to do it once. Remove the
*1E6 from the following lines, so..
smoothLat = (int) (smoothingCoor [0] * 1E6);
smoothLongi = (int) (smoothingCoor [1] * 1E6);
Hi,
There is a section with the title Maintaining a current best estimate
in the following link, it contains an implementation of a method called
isBetterLocation.
http://developer.android.com/guide/topics/location/obtaining-user-location.html
Hope this helps
/Yaron
--
Yaron Reinharts
Hello, I've never dealt with GPS data before, but having a quick look at
your code it looks like you have a mismatch in converting your data to and
from integers and doubles.
I notice you multiply by 1E6 when extracting the lat/long, presumably this
is to maintain some accuracy during the
8 matches
Mail list logo