Your changeset has been reverted.

The app asked specifically about the "Oliobox" container, that is the orange container for cooking oil.

You entered data that suggests that this Oliobox accepts clothes and shoes, this is nonsense. Clothes and glass-recycling containers are mapped separately.

I suppose all 3 containers are still there and fixed the tags appropriately.

Hello,
You have just created a duplicate node of the node you created a few minutes ealier?
node/11101922146
Both of which are duplicates of an existing landuse area
way/197021579

Are you sure this was really necessary?

Hello,

Can I invite you to add real titles to your changesets on OSM. Adding "Informatie verbetering" on every of them is just wasting other mappers’ time because we have to spend a lot of time every time trying to figure out what you have been wanting to do.

There seems to be a problem with this shape, which you broke in a previous changeset, I don’t see what kind of improvements you have been doing.
way/947788394
You even created a multipolygon to join the two broken parts instead of restoring the area. It looks like a mistake, can you please have a look.

As for Oud Stadhuis, do you think the small part in front of the building, with the stairs, is really part of the building?
way/951489558
Or should that be a separate shape? I think government database treats them (and numbers them) separately. Anyway, if you are applying a new policy or if you have good reasons to do so, this is something worth including in the changeset title.

Have a nice day.

Hello,

I am afraid we have a problem here.

When you add "access=yes" on an highway=* object, it makes it open to *every* vehicle.

Combining "highway=footway" + "access=yes" tells routing engines that everyone (cars, horses…) is welcome here. Please do not add "access=yes".

Do not add "foot=yes" either, it is not necessary when the way is already tagged as a footway. (foot=yes will be only used to counteract a generic ban, such as "access=no", or to allow pedestrians on a road where they would not be allowed by default, e.g "highway=cycleway")

Just keep highway=footway without anything else and that will be fine. ;-)

(Don’t let the crappy drop-down boxes in the iD editor fool you into selecting values there, just ignore that and go straight to the tags.)

Hi,
French overseas territories are very widespread. If you want to import data in French Antilles, Tahiti and French Guyana, please make separate changesets. Otherwise, you are creating a huge bbox that covers several countries in Central America and half of South America.
osm.wiki/Changeset#Geographical_size_of_changesets

Can you please try to make smaller changesets next time. Ideally one changeset per town, especially if you import data in multiple countries. Thanks!

Please make sure you put trees as floating nodes.
Never attach them to roads or landuse borders.
node/11096733081
I will try to fix this.

Most third-party maps are copyrighted (e.g. maps in shopping malls are a clear no for OSM). That being said, a small map in a cemetery should not cause the same kind of (legal) trouble. The good thing is that you seem to have not just looked at the map but also checked yourself, I suppose that should be enough.

Done

Hello,

Was there a number on the door?
During the last survey… only one month ago, there was a door here but it was entirely barred; impossible to get into the building here or to deliver mail. Therefore, it does not count as a valid address.

We explicitely added a not:* address point to warn fellow mappers not to create one.
node/11057729716

I see you added this number when visiting the place today.

What did you see please?

Hi.

This looks like you are doing a mechanical edit (starting with cities in A-) to add names in latin, with more changesets to come. Not sure this is a good idea.
Another useful reading here before proceeding further: osm.wiki/Automated_Edits_code_of_conduct

Same concern as @mcliquid: unless the book is in the public domain or has been published under a compatible licence, it is not allowed to import the names you found there into OSM.

Also, the Belgian city of Aalst was already translated as "Alostum", and you changed it into Halosta. This is probably very futile, latin was extinct long before the town was founded.

Hello,

Is the following information still correct for Archie?

opening_hours Mo-Sa 11:30-15:30
phone +32 498 59 53 34

Thanks for the answer. Don’t worry, those things happen.
I’ve just restored the ways, it’s done.
Have a nice day.

Hello,

Please do not trace buildings from aerial imagery. They give a distorted view of buildings and we’ll have to redo everything.

When you are editing, you can change the background. Hit the Background icon on the right of the screen and scroll down to "Digitaal Vlaanderen GRB". You will find the correct outline of buildings, which you can use as a source.

