The same problems show up whether you are building perception for autonomous vehicles, warehouse robotics, drones, construction site monitoring, or survey and mapping — anywhere a LiDAR sensor produces frames that a model has to learn from.

This guide covers what 3D point cloud annotation actually involves: which annotation types exist, the five steps of building a dataset, what drives cost per frame, where in-house point cloud annotation tends to break down, and how to evaluate an outsourcing partner. It is written for engineers and project managers in autonomous driving, ADAS, and robotics who have shipped 2D annotation before and are now sizing up the 3D version of the same problem.

When You Actually Need 3D Point Cloud Annotation

Not every perception problem needs 3D. Adding LiDAR to a project that a camera could have handled multiplies your data cost for no gain, so the first decision is whether you need it at all.

2D image annotation is usually enough when your model only needs to answer “is this object present, and where is it in the image?” Classification, counting, defect detection on a fixed camera, and most retail or inspection use cases fall here. If you are at this stage, our guide to creating training data for YOLO covers the 2D workflow end to end.

You need 3D point cloud annotation when the model has to answer “how far away, how big, which direction is it facing, and where will it be next?” Metric distance and heading cannot be recovered reliably from a single 2D box. Concretely:

• Autonomous driving and ADAS. Path planning needs the distance and orientation of every vehicle, pedestrian, and cyclist in metric space, not pixel space. Braking decisions depend on it.
• Robotics. Point cloud annotation for robotics AI supports navigation, obstacle avoidance, and grasping, where the robot needs the geometry of free space as much as the identity of objects.
• Infrastructure and site inspection. Aerial or terrestrial LiDAR scans of roads, bridges, power lines, and construction sites, where measurement is the output.
• Night, glare, and adverse weather. LiDAR does not depend on ambient light, so datasets covering these conditions often rely on it where a camera-only dataset would fail.

A useful middle case: some teams start with 2D annotation on the camera stream, confirm the model concept works, and only then extend to LiDAR point cloud annotation on the same scenes. That sequencing keeps early costs low and is worth considering before committing to a 3D dataset.

Annotation Types for LiDAR Data

“3D annotation” is not one task. The four types below have very different labor profiles, and mixing them into a single project without deciding which you need is one of the most common ways a budget gets away from a team.

3D cuboid annotation services are the entry point for most detection projects and the type teams request first. Segmentation is where the per-frame labor climbs steeply, because the unit of work moves from “one box per object” to “every point in the scene.” If you are weighing the same question in 2D, the trade-off is structurally identical and covered in our semantic segmentation annotation guide.

Tracking IDs deserve a specific warning. Annotating 200 isolated frames and annotating a 200-frame continuous sequence with persistent IDs are not the same job, even though the frame count matches. The second requires the annotator to hold object identity across occlusion events, and it costs meaningfully more. Decide which you need before you request a quote.

3D Point Cloud & LiDAR AnnotationLiDAR annotation services for autonomous driving, robotics and surveying: 3D cuboids, segmentation and sensor fusion. Full-volume QA, from $0.121 per cuboid.annotation-support.com

Building a 3D Point Cloud Dataset: Five Steps

1. Collect and sample frames

A LiDAR sensor running at 10 Hz produces 36,000 frames per hour of driving. Annotating all of them is neither affordable nor useful, because consecutive frames are highly redundant.

Sample instead. Take keyframes at a fixed interval, then deliberately oversample the situations your model will fail on: intersections, merges, dense pedestrian crossings, night, rain, and unusual objects. A dataset of 1,000 well-chosen frames will beat 10,000 frames of empty highway. Scene diversity, not frame count, is what moves accuracy.

2. Define classes and write the annotation spec

This is the single highest-leverage step, and the one teams consistently under-invest in. In 3D, three questions cause almost all of the spec drift you will encounter later:

