Hello,

To add a shop, please create a floating point inside the building and add the name and shop type.

Do NOT add the name on a container building.

The database does not speak French. If you write "Boulangerie" on the outline of a building, no app will recognise this type of shop. Only the "shop=bakery" tag will list it as a bakery. The OSM data model requires a proper tag, not just a name.

We redid your edit, and added a point here.
node/12895275708

If the cycling infrastructure is really on the same level as the road, e.g. with only dashed lines to mark it, then the recommended way is to map it as part of the road (i.e. adding a cycleway key on the road itself).

From what I can see, the cycle track is slightly elevated, therefore mapping it on its own is correct. There seems to be a mistake in the fact that some people (not you) wanted to draw cycle infrastructure and forgot to think about where pedestrians should go.

I think this can fairly easily be solved by adding "foot=yes" on the cycle track. This will restore correct navigation here. (Alternatively, removing the "foot=use_sidepath" restriction, as I stated in my previous message, would work too.)

Hello,

You have already added this shop yesterday: node/12878819501

In this changeset, you added a duplicate shop in the same building. I reverted your change (and also your third upload, 3 minutes later). Please turn off automatic uploads in Organic Maps, to avoid spamming the map with bad data.

Hello,

I am afraid that this changeset broke a few things. Since you have only made a few contributions so far, I suppose this is simply a beginner’s mistake. Here is an explanation to help you understand what went wrong.

The "foot=use_sidepath" tag which you added instructs navigation engines to ignore the road for navigation.

Here is one of the roads you changed.
way/174908018

The problem is that… there isn’t any sidewalk drawn separately here. The cycle track has been drawn (only open to cyclists) but not the sidewalk. As a consequence of your changes, navigation for pedestrians will not use the road and will have nothing else to use. Therefore, queries will fail here and will request pedestrians to make large detours.

This is not a correct way to map things in OSM.

Here is a correct way:

1. Easy solution: use normal roads and do not add any "foot=use_sidepath" or "foot=no" restriction. Adding "sidewalk=both" is optional (always a good idea to add it, provided they really exist.)

2. More complicated: draw a full network of footways along the roads, and make sure to draw the crossings too. Only when this is done, you can forbid pedestrians on the roads.

Hope this helps.

Hello.

In this edit, you attached the node for a company (node/12873605803) to a boundary way. This should be avoided completely.

You also removed public transport stops in Uttrecht. We have no information about why it was necessary to do this. Can you please write correct titles to your changesets, they look fairly suspicious.

Hello, Teraboll.

Thanks for this.

Since most of your latest changesets contain the same obscure "error correction" title, I would like to suggest that you would use something more descriptive in the future.

The reason is that we see lots of strange edits every day (and even some vandalism) under innocuous-sounding titles. It is therefore important that changeset titles clearly describe the content.
osm.wiki/Good_changeset_comments

Your edit here is fine. If I understand correctly, past building imports had unnecessarily created new nodes instead of reusing existing ones, and this is what you are currently cleaning up, right?

Have a nice day.

Hello,

"Subspace" is the name of the cafe, it is already properly written on the POI: node/6966406043

Please do not duplicate the name on the door itself.

Vous avez supprimé le parking d'un magasin en indiquant « Essai ».

Est-ce que nous comprenons que le parking existe toujours en réalité ? Qu’en est-il, svp ?

Oh, my bad, then.
Indeed, if the words "Rue scolaire" or "Schoolstraat" are written on the sign, then cycling is legal and "vehicle:conditional" is fine. Another exception to the C3 sign, then.
Good to know, thanks.

On this picture (https://www.mapillary.com/app/?pKey=1096736592261040), I see the "F19+M4" combination (one-way with cyclists going contraflow) + C3 + large sign which probably gives the hours where the street is closed.
Cycling during closing hours is legally forbidden here.

Hello,

Pardon my asking but according to Belgian law, the standard sign for school streets is a C3 road sign, which forbids every vehicle. Vehicles that aren’t motor vehicles—the most prominent category being bicycles—may not pass through. This is the reason why we commonly use "vehicle:conditional" for school streets.

Unless of course an M2 sign is placed under the C3 sign.

What did your survey show?

Hello.

Please be kind and do not add postcodes to individual objects.

We don’t do this anymore in Belgium. They are not "missing" because we forgot; we don’t add them for a reason OSM is a geographical database. This data is obtained automatically: every object inside this area is automatically recognised as having post code 8890: relation/3367991

Hope this helps.

Fixed: node/10792703407

Hello,

You added this place next to an existing restaurant in the same building.
node/10792703407

Do I understand that *both* places are still operating in the same building. I would suspect that Olive replaced the existing one, not go along with it.

What did you see here?

Hello,

I see you are changing a lot of paths now.

As a map editor, it is your responsibility to make sure it is still usable by everyone. If you change a footway into a cycleway, then this path will disappear from navigation results for pedestrians. I am asking because I see a lot of gaps here now in the grid. Really not possible for pedestrians to walk anywhere here?

Also, please always inspect the list of tags of objects you edit. I see you use the embedded editor from the osm.org website (which we call iD). In that case, do not just look at presets but also make sure that tags are coherent. I see in this path (way/1317574911/history/4) that you made it a cycleway but did not change other tags, so we end up with highway=cycleway + bicycle=yes on the same way. The latter tag creates an exception for nothing, it should be cleaned up.

Thanks and happy mapping.

Please do not use the scissors tool on buildings. If you do that, you will break correct structures and create silly stuff like this: way/150278434

No problem, I will fix that.

The reason I was asking is that most buildings in Brussels are already on the map. Each building is known through its unique identifier in the UrbIS database, managed by the Brussels-Capital Region. When we see a new building on OSM that is unknown to UrbIS it always raise some questions. Don’t worry, your edit was useful and we will keep those containers on the map.

Happy mapping.

Hello,

Thanks for this.

Are those two small buildings real buildings or containers?
way/1389041760
way/1389041761

We have special tags if those are "semi-permanent" structures.

Hello, and welcome to OSM.

Can you please write real descriptions for your uploads. Writing "/" as the summary of every change is a very bad idea.
osm.wiki/NL:Good_changeset_comments

Hello.

Thanks for importing more data. I came across a potential problem for one address.

way/1380083862 = Rue de Chièvres 23 according to the import.

I see that a user had just added the address as Rue d'Hautrage 23 here, just before your change.
way/156363858/history

I suspect that the user knows his true address. This might indicate a possible error in source data.

Do you think it should be reviewed again? How about this? addr:street=Rue d'Hautrage and addr:street_official=Rue de Chièvres.