Industry
2D/3D annotation for camera, LiDAR, and radar data — supporting perception, prediction, and planning models with safety-critical quality standards.
Faster QA cycles
Frames annotated
3D box accuracy
Avg IoU score
Challenges
Workflow
A structured, domain-specific workflow — from data ingestion to delivery.
Camera, LiDAR, and radar data ingested with calibration matrices; multi-sensor temporal alignment verified within ±5ms synchronization tolerance.
Object taxonomies defined per ODD (Operational Design Domain) — vehicle subtypes, VRU classes, road infrastructure, weather/lighting conditions, and occlusion handling rules.
2D bounding boxes and segmentation on camera images; 3D cuboids and point-wise labeling on LiDAR; cross-sensor projection validation ensures spatial consistency.
Object IDs tracked across frames with interpolation for occluded segments. Track fragmentation rate monitored and kept below 2% per sequence.
Rare scenarios (unusual VRU behavior, extreme weather, construction zones) flagged and cataloged into a searchable edge-case library for targeted model stress-testing.
IoU ≥ 0.90 enforced for all 3D cuboids; 100% review on safety-critical classes (pedestrians, cyclists). Delivered with ASAM OpenLABEL or custom schema.
Expertise
Generic annotation vendors can label data. Domain experts label it correctly. Here's why the difference matters in your industry.
A missed pedestrian label in autonomous driving training data can have fatal consequences. Our annotators undergo AV-specific training covering VRU behavior, occlusion protocols, and edge-case identification — with 100% QA review on all safety-critical classes.
Camera and LiDAR annotations must agree in 3D space. Our calibration-aware pipeline projects 3D cuboids onto 2D images for cross-sensor validation — catching misalignments that single-modal pipelines miss entirely.
80% of perception failures occur on 5% of edge-case scenarios. Our curated library of 2,000+ edge cases — construction zones, jaywalkers, unusual vehicle types — enables targeted data collection and model stress-testing.
Comparison
See how our domain-specific capabilities compare to generic annotation services.
| Capability | UTL Data Engine | Typical Vendor |
|---|---|---|
| Multi-sensor fusion annotation (camera + LiDAR + radar) | ✓ Synchronized pipeline | Separate pipelines |
| 3D cuboid IoU ≥ 0.90 enforced | ✓ All classes | 0.80 average |
| Temporal tracking with < 2% fragmentation | ✓ Monitored | Not tracked |
| Edge-case library & cataloging | ✓ 2,000+ scenarios | Not available |
| ASAM OpenLABEL export support | ✓ | Custom only |
| 100% review on safety-critical VRU classes | ✓ | Statistical sampling |
“UTL's multi-sensor annotation pipeline cut our QA cycle time by 3x. Their edge-case library of 2,000+ scenarios was invaluable for improving our perception model.”
Perception Lead
AV Technology Company
FAQs
We support ASAM OpenLABEL, KITTI, nuScenes, Waymo Open Dataset format, Argoverse, and custom schemas. 3D cuboids include position, dimensions, rotation (quaternion or Euler), and per-point semantic labels for LiDAR.
We validate temporal alignment within ±5ms using sensor calibration matrices. Our pipeline projects 3D annotations onto all camera views for cross-sensor consistency checks — flagging misalignments automatically.
We enforce IoU ≥ 0.90 across all object classes, with 100% manual review on safety-critical classes (pedestrians, cyclists, motorcyclists). Our average IoU across all AV projects is 0.92.
Yes. We maintain consistent object IDs across frames with interpolation for occluded segments. Track fragmentation rate is monitored and kept below 2% per sequence, with manual correction for ID switches.
Our AV annotation pods scale to 100K+ frames per week with consistent quality. We've completed projects exceeding 500K frames with multi-sensor data from fleet vehicles across diverse geographies.
Related
Let's discuss your specific data challenges and build a tailored annotation pipeline.