Whoops, [USER=520]@byanez[/USER] and I exchanged email earlier and I did not follow up with the conclusion here.
The conclusion may actually be of value to others so I will post an abbreviated solution here. I don’t know if Byanez wants his data files strewn around the internet so I have purposely obfuscated some of the details, I am sure the big picture will survive:
[INDENT]It looks like you shot several of the points (1,2,3) more than once, then instructed SurvCE to do a GPS average on the multiple observations of each point. The GPS average overrides the reprocessed points. Thus points 1, 2 and 3 appear to not reprocess (in reality they do, but are overwritten by the averaged SP entry.)
For example:
[INDENT]GPS,PN1,LAxxx,EL1017.313066,–MAG
–GS,PN1,N xxx,EL3420.6261,–MAG
G0,2016/11/25 22:09:27,(Average) – Base ID read at rover: 0001
G1,BPBP004,PN1,DX-7.30561,DY-14.32856,DZ-23.53142
G2,VX0.00015295,VY0.00017713,VZ0.00021476
G3,XY0.00010786,XZ-0.00007321,YZ-0.00011786
GPS,PN1,LAxxx,EL1017.314808,–MAG
–GS,PN1,N xxxEL3420.6318,–MAG
G0,2016/11/25 22:10:37,(Average) – Base ID read at rover: 0001
G1,BPBP004,PN1,DX-7.30817,DY-14.33190,DZ-23.53437
G2,VX0.00012420,VY0.00018157,VZ0.00020579
G3,XY0.00010909,XZ-0.00007426,YZ-0.00012014
SP,PN1,N xxx,EL3420.62896,–MAG
–Averaged position from last two observations[/INDENT]
In this case PN1 is stored, then stored a second time, then averaged to form the SP,… entry. When you reprocess the .RW5 file the first entry is processed, then the second entry is processed and replaces the first result and then the third entry (the SP, record) is processed and is the final value for PN1.
It appears when you look at the point list that the reprocess did not work on these ‘special averaged points’.
To fix this, I like to edit the .RW5 file rename the points with unique ids, get rid of the SP record and then reprocess. Here is my resulting .RW5 file:
[INDENT]GPS,PN1,LAxxx,EL1017.313066,–MAG
–GS,PN1,N xxx,EL3420.6261,–MAG
G0,2016/11/25 22:09:27,(Average) – Base ID read at rover: 0001
G1,BPBP004,PN1,DX-7.30561,DY-14.32856,DZ-23.53142
G2,VX0.00015295,VY0.00017713,VZ0.00021476
G3,XY0.00010786,XZ-0.00007321,YZ-0.00011786
GPS,PN1B,LAxxx,EL1017.314808,–MAG
–GS,PN1B,N xxxEL3420.6318,–MAG
G0,2016/11/25 22:10:37,(Average) – Base ID read at rover: 0001
G1,BPBP004,PN1,DX-7.30817,DY-14.33190,DZ-23.53437
G2,VX0.00012420,VY0.00018157,VZ0.00020579
G3,XY0.00010909,XZ-0.00007426,YZ-0.00012014[/INDENT]
Which when reprocessed generates this:
Which is more along the lines of what you expected.
(Readers Note: there was a third occupation of PN1 as PN1C in the file.)
This brings up a personal preference of mine: I don’t like averaging the data in the field. I like to store a point (in this case it was a 30-second average), then store additional points with unique point ID’s. I want to see the intermediate results, I can average them later (back at the office) if I want to. In this case, my strategy would most likely have been to store a 30-second average, then stake that point with a 30-second average, then do some more work and stake the point a 3rd time later in the day. All three points would appear in my .RW5 file as unique point ID’s, and if the result of any of the staking averages was off by more than 0.02′ I would commence with a total freak out.[/INDENT]
Sorry about the delay, It has been a crazy busy week.
M