Lines

Label

Attributes

Lane Mark

• Single-Dotted
• Single-Dashed
• Single-Solid
• Double-Dotted
• Double-Dashed
• Double-Solid
• Left Dashed Right Solid
• Left Solid Right Dashed
• Inferred
• Occluded

All of these must have:

• Lane Mark Purpose:

• General
• Bicycle Lane
• Hatched Area
• Public Transportation
• No Parking
• Car Parking

• Color

• White
• Yellow
• Red
• Blue
• Other

• Faded

• Yes
• No

• Marked Lane Opening

• Yes
• No

Stop Line

• Single Solid Stop Line
• Single Dashed Stop Line
• Double Solid Stop Line
• Double Dashed Stop Line
• Double Dashed-Solid Stop Line

Road Edge

• Curb
• Guardrail
• Concrete
• Temporary Barrier
• Transition
• Parking Entrance
• Occluded

Unmarked Lane Opening

Railway Track

Polygons

Label

Attributes

Annotable Region

Occlusion Zone

Speed Bump

Pedestrian Crossing

• Pedestrian Crossing Type:

• Zebra Pedestrian Crossing
• Solid Pedestrian Crossing
• Dashed Pedestrian Crossing

Bicycle Crossing

• Solid
• Dashed

Road Surface Marker Arrows

• Arrow Types

• Arrow Left
• Arrow Double Left
• Arrow Merge Left
• Arrow Straight Ahead
• Arrow Merge Right
• Arrow Right
• Arrow Double Right
• Arrow Left and Straight Ahead
• Arrow Left, Straight Ahead and Right
• Arrow Left and Right
• Arrow Straight Ahead and Right
• Arrow Straight Ahead, No Right
• Arrow Straight Ahead, No Left
• Arrow Other

Inspection Polygon

Inner Intersection Area

Outer Intersection Area

Roundabout Center

Roundabout Area

Derived Annotations

• Lane Segment Polygon

• Type

• Vehicle
• Bus or Taxi
• Bicycle

• OSM Type

• Motorway
• Trunk
• Primary
• Secondary
• Tertiary
• Unclassified
• Residential
• Road
• Motorway Link
• Trunk Link
• Primary Link
• Secondary Link
• Tertiary Link

• Merge or Split

1.1 Annotable Region

An Annotatable Region defines the area of the task in which you can make annotations, meaning no annotation should be outside of the Annotable Region.

Some tasks are empty when they’re near the edge of the map. Submit these with NO ANNOTATIONS

Example of Annotatable Region

Example of an empty task on the edge of the Annotatable Region

1.2 OSM Tab

Video on how to use the OSM Tab tool

1. When annotating a task the first step you need to follow is checking the OSM Tool, this tool is located on the left sidebar. You can also access this tool by pressing the shortcut Shift + U.

2. After doing this, a new tab with a map will appear. Wait until the map and roads load completely.

3. If the map on the new tab has no information please submit the task without any labeling. On the other hand if the map has visible roads (with blue lines), please continue with the labeling. The map in the new tab should indicate what roads to label. Also if you click on the roads it will indicate what the Lane Segment Polygon OSM Type should be in that area (see details in the section on Lane Segment Polygons)

Key things to look for on the OSM Tab: Video Explanation

• Once you open up the OSM Tab, look for roads with blue OSM Lines. The lines can be both dashed and solid. You can also click Blue OSM Lines in order to open the attributes menu.

• Bike paths will sometimes appear as smaller blue lines on the map, please ignore these as we do not annotate Bike paths. Another way you can tell that the line should not be annotated is if you try to select the blue line nothing will happen.

• After identifying the road you want to annotate, select the blue OSM line and an attribute menu will appear. The most important attribute that you need to look for is the “highway” attribute, this attribute will give the “Lane Segment Type”.

2.1 Occlusion Zone

Where we can’t see the road we use Occlusion Zones. Here are the Occlusion Types:

• Tree
• Building
• Construction (only where the road / road edge / ego car are affected)
• Overpass

Key things to remember when annotating an Occlusion Zone:

1. Don’t be too detailed with the Occlusion polygons especially around trees. This will make it easier to draw Occluded Road Edge / Occluded Lane Marks
2. We always use best-effort Occluded Road Edge / Occluded Lane Marks over the Occlusion Zones EXCEPT when the overpass is a labeled road. (use OSM tab to see where we label roads)
3. Where we have an overpass that’s labeled we do not label the underpass. Where we have an overpass that’s not labeled then we label the underpass using Occluded Road Edge / Occluded Lane Marks

