![]() I hope you will find all this of use, it's something that has plagued me over the last few years. There is also a record sheet for each discipline that keeps a history of all recorded data should the comparison be required. Lastly, it will record the document revisions, the summary sheet will show the revisions to that tab and also the document revision - the user who ran the script is also recorded along with the data on the Revision tracker tab. Again this is useful as a check to make sure models are aligned correctly. The script also records the elevation, both project and survey, for any levels defined as building stor(e)y. ![]() Then close and export your IFC using this basepoint, all being well it will align perfectly. When you run the script you will be faced with the Data-Shapes input form shown below. Just to be clear, this is not Revit's Project Base Point (PBP), that is something different which can be easily adjusted, the internal origin can not. ![]() This will mean if each discipline's model has a different internal origin point then they will need a separate export from Tekla to get automatic alignment. If you are linking IFC's into Revit it uses the internal origin point to locate them. Everything in the script exports to an Excel spreadsheet which is also linked at the bottom of this article.īefore getting into the detail of this I'd just like to point something out. I'm not going to get into what happens in the graph itself, just the inputs and what they do. The script itself automates the process of gathering the necessary numbers to get the correct basepoint translations for correct alignment in both Revit and in other IFC viewers such as Dalux. That article defines the principles that are used within the Dynamo Script discussed below. Back in 2018, I wrote an article about how to get an IFC out of Tekla that would coordinate correctly with Revit that you can find here: Coordinating between Revit and Tekla using IFC.
0 Comments
Leave a Reply. |