Import Rad
Coming soon
Active document must be open. A JSON file with radiator blocks and an Excel schedule with Length/Family/Type columns must be available. At least one level must exist.
Radiator family instances are placed at JSON coordinates with types from the Excel schedule. Match results are exported to a rad-matches.json file alongside the source JSON. Schedule input is exported to rad-schedule-input.json for comparison.
When to use this
- User wants to place radiators in Revit from a design tool export.
- User has a JSON with radiator positions and an Excel schedule with sizing data.
- User needs to match radiator types to positions via reference attributes.
Importing full MEP layouts with pipes, ducts, trays (use ImportCommand). Manually placing individual radiators (use Revit's family placement). Editing existing radiator parameters (use parameter editing commands).
Inputs
| Name | Kind | Type | Required | Default | Description |
|---|---|---|---|---|---|
jsonPath |
config | string |
no | — | Path to JSON file with radiator positions |
schedulePath |
config | string |
no | — | Path to Excel schedule with Length/Family/Type columns |
Returns
| Name | Type | Description |
|---|---|---|
Placed | int | Number of radiators placed |
Skipped | int | Number of radiators skipped |
What you'll see in the chat
Placing radiators from your design data...
Loading Excel radiator schedule...
Matching blocks to schedule rows by reference...
Placing family instances...
REST API
This command does not carry a [RestApi] attribute today. Once tagged, this section will auto-populate with:
POST /api/v1/commands/import_rad- Request body schema (from
[RestApiParam]) - Response schema (from
[RestApiResponse]) - curl / JS / Python code examples
Keywords & intent patterns
import radiators · place radiators · radiator import · rad import · radiator schedule
Patterns: import * radiator* · place * radiator* · rad * import
Related
| Related commands | ImportCommand |
|---|---|
| Pillar |