Smooth Occlusion Zone:

Detailed Occlusion Zone:

Minor occlusions: Do not use Occlusion Zone and annotate as if the occlusion were not there. Minor occlusion example below:

Major Occlusions: Use Occlusion Zone + Lane Mark Occluded / Road Mark Occluded

Example of Occluded Road Edge placed over Occlusion Zone

Example of Lane Segment Polygon placed over an Occlusion Zone

Example of an Occlusion Zone Tree:

Example of an Occlusion Zone Building:

Example of an Occlusion Zone Construction:

Example of an Occlusion Zone Overpass:

Example of an Occlusion Zone Overpass:

Rules

Description

Example

3.1 Lane Mark

To annotate the lane lines:

1. Draw a Lane Mark line through the middle of the painted line, or in the middle of both painted lines.
2. Select the correct property for each Lane Mark:

1. Single-Dotted
2. Single-Dashed
3. Single-Solid
4. Double-Dotted
5. Double-Dashed
6. Double-Solid
7. Left Dashed Right Solid
8. Left Solid Right Dashed
9. Inferred
10. Occluded (Should only be used on top of Occlusion Zones only)

3. Select the correct attributes for the Lane Mark:

1. Lane Mark Purpose:

1. General
2. Bicycle Lane
3. Hatched Area
4. Public Transportation
5. No Parking
6. Parking Car

2. Color:

1. White
2. Yellow
3. Red
4. Blue
5. Other

3. Faded:

1. Yes
2. No

Key aspects of Lane Marks:

• If the road is unidirectional (one way) the direction of the Lane Mark should match the direction of the road.
• If the road is bidirectional or the Lane Mark splits two lanes going different direction then the Lane Mark direction doesn’t matter
• We only annotate the outer edge of the car parking and no parking areas

How to Change Lane Mark Direction: use the “Toggle Line Orientation” option in the attribute menu. Next to the trashcan icon.

Note: Lane marks should extend to the curb or other lane marks. This is particularly relevant in intersections

Bad example:

Good example:

Yellow and White Lane Marks:

Sometimes you will come across tasks in which you will have both yellow and white Lane Marks on top of each other. This happens when there is construction happening in the area, and the yellow lines are placed to represent the new “street”. Use the following rules.

• Annotate both yellow and white Lane Marks
• Use yellow Lane Marks as the edges for Lane Segments, ignore white Lane Marks.
• Add an Inspection Area polygon over the entire area with yellow Lane Marks.

General Example:

• Single-Dotted
• Single-Dashed

• Single-Solid

• Double-Dotted

• Double-Dashed
• 
• Double-Solid
• Left Dashed Right Solid

• Left Solid Right Dashed

• Occluded

Lane Mark Purpose:

• General

• Bicycle Lane

 We do not label Bicycle Lanes when they’re behind a curb or separated from the road. Only Bicycle Lanes that share an edge with the road should be labeled

• Hatched Area (uses zebra-style paint)

• Public Transportation

PENDING

• No Parking (uses tooth-style paint)

• Car Parking when the lane mark is inferred
• Car Parking when the line mark is painted

3.1.1 Marked Lane Opening

We use the attribute Marked Lane Opening where a car can Enter or Exit the Lane Segment Polygon

We DO NOT use Marked Lane Openings over Stop Lines.

Examples:

In the following image a new lane is formed after the curb  widens up. In cases like these, the Lane Mark with the Marked Lane Opening attribute “Yes” should not be longer than the length of two cars (Less than 140 pixels).

3.1.2 Inferred Lane Mark

We use Inferred Lane Marks to:

• Connect Lane Segment Polygon edges when there’s a gap or a sharp edge
• Unpainted car parking edges

We do not use Inferred Lane Marks to:

• Annotate Openings (entrances/exits) in the Lane Segment Polygons. For unmarked openings see Unmarked Lane Openings

We snap Inferred Lane Mark - Car Parking to the road edge when the road approaches an intersection

When we have Inferred Lane Mark - Car Parking we assume the car parking edge continues where there is room to park a car on the edge of the road.

Example of where to use Inferred Lane Mark - Car Parking

Example of where to snap Inferred Lane Mark - Car Parking back to the curb and Inferred Lane Mark - General to smooth a sharp edge

