County GIS Contours to CAD: A Septic Survey Import Checklist

To import county GIS contours into CAD for a septic survey, confirm the file's coordinate system and units first, bring the lines in with the import tool your CAD offers, then check them against known points on the site before you trust them. An AI agent can read the file's metadata, flag mismatches and prepare a repeatable routine, but you decide whether county contours are good enough for the design or whether the site needs a surveyed topographic map.

Key takeaways

• Most import failures come from a mismatch in coordinate system, units or elevation fields, not from the CAD software itself.
• County contours are a planning aid. Whether they are adequate for a particular design is your professional call, and your state rules and the permit authority may have something to say.
• Check the imported lines against something you know: a property corner, the house slab, a surveyed spot elevation.
• An agent is useful for inspecting the file, reporting what it found, drafting a script and keeping a record of the settings you used.
• A repeatable checklist turns a messy manual import into a short, predictable step.

Why do GIS contours cause so much trouble in CAD?

County GIS data is built for mapping, not for your drawing. It comes in formats like shapefiles or geodatabase layers, or sometimes as DXF or DWG exports, and it is tied to a coordinate system that the file may or may not declare clearly. Your drawing, on the other hand, may be a local grid drawn from a boundary survey in feet, with an origin that someone picked years ago.

So the common failures are predictable. The contours land far from the parcel because the coordinate systems differ. They arrive at the wrong scale because of a units mix, such as feet against meters or survey feet against international feet. They come in flat, with the elevation stored as an attribute instead of as the drawing's Z value. Or they are densified into thousands of tiny segments that make the drawing slow.

If you work in AutoCAD, the Autodesk help documents the import tools and coordinate system settings, and the exact commands depend on your version and toolset. If you work in an older program or an older DWG format, a conversion step through a free GIS tool can bridge the gap. The older-format question is covered in legacy CAD and DWG versions with AI.

What should you check before importing?

A few minutes on the file saves an hour on the drawing. Look at these before you bring anything in.

• The declared coordinate system and its horizontal units.
• The vertical datum and vertical units, if stated.
• The contour interval and what the elevation field is called.
• The extent of the file, compared with the parcel's location.
• The age and source of the data, since terrain changes and grading changes it.
• Any usage notes from the county about accuracy or intended use.

This is a natural job for an agent. It opens the metadata, reads the extent, compares it to the parcel position you give it, and reports in plain language: what the file says, what it does not say and what looks inconsistent. It does not guess a missing coordinate system. It tells you the file does not declare one and asks you to supply it.

A step by step import routine

Adapt this to your CAD program and your habits. The order matters more than the exact commands.

• Save a copy of the drawing before you start, and keep the original GIS file untouched.
• Set or confirm the drawing's coordinate system and units so they match the survey base.
• Clip the GIS data to the neighborhood of the parcel before import, so the drawing does not carry a county's worth of lines.
• Import the contours with the elevation field mapped to the Z value, or to a label you can read.
• Place the contours on their own layer with a clear name and a color that does not fight the survey.
• Check position: the contours should sit on the parcel, not across town.
• Check scale: measure a known distance, such as a property line, and compare it with the survey.
• Check elevation: pick a spot where you know the height and compare it, and read the interval to make sure the labels make sense.
• Simplify the polylines if the file is heavy, without flattening the shape of the terrain you need.
• Note the source, date and settings in a short block on the drawing or in your notes.

An agent can draft a script or a saved routine for the repeatable parts, and it keeps the log of which settings it used. You review the script before you run it, as you would review any macro from a colleague.

An illustrative scenario

This is an illustrative example, not a real project. A designer downloads contours for a rural parcel from the county portal. She imports them and the lines appear in the wrong part of the drawing, far from the boundary.

Instead of dragging them into place by eye, she asks the agent to inspect the file. It reports that the layer declares a state plane system in one linear unit while her drawing uses a local grid, and that the elevation sits in an attribute field, not in the geometry. She confirms the system, redoes the import with the right settings, and the contours land on the parcel.

Then she checks two things the agent cannot judge. A property corner and the house slab are where they should be, and a spot elevation from an earlier survey is close to the contour at that location. She also looks at the terrain behind the house and decides that the interval is too coarse for the drainfield area, so she plans to take a few field shots there. The agent did not make that call. It made sure that she was looking at the right data when she did.

How Be Human handles this as a managed service

Be Human designs, implements and operates personalized AI agents for small businesses. For a design office, an agent can sit beside your CAD workflow: you give it the county file and the parcel, it inspects the data, reports what it found, drafts the import routine for your CAD version and keeps a record of the settings. It works on copies, it does not change your drawings without you, and a person at Be Human maintains it and adjusts it as your tools change.

The contours feed the rest of the site plan, so this step connects to the larger workflow in AI AutoCAD septic site plan and to the overall approach to AI in septic design. The general service is on the managed AI agents page.

Where to start

Pick one county you work in often and write down, once, the coordinate system, units and field names its contour data uses. That short note becomes the first line of your checklist and saves the same detective work on every parcel. Take the free Be Human AI diagnostic to find the first task worth handing to an agent.

Frequently asked questions

Are county GIS contours accurate enough for a septic design? That depends on the source, the age, the terrain and what the design needs, and it is your call as the designer of record. County contours are useful for orientation and early planning, and some sites may need surveyed topography. Check the county's notes on the data and your state rules.

Why do my imported contours appear far from the property? Usually the coordinate system of the GIS file does not match your drawing, or one of them does not declare it. Confirm the system and units on both sides, then import again with matching settings and test the position against a known corner.

How do I get elevations onto the contour lines? Many GIS files store elevation as an attribute, and the import tool has to map that field to the Z value or to a label. Check the field name in the file's properties, set the mapping at import and confirm with a spot you know.

Can an AI agent do the import for me? It can inspect the file, report what it finds, draft the routine and keep a log of the settings. You should review any script before it runs on your drawing, and you remain responsible for deciding whether the contours are suitable for the design.

Be Human editorial guidance. Examples are illustrative unless explicitly attributed. Sources provide background; implementation choices depend on your workflow.