Suggested in camtraptor July 2023 coding sprint

It is a fair expectation that camtraptor also support writing Camtrap DP, to e.g. share cleaned datasets or publish it on the IPT.

Use cases

• Reading Camtrap DP, cleaning and writing: Create update_deployments(), update_media(), update_observations() to update dataframes camtraptor#248
• Reading Camtrap DP, round_coordinates() and writing
• Reading Camtrap DP, filtering and writing: Create filter_deployments(), filter_observations(), filter_media() #23
• Reading Camtrap DP, merging and writing: Create merge() to merge datasets #75
• Reading Wildlife Insights export and writing

All these start from a package object. It will therefore be harder to create a Camtrap DP entirely from scratch, but it could be possible with:

p <- frictionless::create_package()
# user add necessary metadata as elements to list
deployments(p) <- df
media(p) <- df
observations(p) <- df
write_camtrap_dp(p, "directory")

Functionality

• Make best attempt at creating a valid Camtrap DP. E.g. by running validate() Create validate_camtrapdp() and helper functions to validate integrity of a Camtrap DP #58 (and refusing to write if there are errors?)
• read_camtrap_dp() %>% write_camtrap_dp() should create the exact same package (except for created date)
• All existing metadata elements should be retained
• If required metadata elements are not present, user should be warned (especially important if package was created from scratch)
• taxonomy, spatial and temporal should be recreated based on the (filtered) data
• A package that is the result of a merge() Create merge() to merge datasets #75 should combine its metadata (not sure how)