Reading floor plans, OpenImmo and IFC — in the browser, without upload
Three ways in, one report out. A floor plan as an image or PDF, the agent export your software already writes, or an IFC model. Reading happens on the device — there is no endpoint the file could go to.
The difference between the three routes is not convenience but how much truth travels with them. An IFC model carries rooms as named objects with net floor areas. An OpenImmo XML carries the fields somebody filled in. A floor plan image carries lines from which areas must first be read — and that reading can be wrong.
Try it on one address →What is computed — and where it stops
So there is a cross-check rather than a leap of faith: the square metres read are held against the stated total floor area. Two independent statements in the same document. If they agree, no room is missing and none counted twice; if they diverge, the screen says so.
Frequently asked
Is my file uploaded?
No. Reading, computing and the PDF export all run in the browser. A server route would send us the address and the floor plan — at exactly the point where nobody expects it.
What happens without a floor plan?
The report is still produced, using an example layout inside the measured building volume — and it says so in a sentence above the table, not as a footnote. The volume, the neighbouring heights and the sun path are genuinely measured even then.
Does it read every floor plan?
No. Scanned plans without a text layer, very small labels and title blocks that look like rooms are the known cases. That is why there is a correction panel: every line read can be changed before anything is computed.
Can I push the result back into my CRM?
Not today — that route is the next step, and it would be dishonest to advertise it as if it existed.
All measurements · For agents & developers · The light check
Everything in the browser: no upload, no endpoint, no server call. IFC via web-ifc, floor-plan reading local. Values read can be edited before anything is computed.