[all] ifc data extraction

[DaJansenGit]

we need a more robust and flexible system for reading parameter from ifc.
Currently we e.g. search for „Muffenlänge“ in propertyset „Abmessungen“. This will fail if ifc export ist done by an other tool.
IFCunits are not used Right now. There coud be problems when parameters are stored in non si units (e.g. [m] and [mm]).

[DaJansenGit]

I think we are limited by the possibilities of export tools (Revit, Tricad...).
For example, in Revit the property set "Dimensions" is always created by Revit (at least in the German version). Until the software developers use the predefined IFC property sets like "Pset_PipeSegmentTypeCommon", we are probably forced to implement a catch method for the different possibilities that can occur.

Edit: We can check which software was used for export because its listed in the ifc file. That makes it a bit easier

By David Jansen on 2019-02-22T08:26:08 (imported from GitLab project)

[DaJansenGit]

I added a finder system which handles properties not stored in default propertiesets. For now it's a dict like approach. E.g. 'Autodesk Revit 2019 (DEU)' stores 'length' for 'IfcPipeSegment' in Pset 'Abmessungen' 'Länge'.

The dicts are saved to file system as *.json. That way tool dependencies are seperated from source Code.

Performance needs to be optimized.

By Christian on 2019-05-08T13:37:41 (imported from GitLab project)

[DaJansenGit]

created merge request !10 to address this issue

By Christian on 2019-05-09T14:57:21 (imported from GitLab project)

[DaJansenGit]

closed via merge request !11

By Christian on 2019-05-16T09:23:11 (imported from GitLab project)

[DaJansenGit]

mentioned in commit 5598395e03a11f7410c93815cd7e8e73bf2087f6

By Christian on 2019-05-16T09:23:12 (imported from GitLab project)