topic Re: Structural Connections not exported via Document.Export (Revit 2018/Python) in Revit API Forum

Structural Connections not exported via Document.Export (Revit 2018/Python)

igmuz — Fri, 07 Sep 2018 14:41:36 GMT

I am trying to export REVIT Structural Connections to IFC with Document.Export.

When export is run from Python, all Generic Models with Family Category set to "Structural Connections" get exported, while none of the REVIT Structural Connections is exported.

From User Interface I manage to export both without a problem. In Family Mapping File, Revit Category Structural Connections is mapped to IFC Class Name IfcBuildingElementProxy.

Python code is shown below:

options=IFCExportOptions()
options.ExportBaseQuantities = False
options.FileVersion = IFCVersion.IFC2x3CV2
options.SpaceBoundaryLevel=0
options.WallAndColumnSplitting=False
options.FamilyMappingFile="D:\IFC_options.txt"
options.AddOption("ExportInternalRevitPropertySets","true")
options.FilterViewId = views[i].Id
DocumentManager.Instance.CurrentDBDocument.Export("D:\IFC eksport","Structural_Connections.ifc",options)

Re: Structural Connections not exported via Document.Export (Revit 2018/Python)

jeremytammik — Mon, 10 Sep 2018 05:16:55 GMT

Dear Igmuz,

Thank you for your query.

It makes no difference whether you are using Python or any other programming language to drive the Revit API.

I am surprised that you observe a difference between the export generated through the user interface and the API driven result.

I would expect it to be due to the options you are setting.

Are you sure the exact same options are applied when exporting manually?

The best place to discuss questions related to IFC export and import is the Revit IFC open source discussion forum:

https://sourceforge.net/p/ifcexporter/discussion/general

I hope this helps.

Best regards,

Jeremy

Re: Structural Connections not exported via Document.Export (Revit 2018/Python)

igmuz — Sun, 16 Sep 2018 18:33:05 GMT

Dear jeremytammik,

Thank you for your reply.

I tried to recreate UI export options as accurately as possible.

I saved UI export setup as *.json file, and opened it in Notepad++.

Afterwards I implemented all of the options from the '.json file into Python code.

Still no luck with getting Structural Cconnections exported to IFC via API.

Part of the Python code is shown below:

options=IFCExportOptions()

v=UnwrapElement(IN[1][1][0])
options.WallAndColumnSplitting = "false"
options.ExportBaseQuantities = "true"
options.FilterViewId = v.Id
options.AddOption("ExportInternalRevitPropertySets","true")
options.AddOption("ExportAnnotations ","true")
options.AddOption("SpaceBoundaries ", "0")
options.AddOption("VisibleElementsOfCurrentView ", "true")
options.AddOption("Use2DRoomBoundaryForVolume ", "true")
options.AddOption("UseFamilyAndTypeNameForReference ", "true")
options.AddOption("ExportInternalRevitPropertySets ","true")
options.AddOption("ExportIFCCommonPropertySets","true")
options.AddOption("Export2DElements", "false")
options.AddOption("ExportPartsAsBuildingElements", "false")
options.AddOption("ExportBoundingBox", "false")
options.AddOption("ExportSolidModelRep", "true")
options.AddOption("ExportSchedulesAsPsets", "false")
options.AddOption("ExportLinkedFiles", "false")
options.AddOption("IncludeSiteElevation","true")
options.AddOption("UseActiveViewGeometry", "false")
options.AddOption("ExportSpecificSchedules", "false")
options.AddOption("TessellationLevelOfDetail", "0.5")
options.AddOption("StoreIFCGUID", "true")
options.AddOption("ExportRoomsInView", "false")

Re: Structural Connections not exported via Document.Export (Revit 2018/Python)

jeremytammik — Mon, 17 Sep 2018 06:07:43 GMT

Okey-doke, sorry to hear it, time to ask the development team to take a look.

Please provide an absolutely minimal reproducible case:

http://thebuildingcoder.typepad.com/blog/about-the-author.html#1b

