Hello and welcome to OSM.

Can I please suggest you upload your changes from one place *before* editing a place in another country.

Both this changeset and the one from yesterday (with one part in the UK and one part in Congo) are way too large: this create huge boxes entirely covering other countries and unnecessarily cluttering the workflow of all mappers who live in between.

Hope this helps.

My concern is primarily that information duplication inside a database is to be avoided whenever possible. 10 years ago, we filled those tags everywhere but current practice in Belgium has changed.

Nominatim natively gets any full address, so do mobile apps such as OsmAnd~ or Organic Maps (they even work fine for POIs with only addr:housenumber and inheritance of all the other tags from an associatedStreet relation). Likewise, we do not add "addr:country=BE" either.

Thanks for the link to the geoportal for WalOnMap. Indeed, they seem to be oblivious of accented capital letters.

Anyway, I am not here to tell you what to do: do as you please. Other mappers will probably want to clean this up one day.

Have a nice day.

One more time, please: highway=pedestrian MUST have a name.

That being said, I have the impression you are hunting for every such street to add an area around it. You are not obliged to do that; a normal street with highway=pedestrian is more than enough. We created such areas around Bourse/Beurs because there are large areas there, primarily for the sake of rendering/making the map more pleasant to the eye.

Use noname=yes on the area to skip validation, if needed.

Hello,

Where do all those translations come from?

Did you make them up yourself by litterally translating or can you provide a link to a source where those names exist?

width=0???
way/641532382/history

I fixed it.

Adding construction=service won’t make any difference. As long as "highway=track" is set, it will show up as a normal road and routers will consider it is open.

highway=construction + construction=track is the way to go (with this chain of tags, it can easily be set back to highway=track once construction is complete).

I understand the real situation is messy but I am afraid your changes is making the map complety invalid.

For instance, way/997399373 is overlapping two existing roads here, way/123521562 and way/297866051

How was this changeset decided? Did you survey this road yourself or are you using a map we could find somewhere, to find out what is the current situation?

Thanks in advance.

Hello,

Thanks for updating the map but were the changes in the road hierarchy discussed with other members of the community beforehand? Your changes are creating a real mess with several continuity issues, e.g. this roundabout (way/306261922) deliberately left as a secondary road, with only residential streets around. The primary road network is also in an inconsistent state.

Cycle routing is broken in several streets too, e.g. way/306261922 and way/28272508. Are those streets now strictly one-way with NO permission for cyclists or mofas to use it against the flow of traffic? Because this is what the map currently says, and cycle routers will start ignoring those streets.

Hello,

I don’t think the <L'> string should be part of the name. Isn’t it rather "name=Îlot Picard"?
https://ecobuild.brussels/nl/projecten/ilot-picard-cohousingproject-voor-huurders/

Thanks for some useful stuff such as noise barrier walls.

Just a few comments to make your next contributions better:

1) If possible, make your changesets smaller: either do one zone and upload before moving to the other, or stick to one single theme per changeset instead of doing everything at once.

2) Never draw buildings by following aerial imagery. This kind of imagery is distorted; it is okay for objects on the ground such as roads or zebra crossings, but not for buildings because most of them will depend on the angle when the picture was taken. I tried to fix the outlines of those buildings (I think even the iD online editor can show AIV Flanders GRB map for that purpose; please use that one when buildings are concerned).

3) Addresses on buildings: 7A instead of 7a, and do not fill postcodes or city names, it is never necessary to copy that information on every object. All over Belgium we have existing areas that cover everything (for instance everything here is automatically detected as 1950 Kraainem: relation/3479744)

Hope this helps.

"Appartement" should not be used as a name. This is not a valid name.
Either use building=apartment as the main tag for this object, or fill the description tag.

Updated, thanks.

This is what alt_name is for.

Hello,

The name of this place was discussed several times in the past. I remember setting "noname=yes" explicitely on this area because this name is just a colloquial name but is not official. You won’t find any street sign here and you won’t find it on any official map. I recently took a picture of the map at the entrance of the park and this name is not there either.

If you want to keep the name, it would be wise to remove the "noname" tag from it, because you’ve just created an invalid situation in the database.

Any thoughts?

Hello,

Pardon my asking but is there a reason why you need to have postcodes and city names added on every single building with an address?

Example here:
way/1099904516

This information is typically automatically obtained from existing boundary areas (boundary=postal_code for the postcode, boundary=administrative for the city). It might make more sense to create/fix those areas instead of duplicating info of thousands of objects.

One more thing: If improving addresses is the desired outcome, shouldn’t it be written "Rue de l'Église" instead of "Rue de l'Eglise"?

Mori film lab is already on the map, please update your local data before submitting new one.
Your edit (only the part in Brussels) has been reverted.

Thanks for writing back.

What I mean about polygons is this.
Most pools I know are plain rectangles. They must have 90° angles, right?
It looks like you were drawing pools by hand and your drawings looked a bit like wrong trapezes with funny angles.
What I am saying is that you can fix that easily in the editor.
Right-click on your shape and you will see a few icons → select "Square" (or hit the Q shortcut) and your shape will already look a little better.

If you want to edit in Brussels, it’s also better to use UrbIS imagery (CIRB/CIBG option under the background button on the right) than AIV Flanders imagery, which is shown by default. It’s much more accurate too.

Hope this helps.

Hello,

If I judge by this picture taken by a friend in July, cycling is illegal on this footpath (and a little more than just this footpath) because I see C3 signs on *both* sides.

We seem to both agree that it is forbidden for anyone riding uphill.

https://www.mapillary.com/app/?pKey=788285462336511
This picture shows a C3 sign exactly when we enter the footpath to go downhill. I also spot a F45b sign (what you mention as dead-end except for pedestrians and cyclists) but it applies to this road here: way/836877069

I think they put such a sign because anyone walking here could connect the footpath on this point (node/4205478610). The municipaly made a mistake by putting bicycle logo on their sign. Nevertheless, a F45b alone does not make cycling legal anywhere (it is just information).

Has the situation changed since those pictures were taken?

Hello,

Good first edit, thanks!