|
|
TPC provides four ways to specify staked points and their associated design points.
1.Point label contains
2.Point label difference
3.Point description contains
4.Sideshot points in a traverse
In addition, you can exclude points that don’t have an elevation and use the What list to select what survey data to search for staked points in.
This topic describes each of these methods.
Point label contains
This method assumes that staked points are identified by some matching character or string in their point labels, as in the following examples.
•Design point label 100 could have staked points with point labels 100@, 100@1, 100@2 all of which are staked positions for design point 100. You would just tell TPC that the @ symbol identifies staked points.
•Staked point 100SP would related back to design point 100 if you specified SP as the matching string.
This convention allows a design point to be staked any number of times, with each staked position being associated to it.
Point label difference
This method assumes that all your point labels are numbers, or start with numbers and that staked point labels are incremented by some number offsets as in the following example.
•Design point label 100 could have staked points with point labels 1100, 2100, 3100 all of which are staked positions for design point 100. You would just tell TPC that the difference of 1000, 2000 or 3000 identifies the design point.
This method allows you to easily report sequences of repeated stakeouts. For example
•On Monday, you use 1000 as the offset for all your staked points.
•On Wednesday when you go back out to re-stake points that have been destroyed during construction, you use 2000 as the offset.
•On Friday, you would use 3000 as the offset.
Now you can easily create reports that show the points that were staked in each series, 1000, 2000 and 3000 and submit a billing for the extra stakeout required.
Point description contains
This method assumes that staked points are identified by some matching character or string in their point descriptions, as in the following examples.
•Design point label 100 could have any number of staked points with point, each with #100 in their point descriptions.
Any character, like # can be used to identify the point labels in the description and other information can be included in the description either before or after the #[design point label].
Sideshot points in a traverse relate back to their control point
This method assumes that traverse control points are the design points and any sideshots that follow them are their staked positions.
In the example shown here, each control, like 466 includes just one sideshot point, like 1466, but any number of sideshots can follow the control points, allowing for any number of staked positions to be reported.
Related Topics
Stakeout Out Points Specifying Staked Points Stakeout Report
Editions
Personal, Premium, Professional
|
|