# A Civil 3D and InfraWorks Pipeline for a Mill Town Reuse Plan > Source: > Published: 2026-10-26 05:37:31+00:00 A planning-level site package for a 310-acre paper mill property, assembled from a town survey DGN, an exported terrain mesh, Civil 3D grading, an InfraWorks scene, and a generated context patch for an unsurveyed parcel. The technical risks were coordinate registration, vertical faces in the terrain, and generative geometry leaking into schedules. Winslow Falls needed existing conditions, a ground surface, a context model, and three housing options for a town meeting. The property includes a 41-acre industrial yard with 18 buildings, a dam and canal, and 96 mill-era houses on the hill. The town supplied a survey DGN plus sixteen spot elevations; the northern 70 acres had no survey. The stack: MicroStation for base mapping, TopoExport for terrain, Civil 3D for surfaces and grading, InfraWorks for context, and GenAnywhere for the unsurveyed area. Nine weeks, one model, five different kinds of truth. The DGN came with boundary and deed lines. I added a 1994 aerial, the mill's plan set, and parcels as references, then traced footprints, canal edges, and the dam crest. Building and water features went onto separate levels, and the coordinate system went into both the file name and a drawing note. Only the master file was edited. Everything else referenced it. This kept the layer tree predictable and made the survey the single authority for boundary questions. TopoExport accepts a drawn boundary and returns the ground inside it. I traced the property, enabled contours and waterways, and received an OBJ mesh with a separate DXF vector file. Two things needed checking before use: • Vertical match: the flat yard checked within eight inches of the survey shots, using two-foot contours. • Vertical faces: the canal wall arrived as a slope, because a TIN cannot store an overhang. I retained the surveyed wall line for design at the water. The export used local coordinates. I registered it to two survey monuments before bringing it into Civil 3D. Civil 3D rebuilt a TIN from the DXF vectors and the sixteen elevations. From there I created two street alignments, profiles, a storm network to the river outfall, and a terrace for housing. The first mass haul came back with a cut surplus above twenty thousand cubic yards. That is a design warning: the terrace was higher than the ground could support without importing fill or building walls. At three feet lower, the cut and fill nearly matched, and the main road left the regulated floodplain. The yield settled at 130 lots. Existing and proposed surfaces used different styles, and the floodplain was labeled on every exhibit. Anyone reviewing a plan sheet could see the change without opening the model. InfraWorks assembled the terrain, mill structures, proposed streets, and tree cover. Its job was the public meeting: park views from the bridge, the relationship between new streets and old houses, and the visual edge between the mill yard and the river. I did not derive any quantity from it. The town engineer received Civil 3D outputs for numbers and InfraWorks imagery for communication, with the distinction stated in the meeting. The northern parcel had no survey or recent aerial. In GenAnywhere I sketched a rectangle on the map; the service synthesized terrain and building massing inside it. The geometry went onto a layer named `ai_context` and was excluded from lot counts, earthwork, and cost. The patch served its purpose in context views and failed in detail. One generated run placed driveways across wet ground. The layer name and a date in the file were the only things preventing that content from being mistaken for survey. • Local origin: the terrain export did not share the town's coordinate system. Fixed by registering to two monuments. • Vertical wall: the TIN could not represent it. Fixed by using the surveyed line near the canal. • Generative leakage: AI buildings looked like real ones in a PDF. Fixed with a dedicated layer and a written exclusion. • Visual authority: a good InfraWorks frame can silence a room. Fixed by stating the tool's role before showing it.