Hello,

Thanks for adding pictures.

A few questions here:

1) Why don’t you use normal changeset titles describing your actions in real words for real humans? Those cryptic names serve very little purpose and are annoying everyone; reviewing your changesets is slow and painful. For instance, here you added some buildings, you split a road to add a bridge structure, in addition to adding pictures to existing POI or buildings.

2) Are the licence conditions of those pictures compatible with OSM? I guess those are pictures you took yourself. You might consider uploading them to wikimedia commons instead of proprietary services like Google Photos.

3) I don’t think "embankment=yes" is appropriate on a road going to a bridge: way/1085888986

(I think this discussion should have been inserted on the reverted changeset which resulted into having two restaurants with the same name, not under this one.)

That being said, I also went to have a look earlier today. I think I found the source of the confusion: on their website they claim to be located on number 13. But they recently expanded and took over the restaurant next door and they now spread over two buildings, while their official address is still number 13.

In addition, there were problems with the geometry of buildings, which came from an earlier import of UrbIS data. I tried to fix as much as I could.

Hello,

Thanks for this.
There seems to be a problem with the way you are using your app (it looks like you are using Organic Maps): every time you create a point you fill the name in one language (in this case you filled the French translation of the name) instead of writing it where you can give the name to be used in every language.

As a consequence, this bakery was created as "this bakery as no name; translation in French is Aroma". Well, I fixed this one and am busy cleaning up your other edits.

I think Organic Maps does like this: in the "Name of the place" block, ignore the empty fields with languages and click on "Add a language", then scroll to the last entry "Native for each country" and type the name there and nowhere else.
There might be an easier way, I don’t know, but at least it will prevent you from filling the map with invalid data like here.

Happy mapping.

way/1078819332/history

lanes=5 → 5 rijstroken in deze straat?

Misschien bedoelde je dat de breedte 5 meter is.

way/154674305/history (v8)

lanes=0???

I suggest you use lane_markings=no instead.

If there is a road sign you can add it as a node, e.g. traffic_sign=BE:F45b

Hello,

Do you really need a noexit tag here?
Does an app require it?

First, it triggers validation issues on the map because the road _is_ physically connected on both sides

Second, this looks like a car-centric view, ignoring cyclists and pedestrian may legally pass through. ("noexit" applies to everyone, not just motorists.)

I suggest you remove it. Having the block across the road is enough to get routing work properly.

How many Spago’s in this street?

There is another one next door, is that the same?
node/3261814416

OK, thanks for replying.
Good idea if you have someone who can have a second look and clean up tags where appropriate.

Hello,
Don’t forget the https:// part for the website. Some apps report a broken link because you forgot it.

Hello,

Your changeset creates very uncommon tags. I might be mistaken but it looks like you mechanically added bicycle=yes to lots of ways.

For instance, here:
way/33127956

This cycleway was set as access=no because it is currently being rebuilt. I haven’t checked recently but I’ll take your assumption for granted that it is open again. In that case, just remove access=no and that will be fine.
In your change, you kept access=no and added bicycle=yes on top. Technically, most routers will understand it but it’s really dirty to keep pile of nested access tags for nothing (highway=cycleway + access=no + bicycle=yes is quite pointless).

On this one, which is also being rebuilt, you added bicycle=yes but didn’t care to remove the construction key: way/129161264

Hello,

In Belgium, highway=path is automatically open to cyclists.
osm.wiki/OSM_tags_for_routing/Access_restrictions#Belgium

I don’t know what "quality" is improved by forcing bicycle=yes on such a way.

Is there a reason to do this? Does one specific software you use not know how to deal with highway=path?

Thanks in advance.

You are right but this critic has nothing to do with *this* changeset.

After our discussion, I started editing the LEZ. It will take something like 10 or 20 changesets to find all the parts where they changed the boundary. It’s better to do this than one giant changeset, as it’s a lot of work every time. I plan to do this over the next days.

I have just started this part. The part you mention is elsewhere in the region.

Hello,

Thanks for adding them.
In reality, it won’t really matter here: the only connector is tagged as a cycleway, i.e. routers will only allow cyclists to pass through and disallow motor vehicles, whether the bollard is attached to the cycleway or not.

Just one thing: if you want to get in touch with me or with anyone, please use the internal mail function of OSM (click on a name, then select "Send message"). Commenting a changeset is only to report a mistake the other user might have done in one’s changeset.

Have a nice day.

Hello,

FYI, bpost’s zone 1040 spans not just Etterbeek but also the City of Brussels, namely a large rectangle between Avenue des Arts/Kunstlaan, Loi/Wet, Belliard and Cinquantenaire/Jubelpark.

As we wrote on the wiki, there is no 1:1 relationship between postcodes and municipalities in the Brussels-Capital Region. This map explains it more clearly: https://www.brussel.be/sites/default/files/bxl/Postcodes.pdf

I disagree with the changeset title because addr:postcode=1040 and addr:city=Bruxelles - Brussel is technically correct for this street.

That being said, in Belgium we generally only use addr:street and addr:housenumber, no more, because the rest can be obtained from parent relations or boundary zones. Therefore, removing the postcode here is okay. 😉

Hello,

There seems to be a contradiction in the tags for one street here:

way/49042170 is a living street, maxspeed is expected to be 20 at most, not 30.

Could you please check this again?

Hello,

StreetComplete is to be used when surveying places.

Did you really visit South Korea, Luxembourg, Martinique, Salzburg and Madagascar on the same day???

Hypothetically, if this data was collected during multiple trips, please ensure to upload data to the database before moving to another place, to avoid creating bounding boxes spanning half the planet, like this one.

Hello,

Thanks for this and welcome on OSM.

Can one enquire how the name of buildings and areas was acquired?
Are those names official? If yes, do you know where we can check the source?

For instance:
"Ten Bosch Housing": when large residential buildings have names, they are almost always printed in large characters near the doors. We have pictures of this building taken in April (https://www.mapillary.com/app/?pKey=134659612444311) and I cannot see this name anywhere.

"Carré au Platanes": strange French grammar and no official Dutch name?

"Les Venelles": no official Dutch name?

We did some other fixes about this changeset, I understand it’s not easy to get things right on your first contributions.

Thanks in advance for helping with explanations about the names.

Hello,

Thanks for updating the map and welcome here.

Please be careful when you draw new streets or introduce new tags.
It is not acceptable to make a street one-way without looking at exceptions for cyclists (when there are white M2 "except bicycle" signs), which breaks cycle routing.

I tried to fix as much as I could.

Duplicate of node/9580248851

Your edit has been reverted.