Example of where to snap Inferred Lane Mark - Car Parking back to the curb and Inferred Lane Mark - General to continue a Inferred Lane Mark - Car Parking edge across a Parking Entrance

Example of where to user Inferred Lane Marks where a road T’s with a unidirectional road. In the example below the Lane Segment polygons are numbered:

Other example of where to use Inferred Lane Mark - General

Inferred Lines, special cases:

In the following example, you will see two lanes approaching a couple of crossings. In this case we add an Inferred Lane Mark connecting the two (In the image, the Inferred Lane Mark is represented by the green line).

3.2 Unmarked Lane Opening

We use the Unmarked Lane Opening where a car can Enter or Exit the Lane Segment Polygon and AND there is NO painted lane Mark

At intersections, Unmarked Lane Openings should snap to the edge of the Inner Intersection Area polygon:

3.3 Stop Line

Annotate a Stop Line where a vehicle stops before an intersection or Pedestrian Crossing. Only annotate the Stop Lines that are visible, lines must be drawn through the middle of the painted line.

1. Select the correct type of  Stop Line:

1. Single Solid Stop Line
2. Single Dashed Stop Line
3. Double Solid Stop Line
4. Double Dashed Stop Line
5. Double Dashed-Solid Stop Line

2.  Faded:

1. Yes
2. No

Do not annotate Pedestrian Crossing lines or Bicycle Crossing  as Stop Lines

When there is a small gap between the end of the stop line and the road edge, we snap the stop line annotation to the road edge:

Stop Line Examples

3.4 Road Edge

Road Edge is one of the most important attributes, it should be annotated continuously and with no gaps.

1. Draw a line through all the edges of the road and select the correct label:

• Curb
• Concrete Barrier (or wall)
• Guardrail
• Temporary Barrier
• Transition
• Parking Entrance

2. Select the correct attribute for the Road Edge:

1. Side of Road

1. Left
2. Right

Side of road is relative to the direction of the line segment

We use Side of Road = Right when the road edge is on the right hand side of the road (this is the case most of the time).

We use Side of Road = left When the road edge is on the left hand side of the road

Key aspects / common mistakes for annotation Road Edges

• If there are two road edges (e.g., curb and guardrail) then annotate both
• When working on rounded curbs pay close attention and try to be as precise as possible.
• Taskers often miss car parking edges

How to Change Lane Mark Direction: use the “Toggle Line Orientation” option in the attribute menu. Next to the trashcan icon.

NOTE: Every time a road changes attributes such as level or type, a new line must be created.

Curb

Guardrail:

Concrete Barrier:

Temporary Barrier (chain link fences, cones, plastic construction barriers):

Transition:

Parking Entrance:

Occluded:

3.4.1 Parking Entrance

We use Road Edge - Parking Entrance when we have a driveway or entrance to a parking lot.

These are commonly missed by taskers, make sure you

Examples:

3.5 Railway track

Annotate a Railway Track, through the middle of all the railways found in the task. To do this:

1. Draw a line that goes on top of  any  Railway Tracks.

Railway Track annotations can not be used to form Lane Segment Polygons

Place railway tracks on top of trains to continue the line annotation. Do not treat trains as a Occlusion Zone

Examples:

Rules

Description

Example

4.1 Road Surface Markers Arrows

To annotate each Road Surface Marker:

1. Draw a single rectangular polygon that covers the entire road surface marker. In order to do this you have to keep SHIFT pressed while doing the polygon.

[instructions on how to rotate]

2. Select the Arrow Type:

• Arrow Left
• Arrow Double Left
• Arrow Merge Left
• Arrow Straight Ahead
• Arrow Merge Right
• Arrow Right
• Arrow Double Right
• Arrow Left and Straight Ahead
• Arrow Left, Straight Ahead and Right
• Arrow Left and Right
• Arrow Straight Ahead and Right
• Arrow Straight Ahead, No Right
• Arrow Straight Ahead, No Left
• Arrow No Right
• Arrow No Left
• Arrow Other

3. Orientation for arrows is set to the direction of travel

NOTE: All RSM must have a heading direction. The direction of the heading is indicated with a white line and can be changed in the attributes, even though the heading is correct you have to modify it a little bit for it to be correct. This heading direction should be pointing to the direction the road goes.

Example:

NOTE:

4.2 Speed Bump

When annotating a Speed Bump, draw a 4 point polygon, the polygon must be covering the entire area of the bump.

