I'm sure I'm missing something simple but is there a setting in TBC to flag individual RTK vectors that were located out of tolerance.?ÿ I know how to set it to flag meaned vectors but can't find a setting for individual vectors.?ÿ?ÿ
Example: say you have a crew locate a monument in the woods using a single, 2 epoch observation and they force it to store.?ÿ The horizontal and vertical precisions are higher than you'd like.?ÿ Without running a vector report, can you set TBC to flag it and show in the flag pane??ÿ?ÿ
Hmmm... I can't think of anything automated.?ÿ Only thing I can suggest is to use the Vector Spreadsheet.?ÿ You can quickly sort by number of epochs or by H/V precision.
If you use Weighted Mean of All Observations, won't that flag the vectors out of tolerance? Then you can view those vectors using the Point Derivation report.
Thanks for the replies, Alan and Travis.?ÿ Trimble Geomatics Office used to flag them if they were out of tolerance.?ÿ TBC only flags multiple vectors.
I am not sure why I haven't noticed this sooner. Who shoots multiple vectors for topo points? There needs to be a simple way to flag an out of tolerance vector. I mean how hard could that be to get into the software?
Go to Project Settings--> Default Standard Errors--> GNSS and you can set the maximum errors.?ÿ
I have a screen grab of what you should be seeing, but for some reason I am unable to attach it.
@ fairleywell
I have already done that but that setting does nothing to flag out of tolerance GNSS vectors. Unless my TBC has some other setting I am unaware of for flags.
Why would you locate a monument in the woods, or anywhere, with a minimal observation in the first place? If it were a monument it should have multiple observations and we would not be having this conversation.
Paul in PA
What version of TBC are you running? Can you get me some sample data as well as a project where the vectors were not flagged?
While I wouldn't mind a tolerance option for a visual, I generally agree with Paul. If there are so many observations that are out of tolerance that a visual is required, there's something wrong with field procedures or the site is not good for precision GNSS.
The QC process for RTK vectors is in the field, as Access warns you whenever an observation is outside the tolerances set for the survey style. The user has to force it to store the vector. The assumption is that you wanted to store the vector. And unlike static work where you have the option to do some cleanup after the fact, with RTK what you see is what you get at the time of observation. The software workflow is operating on the premise that your RTK observations were desired.
If you do need to perform some cleanup, the vector spreadsheet is what you want for sorting the vectors by horizontal or vertical precision...
I am not talking about monument ties, we complete multiple observations on all monuments. My question is in regard to single vectors for topographic work. @ Rover83, we must not have our settings or something setup correctly as there is no in the field access warning of out of tolerance vectors. Obviously there are in the field operator checks but that's not always foolproof especially considering the field version of Access using 1 sigma 68% Confidence level. I am just looking for a simple way to flag out of tolerance vectors in TBC as a second form of easy QA/QC.
True, I don't think it is too much to ask of TBC. I can't imagine it would be difficult to implement. I think the Trimble community forums have a feature request section, or maybe that was only for the beta testers.
If I remember correctly (I am currently in a Leica-only satellite office, so going off of memory) the precisions are set under the Measurement Methods in the survey style. I think a checkbox (auto tolerance?) has to be unchecked and the "store initialized only" needs to be checked. Then it will throw a warning whenever the vector tolerances are exceeded.
Folks have been asking for the option to set desired sigmas in Access for a long time. All it needs is a simple dropdown menu in the survey style...
Yes, that was it Rover! That takes care of the field warnings, thank you.
