Import DXF
Load and Excavation boundaries can be imported into Settle3 from a DXF file (AutoCAD Drawing Exchange File), using the Import DXF option in the File menu. This allows users to import drawings created in AutoCAD, for example, into Settle3.
Importing boundaries from a DXF file is equivalent to adding boundaries using the Add Polygonal Load or Add Excavation options.
To import boundaries from a DXF file:
- Select Import DXF from the Import sub-menu of the File menu.
- In the DXF Options dialog, select the entities you would like to import, using the checkboxes provided.
- Select the Import button, and you will see an Open File dialog. Select the required DXF file and select OK, and all entities you selected in the DXF Options dialog will be imported into the current Settle3 document.
- NOTE: Load boundaries will be imported as polygonal loads.
Layer and Entity Types
If you are using AutoCAD to create DXF files for import into Settle3, use the following conventions for layering and entity type:
Settle3 Object | Layer Name | AutoCAD Entity Type |
Polygonal Load Boundary | LOAD | Closed LINE / POLYLINE |
Excavation Boundary | EXCAVATION | Closed LINE / POLYLINE |
Importing Arcs from DXF Files
True circular arcs CANNOT be used to define boundaries in Settle3. All boundaries in Settle3 are made up of linear segments connected by vertices.
However, if you import a DXF file which uses true arcs to define boundaries, Settle3 will automatically convert arcs into a series of linear segments, which approximate the arc.
By default, Settle3 will convert an arc from a DXF file into 16 line segments. This value can be customized by the user if desired, in the Preferences dialog. Select File > Preferences, enter a new value for DXF arc discretizations, and select OK. This value in the Preferences dialog will always be used to convert arcs read from DXF files.
DXF Epsilon
When you import a DXF file with multiple lines or polylines of the same layer type (e.g. LOAD entities), Settle3 will automatically attempt to "piece together" individual entities to form larger polylines, if vertices overlap or are within a certain distance of each other. If two vertices are very close to each other, but have slightly different coordinates, Settle3 will automatically join the entities at that location, if the vertices are sufficiently close together.
The parameter which controls this automatic merging of vertices is the DXF Epsilon. The DXF Epsilon option can be found in the Preferences dialog in the File menu. The DXF Epsilon is a relative value, which defines the critical distance between vertices, as a fraction of the maximum extent of the model. If the distance between two vertices is less than the DXF Epsilon (multiplied by the maximum extent of the model), then the two entities will be merged at that location.
A default value of DXF Epsilon is automatically in effect, however, the value can be adjusted by the user, if the DXF file is not importing correctly. In some cases, this may help, although this should be considered an advanced option which is not commonly used. Before you adjust the DXF Epsilon value, you should go through all of the troubleshooting tips listed below.
Troubleshooting Problems with DXF Import
If you are having problems trying to import a DXF file into Settle3, this may be due to one or more of the following issues:
- Carefully examine your coordinate values to determine if this is the problem. Sometimes the coordinates of two vertices are very nearly equal, but are slightly different in the last decimal places. Check all vertex coordinates and make appropriate modifications to ensure that boundaries are continuous and closed.
- If a boundary in a DXF file consists of multiple lines/plines, it is best to convert it into a single, closed polyline, before you try to import into Settle3. Although Settle3 does attempt to join segments in a DXF file into larger polylines (see the DXF Epsilon discussion above), it is better if the user does this manually, rather than relying on the automatic capability of Settle3.
- In AutoCAD, save each boundary entity from the main DXF file, into its own separate DXF file, by using the dxf export option in AutoCAD to pick each entity you want to export.
- Import the DXF files into Settle3 one at a time. Only have one box checked (e.g. Loads) in the DXF Options dialog in Settle3.
- If you follow this simple procedure, this will often allow you to successfully import the DXF geometry into Settle3, and identify the source of any problems.
- You might want to practice this procedure, by starting simple just to get the process down. For example: draw a simple load boundary in AutoCAD, export it. Draw an excavation boundary, export it. Now bring them into Settle3 in the same order, one at a time.
Layer Names
Check that you are using the correct layer name for each entity. A summary of layer names for the various Settle3 entities is given in the table above.
Layer Assignment
Check if entities in the DXF file are assigned to the correct layer.
Polyline Not Closed
In Settle3 Load or Excavation boundaries must always be CLOSED (i.e. they must form a closed polygon with the first vertex equal to the last vertex). If loads or excavations are not properly closed, you will not be able to import them into Settle3.
Coordinates must be 2-dimensional and in the XY plane
Settle3 does NOT support the import of 3-dimensional geometry. All lines/polylines must be 2-dimensional and in the XY plane (Z=0). If you have 3-dimensional (x,y,z) coordinates or if you have 2D coordinates which are not in the XY plane (e.g. XZ or YZ), then you will have to apply appropriate conversions and/or rotations to obtain the desired 2D geometry.
User Coordinates
Settle3 does NOT support the import of entities defined by User Coordinate Systems (UCS). The DXF file reader will only read coordinates in the World Coordinate System (WCS) with the 2D geometry (polylines, lines) on the XY plane (Z=0).
Very large coordinates
If the absolute value of X and/or Y coordinates are very large, relative to the extents of the model, this may cause problems with DXF import due to numerical precision issues. Furthermore, even if the DXF import is successful, very large coordinates can lead to modelling difficulties and/or incorrect analysis results. If the X and/or Y coordinates in your DXF file are extremely large, then you should translate the entire model to the origin (0,0), to avoid potential problems. For example, if the Y coordinates of your model are around 100,000, then apply a translation which shifts the entire model by -100,000 on the Y-axis.
As a general guideline, the ratio of the maximum model coordinates divided by the maximum model dimensions (e.g. maximum X-coordinate divided by maximum X extent), should be less than approximately 10,000. If this ratio is greater than 10,000, then numerical precision issues may occur, and the model should be translated closer to the origin (0,0).
Measurement Units
Make sure that your measurement units are either meters or feet, according to whether you are using metric or imperial units in Settle3.
Importing Arcs
See the Importing Arcs section (above).
Too many closely spaced vertices
It commonly occurs that DXF polylines have a large number of unnecessary vertices (i.e. the geometry could be accurately defined with a much smaller number of vertices). Also, vertices are often located very close to each other, due to the automatic creation of 2D sections from 3D geometry, or due to manual digitizing procedures.
Although there is no limit to the number of vertices which can be imported from a DXF file, it is a good idea to simplify the geometry as much as possible, by deleting unnecessary vertices, so that the geometry is accurately defined by a smaller number of vertices, and vertices are not extremely close to each other.
Recommended DXF Import Procedure
If you have gone through the troubleshooting tips (above) and you are still having problems with trying to import DXF geometry into Settle3, the following procedure is recommended.
Save as DXF version 12
In some cases, it may help if you save the DXF file as (AutoCAD) version 12 or 13. However, this is not recommended unless you have tried all of the above options first.