Irregular Object Boundaries, Instances, Attributes, Occlusion Rules, and Annotation QA
Polygon Annotation Services for Computer Vision Data
Uniworld OS helps organizations create boundary-aware labels for irregular objects and regions in authorized image datasets. Our polygon annotation workflows can include instance-level contours, multi-part regions, occlusion and truncation states, holes and interior exclusions where supported, class and attribute assignment, selected video-frame annotation, pre-annotation correction, polygon-to-mask preparation, edge-case queues, and geometry-focused quality review.
Managed Boundary-Aware Image Labeling
Trace Irregular Objects with Client-Defined Polygon Geometry and Ontology Rules
Polygon annotation uses connected vertices to trace the visible or approved estimated contour of an object or region. It is often selected when rectangular boxes include too much background, adjacent objects need closer separation, object shape matters, or downstream workflows require vector geometry that can be transformed into masks or other supported representations.
Uniworld OS provides polygon annotation beneath Image Annotation. Each project can be configured around the client’s authorized images, object classes, inclusion and exclusion rules, boundary tolerance, vertex density, concavity, holes, multi-polygons, overlap, occlusion, truncation, edge handling, class attributes, instance IDs, output schema, platform, exception reasons, security controls, and acceptance criteria.
The service is kept distinct from Bounding Box Annotation, which represents objects with rectangles; Semantic Segmentation, which typically labels pixels or raster masks; Polyline Annotation, which represents open paths; and Landmark Annotation, which uses defined points or keypoints.
Polygon boundaries versus pixel masks
Polygons are vector shapes created from ordered vertices. Pixel masks are raster representations. A polygon may be rasterized into a mask when the target format and geometry support it, but edge precision, holes, overlaps, anti-aliasing, class priority, and instance separation must be defined before conversion.
- Authorized still images, selected video frames, image IDs, frame IDs, pre-annotations, class ontologies, object examples, difficult-case examples, and annotation instructions
- Client-defined class names, instance rules, boundary tolerance, vertex guidance, overlap handling, visible-versus-full contour rules, occlusion, truncation, holes, small-object thresholds, attributes, and exceptions
- Polygon coordinates, multi-polygon records, masks where approved, class or instance maps, JSON, XML, CSV, client-tool exports, source crosswalks, and client-defined outputs
- Completed annotations, hold items, ambiguous-boundary queues, missing-class reports, invalid-geometry lists, duplicate-object candidates, correction logs, object counts, and reconciled batches
Polygon Annotation Capabilities
Vector Boundary Labeling Configured Around the Object, Ontology, and Target Schema
The exact workflow depends on image quality, object size, contour complexity, overlap, occlusion, transparency, shadows, viewpoint, vertex guidance, class ontology, annotation platform, output format, and the level of review required.
Polygon Annotation for Irregular Objects
Trace approved object boundaries using connected vertices for objects that cannot be represented adequately by a simple rectangle, including vehicles, products, vegetation, structures, equipment, road features, defects, and other client-defined classes.
Instance-Level Polygon Annotation
Create separate polygon records for individual visible object instances, applying client-defined instance IDs, class labels, attributes, overlap rules, occlusion states, truncation states, and object relationships.
Multi-Polygon and Disconnected-Region Labeling
Represent approved objects or regions with multiple disconnected polygon components where the project ontology and target format support multi-part geometry.
Occlusion and Truncation Handling
Apply documented rules for partially hidden, edge-cut, cropped, overlapping, obstructed, or truncated objects, including visible-boundary-only or estimated-boundary workflows where expressly authorized by the client.
Holes, Cutouts, and Interior Exclusion Areas
Create approved interior exclusions or hole regions where the annotation tool and output format support them, while documenting unsupported geometry or ambiguous interior boundaries.
Fine-Boundary and Complex-Contour Annotation
Trace approved curved, angled, concave, narrow, or irregular contours using a client-defined balance between boundary fidelity, vertex density, annotation speed, and downstream requirements.
Class, Attribute, and Relationship Assignment
Apply approved labels, sublabels, object states, conditions, directions, visibility levels, damage types, material types, scene tags, group IDs, parent-child relationships, and other ontology fields.
Polygon Annotation for Images and Selected Video Frames
Annotate approved still images or client-selected video frames with frame IDs, sequence references, object identities, polygons, attributes, and exceptions, without implying continuous video tracking unless separately scoped.
Pre-Annotation Review and Correction
Review client-provided or tool-generated preliminary polygons, correct approved classes and vertices, remove unsupported regions, refine boundaries, apply attributes, and route uncertain cases according to the project instructions.
Polygon-to-Mask and Format Preparation
Prepare approved polygon records, rasterized masks, class maps, instance maps, JSON, XML, CSV, or client-defined annotation files where the selected tool, geometry, and target format are compatible.
Exception, Ambiguity, and Edge-Case Queues
Flag unclear boundaries, severe occlusion, reflections, shadows, transparency, motion blur, low resolution, tiny objects, merged objects, unusual viewpoints, missing ontology classes, and contradictory instructions rather than guessing.
Polygon Annotation Quality Review and Reconciliation
Review class correctness, boundary placement, vertex density, self-intersections, closure, overlap, occlusion, holes, attributes, instance IDs, source-image mapping, exceptions, object counts, and delivery-package completeness.
Representative Polygon Geometry
Configure Boundary Rules Around the Object Shape and Dataset Purpose
Object instances, surfaces, overlaps, thin shapes, aerial regions, and specialist image sets require different contour, vertex, occlusion, privacy, and review rules.
Object Instance Annotation
Separate polygons for individual vehicles, products, people where permitted, animals, plants, tools, components, structures, or other client-defined objects.
Scene and Surface Regions
Polygon regions for roads, sidewalks, roofs, fields, water, walls, work zones, damage areas, floor regions, and other approved surfaces or scene components.
Occluded and Overlapping Objects
Client-defined visible contours, estimated full contours, or hold-and-review treatment for objects hidden by other objects, scene elements, frame edges, blur, glare, or shadows.
Small, Thin, and Complex Shapes
Carefully scoped polygons for cables, branches, narrow defects, irregular product outlines, curved parts, thin structures, and other geometry requiring special vertex guidance.
Aerial, Satellite, and Map-Style Imagery
Approved buildings, parcels, fields, roads, vegetation, water, rooftops, construction areas, and geographic features under client-defined image rights and location-data controls.
Industrial and Specialized Image Sets
Approved manufacturing, infrastructure, agriculture, retail, robotics, scientific, and healthcare-research image sets processed under domain-specific instructions and qualified client review.
Engagement Workflow
How We Set Up and Run a Polygon Annotation Project
Dataset and Use Review
Review images, rights, classes, object density, scene variation, target use, privacy, platform, formats, risks, and exclusions.
Ontology and Geometry Setup
Define classes, boundaries, vertices, holes, overlap, visible or full contours, occlusion, truncation, attributes, exceptions, and QA.
Pilot Annotation
Annotate representative large, small, concave, curved, overlapping, occluded, truncated, blurred, reflective, and unusual objects.
Production and Review
Process approved batches with class, instance, boundary, vertex, geometry, attribute, source, exception, object-count, and format checks.
Delivery and Reconciliation
Deliver annotations and exceptions, reconcile images and objects, apply approved corrections, and update controlled instructions.
Operational Applications
Polygon Annotation Across Mobility, Retail, Manufacturing, Agriculture, Geospatial, and Research Data
Every engagement should define image ownership, permitted subjects, privacy, sensitive classes, ontology ownership, domain-review responsibility, safety-critical boundaries, geographic restrictions, annotation platform, output use, retention, and final client acceptance.
Vehicles, Road Users, Road Features, and Scene Objects
Trace approved visible contours for vehicles, road objects, barriers, signs, lanes as regions where specified, and other classes under client-owned safety rules.
Products, Packaging, Shelves, and Display Regions
Annotate approved product instances, packaging boundaries, shelf areas, display regions, occlusions, overlaps, and product-condition attributes.
Parts, Components, Surfaces, and Defect Regions
Trace approved parts, assemblies, tools, material areas, visible defects, damage regions, and equipment components without making quality-acceptance decisions.
Plants, Leaves, Crops, Fields, Weeds, and Land Regions
Create approved polygons for vegetation, plant structures, crop rows, field areas, weeds, soil regions, water, and environmental features.
Buildings, Roofs, Parcels, Roads, and Land-Cover Regions
Annotate authorized imagery using client-defined classes, geometry rules, coordinate handling, privacy constraints, and location-data controls.
Objects, Workspaces, Grasp Regions, and Scene Geometry
Prepare approved polygon labels for object perception, workspace understanding, pick-and-place research, and controlled machine-vision datasets.
Foreground Objects, People Where Permitted, and Scene Elements
Trace approved subjects, props, backgrounds, regions, and object instances under rights, privacy, consent, and sensitive-content instructions.
Approved Image Regions Under Specialist Protocols
Support authorized research imagery using expert-defined classes and review criteria without diagnosis, clinical interpretation, or medical-device claims.
Polygon Correction, Relabeling, and Format Migration
Review approved legacy polygons, correct geometry, map classes, identify duplicates or invalid shapes, convert supported formats, and reconcile files.
Polygon Annotation Quality Review
What We Check Before Delivery
Review criteria are aligned with the approved ontology, source inventory, geometry rules, boundary tolerance, vertex guidance, overlap policy, visible-versus-full contour rules, occlusion and truncation states, attributes, output schema, and client acceptance criteria.
Clear Annotation, Privacy, Domain, and Model Boundaries
Polygon Labels Support Dataset Preparation—They Do Not Guarantee Model Performance or Replace Expert Decisions
Uniworld OS can create, correct, classify, validate, format, and reconcile authorized polygon annotations according to client-approved instructions. The client remains responsible for image rights, ontology design, domain interpretation, expert ground truth, model architecture, training, validation, bias review, safety analysis, regulatory use, deployment, and final acceptance.
Operational Benefits
Why Organizations Outsource Polygon Annotation Work
Closer Object Boundaries
Represent irregular objects more precisely than rectangular boxes where the training or analysis objective requires boundary-aware geometry.
Instance Separation
Keep overlapping or adjacent approved objects as separate records with controlled instance IDs, classes, attributes, and visibility states.
Ontology Consistency
Apply client-approved class names, subtypes, attributes, relationships, occlusion rules, edge treatment, and exception reasons across batches.
Flexible Geometry Outputs
Prepare approved polygon, multi-polygon, mask, class-map, instance-map, JSON, XML, CSV, or client-defined outputs after tool and format validation.
Source Traceability
Maintain image IDs, frame IDs, polygon IDs, class labels, attributes, reviewer notes, exceptions, corrections, versions, and batch relationships.
Transparent Edge Cases
Separate ambiguous, hidden, blurred, transparent, reflective, tiny, overlapping, incomplete, or unsupported objects rather than forcing labels.
Scalable Annotation Queues
Support pilot datasets, recurring production, relabeling, correction, edge-case enrichment, taxonomy updates, and migration backlogs.
Client-Controlled Model Decisions
Keep ontology ownership, safety criteria, domain interpretation, model selection, training, validation, deployment, and final performance decisions with the client.
Related Annotation and Data Services
Explore Supporting Image, Box, Segmentation, Landmark, Polyline, 3D, and Video Services
Frequently Asked Questions
Polygon Annotation Services FAQs
What is polygon annotation?
Polygon annotation traces an approved object or region with connected vertices so the label follows an irregular contour more closely than a rectangular bounding box. The output may include class labels, instance IDs, attributes, occlusion states, and source-image references.
When should polygon annotation be used instead of bounding boxes?
Polygon annotation is useful when boundary shape matters, objects are irregular, adjacent objects need closer separation, or background inside a box would create too much unwanted area. Bounding boxes are often more efficient when approximate object location is sufficient.
How is polygon annotation different from semantic segmentation?
Polygon annotation creates vector boundaries using vertices. Semantic segmentation typically assigns a class to pixels or produces raster masks. Polygons can sometimes be converted to masks, but the two methods have different geometry, edge, overlap, and format requirements.
Can occluded objects be annotated?
Yes, according to the client’s written rule. Projects may label only the visible boundary, estimate the full boundary when specifically permitted, apply an occlusion attribute, or route severely hidden objects for review.
Can holes or disconnected regions be represented?
They may be supported when the annotation tool and target format allow polygon holes, multi-polygons, or separate components. These rules should be tested during the pilot because format support varies.
Which output formats can be delivered?
Approved outputs may include polygon coordinates, JSON, XML, CSV, client-tool exports, raster masks, class maps, instance maps, or client-defined structures. Final support depends on the annotation platform, geometry requirements, and target schema.
Is a pilot dataset recommended?
Yes. The pilot should include every class, small and large objects, concave shapes, curved boundaries, overlaps, occlusions, truncation, reflections, shadows, holes, multiple instances, unusual views, poor-quality images, and expected exceptions.
What information is needed for a quotation?
Share representative authorized images, image and object volume, class ontology, inclusion and exclusion rules, edge tolerance, vertex guidance, occlusion and truncation rules, attribute schema, output format, annotation platform, review method, security requirements, and target schedule through the contact page.
Discuss Your Polygon Annotation Requirements
Share representative authorized images, image and object volume, class ontology, inclusion and exclusion guidance, boundary tolerance, vertex rules, occlusion and truncation policy, attributes, target format, annotation platform, security controls, review criteria, and expected schedule so the team can assess the project.