mmd-osm left a comment (openstreetmap/openstreetmap-website#6361)
> Could the issue be, that current_num_changes counts only the objects where
> some values (tags/location/members) had really changed
Let's take a look at your second changeset:
https://master.apis.dev.openstreetmap.org/changeset/437817
Since you have uploaded both relation and node in the osmChange message, both
of them end up with a new version in that changeset:
<img width="333" height="177" alt="image"
src="https://github.com/user-attachments/assets/425b454c-aac9-42dd-9545-82dc5d29ecec";
/>
Now, in the changeset metadata
https://master.apis.dev.openstreetmap.org/api/0.6/changeset/437817 , we can see
the number of changes as expected:
```
changes_count="2"
```
So the number of changes reflects any new/modified/deleted object version in
that changeset. It doesn't really matter if you're re-uploading the exact same
object again. The issue is non-deterministic and timing dependent, otherwise we
would see this for many more changesets.
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/pull/6361#issuecomment-3233683214
You are receiving this because you are subscribed to this thread.
Message ID:
<openstreetmap/openstreetmap-website/pull/6361/[email protected]>
_______________________________________________
rails-dev mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/rails-dev
