This branch carried v0.8.0's strict `[tool.ty.rules] all = "error"` config but not the source fixes that were made upstream to satisfy it, so both ci-lint ty gates were failing: `poe ty-ios` reported 256 diagnostics and `poe ty-bonsai` 258. Both are now clean. Most fixes are ported from v0.8.0 and follow two idioms: initialise a name before a conditional that may not bind it (plus an `assert` where the invariant is real but not provable), and close an exhaustive `if`/`elif` chain with `else: assert False, <discriminant>`. The branch's own newer accessors are preserved throughout - `.file`, `.declaration`, `file.types()`, `get_max_id()` are kept rather than reverted to `wrapped_data.*`, and non-ty upstream changes (notably the in-progress geometry cache removal) are deliberately not pulled in. Notable fixes that are not straight ports: * ifcopenshell_wrapper.pyi: `entity_instance.file` was declared as `def file(self) -> file`, where the property name shadows the `class file` below it, so the annotation resolved to `Unknown`. Every `element.file` in the codebase was therefore unchecked. Qualifying it to `ifcopenshell.file` restores `.schema` to its Literal union and surfaces no new diagnostics. * model/wall.py: a duplicated merge fragment in the void-straddle path ran an always-true `if void_straddles:` that read `new_opening` from the mutually exclusive branch (stale value, or NameError on the first iteration), followed by an unreachable duplicate `elif`. Removing it makes the file match v0.8.0. * light/operator.py: upstream's own fix unpacks three targets from two values and raises ValueError unconditionally; corrected to `None, None, None`. * assign_system.py, validate.py, geom/main.py: walrus-in-genexp is valid at runtime (PEP 572 binds in the containing scope) but ty does not model it; rewritten as explicit loops, matching upstream. Verified: poe ty-ios, poe ty-bonsai, ruff check src/ nix/, black --check ., and compileall -W error at py3.10 (ifcopenshell-python) and py3.11 (bonsai). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
ifc5d
Description
Ifc5D is a collection of utilities of manipulating cost-related data to and from formats, reports, and optimisation engines.
Currently supported:
- CSV to IFC
- IFC to XLSX
- IFC to CSV
- IFC to ODS
Planned (would you like to contribute? Please reach out!):
- IFC to PDF
- ODS to CSV
- XLSX to CSV
- IFC to Graph
Usage CSV to IFC
Simple example:
import ifc5d.csv2ifc
csv2ifc = ifc5d.csv2ifc.Csv2Ifc(csv_filepath, ifc_file)
csv2ifc.execute()
See example files as a CSV file format reference:
- Ex1 - BoQ without query.csv (a simple Bill of Quantities)
- Ex2 - SoR.csv (a simple Schedule of Rates)
- Ex3 - BoQ with query.csv (a simple BoQ with the query function)
- Ex4 - BoQ with description.csv (a simple BoQ with description column)
- Ex5 - SoR_with_description.csv (a simple SoR with description column)
- Ex6 - BoQ with categories.csv (a simple BoQ with categories columns)
- Ex7 - BoQ with Rates.csv (a simple BoQ that connect to an existing SoR. It needs an already loaded SoR.)
- Ex8 - Boq with formula.csv (a simple BoQ with formula field used to calculate quantities when specified)
sample_cost_schedule_house_FR.csv/.odsschedule.csv,rates.csv(schedule of rates example)
Some notes on the format:
- Empty lines are ignored.
- Importing ods/xlsx is not currently supported, only csv.
- 'Property', 'Query' columns are required only for non-schedule of rates cost schedules.
- 'Index' was preferred for import hierarchy source over 'Hierarchy' as it's easier to edit from the table view.
- In non-SoR if cost values are not provided in any way and cost item has subitems, then
SUM()will added automatically as it's cost value.
MixingSUM()cost items and items with their own value is not supported.
Columns Description
General Columns
- 'Index' - is a hierarchy depth that's used for building hierarchy during csv import. Starts from 1.
E.g. root items of the same level have index '1', their children have '2', etc. - 'Name' - IfcCostItem.Name.
Some older exports may have 'Description' field instead of 'Name', it is safe to just rename it. - 'Identification' - IfcCostItem.Identification.
- 'Unit' - IfcCostValue unit, should be provided as a unit symbol.
E.g. 'm2', 'm3', 'kg', etc. - 'Value' - overall cost value to assign to IfcCostItem.
- All other columns that are not mentioned in this list or the one below will be interpeted as cost value categories.
Note that if 'Value' is provided, it takes priority over subcategories.
Non-schedule of rates columns:
- 'Quantity' - total cost item quantity.
- 'Property' - quantity name that should be added to IfcCostItem from 'Query' elements.
If 'Query' is provided, 'Property' can be left empty or set to "COUNT" to count queried elements. - 'Query' - selector query for elements to assign to IfcCostItem.
If query is provided, it takes priority over 'Quantity' (using both is not supported).
Exported informational columns (not used for import)
- 'Hierarchy' is just an informational column that doesn't affect the import.
E.g. '1', '1.1', '1.1.1', etc. - 'Id' - IfcCostItem.id
- 'RateSubtotal' - all IfcCostItem specific costs, not including subitem costs.
- 'TotalPrice' - IfcCostItem total cost, including subitem sum calculations.
Usage IFC to CSV, ODS, XSLS
Simple example:
import ifc5d.ifc5Dspreadsheet
# csv.
writer = ifc5d.ifc5Dspreadsheet.Ifc5DCsvWriter(ifc_file, csv_dir)
writer.write()
# ods.
writer = ifc5d.ifc5Dspreadsheet.Ifc5DOdsWriter(ifc_file, ods_dir)
writer.write()
# xlsx.
writer = ifc5d.ifc5Dspreadsheet.Ifc5DXlsxWriter(ifc_file, xlsx_dir)
writer.write()
CLI app for converting IFC files to CSV, ODS or XLSX format.
Usage: python ifc5Dspreadsheet.py input_file output_dir [-l log_file] [-f format_type]
Arguments: input_file (str): The path to the input IFC file to process. output_dir (str): The output directory.
Options: -l, --log log_file (str): The path to the file where errors should be logged. Default is process.log. -f, --format format_type (str): The output format to export in (csv/ods/xlsx). Default is csv.
Examples: python ifc5Dspreadsheet.py "C:\Users\Dev-Machine\Desktop\test_cost.ifc" rev_01_schedule -l error.log -f ODS python ifc5Dspreadsheet.py "C:\Users\Username\Desktop\test_cost.ifc" "C:\Users\Username\Desktop" -l error.log -f CSV
Scripting:
Example for ODS exports:
import ifcopenshell
from ifc5d.ifc5Dspreadsheet import Ifc5DOdsWriter
file = "path_to_file/file.ifc"
path = "directory/cost_schedule"
writer = Ifc5DOdsWriter(file=file, output=path)
writer.write()