Questions about how to work in a TIN-model - missing tools?

Question

Good morning 
 I have some questions about ORD 2022 Release 1. I switched from InRoads and I am now missing some tools. 
 1. How can you edit or modify/delete points (objects) directly in the TIN, especially the elevation (z-coordinate)? 
 2. How can you edit a breakline, e.g. add/delete points or move/modify the breakline? 
 3. We work with mass data. How can you display/delete only partial areas of the TIN using the fence content? 
 4. Is it possible to import/export data from view via fence or level selection? 
 5. Can the surface be thinned out, e.g. create a grid surface? 
 6. How to project elements onto the surface (TIN)? 
 I hope you can help me Thanks a lot and best regards from Germany

Shawn Cooke · Answer

The following recommendations may be anything but "simple", however it's worth mention in the context of assuming missing tools. Yes, ORD has many things to improve on, however we can admit the entire dynamic of the workflows and concepts have changed and frankly, are different. 
 One thing to understand is a "TIN" can be imported into ORD. When imported, it becomes a "Terrain" Feature linked to whatever data file it was imported from (e.g. TIN, DTM, LandXML, etc). You'll notice the ability to resync the data back into the dgn file, but that only goes one direction. When a terrain feature is edited in ORD the modified version becomes active or live data inside the dgn as a Terrain feature (and needs to be exported back out if and when necessary to be shared as an updated TIN). 
 The Survey workflow of ORD may help fill some gaps in what otherwise may seem to be "missing" in the development and analysis of civil terrains. By using the FieldBook import option "features from graphics" or from existing csv/ ascii data, you can generate FieldBooks to contain points and linear graphics that allow terrain attribute control, manipulation and reporting within the "Survey Details" dialog. Terrains generated from those can remain linked to the data. Terrain Feature attribute types will better control how to isolate/ delete areas via voids, hole and islands applied to the FieldBook generated terrain. 
 Question 6 can be achieved by using what Bentley refers as a "self managed " 3D workflow involving 2D dgn graphics having a profile "Set As Active" to generate a surface terrain projected 3D graphic. Once you understand the two separate workflows you can merge 3D projected graphics for importing into a FieldBook (Survey FieldBook workflow must be in a 3D only seed file, in contrast, the Self-Managed 3D geometry process must start with a 2D Seed.) 
 These short examples below may help achieve all with the exception of 5. I would need to understand the question better (is your "data" a raw LAS or point cloud dataset? if so, read more into Point Cloud POD files and achieving lower density before converting a POD to Terrain and back out to TIN). 
 Brief example adding information to a FieldBook and creating a terrain . https://www.youtube.com/watch?v=F2hYfhH2J0A 
 Terrain link and edits for features within a FieldBook (e.g. Survey Generated terrains). https://www.youtube.com/watch?v=kd6hgQ20OvU 
 Point Filter tool (2022 R2): https://www.youtube.com/watch?v=thMkR2RzDgw 
 Points Report from selection set and exporting to CSV demo: https://www.youtube.com/watch?v=boHv1hNv1yE 
 The overall Bentley Survey Learning path below. 
 https://learn.bentley.com/app/Public/ViewLearningPathWithMasterCourseExpanded?lpId=113451&mcId=113451&CourseId=130307&moduleId=135203