Pulled base receiver legs before turning power off, trimming bad data

I have never ever done anything like. RIIIGGHHT!!!?ÿ My data indicates a kinetic property, so, if I ever did something like that, I could find the kinetic marker and cut the data after it.?ÿ ?ÿ

Is there a kinetic property in a RINEX file?

@big-al?ÿ ?ÿI don't know? It shows up as a text note in the raw data, and after that the data gets segmented, so I would think you could recognize that in a rinex file?

Thanks for your help.?ÿ I'm using Carlson SurvCE v6.?ÿ There are some entries in the Carlson raw file RW5 at the beginning of the session when setting up the base, but I don't think there's much more than that.?ÿ Otherwise, all I have is the BIN file saved on the BRx7, which I have converted to the 21O and 21N files provided.

An Ashtech receiver would say "antenna is moving". Used those markers to trim files when the wind blows my setup over. Just recorded when I set it back up and kept on working. One very windy location I had three antennas blow over, one setup twice. Just had more files to process.

Paul in PA

OK, Paul, that triggers two ideas - 1) Contact Hemisphere (manufacturer of BRx7) to see if the native BIN file might have such an indicator, and 2) Contact Carlson to see if the RW5 might have an indicator.?ÿ I'll post my results here for others.?ÿ Thanks.

Even though you got a solution it could be biased by the extra data.

It seems that when I once ran a session through the Canadian NRC site it gave me a graph of position vs time. That would let you identify the beginning of movement, so you could chop off that much of a RINEX file and resubmit to OPUS.

I ran your file as a kinematic observation file, processed against MASH and I can't see that the receiver moved during the observation. I don't think you have anything to worry about.

?ÿ

The results are attached...

3 minutes of 30 s epochs would be 4-5 pings vs the total number over the course of the session. Probably didnƒ??t cause a significant variation in the session.?ÿ

@mark-silver

Very helpful, thank you.?ÿ I agree, your results seem to indicate no movement.?ÿ What software did you use to do this??ÿ (I may encounter this again...and, now, I have to figure out what job I pulled the legs on!)

@bill93

I've never submitted anything to NRC but just signed up and gave it a try.?ÿ VERY cool results.

Al

@big-al

I have several: SPSO, TBC (same, just different version), CGO2 that I use on a regular basis. CGO2 is the easiest, so I used it. This is a VERY common issue for some owners of the static receivers we sell. So we actually have a Trim function built into our download tool and we use it all the time.

There are three ways to screw the occupation up: 1. Turn the receiver on when you take it out of the box and then screw it to the tripod and level up; 2. Take the receiver off mount while on and put it in the box. This is usually also accompanied by a drive back to the office, so the processing reveals all the stops along the way; 3. Exchanging the Base and Rover, then processing a Rover as if it is a static base, usually accompanied by strong denial until a map of the rover's trajectory is produced.

Have a great week!

Mark

@mark-silver

Thanks again Mark.?ÿ I used to have a license of TBC, but moved away from Trimble and ended up selling my license.?ÿ I don't have SPSO or CGO2, either.?ÿ Sounds like CGO2 is a good tool, and I think you sell it?

By the way, I did hear back from Carlson, and neither the static BIN file or the RW5 file at the rover would contain any indicators if the base was moved/knocked over.

This happened to me a few weeks back with the same receiver. Once I converted the .bin to rinex I just opened the observation file with notepad and manually trimmed 5 minutes of data. Took me a minute to see what format it was, but the timestamps are pretty easy to see on each set of observation. I then sent it through OPUS and it processed just fine.?ÿ