Stereo Pool and Spa Area Maintenance Data

It is first-person video of a person looking after a hotel pool area, recorded with two calibrated cameras and with hand pose and sensor streams alongside. The task is the one row the site’s catalog lists in Hotel & Lodging. It is named "Pool & Spa Area Maintenance" and described as: skim and test the pool, arrange loungers, wipe surfaces and restock towels. Stereo describes the capture, and MCAP describes the container. They are separate choices.

The data is human capture by paid, consented contributors, not robot or teleoperation data. No named model was trained on Firsthand data for this page, and Firsthand is not affiliated with Foxglove or the MCAP maintainers.

One, in Hotel & Lodging under Hospitality & Events, in the catalog data file lib/commercial-catalog-data.ts. The environment example line reads "Hotel guest room servicing, resort housekeeping, bed-making, linen changes, bathroom cleaning, amenity restocking". The task "Pool & Spa Area Maintenance" has the description "Skim and test the pool, arrange loungers, wipe surfaces and restock towels.", is rated Easy, lists "Phone (head-mounted) / multiview rig" as its capture setup and is listed as Ready to deploy.

The row was read on the live catalog and the Hotel & Lodging environment page. The first table below reproduces it as the catalog states it, and the second splits the description into its five named steps. The site states no pool size, pool type, equipment, product or tool model for the row, and it names no hotel, resort or region.

The site defines Ready to deploy as contributors and site access already set up, so capture starts once a spec is signed. That differs from Active collection, which means recording that is running now so a spec can join an existing stream, and from Available on request, which means the work is scoped and recruited to spec when a buyer asks for it. The pool row carries the first label.

The site states no delivered hours, no clip count and no delivered stereo footage for this row, so this page claims none. What an order delivers, and when, is quoted against your spec. Ready to deploy describes the catalog capture setup, which is a head-mounted phone or a multiview rig. It does not describe stereo.

Not stated. The catalog lists a head-mounted phone or a multiview rig as the capture setup on the row, and says nothing about a stereo pair. Stereo applies only through the site’s general stereo offer: a stereo pair is a capture choice agreed in the skill spec and confirmed on a Spec Pilot. This page therefore describes stereo as an option for an order, never as the setup the catalog lists.

That distinction matters when you plan a program. If you want a calibrated pair, you say so in the spec, and the site’s stated stereo rigs are the reference for what that can mean. If a head-mounted phone or a multiview rig is enough, the Ready to deploy row is the closest match to what the catalog lists.

Four pages already sit nearby, and only one has the pool as its main topic. The egocentric pool and spa maintenance page covers the same single row with an egocentric treatment and no stereo or MCAP treatment. This page is the stereo and MCAP treatment of that row. The stereo hotel room turnover and housekeeping page covers four room rows, and its main topic is resetting a guest room.

The egocentric hotel amenity restocking page covers one row, Hotel Amenity Restocking, which restocks toiletries, towels, coffee and minibar items from the housekeeping cart and does not name a pool. The stereo window and glass cleaning page covers two window rows in Commercial Cleaning & Janitorial. The third table below sets them side by side.

Pool-area work is about where a hand and an object sit relative to each other and to the pool: how far a lounger is moved, where a towel lands, which surface a cloth crosses. A stereo pair recovers depth from the calibrated frame pair rather than from a standalone depth sensor, so the tools, the furniture, the linens and the hands share a frame.

The site gives no depth accuracy figure and no label for a skimmed pool, a clean surface or a stocked stack of towels, so whether those outcomes are resolvable in depth is Not stated. Capture at your own facility is listed as not offered, and the site names no hotel or pool for the row.

The catalog states one capture setup for the row: a head-mounted phone or a multiview rig. A head-mounted phone records the first-person view, 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 pool 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 pool order uses is Not stated on the site, and the fourth 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. The site states no rules for capturing in wet areas, no lighting for a pool area and no layout, so those are Not stated and are agreed in the skill spec.

The site states that 3D hand pose is delivered as two hands of 21 joints each in metric units in the head-camera frame, with a visibility flag per joint, aligned to depth and RGB. For pool-area work, that records how the fingers hold a cloth or a towel and how they grip a lounger, and the flag records which joints were hidden behind an object. Contact events mark when fingers meet an object, and action segments mark where skimming ends and arranging begins.

