Stereo Order Packing and Taping Data

It is first-person video of a person packing and taping customer orders in a warehouse, recorded from their own point of view with two calibrated cameras and with hand pose and sensor streams alongside. The tasks are the four rows the site’s catalog lists in Warehouse & Distribution Center. 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.

Four, all in Warehouse & Distribution Center under Logistics & Warehousing, and all Ready to deploy. "Packing & Labeling" is described as packing orders into boxes with filler, taping them shut and applying the shipping label. "Pick and pack customer orders using a handheld scanner and packing tape dispenser" is described as walking the pick path with a scanner, picking items to the tote and packing and taping the order. "Pick, scan, pack, and label customer orders using a handheld barcode scanner and a tape gun." is described as a fulfillment warehouse with racked storage aisles, picking carts and packing benches. All three are rated Easy.

"Load and secure outbound freight using a hand truck and stretch wrap" is the fourth, rated Medium and described as moving pallets and boxes to the dock with a hand truck and stacking and stretch-wrapping the load. All four list a head-mounted phone or a multiview rig as the capture setup. This page names only the tools and steps that appear in those rows: a handheld scanner, a handheld barcode scanner, a packing tape dispenser, a tape gun, a hand truck and stretch wrap, and picking, scanning, packing, taping, labeling, stacking and wrapping. The first table below reproduces the rows as the catalog states them.

The egocentric packing and kitting page, the box and parcel handling page and the barcode scanning and labeling page each cover some of these rows as first-person capture. None has a stereo or MCAP treatment of the warehouse order packing rows. The stereo layout marking and taping page is a stereo and MCAP page, but its taping is measuring, marking and drywall taping, not taping a shipping box.

This page is the stereo and MCAP treatment of just the four warehouse rows named above. It does not repeat the manufacturing, palletizing or kitting rows. The comparison table below sets the pages side by side.

Packing work is about where the hands, the box and the tape are relative to one another: whether the flap is down, whether the tape has crossed the seam, whether the label is on the face of the box. A stereo pair recovers depth from the calibrated frame pair rather than from a standalone depth sensor, so the box, the tool and the hands share a frame. The site gives no depth accuracy figure and no label for a sealed seam or a placed label, so whether those are resolvable in depth is Not stated.

The site does not state how a stereo pair behaves on shiny tape, cardboard edges or a scanner beam, so this page promises nothing there. Which warehouses a given program uses is not stated either, and is agreed in the spec. Capture at your own facility is listed as not offered.

The site describes two stereo setups and does not say which one a packing 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 packing 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 a spec can use for a bench the head camera sees only in part.

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 packing 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.

Small tools are the first risk. A scanner, a tape dispenser and a tape gun are held in one hand and are partly hidden by the fingers and the box. The site ships per-frame instance masks for that reason, and the site lists no seam, tape-quality or label-placement label, so what counts as a taped box or a placed label is written into the spec up front.

Hands are the second. Two hands fold flaps, hold the box and pull tape, and fingers are hidden behind the box. The visibility flag on each joint is the answer the site gives, and contact events mark when a hand meets an item. A spec can also ask for wrist views, so a grip the head camera loses is still recorded.

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. Force and tactile readings are not among the listed streams.

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. Text on shipping labels is not listed as a blur category on the site, so this page does not claim it is blurred. Who may be in frame, and how customer items are handled, is agreed in the spec.

The site states no throughput, orders-per-hour, accuracy, load-weight, safety or certification claim for any of these rows, so this page describes none.

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 warehouse packing 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. All four rows are 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 stations and their order, the items and containers and their start state, what counts as a finished step, 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.