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 which returns an id,
e.g. 2111988,
then I fetch the augmented diff file
Just want to be sure that this is the correct way to use the API.


2016-09-17 16:48 GMT+02:00 mmd <>:
> 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
>> 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]
> _______________________________________________
> dev mailing list

dev mailing list

Reply via email to