Civil 3D import points from CSV, Excel or TXT: formats, latitude and longitude, duplicates and the most common errors

Civil 3D doesn't read .xlsx files. Before importing:

1. Order the columns to match the format you'll use. For PNEZD: number, northing, easting, elevation and description.
2. Delete the header row. A row with titles like "Northing" or "Easting" makes the file match no format.
3. The point number must be a whole number. If your points are named BM-1 or CP-12, put that name in the description or use a custom format with a name column.
4. Remove commas from descriptions. "EP, left side" splits the row into two columns and shifts everything after it.
5. Save as CSV (comma delimited) and open it in Notepad to see what Excel actually saved.

The free coordinate converter avoids all three problems: it downloads a PNEZD file with decimal points, no commas in descriptions and numbered points, and if a point is named BM-1 it moves the name into the description.

1. Insert tab › Points from File.
2. Add the file with the add button.
3. Pick the point file format that matches your columns.
4. Check the preview: compare a point against a known control point, and make sure elevations look reasonable. If numbers appear shifted by a column, the format is wrong.
5. Optionally check Add Points to Point Group and create a group named after the survey.
6. Review the advanced options before you click OK: elevation adjustment and coordinate transformation change elevations or coordinates, so only turn them on when you know you need them.

After importing, use Zoom › Extents to see where every point landed.

Easting first or northing first is the most common mix-up: many data collectors and spreadsheets put the easting before the northing. Pick PNEZD for a PENZD file and your points end up swapped and miles away.

To build your own format, open Manage Formats in the import dialog, copy a similar format and change the column order or delimiter. It's saved in the drawing, and in the template if you create it there.

Points from Google Earth, a handheld GPS or many GNSS receivers come in degrees. There are two routes:

Convert them first. Paste the points into the coordinate converter, check them on the map and download the PNEZD file in UTM. It's the safest route, because you see where they fall before importing.

Import them in degrees. First assign the drawing's coordinate system under Drawing Settings › Units and Zone, such as your State Plane zone. Then create a format with latitude and longitude columns. Without a coordinate system, Civil 3D doesn't know how to project the degrees.

If you import a point whose number already exists in the drawing, Civil 3D opens the Duplicate Point Number dialog. The options:

• Use Next Point Number: gives it the next free number.
• Add An Offset: adds a fixed value, such as 10000, to the new point's number.
• Sequence From: renumbers the new points starting at the number you enter.
• Overwrite: replaces the existing point with the new one.
• Merge: updates the existing point with the new data, keeping whatever the new point doesn't provide.

Apply to all uses the same answer for the rest of the file.

• "No point file format match found". The file has a header, is an .xlsx, uses semicolons, or has more columns than the format.
• Imported points not showing. Zoom › Extents. If they show up far away, northing and easting are swapped. If they don't show up at all, the group's point or label style is set to None, or the layer is off.
• Every elevation comes in as zero. The chosen format has no elevation column, or elevation is in another position.
• Points land offset. The file's datum doesn't match the plan's, or degrees were imported without a coordinate system.
• Descriptions get cut off. There was a comma inside the text.
• Point numbers come in changed. There were duplicate numbers and Civil 3D used the next free one without you noticing.

Importing is half the job. What makes the survey useful:

• Description keys. They assign style, label and layer from the code: everything starting with EP goes to the edge-of-pavement layer with its symbol. Set them up once in the template.
• Point groups by code, to decide what goes into the existing-ground surface and what doesn't.
• The surface, with breaklines and a boundary. We cover it in Civil 3D contours.

What eats the most time in a firm, and can be automated:

• Importing straight from the field Excel file, with no CSV step, using each crew's column order.
• Checking before import: duplicate numbers, zero elevations, points outside the project area, or codes missing from the description keys.
• Building point groups by code and the surface with the firm's rules.
• Validating every import with a short report, so errors are caught before they reach the design.