Commands  ›  Architecture / Drawing Production  ›  Architecture Add Filled Region Inside Each Room Boundary

Architecture Add Filled Region Inside Each Room Boundary

Architecture / Drawing Production writes to model Public API · not yet exposed

Coming soon

Before you run this

Active view is a plan. Rooms placed and bounded. Filled-region types defined for each Room Type / Department the project uses.

After it runs

One FilledRegion inside each selected room's boundary using the type that matches the room's Department / Room Type parameter; existing graphics untouched.

When to use this

Don't use this when

Sections / 3D views, rooms without a Department / Room Type set, or schemes where the colour-coding is driven by a view filter rather than filled regions.

Decision flow

1. Confirm the active view is a plan and read the rooms in scope.
2. For each room, read the Department / Room Type parameter and pick the matching filled-region type.
3. Read the room's boundary as a closed curve loop.
4. Create a FilledRegion in one Transaction inside each loop.
5. Report regions placed per Department and any rooms skipped (e.g. no boundary).

What you'll see in the chat

on start
I'll add filled regions inside those room boundaries now — matching each to the project type.
thinking
Reading each room's Department / Room Type and picking the matching filled-region type.
on success
Done — {n_placed} filled regions placed across {n_rooms} rooms.
on failure
Couldn't add filled regions: {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/architecture_add_filled_region_inside_each_room_boundary
  • Request body schema (from [RestApiParam])
  • Response schema (from [RestApiResponse])
  • curl / JS / Python code examples

Keywords & intent patterns

filled region per room · room hatching · departmental colouring · fire strategy plan · wayfinding plan

PillarArchitecture / Drawing Production