Hello,
We don’t use addr:unit in Belgium.
If the address is "2A", then we write 2A for the number.

Hello,

Welcome and thanks for adding more information to the map.

I did some changes for this pharmacy (and for the other ones you added today).

Here are a few hints that can be helpful for your next contributions.

1) You can add the tags on the building outline _only_ if the entire building is a pharmacy. For this one, we have a large building with a private door and residents who live on the upper floors. Therefore, here we will not change the building but we add a single node within the building and put the information there.

2) Phone or fax numbers: we use the international format in OSM, i.e. +32 2 425 15 83. Not "02".

3) Writing postcodes and municipalities names is not necessary. Don’t bother about all the text boxes in the iD online editor: you do not have to fill everything: street name and house number is more than enough.

I fixed everything I could find. Don’t worry, we are all learning. ;-)

Hello,

Pardon my curiosity but this changeset contains much more than adding a new bus route.

It turns out you are renaming TEC bus route relations, and the main name of each route now contains either "[1]" or "[2]". I saw that practice used elsewhere on the TEC network.

I understand what this is about but it looks really ugly in various apps that rely on OSM data. Internal numbering of route variants is usually hidden from end users, that’s why we never do that elsewhere.

Is there a reason why you do that for Wallonia? Is this practice documented anywhere?

Thanks.

No problem, we are here to help.

I restored the former toy shop, which is now tagged as a vacant shop.

If a new shop opens, you can simply select that shop again and change it into the new shop, and then you can add the name, opening hours, contact details… and that will be fine.

Happy mapping.

Hello,

Thanks for updating the map.

Next time, if a shop or business closes down, please replace existing tags and use "shop=vacant" instead of deleting the node. That way, we can easily follow the various changes for an address over time.

(I was lucky to be able to restore this one from backups.)

Hello,

I guess this discussion is a follow-up of a comment on your changesets 118697660 or 118674078.

I get your point and I admit we a borderline case here. I recall a discussion we had within the community several years back. We found a consensus about using amenity=doctors here, because a clinic suggests something "stronger", i.e. getting some kind of treatment or even surgery.

The wiki has been modified more recently and other people may have different views on this. I wish to inform you I started a new discussion with fellow mappers to see if it would make sense to use "clinic" instead of "doctors". I have no personal preference here. I’ll get back to you in a few days. If we settle for clinic, it’s fine with me, and I’ll make sure we unify the tags to make the map better for everyone.

About your other questions:

1) key:healthcare is usually something very generic and gives the general idea of what the place is about (councelling, vaccination, rehab…) while healthcare:speciality would list everything. The way I understand how MM work, they have a broad collection of physicians and we should rather stick to something like centre or clinic.

2) Dual tagging is always a clever move… but it should be avoided for primary tags such as amenity. This is because there are hundreds of apps relying on this tag to render data, and most of them do not support dual tags. Sorry, the OSM data model can be really complicated sometimes.

Have a nice day.

Hello,

This is creating a strange duplicate, and the Brussels UrBIS reference does not have any housenumber for this building.

Housenumber 6B on Drève des Tumuli/Tumulidreef is already used on this building: way/226405416

You added a housenumber but did not associate it with a street. Did you mean this one is 6B on Clos des Chênes/Eikhove instead?

Thanks in advance.

Hello,

If you add those "maisons médicales", please use the correct tag, i.e. amenity=doctors. We do not label them as full-scale clinics, which they aren’t.

You could put the tags on the building itself only if the amenity occupies the entire building (i.e. there are no apartments or other businesses in the same building), otherwise just create a single point inside the building and add the tags to it.

Hope this helps.

You can type multiple values separated by semicolons if you want to list specialties. I tried to fix it.
way/253054370

Thanks. If you have the opportunity to check it in a couple of weeks that will be nice. Otherwise I’ll put it on my To-Do list as well.

Hello,

It looks like another user is active in this area and is setting bicycle=yes on several paths which you surveyed and tagged as bicycle=no.

Here are a few examples below. Could you please have a look. Then we can get in touch with that other mapper and ask whether he really checked.

way/524936894/history
way/571388044/history
way/527340150/history

Thanks.

Thanks for this.

Is the part that is now a footway exclusively for pedestrians or may cyclists legally use it too?

Hello,

Thanks for this.
Are there white signs that say "except bicycles" there? Because your change made it strictly one-way for all users.

Thanks in advance.

Hello,

Thanks for adding a restaurant here.

Can I encourage you to write more accurate titles for your changesets: just stating in a few words what the change is about.
Merely saying "update" is meaningless.

Otherwise, your changes are fine. :-)

Thanks.

Hello,

Out of courtesy to all the other mappers who are reviewing changesets, can I invite you to write better changeset titles for your edits.

We spotted several huge bounding boxes with a cryptic title—"Names"—every time. People are left to guess.

It looks like your latest changesets are about adding translations of cities X, Y and Z in Urdu. This is fine. In that case, just say that in the title of your changesets, that will be more helpful.

Have a nice day.

Hello,
I am not sure entrance #2 of the station is wheelchair-friendly. This one has only stairs and escalators; wheelmap users requested such situations to be treated as wheelchair=no.
Did something change here recently?

Proper access for people in wheelchairs is entrance #3, several meters east of this point.

Hello,

You created this node with housenumber 1
node/3476200717

There is already the same address on the other side of the road.
node/2472070347

Can you please have a second look?
Either the convenience store replaced the pub, or the address of the convenience store is incorrect.

Thanks in advance.

Hello,

Names with several " - " strings will be incorrectly parsed by the validator, which considers this to be where multilingual names are split.

In that case we usually use ndashes, e.g. "Commissariat de police 3 – Roodebeek - Politiecommissariaat 3 – Roodebeek". That way, there is only one hyphen in the middle to separate the FR and NL parts.

Hope this helps.

Hello,

There seems to be a few problems with your latest changes in this area. Could we please discuss it first?

I reviewed the geometry of building outlines in this street this afternoon to be sure they match UrbIS data—official government data we were licenced to use—and it looks like you moved houses again, away from that reference. What data source do you use?

Second question: how do you determine where to put the entrance nodes for those houses? Is that a survey?

In Belgium we usually add the addr:* tags to the building itself, unless there is more than one address for the same building, and in that case we use floating addr:* nodes within the building. Snapping those nodes to the building outline is very uncommon. Moreover, addr:housenumber is insufficient, we always use addr:street too even when there is an associatedStreet relation. Is there any documentation of the scheme you are following? We’d like to understand what is going on.

Thanks in advance.

Hello,

Just for the record: you added an invalid URL for the website. You must use the full URL including https://.

Also, the phone number was incorrect. Phone numbers in OpenStreetMap use the international format, hence always +32 2 ... instead of 02.

Anyway, the phone and URL were already on the object, it looks like you failed to look at existing tags and you just filled the text boxes in the baby editor without looking at the tags. This is a common newbie mistake.

One more thing: it is not necessary to repeat the postcode and city on every POI: we have existing zones that catch everything. I don’t want to start an edit war with you, therefore I left them, but do know that this is not necessary and just makes the database heavier.