1. Draw the Speed Bump polygon, fitting the shape of the polygon as close as possible.

Examples:

4.3 Pedestrian Crossing

A Pedestrian Crossing is a region where pedestrians are expected to be able to cross the road. To annotate a Pedestrian Crossing polygon you must:

1. Draw a 4 point polygon that covers the entire Pedestrian Crossing. (unless it’s on the edge of the Annotatable Region, then you can use more than 4 points)
2. Select the Type of Pedestrian Crossing:

1. Zebra Pedestrian Crossing
2. Solid Pedestrian Crossing
3. Dashed Pedestrian Crossing

Key things to remember when annotating Pedestrian Crossings:

• Do not label unpainted crossings
• You can differentiate Pedestrian Crossings from bike crossings by looking for bike lanes, when bike lanes are connected to bike crossings.

Example:

Example of unpainted crosswalk NOT to label:

Example of Pedestrian Crossing vs. Bicycle Crossing:

4.4 Bicycle Crossing

To annotate a Bicycle Crossing, you have to:

1. Draw a single 4 point polygon that covers all the area where the Bicycle Crossing  is perpendicular to the road. Typically this happens in and around intersections.

Key things to remember when annotating Bicycle Crossings:

• Do not label unpainted crossings
• You can differentiate Pedestrian Crossings from bike crossings by looking for bike lanes. Bike lanes are connected to bike crossings.

Example:

Example of how to identify Bicycle Crossing using the connected Bicycle Lanes

Example of marked Bicycle Crossings in a large intersection. In the example below the Bicycle Crossings (Green Polygon) are all 4 point polygons that cover the road edge and full area of the Bike Crossing. Also the Bicycle Crossing shapes are unrelated to the Inner Intersection Area polygon (Black outline)

4.5 Inner Intersection Area

Draw an Inner Intersection Area when you find a collision of driveable paths (not a merge or split, but a collision). This often happens when two or more roads intersect.

 To annotate an Inner Intersection Area:

1. Find the point on each road edge of the intersection that is closest to the center of the intersection
2. Manually draw the outline of the Inner Intersection Area following the curbs. When drawing the Inner Intersection Area over roads the edge of the intersection polygon should be perpendicular to the road and starting at the corner and divider points

Note: Intersection Polygons are not derived polygons

Key aspects of intersection polygons:

• We only draw an Inner Intersection Area where there is a collision of the Driveable Paths (See below for examples)
• Where possible we snap the edges of the Inner Intersection Area to the Road Edges and Marked/Unmarked Lane Openings

Use Inner Intersection Area Polygons where there is a driveable path collision

Standard driveable path collision:

Unprotected Left - driveable path collision

Do not use Inner Intersection Area Polygons where there is a driveable path that converges (but doesn’t collide)

Step 1: find the point on each road edge of the intersection that is closest to the center of the intersection

Step 2: Where the intersection crosses lanes, draw lines from these curb points perpendicular to the driving direction. Otherwise follow the road edge

Examples

Example of drawing Inner Intersection Area polygons when there is an unprotected left hand turn:

Other intersection polygon examples:

Good Example (ignore the numbers):

When annotating an Inner Intersection Area Polygon, be careful to not include areas that are not part of the intersection:

4.6 Outer Intersection Area

Draw an Outer Intersection Area after the  Inner Intersection Area Polygons.

Outer Intersection Polygons must follow a specific hierarchy and each lane can be labeled differently.

Look at the Intersection hierarchy diagram

Stop Lines are the highest in the hierarchy

Here is an example.

If there is no Stop Line then next is there a Pedestrian / Bicycle Crosswalk present? Label starts at the furthest crossing from the intersection.

Here is an example.

If there is no Stop Line then we default to when the road starts to widen.

Here is an example.

Examples of completed Outer Intersection Polygons

4.7 Roundabout Center

Annotate a Roundabout Center polygon when we have a roundabout in the task. To do this follow the next steps:

1. Draw a polygon around the center of the Roundabout.

Example:

4.8 Roundabout Area

When annotating around a Roundabout Area, you must annotate the area around it following the next steps:

1. Draw a Roundabout Area (including the Roundabout Center)
2. The roundabout area should end where the Lane Segment Polygons outside of the roundabout begin. This should happen at the corners of the roundabout

We do not draw lane segment polygons in the roundabout Area, but we do annotate line annotations and other polygons

Example:

