Stereo Product Labeling Data

It is first-person video of a person applying product and barcode labels to units or cartons, recorded from the worker’s own point of view with two calibrated cameras, with hand pose and sensor streams alongside. 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 their capture setup, so 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, so using it for a specific robot still needs your own retargeting step. Firsthand is not affiliated with Foxglove or the MCAP maintainers.

Two, listed in lib/commercial-catalog-data.ts, both in the Plastic & Light-Assembly Manufacturer environment of the Manufacturing & Workshops sector. "Labeling" is described as "Apply product and barcode labels to units or cartons by hand or with a label gun." "Packaging operations" is described as "Pack finished units into boxes with inserts, seal and label them for dispatch." Both are rated Easy.

Both are listed as Ready to deploy. The site states no delivered hours and no delivered stereo footage for them, so this page claims none. The environment examples read "Consumer goods assembly, packaging operations, labeling, quality inspection on a production line", which are kinds of work, not named firms, and this page names none. The first table below reproduces the rows as the catalog states them. The second row is a packing sequence in which sealing and labeling are the last steps, so a spec decides whether an episode covers the label alone or the whole pack-out.

This page is the stereo and MCAP treatment of product and barcode label application on a manufacturing packaging line. The stereo warehouse sorting and labeling page covers three Warehouse & Distribution Center rows in which boxes are printed, labelled and sorted by type, carrier or route, a warehouse job with sorting carts and a label printer, not a production line.

The egocentric barcode scanning and labeling page covers scanning, printing, applying and tagging across many environments and treats the Labeling row as one entry in a long list, with first-person capture as its subject rather than stereo. The egocentric heat sealing and labeling page covers two Food & Beverage Manufacturing Plant rows built around a heat sealer and a label applicator. The stereo order packing and taping page covers four warehouse rows in which an order is picked, packed, taped and labelled. The second table below sets the pages side by side with each status as the site lists it.

The catalog lists "Phone (head-mounted) / multiview rig" for both rows, and the plastic and light-assembly manufacturer environment page lists the same capture setup. The site does not state a head-mounted stereo setup for either row. Stereo applies through the site general stereo offer: a stereo pair is a capture choice agreed in the skill spec and confirmed on a Spec Pilot.

A multiview rig adds synchronized third-person angles, and wrist cameras give a closer view of the hands, when the spec asks for them. Whether a stereo pair is worn, mounted or combined with a multiview rig on these rows is Not stated, and so is where a rig sits relative to the labeling position. The site also states that Firsthand does not capture at a customer’s own facility, so the line or bench used is agreed in the spec.

Labeling is about where the label meets the unit or carton, how the fingers hold the label and the target and how a label gun is aimed at the surface. A stereo pair recovers depth from the calibrated frame pair rather than from a standalone depth sensor, so the geometry sits in the same capture that shows the hands working. The site gives no depth accuracy figure for these rows, so what a buyer does with that depth is their pipeline’s question.

A stereo pair adds depth, not a verdict. The site states 1080p per eye for dataset 06, and whether that resolves the edge of a label or a printed barcode at working distance is Not stated, so a spec should check it on a Spec Pilot. The egocentric barcode scanning and labeling page already supplies the first-person view and its ten streams; stereo is the addition for a buyer who wants the depth and the MCAP file.

The rows give a natural cut: pick up the unit or carton, apply the product or barcode label by hand or with a label gun, and set the labelled item aside. For the second row the cut extends to packing the unit into a box with inserts, sealing it and labelling it for dispatch. The stages are the catalog’s own wording, except that picking up and setting aside are an illustration of how a spec can cut an episode, not a stated duration.

A spec that says "label the unit" gives one long action segment. A spec that names the steps gives a sequence you can slice by step, and the site does not set an episode length or say how many units make up an episode. Contact events can mark when a hand meets a unit, a carton, a label or a gun, where the spec asks for them, and the spec decides what counts as the item.

A label, a thumb and a carton face can all sit between the lens and the surface being labelled. The site states that fingers disappear behind objects, which is why each hand joint carries a visibility flag, and that reach and grasp frames are where blur and occlusion show up. The egocentric light assembly material says small parts can be hidden by fingers. The head camera is global-shutter, which avoids rolling-shutter skew.

The site gives no figure for how often a finger is hidden on this job, and no placement tolerance, label size or alignment requirement, so a spec can ask for wrist views or a second angle and check it on a Spec Pilot. The site states no applied-pressure, gun-trigger or tool-pose stream, and this page does not claim one.

The rows describe applying labels, and a stereo pair can show the label, the surface and the hands in three dimensions. The site lists no label-placed, label-straight, label-readable or completion label for these rows, so none is claimed. Whether a placement counts as correct is a judgement a buyer’s pipeline or spec has to define.

The site also does not state that footage carries decoded barcode values, read label text or a scan result, so none is claimed here either. An episode is rejected when the manipulated object is out of frame for more than 15 percent of it, and for a labeling job the spec decides what that object is: the unit, the carton, the label or the gun. Label size, symbology, adhesive, printer or gun brand, placement tolerance, line speed, error rate and cycle time are Not stated.

Safety procedures for these rows are Not stated, and this page makes no safety or compliance claim. Tool brands, label printer models and label gun models are Not stated, and so are customer names.

For every delivered episode the site states that faces, plates and screens are blurred irreversibly, that a reviewer confirms the result before anything ships, and that footage that cannot be de-identified is discarded. How other printed text, such as text on a label or a carton, is handled is agreed in the spec. The anonymization record ships with the data, an undocumented bystander is a stated reject criterion, and every episode links to a signed contributor release. This is not legal advice, and the executed agreement controls.

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 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 these rows the site states hand pose, a stereo-derived depth stream with confidence maps, IMU, contact events, action segments, per-frame instance masks and one task instruction per episode 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.

Hand and label occlusion is the first risk, under the visibility flag above. Invalid depth on glossy or low-texture surfaces is the second: an episode is rejected when more than 35 percent of depth pixels in the manipulation region are invalid, and confidence maps ship with depth.

Calibration is measured at the start and end of every session under a 0.28 px RMS gate, and an episode is rejected for a sync breach beyond the ceiling for more than three consecutive frames, for an undocumented bystander or for a mismatch against the named skill spec. A reject log ships with every batch. The fifth table below lists the failure modes beside what the site states.

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 product labeling or packaging-line dataset among them, so this work is custom collection, not an off-the-shelf purchase. The off-the-shelf stereo and hand-tracking video can still show the format before you write a spec.

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. The site does not say which speed applies to these rows, so the timeline is quoted against your spec. Collections are billed per validated hour, and rejected episodes and recaptures are never billed.

Describe the steps and where each starts and ends: picking up the unit or carton, applying the product or barcode label by hand or with a label gun, and setting the item aside. Say whether you also want the pack-out of the second row, with inserts, sealing and a dispatch label. Say whether an episode covers one unit, a batch or one step, what counts as the object and what counts as a completed step, and name 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 sixth table below shows what each spec element decides.