Trimble Business Center

Correction for Adjusted Elevations are not calculating correctly. This is a raw import to an empty project so it's not being influenced by any previously imported control. Misclosure for this run is -0.0001 but the program is applying random corrections of up to 0.5'.

I would look at the other level runs, such as Run-1, Run-3, etc. The yellow dot next to the point number means that point shows up in one of the other runs in the editor. The level editor won't let you have different computed elevations for the same point. My guess is one of the previous runs computed an elevation for one or some of those points and this last run is adjusting to hit those previously computed elevations. I would start with looking at point 758 since that's the largest adjustment in this run. If the other runs are not needed, delete them out of the editor. 

Edit - I didn't notice that those points show up twice in this run. That could be the reason for the yellow dot next to the points. I would still check the other runs but that might not be your fix.

------------------------------
Scott Koffarnus
------------------------------

I'm in agreement with Scott - shared points between runs is likely the culprit here.

With multiple runs that have shared/repeated observations, the proper method to get final values would be a network adjustment rather than trying to daisy-chain the runs together - especially if they weren't done in a very regimented way that allows successive runs to build off of earlier runs.

Import the level file, make sure the "allow network adjustment" radio button is selected, QC your point IDs and misclosures. Uncheck the Create column for turn points. Then click OK and run a network adjustment using the resulting level observations. Ignore the "Adjust Runs" button and be sure to properly apply the correct standard error (by distance or by turns).

I haven't used the Adjust Runs button for years now; everything I do is network adjusted with levels + TS + GNSS which allows for far better blunder trapping and statistical analysis. Incorporating properly weighted level observations really helps to isolate potential issues with height/measure ups. Even if I'm only processing levels, they get a network adjustment.