Method | Data Stream | Content | Type | |
---|---|---|---|---|
recovered_host | glider_eng_metadata_recovered | Metadata | Report M2M | Engineering |
recovered_host | glider_eng_recovered | Engineering Data | Report M2M | Engineering |
recovered_host | glider_eng_sci_recovered | Status Data | Report M2M | Engineering |
recovered_host | glider_gps_position | GPS Position Data | Report M2M | Engineering |
telemetered | glider_eng_metadata | Metadata | Report M2M | Engineering |
telemetered | glider_eng_sci_telemetered | Status Data | Report M2M | Engineering |
telemetered | glider_eng_telemetered | Engineering Data | Report M2M | Engineering |
telemetered | glider_gps_position | GPS Position Data | Report M2M | Engineering |
Deployment | Cruise | Start Date | Stop Date | Mooring Asset | Node Asset | Sensor Asset | Latitude | Longitude | Deployment Depth | Water Depth |
---|---|---|---|---|---|---|---|---|---|---|
1 Review | KN-222 | 10/06/2014 | 12/13/2014 | CGVCP-05MOAS-00000 | CGVEH-GLDRCP-00335 | CGCON-GLDRCP-00335 | 39.8296 | -70.5834 | 200 | 200 |
2 Review | AT-31 | 10/14/2015 | 11/17/2015 | CGVCP-05MOAS-00000 | CGVEH-GLDRCP-00335 | CGCON-GLDRCP-00335 | 40.0708 | -70.4156 | 200 | 200 |
3 Review | AR1-07 | 04/04/2016 | 04/18/2016 | CGVCP-05MOAS-00000 | CGVEH-GLDRCP-00335 | CGCON-GLDRCP-00335 | 39.9685 | -70.5381 | 200 | 200 |
4 Review | AR-04 | 05/27/2016 | 06/28/2016 | CGVCP-05MOAS-00000 | CGVEH-GLDRCP-00335 | CGCON-GLDRCP-00335 | 39.8318 | -70.7249 | 200 | 200 |
5 Review | WJ20170115 | 01/16/2017 | 03/06/2017 | CGVCP-05MOAS-00000 | CGVEH-GLDRCP-00335 | CGCON-GLDRCP-00335 | 40.0423 | -70.3785 | 200 | 200 |
Metadata | Start Date | End Date | Comment |
---|---|---|---|
CP05MOAS |
Bad altimeter pings are apparent in many deployments of the coastal gliders. A few example plots are attached - m_water_depth plotted as semi-transparent bathymetry. By Lori Garzio, on 5/10/19 |
||
CP05MOAS |
Glider optodes typically exhibit a sensor lag of 20-25 seconds. Example attached of several segments with consecutive down and up casts for CP05MOAS-GL335-04-DOSTAM000 on 10/26/2015 showing a typical measurement time lag. Profiles should be analyzed for individual time lags and data should be adjusted. OOI doesn't necessarily need to make the adjustment but users should be aware of the issue. By Lori Garzio, on 5/15/19 |
||
CP05MOAS-GL335 Deployment: 1 |
|||
CP05MOAS-GL335 Deployment: 3 |
Short deployment (15 days) should be annotated. By Lori Garzio, on 5/15/19 |
||
CP05MOAS-GL335 Deployment: 4 |
Metadata | Start Date | End Date | Comment |
---|---|---|---|
CP05MOAS-GL335 |
11/10/15, 4:00 AM | 11/17/15, 9:34 AM |
Deployment 2: Glider experienced a leak in the bellophram and needed to be recovered early. No data expected after 2015-11-10T09:00:00.
Id: 638
By: cdobson
|
CP05MOAS-GL335 |
4/17/16, 8:00 PM | 4/18/16, 7:23 PM |
Deployment 3: Glider was accidentally recovered early by a fishing vessel on 2016-04-18; no data are expected after this date.
Id: 2034
By: cdobson
|
CP05MOAS-GL335 |
3/3/17, 10:00 PM | 3/6/17, 5:45 PM |
Deployment 5: Glider was struck by a vessel on the surface and needed to be recovered. No data are expected after 2017-03-04T03:00:00.
Id: 639
By: cdobson
|