Main Page

Anitra is a software platform we develop to give our users a comfortable tool to store, visualize and analyze telemetry data and manage even very complex telemetry projects.

The tool is flexible enough to host datasets generated by transmitters of any brand (manual and automatic data feed) however some of the most advanced features are tailored to complement the unique onboard functionality of our ANITRA BirdieOne transmitters only.

The functionality is primarily designed for Data Owners/Admins but a limited subset of it is also freely available to other users through elaborated sharing scheme. Each user can act in both modes at the same time (i.e. admin for some devices and viewer for data shared with him)

Login / Sign up screen of ANITRA platform available at https://anitra.cz/app/

AREAS OF FUNCTIONALITY (also indicated by menu icons on the left side)

SIGNING IN

Sign up

• Use "Create new account" link on the login page: https://anitra.cz/app to auto-register yourself as a new platform user

• Use a valid email address as your future username

• Upon completion, an email with account confirmation link will be sent to your inbox
  

• Note that you can also create a new account by using "SIGN IN WITH GOOGLE" button.

• This flow will link a newly created account with a chosen google account (you will not need to type user name+pass anymore)
  

Sign in

• Once registered you can log in
  • using your username and password
  • using "Sign in with Google" functionality (you will not need to type user name+pass anymore)
    

• Manage (add/remove) your linked Google Account(s) in your user profile

Password reset

• you can reset your password using "Forget password ?" link on the Sign In if needed
• you need to enter your login address
  
• a reset password link will be sent to your email address
  
• you can change your user password anytime in your user profile page

MAP

• A tool to analyze multiple Individuals in a single map
  

• The functionality displays all the Tracked Individuals available to a user (both owned/administered and shared only)
• By default an overview of the last positions is shown - the color of the point categorizes data by the last data update.
  

• Filtering functionality below the map limits data in the map and in the right Tracked Object selection list by following criteria:
  • "Search" (full text search across Device/TO codes/names/aliases)
  • Species
  • Last "X" Days (limits all the data showing specified last X days interval)
  • Other: Tracking Status, Country of Tagging, Current Age

• Map functionality

1. Map zoom
2. Full screen mode
3. Overview map
4. Map layers - a wide range of available maps
   
5. Show current user position
6. Map options

• Last positions
• Tracks
• Waypoints
• Night Points

• TO details
  • Track point details in the tooltip (note that more track point tooltips can be displayed simultaneously)
  • Additional TO detail in the right TO selection list (including "Share" button for admins)
  • Click through the link to particular Tracked Object profile

• TO Mortality Indicated by black/red symbols in the right TO side selection and in the tooltips
  

DEVICES

Device list

• List of owned or administered devices (= hardware)
• Click through to device details (profile)
• Available device types:
  • "Anitra": used for Anitra native devices, device functionality includes remote control of active devices in the field
  • "Ecotone": virtual devices for Ecotone data, the possibility of the data feed from Ecotone web (available on request)
  • "Ornitela": virtual devices for Ornitela data, possibly of data feed on Ornitela web (available on request)
  • "Upload/Basic": devices created through Import functionality, any other tracking data, the user who uploads become Device Owner
• Semi-automatic Device Status assignment: devices categorized into activity groups (archive, deployed, backup/stock)
• System of warning messages
  • Incorrect/Missing Device-TrackedObject configuration: "Device Code" followed by the black/red exclamation mark ( "!" or "!" )
  • Mortality indication: "Device Status" colored in red and followed by red skull symbol
  • Missing data last X days: "Last Device Position" followed by red question mark "?". Mouse-over symbol tells the last data delay.
• Search and predefined filtering options (Status = Deployed, Mortality, Last data before +7 days, incorrect Tracked Object configuration, Anitra only, Powered off devices)

• Device information (and configuration) is accessible only to owners/admins (users of shared data do not have the rights see this data]

Device Profile

• Device identification, meta info, status, overview and admin management
• Device data visualized on the map and on the timeline
• Definition of tracked objects (create, edit, delete)
  • Removal of testing/manipulation/storage periods
  • Creation/split of device data into real tracked objects (situation when one logger was subsequently used for more than one animal)
