Hello Fips,

I've noticed that you've created relation/1338717 a long time ago. The problem with it is that this data is not supposed to be on OSM. Would you mind if I delete it?

Regards,
Dimitar155

I usually make it like this but I haven't done it this time. I will keep it in mind.

Dear Valentin,
I agree to leave like it is for now, but I will contact Sofia Municipality to check if this sign is supposed to be there.
Regards,
Dimitar

I'm aware of the Road Traffic Act, but it doesn't make sense for this sign to be there. Up to June 2015 (https://www.google.com/maps/@42.6903115,23.307037,3a,75y,165.1h,81.9t/data=!3m7!1e1!3m5!1seXdxfrQNE5T_E6yOwDhaQg!2e0!5s20150601T000000!7i13312!8i6656) the left two lanes (which currently have marking for car traffic) were part of the parking.

In June 2018 that area was cleared for cars (compare 2018 (https://www.google.com/maps/@42.6896869,23.3070876,3a,75y,37.27h,84.18t/data=!3m7!1e1!3m5!1sBry0SSJQMSKpohmU03Lr2Q!2e0!5s20180701T000000!7i13312!8i6656) to 2015 (https://www.google.com/maps/@42.6896799,23.3070694,3a,75y,37.27h,84.18t/data=!3m7!1e1!3m5!1smrxXT1XS1l6CcXX5fB3gqg!2e0!5s20150701T000000!7i13312!8i6656)). The sign wasn't there in 2018, but it appeared in 2019 which leads me to the thought that somebody placed it there because it should be there according to some outdated plan.

Hi Valentin,

The sign applies (or should apply) to the right lane that is for ambulances only. The left lane is for cars. It's written on the asphalt.

Regards,
Dimitar155

Hi VT&VT,

Why have you added <relation/12928186>? There is no sign that forbids right turn from Pencho Slaveykov Blvd. to Pirogov Hospital?

Regards,
Dimitar155

Hi Cat2006,

It looks alright. The only thing that you should know is that street names should not have "ул." before their name. If you have any questions, let me know.

Regards,
Dimitar155

Hola JAR2004,

¿Podrías decirme si node/2241443858 tiene tablero de salidas electrónico o sólo información de horarios? Gracias de antemano.

Saludos,
Dimitar155

Здравей dam,

Камерите които си добавил не са за отчитане на скоростта. Използват се от АПИ с цел преброяване на преминалите автомобили.

Поздрави,
Димитър

Здравей kocpae,

Сградите които си добавил изглеждат доста добре, но ще изглеждат още по-добре ако след като ги изчертаеш натиснеш Q за да може ъглите им да бъдат точно 90 градуса. Благодаря предварително.

Поздрави,
Димитър

Hello,

It looks like you've changed seasonal=yes to yes=yes. Could you please fix it? Thanks in advance.

Regards,
Dimitar155

Здравей ivanatora,

Възможно ли е да използваш таговете natural=water + water=river за областите на реките вместо waterway=riverbank? Благодаря предварително.

Поздрави,
Димитър

Здравей foreigner037,
Сигурни ли сте за маршрута на пътя през град Драгоман?

Здравей Руди и добре дошъл в OpenStreetMap,
Предишните ти промени са много добри, но за тази имам няколко забележки.
Правилно си се усетил че типовете на площите не са верни. По-правилно би било да са маркирани като трева.
Гаража (way/996262328), който си начертал май не е гараж, съдейки по височината, която си въвел (15 метра).
Когато чертаеш сгради, е хубаво след това да натискаш Q, за да се изправят ъглите им.
Ако имаш някакви въпроси относно OpenStreetMap можеш да ми пишеш на лично съобщение.
Поздрави,
Митко

Здравей Венци. Името на way/97112575 наистина ли е само "Симеон"?

Hi Ventsi. Is the name of way/97112575 really just "Simeon"?

There is the sidewalk=left/right/both/no tag for the sidewalk. If they are very narrow (two cars can't pass each other without one of them going on the pavement) you can tag them as highway=service + service=alley.
highway=living_street is for streets where children can play on them, pedestrians can cross anywhere and cars can't go faster than 20km/h. Such zones have specific signs on the their entrances and exits.

I've read you whole reply but I won't reply to everything of it since my reply would be too big. The service:vehicle:* scheme was introduced by the iD editor. Before that it used the service key with ";" separation for multiple values. That solution wasn't the best one as you can guess. The "issue" with the current way of work of iD is that anybody can write anything in the box and it will pull the closest match from taginfo. If there is no "tires" in taginfo, it won't suggest it. I'm "taking the firehose out of the house" by removing the service:vehicle:tires tag. I've already done the same thing for service:vehicle:Transmission_Repair. As you can see in taginfo it's not being used anymore and there were no other new uses. Note that I didn't have to do any additional clean up after the first "mopping".
Developers usually don't have to do that sort of pattern matching since they could just query for all features with some tags. In case they only request one of the tags, they will notice that the data suddenly disappeared and they will (or at least they should) take action to fix their software.

"The advantage of textual tagging is flexibility (new tags for new situations, without some long bureaucratic approval process). Only problem is, people come up with different ideas of how to do it."

Is there a difference between the meaning of service:vehicle:tires and service:vehicle:tyres? There is consensus on this topic based on the uses (700 for tires vs 2.7k for tyres). There is also consensus to tag the "colour" and not the "color" of roofs, buildings etc.

I'm not looking for absolute unification. I'm not going to abolish widely used tagging schemes as you suggested with your sidewalk vs pavement example. I'm only doing it for tags that have the same meaning like in this case.

About your first part: I haven't occurred this issue so far because I try to edit and upload a few elements at a time which are close together (you can see my profile @Dimitar155/history). There is this one and another big changeset made by me using Level0 but I didn't intend them to be so big.

In an ideal world there would be only one way to tag something. Unfortunately there are a lot of similar examples (see :color vs :colour keys). It's better to have only one scheme and not bother to maintain two (or more) parallel schemes at the same time. If the current trend continues (which will continue if we don't standardise now) we would have a dozen different tags with the same meaning but with slightly different spelling which is not ideal to say the least.

The changeset shoud've included only the node in Hawaii. I'm not sure from where the node in Russia came. Might've been some error or conflict that I didn't notice.