OpenStreetMap logo OpenStreetMap

Changeset When Comment
158634992 about 1 year ago

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

158636356 about 1 year ago

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

158490882 about 1 year ago

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.

158529343 about 1 year ago

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.

158529343 about 1 year ago

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.

158407256 about 1 year ago

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.

158490882 about 1 year ago

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.

158309482 about 1 year ago

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.

158374986 about 1 year ago

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.

158308274 about 1 year ago

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.

158308274 about 1 year ago

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.

158308274 about 1 year ago

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.

158309589 about 1 year ago

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.

158299336 about 1 year ago

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.

158299336 about 1 year ago

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.

158298159 about 1 year ago

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

158266086 about 1 year ago

Sorry but you’ve just created an invalid structure: your inner polygons overlap each other.
Please draw a new outline of the entire "inner" part and use only that.

158245703 about 1 year ago

Thanks for the fix. I also fixed your other changesets in Brussels when they created the same problem.

158247595 about 1 year ago

Hello,

On this picture taken about one month ago, the eastern part of the street is one-way, while the western part isn’t.
https://www.mapillary.com/app/?pKey=504858339001786

I suspect your changeset fixes one part by introducing a mistake for the other part. The road should be split.

Do we agree here or did your users report something different and claim that the entire road should be a two-way road?

158245703 about 1 year ago

Hello,

Thanks for spotting a one-way road here.

Two recommendations, please:

1) Make sure to provide a source, ideally a direct link to the mapillary picture you are claiming to have used.

2) The white signs that come under one-way signs are important in our country, they make the difference between OSM being a map only for car drivers or for everyone. As the following picture shows, this road has a sign allowing cyclists to use the one-way road in both directions, which translates into "oneway:bicycle=no". This is important for routing.
https://www.mapillary.com/app/?pKey=192252756719326

Thanks in advance.