It is kinda more Python than Dynamo but hey, you get the picture ? And it is probably worth backing up your files before running something like this. You can get the supporting nodes from GitHub here:Īs usual, please use with care.
XKCD SIMPLE WRITER DOWNLOAD
You can download the main definition here: In about an hour it fixed the linked file paths of 600 Revit links, all with the click of a single button ? In the future I’ll probably fix it up to be a ‘proper’ Python script but this works for now. I did this in the hacky way of a “counter with List.Map” in Dynamo.
XKCD SIMPLE WRITER HOW TO
Once I figured out how to implement those TransmissionData actions in Python, I just had to build a node that, running from the federated model: This puts the file in an appropriate state for re-opening in the new path environment. But the TransmissionData class is basically what is implemented in eTransmit for Revit – it allows you to ‘lightly touch’ the Revit file and simply change the Revit link paths, and also set a switch saying ‘this file has been transmitted’. You see, I was thinking I would have to set up a batch method to open this files, change the file paths, and close them. What I discovered during this process is that there is a TransmissionData API class that let’s you do some pretty interesting things… I knew that in Dynamo with Python I could get a lot of information about linked files using the ExternalFileReference class.
I set up an ‘approved’ list of Revit file paths, that looked something like this: As you know, people work in many different IT environments, and the pathing of Revit links may vary widely. On one recent project, we had to deliver to a Client a linked dataset, with Revit link file paths resolving correctly. Recently, I have been running quite a few batch operations from the scope of a federated Revit model: so I will have one RVT file, with hundreds of Revit links, and I will process them from that main federated model. People will go on and on about how Revit needs this feature or that feature, but the fact is that you can build almost any feature you like with the API. The Revit API is actually something pretty special. BIM laymans, Simple Writer Tool, understandable No Comments
XKCD SIMPLE WRITER FULL
Check out the full post by author Dan Rossiter at this link. But this is a good reminder that much of our work can actually be described in easy-to-understand language. In BIM world, we can certainly get carried away with terminology and abbreviations and acronyms. To make sure everyone can follow the plan, the builders check their team’s skills before starting the job. Here is just one paragraph:Īfter a builder wins the job, they plan with their team what parts of the job they will do, what information is needed and by when, as well as how information needs to be set out writing all of this into a single agreed plan for everyone to follow. Some of the ideas are somewhat UK centric, but the overall concept is great. According to the author, the XKCD Simple Writer Tool was used to develop the text. A while back on the There’s no BIM like home, there was a very interesting post that aimed to use simple language to describe BIM projects and process.