Egocentric Hanging Basket Planting Data

Egocentric hanging basket planting data is recorded evidence of one person filling a basket, planting it and hanging it, collected by a paid, consented contributor who performs the task written in a skill spec. Each attempt is delivered as an episode with synchronized streams and labeled action segments. It is human capture. It is not robot or teleoperation data, and it is not a fixed corpus you download.

The site states the task in one row of its commercial task catalog. In the Greenhouse, Nursery & Garden Centre environment, the row "Fill hanging basket" reads: "Fill and hang a planted basket." It is an Easy row and its status is Available on request. The environment is described with the examples "Greenhouse / grow-bench set: pots, trays, plants, shears, stakes, crates". This page is built on that row and on the neighbouring greenhouse rows quoted below, and on nothing else the site says about baskets.

The word egocentric in the title needs a plain reading. Firsthand’s general offer is first-person capture, and the catalog lists a head-mounted phone for many rows. For this row the catalog lists something different: a multiview rig with handheld grippers. This page therefore describes the capture setup as the row states it, and treats first-person or stereo capture as a choice made in the skill spec, not as something the site promises here.

People reach this topic through hanging basket planting robot training data, an egocentric garden centre video dataset, a fill-and-hang planted basket dataset or custom nursery data collection. They describe one request from different angles. The work is the same: write the task down, collect it on demand and receive validated episodes.

One row covers it. "Fill hanging basket" sits under the Agriculture & Grounds sector in the Greenhouse, Nursery & Garden Centre environment. Its description is "Fill and hang a planted basket." Its skill rating is Easy, its capture setup is "Multiview rig + handheld grippers" and its status is "Available on request". The table below reproduces the row, and the rows beside it that this page refers to, as the catalog states them.

On the site, "Available on request" means the work is scoped and recruited to spec when a buyer asks for it. It does not mean hours are sitting in a library. This page claims no delivered hours for the row, and no off-the-shelf hanging basket dataset exists; the work is custom collection. The status is shown here exactly as the catalog lists it, and it is the same for every row in this environment.

The site names no basket type, no plant species, no growing medium, no bracket or hook and no hanging height. The words that appear are fill, hang, planted and basket, and this page uses only those. What a finished basket looks like, and where it is hung, is not stated. Those choices belong in the spec, and a Spec Pilot is the place to settle them.

The catalog states one capture setup for this row: "Multiview rig + handheld grippers". The site explains it as a staged working set recorded by a multiview rig while the operator performs the task with handheld grippers, so demonstrations map onto a robot end effector. That is the description this page uses, and it is the only capture description this page makes for the row.

The site does not state a head-mounted phone for this row, and it states no stereo pair for it. A calibrated stereo pair is offered generally, and a head-mounted stereo rig is the instrumented tier of the general capture stack. If a program wants either for hanging baskets, it is agreed in the skill spec. The egocentric label in the title names the general first-person offer and the query people use; it is not a claim about this row’s rig.

The multiview setup is a sensible fit for a task with two phases, because synchronized third-person angles can show both the work at the bench and the hanging step from more than one side. That is an illustration of why a spec might ask for it, not a stated camera layout. A rig that records handheld grippers in the operator’s hands also lines up with the site’s stated reason for the setup: the demonstration maps onto a robot end effector. The site gives no camera count, resolution or frame rate specific to this row.

Each attempt is delivered as one episode, and a two-part task needs a decision up front about what one attempt is. It could be filling and planting a basket, the hang step alone, one finished basket from empty to hung, or a run of several baskets. The site does not set an episode length, a number of baskets per episode or a number of episodes, so the skill spec does.

The cut matters because of one machine-checked rule. An episode is rejected if the manipulated object is out of frame for more than 15 percent of it. In this task the manipulated object changes: it is the basket and its contents at the bench, and the basket again as it is lifted and hung. The spec should say what counts as the manipulated object at each step so the rule is applied the same way across contributors.

A second rule applies to depth: an episode is also rejected if more than 35 percent of depth pixels are invalid in the manipulation region. The site says depth degrades on wet and reflective surfaces and ships per-frame confidence maps. It does not say how depth behaves on baskets or on planted foliage, so this page makes no accuracy claim for them.

Inside each episode, action segments divide the recording into start- and end-timestamped spans, each carrying start_ns, end_ns, verb and noun. For this task a segment can be one step as written in the skill spec, so a basket becomes a run of labeled steps, such as fill, plant and hang, with a noun for the item, rather than one long clip. Other standard fields include hand_joints and hand_visible for 3D hand pose, contact_events, objects and instance_masks, stored at the depth resolution of 848×480 so they line up with the depth stream.

Hand pose is delivered with a per-joint visibility flag for occluded fingers. That flag is the signal that matters when the hands are inside the basket among the plants. The site describes contact events as the moment the hand meets an object. It does not say which objects count in a hanging basket episode, so the spec settles what a contact event means for your task.

The site lists no label for the outcome of the basket. There is no stated fill-level, planting-quality or task-completion score, and no contact force reading. The catalog verbs describe what the contributor does, not a delivered measurement. The site states 6-DoF IMU data at 200 Hz from head- and wrist-mounted sensors, and nothing more about motion.

Delivery is in the format your stack already reads: RLDS, LeRobot, WebDataset, HDF5, zarr or Rerun .rrd, or raw streams with metadata. Readable converter source ships alongside the data so the schema can be retargeted to your own loader. The official documentation for three of these formats is linked in the sources below. Collections are billed per validated hour, and the license is perpetual, irrevocable and worldwide, buyer-owned and non-exclusive by default, with exclusivity available as a separate term.

