[OSM-dev] Read-only API calls, fair usage

[Simon Poole]

IMHO it boils down to one extra API call per edit made in a maproulette
context(on top of a minimum of two API calls (if the editor is doing
things properly that is actually three), so likely it is simply a bit of
added noise, depending on how expensive
https://wiki.openstreetmap.org/wiki/API_v0.6#Query:_GET_.2Fapi.2F0.6.2Fchangesets
is (which depends on which indices exist on the table etc).

I suppose the timing might be a tiny bit tricky due to replication
delays and against which DB server the query runs in the end.

Simon


Am 20.02.2018 um 01:44 schrieb Martijn van Exel:
> Hi, 
>
> We’re thinking about adding task completion validation to MapRoulette. The basic premise is this: a user completes a task in MapRoulette, and marks it as ‘Fixed'. MapRoulette would then make an OSM API call for recent changesets by that same user, and make a best effort at matching a recent changeset to the task they say they completed. This would mean one call to https://www.openstreetmap.org/api/0.6/changesets?user= for every stated Fix in MapRoulette. Currently the number of fixes is in the thousands per week, but that may grow as we roll out the new version of MapRoulette.
>
> Would you consider this a reasonable use of the OSM API?
>
> Martijn
>
>
>
>
>
> _______________________________________________
> dev mailing list
> dev at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/dev


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstreetmap.org/pipermail/dev/attachments/20180220/b5cbbd77/attachment.sig>