-
Notifications
You must be signed in to change notification settings - Fork 32
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
No Qto related to IfcUndergroundExcavation #38
Comments
We are in the middle of the work with Pset and Qto definitions for Geotech, Systems and Excavation/Support. In IFC Tunnel, we added the abstract entity IfcExcavation with IfcEarthworksCut and IfcUndergroundExcavation as subtypes. The quantities in Pset_EarthworksCutBaseQuantities are certainly applicable for all types of excavations which means that we basically need a new Qto_ExcavationBaseQuantities (deprecating Qto_EarthworksCutBaseQuantities). Alternative would be adding a Qto_UndergroundExcavationBase with essentially the same quantities. |
What do you mean exactly by the flag 'wontfix'? The standard will never propose a Qto for IfcUndergroundExcavation? |
I think that this flag is a bit misleading. Of course there will be a Qto. |
The flag only means, that currently we won't fix it. It remains open and on our ToDo list - we will remove the flag as we will tackle it. |
Renamed to backlog to better convey our intentions. |
Since you 'are in the middle of the work', shall I wait to raise similar issues on other entities or shall I raise one issue per entity right now? |
I would prefer that you register issues for the backlog so nothing is forgotten. Thank you in advance for any contributions! |
You are posting in a wrong repo. Here we are just testing with software vendors to deploy the standard and gathering their feedback. Issues regarding the standard are posted here: |
Of course! Thanks @SergejMuhic |
Shall we consider that Qto_EarthworksCutBaseQuantities applies to this entity, in addition to IfcEarthworksCut?
The text was updated successfully, but these errors were encountered: