> For the complete documentation index, see [llms.txt](https://docs.geopard.tech/geopard-tutorials/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geopard.tech/geopard-tutorials/changelog-and-product-releases/release-web-and-mobile-june-2026-ai-assistant-beta-ab-line-grids-trials-exports.md).
# Release Web & Mobile June 2026 (AI Assistant Beta, AB-Line Grids, Trials, Exports)
## Meet the GeoPard AI Assistant
The headline of this release is the new **GeoPard AI Assistant**. Access is available on demand through a short request-access form. It is a conversational helper built right into the platform. You can ask agronomic questions, search your farms, fields, datasets, equation maps, and trials, and trigger real actions like building equation maps, creating sampling plans, or exporting prescriptions to John Deere.
The assistant lives in a resizable side panel that travels with you across the app. It always knows the page you are on. Answers come back as **content-rich widgets** with dataset and map previews, **asset thumbnails** you can open in a new tab.
Because real agronomic decisions need oversight, action requests pause for your **explicit confirmation** first. This includes saving a zones map, assigning rates, or pushing a work plan to John Deere. A clear disclaimer reminds you to validate recommendations.
Conversations are saved to **chat history**. You can **share a session** with teammates in your organization or **read-only by email** with any GeoPard user. This works well for demos and onboarding. The assistant is **fully localized** for non-English users.
> ๐ก *Tip:* Always validate AI-generated rates and formulas against your crop plan, soil tests, product labels, and local regulations. The assistant is a productivity tool, not a substitute for a certified local agronomist.
## Agronomy knowledge base for AI Assistant
You can now strengthen the **GeoPard AI Assistant** with your own **Agronomy knowledge base**. Upload product labels, crop recommendations, trial results, application rates, positioning guidance, safety notes, compatibility details, and regional rules. The assistant uses this content at query time, so answers stay grounded in your portfolio instead of generic agronomy advice.
This helps teams move faster with less manual lookup. You can ask for **field-specific recommendations**, compare products, support **variable-rate workflows**, and answer agronomic questions with company-specific context. That reduces back-and-forth and makes recommendations easier to review before action.
Access follows your workspace structure. For standalone users, the knowledge base stays private to that user. For organizations, it is shared at the org level, so all org users work from the same agronomy source of truth. This keeps recommendations consistent across sales, advisory, and operations teams.
The assistant always retrieves from the correct knowledge base for the current user or organization context. Access is isolated by tenant, so there is no cross-user or cross-organization leakage.
## AI Response Style
You can also guide how the **GeoPard AI Assistant** responds with an **AI Response Style** setting. You can add example wording, preferred phrasing, or response patterns you want the assistant to follow.
The **Agronomy knowledge base** supplies the factual company context. **AI Response Style** shapes the tone, structure, and wording of the answer. This helps teams keep recommendations accurate while matching their style.
You can refine how answers are written without changing your agronomy source files. That gives each user more control over customer-facing responses while keeping product data in the knowledge base itself.
## Equation prescriptions aligned to your AB guidance lines
You can now build **equation and application grids that follow your AB guidance lines**, so prescription cells run in the same direction your machinery drives, reducing overlaps and skips in the field. AB-line setup lives in the **Line configuration** panel of the Create Equations workflow, right next to the existing Heading Line option, and you can define the line in three ways: **import an AB line from John Deere Operations Center**, drag the **A and B points** directly on the map, or type the **A and B coordinates** by hand.
{% @arcade/embed url="" flowId="KOI0yRLNF671o5UIUCYO" %}
## Smarter zones-map editing
Zone editing gained a substantial toolkit upgrade. The **Assign Zones** instrument can now create a new custom-colored zone and no longer leaves small holes and sleeves after a merge. In the same workflow, you can either **keep stable zone IDs** - including gaps after deleting a middle zone - or **resequence them into a clean `1โฆN` order** while preserving polygons, colors, and rates.
Zone colors are easier to read in the Assign Zone and Draw Polygon instruments.
{% @arcade/embed url="" flowId="K6gPPJA6lIFX64tK7yGP" %}
## Field Trials design enhancements
On-farm Field Trials got a strong set of upgrades. You can now lay out **split-plot** patterns for multi-hybrid rate trials, with strips grouped by seeding rate and each hybrid placed as a strip within each rate area. You can also fine-tune plots with **manual adjustments** and a configurable group buffer.
Trials now display consistently wherever you work. This includes **Background Layers**, **Farm View**, and **Compare Layers**. Exports now keep **block-name attributes** so the layout reaches your equipment intact.
## More machine and platform exports
Getting prescriptions onto equipment is easier across more brands. New and improved exports include **Kinze BlueVantage** (`KML`) and improvements to **John Deere** and **Climate FieldView** exports.
When exporting **ISOXML**, you can now **choose the target terminal**. The **Equation Map export** also has a **display-format dropdown**. Export notifications are now consolidated into one clear panel.
## New satellite vegetation indices & Regions
Satellite analysis gained several new indices: **NDYI (canola is flowering detection)** including support for Planet imagery. It also adds a **CONTRAST** mode for clearer visualization.
Imagery coverage expanded too, with **additional Brazil regions coverage**.
## Text (string) attributes for soil, yield, and as-applied datasets
GeoPard now supports categorical text attributes from start to finish. You can upload soil, yield, and as-applied datasets that contain string values, such as crop name, soil texture class, product or variety names, or alphanumeric codes, not just numbers.
These attributes are stored with their proper text type and rendered on the map colored by category with a matching legend.
## Variable-rate status and preview in Data Layers
The Field page **Data Layers** panel now shows at a glance whether each zones map already has a variable-rate prescription. The old plain **Modify** action is replaced with a state-aware VRA pill. Maps without a prescription show an outlined **No VRA** pill that turns into a **Build VRA** prompt. Maps that are ready show a green **VRA ready ยท N zones** pill with a prescription badge.
Hovering a row opens a prescription popover, so you can review details without leaving the panel. For maps that still need rates, the popover shows what is missing and offers a **Build VRA** shortcut. For ready maps, it shows a full breakdown by product and by zone, including unit, zone color, area, field share, assigned rate, average rate, total, and cost. This makes it easy to spot export-ready maps and compare prescriptions before sending them to equipment.
Clicking the pill or any button in the popover opens the rates editor, so you can move straight from preview to editing.
## Replace a field boundary by file upload
You no longer need to recreate a field to fix its shape. You can now **replace an existing boundary by uploading a file** directly from the Field page. This makes corrections and season-to-season updates much faster.
{% @arcade/embed url="" flowId="89CiuB9vrh4wmXWfB1Ef" %}
## Synchronize a Field with John Deere Operations Center
A new on-demand **Synchronize Field with John Deere Operations Center** button lets you sync one field with **John Deere Operations Center** exactly when you want.
Use it after **creating a field** in GeoPard, **replacing its boundary**, or **updating** **its** **organization, client, or farm hierarchy**. GeoPard checks whether the field is already linked and either creates it in John Deere or re-syncs the existing one automatically.
Synchronize a field with John Deere Operations Center from the Field page.
See [Synchronize a Field with John Deere Operations Center](https://docs.geopard.tech/geopard-tutorials/product-tour-web-app/john-deere-operations-center-integration/11.-synchronize-a-field-with-john-deere-operations-center) for the full setup and step-by-step instructions.
### See John Deere sync status on the Field page
The Field page header now shows a sync status pill next to the field name and area. It includes the John Deere logo and the current sync status. Hover over it to open the Field sync status panel with the integration status and quick actions:
* **Synced** โ the pill turns green with a **Synced** label. From here, you can open the field in **John Deere** **Ops Center**, manage field mapping settings, or re-sync the field.
* **Not synced** โ the pill and badge turn grey. To send the field to John Deere Ops Center, click **Synchronize field**.
## Measure distances with the Ruler tool
A **ruler tool is now on every map**, so you can quickly measure distances for planning operations and checking spacings without leaving GeoPard.
{% @arcade/embed url="" flowId="raBHYJi3aFwYBVFCeRDP" %}
## A cleaner, more flexible interface
The app interface was refreshed for daily work with a **compact left menu with persistent labels** and **resizable map and side panels** on the Field page.
{% @arcade/embed url="" flowId="FVjNVdaKOexIoh1q80LR" %}
## Soil interpolation with fewer points
Soil interpolation now handles sparse and collinear input more reliably. It detects collinearity automatically and chooses the interpolation method that best fits the available points. This prevents failures and unstable results when sampling is limited.
* **1 point**
* **2 points**
* **More than 2 points**
Soil dataset polygons are also **clipped to the field boundary on upload**, which helps keep the resulting layer clean and ready for analysis.
## Bug Fixes
* **Reliable zones map saving** โ fixed edge cases for topology and side-location errors, and saving now works even when an edit leaves a tiny zero-area zone.
* **Seamless zone polygon boundaries** โ small holes after manual draw and clone operations are cleaned up.
* **Accurate zone areas after deletion** โ deleting a zone no longer reallocates its area to neighboring zones unexpectedly.
* **Valid geometry in exported shapefiles and KML** โ eliminated invalid slivers, seams, and topology errors in exported boundaries, grids, and sampling plans.
* **Properly named boundary downloads** โ exported archives keep the field and farm name instead of a generic file name.
* **Reliable GeoTIFF and GeoTiff export** โ fixed empty all-zero bands and timeouts when satellite fetches run long.
* **Smooth ISOXML import to more terminals** โ fixed import failures on Kverneland Tellus GO.
* **Soil datasets keep separate sampling dates** โ datasets from different sampling dates no longer merge into one.
* **Accurate soil lab results upload** โ no extra features created when a lab file has more zones than the sampling plan.
* **Soil dataset downloads on large fields** โ large-field soil datasets no longer fail to return their source data.
* **Faster topography export on large fields** โ topography export no longer times out on big fields.
* **Correct dataset resolution handling** โ resolved an invalid `NaN` value in dataset resolution.
* **Dependable Field Potential / Stability maps** โ automated maps now generate reliably.
* **Clean satellite index visualization** โ fixed range-coverage color artifacts in index calculation.
* **Stable trial editing** โ Move or Rotate no longer creates duplicates, revert works on trial changes, and trials display reliably on background layers.
* **Planet imagery search and limits** โ search works again, with a clear "limit reached" message instead of a generic error.
* **Smooth SSO sign-in** โ works correctly when clicking the GeoPard logo or moving between auth pages.
* **Boundary uploads respect your processing choice** โ uploads no longer generate an extra field when auto-processing is off.
* **Cleaner Activity Log** โ correct org name and user email, and silent error reporting instead of crashes.
* **Correct equation cell alignment** โ cell dimensions align with the heading parameter.
* **Accurate sharing status** โ shared farms report correctly instead of always showing as owned.
* **Stable analytics endpoints** โ fixed timeouts and errors on trial pricing and recommendation analytics.
* **Readable menu on small screens** โ restored vertical scrolling for the main menu when the window is reduced.
## Improvements
* **Faster, more stable mapping engine** โ GeoPard maps are now shown faster for raster (imagery, topography) and vector data (soil, yield, as-applied/as-planted).
* **Faster analysis processing** โ related to creation of zones, formula-based maps and processing of datasets.
* **Better visualization binning** โ improved class generation, outlier handling, and bin edges for clearer maps.
* **Yield dataset provenance** โ clean or calibrate and synthetic configuration metadata is stored with the dataset, and the parameters used are shown for Yield Clean-Calibrate and Synthetic Yield datasets.
* **AgInsights beta - the new module related to limiting factors detection, product results (ROI, Yield, Correlation analysis)**
* **Expanded MCP / API toolset** *(API-only)* โ programmatic tools powering the AI Assistant: equation maps, sampling plans, trials search, John Deere export, AB-line guidance, and provider search.
* **AI assistant infrastructure, including highest security and guardrails, incl. per client configurations**
* **Increased automated test coverage to improve overall system robustness.**
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.geopard.tech/geopard-tutorials/changelog-and-product-releases/release-web-and-mobile-june-2026-ai-assistant-beta-ab-line-grids-trials-exports.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.