Learn to manage BIM workflows and create professional Archicad templates with the BIM Manager Program.
yesterday
- last edited
yesterday
by
Laszlo Nagy
Hi,
I am having issues exporting an IFC file that can correctly overlap with another IFC file (made in Revit) on a 3rd party platform (Trimble Connect).
Basically, my model is offset on the Z axis by the value of the altitude (rougly 300m).
I have tried:
- Resetting the altitude to 0 in Archicad
- defining the survey elevation to 0 and, afterwards, the correct sea level height
- trying to input the sea level height into the georeferencing parameter for ifc
- messing around with the IFC translator with all 3 variants for geometry conversion (Project origin only, survey only, both)
- read the IFC reference guide from the Learn portal.
I have still made 0 progress, the file still appears "under" the revit generated ones by the exact value of the sea level elevation..
And unfortunately, I am the only one using Archicad so asking everybody else to accomodate for my needs is not really on the table (altough I have asked a collaborator to export differently (without the sea level value - Project Base Point in Revit) and it overlapped perfectly instantly with my model.
Visual representation of my issues:
Any ideas?
Operating system used: Windows
Solved! Go to Solution.
yesterday
- last edited
yesterday
by
Laszlo Nagy
Hi @CosminF
Anyway (this is not an Archicad solution), as far as I know I think it is possible to adjust the IFC model location in Trimble Connect.
yesterday - last edited yesterday
Hi @CosminF
Try setting up the Z elevation value for your Archicad Survey Point to -300m.
yesterday
- last edited
yesterday
by
Laszlo Nagy
Hi Ricardo,
Thank you for the reply!
Unfortunately, that also did not work..
Survey screenshots:
and the Trimble connect overlap has the same issue:
yesterday
- last edited
yesterday
by
Laszlo Nagy
Hi @CosminF
Anyway (this is not an Archicad solution), as far as I know I think it is possible to adjust the IFC model location in Trimble Connect.
yesterday
That is actually a great workaround - at least for my purposes currently!
Thank you!