Hello Brooo,

If you want to make edits in Germany, Italy and Spain, please edit each location one by one and upload it *before* starting editing places in another country.

You uploaded all your changes at once, and now they cover a huge territory across Western Europe. This is not unnecessarily annoying to other mappers.
osm.wiki/Changeset#Geographical_size_of_changesets

While you are there, you may want to have a second look at the restaurant you created here: node/12311737847
Is the name really in lower case? Also, is the restaurant really located outside a building?

Thanks in advance.

Hello jbieber,

Are you sure that places like "spice mountain", "tea 2 you" or "farmer" must be spelt in lower case? This does not look like the standard practice in OSM.

It would be appreciated if you could:
– Upload changes in one area before moving out to another area, and in particular not edit places in France and in London in the same upload.
– Write changeset titles to explain what you are doing. Leaving it blank or "no comment" sound very much like "It’s none of your business".

One more thing: it is very unlikely that toilets have a *name*, as you did here: node/12307747122 I suppose you meant that Farmer.J is the name of the business. In that case, please use the "operator" tag and instead of "name"… and make sure that you spell it exactly as the place (cf. first part of my comment).

Thanks in advance.

Hello RikDrabs,

You may want to learn that post codes and city names are never added on individual addresses throughout Belgium. The simple online editor you are using does not know about mapping practices in every country, and still shows extra text boxes. This message is to tell you to please not unnecessarily fill those.

The OSM database contains the entire dataset with postcodes and cities in our country. For instance, every object inside this area is automatically recognised as having post code 1700: relation/4012641 and every object here is known to be in Sint-Ulriks-Kapelle: relation/4012646

Next time, please only the street name and the house number, no more.

I redrew the houses in this street a few days ago and added all the numbers found on the official Digitaal Vlaanderen GRB map, which is the reference we use to trace buildings and set addresses: this house between 609 and 613 had no number. I am glad that you have personally surveyed it and confirmed it does have a real number.

Thanks.

Bedankt hiervoor maar aub meer details geven in de opmerkingen van de wijzigingensets.
osm.wiki/NL:Good_changeset_comments

Good point! In that case, we can safely delete this one, thanks.

Hello lulululu123456,

Please make sure to fill the required field when you upload changes to the production database. The field when JOSM says "Please provide a brief comment…"

This will help fellow mappers to understand what you are doing on the map. Your changes look suspicious without a helpful description.

You can read some tips here:
osm.wiki/Good_changeset_comments

Thierry1030’s survey confirms the current situation, i.e. the former road is no longer available and can be retagged with a lifecycle prefix, while small connectors have been built to divert traffic along the existing loop roads. We updated the bus route relations to match the new itinerary they are following. Nothing more to do here.

Apologies for not providing enough instructions about how to repair the situation, I didn’t see you were a new user. I made some additional fixes here, namely restoring the building (the building is still there and should be kept, but without its "religious" attribute if the chapel is mapped separately).

Normally, changes on osm.org are visible within 5-10 minutes at zoom 19. The map you see on osm.org is a collection of PNG images that are regenerated by a server; this server redraws a new image when something changes in an area… but sometimes the server is overloaded when there are too many changes at the same time. I will investigate to see what happened here.

Already on the map here: way/1132715840

Your edit created a duplicate chapel in front of the existing one. Please never do this. Please merge data into one single object.

Bonjour
Pourquoi attachez-vous systématiquement les arrêts de bus aux platformes, comme ici : way/1328542528 ?
Très mauvaise pratique, ne plus faire svp. Merci.

Hello,

I am afraid your "fix" is not correct.
The road has been dismantled earlier this week, as part of a major reconstruction scheme which is expected to last a couple of years, this is why @Thierry1030 changed it from "highway" to "demolished:highway".

We were trying to collect information about how bus routes are diverted so that we can update the relations. I am afraid your changeset, which consists of restoring the "highway" tag on the main road and pretend the road is open again is not a good fix because it misrepresents reality.

