brepjs-bim 0.24.0 → 0.24.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.
- package/README.md +12 -3
- package/dist/brepjs-bim.cjs +3734 -2007
- package/dist/brepjs-bim.js +3732 -2005
- package/dist/elementFns/placedGeometry.d.ts +1 -1
- package/dist/familiesAdapter.d.ts +15 -3
- package/dist/familiesFrame.d.ts +11 -0
- package/dist/familiesProductBody.d.ts +40 -0
- package/dist/ifc-writer/tessellationWriter.d.ts +1 -1
- package/dist/import/placement.d.ts +1 -46
- package/dist/import/spfReader.d.ts +3 -3
- package/dist/index.d.ts +1 -1
- package/dist/placementFrame.d.ts +47 -36
- package/dist/rigidPlacement.d.ts +2 -2
- package/package.json +3 -3
package/README.md
CHANGED
|
@@ -95,9 +95,16 @@ otherwise supplied. Existing non-semantic Families archetypes continue to use th
|
|
|
95
95
|
registry beneath Bridge Parts. Bridge, Bridge Part, and Earthworks Fill require IFC4X3; `fromIfc`
|
|
96
96
|
reconstructs their civil spatial hierarchy, direct containment, and typed Earthworks inventory.
|
|
97
97
|
|
|
98
|
-
|
|
99
|
-
|
|
100
|
-
|
|
98
|
+
Civil-semantic wall and railing routes require `bodyEvaluator` (or the
|
|
99
|
+
`proxyEvaluator` fallback) so the adapter can verify the authored Product Body. Missing the
|
|
100
|
+
evaluator is `FAMILIES_PRODUCT_BODY_EVALUATOR_REQUIRED` (element path and mapped category); the
|
|
101
|
+
adapter does not silently keep a parametric envelope. Conventional archetype walls and railings
|
|
102
|
+
stay specification-authoritative and do not need an evaluator. When the evaluator is present, the
|
|
103
|
+
adapter applies registered wall openings to the parametric candidate, then compares that candidate
|
|
104
|
+
with the evaluated source in Product-local coordinates. Coincident bodies retain editable
|
|
105
|
+
parametric IFC; compound, voided, or otherwise different bodies retain their typed Wall or Railing
|
|
106
|
+
classification and export every authoritative item as tessellation. The evaluator's source handles
|
|
107
|
+
remain borrowed. Other typed civil routes continue to use their semantic envelope dimensions.
|
|
101
108
|
|
|
102
109
|
This is deliberately not a claim of complete IFC infrastructure coverage or unchanged parity with
|
|
103
110
|
the full scratch prototype. Member and Sign remain outside the profile: without `proxyEvaluator`
|
|
@@ -172,6 +179,8 @@ warnings travel inside the payload rather than throwing.
|
|
|
172
179
|
Each `add*` call parses and validates its spec and stores a typed `BimElement` keyed by a `LocalId`.
|
|
173
180
|
Parametric physical elements build an analytical brepjs solid; civil spatial elements are body-less,
|
|
174
181
|
and arbitrary-body products such as Earthworks Fill take ownership of a validated authored solid.
|
|
182
|
+
Families-projected civil walls and railings retain evaluated authored solids when their Bodies do
|
|
183
|
+
not coincide with the post-opening parametric candidate.
|
|
175
184
|
The IFC writer walks the model, applies placement, and emits schema-correct IFC entities; the
|
|
176
185
|
importer is the inverse. No kernel/WASM changes are required.
|
|
177
186
|
|