Thanks to help from a fellow surveyor, I was able to figure out what was going on with GNSS Solutions over the weekend.
I posted the info saturday afternoon, and wanted to "bump" it to the top in case anyone was interested in what I was able to find out. Hopefully the information will help someone from experiencing the issues and stress I dealt with last week.
[msg=210077]GPS Post Processing Question Solved[/msg]
I'm glad it worked for you, Jimmy.
Since we use slant heights on our static occupations, generally, the apply to all won't help us out much. It isn't just that GNSS Solutions botches the slant heights, but it appears that once set, they can't be edited later (sounds like the apply to all approach overrides this). My issues have also been with importing Rinex files.
Shawn,
Thanks for the reply, both to this thread, and the original. The surveyor that helped me figure this out discovered the radius value missing in the NGS file. I wanted to bring it to everyone's attention. The sharing of information amongst ourselves is such a huge benefit to our profession thanks to Wendell and Angel.
I will have to experiment with that, because I do often use slant heights as well. When my receivers are on asphalt or concrete surfaces, I use tripods and tribrachs. I try to use the 2 meter rods when I can set the points in grass.
I have been using GPS for a good while, but I still have a lot to learn.
Jimmy
> I have been using GPS for a good while, but I still have a lot to learn.
>
Especially when they keep changing the rules all the time. 🙂
Glad you were able to resolve it. To me, software issues like these are unacceptable. Yes, we should always test our software and make sure that the output is accurate. But, a glitch like this should be fixed by the software company, in this case Ashtech/Trimble. It would be nice to get some input from them on this issue. You shouldn't have to do a workaround like that. Would the button pushers be testing their output using three different programs? I think not. Good job, Jimmy.
Thanks. I appreciate it.
I did have alot of help. I can't take credit for actually figuring out the problem, my friend is the one that figured it out. I am just sharing the fix that he found.
As far as trying to double check my work, I do my very best to try to double and triple check myself. I try very hard to make sure that the information I provide is done to the best of my ability. I probably spend as much unbillable time on GPS work than I do billable time, just double checking.
I would hate to publish bad data, or stake something wrong because I did not follow good procedures.