Now recruiting capture teams worldwide. Get paid to record first-person video of real work.

Apply to capture

Task row

Egocentric Floor Sweeping and Debris Collection Data

A floor sweep is a long, repeated reach in which the pile changes with every stroke, and the debris has to end up somewhere. This page covers egocentric floor sweeping data for the one catalog row that names this work: what the row states, how a first-person sweep is set up and checked on a staged hospitality set, how it differs from the floor cleaning, lobby, construction cleanup and kennel pages, and what the site does not state. People search for first-person broom and dustpan video; the row names neither tool, and this page says so. We run custom cleaning data collection fast and on demand against a spec you write, as a handheld gripper sweeping dataset.
Catalog row
"Sweep a floor area" (Easy); Available on request
Environment
Hospitality Service Set (table, bar, room)
Capture setup
Multiview rig + handheld grippers
License
Perpetual, buyer-owned

Requirements

What does floor sweeping capture need?

01

Both hands, the tool and the floor in view

A sweep is a two-handed task on a moving pile, so the spec has to keep both hands, the working end of the tool and the debris in frame from the first stroke to the last. The site states that a multiview rig adds synchronized angles when the spec asks for them.

02

Hand pose with a visibility flag

The site states that 3D hand pose carries 21 joints per hand and a per-joint visibility flag, so a finger hidden behind a handle or a pile is flagged as hidden rather than guessed.

03

A stated end point for the debris

The row says to sweep and collect, and no more. Where collected debris ends up, and whether the episode ends there, is Not stated and is set in the spec before capture.

04

Reject rules written before capture

An episode is rejected when the manipulated object is out of frame for more than 15 percent of it, when more than 35 percent of depth pixels in the manipulation region are invalid, or for an undocumented bystander. The thresholds are agreed before capture.

Definition

What is egocentric floor sweeping and debris collection data?

It is first-person video of a person sweeping a floor area and collecting the debris, recorded with synchronized sensor streams alongside. The catalog describes the one row that names this work as "Sweep and collect debris." The row names no tool, no kind of debris and no floor. Nothing else about the sweep is stated.

The data is human capture by paid, consented contributors. It is not robot or teleoperation data, and it is not a fixed corpus you download. Using it for a specific robot still needs your own retargeting step, and this page makes no claim that Firsthand supplies retargeted actions. The site states one task instruction per episode as its language data. Firsthand is the collector; this page names no broom maker, floor-care brand, venue or client.

Catalog row

Which catalog row does this page rely on, and what is its status?

One. In the Hospitality Service Set (table, bar, room) environment of the Hospitality & Events sector the catalog lists "Sweep a floor area" with the description "Sweep and collect debris." It is rated Easy, its capture setup is "Multiview rig + handheld grippers", and its status is Available on request. The environment examples read "A table, a counter/bar, and a housekeeping/room area", which are kinds of area, not named venues.

Available on request means, in the site’s words, that the work is scoped and recruited to spec when a buyer asks for it. It is not a statement that footage of this task has been delivered. The site states no delivered hours, clips or counts for this row, so this page claims none. The first table below reproduces the row as the catalog states it, and the second lists all twelve rows of the environment, each with the same capture setup and the same status.

Difference

How is this different from the floor cleaning, lobby, construction cleanup and kennel pages?

This page is the dedicated task page for the sweep row. The egocentric floor cleaning and mopping page covers a family of mopping, sweeping and vacuuming rows and lists the sweep row in a table. The egocentric hotel lobby and common area cleaning page covers one Easy row, Lobby & Common-Area Cleaning, listed as Ready to deploy. The egocentric construction site cleanup page covers two Easy rows in the Active Construction Site environment, listed as Active collection, and the site names brooms and wheelbarrows in one of them. None of them is the hospitality set sweep row.

The stereo kennel and animal pen cleaning page covers two rows about kennels and pens, delivered in stereo as MCAP. It shares the word cleaning with this page and nothing else. The third table below sets the pages side by side, with each status and setup as the site lists it.

Capture setup

How is the work captured when the setup is a multiview rig and handheld grippers?

The catalog defines the setup 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 different from the head-mounted phone setup listed for the sweeping rows in the Event Venue and Active Construction Site environments. This row does not list a head-mounted phone setup, and this page does not describe it as head-mounted phone capture.

The word egocentric in the title follows the site’s naming for its first-person collection pages. For this row the capture is a staged set, not a crew on a working floor, and the exact camera layout, number of angles, resolution and frame rate are Not stated and are agreed in the spec. On the rig tier the site states that streams are hardware-triggered onto one clock and that the rig is calibrated before capture starts and after it ends, with an episode accepted only if RMS reprojection stays under 0.28 px.

