Description: This polyline dataset provides one ROV track line per dive. All data are based on the navigation sensors of the ROV ranging between 1Hz and 5Hz, depending on availability. The track line is based on the interpolation of filtered data with major outliers removed. For ROPOS, the data are as received from the provider and have been run through a Kalman filter. For Millennium, Jason II and Hercules, the data are manually quality controlled for spikes and range tests. The navigation sensors may have occasionally lost contact with the ship due to range or noise issues, which can cause some outliers or gaps in the data. However, data here are considered continuous during a dive. Further information on dives can be obtained from the Dive Listing page at http://dmas.uvic.ca/Cruises.Millennium specific notes: Dives M0001, M0002, and M0003 do not contain line geometry. These are test dives that did not reach bottom. As the navigation system was still being setup at the time, no latitude and longitude values are available for these dives.Jason specific notes: Dive J0833 recovered after the first 20 m due to a thruster ground fault on the ROV. There are no navigation data available for this time period, and therefore, there is no track line geometry for this dive. Dive J0834 data stream begins at ~400 m depth and ~25 min into the dive. As the ROV is simply descending at this time, it is assumed that the ROV is not moving horizontally.
Description: This polyline dataset provides one ROV track line per dive. All data are based on the navigation sensors of the ROV ranging between 1Hz and 5Hz, depending on availability. The track line is based on the interpolation of filtered data with major outliers removed. For ROPOS, the data are as received from the provider and have been run through a Kalman filter. For Millennium, Jason II and Hercules, the data are manually quality controlled for spikes and range tests. The navigation sensors may have occasionally lost contact with the ship due to range or noise issues, which can cause some outliers or gaps in the data. However, data here are considered continuous during a dive. Further information on dives can be obtained from the Dive Listing page at http://dmas.uvic.ca/Cruises.Millennium specific notes: Dives M0001, M0002, and M0003 do not contain line geometry. These are test dives that did not reach bottom. As the navigation system was still being setup at the time, no latitude and longitude values are available for these dives.Jason specific notes: Dive J0833 recovered after the first 20 m due to a thruster ground fault on the ROV. There are no navigation data available for this time period, and therefore, there is no track line geometry for this dive. Dive J0834 data stream begins at ~400 m depth and ~25 min into the dive. As the ROV is simply descending at this time, it is assumed that the ROV is not moving horizontally.
Description: This polyline dataset provides one ROV track line per dive. All data are based on the navigation sensors of the ROV ranging between 1Hz and 5Hz, depending on availability. The track line is based on the interpolation of filtered data with major outliers removed. For ROPOS, the data are as received from the provider and have been run through a Kalman filter. For Millennium, Jason II and Hercules, the data are manually quality controlled for spikes and range tests. The navigation sensors may have occasionally lost contact with the ship due to range or noise issues, which can cause some outliers or gaps in the data. However, data here are considered continuous during a dive. Further information on dives can be obtained from the Dive Listing page at http://dmas.uvic.ca/Cruises.Millennium specific notes: Dives M0001, M0002, and M0003 do not contain line geometry. These are test dives that did not reach bottom. As the navigation system was still being setup at the time, no latitude and longitude values are available for these dives.Jason specific notes: Dive J0833 recovered after the first 20 m due to a thruster ground fault on the ROV. There are no navigation data available for this time period, and therefore, there is no track line geometry for this dive. Dive J0834 data stream begins at ~400 m depth and ~25 min into the dive. As the ROV is simply descending at this time, it is assumed that the ROV is not moving horizontally.
Description: This polyline dataset provides one ROV track line per dive. All data are based on the navigation sensors of the ROV ranging between 1Hz and 5Hz, depending on availability. The track line is based on the interpolation of filtered data with major outliers removed. For ROPOS, the data are as received from the provider and have been run through a Kalman filter. For Millennium, Jason II and Hercules, the data are manually quality controlled for spikes and range tests. The navigation sensors may have occasionally lost contact with the ship due to range or noise issues, which can cause some outliers or gaps in the data. However, data here are considered continuous during a dive. Further information on dives can be obtained from the Dive Listing page at http://dmas.uvic.ca/Cruises.Millennium specific notes: Dives M0001, M0002, and M0003 do not contain line geometry. These are test dives that did not reach bottom. As the navigation system was still being setup at the time, no latitude and longitude values are available for these dives.Jason specific notes: Dive J0833 recovered after the first 20 m due to a thruster ground fault on the ROV. There are no navigation data available for this time period, and therefore, there is no track line geometry for this dive. Dive J0834 data stream begins at ~400 m depth and ~25 min into the dive. As the ROV is simply descending at this time, it is assumed that the ROV is not moving horizontally.
Description: This polyline dataset provides one ROV track line per dive. All data are based on the navigation sensors of the ROV ranging between 1Hz and 5Hz, depending on availability. The track line is based on the interpolation of filtered data with major outliers removed. For ROPOS, the data are as received from the provider and have been run through a Kalman filter. For Millennium, Jason II and Hercules, the data are manually quality controlled for spikes and range tests. The navigation sensors may have occasionally lost contact with the ship due to range or noise issues, which can cause some outliers or gaps in the data. However, data here are considered continuous during a dive. Further information on dives can be obtained from the Dive Listing page at http://dmas.uvic.ca/Cruises.Millennium specific notes: Dives M0001, M0002, and M0003 do not contain line geometry. These are test dives that did not reach bottom. As the navigation system was still being setup at the time, no latitude and longitude values are available for these dives.Jason specific notes: Dive J0833 recovered after the first 20 m due to a thruster ground fault on the ROV. There are no navigation data available for this time period, and therefore, there is no track line geometry for this dive. Dive J0834 data stream begins at ~400 m depth and ~25 min into the dive. As the ROV is simply descending at this time, it is assumed that the ROV is not moving horizontally.
Description: This polyline dataset provides one ROV track line per dive. All data are based on the navigation sensors of the ROV ranging between 1Hz and 5Hz, depending on availability. The track line is based on the interpolation of filtered data with major outliers removed. For ROPOS, the data are as received from the provider and have been run through a Kalman filter. For Millennium, Jason II and Hercules, the data are manually quality controlled for spikes and range tests. The navigation sensors may have occasionally lost contact with the ship due to range or noise issues, which can cause some outliers or gaps in the data. However, data here are considered continuous during a dive. Further information on dives can be obtained from the Dive Listing page at http://dmas.uvic.ca/Cruises.Millennium specific notes: Dives M0001, M0002, and M0003 do not contain line geometry. These are test dives that did not reach bottom. As the navigation system was still being setup at the time, no latitude and longitude values are available for these dives.Jason specific notes: Dive J0833 recovered after the first 20 m due to a thruster ground fault on the ROV. There are no navigation data available for this time period, and therefore, there is no track line geometry for this dive. Dive J0834 data stream begins at ~400 m depth and ~25 min into the dive. As the ROV is simply descending at this time, it is assumed that the ROV is not moving horizontally.
Description: This polyline dataset provides one ROV track line per dive. All data are based on the navigation sensors of the ROV ranging between 1Hz and 5Hz, depending on availability. The track line is based on the interpolation of filtered data with major outliers removed. For ROPOS, the data are as received from the provider and have been run through a Kalman filter. For Millennium, Jason II and Hercules, the data are manually quality controlled for spikes and range tests. The navigation sensors may have occasionally lost contact with the ship due to range or noise issues, which can cause some outliers or gaps in the data. However, data here are considered continuous during a dive. Further information on dives can be obtained from the Dive Listing page at http://dmas.uvic.ca/Cruises.Millennium specific notes: Dives M0001, M0002, and M0003 do not contain line geometry. These are test dives that did not reach bottom. As the navigation system was still being setup at the time, no latitude and longitude values are available for these dives.Jason specific notes: Dive J0833 recovered after the first 20 m due to a thruster ground fault on the ROV. There are no navigation data available for this time period, and therefore, there is no track line geometry for this dive. Dive J0834 data stream begins at ~400 m depth and ~25 min into the dive. As the ROV is simply descending at this time, it is assumed that the ROV is not moving horizontally.
Description: This polyline dataset provides one ROV track line per dive. All data are based on the navigation sensors of the ROV ranging between 1Hz and 5Hz, depending on availability. The track line is based on the interpolation of filtered data with major outliers removed. For ROPOS, the data are as received from the provider and have been run through a Kalman filter. For Millennium, Jason II and Hercules, the data are manually quality controlled for spikes and range tests. The navigation sensors may have occasionally lost contact with the ship due to range or noise issues, which can cause some outliers or gaps in the data. However, data here are considered continuous during a dive. Further information on dives can be obtained from the Dive Listing page at http://dmas.uvic.ca/Cruises.Millennium specific notes: Dives M0001, M0002, and M0003 do not contain line geometry. These are test dives that did not reach bottom. As the navigation system was still being setup at the time, no latitude and longitude values are available for these dives.Jason specific notes: Dive J0833 recovered after the first 20 m due to a thruster ground fault on the ROV. There are no navigation data available for this time period, and therefore, there is no track line geometry for this dive. Dive J0834 data stream begins at ~400 m depth and ~25 min into the dive. As the ROV is simply descending at this time, it is assumed that the ROV is not moving horizontally.
Description: This polyline dataset provides one ROV track line per dive. All data are based on the navigation sensors of the ROV ranging between 1Hz and 5Hz, depending on availability. The track line is based on the interpolation of filtered data with major outliers removed. For ROPOS, the data are as received from the provider and have been run through a Kalman filter. For Millennium, Jason II and Hercules, the data are manually quality controlled for spikes and range tests. The navigation sensors may have occasionally lost contact with the ship due to range or noise issues, which can cause some outliers or gaps in the data. However, data here are considered continuous during a dive. Further information on dives can be obtained from the Dive Listing page at http://dmas.uvic.ca/Cruises.Millennium specific notes: Dives M0001, M0002, and M0003 do not contain line geometry. These are test dives that did not reach bottom. As the navigation system was still being setup at the time, no latitude and longitude values are available for these dives.Jason specific notes: Dive J0833 recovered after the first 20 m due to a thruster ground fault on the ROV. There are no navigation data available for this time period, and therefore, there is no track line geometry for this dive. Dive J0834 data stream begins at ~400 m depth and ~25 min into the dive. As the ROV is simply descending at this time, it is assumed that the ROV is not moving horizontally.
Description: This polyline dataset provides one ROV track line per dive. All data are based on the navigation sensors of the ROV ranging between 1Hz and 5Hz, depending on availability. The track line is based on the interpolation of filtered data with major outliers removed. For ROPOS, the data are as received from the provider and have been run through a Kalman filter. For Millennium, Jason II and Hercules, the data are manually quality controlled for spikes and range tests. The navigation sensors may have occasionally lost contact with the ship due to range or noise issues, which can cause some outliers or gaps in the data. However, data here are considered continuous during a dive. Further information on dives can be obtained from the Dive Listing page at http://dmas.uvic.ca/Cruises.Millennium specific notes: Dives M0001, M0002, and M0003 do not contain line geometry. These are test dives that did not reach bottom. As the navigation system was still being setup at the time, no latitude and longitude values are available for these dives.Jason specific notes: Dive J0833 recovered after the first 20 m due to a thruster ground fault on the ROV. There are no navigation data available for this time period, and therefore, there is no track line geometry for this dive. Dive J0834 data stream begins at ~400 m depth and ~25 min into the dive. As the ROV is simply descending at this time, it is assumed that the ROV is not moving horizontally.
Description: This polyline dataset provides one ROV track line per dive. All data are based on the navigation sensors of the ROV ranging between 1Hz and 5Hz, depending on availability. The track line is based on the interpolation of filtered data with major outliers removed. For ROPOS, the data are as received from the provider and have been run through a Kalman filter. For Millennium, Jason II and Hercules, the data are manually quality controlled for spikes and range tests. The navigation sensors may have occasionally lost contact with the ship due to range or noise issues, which can cause some outliers or gaps in the data. However, data here are considered continuous during a dive. Further information on dives can be obtained from the Dive Listing page at http://dmas.uvic.ca/Cruises.Millennium specific notes: Dives M0001, M0002, and M0003 do not contain line geometry. These are test dives that did not reach bottom. As the navigation system was still being setup at the time, no latitude and longitude values are available for these dives.Jason specific notes: Dive J0833 recovered after the first 20 m due to a thruster ground fault on the ROV. There are no navigation data available for this time period, and therefore, there is no track line geometry for this dive. Dive J0834 data stream begins at ~400 m depth and ~25 min into the dive. As the ROV is simply descending at this time, it is assumed that the ROV is not moving horizontally.
Description: This polyline dataset provides one ROV track line per dive. All data are based on the navigation sensors of the ROV ranging between 1Hz and 5Hz, depending on availability. The track line is based on the interpolation of filtered data with major outliers removed. For ROPOS, the data are as received from the provider and have been run through a Kalman filter. For Millennium, Jason II and Hercules, the data are manually quality controlled for spikes and range tests. The navigation sensors may have occasionally lost contact with the ship due to range or noise issues, which can cause some outliers or gaps in the data. However, data here are considered continuous during a dive. Further information on dives can be obtained from the Dive Listing page at http://dmas.uvic.ca/Cruises.Millennium specific notes: Dives M0001, M0002, and M0003 do not contain line geometry. These are test dives that did not reach bottom. As the navigation system was still being setup at the time, no latitude and longitude values are available for these dives.Jason specific notes: Dive J0833 recovered after the first 20 m due to a thruster ground fault on the ROV. There are no navigation data available for this time period, and therefore, there is no track line geometry for this dive. Dive J0834 data stream begins at ~400 m depth and ~25 min into the dive. As the ROV is simply descending at this time, it is assumed that the ROV is not moving horizontally.
Description: This polyline dataset provides one ROV track line per dive. All data are based on the navigation sensors of the ROV ranging between 1Hz and 5Hz, depending on availability. The track line is based on the interpolation of filtered data with major outliers removed. For ROPOS, the data are as received from the provider and have been run through a Kalman filter. For Millennium, Jason II and Hercules, the data are manually quality controlled for spikes and range tests. The navigation sensors may have occasionally lost contact with the ship due to range or noise issues, which can cause some outliers or gaps in the data. However, data here are considered continuous during a dive. Further information on dives can be obtained from the Dive Listing page at http://dmas.uvic.ca/Cruises.Millennium specific notes: Dives M0001, M0002, and M0003 do not contain line geometry. These are test dives that did not reach bottom. As the navigation system was still being setup at the time, no latitude and longitude values are available for these dives.Jason specific notes: Dive J0833 recovered after the first 20 m due to a thruster ground fault on the ROV. There are no navigation data available for this time period, and therefore, there is no track line geometry for this dive. Dive J0834 data stream begins at ~400 m depth and ~25 min into the dive. As the ROV is simply descending at this time, it is assumed that the ROV is not moving horizontally.
Description: This polyline dataset provides one ROV track line per dive. All data are based on the navigation sensors of the ROV ranging between 1Hz and 5Hz, depending on availability. The track line is based on the interpolation of filtered data with major outliers removed. For ROPOS, the data are as received from the provider and have been run through a Kalman filter. For Millennium, Jason II and Hercules, the data are manually quality controlled for spikes and range tests. The navigation sensors may have occasionally lost contact with the ship due to range or noise issues, which can cause some outliers or gaps in the data. However, data here are considered continuous during a dive. Further information on dives can be obtained from the Dive Listing page at http://dmas.uvic.ca/Cruises.Millennium specific notes: Dives M0001, M0002, and M0003 do not contain line geometry. These are test dives that did not reach bottom. As the navigation system was still being setup at the time, no latitude and longitude values are available for these dives.Jason specific notes: Dive J0833 recovered after the first 20 m due to a thruster ground fault on the ROV. There are no navigation data available for this time period, and therefore, there is no track line geometry for this dive. Dive J0834 data stream begins at ~400 m depth and ~25 min into the dive. As the ROV is simply descending at this time, it is assumed that the ROV is not moving horizontally.
Description: This polyline dataset provides one ROV track line per dive. All data are based on the navigation sensors of the ROV ranging between 1Hz and 5Hz, depending on availability. The track line is based on the interpolation of filtered data with major outliers removed. For ROPOS, the data are as received from the provider and have been run through a Kalman filter. For Millennium, Jason II and Hercules, the data are manually quality controlled for spikes and range tests. The navigation sensors may have occasionally lost contact with the ship due to range or noise issues, which can cause some outliers or gaps in the data. However, data here are considered continuous during a dive. Further information on dives can be obtained from the Dive Listing page at http://dmas.uvic.ca/Cruises.Millennium specific notes: Dives M0001, M0002, and M0003 do not contain line geometry. These are test dives that did not reach bottom. As the navigation system was still being setup at the time, no latitude and longitude values are available for these dives.Jason specific notes: Dive J0833 recovered after the first 20 m due to a thruster ground fault on the ROV. There are no navigation data available for this time period, and therefore, there is no track line geometry for this dive. Dive J0834 data stream begins at ~400 m depth and ~25 min into the dive. As the ROV is simply descending at this time, it is assumed that the ROV is not moving horizontally.
Description: This polyline dataset provides one ROV track line per dive. All data are based on the navigation sensors of the ROV ranging between 1Hz and 5Hz, depending on availability. The track line is based on the interpolation of filtered data with major outliers removed. For ROPOS, the data are as received from the provider and have been run through a Kalman filter. For Millennium, Jason II and Hercules, the data are manually quality controlled for spikes and range tests. The navigation sensors may have occasionally lost contact with the ship due to range or noise issues, which can cause some outliers or gaps in the data. However, data here are considered continuous during a dive. Further information on dives can be obtained from the Dive Listing page at http://dmas.uvic.ca/Cruises.Millennium specific notes: Dives M0001, M0002, and M0003 do not contain line geometry. These are test dives that did not reach bottom. As the navigation system was still being setup at the time, no latitude and longitude values are available for these dives.Jason specific notes: Dive J0833 recovered after the first 20 m due to a thruster ground fault on the ROV. There are no navigation data available for this time period, and therefore, there is no track line geometry for this dive. Dive J0834 data stream begins at ~400 m depth and ~25 min into the dive. As the ROV is simply descending at this time, it is assumed that the ROV is not moving horizontally.
Description: This polyline dataset provides one ROV track line per dive. All data are based on the navigation sensors of the ROV ranging between 1Hz and 5Hz, depending on availability. The track line is based on the interpolation of filtered data with major outliers removed. For ROPOS, the data are as received from the provider and have been run through a Kalman filter. For Millennium, Jason II and Hercules, the data are manually quality controlled for spikes and range tests. The navigation sensors may have occasionally lost contact with the ship due to range or noise issues, which can cause some outliers or gaps in the data. However, data here are considered continuous during a dive. Further information on dives can be obtained from the Dive Listing page at http://dmas.uvic.ca/Cruises.Millennium specific notes: Dives M0001, M0002, and M0003 do not contain line geometry. These are test dives that did not reach bottom. As the navigation system was still being setup at the time, no latitude and longitude values are available for these dives.Jason specific notes: Dive J0833 recovered after the first 20 m due to a thruster ground fault on the ROV. There are no navigation data available for this time period, and therefore, there is no track line geometry for this dive. Dive J0834 data stream begins at ~400 m depth and ~25 min into the dive. As the ROV is simply descending at this time, it is assumed that the ROV is not moving horizontally.
Description: This polyline dataset provides one ROV track line per dive. All data are based on the navigation sensors of the ROV ranging between 1Hz and 5Hz, depending on availability. The track line is based on the interpolation of filtered data with major outliers removed. For ROPOS, the data are as received from the provider and have been run through a Kalman filter. For Millennium, Jason II and Hercules, the data are manually quality controlled for spikes and range tests. The navigation sensors may have occasionally lost contact with the ship due to range or noise issues, which can cause some outliers or gaps in the data. However, data here are considered continuous during a dive. Further information on dives can be obtained from the Dive Listing page at http://dmas.uvic.ca/Cruises.Millennium specific notes: Dives M0001, M0002, and M0003 do not contain line geometry. These are test dives that did not reach bottom. As the navigation system was still being setup at the time, no latitude and longitude values are available for these dives.Jason specific notes: Dive J0833 recovered after the first 20 m due to a thruster ground fault on the ROV. There are no navigation data available for this time period, and therefore, there is no track line geometry for this dive. Dive J0834 data stream begins at ~400 m depth and ~25 min into the dive. As the ROV is simply descending at this time, it is assumed that the ROV is not moving horizontally.
Description: This polyline dataset provides one ROV track line per dive. All data are based on the navigation sensors of the ROV ranging between 1Hz and 5Hz, depending on availability. The track line is based on the interpolation of filtered data with major outliers removed. For ROPOS, the data are as received from the provider and have been run through a Kalman filter. For Millennium, Jason II and Hercules, the data are manually quality controlled for spikes and range tests. The navigation sensors may have occasionally lost contact with the ship due to range or noise issues, which can cause some outliers or gaps in the data. However, data here are considered continuous during a dive. Further information on dives can be obtained from the Dive Listing page at http://dmas.uvic.ca/Cruises.Millennium specific notes: Dives M0001, M0002, and M0003 do not contain line geometry. These are test dives that did not reach bottom. As the navigation system was still being setup at the time, no latitude and longitude values are available for these dives.Jason specific notes: Dive J0833 recovered after the first 20 m due to a thruster ground fault on the ROV. There are no navigation data available for this time period, and therefore, there is no track line geometry for this dive. Dive J0834 data stream begins at ~400 m depth and ~25 min into the dive. As the ROV is simply descending at this time, it is assumed that the ROV is not moving horizontally.
Description: This polyline dataset provides one ROV track line per dive. All data are based on the navigation sensors of the ROV ranging between 1Hz and 5Hz, depending on availability. The track line is based on the interpolation of filtered data with major outliers removed. For ROPOS, the data are as received from the provider and have been run through a Kalman filter. For Millennium, Jason II and Hercules, the data are manually quality controlled for spikes and range tests. The navigation sensors may have occasionally lost contact with the ship due to range or noise issues, which can cause some outliers or gaps in the data. However, data here are considered continuous during a dive. Further information on dives can be obtained from the Dive Listing page at http://dmas.uvic.ca/Cruises.Millennium specific notes: Dives M0001, M0002, and M0003 do not contain line geometry. These are test dives that did not reach bottom. As the navigation system was still being setup at the time, no latitude and longitude values are available for these dives.Jason specific notes: Dive J0833 recovered after the first 20 m due to a thruster ground fault on the ROV. There are no navigation data available for this time period, and therefore, there is no track line geometry for this dive. Dive J0834 data stream begins at ~400 m depth and ~25 min into the dive. As the ROV is simply descending at this time, it is assumed that the ROV is not moving horizontally.