<div dir="ltr">Hi Graziano.<div class="gmail_extra"><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Date: Mon, 16 Nov 2015 15:24:27 +0100<br>
From: "<a href="mailto:graziano.navalesi@hotmail.com" target="_blank">graziano.navalesi@hotmail.com</a>" <<a href="mailto:graziano.navalesi@hotmail.com" target="_blank">graziano.navalesi@hotmail.com</a>><br>
To: <a href="mailto:foss-gps@lists.osgeo.org" target="_blank">foss-gps@lists.osgeo.org</a><br>
Subject: [FOSS-GPS] RTKLIB - RINEX<br><br>
Good afternoon, I state to know little English and RTKLIB.<br>
I can not with RTKLIB to upload files containing RINEX MARKER and MARKER<br>
NUMBER NAME. I wish recordings made inside a MARKER NAME were loaded as<br>
a single point of coordinates weighted averages.<br>
Thanks, Graziano Navalesi<br>
<br></blockquote><div><br></div><div>Typically rinex marker records are used for stop-and-go type of surveys. AFAIK, RTKLIB doesn't support this type of data processing, see RTKLIB Release Notes:</div><div><div><<a href="http://gpspp.sakura.ne.jp/rtklib_2.4.2_releasenote.htm">http://gpspp.sakura.ne.jp/rtklib_2.4.2_releasenote.htm</a>></div><div>"(12) Support "STOP and GO" mode for RTK or post processing kinematic (not yet)"</div><div><br></div><div>As you pointed out, it could be implemented as a weighted average of epochs processed as kinematic during a given point occupation window. There has been previous discussions, see:<br></div></div><div><<a href="http://lists.osgeo.org/pipermail/foss-gps/2014-January/001026.html">http://lists.osgeo.org/pipermail/foss-gps/2014-January/001026.html</a>></div><div>There has also been discussions about hardware options:</div><div><<a href="http://www.navsparkforum.com/viewtopic.php?f=24&t=189" target="_blank">http://www.navsparkforum.com/viewtopic.php?f=24&t=189</a>></div><div><br></div><div><div>Finally, the upcoming Reach module uses RTKLIB, so its ReachView app could be a good starting point:</div></div><div><<a href="http://docs.emlid.com/reach/Reach/reachview-app/reachview-app/">http://docs.emlid.com/reach/Reach/reachview-app/reachview-app/</a>><br></div><div>Maybe such a feature could be crowd-funded?</div><div><br></div><div>Regards,</div><div>-Felipe.</div></div></div></div>