-
Notifications
You must be signed in to change notification settings - Fork 23
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
IFC4 deserializer fails to parse IfcRationalBsplineSurfaceWithKnots #7
Comments
That's probably a bug in the multidimensional array code. I'll have a look at it, thanks for reporting. I still have very little (valid) IFC4 files to test with, can you perhaps help me with more models? |
I am sorry, we can not share IFC4 files from our research project currently. However, we can keep reporting issues as they arise, and provide minimal test files for these issues, such as the one attached. Would that help? IfcRationalBSplineSurfaceWithKnots.ifc.txt (added .txt extension to make Github happy) |
Sure that's even better! Thanks. Kinda busy at the moment so it can take a while before I get back to this. |
I am adding two new sample files for testing. BIMserver fails when representation items are parsed in isolation without representation context. Thus, in the new file, I have embedded the sample IfcRationalBSplineSurfaceWithKnots_IfcShapeRep.ifc.txt The second sample file with |
IFC4 deserializer fails to parse
IfcRationalBsplineSurfaceWithKnots
with error messageError on line xxx: Field not found: ListAsString
. The offending line looks like this and does not seem to be wrong:#15=IFCRATIONALBSPLINESURFACEWITHKNOTS(3,1,((#1,#2),(#3,#4),(#5,#6),(#7, #8),(#9,#10),(#11,#12),(#13,#14)),.RULED_SURF.,.F.,.F.,.U.,(4,1,1,1,4),(2,2),(0.,0.25,0.5,0.749999999999999,1.),(0.,1.),.UNSPECIFIED.,((1.,1.),(1.,1.),(1.,1.),(1.,1.),(1.,1.),(1.,1.),(1.,1.)));
I checked against the attribute types in the Express file, but did not manage to trace this back to the ecore layer. I am using Bimserver version 1.5.81. Here is the stacktrace.
The text was updated successfully, but these errors were encountered: