A version of CGImap [1] has been deployed which supports "OAuthed rate
limits". What this means is that requests with a valid OAuth signature
will be rate-limited by user account rather than source IP address

This probably makes no difference for most of us, most of the time.
But it potentially could make a huge difference to people at mapping
parties or any other situation where a large number of people are
trying to map from behind a NAT router or firewall.

At the moment, I don't think any editors send OAuth-signed requests
unless authorisation is required for that particular API call, but I
hope that it will be easy to integrate this feature (perhaps
optionally after receiving "509 Bandwidth Limit Exceeded"). Please let
me know or file an issue [3] if you are getting unexpected errors with
OAuth-signed requests, or if there's anything I can help with adding
this feature to your editor.

Another feature released along with this is CGImap support for the
/changesets/#{id} call, including discussions. Again - please let me
know or file an issue [3] if you notice anything amiss with this call.

There is on-going work to support historical versions of elements [4],
which I hope will lead to support for history calls as well as
changeset/#{id}/download (osmChange) API calls. And eventually, the
whole API [5]. If you'd like to help, please take a look at the source
code and get in touch!



[1] https://github.com/zerebubuth/openstreetmap-cgimap/releases/tag/v0.5.5
[2] https://github.com/openstreetmap/operations/issues/36
[3] https://github.com/zerebubuth/openstreetmap-cgimap/issues
[4] https://github.com/zerebubuth/openstreetmap-cgimap/tree/history
[5] http://www.asklater.com/matt/blog/2015/11/18/the-road-to-api-07/

dev mailing list

Reply via email to