wsolihin

You can do it by using a feature called parameter expression (https://sourceforge.net/p/ifcexporter/wiki/Notes%20on%20parameter%20expression/). For example: IfcName = {$type("Family Name")+"/"+$ElementId+"/"+$type("Name")}

IfcName should not be dependent of the parameter group. We don't actually check the parameter group of the IFC related parameters. Have you assign any value to IfcName? The default value for the name is <family name="">:<type name="">:<id> will be assigned when there is no value specified in IfcName, or the IfcName parameter does not exist</id></type></family>

I agree. I am not exactly sure what's really strange about this coordinates, but from the data it does not show anything wrong, and also a few other viewers are able to put them correctly (also Revit import). I guess you may want to report the issue to Solibri in this case.

By manually looking into the coordinates and relevant placement references, the file looks perfectly OK (consistent). I suspect, it is the problem with Solibri especially because of the model is located far away from the origin (Shared Coordinates). If you export it using Project Based, or Survey Point, or Internal. Even Solibri shows the correct result (see attached). Therefore, I conclude that the issue is with Solibri. Also I would recommend that the export for such model, which has far away geo-reference...

By manually looking into the coordinates and relevant placement references, the file looks perfectly OK (consistent). I suspect, it is the problem with Solibri especially because of the model is located far away from the origin (Shared Coordinates). If you export it using Project Based, or Survey Point, or Internal. Even Solibri shows the correct result (see attached). Therefore, I conclude that the issue is with Solibri. Also I would recommend that the export for such model, which has far away geo-reference...

I looked at the model and the exported IFC file. The IFC file produced looks OK, but Solibri and a few other viewers have problem with objects that are located near the 0,0,0. This happens only when the export is done using "Shared Coordinates" coordinate base. Some other viewers work fine with the same model (see the attached example). Both Open IFC and Link IFC in Revit for the same model show the correct result.

I looked at the model and the exported IFC file. The IFC file produced looks OK, but Solibri and a few other viewers have problem with objects that are located near the 0,0,0. This happens only when the export is done using "Shared Coordinates" coordinate base. Some other viewers work fine with the same model (see the attached example)

I looked at the model and the exported IFC file. The IFC file produced looks OK, but Solibri and a few other viewers have problem with objects that are located near the 0,0,0. This happens only when the export is done using "Shared Coordinates" coordinate base. Some other viewers work fine with the same model (see the attached example)