-
Notifications
You must be signed in to change notification settings - Fork 15
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
Documentation? #10
Comments
This has been applied mostly in building code compliance checking and analysis where you want configurable and robust procedural definition of geometric rules (no floating point rounding, no tolerances). We've used it for segmentation of interior/exterior, evacuation analysis, clearance checks, etc. The main use is typically writing the procedures and have I don't think there will be an effort soon to publish docs. But I can answer specific questions. All contributions welcome also :) |
Thanks for the reply Thomas! |
Good example is the 2nd link in the post above: Using IFC element types and geometric operations to form volumes of where users can walk, obstructions and calculate height of free passage. That's the configurable bit. For the robustness it helps to understand that floating point operations are inherently difficult, you need carefully constructed algorithms to deal with rounding errors and imprecision. IFC uses various local coordinate systems which also causes small precision errors. Solving this in the geometry library is error prone, fuzziness and tolerance of algorithms only work up to a certain extent. Voxels only deal with integer math: simpler and robust (at the expense of some well-understood initial discretization/approximation step). |
Hello,
The title of the repository sounds very interesting, but unfortunately I'm not able to deduct from the README.md how exactly voxelization of IFC models works and how to apply it.
Where can I find the documentation?
The text was updated successfully, but these errors were encountered: