<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EstiloCorreioEletrnico17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=PT link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'>Thank you, once again. Now it’s time for a careful reading of appendix E.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'>Regards<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'>Antonio<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><div style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>De:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> foss-gps-bounces@lists.osgeo.org [mailto:foss-gps-bounces@lists.osgeo.org] <b>Em nome de </b>Felipe G. Nievinski<br><b>Enviada:</b> sábado, 14 de Fevereiro de 2015 14:40<br><b>Para:</b> foss-gps@lists.osgeo.org<br><b>Assunto:</b> Re: [FOSS-GPS] RTKPos processing options<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt'><p class=MsoNormal>One more question: integer ambiguity is estimated and resolved by<br>epoch<span style='font-family:"Cambria Math",serif'>‐</span>by<span style='font-family:"Cambria Math",serif'>‐</span>epoch basis. So, if I understand correctly each epoch we have to<br>deal with one unknown ambiguity for each observation. So the number of<br>unknowns equals the number of the available observation equations plus the<br>position unknowns plus etc... How can we manage to get an unique solution<br>to the problem?<o:p></o:p></p></blockquote><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal>It's only in instantaneous AR that ambiguities are reset every epoch. Even then, there are always two observations per satellite signal: one carrier-phase and one pseudorange. So if there are, say, 7 satellites visible from a single-frequency receiver, there are at least 7 x 2 = 14 observations and 7 + 4 = 11 unknowns (7 ambiguities, 3 position coordinates, and 1 receiver clock). As 14 > 11, it's still doable. Furthermore, one can track multiple signals broadcast by a given satellite, which increases redundancy.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>If using fixed positioning mode, there would be only 7 + 1 = 8 unknowns per epoch. And if using static mode, eventually the position coordinates will be well known, so the filter starts having 11 unknowns but ends with effectively only 8 unknowns per epoch; and if you run the filter backwards (then later combine it with the forward run, as RTKPOST does), the start of the session is covered as well.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Now, that was for instantaneous AR, and I don't think you'd ever want to use it, except perhaps if you're investigating the quality of your data, or into some research about the various biases. Continuous AR carries over the previous epoch's ambiguities estimate and their uncertainty into the next epoch, so that eventually the ambiguities will have converged.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>After ambiguities are estimated as "float" (floating-point values), RTKPLOT will also try to resolve double-differenced ambiguities as integer multiples of the wavelength, as they're supposed to be (that's a physical constraint). Finally "fix and hold" means that once an ambiguity is successfully resolved an an integer, it's assumed exactly known afterwards, which improves the precision of the position coordinate estimates subsequently.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Hope this helps.<o:p></o:p></p></div><div><p class=MsoNormal>-Felipe.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div></div></div></div></div></body></html>