3/20/2019 Remotasks

Sky Polygon Annotation

INSTRUCTIONS
Version Number 1.0

Overview

The goal of this task is to use polygons to identify objects, and to use the same ID for objects that appear in
multiple images. Where the same object appears across multiple images - the goal is to apply the same track
ID to each object.
Alerts / Updates

Maintain a 3 pixel gap between a sky polygon and pixels of non-sky

objects!!!
Coarse polygons are OK! Try for tight polygons but it’s ok to have a loose fit on the sky polygon.
Just don’t EVER include pixels from a tree, pole or wire in the sky polygon!
CORRECT INCORRECT

You can see in the red boxes above that the sky polygon
is too tight and pixels from trees and poles are included
in the sky polygon.
This polygon has at least three pixels of
space around trees - this is good!!

DO NOT include poles in sky polygons!! This is really critical.

CORRECT INCORRECT

Pole, in red square, is included in sky polygon.

https://www.remotasks.com/course?id=sky-polygon-intro-training 1/10
3/20/2019 Remotasks

Pole completely excluded from sky polygon.

Sky polygon maintains a three pixel border
around the tree. Awesome!!!

Pole included in small sky polygon.

DO NOT attempt to label small patches of sky in between tree branches! Follow the rule if a
patch of sky is <10 pixels on any edge - don’t label it at all!

CORRECT INCORRECT

Don’t worry about small patches of sky

This polygon is a good example of not with lots of tree branches.
trying to label very small patches of sky
between branches.

Be sure to use the inter-grouping feature and keep label IDs consistent for multiple polygons that cover
the same object.
CORRECT INCORRECT

https://www.remotasks.com/course?id=sky-polygon-intro-training 2/10
3/20/2019 Remotasks

The vehicle with the purple label has

three fragments in the same image - all
This vehicle has two IDs attached. NOT
labeled with the same ID. This is CORRECT! Use the inter-grouping
correct! feature when two polygons are on the
same object.

When labeling sky - ONLY label sky pixels in the sky polygons. Don’t include pixels from trees, poles or
other objects in the sky polygon. NEVER include pixels from trees in the sky polygon. Try to make a
tight polygon - but if needed leave sky pixels out of the sky polygon. It’s less important to include every
sky pixel in the sky polygon. It’s very important to be sure there are ONLY sky pixels in the sky polygon.

It’s also OK to not label some small areas of sky - if there are less than 10 pixels on any two vertices
you don’t have to label that patch of sky. If you can’t draw a polygon with more than 10 pixels on a
single vertices without including a tree branch or other non-sky polygon - you don’t need to draw a
polygon!!!

CORRECT INCORRECT

Sky polygon is tight - but does not

include non-sky pixels.

No very small areas of sky are labeled.

Sky polygon includes pixels from trees

and poles.

https://www.remotasks.com/course?id=sky-polygon-intro-training 3/10
3/20/2019 Remotasks

Don’t worry about annotating very small

patches of sky. If the polygon is less than
10 pixels on two sides - you can skip the
patch of sky.

Instructions

In this task, we are labeling the following classes: sky, water, person, vehicle, animal.

In each task, you will see column of 7 sub-images separated by a gray border.
When the same object appears in any of the 7 images - use the same track ID to label the
object.
These sub-images are distorted, so you have to look very carefully to determine if objects are
the same in each sub-image

An example image with labeling for the sky and person classes is shown below. Note, in the actual task, these
7 images would be presented to you one above the other in a vertical strip. You need to label the objects in all
of the images presented :

https://www.remotasks.com/course?id=sky-polygon-intro-training 4/10
3/20/2019 Remotasks

The person is the same person in all images. The person appears clearly in the un-distorted
image at the bottom of the 7 images. The person also appears in other distorted images, but
can be more difficult to see. The person is annotated in red.

Correct labels for this task would use the same task ID for the person in each image.

General rules for all classes

If an object is far enough away that it is difficult to tell what class it is or it is very small and difficult to
label, it is okay to not label it. As a general guideline, objects that are labeled should be at least 15x15
pixels.

For polygons at the edge of an image, the polygon should extend a little ways into the gray border or the
black region of the subimages.
Review of classes to label

Static Object Class

Sky
Sky is defined as any pixel containing a view
of the sky, clouds, etc. and NOT containing
any other object
Sky should be labeled with coarse polygons.
Do not include any non-sky pixels within the
sky polygons.

https://www.remotasks.com/course?id=sky-polygon-intro-training 5/10
3/20/2019 Remotasks

