We are currently running many processes based on minutely augmented diffs. These are generated by a process (overpass-diff-publisher) that is a bit mysterious (possibly furnished by this repo?).
We have observed cases where some users' geometry updates are not appearing in the augmented diff stream. This is a problem, since we are treating the augdiff stream as the authoritative source of truth for our processes. We need to track down how the augdiffs are getting generated, attempt to start a new process to generate said stream from a sufficiently early time, and confirm that the new stream is capturing geometry as it should.
We are currently running many processes based on minutely augmented diffs. These are generated by a process (overpass-diff-publisher) that is a bit mysterious (possibly furnished by this repo?).
We have observed cases where some users' geometry updates are not appearing in the augmented diff stream. This is a problem, since we are treating the augdiff stream as the authoritative source of truth for our processes. We need to track down how the augdiffs are getting generated, attempt to start a new process to generate said stream from a sufficiently early time, and confirm that the new stream is capturing geometry as it should.