Hi,

Last time I tried consuming augmented diffs on a minutely basis, I hit the 
load-limitations which meant that I could not consume augmented diffs for some 
time afterwards, i.e. this will lead to black holes in your history.

Also, using timestamp start/end to fetch diffs for a given timestamp (like 
avachi) is problematic with some changesets that stay open for > 1 hours (this 
happens quite ofter). The live service running on osm.expandable.dk use the 
API as described previously to get the augmented diff for a changeset. If 
there where a better way I'm all ears!

Regards,
MichaelVL

On søndag den 18. september 2016 01.59.57 CEST Stefan Keller wrote:
> Thanks mmd,
> 
> As said, I'd like to fetch the latest available augmented diff and
> keep uptodate.
> So, to understand it correctly:
> Every minute I first call the
> http://overpass-api.de/api/augmented_diff_status which returns an id,
> e.g. 2111988,
> then I fetch the augmented diff file
> http://overpass-api.de/api/augmented_diff?id=2111988
> Just want to be sure that this is the correct way to use the API.
> 
> :Stefan
> 
> 2016-09-17 16:48 GMT+02:00 mmd <mmd....@gmail.com>:
> > Am 15.09.2016 um 22:53 schrieb Stefan Keller:
> >> I'm setting up a Kafka publish-subscribe messaging system delivering
> >> minutely diffs.
> >> 
> >> AFAIK augmented diffs are rather an experimental feature and I'd like
> >> to avoid the latency time and blackouts of overpass which runs in same
> >> server. So I'm concentrating on the main OSM API.
> >> 
> >> Now, osmChange XML like
> >> http://www.osm.org/api/0.6/changeset/42143238/download obviously does
> >> not include all info (e.g. tags) from ref nodes/ways/relations.
> >> 
> >> I'm not looking for specific info but I'd like to get at least all
> >> data about nodes/ways/relations which are created/modified/deleted in
> >> a changeset.
> > 
> > This sounds a lot like what achavi is doing right now.
> > 
> > Note that with the introduction of the famous 'attic' concept, augmented
> > diffs are nowadays simply translated into a plain Overpass QL query and
> > calculated on the fly.
> > 
> > This also means that you don't have to stick to a minute interval or a
> > global scope as before: you're free to provide time intervals matching a
> > changeset (like achavi does), or restrict the adiff to a certain
> > bounding box or even some nodes/ways/relations with certain tags only.
> > 
> > There's no XSD around, the wiki page should answer most questions,
> > though. In general, the Overpass Dev list would be a good place for more
> > details and discussions. [1]
> > 
> > [1] http://listes.openstreetmap.fr/wws/info/overpass
> > 
> > 
> > 
> > 
> > _______________________________________________
> > dev mailing list
> > dev@openstreetmap.org
> > https://lists.openstreetmap.org/listinfo/dev
> 
> _______________________________________________
> dev mailing list
> dev@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/dev



_______________________________________________
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

Reply via email to