> 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/agronomy/vr-lime-application-based-on-soil-ph-data.md).

# Variable rate lime prescription from soil pH

Turn soil pH samples or scans into a lime rate map, check the cost against a flat rate, and export it to ISOXML, shapefile or Operations Center for the spreader.

A variable rate lime map puts lime where pH is below target and saves it where it is not. Import pH from lab results or a soil scan, set the target pH and the lime rate per zone, compare the total against your usual flat rate, and export the map for the spreader. In the worked example, a 33.9 ha field averaged 6,348 lb/ac against a 7,000 lb/ac flat rate.

{% hint style="success" %}
Turn your pH results into a lime map: [Start free](https://app.geopard.tech/auth/sign-up?utm_source=docs\&utm_medium=cta\&utm_campaign=vr-lime-application-based-on-soil-ph-data)
{% endhint %}

## Create a variable-rate (VRA) lime Rx prescription map from soil pH

Turn soil pH data into a machine-ready lime application map (Rx prescription). Use it to apply lime only where ROI is positive.

### Interactive walkthrough

{% @arcade/embed url="<https://app.arcade.software/share/b99IrB7wBzVDJu24MKFI>" flowId="b99IrB7wBzVDJu24MKFI" %}

### Economics example (VR vs flat 7,000 lb/ac)

This example compares variable-rate lime against a single flat rate across the field. Use it as a quick sanity check before exporting the Rx.

| Item                            | Value                    |
| ------------------------------- | ------------------------ |
| Field area                      | **33.91 ha**             |
| Avg applied rate                | **6,348.2 lb/ac**        |
| Lime price                      | $**0.02 / lb** (\~$40/t) |
| Total lime (calc)               | **523,853 lb**           |
| Material cost (field)           | $**10,477**              |
| Material cost (per ha)          | **\~**$**309/ha**        |
| Savings vs 7,000 lb/ac (total)  | $**441.9**               |
| Savings vs 7,000 lb/ac (per ha) | **\~**$**13.0/ha**       |

### Export the lime Rx prescription

* Export as ISOXML: [Export VRA map In ISOXML Format](https://docs.geopard.tech/geopard-tutorials/product-tour-web-app/export-download/export-vra-map-in-isoxml-format.md)
* Other export options (SHP and more): [Export / Download](https://docs.geopard.tech/geopard-tutorials/product-tour-web-app/export-download.md)

{% hint style="success" %}
Turn your pH results into a lime map: [Start free](https://app.geopard.tech/auth/sign-up?utm_source=docs\&utm_medium=cta\&utm_campaign=vr-lime-application-based-on-soil-ph-data)
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.geopard.tech/geopard-tutorials/agronomy/vr-lime-application-based-on-soil-ph-data.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
