Plot Assessment Guide

Vastu Assessment for New-Build Plots

Surveyed site boundary, orientation measurement, 8-zone analysis, 81-pada Mandala overlay, evaluation of proposed room layouts, and griha pravesh muhurta for new construction.

Site boundary versus building footprint

A plot assessment typically involves two distinct polygons at different stages of a project:

  • Site boundary polygon: the legal property boundary — the outer perimeter of the land parcel. This is used to assess the site's overall Vastu qualities: zone proportions, Brahmasthan, and entrance orientation relative to the land itself.
  • Building footprint polygon: the outer wall line of the proposed building on the site. Used when a floor plan is available but construction has not begun. This tells you the building's zone map and whether the proposed footprint is well-positioned on the site.
  • Floor plan polygons: once a preliminary floor plan exists, room polygons can be supplied to rooms[] to evaluate room placement against zones.
You can run /vastu/plan/analyze multiple times with the same entrance but different plot polygons — first the site boundary, then the building footprint — to compare site-level and building-level zone qualities at different design stages.

Measurement checklist

  • Obtain the site boundary coordinates from the survey plan or title document. Convert to Cartesian vertices (x, y) in a consistent unit (metres preferred), with one corner as origin (0, 0).
  • Establish the True North reference: measure the True North bearing of your plan's +Y (plan-up) axis, clockwise, using a surveyor's compass or GPS (0 if plan-up already points True North). This is north_angle.
  • For entrance direction: identify the proposed main gate or main door bearing, clockwise from plan-up (with north_angle 0 that is a True North bearing). If not yet decided, run the analysis with candidate bearings to compare results.
  • For slope, drainage and soil: these are outside the API's scope — record them separately and address in the architect/engineer brief.

Synthetic teaching example

SYNTHETIC teaching fixture only. The 20×10 rectangle below is the standard fixture from the VedIntel™ Vastu API test suite. It represents no real property. It demonstrates request structure; it does not constitute a real plot assessment.
Site-only analysis (no rooms yet) — SYNTHETIC
POST /api/v1/vastu/plan/analyze
X-API-Key: YOUR_API_KEY
Content-Type: application/json

{
  "plot": [
    {"x": 0,  "y": 0},
    {"x": 20, "y": 0},
    {"x": 20, "y": 10},
    {"x": 0,  "y": 10}
  ],
  "entrance": {"bearing_deg": 45},
  "north_angle": 0
}
With proposed room layout added — SYNTHETIC
{
  "plot": [
    {"x": 0,  "y": 0}, {"x": 20, "y": 0},
    {"x": 20, "y": 10}, {"x": 0,  "y": 10}
  ],
  "rooms": [
    {
      "name": "Master Bedroom",
      "polygon": [
        {"x": 0, "y": 5}, {"x": 8, "y": 5},
        {"x": 8, "y": 10}, {"x": 0, "y": 10}
      ]
    }
  ],
  "entrance": {"bearing_deg": 45},
  "north_angle": 0
}

Recommended endpoint sequence

A typical new-build plot assessment progresses through these stages:

StageEndpointWhat you get
Site boundary — before floor plan/vastu/zones8-zone proportions of the raw plot
Site boundary/vastu/mandala81-pada Mandala grid over the site boundary
Site boundary/vastu/brahmasthanCentral zone cell — no rooms yet, so obstruction=false
Site boundary + entrance/vastu/entranceEntrance direction and applicable rules
Full site analysis/vastu/plan/analyzeAll of the above in one call
Proposed floor plan available/vastu/plan/analyze (with rooms)Zone assignment per proposed room
Ceremony planned/vastu/muhurta (griha_pravesh)Auspicious housewarming windows for a date

Using the Vastu Purusha Mandala overlay

The /vastu/mandala endpoint returns the 9×9 grid of 81 padas overlaid on the plot boundary. Each pada includes:

  • pada_id, row and col: 1-indexed on the north-up grid, row 1 on the south edge and column 1 on the west edge, so R1C1 is the south-west corner pada and R5C5 the centre
  • zone: the 8-direction zone of this pada, or BRAHMA for the 9 centre padas
  • in_plot: whether the pada lies inside the plot
  • is_brahmasthan: whether this pada is in the central 3×3 Brahmasthan cluster
  • polygon: the geometric boundary of this pada clipped to the plot
  • area: absolute area of this pada inside the plot, in squared input units; also area_exact when rounding collapsed a non-zero area to zero
Deity assignments: Full deity and planet assignments for all 81 padas are deferred to a future API version (astro_vastu_rules_version: "0.0.0"). The current Mandala endpoint returns geometry only. Traditional assignment tables are available in primary Vastu texts for practitioners who wish to overlay them manually.

Evaluating proposed room layouts

Once a preliminary floor plan is available, supply room polygons to /vastu/plan/analyze or /vastu/room-placement. The API assigns each room to its directional zone and evaluates applicable placement rules.

You can iterate: adjust room polygon vertices, re-submit, and compare the resulting zone assignments and rule findings across design alternatives. The API has no memory between calls — each is stateless and independently computed.

What the API assesses vs what it does not: The API evaluates directional zone assignment and Brahmasthan proximity. It does not assess structural load paths, thermal performance, natural lighting, ventilation adequacy, accessibility compliance, or legal setback requirements.

Muhurta for ceremonies

The Vastu muhurta endpoint computes auspicious timing from Swiss Ephemeris planetary positions for the ceremony's date and location — not from birth data.

Griha pravesh muhurta request
POST /api/v1/vastu/muhurta
X-API-Key: YOUR_API_KEY
Content-Type: application/json

{
  "event_type": "griha_pravesh",
  "date": "DD/MM/YYYY",
  "lat": <ceremony location latitude>,
  "lon": <ceremony location longitude>,
  "tz": <UTC offset, e.g. 5.5 for IST>
}
Implemented vs not: Only griha_pravesh (housewarming) is live. bhoomi_puja (ground-breaking), griha_arambha (construction start), vastu_puja (Vastu ritual) and griha_pravesh_renovation return HTTP 501 NOT_YET_IMPLEMENTED.

Muhurta selection involves assessment of the full ceremony chart (Lagna, tithi, nakshatra, yoga, karana and planetary positions at the auspicious hour). The API provides computed windows; a qualified Jyotishi's review of the specific muhurta is advisable for important events.

What is outside API scope

Slope and drainage: The API has no concept of topography. Slope, drainage, groundwater and soil quality require on-site survey and civil engineering assessment.
Legal setbacks and planning consent: Zone rules derived from the API do not substitute for local planning regulations, building codes or surveyor/architect advice on legal setback distances.
Structural safety: No structural engineering analysis is performed. Load paths, foundation requirements and structural elements are outside API scope.
Natal Vastu overlay: Linking birth chart planetary positions to spatial zones (a Phase 2 feature) is not available. astro_vastu_rules_version: "0.0.0".

Related guides