Stereo Tire and Wheel Service Data

It is first-person video of a person servicing tires and wheels, recorded from their own point of view with two calibrated cameras and with hand pose and sensor streams alongside. The tasks are the five rows the site’s catalog lists for it in Auto Service Center & Tire Shop. Stereo describes the capture, and MCAP describes the container. They are separate choices.

The site does not state that stereo is already running on these rows. 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.

Five, all in the Auto Service Center & Tire Shop environment under the Automotive & Transport sector, all rated Medium. "Dismount and mount tires using a tire changer and bead lubricant" is described as breaking the bead, dismounting the tire on the machine, lubricating the bead and mounting the new tire. "Dismount, mount, and balance tires using a tire machine and a wheel balancer." is also listed. Both are Active collection.

"Tire Dismount & Mount" is described as removing the wheel, dismounting the tire on the machine and mounting and seating a new one. "Wheel Balancing" is described as mounting the wheel on the balancer, spinning it, reading the result and fitting weights to the rim. "Tire Rotation & Pressure Check" is described as swapping wheels between positions, checking tire pressure with a gauge and adjusting to spec. These three are Ready to deploy.

All five list a head-mounted phone or a multiview rig as the capture setup. The first table below reproduces them as the catalog states them. This page names only the tools and steps that appear in those rows: a tire changer, a tire machine, a wheel balancer, bead lubricant, a gauge, tires, wheels and rims, and breaking the bead, dismounting, lubricating, mounting, seating, balancing, fitting weights, swapping wheels and checking pressure.

The egocentric tire and wheel service page covers the same tire rows as first-person capture with ten streams, and also covers wheel and tire dressing, wheel removal inside brake rows and lug-nut questions. It has no stereo or MCAP treatment. The egocentric vehicle maintenance page covers the oil, filter, battery, brake and diagnostic rows in the same environment and leaves the tire and wheel rows to their own page. The stereo car detailing page covers three polishing, claying and drying rows in a different environment.

This page is the stereo and MCAP treatment of just the tire changer, wheel balancer, tire dismount and mount, and rotation rows. It does not repeat the brake, fluid or dressing rows. The comparison table below sets the pages side by side.

Tire service is about the state of a wheel: whether the bead is broken, whether the tire is on or off the rim, whether the wheel is seated on the balancer, whether weights have been fitted. A stereo pair recovers depth from the calibrated frame pair rather than from a standalone depth sensor, so the wheel and the machine share a frame with the hands. The site gives no depth accuracy figure and no label for a bead, a seat or a balancer reading, so whether those are resolvable in depth is Not stated.

The hard-environments page states that stereo keeps working outdoors where active depth sensors struggle, and that many programs capture both and sync them on one clock. The catalog lists a car garage, a dealership service bay and tire rotation among the examples for this environment, but the site does not say where any batch is captured, so the setting is agreed in the spec.

The site describes two stereo setups and does not say which one a tire service 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 tire service 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 site states that the vehicle itself can occlude the view in a service bay, so a spec can ask for a second angle from a multiview rig.

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 tire and wheel work the site states hand pose, a stereo-derived depth stream, 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.

Hands are the first risk. A wheel is gripped with both hands and a tire is worked over the rim, so the contact point is often hidden behind the wheel or the machine. The visibility flag on each joint is the answer the site gives, and contact events mark when a hand or tool meets an item. A spec can also ask for wrist views, so a grip the head camera loses is still recorded.

The vehicle is the second. The site states that the vehicle can occlude the view in a service bay, and that under-vehicle capture is hostile to infrared depth because painted and oily surfaces absorb the projector pattern, with a depth-quality flag delivered instead of silent interpolation. It does not say how a stereo pair behaves on a rim or a tire, so this page promises no figure.

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 or an undocumented bystander appears, and a reject log ships with every batch.

A service bay is a shared space, so bystanders matter, and a vehicle carries plates. For every delivered episode the site states that faces, plates and screens are blurred irreversibly, licence plates and VIN plates in service-bay footage without exception, and that footage that cannot be de-identified is discarded.

The site states no contributor safety protocol, no torque, tire-pressure or balance values, no seating or balancing result and no certification for any tire row, so this page describes none. Capture at your own facility is listed as not offered.

Off-the-shelf covers what is already in stock: the stereo category lists the stereo datasets and hand-tracking video, and only dataset 06 is stated as MCAP. This page does not claim off-the-shelf coverage of the tire rows. 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 tire rows are Active collection or Ready to deploy, but the site does not say which speed applies to a stereo order, so ask when you request the quote. Collections are billed per validated hour.

Describe the machine, the wheels, the setting and the steps in order, what counts as one completed job, 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.