Stake Slope

The Stake Slope command calculates and marks the "catch point" where Cut or Fill slopes meet the original ground. It can set offset stakes to this point and generate a report with slope stake details. The catch point's location depends on the "pivot" point where the slope starts and the slope value (e.g. 3:1, 4:1, etc). This is commonly used in highway construction to mark the "daylight" points on either side of the centerline. If design information is available, the command also calculates distances and offsets for all breakpoints from the slope stake to the centerline, which is reflected in the report. Further, slope staking can be interval based or accomplished based on your current location in the field, independent of station interval.

Note: In the Stake Road command (which works with both sections and templates), slope staking can be initiated from any desired point. This allows for slope staking of interior, central median catch points and slope staking of any side of a divided highway (perhaps being built in stages).

There are "rules" for slope staking. The slope stake is measured from:

• a user-defined pivot point
• the centerline itself from defined alignments
• the last template point before the Cut or Fill slopes when templates (design files) are involved
• the left- and right-most end-points of sections when using section files

The routine has three main sections:

1. Choosing the Slope Staking Method and its Data
2. (Optional) Setting the Station and Interval for Stakeout
3. Main Measurement

Choosing the Slope Staking Method

Various methods for determining the pivot point location are available and range from the very simple to more advanced:

• Settings: (gears) The Settings icon at the top of the screen (only available for Section Files) that offers an option to Force Section-Templates use per Crt Job.
  More Information

  

  This option is commonly used with the SDR "section template" file. They all are 3D strings such that even if they collapse to another, they continue to have contiguity.

• Reference CL: (icon) Permits a master centerline (horizontal alignment) to be designated for reference, while you stake out a separate alignment as discussed under Stake Line/Arc.

  Note: Visibility of this option is controlled through the Job Settings - Allow Reference Centerline option.

• User Entered: This is the most commonly used method of slope staking. Here, you simply enter the station, offset and elevation of the pivot point.
  More Information

  

  • Centerline File: Launches the standard File Selector that permits a Carlson Centerline File to be opened/specified.
• Defined Alignments: Slope Staking from Defined Alignments requires a horizontal component and a vertical component (profile).
  More Information

  Note: Point-Defined Alignments is often used for staking the top of cut for a ditch, particularly a V-ditch. This method is useful for slope staking existing flow lines, where you simply take two shots at either end, create an alignment by point number, then set the slope stakes at the user-entered slope ratio.

  When a new horizontal alignment is selected by 3D polyline or point method, the program will ask if you wish to overwrite any existing vertical alignment selection. The typical answer is Yes; you want it for both, and you are ready to stake any station at any interval based on user-entered slopes.

  Note: For additional information about the interface, see the detailed write-up under Survey - Stake Offset.

• Design Files:^† This is the most "formal" way of slope staking, but typically only applies to uniform, simple road, drainage ditch or levee projects where the pivot offset positions do not commonly vary from station to station.
  More Information

  While all methods require that a Centerline be selected, the Design File method additionally requires a Profile and a Template file.

  Note: One advantage of the Design Files method is that since each template point has an "ID," the Slope Stake Report will include information to locate all ID'd template points from the slope stake back into the centerline. In this way, the entire road can be built from the information marked on the slope stake, often placed outside the construction area at a user-specified (e.g. 5') offset to the actual catch point.

  Note: For additional information about the interface, see the detailed write-up under Road - Stake Road.

  Note: Named "collections" of Roading Files can be Saved and Loaded using the buttons at the bottom of the screen.

• Section Files:^† Cross-section files can be used to identify the pivot points left and right and minimize fieldwork.

  Note: Data within the Section file is governed by the Road - Sections Include Catch Points toggle.

  More Information

  Section-based slope staking is useful when the pivot points for stakeout vary unpredictably and don't conform to a fixed template. Section-based slope staking has two advantages:

  1. All sections can be entered in the office as 2-point sections (left and right pivot), minimizing field paperwork and reference material.
  2. Odd stations can be staked out (e.g. station 0+27.5), since the pivot points can be straight-line interpolated by the program from neighboring sections.

  

  • Centerline, Profile, Design Section: Use these buttons to launch the standard File Selector that permits each of the file types to be specified.

    Note: Each of the file types can be:

    1. created in SurvPC, or,
    2. created in an external program such as Carlson Civil or TakeOff and loaded onto the collector, or,
    3. imported/converted from other sources.
  • Apply Vertical File: When enabled, the Profile data will be used to set the 0-offset (zero-offset) elevation of the section to that of the profile elevation for the specified station.

    Note: With cross-sections, the Profile is not required but including the profile will lead to more accurate slope staking between known cross-sections and through areas within vertical curves.

  • Continue Last Slope: When enabled, the outer slopes at each section will be used to determine the daylight/catch point.
  • Cut/Fill: Specify the slope value that should be used when the section points are in cut vs fill.
  • Display as Ratio: When enabled, the slope values will be displayed as the amount of "run" per 1-unit of "rise."
  • Load Roading Files: Launches the standard File Selector that permits a previously saved collection of geometry stored in a *.RDF to be recalled.
  • Save Roading Files: Launches the standard File Selector that permits the cited Centerline, Profile and Design Section "collection" of files to be stored into a *.RDF for easy recall later.

  Note: There is no requirement that Starting and Ending Stations (chainage) match. All that is necessary is that they have a station range in common.

  Note: Section files can be used for slope staking within Stake Road. Distinctions between the routines include:

  1. Stake Slope: automatically uses the left- and right-most endpoints of the section as pivot points, which means less screen picks are involved (greater speed).
  2. Stake Road: you can pick any point for staking (greater flexibility).
