A named grounds task list
Mowing, trimming, planting, clearing paths and hedge pruning are different sequences, so a spec names each one and the areas it covers.
Task family
Requirements
Mowing, trimming, planting, clearing paths and hedge pruning are different sequences, so a spec names each one and the areas it covers.
A head-mounted view keeps both hands, the tool and the plant or ground being worked in one view while the work is done on site.
3D hand pose with a per-joint visibility flag records where the fingers are, and which joints were hidden, while a tool is held and used.
Frame-accurate action segments mark where cutting ends and clearing cuttings begins, or where one pass ends and the next starts, aligned to video and depth.
A perpetual, buyer-owned commercial license backed by a documented consent chain.
Why it matters
Egocentric landscaping and groundskeeping data is real-world, first-person video of work on outdoor grounds. It is recorded from the worker viewpoint, with depth, 3D hand pose, contact events and frame-accurate action segments aligned on one hardware clock. The tasks it covers are the ones the site states in its task catalog: landscaping and groundskeeping on commercial property, landscaping and groundskeeping on a farm, and pruning and trimming hedges.
This is outdoor maintenance work done with hand and power tools. The plant care and gardening page covers tending individual plants, the tool use page covers hand-tool manipulation across many settings, and the car washing and detailing page covers another kind of upkeep work.
Setting
The site states grounds work in its task catalog under the Agriculture & Grounds sector. A Landscaping & Groundskeeping environment lists its examples as commercial grounds, parks, corporate campuses and golf courses. Two further rows sit in the Farm & Field Operations environment: a farm landscaping and groundskeeping row, and a hedge pruning and trimming row.
Every row uses the same capture mode, a head-mounted phone or a multiview rig. All three are rated Medium. Two are listed as Active collection and one as Ready to deploy.
Commercial grounds
The catalog row reads "Mowing, trimming, planting and general grounds maintenance on commercial property." It is the broadest of the three.
The row is rated Medium and listed as Active collection. Equipment, site and lawn sizes, plant species, the number of sites and the order of the work are Not stated.
Farm grounds
The catalog row, named Agriculture Landscaping & Groundskeeping, reads "Mow, trim, plant and clear grounds and paths on the farm with hand and power tools." It adds two details the commercial row does not give: clearing paths, and the use of hand and power tools.
The row is rated Medium and listed as Ready to deploy. Which hand and power tools are used, and what a cleared path looks like, are Not stated.
Hedges
The catalog task reads "Prune and trim hedges using hedge trimmers and loppers", and its description reads "Cut hedge tops and sides with trimmers, remove thick stems with loppers and clear cuttings." It covers three linked steps: cutting the tops and sides, removing thick stems, and clearing what was cut.
The row is rated Medium and listed as Active collection. Hedge species, heights, lengths and the tools used are Not stated beyond the two tool types the row names, and so is any success or quality label for a trimmed hedge.
What is not covered
Indoor plant care and watering, greenhouse and nursery tending, and harvesting produce sit on the plant care and gardening page and in other Agriculture & Grounds environments. The farm environment also lists planting and pruning rows of its own. This page lists them as neighbours and does not count them as landscaping rows.
Raking leaves, leaf blowing, edging lawns, weeding and mulching planting beds are tasks people often expect here, but the site states none of them as a catalog row.
Why it is hard
The catalog describes work done with "hand and power tools", "hedge trimmers and loppers" and general grounds maintenance across commercial property, parks and campuses. The site does not state terrain, weather, season, lighting or plant properties, so this page makes no claim about them. What the site does state is what egocentric video puts into the training distribution: hands entering the frame from below, occlusion during grasp and motion blur during reach.
The site also states why a hand pose stream matters here. RGB alone leaves a model to infer 3D hand structure it cannot see reliably through occlusion and motion blur. Firsthand delivers 3D hand pose as handJoints[2][21][3] in metric units in the head-camera frame, with a visibility flag per joint, aligned to depth and RGB. Two hands of 21 joints each are tracked per frame, and the flag records which of them were hidden behind a tool or foliage.
Setting and privacy
The catalog places the rows in a farm environment and a commercial grounds environment. The site names no park, campus, golf course, farm or grounds crew, and it does not state capture at a customer own site or facility. Environment, access and schedule are agreed in the spec, and the number of sites is Not stated.
Every episode links to a signed contributor release through a documented consent chain. Faces, plates and screens are detected and irreversibly blurred at ingest, a reviewer confirms the result before anything ships, and the anonymization record is delivered with the data. An undocumented bystander is also a stated reject criterion, and the site states no further privacy rule specific to outdoor sites.
Capture setup
A head-mounted phone records the first-person view of real work on site, and a multiview rig adds synchronized third-person angles when the spec asks for them. Both are the capture modes the catalog lists for every grounds row.
The site states a head camera at 3840 × 2160 and 60 fps for its instrumented rig, but no camera count, resolution or frame rate for the grounds rows, so the capture tier is agreed in the spec.
Streams and labels
Each episode follows the Firsthand episode schema: ten streams synced under 2 ms, with head and wrist RGB, depth, 3D hand pose with per-joint visibility, contact and grasp events, and frame-accurate action segments. For grounds work, hand pose tracks how the fingers hold a tool, contact events mark when fingers or a tool meet a plant or surface, and action segments mark each step.
Object labels use the terms your spec sets. Force or tactile data, and success or quality labels for a mown area, a cleared path or a trimmed hedge, are Not stated. They are defined in the spec if your policy needs them.
Gloves
The site offers a tactile glove tier as a pilot-ready option. The gloves track the hands, the glove signal is time-synced to a head-mounted stereo camera by hardware timestamps and an IMU, each glove is calibrated every session, and the pipeline checks signal dropout and sync drift.
The site does not state that the glove tier has been used on any grounds row, and it does not state whether gloves fit work with power tools or outdoors. Treat force and tactile data as Not stated for these rows unless a spec adds the glove tier and agrees the fit with you.
Quality gates
Episodes are machine-checked at ingest against the stated reject criteria, listed in the table below, and a human reviewer then checks the result.
It does not state how often a plant or tool leaves the view outdoors, and it states no blur or sharpness rule. A rejected item goes to the reject log and is recaptured at our cost.
Delivery
Delivery formats are RLDS, LeRobot and WebDataset, plus HDF5, zarr and Rerun .rrd. The format table below sets each against what its official documentation states. Landscaping episodes use the same schema as every other Firsthand collection, so a loader that reads another Firsthand dataset reads this one without changes.
Every batch is validated against signed accept criteria before it ships, with a reject log, and delivery is rolling, per validated batch.
Fast · on demand
Where coverage is already deep, the first validated batch lands in a median of 48 hours from signed spec. Thin environments typically take three to four weeks, because vetting operators there is the bottleneck, and we quote that up front.
On-demand top-ups run against the same spec and accept criteria after each training run. The site lists the grounds rows as Active collection or Ready to deploy and states no capture timeline for them beyond a quote against your spec.
The spec
You describe the areas, tasks and sequence your policy needs. We turn that into a written spec covering tasks, environments, capture tier, annotation depth and accept criteria, then quote reach, timeline and price before any capture begins.
A Spec Pilot, a small and fast first batch, can prove the spec and accept criteria before you scale. Billing is per validated hour, and every collection ships under a perpetual, buyer-owned commercial license.
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
| Environment | Catalog task and description | Skill | Status |
|---|---|---|---|
| Landscaping & Groundskeeping | Landscaping & Groundskeeping: mowing, trimming, planting and general grounds maintenance on commercial property | Medium | Active collection |
| Farm & Field Operations | Agriculture Landscaping & Groundskeeping: mow, trim, plant and clear grounds and paths on the farm with hand and power tools | Medium | Ready to deploy |
| Farm & Field Operations | Prune and trim hedges using hedge trimmers and loppers: cut hedge tops and sides with trimmers, remove thick stems with loppers and clear cuttings | Medium | Active collection |
Streams and tasks
| Stream or label | Status on this site | What it carries in a landscaping episode |
|---|---|---|
| Head and wrist RGB, depth | Stated; ten streams synced under 2 ms | Keeps the tool, the plant or ground and both hands on one timeline |
| 3D hand pose, per-joint visibility | Stated; two hands of 21 joints, with a visibility flag per joint | Carries how the fingers hold a tool and which joints were hidden |
| Contact and grasp events | Stated | Marks when fingers or a tool meet a plant or surface |
| Action segments | Stated; frame-accurate | Separates mowing, trimming, planting, clearing and pruning steps |
| Object labels | Set by your spec | Names the areas and steps in the terms your policy uses |
| Force or tactile data | Glove tier stated; use on grounds rows Not stated | Added only if a spec includes the glove tier |
Quality gates
| Reject criterion | Status on this site | On outdoor grounds |
|---|---|---|
| Manipulated object out of frame for more than 15 percent of the episode | Stated | Applies to every episode; how often a plant or tool leaves the view is Not stated |
| More than 35 percent invalid depth pixels in the manipulation region | Stated | Applies to every episode; depth behaviour outdoors is Not stated |
| Sync breach beyond the ceiling for more than three consecutive frames | Stated | Applies to every episode |
| Calibration drift beyond tolerance | Stated | Applies to every episode |
| Undocumented bystander | Stated | Applies to every episode; the episode is rejected |
| Mismatch against the named skill spec | Stated | Checked against the task and steps your spec names |
| Blur or sharpness rule | Not stated | Set in the spec if your policy needs one |
What is not stated
| Item | Status on this site | Where it is settled |
|---|---|---|
| Equipment and tool lists, and tool models | Not stated beyond the tools named in the catalog rows | The written spec |
| Lawn, hedge and site sizes | Not stated | The written spec |
| Plant species | Not stated | The written spec |
| Seasons, weather and lighting conditions | Not stated | The written spec |
| Raking, leaf blowing, edging, weeding and mulching | Not stated as catalog rows | The written spec, if needed |
| Number of sites, crews or episodes | Not stated | The written spec |
| Throughput | Not stated | Quoted against your spec |
| Force or tactile data on grounds rows | Not stated | The written spec, if needed |
| Success or quality labels, robot results | Not stated | The written spec, if needed |
Formats
| Format | What the official documentation states | Used for here |
|---|---|---|
| RLDS | A dataset is retrieved as episodes, and each episode holds a dataset of steps (RLDS repository README) | Episode-based training loaders |
| LeRobot | LeRobotDataset v3.0 is a standardized format for robot learning data, including multi-camera video, with many episodes stored per Parquet or MP4 file (LeRobot documentation) | LeRobot dataset format and tooling |
| WebDataset | Tar files in which files that belong together share a basename, split into numbered shards (WebDataset README) | Sharded streaming for large training runs |
| HDF5 and zarr | Stated by Firsthand only | Array storage for custom pipelines |
| Rerun .rrd | Stated by Firsthand only | Multi-stream synchronized playback for review |
FAQ
Sources
Tell us the areas, tasks and sequence your policy needs to handle. We will quote reach, timeline, and price against a written spec, with a first validated batch in a median of 48 hours where coverage is deep.