Egocentric Meal Plating and Serving Video Data

It is first-person video of a person plating, portioning or serving food and drinks, 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 a hand does at the end of the chain: placing a portion, finishing a plate, setting a tray down in front of someone. 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 eleven rows that are explicitly about plating, portioning or serving. Three are plating rows: "Banquet plating", "Plate + garnish" and "Cooking / Line Cooking", whose description includes plating and service. Four are portioning rows: "Kitchen Meal Portioning & Packaging", "Portion and package meals using a kitchen scale and food-grade containers", "Chop and portion produce using a chef’s knife and cutting board" and "Food Prep".

Four are serving rows: "Pour + serve beverage", "Tray assembly + delivery", "Counter service and packaging" and "Order assembly". Statuses vary: Ready to deploy, Active collection or Available on request, and the catalog does not define any of them further, so ask which applies to your row.

The second table lists neighbouring rows, such as setting a table, that are not plating or serving rows themselves.

The catalog ties these rows to four environments. Catering & Event Kitchen lists examples such as a hotel banquet kitchen, airline catering and a hospital canteen. Restaurant & Commercial Kitchen lists a sit-down restaurant kitchen, a café and an artisan bakery. Fast Food & Quick Service Kitchen is the third. Hospitality Service Set is described as a table, a counter or bar, and a housekeeping or room area.

The rig differs by row. Kitchen rows list a head-mounted phone or multiview rig, and the Working Kitchen Set and Hospitality Service Set rows list a multiview rig plus handheld grippers. The site does not state capture at a customer’s own facility.

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 plate, a utensil or a tray 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 plating, 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 "plate the meal" gives you one long segment. A spec that names portion, place, garnish and load 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 label for dish type, portion weight, presentation quality or task success, 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 guests or customers in a dining room or a service area 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 the plating and serving rows and promises nothing faster, so ask when you request the quote.

Collection is on demand, so a focused brief, such as one banquet plate from first portion to loaded tray, 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 plating 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.