Dissolved Oxygen
- Reference Designator
- GP03FLMA-RIS01-03-DOSTAD000
- Review Status
- Review Complete
- Note
- Depth
- 30m
- Class
- DOSTA (Dissolved Oxygen Stable Response)
- Make / Model
- Aanderaa / Optode 4831
Dataset Reviews Last processed: 7/25/19, 7:22 PM
| Dep. | Preferred Method | Stream | DD | FD | SG | EG | Gaps | GD | TS | Rate (s) | Pressure Comp. | Time Order | Valid Data | Missing Data | Data Comp. | Missing Coords. | Review |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | recovered_host | 330 | 329 | 0 | 0 | 0 | 0 | 31,493 | 900 | 28 / 15 | 1 | 1 | Complete | ||||
| 2 | recovered_host | 354 | 353 | 0 | 0 | 0 | 0 | 33,863 | 900 | 28 / 0 | 2 | Complete | |||||
| 3 | recovered_host | 389 | 389 | 0 | 0 | 0 | 0 | 37,234 | 900 | 48 / 33 | Complete | ||||||
| 4 | recovered_host | 383 | 28 | 0 | 276 | 1 | 79 | 2,547 | 900 | / 43 | Complete | ||||||
| 5 | recovered_host | 380 | 119 | 0 | 192 | 1 | 70 | 11,093 | 900 | / 41 | 1 | 1 | Complete |
Test Notes
- no other streams for comparison
- missing: ['pressure']
Data Coverage
| Deployment: | 1 | 2 | 3 | 4 | 5 |
|---|---|---|---|---|---|
| 100% | 100% | 100% | 7% | 31% |
Lat/Lon Differences (km)
| Deployment: | 1 | 2 | 3 | 4 | 5 |
|---|---|---|---|---|---|
| 1 | 0.00 | ||||
| 2 | 0.62 | 0.00 | |||
| 3 | 0.65 | 0.09 | 0.00 | ||
| 4 | 1.16 | 0.56 | 0.51 | 0.00 | |
| 5 | 9.06 | 9.67 | 9.72 | 10.22 | 0.00 |
Example Composite Data Plot
System Annotations Show
| Metadata | Start Date | End Date | Comment |
|---|---|---|---|
|
GP03FLMA-RIS01-03-DOSTAD000 |
7/21/13, 6:44 PM | 6/14/14, 8:00 PM |
Deployment 1: Dissolved oxygen noise was high at various times throughout the deployment, possibly from biofouling.
Id: 774
By: lgarzio
|
|
GP03FLMA |
7/21/13, 6:44 PM | 6/14/14, 8:00 PM |
Deployment 1: Mooring was deployed 10-15m shallower than planned. Telemetered data are not available for this deployment. Id: 150 By: lgarzio |
|
GP03FLMA |
6/17/14, 2:00 AM | 6/4/15, 8:00 PM |
Deployment 2: Mooring was deployed 15-20m shallower than planned. Upon recovery of platform, biofouling was apparent on shallow CTDs. Id: 151 By: lgarzio |
|
GP03FLMA-RIS01-03-DOSTAD000 |
12/31/14, 7:00 PM | 6/4/15, 8:00 PM |
Deployment 2: Dissolved oxygen noise increased, possibly from biofouling.
Id: 775
By: lgarzio
|
|
GP03FLMA |
6/6/15, 6:40 PM | 6/28/16, 3:10 PM |
Deployment 3: Mooring was deployed 10-15m deeper than planned. Id: 152 By: lgarzio |
|
GP03FLMA |
6/30/16, 9:07 PM | 7/18/17, 11:13 AM |
Deployment 4: Mooring was deployed 10-15m deeper than planned. Id: 153 By: lgarzio |
|
GP03FLMA |
7/13/17, 7:00 PM | 7/27/18, 6:14 PM |
Deployment 5: Telemetered data are not available for this deployment because gliders were not deployed. Id: 141 By: lgarzio |
Review Notes
| Metadata | Start Date | End Date | Comment |
|---|---|---|---|
|
GP03FLMA |
7/1/16, 1:07 AM | 7/27/18, 10:14 PM |
Deployments 4 and 5 don't have deployment depths defined in asset management. By Lori Garzio, on 1/3/19 |
|
GP03FLMA-RIS01-03-DOSTAD000 Deployment: 1 |
7/21/13, 10:44 PM | 6/15/14, 12:00 AM |
Suspect data from biofouling - see annotation ID 774 By Lori Garzio, on 8/1/19  |
|
GP03FLMA-RIS01-03-DOSTAD000 Deployment: 2 |
The deployment 2 .nc file is missing the pressure coordinate. By Lori Garzio, on 8/1/19 |
||
|
GP03FLMA-RIS01-03-DOSTAD000 Deployment: 2 |
6/17/14, 12:00 AM | 6/20/14, 12:00 AM |
Suspect values at the beginning of the deployment, most likely while the mooring was settling. By Lori Garzio, on 8/1/19  |
|
GP03FLMA-RIS01-03-DOSTAD000 Deployment: 2 |
12/1/14, 12:00 AM | 6/5/15, 12:00 AM |
Suspect data from biofouling - see annotation ID 775 By Lori Garzio, on 8/1/19  |
|
GP03FLMA-RIS01-03-DOSTAD000 Deployment: 3 |
3/1/16, 12:00 AM | 6/28/16, 7:10 PM |
Suspect data - values drop suddenly towards the end of the deployment By Lori Garzio, on 8/1/19  |
|
GP03FLMA Deployment: 5 |
7/13/17, 11:00 PM | 7/27/18, 10:14 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 |