Trimble Business Center

I have several runs of Level Traverses with Trimble DiNi in a three files.

I imported all of them. Examined to see all Bench Mark points had the "Known" Elevation value used as a "Control Quality".

I received above message. I did not know how to zero in on any of these "unresolved errors". I chose to continue to adjust. The result was not good. Had some erratic and duplicate values.

I measured all surveyed points with a GPS and compared the deltas. Attached excel file describes my attempt. It seems all is good (according to me !!). And the Adjustment report is not satisfactory.

Could some one please examine the files and educate me. The zip file is a *.vce file.

Thanks.

Hi Saif,

I have had a quick look at your files and notice you have what i am assuming is a lot of change points (AFxx and MAxx series of points) that have multiple level level runs to them.

From my expereince in the past, I have been caught out when i have gone through common change points however the guy holding the staff has not held the staff on the same point as previous. This means that the reduced level for what i thought was the same point will be wrong, however TBC takes the point names as gospel and will try to match them up and throw an error to say the readings are out of tolerance because you are not comparing the same reduced level. 

A prime example of this is using top of bolts to change on, however if the same bolt is not used in each run (because the staff holder forgot which one they used previous) but you type in the same name into the DiNi, there will be slight errors in the level run as there may be 10mm height difference between the bolts, TBC will however take it as gospel that these two change points are the same point and match them in the level run, throwing a small error.

Another issue can arrise when the DiNi auto-incriments the point number and can accidentally overlap a previous used point number, the reading you have taken for a completely different change point. TBC will then match these runs and throw a larger error.

Looking at your data, point AF-29 has thrown up 3 errors of 0.353, 0.353 and 1.265m and there are six legs that link through this change point. These legs might not actually be tying into this point correctly as they have either:
- been named AF-29 incorrectly and the reading is actually for another change point somewhere else on site (most likely to throw this large of an error)
- change point is AF-29 but the reading hasnt been taken on the correct point (like the bolt example above).

Going forward, there is no magical solution if this is the case to resolve, i would focus in on point AF-29 and rename some of the change points in the runs linked to this point and recompute. If you are familiar with where these points are on site, one may stand out to you as being an incorrectly named leg. (For example:  E41 and E692 are both MA-110 to AF-29 however E695 is MA-111 to AF-29 so maybe MA-111 is labelled incorrectly and should be MA-110 as well). It may as simple as one leg throwing the whole adjustment out!


  

I have several runs of Level Traverses with Trimble DiNi in a three files.

I imported all of them. Examined to see all Bench Mark points had the "Known" Elevation value used as a "Control Quality".

I received above message. I did not know how to zero in on any of these "unresolved errors". I chose to continue to adjust. The result was not good. Had some erratic and duplicate values.

I measured all surveyed points with a GPS and compared the deltas. Attached excel file describes my attempt. It seems all is good (according to me !!). And the Adjustment report is not satisfactory.

Could some one please examine the files and educate me. The zip file is a *.vce file.

Thanks.