How this calculation works
Subtract the entered insets from both ends of each dimension. Count aligned point positions inclusively at the allowed endpoints, multiply rows by positions per row and compare the other row direction. Negative usable spans give no positions.
Rows = floor(usable cross span / row spacing)+1; positions per row = floor(usable run / plant spacing)+1A worked example
For 100 × 60 m, 2 m insets, 10 m between rows and 8 m within rows, lengthwise rows have 6 × 13 = 78 positions. Rotating the row direction gives 10 × 8 = 80 positions under the same stated inset conventions.
Good to know
A rectangular aligned-point grid with supplied distances, not agronomic spacing or maximum packing. No species recommendation, canopy clearance beyond the entered inset, paths, irregular boundaries, yield or survival is inferred. The row table shows at most 40 rows while the full count remains available.
Reference: NIST: exact international-foot and acre factors (opens in a new tab) ↗
Check the land-unit definitions and sources
The standard factors use the international foot and an acre of 43,560 sq ft. Cent means 1/100 acre; gunta means 1/40 acre; the selected Chennai ground means 2,400 sq ft.
The Assam report defines bigha as 14,400 sq ft, katha as 2,880 sq ft and lecha as 144 sq ft. The cited West Bengal court order mentions a 720-sq-ft katha convention. These are explicit presets, not an automatic definition for every record or every place using the same name. Match your record to the stated convention, or use its verified custom factor.
- NIST: exact international-foot and acre factors (opens in a new tab) ↗
- API Setu MDDS: acre/cent and acre/gunta relationships (opens in a new tab) ↗
- Greater Chennai Corporation: one ground is 2,400 sq ft (opens in a new tab) ↗
- Government of Assam AIRBMP framework: section 7.2, page 28 (bigha, katha and lecha) (opens in a new tab) ↗
- Supreme Court order, 7 May 2025: paragraph 2, page 2 (West Bengal katha) (opens in a new tab) ↗
The acre relationships are converted using exact base factors. Rounded or unrelated regional values in a reference table are not substituted for these definitions.
Points and the intervals between them are not the same count
Across a usable 96 m run, spacing 8 m fits twelve intervals and thirteen point positions when both endpoints are permitted. Across a usable 56 m width, spacing 10 m fits five intervals and six row positions. Multiplying gives 78 aligned points for the demonstration layout.
Dividing the full 6,000 m² plot by 10 × 8 would give 75 nominal spacing rectangles. That is a different boundary convention: this tool counts points within entered insets, not whole spacing cells that must fit inside the plot. Neither result establishes an appropriate crop layout without the relevant assumptions.
The drip lateral calculator shares the concept of entered rows but answers a pipe-quantity question. Plant positions are not automatically emitters, and an allowance on tubing does not add plant positions or change the spacing.
Compare orientation without claiming an optimum
The supplied 100 × 60 m example has 78 positions when rows run lengthwise and 80 when the row direction is rotated. The direction comparison uses the same numerical row-end and cross-row inset assumptions. If those two insets differ, rotation changes which physical boundary receives each inset.
A narrow usable span of zero can contain one permitted point. A negative usable span contains none. This endpoint convention is shown explicitly; it does not assume canopy clearance, paths, irrigation access or any legal setback beyond what you entered.
The grid is rectangular and aligned. Staggered or triangular layouts, irregular exclusions and crop-specific requirements are outside this calculation. A higher geometric count is not a crop-spacing recommendation, a yield forecast or proof of maximum packing.
A few questions, answered
Are the defaults recommended for coconut, mango or teak?
No. They are editable geometry examples, with no species or agronomic recommendation.
Why show only 40 rows in the table?
The table is capped for a fast usable page. The full arithmetic row and point counts are still calculated.
Is the point at the far boundary counted?
It is counted if its coordinate is within the permitted inset boundary, including exact equality. The next point beyond that boundary is excluded.