Account settings
Your details
Password
At least 8 characters. If you've only ever signed in with an emailed link, this sets your first password.
Your access
Billing
Plans and invoices will appear here.
At least 8 characters. If you've only ever signed in with an emailed link, this sets your first password.
Plans and invoices will appear here.
Loading your farms…
Upload the files off your harvester once a year. See yield, the zones that hold year after year, and where to soil sample.
No password, or invited by email?
By using PaddockPix you agree to the terms and privacy note.
Demo only: any email and password will do. Nothing is checked or stored.
Pixel Analytics checks every new account by hand, so farm data only ever goes to the right people. Once you're approved you can add your farms and upload your harvest files.
By using PaddockPix you agree to the terms and privacy note.
Add each farm you'll upload harvests for. You can also add one while you're uploading.
Drop in the files straight off the harvester display, or yield-map exports from your contractor or agronomist. We work out the format, the season and which paddocks they cover. You check it on the next step.
3 paddocks in 3 files. We matched each one to a paddock you already have by where it sits on the ground, not by its name. Fix anything that's wrong, then build the maps.
This usually takes under a minute for shapefile exports, a few minutes for a display backup.
Some paddocks in this display backup don't record which part of Australia they're in, only where they sit within about 50 km. Pick the nearest town and we'll place them.
These shapefiles don't record a harvest date, so please pick the season.
| File | Matched to | Crop | Variety | Area | Avg t/ha |
|---|
Add the tonnes delivered from each paddock and we'll calibrate its map to them. Harvesters can be well off for canola. Not part of this demo.
This usually takes about a minute. You can close this page; we'll email you when it's done.
Give people access to a grower's farms, and add growers and farms. Only admins see this page.
People who signed up and asked for access. Approving a grower creates their grower (or links them to one that already exists) with the role you choose.
If they already have an account, they see the farms straight away. If not, the access waits for them and applies when they sign up with this email.
These people have an account but can't see any farms.
Admins can approve people, see every grower's farms (read-only) and add or remove other admins. You can't remove yourself.
A grower is a farming business. You're added to it as an adviser so you can see its maps.
Click a topic to expand it and read more.
Pick a season to see that harvest. The buttons beside the seasons look across all years: Stable zones for every paddock with two or more seasons (paddocks with only one season are grey), Elevation, and Years of data, which colours every paddock by which harvest years it has data for. Click a paddock for its detail, interpretation and soil sampling sites. Yield, vs field avg and Moisture describe a single harvest, so they only appear when you pick a season. Each paddock is coloured against itself. Yield shows that paddock's weakest 5% as pale straw and its strongest 5% as deep green. "vs field avg" shows each spot as a percentage above or below the paddock's average for that season. Zones split a single season into low, medium and high areas.
Crops change between seasons, so seasons are compared on relative yield: each 5 m cell's yield as a percentage of its paddock's average that season. That also cancels out the harvester's crop-by-crop calibration errors. For each cell, stable high means the average across seasons is at least 5% above the paddock average, stable low means at least 5% below, and average means within ±5%. Unstable means the seasons disagree by more than 20 percentage points, for example good one year and poor the next. That usually points to seasonal causes such as frost, waterlogging or a dry finish rather than soil, so unstable areas shouldn't drive fixed input rates. Zones are cleaned with a 25 m majority filter and patches under 0.5 ha are merged. Each paddock uses every season it was harvested in. With three or more seasons, a cell is unstable when the standard deviation of its relative yield is more than 14 percentage points, which gives the same result as the 20-point rule when there are only two. More seasons give a firmer stability call.
Seasons are matched by location, not by name. Every harvest is drawn on the same fixed 5 m grid, and older data is attached to whichever current paddock it physically overlaps. Renamed, split or merged paddocks therefore still line up across seasons, and a paddock that wasn't harvested in the latest season is built from its older seasons.
Elevation comes from the harvester's own GPS height, logged every second. Where passes from different days cross, heights usually agree to within a few tenths of a metre, which is precise enough to show hollows and rises of half a metre or more. "Landform" (hollows and rises) compares each spot with the average ground height within 100 m: blue is lower than its surroundings (where water and cold air collect) and brown is higher (crests and sandy rises). "Height" shows absolute elevation with hill shading. Comparing landform with the stable zones often explains them: unstable areas in hollows suggest seasonal waterlogging or frost, and stable low on rises suggests sandy or shallow soil. Some files (for example classified yield-map exports) carry no GPS height and add nothing to this layer.
In Stable zones, each paddock with stable zones has up to 9 suggested soil sampling sites, numbered on the map (L = stable low, H = stable high, A = average, U = unstable). Sites are allocated by zone (normally 3 low, 3 high, 2 average and 1 unstable; fewer where a zone is small). Each is placed at least 25 m inside its zone where possible, at a spot with yield typical of the zone, and at least 60 m from any other site. Comparing stable low against stable high sites is what shows whether a soil constraint explains the difference.
Yields are shown as logged by the harvester unless marked. ✓ Calibrated means the paddock's yield has been scaled to its delivered tonnes. ? Estimated means a standard factor for that crop has been applied, worked out from paddocks that were calibrated; it's an estimate, not that paddock's deliveries. ≈ marks maps imported from classified (banded) yield-map exports, which store yield as bands rather than readings, so each spot takes its band's mid-point. Harvester monitors can read well off for some crops (canola especially), so treat uncalibrated tonnes with care. Relative yield, zones and stability are not affected by calibration.
Each harvester log record carries its position, the cut width, distance travelled, grain flow or yield, and moisture. Records are drawn onto the 5 m grid using the area each one covered. "Smoothed" (the default) is an inverse-distance-weighted average (IDW, power 2) of logged points within 15 m; "Raw" is the plain average in each cell. Points outside 2 × the interquartile range of each paddock are dropped as fill-up, turning and end-of-run noise, as are zero and stationary readings. The crop, variety and harvest dates come from the files where they're recorded; otherwise they're entered when the files are uploaded.