Lime (SMP buffer)

Buffer pH decides how much lime; soil pH decides whether any is needed. A zone at or above the target pH gets none, and so does a zone whose buffer pH is at or above the no-lime threshold.

Buffer pH → lime (T/ac ENM)

Lower buffer pH means more acidity to neutralise. The 90–50% CCE columns are derived from the 100% rate and shown for reference.

Optimum values

These anchor the soil colours and pre-fill the Target box on the Rates page. Blank the target to colour an attribute relative to whatever the field contains instead. Values you change are kept with the project; Reset puts everything back to the built-in defaults.

Formula tool — how it works

How it works. For each zone, the app takes the zone's average soil test for the attribute you pick and calculates:
Rate = Base + Factor × (Target − zone average)
The further a zone tests below target, the more product it gets. A zone testing above target gets less than the base rate (never below Min).
Attribute — which soil test the formula reads (P, K, pH, etc.).
Target — the soil test level you want every zone built up to. Zones below it get extra product; zones at or above it get the base rate or less.
Factor — how much extra product per 1 unit below target, in rate units per soil-test unit (e.g. lbs of potash per ppm of K). This controls how aggressively rates ramp up. If it takes roughly X lbs of product to raise the soil test 1 ppm over your rotation, use that.
Base rate — the rate a zone gets when it's exactly at target. Typically your maintenance / crop-removal rate. Use 0 if zones at target should get nothing.
Min / Max rate — hard floor and ceiling. Min stops rich zones from going to zero (or lets them, if you set 0); Max caps poor zones at what's agronomically or economically sensible in one pass.
Round to — rounds each rate to the nearest increment (5 or 10 keeps rates blender- and controller-friendly).
Example — potash on K: Target 120 ppm, Factor 2, Base 50, Min 0, Max 300, Round to 5.
Zone testing 95 ppm → 50 + 2 × (120 − 95) = 100 lbs/ac.
Zone testing 120 ppm → exactly the base, 50 lbs/ac.
Zone testing 150 ppm → 50 + 2 × (−30) = −10 → floored at Min, 0 lbs/ac.
Rates it fills in are suggestions — every zone stays editable in the table above.

Import shapefile

Soil CSV template — how to use it

The two required columns are Lon and Lat — the GPS position of each soil sample, in decimal degrees (WGS84). Longitude is negative in North America, e.g. -82.94217. Everything else is optional.
Nutrient columns — any numeric column becomes an attribute you can map, zone, and build rates from: OM, pH, BpH, P, K, Ca, Mg, S, Zn, B, CEC, base saturations. Delete columns you don't test for, or add your own — the app picks up whatever numeric columns are present.
Column names are flexible — Lon/Longitude/X and Lat/Latitude/Y are all detected automatically, and you can re-map them by hand after upload. Unit columns from lab exports (P_U, K_U, …) are ignored.
One row per sample point. Rows without valid coordinates are skipped, and blank nutrient cells are simply treated as "not tested" for that point.
Id, Date, Grower, Farm, Field are labels for your own reference — they are not used in calculations.
If you use the example-row template, delete the three sample rows before uploading — they are only there to show the expected format. After upload, check the point count in the toast to confirm everything loaded.

Create map book

Six nutrient maps per page, one page set per field. Interpolated from your soil sample points.

Nutrients

Drop file to importboundary or prescription (.zip · .geojson · .kml) · soil .csv · saved project