Linked files and IFC export

[F_Rosa]

I don't know much about the IFC schema, so I don't how it handles, say, doors of same types. But, at the moment, Freecad does not export std_links. Instead of manually having to unlink the objects and make them local in the current file, it would be ideal if the IFC exporter could do that in the same manner that the OBJ exporter grabs all links, makes them dumb, and exports them.
...

I fully agree! But it's possible to export linked objects as I exposed in https://forum.freecadweb.org/viewtopic. ... 1&start=10.

[pdpb59]

BIM means establishing communication between the individual specialist planners of a construction project.

The approach to communication can be:
a) Create another design on top of an existing design without changing the existing design.
b) Create another design on top of an existing design and change the existing design for this purpose.
c) Define an existing design as a control standard.
-------

a) Create another design on top of an existing design without changing the existing design.

In a) I can make an exchange between FC and FC or between FC and an ifc file. Let's start with FC-FC
In FreeCAD, this can be done via "BIM : Create an external reference object".

I can connect buildings, floors, components and update subsequent changes.

With the axes it runs uncleanly, sometimes I can connect axes, sometimes not. If I place an axis in a floor, this change is not applied.

For buildings and floors FC takes the subobjects with it.
For site and project, the subobjects are not taken.

The next tests follow ... Peter

[pdpb59]

Let's continue with a). Read an IFC file into FC.

An FC project exported an ifc file.

Project: "could not convert string to float".
Building: it works
But the axes are not entered into the ifc file. But this is also a problem in ifc!
----
Import an ifc file into a new project in FC.
Move the objects in FC, but do not change them.
---
Import an ifc file that comes from REVIT into a new project in FC.
Move the objects in FC, but do not change them. But the structure is unclean.

[pdpb59]

b) Create another design on top of an existing design and change the existing design for this purpose.

I want to change the existing project.

In FC via "merge project". There is no link to the old file. If desired this is ok.

Or in FC via "make link". Here I have problems with the application. In essence because I have to address each object individually.
But here I keep the connection to the old FC-file.

About an IFC import it does not work. Because the objects from IFC cannot be changed in FC (unfortunately).

c) Define an existing planning as control standard.

In FC via "BIM Create external reference object " or ifc import. But these requirements can be better processed via ifc-viewer.

Peter

[paullee]

Thanks for testing. Another issue is the difference in current functionalities and pros and cons between Arch Reference and App::Link. Maybe a roadmap between the two will be more clear for user to understand

[pdpb59]

Maybe a roadmap between the two will be more clear for user to understand

would be nice if I can help somehow ...

Working with "BIM External reference" is good, but cumbersome. I would have three ideas:
a) you could sort the list alphabetically.
b) you could include an input for the search in the selection field and
c) you could allow multiple selection of objects.
Peter