All timestamps are displayed in Coordinated Universal Time (UTC).

The option to be alerted when a new transmission has been received for a project or tag for the configured duration. Zero indicates no alert.

The option to be alerted when no new transmissions have been received for a project or tag for the configured duration. Zero indicates no alert.

There are three user permission roles.

Project Administrator - can administer the project and associated tags and share them with others.

Standard - can view data for projects and tags that have been shared with them.

Viewer - can view a limited time range of data from projects and tags that have been shared with them. Not yet implemented.

At the Tag level a user cannot be made Project administrator, they can only have data shared with them to view.

Sometimes the data sent to the Argos satellites can get corrupted. Our processes check for corruption, and try to correct it. This results in three types of data.

Good: the data has not been corrupted.

Corrected: an attempt has been made to correct the data, but there may still be an error in any part of the data, e.g. date, location or sensor data. These can be shown on the map by selecting the “Error Locations” checkbox within the filters.

Failed: the data is too corrupted to attempt a correction.

Note that fixes are transmitted several times, so although you may see a failed or corrected location, that does not mean that you do not have a good copy of the fix. Sometimes you may see a corrected location next to a good location, because there is still an error within the corrected fix.

Queue Argos Request - the next time the Argos CLS is queried for transmissions, this tag will be included.

Reprocess Sensor Data - the next time Sensor Data is decoded, delete existing decoded sensor data records and reprocess for this tag.

Refresh reporting tables - the next time the reporting tables are updated, this tag will be included.

Full Refresh Reporting tables - the next time reporting tables are updated, delete existing records and update for this tag.

The various location and sensor database tables are flattened into a pair of database tables to improve website data retrieval times and server load.

The background workers that collect transmissions, decode sensor data and update reporting tables are staggered on a four hourly cycle, so there is a four hour lag between tag transmissions being saved and becoming visible in the data or map views.