• Last known geolocation (DateTime + country etc.)
• System of warnings
  • Incorrect/Missing Device-TrackedObject configuration
  • Mortality indication: red/black warning in "Last device Position" row (red = for deployed and currently tracking devices/black = tracking finished)
  • Missing data last X days: red warning in "Last Device Position" row (warning active just for deployed and currently tracking devices)
• Summary for related TO profiles including Mortality Indication symbols

Device Configuration

• Customer Owners/Admins of ANITRA devices can access device configuration
  • from Device List
    
  • from Device Profile
    

• Configuration for ANITRA loggers covers the following main areas and features
  :
  • Data collection settings
    • GPS/sensor sampling
      • configurable based on both solar or human time)
      • comfortable day/night transition set up
    • Data collection triggered by activity
    • Continuous Activity Estimation
    • Dedicated Mortality detection functionality
    • Adjustment of basic data collection cycles based on location (Geofencing using Points of Interest (POIs))
    • Communication schedules
  • Communication schedules
    • "Fixed times" - four fixed time slots a day
    • "Alternative schedules" - three additional comfortable data delivery planners
      • Human time: cyclic frequency + adjustable cycle sync start
      • Solar time: option of different communication timer during day and night
      • Data: communication can be launched whenever a defined number of records collected by the logger
    • One-off schedule: allows scheduling a single communication at particular date and time (e.g. data to be pushed to the server while performing a field check)
  • Storage mode management: allows to power off devices and configure timeslot for regular device/battery state notification only (i.e. device wakes up only to report battery state at predefined day hour each X days)
• for more details see the complete configuration guide

TRACKED OBJECTS

Tracked Object List

• List of owned TO (tab "my tracked objects")
• List of TO shared with me (tab "shared with me")
• Overview of all tracked objects including first and last data
  • Click through to TO detail/profile
  • System of warnings
  • Mortality indication: "Tracking" followed by red skull symbol
  • Missing data last X days: "Last Data " followed by red questionmark "?". Mouse-over symbol tells the last data delay.
• Search and predefined filtering options (Mortality, Last data before +7 days)

Tracked Object Profile

• Details of tracked object (= tracking of individual bird)
  • Identification (code, name, ringing, tagging etc.)
  • Info related to particular Individual (species, sex, age, origin)
  • Info related to Start of tracking (including photo and file documentation)
  • Info related to End of tracking (~ mortality/device failure)
• System of warnings
  • Mortality indication: red/black warning in "Last known Position" row (red = for deployed and currently tracking devices / black = tracking finished)
  • Missing data last X days: red warning in "Last Device Position" row (warning active just for deployed and currently tracking devices)

• TO data visualized on the map and on the timeline
  

• "Share" button allows sharing TO to other Anitra users
• Possibility to attach photos /documents related to
  • tracking start
  • Mortality
• Same photo can be shared by various Tracked Objects
  

PHOTO GALLERY

• Displays a complete gallery of pictures from all the Tracked Objects (own and shared)
• Filtering by main attributes
  

IMPORT DATA

• Allows importing any other tracking data in the predefined structure. Currently, we support:
  • Data in simple structure device-GPSDateTime-latitude-longitude-note (type "Basic")
  • Ecotone CSV format
  • Ornitela CSV format
• "Upload" automatically analyses imported data and offers the creation of new "Devices"
• Data for already existing devices are appended to these devices (e.g. allows a user to update data in the system by monthly update files..)
• The user who uploaded data becomes Device Owner
  

CUSTOMERS AND INTEGRATION

• visible only for users who act in the system as "Customer Owners" or "Customer Admins"
  

• Customer detail can hold the definition of one or more integration connections (currently Ecotone and Ornitela data feeds supported)
  

• Integration connection toolbox allows
  • Create-edit-remove management of the connection
  • Sending a request for automatic integration run
• Review of the log of the service
  
  

EXPORT DATA into CSV/XLSX/KMZ/GPX

• places to export data:

1. Customer profile: full data for all ANITRA devices owned by Customer (available for CustomerOwner and CustomerAdmins)
2. Device profile: all data for a single device (available for all Customer/Device Owner/Admins)
3. Context menu from Device/TO list: all data for a single Device or TO (available for all Customer/Device Owner/Admins)