Bonjour,

Intéressant mais incorrect. Les tags doivent aller sur le multipolygon ET être retirés du way externe. Ne pas laisser les tags en double, c'est invalide. Nous réparons.

Hello,

Some parts of your change are intriguing.

1) We restored the bilingual name. This is because Brussels is a multilingual city with two official languages. Removing the Dutch part of the name to make it appear as if Brussels was only a French-language city is not acceptable.

2) You changed the target key as if this was the embassy of Ireland to the EU. Yet, their website seems to be clear that this is the embassy to Belgium (https://www.ireland.ie/en/belgium/brussels/about/ambassador/). Could you please elaborate about this.

You may be intrested to know that the representation office of Ireland to the EU is in the same building, that might explain the confusion for people who are not familiar with our city: node/7395949845

Thanks in advance.

Sure, one can revert everything in bulk but I won’t do this, because this will create another giant bounding box, which would annoy every mapper.

Instead, I reviewed them one by one and looked for interesting tags that could be kept, before removing duplicate information. The only one I left untouched was the viewpoint here: node/100337302 It looks okay.

The rest has been fixed.

You added this convenience store in Cromer (England)
node/12285904878
However, the building itself was tagged as a convenience store, named RedOrange.
way/345723353

Please clarify the situation here, if you still remember what you saw there. If the data you entered is the current situation, then old data must be removed; as you can see you left the map in a state where two convenience stores are piled on each other, here. People who look for a store here will be confused.

About this café in Rotterdam, you added this: node/12285944314 but it had already been added to the database 2 months ago: node/12137690001
You probably know this but OsmAnd does not read real-time data; your device holds a local copy of data; make sure to run updates frequently, to avoid editing on outdated data.

Same for this restaurant in Germany. You added a node here: node/12285944607 inside a building that already included most of the data: way/126206830

Please make sure to only add relevant data to the map. In general, it is better to edit the existing data than create duplicate data next to it, because that makes the map really ugly and unreliable.

Hello,

This edit suggests that you have visited places in 7 different cities today, which seems unlikely. As a consequence, your edit now shows as a giant bounding box covering most of Western Europe.

It is recommended to upload changes separately when you are done with edits in one place (usually a city or region).
osm.wiki/Changeset#Geographical_size_of_changesets

Thanks in advance.

Hello,

I am sure you have good intentions and sincerely want to improve the map, but I am afraid you have damaged structures here too. This self-intersecting polygon, along with connecting a landuse area to roads is bad practice. Please fix asap; if you cannot do it yourself I will be happy to help. Please reply to this message; it looks like people have been trying to warn you in the past days.

Hello again,

Sorry, I see that the restriction is a "only_straight_on" type, not a real turn restriction. This would match the situation on Mapillary, indeed. In that case, it does not prevent traffic from using the road normally.

However, I feel that such a relation is not needed, because oneway=* tags on the side road make the situation unambiguous.

Have a nice day.

Hello,

The turn restriction you added prevents motor vehicles from using this street from north to south, forcing a left turn into the tiny street here: way/916587513

The changeset claims to use Mapillary. The latest Mapillary picture, taken during the summer, does not show any sign of a restriction on the main road.
https://www.mapillary.com/app/?pKey=474309668537116

Would you please be so kind as to provide some documentation about why such a restriction blocking traffic on a major road is necessary?

In general, it is always a good idea to copy a direct link to the Mapillary picture in the source field of the changeset, that will help local mappers to understand what you are doing.

Thanks in advance.

Hello,

Pardon my curiosity but this changeset is really intriguing.

Your change keeps way/31658095 as a two-way road, but creates two turn restriction relations that make it impossible to enter it from the east. Has it become a one-way road? In that case, wouldn’t oneway=yes (with possible exemption for cyclists, if any) be more appropriate than relations, which some engines do not support? I could not find recent images on Panoramax or Mapillary; is there a public source of data to help here?

relation/18205739