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.

Feature Line Elevation Points and PIs

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.

Surface Supplementing Factors or Feature Line Elevation Points?

Civil 3D does have another way to densify the TIN. Supplementing factors can add intermediate surface vertices along a breakline without adding elevation points to the Feature Line itself. That can be exactly the right answer when all you want is a denser surface.

Maximum-distance supplementation adds intermediate TIN vertices along breaklines where the spacing would otherwise exceed the specified maximum. Mid-ordinate settings control how curved segments are tessellated into straight segments. These are surface-definition vertices, not editable elevation points on the source Feature Line.

This native option also works across multiple Feature Lines: add the selected lines to a surface as one breakline set and assign a common Supplementing Distance. Civil 3D creates supplementary TIN vertices without adding elevation points to, or otherwise modifying, the source Feature Lines. It is a legitimate and often preferable option when the sole objective is denser surface triangulation. Both methods can work on multiple Feature Lines; the choice is where the added control should live.

I generally prefer to control this through selected Feature Lines. I can see the elevation points being added, limit the change to the Feature Lines that actually need it, inspect the result directly and restore the pre-Sean point population if I decide I went too far. It is a more interactive way of making the decision instead of blanketing an entire breakline definition and hoping that more triangles automatically means a better surface.

Sean supports that preference by deliberately adding visible elevation points to selected Feature Lines at an entered horizontal spacing. The designer chooses which Feature Lines are altered and can inspect the resulting points before relying on the rebuilt surface.

Restore Pre-Sean State supports reversing the point-population decision while retaining the current eligible Feature Line geometry, subject to recovery and validation rules. NUKE ALL ELEV POINTS provides a deliberate way to remove all non-PI elevation points when a complete reset is intended; its effect on restoration eligibility still applies.

Neither method should be applied indiscriminately. Unnecessary vertices can increase surface data and processing requirements. Added control points may affect triangulation and resulting contour behaviour, so targeted placement and visual review matter. Surface supplementation is a valid native approach when the goal is only to densify the TIN; Sean is not the only technically valid method.

Sean’s actual elevation points persist in the Feature Lines: they are visible in the Elevation Editor, individually editable and reusable independently of any particular surface. Supplementation can use different settings for different surfaces. Sean’s points belong to the Feature Lines, so their added control affects every workflow that uses that geometry.

Supplementation needs no Feature Line restoration because it does not modify those lines. Sean Restore exists because Sean deliberately changes their point population; it is not universal Undo. Adding many actual Feature Line points increases object complexity, but no quantified memory or performance penalty is claimed here without testing. The resulting TINs may be similar, but are not guaranteed to be mathematically identical: point-stationing, endpoints and remainder handling may differ.

Neither method is universally better. Breakline supplementation is an efficient native choice when densification belongs only to the surface. Sean is intended for designers who want that added control to exist explicitly in selected Feature Lines—visible, editable, reusable and recoverable.

Autodesk reference: breakline supplementing distance and mid-ordinate distance

Adding Elevation Points at a Consistent Spacing

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

Sean operates on user-selected Civil 3D Feature Lines and accepts a user-entered horizontal plan spacing. It calculates and inserts native elevation points along the selected eligible Feature Lines using that spacing.

You choose the spacing. Sean does not automatically choose it, create the Feature Lines or redesign them. Horizontal plan spacing is measured along the plan path, rather than the sloping 3D length.

Processing Multiple Feature Lines

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.

Select the intended Feature Lines, enter the spacing once, and review the prompts and reported counts.

In one demonstrated stress test, Sean processed 432 Feature Lines and inserted 99,936 elevation points in a single operation.

This is a documented demonstration, not a guarantee that every drawing will produce identical performance. Drawing geometry, eligibility and the chosen spacing affect the work involved and the resulting point count.

See Sean add elevation points at a selected horizontal spacing, including a demonstrated 432-Feature-Line batch operation.

Watch the Sean Short on YouTube →

Try Sean Free for 3 Days

Restoring the Pre-Sean Point Population

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.

Before Sean modifies a Feature Line, it records the existing elevation-point population and stores recovery information in the DWG. Restore Pre-Sean State restores that saved pre-Sean elevation-point population onto the current eligible Feature Line geometry, subject to Sean's recovery and validation rules.

It removes the current non-PI population and recreates the saved elevation points on the current eligible geometry. It does not roll the entire drawing backward or discard legitimate PI and path changes. Feature Lines that cannot be safely restored are skipped rather than guessed at.

Removing All Non-PI Elevation Points

NUKE ALL ELEV POINTS removes all non-PI elevation points from the Feature Lines you select, regardless of whether Sean created them. The Feature Line objects remain, and their defining PIs remain intact.

The user selects the target Feature Lines, and the command requires deliberate confirmation. NUKE is distinct from Restore Pre-Sean State: use Restore for the saved pre-Sean point population; use NUKE when the intended outcome is removal of every non-PI elevation point.

A complete NUKE reset affects Sean restoration eligibility under the product's documented recovery rules. Do not assume Restore Pre-Sean State will remain available after a complete reset; check the maintained product documentation before relying on that recovery path.

NUKE ALL ELEV POINTS removes every non-PI elevation point from selected Feature Lines while preserving their defining PIs.

Watch the NUKE Short on YouTube →

A Deliberate, Recoverable Workflow

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.

For substantial operations, also:

• Select only the intended Feature Lines.
• Review prompts, deliberate confirmation and reported counts.
• Understand whether Restore Pre-Sean State or NUKE ALL ELEV POINTS fits the intended outcome.
• Use Undo where applicable.
• Verify geometry and elevation-point counts after processing.

This Field Note explains the workflow. Keep the maintained Sean product documentation at hand for complete operational instructions, recovery eligibility and edge-case details.

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 the complete Sean ET-007 workflow, including spacing, batch processing, restoration and removal.

Watch Sean in Action →

Sean ET-007 Availability

Sean ET-007 is available now.

View Sean ET-007 — Available Now

Try Sean Free for 3 Days