

I don't want to suggest that we aren't going to pursue the long term goals of interoperability, but what is often easier to do is to supply features in Chief that solve specific problems. And where we can step up to good interoperability, such as exporting and importing to/from. I think talking about these things is important. We handle this currently by allowing you to import 3D models from other software. The only current solution is simple 3D meshes of triangles with texture mapping which then becomes very difficult to edit. Parametric models would be poor, maybe good enough to count windows, or doors, but not good enough to provide highly detailed 3D views that look good. Some things in the IFC standard are not supported internally by Chief, which while we could support, may not make sense to do.Įventually, if you take the BIM/Interoperability idea to it's ultimate conclusion you end up with vanilla software that can only do only extremely basic things requiring a lot of fix up work at the end to get things the way you want. While we could dumb down what we export, the importing of the data after modification in another application would have lost many of the things that we support. The IFC standard suffers in that it cannot accurately represent the very rich Chief parametric models of things like windows, doors, and walls. Which means the goal of clean data exchange will not be achieved except for extremely basic things, such as lines and 3D triangles with simple texture mapping. So some data loss is expected today and for the foreseeable future. I use this as an example because no matter how complete an export or import format is, there is always something that the format doesn't handle either on the exporting application side or the importing application side.

For example notepad on Windows is brain dead when it comes to dealing with text files from other platforms. And while this is easy to convert, it isn't always done by every application. This results in confusion when exchanging text data between platforms. On Windows a line ending is created by inserting both Carriage Return and Line Feed characters while everyone else uses just a line feed. In practice clean data exchange is difficult.Ī good example is moving a pure ascii text file between Windows and any other operating system.
