Computer-aided design (CAD) drawing showing 3D wireframe models of a box in green outlines and solid blue 3D models of the same box in different view angles, with a coordinate axis in the lower left corner.

Adding Elevation Points to Civil 3D Feature Lines

Civil 3D Feature Lines are extraordinarily useful grading objects.

They're also objects where the distinction between horizontal geometry and elevation control matters.

Sometimes you need considerably more vertical definition along a Feature Line without wanting to introduce a corresponding collection of horizontal geometry points.

That's where elevation points become particularly useful.

And that's also where adding them manually can become tedious very quickly.

One elevation point is editing. A few thousand elevation points is a lifestyle choice.

We built Sean so you don't have to make that choice.

A Feature Line's geometry points, or PIs, define its horizontal geometry.

Elevation points provide additional vertical control along the Feature Line without necessarily changing that horizontal geometry.

That distinction gives us a useful general principle:

Keep the horizontal geometry as simple as the design allows, then add elevation information where the vertical design requires it.

There are plenty of situations where that might mean a large number of elevation points.

Adding those points individually is technically possible.

So is excavating a subdivision with a garden shovel.

We're mostly interested in whether it's a good use of your afternoon.

Before performing a large batch operation on Feature Lines, we recommend getting the horizontal geometry where you want it first.

In practical terms:

  1. Establish the Feature Line geometry.
  2. Confirm the PIs and horizontal path are correct.
  3. Save the drawing.
  4. Add the required elevation-point detail.
  5. Review the resulting Feature Lines in plan and elevation.
  6. Continue with the grading/design workflow.

The important principle is that adding vertical detail shouldn't unnecessarily complicate the horizontal geometry.

Also notice Step 3.

We have a theme.

Sean ET-007 — Batch Feature Line Elevation Point Tool was built for this workflow.

Sean allows elevation points to be added across eligible Civil 3D Feature Lines as a batch operation rather than forcing the designer to work through them individually.

The primary command, ETSEAN, handles the batch addition.

But there was an obvious question once we'd built that:

“Great. What if I want them gone again?”

Fair.

So Sean also includes tools for restoring or removing non-PI elevation points when the design workflow requires it.

The intent isn't add several thousand points and wish everyone the best of luck.

It's to make detailed Feature Line elevation control something you can use deliberately and, where appropriate, reverse.

Depending on the workflow, there may be times when you want to return Feature Lines toward their pre-Sean elevation-point condition or simply remove non-PI elevation points.

Sean includes dedicated commands for those operations.

That makes experimentation considerably more practical. You can add the elevation detail needed for a workflow without treating every batch operation as a lifelong commitment.

We still recommend the most sophisticated Civil 3D protection system ever devised:

Save your drawing.

Technology marches on.

QSAVE remains undefeated.

Sean is useful when:

  • numerous Feature Lines require additional elevation points;
  • manual point insertion would be repetitive;
  • vertical definition needs to increase without unnecessarily adding horizontal PIs;
  • a grading workflow involves repeated manipulation of Feature Line elevation detail; or
  • the number of Feature Lines makes individual editing impractical.

Sean isn't intended to replace thoughtful Feature Line design.

We haven't figured out how to automate thoughtful yet.

It's intended to remove the repetitive part.

Not every Civil 3D Feature Line-like object is editable in the same way.

Objects controlled dynamically by Civil 3D, including certain automatically generated Feature Lines, may be read-only and therefore aren't appropriate targets for direct modification.

Sean respects those boundaries rather than trying to force modifications into objects Civil 3D considers non-editable.

Sometimes Civil 3D says no.

Sean knows when arguing isn't going to help. He's been married a long time.

Watch Sean in Action →

Sean ET-007 is available September 2026.

View Sean ET-007