I ran into some weird problems a week ago, and with help from experts here, I figured out my problem: Importing DWG elevation data is hit or miss--if it wasn't set up for a logical terrain perimeter, or some elements of the terrain elevation layer are 0, it will totally mess up the Terrain Build in Chief.
Import survey data to a neutral layer (that is, don't map to elevation data), or just import a PDF file for tracing. Experts warn against using elevation points, and the tutorial videos make elevation lines seem like the obvious choice for creating fairly simple slopes. In my case, I modeled an entire neighborhood by tracing ~40 contour lines. Chief warned that building terrain with 2000+ interpolation points in non-Linear mode might take too long, but it finished in a few minutes.
Avoid these pitfalls:
Make sure the elevation splines start and end outside the Terrain Perimeter Don't let contour lines cross (thanks, @glennw!) Make sure that each elevation spline is continuous--I kept missing by a few pixels when I zoomed in, meaning that most of the spline was at the elevation I set and part of it was at 0. Move the ends near each other and Chief makes it just one spline. Double-check each spline's elevation--if just one is 0, your terrain will be messed up. Good news, though--fix it, re-build, and you're good
My smaller tests were successful, so I went for the whole 11-acre neighborhood--27 lots. My Terrain Perimeter is 892' x 550'.
Note: I didn't have to trace anywhere near the number of contour lines you see. I traced a plan with a 5' interval, and Chief interpolated to a 2' interval. Actually, I skipped some contours that added no value, but of course, Chief didn't.
Thanks to @glennw, @Renerabbitt, @Kbird1, @Chopsaw and--from a 15-month-old post-- @DavidJPotter
Clearly, I'm not thinking about this correctly.
On a new plan, create a default terrain perimeter. I drew 8 elevation splines, careful to start and end them outside the terrain perimeter. I opened each spline in turn and set the elevation to 92', 94', 96'...up to 106' in the upper right. Zooming in, the splines are labeled, showing that the lines are around 100'. Each spline started at the default elevation 0', but I manually set other values. There are no other objects on the plan that could suggest anything but 92' to 106'. I checked--Terrain Perimeters don't have an elevation.
So, imagine my surprise when I built the terrain and got this:
This can only be caused by my utter misunderstanding of how elevation splines are meant to translate to contour lines. Help!
I'm running Chief X13, Build 18.104.22.168x64 on a Dell running Windows 10.
Difficult terrain situation, help with creating appropriate slope on driveway on project using GPS terrain dataBy TrimbachDesign
Good afternoon Chief users,
All of our projects to date have been pretty straightforward terrain-wise, and despite spending way more time on this than I can to admit, and watching all of the tutorials I am still scratching my head.
A little background:
The site for this home has a lot terrain character, swales, hills, etc. Due to this, we brought our survey crew out to GPS map the site. I followed the Chief tutorial to bring in the terrain data generated (very slick process). During the design of this home a goal was to minimize grading and to preserve the unique characteristics of the site. I decided to stick the uphill side of the home into the hillside with a taller retaining stem wall to "split" the grade over the width of the home.
To get the site grading to mimic what we envisioned, I used elevation areas, some with "interior is flat" checked, a lot of trial and error during this process. One terrain modification I did was creating a flat area around the front of the home for the entry, and parking. Coming off this elevation area is where I am struggling. I have tried using multiple elevation regions and elevations lines to force the terrain to build at a gentle slope off of this pad. From my calcs we could easily adjust the driveway grade to have an appropriate slope. The problem area (directly off the flat parking area) is about 12 feet of rise over 80 feet of run (15% slope). I just want this area to be filled to allow for an even 15% slope. I have bumped up line weights, colored them red, and removed unnecessary information from the screenshot attached below for clarity.
Do any of you terrain wizards have any advice for me? I am happy to attach the plan file if desired.
Thank you all,
This is my first time trying to bring in data collected from GPS into chief arch. I have converted the CSV file into a txt doc but when i bring it into chief arch the land/terrain looks very off; there are tons of spikes/triangles on the area and I'm unsure how to make it "smooth". Also unlike other programs I've used when I click a point I don't get a description of the point, meaning i cant tell if I'm looking at a shot of the sidewalk or a portion of the driveway, im wondering if there is a more effective way to input this data or a way that will allow me to keep my codes/point descriptions that I set when i was in the field.
Any info/solutions on this topic would be appreciated.
I imported a Import a surveyor DWG file. I followed the instruction in the tutorial (Import a Surveyor DWG file for a Site Plan or Terrain Perimeter (chiefarchitect.com) . And got some strange spikes hills. I have tired cleaning up the elevation data but no luck. There is simply no elevation data in the area that is that tall, not sure what is generate this. Pleas see the attached pic and surveyor map.