Step 4: Camera trap field protocol

A camera trap project works best when cameras are prepared, deployed, serviced, and retrieved in a consistent way.

This page provides a practical field protocol for camera trap monitoring. It covers what should happen before a Monitoring Session begins, how cameras should be installed and checked in the field, and what should happen when SD cards and cameras return from the field.

The exact protocol may need to be adjusted depending on the goals of the monitoring project, the camera models being used, and local knowledge about where and how cameras should be placed.

nota

Before standardizing a camera trap protocol, the team should have a clear understanding of why camera traps are being used and what questions the monitoring is intended to answer.

The appropriate number of cameras, locations, spacing, placement, duration, and other aspects of the protocol may depend on these goals.

Before a Monitoring Session

Before beginning a new Monitoring Session, prepare the cameras, SD cards, batteries, field data collection tools, and monitoring team.

Equipment checklist

• Check that every camera has a clearly visible camera ID.

• Place the label inside the camera door.

• Place another label on the bottom or exterior of the camera.

• Do not rename cameras between Monitoring Sessions.

• Check that every camera has two SD cards.

• Label both cards with the same ID as the camera.

• Add A and B to distinguish the two cards.

• For example, camera C01 should have SD cards C01A and C01B.

• Charge all rechargeable batteries.

• Recharge batteries even if they have not recently been used, since batteries can slowly lose charge while stored.

• Check that all cameras are functioning.

• Program all cameras using the agreed project settings.

• Confirm that the field data collection forms or categories are ready on the devices that will be used in the field.

important

The camera ID recorded in the field data, the ID physically written on the camera, and the ID written on its SD cards must match.

This relationship is what later allows the images on an SD card to be reliably connected to the camera deployment and location recorded in the field.

Prepare the monitoring team

Before beginning the Monitoring Session, make sure everyone participating understands the agreed workflow.

Review:

• How to record a camera deployment.
• How to record a maintenance visit or SD card change.
• How to record retrieval of a camera.
• The standard camera settings being used.
• The camera ID and SD card naming system.
• That camera IDs should not be renamed.
• The recommended camera height and positioning.
• How to perform the motion test.
• Why field records should be created while physically standing beside the camera.

Depending on the tools being used, these records might be collected with CoMapeo, ODK, KoboToolbox, a spreadsheet, paper forms, or another field data collection system. See Choosing a tool for deployment data collection.

Define the monitoring goals

Before a Monitoring Session, document what the project is trying to learn.

Questions to discuss include:

• Why are camera traps being used?
• What questions should the resulting data help answer?
• Are there particular species the team hopes to document?
• Is the project trying to determine whether particular species are still present?
• Are rare or difficult-to-observe species especially important?
• Is the project comparing different habitats, management areas, or environmental conditions?
• Is part of the goal to build community experience and familiarity with camera trap monitoring?
• Will the data eventually be used for quantitative analysis?
• If so, what kind of analysis?

nota

These questions do not need to have the same answers for every camera trap project.

Their purpose is to make sure the field protocol supports the actual monitoring goals rather than collecting camera trap data without a clear idea of how it will eventually be used.

Plan the Monitoring Session

A Monitoring Session groups together camera deployments that form part of the same monitoring effort.

For example:

Upper Jatapu Camera Trap Project

Monitoring Session: MS01

Cameras:
C01
C02
C03
C04
C05

When possible, deploy the cameras belonging to one Monitoring Session within a relatively short period, such as several consecutive days.

Similarly, plan to service or retrieve cameras on approximately the same schedule.

For example:

MS01

Deployment:
May 10–13

First maintenance visit:
approximately one month later

The exact schedule depends on battery life, SD card capacity, travel time, accessibility, and the goals of the project.

Decide how standardized placement should be

Before entering the field, discuss how much camera placement should be standardized.

For example:

• Should every camera be approximately the same height?
• Should cameras be placed on particular habitat features?
• Should cameras be spaced a particular distance apart?
• Should locations be selected primarily using local and Indigenous knowledge?
• Is the goal to document species presence, compare areas, estimate abundance, or answer another specific question?

A project designed for formal quantitative analysis may require a more standardized sampling design than a project focused primarily on documenting wildlife presence.

Camera settings

Cameras within the same monitoring project should normally use the same settings unless there is a specific reason to configure them differently.

Record and verify the agreed settings before cameras enter the field.

An example standardized configuration is:

Setting	Value
Date	Current date
Time	Current local time
Mode	Trail
Capture Delay	1 second
Picture Size	High 16 MP
MultiShot	RPF-2Shot
Capture Start	12:00 PM
Capture End	12:00 PM
SmartIR	On
Night Exposure	Fast Motion
Temperature Unit	°C
Info Strip	On
SD Management	Off
Motion Detection	Normal
Battery Type	NiMH
Language	English
Camera Name	Same ID written on the camera

nota

Camera menu options vary between manufacturers and models.

If different camera models are introduced, document the equivalent settings for each model rather than assuming that menu names and available options will be identical.

Deploying a camera

Complete a Camera Trap Deployment record whenever a camera is installed at a location.

A new deployment should also be recorded if one camera replaces another camera at an existing location.

For the full list of metadata fields to record, see What information should be recorded?.

Choose the location

Camera locations should reflect the goals of the monitoring project and the knowledge of the monitoring team.

Where appropriate, position cameras so that their field of view includes a feature identified through local or Indigenous knowledge as useful for observing wildlife, such as:

• Animal trails
• Water sources
• Feeding areas
• Crossing points
• Fruit-bearing trees
• Burrows
• Other locations where animals are expected to pass

Use lock boxes or other protection where there is a significant risk that cameras could be stolen or damaged.

