Multiple deployment import CSV fields

Modified on Thu, 2 Apr at 12:57 PM

This guide provides detailed information about the fields in the import multiple deployments CSV file, their behaviour when importing into the WildObs Image Platform, and links to more information. For more information on how to upload multiple deployments to a project, visit Import multiple deployments to a project.


This guide is for WildObs platform testers only. You will not be able to sign in to the WildObs test platform if you have not been invited by the WildObs team. If you are interested in becoming a platform tester, please register your interest here


TABLE OF CONTENTS


The CSV file must use the exact column names as the example CSV, which can also be downloaded from the project overview page. Read on for further details on each column. 


Notes about the following information:

  • Each row of the CSV file will be treated as an individual deployment. 
  • Required fields are denoted by an asterisk, all other fields are optional. 
  • If the field maps directly to a Camtrap DP field, a link to the Camtrap DP page is provided which contains more information, constraints and examples. 


Location information

The following details create a location entry within the project that can then be selected for future manual uploads. At present, new Location entries are created for each line/deployment even if they are identical.


locationID *

Identifier describing the field location.


Each location ID should have unique coordinates. 


In the platform, this is called location name. 


https://camtrap-dp.tdwg.org/data/#deployments.locationID


string

latitude * 

Geographic latitude of the deployment site. Example: 45.12345

https://camtrap-dp.tdwg.org/data/#deployments.latitude


number

longitude * 

Geographic longitude of the deployment site. Example: 45.12345
https://camtrap-dp.tdwg.org/data/#deployments.longitude


number


Camera information

A unique set of camera information creates a Camera entry within the Project that can then be selected for future manual uploads. If identical information is used, only one new Camera entry will be added. 


cameraID *

Unique camera identifier. e.g., CAM_1001

It is recommended that the camera serial number is used as the cameraID to align with Camtrap DP https://camtrap-dp.tdwg.org/data/#deployments.cameraID

string

cameraMake

Manufacturer and model of the camera formatted as manufacturer-model.

Example: Reconyx-PC800

https://camtrap-dp.tdwg.org/data/#deployments.cameraModel


string

cameraSerialNo

Serial number of the camera.

string

cameraYOP

Year of purchase of the camera.

integer


Time information

deploymentStart *

Date or date-time when the deployment begins.

Examples:
12/02/2025
12/02/2025, 12:06:00 AM

When exported from the platform, this field will be converted to the correct format for https://camtrap-dp.tdwg.org/data/#deployments.deploymentStart


DD/MM/YYYY

or

DD/MM/YYYY, HH:MM:SS [AM or PM] 

deploymentEnd *

Date or date-time when the deployment ends. Must occur after the deployment start.

Examples:
12/02/2025
12/02/2025, 12:06:00 AM

When exported from the platform, this field will be converted to the correct format for https://camtrap-dp.tdwg.org/data/#deployments.deploymentEnd


DD/MM/YYYY

or

DD/MM/YYYY, HH:MM:SS [AM or PM]

utcOffset

Time zone offset for the deployment.  If not provided, the system will use the user's local time zone. Must start with "UTC".

Example: UTC+10


UTC[+ or -]HH

timestampIssues

Used to indicate known timestamp problems.

Reflected as "Invalid" column in deployments. Invalid deployments are excluded from data exports.


https://camtrap-dp.tdwg.org/data/#deployments.timestampIssues
TRUE or FALSE


Deployment classification

deploymentTags

Tags used to describe the deployment.

Example: Tag 1, TAG2, Tag*3

When exported from the platform, this field will be converted to the correct format for https://camtrap-dp.tdwg.org/data/#deployments.deploymentTags


string

Comma-separated values

deploymentGroups

Labels used to group deployments, particularly denoting when and where deployments occurred.

Example: Group 1, Group2

When exported from the platform, this field will be converted to the correct format for https://camtrap-dp.tdwg.org/data/#deployments.deploymentGroups


string

Comma-separated values


Camera setup information

detectionDistance

Maximum distance in meters at which the camera can reliably detect activity.
https://camtrap-dp.tdwg.org/data/#deployments.detectionDistance


number

cameraHeight

Height of camera installation in meters.

https://camtrap-dp.tdwg.org/data/#deployments.cameraHeight


number

cameraHeading

Camera installation direction.

The exact value of this field must match one of:
North

North-East

East

South-East

South

South-West

West

North-West


Example: North-East

When exported from the platform, this field will be converted to the correct format for https://camtrap-dp.tdwg.org/data/#deployments.cameraHeading


string

cameraTilt

Vertical tilt angle of camera installation, where -90 is facing down, 0 is horizontal and 90 is facing up.

The value can range from -90 to 90.

Example: -20

https://camtrap-dp.tdwg.org/data/#deployments.cameraTilt


number

baitUse

Indicates whether bait was used.

The exact value of this field must match one of:
Food
No bait
Visual
Other bait
Acoustic
Scent

Example: No bait

The WildObs Image Platform only supports a single value from a set selection. When exported from the platform, this field will be converted to a boolean value of true or false to meet the correct format for https://camtrap-dp.tdwg.org/data/#deployments.baitUse
string


Personnel information

If the person in the following fields is a user on the project, use the matching first name and last name for the person. If details entered do not match a user on the project, the Principal Investigator will be added to these fields. 

If there is no Principal Investigator set, it will default to the project owner. Entering details here that do not match an existing user will not create a user on the project. 


setupBy

Person responsible for camera setup. 

Example: Jane Doe

https://camtrap-dp.tdwg.org/data/#deployments.setupBy

string

pickupBy

Person responsible for retreiving the camera. 

Example: Jane Doe


string



Additional information

deploymentComments


Free-text field for notes about the deployment.
https://camtrap-dp.tdwg.org/data/#deployments.deploymentComments

string


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article