AutoCAD Civil 3D

[#1]

So I have a 2' wide sidewalk behind my curb and gutter sub-assembly.  I used the "basiclane" sub-assembly for this sidewalk.  Behind the sidewalk I used a "linkslopetoelevation" sub-assembly for a retaining wall we are putting in.  We need to transition that "linkslopetoelevation" sub-assembly so it comes up and attaches to the back of curb for about 15'.  Thus, the 2' wide sidewalk will go away in that area.  Why doesn't the "linlsopetoelevation" sub-assembly show up in the "Width or Offset Targets" for targetling lines but it does show up in the "Slope or Elevation Targets".  I have target lines that I want the wall to follow but I can only target the vertical, not the horizontal?  Why?

The attached .pdf show the sub-assembly showing up in the elevation targeting but not the offset targeting.  If indeed this will not work, how do I transition this.  There is a concrete pad on a hill that we need to keep in place so we are just going to build the wall around it but the sub-assemblies need to do this.  At first I thought I could transition my sidewalk and the wall woule follow but like I said, the "basiclane" sub-assembly doesn' who up for horizontal targeting either.

[#2 · Accepted solution]

Instead of a Basic Lane, use a UrbanSidewalk with a 0' inside width, 2' walk, 0' outside width. Attach the ret.wall to this, the sidewalk width can be set to a target.

[#3]

So basically the wall at the back of the sidewalk needs to slide in so it's up agains the back of curb and then slide back out so the sidewalk shows up again.  You can see what I am talking about in the attached .pdf.  This is a picture of my sub-assembly.

[#4]

I'll try the urban sidewalk sub-assembly.  I think I tried using that before but I do not remember.  I worked on this 2 months ago and then it sat until now, go figure.  I'll let you know what I come up with.  Thanks.

[#5]

---

taneum wrote:

.  Why doesn't the "linlsopetoelevation" sub-assembly show up in the "Width or Offset Targets" for targetling lines but it does show up in the "Slope or Elevation Targets". 

---

That subassembly does not provide offset targeting, only elevation. You could use Linkoffsetandslope, which provides both offset and elevation targeting.

Tim

[#6]

I refrain from using any subassembly with the word "Basic" in it. Look at the help file they tell you it is not intended for production, in not so many words

[#7]

---

Joe-Bouza wrote:

I refrain from using any subassembly with the word "Basic" in it. Look at the help file they tell you it is not intended for production, in not so many words

---

You wouldn't be talking about this would ya?

"This subassembly is one of a group of Getting Started subassemblies used for simple roadway modeling, and for tutorial and training purposes."

I'm glad you mentioned that as I had never read the wording on them before.

[#8]

What...? Like your 401k will take a hit if you use these? 

The UrbanSidewalk is overcomplicated and underpowered for his application. It gives him no elevation control for what he is doing if he needs possibly a little vertical adjustment to fit the wall in. 

He just missed it by one.. use the BasicLaneTransition. Then he won't have any extra parameters to set to zero, and then if needed, he could use a feature line for horizontal and vertical control (or not).. 

It's a perfectly straightforward SA to use for his sidewalk transitioning application.

[#9]

Its only my opinion Fred.

No. Take the the basic curb for example: it has not adjustment to offset the top face of curb from the the bottom face of curb. This creates a vertical face in the TIN that, from my understanding of the Tin algorithm is a no no

[#10]

Think about it... They wouldn't put something in that's going to fail the TIN alogrithm like that...

All of the "vertical" links in the OOTB SA's have a little offset built in.