In addition to errors, you may also see error hypotheses (theories based on data analysis about why certain errors are made). For example, a user may conclude that a speed limit was entered incorrectly because it appears incorrectly in dashboard images.

To fix an error and/or respond to an error hypothesis:

Click Layers.

In the menu that appears, click Show error messages on the map (Error hypotheses):

Select the type of error that you want to fix (some error types are not accessible to certain users):

All error types

Placemark in wrong position

I know a better route (these errors only relate to walking routes)

Item not on map

Incorrect walking route (these errors only relate to walking routes)

Delete the map item from the map (only moderators can access these errors)

Incorrect route time (these errors only relate to walking routes)

Incorrect name

Wrong speed limit

Other

Placemarks containing error messages and hypotheses will display on the map. When you hold your cursor over the placemark with the error, you'll see a tip containing the error type:

If the error was registered more than 24 hours ago and has not been corrected, the placemark will be a red or orange circle with an exclamation point inside.

Placemarks located close to each other are grouped together and the circle shows how many there are. To ungroup the placemarks, increase the map scale.

Note.

If the error has been processed (see below), the placemark will change to a green circle with a check mark.

Click on a placemark. An error-processing card opens and the message will be selected on the map. If you select an error hypothesis, the hypothesis card will open:

The errors card indicates:

The error name.

The message text and creation date.

A What user drew link (for errors that involve places or routes).

The link leads to the area on Yandex.Maps that contains the places and routes that the user drew. If the error concerns an incorrectly set route, then the route builder's suggestion will appear as a blue dotted line, and the route that the user suggested will appear as a gray line.

If you look at the map and can't tell what actions are required to fix the error, then don't try to fix it.

A What user saw link (for errors that involve places or routes).

The link leads to the area of Yandex.Maps that the user saw when they reported the error. If that area doesn't correspond to the YME area where the error displays, it means that the error was incorrectly linked.

If you look at the map and can't tell what actions are required to fix the error, then don't try to fix it.

An Add comments link. Click it to add an error comment.

An Accept button. Click it if you decided to make a correction.

After you click this button, the error will be assigned to you: it will no longer be visible to other users and all further edits will be recorded in the error history.

If you decided not to make corrections, close the card by clicking Decline (or Close).

The error hypotheses cards contain the following:

Hypothesis name.

Accept and Decline buttons (similar to in the error card)

Date hypothesis was created.

Context — a link to material that supports the user's hypothesis (for example, in cases where a user suspects that the speed limit is incorrect, the link will lead to corresponding dashboard images).

If the hypothesis is based on map data, then the card will not contain a link.

Map item — a link to the map item (road) that the error hypothesis is linked to.

If you click Accept, the error card will look like this:

A Back to error button will display next to the Create button: it you click it, you'll return to the error (even if you already closed the error card).

Note.

The edit counter will appear on the button as you work on the task:

If the counter displays an incorrectly high number of edits (as shown in the drawing), then something probably went wrong.

Every error-processing card has its own counter. The counter value will not reset, even if you reject a task and then return to it later.

The error-processing card includes these buttons:

Edits unnecessary ─ click this button if the information in the message has already appeared on the map (for example, if an error was corrected in the process of correcting a related issue, or the edit was unnecessary).

Reject ─ click this button if the information in the message is incorrect.

For example, the information might be wrong, incoherent, not relate to items on Yandex Map Editor, contain links to unidentifiable map items, etc.

You should only reject user requests that are clearly incorrect or intentionally misleading.

Sometimes messages contain useful information that the user just couldn't phrase correctly, or they linked to the wrong item. In these cases, try to clarify the information by using additional sources.

For example, if the user reported that a “section of Lenin Ave. is closed for repairs” in the field for the Vladimir region, it's worth checking if Lenin Ave. in Vladimir is indeed closed for repairs.

If you clicked Reject, the card will look like this:

Refuse ─ click this button if you don't know how to correct an error or you are not sure if the information in the message is valid.

In this case, the error will become visible again and available to other users; another moderator can correct the error.

When you click Accept, you will enter error correction mode where you can fix the mistake. In error correction mode you can't accept a different error to work on (if you try to do this, you'll see the message “You have already accepted a different task”).

When you've accepted an error, the error-processing card closes, but the Back to error button will remain visible and the edits you make will appear on the counter that is connected to it.

When you've made all the necessary edits, click Back to error.

An error card opens with information about how many edits were made for that particular error, and who made them:

If you've finished correcting the error, click Corrected.

The card and icon will look like this:

When you've finished working on an error, click Close (or press Esc).

If the error requires additional edits, click Reopen.

Examples of corrections

If the message states that a building was demolished, check this information. If you can confirm it, select one of these edit options:

If the building is visible on the satellite image (meaning the image is outdated), set Demolished as the value of the Condition attribute.

If the building is not on the image (i.e. the image is current), delete the item from the map.

If the message claims that road construction/sinkholes/lanes repairs, etc. are present, check this information. If you can confirm it, select one of these edit options:

If there are long-term non-seasonal road repairs (lasting more than three months), disable vehicle accessibility for all types of vehicles for the sections where there is road construction (see 3.3.2.3. Accessible for),assign them the “under construction” flag (see 3.3.2.11. Under construction) and downgrade the class to “Minimal significance road” (See Cl. 3.3.2.1.7).

If a road is temporarily closed (for less than three months), a planned re-paving is underway, or if there are potholes, river flooding or similar situations that make it difficult or impossible to traverse certain sections of road, then don't correct the error (a Yandex employee will address it).

If the message states that a street or address doesn't exist on the map, check this information. Make sure that the item is not included among the current data and enter it on the map.

If the message concerns a walking route:

In this case, you should generally draw the missing paths, rather than deleting existing ones.

You should not draw unofficial trails formed by people trampling down grass, making holes in fences, or other means that break the rules.

If all the roads necessary for building a route have already been plotted on the map, but a user is claiming that the route was incorrectly set, then make sure that all roads on that route are accessible to pedestrians.

Routes set by the route builder may not match routes suggested by users.

For example, a route that a user suggests that goes through a park may be longer than the one set by the route builder. We can finish drawing the park trails, but the route will be set in accordance with the shortest trajectory as previously.