Hello,

It would be more beneficial to map users if you could please write bus stop names with the proper case.

I am aware that TEC does a very strange thing on their website/app/GTFS data, i.e. they write towns names in all-caps and without accented characters.

But this is not how we map in OSM: our responsability as mappers is to clean up those names and write them properly, i.e. not a screaming "VILLERS-SAINT-AMAND Église" but "Villers-Saint-Amand Église".

Thanks in advance.

Hello,

Is this a crossing?
way/1225853033

Looks more like a traffic hump, and footway connectors here are not necessary since there are proper zebra crossings nearby.
(Also, crossing:island=yes means there is a refuse for pedestrians in the middle, I don’t see any here.)

What do you think?

We fixed it.

Bonjour,

Ceci est un commentaire après examen de vos modifications sur OpenStreetMap.

Deux conseils d'amélioration :

1) Quand un magasin ferme, il faut uniquement retirer les tags. Mais ne pas détruire l’objet lui-même, ça doit rester dans la database ("keep the history" principle).

2) Svp ne pas ajouter des adresses sur le bâtiment. Le grand bâtiment contient déjà 4 addresses : 157 157A 159 161, il ne faut pas ajouter en plus de ça une adresse "161" sur le contour du bâtiment, ce n'est pas correct.

Merci.

Merci mais ne pas ajouter les adresses sur les magasins, les adresses sont déjà sur la carte.

Hello,

Thanks for this but I wonder about this node:
node/11487030963

ref=Poste 36 kV Pêcherie
Is this a valid tag for a ref? Description, probably.

OK, I’ll fix it.

Hello,

AFAIK, there is no legal restriction against cycling here (southbound road)
way/31428753
Sure, it is for the mighty, and a careful cyclist will prefer to use the service road next to the bus depot, but I don’t think a restriction is a appropriate.

The opposite direction should not be taken as an example because the northbound road has a D10 sign on the sidewalk, which legally forbids to cycle on the road. There is no such sign on the southbound road.

Hello,

associatedStreet relations are a special type of relation used to create a logical connection between addresses and named roads. Please do not tamper with them. In particular, please do not add sidewalks into those relations.

Have a nice day.

Hello,

Why did you change the "network" tag for TEC route 84 from TECX into TECL?

(relation/15828348 + its 2 child-relations)

I believe this is incorrect. TEC’s public transport network is split into 5 operating entities, with proper codes, and TECX is for Namur-Luxembourg area (TECL is only for routes in Liège area and they are coded differently). Maybe you would be so kind as to explain the reason for this change.

Thanks in advance.

Hello,

Thanks for this. I have reviewed and fixed some of your latest edits.

Can I please suggest to turn on the "Prefer contact prefix" option in the settings of the Every Door app. This will ensure that when you add a phone number to a POI, it gets the modern tagging convention.

Don’t worry, I’ve already fixed this one.

Hello,
It looks like you managed to upload this changeset on midnight (GMT), making it the very first change in 2024 in the database. Congrats!

Hello,

There is already a Lebanese restaurant in this building.
node/9713094717

In your edit, you added NYYÓ as if it was a second restaurant in the same house. This would be very surprising. I suppose you wanted to replace the existing object instead of creating a new one.

I can fix it but could you please tell us what you saw here?

Hello,

I guess someone may have told you already but please never trace on aerial imagery for buildings or walls between properties. We have to redo all your edits and it takes much more time cleaning someone else’s mistakes than to do it right the first time. :-(

In the Brussels-Capital Region, please use UrbisAdm (URBIS numerical imagery).

Thanks in advance.

Hello,

I don’t understand your edit.

There is a "site relation" in OSM which already stores information about artist, dimension and more
relation/14727703

In your edit, you added the same information on one single element of that fountain. Duplicating information in a database is something we strive to avoid.

Could you please explain what was the intention here. We’d like to clean this up.

Do they? They are named after the former place that no longer exists.

Perhaps it would be more appropriate to rename the Wikidata and Commons entries, then we can link to them again. Or, if what is required is to show a picture of the building (regardless of the café currently operating it), perhaps just the image tag might be appropriate.

Bonjour,

Merci pour les ajouts. Question : quelle est la source de données pour ces arbres ? C'est un import de base de données de quelque part ou un travail 100 % sur vos propres relevés ? Ou juste un travail sur les photos aériennes ?

Hello,

Do those streams have to be written entirely in lower case? Anything special about those names?

Hello, and congrats for a nice first edit on OpenStreetMap with a very clear description.

Hello,

Next time, would you please be so kind and upload changes like this in smaller blocks.

Adding 27 objects at once on various places all over the Netherlands generate a fairly large bounding box spanning over several cities in the Ruhr area in Germany as well as about 1/4 of Belgium. This is unnecessarily annoying for mappers in other regions.

(On an unrelated note: it is unlikely you surveyed those 27 locations yourself, it looks like you are probably importing an existing government dataset here (osm.wiki/Import/Guidelines).