Stereo Warehouse Receiving and Truck Loading Data

It is first-person video of a person receiving and loading freight: breaking down inbound pallets with a pallet jack, unloading inbound goods from the truck and checking quantities against the paperwork, moving pallets and boxes to the dock with a hand truck, and staging pallets and parcels at the dock to load them into the trailer in sequence. It is recorded from their own point of view with two calibrated cameras, with hand pose and sensor streams alongside. The tasks are the ones the site’s catalog lists in four rows. 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. It describes task video only and makes no load-weight, safety, certification or throughput claim. Firsthand is not affiliated with Foxglove or the MCAP maintainers.

Four, all in the Warehouse & Distribution Center environment of the Logistics & Warehousing sector, all rated Medium, and all listed as Ready to deploy. "Receive and unload inbound pallets using a manual pallet jack" reads "Break down inbound pallets with a pallet jack, check contents against the manifest and shelve." "Receiving & Unloading" reads "Unload inbound goods from the truck, check quantities against the paperwork and move them to storage." "Load and secure outbound freight using a hand truck and stretch wrap" reads "Move pallets and boxes to the dock with a hand truck, stack and stretch-wrap the load." "Loading Outbound Trucks" reads "Stage pallets and parcels at the dock and load them into the trailer in sequence."

All four list a head-mounted phone or a multiview rig as the capture setup. The catalog lists the environment examples as an e-commerce fulfillment hub, a distribution center, a cold storage facility and a freight warehouse, and does not say which one a row was captured in. The site says nothing further about what Ready to deploy means in volume, hours or delivered stereo footage, so this page claims none. It names only the tools and items that appear in the rows: a manual pallet jack, a hand truck, stretch wrap, pallets, boxes and parcels, the manifest and paperwork, the dock, the truck and the trailer. The first table below reproduces the four rows as the catalog states them.

The egocentric truck loading and unloading page covers these four rows as egocentric capture, with delivery in RLDS, LeRobot or WebDataset, and makes no stereo or MCAP treatment of them. The stereo palletizing and stretch wrapping page gives stereo and MCAP treatment to two finished-goods rows in a plastic and light-assembly environment, not to these. The stereo order packing and taping page gives stereo and MCAP treatment to four warehouse rows, one of which is the hand truck and stretch wrap row that also appears here.

This page is the stereo and MCAP treatment of the two receiving rows and the two loading rows together, with their own stream map and failure modes. The hand truck and stretch wrap row overlaps with the order packing page, and this page treats it only as the step that moves a load to the dock. The comparison table below sets the pages side by side.

Receiving and loading is about where a load is, where it is going and what is in the way: a pallet broken down at a rack, goods carried off a truck, a load staged at the dock and then placed into a bounded trailer. A stereo pair recovers depth from the calibrated frame pair rather than from a standalone depth sensor, so the load, the vehicle edge and the hands share a frame. The site gives no depth accuracy figure for these rows and no pallet-count, load-stability or task-completion label, so what a buyer does with that depth is their pipeline’s question.

The site states that depth degrades on wet and reflective surfaces and ships per-frame confidence maps so a buyer can mask rather than guess. How a stereo pair sees stretch film, a trailer floor or a dim trailer interior 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 states 3D hand pose of 21 joints per hand with a per-joint visibility flag, and contact and grasp events that mark when fingers meet a tool or an item. In these rows that is the hands on a pallet jack or hand truck as it is moved, the hands that take a box or parcel off a pallet or a truck, and the hands that place freight into a trailer or stretch-wrap a load.

The site does not say whether the pallet jack, the hand truck, a pallet, a box or the stretch wrap counts as the object for contact events, so settle it in the spec. Wrist cameras give a closer view of the hands, and a multiview rig adds synchronized third-person angles when the spec asks for them.

The site describes two stereo setups and does not say which one a receiving or truck loading 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 receiving or truck loading 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. Dock height, trailer dimensions, lighting, load weight and camera clearance are Not stated, so any requirement is settled in the spec.

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 these rows the site states hand pose, a stereo-derived depth stream with confidence maps, IMU, contact events, action segments and per-frame instance masks elsewhere, and states instance segmentation for warehouse collections. 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.

Load and box occlusion is the first risk. A carton, a pallet or a stacked load can hide the fingers that hold it. The visibility flag on each joint is the answer the site gives, contact events mark when a hand takes hold of an item, and a spec can ask for wrist views or a second angle so a grip the head camera loses is still recorded. The site notes that reach and grasp frames are where blur and occlusion show up. An episode is rejected when the manipulated object is out of frame for more than 15 percent of it.

Dim light and motion are the second. The site ships transitions and hard cases uncut, including walking between rooms, exposure hunting in dim light and occluded grasps, rather than curating footage down to the clean segments. It states no handling specific to dock or trailer lighting and no figure for motion while walking with a pallet jack or hand truck, so this page promises none, and how a stereo pair behaves in a dim trailer or while the wearer walks with a load is Not stated. The head camera is global-shutter, which avoids rolling-shutter skew, and depth is flagged rather than interpolated where it is unreliable: an episode is rejected when more than 35 percent of depth pixels in the manipulation region are invalid.

Sequence is the third. The rows chain breaking down a pallet, checking contents against the manifest or paperwork, moving freight to the dock and loading the trailer in sequence, so a spec naming each step and where it starts and ends gives a sequence that can be sliced by step, while a spec saying "load the truck" gives one long action segment. The rows do not say what one episode covers, so the spec decides. Load weights, forklift or powered-vehicle use, operator certification, carrier, facility or customer names, scanner or warehouse-system brands and throughput are Not stated and are not claimed on this page; the rows name a manual pallet jack and a hand truck.

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

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. The anonymization record ships with the data, and an undocumented bystander is a stated reject criterion.

Paperwork text, manifest text and labels on parcels are not listed as blur categories on the site, so this page does not claim they are blurred. The site does not state a rule specific to a dock, a trailer or a carrier, or how handling differs between a fulfillment hub, a cold storage facility and a freight warehouse, so this page makes no such claim. Settle it in the spec.

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 lists no off-the-shelf receiving or truck loading dataset, so stereo receiving and truck loading in MCAP is custom collection: custom collection at scale through a network of thousands of capture providers, for a consistent, recurring data flow to labs. The off-the-shelf stereo and hand-tracking video page shows what the 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. All four rows are Ready to deploy, and the site does not say which speed applies to a stereo receiving or truck loading order, 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: breaking down inbound pallets with a pallet jack, unloading goods from the truck against the paperwork, moving freight to the dock with a hand truck and stretch-wrapping it, and staging and loading the trailer in sequence. Name the tools you expect to see, whether an episode covers one pallet, one truck or a whole shift, 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.