| Method | Data Stream | Content | Type | |
|---|---|---|---|---|
| recovered_host | sio_eng_control_status_recovered | Control Status Data | Report M2M | Engineering |
| telemetered | sio_eng_control_status | Status Data | Report M2M | Engineering |
| Deployment | Cruise | Start Date | Stop Date | Mooring Asset | Node Asset | Sensor Asset | Latitude | Longitude | Deployment Depth | Water Depth |
|---|---|---|---|---|---|---|---|---|---|---|
| 1 Review | MV-1309 | 07/24/2013 | 06/18/2014 | CGMGP-03FLMB-00001 | CGCON-SIOCON-12371 | 50.3317 | -144.401 | 30 | 4145 | |
| 2 Review | MV-1404 | 06/20/2014 | 06/07/2015 | CGMGP-03FLMB-00002 | OL000103 | 50.3313 | -144.398 | 31 | 4145 | |
| 3 Review | TN-323 | 06/08/2015 | 07/03/2016 | CGMGP-03FLMB-00003 | CGCON-SIOCON-12371 | 50.3303 | -144.398 | 47 | 4145 | |
| 4 Review | RB-16-05 | 07/04/2016 | 07/17/2017 | CGMGP-03FLMB-00004 | CGCON-SIOCON-28614 | 50.3293 | -144.398 | 4146 | ||
| 5 Review | SR17-10 | 07/14/2017 | 07/25/2018 | CGMGP-03FLMB-00005 | CGCON-SIOCON-14876 | 50.3777 | -144.515 | 4169 | ||
| 6 Review | SR1811 | 07/24/2018 | 09/27/2019 | CGMGP-03FLMB-00006 | CGCON-SIOCON-13282 | 50.3295 | -144.398 | 4145 | ||
| 7 Review | SKQ201920S | 09/27/2019 | CGMGP-03FLMB-00007 | CGCON-SIOCON-13284 | 50.3755 | -144.514 | 4176 |
| Metadata | Start Date | End Date | Comment |
|---|---|---|---|
|
GP03FLMB |
7/4/16, 11:07 PM | 7/25/18, 5:11 PM |
Deployments 4 and 5 don't have deployment depths defined in asset management. By Lori Garzio, on 1/3/19 |
|
GP03FLMB Deployment: 5 |
Annotation ID 1531: recovered_host data are not available for download (Redmine 13628). Issue should be addressed and annotation needs be updated. By Lori Garzio, on 1/10/19 |
||
|
GP03FLMB Deployment: 5 |
7/14/17, 10:49 PM | 7/25/18, 5:11 PM |
The mooring was deployed 9 - 10 km from the location of the previous 4 deployments of this mooring. If this location is correct, the platform should be annotated to inform the users as to why the deployment location changed. By Lori Garzio, on 1/4/19 |
| Metadata | Start Date | End Date | Comment |
|---|---|---|---|
|
GP03FLMB |
7/24/13, 2:32 AM | 6/17/14, 8:00 PM |
Deployment 1: Mooring was deployed 5-10m shallower than planned. Id: 154 By: lgarzio |
|
GP03FLMB |
6/19/14, 10:00 PM | 6/6/15, 8:00 PM |
Deployment 2: Mooring was deployed 10-15m shallower than planned. Upon recovery of platform, biofouling was apparent on shallow CTDs. Id: 155 By: lgarzio |
|
GP03FLMB |
6/8/15, 5:25 PM | 7/3/16, 2:35 PM |
Deployment 3: Mooring was deployed 10m deeper than planned. Id: 156 By: lgarzio |
|
GP03FLMB |
7/4/16, 7:07 PM | 7/17/17, 11:02 AM |
Deployment 4: Mooring was deployed 10m deeper than planned. Id: 157 By: lgarzio |
|
GP03FLMB |
7/14/17, 6:49 PM | 7/25/18, 1:11 PM |
Deployment 5: Telemetered data are not available for this deployment because gliders were not deployed. Id: 142 By: lgarzio |