Egocentric Food Portioning and Weighing Data

It is first-person video of a person portioning food in a commercial kitchen, recorded from a head-mounted camera, with two wrist cameras for a closer view of the hands. The contributor is a paid, consented person following a written skill spec, not an actor and not a robot.

The point of the data is what the hands do between the scale and the stack: weighing, filling, sealing, labeling. It is labeled so each step can be sliced out. Where the site states nothing, a table says "Not stated" and the answer lives in the spec or the quote.

The task catalog names two rows that are about weighing and portioning food into containers, both in the Restaurant & Commercial Kitchen environment. "Kitchen Meal Portioning & Packaging" is described as "Weigh cooked food into portions, fill containers, seal, label and stack them for service." It is rated Easy and listed as Ready to deploy.

"Portion and package meals using a kitchen scale and food-grade containers" is described as "Weigh each portion on the scale, fill containers to spec and seal and label them." It is rated Easy and listed as Active collection. Both list a head-mounted phone or multiview rig. The site says nothing further about what these statuses mean in volume or delivered hours, so this page claims no completed collection, and what applies to your order is confirmed when you request the quote.

This page names only the tools and steps that appear in the two rows: a scale, portions, containers, filling to spec, sealing, labeling and stacking for service. The first table below reproduces the rows as the catalog states them.

The catalog ties both rows to Restaurant & Commercial Kitchen, with examples that include a sit-down restaurant kitchen, a café, a coffee shop, an artisan bakery and a patisserie. Both rows list a head-mounted phone or multiview rig as the capture setup.

The site does not state capture at a customer’s own facility or who hosts it, so the spec settles location and access.

An episode is one contributor performing one task from the skill spec, recorded with ten hardware-synchronized streams that line up within 2 ms. The site documents a canonical episode schema, and every delivery format is a view of it.

Hand pose is stored as 21 joints per hand in metres in the head frame, with a visibility flag for each joint. Contact events record when a hand meets an object. The site does not say whether a scale or a container counts as the object, so settle it in the spec.

Action segments carry a start, an end, a verb and a noun from a taxonomy the site states as 97 verbs and 512 nouns, human-reviewed. For portioning, a segment can be one step as written in the spec. Every episode links to its contributor’s signed release by a consent artefact ID, and each batch ships with a data card.

The unit of labeling is the action segment. A spec that says "portion the meal" gives you one long segment. A spec that names weigh, fill, seal, label and stack gives you a sequence you can slice by step.

Every episode is machine-checked, then reviewed by a human against its skill spec, and rejected episodes are recaptured at our cost. The site states no scale reading, portion weight, fill level or task-success label, and no force or tactile reading, so ask for any such label at the start.

Only what the site already states applies. Every contributor signs a written release, and each episode links to it. Faces and screens are detected and blurred irreversibly, a human reviewer confirms that no un-consented person is identifiable, and footage with bystanders who cannot be de-identified is discarded rather than shipped.

The site does not state how a kitchen’s own staff, menus or container labels are handled beyond that general rule, so settle it in the spec before capture. This is not legal advice, and the executed agreement controls.

Data is delivered in RLDS, LeRobot, WebDataset, HDF5, zarr or Rerun .rrd, or as raw streams with metadata, with the episode schema as the canonical layout. QA runs once, against the canonical episode, before any format is cut. The formats table sets the site’s delivery next to each maintainer’s own documentation, linked under Sources.

The license is perpetual, irrevocable and worldwide, buyer-owned and non-exclusive by default, with exclusivity available as a separate term and the executed order form governing.

The site states one published timeline: from a signed spec to a first validated batch, a median of 48 hours where coverage is already deep, and typically three to four weeks where it is thin because operators have to be staffed. The site does not say which applies to these two rows and promises nothing faster, so ask when you request the quote.

Collection is on demand, so a focused brief, such as one container from first weigh to stacked for service, is a normal starting point.

Start with the free sample pack to check the loader and label quality, then move to a Spec Pilot: a small, fast first batch against the written spec that proves the fill rate and reject rate on your conditions before you scale.

A good portioning brief names the setting, the sequence of steps, how each step starts and ends, what counts as a reject and the privacy rule for the room. The site’s skill-spec guide walks through that structure. Then request a custom dataset.