The site states no stereo pair for this row. Stereo is available only through the site’s general stereo offer, and a stereo pair for sweeping work would be agreed in the skill spec, with MCAP as one delivery container among others.

Why it matters

Why is a swept floor and collected debris worth capturing on its own?

This is the page’s own reasoning, not a figure from the site. A sweep leaves a trace: the pile moves on every stroke, and the next stroke depends on where the last one left it. A spec for wiping a counter and a spec for sweeping a floor ask for different reaches and different views, and a clip of one does not stand in for the other. The catalog lists them as separate rows, "Wipe + reset counter" and "Sweep a floor area", for that reason.

The row is rated Easy, the same as the tray, restock, bus and check-in rows on the set, and below the Medium folding, bedding and beverage rows. The site states no success rate, cycle time or error rate for any of them. A custom collection lets you name the sweep, the setting and the accept criteria you need, and have it captured, labeled and checked to terms you agreed, instead of hoping a public release contains it. This page does not claim that any public corpus lacks floor sweeping.

Steps

Which steps of sweeping and collecting can a spec label?

The catalog gives two verbs in its own wording: sweep, then collect debris. A spec that says "clean the floor" gives one long action segment. A spec that names the sweep and the collection as separate stages gives a sequence you can slice by step, with frame-accurate action segments where the spec asks for them. The site does not set an episode length or say how large a floor area is.

Whether an episode ends when the debris is collected, when the tool is set down or when a second area begins is Not stated and is set in the spec. Contact and grasp events can mark when a hand meets the handle or the debris where the spec asks for them. This page gives no procedure, and the stages above are the catalog’s wording, not instructions.

Streams

What does each floor sweeping episode contain?

Episodes follow the Firsthand episode schema: ten streams synced under 2 ms, with RGB, depth, 3D hand pose with per-joint visibility, contact and grasp events, and frame-accurate action segments. Which of those streams a multiview rig with handheld grippers produces for this row, and from which angles, is agreed in the spec and confirmed on the Spec Pilot.

Object labels use the terms your spec sets, and one task instruction is attached per episode. Force or tactile data and success or quality labels are Not stated for this row, and this page does not claim a coverage map or a floor-state label. The fourth table below sets each stream beside what the site states.

Failure modes

What goes wrong when you record floor sweeping, and what does QA reject?

Hand and tool occlusion is the first risk. The site states that fingers disappear behind objects, which is why each hand joint carries a visibility flag, and that reach and grasp frames are where blur and occlusion show up. A sweep puts the hands low and close to the handle, so how often a finger is hidden on this row is Not stated.

An episode is rejected when the manipulated object is out of frame for more than 15 percent of it, when more than 35 percent of depth pixels in the manipulation region are invalid, for a sync breach beyond the 2.0 ms ceiling for more than three consecutive frames, for an undocumented bystander, or for a mismatch against the named skill spec. A reject log ships with every batch. The fifth table below lists the failure modes beside what the site states.

Safety and privacy

What does the site say about safety, people and privacy?

Protective equipment, lifting and slip safety rules are Not stated, and this page makes no safety or compliance claim. Tool types, floor surfaces, debris types, area sizes, task times and stroke counts are Not stated too, and so are tool and cleaning-product brands.

For every delivered episode the site states that faces, plates and screens are blurred irreversibly, that a reviewer confirms the result before anything ships, and that footage that cannot be de-identified is discarded. The anonymization record ships with the data, and every episode links to a signed contributor release. This is not legal advice, and the executed agreement controls.

Collection

How fast can a floor sweeping dataset be collected, and at what scale?

The row is Available on request, so contributors are recruited to your spec when you ask, and the timeline is quoted against the spec before capture begins. 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. The site does not say which applies to this row. Collections are billed per validated hour, and rejected episodes and recaptures are never billed.

For volume, the site’s stated model is custom collection at scale through a network of thousands of capture providers, for a consistent, recurring data flow to labs. This page states no provider count, hours, throughput or cadence beyond that wording.

Ordering

How do you order a floor sweeping dataset?

Describe the two stages, where each starts and ends, whether an episode covers one stage or the whole job, what counts as the object, and the setting. Then name the streams you want, whether you want a stereo pair through the general stereo offer, and the delivery format: RLDS, LeRobot, WebDataset, HDF5, zarr or Rerun .rrd.

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 sixth table below shows what each spec element decides.

At a glance

What you get.

