9.0 Image/Sequence#

The image/sequence level provides information on the data for an image (individual photo) or sequence of related images (e.g., images that are grouped as part of the same trigger “event”).

An image may be part of a multi-image sequence.

A sequence refers to a user-defined group of images or video clips that denote a single “detection event”. Often camera users choose a certain time threshold (or “inter-detection interval”) to define independent detection events; (e.g., 30 minutes (O’Brien et al., 2003; Gerber et al., 2010; Kitamura et al., 2010; Samejima et al., 2012) or 1 hour (e.g., Tobler et al., 2008; Rovero and Marshall, 2009)). This threshold should be recorded in the Survey Design Description field, if applicable.

When a Sequence Event Type is used, only enter data once for the sequence of images (not for each unique image) and use the first image of the sequence as the Sequence Name, as this is the time of the first detection.

Refer to the Data Management section for information on image processing software, and recommendations on data file structure and naming conventions.

9.1 Image Name#

A unique alphanumeric identifier for the image. It is highly recommended that users develop a photo naming convention prior to entering data. It is important to include (at a minimum) the camera location, date, time, and image number when generating an Image Name to avoid duplicate file names. For example, the Deployment Name and image number would not be unique for the same deployment within Reconynx overflow file subfolders (i.e., when the number of images exceeds 9,999, another folder is created [e.g., 101MEDIA] and the numbers in the image file names begin again at img_001).

We recommend using either of the following naming conventions for Image Names:

  1. Deployment Name”_Camera_Serial Number”_Image_Sequence_Date_Time”_”Image Number” (e.g., “bh1_17-Jul-2018_P900FF04152022_22-Jul-2018_10:34:22_img_100”), or

  2. Deployment Name”_Image_Sequence_Date_Time”_”Image Number” (e.g., “bh1_17-Jul-2018_22-Jul-2018_10:34:22_img_100”)

The file name used to create the Image Name should ideally match the file name of the original image.

9.2 Sequence Name#

A unique alphanumeric identifier for a multi-image sequence.