Presumably, a minimal structural model containing only one or two structural connections that export perfectly well driven manually will suffice, with a (Python?) SharpDevelop macro attempting to export them in the same way that fails.

Thank you!

Cheers,

Jeremy

Re: Structural Connections not exported via Document.Export (Revit 2018/Python)

igmuz — Thu, 20 Dec 2018 14:56:38 GMT

Hi again,

I am attaching the test model, Dynamo script and the FamilyMapping text file.

In REVIT structure looks like this:

IFC exported by user interface looks like this:

And when exported via API, structural connection defined via REVIT Add-In is not exported:

Notice that elements of Structural Connection category, if modelled as Family, do get exported.

Thank you very much for your help.

Igor Muzdeka

Re: Structural Connections not exported via Document.Export (Revit 2018/Python)

igmuz — Thu, 20 Dec 2018 15:01:05 GMT

It looks like I cannot attach Dynamo script, so I am pasting Python code instead:

import clr
clr.AddReference('ProtoGeometry')
from Autodesk.DesignScript.Geometry import *
clr.AddReference('RevitAPI')
from Autodesk.Revit.DB import*
# RevitServices to access the REvit file content (aka document)
clr.AddReference('RevitServices')
from RevitServices.Persistence import DocumentManager
from RevitServices.Transactions import TransactionManager

import sys
sys.path.append(r'C:\Program Files (x86)\IronPython 2.7\Lib')
import os

# Define the doc you want to work with
doc = DocumentManager.Instance.CurrentDBDocument
#Start Transaction
TransactionManager.Instance.EnsureInTransaction(doc)

#The inputs to this node will be stored as a list in the IN variables.
dataEnteringNode = IN

for v in FilteredElementCollector(doc).OfCategory(BuiltInCategory.OST_Views):
    if v.Name=="Export Structural Connections":
        view=v

output=[]

options=IFCExportOptions()
options.AddOption("Name","IFC Export")
options.AddOption("IFCVersion","21")
options.AddOption("IFCFileType","0")
options.AddOption("SpaceBoundaries","0")
options.AddOption("SitePlacement","0")
options.AddOption("ActivePhaseId","0")
options.AddOption("ExportBaseQuantities","False")
options.AddOption("SplitWallsAndColumns","False")
options.AddOption("ExportInternalRevitPropertySets","False")
options.AddOption("ExportIFCCommonPropertySets","True")
options.AddOption("Export2DElements","False")
options.AddOption("VisibleElementsOfCurrentView","True")
options.AddOption("Use2DRoomBoundaryForVolume","False")
options.AddOption("UseFamilyAndTypeNameForReference","False")
options.AddOption("ExportPartsAsBuildingElements","False")
options.AddOption("ExportSolidModelRep","False")
options.AddOption("ExportSchedulesAsPsets","False")

options.AddOption("ExportUserDefinedParameterMapping","True")
options.AddOption("ExportUserDefinedParameterMappingFileName",os.path.abspath("C:\ProgramData\Autodesk\ApplicationPlugins\IFC 2018.bundle\Contents\2018\ParameterMappingTable.txt").ToString())

options.AddOption("ExportUserDefinedPsets","False")
options.AddOption("ExportUserDefinedPsetsFileName",os.path.abspath("C:\ProgramData\Autodesk\ApplicationPlugins\IFC 2018.bundle\Contents\2018\IFC2x3 Coordination View.txt").ToString())

options.AddOption("ExportBoundingBox","False")
options.AddOption("IncludeSiteElevation","False")
options.AddOption("UseActiveViewGeometry","True")
options.AddOption("ExportSpecificSchedules","False")
#options.AddOption("TessellationLevelOfDetail",str(0.5))
options.AddOption("UseOnlyTriangulation","False")
options.AddOption("StoreIFCGUID","False")
options.AddOption("ExportRoomsInView","False")
options.AddOption("ExportLinkedFiles","False")
options.AddOption("ActiveViewId","0")
options.AddOption("ExcludeFilter","")
options.AddOption("COBieCompanyInfo","")
options.AddOption("COBieProjectInfo","")
options.AddOption("IsBuiltIn","False")
options.AddOption("IsInSession","False")
options.AddOption("FileVersionDescription","IFC 2x3 Coordination View 2.0")
options.FamilyMappingFile="D:\REVIT 2018\DYNAMO\Export Structural Connections\Export Structural Connections.txt"

