Skip to content

Main concepts

Anitra data model is based on the following key concepts:

Device

  • Device (or Tag) entity represents the physical telemetry hardware that collects particular telemetry data. Any tracking and sensor data are linked to one of the devices.
  • Devices are created automatically in the system while importing a new telemetry dataset (via Import or Integration flow) or created by us in the case of Anitra devices (created as part of the device purchase process).
  • Device Status attribute reflects the current usage of the devices (statuses are pool-new (1), pool-used (2), deployed-active (3), deployed-delayed (4), and deployed-missing (5)).
  • Besides, a "Discard" flag is available to mark the tags that are considered out of service.
  • More on device statuses and discard flow here.
  • Attributes related to the hardware (brand, model, serial no., GSM no., etc.) or summary metrics can be seen and managed in the Device profile.
  1. Devices never deployed previously.
  2. Devices returned to the device pool after deployment.
  3. Deployed on animals, known to have delivered fresh data within the last 3 days.
  4. Deployed on animals, known to have delivered fresh data within the last 4-7 days.
  5. Last data older than 7 days.

Organisation, Customer, or Ownership

  • Device "Ownership" defines which organization/customer holds ownership of the data.
  • Purchased Anitra devices are transferred under the Customer account during the purchasing process.
  • Non-Anitra devices are linked to particular Customers by running integration connectors or Importing data manually.
  • Customer account also holds the credit balance (data fee prepay)

Animal

  • Animal (or Individual) entity represents a particular animal/individual
  • The main attributes for an Animal are its Species, Sex, and Dates when Born and Died (~ which also defines the current age e.g.).
  • Additional complex meta-information can be linked-to Animal such as origin info, relationships to other animals, ringing, tagging or trapping details, and mortality attributes
  • Photos (or documents) can be attached either directly to the Animal entity or indirectly to some related entities or Events such as Tagging or Mortality.

Tracking

  • Tracking (or Deployment) entity defines the relationship between Devices and Animals primarily in terms of time. Check out a detailed guide on creation and modification of the tracking range.
  • The date(time) interval defines when the device was physically attached to the Animal
  • Note when looking at the timeline of a particular Animal, multiple telemetry devices might have been used to track it subsequently (e.g. first tag failed and removed or was shed by the animal). Similarly, when analyzing Device usage history a single device might have been possibly reused several times for Tracking various animals (e.g. one animal died, the tag was recovered and reused elsewhere).
  • Besides the time aspect, some additional details such as place of tagging, place of release, tagging persons, various notes, photos, etc can be attached to Tracking Start/End.
  • Tracking inherits permissions from its parent Device entity so users with device owner/admin access can create and modify the deployments as well.

Group, Project, Study

Person, User, Role

  • Data owners can make their data available to other users or even make their data public in a simplified and secured way using an elaborated sharing scheme. Each user can act in both modes (i.e. admin for owned or administered devices and viewer for data shared with him by others). Most of the platform functionality is free of charge and available to anyone. Only large data volumes might be possibly restricted or charged.

Place, Point of Interest (POI)

Event, Observation

Device Data, Records, Positions, Outliers

  • Measurement data collected by telemetry devices.
  • A combination of the device ID and UTC timestamp (date time in milliseconds) uniquely identifies each record.
  • Records are linked to devices but can also be fetched for child Trackings, or Animals.
  • Record: a dataset related to particular UTC timestamp carrying measurements performed by particular device sensors (such as GNSS module, IMU, barometer)
  • Position: a record with a successful GPS fix (obtained Latitude and Longitude). Positions can be shown on maps.
  • Outlier: a record without GPS fix (no valid Latitude/Longitude) due to unsuccessful, skipped, or wrong GPS fixing. Note Outliers are not shown in maps but can still be displayed in table, timeline, and graph view.
  • You can visualize, analyse, or download data using the Anitra platform functionality.
  • Note the list of columns/metrics covered by the Anitra data model can be understood from various places:

Data Cluster, Annotation

  • An object created (automatically or manually) on top of the telemetry data that annotates a series of Records into semantic groups (such as Mortality or Night clusters).
  • These clusters can be used to simplify the visibility of tracks and positions in the maps by masking details showing statistically aggregated information.