Depth of the wheel, the valve and the gauge
The site states that a stereo pair at human-eye spacing makes depth recoverable from every frame pair, so the wheel, the gauge, the tire and the hands that hold them sit in one frame.
Now recruiting capture teams worldwide. Get paid to record first-person video of real work.
Apply to captureTask family
Why stereo and MCAP here
The site states that a stereo pair at human-eye spacing makes depth recoverable from every frame pair, so the wheel, the gauge, the tire and the hands that hold them sit in one frame.
A wheel is lifted, carried and fitted, and a gauge is pressed onto a valve. Either can hide the fingers that hold it. 3D hand pose carries a per-joint visibility flag, so a hidden finger is flagged as hidden rather than silently guessed.
The order matters: the row moves wheels first and checks pressure after. Streams are hardware-triggered onto one clock with a 2.0 ms cross-stream ceiling, and action segments carry start, end, verb and noun as the skill spec defines them.
MCAP stores multiple channels of timestamped, pre-serialized data, so a stereo pair, hand pose and IMU can share one file on one log-time axis. Which streams go in the file is set in the skill spec.
Definition
It is first-person video of a person rotating tires and checking their pressure: swapping wheels between positions, checking tire pressure with a gauge and adjusting to spec. It is recorded from their own point of view with two calibrated cameras, with hand pose and sensor streams alongside. The task is the one the site’s catalog lists in a single row. 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 stereo applies here only through the site’s general stereo offer: 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, and this page makes no claim that any robot has been trained on it. Firsthand is not affiliated with Foxglove or the MCAP maintainers.
Catalog row
One, in the Auto Service Center & Tire Shop environment of the Automotive & Transport sector. It is named "Tire Rotation & Pressure Check", and its catalog description reads "Swap wheels between positions, check tire pressure with a gauge and adjust to spec." It is rated Medium, its status is Ready to deploy, and its capture setup is a head-mounted phone or a multiview rig.
The site defines Ready to deploy plainly: contributors and site access are set up and capture starts once a spec is signed. It is not the same as Active collection, where recording is already running, and it is not Available on request, where the work is scoped and recruited to spec when a buyer asks. The site says nothing further about volume, hours or delivered stereo footage for this row, so this page claims none. It names only the items that appear in the row: wheels, tires and a gauge. The first table below reproduces the row and its neighbours as the catalog states them.
Difference
The egocentric tire rotation and pressure check page covers the same row as first-person capture and lists RLDS, LeRobot, WebDataset, HDF5, zarr and Rerun .rrd as delivery formats. It does not centre a stereo pair or MCAP. The egocentric tire and wheel service page covers the whole family of tire and wheel rows, and the egocentric wheel and tire dressing page covers cleaning wheels and tires and applying dressing.
The stereo tire and wheel service page gives stereo and MCAP treatment to the full set of five tire and wheel rows, and rotation is one of them. This page gives the rotation and pressure check row its own stereo and MCAP treatment, stream map and failure modes. The stereo car battery page treats a different job in the same environment. The comparison table below sets the pages side by side.
The steps
The row names three actions in order: swap wheels between positions, check tire pressure with a gauge, and adjust to spec. The swap is handling work: lifting a wheel, carrying it, lining it up and fitting it at a new position. The data needs to show the grip on the wheel and where it ends up, and a spec decides whether each wheel is a separate episode or part of a longer one.
The check is the small, precise half. The data needs to show the gauge, the valve and both hands, and a spec decides whether reading the gauge and adjusting are steps of their own. The site gives no rotation pattern, no wheel count, no vehicle type, no pressure value and no gauge type for the row, and it states no task time. Which wheels move to which positions and where an episode starts and ends are agreed in the spec rather than assumed. The row does not describe lifting or jacking a vehicle, and this page gives no lifting, jacking or shop safety instruction.
Why stereo
A rotation is close-range work: two hands taking the weight of a wheel, a wheel lined up against a hub, a gauge pressed onto a valve. A stereo pair recovers depth from the calibrated frame pair rather than from a standalone depth sensor, so the wheel, the gauge, the valve and the hands share a frame. That is the case the pair is for in stereo tire pressure gauge video, where the question is how close the wheel sits to its new position and how the hand closes on the gauge.
The site also states that depth degrades on wet and reflective surfaces and handles that with per-frame confidence maps. It states no depth accuracy figure for tire work, so whether a valve stem or a gauge head is resolvable in depth is Not stated, and a spec should check it on a Spec Pilot.
Capture setup
The site describes two stereo setups and does not say which one a tire rotation 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 rotation 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, which matters in a service bay because the vehicle can block the first-person view. The site does not state where the work is done in a bay, so this page does not describe the layout.
MCAP
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.
Streams
Firsthand offers MCAP delivery, and dataset 06 is stated as shipping as MCAP. For tire 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.
Failure modes
Occlusion is the first risk. A wheel or a gauge can hide the fingers that hold it, and the vehicle can block the first-person view. The visibility flag on each joint is the answer the site gives, contact events mark when a hand takes hold of an item, masks are recorded per frame, and a spec can ask for wrist views or a second angle so a grip the head camera loses is still recorded. The site does not say whether a wheel or a gauge counts as the object for contact events, so settle it in the spec.
The gauge reading is the second. The row describes checking pressure with a gauge, but the site states that screens are detected and blurred at ingest and does not say whether a gauge display counts. Whether the reading stays legible in the delivered video is Not stated, so decide in the spec whether it matters before capture. Surfaces are the third: the site states that depth degrades on wet and reflective surfaces and that automotive episodes can carry a depth-quality flag instead of being silently interpolated. How a stereo pair behaves around a wheel and a tire is Not stated, so ask for the flag and the confidence maps to be delivered with each episode.
Sequence is the fourth. A spec saying "rotate the tires" gives one long action segment, while a spec naming the swap, the reading and the adjustment gives a sequence that can be sliced by step. The row does not say what one episode covers, so the spec decides. Pressure values, gauge types, rotation patterns, wheel counts, vehicle or tire types, task times, throughput, force or tactile data and any safety or certification claim are Not stated and are not claimed on this page.
Calibration is the fifth, 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.
Privacy
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. It also states that licence plates and VIN plates in service-bay footage are blurred at ingest without exception. Every episode links to a signed contributor release through a documented consent chain, and the anonymization record ships with the data.
Text on a tire sidewall is not listed as a blur category on the site, so this page does not claim it is blurred. Whether shop signage, a work order or a customer’s documents are blurred beyond the general rule is also Not stated. Raise any such rule in the spec.
Scale
This is custom collection: custom collection at scale through a network of thousands of capture providers, for a consistent, recurring data flow to labs. The site states no provider count or throughput for this row, and none is claimed here. The off-the-shelf stereo and hand-tracking video page shows what the stereo rig delivers, and the custom order applies it to your task.
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 row is currently Ready to deploy, and the site does not say which speed applies to a stereo rotation order, so the timeline is quoted against your spec. On-demand top-ups run against the same spec and accept criteria after each training run. Collections are billed per validated hour, and rejected episodes and recaptures are never billed.
Ordering
Describe the steps and where each starts and ends: the wheel swap, the gauge reading and the adjustment. Name the wheels and positions you expect to see, whether an episode covers one wheel or a full set, whether the gauge reading must stay legible, 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. Delivery is rolling, per validated batch, under a perpetual, buyer-owned commercial license, with exclusivity available. The fifth table below shows what each spec element decides.
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 row
| Task (as listed) | Description (as listed) | Skill | Capture setup | Status |
|---|---|---|---|---|
| Tire Rotation & Pressure Check (this page) | Swap wheels between positions, check tire pressure with a gauge and adjust to spec. | Medium | Phone (head-mounted) / multiview rig | Ready to deploy |
| Tire Dismount & Mount | Remove the wheel, dismount the tire on the machine and mount and seat a new one. | Medium | Phone (head-mounted) / multiview rig | Ready to deploy |
| Wheel Balancing | Mount the wheel on the balancer, spin it, read the result and fit weights to the rim. | Medium | Phone (head-mounted) / multiview rig | Ready to deploy |
| Wheel & Tire Dressing | Clean wheels and tires and apply dressing to the rubber and wheel faces. | Easy | Phone (head-mounted) / multiview rig | Ready to deploy |
Compared pages
| Page | What it covers | Treatment of tire rotation and pressure check |
|---|---|---|
| This page: stereo tire rotation and pressure check data | The one rotation and pressure check row in Auto Service Center & Tire Shop | Stereo pair and MCAP delivery, stream map and failure modes for this row only |
| Egocentric tire rotation and pressure check data | The same row as first-person capture | The steps in order, capture setup and labels; RLDS, LeRobot, WebDataset, HDF5, zarr and Rerun .rrd delivery; stereo and MCAP are not its focus |
| Stereo tire and wheel service data | Five tire and wheel rows with a stereo pair and MCAP delivery | Rotation is one of five rows; this page narrows to it |
| Egocentric tire and wheel service data | The whole family of tire and wheel rows as first-person capture | One row among several, as egocentric capture |
| Egocentric wheel and tire dressing data | Cleaning wheels and tires and applying dressing (Easy) | Not covered; surface finishing, not wheel swaps or gauge checks |
| Stereo car battery test and replacement data | The three battery rows with a stereo pair and MCAP delivery | Not covered; these are battery rows, not tire rows |
| Egocentric stereo data in MCAP | The stereo and MCAP hub across tasks | General stereo and MCAP treatment; not specific to tire work |
Stated vs not stated
| Item | What the site states | For a stereo rotation order |
|---|---|---|
| Catalog capture setup | Phone (head-mounted) / multiview rig on the row | A stereo pair is a spec choice; not stated on the row |
| Stereo head rig (dataset 06) | Dual fisheye, 1080p per eye, 62 mm baseline, per-unit calibration, 9-axis IMU, hand-tracking output; shipped as MCAP | Whether a rotation order uses it: Not stated |
| Hard-environments stack | 4K/60 head camera, 120° lens; two 1080p/60 wrist cameras; depth 848×480 at 30 fps; 200 Hz 6-DoF IMU | Whether a rotation order uses it: Not stated |
| Objects, hands and masks | Per-frame instance masks stored at 848×480; per-joint visibility flag on hand pose; contact events | Stated; whether a wheel or a gauge counts as the object is Not stated |
| Gauge display | Screens are detected and blurred at ingest | Whether a gauge display counts, and whether the reading stays legible: Not stated |
| Depth around a wheel | Stereo depth degrades on wet and reflective surfaces with per-frame confidence maps; automotive episodes can carry a depth-quality flag | Behavior of a stereo pair around a wheel and a tire: Not stated |
| Calibration | Measured every session and shipped with the episode; 0.28 px RMS reprojection gate | Stated |
| Synchronization | Hardware-triggered onto one clock; 2.0 ms cross-stream ceiling | Stated |
| Row status | Ready to deploy | No volume, hours or delivered stereo footage is claimed on this page |
| Pressure values, gauge types, rotation patterns, wheel counts, vehicle or tire types | Not stated | Agreed in the skill spec, or not claimed on this page |
| Task times, throughput, safety or certification claims | Not stated | Not claimed on this page |
| MCAP topics, schemas, rates | Not stated | Agreed in the skill spec |
Stream map
| Stream or item | What the site states | In an MCAP delivery, as the site states it |
|---|---|---|
| Stereo pair | Dual fisheye, 1080p per eye, 62 mm baseline (dataset 06) | Dataset 06 is stated as shipped as MCAP; channel layout not stated |
| Depth with confidence maps | Recovered from the calibrated stereo pair; confidence map masks low-confidence regions | Not stated |
| Hand pose | 21 joints per hand with a per-joint visibility flag | Channel layout and joint order not stated |
| IMU | 9-axis (dataset 06); 6-DoF at 200 Hz (hard-environments stack) | Channel layout and rate not stated |
| Contact events, action segments, instance masks | Listed in the site’s episode schema; masks stored at 848×480 | Not stated |
| Task instruction | One per episode | Not stated |
| Calibration | Measured every session and shipped with the episode | Placement in the file not stated |
| Topic names, schemas, encoding, rates | Not stated | Agreed in the skill spec |
Skill spec
| Spec element | What it decides | Where it shows up |
|---|---|---|
| Tasks and order | What one step is: the wheel swap, the gauge reading or the adjustment | Episode boundaries and action segments; set per program |
| Episode scope | One wheel or a full set | Set per program; the site does not state an episode length for this row |
| Rig and streams | Stereo pair, wrist views, a second angle, hand pose, IMU and any others | The channels you can read; confirm on the Spec Pilot |
| Object definition | Whether a wheel, a valve or a gauge counts as the object | Contact events; set per program |
| Gauge reading | Whether the gauge display must stay legible | Blurring of screens in the delivery; set per program |
| Step labels | Whether swap, read and adjust are separate labelled steps | Action segments; set per program |
| MCAP topics and encoding | What your reader expects | Set per program |
| Calibration delivery | Inside the file or beside it | Set per program |
| Delivery format | How the data is packaged | MCAP alone, or beside RLDS, LeRobot, WebDataset, HDF5 or zarr |
| Accept criteria | What passes QA, including what counts as a reject | Reject log per batch |
| Privacy | How people, plates and screens in frame are protected | Faces, plates and screens blurred at ingest |
| License | Who owns the dataset | Perpetual, irrevocable, buyer-owned, non-exclusive by default |
Example footage
One real clip already published on this site, shown as a format and rig example: a head-mounted stereo capture with hands in frame. It does not show tire rotation or a pressure check.
No tire rotation or pressure check clip is published on the site, so this is labelled as a format and rig example. Request a sample to see delivered files. See stereo sample page, stereo + wrist-cam example videos, request an egocentric data sample.
FAQ
Sources
Tell us the wheels and positions, whether an episode covers one wheel or a full set, how the gauge is handled, whether the reading must stay legible, the streams you want in the file and whether MCAP sits alone or beside a training format. We will quote reach, timeline and price against a written spec.