Hi Sinc
I have tried some variations of the weeding and the results of what the contours look like or don't seem hard to submit
in a plat that I would want to turn in. My example was taken from Lidar and made into a 3d Poly. So, wanting to make a surface
with it is where it got to be challenge. I tried weeding and the contours on the top of mesa's started to make nonsense contours.
So, this is a working from a 1/2 section of data. I am hoping to use data shortcuts to work with the surface and that seems to work.
What was happening in the experience over this weekend of experimenting was that I had to switch from Win 7 32bit to Win 7 64bit
because of memory limitations. Now after playing with the large file of contours it died after 4.7 gig of memory used. I have plenty of memory
and set page file to 12 gig max and wondered why it died so quickly. I thought Civil 3d 2010 could handle it. Am I the only one finding a
another limitation with filesize and Civil 3D? This has to be answered first before I can start to understand the procedures to use for
working on large projects and phasing. Your thoughts?
MJP
The test is relevant to show that weeding can indeed introduce error in the resultant surface built from contours.
LIDAR data is another animal, and one will in most instances need to use judgement in reducing that data to create a usable surface model from.
Well, of course weeding can introduce error. That's a given, and we don't need a test to prove it.
The goal in this sort of task is simply to reduce our Civil 3D surface to a point where we have an acceptable trade-off between performance and accuracy.
And the only thing that's important for that is, after we try some weeding factors, to compare the resulting contours with the starting contours. If the results are "close enough" for whatever purposes we intend, then we can proceed. We do not need to worry at all about the fact that the contours originally came from Lidar data.