This issue is a duplicate with an issue i made previously on the campraptor github page. inbo/camtraptor#297
When a timeLapse photo is taken while a motion trigger is active, read_camtrapdp() now duplicates the eventID of the timeLapse sequence and activityDetection sequence. This issue seems to be triggered only when a timeLapse is taken during a acitivity trigger. It occurs here in the source code: https://github.com/inbo/camtraptor/blob/45b72a292ac040d94af86c7131e992df41d3999a/R/zzz.R#L716 when the event_obs is joined to the media. This is done on the basis of deploymentID and a time interval, without specifying what type of trigger induced the asset creation.
A proper way to solve this issue would be adding back the eventID-identifier to the media.csv (now absent) and joining to eventID. Otherwise adding an extra grouping to the event_obs join that differentiates between timeLapse and activityDetection would likely solve the issue. However, it does not seem right to drop a key column like eventID from the media.csv because it holds the very much required connection of asset-info to the photo sequences.
A dummy project reproducing the issue is available, as is an example script.
See below an example of the issue
Kind regards,
Laurens Dijkhuis
This issue is a duplicate with an issue i made previously on the campraptor github page. inbo/camtraptor#297
When a
timeLapsephoto is taken while a motion trigger is active,read_camtrapdp()now duplicates theeventIDof thetimeLapsesequence andactivityDetectionsequence. This issue seems to be triggered only when atimeLapseis taken during a acitivity trigger. It occurs here in the source code: https://github.com/inbo/camtraptor/blob/45b72a292ac040d94af86c7131e992df41d3999a/R/zzz.R#L716 when the event_obs is joined to the media. This is done on the basis ofdeploymentIDand a time interval, without specifying what type of trigger induced the asset creation.A proper way to solve this issue would be adding back the eventID-identifier to the media.csv (now absent) and joining to
eventID. Otherwise adding an extra grouping to the event_obs join that differentiates betweentimeLapseandactivityDetectionwould likely solve the issue. However, it does not seem right to drop a key column likeeventIDfrom the media.csv because it holds the very much required connection of asset-info to the photo sequences.A dummy project reproducing the issue is available, as is an example script.
See below an example of the issue
Kind regards,
Laurens Dijkhuis