The Sequence Name should ideally consist of the Deployment Name and the names of the first and last images and videos in the sequence (separated by “”) (i.e., “Deployment Name”_”img_#[name of first image in sequence]”_”img#[name of last image in sequence].” For example, if a particular sequence contains five images, the Sequence Name might be “bh1_22-Jul-2018_img_001-img_005.” If “img_ “ prefixes are used to create the Sequence Name, they ideally should match the names of the original photos. Leave blank if not applicable.

Even though the first image of a sequence is the only image used to derive the Sequence Name, the remaining images typically also include useful information (e.g., images of all individuals in a group). Therefore, it is ideal to archive all of the images from a sequence. If it is not possible to submit all of the images, users should ideally submit the image(s) from a sequence that best represents the sequence (e.g., those that can be used to verify the Species and Individual Count).

9.3 Image/Sequence Date Time (DD-MMM-YYYY HH:MM:SS)#

The date and time of an image, or the image chosen to represent the sequence, recorded as “DD-MMM-YYYY HH:MM:SS” (e.g., 22-Jan-2018 12:00:02).

Sequence date/time information may be reported for a “representative image” of a sequence (i.e., the image with the most information). For example, if three images were included in a sequence, but the Sex Class could only be discerned in the second image [all else remaining equal], the second image would be the best representative image of the sequence.

The Image/Sequence Date Time differs from the Image Set Start Date Time which refers to the first image or video collected during a deployment.

9.4 Analyst#

The first and last names of the individual who provided the observation data point (Species identification and associated information). If there are multiple Analysts for an observation, enter the primary Analyst.

9.5 Species#

The common name of the Species being categorized (“tagged”) in the tag, image or sequence (e.g., “coyote” or “common goldeneye”). If there is more than one wildlife Species present in an image/sequence, data for each Species should be entered on a unique row but with the same Image Name or Sequence Name (reporting as Event Type = “Tag”).

For detections where you are unsure of the specific Species, report the level of lowest taxonomic ranking known (e.g., “class,” “order,” “family,” “genus”), followed by the scientific name of the taxa.

For example, for a detection of an individual that is in the Canidae family, but for which the genus or Species or unclear, report “family canidae.” Refer to the species_crosswalk tab of the Remote Camera Metadata Standards: Metadata Template v3 (RCSC, 2024) for ease of reference.

If no Species is present (i.e. blank or empty image), enter “none.”

9.6 Individual Count#

The number of unique individuals being categorized. Depending on the Event Type, this may be recorded as the total number of individuals, or according to Age Class and/or Sex Class.

9.7 Age Class and Sex Class#

The age and sex classification of an individual(s) being categorized.

Select one Age Class from the following:

  • “Adult” (animals that are old enough to breed; reproductively mature)

  • “Juvenile” (animals in their first summer, with clearly juvenile features (e.g., spots); mammals older than neonates but that still require parental care)

  • “Subadult” (animals older than a “Juvenile” but not yet an “Adult”; a “Subadult” may be further classified into “Young of the Year” or “Yearling”)

  • “Subadult - Young of Year” (animals less than one year old; born in the previous year’s spring, but has not yet lived through a winter season; between “Juvenile” and “Yearling”)

  • “Subadult - Yearling” (animals approximately one year old; has lived through one winter season; between “Young of Year” and “Adult”)

  • “Unknown”

Select one Sex Class from the following:

  • “Male”

  • “Female”

  • “Unknown”

If there is more than one Age Class or Sex Class in an image/sequence, users can enter either:

  1. each unique Age Class/Sex Class combination as a unique row (Event Type = “Image” or “Sequence” or

  2. each unique combination within the same row under an appropriate field (Event Type = “Tag”)

For example, if an image/sequence contains 6 elk, 2 of which are adult females, 3 of which are juveniles of unknown sex and one of which is an adult male, the data could be entered as 3 unique rows, each with the same Image/Sequence Date Time) and unique identifier (Image Name or Sequence Name), where:

Alternatively, the same data could be entered in one single row as:

Deciding how to enter the data is at the user’s discretion. However, the recommended approach to entering data where unique individuals are identified (or the Behaviours of individuals are identified) is to enter data for each individual as a unique row.

9.8 Behaviour (optional)#

The Behaviour of the individual(s) being categorized.

Select one of the options from the list provided:

  • “Travelling”

  • “Standing”

  • “Running”

  • “Bedding”

  • “Drinking”

  • “Feeding/Foraging”

  • “Territorial Display”

  • “Rutting/Mating”

  • “Vigilant”

  • “Inspecting Camera”

  • “Inspecting (Non-specified)”

  • “Unknown”

  • “Other§” (describe in Image/Sequence Comments field)

  • “Multiple§” (describe in Image/Sequence Comments field; e.g.,”Behaviour[Standing,Vigilant]”)

  • “Unknown” (not applicable or did not collect)

If observing a group of individuals, record the Behaviour of all the individuals in the group or enter the Behaviour of each animal as a unique row (see example in the Age Class and Sex Class section above).

If an animal is performing multiple Behaviours, select “Multiple§,” and include all the Behaviours in the Image/Sequence Comments as a comma delimited list. To help parse out this information later most easily, we recommend using a format that includes a header followed by the Behaviour(s), e.g., “Behaviour[Inspecting Camera,Travelling].”

9.9 Animal ID (optional)#

A unique ID for an animal that can be uniquely identified (e.g., marked in some way). If multiple unique individuals are identified, enter an Animal ID for each as a unique row. Leave blank if not applicable.

9.10 Human Transport Mode/Activity (optional)#

The activity performed, or mode of transportation used, by a human observed (e.g., hiker, skier, off-highway vehicle, etc.). This categorical field should be populated when data on humans (in addition to wildlife) are collected.

Select one of the options from the list provided:

  • “Activity - Walking”

  • “Activity - Hiking” (e.g., backpacker)

  • “Activity - Running”

  • “Activity - Cycling” (e.g., non-motorized or e-bike)

  • “Activity - Skiing”

  • “Activity - Snowshoeing”

  • “Activity- Fishing”

  • “Activity - Hunting”

  • “Activity - Unspecified”

  • “Transport - Horse/Mule”

  • “Transport - Off-Highway Vehicle” (e.g., all-terrain vehicle, snowmobile, motorbike, snowmobile, 4 x 4 truck)

  • “Transport - Passenger Vehicle” (e.g., car, truck without 4x4)

  • “Transport - Large Commercial Vehicle/Heavy Equipment” (e.g., logging truck, semi-truck, bus)

  • “Transport - Unspecified”

  • “Activity/Transport - Other§” (describe in Image/Sequence Comments field)

  • “Unknown” (not applicable)

Where there are multiple individuals and transport modes within a tag, image, or sequence, enter the data for each individual mode as a unique row. Leave blank if not applicable and record “Unknown” if not known.

9.11 Image/Sequence Comments (optional)#

Describe any additional data about the image or sequence.

If you selected the “Multiple§” option from the Behaviour field, enter all the Behaviours here (e.g., “Behaviour[Inspecting Camera,Travelling]”)

9.12 Image Trigger Mode (optional)#

The type of Trigger Mode used to capture the image as reported in the image Exif data. This field is categorical; record “Unknown” if not known.

Data should be entered as one of the following:

  • “Motion Detection”

  • “Time Lapse”

  • “CodeLoc Not Entered”

  • “External Sensor”

  • “Unknown”

9.13 Image Sequence (optional)#

The order of the image in a rapid-fire sequence as reported in the image Exif data (text; e.g., “1 of 1” or “1 of 3”). This field is in text format; leave blank if not applicable.

9.14 Image Infrared Illuminator (optional)#

The Image Infrared Illuminator is an image metadata field indicating whether the infrared illuminator setting was enabled (if applicable; to obtain greater visibility at night by producing infrared light). Record as reported in the image Exif data (e.g., “On” or “Off”). This field is categorical; leave blank if not applicable and record “Unknown” if not known.

Data should be entered as one of the following:

  • “On”

  • “Off”

  • “Unknown”

9.15 Image Flash Output (optional)#

The Image Flash Output is an image metadata field indicating the level of intensity of the flash [if enabled/applicable]). Record as reported in the image Exif data (e.g., “Flash Did Not Fire”, “Auto”). This field is in text format; record “Unknown” if not known; leave blank if not applicable.