Catalog row
"Sweep a floor area" (Hospitality Service Set (table, bar, room), Hospitality & Events); Easy; Available on request
Catalog description
"Sweep and collect debris."
Environment examples
"A table, a counter/bar, and a housekeeping/room area"
Catalog capture setup
Multiview rig + handheld grippers: a staged working set recorded by a multiview rig while the operator performs the task with handheld grippers
Stereo
Not stated for this row; stereo is available only through the site general stereo offer, agreed in the skill spec
Hand pose
21 joints per hand with a per-joint visibility flag
Sync
Hardware-triggered onto one clock; 2.0 ms cross-stream ceiling
Language data
One task instruction per episode
Delivery formats
RLDS, LeRobot, WebDataset, plus HDF5, zarr and Rerun .rrd
Broom, dustpan or other tool, debris type, floor surface, area size, success rates
Not stated; agreed in the skill spec
License
Perpetual, irrevocable, buyer-owned, non-exclusive by default

Every collection runs through the same seven-stage end-to-end custom collection pipeline. End-to-end custom data collection is a managed service that takes an AI data need from problem to owned dataset in a single accountable pipeline.

Catalog row

Which catalog row covers floor sweeping and debris collection, and what is its status?

The subject row from the site task catalog, reproduced with the catalog description, environment, skill, capture setup and status as listed.
Task (as listed)Description (as listed)EnvironmentSkillCapture setupStatus
Sweep a floor areaSweep and collect debris.Hospitality Service Set (table, bar, room)EasyMultiview rig + handheld grippersAvailable on request

Environment rows

Which twelve rows does the Hospitality Service Set list?

All rows of the environment as the catalog lists them. Every row has the capture setup "Multiview rig + handheld grippers" and the status Available on request.
Task (as listed)Description (as listed)Skill
Check-in handlingHandle documents and room keys.Easy
Clear + bus tableStack dishes, bus, and wipe.Easy
Fold napkinsFold napkins to a set style.Medium
Fold towels + linensFold towels and linens; stack by type.Medium
Make up room beddingChange case and spread cover.Medium
Pour + serve beveragePour a drink and serve to a place.Medium
Prepare + garnish drinkBuild and garnish a bar drink.Medium
Restock amenitiesRestock a minibar/amenity tray.Easy
Set table serviceLay a full place setting.Medium
Sweep a floor areaSweep and collect debris.Easy
Tray assembly + deliveryArrange, carry, and set a tray.Easy
Wipe + reset counterClear, wipe, and reset a counter.Easy

Compared pages

How does this page differ from the floor cleaning, lobby, construction cleanup and kennel pages?

Each page, what it covers and how it treats floor sweeping. Statuses and setups are as the site lists them.
PageWhat it coversSetup and status as listedTreatment of floor sweeping
This page: egocentric floor sweeping and debris collection dataThe one "Sweep a floor area" row (Easy)Multiview rig + handheld grippers; Available on requestTask page: stages, streams, failure modes and spec
Egocentric floor cleaning and mopping dataMopping, sweeping and vacuuming rowsMixed across rowsLists the sweep row in a table; family page across floor tasks
Egocentric hotel lobby and common area cleaning dataThe Lobby & Common-Area Cleaning row (Easy)Ready to deployNot covered; lobby and common-area work
Egocentric construction site cleanup dataTwo Easy rows in Active Construction SitePhone (head-mounted) / multiview rig; Active collectionNot covered; site debris removal with brooms and wheelbarrows
Stereo kennel and animal pen cleaning dataTwo rows: Kennel cleaning and Animal Pen Cleaning & Waste RemovalKennel cleaning Available on request; pen cleaning Ready to deploy; stereo as MCAPNot covered; kennel and pen work in stereo

Stream map

Streams for floor sweeping and what the site states about them

Left to right: the stream or label, its status on the site, and what it carries in a sweeping episode. "Not stated" means the site does not say.
Stream or labelStatus on this siteWhat it carries in a sweeping episode
RGB and depthPart of the ten-stream episode schema, synced under 2 ms; which streams this setup yields is set in the specKeeps the tool, the debris and both hands on one timeline
3D hand pose, per-joint visibilityStated; 21 joints per handCarries how the fingers hold and move the handle
Contact and grasp eventsStatedMarks when fingers meet the handle or the debris
Action segmentsStated; frame-accurateSeparates the sweep from the collection
Task instructionOne per episodeStates the job in language
Force or tactile data; success or quality labelsNot stated for this rowDefined in the spec, if needed

Failure modes and QA

What goes wrong in floor sweeping capture, and what QA does about it