Position the camera

Cameras should generally be installed approximately 0.5–2.0 meters above the ground.

For a more standardized installation, aim for approximately:

0.75–1.25 meters

Position the camera slightly downward from parallel with the ground when appropriate for the site.

The exact height may need to change depending on the target species, terrain, vegetation, and monitoring goals.

Clear the field of view

Before leaving the camera:

• Remove branches, leaves, and grasses directly in front of the camera.
• Look for vegetation that could move in the wind and repeatedly trigger the camera.
• Consider vegetation that may grow into the field of view during the next several weeks.
• Make sure the intended trail, feature, or monitoring area remains visible.

Some disturbance may temporarily affect wildlife activity immediately after installation, but an obstructed camera can produce poor data for the entire deployment.

Complete the deployment record

While standing beside the camera, complete the project's Camera Trap Deployment form or observation.

Record:

• Monitor name or username
• Monitoring Session ID
• Camera ID
• Installed SD card ID
• Place or location name
• Camera settings
• Camera height
• Information about the deployment location
• Motion-test result
• Any additional notes

Take a photograph showing the installed camera when possible.

important

Record the deployment while physically standing next to the camera whenever your data collection tool captures GPS coordinates.

Entering the information later or from somewhere else can result in an incorrect camera location.

Perform a motion test

Before leaving the site, confirm that the camera detects movement correctly.

Walk away from the camera while watching its motion-detection indicator.

Record approximately how far from the camera movement continues to trigger the detection light.

For example:

Motion detection distance: 11 m

Also trigger the camera intentionally and confirm that it is pointed toward the intended area.

Servicing a camera

Cameras should be revisited on an agreed schedule. For many projects, approximately once per month is a useful starting point for replacing SD cards, checking batteries, and inspecting the camera.

Complete a Camera Trap Maintenance record for each visit.

At the camera

Record:

• Monitor name or username
• Camera ID
• Whether the camera is still present
• Whether the camera is damaged
• Whether the camera was still functioning when the team arrived
• SD card being removed
• SD card being installed
• Any problems observed

Record the visit even if the camera has disappeared or appears to have been stolen.

Replace the SD card

Each camera should have two SD cards so that cards can rotate between the field and the computer.

For example:

Camera: C01

Removed:
C01A

Installed:
C01B

At the next maintenance visit:

Removed:
C01B

Installed:
C01A

Always verify the SD card ID before installing or removing it.

important

An SD card belonging to one camera should not be accidentally installed in another camera.

For example:

C01 → C01A / C01B
C02 → C02A / C02B

Keeping these relationships consistent greatly reduces the risk of losing the connection between images and deployment metadata.

Inspect the camera

Check whether:

• The camera is still securely attached.
• The camera is pointing in the intended direction.
• The enclosure has been damaged.
• Water has entered the camera.
• Animals have chewed or disturbed the camera.
• The tree or mounting point has moved.
• Batteries still have power.
• The SD card still has available space.
• The camera was still taking photographs when the team arrived.

Correct problems where possible and record significant issues.

Check date and time

Confirm that the camera's:

• Date
• Time
• Timezone, when configurable

are still correct.

Correct them if necessary and record any known timestamp problems.

Clear vegetation

Check the camera's field of view again.

Remove new vegetation that:

• Blocks the view
• Has grown directly in front of the camera
• Could repeatedly trigger the motion sensor

Repeat the motion test

Perform another motion test and record the approximate detection distance.

This can help identify cameras whose performance has changed over time.

Retrieving a camera

Complete a Camera Trap Retrieval record when a camera is removed from the field.

While standing at the camera location, record:

• Monitor name or username
• Camera ID
• Whether the camera was still present
• Whether the camera was damaged
• Whether the camera was still functioning
• SD card being retrieved
• Any problems or unusual conditions

Remove the camera and SD card from the field.

important

When GPS coordinates are being collected, record the retrieval before leaving the camera location so that the coordinates represent the actual deployment site.

Returning from the field

SD cards and batteries should be processed soon after returning from the field.

SD cards

For every returned SD card:

• Confirm the SD card ID.
• Copy all images and videos to the appropriate project folder.
• Confirm that the files copied successfully.
• Back up the media to a second storage device.
• Only clear the SD card after the files have been copied and backed up.
• Return the SD card to the equipment set for its camera.

For folder structure and SD card handling details, see Organizing camera trap photos and videos.

important

Camera trap media should have at least two copies before an SD card is erased or returned to the field.

For example:

Copy 1 → Working computer
Copy 2 → External hard drive

An SD card should not be treated as the long-term backup.

Batteries

For returned batteries:

• Recharge them as soon as practical.
• Inspect them for damage or corrosion.
• Store charged batteries with the equipment being prepared for the next Monitoring Session or maintenance visit.

Recommended field workflow

A complete Monitoring Session might follow this sequence:

Prepare cameras, SD cards, and batteries
                ↓
Confirm monitoring goals and field protocol
                ↓
Create Monitoring Session
                ↓
Deploy cameras over several days
                ↓
Record each deployment
                ↓
Return approximately monthly
                ↓
Replace SD cards and check cameras
                ↓
Record each maintenance visit
                ↓
Copy and back up media
                ↓
Return to service cameras as needed
                ↓
Retrieve cameras
                ↓
Record each retrieval
                ↓
Copy and back up final media

The deployment, maintenance, and retrieval records can be collected using whichever tool is most appropriate for the project, including CoMapeo, ODK, KoboToolbox, spreadsheets, or paper forms.

The goal is to maintain a consistent relationship between the physical equipment, the field records, and the media collected by each camera throughout the entire Monitoring Session.