4.9 Inspection Polygon

Draw an Inspection Polygon, whenever you find yourself with a very unusual Road Area you do not know how to annotate.

Still annotate the image to the best of your ability, but please place the Inspection Polygon over the unusual road area.

Examples of where to place Inspection Polygons:

• Heavily occluded roads
• Narrow Roads
• Faded Roads

Examples:

Heavily Occluded Roads:

Inspection Polygon on narrow road:

Unclear if there is a painted line on the road

Rules

Description

Example

5.1 General Info: Primitives

Primitives are all the line annotations that we placed manually on the task.

• Road Edges
• Lane Lines
• Unmaked Lane Openings
• Stop Lines

Primitives are used to create Derived Polygon Annotations.

 5.2 General Info: Derived Annotations

Derived Annotations are polygons that we create using Primitive annotations and the Derived Annotation Builder Tool.

In order to properly generate a Derived Annotation, we need to select the Primitive annotations surrounding the area that you want a Derived Annotations polygon.

Note: NEVER manually draw the derived polygon annotations.

It is super simple to identify polygons that were manually drawn versus polygons that were created using the Derived Annotation Builder. Select a polygon and look at the vertices, if it was created using the Derived Annotation Builder a ribbon symbol will appear. If it is manually drawn, then the vertices appear normal.

Example of a Derived Polygon:

Example of a Manually Drawn Polygon:

5.3 General Info: Derived Annotation Builder

The Derived Annotation Builder is the tool that we use to generate Derived Annotations (polygons).

You can locate it on the left sidebar, it is the hammer button.

You can also enable/disable the Derived Annotation Builder using the shortcut “Shift + D”.

You will notice the DAB menu open up below the annotation list.

Once the DAB tool is enabled, select the primitives surrounding the area you want to place a polygon. Hold down the “Shift” key while selecting the primitives in order to select multiple annotations (if you DO NOT hold down shift the DAB tool won’t work).

There is no need to select the Annotatable Region, the tool automatically takes it into account.

After selecting the annotations, click the “Show Preview” option. This will automatically generate a possible polygon.

Make sure that the polygon has the correct shape you want and then click the “Generate Drivable Region Zone” (the blue button)

If a polygon doesn’t show after selecting the “Show Preview” option, it is most likely that there is a gap between annotations. To correct this error, make sure that all the annotations are properly snapped to each other.

5.4 Lane Segment Polygons

Lane Segments are polygons composed of Lane Marks, Road Edges, Stop Lines, Unmarked Lane Openings and the Annotatable Region as edges

Lane Segment Polygons should always have at least two Stop Lines or Unmarked/Marked Lane Openings. (where you can enter/exit the lane). The EXCEPTION to this rule is when the Lane intersects with the Annotatable Region

Lane Segment Polygons should start / end when a road:

• Meets an Inner Intersection Area polygon
• The road loses middle paint and becomes bi-directional
• Gains/loses a new lane
• The road T’s
• Stop Lines
• OSM type changes
• Cul-de-sacs
• Roundabouts
• Dead ends

Key Aspects of Lane Segment Polygons

• Always use a Derived annotation (select edges + shift D)
• Lane Segment Polygons should NOT overlap with each other.
• Lane Segment Polygon should NOT be placed inside Inner Intersection Polygons.
• Lane Segment Polygons should extend to the edge of another Lane Polygon or Intersection Polygon
• It is okay to have Lane Segments overlap with Outer Intersection Polygons. DO NOT segment Lane Segments when they reach the Outer Intersection Polygon.

Example of Lane Segment Polygons approaching intersection.

• the Lane Segment Polygon Split (red polygon) starts where the road begins to widen and ends where the new middle lane mark starts
• We do not use a Lane Segment Polygon Split when a right turn lane starts on the other side of a Bike Lane
• Lanes start/stop at stop lines
• Lanes continue to the edge of the Inner Intersection Area

Example of Lane Segments between stop lines and inner intersection area polygons:

Example of Lane Segment Polygons where we have an unmarked intersection. Lane Segment Polygons end where the inner intersection polygons begin :

In the following image, look how the Lane Segment (highlighted in cyan) is not affected at all by the Outer Intersection Polygon. Remember that we never use Outer Intersection Polygons to cut Lane Segments.

5.5 Lane Segment Polygon Type

After annotating the Lane Segment Polygons, you must select the correct attributes for this one. To do this follow the next steps:

1. Identify the type of Lane Segment Polygon it corresponds to:

1. Vehicle
2. Bus or Taxi

We do not draw Lane Segment Polygons in the following areas:

• Inner Intersection Areas
• Roundabout Areas
• Parking Areas (side of the road, and in parking lots)

5.6 Merge/Split Lane Segment Polygon

Merge/Split Polygons:

We only use a Merge/Split polygon when lane separators are unmarked and the split is roughly symmetrical. We do not use split polygons when there is a clear “main successor” or “main predecessor”  in a driveable path split or merge.

See the image to the right for more details

A road is merging if two lanes are consolidating into one and the edge of the lane narrows

A road is splitting if one lane become two and the road widens

Split/Merge Polygon definition:

Example of Lane Segment Polygon Merge:

Lane segment #5 here has attribute of merge

Examples of a Split Polygons:

Example of when not to use a Lane Segment Polygon Merge. We do not use a Merge  here because each lane continues on its own. The lanes get closer together, but they don’t actually merge:

Example of when not to use a Lane Segment Polygon Merge. We do not use a Merge  here because each lane continues on its own. The lanes get closer together, but they don’t actually merge:

Example of when not to use a Lane Segment Polygon Split. We do not use a Split here because we get a new lane segment. The existing lane segment doesn’t split, it just moved to the right:

Example of Lane Segment Polygon that is NOT Merge & Split. We use a regular Lane Segment polygon here because there is a clear successor to the continuing road and the lane separator does not split an existing lane segment.

5.7 Bicycle Lane Segment Polygon

We annotate Bicycle Lane Segment polygons wherever shares an edge with the road

Here are some key things to remember about Bicycle Lane Segments:

• Bicycle Lane Segments are derived annotations
• Bicycle Lane Segments may overlap other annotations (including inner and outer intersection areas and vehicle lane segments)
• Bicycle Lane Segments overlap marked Bicycle Crossings when they cross lanes
• Bicycle Lanes are sometimes inferred since the painted bicycle lane marks are not always continuous. Here we use context clues

Inferred Bicycle Lane context clues:

5.8 Lane Segment Polygon OSM Type

Video on how to use the OSM Tab tool

In order to use the OSM tool:

1. Open the tab by clicking on the OSM tool or by pressing (Shift + U).
2. Click on the road you are located.
3. Check the attributes of the road.
4. Select the correct type of road as an attribute:

1. Motorway
2. Trunk
3. Primary
4. Secondary
5. Tertiary
6. Unclassified
7. Residential
8. Road
9. Motorway Link
10. Trunk Link
11. Primary Link
12. Secondary Link
13. Tertiary Link

Step 1.

Step 2.

Step 3.

Step 4.

Rules

Description

Example

6.1 General Info: Existing Annotations

Existing Annotations are all the annotations that we previously placed manually on the task. You can find these annotations outside of the Annotable Region. Some examples of this ones are:

• Road Edges
• Lane Lines
• Unmarked Road Opening
• Stop Lines

Some annotations will be locked and cannot be modified. When you need to remove an annotation (e.g., a Segmenter, incomplete Intersection Region) that’s locked then use a Delete Line or Delete Polygon

Be careful about how you use Delete Lines since it might accidentally delete a Lane Segment outside of the Task.

The annotations outside of the AR can’t be modified or deleted.

Example on how annotations look outside of the AR:

6.2 Matching Annotations

When your task has existing annotations outside of the Annotable Region, you must add and  connect your new annotations inside AR with the annotations outside AR, making them match perfectly.

Note: DO NOT place Unmarked Openings directly on the edge of the AR.

Example of annotations having the same type and attributes:

6.3 Linking Polygons

When there are existing Lane Segment, Merge/Split Lane polygons or Bicycle Lane outside of the Annotable Region, and these ones are divided by the AR  this must be linked with the continuation  of  the Lane Segment Polygon created inside of the AR.

To do this you must follow the next steps:

1. Select the Lane Segment Polygon that is located outside of the AR.
2. Press Shift + A
3. Click on the continuation of the Lane Segment Polygon previously selected.

NOTE: Linking is only done on Derived Polygons (Lane Segment)  no linking has to be done on manual polygons.

Example of Lane Segment Polygon Linking:

Rules

Description

Example

Review the Task

Do a full review of the task for incorrect or missing annotations.

Attach inline comments to annotations with errors.