Hand occlusion is the main one. While a basket is being filled and planted, the fingers, the plants and the basket occupy the same small space, and the hands go inside the work. The site’s answer is hand pose with a per-joint visibility flag, so a model can tell a hidden finger from a missing one, and multiview angles that see the hands from more than one side. The spec decides which angles matter for your task.

The second is the object leaving the frame. A basket is lifted, carried and hung, and the manipulated object can drop out of view or move to the edge of it. The 15 percent out-of-frame rule exists for that, and the episode is rejected rather than quietly accepted. Rejected items are recaptured at our cost, and only footage that clears the signed accept criteria is billed as a validated hour.

The third is ambiguity about what one object is. A planted basket is the basket plus what is in it, and a per-frame instance mask is only useful if the spec says what is one object. The site delivers per-frame instance masks where the spec calls for them, and it does not say how well they separate a basket from its plants, so this page claims nothing about it.

A fill-and-hang task is a useful shape of work because it chains two different kinds of manipulation in one short sequence: loading and arranging material in a container at a bench, and then lifting the finished container and placing it somewhere else. The site rates the row Easy, the same rating it gives to potting, produce packing and grading in the same environment. This page does not claim that any current robot performs the task.

First-person and multiview human video of the task sits at the base of the data pyramid the glossary explains, where volume is high and the gap to a robot body is widest. Human capture does not replace robot data, and this page does not claim that it does. The staged working set with handheld grippers is the site’s own way of narrowing that gap for rows like this one, because the demonstration is made with a tool that maps onto an end effector.

Every contributor signs a written release before capture, and each delivered episode links to that record through consent artefact IDs in the batch data card. At ingest, automated detection finds faces, plates and screens and blurs them irreversibly, and speech is scrubbed of names, addresses and card numbers while ambient audio is kept. A human reviewer confirms that no un-consented person is identifiable in any frame, and footage that cannot be de-identified is discarded. An undocumented bystander is also one of the machine-checked reject criteria. The anonymization record is delivered with the data.

The site names no nursery, garden centre, grower, region or city for this row, and it lists capture at your own facility as not offered. This page therefore makes no claim that episodes are recorded at a particular site, and none that they are recorded at yours. Capture is run to your skill spec using the settings and contributors Firsthand arranges. The site states nothing specific about customers or staff who might be in a garden centre background, so this page makes no claim beyond the general process.

On handling safety, the site states no hanging, lifting or tool-safety protocol, no contributor safety protocol and no agricultural certification for this row, and this page does not describe one. If your program needs terms about the conditions under which the work is done, raise them when you scope it. None of this is legal advice, and the executed agreement controls.

The table below sets this page against the neighbouring greenhouse and nursery pages on this site. Each row states the page’s main subject and the catalog rows it draws on, with the status as the catalog lists it. No delivered hours are claimed for any of them.

The short version: the potting page covers filling a pot, planting and watering, and replanting seedlings on the bench; the seed tray page covers sowing; the pruning and trellis page covers cutting and supporting stems; the staking and deadheading page covers clipping and trimming; the herb page covers bunching; the plant care page covers the wider run of gardening tasks. This page treats the basket, and the step of hanging it, as the subject. The plant care page lists the hanging basket row among many, and none of the other pages names it as a subject.

From signed spec to first validated batch, the site states a median of 48 hours where coverage is deep and three to four weeks where it is thin. It does not say whether the Greenhouse, Nursery & Garden Centre environment counts as deep or thin, so ask which timeline applies when you request the quote. Speed comes from a warm pipeline, not from cutting consent, review or anonymization.

The site also states program milestones: a pilot reaches its first delivery in two to three weeks, and a standing program reaches full rate in four to six weeks. Those assume capture coverage is already in place. After the first batch, on-demand top-ups run against the same accept criteria, so you can add settings or variations without rewriting the spec. The site does not state a turnaround for those later batches, so plan them in your quote.

The site does not publish a price list, a minimum order or a batch size for this row, so those are set in your quote. Collection is fast and on demand in the sense that you do not need a standing program: a focused brief is a normal starting point.

No. The site lists no off-the-shelf dataset for this task, and the catalog row is Available on request, so this is custom collection. The off-the-shelf catalog on this site covers other recordings; none of its entries is described as showing a planted basket being filled or hung, and this page does not borrow their figures.

The practical consequence is that nothing about this row is pre-recorded. Your spec defines the episode, the contributors are recruited to it, and the first validated batch is the first time the footage exists. A request for custom nursery data collection therefore starts from a written brief rather than from a catalog sample.

Where this site does not state something, this page says "Not stated" rather than filling the gap. There is no basket type, no plant species, no growing medium, no bracket or hook type, no hanging height, no task duration, no site count, no region or city, no episode count, no planting-quality or completion label and no tool-safety guidance. Nothing here reports a robot result, a benchmark or a model improvement.

Counts of contributors, hours and tasks are set in your skill spec. A task outside the rows quoted on this page, such as a watering or labelling step the catalog does not name for this row, is settled in a Spec Pilot rather than assumed.

Describe what one basket is, what filled and planted mean, where and how it is hung, and the variation or failure cases your pipeline is missing. That becomes a written skill spec, quoted for reach, timeline and price before any capture begins, and most programs run a Spec Pilot first, a small, fast first batch that proves the spec and the accept criteria on real footage before volume scales. The scoping checklist below maps the parts of a skill spec onto a basket request.

Three choices matter most. Name the step and the item rather than a broad activity, because that is what lets each fill and each hang become one action segment. Decide whether you want the capture setup the row states, a multiview rig with handheld grippers, or a first-person or stereo rig agreed in the spec. And name where the episode starts and stops, since the site does not set an episode length.