The site states that egocentric video puts hands entering the frame from below, occlusion during grasp and motion blur during reach into the training distribution. A lounger moved by hand or a stack of towels carried against the body is that case. Force or tactile data is Not stated for this row. The site offers a tactile glove tier as a pilot-ready option, but does not state that it has been used on a pool row, so treat force data as an add-on to agree in the spec.

Little, and this page stays inside it. The site names reflective surfaces and clutter as cases where a single camera struggles in hard environments, and notes that wet and reflective surfaces degrade active-stereo depth in its kitchen dataset. A pool area is wet and bright, but the site states no depth result for a pool, for water or for glare, so how a stereo pair behaves there is Not stated.

The site ships per-frame depth confidence maps for its kitchen captures, and whether a pool order ships them is Not stated, so ask in the spec. The row says to test the pool, but the site does not say what is tested, with what, or what the result is used for. This page makes no water-chemistry, chemical-handling or water-safety claim, and none should be read into it.

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 pool-area work the site states hand pose, depth recovered from the stereo pair, IMU, contact events, action segments and per-frame instance masks elsewhere. 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. The only language data tied to Firsthand capture is one task instruction per episode.

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 fifth table below sets each stream beside what the site states about it.

Hand occlusion is the first risk. The site states that fingers disappear behind objects, and a hand closing on a towel stack or sliding under a lounger frame is partly hidden from the head camera. The visibility flag on each joint is the answer the site gives for hidden fingers, and a spec can ask for wrist views so a grip the head camera loses is still recorded.

Reflective and cluttered scenes are the second. Whether glare off water, wet tiles or glass, or a pool deck crowded with furniture, behaves like the kitchen case on a stereo pair is Not stated. Calibration is the third, 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.

Force and tactile readings are not among the listed streams, and the site states no label for a skimmed pool, a clean surface or a restocked shelf, so what counts as one finished pass is written into the spec.

The catalog line names five activities, and they do not look alike on camera: a skim, a test, moving loungers, wiping surfaces and placing towels. Action segments carry start, end, verb and noun, so the spec decides where one segment ends and the next begins, and which object is the noun. The segments can follow the catalog verbs: skim, test, arrange, wipe and restock.

The site states no episode length, no segment count and no order for the row, and the catalog does not split it into finer steps. Whether an episode is one step, one lap of the pool area or a full pass is set per program. Put that boundary and the verbs you expect into the skill spec, and check them on the Spec Pilot before you scale.

Episodes are machine-checked at ingest against the stated reject criteria, and a human reviewer then checks the result. The site states these reject criteria for every episode: the manipulated object out of frame for more than 15 percent of the episode, more than 35 percent invalid depth pixels in the manipulation region, a sync breach beyond the ceiling for more than three consecutive frames, calibration drift beyond tolerance, an undocumented bystander, and a mismatch against the named skill spec.

The site states no blur or sharpness rule and no rule for glare. A rejected item goes to the reject log, which ships with every batch, and is recaptured at our cost. Each batch is validated against signed accept criteria before it ships.

For every delivered episode the site states that faces, plates and screens are detected and irreversibly blurred at ingest, that a reviewer confirms the result before anything ships, that any identifiable un-consented person goes to human review, and that footage that cannot be de-identified is discarded. Every episode links to a signed contributor release through a documented consent chain, and the consent record and the anonymization record are delivered with the data.

A hotel pool area can be a place where guests are present. The site’s hospitality page states that front-of-house settings are bystander-dense, with lower yield after de-identification, and does not say whether a pool area counts as front-of-house. Who may be in frame is agreed in the spec. This page makes no safety, certification or water-handling claim beyond the site’s own wording.

Off-the-shelf covers what is already in stock: the stereo category lists the stereo datasets and hand-tracking video, and only dataset 06 is stated as MCAP. This page does not claim an off-the-shelf dataset of pool or spa upkeep, so this is custom collection: custom collection at scale through a network of thousands of capture providers, for a consistent, recurring data flow to labs.

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’s hospitality page lists hospitality coverage as thin, and the site does not say which speed applies to a pool order, so ask when you request the quote. Collections are billed per validated hour, and on-demand top-ups run against the same spec and accept criteria after each training run.

Describe the pool-area steps and their order, the items involved, what counts as a finished pass, the setting 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 sixth table below shows what each spec element decides.