This is a followup to the Materials release. The goal is to solidify our UAV workflow and improve cleanup of point clouds.

• Additional Surfaces & Layers ( Gradework only?)
  • Although we know we can add more surfaces, some guidance on reasonableness from Dave should be requested. With 64 bit computers and larger amounts of Ram the current limits are conservative and drone data highlights the need.
  • Also examine Highway limitations on how it can use surfaces.

• Image View Control (Gradework and Sitework) - Similar to Alt-B but non-modal
  • Lists all images available with full names - toggle visibility - deletion
  • Versioning on images and separation to an images layer that like benchmarks is not bound to a surface

• Paint Brush cleanup (Gradework) - the ability to use the paintbrush feature to remove points by painting over them.
  • Designed for point clouds
    • Size can be varied by on-screen control or by “[” and “]” keys like Adobe products
    • Ideally using the paint brush also allows for a shading of of elevations that can be set like the shade increment. It would be extremely handy on cleanup
• Dynamic point cloud enhancements
  • Capability to sample tighter in dynamic for areas of change. Several variations that could be useful. Especially in Materials

* The ability to use the cut/fill map as a background image

* Modeling label control change (Gradework and Sitework)

• New/Assign label creation

As the use of orthomosaics and multiple sheet plans grows we really need to refine our image handling beyond the current annotation line, pick to select method. The use of mapping images and large drone orthos from highway projects also hints at a future where we have to tile imagery like SmartDirt (large overall low res, smaller, hir-res tiles when zooming). Breaking this out is step in this direction and should be designed with eventual tiling in mind.

Image boundaries should be their own layer that like benchmarks are independent of surfaces. The

Modeling features from Jason Lambrecht?