Hi, While thanking you for the photo you took, I will add the mapillary number to the village so that another user does not repeat the same process later. Also, according to the rules, the name on the sign is placed in full in the name tag. The shortened name is recorded in the short_name tag.

Of course, I just checked the history, the first change was not made by you, but by user @nshz. Thank you for your efforts.

Hi; You have changed the name of a street in Ardabil to Yousefi. But the name tag belongs to the name used on the official sign. In this example, the name on the sign is: 18 meters of Ostad Shahriar. If there is an unofficial name, we can add it in the local name or old name tag.

Hello
Our criteria for choosing a name tag is the municipal sign. If you are sure of the old name, you can put it in the old_name tag. If you are not sure or the locals call it differently, use the loc_name tag. For changes, use the documentation again.

Hello, you have changed the city marker to another location. The previous location selection has a historical reason and since ancient times, the zero point of Ardabil was Tazeh Meydan. If you have made this change to display region 5, the city will be displayed in layer 4 and the regions in another layer and will not interfere with each other.

I have searched around that area but have not seen a sign. If you know the location of the sign, please add a mapillary photo of the sign, so that we do not have to make any changes to this village later.

There is a pedestal here with three signs on it indicating which cities this road leads to, and there are no cameras on it. Field survey date on site: 2026.06.06

The correct equivalent for the dirt paths for rescuing trucks with brake problems is the phrase "شیب‌راهه فرار", which is both written on the sign and the correct Persian equivalent.

The name tag should only contain the business name. Operator information, descriptions, and English names belong in separate tags. You can update this entry according to OSM tagging guidelines.
Also, multi-polygon should be used here so that multiple lines do not overlap.

This building has been redrawn incorrectly. You can review OSM guidelines for creating adjacent buildings with a proper structure. Repeating this incorrect structure creates inconsistent data.

The same building geometry issue continues after prior clarification. Adjacent buildings must use shared nodes or correct structure. Further repetition may require review.

Branch naming conflicts with OSM tagging guidelines. Awaiting DWG review.

This building geometry issue has already been explained and corrected previously. Continuing to draw adjacent buildings without shared nodes or proper structure creates inconsistent data. Please review the guidelines before further edits.

The operator tag should reflect the official full name as displayed. Please avoid shortening personal names.

The level tag should only be used on actual building areas. Standalone nodes outside buildings are not valid. Please follow OSM building guidelines. Awaiting DWG review.

The level tag should only be used on actual building areas. Standalone nodes outside buildings are not valid. Please follow OSM building guidelines. Awaiting DWG review.

The level tag should only be used on actual building areas. Standalone nodes outside buildings are not valid. Please follow OSM building guidelines. Awaiting DWG review.

The level tag should only be used on actual building areas. Standalone nodes outside buildings are not valid. Please follow OSM building guidelines. Awaiting DWG review.

The operator tag should reflect the official full name as displayed. Please avoid shortening personal names.

The level tag should only be used on actual building areas. Standalone nodes outside buildings are not valid. Please follow OSM building guidelines. Awaiting DWG review.