Layouts and SVG Site Maps

For a Layout subproject — a plotted development — Vruksha lets you upload the actual SVG site map and turn it into an interactive plan. Each plot shape and amenity in the drawing is matched to its record automatically, by id, using your naming conventions — so you prepare the drawing once, and the system does the linking. The result is a live, colour-coded map where every plot shows its current sales status at a glance.

This is what powers the visual "pick a plot" experience: a buyer or sales staff member can look at the map and instantly see which plots are available, blocked, booked, or sold.

Step 1 — Upload the SVG

1. Open the Layout subproject and go to its SVG / Layouts section.
2. Click Upload SVG.
3. Choose your .svg site map file and give it a name (for example, "Phase 1 Site Plan").
4. Optionally record floor number, dimensions, and display order (useful when a subproject has several maps).
5. Save. The file is stored against the subproject and an upload entry is written to the audit log.

You can upload more than one SVG per subproject — for instance, separate sheets for different phases or floors — and reorder them with the display-order field. When you open the layout viewer you pick which sheet to view from a Layout dropdown.

SVG file requirements

• The file must be a real .svg vector file — other image formats are rejected.
• The file must be 10 MB or smaller.
• For safety, the system strips any scripts or interactive code from the SVG when it renders the map, so only the drawing itself is shown.

tip

Use a clean SVG where each plot is a separate, identifiable shape with an id that follows your naming convention (see Steps 2 & 3). The clearer and more consistently named the source drawing, the more plots map automatically.

Step 2 & 3 — How plots map to units (automatically)

You do not trace plots by hand. Instead, the map links each shape in the SVG to a unit record by its id, using the prefixes you set in Settings → Naming Conventions:

• SVG Unit Prefix — for example plot. A shape with the id plot-12 (or plot_12) is matched to the unit whose number is 12 in this subproject.
• SVG Amenity Prefix — the equivalent for amenities (see Step 4).
• Group IDs (optional) — if your drawing groups all plots under one <g> and all amenities under another, you can name those groups so matching only looks inside the right group.

When you open the layout, the viewer reads the SVG and resolves the matches:

• A shape whose id matches a real unit number becomes a mapped plot — it takes the unit's status colour and shows the unit's details on hover.
• A shape that uses the prefix but has no matching unit is listed as Pending ("unit not yet created"). Create the unit with that number and it maps on the next view.

The right-hand Units panel shows the running tally — how many plots are Created (mapped) and how many are Pending.

note

The shape is just the drawing of the plot. The plot's real data — number, area, price, status, owner — lives on the unit record. The id on the shape is what connects the picture to the data.

Editing or removing a mapping

Because the link is driven by the id on the shape and the unit number, you change a mapping by changing one of those — there is no in-app polygon editor:

• To re-point a plot to a different unit, change the shape's id in the source SVG (or the unit's number), then re-upload the corrected SVG.
• To unmap a shape, rename or remove its prefixed id so it no longer matches a unit, then re-upload — or simply leave the unit uncreated, in which case the shape stays Pending and is shown as an empty plot.
• A plot recolours on its own as the unit moves through its lifecycle; you never edit colours on the drawing (see Keeping the map in sync).

Step 4 — Amenity markers

Amenities work the same way as plots: a shape in the SVG whose id uses the SVG Amenity Prefix (for example amen-clubhouse) is recognised as that amenity's marker on the map. The right-hand Amenities panel lists everything it matched. Clicking an amenity in the panel zooms and highlights its location on the map; an amenity that has no matching shape in the drawing is flagged as not mapped. As with plots, you adjust amenity markers by fixing the ids in the source SVG and re-uploading — there is no drag-to-place marker tool.

The interactive layout and status colour legend

Once polygons are mapped, the layout viewer renders the SVG with every plot coloured according to its unit's current status. A status colour legend beside the map tells you what each colour means.

The colours come from your organization's status configuration, so the legend reflects exactly the statuses your units use. Conceptually it works like this:

Unit status	Meaning on the map
Available	Open for booking — the buyer can pick it.
Blocked	Temporarily reserved — not selectable.
Booked	Booking confirmed — not available.
Advanced / Registered	Sold — not available.
Draft / Cancelled	Not shown as sellable.
Frozen	Held for an issue / legal reason — not available.

The exact colours and the statuses shown are driven by your configuration — the legend on screen is the source of truth. Hovering a plot shows a tooltip card with that unit's key details. For the meaning of each unit status, see the Unit lifecycle.

Keeping the map in sync

Because each plot is linked to a live unit, the map updates as units move through their lifecycle — when a sale books a unit, its plot recolours automatically. You don't recolour the map by hand; the status drives the colour.

Working with the layout viewer

Open a layout with View Layout. The viewer behaves like an online map:

• Pan by dragging, zoom with the scroll wheel, the + / − buttons, or a double-click, and Reset view to fit the whole plan again.
• Hover a plot for a tooltip of the unit's key details; click a plot to jump straight to that unit's record.
• Click a row in the Units or Amenities panel to highlight and zoom to that element on the map.

Downloading the map

Use the Download menu in the viewer to save the current map as an SVG or a PNG image. Both are stamped with the subproject name and the date/time they were generated — handy for brochures, site boards, or sharing a snapshot of current availability.

Advanced: replacing and managing SVGs

A subproject can hold several layouts, and you manage them from the SVG / Layouts section:

• Add another layout — upload a new .svg (Step 1). Use display order to control the sequence they appear in the Layout dropdown.
• Update a layout's details — its name, floor number, dimensions, or display order can be edited without re-uploading the file.
• Replace a drawing — there is no in-place "swap file" action. To replace a layout's artwork, upload the corrected SVG as a new layout and delete the old one. This is also how you apply a re-numbered or re-grouped drawing so more plots map automatically.
• Remove a layout — deleting an SVG is a soft delete: the layout stops appearing in the viewer, but the units it referenced are untouched, and the action is recorded in the audit log.

note

Editing or deleting a layout needs the layout-edit permission, and uploading needs the layout-upload permission. If you don't see these actions, ask an Admin.

See also

• Subprojects overview
• Create a subproject
• Create a unit
• Unit lifecycle