-
Notifications
You must be signed in to change notification settings - Fork 174
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
How to add a light source to an IfcLampType #123
Comments
Hi @KonstantinHamm , there is a facility in xBIM to check if the data you have created is valid IFC according to schema constrains and rules. However, specific implementation should be directed by information requirements of the receiving application. Martin |
Hi @martin1cerny, Thank you in advance. Konstantin |
@KonstantinHamm, You can download xbimxplorer from here. Then select in the menu View->Developer windows->IFC Validation Press the "Validate model" button and the validation report is presented in the text as shown above. |
Or in code, in case you needed automated quality check: using (var model = IfcStore.Open(file, null, 0))
{
var v = new IfcValidator
{
ValidateLevel = ValidationFlags.All,
CreateEntityHierarchy = true
};
var errors = v.Validate(model);
foreach (var validationResult in new IfcValidationReporter(errors))
{
Console.WriteLine(validationResult);
}
} |
I was able to find a problem with my IfcLightSourceGoniometric. (XbimXplorer tells me the IfcLightSourceGoniometric does not have a geometric representation). I guess i'll have to find out why :) |
Hi all,
first of all I want to thank you for that awesome piece of software that you are creating. Keep up the good work!
My question is: How do I add a light source like IfcLightSourceGoniometric to an IfcLampType?
I already have the IfcLightDistributionData at hand. Here is the piece that I've tried to implement:
Am I creating and adding the LightSourceGoniometric the right way? Unfortunately I could not find an Ifc-Viewer / Editor that is able to visualize the light distribution curve.
The text was updated successfully, but these errors were encountered: