Navisworks: Export

12 nodes. Types ending in [] are lists. An input with a default is optional.

Nodes

BCF.ExportIssues

Exports clash results (or saved viewpoints) as BCF 2.1 issues (.bcfzip: markup, camera viewpoint, component GUIDs, snapshot) — the vendor-neutral bridge into BIMcollab / Konekt / Revizto / ACC. Components use the IFC GlobalId when present, else the InstanceGuid (lossy for non-IFC sources). Cameras are written in meters per the BCF convention. Navisworks numbers clash results per test (Clash1 in every test), so when the results come from more than one test each issue title gets its test in front ("Test - Clash1"), and titles that would still repeat are numbered (2), (3) with a warning.

Inputs

Input	Type	Default	What it does
filePath required	string	—	Destination .bcfzip (or .bcf) path; the directory is created when missing. A relative path is next to the graph file.
results	SavedItem[]	null	Clash results or result groups to export as topics (from ClashTest.Results).
viewpoints	SavedViewpoint[]	null	Saved viewpoints to export as topics (instead of, or besides, results).
includeSnapshots	boolean	true	True to render a snapshot.png per topic (slower on big result lists).
statusMap	IDictionary	null	Optional Navisworks-status → BCF-topic-status map (e.g. {"New": "Open", "Approved": "Closed"}). Unmapped statuses use the default map: New/Active → Open, Reviewed → In Progress, Approved/Resolved → Closed.
document	Document	null	The document (defaults to the active document).

Outputs

Output	Type
filePath	file
topicCount	integer

Returns: The written path and the number of topics exported.

Tags: bcf export issues bcfzip bimcollab revizto konekt acc exchange

BCF.ImportIssues

Reads a BCF 2.0/2.1 package: per topic title/status/description/comments/component GUIDs/camera, plus the model items each topic's components resolve to (matched by IFC GlobalId, then InstanceGuid). Optionally applies one topic's camera to the current view — feeds ClashResult.SetStatus and Selection.SetCurrent for the issue-sync return leg.

Inputs

Input	Type	Default	What it does
filePath required	string	—	The .bcfzip (or .bcf) file to read. A relative path is next to the graph file.
applyCameraTopicIndex	integer	-1	Index of a topic whose camera should be applied to the current view (-1 = leave the camera alone).
document	Document	null	The document (defaults to the active document).

Outputs

Output	Type
topics	dict[]
modelItems	ModelItem[][]

Returns: Topic dictionaries and, per topic, the list of model items its component GUIDs resolve to (a list of lists).

Tags: bcf import issues bcfzip read roundtrip exchange

Export.ClashReport

One-node clash report. A .csv path writes one row per result (test, group, result, status, distance, assignee, description, both item paths and GUIDs, the clash point; Excel-ready). A .html path writes a self-contained page, one section per test, optionally with a snapshot of every result (Advanced: includeImages, imageWidth, imageHeight), shareable as one file. Unwired tests reports every test in the document; an empty list reports none, so a filter that finds nothing gives an empty report instead of a report on everything.

Inputs

Input	Type	Default	What it does
filePath required	string	—	Destination .csv or .html (.htm) path; the directory is created when missing. A relative path is next to the graph file.
tests	ClashTest[]	null	The clash tests to report. Leave unwired for every test in the document; an empty list reports no test.
includeImages	boolean	false	HTML only: true embeds a snapshot per result (larger file, needs the Navisworks viewport).
imageWidth	integer	320	HTML only: snapshot width in pixels.
imageHeight	integer	240	HTML only: snapshot height in pixels.
document	Document	null	The document (defaults to the active document).

Outputs

Output	Type
filePath	file
rowCount	integer

Returns: The written file path and the number of result rows.

Tags: export clash report csv html excel triage snapshot share clashreportcsv clashreporthtml

Export.IfcClasses

Lists the friendly IFC class names (Wall, Beam, Door, …) accepted by Export.IfcSetClassMap.

No inputs.

Outputs

Output	Type	What it gives
classes	string[]	The catalogue of mappable IFC class names.

Tags: ifc export class catalog types

Export.IfcCoordinates

Base-point and georeferencing options for Export.ToIfc: geometry/model/custom origin, rotation and IFC4 georeferencing. eastings, northings and elevation are in metres and are used only when basePoint is Custom.

Inputs

