Data integrity endpoints #17

Open
opened 2025-10-25 17:14:18 +02:00 by ViMaSter · 0 comments
Collaborator

As of 25-10-2025, instances provide no way to synchronize or compare datasets.
While data integrity for OSM cannot be guaranteed, other instances of SunderS should be able to compare their datasets with one another.

Instances should provide an HTTP endpoint that takes a timestamp and returns a hash of the current dataset up to that point.
Instances should also provide an HTTP endpoint that takes a timestamp and URL to another instance, generates the hash up to that point, compares it with the instance provided, and returns the result to the user.

As of 25-10-2025, instances provide no way to synchronize or compare datasets. While data integrity for OSM cannot be guaranteed, other instances of SunderS should be able to compare their datasets with one another. Instances should provide an HTTP endpoint that takes a timestamp and returns a hash of the current dataset up to that point. Instances should also provide an HTTP endpoint that takes a timestamp and URL to another instance, generates the hash up to that point, compares it with the instance provided, and returns the result to the user.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
CCCHH/sunders#17
No description provided.