Waow, that was fast. Thanks for the fix.

Hello,
You removed construction tags here, this is fine, but access=no is still set. So, the road may not be used for routing. I want to check with you if that was intentional. Still closed to traffic, then?
way/28108935
Thanks.

Bedankt. Wij hebben dit aangepast, zie mijn commentaar hier:
way/1117339196

Yes, Digitaal Vlandeeren GRB is the layer you can use to draw buildings.
I was planning to do a revert but it proved impossible because you have been changing more stuff in this area since this change. I will try to do it manually.

I am actually quite horrified at the number of mistakes. I admit that it must not be easy to get your first contributions right. With respect, I’d like to invite you to consider doing fewer changes on the same day and spending a little more time studying how the map works and how we tag objects.

I was preparing an email to you to warn you about several mistakes with today’s edits, namely this: Silly shapes like this, which I found in invalid multipolygons, way/1192331501
Areas overlapping footways, double or triple definition of some addresses, abuse of the layer tag (probably to escape genuine warnings by the iD editor), damage to building outlines, and more.

I will try to spend some time fixing as much as I can. I will ask other mappers to help.

Hello,
That seems very unlikely. Grassland is typically found in remote country areas, not on a town square.
For a simple square with well-cultivated grass, landuse=grass is much more appropriate.

Hello,

Welcome to OSM.

I see you added a small path on the map. You can see your path on the map already. The only problem is that if a path is not connected to anything else, it will be pretty useless on the map.

Does this path connect the road somewhere? I can help fixing this if you give some hints about where.

Anyway, the first correction to apply here should be to tag it as a private path, especially if it only used for railway maintenance and not aimed at any random person having a walk there.

Looking forward to your reply.

Hello,
The outline of this building had a 100% match with Digitaal Vlaanderen GRB imagery, which is the official reference for building shapes in Flanders.
way/1034374088
Why did you redraw it? It looks like you drew it according to… aerial imagery instead, which does not match. Is there anything special about this building that GRB would not know?

Hello,

Thanks for this. Your latest contributions are quite good. Though, I would like to raise your attention about the use of the "access" key on ways. I recently came across strange routing suggestions for vehicles being sent over footways or stairs and it turned out the problem was created by a few changesets of yours.

Here it is. Routing algorithms have a look at all the ways in the database and must determine whether a given mode of transport may use it. So, highway=footway|steps means "This is only for pedestrians", and then "access=yes" means "Every mode of transport (car, bicycle, foot) may use it." The "access" tag always overrides the default values set by the highway type. Consequently, highway=footway + access=yes allow cars on the footway. I know it might sound counter-intuitive but that is how routing works.

So, the recommended way is to avoid using access=yes on footways and stairs. The tag is not needed at all when it is set to yes. When there is a risk of ambiguity, e.g. public paths across private property, you can use "foot=yes" or "foot=permissive" and that will be all right.

Happy mapping.

Incidently, this is a town hall, right?
way/1190641282

In that case, just putting a name on the building will have no real effect. The map will understand it only as "a building with a name".
If someone wants to lists all the town halls in Benin, they will never be able to find this one. You should add an extra tag to the building, namely amenity=townhall

Hope this helps.

Hello and welcome to OSM.

A good practice on OpenStreetMap is to restrict uploads to a small territory.

If you want to update the map in the Netherlands and in Benin, please do the changes separately: work on one area first and then upload. And only after uploading changes for one country, you can start working on the part elsewhere in the world.

The reason is because if you edit two remote parts and upload them at once, your change is considered as spanning a large part of the globe, as you can see. This is unnecessary annoying many other mappers: people in Belgium, France, Spain, Algeria and oher countries are notified about your change.

osm.wiki/Changeset#Geographical_size_of_changesets

Happy mapping.

Hello,

station=light_rail is plainly incorrect if the other tags about this line are not coded as light_rail. I changed this into station=tram.

OK, thanks, I see now.
I understand this is complicated to achieve in the data model and I cannot blame you for not knowing how to solve that properly. I removed the oneway tags that were essentially barring everyone from using the connection (even legitimate uses) and added a right_turn_only connection here. Routers will now work as intended.
Have a nice day.

Hello,

I suppose the map you are talking about is the standard map on openstreetmap.org: this is a collection of PNG images built from map data. They are regenerated a few times an hour; your place is already visible on higher zoom levels. It might take a few more hours to make sure the tiles at all zoom levels are refreshed too.

It is also searchable: someone who type quartier latin, brussels in the search box will see it in the search results.

Hello,

Thanks for adding some information to the map.

I will fix the tagging mistakes, because the place is unlikely to appear on the map with wrong data.

Hello,

Pardon my asking but what particular sort of issue were you trying to address here?

After your change, any vehicle driving on Zonneboslaan is now prevented to reach Haachtsesteenweg at all because there is a one-way road facing them (this small segment here: way/1190196610). Car navigation is now broken here.

As for cyclists, after your changes, a cyclist coming from Zonneboslaan may only turn right towards Brussels and may not reach the eastbound cycle lane (also because of the oneway restriction).

Are you sure this is the intended behaviour?

Hello,

Adding name translations is a nice addition. But was this change discussed with the community beforehand?

Whether the main name tag should be in Dutch only or Dutch+French has always been a very controversial topic. (I am personally in favour of bilingual names because they are signposted as such, but several other mappers disagree.)

Out of curiosity, where do the French translations come from? Your own survey or did you find a map or a list with them?

That being aside, two technical remarks below:

1) In OSM, street names are also repeated on buildings, this is how we group streets and buildings. If you change street names and ignore the buildings, that will invalidate almost all the addresses in this area. (Yes, the validator is "dumb" and only compares texts strings.) Are you planning to update those too?

2) Spelling and grammar rules are important, even when municipalities create street signs with unaccented characters for simplicity, e.g. "Wilde Rozenlaan - Avenue des Eglantines" → Églantines ; "IJsvogellaan - Avenue du Martin Pècheur" → Pêcheur ; "Heldenlaan - Avenue de Héros" → des Héros ; "Kerkbergstraat - Rue Montagne de l'Eglise" → Église, "Ooievaarslaan - Avenue des Cygognes" → Cigognes,… We’ll have to fix that too.

Have a nice day.

@Jakka: This is in reality a UX problem with Organic Maps.

OM is a mobile app and when adding/editing a point it presents a list of blank fields with languages. Those will populate name:en, name:nl in OSM but not the "name" tag.

The correct way to fill the "name" tag in OSM requires a fairly complicated procedure (0% chance a new user will think about this), i.e. hit the "Add a language" button and scroll all the way down to "Native for each country".

The problem has been reported to the Organic Maps devs, this will avoid faulty edits like here.

Also, the link of the hotel is bad, instead of linking to the brand it should link to the hotel itself, i.e.
https://www.hotel-bb.com/en/hotel/antwerpen-centrum

Hello,

Welcome to OSM and thanks for adding more details here.

Just one thing: It is not necessary to change the name of a statue into "Standbeeld Mercator". The object is already properly recognized as a statue. We don’t add descriptions in the name. I suggest you correct this.

Bonjour et bienvenue sur OSM.

Merci pour l'ajout. Nous avons corrigé pour indiquer les bons codes afin que ce soit correctement reconnu comme un cabinet de médecine générale.

Vous pouvez si nécessaire compléter le point avec d'autres infos utiles, p.ex. téléphone, heures d'ouverture, etc.

Thanks for adding more stuff.

"type=stand" is unknown and won’t be understood by most apps.

The correct key is "bicycle_parking=stands".