Hello,

Here is a review on your changeset.

This area was tagged as a parking lane (amenity=parking + parking=lane), which you changed into a Cambio car-sharing station.

Mapping such a station as an area is okay but while you (correctly) changed the amenity tag, it looks like you forgot to remove "parking=lane". This tag is still there among the properties of the car-sharing station, and this is a strange mix.

There is also an issue with names. I know that the strange spelling here comes from Cambio’s website. Brussels is a multilingual city. You may have noticed that we consistently use the " - " (space hyphen space) text string to separate the languages, and not "/" (slash). So, we’d better write it "Cerisier - Kerserenlaan". The way we write multilingual names is as such: bilingual name as "name", then we take each part and fill "name:fr" and "name:nl", each one having the corresponding part.

Feel free to reply if you need more details. You may want to fix the situation yourself here. I’ll put this object to my watchlist and will fix it later this week in case you don’t come back here.

Have a nice day.

Hello,

I saw you wanted a review about this changeset.

Thanks for adding this shop.
However, repeating addresses on places is heavily discouraged; we are working hard to keep the addressing system clean, so please do not add them. OSM is a geographical database, and getting the address of a place is fairly trivial, that is one of the reasons why information should never be duplicated.

Happy mapping.

This changeset issued a warning because "ref" is not recognized on bus stops in Belgium.

If this is a stop by De Lijn, you should use "ref:De_Lijn" to store the code. It is advised to type the tags directly in the list; do not use the text boxes in the baby editor because that won’t give you the correct tags.

Thanks for your attention.

Hello,

Thanks for this. We erased the bpost post office because this place was already on the map: node/12400253640/history

The other node was created 24 days ago. I have seen this problem before, with Organic Map users not realizing some data was already on the map because they use an outdated local copy of the map. You may want to check and refresh your local data before your next edit.

Thanks.

You are welcome.

Hello,

You can group the various names in the same alt_name field, with the semicolon (;) separator between them. The various tools in the OSM ecosystem that use alt_name will index each part on its own.

The "short_name" key is, as the name says, only for a shortened version of a name, for instance when a place has an acronym. Please do not add alternative names here if they do not qualify as a short name.

Also, please bear in mind that Brussels is a bilingual region. Since I see that you are new, I will consider that this is just a beginner’s mistake and not a deliberate act of vandalism, but please use a bilingual version of the name as the main name tag for this skatepark.

Thanks.

Hello, and welcome to OSM.

We fixed your edit to indicate the place as a floating node instead of mixing it with the building outline.
node/12460933253

It looks like this is your own place, so can you please confirm that "English Speaking Physio" is the official name of this business? We are asking because people frequently write descriptions instead of names, so we want to be sure.

Thanks in advance.

Bonjour,

Merci pour l'ajout de maisons mais attention, il y a une erreur car on dirait que vous utilisez les photos aériennes pour tracer les contours. On ne peut pas faire ça pour les bâtiments.

Pour obtenir la forme correcte d'une maison, uniquement la carte "PICC SPW(allonie)" est valable. Quand vous êtes dans l'éditeur, cliquez sur B pour ouvrir le menu Backgrounds et changer le fond de carte.

Là, vous aurez la forme exacte sans la distorsion des photos. 😉

Hello,

Why did you change the network tag on route relations? By doing so, you are breaking queries that rely on this tag. Network and operator tags are two separate concepts in OSM, they should not be mixed.

It looks like an undiscussed edit. It should be reverted.

Did someone ask you to do this? Please reply within this thread.

Thanks in advance.

### REVERTED

Hello,
Your changeset has been reverted.
No tests in the production database, please.

Should there be a welcome sign somewhere here, you can map it but in that case please create a new floating node for it instead of adding tags to a node that belongs to footpaths.

Have a nice day.

The bar and the restaurant have the same name (and the same organisation behind them) but are two different objects for OSM.

No address duplicates on POI in Belgium, please.

We will revert your changes.

Hello,

Whereas adding "further information" is always welcome, please do NOT add address duplicates on points. All the addresses within the Brussels-Capital Region are already mapped separately, they should not be repeated; this is too error-prone and might end up corrupting the database.

This changeset is a sad example of this: add:city is incorrect because this area is Saint-Josse-ten-Noode - Sint-Joost-ten-Node and not Bruxelles - Brussel.

We will clean up.

Hello,

Thanks for the various updates here.

One important thing: if "shrubbery" is more appropriate, you should not change its category solely to have it appear on some given renderer (in particular osm-carto, which is the default view on osm.org).

natural=shrubbery is rendered on other maps using OSM data. osm.wiki/Tagging_for_the_renderer

Bonjour,

Un petit conseil pour vos contributions sur OSM : mettre un titre qui corresponde fidèlement au contenu.

« Ajout de lampadaires » signifie que vous ajoutez des lampadaires.

Je vois que le changement ici contient aussi un changement de forme d'un trottoir (way/535186770) + la création d'un stationnement (way/1345993450).

+ Essayer de faire des changements sur des zones plus petites car le stationnement est à 1,6 km du lampadaire. Bonne pratique = changements pour un thème et un endroit précis. C'est plus facile quand nous examinons. Merci.

Hello,

Please do not draw houses on aerial imagery, those images do not show the correct shape of buildings.

When you open the editor, click the "Background" button and scroll down to "Digitaal Vlaanderen GRB". You can safely use this to trace buildings.

Yes, removing the 5 addr:* tags from the node is the best option.

Hello, and welcome to OSM.

Please do not repeat addresses on restaurants (or shops, amenities…); addresses are already on the database and the POI was linked to it. I will fix your edit.

Hello,

The address in automatically computed from the container building (street and house number)
way/142694409

And the postcode and municipality is automatically computed by the existing areas.

This is the reason why in most cases this information should never be duplicated on shops themselves.

Hello,

Is this problem with the router documented? Should there be such a problem ("bicycle=no" on nodes is only relevant on Key:barrier but should be ignored elsewhere, in particular "highway=crossing", which only means that no cycle path crosses here), the normal way would be to fix the issue directly in the routing engine instead of changing the underlying data.

AFAIK, there are thousands of crossing nodes with "bicycle=no" in Belgium, especially now that MapComplete adds it.

Thanks in advance.