It is okay if some sky pixels at the borders of

objects are missed. It is important to be
conservative here and not label any non-
sky pixels as sky.
DO NOT LABEL areas of sky that are less
than 10 pixels on any side. Leave these
small patches of sky blank.

Water
Lakes, ponds, puddles, etc. - any noticeable
water in the image
Non-water objects (such as rocks) that are
fully within a body of water:
If they are less than 15x15 pixels,
treat them as if they were water
If they are larger than 15x15 pixels,
they deserve their own annotations
and their polygon can be included
within the surrounding water polygon.
If the object’s class does not fit
any of the other specified
classes, please label them as
“Other”. (Note that this is the
only case where an object
should be labeled as “Other”).

Dynamic Object Class

For dynamic object classes below, the following common guidelines apply:

Generally, dynamic object polygons should be at least 20 pixels long or wide; if an object is
very small - for example less than 5 pixels tall or wide at the shortest or narrowest
point of the polygon - it’s ok not to annotate that object.
Polygons should form a tight outline of the object. Wherever possible, this should be pixel
tight. If it’s not possible to make a pixel tight mask - include pixels from other objects in the
polygon for the dynamic object.
Occlusions by thick objects should be split into multiple polygons and grouped into the same
identity.
The same object appearing in different sub-images should be grouped into the same identity.

Person
Any person in the image, including people
who are sitting, lying down, standing or in
motion
Include people of all ages
If the person is in or getting into / out of a
vehicle - annotate the person as tightly as
possible

https://www.remotasks.com/course?id=sky-polygon-intro-training 6/10
3/20/2019 Remotasks

Vehicle
The polygon should contain the entire
vehicle, including windows
Apply an attribute for the vehicle type:
ATV
Car
Truck
Van
Motorcycle
Scooter (Vespa)
Semi truck
Boat
Other

Animal
Annotate any animal visible in the image,
down to animals that are less than 5 pixels
tall or wide at the shortest or narrowest
point of the polygon
Apply an attribute for the animal type:
Dog
Cat
Horse
Other

Common Errors to avoid

NON-SKY PIXELS INCLUDED IN SKY POLYGON

INCORRECT (Below)

INCORRECT - NON-SKY PIXELS INCLUDED IN SKY POLYGON:

Including non-sky pixels in the sky polygon: draw these polygons as tightly as possible.
Always avoid including non-sky pixels in the sky polygon. If necessary include sky pixels in
non-sky polygons to avoid errors.

https://www.remotasks.com/course?id=sky-polygon-intro-training 7/10
3/20/2019 Remotasks

OBJECT IDS WERE SWITCHED ON THE WHITE VAN

INCORRECT (Below)

INCORRECT - OBJECT IDS WERE SWITCHED ON THE WHITE VAN

Track consistent IDs across sub-images: a common error is that objects will have different IDs
across images. It also happens that objects in the same image have the same ID. We must avoid
both situations. Be very careful to give the same object in different images the same ID. The image
below is an INCORRECT example, as the truck has different IDs but should not.

CORRECT VS. INCORRECT HANDLING OF LABELING OBJECT WHEN THAT

OBJECT APPEARS IN MORE THAN ONE OF THE 7 SUB-IMAGES
CORRECT (Below) : The person that is shown in the images below is the same person!
These are just different views of the person taken from the drone camera. Note that there
is only one label/object ID applied to this pedestrian.

https://www.remotasks.com/course?id=sky-polygon-intro-training 8/10
3/20/2019 Remotasks

INCORRECT (Below) : Note how this pedestrian has incorrectly been given two different
labels, which is wrong. Although the pedestrian appears in different images, it is the same
pedestrian and thus should be given one label/ID as shown above.

[text description]

INCORRECT (Below)

INCORRECT - RE-USING THE SAME OBJECT ON TWO DIFFERENT OBJECTS

This image is also INCORRECT, as the same ID is applied to different objects in the same image:

https://www.remotasks.com/course?id=sky-polygon-intro-training 9/10
3/20/2019 Remotasks

INCORRECT (Below)

INCORRECT: NOT EXTENDING SKY POLYGONS TO CAPTURE A FEW PIXELS INTO THE
GREY AREA AT THE EDGE OF THE SCREEN.

Extend polygons to the edge of the image or a few pixels into the grey area at the edge of the
image: THIS ERROR IS EASY TO AVOID AND SHOULD NOT OCCUR! ALWAYS check to be sure
the polygon extends to the edge of the image, which is the grey area.

https://www.remotasks.com/course?id=sky-polygon-intro-training 10/10