deejoin/ifcdb

IFCDB is a database system built around the IFC format, the open standard used in the construction industry to describe buildings, their parts, and how those parts relate to each other. It is made by Shanghai DeeJoin Information Technology, and the README presents it as a way to keep an entire project's BIM data, which is short for Building Information Model, in one queryable place rather than scattered across separate model files. Under the hood the system uses a cloud native architecture that mixes a NoSQL store with a NewSQL store, then exposes a standard SQL interface on top so that attribute data, geometry, and the relations between building components can all be read with the same query language. The README also says IFCDB has an AI model wired in, so a user can type a request in natural language, for example asking for a count or a volume, and the system turns it into the right query. The README lists five features. Multi model visualization lets the user merge any number of sub models or models from different professions into one 3D view, with sectioning, measurement, transparency, and isolation controls. Properties and property set management stores attributes for every component and supports natural language queries such as range filters or counts by IFC type, with results that can be shown as pie charts. Sub model export lets the user pull components from one or many models and write them out as a fresh IFC file that other software can open or build on. Real time engineering quantity calculation runs the same kind of multi condition query but is aimed at quantity takeoff, the construction task of counting how much material a design needs. The README says this shortens manual takeoff work from hours to minutes and is especially suited to models with a lot of steel reinforcement bars. Collision detection runs across the full merged model using a spatial index, reports the location, the components involved, and the overlap volume, and can jump the 3D view to each clash. The README is short, lists no install steps, no license, and no command examples, so it reads more as a product overview than a developer guide.