bimdown-cli 0.2.1 → 0.2.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -15,3 +15,13 @@ fields:
15
15
 
16
16
  - name: name
17
17
  type: string
18
+
19
+ - name: boundary_points
20
+ type: string
21
+ computed: true
22
+ description: Space boundary polygon vertices (computed by build from surrounding walls)
23
+
24
+ - name: area
25
+ type: float
26
+ computed: true
27
+ description: Space area in square meters (computed from boundary polygon)
@@ -58,7 +58,7 @@ All elements belong to a **base level** (their `level_id`).
58
58
  | `wall` | Line | `<path>` | Architectural wall with thickness and vertical span |
59
59
  | `column` | Point | `<rect>`/`<circle>` | Architectural column with section profile |
60
60
  | `slab` | Polygon | `<polygon>` | Floor/roof/finish slab |
61
- | `space` | Seed point | No | Named space/room (boundary derived from walls + room_separator) |
61
+ | `space` | Seed point | `<polygon>` (computed) | Named space/room (boundary computed by `build` from walls, curtain walls, room separators) |
62
62
  | `door` | Hosted on wall | No | Door with operation type |
63
63
  | `window` | Hosted on wall | No | Window with dimensions |
64
64
  | `opening` | Hosted | Conditional | Wall opening (no SVG) or slab opening (`<rect>`/`<polygon>`) |
@@ -196,7 +196,7 @@ Line elements use `<path>` with `M`, `L`, `A` commands. This naturally supports
196
196
 
197
197
  Some elements have no SVG representation:
198
198
  - **Door/Window**: Fully defined by `host_id` + `position` (parametric placement on wall). Absolute coordinates would require re-syncing whenever the host wall moves.
199
- - **Space**: Defined by seed point `(x, y)`. Boundary is auto-derived from surrounding walls and room separators.
199
+ - **Space**: Defined by seed point `(x, y)` in CSV. Boundary polygon is auto-computed by `bimdown build` from surrounding walls, curtain walls, room separators, and structure walls using a half-edge face tracing algorithm. The generated `space.svg` contains `<polygon>` elements whose IDs match the space CSV rows.
200
200
  - **Grid/Level**: Global reference data with coordinates in CSV.
201
201
 
202
202
  ### Unified Foundation Type
@@ -222,7 +222,7 @@ MEP networks form a **bipartite graph**: `mep_curve` (duct, pipe, cable_tray, co
222
222
  **AI authoring workflow**:
223
223
  1. Place equipment and terminals (anchors)
224
224
  2. Draw duct/pipe segments connecting them (endpoint coordinates)
225
- 3. Call CLI `validate` / `resolve-topology` — this detects coincident endpoints, generates `mep_node` entries at junctions, and back-fills `start_node_id`/`end_node_id` on each segment. Warns about disconnected endpoints.
225
+ 3. Call CLI `build` / `resolve-topology` — this detects coincident endpoints, generates `mep_node` entries at junctions, and back-fills `start_node_id`/`end_node_id` on each segment. Warns about disconnected endpoints.
226
226
 
227
227
  **Revit export**: Fittings and accessories are exported as `mep_node`. Curve endpoints are taken from connector positions (not `LocationCurve`), so they naturally coincide with node positions. `start_node_id`/`end_node_id` are derived from Revit's connector relationships.
228
228
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "bimdown-cli",
3
- "version": "0.2.1",
3
+ "version": "0.2.2",
4
4
  "description": "An open-source, AI-native building data format using CSV and SVG.",
5
5
  "author": "NovaShang",
6
6
  "license": "MIT",
@@ -41,6 +41,7 @@
41
41
  "@duckdb/node-api": "^1.5.0-r.1",
42
42
  "commander": "^13.1.0",
43
43
  "fast-xml-parser": "^5.2.0",
44
+ "fflate": "^0.8.2",
44
45
  "sharp": "^0.34.5",
45
46
  "yaml": "^2.7.0"
46
47
  },