Create active_time()

[jimcasaer]

Create new indicator based on number with at least one observation of a species within a deployment

• somewhere between the RAI (#obs / #days of effort within the deployment) and raw occ (number of deployments having at least on obs of the species / total number of deployments) there is the #days with at least one observation (of a species) / #days of camera trap effort within the deployment => this ranges from 0 tot 1 (each day of the trapping effort)
• given that this indicator can be calculated for each deployment this could easily be integrated as a feature in map_dep()

[damianooldoni]

Nice feature. Yes, it's possible to visualise it of course.

We can use number of days, but we could use hours, weeks or months as well. So, days should be the default value of an argument.

Now, the most difficult stuff: naming. As this function measures the proportion of active days/hrs/weeks/months, I think to a name like get_active_time(). @jimcasaer, @peterdesmet ?

[peterdesmet]

Suggested in camtraptor July 2023 coding sprint

active_time(
  package = NULL,
  group_by = "deploymentID" # new param, not sure if other groups make sense?
)

The returned information would be:

deploymentID
active_time