Skip to content
Get started

Crop spacing and rotation review

Calculate rectangular planting capacities and review occupancy conflicts, family intervals and missing history without inventing growing rules.

Input

Measured beds: id,name,length,width,unit,note B1,North bed,4,1.2,m,Rectangular measured bed. B2,South bed,3,1,m,Separate planting area. Planned crops: id,bed_id,crop,family,start,end,row_spacing,plant_spacing,note C1,B1,Carrots,APIACEAE,…

Result

The 4 m × 1.2 m north bed holds 160 rectangular carrot positions at 10 cm plant and 30 cm row spacing; the 10% path allowance leaves 144 planning positions. The beetroot interval overlaps the carrot interval. The previous carrot-family r…

A crop schedule can look plausible while occupying the same bed twice or relying on missing history. This tool combines supplied rectangular bed measurements, explicit plant spacing, inclusive dates and declared family intervals. Deterministic checks expose capacity assumptions, occupancy conflicts and rotation gaps. The AI reviews the source notes for spacing, timing, rotation and history concerns while preserving exact evidence.

Your texts, pages and images are processed on our own servers in the EU. Trust Center

Try it now Pricing

Who it is for

Market gardens, allotment coordinators, educational gardens and small growing teams maintaining explicit bed records. Suitable for planning and review from supplied rules, not crop-protection advice, yield prediction or an independently validated agronomic plan.

Typical uses

  • Calculate rectangular row and plant positions with explicit edge and path allowances.
  • Identify whole-bed occupancy overlaps across planned and historical records.
  • Check complete clear days between same-family crops against supplied rules.
  • Keep missing family rules and incomplete history visible.
  • Filter the displayed season without hiding conflicts with other supplied records.

Example

Input

Measured beds: id,name,length,width,unit,note B1,North bed,4,1.2,m,Rectangular measured bed. B2,South bed,3,1,m,Separate planting area. Planned crops: id,bed_id,crop,family,start,end,row_spacing,plant_spacing,note C1,B1,Carrots,APIACEAE,2027-03-01,2027-06-30,30,10,Check the supplied row spacing. C2,B1,Beetroot,AMARANTHACEAE,2027-06-15,2027-09-30,30,15,The planned dates overlap the earlier crop. C3,B2,Peas,FABACEAE,2027-03-01,2027-06-01,40,10,Review the available history. Recorded previous crops: id,bed_id,family,start,end,note H1,B1,APIACEAE,2026-03-01,2026-08-31,Recorded previous crop. Supplied family intervals: id,family,break_days,note T1,APIACEAE,365,Explicit supplied interval. T2,AMARANTHACEAE,180,Explicit supplied interval. Spacing and edge-margin unit: cm Edge margin on each side: 0 Planning allowance for paths: 10 Rotation-rule source: Explicit family rules Global clear-day interval: 365 Counts during occupancy conflicts: Flag conflicts and retain draft counts Historical coverage declaration: Declared incomplete Displayed decimal places: 3 Result order: Source order Show exact source notes: Enabled

Result

The 4 m × 1.2 m north bed holds 160 rectangular carrot positions at 10 cm plant and 30 cm row spacing; the 10% path allowance leaves 144 planning positions. The beetroot interval overlaps the carrot interval. The previous carrot-family record also leaves fewer than the supplied 365 clear days. The pea-family rule is missing, and the declared incomplete history remains visible.

A fixed example, shortened. Real results are AI-generated: please check them.

Price and limits

Price
usually 1–3 credits
Available with
Free, With package
Input limit
One page with up to 160,000 characters of HTML

Privacy

Processed on our own servers in the EU (Poland). Inputs and results are deleted after 7 days (Free) or 30 days (packages), or right after you see the result if you choose not to store them. Images are deleted right after processing.

In the API

Tool name: crop_planning. Create a job with POST /api/v1/jobs and fetch the result with GET /api/v1/jobs/{id}. You find your API key in your account.

curl -X POST https://do4u.eu/api/v1/jobs \
  -H "Authorization: Bearer d4u_…" -H "Content-Type: application/json" \
  -d '{"tool": "crop_planning", "url": "https://example.com/"}'

Full API documentation →

Questions and answers

Are crop families or rotation rules supplied automatically?

No. family is an explicit technical key and every rotation interval comes from the input or the selected global interval. Names do not authorize a botanical classification or a new agronomic rule.

How are dates compared?

Start and end dates are inclusive. Rotation counts complete clear days strictly between a previous end date and the following start date. A shared boundary date is an occupancy overlap.

Does a conflict-free result prove a safe or complete rotation?

No. Results cover only the supplied beds, records, family keys and rules. Missing external history, soil conditions, local restrictions and crop-protection requirements are not inferred.

Is my text stored?

Only as long as needed: 7 days on Free, 30 days with a package – or not at all if you choose not to store it. Processing happens on our own servers in the EU (Poland).

Can I use the result right away?

Results are AI-generated. Please read them before you publish or send them.