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

only write to s3 if data has changed #10

Open
smnorris opened this issue Aug 29, 2024 · 1 comment
Open

only write to s3 if data has changed #10

smnorris opened this issue Aug 29, 2024 · 1 comment

Comments

@smnorris
Copy link
Collaborator

Updated requirement - it is not necessary to retain all downloads indefinitely - only write download to s3 if something has happened.

A file structure something like this should work:

/MVRD/surrey/<layer>.gdb.zip                                                            
/MVRD/surrey/<layer>_changes/<layer>.gdb.zip               
/MVRD/surrey/<layer>_changes/change_report.xlsx      
/MVRD/surrey/<layer>_changes/change_report.gdb.zip
@smnorris
Copy link
Collaborator Author

smnorris commented Sep 11, 2024

Definitions of data in the changes folder:

  1. Spatial layers representing the diff
  • additions
  • deletions
  • modifications - geometry only
  • modifications - attribute only (with old/new attribute diff)
  • modifications - geometry + attribute (with old/new attribute diff)

All modification layers to use the latest geometries.

2 Report summarizing changes with columns:

  • jurisdiction
  • layer
  • record_count_old
  • record_count_new
  • record_count_difference
  • record_count_difference_pct
  • n_unchanged
  • n_deletions
  • n_additions
  • n_modified
  • n_modified_spatial_only
  • n_modified_spatial_attributes
  • n_modified_attributes_only

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

No branches or pull requests

1 participant