I want to write about cleaning up surface data thats comes from lidar and other surfaces. So that Gradings tools and Corridors work more efficiently.

Use Val as example.

You can probably get what you want by using the surface selection “section 1 and 2”/configuring your styles and removing weeding.

First to help you understand the two section selections

Once you have this worked out you will want to make sure you have a style that is displaying elevations at “grade breaks and using the “section 2 elevations”

Then you should be laughing!

I want to write on the following topics in the next 2 weeks as part of my Subassembly Composer How-To Guide.

1. Do I even need a custom subassembly?

2. Setting up your subassembly

3. Keeping it logical

4. Fixed and Variable Links

5. Switches and Enumeration

6. Avoiding Duplication and Zeroing out

7. Looping (i.e benches)

8. Making Shape codes work for you

9. Updating to your Projects

10. Naming Conventions and Sharing

Regards

Quite often using generic subassemblies can be confusing, particularly when you are trying to code them. You can generate some basic code styles like so to not only show on your assemblies but also on your sections views.