• Slope Stk Sta Interval: When enabled, the station being slope-staked occurs at a user-specified station interval.
• Crt Cut/Fill to CATCH: When enabled, SurvPC will give the Cut/Fill to the current location on the catch basin.
• Round Station to Nearest: This option applies only if you toggle Slope Stake Station Interval off and move into "fluid" slope staking. The elevation to stake from is calculated to the rounded station value. Rounding only applies to the stored report; the target still moves fluidly as you move parallel to the alignment.
• Load Road Net File: Launches the standard File Selector that permits a *.RNF file that can contain a packaged collection of roadway data to be read into memory.

  ^†Note: Since the RNF file contains both templates and final sections, the Load RoadNet File option is accessible when slope staking by Design Files and Section Files.

  More Information

  The RoadNET^™ routine included in Carlson Civil or TakeOff has the option to output a *.RNF file. This file contains all the design geometry for the processed collection of roadway/corridor projects. For example, a complete subdivision road system can be output as a single RNF file, and then SurvPC can stake out any element of the RoadNet project.

  

• Select Road Net Element: Permits the graphical selection of a RoadNET element that is to be staked and populates the data files into the specified option of Design Files or Section Files.
  More Information

  Choices of elements that can be picked are:

  1. centerlines
  2. cul-de-sacs^†
  3. intersection curve returns^†

  

  ^†Note: Keep in mind that for cul-de-sacs and curve-returns, the position of the horizontal alignment is set in RoadNet and is typically set to the edge-of-pavement position. Slope staking will therefore use just the outer part of the template (i.e. from EP outward) to find the pivot point.

  Note: Also within the RoadNET Element Selection interface are other common controls; most notably the various Map Screen View Controls.

Station and Stake Interval

In most cases, you are prompted to indicate the Station and Section Interval to stake, the options of which will vary based on the Stake Slope method.

• Station: Indicate the station along the alignment from where staking should commence.

  Note: The (in)ability to stake station prior to, or past, the alignment is governed by the Alignment Settings - Extend Alignments option.

• Next Interval: Indicate the normal station increment along the alignment.
• Pivot Off: Indicate the Offset distance away from the alignment of the pivot point where tie-slope extends to existing ground.

  Note: Do not enter a minus sign (-) for a left offset as the program detects whether you are left or right of centerline.

• Pivot Elev: Indicate the elevation of the pivot point where the tie-slope begins its journey to existing ground.
• Read Instrument: Use this button to perform a "get here" station (and optional offset/elevation) value.

  Note: The point location is projected onto the centerline to determine the station.

• Use Point ID: Indicate if an existing point should be used to determine the station (and optional offset/elevation) value.

  Note: Additional controls permit the point to be specified from the Job Point List or a Map Screen pick.

• Display as Ratio: When enabled, the CUT/FILL slope values will be displayed as the amount of "run" per 1-unit of "rise."
• CUT/FILL: Indicate the slope of Cut/Fill tie-slopes, respectively.

All paths lead on to the navigation or stakeout (some call it the "set out") screen.

The Navigation (Stakeout) Screen

Although office plans may predict the position of the catch points, Slope Staking is necessary to accurately determine the catch points based on actual field conditions. Slope Stakes are often set at an offset to the actual catch points, since stakes at the precise catch points are likely to be knocked out by earthmoving activity. Furthermore, Slope Stakes are often marked with information on the slopes and distances toward the reference object. The information on the Slope Stake is often written in "progressive" form:

