Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/mvexel/whotouchedme
Who touched the things I edited in OSM?
https://github.com/mvexel/whotouchedme
Last synced: 24 days ago
JSON representation
Who touched the things I edited in OSM?
- Host: GitHub
- URL: https://github.com/mvexel/whotouchedme
- Owner: mvexel
- License: mit
- Created: 2019-12-16T03:20:28.000Z (about 5 years ago)
- Default Branch: master
- Last Pushed: 2019-12-16T19:07:19.000Z (about 5 years ago)
- Last Synced: 2024-10-21T23:08:15.677Z (2 months ago)
- Language: Python
- Size: 4.88 KB
- Stars: 1
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# WhoTouchedMe
A command line tool that helps you find out who edited OSM features that you created or edited before.
## Requirements
* Python 3.7+
* [pyosmium](https://osmcode.org/pyosmium/) 2.15+## To run
```
usage: whoedited.py [-h] [--keylist KEYLIST] [--skipnodes] [--skipways]
[--skiprelations]
pbf_history_file osm_username out_path
```There are two required positional arguments:
* `pbf_history_file` --> full path to an OSM History PBF file.
* `osm_username` --> the OSM username to check against
* `out_path` --> Where the 1-3 output files will be writtenAnd four optional arguments:
* `--skipnodes` --> Don't look at nodes
* `--skipways` --> Don't look at ways
* `--skiprelations` --> Don't look at relations
* `--keylist KEYLIST` --> A comma-separated list of OSM tag keys. Only features that have any of these keys will be considered
* `--includemine` --> Include `osm_username`'s edits in output
* `--shallow` --> Only include modifications made after `osm_username`'s **last** edit## Output
The tool will output 3 CSV files with the following columns:
* OSM ID
* Version
* Changeset ID
* Edit timestamp
* OSM Username
* Feature deletedThere will be one file for each type of OSM feature: `nodes.csv`, `ways.csv`, `relations.csv`, unless you skip one of the feature types, see above.
Each file will have one line for an OSM feature version that superseded a version edited by you. if you toggle `--includemine`, your own edits will also be included. The output will contain all newer edits since the *first* edit you made to a feature, unless you use `--shallow`.