I know this has been discussed fairly extensively, but would like some final clarification as I came away from reading the links below more confused by the different approaches/opinions than I started with. So don’t get angry
I’m a base over known position person…usually.
If a base is set up to collect and average n minutes of data before establishing itself as a base, in which file is the base location that is transmitted to a rover stored??
My understanding is that this position is stored in the RTCM3 file logged by the rover. This file is converted (RTKCONV) from RTCM3 to a .obs, and the location or “APPROX POSITION XYZ” is given in the header in ECEF coordinates. Is this correct? Bearing in mind the .obs file created from converting the .UBX logged at the base also has a set of ECEF coordinates (which I assume is the product of averaging for n minutes).
A comparison between the two sources of base location in my case (lat, lon, elp, X, Y, Z):
Rover logged RTCM3 to .obs:
-16.8038377, -179.7822333, 56.261, -6107509.9512, -23213.1962, -1832078.4976
Base logged .UBX to .obs:
-16.8038347, -179.7822344, 54.239, -6107508.1108, -23212.7469, -1832077.6033
Not massively different but certainly different enough to cause errors.
You may be asking in what way do I care…well I have corrected the base (Static PPK) and would really like to know what the dX, dY, and dZ are from what the rover thought it was.
Lastly, why are they different???
Thanks in advance, don’t want to open a can of worms!