<html><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:12pt"><div><span>Dear Felipe G. Nievinski,<br><br>Sorry for my delay.<br><br>RTKLIB, rnx2rtkp, do not have stop and go processing option, at least 2.4.2.<br>I process as kinematic and use the tagged rinex information to extract stoped location interval ( mean position).<br><br>I can share my test data if you wanna see it.<br><br>I do not know if the processing algorithm can or must use some constraint for stop and go.<br>my doubts:<br>1) at field session start point, the rover must stay over a known point for a while or use antenna swap or a fixed lengh bar as initialization.<br>2) how to restart in case of loss of lock, restart from previous good measured point ?<br>3) can we perform backward solution, and discard the signal loss portions and remeasure it back later ? i guess yes.<br><br>back
to time:<br>I have one u-blox 4T (time receiver ).<br>looking inside RINEX files I realise some time offset like this:<br> 12 3 18 14 20 9.9940000 0 10G 2G26G25G 9G15G 4G29G12S20G27<br>we have 9.994, where should be 10.000. RINEX file starts as integer seconds. <br>a) Is this a cristal oscillator instability ?<br>b) could it affect pseudorange and carrier phase measurements ?<br>c) could this clock jump effects be modelled and fixed by software ?<br></span></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif; background-color: transparent; font-style: normal;"><br><span></span></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif; background-color: transparent; font-style: normal;"><span>regards</span></div><div style="color: rgb(0, 0, 0); font-size: 16px;
font-family: HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif; background-color: transparent; font-style: normal;"><span>julio menezes</span></div><div style="display: block;" class="yahoo_quoted"> <br> <br> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 12pt;"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 12pt;"> <div dir="ltr"> <font face="Arial" size="2"> Em Sexta-feira, 17 de Janeiro de 2014 3:05, Felipe G. Nievinski <fgnievinski@gmail.com> escreveu:<br> </font> </div> <div class="y_msg_container"><div id="yiv0442426572"><div dir="ltr">Dear Julio,<div><br></div><div>did you find a solution to process stop-and-go data with RTKLIB?</div><div>I'm facing the same problem.</div><div><br></div><div><<a rel="nofollow" target="_blank"
href="http://lists.osgeo.org/pipermail/foss-gps/2012-August/000779.html">http://lists.osgeo.org/pipermail/foss-gps/2012-August/000779.html</a>></div>
<div><br></div><div>Thanks,</div><div>-Felipe.</div><div><br></div></div></div><br>_______________________________________________<br>This message is sent to you from <a ymailto="mailto:FOSS-GPS@lists.osgeo.org" 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><br></div> </div> </div> </div> </div></body></html>