Hi and welcome!

You don't have to add names to everything. Paths usually don't have names. Mostly, we try to keep things more or less in sync with Maa-amet (land board) and road registry in Estonia.

With exceptions when there are signs on the ground which specify the name of a path or a forest path having a distinct name from being a known trail for training or being advertised with such name. I guess Peedu kergliiklustee along the tracks nearby is one of such cases.

Consider removing Tuletõrje and Oja names from paths.

Yes, you can remove them

Hi, you can check address history in Maa-amet
https://xgis.maaamet.ee/adsavalik/ads?ads_oid=ME03789343

it does show that previously it had a lot of addresses

Harju maakond, Tallinn, Lasnamäe linnaosa, Kesk-Sõjamäe tn 10a // Lennujaama tee 4 // 6 // 10 // 11 // 12 // 14 // Tartu mnt 101 // 103 // Väike-Sõjamäe tn 1a // 2 // 12 // 12a

but now it's just
Harju maakond, Tallinn, Lasnamäe linnaosa, Väike-Sõjamäe tn 22b

Hi, it makes little sense to have these two
way/1256031933
relation/11737303
as separate features.

Hi, when using conditional tags, you should specify the default value too, so that the data consumers would know what it is when the condition does not apply.

In this case
access=no
access:conditional=yes @ (May-Sep)

you may also want to reverse this condition so that data consumers who don't know about conditional suffixes would parse just access=yes.

Hi,
1) highway links should be of the highest type of highway. So a link of a residential road with a highway=secondary will always be highway=secondary_link
2) there is no such thing as a highway=residential_link in OSM

osm.org/edit#map=20/59.36898/24.64031
bicycle=yes on the way and bicycle=dismount on cycle barriers contradict each other.

If cycling is forbidden, then it's not only at barriers. If it's just hard, but not forbidden, then barrier by itself is enough, not need for access tags on it.

Hi and welcome, you probably wanted to use ditches instead of canals

There is no need to add all those access tags to footways. They allow only pedestrians by default. I'll remove them so that they don't confuse osm standard renderer

Hi, it's better to tag dirt roads as paths. Some data consumers don't read the surface tag. It also allows bicycle routing on these paths.

I'm really surprised you do this in iD. JOSM has some plugins to display lanes in the editor and also edit them not as a text.

There are actually 11 spaces, fixed it.

Hi,
if the place is closed forever either delete it or add a lifecycle prefix
osm.wiki/Lifecycle_prefix
for example:
was:shop=cannabis
was:amenity=restaurant

Hi, it's better to use highway=path or highway=cycleway when it's bicycle=designated (then need foot=designated too).

footways are usually for pedestrians only

I've added bicycle=yes to crossings

Hi, was there a street sign on the ground or how did you determine this road name?

Hi, consider not mapping private backyards (sauna, trampoline)
osm.wiki/Limitations_on_mapping_private_information

I also see "Distance in property description is calculated using © OpenStreetMap", but the key word here is "distance". I've checked and distance to Rooslepa Beach, which is mentioned on booking, directly is 3.7km, while booking says 2.8 km. Maybe the data about beaches is not from OSM or Google. I hope booking support helps you!

Hi, I've checked it out

1) Roosta rand is already tagged correctly on OpenStreetMap. I'll remove your changes.

2) The search bar on this page

https://www.booking.com/hotel/ee/villa-hanson.et.html#map_opened-hotel_surroundings

does requests to Google's API, not OpenStreetMap.

3) On Google Maps this place is called "Elbiku rand" and is marked as a hiking area.

4) I suggest you select it on Google Maps and use "Suggest an edit" button at the bottom to change it's type, and, if "Roosta rand" is a more correct name, then a name too.

5) I don't know how much time will it take for Google to accept it, but also be aware that even after it's updated in Google Maps, booking.com may not update the beaches nearby data from Google automatically or fast enough.

Wow, those trees. I'm not sure about removing natural=wood though. Trees and the forest are not mutually exclusive. The same as you can map individual trees in a tree row but it doesn't make the tree row redundant.

Some clients may ignore trees or display them only at higher zoom levels.