Dion Moult
Dion Moult
Yes that makes sense. To a small degree specifying the predefined type (which is inherited) may help. Thanks for clarifying :)
@TLiebich yes but in IFC the rule is that the predefined type is "inherited" from the type.
I'm fine with either solution. I have a small personal bias to encourage people to upgrade to IFC4. IFC2X3 is ancient. Get a move on, or this will hurt IFC...
In addition it was noted that the "Point Type" should be identifiable, for example is it a Control Point? Is it a Traverse Point? Is it a Monument? Etc. These...
I was under the impression that the schema version was purely as a comment but didn't actually have any impact on the running of the IDS.
https://github.com/buildingSMART/IDS/blob/master/Documentation/testcases-ids.md#pass-specification-version-is-purely-metadata-and-does-not-impact-pass-or-fail-result ^ I can't remember who I asked or who told me that this should be the case, I merely documented it.
@IronBob01 at a guess, can you make sure that the rhino3dm module is available to Blender's Python (which may be different to your system Python)?
How does the test case contradict this?
> My reading is the test cases treat Prohibited specifications as a logical NOT of Required specifications. @andyward agreed. > Prohibited, would mean that no elements should be matched, regardless...
Considering the relative rarity of mesh programs supporting inner loops (perhaps sketchup is one), I propose: `IfcPolygonalFaceSet` and `IfcPolygonlFaceSetWithVoids`. The former is as I have proposed, the latter could be...