<div><p class="MsoPlainText"><span lang="EN-GB">Dear Mr. Takasu an other list members:</span></p><p class="MsoPlainText"><span lang="EN-GB"><br></span></p><p class="MsoPlainText"><span lang="EN-GB">I am
aware (not really aware, I've just heard off...) of the following solutions to
the positioning problem we are dealing with (GNSS positioning):</span></p>
<p class="MsoPlainText"><span lang="EN-GB"> </span>a) Least
mean square (LMS)</p>
<p class="MsoPlainText"><span lang="EN-GB">b)
Weighted least mean square (WLMS)</span></p>
<p class="MsoPlainText"><span lang="EN-GB">c)
Kalman filter</span></p>
<p class="MsoPlainText"><span lang="EN-GB">c.1) static
positioning: coordinates of the receiver are constants and the estimated clock
offset of the receiver is white noise with zero mean</span></p>
<p class="MsoPlainText"><span lang="EN-GB">c.2)
kinematic positioning for high receiver velocity: coordinates and clock offset
are modelled as zero mean white noise</span></p>
<p class="MsoPlainText"><span lang="EN-GB">c.3)
kinematic positioning for low velocity: the coordinates are modelled as a
random walk</span> </p>
<p class="MsoPlainText"><span lang="EN-GB">I think
that a) and b) are not suitable to RTK positioning because of the
ill-conditioning of the design matrix (very short observation time spans,
frequently one solution per epoch). I'm I right?</span> </p>
<p class="MsoPlainText"><span lang="EN-GB">If I'm
right then it follows that in RTK we are using some sort of "Kalman filter"
type solutions. And if we are using "Kalman filters" type solutions
then the following questions arise:</span> </p>
<p class="MsoPlainText"><span lang="EN-GB">1.
RTKPOST "static" is like c.1)?</span></p>
<p class="MsoPlainText"><span lang="EN-GB">2. RTKPOST "kinematic" is like c.2) or c.3)?</span></p>
<p class="MsoPlainText"><span lang="EN-GB">3. And
RTKPOST "single"? Is it LMS/WLMS?</span></p>
<p class="MsoPlainText"><span lang="EN-GB"> </span></p>
<p class="MsoPlainText"><span lang="EN-GB">Regards</span> </p>
<p class="MsoPlainText"><span lang="EN-GB">Antonio</span></p></div><div><br></div><br><br><div class="gmail_quote">2011/10/28 Tomoji TAKASU <span dir="ltr"><<a href="mailto:ttaka@yk.rim.or.jp">ttaka@yk.rim.or.jp</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Dear Antonio<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Can anyone explain give me a brief explanation regarding the differences<br>
between the position modes options in RTKPOST? I am especially interested in<br>
the following modes: Single, Kinematic, Static, Moving-base and Fixed.<br>
</blockquote>
<br></div>
I think they are generally common terminologies<br>
among GNSS positioning area except for "Fixed".<br>
<br>
So see the manual and search by Google.<br>
<br>
"Fixed" is special in RTKLIB. In the mode, the user<br>
position is fixed to a priori values specified by user<br>
options and other parameters like ionosphere,<br>
troposphere are estimated. It is also used for the<br>
analysis of measurement noise and multi-path with<br>
residuals.<br>
<br>
regards,<br>
<br>
*********<br>
Tomoji TAKASU<br>
<br>
------------------------------<u></u>--------------------<br>
From: "António Pestana" <<a href="mailto:afsm.pestana@gmail.com" target="_blank">afsm.pestana@gmail.com</a>><br>
Sent: Saturday, October 29, 2011 3:34 AM<br>
To: "Open Source GPS-related discussion and support" <<a href="mailto:foss-gps@lists.osgeo.org" target="_blank">foss-gps@lists.osgeo.org</a>><br>
Subject: [FOSS-GPS] Position modes in RTKPOST<div><div></div><div class="h5"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Can anyone explain give me a brief explanation regarding the differences<br>
between the position modes options in RTKPOST? I am especially interested in<br>
the following modes: Single, Kinematic, Static, Moving-base and Fixed.<br>
<br>
Regards<br>
<br>
Antonio<br>
<br>
</blockquote>
<br>
<br>
<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
______________________________<u></u>_________________<br>
This message is sent to you from <a href="mailto:FOSS-GPS@lists.osgeo.org" target="_blank">FOSS-GPS@lists.osgeo.org</a> mailing list.<br>
Visit <a href="http://lists.osgeo.org/mailman/listinfo/foss-gps" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/foss-gps</a> to manage your subscription<br>
For more information, check <a href="http://wiki.osgeo.org/wiki/FOSS-GPS" target="_blank">http://wiki.osgeo.org/wiki/<u></u>FOSS-GPS</a><br>
<br>
</blockquote>
<br>
<br>
______________________________<u></u>_________________<br>
This message is sent to you from <a href="mailto:FOSS-GPS@lists.osgeo.org" target="_blank">FOSS-GPS@lists.osgeo.org</a> mailing list.<br>
Visit <a href="http://lists.osgeo.org/mailman/listinfo/foss-gps" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/foss-gps</a> to manage your subscription<br>
For more information, check <a href="http://wiki.osgeo.org/wiki/FOSS-GPS" target="_blank">http://wiki.osgeo.org/wiki/<u></u>FOSS-GPS</a><br>
</blockquote></div><br>