RTK

Makefile modifications Adding -gdwarf-4 -g3 enables gdb debugger to be triggered within VSCode Before CFLAGS = -Wall -O3 -ansi -pedantic -Wno-unused-but-set-variable -I$(SRC) $(OPTS) After CFLAGS = -gdwarf-4 -g3 -Wall -O3 -ansi -pedantic -Wno-unused-but-set-variable -I$(SRC) $(OPTS) tasks.

Following was written by rtklibexplorer. As of now, all comments expressed on this page are of rtklibexplorer and the original source document can be found here. I’ve added it here for ease access, as well as it’ll allow Google’s SEO engine to capture the content to help others as well as create even more awareness of rtklibexplorer’s top notch work.

Overview Config Timetag If you would like to replay your live data with rtkcv, you need to generate a timetag file per input source logstr1-type =file # (0:off,1:serial,2:file,3:tcpsvr,4:tcpcli,6:ntripsvr) logstr2-type =file # (0:off,1:serial,2:file,3:tcpsvr,4:tcpcli,6:ntripsvr) logstr3-type =file # (0:off,1:serial,2:file,3:tcpsvr,4:tcpcli,6:ntripsvr) logstr1-path =%Y%m%d%h%M_logstr1::T logstr2-path =%Y%m%d%h%M_logstr2::T logstr3-path =%Y%m%d%h%M_logstr3::T Sequence Diagram Scroll down (bug in rendering)

Sequence Diagram Scroll down (bug in rendering) %%{init: {'theme':'forest'}}%% sequenceDiagram autonumber activate relpos() relpos()->>relpos(): satposs() compute satellite positions, velocities and clocks note over zdres(): Base station relpos()->>zdres(): undifferenced phase/code residuals (apriori/misclosure) zdres()->>relpos(): .

Sequence Diagram Scroll down (bug in rendering) %%{init: {'theme':'forest'}}%% sequenceDiagram autonumber alt PMODE_SINGLE single point positioning rtkpos()->>pntpos(): rover position and time by single point positioning pntpos()-->>rtkpos(): return rtkpos()->>rtkpos(): return 1 end alt PMODE_PPP_KINEMA precise point positioning rtkpos()->>pppos(): precise point positioning pppos()-->>rtkpos(): return stat rtkpos()->>rtkpos(): return 1 end alt PMODE_MOVEB moving baseline rtkpos()->>pntpos(): estimate position/velocity of base station pntpos()-->>rtkpos(): return rtkpos()->>rtkpos(): timediff() alt TTOL_MOVEB time sync tolerance for moving-baseline rtkpos()->>rtkpos(): return 0 end rtkpos()->>rtkpos(): time-synchronized position of base station else maxtdiff max difference of time (sec) note over rtkpos(): Static base station correction QC rtkpos()->>rtkpos(): age of differential error rtkpos()->>rtkpos(): return 1 end note over rtkpos(): Always runs for PMODE_MOVEB (moving base) and PMODE_FIXED (static base) rtkpos()->>relpos(): relative positioning relpos()->>rtkpos(): return rtkpos()->>rtkpos(): outsolstat() rtkpos()->>rtkpos(): return 1 Reference : https://mermaid.

The future of RTK had always intrigued me, especially as I was trained with the yellow kit and flat white frisbee. Then, I went on to study an area of research that promised to make RTK irrelevant, called PPP. Given my foundation began in a world of RTK but mastered the art of GNSS measurement processing with PPP, it ignited the search for the answer if RTK is still relevant and are we seeing the signs of a return of RTK.

Typical RTK performance is limited to baselines of <10-15 km, as longer distances cause increased measurement errors, which cannot …

This study assessed the vertical accuracy of measurement using different types of survey techniques namely LiDAR, Aerial Photogrammetry …