Frequently Asked Questions

I’m having trouble downloading large files from LILA; my browser eventually gives up. Help!

If you’re having download issues, we recommend trying AzCopy, a command-line tool for downloading large files that are stored on Azure. Install from here for Windows or here for Linux.

If the URL you’re trying to download is:

…use the following AzCopy command line on Windows to copy it to your current directory:

azcopy /source: /dest:./

…and on Linux, use:

azcopy --source --destination ./

What format do you use for metadata on LILA?

We use different formats depending on the nature each data set, but for camera trap data (and we love camera trap data!), we have tried to convert all data to a common format. More on the details of this format in a second, but if you share data on LILA, we’re willing to do the work to get your data into this format, and post that along with your original metadata. This greatly facilitates letting new researchers work with your data.

We use the “COCO Camera Traps” .json format proposed by Beery et al., which is a refinement of the format used by the COCO data set, adding fields specific to camera trap data sets. Details follow; fields in bold are required (i.e., guaranteed to be present), others are optional. Other fields may be present as well for specific projects.

  "info" : info,
  "images" : [image],
  "categories" : [category],
  "annotations" : [annotation]

  "year" : int,
  "version" : str,
  "description" : str,
  "contributor" : str
  "date_created" : datetime

  "id" : str,
  "width" : int,
  "height" : int,
  "file_name" : str,
  "rights_holder" : str,
  "location": int,
  "datetime": datetime,
  "seq_id": str,
  "seq_num_frames": int,
  "frame_num": int

  "id" : int,
  "name" : str

  "id" : str,
  "image_id" : str,
  "category_id" : int,
  # These are in absolute, floating-point coordinates, with the origin at the upper-left
  "bbox": [x,y,width,height]