Skip to content
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

Open
FLR3DS opened this issue Feb 7, 2023 · 9 comments
Open

No Qto related to IfcUndergroundExcavation #38

FLR3DS opened this issue Feb 7, 2023 · 9 comments
Assignees
Labels
backlog This will not be worked on currently documentation Improvements or additions to documentation

Comments

@FLR3DS
Copy link

FLR3DS commented Feb 7, 2023

Shall we consider that Qto_EarthworksCutBaseQuantities applies to this entity, in addition to IfcEarthworksCut?

@pjanck pjanck added the documentation Improvements or additions to documentation label Feb 8, 2023
@larswik
Copy link
Collaborator

larswik commented Feb 8, 2023

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.

@pjanck pjanck added the backlog This will not be worked on currently label Feb 9, 2023
@FLR3DS
Copy link
Author

FLR3DS commented Feb 13, 2023

What do you mean exactly by the flag 'wontfix'? The standard will never propose a Qto for IfcUndergroundExcavation?

@larswik
Copy link
Collaborator

larswik commented Feb 13, 2023

I think that this flag is a bit misleading. Of course there will be a Qto.

@pjanck
Copy link
Member

pjanck commented Feb 14, 2023

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.

@pjanck
Copy link
Member

pjanck commented Feb 14, 2023

Renamed to backlog to better convey our intentions.

@FLR3DS
Copy link
Author

FLR3DS commented Feb 14, 2023

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?

@larswik
Copy link
Collaborator

larswik commented Feb 14, 2023

I would prefer that you register issues for the backlog so nothing is forgotten. Thank you in advance for any contributions!

@SergejMuhic
Copy link
Collaborator

SergejMuhic commented Feb 14, 2023

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:
https://github.com/bSI-InfraRoom/IFC-Specification

@larswik
Copy link
Collaborator

larswik commented Feb 14, 2023

You are posting in a wrong repo. Here we are just testing with software vendors to deploy the standard. Issues regarding the standard are posted here: https://github.com/bSI-InfraRoom/IFC-Specification

Of course! Thanks @SergejMuhic

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog This will not be worked on currently documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

4 participants