DATA COLLECTION CASE STUDY

Collection case study

From a scene gap.To a pilot plan.

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
Road collection · scene and equipment concept
Road-data collection vehicle and sensor equipment
120Target clips
20 secTarget clip duration
3Scene groups
Road collection · sensor and scene planning

01 / PROJECT BRIEF

Agree on coverage before counting clips.

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.

Client profile
road-perception research team
Task
Road-video collection plan
Coverage
Urban day, urban night and suburban day
Current stage
Collection planning · pilot review

02 / SCENE COVERAGE

Three scene groups. Distinct review priorities.

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

Urban · daytime

Organize coverage around road users and junction types. Keep repeated scenes from occupying separate target slots.

Target clips
60
Target duration
1,200 sec

Pilot review focus

  • Scene tags match junction and road-user requirements
  • Clips decode, remain complete and meet the target duration
  • Adjacent or duplicate content is identified separately

Review recordCOL-D-008 · A replacement passes recheck. The original retains its exclusion note and is not counted again.

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

Give every gap a clear next step.

Align scene and file requirements first. Pilot checks distinguish usable records from items needing more work; revisions remain linked to their original planning item.

  1. 01

    Clip counts can conceal duplicates

    ApproachGroup 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.

    Record retainedPlanning item, original record, duplicate reason and replacement reference

  2. 02

    Nighttime usability is uncertain

    ApproachUse pilot examples to agree on exposure and visibility. Keep items pending when evidence is insufficient and describe what needs to be supplied.

    Record retainedCheck criteria, issue location, proposed action and recheck decision

  3. 03

    Distant-subject coverage is hard to verify

    ApproachInclude subject distance and background variation in the scene checklist, then link records to coverage items. Unsubstantiated coverage remains incomplete.

    Record retainedScene tags, coverage evidence, gaps and instruction version

04 / PILOT REVIEW

Use pilot records to refine the next collection.

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.

Pilot review24Records · split 12 / 6 / 6
Initial pass83.3%20 / 24 records
Recheck pass75.0%3 / 4 records requiring action
Currently passed95.8%23 / 24 records
COL-001 · preliminary review ledger
SceneChecksInitial passRecheck pass / action itemsCurrently passed
Urban day12111 / 112
Urban night641 / 25
Suburban day651 / 16
Total24203 / 423

Rates cover these 24 preliminary records only. Completion, coverage and acceptance of the subsequent 120-clip plan are recorded separately.

Explore delivery and quality

05 / HANDOVER STRUCTURE

Connect the files, coverage and issue records.

Connect collection files, scene coverage and issue handling through batch indexes, linking each deliverable to its plan and review evidence.

  1. 01

    Clips and batch indexes

    Link each planning item to its clip, revision, duration and batch, keeping files and indexes aligned.

  2. 02

    Scene and coverage manifest

    Record road type, lighting, subject coverage and gaps. Distinguish target counts from verified counts.

  3. 03

    Collection instructions and equipment references

    Version the naming, encoding, resolution, equipment and timing requirements.

  4. 04

    Review and recollection records

    Retain initial checks, replacement references, rechecks and open issues without counting original and replacement records twice.

PROJECT TAKEAWAYS

Align three things before scaling a pilot.

  1. 01

    Separate targets from completion

    Use explicit definitions for planned clips, checks and actual completed collection.

  2. 02

    Make replacements traceable

    Link replacement records to the original issue and planning item, retaining exclusions to prevent double counting.

  3. 03

    Keep coverage gaps visible

    Passing some checks does not establish complete coverage. Retain recollection needs and unresolved items.

LET’S DEFINE YOUR COLLECTION TASK

Define the pilot around your missing scenes.

Describe the model task, scene gaps and expected volume to clarify what the first pilot needs to verify.