Exporting a floor plan as JSON

Why keep your own backup

A floor plan is working time. A survey done once should not depend on a single system staying available. One JSON file per property in your own storage is cheap insurance.

For landlords and managing agents there is a second reason: traceability. Saving the state of a plan at a point in time lets you later evidence what a floor area in a tenancy agreement was based on.

• Keep one backup file per property and storey
• Name files with property, storey and date
• Save the old state before major alterations
• JSON is text — still readable many years from now

Analysis across a portfolio

Because JSON is structured, it answers questions that would otherwise be manual work: what is the average kitchen size across the portfolio? How many flats have an internal bathroom? How does living area distribute across room sizes?

Such analysis needs no heavy tooling. A short script is enough, because every file shares the same shape and already contains the computed areas.

Where the format stops

JSON is not something to look at. Neither prospects nor colleagues can use it — for any kind of communication you need a PDF or an image.

And it is not an industry exchange standard: it describes this plan in its own structure. OpenImmo XML exists for agency systems, DXF for design software.