From AnitraWiki
Jump to: navigation, search

Device Status Management

To have a full array of Anitra functionality available (data filtering, mortality warnings, advanced sharing, etc.) maintain the Device statuses in line with reality.

Backup / Pool: 
To be used for spare/pool devices which are not currently deployed and are ready to be (re)used in the future.
New purchased devices receive "Backup/Pool" status automatically
Use for devices that are currently deployed on animals and still collecting/sending data (at least potentially)
Tags are automaticaly moved from Backup/Pool to Deployed status when user enters information on the tag deployment (Tracking) and about Tracked Animal. Check the detailed guide here.
Deployed status is additionaly automatically extended by the system based on the information on the last data delivered
Deployed Active: known to have delivered fresh data within last 7 days
Deployed Missing: last data older than 7 days
Archive / Discarded:
Meant for achieving data of "out of use" devices not expected to deliver any new data (inactivated, suspended, finished)
Turning the device into this state suppresses the warning and notification scheme
Note that devices created using import functionality are by default switched to "Archieve" state

Tracking range management

Define Tracking/Deployment and Animal/Individual meta info to organize your data and to benefit from all the Anitra tracking/animal-related features (such as seeing animals in maps, activity clusters, mortality detection, etc).
You can create and edit Trackings/Deployments on the Data tab of the Device profile
Use right-click context menu items for these actions:
Create new tracking: launches empty tracking (start) creation wizard, a general option available anywhere in the Data tab
Create new tracking here: launches wizard prefilled with selected position DateTime and GPS, available over any point within the tracking range (in the table or in the timeline)
Open tracking: opens the tracking/animal profile in a new browser tab, available over any existing tracking (in the table or over the band the timeline)
Edit tracking start: opens tracking start edit form, available over any existing tracking (in the table or over the band the timeline)
Add tracking end: launches empty tracking end wizard, available over any existing tracking (in the table or in the timeline)
Add tracking end here: launches wizard prefilled with selected position DateTime and GPS, GPS proposed from the last point before the end time, available over any point belonging to the tracking (in the table or in the timeline)
Edit tracking end: opens tracking end edit form, available over any existing tracking with end defined (in the table or over the band the timeline)
Using „here“ actions over selected points offers the comfort of instant visual croschecking of input values (in the table, map, and timeline).
Select the right start point for creating you new tracking with Create new tracking here action:
01 create new tracking here - kontext.jpg
The „start here“ action additionaly prefills the date-time and GPS position from the selected point into the tracking start form:
02 create new tracking here - prefilled.jpg
You can modify the proposed position of the tracking start to the correct place of release.
It can be done either by moving the cyan icon in the map or by typing the latitude/longitude in the form:
03 create new tracking here - prefilled, modified place.jpg
You can also adjust the start date/time manually by adjusting it in the form. Note that after changing the date a new icon appears in the form.
Click it to update the position of the start from the new first position of the tracking automaticaly:
04 create new tracking here - prefilled, modified datetime.jpg
Saving the tracking start by the check icon will open the new tracking/animal profile in a new browser tab. You should fill in all details about the deployment and about the tagged animal there (see more on this).
The device profile browser tab also gets refreshed and updated to reflect the new tracking creation.
The tracking range is displayed as a colored band in the timeline and the same colored column in the table.
From now on you can see additional actions in the right mouse click context menu over the area of tracking range (over the table rows and over the band in the timeline):
05 Existing tracking modification.jpg
In case you wish to end the tracking select the right endpoint and use Add tracking end here action.
Similarly as for the „start here“, the „end here“ action also prefills the date/time and GPS from the selected point
06 add tracking end here.jpg
You can remove the end of tracking by editing it and using a remove button there:
07 edit tracking end (remove).jpg
Note you can create new tracking and/or add the tracking end using general actions without "here". Make sure you enter the correct dates to avoid overlapping with existing trackings.
A special workflow is launched when creating a new tracking before the existing one. In that case, the end date must be also specified at the time of creating the new tracking definition:
08 tracking created before tracking.jpg
Also note the trackings and animals can sometimes be created automatically (e.g. by importing reference data from the Movebank).
In Movebank data only the date/time information for the tracking/deployment range is mandatory and indeed typically GPS missing in reference files.
To display on the map the GPS position of the start/end is needed. Therefore Anitra import flow intends to auto-propose it from the available telemetry data using the date/time provided - i.e. from the first/last position in the range. (Note this only works if data are available at the time of creating the tracking item)
Tracking starts/ends with auto-proposed GPS are labeled by a warning symbol. Users should review and adjust the definition on the Anitra map. The warning sign disappears by saving the confirmed location.
10 auto-proposed position.jpg
if the GPS of the start/end cannot be fetched for some reason the tracking visibility might be restricted till not manually entered by a user in the map.
If you need to delete the Tracking item itself navigate to the tracking profile and use the "Delete" button there:
09 delete tracking.jpg
Semantically the "End Of Tracking" usually reflects the date/time when the tag was physically removed from the animal (dead or alive)
In case of mortality use dedicated Mortality fields including "Estimated date of death" in parallel independent of Tracking End (see more).
As in normal situations End the tracking in mortality only after the device was physically found and removed.
The Tracking should also be ended when the device could not be physically located but the tag will not deliver any more data (e.g. by terminating the SIM card).

Mortality warnings


  • Notifies on possible mortality in the last position of finished (archive) trackings
  • You can set the end date of tracking so that the mortality sign is displayed in your archive data (see the end date for the first two tracked objects in example no 1)


  • Warns on possible mortality detected in the last position of active trackings
  • In order to have relevant red warnings shown correct device/TO configuration needs to be kept by project admin
Note. the detection of mortality is currently based on
  • Anitra: dedicated sensor/accelerometer mortality detection logic
  • Ornitela: identical body position between subsequent measurements
  • Ecotone Activity column with a simple rule (Activity < 10) triggering the alert. More complex logic is being developed for Anitra native devices
  • You can find these last data mortality warnings on various screens of the Anitra platform:
    • Device list (only Red warning for Active trackings)
  • Device Profile
  • Tracking List (both Red warnings for Active trackings and Black Info for Archive trackings)
  • Tracking profile
  • Map (both Red warnings for Active trackings and Black Info for Archive trackings)


  • Device Owner/Admins can freely switch devices from one state to another and modify Tracking end dates in order to achieve desired Anitra behavior