• Occlusion. A vehicle is 60% hidden behind a truck. Do you box the visible points only, or do you extrapolate the full vehicle extent from the visible portion? Both are defensible. Only one can be in your dataset.
• Sparse distant objects. At what point does an object have too few points to label? Define a minimum point count or a maximum range, and state it explicitly. “Use your judgment” guarantees inconsistency.
• The ground plane. Does a cuboid extend down to the road surface, or does it stop at the lowest returned point on the object? Wheel-level returns are noisy, and this choice shifts every box in the dataset.

Write the answers down, with annotated example frames showing the edge cases. A spec with pictures resolves disputes that a spec with prose does not.

3. Annotate

Work in a point cloud annotation tool that supports oriented cuboid fitting, multi-view panels (top-down, front, side), and frame-to-frame interpolation. Interpolation matters more in 3D than in 2D: annotating an object at frame 1 and frame 20 and letting the tool interpolate the intermediate poses removes a large share of the manual work in sequence projects. Open-source and commercial options both exist, and the right choice depends on whether you need sensor fusion views and how your team handles review. We will cover tool selection in detail in a follow-up article.

Whichever tool you use, plan the review pass at the same time as the annotation pass. In 3D point cloud labeling, review is not a formality — see the cost section below.

4. Convert and split

Export to a format your training pipeline already reads. KITTI and nuScenes are the common public conventions, and most detection frameworks ingest one or both. Confirm two things before you export at scale: the coordinate convention (which axis points forward, where the origin sits) and the heading angle convention. A 90-degree systematic rotation error is easy to introduce and hard to notice until your evaluation numbers are inexplicably poor.

Split train, validation, and test by scene or by drive, never by randomly shuffling individual frames. Consecutive frames from the same drive are near-duplicates; shuffling them puts near-identical data on both sides of the split and produces an evaluation score that flatters your model and will not survive deployment.

5. Train, evaluate, and go back to the data

Train a baseline on the smallest dataset that could plausibly work, then look at the failure cases before annotating more. In 3D, failures cluster into recognizable groups: distant objects, heavily occluded objects, and rare classes. Each of those points at a specific gap — in your sampling, in your spec, or in class balance — and fixing the gap is usually cheaper than adding volume indiscriminately. Expect to revise the spec at least once after the first training run. That is normal, not a planning failure.

How Much Does 3D LiDAR Annotation Cost per Frame?

There is no single per-frame price, because a “frame” is not a fixed unit of work. A highway frame with four vehicles and an intersection frame with forty vehicles and pedestrians differ by an order of magnitude in labor while both counting as one frame.

Pricing at ANOSUPO is per annotated object, not per frame, and billing is fully usage-based with no setup fee, no management fee, and no minimum order:

The 2D rates are shown for comparison: a 3D cuboid carries roughly three times the unit price of a 2D bounding box, which reflects the additional work of fitting depth, extent, and heading rather than a rectangle. Your effective cost per frame is therefore the object count in that frame multiplied by the unit rate, adjusted for the factors below. At the entry rate of $0.121 per cuboid, the highway frame above works out to about $0.48 and the intersection frame to about $4.84 — a tenfold difference for the same single frame, which is why frame count alone is a poor basis for a budget.

What moves the number:

• Objects per frame. The dominant factor. Scene density drives cost more than anything else on this list.
• Class count and attributes. Five classes with occlusion flags and heading precision requirements cost more per object than two classes with no attributes.
• Tracking across frames. Persistent IDs through occlusion add work that isolated-frame annotation does not have.
• Sensor fusion. Linking each 3D instance to its camera counterpart adds a second pass over the same objects.
• Inspection standard. Full-volume inspection costs more than spot-checking a sample, and produces a materially different dataset.

For current published rates across all annotation types, see our pricing page. For a number specific to your sensor setup, scene density, and spec, request a quote — we can estimate from a handful of representative frames.

PricingTransparent annotation pricing — Bbox from $0.036/label, keypoints from $0.021/point, segmentation from $0.152/region, 3D cuboids from $0.121, LLM evaluation from $0.121. $0 setup, fully usage-based, no minimum order.annotation-support.com

Three Places In-House 3D Annotation Breaks Down

