Stereo Landscaping and Groundskeeping Data

It is first-person video of a person working commercial grounds: mowing, trimming, planting and general maintenance, recorded from their own point of view with two calibrated cameras and with hand pose and sensor streams alongside. The task is the one row the site’s catalog lists for it. Stereo describes the capture, and MCAP describes the container. They are separate choices.

The site does not state that stereo is already running on this row. The catalog lists a head-mounted phone or a multiview rig as the capture setup, and a stereo pair is a capture choice agreed in the skill spec and confirmed on a Spec Pilot. The data is human capture by paid, consented contributors, not robot or teleoperation data. Firsthand is not affiliated with Foxglove or the MCAP maintainers.

One, named "Landscaping & Groundskeeping", in the Landscaping & Groundskeeping environment of the Agriculture & Grounds sector. Its listed examples are commercial grounds, parks, corporate campuses and golf courses, and its description reads "Mowing, trimming, planting and general grounds maintenance on commercial property."

The row is rated Medium, lists a head-mounted phone or a multiview rig as the capture setup, and is listed as Active collection. The site says nothing further about what that status means in volume, hours or delivered stereo footage, so this page claims none, and what applies to a given order is confirmed when you request the quote. This page names only the tasks that appear in the row: mowing, trimming, planting and general grounds maintenance. The first table below reproduces the row as the catalog states it.

No claim is made. The catalog row says commercial property, and the site makes no residential yard-work claim, so this page makes none either. Whether a residential site could be captured is Not stated and would be raised in the spec, not assumed.

The egocentric landscaping and groundskeeping page covers three grounds rows, including this one, as egocentric capture, with a farm row and a hedge pruning row beside it. It does not give a stereo and MCAP treatment of them. The stereo heavy machinery operation page is the stereo treatment of machinery rows and makes no landscaping or grounds claim.

This page is the stereo and MCAP treatment of the one commercial grounds row. The site does not list an off-the-shelf landscaping or groundskeeping dataset, so this work is custom collection. The comparison table below sets the pages side by side.

Grounds work is a sequence of passes over uneven ground and living plants, done with a tool that is often near the hands. A stereo pair recovers depth from the calibrated frame pair rather than from a standalone depth sensor, so the tool, the surface under it and the hands share a frame.

The site gives no depth accuracy figure and no label for lawn height, cut quality, planting depth or a finished area, so whether those are resolvable in depth is Not stated. How stereo depth behaves in sunlight, shade, wet ground or moving foliage is Not stated, and a spec should check it on a Spec Pilot. Capture at your own facility is listed as not offered.

The site describes two stereo setups and does not say which one a grounds order uses. The hard-environments stack is a global-shutter 4K/60 head camera with a 120° lens, two 1080p/60 wrist cameras, a depth sensor at 848×480 and 30 fps, and 200 Hz 6-DoF IMUs. The off-the-shelf stereo head rig, dataset 06, is dual fisheye cameras at 1080p per eye, a 62 mm baseline, per-unit calibration, a 9-axis IMU and hand-tracking output.

Which rig, resolution and streams a grounds order uses is Not stated on the site, and the third table below sets what is stated beside what is not. Intrinsics and extrinsics are re-solved at the start and end of every session, and streams are hardware-triggered onto one clock with a 2.0 ms cross-stream ceiling. The catalog states that a multiview rig adds synchronized third-person angles when the spec asks for them, and wrist cameras give a closer view of the hands.

MCAP is an open source container file format for multimodal log data, supporting multiple channels of timestamped pre-serialized data. It is serialization-agnostic, so messages can be Protobuf, DDS (CDR), ROS, JSON and more. Its design is row-oriented and append-only, it stores schemas alongside the data, and it offers an optional index plus optional LZ4 or Zstandard chunk compression.

Reader and writer libraries exist for C++, Go, Python, Rust, Swift and TypeScript, and the mcap CLI can inspect, merge and split files. The foxglove/mcap repository is MIT-licensed; that is the MCAP project’s licence, not the licence of a Firsthand delivery. The MCAP hub page and the glossary entry cover the format in full.

Firsthand offers MCAP delivery, and dataset 06 is stated as shipping as MCAP. For grounds work the site states hand pose, a stereo-derived depth stream with confidence maps, IMU, contact events, action segments and per-frame instance masks elsewhere. What it does not state is which of those are channels in an MCAP file, how they are named, what encoding they use or at what rate.

No topic name, message schema or rate is stated on this page, and none should be assumed. Name the streams that matter in the skill spec and confirm them on a Spec Pilot batch. The fourth table below sets each stream beside what the site states about it.

Occlusion is the first risk. A tool or foliage hides the fingers that hold it, and the plant or surface being worked can leave the view. The visibility flag on each joint is the answer the site gives, contact events mark when a hand or tool meets a plant or surface, masks are recorded per frame, and a spec can ask for wrist views so a grip the head camera loses is still recorded.

Sequence is the second. Mowing, trimming and planting are separate sequences, so the spec decides how each is split into action segments. A spec that says only “maintain the grounds” gives one long segment. Terrain, weather, season, lighting, glare, vibration and motion blur are Not stated for this task and are raised in the spec. Force and tactile readings are not among the listed streams of standard capture, and no label is stated for cut quality or finished area.

Calibration is the third, because stereo depth is only as good as the rectification behind it: calibration is measured at the start and end of every session under a 0.28 px RMS gate. An episode is also rejected when the manipulated object is out of frame for more than 15 percent of it, when more than 35 percent of depth pixels in the manipulation region are invalid, or when an undocumented bystander appears, and a reject log ships with every batch.

Nothing beyond the row. Safety certifications, protective equipment, equipment models, site and lawn sizes, weather limits, cycle times and throughput are Not stated for this row, and this page makes no such claim. What a contributor may wear, do or show is agreed in the spec.

For every delivered episode the site states that faces, plates and screens are blurred irreversibly, and that footage that cannot be de-identified is discarded. An undocumented bystander is a stated reject criterion. How the public on or near commercial grounds is handled beyond that general rule is Not stated and is settled in the spec before capture.

The site lists no off-the-shelf landscaping or groundskeeping dataset, so this work is custom collection. The only stereo head rig the site states as shipping as MCAP is dataset 06, and this page does not claim off-the-shelf stereo coverage of grounds work. Custom collection covers the rest: 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. The site does not say which speed applies to a stereo grounds order, and the catalog lists the row as Active collection without defining it further, so the timeline is quoted against your spec. Collections are billed per validated hour, and rejected episodes and recaptures are never billed.

Describe the tasks and where each starts and ends: the areas, the mowing, trimming and planting steps, the start state of each area, what counts as a reject, and the variation your pipeline is missing. Then name the streams you want in the file, the topic naming and message encoding your reader expects, whether calibration ships inside the file or beside it, and whether MCAP is the only delivery or sits beside RLDS, LeRobot or WebDataset.

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 fifth table below shows what each spec element decides.