A personal rule and good forum conduct, is to post the answer to the question so other people who search for the same issue, can find a solution instead of more people with the same woes. Jeff pretty much had the right idea, formatting. At first I thought that was crazy talk, because the files are so large, but using 'find and replace' automated everything for me, so he really was correct. Below is how to format the file.
What was FILE.LIN looked more like this:
2
5737515.60 2100874.22 421.89
5737495.34 2100874.94 422.32
5737493.00 2100875.02 422.37
END
2
5737532.54 2101180.39 459.01
5737527.41 2101179.87 458.02
5737505.69 2101172.95 454.11
5737493.00 2101168.90 451.87
END
2
5737973.52 2100951.14 507.74
5737939.26 2100958.91 500.55
5737904.99 2100966.67 493.34
5737878.68 2100974.46 487.08
5737852.36 2100982.24 480.80
5737825.86 2100994.17 471.95
5737825.51 2100994.33 471.83
END
So, I renamed the file extension to FILE.FLT and performed the following series of find and replaces...
Find Replace
7 spaces 1 space
3 spaces 1 space
2 spaces 1 space
END blank (meaning replace them with nothing)
2 S (check the match whole word checkbox in settings)
3 S (check the match whole word checkbox in settings)
S^p S
S with 1 space S
That produced a file that looks like this:
S5737515.60 2100874.22 421.89
5737495.34 2100874.94 422.32
5737493.00 2100875.02 422.37
S5737532.54 2101180.39 459.01
5737527.41 2101179.87 458.02
5737505.69 2101172.95 454.11
5737493.00 2101168.90 451.87
S5737973.52 2100951.14 507.74
5737939.26 2100958.91 500.55
5737904.99 2100966.67 493.34
5737878.68 2100974.46 487.08
5737852.36 2100982.24 480.80
5737825.86 2100994.17 471.95
5737825.51 2100994.33 471.83
This tells whatever fault types 2 and 3 to be treated as standard faults. If you have zero elevations, you'll want to replace with P for proximity faults. Good luck! =)
Edited by: steve-dude on Aug 12, 2009 4:49 PM