d1g, I understand the reasoning behind your posts/comments, but please don’t insult people, even if you think they deserve it. It makes for a negative atmosphere for everyone, it does not contributes to the discussion and forces most of you readers to disregard your arguments completely even if there may be truth in them.

Good idea, sounds doable !

However watch out, some people hate automated changes, and would revert your edit, even if done perfectly. So in order to avoid having your work thrown out by such persons, maybe you could add do a map to display such nodes and allow their manual deletion, even if this means slowing the correction process.

Nice tool !

I often use achavi to view changesets, maybe you could add it next to Visualdiff ?

Your contributions are welcome, however please use a better changeset message than just “Mapping Improvements”. It allows better understanding of why you did the changes present in the changeset for other mappers, as well as yourself in the future.

Hello, nice tool ! Do you plan on releasing the source code ? I would be interested to have a look at it in order to improve my own QA tool

Thank you

@masticator The problem is that a full history of changes made in OSM is kept. Such modifications will be stored forever.

Another “limitation” of OSM is that data consumers can be out-of-date (e.g. OSMAnd) until a manual update. That means that some users will not have the event mapped on their phone, while users having downloaded the map while the event is present in OSM will keep it that way until the next update.

So in my opinion, only long or medium-term modifications should be mapped (>2 months minimum)

The API is documented here, but sadly this feature hasn’t been developped yet.

What I do is bookmark each changeset I’m interested in, and check them sometimes.

Neat !

Very good post summarizing the tagging process for subways. Thank you !

(Et oui, au moins une personne a lu jusqu’au bout :)

I recently discovered a neat tool that help fixing highways by displaying lanes, turn lanes and destinations, I thought it would be relevant to mention it here :

http://osm.mueschelsoft.de/cgi-bin/render.pl

(I meant without associatedStreet, silly me not reading my post before posting)

I’m not sure if this post is just for the laughs, but just in you are trying to get a point across :

The name would have been duplicated even more, so the problem would have been the same…

Bonjour, n’hésitez pas à déposer des notes sur la carte du site osm.org directement, c’est un peu plus facile pour les mappeurs de corriger les erreurs.

@imagic : Administrative boundaries are hard to map, so we should not map them badly, even if information is readily available in order to map them correctly? Some data are not trivial in the real world, and they still need to be mapped.

As you said : “it might be a horror to use for any consumer, but it is still valid data”. If a data is not usable by data consumers, it have almost zero value to OSM. OSM is not an atlas, read by humans. The OSM database must be parsable in order to be of use.

If we go down that path, why defining a format for opening hours, as humans could parse it, and why create specialized tags when we could only use name=* as it would be still readable by humans ?

Let’s not forget that OpenStreetMap is a database. It comes with responsibilities in order to deliver it’s true potential.

@chilly, I think it’s a circular problem. Data consumers try to do something with the tags already used, and people, seeing that a certain tagging scheme is used, so they continue tagging stuff using that.

The problem is that often tags were introduced with low detail & complexity in mind, which regularly hinders data completeness of a feature (I’m thinking highway=bus_stop vs Public Transport) As described in the first paragraph, people would never go out of their way and use more complete or precise tags, as long as data consumers does not force them to use better tagging scheme.

The only way people could be encouraged to do so would be with votes leading to approved tagging schemes, but sadly, taginfo stats often wins over well-defined tags.

Or allowing users to report bullies to moderators

Merci bien pour ses astuces je dormirais moins bête ce soir !

It seems not, I just posted the link for reference.

Here is a example of a working iframe, just taken from the “HTML export” from the OSM frontpage

I think you can have more luck here.

If it’s a website bug, it can be reported on the OpenStreetMap-Website Github issues

Thank you for this new iteration of Overpass API, looking forward to experiment with out geom