just checking… you know u can change the number of decimal output for .pos file times in RTKPOST [options] > [output] page? no need to go into the rinex or .ubx file to get all 7 decimals.
going over the error estimates again, i assign a standard deviation for easting as the square root, of the sum of the squares of the following:
- 0.01m as a base uncertainty
- timing uncertainty * E component of horizontal velocity
- stability number (standard deviation of 4 surrounding dE)
- Q penalty (assigned if sum of 3 surrounding Q’s is > 3. It is arbitrary 0.5m * sqrt(sum(3 Q’s))
northing stdev is assigned similarly. height same except 0.015m base uncertainty and arbitrary 0.8m for Q penalty factor. obviously with my 4ms timing, the timing uncertainty dominates the horizontal stdev in straight flight, with the stability number blowing it out in turns and in wind. I don’t care for pos file error estimates if phase fix hasn’t been held for a few epochs and that is the purpose of my Q penalty. I just tried to think of the relevant error sources and apply them in the quantities I think were appropriate. I haven’t done a post-adjustment, group variance factor test to see if the stdev’s are statistically ‘correct’, but the errors in photoscan post adjustment looks fine to my eye. and my calibration/check points hit pretty well.