tunnel=building_passage

"The layer should be the same as the layer of the building, with the exception when several tunnels are passing on different levels. So if the building doesn't have a layer tag, the way should not have one either."

way/817657559
way/817657561

Current Bing offset: 3.20; -4.10

Next time you remake it to your great liking, please don't break the routing. :(
Fixed in 153271100

Very, very bad practice: ignoring dialog & arguments (changeset/152730077). Just silent revert & redraw.

It looks like a conscious preference for a war of edits over any other solution :(

There is now new seaprate way here. Just at that moment this street has path status.
Current solution (highway=path + construction=*) is widely used: https://overpass-turbo.eu/s/1Ne9

So, only reason for this tagging - for renders. osm.wiki/Tagging_for_the_renderer

Good practice - tunnel=building_passage without any layer:

tunnel=building_passage
"The layer should be the same as the layer of the building, with the exception when several tunnels are passing on different levels. So if the building doesn't have a layer tag, the way should not have one either."

Also, that's about using layer for buildings. Yes, layer is not level. But building and zero floor tunnel has same layer.

way/826235624 (and several other)
But why layer=-1? Is this way really lower, then building ground level? And goes under the building? (not on building ground level)

About Алмашки крај reconstruction - earlier wrong revert & unreplied for now comment: changeset/152730077

Sorry, but, ground truth: now (for more than 6 month - it's not one week status) you can't drive thru this streets, but you can walk bicycle in any direction. My mistake: it's not footway. It's path. Can you offer better tagging of current status?

[out:json];
node[name=Meridianbet](user:"Kladionica Meridian") -> .a;
foreach.a(
._ is_in -> .b;
nwr.b[building] -> .b_in;
way(around:20)[building] -> .b_around;
if (b_in.count(wr) == 0 && b_around.count(nwr) > 0) {
._;
out;
}
);

Please, stop your mass commertial import and fix your previous changes.

Examples:

Placing or roads (about 1/10 of your mass import):
node/11981093698
node/11981099515

Placing outside buildings (about 1/4 of your mass import):
node/11981145143
node/11981100142
node/11981259638

Duplicates:
node/11981251677
node/11978931897

About deleted path way/1282086743.

It's really totaly impossible to go between this two parts of cycleway? What happend with deleted path (I checked it abou month ago).

way/753932091 <-> way/1000566379

There is no continuous cycleway there. Road signs (as ground truth) break it several times, as I mapped earlier.

2 и 3 - исправил.

1. Спутниковые снимки Google категорически запрещено использовать при редактировании OSM. Используя их, вы подвергаете проект OSM юридическим рискам (хотя, вероятнее всего, всё просто кончится откатом всех ваших правок - прецеденты были).

2. "Тоненькая тропинка..." - это не название тропинки (way/585731614).
Пожалуйста, прочитайте об использовании тега "name". Например, тут: osm.wiki/RU:%D0%9D%D0%B0%D0%B7%D0%B2%D0%B0%D0%BD%D0%B8%D1%8F#%D0%98%D0%BC%D1%8F_-_%D1%8D%D1%82%D0%BE_%D0%BD%D0%B0%D0%B7%D0%B2%D0%B0%D0%BD%D0%B8%D0%B5_%D0%B8_%D1%82%D0%BE%D0%BB%D1%8C%D0%BA%D0%BE

3. Также это описание не является адресом (тег addr:street) точки node/10980282230.

Подобные описания могут размещаться в теге description, а в вашем случае - в description:bicycle.

Oh, what a complex world! :) Thanks!

But why???

Не по пропуску, а по глупости :)
Исправил, спасибо.

Одно из не надоедающих занятий, когда надо вечером чуть потупить :)

JFYI: вдоль Серебрякова из-за идущей сейчас реконструкции доступные для OSM спутниковые снимки уже не актуальны. Тепловая карта Стравы (куда входят треки за два года) - тоже.

Местами чуть вернул пешеходку в соответствие с актуальной реальностью.