store versions to compare historical edits about osm-p2p-db HOT 2 CLOSED

Thinking about this more... this does increase the chance of forks being created, i.e. without this two users could move some nodes in a way and the way would not appear as forked. Is there a way around this by comparing the seq number of nodes within a way to the seq of the way, hence knowing which nodes have been edited since the way version was edited? That would be enough to be able to show a history of the geometry of the way.

I don't think this is needed for relations. I also wonder whether we should be internally storing members on the relation object at all? Instead store a owners property on the members of a relation? The order of members in a relation does not matter. Ideally we can store long ways (rivers, paths, roads) as relations and minimize conflicts / forks when different users edit different parts of a way. This way additional ways could be added to a relation without bumping the version number of the relation itself.

from osm-p2p-db.

Moved to #49

from osm-p2p-db.