-
Notifications
You must be signed in to change notification settings - Fork 34
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
Geometry of terrain #29
Comments
Direct representations assigned to IfcSite (1,2,3) are discouraged for quite some time already (but I don't think it actually made it into the spec.....). For non-geotechnic purposes I would recommend 4 or 5, which are mostly equivalent, except that we maybe need to look into some of the usage constraints of TINs. |
I have not very strong opinions about, but this is how we do this in Quadri: And I would say that it would be smart to discuss this with the IFC4.4 schema development team, like Lars Wikstrøm or Sergej e.g., because the expansion of the schema to better defining terrain, geotechnics and geology are important aspects of IFC 4.4 work. |
I think it would be lovely if a terrainmodel is easily identifiable that it is some kind of terrain surface that you might want to use for volume calculations and such. It helps to know that so we can import it to the proper type of object straight away. I think some of the examples for JanErikHoel are really good when you easily can read ground surface but some of the files we have seen this is not easy to know. |
See valid examples of terrain models here |
What is the recommended geometry to export the triangles of a terrain ?
Over the years, I found many IFC with different ways to export terrain :
For IFC 4x3, what recommend the MVD about that ?
The text was updated successfully, but these errors were encountered: