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

> > There's no guarantee that the read-only changeset call will go to the same > backend server as the write call. > https://github.com/openstreetmap/iD/issues/1646 shows the problem caused > by iD not parsing the diff response and relying on redownloading. > This suggests that currently apidb

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

On 2/20/2018 2:56 AM, Frederik Ramm wrote: Hi, On 20.02.2018 10:51, Michał Brzozowski wrote: You can use changeset replication with ChangesetMD to query your own DB. I was tempted to respond the same, but I imagine the idea is that as soon as the user clicks on the "I have fixed this" button,

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

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

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

Hi, On 20.02.2018 10:51, Michał Brzozowski wrote: > You can use changeset replication with ChangesetMD to query your own DB. I was tempted to respond the same, but I imagine the idea is that as soon as the user clicks on the "I have fixed this" button, MapRoulette checks what has been

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

You can use changeset replication with ChangesetMD to query your own DB. Michał 20.02.2018 01:45 "Martijn van Exel" napisał(a): > Hi, > > We’re thinking about adding task completion validation to MapRoulette. The > basic premise is this: a user completes a task in MapRoulette,

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

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