You already got some excellent advice.
Here are my somewhat meandering thoughts.
- Feature line based corridors can model curbs.
This exhausts my knowledge of feature line based corridors.
- You can use feature line grading and Stepped Offsets as suggested in posts 3 and 4.
(Stepped or Offsetfeature)
The source and offset feature lines are not dynamically linked.
- Once added to a surface, as a breakline, or via a grading object, curve segments become tessellated.
- The curve radius and the mid-ordinate distance determine the tessellation segment length.
- As noted in post 5, C3D can have triangulation issues with very small offsets.
Tight feature line spacing and tessellation segment length can cause feature lines to cross, and it would be bad. I am talking wonky surface bad, not total protonic reversal bad, but still bad.*
- As noted in post 6, The "Grade to Distance" and "Grade to Relative Elevation" grading tools can be used to create Grading Objects that model curbs.
- These grading objects are dynamically linked to the base feature line.
- These Grading Objects do not exhibit the triangulation issues notes in 3. c.
- Grading Objects are powerful. Grading Objects can be finicky, fragile, unstable, and self-corrupting.
When using Grading Objects, you should save often. It is a good practice to save between saves.
- A productivity hint: Reference Surfaces
- Use a reference surface ** to define the overall pavement elevations.
- Feature lines defining the curb flange, lip, or gutter location should be "relative" to the reference surface with Elevation (Relative) = 0.00
- Feature lines defining the top of curb location should be "relative" to the reference surface with Elevation (Relative) = Curb Height.
- These feature lines will be dynamically linked to changes made to the reference surface.
- ** Secondary reference surfaces can be made by pasting in the reference surface and applying an edit Raise/Lower Surface.
i.e., Raise 0.50 feet for a 6-inch curb.
Top of curb features would be relative to a secondary reference surface with an Elevation (Relative) = 0.00
- There was an example of this in a recent post:
Link: commercial-grading-setup-surface-vs-finish-grade-surface
- A Conundrum: Labeling Curbs.
- In my experience, curb labels show two elevations. Top of curb and "adjacent" Pavement, gutter, lip , or flange.
- Civil 3D surfaces never have vertical faces. A vertical curb face needs to incorporate some batter (horizontal offset).
- In my experience, curb labels are typically surface spot elevation labels. The surface has exactly one elevation value that is available to the label. The secondary elevation needs to come from something else.
- An expression is often used to display this secondary elevation.
T.C. = {Surface Elevation} + 0.50
G = {Surface Elevation} - 0.50
- Using secondary reference surfaces, you can use a reference text component in your label definition.
Reference Text Component: "T.C. = (Surface Elevation)" - target surface = "TC Ref"
Primary Text Component: "G. = (Surface Elevation)" - target surface = "Pvmt Ref"
- This discussion has been about How to model curbs.
There is merit in considering the Who, Why, and What of modeling curbs.
This is part of my ongoing process of reminding myself that Sometimes Good Enough ... Is Enough.

- Who and Why are closely liked. Possibility include:
- Owner, Contractor, and Surveyor
To document my site design to an appropriate level on Production Drawings
(Plan and profile, cross-section, etc.)
It may help with water drop analysis.
Object viewer might help me visualize during design, but it is a secondary concern.
- Other members of the design team.
To provide an accurate, usable surface to other design team members.
- Specialty
To provide a base for photorealistic renderings.
Even here, consider that a 6" high curb is not very prominent in an elevation view of a 20-foot tall building.
- What do I need/want to model for curbs? Who and Why greatly influence this.
- Using expressions to facilitate T.C. and P. labels for parking islands may eliminate the need to model the back of curb line. The surveyor doing the layout may want the back of curb points that can be tied to a secondary reference surface for elevation.
- We typically draw 3-line vertical curbs. The back of curb, used for layout and for designing attached sidewalk, may need to be modeled. Top Face of curb will need for proper display of contours crossing the gutter pan, but is that level of detail required? I do not know of any contractors that will look for it.
- Does one need to model ramps fully? Probably. This is a place for extra effort.
- Street design typically needs a lip of pavement and the back of curb.
- Tips
- Refrain from modeling unnecessary detail.
- Avoid "chasing a hundredth."
A 0.02' simplification across a 40' wide drive aisle + parking stall is a 0.05% cross slope deviation.
Good Luck!
-
* Bonus:
Crossed feature line always reminds me of Ghostbusters (1984)
Egon Spengler:
There's something very important I forgot to tell you.
Peter Venkman:
What?
Spengler:
Don't cross the streams.
Venkman:
Why?
Spengler:
It would be bad.
Venkman:
I'm fuzzy on the whole good/bad thing. What do you mean, "bad"?
Spengler:
Try to imagine all life as you know it stopping instantaneously and every molecule in your body exploding at the speed of light.
Ray Stantz:
Total protonic reversal.
Venkman:
Right. That's bad. Okay. All right. Important safety tip. Thanks, Egon.
Christopher Stevens
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
