Fixed in changeset/165163102

Ok, I see in highway=footway :

> For ways designated for pedestrians, but which also allows bicycles, use either highway=footway and bicycle=yes or highway=path, foot=designated and bicycle=yes.

I'm terrified of how complicated it is now for newbies to grab just a base minimum knowledge to contribute into OSM… The only hope is for the community, which will guide and help.

I can add bicycle=yes only when I'm 100% sure it is allowed (so there is a sign or marks), so I will use highway=path. But it will be really hard to change a habit to mark all footways as highway=footway…

@maraf24, thank you for notifying me! Sorry it goes slow to figure out and fix…

Yes, there is no bicycle ban there.

Hmm, till today I thought this way:

> "Paths kept mainly by the fact of people walking on them or paths that are only minimally constructed are usually tagged as highway=path. Their surface might be uneven (typically ground)…"

(this is from highway=footway )

Now I see a problem:

> "For urban paths which are intended primarily for pedestrians (potentially with bicycle=yes), some argue it's better to use highway=footway. Others prefer to only use highway=footway for formal footways…"

(this is from highway=path )

Let me read more about it…

I will visit this place again and check all the details.

Thank you very much for controlling the changes!

Yes, I agree, "footway:smoothness=good" should be logical here. The problem is — I'm not 100% sure about it — I used a bicycle part, which was really good, and in common about the whole road I can say "smoothness=good".
I can visit this place one more time to check the smoothness of the footway.

@maro21, I've added more details about 2 x "Chatka przy Jatkach" restaurants in changeset/162824973
Thank you for answers!

Yep, in my opinion it is better to have an approximate area — once someone will see that it is not accurate and fix it.

In case of just one node, it is possible that it will stay as a node for years.

Hi, LM_1!

If you was there, could you please create an area for the hotel territory and move tags from node node/8927411925 to the area?

Hi!

Please don't do changes with such big area.

Please note for the future: changesets should be local.

To avoid conflicts and as a courtesy to reviewers, it is recommended to:
• combine changes in a small geographical area (within a city, district or province)
• keep changes within the same country
• upload/save changes before moving on to map in a different area

Why? Have a look at the section
"Geographical size of changesets" on this wiki page:
osm.wiki/Changeset#Geographical_size_of_changesets

Thanks for considering, have a nice day and happy mapping!

note/4483290 was fixed here, thank you!

@theDM, please write better description of your changes, see osm.wiki/Good_changeset_comments

"Chatka przy Jatkach" node/5451815459 looks like a duplicate of node/280727473

I found the address in a cash withdrawal report.

Exactly this one ATM has a unique address! I couldn't find address "Piłsudskiego 49/57" is OSM, so I decided to add it, and now it is searchable:
osm.org/search?query=Wrocław Piłsudskiego 49%2F57

FYI: one mistake fixed in changeset/161713760

> There should always be capital letters in names in Polish.

@maro21, do you have a reference for this?

I follow https://en.wikipedia.org/wiki/WP:CAPITALIZATION , there is also a link to https://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style/Poland-related_articles , but I don't see the rule you've mentioned.

FYI: addresses were removed in changeset/159255997

Fixed in changeset/158871918
;)

Hello, maro21!

When you delete something I added, could you please notify me ?

Perfect way, I think, is to add a comment to the changeset where I added an object (in this case, this changeset: changeset/157682416 )

> look messier
I agree.

I know some roads which became worse, for example way/366085036 was probably good in past, but now it is not.

I hope apps like https://github.com/streetcomplete/StreetComplete can use such tags to ask to update such information when 2-3 years passed.

Also, theoretically, auto-checkers can just check when tag `smoothness` was changed, without additional tag `check_date`, but I've never heard about such apps.

Fixed in changeset/156579720