Filling in the Roadway Gaps: Link Slope Between Points (2 of 4)

June 14, 2021 Leo Lavayen

This is the 2nd post in the series on how to utilize subassemblies to fill in the gap on divided roadways.  Here the Link Slopes Between Points from the Tool Palettes Generic tab will be used:

These subassemblies need to be built in the correct order and even though at times the layout might look wrong, they work!

 

Generic Subassemblies: Link Slope Between Points (the tool)

From the HELP file:  

This subassembly is used to insert intersecting links between two points.

It is typically used to place intersecting slopes to a V-ditch between the edges of two adjacent or merging roadways. A flat-bottomed ditch can also be specified.

 

Generic Subassemblies: Marked Point (the key)

From the HELP file:  

This subassembly is used to mark an existing point on the assembly with a name.

This is usually done so that other subassemblies can later insert links that attach back to this point (for example, LinkToMarkedPoint). The attachment point is the point that is marked. You can add user-defined point codes to this marked point.

In the example below, there are two roadways with independent profiles. Once the links for the first roadway are created, the point at the left outside edge is being marked. Later, after the links for the second roadway are created, a link can be inserted from its right outside edge back to the marked point.

 

How to put it all together:  Assembly (the secret)

Per the help file above, to use the Link it must be paired with a Marked Point.  The key things to remember here are:

  1. Name the Marked Point (case matters)
  2. When using the Link, set for the Name of the Marked Point
  3. Ensure correct Build in order, Marked Point FIRST, then Links.

First, the Marked Point.  In the example below, it is given the name “MP

It can be added to the LEFT or RIGHT side of the Assembly (depending on the original creation order).  Here placed on the LEFT inside edge of Pavement (stylized and shown below as an Orange triangle).

Then, use the Link Slope Between Points subassembly, making sure to set Marked Point Name

Shown here attached to the RIGHT side of Assembly, on the inside edge of pavement.  It appears to be going in the wrong direction, ignore that for now.  Notice the “Layout Mode” on the screen.

Last, make sure the build order is correct as listed in the Assemblies Properties dialog boxes. Note if the RIGHT or LEFT attachment was created FIRST, that is how we decide where the Marked Point and Link should be attached.

The way I think about his is similar to air travel, we need to know where to land (Named Marked Point) to then be able to take off (smart Link)

If everything is right, our corridor will be built correctly as shown in the cross-sections below:

Taking a closer look, 2 slopes (4:1) are created along with a flat bottom creating a ditch (2’).

I hope this clears how to pair the Generic Links with Marked Points.  Stay tuned for the next posts on other methods to fill the roadway gap.

 

Link to earlier post in the series:

Filling in the Roadway Gaps: Link to Marked Point (1 of 4)

About the Author

Leo Lavayen

Civil Applications Expert<br><br>As an Applications Expert, Leo is responsible for supporting, training and implementation of software for survey and civil engineering professionals. He has more than 19 years of experience helping large and small, public and private clients in the eastern United States.

More Content by Leo Lavayen
Previous Article
Filling in the Roadway Gaps:  Raised Median with Crown (3 of 4)
Filling in the Roadway Gaps: Raised Median with Crown (3 of 4)

Here the Median Raised with Crown from the Tool Palettes Medians tab will be used

Next Article
Filling in the Roadway Gaps: Link to Marked Point (1 of 4)
Filling in the Roadway Gaps: Link to Marked Point (1 of 4)

These subassemblies need to be built in the correct order and even though at times the layout might look wr...

×

Get Tips Delivered.

Subscribe to Email Updates.

First Name
Last Name
Country
Thank you!
Error - something went wrong!