Two rows, stated exactly
The catalog lists "Farm equipment operation" (Active collection) and "Tractor & Implement Operation" (Ready to deploy). Both are rated Hard and both list a head-mounted phone or a multiview rig as the capture setup.
Now recruiting capture teams worldwide. Get paid to record first-person video of real work.
Apply to captureTask family
Requirements
The catalog lists "Farm equipment operation" (Active collection) and "Tractor & Implement Operation" (Ready to deploy). Both are rated Hard and both list a head-mounted phone or a multiview rig as the capture setup.
The rows name attaching and detaching implements, driving, hitching and operating across the field. Where each step starts and ends is not a default. The written spec states it, and QA checks episodes against it.
Fingers disappear behind objects in manipulation, so 3D hand pose carries a per-joint visibility flag, and a hidden joint is marked as hidden rather than guessed.
No machine make or model, implement type, crop, field condition, safety statement or outcome label is stated for either row, and this page makes no such claim. Those details are agreed in the skill spec.
Definition
It is first-person video of one person operating farm equipment, recorded from that person’s own point of view. A paid, consented contributor performs the task written in a skill spec, and each attempt is delivered as an episode with synchronized streams, hand pose and labeled action segments. It is human capture, not robot or teleoperation data, and not a fixed corpus you download. It is also described as egocentric tractor operation data, first-person farm equipment video or the human-capture side of an implement hitching robot dataset.
The camera sits on the head, close to what a robot’s onboard camera would see, as the egocentric farm and field page puts it, so the frames show what the hands are doing. This page keeps to the catalog wording. It names no machine make, model, implement type or crop, because the site names none, and it treats anything more specific as a spec question settled in a Spec Pilot. It makes no claim about a trained model, benchmark or success rate.
Catalog rows
Two, listed in lib/commercial-catalog-data.ts, both in Farm & Field Operations under the Agriculture & Grounds sector, and both rated Hard. "Farm equipment operation" reads "Operate tractors, mowers or loaders and attach and detach implements" and is Active collection. "Tractor & Implement Operation" reads "Drive the tractor, hitch implements and operate them across the field" and is Ready to deploy.
The site defines Active collection as recording running now and Ready to deploy as contributors and site access already set up. Those describe the catalog rows, not delivery dates. The site states no delivered hours for either row, so this page claims none. The first table below reproduces both rows as the catalog states them.
Why it is demanding
Hard here means only what the site’s Skill column says: both rows carry that rating, and the same column rates other farm rows, such as the harvesting rows, Easy or Medium. The site gives no scoring rubric for the column, and this page adds none. It does not state why the two equipment rows are rated Hard, so the reasons below come from the row text and from what the site says about capture generally.
The row text combines several different things in one task: operating a tractor, mower or loader, attaching and detaching implements, driving, hitching and operating the implement across the field. The stereo sibling page describes this as work where the hands, the controls and the implement all compete for the frame. No failure rate, tolerance or statement about the skill of any worker is made here, because the site states none.
Difference
This page is the first-person treatment of the two equipment rows in Farm & Field Operations. The stereo tractor and farm equipment operation page covers the same two rows from the stereo pair and MCAP side, and this page does not describe the rows as stereo capture. The egocentric farm and field task page covers all 21 rows of the environment as first-person video, including both of these, so equipment operation is one part of it rather than its main topic.
The egocentric heavy machinery page covers one different row, working the levers and control panels of presses, cranes or machinery in Heavy Industry & Fabrication, and the stereo heavy machinery page adds stereo and MCAP to that same row. The stereo crop harvesting page covers four rows about picking and cutting produce, which is plant work rather than equipment work. The second table below sets the pages side by side.
Capture setup
The catalog lists "Phone (head-mounted) / multiview rig" for both rows. That means either a head-mounted phone or a multiview rig, and the site does not say which one a given equipment order uses, how many cameras are involved or what is mounted where. The site states no stereo pair for either row, so this page does not describe the capture as stereo.
The wider stack the site documents is a global-shutter 4K/60 head camera with a 120 degree lens, two wrist cameras at 1080p and 60 fps, a depth sensor at 848×480 and 30 fps and 200 Hz 6-DoF IMUs, with ten streams hardware-triggered onto one PTP clock domain and aligned under 2 ms. The rig is calibrated at the start and end of every session. Which of these applies to a tractor collection is set in the skill spec; the site states no camera count, resolution or frame rate specific to these rows.
Episodes and labels
Each attempt is delivered as one episode, and these rows need a decision up front about what one attempt is: a full drive, hitch and operate sequence, or a single step such as attaching an implement. The site does not set that length or say how many steps make up an episode, so the spec does.
Action segments divide the recording into spans carrying start_ns, end_ns, verb and noun, from a taxonomy of 97 verbs and 512 nouns, annotated to the frame and human-reviewed. A spec that says only "operate the tractor" gives one long segment. A spec that names the steps gives a sequence you can slice by step. Other fields are hand_joints and hand_visible (21 joints per hand), contact_events, objects and instance_masks at 848×480, plus int64 nanosecond timestamps and intrinsics and extrinsics per stream.
Steps
The rows give a natural cut: operate a tractor, mower or loader, attach and detach implements, drive, hitch, and operate the implement across the field. Whether driving and operating are one segment or two, and whether attaching and detaching are separate spans, is a spec decision, not a default.
The site lists no control position, machine state or implement state label for these rows, and it gives no ordering for the steps. A buyer who needs a hitching span as its own accept criterion writes that into the spec, and a Spec Pilot proves it on real footage before you scale. Nothing on this page is guidance on how to operate equipment; it describes what a dataset can label.
Occlusion and light
The site states that the hands occlude the work, that fingers disappear behind objects and that reach and grasp frames are where blur and occlusion show up. That is why each hand joint carries a visibility flag, why instance masks are recorded per frame and why wrist views are an option when a grip is lost from the head camera.
Vibration, dust, outdoor lighting changes and implement occlusion are Not stated for these rows, and this page does not imply a fix. The site does state that glare-heavy and low-texture scenes make single-frame depth worse and that depth degrades on wet and reflective surfaces, with confidence maps masking low-confidence regions. A program that cares about time of day or a covered setting puts it in the spec and checks it on a Spec Pilot.
What video cannot show
The site lists no label for the outcome of operating or hitching: no hitched-state, attached-state, completion or quality label for these rows. Force, tactile and torque readings are not among the standard streams either. If your pipeline needs one of these, it is scoped in the spec rather than assumed.
The GR00T N1 paper says its human video datasets do not include explicit action labels, and handles that with learned latent actions. Firsthand captures people, not robots, so using the episodes for a specific robot means your own retargeting step. The site states reject thresholds that apply to every collection: a cross-stream sync error above a 2.0 ms ceiling for more than three consecutive frames, the manipulated object out of frame for more than 15 percent of the episode, and more than 35 percent invalid depth pixels in the manipulation region. These are reject thresholds, not a stated pass rate.
Safety and privacy
Equipment safety, operator licensing, certification and machine condition are Not stated for these rows, and this page makes no such claim and gives no operating guidance. Who may be in frame and what the footage may show are agreed in the spec.
For every delivered episode the site states that faces and screens are blurred irreversibly, that a reviewer confirms no un-consented person is identifiable, and that footage that cannot be de-identified is discarded. The anonymization record ships with the data, and consent artefact IDs link every episode to a signed contributor release. This is not legal advice, and the executed agreement controls.
Quality
Calibration is measured at the start and end of every session under a 0.28 px RMS gate. An episode is rejected for a sync breach, for the manipulated object out of frame for more than 15 percent of the episode, for more than 35 percent of depth pixels in the manipulation region being invalid, for an undocumented bystander or for a mismatch against the named skill spec. A reject log ships with every batch, and the site states no pass rate for these rows.
Scale and speed
The October 2026 off-the-shelf catalog lists ~324,800 hours across 18 datasets, of which stereo is ~64,800 hours across 9 datasets. The site names no tractor or farm equipment dataset among them, so this work is custom collection, not an off-the-shelf purchase.
It is custom collection at scale through a network of thousands of capture providers, for a consistent, recurring data flow to labs. Where coverage is deep, the median time from signed spec to first validated batch is a median of 48 hours; where it is thin, turnaround runs three to four weeks. One row is Active collection and the other Ready to deploy, but the site does not say which speed applies to which, so the timeline is quoted against your spec. A tight spec is the quickest route to a fast, on-demand dataset.
Delivery and licence
Delivery formats offered on the site are RLDS, LeRobot, WebDataset, HDF5, zarr and Rerun .rrd, or raw streams. Which one an equipment order uses is set in the spec. Stereo and MCAP delivery for the same rows is covered on the stereo sibling page.
The license is perpetual, irrevocable and worldwide, buyer-owned and non-exclusive by default, with exclusivity available as a separate term. Collections are billed per validated hour, rejected episodes and recaptures are never billed, and the site states no price list for this task.
Ordering
Describe the steps and where each starts and ends, what counts as a finished step, the privacy rule for the space, and the delivery format your reader expects. Most programs begin with a Spec Pilot, a small first batch that proves the spec and accept criteria on real footage before you scale. The hard-task hub lists these rows alongside the site’s other Hard rows if you are comparing tasks.
At a glance
Every collection runs through the same seven-stage end-to-end custom collection pipeline. End-to-end custom data collection is a managed service that takes an AI data need from problem to owned dataset in a single accountable pipeline.
Catalog rows
| Task (as listed) | Description (as listed) | Environment | Skill | Capture setup | Status |
|---|---|---|---|---|---|
| Farm equipment operation | Operate tractors, mowers or loaders and attach and detach implements. | Farm & Field Operations | Hard | Phone (head-mounted) / multiview rig | Active collection |
| Tractor & Implement Operation | Drive the tractor, hitch implements and operate them across the field. | Farm & Field Operations | Hard | Phone (head-mounted) / multiview rig | Ready to deploy |
Compared pages
| Page | What it covers | Row status as listed | Relation to this page |
|---|---|---|---|
| This page: egocentric tractor and farm equipment operation data | Two Hard rows in Farm & Field Operations: Farm equipment operation and Tractor & Implement Operation | One Active collection, one Ready to deploy | First-person capture of the two equipment rows |
| Stereo tractor and farm equipment operation data | The same two rows, with a calibrated stereo pair and MCAP delivery | One Active collection, one Ready to deploy | Stereo sibling; stereo is a spec choice, not stated on the rows |
| Egocentric farm and field task data | All 21 Farm & Field Operations rows, including both equipment rows, as first-person video | Active collection or Ready to deploy, by row | Broader page; equipment operation is two of its rows |
| Egocentric heavy machinery operation data | One row: Operating Heavy Machinery Controls, levers and control panels of presses, cranes or machinery, in Heavy Industry & Fabrication | Available on request; Hard | Different environment and row from the farm equipment rows |
| Stereo heavy machinery operation data | The same single Heavy Industry & Fabrication row, with a calibrated stereo pair and MCAP | Available on request; Hard | Stereo, for a fixed operator station rather than the farm rows |
| Stereo crop harvesting data | Four harvesting rows: pick, cut with shears, check, sort and place in crates | Three Active collection (Easy); one Available on request (Medium) | Same environment; plant work, not equipment operation |
Row wording
| Topic | What the site states | Where it is settled |
|---|---|---|
| Operating tractors, mowers or loaders; attaching and detaching implements | Stated: "Operate tractors, mowers or loaders and attach and detach implements" | Catalog row |
| Driving the tractor, hitching implements, operating them across the field | Stated: "Drive the tractor, hitch implements and operate them across the field" | Catalog row |
| Machine makes and models, implement types, crops, acreage, field conditions | Not stated | Written skill spec |
| Step order, step count and attempt length | Not stated | Written skill spec |
| Outcome labels such as hitched, attached or completed | Not stated | Written skill spec |
| Stereo capture | Not stated for these rows | Written skill spec |
| Equipment safety, licensing and certification | Not stated | Not claimed |
| Task times, success rates, episode or hour counts | Not stated | Quote |
Capture setup
| Part | What the site states |
|---|---|
| Catalog capture setup | Phone (head-mounted) / multiview rig on both rows |
| Head camera | Global-shutter 4K at 60 fps with a 120 degree lens |
| Wrist cameras | Two wrist-mounted cameras at 1080p and 60 fps |
| Depth and motion | Depth sensor at 848×480 and 30 fps; 200 Hz 6-DoF IMUs |
| Sync and calibration | One PTP clock domain, aligned under 2 ms; calibrated at the start and end of every session |
| Stereo pair, camera count and mounting for these rows | Not stated |
Spec checklist
| Spec item | Question to settle | How it is settled |
|---|---|---|
| Scope | Which row, or both, and whether an attempt is the whole sequence or one step | Written in the spec; proven on a Spec Pilot |
| Step boundaries | Where driving, hitching, attaching, detaching and operating each start and end | Verb and noun per step |
| Accept criteria | What counts as a finished step, and what is a reject | Written before capture; QA checks against it |
| Masks | Whether per-frame instance masks are needed | Decided in the spec |
| Capture setup | Head-mounted phone or multiview rig, and whether a stereo pair is added | Decided in the spec |
| Delivery format | How the data is packaged | RLDS, LeRobot, WebDataset, HDF5, zarr or Rerun .rrd, or raw streams |
| Privacy and license | Handling of anyone and any screens in frame; ownership | Blurring as stated above; perpetual, buyer-owned, non-exclusive by default |
Example footage
One real clip already published on this site, shown as a format example: ten seconds of first-person home cooking with faces blurred. It does not show a tractor, an implement, a field or any farm work, and it is not an equipment clip.
No tractor or farm equipment clip is published on the site, so this is labelled as a format example. Request a sample to see delivered files. See sample data outputs, request an egocentric data sample.
FAQ
Sources
Tell us which equipment row you need, the steps and where each starts and ends, the privacy rule for the space and the delivery format you want. We will quote reach, timeline and price against a written spec, with a first validated batch proven on a Spec Pilot.