Uploader
The uploader signs local files and uploads them to the ingestion service. This is useful to upload existing data sets, or to migrate data between Edge Impulse instances. The uploader currently handles these type of files:
  1. 1.
    .cbor - Files in the Edge Impulse Data Acquisition format. The uploader will not resign these files, only upload them.
  2. 2.
    .json - Files in the Edge Impulse Data Acquisition format. The uploader will not resign these files, only upload them.
  3. 3.
    .csv - Files in the Edge Impulse Comma Separated Values (CSV) format.
  4. 4.
    .wav - Lossless audio files. It's recommended to use the same frequency for all files in your data set, as signal processing output might be dependent on the frequency.
  5. 5.
    .jpg - Image files. It's recommended to use the same ratio for all files in your data set.

Upload data from the studio

You can now also upload data directly from the studio. Go to the Data acquisition page, and click the 'upload' icon. You can select files, the category and the label directly from here.
Uploading data from the studio

Uploading via the CLI

You can upload files via the Edge Impulse CLI via:
$ edge-impulse-uploader path/to/a/file.wav
You can upload multiple files in one go via:
$ edge-impulse-uploader path/to/many/*.wav
The first time you'll be prompted for a server, and your login credentials (see Edge Impulse Daemon for more information).

Category

Files are automatically uploaded to the training category, but you can override the category with the --category option. E.g.:
$ edge-impulse-uploader --category testing path/to/a/file.wav
Or set the category to split to automatically split data between training and testing sets (recommended for a balanced dataset). This is based on the hash of the file, so this is a deterministic process.

Labeling

A label is automatically inferred from the file name, see the Ingestion service documentation. You can override this with the --label option. E.g.:
$ edge-impulse-uploader --label noise path/to/a/file.wav

Clearing configuration

To clear the configuration, run:
$ edge-impulse-uploader --clean
This resets the uploader configuration and will prompt you to log in again.

API Key

You can use an API key to authenticate with:
$ edge-impulse-uploader --api-key ei_...
Note that this resets the uploader configuration and automatically configures the uploader's account and project.

Bounding boxes

If you want to upload data for object detection, the uploader can label the data for you as it uploads it. In order to do this, all you need is to create a bounding_boxes.labels file in the same folder as your image files. The contents of this file are formatted as JSON with the following structure:
{
"version": 1,
"type": "bounding-box-labels",
"boundingBoxes": {
"mypicture.jpg": [{
"label": "jan",
"x": 119,
"y": 64,
"width": 206,
"height": 291
}, {
"label": "sami",
"x": 377,
"y": 270,
"width": 158,
"height": 165
}]
}
}
You can have multiple keys under the boundingBoxes object, one for each file name. If you have data in multiple folders, you can create a bounding_boxes.labels in each folder.
You don't need to upload bounding_boxes.labels
When uploading one or more images, we check whether a labels file is present in the same folder, and automatically attach the bounding boxes to the image.
So you can just do:
edge-impulse-uploader yourimage.jpg
or
edge-impulse-uploader *
Also note that this feature is currently only supported by the uploader, you cannot yet upload object detection data via the studio.
Let the Studio do the work for you!
Unsure about the structure of the bounding boxes file? Label some data in the studio, then export this data by selecting Dashboard > Export. The bounding_boxes.labels file will be included in the exported archive.

Upload data from OpenMV datasets

The uploader data in the OpenMV dataset format. Pass in the option --format-openmv and pass the folder of your dataset in to automatically upload data. Data is automatically split between testing and training sets. E.g.:
$ edge-impulse-uploader --format-openmv path/to/your-openmv-dataset

Other options

  • --silent - omits information on startup. Still prints progress information.
  • --dev - lists development servers, use in conjunction with --clean.
  • --hmac-key <key> - set the HMAC key, only used for files that need to be signed such as wav files.
  • --concurrency <count> - number of files to uploaded in parallel (default: 20).
  • --progress-start-ix <index> - when set, the progress index will start at this number. Useful to split up large uploads in multiple commands while the user still sees this as one command.
  • --progress-end-ix <index> - when set, the progress index will end at this number. Useful to split up large uploads in multiple commands while the user still sees this as one command.
  • --progress-interval <interval> - when set, the uploader will not print an update for every line, but every interval period (in ms.).
  • --allow-duplicates - to avoid pollution of your dataset with duplicates, the hash of a file is checked before uploading against known files in your dataset. Enable this flag to skip this check.

Uploading large datasets

When using command line wildcards to upload large datasets you may encounter an error similar to this one:
edge-impulse-uploader *.wav
zsh: argument list too long: edge-impulse-uploader
This happens if the number of .wav files exceeds the total number of arguments allowed for a single command on your shell. You can easily work around this shell limitation by using the find command to call the uploader for manageable batches of files:
find . -name "*.wav" -print0 | xargs -0 edge-impulse-uploader
You can include any necessary flags by appending them to the xargs portion, for example if you wish to specify a category:
find training -name "*.wav" -print0 | xargs -0 edge-impulse-uploader --category training
Export as PDF
Copy link
Outline
Upload data from the studio
Uploading via the CLI
Category
Labeling
Clearing configuration
API Key
Bounding boxes
Upload data from OpenMV datasets
Other options
Uploading large datasets