Input	Type	Default	What it does
basePoint	string	"GeometryOrigin"	"GeometryOrigin" (default), "ModelOrigin" or "Custom".
eastings	number	0	Custom base-point easting in metres; used only when basePoint is Custom.
northings	number	0	Custom base-point northing in metres; used only when basePoint is Custom.
elevation	number	0	Custom base-point elevation in metres; used only when basePoint is Custom.
rotationDegrees	number	0	Grid/true-north rotation, recorded in IFC4 georeferencing.
writeGeoref	boolean	true	Write IfcMapConversion/IfcProjectedCRS (IFC4 only).

Outputs

Output	Type	What it gives
coordinates	CoordOptions	A coordinate-options object to wire into Export.ToIfc.

Tags: ifc export coordinates base point georeferencing origin rotation

Export.IfcParameterRule

One property rename/relocate rule for Export.ToIfc — moves/renames a source property into a target IFC Pset/name on export. The search button next to source and sourceCategory lists what the elements selected in Navisworks right now carry.

Inputs

Input	Type	Default	What it does
source required	string	—	Source property name to match (case-insensitive).
targetPset	string	""	Destination Pset (blank = keep original category).
targetName	string	""	Destination property name (blank = keep original name).
sourceCategory	string	""	Only match this source category (blank = any).

Outputs

Output	Type	What it gives
rule	ParamMapRule	A parameter-map rule; collect several into a list for Export.ToIfc.

Tags: ifc export parameter property pset rename map rule

Export.IfcRoles

Maps Navisworks source properties to IFC roles — Type→IfcElementType, Level→IfcBuildingStorey, Material→IfcMaterial, Classification→IfcClassificationReference — for Export.ToIfc. The search button next to a name lists the tabs and properties of the elements selected in Navisworks right now.

Inputs

Input	Type	Default	What it does
typeProperty	string	""	Property whose value groups occurrences into IfcElementType (+ ObjectType).
typeCategory	string	""	Category carrying the type property (blank = any).
levelProperty	string	""	Property whose value assigns each element to an IfcBuildingStorey.
levelCategory	string	""	Category carrying the level property (blank = any).
materialProperty	string	""	Property whose value becomes the IfcMaterial name.
materialCategory	string	""	Category carrying the material property (blank = any).
classificationProperty	string	""	Property whose value becomes an IfcClassificationReference (IFC4).
classificationCategory	string	""	Category carrying the classification property (blank = any).

Outputs

Output	Type	What it gives
roles	PropertyRoles	A property-roles object to wire into Export.ToIfc.

Tags: ifc export roles type level storey material classification mapping

Export.IfcSetClassMap

Assigns an IFC class to every item of the named saved/search sets (set→class), producing the classMap for Export.ToIfc.

Inputs

Input	Type	Default	What it does
setNames required	string[]	—	Saved/search set display names to map.
ifcClasses required	string[]	—	IFC class per set (friendly names, e.g. "Wall", "Beam"; see Export.IfcClasses).
predefinedTypes	string[]	null	Optional predefined type per set (parallel list; blank entries allowed).
document	Document	null	The document (defaults to the active document).

Outputs

Output	Type	What it gives
classMap	dict	An item→class map to wire into Export.ToIfc's classMap.

Tags: ifc export class set selection set map type ifcwall

Export.IfcSpatialNames

Names for the IFC spatial tree (Project/Site/Building/default Storey) used by Export.ToIfc.

Inputs

Input	Type	Default	What it does
project	string	"BIMCamel Export"	IfcProject name.
site	string	"Site"	IfcSite name.
building	string	"Building"	IfcBuilding name.
storey	string	"Storey"	Default IfcBuildingStorey name (level-less elements).

Outputs

Output	Type	What it gives
spatialNames	SpatialNames	A spatial-names object to wire into Export.ToIfc.

Tags: ifc export project site building storey spatial

Export.ToCsv

Writes one CSV row per model item with a Name column plus property columns, straight from the model: a quick quantity take-off file. For anything you want to shape first (sort, filter, group, add columns, dates as dates, an Excel workbook) use Properties.ToTable and the Table nodes, then Table.ToCsvFile or Table.ToExcelFile: they share the CSV and Excel options of the rest of the library.

Inputs

Input	Type	Default	What it does
items any number of wires required	ModelItem[]	—	The model items to export (one row each).
filePath required	string	—	Destination .csv path; the directory is created when missing. A relative path is next to the graph file.
categoryName	string	null	Property category to export; null exports every category as "Category.Property" columns.
propertyNames	string[]	null	Property names to export from the category; null exports all found.

