-
Notifications
You must be signed in to change notification settings - Fork 607
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Two IFC 2x3 files do not match #1281
Comments
I am not totally clear on what's wrong with this - the files themselves or something in the process of storing, retrieving and finally displaying the two projects together. They differ in various ways with regard to how elements are positioned, for example one has length measures in millimeters, the other in meters. Also one has WGS 84 coordinates, the other one has not. Given the different length units, the placement coordinates seem to be roughly in the same range. |
These files are created in two different programs. The bridge was made in Autodesj Revit, and the road in Topomatic Robur. And in the programs for viewing the IFC, the road and the bridge are joined. I tried the variant and IFC v2x3 and v4. Does Bim Server look at geographic coordinates? It doesn't place objects X Y Z? |
As I said, at the moment I can't tell from the top of my head whether the reason is in the file itself (or the export from authoring software accordingly) or in the downstream IFC processing chain leading to the wrong display (BIMserver, BIMvie.ws, IfcOpenShell ...). I just did a quick analysis and listed a couple of differences that appear as potential sources for the issue. |
Two IFC 2x3 files do not match.
In other programs (Autodesk NavisWorks and BIMVision) - the same.
bimserverjar-1.5.182
Google Chrome 98.0.4758.102
Small project
If you turn on the visibility of both elements, only one will be visible. The second element will be in a different location.
In BIMVision they are close by
I post 2 files with examples
Is this a bug in the program or am I doing something wrong?
DTP.zip
PartOfBrigde.zip
The text was updated successfully, but these errors were encountered: