Questions we get asked

Minutes, if you have boundary files. Shapefile, KML and GeoJSON import directly. If you have nothing but the farm itself, draw on satellite imagery with the area reading out as you go. The drive simulator can run a complete field the same afternoon, before any hardware is ordered.

No, import it. A layer of many small uniform polygons is solved back into the grid that made it, including origin, bearing, rows, size pattern and numbering, and the fit is verified before it is accepted. A previous season can be edited rather than redrawn.

No. Start with the map, the notes and the machine, which is most of a farm season. A split field is just two boundaries: draw each part in whatever shape it really is, and every record (passes, readings, notes, photos) lands against the right one, so the parts can be compared from their own records. Replicated plots and statistics exist in the same product for the day you want them; most farms never need them.

The plans and what each one carries are on the pricing page. Numbers are agreed directly, because a trials unit, an advisory firm and a farm comparing two rates are not buying the same thing. Tell us what you want to run and we will quote it plainly.

Either. Fieldbase authors the designs it names (completely randomised, randomised complete block, Latin square, split plot and factorial) and places them with a stored seed, so a layout can be reproduced and defended a year later. It also works happily downstream of a design made elsewhere: import a fieldbook from ARM, agricolae, FielDHub, Breedbase or a statistician's spreadsheet and bind it onto the grid, so the geometry carries the identities your pipeline already knows.

Yes. One row per plot in XLSX or CSV, a BrAPI v2 observation hand-off for breeding pipelines, and shapefile, ISOXML, KML, KMZ and GeoJSON for anything that thinks in geometry. Field exports carry the agronomy; machine-setup exports carry the trigger points and the driven route, because a spraying export and a harvesting export of the same field are different files.

With an Organisation plan, every signed-in device converges on the same project through cloud sync. Shared field hardware unlocks with a per-person PIN, and every reading records who took it and where the value came from, so who scored block C is in the record, not in anyone's memory.

Yes. Pin the fields you are taking out and everything about them is held on the device before you leave the yard: the map, the plots and the season's records. Notes, readings and runs are recorded locally whether or not there is signal, and sync catches up on its own when you are back in coverage.

Yes. Chromium-based browsers get the full feature set including serial hardware; there are desktop builds for Windows, macOS and Linux with a serial port picker whose permissions survive a restart; and there is a native iPhone and Android app for collection on the go, with hands-free voice dictation for scoring plots and everything working offline. Phones and tablets also run the web app for field notes. The phone app has its own page under /mobile/.

On your device first. Projects are held in browser storage and on disk as .agproj files, and everything works with no connection. With an organisation subscription, projects and field data also sync through Fieldbase Cloud, so every signed-in device converges on the same project and a lost device does not lose a season. And export is never gated, so your data leaves whenever you want it to.

A GPS receiver over serial, and output hardware: an off-the-shelf USB or Modbus relay module, or an I/O board running the supplied Fieldbase firmware. All of it is standard industrial equipment, and there is no proprietary control box to buy. And you need none of it to evaluate the product: a built-in drive simulator and NMEA log replay run the whole pipeline on a bench.

No. Fieldbase is deliberately brand-neutral: export ISOXML task data to GreenStar, Fendt, CNH and other ISOBUS terminals, or let Fieldbase operate the outputs itself through standard industrial hardware. Nothing requires the tractor, the implement and the software to share a badge.

Every GPS fix is projected into the grid's own local frame and gated by pass and travel direction, then triggers fire on a signed crossing of the plot edge. Fixes are interpolated, single-fire hysteresis means jitter cannot double-fire, and latency compensation fires early by speed × latency to cover actuation delay.

A blocking preflight check, a two-step ARM/DISARM gate, and a GPS watchdog that auto-disarms and drives outputs to a safe state if fixes stop arriving or quality drops. A phone's own location service can never fire outputs, and a missed trigger is never fired late.

Only if nothing free reaches you. Fieldbase's NTRIP client takes corrections from any caster, commercial or public. More than twenty US states run free public networks, and commercial services work the same way everywhere else. Receiver presets include the u-blox ZED-F9P found inside most low-cost RTK kits.

Yes. Run your firm as one organisation: staff sign in on any device, each client's work lives in its own project, and every reading carries who recorded it. Hand-over is whatever format the client's own system reads, and their data is never locked in, because export is never gated.

The application becomes read-only. It does not hide your work. Feature gating affects the interface only and never the data, so a project created with a paid feature keeps all of it and opens intact on an installation that never held that licence. Export is never gated, so a lapsed subscription cannot prevent you retrieving a season's data.