Annotation of acceleration data
In case your project includes acceleration data (XYZ accelerometer data), Firetail provides a fast way to annotate burst level data for
- Movebank individuals
- Movebank tags
- Movebank deployments
layers as highest level of organisation.
layer can hold arbitrary many
category resides on one specific layer.
burst (see also Burst vs. continuous recording) can be assigned to
one or more categories.
Add new categories
To add a new category press
Add Category above the acceleration window
Assign a name to the category
The category will show up above the acceleration window
Save and Load Annotation Categories
Annotation is usually a process done as a team to ensure consistency to have the possibility to check for inter-annotator agreements. Sharing a common set of annotation categories is crucial.
With Firetail you can save the current set of categories and layers.
File > Annotations > Export Annotation Categories.
The resulting file can be shared and reimported. To add the categories to your current project, use
File > Annotations > Import Annotation Categories.
Working with external annotations
Starting from version 9 Firetail introduces a simple yet powerful exchange format for annotations.
You can import multiple external annotation files. This allows you to
- show gold standards alongside with predicted annotations
- interpret reference data in the context of FireSOM predictions
- compare multiple predictions
- merge annotations from distinct sources
and much more.
Caveat: Export/Import must not be confused with
File > Save AnnotationsSaving causes the data to be saved along with your project. Export is designed to share annotations with peers or process external annotation resources.
To export annotations from Firetail use
File > Annotations > Export Annotations.
Select a filename of your choice and confirm your selection.
To import annotations use
File > Annotations > Import External Annotations.
Choose a csv annotation file and confirm your selection.
You will be asked about the procedure.
- Replace: existing annotation layers will be replaced by the annotation file
- Merge: layers and categories are merged with the existing annotation
The Firetail annotation exchange format
The current exchange format is contains comma-separated values as follows. The following sample shows the required header columns (UTF8 csv) and few sample categories across several layers
category, layer, start-timestamp, end-timestamp
"in", "default layer", 2012-06-01 08:20:00.000, 2012-06-03 21:21:10.000
"out", "default layer", 2012-06-15 16:22:03.000, 2012-06-15 23:27:30.000
"foo", "default layer", 2012-06-16 00:50:01.000, 2012-06-18 22:02:02.000
"bar", "flying", 2012-06-16 23:51:01.000, 2012-06-18 23:55:02.000
"bar", "flying", 2012-06-16 23:56:01.000, 2012-06-18 23:57:02.000
Each line one annotation category mapped onto a layer.
string types, whereas the timestamp should be an ISO timestamp with 3 ms digits.
If external resources do not feature a layer concept, the “default layer” can be assigned.
Firetail will gradually be extended with specific converters/import filters for external annotation formats. If you feel that a format is sufficiently important for many users please don’t hesitate to contact us!
Currently, the tag/individual/deployment information is not saved along with the data. The reason is that external tools are not aware of movebank conventions while grouping (layering) and category assignments with a distinct start and end are generic concepts. Exported data must not be mistaken for a complete snapshot including all required meta-information.
Make sure to include sufficient information in your filename structure to properly map your data to the respective tags or individuals.
Assign a category to a region
Once you have defined categories, you can use the selection mechanism described here to define regions that you’d like to annotate with one of your categories.
- Select a region within the bursts or the map
- Press on the category you want to assign this region to
The newly assigned category will be shown in a row/layer above the acceleration data.
Each category can be assigned to a single layer (visual group shown as a single row of data).
Note that overlapping categories shown in a single layer are possible, yet may not be visually sensible.
Right-clicking a category will yield a popup-menu for:
- category modification
- annotation deletion
Saving Annotations and Removing a category
You can remove existing categories via right-clicking on the respective category and select
delete category. You are prompted that all annotations contained will be lost. There is currently
no undo for this, so make sure to use
File > Save Annotations
to save the current state.
Expert hint: the annotation resides in the respective
annotation2.csv(to ensure compatiblity with AccelerationViewer, this will likely change in future versions). Make sure to include this folder in your regular backup procedure