Novi Kvadrat

An in-browser SVG editor turns a scanned plan into rooms with measured areas, so each photo lands in the room it shows, with its camera angle.

1. Upload the plan; one line locks the scale.
2. Trace the walls; corners snap to 90°.
3. Closed loops become rooms, with their areas.
4. Doors and windows snap onto the walls.
5. Photos land in their rooms, cameras aimed.
6. The plan goes live on the listing.

Walls become rooms through a planar-graph polygonizer: it walks the faces of the wall graph, orients each by its signed area and joins holes to their rooms. Photos drop into rooms by point-in-polygon tests, not bounding boxes, and each camera carries a bearing and a 45, 65 or 90° field of view, so a visitor sees where a photo was taken.

It ships in rent and sale, in the admin console and the business portal, in five languages.

A developer sells named buildings. The map knows only outlines, often more of them than there are buildings, and none of them named. Site Plan Studio joins the two, and it is live in the staff admin.

1. Upload the developer’s site plan and set north.
2. Trace each building on the plan.
3. Link each traced shape to its building.
4. Group the map’s outlines under the buildings they belong to.
5. Pin the plan to the map.
6. A buyer picks a building by what is left in it.the public view is a design

Nothing on the map is thrown away: the studio groups the map’s outlines under the developer’s buildings and keeps the old rows. On the project page, the plan is meant to show every building with what is left in it, so a buyer starts from what is for sale.

A tap on a 3D building must pick the right storey, even half hidden behind another one. The approach was measured before it was built: a throwaway spike ran 81 headless GPU runs and 199 renders.

1. Building footprints come in.
2. Storeys extrude, slab by slab.
3. A pick ray finds the first visible storey.
4. That storey unfolds into its floor plate.
5. BD0–BD9 run in the staff studio.
6. The public 3D viewer waits behind a flag.

Plain map extrusions picked the correct storey 99.65% of the time; 5,400 storeys updated in about 123 ms, and a whole floor plate opened in 13 ms. The numbers come from one desktop GPU, headless, so they say nothing yet about a phone.

One bug taught the model something. On one map tile, 40 basemap features held 750 building polygons, and one feature id spanned 2.2 km, so hiding a duplicate by its id hid 17 unrelated buildings. Duplicates are now suppressed by their geometry, and the basemap is never hidden.

In the staff admin, the 3D Buildings Studio groups the map’s parts into the developer’s buildings, stacks their storeys, traces a whole-floor plate and links each storey to its units. The public viewer stays behind a flag.

A small model returns validated filters, never listings, and a deterministic fallback stands behind it. The model shapes the search; it never writes the results.

The query goes to an edge function with its input capped at 500 characters and its answer at 400 tokens. With no key set, the page falls back without a word. Projects also carry 1,024-dimension embeddings for semantic search.