Sorry, I had to revert your change.

Organic Maps is a nice and user-friendly app but it has a problem: the map you see in the app is not refreshed in real time and lags behind.
Lloyd Coffee Eatery was already on the map before your change.
node/1242137440

Hello,

Thanks for this again, and for finding missing names.

Tip of the day: do not forget to add the fields for multilingual names (French and Dutch), so that we won’t have to redo the work after you each time. ;-)

Hello @ChaBog,
I am afraid there are some problems with this edit and with some of other changes you brought to the map.
I had to undo this changeset because those ways were either duplicating existing crossings or were failing to connect with existing stuff. As you can see above, the editor triggered a huge number of warnings for such a changeset.
I am available for help or guidance if you want to learn how to do edit OSM data, in a way that would be useful for everyone.
Have a nice day.

Hello,

Thanks for editing the map and helping out with outdated info.

You seem to be using "Organic Maps". Perhaps you should have a look at your settings. It looks like you are adding French translations ("name:fr" in OSM language) while keeping the names unchanged ("name" in OSM).

I guess you wanted to change the name altogether. Maybe you should have a look, otherwise there will be no visible changes on the map.

In the mean time, I fixed data for The Scott and Sequoia.

Hello,
Thanks for this, I didn’t know the community decided to change it into BE:cyclestreet. But it makes more sense, indeed.

Hello,
Technically correct, indeed.
I added the former name as short_name, to make it available for geocoders.

OK, thanks.
My attention was raised by the name field as "BX29 - Gueux", which is not visible on the boxes themselves and looked like it was directly copied from their website.

What about this one?
node/7234433734/history

It looks like @Thierry1030, who lives in that area, recently surveyed it and located it somewhere else. (Check his latest comment.)

Hello,

It seems like you wanted to draw Infrabel Academy as an area. This is a good idea but I think there is a little mistake in your multipolygons. iD is really buggy because it apparently does not warn you when you create invalid 1-member multipolygons, like this one: relation/11733074

An ordinary way for this building will be more appropriate, while transferring the description and operator tag to the area (way/975840095).

Would you mind fixing this?

Hello,
Thanks for spotting this. It looks like changeset/107200925 was a mistake by a newbie.
I undeleted the original node, to preserve history and keep the location that is in sync with our other databases.
Happy mapping.

Well, I fixed it, thanks for the directions.

Sorry, I thought you knew how to view them directly on the maps.
Here are the links:

1) The "forest area" you gave a name to
way/532979509

2) The park
way/23231090

Hello,
I removed tunnel=culvert (man_made=tunnel is enough)

Hello,
Thanks for spotting this.
I completed the change and also updated the name on the other segments of the same street.

Hello,
Are you sure you touched the right object?
way/532979509 is a landuse area tagged with landuse=forest, and it looks like it is overlapping way/23231090, which is a—currently unnamed in OSM—park. I suppose you meant the latter, didn’t you?

Hello,
Thanks for this. If you don’t mind, could we have a quick check of the spelling of the name here.
In the phone directory I found this pharmacy spelt "Bauduin". "Baudouin" also exists (there was a king named like this). "Baudoin" is usually non-existing, though this is a frequent mispelling of the former.
What do you think?

Hello, @elucci.

It looks like you are importing data from cycloparking.brussels’s website.

I am afraid this is a violation of their legal terms. In the past we had contact with them and they seemed rather hostile against having this data showing in OSM, because of that reason.
https://cycloparking.brussels/en/legal-notice/

Did you obtain written permission from them to copy from their website and import data under the ODbL (OSM’s licence)?

But I bet this is a copy-and-paste error, as this looks like the reference of a book.

Hello,

The huge list of name is addr:unit on housenumber 9 looks a little weird.
node/8984244527

As you can see, addr:unit is directly rendered on the main map layer.

If this is name of residents of this building, then this information must be deleted from OSM immediately.

I suppose this is a mistake but I’d rather ask you first.

Hello again,

Something else, a piece of advice: if you change several things on the map, it’s better to either make separate changesets, or at least write what you did exactly.

In this changeset, you also renamed a bit of Avenue de l'Yser/IJzerlaan into Avenue de la Chevalerie/Ridderschapslaan (which is okay by itself, it’s just that this caused a validation issue because of unmatching relations. Yes, OSM is complicated stuff, that’s why we have validators and peer-review, and you will help to make life easier by writing good changeset titles.
Happy mapping.