I meant that paths are often managed and choosing between a footway and a path should not be done based on it. Footways should only be chosen if cycling is not allowed there. Paths are versatile and allow to map all kinds of non-car roads by combination with other tags.

Just wanted to add that this "managed" argument is IMO should not be taken into account. It's common to tag combined bicycle/pedestrian paths as a highway=path with foot and bicycle=designated and actually more preferred to highway=cycleway by some data consumers. These ways are managed, but are still highway=paths.

Actually, nevermind, my mistake. I've looked only at one direction. The other direction shows route through now non-existent road and it's obviously not updated.

Sorry, strange website. It's about 318. https://web.peatus.ee/ in the first field select route and type 318. In Rakvere it seems to take a more straight route if this website is correct. I have not verified it.

Not sure if it's correct, but the route here is different
https://web.peatus.ee/linjat/estonia:8430eec841b988beacb10d0011e9bc9f/aikataulu/estonia:8430eec841b988beacb10d0011e9bc9f::02

Looks like the toilet building at the northern entrance got buried under the pedestrian area.

Hi, you seem to have accidentally removed building=yes tag. It's still a buliding. The social_facility does not assume that it's a building and is usually drawn around the whole campus (I often use maa-amet's cadastral map for this)

Maybe footways should have been changed to paths instead of bicycle=yes? I think it would be enough for mtb routers and renderers like cyclosm.

Just noticed that id editor actually saves your Strava key under imagery_used. Not sure if it can be used somehow, but just so you know. You can remove it under "Tags" section when uploading.

Hello, name tags are not for addresses

Hi, you don't really need to put oneway=no on the roads. They are not oneway by default.

Hi, Aulo.
You may want to consider using
highway=service
service=driveway
surface=unpaved or ground

instead of highway=track for driveways. Tracks are for accessing land, service roads are for accessing buildings.

Hi, do you mind adding parking=street_side to parkings like this? Those P's are quite dominating the view currently, street_side's P's are at least smaller in the default renderer.

changeset/129635785

reverted

Hi, maybe you wanted to update the theater node nearby? Also, it seems that Eesti Noorsooteater is the new name of the theater, then it shouldn't be alt_name. It should go into the name tag and the previous name into old_name.

As for this node, judging by the website, it's current name should be a "Nukuteatrimuuseum"

>By default the set of tags are general=yes

This is what you see in iD editor which you shouldn't really trust, it's a separate piece of software with it's flaws. Not an official reference for tagging.

The reality is that to my knowledge routers do not avoid residential roads when doing on foot navigation. That's why I proposed that you don't waste your time on this. Of course, you can add these tags. Just wanted to save your time :)

As for the cycleways many routers actively avoid routing pedestrians there, since this is usually forbidden by law or just not advised to use a cycleway for walking. For example, OrganicMaps' on foot router will choose footway crossings over cycleways.

Not sure you really need to add this. highway=living_street should already allow walking.

btw I've visited this workshop once and used the main entrance and payed at the main cash register where all purchases are paid for.

You can use the main entrance too. Many bike services have a back door, but are also accessible from the front door. And the title literally says "<bike_shop_name> workshop" which is just an additional word. I think it's better to remove this node. Entrances can be mapped as entrance=*** tags.