Teams that successfully ran 2D annotation in-house often assume 3D is the same job with an extra axis. Three things are different, and each one has ended 3D annotation projects.

1. Occlusion rules fracture between annotators. In 2D, the outline of an object is visible and two annotators mostly agree. In 3D, a partially occluded vehicle has no observable “true” extent, so annotators infer it — and they infer it differently. The result is low inter-annotator agreement on exactly the cases your model most needs to get right. This is a specification problem, not a diligence problem, and it does not resolve by asking people to be more careful.

2. Inspection is heavy, and sampling does not work. Reviewing a 2D box is a glance. Reviewing a 3D cuboid means rotating the scene, checking the top-down view, checking the side view, and confirming the heading. Because 3D errors are systematic rather than random — a misunderstood occlusion rule affects every occluded object in the batch — inspecting a 10% sample tells you very little. You either inspect everything or you accept unknown quality. ANOSUPO uses full-volume inspection rather than sampling, with 99.7% quality consistency, and corrects any defect attributable to us against the agreed specification free of charge for one year after delivery.

3. Engineering time disappears into labeling. The engineers who understand the spec well enough to annotate correctly are the engineers who should be training models. In 3D, per-frame labor is high enough that this trade becomes expensive fast, and it is rarely visible in a budget line.

How to Choose a 3D Point Cloud Annotation Provider

Many vendors that offer image annotation list 3D as a capability without having run it at volume. Use this checklist when evaluating any 3D point cloud annotation company:

• Which 3D types can they actually deliver? Ask specifically about cuboids, point-level segmentation, cross-frame tracking IDs, and sensor fusion. These are four different capabilities. A provider handling cuboids well may have no segmentation workflow at all.
• How do they inspect? Full-volume or sampling? If sampling, at what rate, and what happens when a systematic spec error is found in the sample — is the whole batch reworked?
• How is security handled? Vehicle and site data typically contains public spaces, faces, and license plates, and is often commercially sensitive as well. Look for a certified framework rather than assurances. ANOSUPO is certified to ISO/IEC 27001 (ISMS), operates cloud-only with no local retention, has NDAs with all staff, separates teams per project, never reuses client data to train our own models, and physically deletes data at project close. Details are on our security page.
• How do they bill? Setup fees, management fees, and minimum order volumes change the economics of a first project far more than the unit rate does.
• Can you start small? A provider confident in their work will annotate a sample of your real data before you commit. If a vendor requires a large minimum commitment to begin, you cannot evaluate them on your own data — only on their marketing.
• Do they engage with your spec? The best signal in a first conversation is whether the provider asks about occlusion handling, ground-plane convention, and minimum point thresholds. Providers who ask these questions have annotated point clouds. Providers who only ask for frame counts have not.

Comparing 3D point cloud annotation companies on unit price alone is a mistake, because unit price is only meaningful once the spec and inspection standard are held constant. A lower per-cuboid rate with sampled inspection and no rework guarantee can easily cost more once you account for the model retraining that follows a bad batch.

3D point cloud work narrows your vendor options considerably. Our data annotation outsourcing guide lists seven criteria for evaluating an annotation partner.

In-House vs. Outsourcing

Neither answer is universally correct. The split usually follows project stage.

A common and effective pattern: keep the first few hundred frames in-house to discover what your spec actually needs to say, then hand the stable spec and the volume to a partner. The in-house phase is spec development, not data production.

Our 3D LiDAR annotation services cover cuboids, point cloud segmentation, cross-frame tracking, and sensor fusion — see our LiDAR annotation services page for scope. For research and robotics projects where the task does not fit a standard workflow, our OMRON SINIC X case study describes a complex, specialized annotation task handled with a purpose-built interface.

Complex, specialized annotation handled with custom UIs and flexibilityHow ANOSUPO walked alongside OMRON SINIC X's AI research through annotation — flexible handling of specialized tasks, custom UI design, and a sharp cut in dataset creation time.annotation-support.com

Frequently Asked Questions

Getting Started

