Thanks for this.

One recommandation: even if corporate websites like writing names in ALL CAPS to sound bigger, we do not do this on OSM. We can keep KBC with upper letters, but words like Brussels and Bizet should be written in normal case when you add data to OSM.

I will fix this one.

Hello,

Thanks for adding more details here.
Are you planning to put in more work here? I am asking because your changeset was flagged with a large number of warnings of ways incorrectly crossing each other. Perhaps this is only a temporary situation, which you were planning to clean up in the next days.

Also, I cannot help but notice illogical situations, like this footway being connected to the outline of the parking area (node/12849517905). Routing won’t work correctly unless it is connected to a road or another footway.
Same for this orphan node (node/12849517948) and several others.
When footways cannot be connected to anything, standard mapping practice in OSM is not to map them and stop at the previous junction.

One more thing: you set way/1388080077 and node/12849517908 as having no markings… whereas the latest available imagery (both UrbIS and Digitaal Vlaanderen) clearly shows proper zebra marks. In case you use other data sources (e.g. a recent survey) it is better to mention this explicitely in the changeset source field, otherwise people will raise questions about your changes.

Thanks in advance.

Bonjour,

Le nom français sur le site https://monument.heritage.brussels/fr/Schaerbeek/Avenue_Louis_Bertrand/A001/21740 est « Vase Bacchanala » et l'article donne « Vase aux Bacchantes ». C’est différent de votre addition. Avez-vous svp une source à proposer pour votre changement ?

Aussi, pourquoi changer uniquement le champ name:fr et pas le champ name ? À cause de ça, il y a une erreur de validation. Quel nom retenir ici svp ?

Hello.

The previous situation seemed correct, i.e. linking the place in Kinshasa as the etymology for this neighbourhood in Brussels.

Your edit adds the same value for wikidata and the etymology, which creates a self-reference.

name:etymology:wikidata=Q900749
wikidata=Q900749
both point to the same article, they shouldn’t.

And a second piece of advice here: making one separate upload for each topic is recommended. For instance, do one upload to change the speed limit in one place, and upload that. Then, move on and redraw a road elsewhere. It will makes review of your changes much easier, in particular if you provide a clear explanation in the title (thus, not "did some fixes" but "I redrew 2 roads to match the latest aerial imagery")

Hello,

I saw you requested a review here.

My first advice would be to gain a little more experience in mapping before claiming to correct "map errors". This changeset seems to have created more errors; I spotted a road which had an incorrect structure and broke the continuity of all the bus- and cycle relations on it. As you can see in the summary, the iD editor sent you some warnings about your changes, like highways crossing each other, which you ignored.

Don’t worry, everything has been repaired and the useful part of your changes have been kept.

Have a nice day.

@simpliston. Yes, the problem is about the way Organic Maps computes addresses. We see that problem very often: this app is able to associate a show with an address if the container building has address tags but does not recognize addresses as nodes… despite every geographical-aware application should. (Especially because Norway, Denmark, Netherlands and other countries exclusively use nodes for addresses).

I understand the frustration as a user, but the best we can do it get Organic Maps devs to fix their app instead of changing data all over the world.

Hello,

There might be a validation problem here.

I see you merged stop_area relations and have one single relation to group all the stops. I won’t reopen this eternal debate but at least inform you of something: "name:operator:TEC" is not the same for tram and bus stops here, as I can see, so it should either be removed from the relation, or you should have separate relations for each mode of transport.

That said, the current practice in Belgium is one platform = one relation, it might sound complicated to some but is much easier to unambiguously pair stop position nodes with the platform. I recommend you would keep to this established practice.

Thanks.

Hello,

Addresses should not be added on POI, especially in Norway, where there is already a structured process to keep the address inventory clean and in sync with government data.
osm.wiki/Import/Catalogue/Address_import_for_Norway#Tagging_scheme

Also, please make sure to upload changes separately, especially when editing places in different countries or continents. As a consequence of sending your edits in Mexico and Norway as one single upload, your changes are now showing as a huge bounding box covering most of Europe and Northern America.
osm.wiki/Changeset#Geographical_size_of_changesets

Thanks in advance.

Hello,

I see a large number of edits where you added names of cities all over the world in various—and obviously non-local—languages.

Do I understand that you copied names from Wikipedia into OSM?

Should that be so, this is not a good idea. Having a link to the wikidata entry is enough, and the name in every language can be retrieved from there without being duplicated in OSM.

But more importantly for licencing reasons.

osm.wiki/Collaboration_with_Wikipedia
Do not copy any information from Wikipedia into OSM. Wikipedia is licensed under CC BY-SA 3.0 which is incompatible with OSM.

Kind regards.

Hello.

If you want to redraw a forest outline in Chile and one in Norway, please make sure to always upload them separately.

Making one single upload for both actions renders your edit as a giant area on the map, covering several continents at once.
osm.wiki/Changeset#Geographical_size_of_changesets

Thanks for the change.
However, please do not add addresses to places, because that would create unwanted duplicate information on the map. It is not needed. In particular, you may want to know that Brussels is a bilingual city where addresses are always written in both languages and you wrote a French-only address.
Don’t worry, we fixed everything here.

Hello,

While adding a path in Geneva, you also inadvertently dragged a tree and a fast food restaurant in Rotterdam to random locations. That explains this giant bounding box spanning from the Netherlands to Switzerland.

I reverted the changes in Rotterdam.

Hello.

Is "Sortie P1 VIP" an official name for this road? way/1386128751

It looks very unlikely the name would be in French.

Perhaps this should be moved to the "description" field. Names are for real names only.

SVP ne pas ajouter des adresses en double, les adresses sont déjà sur la carte. Uniquement le point relevant pour Croix-Rouge avec les tags et nous pouvons lier avec une adresse existante.

### REVERTED

You added a duplicate POI for this clothes shop, after having uploaded it 2 hours earlier on the same day.
node/12819086502/history

The duplicate item has been reverted.

Hello @NguyenChuong.

Can we please request that you type correct description when you push data into the OSM database.

We saw a large number of edits by you, which you titled "Changes" or "Add". This is not a correct way to describe your actions. Especially not saying that you "add" things when you massively delete buildings like in this changeset. (I do not object against erasing old buildings, but please describe correctly what to expect with your changes.)
osm.wiki/Good_changeset_comments

Thanks in advance, and happy mapping!

Hello,

It looks like you added another bag shop with the same name a few days earlier: node/12751721901

Either there really are two RSVP Paris facing each other, or one of them should be removed. Can you please review your edits and fix the map accordingly.

Hello,
Thanks for adding a clothes shop.
Please ALWAYS write a description when you push data to the OSM database. It is not acceptable to leave this field blank, as if you wanted to hide what you are doing.
Thanks in advance.

Thanks for the reply.

The primary reason not to repeat the same information is that OSM is a geographical database. Doing so guarantees better data consistency. This is particularly true in a place like Brussels with multilingual street names.

I understand that some people would prefer that every POI contained all the information, to obtain everything with a single query.

Most reverse geocoders automatically understand address inheritance, for instance Nominatim, which will automatically obtain the address of the container building (way/228248709) but also post code areas, nearest city node, country, etc.

Have a nice day.