*spiral staircase
*layering - river area <> stairs segment <> stairs segment

The title should be understood as: I reverted the changeset in revert:id because it (the author) <title>

reverted in -changeset/185725366 - please, familiarize yourself with mapping practices on OSM, for one, the "One feature - one element" guideline - osm.wiki/One_feature,_one_OSM_element

Quoting:
> Examples of bad situations:
> Shop in a building mapped as a single object with building=* and shop=* and name=* (which will often apply only to POI). This one is more debatable, and it is generally not treated as obviously wrong as long as all properties are applying to all features at the same time.

This changes got uploaded prematurely - I intended to draw an building building for aisle of shops in the tunnel, so that Key:level makes sense and add Key:layer where needed. If it breaks routing in any way, we can revert this or leave it half-way for me to make adjustments later.

edit:
* changeset/183489843

partly reverted - mistakenly marked amenity as disused

changeset/183481182

thank you, these addresses tagged on relations are not rendered to the stand. tiles and neither does EveryDoor expose or indicate tagging on wider relation, or separate addr nodes in any way I could see. Maybe I could try to raise that with the developers.. and be more carefull with addr edits on large building using EveryDoor only.

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.