Seawater pH
- Reference Designator
- GP03FLMA-RIS01-04-PHSENF000
- Review Status
- Review Complete
- Note
- Depth
- 30m
- Class
- PHSEN (Seawater pH)
- Make / Model
- Sunburst / SAMI-pH
Dataset Reviews Last processed: 11/28/18, 5:31 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_inst | 329 | 328 | 0 | 0 | 0 | 0 | 3,936 | 7,200 | 28 / | 1 | 2 | Complete | ||||
| 2 | recovered_inst | 353 | 352 | 1 | 0 | 0 | 0 | 4,219 | 7,200 | 28 / | 3 | 2 | Complete | ||||
| 3 | recovered_inst | 389 | 388 | 0 | 0 | 0 | 0 | 4,653 | 7,200 | 48 / | 2 | Complete | |||||
| 4 | recovered_host | 383 | 27 | 2 | 273 | 1 | 79 | 314 | 7,200 | / | 4 | 2 | Complete | ||||
| 5 | recovered_inst | 380 | 372 | 7 | 0 | 0 | 0 | 4,464 | 7,200 | / | 2 | Complete |
Test Notes
- fail: data found in another stream (gaps: [3, 4] days: [3, 7])
- missing: ['pressure']
- fail: data found in another stream (gaps: [1] days: [1])
- no comparison: timestamps do not match
Data Coverage
| Deployment: | 1 | 2 | 3 | 4 | 5 |
|---|---|---|---|---|---|
| 7% | |||||
| 100% | 100% | 100% | 98% |
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 |
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 |
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 |
|
GP03FLMA-RIS01-04-PHSENF000 Method: telemetered |
7/23/18, 6:54 PM | 9/29/19, 11:54 AM |
Deployment 6: There will be no telemetered data from this instrument due to issues between the instrument and controller. The instrument is logging internally and data should be available at recovery. Id: 1497 By: cdobson |
Review Notes
| Metadata | Start Date | End Date | Comment |
|---|---|---|---|
|
GP03FLMA-RIS01-04-PHSENF000 |
pressure coordinate missing in the NetCDF files By Leila Belabbassi, on 5/29/19 |
||
|
GP03FLMA-RIS01-04-PHSENF000 |
data gaps are not annotated in the system for deployments 2, 4 and 5 By Leila Belabbassi, on 5/29/19 |
||
|
GP03FLMA-RIS01-04-PHSENF000 |
missing data found in another stream may be related to a time lag By Leila Belabbassi, on 5/29/19  |
||
|
GP03FLMA-RIS01-04-PHSENF000 |
8/1/13, 12:00 AM | 6/15/14, 12:00 AM |
suspect data By Leila Belabbassi, on 5/29/19 |
|
GP03FLMA-RIS01-04-PHSENF000 |
8/15/15, 12:00 AM | 10/1/15, 12:00 AM |
suspect data By Leila Belabbassi, on 5/29/19 |
|
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-04-PHSENF000 Deployment: 2 |
missing data found in another stream By Leila Belabbassi, on 5/29/19  |
||
|
GP03FLMA-RIS01-04-PHSENF000 Deployment: 4 |
recovered_inst data are missing in the system By Leila Belabbassi, on 5/29/19 |
||
|
GP03FLMA-RIS01-04-PHSENF000 Deployment: 5 |
7/13/17, 12:00 AM | 8/1/18, 12:00 AM |
suspect data By Leila Belabbassi, on 5/29/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 |