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

IfcAlignmentVerticalSegment - Gradient is an IfcLengthMeasure? #92

Closed
pjanck opened this issue Jan 16, 2021 · 9 comments
Closed

IfcAlignmentVerticalSegment - Gradient is an IfcLengthMeasure? #92

pjanck opened this issue Jan 16, 2021 · 9 comments
Assignees
Labels
documentation Improvements or additions to documentation infra depl Infrastructure Extensions Deployment content

Comments

@pjanck
Copy link

pjanck commented Jan 16, 2021

I must have missed a discussion somewhere. What is the rationale that the IfcAlignmentVerticalSegment.Gradients are expressed as IfcLengthMeasure?

EDIT: markdown syntax

@pjanck pjanck added documentation Improvements or additions to documentation infra depl Infrastructure Extensions Deployment content labels Jan 16, 2021
@SergejMuhic
Copy link

SergejMuhic commented Jan 17, 2021

Should be IfcRatioMeasure, shouldn't it? It is a relic from RadiusOfCurvature.

@pjanck
Copy link
Author

pjanck commented Jan 18, 2021

Well, yes. I think. Looking at the changes from IFC4x3_RC1, it was an IfcRatioMeasure:

grafik

@SergejMuhic
Copy link

Thanks, will correct.

@TLiebich
Copy link

Hi all - I had reported this issue before (I checked, it was in the IFC Rail Sandbox). So obviously, there are different places to report IFC4.3 RC2 issues - lets agree on ONE place to offically log requests to schema and documentation changes.

How about here?
https://github.com/buildingSMART/IFC4.3.x-development/issues

@TLiebich
Copy link

and don't forget to also change EndGradient

@SergejMuhic
Copy link

and don't forget to also change EndGradient

This is done. Thanks for thinking about it.

@SergejMuhic
Copy link

Hi all - I had reported this issue before (I checked, it was in the IFC Rail Sandbox). So obviously, there are different places to report IFC4.3 RC2 issues - lets agree on ONE place to offically log requests to schema and documentation changes.

How about here?
https://github.com/buildingSMART/IFC4.3.x-development/issues

Would be good but I would prefer here: https://github.com/buildingSMART/IFC/issues as it features the entire baseline, not just a part. Also, we will be merging all the changes from alignment into this repo.

@TLiebich
Copy link

I could go for either of the two. Seems we need a policy here @berlotti ?

@SergejMuhic
Copy link

Corrected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation infra depl Infrastructure Extensions Deployment content
Projects
None yet
Development

No branches or pull requests

3 participants