OpenStreetMap logo OpenStreetMap

Changeset When Comment
141977216 over 2 years ago

Hello and welcome to OSM,

I saw a "review_requested" flag on your change.

You added wikidata and wikimedia_commons tag to an existing node. It looks fine, this is a good improvement.

Have a nice day.

141956124 over 2 years ago

Hello,

Many thanks for adding more data to OSM. I saw you did many changes today and it’s very good.

Just one thing: please do *not* add addresses on shops or amenities. We have already spent considerable time cleaning up all the addresses in Brussels so that they are only on buildings or doors, they should not be repeated because this corrupts the database when the same address is matched with several objects. Don’t worry, shops can still be found without that.

Thanks for this and happy mapping!

139764631 over 2 years ago

Reverted.

Duplicate of node/11108241805/history which you had previously.

141840537 over 2 years ago

Duplicate of node/11108241805

Reverted. Please update your map data before assuming something is missing.

141921826 over 2 years ago

Hello,

Thanks for spotting the change.
Next time, please start from the existing restaurant and change the name and details. Do not create a new restaurant next to it because it creates a misleading map, where it looks like there are two competing restaurants in the same building.

I fixed it.

141861241 over 2 years ago

Hello,

Here is one more tip: If you add addresses, please only add the street and housenumber. In Belgium it is not required (and not desired) to fill city and postcode. This is because there are existing catch-all areas, e.g. everything within this zone is automatically recognized as having postcode 1400
relation/5724100
;-)

141916641 over 2 years ago

Hello,

With respect, having a road with "service=parking_aisle" outside a parking area is incorrect.

I suggest you either draw an amenity=parking area here—probably with access=private, I guess they use it only to store new cars—or find a more suitable tag if the intention is to render them is smaller print.

141900912 over 2 years ago

Hello,

Can you please make sure to make smaller uploads in the future. I understand you want to fix several notes on the same day, but it will be more considerate to other mappers to upload those separately. This will avoid creating huge bounding boxes, like this one that spans over 7 different countries, despite you only edited 3 places in France and 1 on Germany.

Thanks in advance.

141834653 over 2 years ago

Reverted.

141793923 over 2 years ago

Super. Merci pour l’ajout, alors.

141793923 over 2 years ago

Bonjour et bienvenue.

D’après un autre utilisateur, ce passage à niveau a été supprimé définitivement il y a plusieurs mois, voir version précédente de l’objet.

Version #6
« Le passage à niveau a été supprimé par la SNCB, il n'est plus du tout possible de traverser les voies à cet endroit »
Edited 4 months ago by JChr

Quelle est la situation exacte, svp ? La fermeture était uniquement temporaire et vous avez vu le nouveau passage ? Ou est-ce juste un travail sur photos aériennes ?
Merci.

141793582 over 2 years ago

Hello,

The country code is not "missing".
It is just not needed. That is the primary reason why we never fill it in Belgium. Geoqueries can easily identify the country where a POI is located. There are very few places in the world where this tag is required.

Same goes for city names and postcodes, there is no need to repeat those values on every address or every point of interest.

(Example here for another set of changeset of yours: every object within this territory is automatically recognized as located in Isnes: relation/3521530 ; that is the advantage of a geographical database; it also preserves against typos because people occasionally make mistakes when filling postcodes or city names.)

Happy mapping.

141785367 over 2 years ago

Reverted (I made two separate changesets to avoid having a giant bounding box).

1) Mexico
changeset/141786777

2) Poland
changeset/141786921

141785367 over 2 years ago

This changeset is fantasy mapping.
Reverted.

141779096 over 2 years ago

With respect, the problem is not to know whether left and right exist on a one-way street. For instance, for parking tags, there is absolutely no problem with that. But when the "cycleway" tag is concerned, it is linked to the direction used by cycle traffic.

It is true that some people started using cycleway:right because of a bug in the CyclOSM renderer. For a strictly one-way street, cycleway and cycleway:right are synonymous, no problem for the :right tag alone.

141764893 over 2 years ago

Bonjour,

Merci mais attention à ne pas effacer les points.
Si un shop n'existe plus, enlever les informations du magasin et garder le point.
Ici, il y avait une erreur : quelqu'un avait ajouté le magasin de chocolat sur un point d'adresse, c'est donc très embêtant si on efface tout car alors ça efface toute adresse 84 de la rue.
Nous avons corrigé.
Vos autres modifications dans la rue sont très bonnes.

141761277 over 2 years ago

Hello,

Sorry but your changeset has been reverted.

There are several municipalities within the Brussels-Capital Region and sometimes the name of a street changes when crossing the border. This is exactly what happens here, because one municipality spells the Dutch name as Zeven Bunderslaan (two words) while the others spells it Zevenbunderslaan (one word). The border is here:
way/23544260

It was not a mistake, it is exactly because the local name changes, depending on where we are. (And yes, we also believe it is a silly situation and that municipalities should agree to rename streets in a more coherent manner.)

141760791 over 2 years ago

Thanks for spotting this.
Reminder: it’s better to keep existing nodes, so that we can re-use them (especially shops, which we use for research, to see how places evolve over time).
osm.wiki/Keep_the_history

141773953 over 2 years ago

Reverted

141773616 over 2 years ago

Fixed. A small convenience store is not the same as a supermarket. Please do not list them as supermarkets, we don’t want to create a misleading map.