In this tutorial, you will learn how to run offline data collection in Toloka. We will use a project preset designed specifically for this type of data labeling.
Offline data collection is intended for field tasks in the Toloka mobile app. A Toloker selects a point on the map, goes to the location, takes photos, and writes a comment.
You may need additional projects for your task, such as dataset pre-check or checking Tolokers' responses. Learn more about this in Decomposition of the task.
Before you begin:
Make sure you are registered in Toloka as a requester.
Top up your Toloka account. If you are unsure about the budget, you can do that later in this tutorial. Toloka will display the budget estimate for your project.
We recommend starting with a project preset for easier configuration and better results.
Follow this link, or create a project manually:
Click Create a project.
Click Do it myself.
Select the Spatial Crowdsourcing preset.
Click Choose this preset in the pop-up tab.
In the General information section, add the project name and description:
Name to show Tolokers: In 2–5 words, state the general idea of the project.
Description for Tolokers: In a couple of sentences, explain what you expect Tolokers to do. This is just an overview. You will write instructions later.
In the Task interface section, set up what your tasks will look like.
This tutorial uses Template Builder, but you can use the HTML/JS/CSS editor for the same purpose.
Copy the code of the example and paste it to the Config section of your project. This code has validation and task layout pre-configured.
You can edit the code. For example, to configure the text above the Take photo section, replace the sample text with your value in the
The Toloker will be able to submit the response when they are within 50 meters of the specified location. To change this condition, replace the value of the
max property with the desired distance:
To learn about other properties of the Config section, their possible values and the impact on the task interface, see the Template Builder Help.
Raw task data is stored in the XSLX, TSV, or JSON format. The labeling results are presented in a TSV file. The Data specification section determines which parameters these files might contain.
Click Show specifications and check the values:
Input data: Parameters in the file with raw task data.
Output data: Parameters in the file with labeling results.
Input data and Output data match the task interface you set up in Template Builder. Check that there are fields for all data types you use for your tasks, and for the ones you want to see in the results file.
In the Settings for displaying field tasks section, configure the settings which affect the task display on the map.
The Title format and Short description format are used to help a Toloker distinguish one task from another when they select a task on the map. These fields contain links to the input data fields to show the name of the point and its coordinates. You can leave these fields unchanged.
The Map provider for tasks field sets which map a Toloker will use when performing your tasks.
In the Instructions for Tolokers editor, enter the instructions Tolokers will see when they start doing your tasks. You can add text, tables, and images to your instructions.
Check the sample text of the instructions, and update it to fit your project.
Field task instructions should be easy to read on a mobile phone screen.
When writing instructions, remember that most Tolokers don’t know anything about your tasks beforehand. Make sure your instructions are as clear as possible, but not too wordy. For successful data labeling, try to strike a balance between covering all the essentials and keeping it short. Learn more in our knowledge base.
In the upper-right corner, click Save.
Learn more about working with the project in the Project section.
A pool is a set of tasks sent out to Tolokers at the same time. One project can have many pools. When creating a pool, you set up pricing, audience filters for Tolokers, and quality control.
Click Add a pool on the project page.
Select the value in the Pool type drop-down list.
If the price per task suite is zero, you must select the pool type.
Set the Pool name (visible only to you) field. Only you will see this pool name on the project page.
Specify the pool description which will be displayed instead of the project description in the task list for Tolokers. By default, Tolokers see the description from the project settings. To use a different description, uncheck the Use project description box and set Public description. If necessary, click + Private comment to add a private project description that only you will see.
At the Select the audience for your task step, set up filters to select Tolokers for your pool.
Clear My tasks may contain shocking or pornographic content if your project has none of those.
To select Tolokers based on their language, location, age, gender, and other parameters, click the Add filter button.
Tasks in pools are available in the web version of Toloka and the mobile app by default. Make your tasks available in the mobile app only: add the Client filter and select the Toloka for mobile option.
Use the Speed/quality balance slider to change the number of Tolokers who can see your tasks. Move the slider to the right to exclude Tolokers with lower ratings from participating in your project.
At the Setup quality control step, set quality control rules for more accurate results:
Click the Review task responses manually toggle, and specify the number of days for checking the task in the Review period in days field (for example, 21).
Click Add a quality control rule → Results of manual review, and enter the following values:
This means that if 35% or more of a Toloker's responses are rejected, the Toloker is banned and can't access your tasks for 15 days. The rule takes effect after 3 responses of the Toloker are reviewed.
Add the Processing rejected and accepted assignments rule. When the overlap value is 1, you should resend assignments to the pool for other Tolokers to redo them.
This means that if you reject assignments during the review, they’ll be sent for re-completion to another Toloker.
At the Add optional pool settings step, specify the Time per task suite, sec.
It should be long enough to get to the place, find the specified point and upload the photos. For field tasks, this time is usually 86,400 seconds (24 hours).
At the Set the task price and overlap step, set up how much a single task will cost for you.
In Price per task suite, set the amount of money to pay per task suite done by one Toloker. A task suite is a page with a number of tasks.
For this type of project, a task suite must contain only one task. You will set the number of tasks per suite later in this tutorial.
In the Overlap field, define how many Tolokers must do each task.
For field tasks, it is usually 1. This means that each task will have 1 response.
At the Prepare and upload data step, upload your task data.
Create the tasks for Tolokers:
To download a template, click one of the buttons:
Template in XLSX
Template in TSV
Template in JSON
For this type of project, the file with tasks must four parameters:
INPUT:name: A string with the name of the object.
INPUT:position: The coordinates of the place where the Toloker should go.
AI:longitude: The latitude and longitude from the
INPUT:position parameter presented separately. The values of
AI:longitude should have the same accuracy, that is have the same number of digits after the decimal separator.
INPUT:name INPUT:position AI:latitude AI:longitudeName 1 53.947516,27.669428 53.947516 27.669428Name 2 53.947517,27.669429 53.947517 27.669429Name 3 53.947518,27.669428 53.947518 27.669428
Open the downloaded file, and replace the sample values with your data. You can use a service like Google Maps to get the coordinates.
Click Drop file here or select, and upload the file you’ve just made.
Tasks are shown to Tolokers in suites. A suite is a single page with multiple tasks. Define how many tasks to include per suite:
Go to the Set manually tab.
In this type of project, the task suite must contain only one task:
Click Combine tasks into suites.
At the Double-check your project and try out tasks step, check how the task will look from the Toloker's point of view.
This step will be enabled after you complete the previous steps. You can skip this step by clicking Do it later.
After all the steps, you'll see the Set up is finished and your pool is ready for labeling tip on the pool page.
Make sure you have topped up your account.
To send the tasks to Tolokers and begin the labeling process, click Start labeling.
In the pop-up panel, review the budget and click Launch.
Track the labeling progress on the pool page. You can start the review when the first results are received.
After the specified time period, all responses are automatically accepted, regardless of their quality.
Go to the pool, and click Review assignments.
Choose an assignment.
Check the responses, and click Accept or Decline. For rejected responses, enter a comment to specify the reason.
To learn about other ways of review, see the Reviewing Tolokers' responses section.
After checking all the assignments, click Download results.
You will get the TSV file with the labeling results.
To download the files Tolokers attached to the tasks, go to the pool page and click the arrow next to the Download results button. Choose Download attachments from the drop-down menu.