This is a static archive of our old OpenStreetMap Help Site. Please post any new questions and answers at community.osm.org.

Investigating changesets

4
1

I find that it's very hard to understand what it happening in a changset, it's easy to get an suspicion that something is amiss but it's very hard to dig deeper. Does anyone have any scripts, methods or just tips that will help in investigating a changeset?

The only two things I've find was:

Take this changeset on OSM main site and on OSM History Vizualizer, it's very hard to figure out exactly what happend. (I'm not pointing fingers at the creator of the changeset, I just haven't been bothered to find a changeset where I have recreated and removed lots of stuff.)

So to restate some questions.

  1. what do you look for when you look at a changeset?
  2. is there a way to create the before.osm and after.osm files given a changeset ID. (to make osmdiff happy)
  3. is there a similar changeset viewer like the one on the main site, that doesn't make you click "next page" all the time.?

It might be a good idea to try to split up answers

asked 14 Aug '11, 01:20

emj's gravatar image

emj
2.0k123547
accept rate: 15%

edited 24 Oct '11, 09:09

2

If you know that the question should be discussed on the mailinglist why do you ask it here?

(14 Aug '11, 12:22) petschge
2

This does not appear to be a question, rather the author wants to have a discussion.

(14 Aug '11, 13:00) emacsen
4

Might is not the same thing as "should". There must be people who have researched changesets and answers describing personal methods would really help. I do not think it warrants down votes just because it's hard to give good answers.

(14 Aug '11, 14:54) emj
3

I would quite like to know some people's answers to this question myself. From that point of view it's quite good. But yes, it's more of a discussion than an a specific question.

(15 Aug '11, 13:48) Harry Wood
1

Thanks for mentioning the history viewer. This is a great tool. I usually used itoWorld for this, but its updates take a week.

(14 Oct '13, 08:21) Chaos99

Source code available on GitHub .