Linking IFC from AECOsim
- Dominant language
- C#
- Stars
- 637
- Forks
- 225
- PR merge metrics
- No merged PRs in 30d
Description
***[Ported unresolved issue over from SourceForge](https://sourceforge.net/p/ifcexporter/discussion/general/thread/fda2b9f1/)***
We are experiencing issues with the positioning of linked IFC models from Bentley AECOsim. This may occur for other software but we have not tested yet. We also note that same issue occurs when using the Revit IFC file reader in Navisworks too (Same code? Who develops this?)
Further informaiton on the issue can be found [here](https://sourceforge.net/p/ifcexporter/discussion/general/thread/fda2b9f1/).
The guys involved in this project have all raised the issue with their Autodesk representatives but nothing has been done. I understand from @AngelVelezSosa that improvements are coming so wanted to make sure we have it captured in the official issue list until that point.
This maybe the same issue as #16 ?
**For others experiencing the same issue, workaround options we have found (although non are ideal!):**
1. Save the AECOsim .dgn file into .dwg and setting the UCS to World before linking in the dwg into Revit for coordination purposes. This has prove to work however not recommended as there might be some elements missing in the model.
2. Manually move the project in AECOsim to offset the difference in location placement occuring in Revit and then export IFC as normal. However please note the IFC exported out from this process can’t be used for coordination in Navisworks, Solibri, etc and can only be used for the purpose of Revit coordination.
3. Use iModel container as the method to share data with Revit, import the iModel into a RVT (or better still RFA) and then share that with interfacing consultants.
Contributor guide
Research direction
Start with the linked SourceForge discussion and compare this report with issue #16; no repository file, test, or reproduction steps are identified here. Reproduce the AECOsim IFC-link positioning problem in Revit and Navisworks, then confirm the affected behavior and add coverage showing that linked models retain the correct position.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100