Skip to main content

IFC-SDK : Open Source IFC 2x3 Library

IFC-SDK
Formerly: http://www.osor.eu/projects/ifc-sdk
Moved in Dec 2011 to https://joinup.ec.europa.eu/software/ifc-sdk/home

This is an Open Source C++ library for reading and writing IFC files. It does not depend on any external libraries and can be compiled on most modern compilers. It was tested on Windows (g++ and VC++ 2003+2005) and on Linux (g++ 3 and 4).
I had no problem compiling it on OSX Snow Leopard, using XCode 3.2.5.

It contains a STEP library and an IFC library, alongside a quite large list of example programs, including tests, to explain the features of the library.

Using CMake it could compile the full library without problems and the example programs seem to work fine. They are all command-line, so no GUI problems, but nothing fancy to see either.


However, there are some caveats...
  • I see very little actual information (project homepage, author and licensing details).
    • however, inside the source code, it is "copyrighted 2009 CSTB" and released under the LGPL 2.1 license, which is Open Source, but with the possibility to link it in a commercial software.
  • Last update was in October 2009, which is a bad sign... as it seems to not be (publicly) maintained. It is numbered 1.0-beta.
  • The library is made for IFC 2x3 which is not the current version of the IFC standard.
  • Most of the included examples focus on the geometric aspects and not the building information
    • ifcRevolvedAreaSolid_app (see above)
    • ifcVector_app
    • ifcShellBasedSurfaceModel_app etc...
So if anybody has more details about it and if a more recent version is available, then please comment.
Labels:

Comments

  1. Mark02 September, 2011

    Regarding IFC-SDK - I emailed the developer in 2009, and found that the source had been generated with one of ESA's tools, lightcpp. It might be possible to get them to do so with lightcpp's replacement, expressik.

    ESA hasn't yet released their tool as open source, though I've been told that they wish to do so.

    ReplyDelete
  2. Laurent Bauer11 October, 2011

    You probably know the SCL (Step class library) developed by the NIST in the early 90's.
    There is an attempt to refresh it. This initiative sounds very interesting. See :
    https://github.com/mpictor/StepClassLibrary#readme
    I've tested the release 0.1 and could generate AP203 and IFC classes. But couldn't find the required SDAI classes... must investigate some more. What do you think about this refreshed SCL ?

    ReplyDelete
  3. stefkeB19 October, 2011

    Hard for me to tell, because I mainly look at IFC files through intermediate libraries or applications and never directly at STEP files.

    But I hope that some common ground between the different STEP and IFC initiatives would help everybody improving their offerings.

    ReplyDelete
  4. Mathieu MARACHE27 January, 2012

    Hi,
    I'm the main developer behind this SDK. The SDK hasn't been much updated since the version of the IFC standard hasn't changed (yet).
    It is using the latest public IFC Specification IFC2x3 TC1 as of this date.
    It is a (central) part of our most active software in my team, so it might feel not very maintained but we don't have any problems with it !

    ReplyDelete
  5. stefkeB30 January, 2012

    Recompiled revision 11 (current trunk) in OSX Lion, with latest Apple developer tools and all works fine, apart from some compilation warnings about "comparison is always true due to a limited range of data type" in the init() function. I guess that the repeated warning is just a single issue and nothing to worry about too much.

    ReplyDelete

Post a Comment

Popular posts from this blog

Improve usage of BIM during early design phases

When I was collecting ideas for a book chapter on BIM (that seemed to never have emerged after that), I collected 10 ideas, which I believe still reflect good recommendations to improve the usage of BIM during the early design phases. These ideas are related to BIM software, but you can apply them in any flavor, as long as you can model with Building Elements, Spaces and have control over representation. Introduction This article gives an overview of several recommendations and tips, to better apply BIM applications and BIM methodologies, in the context of the early design phases. Many of these tips are applicable in any BIM application and they are based on experience gathered from teaching, researching and using BIM software. Sometimes they could help software developers to improve the workflow of their particular BIM implementation. Tip 1 : Gradually increase the amount of information In the early design phases, the architect makes assumptions and lays out the main design in...
2 comments
Read more

Getting BIM data into Unity (Part 0 - Introduction)

This post reflects on work that I carried out, elaborated during my guidance of a few Master thesis students, to better integrate BIM models into Unity. This will be a multi-part post. This makes each article a bit shorter to read, but allows more in-depth information overall. Hope you like it. Please comment with feedback and further improvements. Basic methodology Unity can import geometry from FBX and Collada (DAE) files primarily. There are a few other formats, but these are the preferred ones. When integrating CAD or BIM files into a realtime environment, you have to convert the geometry. During my Unity teaching and the writing of the book Unity for Architectural Visualization ( buy from Packt ), I’ve come up with a basic diagram explaining geometry exchange between CAD and BIM software and Unity. Throughout these posts, we’ll go more into detail. We start with ArchiCAD, but will tackle Revit in a follow-up post. Promised!
Post a Comment
Read more

PythonOCC : Open Source interactive CAD shell (and how to run it on OSX)

What is PythonOCC? PythonOCC is an Open Source (LGPL) Python-wrapper for OpenCASCADE. So what is OpenCASCADE (OCC)? This is an advanced Open Source (custom license) modeling kernel, comparable to commercial engines, such as ACIS or Parasolid, which are used in quite some commercial CAD programs. When you want to develop CAD software, you could use OCC and write programs in C++. And why using Python? With this wrapper, you can create CAD and geometry scripts in Python, which is an interpreted Object-oriented scripting language. You can write almost "on-the-fly" and seriously reduce the implementation effort, by skipping the compiling-phase. You can even interact with a running program in the Python interpreter. Want to read more about this? The OpenCASCADE official website  (currently Linux and Windows are officially supported) The PythonOCC website/blog  (beware that the core of the actions happen in the development repositories). So far so good. Now the nasty, techn...
4 comments
Read more