1. distance and slope from offset stake (OS) to slope catchpoint (CP) stake
2. distance and slope from slope catchpoint (CP) stake to outside pivot point (PP) shoulder
3. distance and slope from outside pivot point (PP) shoulder to edge of pavement (EP)
4. distance and slope from edge of pavement (EP) to centerline (CL)

Thus, the Slope Stake, placed safely beyond the area of construction, tells the story of the Cuts and Fills in toward centerline or toward the center of the work.

Within Stake Slope are these measurement/configuration tools:

Stake Slope Measurement/Configuration Buttons

Legacy Icon	Graphic Icon	Availabe For	Action
			Read: Depending on whether or not the connected total station is robotic, the following options will happen: Total Station: The instrument will take a reading and report it. The reading is not stored as a point until either the Store option is selected or another reading is initiated. Robotic Total Station: The instrument will take a reading and offer to store the reading as a point.
			Store: Stores the current reading as a point, it's time to drive the stake. The functionality of this routine is governed (in part) by the General - Enter Key setting.
			Next: The next available point for stakeout is presented.
			Launches the Configure interface for the active piece of equipment.
			Directs the user to the Total Station Orientation interface.
			Launches the GNSS Monitor/Skyplot command.

Note: Also within Stake Slope are other common controls; most notably the various Map Screen View Controls.

Various options can be set through the Configure to adjust how the directions are provided to best suit your needs and also features an option to establish a Minimized View of the data.

Storing the Slope Stake

Note that there are two options for the slope stake report:

1. Elevation: This assumes you were able to survey the actual slope stake point with reasonable accuracy, and it reports the actual stake to pivot point results and is the common method.
2. Offset: Useful in situations where the catch-point is obstructed.
   • In Cut: walk out and away from centerline,
   • In Fill: walk toward centerline,

   and drive the stake where you can.

• Ref CL: (CL) When enabled, the stationing will be based on a reference centerline.
• Pivot Pt: (PP) Summarizes the calculated Station, Offset and Elevation of the pivot point.
• Catch Pt: (CP) Summarizes the calculated Station, Offset and Elevation of the daylight/catch point.
• Stake Pt: (STK) Summarizes the staked Station, Offset and Elevation of the daylight/catch point.
• Reference Values: Various items of information (i.e. slope values, distances, Cut/Fill, In/Out, Back/Ahead) between the items above are reported.
• Store Data to Cutsheet File: When enabled, values are stored into the specified Slope Stakes Cutsheet.
  More Information

  Surveyors doing slope staking have the option to write the information on the stake as each is surveyed, or to come back at a later time, refer to the slope stake report, and write on all the stakes after the surveying is complete. The slope stake report file is a comma-separated text file that can be formatted to resemble the following:

  Example Report

  #Des Sta	Des Off	Des Elv	Staked Sta	Staked Off	Stake Elv	Desc
  1+00.000	L33.849	998.075	0+99.966	L33.453	998.075	Catch Point
  1+00.000	L38.849	--	1+00.019	L38.866	998.15	First Offset Point

• VOff/Elv: Indicate an additional vertical offset amount or elevation, respectively, for the staked point location.
• Point ID/Desc: Indicate the point number and optional description for the staked point.

  Note: Slope Staking will not respond to the Configure - Height/Description option.

• Store Point to CRD File: When enabled, the staked point location will be added into the current job.

Note: Upon pressing ✅, you are prompted for whether to stake the first of two optional offset stakes:

1. The first offset stake is commonly placed a distance outside of the catch-point stake and used in situations where construction activity might remove the catch-point stake. The slope stake information is typically written on the first offset stake.

   Note: After the first offset stake is set, and before the prompt for the optional second offset stake, a summary screen will appear.

   More Information

   

   • Progressive: Lists the incremental information from each breakpoint to the next, going in toward the centerline. It is commonly cited as a story or "and then" (or // nomenclature) staking.
   • Total: Offset distances to all breakpoints are measured as totals from the offset stake. It is commonly cited as "and" (or / nomenclature) staking.
   • Combo: Permits distances to be cited from the Offset or Catch location.
   • Show Report up to CENTER: When enabled, data in the report will only continue to the Centerline. Alternatively, data will be included past the centerline.

   Note: Regardless, the report is issued only if you stake the offset point to the catch.

   

2. The second offset stake is commonly placed an additional distance outside the first offset stake and is used to "establish line" to reset the catch-point stake if it is knocked out.

Note: When using Road Design or Section Files, setting the first offset point is the recommended procedure, as it produces the full report, referenced to cross-section and template IDs, for all breakpoints all the way into the centerline point.

The Slope Stake Report and Writing on the Slope Stake

A report might appear as follows:

Once staked, the next station can be specified.