Announcement

Collapse
No announcement yet.

IFC back-save irregularities

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    IFC back-save irregularities

    So some of you may know we "can" backsave Revit, in a way, by exporting the .rvt to and .ifc - I've just done as much to get some 2014 content I developed back to 2013, but just noted something quite peculier...

    The IFC appears to read retained (?) information of certain elements, (families in particular) that aren't "present" in the original .rvt.

    Example; titlesheet family (in Revit) : "A_XXX_ANO_SHEET_A1L.rfa" is renamed "A_KP_ANO_SHEET_A1L.rfa" = which was the original name of the file when I first developed it. It had, since then, been renamed in (& saved out from) the Revit file - but somehow IFC "finds" that original name?!

    Now I'll confess to having a minimal grasp on the concepts of IFC translations, (IFC as a whole to be honest) - but find this quite peculier.

    In fact, oddly, looking through the .ifc (in 2013) more and more, the file (browser/naming structure, not the elements) looks very little like the (.rvt) file, at least in it's present state, nd very much like it's "starting" state (my template that is, with the "A_KP_" prefixes rather than the "A_XXX_")

    Has anyone else seen this? Or able to recreate/confirm this?

    #2
    Does this mean that Revit retains a history of the information in each file and the IFC translation is reading this history? Maybe it's an issue with IFC and the "rename" function. I'll set something up later on to try and replicate this.

    Edit : I'm currently working through an IFC experiment with someone that uses ArchiCAD, so I'll let you know of any results that come from that also.
    Last edited by Cyus; July 25, 2013, 11:45 AM.
    "I WANT SOUP! This fork is useless! I'm going to use my spoon for everything."

    Comment


      #3
      Which exporter did you use?
      Also note that the IFC schema is different from the Revit one, so differences are to be expected.

      Comment


        #4
        Originally posted by DanielHurtubise View Post
        Which exporter did you use?
        I only did a quick couple of tests this morning over "breakfast" before work, with the 2x2 and 2x3 types.

        But
        Originally posted by DanielHurtubise View Post
        Also note that the IFC schema is different from the Revit one, so differences are to be expected.
        It's not the .rvt-to-.ifc convert differences I'm seeing here, it's the fact the .ifc somehow pulls out from the depths of ancient legacy information that was once there, but is not anymore - or at least, information that is different.

        Comment


          #5
          So you used the one provided with Revit right?
          Try that one IFC Exporter for Revit | Free software downloads at SourceForge.net

          Comment


            #6
            Originally posted by DanielHurtubise View Post
            So you used the one provided with Revit right?
            I don't think you're following me, or the thread, Daniel.

            Comment


              #7
              I am, hence the reason i said try this other exporter to see if it carries the "legacy" information

              Comment

              Related Topics

              Collapse

              Working...
              X