Does anyone know if if there’s a way to have a complete list of the changesets I commented?
https://resultmaps.neis-one.org/osm-discussion-comments?uid=[USERNAME]&commented is capped to 500 changesets max, and the exact changeset I’m looking for is way older.
The answer may be here filtering on specific words. The other solution no longer works, it complaining being in need of a var value but not telling what var.
This seems to be limited to changeset comments (and not discussions) and only to the last 7 days tho. Or am I missing something?
There are various download scripts kicking around (the perl revert scripts have a version) that you should be able to modify to include the discussion.
Of course, the wiki “documentation” tends to tag along after the code rather than be maintained with it, and I haven’t tested it so there may be a problem with this example.
The complete list of comments can be found in the discussions planet dump.
I’m interested too in changeset metadata, but I was not lucky in finding a tool able to filter this file… maybe libosmium can help, but my current C++ knowledge does not help.
Anyway I made some experiments with Python scripts in the past which I now patched to allow managing these multi gigabyte XML based files with regular PC RAM size.
I tested it with a 10GB discussions dump from 2015 that my old i5 cpu @ 3.1GHz processes at roughly 4.5M changesets per minute. I estimate that the analysis of the current dump should take 30 minutes, less if you have a better processor.
The script loads the dump in an incremental way, scans for comments made by a list of users and outputs a csv file with changeset id, user, comment time and comment text (this last field has carriage returns transformed to \n to allow better csv ingestion in other tools).
Let’s say that it’s far from perfect:
You can find it here
Command line is like this:
GetOSMComments.py user1,user2,userN c:\temp\discussions-latest.osm c:\temp\comments.csv
Hope you can test it.
GitHub - matkoniecz/StreetComplete_usage_changeset_analysis: Process metadata of all changesets ever made to make StreetComplete usage analysis may be helpful, though it has an ugly PHP code for that part (not even proper XML parser)
but in general changeset metadata is a really simple XML file, can be processed line by line, even without proper XML parsing
@SekeRob The tool still works, but you have to use the user ID (UID), not the username, e.g.:
https://resultmaps.neis-one.org/osm-discussion-comments?uid=7494825&commented
(You get a user’s ID by clicking on ‘Changeset XML’ at the bottom left of any changeset of the user in question.)
But, as ivanbranco wrote, it is limited to 500 changesets.