reverted: mass changes using not on-the-ground checking, but some undetermined sources, possibly simply aerial imagery; including incorrect surface tagging (asphalt instead of unpaved or sett), incorrect addresses to buildings etc.

changeset/177651581

reverted: mass changes using not on-the-ground checking, but some undetermined sources, possibly simply aerial imagery; including incorrect surface tagging (asphalt instead of unpaved or sett), incorrect addresses to buildings etc.

changeset/177651581

reverted: mass changes using not on-the-ground checking, but some undetermined sources, possibly simply aerial imagery; including incorrect surface tagging (asphalt instead of unpaved or sett), incorrect addresses to buildings etc.

changeset/177651581

reverted: mass changes using not on-the-ground checking, but some undetermined sources, possibly simply aerial imagery; including incorrect surface tagging (asphalt instead of unpaved or sett), incorrect addresses to buildings etc.

changeset/177651581

reverted: mass changes using not on-the-ground checking, but some undetermined sources, possibly simply aerial imagery; including incorrect surface tagging (asphalt instead of unpaved or sett), incorrect addresses to buildings etc.

changeset/177651581

reverted: mass changes using not on-the-ground checking, but some undetermined sources, possibly simply aerial imagery; including incorrect surface tagging (asphalt instead of unpaved or sett), incorrect addresses to buildings etc.

changeset/177651581

reverted: mass changes using not on-the-ground checking, but some undetermined sources, possibly simply aerial imagery; including incorrect surface tagging (asphalt instead of unpaved or sett), incorrect addresses to buildings etc.

changeset/177651581

reverted: mass changes using not on-the-ground checking, but some undetermined sources, possibly simply aerial imagery; including incorrect surface tagging (asphalt instead of unpaved or sett), incorrect addresses to buildings etc.

changeset/177651581

reverted: mass changes using not on-the-ground checking, but some undetermined sources, possibly simply aerial imagery; including incorrect surface tagging (asphalt instead of unpaved or sett), incorrect addresses to buildings etc.

changeset/177651581

reverted: mass changes using not on-the-ground checking, but some undetermined sources, possibly simply aerial imagery; including incorrect surface tagging (asphalt instead of unpaved or sett), incorrect addresses to buildings etc.

changeset/177651581

reverted: mass changes using not on-the-ground checking, but some undetermined sources, possibly simply aerial imagery; including incorrect surface tagging (asphalt instead of unpaved or sett), incorrect addresses to buildings etc.

changeset/177651581

reverted: mass changes using not on-the-ground checking, but some undetermined sources, possibly simply aerial imagery; including incorrect surface tagging (asphalt instead of unpaved or sett), incorrect addresses to buildings etc.

changeset/177651581

No, it's better to separate landuse tagging and place name tagging... Probably some new ways/relations for landuses should be added...

Hmm... I guess *some* way or relation should keep landuse=residential... Can't say that I find them anyhow useful, but many people do... And no this are just lacks any landuse tags...

а ты сознательно сдвинул дорогу?

I can only notice the great variability of naming as of now: Shankhai node/3659867594/history , Samretsvelo node/6276184773/history , Airport way/199479145/history , 8th Legion node/930617567/history , Lisi relation/20108635 , Lilo way/57792577/history , Orkhevi node/11042041829/history , Tetrikhevi way/1334988507/history

Some have Wikipedia articles with დასახლება in title, like https://ka.wikipedia.org/wiki/ლილოს_დასახლება , some without https://ka.wikipedia.org/wiki/თეთრიხევი_(თბილისი)

J4kee has added Lisi as ლისის დასახლება to the template at Wikipedia: https://ka.wikipedia.org/w/index.php?diff=prev&oldid=4821136 , but just as Lisi here to OSM.

One consideration is that without დასახლება / Settlement the locality may sometimes be confused with other objects, like the Airport , Didi Lilo & Patara Lilo villages, Lisi Lake... Some are really unclear without it, like საქნავთის დასახლება http://www.nplg.gov.ge/gwdict/index.php?a=term&d=89&t=2192 (which BTW should be reinstated as the correct name of way/77767105/history ). Also note that this dictionary gives the names in full, like საქნავთის დასახლება and http://www.nplg.gov.ge/gwdict/index.php?a=term&d=89&t=1348 . So at least in cases where confusion is likely or where the name is more of a genitive clause like საქნავთის დასახლება, I think it would be better to leave დასახლება in name, also providing alt_name without it.

Considering translations... In case of Russian, in many cases a historic name from Soviet times can be found, like here https://commons.wikimedia.org/wiki/File:2025-04-17_Old_street_sign_at_21_Revaz_Japaridze_1st_Lane.jpg or like поселок грузнефти in the dictionary entry above; and such names would likely still be used by native or near-native speakers of Russian from Georgia. So in case of name:ru I definitely favour translation.

In case of name:en... Well, in the majority of cases there aren't any established names for Georgian toponymy in English (with some exceptions as Narikala instead of Nariqala), so this argument is not valid. However, I would also favour translating to "Settlement"... Like J4kee noted above, it's not an essential part of a name, more like a qualifier; if transliterated, it looses this functionality and only makes the name look more complex and inexplicable. If we need some examples from outside OSM, here is one: https://transit.ttc.com.ge/#/board-info/1:2621/arrival-times https://transit.ttc.com.ge/#/board-info/1:2919/arrival-times

All in all, I would consider the issue with დასახლება similar to street names. Sometimes foreign names of streets are kept unchanged, like Karl-Marx-Allee in English or Бейкер-стрит in Russian. But if we agree to translate გამზირი to "Avenue", even though გამზირი lacks the avenue's usual sense of having trees on the sides, so why should we leave დასახლება untranslated...

(Although that is not a strong argument, of course, as Saburtalo has even been divided between two raions...)

(I can only note that administratively, Kaklebi was assigned to Tsqneti Ubani (II-8) relation/14900502 , while Bagebi was assigned to Vake Ubani (II-5) relation/14900501 ,
as outlined here: https://commons.wikimedia.org/wiki/File:Tbilisi_Ubnebi_2014.jpg

Humph... So is Kaklebi regarded part of Bagebi or not?
Please see way/1467893914 and changeset/177251744

Hm, please take notice of changeset/177544111