<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Thanks a lot for the hint! Can you perhaps detail a bit on the second part - how would I use GPS to handle the drift (also, if you knew a document accessible on the web describing this, that would be extremely helpful!)? </div><div><br></div><div>Regarding the first point, is it correct that "continuous" integration uses the following equation:</div><div><br></div><div>v(t1) = v(t0) + A * dt?</div><div><br></div><div>But then,  how do I combine the measures for the 3 axes - I found a formula that takes the square root of all three values squared, would that be correct?</div><div><br></div><div>Thanks in advance,</div><div>Sigrid</div><div><br></div><div><br></div><div><br></div><div><br></div><br><div><div>Am 03.11.2010 um 00:18 schrieb Patrick Li:</div><br class="Apple-interchange-newline"><blockquote type="cite">I think the most accurate thing you can probably do is integrate the accelerometer data to get velocity, and use the GPS data to handle the accumulating numerical drift. My friend used that approach for this thesis project for good results.<div>   -Patrick<br><br><div class="gmail_quote">On Tue, Nov 2, 2010 at 5:27 PM, <a href="mailto:keydana@gmx.de">keydana@gmx.de</a> <span dir="ltr"><<a href="mailto:keydana@gmx.de">keydana@gmx.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> Thanks Noel - the scale would be meters rather, but I somehow assumed that this might be too small-scale for GPS ...<br> <br> I guess I really ought to compare both measures, but for the GPS part, I wonder what would be the most "architecturally adequate" way to adapt 'world-updater' s contract to handle the additional geolocation field (and the other fields currently unused, possibly).<br> <br> ciao,<br> Sigrid<br> <br> <br> <br> Am 02.11.2010 um 22:08 schrieb Noel Welsh:<br> <div><div></div><div class="h5"><br> > I don't /really/ know, but isn't one reading from the accelerometer<br> > and the other from GPS? The answer depends, I think, on the distance<br> > over which you want to operate. If you want velocity from, e.g., hand<br> > movements, the accelerometer is the way to go. If you want velocity<br> > over large scale (metres, kms) use GPS.<br> ><br> > HTH,<br> > N.<br> ><br> > On Tue, Nov 2, 2010 at 5:52 PM, <a href="mailto:keydana@gmx.de">keydana@gmx.de</a> <<a href="mailto:keydana@gmx.de">keydana@gmx.de</a>> wrote:<br> >><br> >> Hi,<br> >> I am wondering how best to calculate velocity in a moby/phonegap/android application.<br> >> In general, would anyone have experience (or intuition) whether velocity might better be calculated from the acceleration values delivered by phonegap's Acceleration object, or directly be extracted from the Position object returned from Geolocation (it has a field 'velocity')?<br> <br> _________________________________________________<br>  For list-related administrative tasks:<br>  <a href="http://lists.racket-lang.org/listinfo/users" target="_blank">http://lists.racket-lang.org/listinfo/users</a><br> </div></div></blockquote></div><br></div> </blockquote></div><br></body></html>