DWG Import Issues

[PoiPounder]

I don't know if I am just too naive or if the file was set up incorrectly from the surveyor, but I can't figure out how to import the boundary and elevation data into my new project properly. Attaching the file below. I have followed other posts on the import process, but keep having issues. Can anyone tell me if it's possible with this file? 

 

Everything seems to be under the label "0" for what I need. The perimeter boundary as well as the elevation data.  Unsure how to correct this and import the proper way. I noticed that the jagged elevation lines are in one big block, unsure how to separate those out? I would really appreciate your help with this daunting endeavor.  

 

Using Chief 10

23-84 subd 7-2-24.dwg

Edited March 3 by PoiPounder

[SteveCanbury]

Worked fine for me. BUT, I think what is going on, there are 2 drawings that are separated, I'm assuming they should be superimposed.

If you scroll WAAAAY out you'll notice 1 part of the image (appears to be a neigborhood/ cul de sac) with no information on the top right corner.

THEN to the bottom left is all your Compass and Elevation Data.

As far as how to proceed from there, That is beyond my current level of Chief knowledge.

Hope this helped you get a little further.

 

New Plan > File > Import > Import Drawing 

In the Import Drawing Assistant I used these settings shown in screenshots ...

[SteveCanbury]

Problem Solved

I removed the black overlay and moved the Information Layer

Chief User DWG.plan

Edited March 4 by SteveCanbury

[PoiPounder]

I can import the file, but actually converting that into elevation data to show the gentle hill is what I can't figure out how to do? I don't necessarily need all the information. Just the boundaries and the ability to import the terrain data that actually will translate on the program. Instead of seeing the lines, actually have it affect how the terrain and elevation look. Any ideas?

 

Unfortunately I have an older version of Chief and can't open the file you created. I appreciate you doing so though.  Thanks for going above and beyond. The other thing I don't get is that when you click on the elevation lines in the plan its one giant BLOCK. not separate information.

Edited March 5 by PoiPounder
missed something

[BenPalmer]

https://www.chiefarchitect.com/support/article/KB-00719/importing-terrain-elevation-data-from-a-dwg-or-dxf-file.html

 

https://www.chiefarchitect.com/videos/watch/1056/import-a-surveyor-dwg-file-for-a-site-plan-or-terrain-perimeter.html

[PoiPounder]

I am seriously banging my head against the wall here. Watched both videos and followed all steps and it's just not working. From what I can tell there are only really 3 contour elevation data points, which is very odd. The other numbers seem like they are just labels, which makes no sense as there is a berm at the bottom of the lot on the wider side of the dwg file. 

 

The perimeter isn't closed and i have to try and reconnect it to convert to my terrain perimeter. It's a real pain the as* and doesn't work like the videos say it should. Sometimes i have to retrace the whole polyline just to be able to close it and create a terrain perimeter. 

The elevation data points just don't work. I swear I am doing something wrong. The company that did the survey told me the elevation data was on the POINTS label, but it really doesn't do anything when i import it that way. Any ideas? Does this create properly for you when you import it? Am i just daft?

[PoiPounder]

I select Terrain>Elevation Data>Elevation Line and trave the ones that have actual elevation data (52, 50, 48) and I get this whack elevation map afterwards. Do I need to trace every single one of the contour elevation lines? Any advice would be greatly appreciated.

[JiAngelo]

The surveyor needs to unblock everything on Layer 0.  

 

Your points() layer is importing as a block on Layer 0.  Select one and you can only hide it by turning off Layer 0.  Turning off the points() Layer does nothing until you unblock an object on Layer 0.  Chief can't read points data within a blocked object.

 

Contact your surveyor and have him send you the unblocked model.  He exported his plan view.

 

Also, the unit of import is Feet.

Edited March 11 by JiAngelo
Additional info

[PoiPounder]

I called him and asked him to unblock everything and he sent me this file. Now it seems not to work more so than before...

 

I don't know what to do at this point. Does this seem like it works for you when you open it? I don't even see the perimeter lines anymore...

john updated23-84 draft subd (1).dwg

Edited March 14 by PoiPounder

[JiAngelo]

Actually, import with Contours as elevation data and you will find the data is there on Contours. The one I selected says 49'

If you zoom in you will see your points(4-13-24) fall between the correct contours.  Unfortunately, your going to need to call him back and tell him "unblock everything" includes everything, not just some things. Everything on Points(4-13-24) is still in blocks on Layer 0. And Chief doesn't assign elevation data to a block.

• Red circle is his block of points(4-13-24) data, still blocked up on Layer 0..
• Green circle is after I unblocked one group.  It contains 4 objects.  Chief needs them unblocked to read the data.  Technically the elevation "X" point & Point.ELEVATION data (49.505) should be on its own layer.  Point.NUMBER (129) and Point.NAME (GD) should be on separate layers.  At least that's how my equipment exports them and Chief loves it.   And if he doesn't move Point.NUMBER to another layer, you may find an elevation 129' and 49.505' right beside one another.
• If you tell Chief Points(4-13-24) is elevation data, when you import now the "X" disappears, but no values are set because the data is in a block 