• /* mass data takeout not available for people with shared access only */
• Ref 1) Mass export ANITRA data on "Customer profile"

(Both CSV and formatted Excel sheet available):

• Ref 2) Export data for one particular device
  

• Export columns specification:

• CSV file sample preview:

• XLSX file sample preview:

DEVICE-TRACKED OBJECTS-MORTALITY

• Anitra platforms data model is based on the following key concepts:

Device

• Represents physical hardware device to which all the tracking and sensor data are linked
• Allows storing info related to hardware (Brand, logger model, serial number, GSM no. etc.)
• The device in the system can be created:
  • By purchasing Anitra logger (the device will be created and assigned to Anitra Customer)
  • By importing tracking file (csv, kml/kmz, gpx)
  • Automatically by Integration (i.e. automated data feed e.g. from Ecotone or Ornitela panels)

Tracked Object (or Tracking)

• Represents particular animal carrying logger device, a single device can be reused several times (in case of mortality of tracked object)
  • Allows filtering (e.g. display, share) relevant subset of device data
  • Allows attaching metainformation related to:
    • The tracked Individual (species, sex, age, ringing, origin, etc)
    • The tracking of that animal (start of tracking, end of tracking, mortality attributes, photos/documents)
  • Tracked Object in the system can be created
    • Using "split TO" functionality in the device profile
    • Using "create new TO" functionality in the device profile

Device Data

• A basic level of tracking/measurement information
• Data are accessible through devices and their tracked object(s)

Device Status Management and Tracked Object configuration

• For maximum benefit of a full array of Anitra functionality (data filtering, mortality warnings, advanced sharing, etc.) we highly recommend to maintain "Device Statuses" for your devices and Tracked Objects for your study animals up to date.

• Available basic "Device Statuses":
  • Backup / Pool:
    • To be used for spare/pool devices which are not currently in the field and are planned to be (re)used in the future.
    • New devices which appear in the system are labeled "Backup" status automatically
  • Deployed:
    • To be used for devices which are currently deployed "in the field" and potentially sending data
    • There are 4 sub-statuses available which allow the user to configure Anitra behavior further

1. Deployed Active:

• Known to be currently delivering data reliably and new data expected to be updated on a regular basis
• Mortality notification should work reliably

2. Deployed Down:

• Known to be still delivering data (at least for some time), but based on data received the device very likely not already attached to target animal (shed/down logger, the killed animal)
• Hardware to be either recollected or written-off
• "New data" notifications could help investigate the case until the logger transmits data
• After collecting all possible information and closing the case the device should be turned to "Archive" status

3. Deployed Missing:

• Data delivery suddenly interrupted, last positions do not show animal/logger issue
• "New data" notifications possibly used to notify on the restoration of data transfer

4. Deployed Problem:

• Depending on the issue type the data delivery fails or some sensor data might be unreliable
• Allows suppressing mortality notification as false or confusing warnings may be raised

• Archive / Discarded:

• meant for "out of use" devices (inactivated, suspended, finished) not expected to deliver any new data
• Turning device into this state allows suppressing warning scheme
• Allows to store and filter out archive data
• Note that devices created through import functionality are by default switched to this state

Tracked Object EndDate

• Device Statuses are meant to help to control active Loggers >> Tracked Objects (Trackings). In order to receive a meaningful warning, it is highly recommended not only to turn inactive devices to Archive but also to end related active Tracked Objects (Trackings) whenever the tracking in the field is over (i.e. you do not expect to receive any new data).
  • Ending Tracked Object / Tracking is done by filling in date into field "End of tracking" in the Tracked Object profile
  • "End Of Tracking" field leaves space for individual interpretation. For instance in case of mortality you can include the period when the tracked individual was alive only or you might as well close the tracking date later when the device was physically found and removed.
  • Note that you can additionally enter more detail related to mortality event ("Estimated date of death", "Mortality Reason", "Mortality Note", "Mortality Photos/Documents/Reports")

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 you archive data (see the end date for the first two tracked objects in the 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 Anitra platform:
  • Device list (only Red warning for Active trackings)

• Device Profile

• TO List (both Red warnings for Active trackings and Black Info for Archive trackings)

• TO 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 Tracked Objects end dates in order to achieve desired Anitra behavior