[OSM-talk] New API suggestion: Allowing contributors to easily track their OSM-objects over time

[mmd]

On 2020-08-22 11:08, pangoSE wrote:
> The system can then be queried lke this:
> 
> IMPLEMENTATION SUGGESTION:
> 
> GET Openstreetmap.org/api/userobjects/pangoSE
> Outputs objects for user pangoSE with the oldest first (outputs 10
> entries, &offset can be used to get more, &size can be used to output up
> to 300 entries, &modified_date=desc by default)

I don't think this is in any way feasible for the main API (and it
wouldn't fit its main purpose as editing API due to the analytical
nature of this request).

OTOH, I know that some people monitor dozens of boundary relations for
any changes via a single Overpass API queries. If you run your own
Overpass instance, and feed it with a list of object ids, you already
have your solution, and we can stop the discussion right here.

Transitions from "I used to be a node, and now live on as way" are more
complex to deal with. At least you would find out that the node ceases
to exist at one point.

By the way, quite a number of people have come up with your suggestion
before, and those projects always projects fail due to the sheer size of
OSM data. OWL (that was one project that was mentioned as GSoC project
in another thread) never took off exactly for that reason.

--