Skip to main content

bimforge

A standalone CAD/BIM toolkit in Python: measure 2D plan sheets, author parametric IFC models, roll them up into quantities, stage them in 4D/5D, and produce control, layout and structure sheets — with no dependency on any estimating product.

  • bimforge.bim — DXF → IFC authoring (IFC4X3 by default, exact extrusions and alignment sweeps), IFC → quantity takeoff, plan-sheet calibration and vector measurement, georeferencing, 3D KML/KMZ for Google Earth, 4D schedule embed/read-back (IfcWorkSchedule) and 5D cost and resource loading (IfcCostSchedule). Schedule readers for GanttWarrior JSON, Primavera P6 XER and MS Project MSPDI live here too.
  • bimforge.author — the structure-family kernel: alignments, section prisms, battered walls, reinforcing bars, plates, saddles, spillways, standard-plan families, with quantities taken from the emitted geometry and never from a parallel formula.
  • bimforge.sheets and bimforge.cad — sheet production and the org-neutral DXF/KML/geo engine, styled by pluggable style packs.
  • bimforge.terrain — terrain grids, watertight terrain solids and excavation carves from point clouds and contours.

Install

pip install bimforge            # IFC stack included (ifcopenshell, ezdxf, shapely, pyproj, numpy)
pip install 'bimforge[all]'     # + PDF plan sheets, matplotlib drawing, build123d exact solids
pip install 'bimforge[terrain]' # + point-cloud / mesh terrain

Two CLIs ship with the package:

est-bim --help      # dxf2bim, ifc2dxf, takeoff, schedule, cost5d, kml, calibrate, measure, build, ...
est-sheets --help   # control / layout / structure sheet production

Style packs

CAD styling (title-block borders, layer colours, KML and IFC surface styles) comes from a style pack: a package or directory with templates/*.dxf and an optional styles.yaml. Resolution is explicit argument → registered providers → built-in neutral defaults. Any installed distribution can register a provider through the bimforge.style_packs entry-point group (a zero-argument callable returning a pack spec or None); bimforge never imports the provider's package by name.

Fixture provenance

Test fixtures cite public sources or derive their quantities in-repo. They carry no employer bid numbers and no working-directory paths, and CI's de-org scan refuses a change that adds one.

License

Apache-2.0. See LICENSE and NOTICE. Security reports: SECURITY.md.

Metadata

Release files for bimforge 0.1.87

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for bimforge 0.1.87
File Size Uploaded Provenance Actions
bimforge-0.1.87.tar.gz 476.0 kB With provenance Details for bimforge-0.1.87.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for bimforge 0.1.87
File Interpreter ABI Platform Actions
bimforge-0.1.87-py3-none-any.whl Python 3 none any Details for bimforge-0.1.87-py3-none-any.whl

Total release size: 1.0 MB

Release files / bimforge-0.1.87.tar.gz

Download URL bimforge-0.1.87.tar.gz
Size 476.0 kB
Tags Source
SHA-256 checksum
How to use checksums
f0db723efec10f1cb64d38c97b679570442b2cbadd51f9b68bb8a3dad1007bec
BLAKE2b-256 checksum
How to use checksums
adf1bdc268b1f0a525db88bf3845041e3e6e8cc26bcaf11d5ab401685a9ca81e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 16, 2026.

Transparency log

Release files / bimforge-0.1.87-py3-none-any.whl

Download URL bimforge-0.1.87-py3-none-any.whl
Size 554.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
04a9ed4dbce46f6613cd85afd63a3114fc5046d282af454cd76bf9bb2524a579
BLAKE2b-256 checksum
How to use checksums
e1d3622543130aa5e265ee4f12acef8827be7ea9b5f8360c63612cb4a276ea21
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 16, 2026.

Transparency log

Security for bimforge 0.1.87

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for bimforge-0.1.87.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 16, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page