Left to right: the failure mode, what the site states, and what a buyer sees. "Not stated" means the site does not say.
Failure modeWhat the site statesWhat a buyer sees
Fingers hidden behind the handle or the pilePer-joint visibility flag on hand pose; a multiview angle available in the specA hidden joint flagged as hidden, not guessed
Reach and grasp blur and occlusionReach and grasp frames are where blur and occlusion show upHow often it occurs on this row: Not stated
Invalid depth in the manipulation regionEpisode rejected when more than 35 percent of depth pixels are invalidReject log per batch
Tool or debris out of frameEpisode rejected when the object is out of frame for more than 15 percent of itReject log per batch
Bystander in frameFaces, plates and screens blurred and reviewer-confirmed; undocumented bystander rejected; footage that cannot be de-identified is discardedReject log per batch; anonymization record ships with the data
Calibration driftSolved before and after each session; 0.28 px RMS gateCalibration shipped with the episode
Sync breachRejected beyond the 2.0 ms ceiling for more than three consecutive framesReject log per batch
Judgement of whether the floor is cleanNot stated; no success label is listedNot claimed; set in the spec

Skill spec

What the skill spec fixes for a floor sweeping order

Spec element and where a buyer can see it in the delivery. "Set per program" means the site states no fixed value.
Spec elementWhat it decidesWhere it shows up
Row"Sweep a floor area", Available on requestSet per program; scoped and recruited to spec
Stages and orderWhat one step is: the sweep, the collectionEpisode boundaries and action segments; set per program
Episode scopeOne stage or the whole jobSet per program; the site does not state an episode length
Object definitionWhether the tool or the debris counts as the objectContact events and the out-of-frame reject rule; set per program
Rig and streamsMultiview angles, hand pose and othersThe channels you can read; confirm on the Spec Pilot
StereoWhether a stereo pair is wantedAgreed through the general stereo offer
Delivery formatHow the data is packagedRLDS, LeRobot, WebDataset, HDF5, zarr or Rerun .rrd
Accept criteriaWhat passes QA, including what counts as a rejectReject log per batch
LicenseWho owns the datasetPerpetual, irrevocable, buyer-owned, non-exclusive by default

Example footage

What does first-person capture look like?

One real clip already published on this site, shown as a format example: ten seconds of first-person home cooking with faces blurred. It does not show floor sweeping, a multiview rig or handheld grippers.

egocentric_cooking_10s.mp4 · first-person view · faces blurred · 1080 × 1080 web preview · format example, not a floor sweeping clip

No floor sweeping clip is published on the site, so this is labelled as a format example. Request a sample to see delivered files. See sample data outputs, request an egocentric data sample.

FAQ

Egocentric floor sweeping data, answered.

What is egocentric floor sweeping and debris collection data?
First-person video of a person sweeping a floor area and collecting the debris, with hand pose alongside, collected on demand to a written spec.
Which catalog row covers it, and what is its status?
One row in the Hospitality Service Set (table, bar, room): "Sweep a floor area", described as "Sweep and collect debris.", rated Easy, with the capture setup "Multiview rig + handheld grippers". Its status is Available on request, and this page claims no delivered hours.
Is this head-mounted phone capture?
No. The row lists a staged working set recorded by a multiview rig while the operator uses handheld grippers. Stereo is available only through the site general stereo offer, agreed in the skill spec.
Does the row name a broom or a dustpan?
No. The row says only "Sweep and collect debris." The catalog names no broom, dustpan, debris type or floor surface for it, so this page claims none. The tools are set in the skill spec.
How is this different from floor cleaning, lobby or construction cleanup data?
Floor cleaning and mopping is a family page across mopping, sweeping and vacuuming rows, the lobby page covers one Ready to deploy row, and construction cleanup covers two Active collection rows. This page is about the one sweep row on the hospitality set.
What does each episode contain?
The episode schema has ten streams synced under 2 ms, including depth, 3D hand pose with per-joint visibility, contact and grasp events and frame-accurate action segments, plus one task instruction. Which streams a multiview rig yields for this row is agreed in the spec.
Does the site state floor surfaces, area sizes or task times?
Not stated. The site lists no floor surface, area size, debris type, safety procedure or task time for this row, so none is claimed.
How fast can it be collected?
The row is scoped and recruited to spec when you ask. The site states a median of 48 hours to a first validated batch where coverage is deep and three to four weeks where it is thin; the timeline is quoted against your spec.

Sources

Where are the delivery formats documented?

Request a custom floor sweeping and debris collection dataset.

Tell us the stages and where each starts and ends, whether an episode covers one stage or the whole job, what counts as the object, the streams you want, whether you want a stereo pair and the delivery format. We will quote reach, timeline and price against a written spec.