About Supported Data Types

AutoCAD Architecture 2022 toolset can read and convert the following LandXML data types:

Parcels

Parcels are two-dimensional shapes created from closed lines, arcs, and polylines. When a parcel is imported, the parcel name and the lines (segments) and curves (arcs) that make up the parcel boundary are used for the conversion.

Parcels in a street layout from Autodesk Land Desktop

You can convert parcels to spaces or polylines. When you convert parcels to spaces, you can define a space style that is applied to the spaces generated from the parcels, and the parcel name is used as the space name. When the parcel is converted to a polyline, the parcel name is lost.

Parcel data in LandXML

COGO (Coordinate Geometry) Points

You can import LandXML COGO (Coordinate Geometry) points and convert them to AutoCAD points.

Civil engineers create COGO points to locate crucial surveying locations. A COGO point can be a project benchmark point - a common datum that the entire civil team works off and from which all critical dimensions are located.

Note: A LandXML file usually contains a large number of COGO points. In most cases, you need only a small set to work within the drawing. You do not need to import all COGO points, only those that have a special meaning for the drawing.

COGO points are the foundation for any civil engineering or surveying project. In Land Desktop, you can use description keys to place points in the drawing with symbols on specific layers. When importing a LandXML file you can map selected points to the appropriate layer.

When a COGO point is imported it is defined by its coordinates in the form of “northing easting” or “northing easting elevation.”

For example, a COGO point could be represented as: <CgPOINT NAME="1" DESC="MYPOINT">248.04605951 359.53997314 1.000000</CgPOINT>.

COGO points on a map

Note: Autodesk Land Desktop uses two coordinate systems for locating points: X,Y and northing/easting. When you start a new project, these values all default to 0 so that the Y coordinate is the same as the northing, and the X coordinate is the same as the easting. Unless you change that in Land Desktop before exporting a drawing to LandXML, the exported northing value will be identical to Y and the exported easting value will be identical to X.

Surfaces

In most surveying and civil engineering operations, you gather information about elevations to generate surface contours that represent a model of the ground surface. The surfaces in LandXML are made up of many faces which are either TINs (Triangular Irregulated Networks) or quadrilaterals. Points or contours are usually a primary part of the original surface information and are supplemented with break lines and boundaries. You can create a surface in LandXML, and then import it. It is converted to a Free Form mass element.

In the following cases, importing surfaces can create errors or fail altogether:

If the import fails, an error message is displayed on the command line, such as “Failed to create mass element from terrain.”

Surface model in Autodesk Land Desktop

A surface model is usually a complex structure with many defining points and faces. When you convert a surface model to a Free Form mass element, the points and faces are merged into one composite mass element body.

Surface model detail

A Free Form mass element contains a large number of grips. Displaying all grips can slow down the performance and be unnecessary for using the mass element. There are two ways to control the display of grips on mass elements:

A surface in the LandXML Schema contains information about the surface name, type, 2D and 3D area, and the maximum and minimum elevations. It also contains information about each of the points and faces that comprise the surface. The surface information is merged into one composite mass element body, which can have thousands of faces. Applying a surface hatch or texture map to a complex mass element can be quite time-consuming.

Surface data in LandXML