It’s worth noting that the OSM API is for editing the map data, and if someone were to apply this solution to more than a few mappers who hadn’t made any changesets they’d run a chance of getting blocked. See https://wiki.openstreetmap.org/wiki/API_usage_policy.
I believe the changeset query is one of the more expensive ones. There aren’t any great solutions yet for small-scale historical analysis. From: Pierre Béland [mailto:[email protected]] Sent: Friday, May 31, 2013 8:38 PM To: Paul Norman; 'william skora'; [email protected] Subject: Re: [OSM-dev] Querying Changeset Tags in OSM API I work with Will on the CAP103 project and succeeded yesterday to calculate daily statistics for the CAP103 geographic zone. I adapted a python script originally written by Sebastien Pierrel. The OsmApi module contains changeset functions that are usefull to interrogate the OSM API and obtain the history of objects. For a BBOX, a specific contributor and a date range, we can interrogate the OSM API an list the changesets. Below are examples for changeset ID=16327554. And looking more in detail about the Changeset function, I see that there are collection of objects edited. We should be able with this historical data to calculate more detailed statistics (ie. objects created, modified, deleted). It is quitee easy to treat this with Python script but there might be some limits when interrogating the OSM API. Then, it is possible to shorten the period analyzed.
_______________________________________________ dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/dev