In case he still doesn't get it, show him this.

• 
• This is a block of points(4-13-24) data.  Notice it is also on Layer 0 (as a Cad block).  You can only turn it off by selecting Layer 0.  Selecting the points() does nothing.

And show him this.

• 
• This is after I unblocked the group.  Notice they all now exist individually on only the points(4-13-24) layer.

 

Pro Tip - the Boundary is on BDRY2, and true to form, it isn't closed.  In fact it's nowhere close.

• The BLACK and RED lines don't share a common point, so they can't join with one another.
• The GREEN line has no "Polylines, Label" Layer so it can't join with either Black or Red, which do have a "Polylines, Label" Layer.
• And I don't know if the YELLOW line means this is two lots, but it has no "Polylines, Label" Layer either and neither BLACK or RED have breaks in their lines where YELLOW meets them..
• Chief requires all to be the same to connect automatically.
• This just means you are going to have to draw that terrain perimeter yourself.  Not the end of the world, but just maddening when surveying is all about precision.
• 

 

Hope this helps.

 

[PoiPounder]

This is really helpful John. Thank you for the details and the screenshots. I emailed our surveyor what you mentioned above and he sent me these two files attached below.

 

He re-saved the file for a different version of CAD. 

The TXT file shows point information (Point,Easting,Northing,Elevation,Description).

 

When I import this and label 0 as perimeter and points(4-13-24) as elevation data. I get the following screenshot.

 

The polylines around the perimeter are gone and same with the elevation contour lines. I can see them when i display the other layers in 0. I guess this means he still failed to explode all block objects. He merely saved it as an older CAD version?

 

When you open up this file did he do what you mentioned above and unblock everything like I requested? Or did he just save the exact same file for a different version of cad and do nothing with the layers? 

 

 23-84 savedown.dwg23-84.txt

Edited Tuesday at 01:43 AM by PoiPounder

[JiAngelo]

I think the only thing the surveyor cleaned up was the boundary on BDRY2.  Points() layer is still grouped as a cad block.in Layer 0.  I forgot that if you don't specify anything as a terrain, but you do specify a Layer that does have elevation data present, Chief will automatically add a terrain that encompasses all the elevation data.  Import the file and only specify contours as elevation data.

 

I work on a white background, most Surveyors use black.  I've changed the Terrain Layer to Color Orange with Line Weight 1000.  On the BDRY2 layer, I change it to Color Blue & Line Weight 1000 (which initially does nothiing because every surveyor has this unchecked and yellow individually.)  Select each BDRY2 lot perimeter line and in the dbx check Line Style boxes Color, Style & Weight.  Close dbx and the lines should change to Blue & 1000.  You should see this.

 

With regard to the green circles,

The bottom arc doesn't run to the end, it straightens out and you need to change that line to Blue 1000 too.

At the upper left circler there are two lines that I'd seen in the file earlier.  You can ignore them, or move them out of the way temporarily. 

 

Now that the perimeter has all blue lines with the same Styles checked, select on at the corners and it will connect to the adjacent blue lines automatically.  Do this at each disconnected corner until you see a closed boundary for your lot perimeter.  

Notice the Terrain perimeter doesn't cover the entire lot - because there is no elevation data in those corners.

Notice below your contour lines don't reach the ends of your lot.

Chief guesses (extrapolates) what to do where no data is present and it rarely guesses what you'd like to see.

Typically I'd reshape my terrain perimeter to match the lot + 5-10 feet at the sides and rear, maybe 30-60' at the front to show the road.

The easiest way is to first drag each corner to a lot corner.

Which then becomes this.

Note you could have simply deleted the terrain, copied the lot perimeter in place and changed that polygon to a terrain if you wanted the curves to match. 

 

Open a 3D Camera and Chief will generate the contours as best it can with the data thus far.  When you go back to the 2D drawing you will see these contours.

At this point I'd probably give up on my surveyor and since I didn't import the Points() layer as data, I would place some elevation points on those X's.  I don't care if they are slightly off.   Make sure CAD is set to Ft, decimal feet, with precision 3 decimal places (I usually have quadrant bearing turn on as well.) and add the macro to show elevation label.  Here's what you should see.

  

I'm not so concerned with the rear lot contours.  But the 52' contour line that is running under the Makalulu text I extended past the perimeter edges so that it wouldn't create a circle. these random extensions cross one another.  Below is all layers off with contours, bdry2 and terrain perimeter turned on. (easier to see what you are doing)

Now, wherever I'm planning to build and I need finer point data (or at the lot corners & road, where it is missing data, I would copy the elev point to those locations and change the value.  I copy it because it already is set up for how I want to see the data formatted & displayed.

Place as many points as you actually need.  I also add a 1' tall fence along the side property lines and the road so that my 3D view looks like this.

This way when i start drawing a building I have some perspective on how close it is to the road and side lot lines in 3D views.

 

I hope this helps.