DATA COLLECTION CASE STUDY
Collection case study
Bring road types, lighting and subject coverage into one plan, then use pilot review to identify duplicates, exposure issues and coverage gaps.
All case studies
01 / PROJECT BRIEF
A road-perception team wants to add daytime, nighttime and suburban scenes. Start with targets, clip requirements and checks; use a pilot to refine the instructions before discussing production.
02 / SCENE COVERAGE
Keep the existing 60 / 30 / 30 clip allocation. Select a group to see its target, review priorities and the way a pilot record links to a scene.
URBAN · DAYTIME
Organize coverage around road users and junction types. Keep repeated scenes from occupying separate target slots.
Review recordCOL-D-008 · A replacement passes recheck. The original retains its exclusion note and is not counted again.
URBAN · NIGHTTIME
Include low-light usability and exposure in pilot checks. Define what needs recollection before increasing volume.
Review recordCOL-N-005 · An exposure issue awaits recollection review. It is excluded from the 23 currently passed records.
SUBURBAN · DAYTIME
Track distant subjects and changing backgrounds. Reaching a clip count does not establish that coverage is complete.
Review recordCOL-S-004 · A replacement addresses distant-subject coverage. The recheck applies only to this individual record.
Each target clip lasts 20 seconds: 120 clips and 2,400 seconds across three groups. Coverage requirements and checks are tracked by scene.
03 / WORKING METHOD
Align scene and file requirements first. Pilot checks distinguish usable records from items needing more work; revisions remain linked to their original planning item.
01 / THE APPROACH
Group indexes by scene and identify repeated or highly similar content. Replacements keep the same planning item so old and new records are not counted twice.
01 / THE APPROACH
Use pilot examples to agree on exposure and visibility. Keep items pending when evidence is insufficient and describe what needs to be supplied.
01 / THE APPROACH
Include subject distance and background variation in the scene checklist, then link records to coverage items. Unsubstantiated coverage remains incomplete.
04 / PILOT REVIEW
The preliminary review contains 24 records, split 12 / 6 / 6 across three scenes. Twenty pass initially; of four requiring action, three pass after replacement and one remains unresolved.
| Scene | Checks | Initial pass | Recheck pass / action items | Currently passed |
|---|---|---|---|---|
| Urban day | 12 | 11 | 1 / 1 | 12 |
| Urban night | 6 | 4 | 1 / 2 | 5 |
| Suburban day | 6 | 5 | 1 / 1 | 6 |
| Total | 24 | 20 | 3 / 4 | 23 |
Rates cover these 24 preliminary records only. Completion, coverage and acceptance of the subsequent 120-clip plan are recorded separately.
Explore delivery and quality05 / HANDOVER STRUCTURE
Connect collection files, scene coverage and issue handling through batch indexes, linking each deliverable to its plan and review evidence.
Link each planning item to its clip, revision, duration and batch, keeping files and indexes aligned.
Record road type, lighting, subject coverage and gaps. Distinguish target counts from verified counts.
Version the naming, encoding, resolution, equipment and timing requirements.
Retain initial checks, replacement references, rechecks and open issues without counting original and replacement records twice.
LET’S DEFINE YOUR COLLECTION TASK
Describe the model task, scene gaps and expected volume to clarify what the first pilot needs to verify.