Also, addresses in Belgium are only
House number + Street name.
Do *not* add postcodes and town manually, it is not necessary. We already have large catch-all areas to do the job.

Happy mapping.

SVP lire les commentaires qui vous sont envoyés.

way/1194042556
La rue n'a pas de nom ?
Ou alors ça doit être une allée de service simplement, pas une rue.

way/1194042555
1) name=3A ????? Je crois que vous avez confondu le « nom de la maison » et son adresse. C’est très rare qu'une maison ait un nom.
2) 1700 Dilbeek ne doit pas être ajouté manuellement dans les adresses. Tout ce qui est dans la zone ici relation/4012641 est automatiquement déjà avec CP 1700.

Hello,

I saw you requested a review.

First, I suggest you read the comments that have been emailed to you after your former edit on May 31. User Jakka made important comments to help you improving the map. We finally had to delete your changes because it contained way too many mistakes, such as invalid addresses.

Here are some comments below.

1) Parking areas

amenity=parking is for large parking structures. Think about a car park in front of a supermarket or a railway station.
Having a few spaces along the road is not necessarily drawn like this, we prefer adding regular attributes to the road. Should you insist drawing them separately, please add an extra tag to them, e.g. parking=lane.

(Not doing so will make the map look completely ugly and stupid, and will annoy users.)

2) Footways

Adding sidewalks or footways is cool.
But never create unfinished structures.
Example here: way/1194026828 This footway starts at one point and terminates in the middle of nowhere.
OSM is used in real-life to route users, sometimes blind people. It is the responsibility of every mapper to ensure not to create a mess. Should the sidewalk really be interrupted here, add a "noexit=yes" tag on the last node. Otherwise, connect it or don’t draw footways at all.

3) Shapes

We value quality over quantity. If you draw objects, please try to make the extra bit of effort to draw realistic shapes.
way/1194026819
This looks like an ugly trapeze.
Even the online editor has an option to automatically make it a rectangle. Use it.

4) Buildings

Never draw buildings according to aerial imagery.
way/1194035004
When you are editing, look for the Backgrounds button on the right part of your screen. It shows a list with other background layers. In Flanders, the right one is "Digitaal Vlaanderen GRB". It gives the outline of buildings (i.e. the outer walls). This is okay to trace in OSM.
I repeat: never draw buildings according to aerial imagery. (Aerial imagery is fine to locate low-height objects such as zebra crossings, benches, etc. but not for larger structures. This is because those are images taken from aircrafts, and there is always some distorsion, which is proportional to the size of the object.

5) Traffic signs

node/11083760954
"traffic_sign=yes" alone is useless.
The correct way to use those objects is by providing the code of the traffic sign. (prefixed be "BE:" in Belgium)
For instance, a no entry sign barring access to a road is: "traffic_sign=BE:C1"
A give-way sign before entering an intersection is: "traffic_sign=BE:B1" and so on.

Happy mapping.

Hello,

I am not sure your data sources are up to date. Also, mapping an area without local knowlewge, without looking at existing tags or without asking locals first is a terrible idea.

Here is an example of a former roundabout in my area:
way/22971968

The last changeset has a very clear title. We wrote this:

Square Amnesty International/Amnesty Internationalplein - new traffic scheme, no longer a roundabout but cut into multiple parts, some of them in both directions, some entirely closed to motor vehicles

We put "was:junction=roundabout" to alert armchair mappers that it *was* a roundabout but is no longer one.

All this careful work is damaged when you arbitrarily restore the tags, presumably on outdated imagery. I am afraid I’ll have to revert your change.

Hello,

Interesting but do I read that "Bing aerial imagery" was used as a source to change the geometry of this building?

You may be interested to know that "Digitaal Vlaanderen GRB" is the official source for this part of the country, and shows proper building outlines. Available out of the box in JOSM and iD.

Thanks for this.
I removed the name and brand tags: such a device does not really have a name.

Hello,

Thanks for this.

I think there might be a little bit of an issue with the following POI:
node/11074286639

operator wikidata=Q87990220
is a very strange value.

I suppose you mean this:
brand:wikidata Q87990220

If you do this, apps will be able to correctly associate this shop with the parent company.

Happy mapping.