Sdnf file format

If the user changes the version setting, the system will not work because it is expecting a file of a radically different format. However, the interface will fail in a controlled manner producing a "catch-all" error message such as…. If the user manually selects the wrong SDNF version, they may also get an error message in the log file about syntax errors in the incoming file.

This is because the Packet 00 records are different. Only 1 Packet of this type must be included. It describes the run for the data transfer. Its record structure is as follows:. They are described in the SDNF file as follows:. There are several ways of defining a Linear Member using different combinations of the above data elements, some of which will not be interpretable by other systems. The method of interpretation of these fields is defined below.

Close and rigorous study of the definition of Linear Members in SDNF will reveal that there are many ways in which a Linear Member may be located in space. Combinations of information stored in records 3 to 5 per Linear Member will determine its location. The main requirement is that the Cardinal Point is to be used to draw the lines in schematic drawings such that, where possible, a connected model may be deduced.

The Start and End cutbacks Record 3 are ignored by default, but see section 6. The Start and End Position of the Member Record 3 is the start and end position of the 'real length of steel' located on the line described by the Cardinal Point Record 1. Thus, using Record 5 with Record 3, the Node position could be determined. The sense of this eccentricity is a vector from the end of the member to the node position.

All packages are assumed to export the start and end positions of the Linear Member's Cardinal Point Line. The Rotation and Orientation Vector attributes of a Linear Member determine the orientation of the element about its axis. The Orientation Vector defines the default orientation of the member before any rotation has been applied to it.

The Rotation is then taken as a right handed rotation about the axis from that default vector as one looks along the member from start to end - the local Z axis. Each plate is represented by a variable number of records that follow:. Plate periphery defines the type of boundary: 0 is a boundary with straight edges; 1 is a boundary with straight and curved segments; 2 is a circle.

ProStructures is able to export the CAD-system data for standard shapes and plates without detailing processes and connection elements. A plate made out of a number of polygons is exported correctly.

If detailing processes created it, only the basic polygon will be output. In addition, the static analysis system for standard shapes can be written. In combination with a suitable exchange list it is thus possible to create a file with imperial units from a metric drawing file or vice versa.

SDNF supports the exchange of a steel structure data between two applications. Each packet of information in the file contains a specific type of information: Packet 00, Title Packet Packet 10, Linear Members Packet 20, Plates Packet 00 contains information necessary to identify the neutral file.

The name of the engineering firm, the client name, structure name, project name, date and time of file creation, issue code and design code are identified within this packet. Packet 10 contains the description of the structural framing in the structure. All information required to locate, orientate and describe a particular framing member is contained within this packet. This packet also identifies member end connections as released or fixed.

For purposes of revision tracking, each member is also assigned an individual revision level. Packet 20 contains plate information. Plates are located spatially by identifying the number of plate vertices and the co-ordinates of each vertex. Maximum record length will be characters. All records except the fixed-format Packet identification records are free formatted, with fields delimited by white space blanks.