3D point cloud annotation is not 2D annotation with an extra axis. The specification questions are harder, inspection is heavier, and per-frame labor is high enough that decisions made early — what to sample, how to handle occlusion, whether you need tracking or fusion — determine your budget more than any unit rate does.

The practical starting point is small: pick a few dozen representative frames including the hard scenes, write the spec down with example images, and annotate them. You will learn more about what your dataset needs from those frames than from any amount of planning. From there, the decision of what to keep in-house and what to hand off becomes a straightforward one.

If you would like a second opinion on your spec, or a cost estimate based on your actual frames, we are happy to look at them with you.

Free TrialTry ANOSUPO annotation free. Test our quality and communication on a sample of your real data before you commit — images, video, 3D/LiDAR and LLM evaluation.annotation-support.com

投稿 3D Point Cloud Annotation: Workflow, Cost per Frame, and How to Choose a Vendor は アノサポ｜AIアノテーション・学習データ作成の伴走パートナー に最初に表示されました。

This guide covers when segmentation is actually necessary, a 5-step workflow for building a segmentation dataset, where teams typically get stuck doing it in-house, and how to start small with a PoC instead of committing to a full dataset upfront.

When You Actually Need Segmentation

Segmentation matters when the shape of an object — not just its location — determines whether your model is useful. Three cases come up repeatedly:

• Medical imaging: precisely delineating a tumor, organ, or lesion boundary
• Autonomous driving / ADAS: pixel-level drivable-area, lane, and pedestrian boundaries
• Manufacturing visual inspection: measuring the exact shape and area of a defect

If your use case only needs to know whether and roughly where an object is present — inventory counts, simple detection alerts — bounding boxes are usually sufficient and considerably cheaper to produce. Getting this distinction right up front avoids paying for precision you don’t need.

For point-level segmentation of LiDAR data rather than images, see 3D point cloud annotation.

Bounding Boxes vs. Segmentation

The higher per-unit cost of segmentation reflects the labor of tracing a precise boundary rather than dropping four points. It’s easy to over-specify — requesting pixel-perfect masks for a task that only needed coarse localization — so it’s worth confirming the precision requirement before committing to a labeling spec.

Building a Segmentation Dataset: 5 Steps

1. Collect representative data

Start by gathering images or video that reflect the conditions your model will actually see in production. Medical images vary by device and facility; driving scenes vary by weather, time of day, and region. Most downstream accuracy problems trace back to insufficient diversity at this stage, not to the model architecture.

2. Define classes and a labeling spec

Next, define exactly what gets labeled and how. This is where class-boundary ambiguity causes the most trouble: should “pedestrian” and “cyclist” be separate classes? How should overlapping or adjacent objects be handled — allowed to overlap slightly, or forced to have a gap? Writing these rules down before annotation begins prevents a costly full re-label later. Annotation guidelines here function the same way a style guide functions for text — without one, inter-annotator agreement drops fast.

3. Annotate

With the spec in place, annotators trace boundaries using polygon or brush tools. Many teams now use semi-automatic tools like Segment Anything (SAM) to generate a rough mask that a human then corrects — this speeds up throughput, but raw model output shouldn’t be accepted as-is. Boundary precision from automated pre-labeling varies enough that a review step is non-negotiable if consistency matters.

4. Convert format and split the dataset

Once labeling is done, convert annotations into the format your training pipeline expects — commonly COCO-style polygon coordinates or PNG mask files — and split the data into train, validation, and test sets.

5. Train, evaluate, and go back to the data

Train the model and evaluate using metrics like IoU (Intersection over Union). When accuracy falls short, the fix isn’t always architectural — check which classes had the most boundary ambiguity or which scenarios were underrepresented in the training set. In a data-centric AI workflow, the dataset is usually where the fastest gains are found.

Where In-House Teams Get Stuck

Three problems show up consistently in teams building segmentation datasets internally:

