Commands  ›  Clash Manager / Reporting  ›  Clash Manager Export Results To Navisworks Xml

Clash Manager Export Results To Navisworks Xml

Clash Manager / Reporting writes to model Public API · not yet exposed

Coming soon

Before you run this

Active doc; staging DB has ≥ 1 clash row.

After it runs

Single .xml file on disk.

When to use this

Don't use this when

Reading NW XML — use ClashFinderImportResultsFromNavisworksXmlCommand.

Inputs

NameKindTypeRequiredDefaultDescription
PresetKind config string no "clash_tolerances" Deterministic config preset

Decision flow

1) Resolve output path (default .mepbridge/qa/reports/clashes_{ts}.xml).
2) Pull rows via repo.ListByState(state_filter ?? "*").
3) Build XDocument: <exchange><batchtest><clashtest><clashresults><clashresult><description>...</description><clashpoint><pos3f .../></clashpoint><objects><object ...>...</object></objects></clashresult>...</clashresults></clashtest></batchtest></exchange>.
4) Pull element centroids for clashpoint; elements as <object> with guid + displayname.
5) Save XML with indentation; emit result summary.

What you'll see in the chat

on start
Exporting clashes to Navisworks XML…
thinking
Querying staging DB…
Writing XML tree…
on success
Navisworks XML written to {output_path}.
on failure
Navisworks export failed: {error}

REST API

Not yet exposed

This command does not carry a [RestApi] attribute today. Once tagged, this section will auto-populate with:

  • POST /api/v1/commands/clash_manager_export_results_to_navisworks_xml
  • Request body schema (from [RestApiParam])
  • Response schema (from [RestApiResponse])
  • curl / JS / Python code examples

Keywords & intent patterns

clashmanagerexportresultstonavisworksxml · export navisworks xml · qa nw export

PillarClash Manager / Reporting