IFC export: a duct segment has no name, and its size is only in its swept profile

Aperta
  • Qualcosa non va?
#63 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
backend, data

Direzione di ricerca

Start at packages/bim-ifc/src/export.ts:575-579 and trace how the shared run export branch handles duct segments and fittings. Check the IFC output and existing property set and quantity conventions; the issue names no tests, so locate relevant export tests before running them. Done when exported segments have a readable name and size properties with units, with any length quantity handled if chosen.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement
The problem

As a mechanical engineer sending a model to a coordinator or estimator, I want each duct segment in the IFC file to say what it is and what size it is. Today a reader sees an unnamed IfcDuctSegment (observed):

#147=IFCDUCTSEGMENT('1HE0d5M_TMhQMiWOp8UG6D',$,$,$,$,#135,#146,$,$);

Its only property set is MutinyBIM_Organization (observed). The model stores {"shape":"rect","width":1168.4,"height":305}, and that size is only in the swept profile's dimensions. A schedule or takeoff tool that reads properties gets no size (inferred).

Where in the code (observed, at 94513ba): packages/bim-ifc/src/export.ts:575-579 passes null for the name and adds no size property. Fittings get a name ("90° elbow") from the catch-all branch, so segments are the odd one out.

An AI agent helped find this and ran the repro on its own machine against 94513ba; I reviewed the output.

What you would like to happen
  • A Name on each segment, for example its size and system ("46x12 Supply"). The exact words are up to the maintainers.
  • Its size as properties: width and height (or diameter) for a rectangular (or round) duct, in a standard pset if one fits. Otherwise in a MutinyBIM set, with units.
  • Optionally, its length in Qto_DuctSegmentBaseQuantities.
The shared idea underneath

Run segments are a kernel concept for every domain (duct, pipe, conduit, cable tray), and the export branch is shared. Writing a run's size and a readable name helps every trade (inferred).

Discipline

Mechanical

Area

Sheets, PDF or IFC

Engineering content
  • This involves an engineering calculation, code rule or design default (it will need review by a licensed professional).
Helping
  • I would like to work on this.
Lingua principale
TypeScript
Stelle
85
Fork
10
Merge medio
1h 28m
PR unite (30g)
20

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di permitzip/mutinybim

Tutte le issue di permitzip/mutinybim

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.