Anonymized engagement

Video datasets, assembled
instead of licensed.

An executive team asked what it would cost to build a video dataset in house rather than license one. We surveyed the sources, designed the label taxonomy, and specified the annotation and ingestion pipeline that turns raw footage into data a model can learn from.

The brief

Licence the data,
or build the pipeline?

Commercial licensing quotes for a single source ran between $150,000 and $225,000. The question was whether an equivalent corpus could be assembled from open-access repositories and permissively licensed material, annotated to a professional standard, for materially less — and what the architecture would have to look like to keep that credible at scale.

The answer was yes, with conditions. What follows is the architecture, with the client and the subject matter removed. The shape is domain-independent: it is the same whether the footage is road scenes, industrial inspection or anything else where video becomes model data.

$150K–$225KLicensing quoted per source
~20,000Clips in the primary open corpus
95%+Annotation accuracy target

01 · Source survey

Every candidate, scored the same way.

Open-access repositories first, permissively licensed material second, custom capture only where coverage was genuinely missing. Each candidate source was assessed against the same six questions, so sources could be compared rather than argued about.

WHAT IS IN IT

Volume and coverage

Clip counts per category, not just totals. A corpus with a long tail of thin categories is a different proposition from an evenly covered one.

  • The primary open corpus carried roughly 20,000 clips across 200 categories
  • Per-category duration and clip counts documented rather than estimated

IS IT USABLE

Quality and structure

Resolution and duration decide whether a clip survives preprocessing. Structure decides whether it can be addressed at all.

  • Most source clips at 720p or better, averaging about two minutes
  • Segment-level annotations marking where in the clip the labelled event occurs

CAN WE USE IT

Licence and access

The cheapest corpus is worthless if its licence does not cover the intended use. Licence terms were recorded per source alongside the access method.

  • Cost and licence class recorded for every candidate
  • Access route noted: direct download, API, or loader library

02 · Taxonomy

The taxonomy is the contract
between data and model.

A label set that looks obvious at four clips falls apart at five hundred. We specified the taxonomy as a deliverable in its own right: a flat, explicit class list that grows on a schedule rather than by accretion, expanding to thirty to forty classes by the pilot tier.

Every label carries a start and an end. That single decision is what makes a corpus addressable at the segment level instead of the file level — you can ask for the four seconds that matter rather than the two-minute clip that contains them, which changes both storage economics and what a sampling strategy can do.

03 · Ingestion

Pull the subset, not the corpus.

Open-source loader libraries made the difference between a workable pipeline and a storage problem. A filtered subset is requested declaratively — split, class, maximum duration, maximum sample count — and only the matching material is fetched.

FETCH

Declarative subsets

A handful of lines pulls a filtered slice of a public corpus. Nothing is downloaded in bulk, and the same expression reproduces the slice later.

NORMALISE

One output contract

Everything lands in the same shape regardless of source: 1080p MP4 alongside labels as JSON or CSV, so downstream code never branches on provenance.

COST

Open tooling throughout

The ingestion layer is free and open source end to end. The spend sits in annotation and review, which is where it buys something.

04 · Annotation and review

Four tiers, each one earning the next.

Annotation is the expensive part, so it is staged. Each tier is sized to answer one question before any larger commitment is made, with hours estimated up front and quality controls added as volume grows.

TIER 0 · 4 CLIPS

Workflow validation

Proves the annotation workflow end to end and produces the first labelled output in the agreed format.

  • Lightweight single-review spot check
  • Estimated 18–24 hours

TIER 1 · 20 CLIPS

Quality controls

Scales the workflow and introduces the first real quality controls, including sampling and format validation.

  • QA report per batch
  • Estimated 44–56 hours

TIER 3 · 500 CLIPS

Production pilot

Production-scale pilot on a quality-control workflow that holds at volume, with accuracy measured rather than asserted.

  • Sampling-based review at 95%+ accuracy target
  • Scalable QC workflow

05 · When the footage does not exist

Build the world
in software instead.

Some of the cases that matter most are the ones a camera rarely catches. On separate work we build the environment in software and expose it through the standard reinforcement-learning interface — a discrete action space, dictionary observations of typed numeric arrays, a step and reset contract — so an agent developed against the simulator talks to it exactly as it would to any other environment, and the simulator can be swapped for recorded data without touching the agent.

That interface is the join between the two halves of this page. Recorded footage gives you the distribution the world actually produces; a simulated environment gives you the rare case on demand. Most serious programmes need both.