Point and line files

A DXF file is a 2D or 3D vector graphic file format generated from CAD software such as AutoDesk. DXF stands for Drawing Exchange Format.

For DXF files that contain layers, a name is generated for every selectable feature in the file. A code can be generated for every selectable feature within the file. This is derived from the attributes stored in the file; often, it is the name, code, and attributes of features in the original file.

For DXF files, the name is the first 8 characters of the layer name, followed by a space and then the line number of the feature in the DXF file. For DXF files from Survey Office the item name, where present, is used.

You can review a selectable feature in the map to find the file and layer name.

Displayable and selectable DXF items:

• ARC, CIRCLE, INSERT, LINE, POINT, POLYLINE, LWPOLYLINE.

Display only DXF items:

• 3D FACE, SPLINE, SOLID, ATTRIB, BLOCK ATTRIB, TEXT, MTEXT, HATCH.
• Control characters: C – diameter symbol, D – degree symbol, P – plus/minus symbol, % – percentage symbol.

Extrusion arcs contained in a DXF file are displayed correctly in the map, but cannot be made active. Extrusion arcs form an ellipse in plan view and the staking of ellipses is not supported.

A Shapefile is an ESRI vector data storage format for storing geographic features as points, lines, or polygons as well as attribute information.

For Shapefiles that contain layers, a name is generated for every selectable feature in the file. A code can be generated for every selectable feature within the file. This is derived from the attributes stored in the file; often, it is the name, code, and attributes of features in the original file.

For Shapefiles, the name is the first five characters of the Shapefile name, followed by a file index number, then a space and then the line number in the Shapefile where this feature is defined.

You can review a selectable feature in the map to find the file and layer name.

Supported Shapefile items:

• Null shape, Point, PolyLine, Polygon, MultiPoint, PointZ, PolyLineZ, PolygonZ, MultiPointZ, PointM, PolyLineM, PolygonM, MultiPointM, MultiPatch, Hatching.

To view attribute information for Shapefile items, the Shapefile must have an associated .dbf file.

The displayed layers in a 12da file are based on the model names in the 12da file. In addition, any surfaces and alignments read in from a 12da file are placed in their own layer. If there are any duplicate layer names, suffixes consisting of an underscore character plus an incrementing number are used to ensure unique layer names.

Point strings are read in as points and assigned to the appropriate layer. The points are given the names specified in the 12da file, but if no names have been specified they are given names based on the string name plus a suffix consisting of an underscore character plus an incrementing number.

Line, arc and circle strings are read in as standard lines and arcs and assigned to the appropriate layer using the color specified in the 12da file, when standard colors have been used.

Polyline strings are read in as polylines or polygons (for closed polylines) and assigned to the appropriate layer using the color specified in the 12da file, when standard colors have been used.

Super alignments and alignments are read in as alignments and each alignment is assigned to its own layer. Alignments are displayed as a red line.

Triangulated surfaces are read in and each surface is assigned to its own layer.

A LandXML file is an XML file format for civil engineering design and survey measurement data such as points, surfaces, parcels, pipe network data and alignments.

LandXML files can contain different XML elements and what they contain will depend on the application that created the LandXML file, the items selected and options chosen at the time of export. Only points, lines, surfaces, and alignments that are contained in elements directly under the primary LandXML element are supported.

The following lists the element types and how they can be used in Origin:

• Alignments only

  Stake as an alignment, using Origin General Survey or Origin Roads.

• Alignments with templates

  Save and then stake as an RXL road, using Origin Roads.

• Parcels and feature lines

  Stake as a polyline, using Origin General Survey or Origin Roads.

• Alignments and feature elements defined as per the Inframodel specification

  Alignments are grouped to form a road surface, you can have multiple roads in a single file. Stake using Origin Roads.

• Alignments and breakline elements in a surface element

  Alignments and breaklines from the surface element are grouped to form a road surface, you can have multiple roads in a single file. Stake using Origin Roads. The Survey Office LandXML exporter creates files using this format, Points, surfaces, parcels and feature lines can also be included in this file export. For more information, see Export LandXML string roads from your office software.

The layers created for LandXML files are based on the following:

• Point items (from <CgPoint> elements) are placed in a layer called Points.

• Line items (from <Parcel> and <PlanFeature> elements) are placed in a layer called Lines.

• Alignment and surface items are placed in layers named according to the alignment and surface names.

A code can be generated for every selectable feature within the file. This is derived from the attributes stored in the file – often, it is the name, code, and attributes of features in the original file. You can review a selectable feature in the map to find the file and layer name.

If there are overlapping surfaces on the map, the interpolated elevation will be that of the first surface returning a non‑null elevation (the surface with the first name alphabetically).