Tracking API Argos FAQ

#Argos FAQ

Argos data formats

Argos data is originally plain text files, known as DS and DIAG files (formerly .DAT and .DIA).

The Argos data is stored consists of JSON http://json.org/ https://chrome.google.com/webstore/detail/json-formatter/bcjindcccaagfpapjjmafapmmgkkhgoa

Q. Is all the original data preserved in the Tracking API? A. Yes. All data is converted to JSON, see argos-ruby for details on the data format, or this example

Q. Can I access the data giving information on the error ellipse for each position (radius, semi-minor and semi-major axes)? I use them in my location filtering. I did not manage to retrieve them. lc location class http://www.argos-system.org/web/en/78-faq.php http://www.argos-system.com/html/system/kalman_faq_en.html http://www.telonics.com/technotes/argosintro.php Accuracy of ARGOS Locations of Pinnipeds at-Sea Estimated Using Fastloc GPS http://www.plosone.org/article/info:doi/10.1371/journal.pone.0008677 https://www.movebank.org/node/38

Q. Do you have all the technical information on the collars used Q. the first sensor data column should provide with information from a temperature logger.

"deploymenT" =>

http://api.npolar.no/tracking/deployment/a670226c-8a78-42a2-9309-9ab987780ea6

Q. Why do sensor data sometimes contain more values?

A. In the original Argos data, the number of sensor data varies, more than it should, ie. sometimes a large number og sensor data is present, while only (e.g.) 3 is expected. Notice that the "warn" field contains "sensors-count-mismatch" if the reported (in the Argos message) number of "sensors" is different from the actual sensor count (the number of itmes in "sensor_data")

Q. Is it possible to remove data with wrong sensor count?

A. Yes, supplying a query like http://api.npolar.no/tracking/?filter-sensors=3&filter--warn=sensors-count-mismatch&q=&format=