-
-
Notifications
You must be signed in to change notification settings - Fork 776
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 serialization #71
Conversation
This looks crazily AWESOME Thomas!! No other IFC app will have that feature! Does the serializer absolutely need pythonOCC? it gives me some error here, not sure if it is related or not...
|
Thanks Yorik :) Hope you can put it to good use. Not exactly sure. In principal pythonOCC is not required, but to be honest have not tested without it. The error seems to suggest that somewhere in the C++ code an exception is thrown. Maybe you can provide the entire contents of |
Ok, I'll make a series of test shapes for us to test... I'll also build OCC to see if there's any difference. |
Oho, I wasn't using the right way to obtain shape data from FreeCAD... Got it working now, this is amazing!!! for who is interested to test from FreeCAD, this works with any Part-derived object:
I'll adapt the IFC exporter of FreeCAD to use this, so we can produce some baffling examples :) |
Currently "type" attribute in selector returns something like "#71=IfcWallType('20jY5HfLH4LBwMrDEoTdML',$,'WAL100',$,$,$,$,$,$,.NOTDEFINED.)" when the code was expecting the class name like "IfcSlab" or "IfcWall". Changed it to "class" atribute that returns just class name.
#60
Serialization of arbitrary Open Cascade boundary representation (for example, from STEP data) to IFC. Due to the difference in required semantics, a 1-1 automatic conversion is not possible. The python script below creates the required IFC semantics (project->site->building decomposition) and transfers the STEP shape to IFC.
STEP


IFC
STEP


IFC
Python script