DATA COLLECTION

Data collection services

Fill the gaps in your data.Start with a collection pilot.

Plan collection around missing scenarios and data types, and validate the approach with a pilot. Collect images, video, speech, text, 3D and multimodal data with source records and file indexes.

Images · Speech · Text · Spatial data
TASK-BASED SOURCES & COVERAGE
BriefTask · scenes · constraints
ProcessPilot · records · checks
DeliveryFiles · indexes · manifests

TASK-BASED SOURCES & COVERAGE

YOUR STARTING POINTIf you already have some data, first identify coverage gaps. You may not need to collect everything again.

COLLECTION SCENARIOS

Choose the data. Define the first collection batch.

Review coverage, collection conditions and checks for each data type. Agree source permissions before work begins.

IMAGE
Product capture: organize images by subject, viewpoint and lighting.
Product capture: organize images by subject, viewpoint and lighting.

IMAGE

Match image coverage to real tasks.

Coverage
Plan subjects, backgrounds, viewpoints and lighting; record sources and capture conditions.
Collection brief
Agree on resolution, clarity, source permissions, deduplication and class distribution.
Quality checks
Sharpness, exposure, duplicates, missing files and class coverage.
Discuss this collection type

COLLECTION PLAN

Road-video collection: a pilot plan.

This road-perception project shows how to break down coverage targets. Other data types use the same dimensions–volume–checks approach with task-specific units.

COL-001 · Initial pilot plan

PILOT PLAN
COL-001 · Initial pilot plan
Scene combinationPlanned volumeReview focus
Urban road · daytime60 clipsParticipants and junction coverage
Urban road · nighttime30 clipsLow-light usability and exposure
Suburban road · daytime30 clipsDistant objects and varied backgrounds

120 clips total · 20 seconds each · Three scene groups

Review target volumes by scene group and use the pilot to confirm routes, equipment settings and recollection criteria.

Data requirements

  • Match every clip to a batch-index record
  • Record scene tags, timing and equipment references
  • Confirm naming, encoding and resolution in the pilot

Collection quality checks

  • Check decoding and clip completeness
  • Review duplicates, scene tags and coverage
  • Log failed checks and the recollection approach
Road collection scene

See how this plan handles duplicate clips, exposure issues and coverage gaps.

View collection case

INPUTS & DELIVERABLES

Clear requirements. Defined deliverables.

From files to text entries, recording logs to pair indexes, define delivery units and structure for the task. The downloadable plan illustrates road-video coverage.

Prepare for the first discussion

  • Model task and intended use
  • Scene dimensions, estimated volume and exclusions
  • Output preferences, equipment and timing constraints
  • Source permissions, access and data-handling needs

Deliverables agreed for your project

  • Collection files organized by batch
  • Indexes, scene tags and association records
  • Collection guidelines and equipment / calibration references
  • Coverage checks, exception records and version manifests

PROCESS & QUALITY

Use a pilot to turn requirements into instructions.

Each stage produces a record you can check. Agree volumes, schedules, acceptance criteria and responsibilities for your project.

  1. Define the brief
  2. Plan & pilot
  3. Collect in batches
  4. Review & complete
  5. Accept & deliver

STAGE 01 / 05

Define the brief

Clarify the task, scenes, source conditions and handover boundaries.

THE OUTPUTbrief & coverage draft
  1. Define the brief
  2. Plan & pilot
  3. Collect in batches
  4. Review & complete
  5. Accept & deliver

STAGE 02 / 05

Plan & pilot

Assess capture conditions and check a small batch against expectations.

THE OUTPUTpilot samples & guidelines
  1. Define the brief
  2. Plan & pilot
  3. Collect in batches
  4. Review & complete
  5. Accept & deliver

STAGE 03 / 05

Collect in batches

Follow the agreed plan, recording equipment, scenes and exceptions.

THE OUTPUTfiles & batch records
  1. Define the brief
  2. Plan & pilot
  3. Collect in batches
  4. Review & complete
  5. Accept & deliver

STAGE 04 / 05

Review & complete

Check integrity, usability and coverage, then identify missing items.

THE OUTPUTreview & issue lists
  1. Define the brief
  2. Plan & pilot
  3. Collect in batches
  4. Review & complete
  5. Accept & deliver

STAGE 05 / 05

Accept & deliver

Reconcile files and indexes, check formats and complete the handover.

THE OUTPUTdataset & version notes
Every step leaves a record.

FAQ

Before collection begins

01Do we need to recollect data we already have?

No. Review the coverage and usability of existing data first, then plan collection for the gaps. Reuse depends on source permissions and task requirements.

02Can we specify equipment, regions, languages or scenarios?

Yes, as requirements for assessment. Feasibility depends on equipment, site conditions, source permissions and project arrangements, and is checked during the pilot.

03How are source permissions and participation agreed?

Define intended use, participation, permissions and retention before collection. Sources with unclear conditions remain pending until those conditions are resolved.

START WITH THE SCENE

Define the first batch around your use case.

Share the model task, scene scope and estimated volume to identify what the pilot should validate.