Detection Extracts

For Trackers: All detections of all tags released by the project no matter where they occurred. False detections no longer being marked/separated. There may be detections of some of your tag ids which have not been matched. There can be many reasons for this. To check if any of your tags may have been missed please see the mystery tag list for your region or series. For Deployment Operators: Sets of sentinel tag detections, sets of detections mapped to animals without the animal details, sets of 'UNQUALIFIED' detections.
Unqualifed Detections 2018

These are detections for which we do not know the owner. There may be several reasons for this. One: It is a test or sentinel tag and we have not been informed. Two: It is an ambiguous tag which means we have more than one set of tag metadata which the detection could belong to. Three: We have not received any release metadata for the tag. Four: It is an old style sensor tag and we have not been able to determine the associated pinger id, or even if there should be one, because we do not have the vendor tag specifications.

Unqualifed Detections 2017

These are detections for which we do not know the owner. There may be several reasons for this. One: It is a test or sentinel tag and we have not been informed. Two: It is an ambiguous tag which means we have more than one set of tag metadata which the detection could belong to. Three: We have not received any release metadata for the tag. Four: It is an old style sensor tag and we have not been able to determine the associated pinger id, or even if there should be one, because we do not have the vendor tag specifications.

Unqualifed Detections 2016

These are detections for which we do not know the owner. There may be several reasons for this. One: It is a test or sentinel tag and we have not been informed. Two: It is an ambiguous tag which means we have more than one set of tag metadata which the detection could belong to. Three: We have not received any release metadata for the tag. Four: It is an old style sensor tag and we have not been able to determine the associated pinger id, or even if there should be one, because we do not have the vendor tag specifications.

Unqualifed Detections 2015

These are detections for which we do not know the owner. There may be several reasons for this. One: It is a test or sentinel tag and we have not been informed. Two: It is an ambiguous tag which means we have more than one set of tag metadata which the detection could belong to. Three: We have not received any release metadata for the tag. Four: It is an old style sensor tag and we have not been able to determine the associated pinger id, or even if there should be one, because we do not have the vendor tag specifications.

Unqualifed Detections 2014

These are detections for which we do not know the owner. There may be several reasons for this. One: It is a test or sentinel tag and we have not been informed. Two: It is an ambiguous tag which means we have more than one set of tag metadata which the detection could belong to. Three: We have not received any release metadata for the tag. Four: It is an old style sensor tag and we have not been able to determine the associated pinger id, or even if there should be one, because we do not have the vendor tag specifications.

Unqualifed Detections 2013

These are detections for which we do not know the owner. There may be several reasons for this. One: It is a test or sentinel tag and we have not been informed. Two: It is an ambiguous tag which means we have more than one set of tag metadata which the detection could belong to. Three: We have not received any release metadata for the tag. Four: It is an old style sensor tag and we have not been able to determine the associated pinger id, or even if there should be one, because we do not have the vendor tag specifications.

Unqualifed Detections 2012

These are detections for which we do not know the owner. There may be several reasons for this. One: It is a test or sentinel tag and we have not been informed. Two: It is an ambiguous tag which means we have more than one set of tag metadata which the detection could belong to. Three: We have not received any release metadata for the tag. Four: It is an old style sensor tag and we have not been able to determine the associated pinger id, or even if there should be one, because we do not have the vendor tag specifications.

Unqualifed Detections 2011

These are detections for which we do not know the owner. There may be several reasons for this. One: It is a test or sentinel tag and we have not been informed. Two: It is an ambiguous tag which means we have more than one set of tag metadata which the detection could belong to. Three: We have not received any release metadata for the tag. Four: It is an old style sensor tag and we have not been able to determine the associated pinger id, or even if there should be one, because we do not have the vendor tag specifications.

Unqualifed Detections 2010

These are detections for which we do not know the owner. There may be several reasons for this. One: It is a test or sentinel tag and we have not been informed. Two: It is an ambiguous tag which means we have more than one set of tag metadata which the detection could belong to. Three: We have not received any release metadata for the tag. Four: It is an old style sensor tag and we have not been able to determine the associated pinger id, or even if there should be one, because we do not have the vendor tag specifications.

Unqualifed Detections 2009

These are detections for which we do not know the owner. There may be several reasons for this. One: It is a test or sentinel tag and we have not been informed. Two: It is an ambiguous tag which means we have more than one set of tag metadata which the detection could belong to. Three: We have not received any release metadata for the tag. Four: It is an old style sensor tag and we have not been able to determine the associated pinger id, or even if there should be one, because we do not have the vendor tag specifications.

Sentinel tag detections 2013

Hebert, D., Barthelotte, J., O'Dor, R., Stokesbury, M., Branton, R. 2009. Ocean Tracking Network Halifax Canada Line Metadata and Data Set.

Sentinel tag detections 2012

Hebert, D., Barthelotte, J., O'Dor, R., Stokesbury, M., Branton, R. 2009. Ocean Tracking Network Halifax Canada Line Metadata and Data Set.

Sentinel tag detections 2011

Hebert, D., Barthelotte, J., O'Dor, R., Stokesbury, M., Branton, R. 2009. Ocean Tracking Network Halifax Canada Line Metadata and Data Set.

Sentinel tag detections 2010

Hebert, D., Barthelotte, J., O'Dor, R., Stokesbury, M., Branton, R. 2009. Ocean Tracking Network Halifax Canada Line Metadata and Data Set.

Sentinel tag detections 2009

Hebert, D., Barthelotte, J., O'Dor, R., Stokesbury, M., Branton, R. 2009. Ocean Tracking Network Halifax Canada Line Metadata and Data Set.

Detections Mapped to other Trackers 2018

These detections have been mapped to releases by other trackers. To get the list of associated trackers see your discovery metadata page by clicking on your collectioncode at: https://members.oceantrack.org/data/discovery/bycollection.htm

Detections Mapped to other Trackers 2017

These detections have been mapped to releases by other trackers. To get the list of associated trackers see your discovery metadata page by clicking on your collectioncode at: https://members.oceantrack.org/data/discovery/bycollection.htm

Detections Mapped to other Trackers 2016

These detections have been mapped to releases by other trackers. To get the list of associated trackers see your discovery metadata page by clicking on your collectioncode at: https://members.oceantrack.org/data/discovery/bycollection.htm

Detections Mapped to other Trackers 2015

These detections have been mapped to releases by other trackers. To get the list of associated trackers see your discovery metadata page by clicking on your collectioncode at: https://members.oceantrack.org/data/discovery/bycollection.htm