Guidance Lines Simulator
Drop your boundary + AB lines or pick a sample — we score AB Straight · AB Curve · Boundary · Topography · Auto-blocks · Concentric (pivot) on coverage, fuel, and time, then play back the winner.
Your uploaded files stay in your browser. Only the field boundary shape is sent to GeoPard to compute the plan, and it is not stored.
Guidance lines decide how much of your season goes into productive passes and how much is burned on turns, overlap, and re-driven ground. This simulator reads your field boundary (GeoJSON, KML, or a shapefile) or a built-in sample field, generates a complete drive plan for six approaches - AB Straight, AB Curve, Boundary Follow, Topography Follow, Auto-blocks, and Concentric for center-pivot fields - and scores every plan on coverage, overlap, path crossings, turnarounds, fuel, and time.
Headland passes, interior obstacles, and multi-part fields are handled the way an operator would drive them: the machine never leaves the boundary, works around exclusion zones, and finishes one block before moving to the next. Turnarounds match your equipment: half-circle U-turns, skip-row / lands patterns for trailed implements, or none if the driver decides at the headland. The playback shows the full route with wheel-track and swath rendering, so a bad plan is visible before it costs diesel.
When the plan looks right, export it as GeoJSON, KML, or a zipped shapefile and load it into your display. The full GeoPard platform goes further: it connects the same fields to yield and soil data, builds variable rate prescriptions, and lets the GeoPard AI Assistant reason through the agronomy with you.
AB lines are the reference lines a tractor autosteer system follows: you set point A and point B, and the machine drives parallel passes offset by the implement width. Straight AB lines suit rectangular fields; curved AB lines, boundary-following passes, and terrain-aware passes suit irregular shapes, contoured land, and fields with obstacles; concentric circles suit round center-pivot fields.
With the Concentric approach: full circular loops around the field centre, spaced one implement width apart, driven from the outer edge inward. A circle has no ends, so there are no headland U-turns. Between loops the machine lifts and steps one width inward along a single transition line. The loops stop when the radius gets too tight for your turn radius, leaving a small uncovered disc at the centre where the pivot tower stands. On a round field this cuts turnarounds to zero and fuel well below any parallel-pass plan; on a non-circular field its coverage collapses and the comparison table shows exactly why it loses.
GeoJSON (Polygon or MultiPolygon), KML, and shapefiles in EPSG:4326 (WGS84) — either the zip, or the loose .shp with its .dbf and .prj selected together. Boundaries with interior holes such as ponds or pylons are recognized and driven around. Existing AB lines can be imported alongside the boundary.
Your uploaded files (GeoJSON, KML, shapefiles) are read entirely in your browser and are never uploaded. To build the plan, only the field boundary shape (its outline coordinates, no file, no name) is sent to GeoPard, used to compute the guidance lines, and then discarded. It is not stored.
Yes. Set Turnarounds Style to Skip passes (lands): passes are worked in an offset order so every headland turn spans two or more implement widths — the wide, no-reverse turns operators run with trailed implements that cannot turn into the adjacent pass. The skip offset is derived from your implement width and turn radius. Coverage stays the same; the plan honestly shows the extra headland travel and the wheel-track crossings the pattern trades for feasible turns. On fields fragmented by obstacles the planner falls back to adjacent passes so the machine still works one area at a time.
Yes. Export the generated lines as GeoJSON, KML, or a zipped shapefile and import them into your terminal. From the full GeoPard platform you can also exchange files with John Deere Operations Center, CNH FieldOps, and AGCO / PTx FarmEngage, plus ISO-XML exports for other monitors.
Every plan reports total drive distance, coverage percent, overlap percent, path crossings, turn count, and a fuel and time estimate from your implement width, turn radius, and diesel price. The numbers are estimates — the point is the ranking between plans, the fuel and time delta, not the absolute liters. The recommended approach is the one you can execute with the best balance of coverage and cost, never a plan that hides gaps or double-driven ground in the totals.
Reasoning AI for precision agriculture: it asks the right agronomic questions, shows its math, and builds dry-run validated prescriptions from your data. You approve every step.
Ready?
English English 
German
Ukrainian
French
Kazakh
Portuguese
Spanish
Arabic
Swedish
Serbian
Romanian
Norwegian
Finnish
Lithuanian
Estonian
Latvian
Croatian
Slovenian
Slovak
Japanese
Polish
