OK, explication ici :

Quand vous êtes dans l'éditeur, il faut aller cliquer sur un des boutons de la barre de menu à la droite de l’écran.

C’est le bouton "Background Settings".
Le choix par défaut est "AIV Flanders most recent aerial imagery" → descendre dans la liste pour trouver "AIV Flanders GRB".

Happy mapping.

Hello,

This message is to warn you that you are putting incorrect information in the database.

Please read this message carefully. I also wrote to you yesterday, this is a second attempt to warn you.

This shape is really weird:
way/1178619614
It looks like you used the curved image of the gabled roof as if the building was making a dent. This is unfortunately wrong.

The hedges are poorly located, I fear some other mappers will have to erase all your edits and start again.

As we already advised, please learn how OSM works before submitting work to the database. Also, if you want to use the online editor to add buildings and separators, please switch to "AIV Flanders GRB" background. Do NOT trace buildings on aerial imagery.

Dit gebouw lijkt veel groter dan het in werkelijkheid is. 432 m², echt?
way/1178033234
Ben je zeker van de vorm van dit gebouw? Hoe heb je het getekend?

Bonjour,
Il faut utiliser le fond de carte AIV Flanders GRB pour les bâtiments svp.
Aussi utile pour les haies, pour aligner sur les limites des propriétés, car ici vous avez tout dessiné sur des photos aériennes et vos bâtiments et haies sont tout à fait décalés et ne sont pas conformes à la réalité.
Merci.

Bonjour,
C’est bien mais c'est étonnant que vos éditions utilisent l'image aérienne de la Flandre (AIV Flanders) alors qu'il y a moyen d'utiliser les images UrbIS pour Bruxelles, qui sont plus récentes et plus précises.
Et peut-être essayer de mieux aligner les arbres : le point doit être mis évidemment à la base du tronc et non sur l'image (déformée) du feuillage, sinon ça oblige les autres à tout corriger après vous.

Hello,

Adding trees to the map is a nice thing.

But it may raise a few questions to avoid clashing with existing data and to prevent legal issues, e.g. database rights.

Where does this inventory of trees come from? Are you trying to import an existing database into OSM? Or did you survey all those trees yourself? Or are you working from aerial imagery?

Thanks in advance.

Bonjour,

Ne pas ajouter manuellement les codes postaux et localités sur les objets, svp.

Par exemple CP 6670 est automatiquement attribué à tout ce qui est dans cette zone.
relation/12901770

(The reason you see it is that the online editor is a very simple editor and can be used worldwide… but in Belgium we already have catch-all zones to avoid duplicating all the info, so we leave the fields blank.)

@Palgrave Peter: The recommended way is to hit the upload button in StreetComplete *before* moving on to another territory.

It looks like you had solved some quests in Cyprus, which you hadn’t uploaded, and then you used StreetComplete again in London… uploading past and current changes at the same time. That explains why your changes create a huge bounding box that spans across most of Europe. This is an annoyance for thousands of mappers.

Hope this helps.

Hello,

I saw you wanted a review.

Thanks for caring about the map. Sadly, we had to undo your change.

First, because other mappers already had implemented the change. We surveyed it recently and spotted the signs along the roundabout, confirming that the road itself was named after Mounia Ouyahia. It is not necessary to add a name to the small green space in the middle.

Also, street names in Brussels always have to be written in both official languages: French and Dutch.

--
(Original version in English. French translation provided by deepl.com)

Bonjour,

J'ai vu que vous vouliez une évaluation.

Merci de vous soucier de la carte. Malheureusement, nous avons dû annuler votre changement.

Tout d'abord, parce que d'autres cartographes avaient déjà effectué le changement. Nous l'avons arpentée récemment et avons repéré les panneaux le long du rond-point, confirmant que la route elle-même portait le nom de Mounia Ouyahia. Il n'est pas nécessaire d'ajouter un nom au petit espace vert situé au milieu.

Par ailleurs, les noms de rue à Bruxelles doivent toujours être écrits dans les deux langues officielles : le français et le néerlandais.

Hello,

The previous changeset stated the situation quite explicitely.

"Ferry to Île Robinson/Robinsoneiland - vehicle=no instead of motor_vehicle to also exclude bicycles from using that service (follow-up of changeset/117426678) "

"motor_vehicle" is a subset of "vehicle". What was the idea about adding it? Is there a special requirement or apps that are unable to deal with the "vehicle" key?

OK, it looks fine, well done.

Hello,

The cycleway you are talking about was not created by me (you may have seen my username on it but it’s because I split a longer way to solve an unrelated problem, and upon doing so the database generates new ways and starts numbering at version 1 even though they had been on the map before.)

So, if I understand correctly, what you are saying is that we should remove way/1053473710 entirely and remove bicycle-related tags on way/531210486 to make it only for pedestrians. If that matches the local situation better, yes it’s definitely a good idea. Routing will work fine along normal roads. I can do the changes if you want.

While you are at it, there seems to be an issue with cycle routing. Starting from the point we are talking about, how can a cyclist reach this point?
node/2063613677

This look like a fake hospital node near an existing hospital.
node/10933561605

"Dfff temp", "Temp vg" and "Temp1" do not seem to be real names.

Sorry, the comment was aimed at the note. Your changeset is fine.

way/1176636854

No name on trees please.

Filling the "species" tag with the latin name is the best way to describe a tree.

Only a handful remarkable trees have their own and unique name.

Hello,

Thanks for adding more information about trees.

A bit of a warning: "wikidata" or "wikipedia" links are to be used exclusively if there is a corresponding entry about the object itself.

For instance, if there is a particularly remarkable tree that has its own wikipedia entry, then it is eligible. (This is very rare, apparently there are only 3 such objects in Belgium, here is one of them: https://nl.wikipedia.org/wiki/Linde_van_Conjoux)

For most trees, you should definitely not associate them through those tags.

You can use "species.wikidata" for this.

Some useful documentation here: species:wikidata=*

I surveyed it this evening and I can confirm that the street has NOT changed. All the C43 roadsigns granting a 50 kph maxspeed are still there. You can see some pictures in the note here:
note/3702883

Maybe you changed the map after reading that the government *intends* to lower the speed regime. However, OpenStreetMap only maps ground truth and at the moment this street still has roadsigns.

I will undo your edit.

Hello,

I passed by on Saturday and I confirm that the 50 kph speed signs were still there.

Major contributions on a first edit always raise a little suspicion.

Can you please confirm you saw that the new speed regime has really been changed. Did you see it with your own eyes? Or can you provide a link to a news article, because I couldn’t find any.

Many thanks.

Hello,

It is always a good idea to look at the history of objects before editing them.

This changeset reintroduces a mistake we had just cleaned up some time ago.
way/27838600/history

Let me explain.

If we declare a path as a footway (highway=footway), it will automatically get "yes" for pedestrians and "no" for everyone else (cyclists, horse riders, cars…).
Any (good) router is asked to adhere to this list of values.
osm.wiki/OSM_tags_for_routing/Access_restrictions#Belgium

You can create an exception when… there is an exception to the rule, e.g. if a footway is shared with cyclists, having "highway=footway" + "bicycle=yes" is fine.

But applying an exception to repeat the normal rule (i.e. "bicycle=no" on a footway) is just disturbing and a waste of time, for you and also for other mappers who endlessly have to come across the reports about the issue. Should the problem come because you found one routing algorithm somewhere that incorrectly assumes footways are for cyclists, then the problem must be solved upstream and not by manually adding entries to OSM data.

Hope this helps.
Have a nice day.