IMAGE, 3D & SENSOR DATA
Four sensors read one instant. Calibration makes them agree.
A camera, a LiDAR, a radar and an IMU record the same moment, each in its own frame and on its own clock. A label is only true once it survives the projection between them.
YPAI collects, calibrates, labels and evaluates image, 3D and sensor data in one chain of custody. Intrinsics and extrinsics are verified per delivery, streams share one clock, and every record carries its consent, calibration and inspection. Built in Norway on EEA infrastructure, with identity-verified contributors.
0.4px
live · mean re-projection error · specimen
within tolerance
tolerance set at scoping · in the SOW
the returns and this number are computed in your browser from this frame's depth
THE REGISTER
Two sensors disagree until the mount is right. Re-projection error says by how much.
A specimen rig looks at one pallet. The camera's box is the reference, and the LiDAR's cuboid reaches it through the mount you set. Move the mount and the re-projection error moves with it. Solve the calibration and the two agree.
- live · re-projection error
- 71.30px
- box agreement
- 0.491IoU
- corners within 1 px
- 0/ 8
camera · reference lidar · through the mount
specimen rig · synthetic geometry · every number is computed in this tab
Or read your own frame.
Drop a photograph. yolov10n draws the camera's box and Depth Anything v2 reads relative depth from the same pixels, which lifts the box into a depth slab. Both models run in this tab and the file stays in your browser. This is monocular depth from one photograph: a model's first pass.
THE CONDITION SPACE Sensor · Geometry · Light and weather · Scene · Motion · Time
Six axes decide whether the data holds up in deployment.
You name the range the system has to work across. The rig is built to span it, and every frame lands tagged on all six, so a delivery's coverage is a count.
this frame as captured
the rig's own frame, at rest
every pass is computed from this frame's depth
AXIS 01
Sensor
AXIS 02
Geometry
AXIS 03
Light and weather
AXIS 04
Scene
AXIS 05
Motion
AXIS 06
Time
this frame as captured · the value needs its own capture all six axes recorded per frame
returns computed from a monocular depth map of this frame · fog, night, glare and the moved mount rendered on your GPU from that depth
THE CHANNELS six specialists · the models run in this tab
Six specialists, each with its own measure.
Each frame below gets a model's first pass in your browser, in the label type that specialist delivers. The service behind it carries the guideline, the human review and the acceptance measure.
- 01 Image annotation Boxes, polygons, keypoints and attributes on the camera frame, with the guideline and the record. every object, its class, its confidence, one polygon measured as IoU per box · agreement per batch
- 02 Semantic and instance segmentation Pixel masks with boundary rules and human-only lanes for medical, aerial, 3D and microscopy. instances and classes, one mask each measured as mIoU · Dice · boundary F
- 03 LiDAR and 3D point cloud 7-DoF and 9-DoF cuboids, per-point semantics and tracking, calibration-aware labels. a 7-DoF cuboid on classified returns measured as 3D IoU · track continuity
- 04 Sensor fusion One label held across camera, LiDAR, radar and thermal, on one clock with the IMU's ego-motion. one label on three streams, the error drawn measured as projection consistency · sync
- 05 Medical imaging Expert-reviewed labels under a task protocol, reader qualifications on file. two readers, the disagreement drawn measured as reader agreement · Dice
- 06 Robotics and industrial vision Perception labels for robots and visual quality control on the line. the part's pose from its mask measured as defect recall · IoU
boxes, polygons, instance masks, the cuboid and the pose were read by yolov10n, EdgeTAM and SlimSAM in your browser as the plates scrolled in · each frame lifted on its own depth map · the frames stay in this tab · in a delivery this is the first pass a reviewer starts from
scoped at intake Image collection Sensor and IoT collection Geospatial capture
Image dataVideo dataPhysical AI dataSpeech and audio dataThe annotation operating model
ONE FRAME'S RECORD
Every frame ships with what was done to it.
Capture, consent, calibration, label, inspection, acceptance, delivery. The record is written as the work happens and travels with the file. Hold the gate the way a reviewer does, and the frame is accepted.
- 01 captured cam0 30 Hz · lidar0 10 Hz · radar0 20 Hz · imu 200 Hz · one PTP clock
- 02 consent contributor verified by identity · release v3 · purpose written in
- 03 calibrated intrinsics K · extrinsics lidar0→cam0 · re-projection error 0.41 px
- 04 labelled 1 cuboid · projected to cam0, cam1, radar0 · SAM 3 first pass · 6 of 8 vertices moved by a person
- 05 inspected consensus 2 of 3 · κ 0.91 on the batch · honeypot pass
- 06 accepted gate held by a named reviewer · rubric v4
- 07 delivered manifest · sha256 per file · Croissant · Article 10 data card · erasure within 30 days
WHO DOES THE WORK model first pass → human decision
A model draws first. A person decides. Some lanes are human from the first vertex.
SAM 3 reads a concept from a text prompt and draws the first pass on the server. The reviewer decides, and the file records which vertices the model drew. Medical, aerial, 3D and microscopy lanes are drawn by people from the start.
- Natural images SAM 3 first pass, human review and adjudication model first
- Industrial and robotics first pass where the concept is nameable, human on every defect model first
- LiDAR and 3D human-drawn cuboids, model-assisted tracking human-led
- Medical and microscopy credentialed readers from the first vertex human only
- Aerial and geospatial human-drawn, agreement per tile human only
A network of 210,000+ contributors across 50+ countries, verified by identity. Each project's crew is recruited from it for the rig and the scene the project names.
THE RELEASE, PER RECORD
- consent
- recorded per contributor, per purpose, per session, withdrawable
- evaluation use
- written separately from training use
- training use
- territory, term and withdrawal handling defined
- commercial deployment
- named at scoping and written into the release
- residency
- EEA processing; subprocessors and transfers defined per engagement
- erasure
- within 30 days of contract end, with execution evidence
THE PLATFORM
Every decision stays bound to the frame.
The platform carries your requirement through the work and binds every decision to the asset it was taken on. The record ships with the delivery, so what you receive can be inspected, not just trusted.
- binds
- capture, consent, label, review, inspection, acceptance
- record
- ships with every delivery, with an integrity check
- console
- native human-review core on self-hosted European servers
- residency
- subprocessors and transfers defined per engagement
- consent recorded per contributor
- residency and transfers defined per engagement
- erasure within 30 days of contract end
PILOT TO PRODUCTION
One pilot against your requirement.
A pilot is scoped to your specification, quality thresholds and acceptance criteria, and reviewed against them before anything scales. Scope and commercial terms are agreed before it starts. Production is a separate decision, taken after the pilot review.
The pilot fixes
- 01 Scope of work
- 02 Technical requirements
- 03 Acceptance criteria
- 04 Data protection and rights
- 05 Commercial structure
- 06 Remediation and change control
WHERE THE RIG GOES
Every industry mounts a different set of sensors.
The table shows what a typical programme carries, and each row opens the industry's own page. The scoping call fixes yours.
SCOPE THE FIRST DELIVERY
Two sentences start the scoping.
Name the sensors, the task and where the model fails today. An engineer or delivery lead reads the brief and replies within one EU business day, starting with what is feasible.
- 01 Describe the rig and the task
The sensors on the bar, what the model has to do, where it fails, and how the data will be used.
- 02 Feasibility read
Scenes, sensors, calibration needs and volume checked against the network. You get a plain answer on what is feasible.
- 03 Pilot delivery
Representative frames with their calibration, consent and inspection records, judged against your acceptance criteria.
- 04 Production
Weekly deliveries with per-sensor QA, versioned manifests and the record for every frame.
GOVERNANCE
Calibration, consent and audit readiness
What ships with an image, 3D or sensor delivery?
Every frame carries its capture metadata on one clock, the consent record of the contributor, the calibration in force (intrinsics and extrinsics with the re-projection reading), the label with the provenance of each vertex, the inspection result and a SHA-256 hash. The delivery carries a versioned manifest, a Croissant description and a data card written in the order EU AI Act Article 10 asks for, and a signed data processing agreement. The sensor fusion service shows how one label is checked across streams.
How are the sensors kept on one clock?
The rig's instruments are synchronised with IEEE 1588 Precision Time Protocol where the hardware supports it, and every record carries the clock offset observed at capture. The tolerance a project needs is set at scoping as a service specification and checked on every delivery. It is written into the acceptance criteria.
Which parts does a model draw, and which does a person?
SAM 3 concept pre-labelling draws the first pass on the server from a text prompt. A reviewer decides in the native review console, and the file records which vertices the model drew and which a person moved. Medical, aerial, 3D and microscopy lanes are drawn by people from the first vertex. A model output is a first pass; what is delivered is the reviewer's decision.
When do the EU AI Act data-governance obligations apply?
Article 10 sets the data-governance duties for high-risk systems: documented collection processes, origin, preparation including annotation, and examination for bias and gaps. Under Article 113 as amended, the Annex III obligations apply from 2 December 2027 and the Annex I obligations, which cover AI embedded in type-approved products such as vehicles, from 2 August 2028. YPAI writes the data card in that order now.
Where is the data processed, and what happens when a contributor withdraws?
Primary operations are in Norway on EEA infrastructure, with subprocessors and transfers defined per engagement. When a contributor withdraws consent, the affected records are quarantined, the withdrawal is reported to you with a ledger entry, and erasure completes within 30 days with execution evidence. Delivery controls are described on the ethical framework page.
Bring the rig, the dataset or the failure case.
If YPAI is not the right fit, we will say so directly.