Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
Being able to export to IFC with e.g. the Survey Point as Origin is great. Others can link that into their software, do what they need to do and export with the same point as Origin. Only to find out that Linking IFC puts the IFC-Origin on the Internal Origin. No way to Link IFC-Origin to Survey Point, Project Base Point or something actually useful.
I guess they still need to see the full workflow circle to realize that link/import en export go hand in hand.
@fabiosato If youopen the IFC file to create a RVT file, then link this RVT file and acquire its coordinates, then how do you ensure that the coordinates you acquired are correct. The point, if we don't know how and from which tool this .ifc file has been generated, then how would you ensure that the coordinates would be correct. The tool from which this .ifc is generated may not be Revit
Are there any workflows proposed by autodesk regarding this topic?
I have a similar problem with IFCs created in Tekla. They are supposed to be compatible to be visible in the ACC Model Coordination module, but the location problem makes them unusable.
I had to resource to use @fabiosato's 7 year old solution. Any chance to get this sorted before I go into retirement?
