Deployment and Import All CSV fields

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 (in progress).

TABLE OF CONTENTS

• About deployment fields
• How the Import All CSV file is processed
• Location information
  • locationID *
  • latitude * 
  • longitude * 
• Camera information
  • cameraID *
  • cameraMake
  • cameraSerialNo
• Time information
  • deploymentStart *
  • deploymentEnd *
  • utcOffset
  • timestampIssues
• Deployment classification
  • deploymentTags
  • deploymentGroups
• Camera setup information
  • detectionDistance
  • cameraHeight
  • cameraHeading
  • cameraTilt
  • baitUse
• Personnel information
  • setupBy
  • pickupBy
• Additional information
  • deploymentComments

About deployment fields

Deployment fields populate the deployments.csv file of the Camera Trap Data Package (Camtrap DP). 

This information can be entered to the WildObs Image Platform when you Add a deployment to a project or you can Import multiple deployments to a project at once by uploading a pre-filled CSV file. 

The tables in each section below provide the following information:

• CSV name – Header name of the column for the multiple import all CSV file. 
• Field name - This is the name of the field on the WildObs Image Platform. If the field appears differently depending upon the current view, multiple names may be added. For example, Deployment / Camera identifier lists the Camera / Label field. 
• Description of the field, examples and units of measurement, if applicable. Please note that units of measurement required may differ between the CSV, platform and the Camtrap DP standard. 
• 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. 

How the Import All CSV file is processed

It is important that the CSV file is completed correctly for successful import:

• The CSV file must use the exact column names as the example CSV.
• Each row of the CSV file is treated as an individual deployment. 
• Required fields (denoted by an asterisk) must be complete for each deployment or an error will be given.
• Formats for fields are validated when uploading. Be sure to check the input date format to avoid errors. 
• Some information creates an entry on the platform, such as camera, tags and groups. The behaviour of these fields is noted under each section. 

Location information

The following details create a location entry within the project that can then be selected when adding future deployments. Locations can be added manually from the Locations view, when creating a deployment or when using the import all feature.

Camera information

A unique set of camera information creates a camera entry within the project that can then be selected for deployments. If identical information is used, only one new camera entry will be added. Only camera identifier appears on the deployment view on the platform – other details are accessible via the Cameras list. 

Time information

These fields all appear under the Deployment view when adding manually. 

Deployment classification

Deployment tags and Deployment groups can be added under Settings sub-menus. For more information, see Project settings - Other settings. 

Camera setup information

When entering deployments manually, the Platform requests measurements in different units to what is required in the multiple import CSV file detailed below. 

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. 

Additional information