Hello Adam. I feel your pain. I don't deactivate the survey rules in my survey base file. Many times I have to add supplemental data to a survey. As you have found "re-activating" survey rules really open a can worms.
Is the client requesting a single file deliverable? Or do they want a DTM file (.tin)?
Here is my very abbreviated workflow:
1. I will create a surface file from the survey field books. Get that model worked out. Resolve crossing break lines, spikes etc.
2. Once I'm happy with that model, export that surface to TIN.
3. Re-import the TIN file through the "Create Terrain Model from file" tool. I make sure the TIN file has name that includes the creation date.
4. That surface is now the "frozen" in time. My survey surface can remain in an open state that allows revisions. If something does come up (and it will) I just repeat the process.
Our DOT is requiring us to submit a 3d survey file with no survey field books. Having the surface as a TIN file seems to fit into this workflow well.
Cliff
Is the client requesting a single file deliverable? Or do they want a DTM file (.tin)?
Here is my very abbreviated workflow:
1. I will create a surface file from the survey field books. Get that model worked out. Resolve crossing break lines, spikes etc.
2. Once I'm happy with that model, export that surface to TIN.
3. Re-import the TIN file through the "Create Terrain Model from file" tool. I make sure the TIN file has name that includes the creation date.
4. That surface is now the "frozen" in time. My survey surface can remain in an open state that allows revisions. If something does come up (and it will) I just repeat the process.
Our DOT is requiring us to submit a 3d survey file with no survey field books. Having the surface as a TIN file seems to fit into this workflow well.
Cliff