A permit-set PDF, a native CAD set, a landscape drawing, a revision series and a hand-drawn
sheet each need a different route. Four share the last two steps: build it, then check it by re-opening it.
The fifth stops earlier, on purpose.
The thing that decides the routeWhy five and not one
Four of these drawings were plotted from CAD: what looks
like a picture is still stored underneath as lines, text and dimensions, so nothing has to be recognised by eye.
That is why those routes differ in where they read from rather than in how hard they look.
The fifth has no CAD underneath at all — a scan of a hand drawing, the one case where the pipeline must
work from colour and shape, and the one whose honest output stops at massing.
The drawing is a PDF, but it was plotted from CAD — so every line and every dimension is still stored as data, not as pixels. Nothing has to be recognised by eye.
These are the architect’s own working files. The structure the architect put in — layer names, block names, level datums — is worth more than anything that could be inferred from the picture.
A landscape drawing has no walls. The subject is ground: paving, planting beds, water and grade — so the model is made of surfaces and plants instead of rooms.
Read from the drawingWorked outBuiltChecked
Pipeline D · Landscape · revisionsRevision series → versioned models
Design is not one drawing, it is a sequence. Running the same reader across every revision turns a folder of dated files into a history you can step through.
Read from the drawingWorked outBuiltChecked
Pipeline E · Riverside DriveHand drawing → site massing
A scan has no entities to read, only pixels — so this route reads COLOUR instead of geometry, and it stops at massing. It is the only pipeline here whose honest output is less than a building model, and saying where it stops is the point of it.