Annotate Objects

Annotate Objects

Draw bounding boxes around objects in your images. Accurate annotations are crucial for model performance.

Annotation Interface

Annotation Guidelines

Box Placement Rules

Good annotation:
┌─────────────────┐
│   ┌─────────┐   │  Box tightly surrounds
│   │ [car]   │   │  the visible object
│   └─────────┘   │
└─────────────────┘

Bad annotation:
┌─────────────────┐
│ ┌─────────────┐ │  Box includes too much
│ │             │ │  background
│ │   [car]     │ │
│ └─────────────┘ │
└─────────────────┘

Handling Special Cases

ScenarioApproach
Partially visibleAnnotate visible portion
Occluded objectsAnnotate visible parts, or use “occluded” tag
Overlapping objectsCreate separate boxes for each
Small objectsZoom in for precision
Ambiguous objectsUse “difficult” or “uncertain” tags

Quality Control

Review Workflow

  1. Random sampling - Review 10% of annotations
  2. Inter-annotator agreement - Have multiple people annotate same images
  3. Edge case review - Focus on difficult images
  4. Label distribution - Check for class imbalance

Annotation Statistics

# Get annotation statistics
stats = client.get_dataset_stats(
    dataset_id=dataset.id,
    version_id=version.id
)

print(f"Total images: {stats['total_items']}")
print(f"Annotated: {stats['annotated_items']}")
print(f"Boxes per image: {stats['avg_annotations_per_item']}")

# Label distribution
for label, count in stats['label_counts'].items():
    print(f"  {label}: {count} boxes")

Data Augmentation Preview

SeeMe.ai applies augmentations during training. Preview how your annotations will be transformed:

# Preview augmentations
augmented = client.preview_augmentation(
    item_id=item.id,
    augmentation_type="flip_horizontal"
)

# Shows image with transformed bounding boxes

Best Practices

  1. Consistency is key - Same rules for all annotators
  2. Tight boxes - Minimize background, maximize object
  3. Label everything - Don’t skip small or partially visible objects
  4. Use labels consistently - “car” vs “Car” vs “CAR” are different!
  5. Take breaks - Annotation fatigue leads to errors

Next Step

3. Train Model →