If you select "Image Category" as one of the annotation types on the first step, you'll be taken to the page that looks something like the above. Here, you can type in category names, and optionally group them into category groups.
If you select "Bounding Box", "Polyline", "Polygon Segmentation" or "Keypoint" on the first step, you'll see the above page.
The left half of the page is for you to create the list of object classes you want to use. For each annotation, you will need to select what class of annotation it is — be it a person, dog, car or whatever you wish. For each class you add, you must select its annotation type from the drop-down list.
You can also set up the auto-label feature for each object class that you have just created.
To do so, click the “Configure Auto-Label” button (from the label specs set up page). Then, you can select a class to auto-label from the class list (on the left side of the screen) and map it with the auto-label class from the box shown on the right side of the screen. Click the “Save” button to configure the auto-label feature.
The right half of the page is for you to add any additional properties you want to add to each class (sometimes called object attributes). First, select a class from your list on the left-side and then add as many properties for this class as you need.
There are a few types of properties you can choose from: Multiple Choice, Multiple Select, and Free Response.
For multiple choice and multiple select properties, you can add, delete, or edit the name of each option. You can also choose a default option for each property, and decide whether to require a property to be selected / answered in the Annotation App before submitting.
You can also decide to enforce a minimum and a maximum (therefore a range) on how many annotations of each class can exist in a label. When you select a class At the bottom-right of this page, you will
Minimum — The default value is None. It can't be negative or higher than the maximum.
Maximum — The default value is None. It can't be negative or smaller than the minimum.
This option is especially useful for catching human errors when you know for sure how many annotations should exist in a label. For example, a user will not be able to submit a label on the Annotation App if this requirement isn't met.
i.e.) User cannot submit a label on the Annotation App if the count requirement is not satisfied.
When you are done, click next to move on to the next step. Click on the arrow at the top-left the return to the previous step.
Any other questions? E-mail us at firstname.lastname@example.org.