Thanks for the tip! By extracting the receiver clock bias from the status-file, and playing around with the RTKPOST settings I now get better results: http://imagebin.org/283266
There's still a 4 ns offset between the CSRS and RTKLib solutions - I don't know where it comes from?? ESA gLAB arrives at the same result as CSRS, so maybe I will look closely at the gLAB settings next. Thanks for your help - I will try to write a blog post about my findings if/when I get at least three methods to agree on the results (CSRS, gLAB, and RTKLIB) Anders On Sat, Dec 21, 2013 at 12:07 AM, Felipe G. Nievinski <fgnievin...@gmail.com > wrote: > I don't think you should use the time tag in the .pos file. > I'd use instead the CLK records in the .stat file. > See Appendix B.3 in the docs, "Solution Status File": > > *Receiver Clockâbias States* > *Estimated receiver clock bias parameters. The format of a record is as > follows.* > *$CLK,week,tow,stat,rcv,clk1,clk2,clk3,clk4* > *week/tow : gps week no/time of week (s)* > *stat : solution status* > *rcv : receiver (1:rover,2:base station)* > *clk1 : receiver clock bias GPS (ns)* > *clk2 : receiver clock bias GLONASS (ns)* > *clk3 : reserved* > *clk4 : reserved* > >
_______________________________________________ This message is sent to you from FOSS-GPS@lists.osgeo.org mailing list. Visit http://lists.osgeo.org/mailman/listinfo/foss-gps to manage your subscription For more information, check http://wiki.osgeo.org/wiki/FOSS-GPS