options.FilterViewId = view.Id
x=doc.Export("D:\REVIT 2018\DYNAMO\Export Structural Connections","Export Structural Connections_API.ifc",options)
output.append(x)


#End Transaction
TransactionManager.Instance.TransactionTaskDone()

OUT = output

Re: Structural Connections not exported via Document.Export (Revit 2018/Python)

matthew_taylor — Wed, 06 Feb 2019 18:37:55 GMT

Hi @igmuz / @jeremytammik ,

Any news on this?

Re: Structural Connections not exported via Document.Export (Revit 2018/Python)

jeremytammik — Thu, 07 Feb 2019 12:00:05 GMT

Dear Igmuz and Matt,

Thank you for your sample material and prompt for progress.

I logged the issue REVIT-143711 [Structural Connections are missing after Document.Export -- 14594124] with our development team for this on your behalf as it requires further exploration and possibly a modification to our software. Please make a note of this number for future reference.

I have not heard back from them yet on it.

I see two vaguely related issues:

RVTLMV-467 [Failed to export Structure connection (Revit 2017 new element], closed as 'by design'; checked with Structure team, both generic connection and red connection have no really geometry, so export nothing.
REVIT-62829 [[Export IFC] Some DirectShapes are not exported as properly categorized items in IFC], still open; Attached project is placed structural framing which is created as direct shape geometry. After exporting IFC format, only Structural Connections and Structural Column category disappeared.

You are welcome to request an update on the status of this issue or to provide additional information on it at any time quoting this change request number.

This issue is important to me. What can I do to help?

This issue needs to be assessed by our engineering team and prioritised against all other outstanding change requests. Any information that you can provide to influence this assessment will help. Please provide the following where possible:

Impact on your application and/or your development.
The number of users affected.
The potential revenue impact to you.
The potential revenue impact to Autodesk.
Realistic timescale over which a fix would help you.
In the case of a request for a new feature or a feature enhancement, please also provide detailed Use cases for the workflows that this change would address.

This information is extremely important. Our engineering team have limited resources, and so must focus their efforts on the highest impact items. We do understand that this will cause you delays and affect your development planning, and we appreciate your cooperation and patience.

Best regards,

Jeremy

Re: Structural Connections not exported via Document.Export (Revit 2018/Python)

angel_velez — Wed, 06 Mar 2019 14:26:20 GMT

Sorry for the slow response. Please try adding:

options.AddOption("IncludeSteelElements","true")

and see if that fixes the issue. I will try it locally, and also suggest that we make that the default, to match the UI.

Regards,

Angel

Re: Structural Connections not exported via Document.Export (Revit 2018/Python)

igmuz — Fri, 15 Mar 2019 10:40:42 GMT

Hi,

options.AddOption("IncludeSteelElements","true") did not solve the problem.

Structural Connections are still not exported to IFC modell.

Re: Structural Connections not exported via Document.Export (Revit 2018/Python)

jeremytammik — Fri, 15 Mar 2019 19:34:11 GMT

Dear Igor,

Angel repeats that it works fine for him.

Can you please check that your structural connections are not set to 'not exported'?

Thank you.

Best regards,

Jeremy

Re: Structural Connections not exported via Document.Export (Revit 2018/Python)

igmuz — Fri, 29 Mar 2019 10:49:08 GMT

Hi Jeremy,

In the code I am specifying same IFC Options that are used in export via User Interface:

options.FamilyMappingFile="D:\REVIT 2018\DYNAMO\Export Structural Connections\Export Structural Connections.txt"

IFC Options er set up so Structural Connections are exported as IfcBuildingElementProxy:

Re: Structural Connections not exported via Document.Export (Revit 2018/Python)

jeremytammik — Fri, 29 Mar 2019 11:50:25 GMT

Dear Igor,

Thank you for your update and confirmation.

I passed it on to the developers.

Best regards,

Jeremy

Re: Structural Connections not exported via Document.Export (Revit 2018/Python)

jeremytammik — Fri, 29 Mar 2019 12:56:12 GMT

They reply:

Have you tried to replicate this in the native Revit API?

I haven't tried Python, but using Revit API it works.

Cheers,

Jeremy

Re: Structural Connections not exported via Document.Export (Revit 2018/Python)

igmuz — Fri, 29 Mar 2019 15:48:18 GMT

Jeremy, what do you exactly mean with native Revit API?

I wrote a macro in C# and it did not work either! 😞

Re: Structural Connections not exported via Document.Export (Revit 2018/Python)

jeremytammik — Fri, 29 Mar 2019 17:33:25 GMT

Yup, that's exactly what I meant.

Good for you.

Can you provide a minimal reproducible case to share with the development team to prove to them unequivocally that it does not work?

https://thebuildingcoder.typepad.com/blog/about-the-author.html#1b

A minimal sample model with just a very few elements plus that macro should do the trick, plus exact step by step instructions to reproduce the problematic behaviour.

Thank you!

Cheers,

Jeremy

Re: Structural Connections not exported via Document.Export (Revit 2018/Python)

igmuz — Mon, 01 Apr 2019 06:21:13 GMT

Hi,

I am attaching the same minimal reproducible case file as before, this time with macro included.

Re: Structural Connections not exported via Document.Export (Revit 2018/Python)

igmuz — Mon, 01 Apr 2019 06:34:51 GMT

This time with correct REVIT file.

Re: Structural Connections not exported via Document.Export (Revit 2018/Python)

jeremytammik — Mon, 01 Apr 2019 07:22:12 GMT

Dear Igor,

Thank you for your update and reproducible case.

I opened your sample file in Revit 2019 and noted that it is stored in Revit 2018 format.

I see your macro IFC Export in there and executed it.

It is taking a very long time to complete...

In fact, it does not seem to be completing at all, just running forever.

I cancelled the first attempt after a couple of minutes and looked at the macro code next.

[Window Title]
Run Macro Failed

[Main Instruction]
Revit failed to execute IFCExport. 

[Expanded Information]
A problem has been detected. 

Autodesk.Revit.Exceptions.InvalidPathArgumentException: The folder does not exist.
Parameter name: folder
   at MacroModule.executeMacro_(MacroModule* , AString* macroName)
   at MacroModule.executeMacro(MacroModule* , AString* macroName)
   at MacroModule.executeMacro(MacroModule* , AString* )
   at UIMacroGeneralManager.runMacro(UIMacroGeneralManager* , MacroModule* pModule, AString* macroName)

[^] Hide details  [Close]

OK, I see that I have to edit the folder path.

I fixed the output folder path, and I still get the same problem.

Oh, looking again, I see that your code specifies several input files as well, e.g., ParameterMappingTable.txt, IFC2x3 Coordination View.txt, Export Structural Connections.txt.

They seem to be spread all over the place in your system.

Well, they are apparently not present in mine.

Unfortunately, I cannot run your code like this, nor pass it on to the development team.

Please realise that a reproducible sample setup means that it can truly be reproduced, preferably with a single click.

If any paths need to be edited, please specify that explicitly.

Please specify every single minute step required to reproduce the issue.

Nobody is ever eager to reproduce any problems, so you have to make it very convincing and simple, inevitable.

If you do not, people will not be able to see any problem, and it will remain yours only.

Can you please supply the missing files and instructions, so I can give it another try?

Thank you!

Best regards,

Jeremy

Re: Structural Connections not exported via Document.Export (Revit 2018/Python)

igmuz — Mon, 01 Apr 2019 12:22:44 GMT

Hi again,

I forgot to send Parameter Mapping File. Attached within this post.

Have fixed the directory issue. In the new attached file, code is refering to current file directory so please keep parameter mapping file within same folder as REVIT file.

ExportUserDefinedPsets is now set to false and the path to user defined pset is commented out.

Sorry for the inconveniece.