Am 19.09.2016 um 05:50 schrieb patrick keshishian:
> It seems that this association is a mistake. If so, is there a
> better place to report these sort of things as I come across them?
> As I am still learning my way through the data, I don't wish to
> do wholesale edits.
You can add a note about
Greetings,
Sorry about the subject line. I couldn't come up with anything better.
Continuing to learn my way through "relations" and assorted "tags",
I came across relation=3489649 [0], island of Oahu, HI, USA. What
interests me is its "way" member=428362225 (Way: War Memorial World
War II) [1]
Am 18.09.2016 um 15:27 schrieb Stefan Keller:
>
> 0. The typical delay (augmented diff id) compared to current time is 1
> to 4 minutes.
Right, you can see the current delay in munin [1], and the current
timestamp via a dedicated API call [2].
[1]
Thanks mmd: That was exactly what I tried to summarize after some observations:
0. The typical delay (augmented diff id) compared to current time is 1
to 4 minutes.
1. The id is always increasing but sometimes an id (or more) is/are
left out between to consecutive deliveries.
2. The time interval
Hi,
Am 18.09.2016 um 14:41 schrieb Michael Larsen:
> 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.
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
6 matches
Mail list logo
