Hello,

Thanks for the website and phone number of the restaurant, but please do not repeat addresses of places on objects. Addresses in Belgium are already mapped (on building outlines or floating address points). OSM is a geographical database, the map services automatically assign the address of any place, this is why duplicate addresses are not welcome.
Thanks, and happy mapping.

The address already exists on the container building, please do not repeat on the newsagent itself.
We reverted the edit.

Hello,

When a house number is correctly located within a building, its ref:UrbIS matches the id of the building.

But this is not the case here. The official ref:UrbIS attached to Rue au Bois/Bosstraat 365B is 5041433, and that may not be changed.

Should there be an error in UrbIS, the best practice is to document the change through another tag. Here is a standard tag I applied to several nodes (to make it easy to query them):
"note=Location established through a survey, despite UrbisAdm locates it in another building"

Hope this helps.

FYI, the places named "Au Primeur d’Etterbeek" and "Sandwicherie Picasso" were already added to the map… by yourself. They should not be added a second time through Organic Maps. We deleted the duplicates.

Hello,

Can you please make the extra effort to correctly snap objects to their neighbours? So that we’ll have less work of always redoing all your edits.

Example here: with this scrub slightly overlapping the adjacent parking area.
way/1321850434

## REVERTED
Reason: address already on the container building

Please type real changeset descriptions when you update the production database.

Typing a single dot (.) to evade the warnings make your edits look really suspicious.

Hello,

Why did you change this former church into an active "place of worship"? It is not an active church.

Hello,
Thanks for adding names.
It is recommended to write the names in a normal style on OSM. Even if business want to sound bigger by writing their names in capital letters, we do not apply this style on our map, otherwise the map would rapidly look ugly.
I will try to fix your various edits of the last hours.

OK, thanks.

Don’t forget to upload your changes, because so far the tags have not been modified, it looks like they are still in your own device and not pushed to the database.

Please use "building=house" and no name.
Please do not add "house" as a name.
The name tag is exclusively for objects that really have a name. We don’t use this to describe objects.

Hello,

I don’t think that "(formally Foto Gregor)" should be part of the name, unless it is explicitely marked as being the name. Was this the case here?

Should there really be a need to mark the former name of a place in OSM, you should use the "old_name" key.

Hello,

Is "Red Jurassic - Dental Treatment and Orthodontics of Dinosaurs" a real name?
node/12222708701/history

On Mapillary (https://www.mapillary.com/app/?pKey=1902062726942257) I see Orthodental Red Jurassic.

If it is a joke name, please do not upload that to OSM.

Would you mind explaining what you saw here? Thanks in advance.

Your changeset title says "Building".

This is a really lame description which provides no real content. Please be aware that contributions on OSM are public and other users are affected by your actions. We expect users to write meaningful titles, as courtesy to fellow mappers.

Another problem: instead of mapping a building, you drew a simple polygon with "area=yes" as its tags. Such a shape will not be rendered, it just clutters the map. I am sure you have good intentions, perhaps it would be useful to redo the tutorial or read the wiki to learn a bit more about OSM works.

Kind regards.

Ne pas ajouter les arrêts n'importe comment dans la relation bus, svp. Il faut toujours veiller à garder les arrêts dans le bon ordre. Vous avez mis l’arrêt Tournai Rue Royale tout à la fin de la liste, c’est incorrect.
Votre edit a cassé 3 relations : 11978933 + 11962495 + 11962313

Pour rappel

1) Ne pas attacher les landuses aux routes ou aux chemins. Vos changements sont une véritable plaie à nettoyer.
Exemple de nœud commun : node/12216489245

2) Éviter nesting et overlap des zones landuse (sorry, je ne connais pas le mot français), exemple way/1320132279 croise et déborde d'une autre zone, ou way/223296370 industrial dans une autre zone industrial et avec des débordements.

Please redo or revert.

Hello,

Please no forcing of address tags on POI in Belgium. Addresses are already on the map. Next time, please just add a point and it will be fine.
We fixed your edit.

Hello,

Adding or updating shops is great, but please do NOT steal UrbIS address points to transform them into shops.
Found a new shop? Great, add new node near the location, no more. The links between shops and addresses is computed automatically nowadays, so no need to repeat address tags or merge objects.

Also, if a shop is gone, do NOT erase the point from the database. You can remove the shop-related tags. We usually use "shop=vacant" so that it will automatically be recognised as empty

I tried to repair everything here, while keeping your changes.

Thanks in advance.

Hello,

I wish to inform you that in Belgium we never repeat postcodes or city names on every possible address or POI. This is because we successfully drew all the postcode areas; this also provides a safer system than relying on every mapper to guess the full address. (Yes, in this country some areas have strange shape and people can easily get this wrong; we chose this system as a response to massive data corruption.)

See an example here: every point within this area is automatically understood has having postcode 1000, this is the reason why we don't repeat it.
relation/3379410

Happy mapping.

SVP ne pas utiliser les points d’adresses pour ajouter des éléments.
Créer des points à part pour les deux restaurants. Les adresses seront automaticallement calculées par la database.
Nous allons effacer vos changements.