Hello,

You set it as a one-way street but you provided no exemption tag for cyclists.

Most streets have M2 or M3 signs granting access contraflow. It is very likely there would be one here.
(osm.wiki/File:Belgium-trafficsign-m2.svg)

On top of "oneway=yes" which you added, we must add "oneway:bicycle=no" to reflect this.

Can you please tell us whether you spotted such a sign? Ideally, did it include just bicycles, or moped A and/or moped P? Thanks in advance.

Hello,

I guess you are pushing uploads through a third-party app, but would you please consider handling "contact:website" when it exists.

If "contact:website" is set and you want to change the URL, please use that tag. Otherwise, we will end up with two tags, having "contact:website" and "website" providing different information.

FYI, there is a wide consensus within our local community that the contact:* namespace is a superior tagging scheme and should be preferred anyway.

Hello,

For your information, standard practice in Belgium is that we no longer repeat full addresses on POI. I know mappers in some countries still do this but this is unnecessary, and we prefer to keep a clean address register. Don’t worry, I fixed your latest edits of the last hours. ;-)

OK, this is useful follow-up info, thanks.

Next time, please do not comment the changeset itself, which was not faulty. (This changeset did not erase anything, it merely transferred existing tags to a node.)

Hello,

Here is a reply to your request for review.
This is a grey zone between "amenity=clinic" (we do this for the "maisons médicales" that are commonly found in Brussels) and "amenity=doctors". In doubt I chose the latest option. This is already fixed. ;-)

Just one thing: to add a new place, the safest way is to create a new node, do not re-use existing address points (we are gradually moving them while doing door surveys).

Hello,

Nice try but I am afraid there are several issues here.

This changeset seems to have inadvertently erased a few useful elements, e.g. the stop position node for track 16 was entirely gone and caused many bugs for apps relying on OSM data.

You also inadvertently modified the shape of existing platforms, as those nodes node/11227247613
node/11309876923 now break the straight line, as if the platforms were inflated near those markers.

I would advise you to spend a little more time learning how OSM works. Please try to do small contributions in minor railway stations first, before dealing with the main railway hub of the country.

Interesting edit. If I understand correctly—and for the enlightenment of other reviewers who would want to inspect this changeset—you added a link to NMBS/SNCB website in every language to the station page, where they provide details such as address and equipment.

One question here about the language you chose for the main "website" tag.
I see that stations in Flanders are always NL, stations in Wallonia are always FR (though DE would have been preferred for Eupen, it seems)… and that NL and EN are used in the Brussels-Capital Region. Why this choice for Brussels? Wouldn’t it have been preferable to either use English everywhere or equally distribute FR and NL links?

Hello,
Good practice in OSM is to keep the history.
If a new restaurant opens and replaces a previous one, it is strongly recommended to keep the existing node and just change the tags.
osm.wiki/Keep_the_history

(And yes, in this case, it looks like a newbie had created a duplicate, so there was at least one node to delete, but not all of them. 😉)

Don’t worry, it’s already fixed by now.

Hello,
Nice try but I am afraid there were a few mishaps here. I can understand it is difficult for your first contributions.
Rule of thumb: do not abuse existing data, add a floating node instead if you want to add a missing place. (Nodes containing an address are solely for addresses and we are gradually moving them to map doors.)
Don’t worry, we fixed it.
node/12053843743
Happy mapping!

Hello,

I am afraid we have a double tagging issue here: way/1301155225 + node/4068473279 convey the same information with similar tags, that should not happen.

Also, please do not use dummy titles such as ".", "fixes" or "aanvulling" for most of your changes, it looks like obfuscation of what you are really doing, this is why your latest changes were flagged as potentially suspicious and set for review.

Happy mapping.

In dat geval, "source:maxspeed=BE-VLG:urban" is fout want dit is de tag voor 50 km/u.

Welke borden hier: zone 30 of C43 met "30"?

OK mais svp utiliser l'imagerie *numérique* et jamais les photos aériennes pour les bâtiments, afin d'avoir des contours corrects et qui ne changent pas à chaque nouvelle photo.

Il faut changer le fond de carte, voir bouton à droite de l'écran.

En Flandre, toujours "Digitaal Vlaanderen GRB" pour tracer les bâtiments. En Wallonie, "Imagerie numérique PICC SPW(allonie)". Merci.

Pour effacer une forme depuis l'éditeur iD : clic droit sur le contour de l'élément + icône Delete (poubelle).

Mais ici, comme la forme est toujours visible sur la carte GRB (référence officielle Vlaams Gewest) on peut changer le bâtiment en demolished:building=shed. C'est fait.

Thanks for this but please use correct tags for "species". Use recognised Latin names for the trees, this tag is not the place to store a common English name. I already fixed yesterday’s edit but I’ll let you fix this one.

Pardon my asking but if there are no maxspeed signs on a road, default values apply. Within the Brussels-Capital Region, the default speed is 30 km/h. What did you see exactly?
I am afraid we’ll have to revert this.

I fixed your subsequent edit.
FYI, when we write generic keys such as "demolished:highway=*", the star sign (*) is expected to be replaced with a value, not to be written as such on OSM data.
So, highway=trunk_link becomes demolished:highway=trunk_link, highway=primary becomes demolished:highway=primary and so on. ;-)
Don’t worry, it’s been fixed now.

Hello,
This is a comment about your review request here.
It looks fine but if roads are no longer open to vehicles and will be removed in the future, they might be better tagged as "demolished:highway=*" (or another lifecycle prefix).
This is because "highway=construction" is only for future roads (i.e. a road which is built for the first time). The tag is frequently abused for temporary closures during reconstruction, but I don’t think it makes sense if the road will be entirely removed from the map in a few months.
Have a nice day.

Hello,
Thanks for this but for a short-distance move, it is better to *move* the existing node instead of destroying one and recreating a new one beside. This will preserve the history of objects, which is good practice in OSM.
I will fix this one.

This changeset only cared to realign the polygon. This is routine maintenance work, as people using the online iD editor are often unaware of this when drawing. No information was lost: 5 nodes were touched, with a move of respectively 3, 7, 25, 28, and 28 cm.
OSM mappers are fully aware that UrbIS geometries are sometimes wrong or outdated, and that is why these cases can be documented on the object themselves, if necessary. That would prevent misunderstandings like here.

There is a 36-meter long elevated part stretching across the entire intersection. This is a fairly common case, and we map traffic_calming=table on the way itself rather than on a random node. This is what the changeset is about.
Here is a Mapillary pictures that shows the infrastructure.
https://www.mapillary.com/app/?pKey=823085459041912