In relation to the original query of this post, I just pushed a commit to the dev branch of the exporter that improves the setting of the GlobalId to elements that are copied from an element with the GlobalId previously set.
I added a command and form in ggRevitIFC to permit nomination or replacement of the builtin parameter values at any time if anyone wants to test and provide feedback. www.geometrygym.com https://twitter.com/geometrygym/status/1076953794204712963?s=21
I added a command and form in ggRevitIFC to permit nomination or replacement of the builtin parameter values at any time if anyone wants to tedt and provide feedback. www.geometrygym.com https://twitter.com/geometrygym/status/1076953794204712963?s=21
Hi Dirk, Branches for different versions is one of the big reasons why I was advocating for the switch from Source Forge and github. I just created a Revit2018 branch, you should be able to work in that branch if you prefer and we can still merge changes into the master (2019) branch. https://github.com/Autodesk/revit-ifc/tree/Revit2018 Post if you have problems with this. Cheers, Jon
Hi Einar, I've been helping Angel and his team with some improvements to the IFC exporter to Revit, and I was the one who primarily developed the changes we're seeing. Exporting with the shared coordinates as the basis should generate the same model as before these changes, when project north/true north rotation was including on the element. If you can clarify a bit further what you think is not correct with the resulting files, we can consider if the implementation needs adjustment. Cheers, Jon
Hi Einar, Thanks for posting. Here's some more information about how project north is defined on an element in the two options. See if it makes sense or you disagree. When you nominate internal or project base point as the basis of the element transforms, the true north direction and origin placement are defined on the representation context. If the shared coordinates are nominated, then this data is included explicitly on the element transformations. I've attached some files to demonstrate this....
Where are you importing the resulting file into? If it's desktop software, then I support quite a few popular options. I've been using IFC files for about 8 years now, I've never seen the domain not be the full extent of the curve, so if you were comfortable with it you could defer the trimming for a later date if it is a lot of work.
I did prepare some sample/test files for Building Smart on parameterization (https://github.com/BuildingSMART/IfcScript/blob/master/Examples/CurveParametersDegrees.ifc). Polylines are 0 to n for n segments (so 0 to 1 for single segment) but if an IfcLine is the basis then it is based on length.