Outputs

Output	Type	What it gives
filePath	string	The written file path.

Tags: export csv qto takeoff report excel table properties

Export.ToIfc

Exports model items to IFC (IFC4/IFC2x3) via the BIMCamel exporter: spatial tree, instancing, property sets, materials, base quantities and georeferencing. The main inputs are the items, the file and the schema and units; the options of the Advanced panel (instancing, property sets, materials, quantities, quality, splitting, validation and the Export.Ifc* option nodes) have sensible defaults. filePath always comes out as ONE text, the first file written; files lists every file (more than one only when splitMegabytes splits the export), so a node after it sees the same kind of value whatever the split.

Inputs

Input	Type	Default	What it does
items any number of wires required	ModelItem[]	—	The model items to export (resolved to leaf geometry, like the exporter's scope).
filePath required	string	—	Destination .ifc path; the directory is created when missing. A relative path is next to the graph file.
schema	string	"IFC4"	"IFC4" (default) or "IFC2x3".
instancing	boolean	true	Reuse repeated geometry as IfcMappedItem (smaller files); off writes every mesh in full.
properties	boolean	true	Write Navisworks properties as IfcPropertySets.
materials	boolean	true	Write element colours as IfcSurfaceStyle / IfcMaterial.
quantities	boolean	true	Compute base quantities (volume/area/length) from the mesh.
units	string	"Auto"	Source units: "Auto" (from the model) or Millimeters/Centimeters/Meters/Feet/Inches.
quality	string	"Balanced"	"Balanced" (default), "Small file" or "High detail" — sets weld tolerance and coordinate precision.
coordinates	CoordOptions	null	Base-point / georeferencing options from Export.IfcCoordinates (default: geometry origin + georef).
spatialNames	SpatialNames	null	Project/Site/Building/Storey names from Export.IfcSpatialNames (default: sensible names).
roles	PropertyRoles	null	Type/Level/Material/Classification source-property mapping from Export.IfcRoles.
parameterRules	ParamMapRule[]	null	Property rename/relocate rules from Export.IfcParameterRule.
categoryFilter	string[]	null	Only export these property categories (null = all).
classMap	dict	null	Item→IFC-class overrides from Export.IfcSetClassMap.
splitMegabytes	number	0	Split the output into parts near this size (0 = single file).
validate	boolean	false	Run the built-in structural validator on each written file.
document	Document	null	The document (defaults to the active document).

Outputs

Output	Type
filePath	file
fileCount	integer
elementCount	integer
triangleCount	integer
fileSizeKb	number
files	file[]

Returns: The first written path, how many files were written, the exported element and triangle counts, the size, and every written path.

Tags: export ifc openbim bim qto ifc4 ifc2x3 bimcamel

Export.ViewpointImage

Renders a view to a .png/.jpg/.bmp file via the Navisworks image exporter. Without 'viewpoint' it is the view as it is when the node runs: wire what sets the view into 'after'. Wire saved viewpoints into 'viewpoint' and the node shows each one itself and takes its picture; put {name} in the file path ("C:\Pictures\{name}.png") for one file per viewpoint. That is the batch for a folder: Viewpoints.InFolder into 'viewpoint'. (SavedViewpoint.Apply followed by this node over a list does not work: every Apply runs first, then every picture shows the last view.) The view is left on the last viewpoint shown; Camera.Save and Camera.Restore put it back.

Inputs

Input	Type	Default	What it does
filePath required	string	—	Destination .png, .jpg or .bmp path; the directory is created when missing. A relative path is next to the graph file. With a viewpoint, {name} in the path becomes the viewpoint's name.
width	integer	1920	Image width in pixels.
height	integer	1080	Image height in pixels.
viewpoint	any	null	Optional: the viewpoint to show first (a saved viewpoint, its name or folder path, or a camera from Camera.Save). A list takes one picture per viewpoint. Empty takes the picture of the view as it is.
after	any	null	Anything at all, only to run this node after the node it comes from: the picture is of the view at the moment this node runs, and the engine does not order nodes that share no wire.
document	Document	null	The document (defaults to the active document).

Outputs

Output	Type	What it gives
filePath	string	The written file path.

Tags: export image screenshot render viewpoint png picture batch