Sorry but, again, this mechanical edit is completely misguided.

There is no roundabout here.
https://www.mapillary.com/app/?pKey=591746126626916

Your edit has been reverted.

Hello,

This may *look* like a roundabout to you but its legal status is *not* a roundabout.

We’ll have to revert your edit.

There was a typo in the changeset title because the wrong tag, which was correctly removed here, is "layer=-1".

If you want to mention that a road is below the surface (while not being in a tunnel), level=-1 would be okay.

If you want to ask questions, you can reach out through direct messages instead of commenting on random changesets, because this gives the false impression that this changeset damaged the map (it did not).

Hello,

You did not reply to this comment.
But I found out that you made another changeset here: changeset/171772522 intended as a fix.

I made some additional fixes, it should be okay now.

operator=Solid'R.

I don’t believe Solid’R collects glass bottles and cooking oil. That is for the other containers in this area, right?

Don’t forget to keep tags in sync.
30 km/h is the default urban speed in Brussels whereas 50 km/h is the exception. "source:maxspeed" is used for that purpose. You can not just change the maxspeed tag and ignore the rest.

Fixed by changeset/171827634

Thanks for this.

Instead of a hard noexit tag (that applies to every mode of transport), shouldn’t we create a short connector between node/13127929852 and the intersection with Rysheuvelsstraat? It looks like cyclists and pedestrians can go through.

Thanks for adding details here.

However, please do not use tags such as "layer=1" on buildings if the purpose is to evade validator warnings.

In this edit, as long as in yesterday’s edit, you created a long footway across a building (way/1428252282). This mistake triggered the warning. Cheating with the layer tags gets rid of the warning but keeps the error.

The correct way to map those situations is to cut the footway when crossing the building and tag the inner part as tunnel=building_passage.

Example of a fix here: way/1427974749

I see you used the iD online editor.
The building tag was probably added if you clicked on a building preset, e.g. "Craft Brewery".
Don’t worry, it’s already fixed anyway.

OK, thanks for the explanation. I see you commened on the original changeset, so that the discussion can take place with the mapper who initiated this move. Well done!

Hello,
Changing the brewery type is okay BUT please do not add "building=yes" on a polygon encompassing several existing buildings and please do not add addresses that are already on the map. Overlapping building structures or duplicate addresses are not desirable on the map.
I fixed yours various edits from today.

Hello,

I suspect there is a false-positive issue from Osmose here.

A user recently retagged the railway lines and provided an explanation why the operator tag should be changed.
changeset/170020049

Probably that Osmose uses the wrong validation list… which prompted you to undo this mapper’s work.

Hello, and welcome to OSM.

I am afraid to tell you that your change is misguided.

The official name in Dutch is "Bergense Steenweg" for the entire road across Anderlecht. This name is written in two words on street signs as well as in the UrbIS database, which is the official reference for street names in the Brussels Region.

The "Bergensesteenweg" spelling is found in Sint-Pieters-Leeuw only, not in Brussels.

We will revert your change.

You are welcome.

Hello, and welcome to OSM.

Thanks for your recent edits.
However, can you please make sure to write real changeset titles when you send uploads to the database.

"adding data" is not an acceptable changeset description. It provides no useful information. After all, we are all adding data here.

More explanations on the OpenStreetMap wiki.
osm.wiki/Good_changeset_comments

Thanks in advance.

Bonjour,

Ne pas dupliquer les liens Wikipédia sur les objets OSM, svp.

Il y a déjà un lien "wikidata" qui lie *toutes* les langues. C’est comme ceci que les apps peuvent fournir le lien approprié.

+ Éventuellement 1 (un) lien Wikipédia dans la langue locale. Pas plus.

All right, thanks for this. I’ll retag it as broken, then.

I agree with you, @borishag. Those tags are not necessary. This changeset is a mistake and has been reverted now.

That said, "addr:city" and "addr:postcode" should also be deleted all across Belgium, because we have zones covering the country to provide this information much more reliably.

When cleaning up data, I currently make an exception for AS Watson shops because I understand that you regularly query OSM data and expect to find city name and postcode directly on the nodes instead of doing geoqueries. It would be nice if you could find a way to improve this in the future.

For the enlightenment of those who would wonder what this changeset is about, it looks like it contain two different things.

1. A typo fix (dogs=no → dog=no) on a playground in Warsaw (Poland). This part matches the changeset title, and it is a good fix.

2. Drawing about 35 polygons for woods in Colorado (USA).

Notwithstanding the fact that one changeset per country would have been better, can I also suggest typing real changeset descriptions when you upload data.

"MAJ OSM diverses le 260825" unfortunately provides no useful information about what and why you edited those objects. We can only guess that you claim to have surveyed those 3 remote locations today.

osm.wiki/Good_changeset_comments

By the way, the date is automatically generated in the changeset summary, there is no need to type the date manually in your changeset titles.