Linking IFC/RVT files into projects with Project North differing from True North
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
I am trying to understand whether it is a question of Revit logic, ie "what revit wants you to do" and in that case, that I have misunderstood the Revit logic, or if it is in fact a bug.
Site.RVT - this is the site model, with Project Base Point on its right position (not at 0,0,0). The site model has also a project north, oriented nicely to the building's orientation.
Model.RVT - this is a model where True and Project north are pointing the same way - perpendicular to the building, ie not how the building is actually rotated in the real world.
Model.IFC - this is a model I received from an external part. This model is oriented correctly to real world.
When I link the IFC file to site.rvt that has a project north defined (different from true north), I am counting that the model will be oriented to true north. I am assuming that Revit will prioritise True North before Project North.
What is happening though, is that the model is oriented as if Project North is True, and hence, in true north, it has an offset rotation.
I could, but I don't want to manually rotate it to its correct rotation around Project Base Point as rotation axis.
Instead, the solution I have is to reset Project North (so it matches True North), do the linking, and once I am done, I recreate Project North.
In my opinion, this method cumbersome, not to mention that it actually causes some troubles for me (things disappear in the project).
When I import a RVT-file, I can understand that the same behaviour would occur, because True and Project North are the same and whether Revit favours True or Project north, the result would be the same. To prevent this, I need a Shared Coordinate System, this I understand.
But why is this happening when I link IFC files where the models are oriented correctly to the real world.
Does Revit favour Project North before True North?