• Boundary drift: different annotators trace edges differently, and consistency degrades as more people are involved — a direct inter-annotator agreement problem
• Underestimated QA time: review and correction usually take longer than the initial labeling pass, and teams rarely budget for it upfront
• Engineering time diverted: hours meant for model development get absorbed by labeling logistics and spec revisions instead

None of this means segmentation should always be outsourced — but any in-house plan should account for these costs explicitly rather than discovering them mid-project.

Pixie Dust Technologies ran into exactly this. Color-coding rebar by type for their construction-site inspection AI is segmentation work, and doing it in-house alongside algorithm development was estimated at four months. A six-person annotation team completed it in two, returning roughly two months of engineer time to the development work.

Data for construction-site AI delivered at scale, fastCase study: Pixie Dust Technologies' rebar-inspection DX "TOTTARROW" recognition AI. A dedicated 6-person ANOSUPO team delivered high-quality, color-coded rebar annotation in two months — saving about two months of in-house engineer time and freeing the team for core algorithm work.annotation-support.com

Start Small: The Case for a PoC

Estimating “how many regions we’ll need” precisely, before you’ve labeled anything, is close to guesswork. A more practical approach: run a PoC on 50–100 images first, confirm both model behavior and the soundness of your labeling spec, and only then scale to a full dataset. If your raw data also needs cleanup or preprocessing before labeling can start, it’s worth scoping that alongside the PoC — see data collection and preprocessing for what that typically involves.

Data Collection & PreprocessingData collection & preprocessing outsourcing — collection/capture, cleansing, anonymization & annotation preprocessing. We collect hard-to-source data from scratch. 99.7% quality, $0 setup, fully usage-based.annotation-support.com

In-House vs. Outsourcing

Segmentation is one of the more expensive annotation types, so it’s often the first task teams outsource. See our data annotation outsourcing guide for what drives unit price and how to compare vendors.

Working with a Japan-Based Annotation Partner

ANOSUPO, operated by Borderless Japan, provides segmentation annotation as part of its image and video annotation service. Instead of sampling-based spot checks, every deliverable goes through full-volume inspection, with a measured label consistency of 99.7%. Pricing is fully usage-based — no setup fee, no account management fee, and no minimum order — with segmentation PoCs typically starting around 50–100 images. Any defects traced to our process are corrected free of charge for one year after delivery. Rate details are on the pricing page.

PricingTransparent annotation pricing — Bbox from $0.036/label, keypoints from $0.021/point, segmentation from $0.152/region, 3D cuboids from $0.121, LLM evaluation from $0.121. $0 setup, fully usage-based, no minimum order.annotation-support.com

On the security side, the company holds ISO/IEC 27001 (ISMS) certification, doesn’t retain or process data locally (cloud-only), has NDAs with all staff, isolates teams per project, and physically deletes data once a project is complete — none of it is used to train the company’s own models.

For teams working primarily with bounding boxes rather than segmentation, our companion guide on building YOLO training data covers the box-annotation workflow in the same level of detail.

How to Create Training Data for YOLO: Annotation Workflow and Starting Small with a PoCA five-step workflow for YOLO training data: class design, annotation, label format, and sizing your first PoC.annotation-support.com

Frequently asked questions

SecurityANOSUPO security. ISO/IEC 27001 (ISMS) certified, with a strict no-retention/no-local-storage policy, NDAs with all staff and per-project team isolation to keep your training data safe.annotation-support.com

Summary

Segmentation earns its cost when shape — not just location — determines whether a model is useful. The workflow itself isn’t exotic: representative data, a clear labeling spec, careful annotation, format conversion, and a feedback loop back from evaluation to the dataset. Where teams typically lose time is boundary consistency and QA, in-house or out. Starting with a small PoC, rather than committing to a full dataset upfront, is usually the fastest way to find out which approach fits.

Free TrialAnnotate a sample of your own data under our production workflow before committing to a full order.annotation-support.com

投稿 Semantic Segmentation Annotation: Pixel-Level Data and Outsourcing は アノサポ｜AIアノテーション・学習データ作成の伴走パートナー に最初に表示されました。