Follow up with addresses in changeset/182984400

Partial revert mentioned above - changeset/182975328

If you did that sync-up with cadastre as a single/several changesets and you have the changeset ids at hand, I can try to review it for validity of any/some change. Otherwise, I can do it gradually.

On a different note, apparently, my trivial search & replace on level0 representation of objects - the way I created this changeset https://osmlab.github.io/osm-deep-history/#/way/971057740- somehow broke Farsi name of Caucasus University - https://osmlab.github.io/osm-deep-history/#/way/971057740 - at least the change was *not* intended.
I don't know what caused it yet. But I think I should restore the old name in any case.

Hey! Street signs.. along with gut feeling for grammar rules. :)
As people were faster to respond in TG than me here - in Georgian in number of scenarios, a noun in genitive loses vowel. I remember making similar correction here - changeset/180124208 - also mirroring street signs. In general, I have been seeing street names here and there not honoring this gram. rule, prob. filled by non-native-georgian speakers - and I'm trying to correct those gradually.

Handled by:
changeset/181782250
changeset/181782062

Good catch! I mistook newly mapped nearby art cinema - node/13665198701 - as the new location, making subject node leftover. Thanks for reviewing.

node/13756731305 - layer

node/10781831229 + shop=convenience

Hi! I assume you are the owner of the hotel node you deleted, because it's no longer functioning? Just in case if it's entirely different venue it can be tagged appropriately to differentiate between the two.

For the Nakashidze 10 hotel, internet_access:fee=customers is more appropiate for the common case - "no for customers / free for customers" - see internet%20access:fee=*?uselang=en

About the cafe's outdoor_seating=yes , are you sure? :) I didn't see it when visiting couple days ago, but maybe you put out folding chairs/inventory seasonally?

Hi! I'w working with the park data and saw your most recent edits for pedestrian multipolygon. What do you think about merging the rest of the paths into multipolygon? E.g.
way/235147299
way/225532578
way/133607469
way/1062602501
way/483736997
way/1062602506
way/1062602505

Not the area of this changeset, but Chugureti. Still, maybe you can take a glance at your convenience.
changeset/180815627
changeset/180778106

.. fix typo in all lang variants of last name "Chokhonelidze"; add name:eymology:wikidatasfor all mentioined persons' respective str. relations.

That makes sense, thanks for clarifying.

While we are at it - I would think single segment streets warrant the relation as well? - for arguments of uniformity, the fact that tagging scheme is also about (potentially) addresses, not only street segments.. and the possibility that talked about segment might need to be split in the future to accomodate varying attributes along.

*fix typo in :en spelling, *not* :ka

Hi, thnx for showing the proper way to do it and fixing the part of it.

I intend to create street relations for the rest of the ways touched by the changeset and move the tagging there.

Some questions:
1. Do the eponymous lanes and dead ends belong to relation as street members? (I assume no, but some different named members?)
2. The wiki - osm.wiki/Relation:street - specifically warns agains deleting existing tagging in favour of the relation scheme. I assume it's fine to remove tags from the ways in the context of this changeset, as it's very recent. I'll also copy wikidata and wikipedia tags to the relation too and it's tempting to remove it from ways, wdyt? What about old_name:XX tags handling? Any other notable cases that I might have missed here?

reverted - changeset/177311794

needs reverting, misshaped :(

It's a bubbler - fixed here - changeset/175126468
thanks

Thanks for feedback, corrected here - #174156653