Hello,

Next time, please create a single point inside the building instead of putting the tags directly on the building outline.

You told the map: "This entire building is a huge pharmacy."

Don’t worry, I fixed this one.

You might consider using the following tag here:
amenity=parcel_locker

Please *either* undo your edit (by restoring amenity=vending_machine, which is a required tag for the vending key here) *or* use the suggested scheme. The current set of tags you left is broken, making this point essentially useless.

Hello,

It would probably make more sense to set layer=1 on railway features and leave the small road at level 0.

I always feel uncomfortable when people put "tunnel" tags to objects that are not really tunnels, e.g. it makes it impossible to query the OSM database and get the number of kilometers of tunnels we have in the city.

Technically, it is a normal road going across the railway "hill", while the railway line is really on another level, exactly like when the railway is on a bridge.

What do you think?

That being said, the main issue in this area would be to make sure roads are in the correct direction and whether cyclists may use it in both directions.

I see several roads that are tagged as strictly one-way, which is quite rare in Flanders, but it’s possible for streets that are really too narrow. If you have local knowledge and are willing to help, it might be useful to check the streets in that area to be sure that the map reflects the legal situation.

(oneway=yes + oneway:bicycle=no is the combination of tags to use for streets with the white "uitgezonderd fietsers" signs.)

Not really, in fact.

If there are F111 signs, adding cyclestreet=yes is enough. The rest is automatically implied. That’s what we call "implicit tags" in OSM. (For instance, if you draw a road as highway=motorway, it is not necessary to add motor_vehicle=yes, bicycle=no, foot=no… on every road because that is the normal and documented behaviour.)

What the wiki actually says is that if we _explicitely_ want to tag a cyclestreet will all the tags, it should have things like overtaking:motor_vehicle=no and more.

Don’t bother too much with those ones: good navigation software which sees cyclestreet=yes on a road should know that in Belgium the speed can never be higher than 30 kph and that overtaking is prohibited.

The original comment was especially to comment about the "overtaking:bicycle" tag because that was a mistake, which is now fixed.

Hello,

Would you please be so kind to explain why a name such as "Basiliek van Onze-Lieve-Vrouw" would trigger a "profanity" warning and a name change.

(I don’t object the name change itself, I just want to know why those hashtags have been added to your changesets.)

"maxlength=10" is correct.
Well done!

(In case there would be additional signs stating that longer trucks are allowed to enter if they are going specifically to this street, then there is an extra tag to add:
"maxlength:conditional = no @ destination")

On the latest Mapillary pictures we took (January 2022) there was no such lane.
https://www.mapillary.com/app/?pKey=763400435062488

If it was painted recently, indeed we can add it. As a matter of fact, I was preparing to survey it myself in the coming days, to be sure. This is because cycle infrastructure in Brussels is changing really fast.

Only bicycle logos, colour or V-signs: cycleway:left=shared_lane

Dashed lines: cycleway:left=opposite_lane

OK, I get your explanation.

Indeed, your edit was flagged as suspicious because it broke the continuity of existing highway types.

Hello,

I am sure you want to make helpful edits but you are not using the right tags.
Tagging proper cycle infrastructure is a bit tricky and in some of your latest edits such as this one, or Rue Maurice/Mauricestraat, you are actually REMOVING bicycle access.
We suddenly got negative comments about broken itineraries in this area, because of the changes you made.

Here is how OSM data model works:
* oneway=yes means that a street is a one-way street → this applies to all vehicles by default (cars, bicycles)
* oneway:bicycle=no means that cyclists are exempted from the one-way restriction.

Therefore, the typical combination found in Brussels with a white M2 sign ("except for bicycles") translates as "oneway=yes + oneway:bicycle=no" in OSM.

I see you are putting "oneway:bicycle=yes"… which means the opposite (with oneway:bicycle=yes, cycling is entirely forbidden in the contraflow direction, notwithstanding the cycleway tags you are adding).

I felt I had to tell you.

Hello,

I spotted your edit here.

I am also interested in finding a good way to map those charging stations, because there are more of them every month. It’s nice if someone took the time to set up standards. Up to know, we have been using set up by MapComplete and added some tags found in the wiki (e.g. socket:type).

My question is: where can one find the recommendations you are refering to?
Also, according to this, charge.brussels is the network but also the _name_ of each station?

The changeset here is not about this.
In this changeset, we added 4-digit ref numbers to the metro platforms themselves.

What you are talking about is that stations also have a 2-digit identifier on their own. In the past we used to have the ref numbers on the station nodes, until user Zverik complained and urged to have them removed. I believe restoring them would be interesting, using ref:STIB_MIVB.
I’ll put this to my To-Do list.

Hello,

If you want to import ref numbers for the T-bus service, I request that you do not erase valid ref numbers for the tram stops, as you did here.

Despite the tram is temporarily not operated here, it should remain untouched on OSM: OpenStreetMap is not (solely) a map for day-to-day status of the network but we offer a view about the normal situation as well.

Hello,

Thanks for editing OpenStreetMap.

Is there really a cafe inside the building with housenumber 33? I tried to look at mapillary imagery and couldn’t find a cafe here. That’s why I’d like to check with you first if this was intended to be a real edit or just a test.

Looking forward to your reply.

Hello,

This is a tram-only stop here, the infrastructure makes it physically impossible for buses to run along the infrastructure.

Looks like one more mistake in the GTFS feed. You’re not blindly applying the GTFS onto OpenStreetMap, are you?

What bus line did you spot here, please?

I see a speed cushion in one direction (traffic_calming=cushion + direction=backward) but no traffic island.
https://www.mapillary.com/app/?pKey=284821247065059

Has the situation changed since this picture?

I am saying this because the history of some nodes suggests you added all those tags in this changeset.
node/2345001271/history

On second thought, perhaps you just merged two nodes and didn’t type those addr:* tags yourself. In that case, you are not the one who did the mistake. ;-)

No need to manually add extra tags like this on every node

addr:city=Bruxelles - Brussel
addr:country=BE
addr:postcode=1000

Those nodes belong to an associatedStreet relation.
Relations have been invented precisely for this purpose: to avoid duplicating the same information hundreds of time.

Not sure the address of the "frituur" is correct. I bet housenumber 180 belongs to Rue de Laeken - Lakensestraat.

We are currently processing and reviewing all the stops to ensure this key will be set properly.