I spent two weeks trying to make InfraWorks do something it does not want to do: run unattended. The goal was a repeatable corridor model for a rail extension study, rebuilt from a config file every time the alignment moved. What I learned was more useful than the script I ended up with.
What Model Builder Gives You for Free
Model Builder is the closest thing to an API in the normal workflow. You hand it a name, a coordinate system and a bounding area, and it pulls terrain, roads, buildings and water from open sources into a cloud model. For the rail study I scripted the request side in Python: build the payload, post it, poll until the model exists, then download. That part is boring and reliable, which is what you want.
The Model Is a Database, Not a File
InfraWorks models live in the cloud and sync down. Your automation is really a sync problem wearing a modeling hat. Two of my first three failures were not code errors at all. They were a machine holding a stale local copy and pushing it over a newer one. Treat the cloud model as the source of truth and the local copy as a cache with an expiry, or you will lose an afternoon to a conflict that looks like corruption.
IMX Is the Real Interface
The exchange format that matters is IMX. It moves content between InfraWorks and Civil 3D, and it is the seam where concept meets design. My pipeline ran like this: build context in InfraWorks, export IMX, open in Civil 3D, swap the concept alignment for the surveyed one, export back. The round trip works with caveats. Styles do not survive cleanly, and anything modeled with components rather than native objects tends to return as dumb geometry, which means no editable parameters on the other side.
Where the Script Ends and the Human Starts
There is no supported way to drive bridge design or traffic simulation from a script. I looked, and I asked. The traffic simulation needs a cleaned network, and cleaning a network is a series of judgment calls about how a real intersection behaves. That is not something I want an automated step guessing at. Sight distance is similar: the check is automated, the decision about whether a crest is acceptable is not.
GenAnywhere in the Same Pipeline
GenAnywhere has no pipeline to speak of. Draw a box, get a mesh. For the rail study I used it once, to generate a quick valley backdrop for a presentation slide while the InfraWorks model was still ugly. Export options are limited, the geometry is a surface, and there is no way to query it for lane widths or vertical clearance. As a source of plausible 3D background it is fast and cheap. As a data source it is not one, and I stopped trying to make it into one.
What I Actually Shipped
The deliverable was a Python wrapper around three things: the Model Builder request, an IMX export, and a Civil 3D batch that regenerated plan and profile sheets. The wrapper logs every step to a JSON file so the next person can trace which config produced which output. A full corridor run takes about forty minutes, most of it spent waiting on the cloud and pretending to read logs.
One piece I did automate was validation. A short script reads the exported model and checks that every alignment has a matching profile, that stationing increases, and that no structure pokes outside the clearance envelope we set. It caught a bridge deck that had drifted about a foot low after a profile edit. That kind of check pays for itself because it enforces a rule instead of making a decision.
Advice If You Try This
Version the config file, not only the script. Pin the coordinate system explicitly, because the default is not what you expect on a corridor that crosses a state plane boundary. Check the cloud model's modified time before syncing. And keep a manual path for anything that touches design decisions, because the moment your automation quietly changes a bridge length, you have a much worse problem than a slow build.
InfraWorks rewards automation around the model and punishes automation inside it. Once I stopped trying to script the design and started scripting the handoffs, the whole thing settled down and my weekends came back.
Top comments (0)