> For the complete documentation index, see [llms.txt](https://docs.openbrim.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openbrim.org/templates/steel-i-girder-bridge-workflow/export-sig/dxf-seed-file-configuration-sig.md).

# DXF Seed File Configuration \[SIG]

The DXF Seed File Configuration object maps OpenBrIM level names onto the layer names an AutoCAD standard requires, so an exported drawing does not have to be re-layered by hand before it is issued. It is the AutoCAD counterpart to the DGN Seed File Configuration.

Uploading a `.dxf` seed file is **optional**. With no seed the object is still a complete rename table, which is the common case. When a seed is present, its LAYER table is read and supplies the list of target layers to pick from, so the mapping can be built against the real standard rather than typed from memory.

## Parameters

**Name:** The identifier for the configuration. This name appears in the Seed File Config list when setting up a DXF export, and it is the name the `export_model` agent tool takes.

**Type \[2D/3D]:** Whether this configuration is for 2D drawing exports or 3D model exports. A configuration is refused if it is used on the other kind of export — a 2D table applied to a 3D export would match nothing and produce a clean-looking but entirely unmapped file.

**Seed File:** An optional reference to an uploaded AutoCAD (`.dxf`) seed file. Only its LAYER table is read, to populate the target-layer list.

**Layer Mappings:** How OpenBrIM levels are renamed on export, with optional per-layer property overrides.

**Use Seed Layer Colors \[NO=0/YES=1]:** When a seed is present, take each target layer's colour, linetype and lineweight from the seed's own LAYER table rather than from the model.

## Layer Mappings

Each mapping entry has these fields:

| Field                   | Description                                                   |
| ----------------------- | ------------------------------------------------------------- |
| **OBrIM Level**         | The level name used in the OpenBrIM drawing                   |
| **DXF Layer**           | The layer name to write in the exported file                  |
| **Color Override**      | ACI index or true colour; leave empty to keep the model's own |
| **Linetype Override**   | Linetype name; leave empty to keep the model's own            |
| **Lineweight Override** | Lineweight; leave empty to keep the model's own               |

Overrides **merge field by field**. Override only the colour and the model's own linetype and lineweight survive.

### Editing layer mappings

Click the three-dot icon in the Layer Mappings parameter:

**Edit (Spreadsheet)…** opens a sub-spreadsheet where entries can be added, changed and deleted.

**Import from Drawings…** reads the level names out of the drawings you select and adds any that are not already mapped. Existing entries are preserved.

### Example

| OBrIM Level    | DXF Layer   | Color Override | Linetype Override | Lineweight Override |
| -------------- | ----------- | -------------- | ----------------- | ------------------- |
| GirderLevel    | S-BEAM      |                |                   |                     |
| DeckLevel      | S-DECK      |                |                   |                     |
| DimensionLevel | A-ANNO-DIMS | 2              |                   | 25                  |

## Usage notes

* **Cut-view companions travel with the rename.** Renaming a level also renames its `-PROJ`, `-HIDDEN` and `-CL` companion layers, so the freeze-hidden-lines workflow those layers exist for keeps working after a rename.
* **Layer `0` and `OBRIM-VIEWPORT` are reserved** and cannot be renamed or used as a target. Layer `0` carries block content drawn with BYBLOCK graphics — that is the contract that lets a recipient restyle a dimension or a title block by restyling its INSERT.
* The configuration must exist before it can be selected in the export settings.
* An unknown configuration name, or one whose Type does not match the export, is **refused**. The export never falls back to writing an unmapped file.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.openbrim.org/templates/steel-i-girder-bridge-workflow/export-sig/dxf-seed-file-configuration-sig.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.