Sorry but you’ve just created an invalid structure: your inner polygons overlap each other.
Please draw a new outline of the entire "inner" part and use only that.

Thanks for the fix. I also fixed your other changesets in Brussels when they created the same problem.

Hello,

On this picture taken about one month ago, the eastern part of the street is one-way, while the western part isn’t.
https://www.mapillary.com/app/?pKey=504858339001786

I suspect your changeset fixes one part by introducing a mistake for the other part. The road should be split.

Do we agree here or did your users report something different and claim that the entire road should be a two-way road?

Hello,

Thanks for spotting a one-way road here.

Two recommendations, please:

1) Make sure to provide a source, ideally a direct link to the mapillary picture you are claiming to have used.

2) The white signs that come under one-way signs are important in our country, they make the difference between OSM being a map only for car drivers or for everyone. As the following picture shows, this road has a sign allowing cyclists to use the one-way road in both directions, which translates into "oneway:bicycle=no". This is important for routing.
https://www.mapillary.com/app/?pKey=192252756719326

Thanks in advance.

Bonjour et bienvenue,

Je vois votre édition. Ça appelle quelques commentaires et conseils.

1) « crèche du petit poucet » comme nom, c’est bien mais peut-être pas uniquement des minuscules. Pourquoi pas « Crèche du Petit Poucet » ?

2) Important : mettre un titre correct, vous avez écrit « vrai » à la place du titre, ça n'apporte aucune information pour comprendre le changement.

Hello willsandy,

Please make sure to always write a clear changeset description before uploading data to the main OSM database Failing to do this results in your contribution showing as "no comment", which looks really suspicious and might encourage people to erase them.

Hello,

The hospital is already on the map.
way/447688255

Perhaps you meant to add the door to the emergency service. Please use appropriate tags for this but please do NOT create a hospital inside an existing hospital, this won’t make any sense.

OK, thanks for the reply.
So, maybe you might want to remove the "dyke" tag if it’s not there.
Feel free to add the extra details you spotted there, it is interesting to have them on the map. Flanders refreshes aerial imagery about once a year for each area, so probably in a few months there will be newer images that will make it easier to trace the water basin and spot the new objects.
For clarity, no-one is saying you should stop mapping at all, we merely requested to improve how you describe your work.
Have a nice day.

"addr:city=Bruselas" is incorrect.

1) The official languages here are French and Dutch, we do not write city names in Spanish. For the record, this place is within the Brussels Region, but the addr:city here is Woluwe-Saint-Pierre - Sint-Pieters-Woluwe.

2) In general, it is not necessary to add city or municipality names on objects. The reason is that OSM is a geographical database; such information is already automatically computed. If you repeat information on nodes, you artificially create duplicate places, and it also corrupts searches. Please don’t do that.

Your edit has been reverted.

Hello,

You replaced "addr:city=София" with "addr:city=Sofia, Bulgaria".

This is incorrect, and can be qualified as a form of vandalism because you are transforming a perfectly valid data entry (in the local language) into a mashup of city=country name in the latin alphabet. This will damage searches in this area, please repair immediately.

Hello,

This changeset raises a few questions.

In the previous changeset, a user had explicitely marked the embankment as razed.
way/901325687/history
On the latest aerial imagery it looks like the former infrastructure is gone, it is not immediately apparent why you are reintroducing man_made=dyke here.
Would you please explain? Has the situation changed here recently? Are you mapping after surveying the place yourself or working from other sources?

I also notice that you are doing a lot of various stuff, like adding a new restaurant or adding changing points for e-vehicles. I must insist: please make sure to properly document your changes instead of hiding them under a vague "fixme" claim, which does not reflect what you are really doing on the map.
osm.wiki/Good_changeset_comments

Looking forward to your reply, on this changeset page. Thanks in advance.

Hello,

This is a comment on your latest changes on OpenStreetMap.

Please read this carefully, this is important.

1) It is advised to do small edits. Please do one thing at a time and upload it. Not a bunch of unrelated "fixes" in the same upload. In particular, don’t name it "klein" when you are creating a 13 km² bounding box to the map; the box of your edit is almost as large as the whole municipality!

2) Please make sure to write real changeset titles. This is the first thing we see when we read your contributions. Make sure that the descripttions correctly reflect what you are doing. In particular, abstain from vague comments like "een paar fixme’s" or "kleine aanpassingen", this says absolutely nothing about what you are changing and why.

Hope this helps. Have a nice day.

Hello,

Did your app show you that there was already a restaurant here? I am asking because your app made you merely add Oishii Rood on top of the existing one, as if there were multiple restaurants in the same house. We fixed your edit by re-using the existing amenity.
Have a nice day.

Bonjour,

Merci pour l'info sur le déménagement.
J’ai corrigé : on n'indique évidemment pas une adresse à LLN sur un point à Bruxelles, donc on a recréé un nouveau point ici.
node/12252791846

Hello,

Thanks for adding local shops to the map.
Just one point: to add a shop, it is better to create a floating point inside the building instead of changing the tags of the building directly, as you did here:
way/675771251/history

Also, phone numbers won't work if you use the "Belgian style". Apps will work better if you use the ITU-T E.123 format, which is the standard for OSM.
Therefore: +32 2 123 45 67 instead of "021234567", where +32 is the international calling code.

Hope this will help you making better contributions. Happy mapping.

Hello,

Please make sure to use a correct changeset title when you upload data.

You added this: "#DRCFloods, #DRC Congo River floods response"
… but this change is in Angola, I am afraid it has nothing to do with the Congo River.

It’s better that shops are mapped as nodes, please do this and no longer mix shop information with the container building itself.
We redid your edit.
node/12249171955

Hello and welcome to OSM.

I see you wanted a review, so here it is.

This is a good changeset, you added a floating node inside the building, which is the correct way of adding shops. We just fixed a few minor details, nothing to worry too much.

Happy mapping.

Hello,

Thanks for the fires. However, the changeset seems to introduce new mistakes, e.g.
way/91434627
building=government_office is not a recognised tag. (And the amenity=post_office should preferably be mapped as a floating node instead of merging everything on the building itself).

way/848166251
The operator of an OCMW is the municipality, therefore "operator=Sint-Genesius-Rode - Rhode-Saint-Genèse" was correct. You changed it into operator=OCMW… which means that the OCMW operates itself. We never do this on OSM. Did anyone request that you do that?

node/2338251650 and many others: zebra markings are visible, therefore it’s better to tag crossing:markings=zebra directly instead of crossing:markings=yes, because "yes" won’t give enough information to renderers and it will require other mappers to change it again. Let’s save time for everyone.

Hope this helps. Have a nice day.

Sure, Aarschotsetraat is definitely a typo but, as H4N5-antw explained in his reply, Mapillary pics show that the real name of this small path is Aarschotsebaan.

We edited the name according to what the street signs say.
way/384662326