How Municipalities Can Turn Engineering Drawings into GIS Asset Data

Ask a public works supervisor where a 1970s watermain runs and you’ll often get two answers: the version in the drawing cabinet and the version a senior operator remembers. Decades of design plans, as-builts, and survey sheets hold most of what a municipality knows about its buried infrastructure, but in that form the information is hard to search, hard to share, and easy to lose.

Moving engineering drawings to GIS changes that. Instead of flipping through rolls of paper, staff can click on a pipe and see its size, material, install date, and the drawing it came from. This guide walks through how that conversion actually works, from finding the records to keeping the new data current.

Why Engineering Drawings Are Difficult To Use When Records Are Disconnected

The drawings themselves are usually fine. The trouble is everything around them.

Records Spread Across Too Many Places

Over the years, drawings end up in flat files, archive boxes, consultants’ offices, and scattered network folders. Finding the right sheet for one street can take an afternoon, and some records simply can’t be found.

Drawings That Don’t Line Up With Today’s Maps

Older plans were drawn at different scales and in older coordinate systems. Toronto’s legacy utility maps, for example, cover 5,260 sheets at a 1:200 scale in the MTM NAD 27 system, drawn from as-built and survey data. Even a well-organized collection like that needs conversion before it fits with modern mapping.

Accuracy That Can’t Be Taken for Granted

What was drawn isn’t always what was built. The City of Greater Sudbury’s engineering records page states plainly that it doesn’t guarantee the accuracy of record information and that field verification must be completed. Any conversion project needs to plan for that uncertainty from day one.

Finding, Assessing and Preparing Existing Drawings and Records

Before anything gets scanned, you need to know what exists and what’s worth converting.

Where Records Usually Hide

  • Flat files and plan cabinets in the engineering office
  • Off-site storage boxes
  • Consultant and contractor archives
  • Development and subdivision files
  • Microfiche, older CAD files, and shared network folders

Sorting and Prioritizing

Successful municipal engineering records digitization starts with sorting, not scanning. Go through the collection and group records by asset type, area, and date. Then decide what to tackle first:

  • Start with critical networks: Water and sanitary systems usually come before less urgent records.
  • Prefer as-builts over design drawings: As-builts reflect what was actually installed.
  • Flag duplicates and superseded sheets: So they don’t end up captured twice.
  • Note damaged or faded sheets: They may need special handling or a second source.

Scanning, Georeferencing, and Organizing Documents

Scanning

There’s no single national standard for scan settings, so set your own and write them down. Your data capture standard should spell out the resolution, file format, and color settings for each type of record. That way every sheet scanned this year matches the ones scanned three years from now.

Georeferencing

Georeferencing places each scanned drawing on the map in its correct position. Staff match points on the drawing, like property corners, curb lines, or manholes, to the same points on current aerial imagery or survey data. The scanned sheet then sits under your GIS layers, ready for tracing.

A few practical points:

  • Use the municipality’s official coordinate system for every sheet.
  • Choose control points spread across the whole drawing, not clustered in one corner.
  • Record how well each sheet fits, since older drawings may never line up perfectly.

Naming and Indexing

Give every scan a consistent file name and link it to a simple index showing the street, asset type, drawing date, and contract number. This index is what makes a converted set of engineering drawings to GIS actually searchable later, rather than just a folder of thousands of images.

Capturing Infrastructure Features and Attribute Data

With the drawings in place, the real GIS infrastructure data capture begins. Staff trace each asset from the georeferenced drawing into the GIS, creating a digital feature for every pipe and fitting.

What Gets Captured

  • Lines: Watermains, sanitary sewers, storm sewers, service connections.
  • Points: Valves, hydrants, manholes, catch basins, fittings.

Details Worth Recording

Every feature needs useful information attached. A typical set looks like this:

Attribute Example
Asset ID WM-1045
Material PVC, cast iron, concrete
Diameter 200 mm
Install date 1978
Contract number C-78-12
Source drawing Scanned sheet reference
Location source Georeferenced drawing or field survey

Recording Where Each Feature Came From

