Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for arbitrary conflict resolutions #101

Merged
merged 1 commit into from
Jun 7, 2020
Merged

Conversation

olsen232
Copy link
Collaborator

@olsen232 olsen232 commented Jun 5, 2020

$ sno conflicts -s --flat
table_A:fid=5
table_A:fid=6
table_A:fid=7

$ sno resolve table_A:fid=5 --with-file=5.geojson
Resolved 1 conflict. 2 conflicts to go.

The user can provide an arbitrary number of features in a geojson file, and store them as the resolution to a conflict. Generally, the appropriate number of features will be either 1 - in the case of an edit/edit conflict that needs manual resolution - or 2, in the case of an add/add conflict, the resolution should probably contain both features in some form. (Zero is also a useful number of features, but it is already possible to resolve a conflict by supplying zero features without providing a file).

sno/gpkg.py Outdated Show resolved Hide resolved
sno/resolve.py Outdated Show resolved Hide resolved
sno/resolve.py Outdated Show resolved Hide resolved
@olsen232 olsen232 merged commit d161ddd into master Jun 7, 2020
@olsen232 olsen232 deleted the resolver branch June 7, 2020 22:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants