This might be useful<div><br></div><div><a href="https://docs.google.com/viewer?a=v&q=cache:KwqABhW5RwQJ:webone.novatel.ca/assets/Documents/Waypoint/Reports/RelativeMovingBaselineSoftware.pdf+moning+baseline&hl=en&gl=au&pid=bl&srcid=ADGEESip1pqI9lDLzK30iN-QyiqdifxWWk-ETfQM2hUeMBkympYL-FjapqnmtzCz3cSMxLfvs2viTjUlPxZP3fmUFVkYtAsdmmBDpT3MjGTXzajnfGsw9L2NNdtIthScp7Ba5-_rGiNp&sig=AHIEtbT0C2pCNKVdKdZDw8kXC9D4SJ_Egw">https://docs.google.com/viewer?a=v&q=cache:KwqABhW5RwQJ:webone.novatel.ca/assets/Documents/Waypoint/Reports/RelativeMovingBaselineSoftware.pdf+moning+baseline&hl=en&gl=au&pid=bl&srcid=ADGEESip1pqI9lDLzK30iN-QyiqdifxWWk-ETfQM2hUeMBkympYL-FjapqnmtzCz3cSMxLfvs2viTjUlPxZP3fmUFVkYtAsdmmBDpT3MjGTXzajnfGsw9L2NNdtIthScp7Ba5-_rGiNp&sig=AHIEtbT0C2pCNKVdKdZDw8kXC9D4SJ_Egw</a> </div>
<div><br></div><div>regards</div><div><br><br><div class="gmail_quote">On Tue, Jan 3, 2012 at 7:23 AM, julio menezes <span dir="ltr"><<a href="mailto:yjmenezes@yahoo.com.br">yjmenezes@yahoo.com.br</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">--- Em seg, 2/1/12, Mauro Ugarte Avilés <<a href="mailto:mauro.ugarte@cefop.udec.cl">mauro.ugarte@cefop.udec.cl</a>> escreveu:<br>
<br>
> De: Mauro Ugarte Avilés <<a href="mailto:mauro.ugarte@cefop.udec.cl">mauro.ugarte@cefop.udec.cl</a>><br>
> Assunto: Re: [FOSS-GPS] Re: New Project with RTKlib & need help.<br>
> Para: "Open Source GPS-related discussion and support" <<a href="mailto:foss-gps@lists.osgeo.org">foss-gps@lists.osgeo.org</a>><br>
> Data: Segunda-feira, 2 de Janeiro de 2012, 17:55<br>
<div class="im">><br>
> ><br>
> > Taking your words, I'm not good at GPS relative terms<br>
> and algorithms too.<br>
> ><br>
> Me neither :-)<br>
> > I think that the moving base must have an fixed and<br>
> known lenght .<br>
> If you review the "setting2" tab on RTKNAVI 2.4.x options,<br>
> you will see<br>
> that the "Baseline Length Constraint (m)" is an option, not<br>
> a<br>
> requirement, even when "Moving Base" is selected as<br>
> positioning mode on<br>
> "setting1" tab. Considering this, I thought that both<br>
> options where<br>
> valid (constrained and unconstrained length). One may think<br>
> that is just<br>
> a programming bug if it remains as an option and not as a<br>
> requirement,<br>
> but if you select "moving base" you will see that on the<br>
> "Positions" tab<br>
> automatically the option to input the base antenna position<br>
> dissapeared,<br>
> from which I conclude that nothing is left to chance on<br>
> this swiss knife<br>
> that RTKlib is :-).<br>
<br>
</div>Hi Mauro,<br>
<br>
tks for your explanation, I hope to return to study the RTKLIB very soon.<br>
As you say, "nothing is left to chance on this swiss knife" !<br>
A moving base without lenght constrains let me realy impressed with RTKLIB.<br>
My tks for all developers.<br>
<br>
[]s<br>
<span class="HOEnZb"><font color="#888888">julio menezes<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
This message is sent to you from <a href="mailto:FOSS-GPS@lists.osgeo.org">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/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/FOSS-GPS</a><br>
</div></div></blockquote></div><br></div>