Point table with comparison benchmark elevation.

[civman_daar]

I am working on a project that uses a Lidar surface for elevation information.  We believe that the Lidar surface elevations may be off by .05-.15', in comparison to a surface shot with a total station.  The surveyor will shoot construction staking with the total station.  I would like to use known benchmark points to create a cut/fill elevation situations for construction staking.  I need to generate a point table that will list the known benchmark and list cut/fill elevations for the stakeout points.  The initial design points are tied to the Lidar surface.

Examples:  BM=100.00

                   Point 200: FL (lidar)=100.15

                   Elevation difference vs benchmark=0.15'

                    BM=100.00

                   Point 201: FL (lidar)=99.90'

                   Elevation difference vs benchmark= -.10'

I would like to display the BM elevation in the table just once, list the elevation difference in a column, and the adjusted elevation in another column.

Table format:  Point Number|Northing|Easting|Elevation|Description|Elevation Difference|Adjusted Elevation

How to create the elevation difference and adjusted elevation columns?  Any ideas?

Thanks

Rick Spangenberger

[rl_jackson]

If you have lidar data, thats within 1" you're doing good. Now I would ask why you would make the error known; it's not going to matter from a construction standpoint. Use local elevation that was used by the surveyor and whatever your design plans say and do the stakeout. 

Honestly, I can't see an inch from my house to where you live and we don't build rocket ships to Mars. Just my take

EDIT: There's always going to be a "fluff area" where the surveyor needs to make an educated guess based on the plans as to how to tie into a road this is what surveyors do, at the same time engineers make these same guess's.