Draw spotter polygons around areas of missing annotations and attach an inline comment to it

You can also draw spotter polygons around areas with existing annotations with errors if you think it will be faster than attaching individual comments to each annotation.

Spotter Polygons

Spotter polygons are polygons you will draw around areas with missing annotation(s) or around areas with existing annotation errors if you think it'll be faster than leaving multiple comments.

Every spotter polygon must have an inline comment attached to it.

Inline Comments

Right-click on an annotation and select inline comment to leave an attached inline comment.

Make sure your comment has the appropriate error category selected and a description of the error detailed enough so the error can be corrected in the next stage of the project.

Cases

How to Handle It

Example

Road T’s with a continuing Unidirectional Road

We don’t use an intersection polygon since there’s no driveable path collision

The unidirectional road should extend

Also, we extend the unidirectional road to where the curb stops widening or the curb meets the edge of the next lane segment

We always end the approaching lane segment (polygon 1) at the edge of the continuing lane segment (polygon 4). We place the Unmarked Lane Opening across the continuing road where the road stops widening

Road T’s with a continuing bidirectional road or a road where you can take an unprotected left

In these cases we use an Inner Intersection Area polygon because there is a driveable path collision (due to the unprotected left)

We extend the lane segment polygon to the edge of the intersection polygon.

We place Unmarked Lane Openings on the edges of the Inner Intersection Area where lanes are approaching/exiting

Where we have car parking edges, we snap them back to the curb when they approach the intersection since cars normally can’t park around the curved curb on intersections

But sometimes cars can park on the curved curb of the intersection

Intersections with stop lines & crosswalks

When we have intersections with stop lines 

For approaching lanes:

we use inferred lane marks to continue the approaching lane segment polygons to the edge of the Inner Intersection Area after stop lines

For exiting lanes:

We start the lanes at the edge of the inner intersection polygon

Outer Intersection Areas will overlap with Lane Segments as they approach the Inner Intersection Area

Gain a turn lane when approaching intersection

When we gain a turn lane approaching an intersection we often will use a new lane segment polygon

Lane shapes when approaching an intersection

Corner ares of lanes when approaching intersections should be included in the lane segment on the edge

How do we differentiate between bicycle crossing and pedestrian crossing?

Bike crossings (green in the example below) are narrower and connected to bike lanes

Pedestrian crossings (blue in the example below) are larger and not connected to bike lanes

How to annotate two intersections together?

When you have two intersections together, analyze the distance between both of them to see if it could be replaced for one big intersection; if not, separate the intersection into two.

Example of separating intersections:

Example of using one big intersection:

Emerging Lanes inside roads

There are going to be instances, in which a Lane Line will appear at the edge of the road/lane and will move towards the center of the lane. At the end creating two lanes inside the road.

In these cases, we DO NOT apply a Merge/Split Lane, we make two normal lanes.

Example of Correct Lane Segment placement:

Example of incorrect Lane Segment placement:

What happens if a Bidirectional Road becomes an Unidirectional Road ?  

If (1) Lane Lines suddenly appear on a  Bidirectional Road (normally Bidirectional Roads do not have any lane lines/markings in the middle), creating two Unidirectional Roads AND (2) the road narrows then

We should create a small Merge/Split polygon between the Unidirectional and Bidirectional Roads.

Good Example:

• Use a split polygon since the road narrows and we switch from one lane to two lanes
• If the road did not narrow then we would not use a merge/split polygon here

Bad Example:

• Here the road doesn’t narrow so we don’t use a merge/split polygon

Good Example:

• Here the road doesn’t narrow so we don’t use a merge/split polygon

No annotation required in the task

If your task Annotable Region, requires no annotation then you should submit it just as it is.

Check the OSM Tab to confirm that there’s no roads to label on the task.

Example:

Edge Cases

How to handle

Loop Lane

When annotating Loop Lanes, you must draw 4 separate Lane Segments instead of drawing one big one that goes around all the area.

Wrong way to annotate Loop Lanes:

Correct way to annotate Loop Lanes:

Power lines

On  some tasks we can find visible markings that can seem to be Lane MArks, you should be extra careful with this since they are not Lane Marks, but they are Power Lines which shouldn't be annotated.

In the image below we should ignore the very faint white lines because they’re power lines

Error

Example

N/A

N/A

Labels/Attributes

Description

Example

Label 1

Label 1 description

Insert image here

Attribute 1

Attribute 1 description

Insert image here