Some relations can have thousands of revisions and the “View History” link times out. There is a full history dump but it is vastly greater than the history of a single element and takes too much time and space for a home computer or mobile device. Is there a more efficient way to do this, maybe starting with the most recent revisions? asked 08 Mar '16, 22:16 Wynndale |
You might find osm.mapki.com useful - see for example with this relation. If necessary you can also get individual versions from the API:
answered 08 Mar '16, 22:21 SomeoneElse ♦ Also, for objects with ultra long history, I recommend just deleting and re-creating them under a new ID, with an additional tag "note=original object ID was ..." or so. Makes life easier for those that come after you!
(08 Mar '16, 22:31)
Frederik Ramm ♦
|
One option is to use josm to view the history. Download the location or just the object (file -> download from osm or file -> download object), select the object, and view its history (Ctrl-H or view -> history). In my experience it's much faster than mapki or even osmhv, taking 20s to show this test relation's history when the other two timed out on me. answered 09 Mar '16, 10:15 Vincent de P... ♦ |
Finding those relation versions from the full history dump on your home computer probably doesn't take as much time as you think. With the osmium command line tool you can easily pick out all the versions of a particular object. For instance reading all versions of the relation id 1820890 took only about 7 minutes on my notebook:
Downloading the full history dump will probably take longer. :-) Make sure to use the PBF version of the history and not the XML version, because parsing it is much faster. answered 09 Mar '16, 09:55 Jochen Topf |