Revit Architecture Forum
Welcome to Autodesk’s Revit Architecture Forums. Share your knowledge, ask questions, and explore popular Revit Architecture topics.
abbrechen
Suchergebnisse werden angezeigt für 
Anzeigen  nur  | Stattdessen suchen nach 
Meintest du: 

Textfile IFC Export Classes issues

3 ANTWORTEN 3
Antworten
Nachricht 1 von 4
Joris.vd.Meulen
1861 Aufrufe, 3 Antworten

Textfile IFC Export Classes issues

Hi guys,

 

Can anybody explain how the text file of IFC Export Classes works? This because I noticed that it changes a lot. And most times not for the better.

 

So I'm using IFC exporter (latest version, sourceforge). When exporting I notice that objects aren't exported while they should and more important they DID export before. Nowadays I start checking this text file.

 

So

- this txt file is changed all the time (ours is office wide used, and on network location)

- new subcategories are set to the main category in brackets {IfcClass} 

- existing subcategories are altered to 'Not Exported' sometimes and I don't understand why and how (not by our colleagues for sure).

  • regarding this change I found out that:
  • I create a simple Generic Model
  • create subcategory 'test'
  • load into project.
  • check txt file: {IfcBuildingElementProxy} @ subcategory 'test'.... fine.
  • Edit family 'test'
  • Add shared parameter IFCExportAs
  • change that value to let's say "IfcWindow"
  • Load into project.
  • Choose the first option (not overwrite the values).
  • Check text file
  • subcategory is 'Not Exported' now. (if not, try chaging while loading into project 'overwrite gthe values too')
  • odd right?

 

But more important how is the hierarchy?

How do you guys make sure that your export is spot on every single time?

 

 

 

 

 

 

 

 

love python coding
3 ANTWORTEN 3
Nachricht 2 von 4
pipapongo0909
als Antwort auf: Joris.vd.Meulen

Hi,

 

i do not really understand the question?

 

I learned the hard way that the Ifc Export Settings are Recit installation specific and not project specific! Menaing that i played quite a long time around to get the desired ( almost, is till have some things messed up) Ifc export on one project.

 

On another project i changed the settings. then when exporting the first one again two weeks later nothing worked....

 

So to my undertsanding the ifc Mapping table ( Revit--> Export --> Options --> IFC) is just like the shared parameter file Installation specific!

 

So now i export for every project and even file the settings to the project folder just in case things get messed up again.

 

 

the hierachy works like follows:

 

the IfcExportAs Parameter is stronger than the mapping table

Ifc Mapping table

 

in case you are creating custom property sets you need to make sure that the element/ category you want to attach parameters from Revit to the IFC is exported into the right IFC class, otherwise you will not get a propertyset and no parameters.

I only use the IFC classes from this list supported IFC classes

And not every category is changeble, e.g. you can not change a wall from Revit to an IfcSlab.

 

personnally i still have problems exporting a slabEdges to IfcFooting.

see this post

 

 

please reform your question and maybe provide an example/snapshots i'll do my best to assist

 

good luck

 

 

 

 

 

 



Jeff Wurth
BIM Manager | Dipl Ing. Bauingenieur
LinkedIn

Nachricht 3 von 4
Joris.vd.Meulen
als Antwort auf: pipapongo0909

You got it fairly good P,

 

Rephrase-modus-on:

  1.  hierachy:
    #1 family IfcExportAs
    #2 project mapping txt file > subcategory
    #3 project mapping txt file > main category

    True?

  2. Revit's bug changing it's txt mapping file subcategory to 'Not Exported':
    If you are correct it won't affect my family since it has IfcExportAs defined.

    However: families that don't have the IfcExportAs defined but depend on the subcategory are screwed (pardon language) in that way.

    So how do I make sure that each of my families are well protected during export (read: the go to the correct Ifc classes). Do I have to use an IfcExportAs on ALL of my families because of the Revit mapping file being able to change?

Does this make more sense? Ill try to make a screencast on Thursday to show the issue we have.

 

love python coding
Nachricht 4 von 4
pipapongo0909
als Antwort auf: Joris.vd.Meulen

Hi @Joris.vd.Meulen


Rephrase-modus-on:

  1.  hierachy:
    #1 family IfcExportAs
    #2 project mapping txt file > subcategory
    #3 project mapping txt file > main category

    True?

 


I would say yes, for subcategories i can't really tell since i do not use them

 

For the second question:

Why is Revit changing the Mapping table and when? I haven't notice this yet. a simple solution would be to set it up correctly and then export the file. This way you can import the file just before you create the IFC file.

to give every family an IfcExport parameter would be quite tedious. You implement them directly in the family?

 

have a nice day,

 



Jeff Wurth
BIM Manager | Dipl Ing. Bauingenieur
LinkedIn

Sie finden nicht, was Sie suchen? Fragen Sie die Community oder teilen Sie Ihr Wissen mit anderen.

In Foren veröffentlichen  

Autodesk Design & Make Report