Multiple versions of an element in the same changeset

Help and support
1

Hello, how is it possible that several versions of an element, like a node for example, are generated in the same changeset?
Example:
changeset 846962, node 317780185 v116 to v128
https://osmlab.github.io/osm-deep-history/#/node/317780185

2

These changes were made 13 years ago, maybe script created many identical versions and the server created many versions. The algorithms were significantly less advanced at the time.

3

Thanks, it seems something like that.
Another example, October 2021, a relation:

changeset 112464934 v180 to v186
9924323

4

It is still pretty common https://www.openstreetmap.org/changeset/120376431 is one of mine from yesterday.

If you save before closing a changeset, it can happen.

3 Likes
5

If someone changes the members (composition, order, or assigned roles) in a relation, then the version changes. Most likely the reason is this.

1 Like
6

The OSM API even allows to create multiple versions of the same object in the same upload. Some editors also don’t consolidate multiple changes into a single change. While this is not perfect, it’s still technically valid.

2 Likes
7

Changesets are not atomic, so you could modify an object in one upload, then modify it again in a second upload.

8

As said, it doesn’t even require a second upload. You can achieve the same result with a single upload only.