Hopefully I can get my point across without typing too much.
I posted a thread 8-10 months ago about double headers in the RINEX file and OPUS not playing nice with those files. I know several of you use TECQ but I'm not a DOS person so I typically just open the file in NOTEPAD and edit out the non-happy lines until OPUS likes it. Haven't had too many issues doing it that way until now. I can't find the offending line...........back to try another editing method
So that's not my real issue. I have been having trouble with many of these files in certain offices and zero from other offices. I think it boils down to the method and STYLE that is being used and I wanted to confirm if I'm right. Once I learned to use OPUS 12+ years ago I've never had an issue except for noisy data or bad CORS stations. (Thanks Loyal for fixing all of those files for me when I first started this stuff) I've always just created a STATIC STYLE in the DC and started the receiver.
Move forward to today. I have a crew in the field right now (out of town) and they are sending me the .T02 files realtime sot hat I can check them before they head back. Everyone of the files is coming back from OPUS with the typical "The RINEX data submitted to OPUS contains data taken from more than one location." They all have a *** Start of Kinematic Data *** header after the initial data. All of them except the first file I was sent yesterday whcih doesn't have the extra lines of information. It went through with flying colors.
I call the crew and ask if they are starting in RTK and infill and trying to start a base or something like that. Nope, they are just using the STATIC/FAST STATIC style, but.....their receiver mode is set to ROVER and not a BASE STATION which I think is adding the extra MARKER in the RINEX. The file that passed was the only one set up as a BASE STATION. They wanted to debate that it doesn't matter, but I'm sure it does since I can see it in the RINEX file. I'm of the mindset that if it ain't broke don't fix it.
Can anyone shed light as to why this is consistent with what I'm finding in the RINEX. Base vs Rover method/mode? Extra Marker in RINEX?
WINteqc, Windows GUI for teqc. No worry about DOS.
Paul in PA
Quick question, is it possible the field crew is starting the static session before the unit is level? I know some antennas are set up to start logging as soon as they are turned on.
That being said, I??m assuming by the file type that you are using Trimble receivers. Have you tried submitting the .T02 files to OPUS directly from Trimble Business Center? Not sure you would get any better results but it might be worth a try.
Sent from my iPhone using Tapatalk
It probably has more to do with how they end the previous session than how they begin the new.
What dc software, what receiver hardware?
I no longer use a controller for Trimble static work. I use my android phone or tablet with the Trimble DL app. It even e-mails the files for you. Easy to run solutions from the field after wait time as well..
It's because they're starting it as a rover, if they start it as a base it won't do that. If you use the most recent Convert to RINEX utility there's an option to remove kinematic data that should fix those files.
thebionicman, post: 443923, member: 8136 wrote: I no longer use a controller for Trimble static work. I use my android phone or tablet with the Trimble DL app. It even e-mails the files for you. Easy to run solutions from the field after wait time as well..
Tom, that's what the crew has been experimenting with today as well. I've been getting double files in near real time. Downfall is company only lets us have Iphones :mad:. The crew is using their personal phones right now. Eric mentioned that to us over a year ago and I've been campaigning for an Android based phone since then.
Lee D, post: 443926, member: 7971 wrote: It's because they're starting it as a rover, if they start it as a base it won't do that. If you use the most recent Convert to RINEX utility there's an option to remove kinematic data that should fix those files.
&^*%^$%$#@^!!!
I've been looking at that option screen for 2 years now and never really paid attention to that. Thanks you Lee!
You're quite welcome.
When we do static networks I make the crews start EVERY session as a base.
I NEVER use a data collector to start a static session (except if it is also an RTK base, which always collects a static file). Our receivers are setup to start collecting at power-up. So a static file never has extraneous start/stop records in it.
The (minor) drawback is that if I am doing RTK the unit will collect a small file before the RTK survey is started, but those are easy to ignore, they are usually about 10kb or so. .
Rob O'Malley, post: 443928, member: 154 wrote: Tom, that's what the crew has been experimenting with today as well. I've been getting double files in near real time. Downfall is company only lets us have Iphones :mad:. The crew is using their personal phones right now. Eric mentioned that to us over a year ago and I've been campaigning for an Android based phone since then.
I got a 'data for life' android tablet a few years ago. They are only a few hundred bucks. Not super fast but they come in handy...
Glad you got it fixed.
Lee D, post: 443931, member: 7971 wrote: You're quite welcome.
When we do static networks I make the crews start EVERY session as a base.
Well just like I mentioned in the first post, that's what I've always done. That's what two of our other offices do. There has been a consistent issue with this and I finally realized what it was after going through the STYLE over the phone.
John Hamilton, post: 443934, member: 640 wrote: Our receivers are setup to start collecting at power-up. So a static file never has extraneous start/stop records in it.
The reason I don't use power ups is that I want the receiver on the tripod, level, plumb, and undisturbed before any logging starts. I also don't think it's a horrible idea to let it run for a couple minutes before beginning to log.
Valid points, Lee, but this way we do not mess with data collectors at all during static surveys. But we don't turn it on until it is all set. I agree sometimes the first few epochs can be problematic.
I've been training the IMs to put the brass plug and the R8 base on the 0.25m pole, fire the R8 up, and then put the pole onto the fixed height and tighten the clamp screw. Lastly recheck the setup and make any fine adjustments.
Most of our static sessions are on RTK bases anyhow, so the data collector is going to be a part of it. I might do a half dozen static networks per year at most.