The last two rows matter more than they look. Linking each feature back to its source drawing lets anyone check the original with one click. Noting whether its location came from a drawing or a field survey tells future users how much to trust it.

Building a GIS-Based Database for Pipes and Related Assets

Choosing a Data Model

A data model sets the structure for how pipes, fittings, and their details are stored and connected. There’s no need to design one from scratch. Esri, for instance, moved its water, wastewater, and stormwater datasets out of its general local government model in 2017 and now offers dedicated Utility Network Foundation models for these networks at no additional cost to ArcGIS users.

Connecting the Network

Pipes and fittings should connect properly, so the GIS understands that a valve sits on a main and a main flows into a manhole. Good connections let staff trace a network, find which valves isolate a break, and spot gaps where records are missing.

From Converted Drawings to a Working Inventory

Once the network is built, the converted data becomes a GIS-based infrastructure inventory that staff can query, map, and report from. Each pipe carries its details and a link back to its source drawing.

That inventory then feeds wider work like condition tracking and capital planning. Our guide to building a municipal asset inventory covers how this data fits into a complete record of everything a community owns.

Checking Quality and Keeping Records Current

Quality Checks Before Anyone Relies on the Data

  • Confirm every pipe connects at both ends.
  • Check for missing diameters, materials, or install dates.
  • Compare a sample of features against the original drawings.
  • Field-verify high-risk areas, such as major trunk mains.
  • Fix duplicates and overlapping features.

Keeping these records reliable also requires consistent processes for updating and validating asset information. Our guide to municipal asset data management explains how municipalities can maintain accurate, usable asset records.

Stopping the Backlog from Growing Back

Converting old drawings only solves half the problem. New subdivisions and capital projects keep producing more drawings every year, and if those arrive as paper or loose PDFs, the backlog simply rebuilds itself.

Requiring digital submissions closes that gap. The Region of Peel, City of Brampton, Town of Caledon, and City of Mississauga share one digital submissions manual that requires source CAD files, so GIS staff can bring new infrastructure into their systems quickly. The City of Waterloo goes further on timing, asking for as-recorded drawings within three months of construction.

Setting rules like these keeps engineering drawings to GIS conversion from becoming a project you have to repeat every decade.

These requirements work best as part of a wider municipal GIS operational plan that defines data standards, responsibilities, and procedures for keeping information current.

Once records are flowing in digitally, the bigger payoff starts. Our article on GIS for municipal asset management shows how this data supports field work, planning, and decision-making.

Lessons from Real Municipal Projects

Canyon Logics has carried out this kind of work for Ontario municipalities, and a few lessons carry over to almost any project.

City of Barrie

Canyon Logics scanned more than 10,000 engineering drawings for the City of Barrie and developed the data capture standards to go with them. The team then positioned each as-built drawing against the City’s aerial imagery and captured pipes, valves, hydrants, and manholes, along with details such as install date, diameter, type, and contract number. The result became the foundation for a GIS-based piped infrastructure database covering water, wastewater, and drainage.

City of Greater Sudbury

For Greater Sudbury, the work focused on survey and engineering records. More than 30,000 documents were scanned and placed in a web-based search and viewing application. The City reduced its storage needs and costs, gave staff across the organization easier access to records, and gained a secure backup of drawings that previously existed in only one place. This kind of records work is now part of the ongoing municipal asset management services Canyon Logics provides, rather than a one-off scanning job.

What These Projects Have in Common

  • Standards were set before scanning started, not after.
  • Each digital feature kept a link back to its source drawing.
  • The work was phased, so value showed up early.
  • The end goal was usable data, not just scanned images.

That last point is the one most often missed. A folder of scans is a better filing cabinet. Turning engineering drawings to GIS features is what makes the information truly useful.

Getting Started

Ready to Organize Your Municipality’s Engineering Records?

You don’t need to convert every drawing at once. Start with one critical network or one part of town, set your standards, and build from there. Each phase makes the next one faster.

If your municipality is sitting on years of paper records and disconnected files, discuss digitizing and organizing your municipality’s engineering records with Canyon Logics.