I will do it. It’s always better to avoid duplicate values in the database.

Hello,

Very puzzling indeed.

On this recent set of pictures, taken last October, C43 roadsigns on the southbound road seem to be properly installed everywhere.
https://www.mapillary.com/app/?pKey=649227893482890

I see you changed the maxspeed in one direction and kept the "source:maxspeed=sign" tag. Do I understand you wanted to confirm there are roadsigns explicitely stating it’s 30 kph now. Are those C43 signs?

Hello,

There were some problems with this changeset.

As a new user, please do not attempt to change multipolygons, they are a complicated feature of the database and you might inadvertently make mistakes, such as erasing the hospital or more.

I fixed the helipad.

Hello,

The phone number and website have been in the object since version #1.
node/10178835187/history

It is always a good idea to look at the tags of an object before editing.

contact:phone and contact:website is the current best method to add contact details. Do not rely solely on the "preset boxes" of the iD editor, this software is not reliable and will hide essential data from you.

Happy mapping.

Hello,

I know it’s been 3 years but you may want to have a second look at your edit.

You probably meant to move the main icon of the cafe near the entrance… but it turns out you moved it out of the building. This makes very little sense now.

I hope that helps.

Hello,

access=destination
+ motor_vehicle=destination
+ bicycle=permissive

There might be some cleanup to do here because this is a fairly unlikely combination of tags.

If you mean that the street is restricted to local traffic (C1 sign + a blue sign), then it will be "vehicle=destination" instead of "access=destination".

In such a case, cyclists and horse riders are legally exempted by law, then you might want to add "bicycle=yes" and "horse=yes".

I don’t know why there is "bicycle=permissive", it is very rare outside of the UK, it is primarily aimed at private roads where we assume access is granted. Not on public roads.

Hope this helps.

Hello,

I see you requested a review.

Nice to add this. Cool to have a LUG on the map!

I am not sure whether "amenity=community_centre" and "community_centre=club_home" are appropriate.

I would tend to only have club=linux on the node. But though it will be searchable, there will be no icon on the main map.

Another issue is the location. If you put the address as 121 we’ll have a duplicate address with this one which you moved a few years ago: node/2622408355 ← and indeed the location of that node matches UrbIS data.

Are you sure Caldarium is in the correct building? Shouldn’t it there be near the node with housenumber 121? If that is the right building, I suggest removing the address entirely on Caldarium.

Multipolygons are a special kind of relations, they are not just borders. They are technically a relation but follow the same rules as areas. (Many buildings are multipolygons, even Belgium is a multipolygon in OSM.)

I understand that the purpose of this changeset was to draw it as an area instead of a MP. I would tend to agree with that. But it is true that "type=multipolygon" should not be used on a way.

Hello,

This changeset came to my attention, after changeset/133450402 had to fix almost every single of those ways.

I am curious to hear why you are using landuse areas for each house. I don’t know any other part of the world where people do that: there will be one single landuse area for an entire block, and then we may make small areas with walls between each property, but areas will be tagged as gardens, not as landuse.

I am particularly concerned about the time and effort it must take you to do this.

Was this decided or recommended by anyone?

You deleted "man_made=survey_point" on this point in Russia.
node/2/history

This explains why your changeset spans across several continents.

Also, this point in Quebec has a problem:
node/10721526668
It has just a name and a description. This point will not be shown on any map.
To make your contribution more useful, you need to add extra tags on it, e.g. tourism=chalet

Hello,

Welcome to OSM!

I see you added a tree.

Pardon my curiosity but was this a test edit? Unless it was planted in the last days, to the best of my knowledge there is no tree in front of number 5 here, as this picture shows:
https://www.mapillary.com/app/?pKey=417348296481940

OSM relies a lot on peer reviewing and accountability. If something is not obvious to observers—for instance if a change is very recent—it is always a good idea to explain this in the description, when uploading.

Looking forward to your reply.

Hello,

Medi-Market is not a pharmacy but a para-pharmacy. There are important legal differences because they are not allowed to sell prescription drugs. They should be tagged as shop=chemist in OSM.

Example here: node/5266682350

Isn’t it a duplicate of this one?
node/634187532

Just in case: the OsmAnd~ app uses an offline map, so you have to download an update every now and then, otherwise you map want to add objects that are already on the map.
You can activate the "Live updates" to get a fresh copy.

To update, you can do: Menu > Download maps > Updates > Live updates > Belgium > Update now

Isn’t it a duplicate of this one?
node/6742596577

Nice work to update the shops and businesses here.

I admin doing edits with OsmAnd is complicated, because there is a little issue here:

The building was tagged as a computer shop.
You added the new activity: tax advisor. Fine, but since a tax advisor is in the "office" category, adding the office tag does not remove the "shop=computer" tag… and now the building is mapped as being both an office and a computer shop.
Your next step is to remove shop=computer.

While you are at it, I suggest the following action:
1) Is 100% of the building used for the tax advisor activity? If yes, you can leave the office tags on the building.
2) If no, it’s better to create a single point floating inside the building, and put the office tag and the name onto it, while the building outline keeps building=house and the addr:* tags.

Hope this helps.

If it is closed, do not only remove the name, but change this tag too:

shop=department_store

(I suggest changing "shop" into "was:shop", that will help future mappers to understand the situation… and will prevent others to recreate it if they map from memory or from outdated pictures.)

Hello,

Before splitting a way, as you did for this one (way/1150973353), it is always a good idea to download the entire set of elements around it, including its relations.

In this changeset, you split a part of the roundabout but the relations using it were apparently not in your active JOSM layer. That creates a gap in all those relations—several bus routes and local cycle routes—because they are untouched and refer to the only object they know, which is only one part of the roundabout.

Don’t worry, it’s all fixed. I thought you might be interested to know about this kind of issue.

Hello,

Can you please NOT add addresses to objects located within buildings with a single address.

Example here: node/10700762536/history
It is not necessary to repeat on the restaurant itself that it is on number 904 and on Chaussée de Louvain/Leuvensesteenweg because the information is automatically computed by the database.

It is really painful to have to clean up afterwards, thanks.

Additional tip: in the settings of EveryDoor, be sure to activate "Prefer contact: Prefix", because it is the preferred way to write tags nowadays in Belgium.

Please do NOT change addresses on existing address nodes.

They are part of a validation scheme for addresses.

If you want to create the office of Wallonie-Bruxelles Enseignement, add a new node beside.

But do NOT change "20" into "20-22" on the existing address.

Your change has been reverted.

Hello,

Welcome to OSM.

We had to fix your changes here because of several mistakes. Most mistakes are typical for new mappers.

In a nutshell.

1. We ask people to *not* delete points related to former activities. If the bank is gone, do not delete it from the database, remove its bank-related tags and change it into the new activity instead. This helps to follow the life cycle of nodes.

2. Some minor fixes for the KFC. We use "Kentucky Fried Chicken" as the main name, while KFC is a short version → based on this, the rendered will choose to use the short or long name based an available space on the map. Also, building=yes is for building outlines only. You added it to your KFC, making it a "building inside a building". Don’t worry, we fixed the error.

3. Some more details but on your first day you cannot know everything: in Belgium we do not fill address tags on elements (at least not the postcodes or city), etc.

You can open the editor again and see how the tags have changed, and use this as inspiration for furher edits.

Happy mapping!