Skip to main content
U.S. flag

An official website of the United States government

Official websites use .gov
A .gov website belongs to an official government organization in the United States.

Secure .gov websites use HTTPS
A lock ( ) or https:// means you’ve safely connected to the .gov website. Share sensitive information only on official, secure websites.

Skip to content
  • Feedback

    • Glider - La Push Line: 2010 July - October

    Metadata Updated: October 27, 2025

    Seaglider La Push NANOOS line, Washington. Glider covering a 200km SW-NE transect off La Push (Olympic Peninsula), Washington, as part of the Northwest Association of Networked Ocean Observing Systems (NANOOS). Glider deployments complement two NANOOS moorings off La Push at the onshore (NE) end of the transect, and provide observations on dissolved oxygen and oceanographic conditions in this dynamic upwelling region that interacts with waters in the Salish Sea. Operated by the University of Washington Applied Physics Laboratory (UW-APL) and funded by NOAA via the U.S. Integrated Ocean Observing System (IOOS), with previous support from the Murdock Charitable Trust and the UW.

    Access & Use Information

    License: No license information was provided. If this work was prepared by an officer or employee of the United States government as part of that person's official duties it is considered a U.S. Government Work.

    Downloads & Resources

    Dates

    Metadata Date October 2, 2025
    Metadata Created Date July 27, 2025
    Metadata Updated Date October 27, 2025
    Reference Date(s) January 25, 2017 (creation), January 25, 2017 (issued)
    Frequency Of Update

    Metadata Source

    Harvested from ioos

    Other Data Resources

    Additional Metadata

    Resource Type Dataset
    Metadata Date October 2, 2025
    Metadata Created Date July 27, 2025
    Metadata Updated Date October 27, 2025
    Reference Date(s) January 25, 2017 (creation), January 25, 2017 (issued)
    Responsible Party Applied Physics Lab\nUniversity of Washington\nSeattle, WA (Point of Contact)
    Contact Email
    Guid glider_lapush_SG187-20100716T1208
    Access Constraints
    Bbox East Long -122.95865
    Bbox North Lat 48.162422
    Bbox South Lat 46.99215
    Bbox West Long -127.01479
    Coupled Resource [{"title": [], "href": ["#DataIdentification"], "uuid": []}, {"title": [], "href": ["#DataIdentification"], "uuid": []}, {"title": [], "href": ["#DataIdentification"], "uuid": []}]
    Frequency Of Update
    Harvest Object Id b7da0e56-472a-4a05-b6a3-0470e1a15b80
    Harvest Source Id 54e15a6e-6dde-4c9c-a8f0-345cc0dfccfb
    Harvest Source Title ioos
    Licence
    Lineage Processing start:\n20:37:40 23 Sep 2014 UTC: INFO: QC.py(381): Changed (6/467) 2:4 462 463 465 to QC_PROBABLY_BAD because raw temperature spikes\n20:37:40 23 Sep 2014 UTC: INFO: QC.py(393): Changed (2/467) 465 467 to QC_BAD because raw salinity below bound\n20:37:40 23 Sep 2014 UTC: INFO: QC.py(404): Changed (1/467) 467 to QC_BAD because bad raw salinity indicates raw conductivity issues\n20:37:40 23 Sep 2014 UTC: INFO: QC.py(424): Changed (8/467) 2:5 459 460 464 465 to QC_PROBABLY_BAD because raw conductivity spikes\n20:37:40 23 Sep 2014 UTC: INFO: MakeDiveProfiles.py(3099): Changed (1/467) 466 to QC_BAD because uncorrectable 0.0m raw conductivity bubble on climb\n20:37:40 23 Sep 2014 UTC: INFO: QC.py(196): Changed (5/467) 2:4 462 463 to QC_PROBABLY_BAD because changed raw temp implies changed raw salinity\n20:37:40 23 Sep 2014 UTC: INFO: QC.py(196): Changed (4/467) 5 459 460 464 to QC_PROBABLY_BAD because changed raw cond implies changed raw salinity\n20:37:40 23 Sep 2014 UTC: INFO: QC.py(196): Changed (1/467) 466 to QC_BAD because changed raw cond implies changed raw salinity\n20:37:40 23 Sep 2014 UTC: INFO: QC.py(381): Changed (6/467) 2:4 462 463 465 to QC_INTERPOLATED because temperature spikes\n20:37:40 23 Sep 2014 UTC: INFO: QC.py(393): Changed (2/467) 465 467 to QC_BAD because salinity below bound\n20:37:40 23 Sep 2014 UTC: INFO: QC.py(404): Changed (2/467) 465 467 to QC_BAD because bad salinity indicates conductivity issues\n20:37:40 23 Sep 2014 UTC: INFO: QC.py(424): Changed (6/467) 2:5 459 460 to QC_INTERPOLATED because conductivity spikes\n20:37:40 23 Sep 2014 UTC: INFO: MakeDiveProfiles.py(3145): Changed (1/467) 466 to QC_BAD because uncorrectable 0.0m conductivity bubble on climb\n20:37:40 23 Sep 2014 UTC: WARNING: MakeDiveProfiles.py(3215): Mass of vehicle in sg_calib_constants (51826.0) does not match $MASS in log file (52000.0); using sg_calib_constants\n20:37:40 23 Sep 2014 UTC: INFO: MakeDiveProfiles.py(3272): Changed (38/467) 156:193 to QC_BAD because slow apogee CT flow\n20:37:40 23 Sep 2014 UTC: INFO: MakeDiveProfiles.py(3299): On the bottom at 93.4m for 4.4 minutes.\n20:37:40 23 Sep 2014 UTC: INFO: MakeDiveProfiles.py(3305): Changed (11/467) 194:204 to QC_BAD because stuck on the bottom\n20:37:40 23 Sep 2014 UTC: INFO: MakeDiveProfiles.py(3373): Changed (10/467) 1:10 to QC_BAD because prior to dive start\n20:37:40 23 Sep 2014 UTC: INFO: MakeDiveProfiles.py(3452): Changed (5/467) 460:464 to QC_BAD because end of climb\n20:37:40 23 Sep 2014 UTC: INFO: QC.py(511): Changed (1/467) 459 to QC_PROBABLY_BAD because bad interpolation anchors\n20:37:40 23 Sep 2014 UTC: INFO: QC.py(512): SUGGESTION: 360 bad_conductivity data_points in_between 457 459 % bad interpolation anchors\n20:37:40 23 Sep 2014 UTC: INFO: MakeDiveProfiles.py(3479): Changed (67/467) 1:10 156:204 460:467 to QC_BAD because bad corrected temperature and conductivity suggests bad salinity\n20:37:40 23 Sep 2014 UTC: INFO: QC.py(196): Changed (67/467) 1:10 156:204 460:467 to QC_BAD because changed corrected salin implies changed speed\n20:37:40 23 Sep 2014 UTC: INFO: TempSalinityVelocity.py(1154): TSV: 0 12 stalled points 420 421 427:429 432 433 442 445 446 449 456\n20:37:41 23 Sep 2014 UTC: INFO: TempSalinityVelocity.py(1175): TSV exiting after 3 iterations\n20:37:41 23 Sep 2014 UTC: INFO: TempSalinityVelocity.py(1190): SUGGESTION: 360 interp_salinity data_points in_between 12 22 % suspect thermal-inertia points 13:18\n20:37:41 23 Sep 2014 UTC: INFO: TempSalinityVelocity.py(1190): SUGGESTION: 360 interp_salinity data_points in_between 390 392 % suspect thermal-inertia points 391\n20:37:41 23 Sep 2014 UTC: INFO: TempSalinityVelocity.py(1190): SUGGESTION: 360 interp_salinity data_points in_between 394 395 % suspect thermal-inertia points 394 395\n20:37:41 23 Sep 2014 UTC: INFO: TempSalinityVelocity.py(1190): SUGGESTION: 360 interp_salinity data_points in_between 397 398 % suspect thermal-inertia points 397 398\n20:37:41 23 Sep 2014 UTC: INFO: TempSalinityVelocity.py(1190): SUGGESTION: 360 interp_salinity data_points in_between 400 402 % suspect thermal-inertia points 400:402\n20:37:41 23 Sep 2014 UTC: INFO: TempSalinityVelocity.py(1190): SUGGESTION: 360 interp_salinity data_points in_between 404 409 % suspect thermal-inertia points 404 405\n20:37:41 23 Sep 2014 UTC: INFO: TempSalinityVelocity.py(1190): SUGGESTION: 360 interp_salinity data_points in_between 417 443 % suspect thermal-inertia points 431 443\n20:37:41 23 Sep 2014 UTC: INFO: QC.py(196): Changed (1/467) 459 to QC_PROBABLY_BAD because changed corrected cond implies changed corrected salinity\n20:37:41 23 Sep 2014 UTC: INFO: MakeDiveProfiles.py(3635): 67 (14.35%) HDM speeds are QC_BAD; 36 (7.71%) are stalled (467)\n20:37:41 23 Sep 2014 UTC: INFO: MakeDiveProfiles.py(3657): Average estimated final speed: 16.75 cm/s\n20:37:41 23 Sep 2014 UTC: INFO: MakeDiveProfiles.py(3660): RMS observed vs. computed w: 4.46 cm/s\n20:37:41 23 Sep 2014 UTC: INFO: MakeDiveProfiles.py(3712): Starting sensor extensions data processing\n20:37:41 23 Sep 2014 UTC: INFO: QC.py(196): Changed (6/467) 2:4 462 463 465 to QC_INTERPOLATED because changed temperature implies changed SBE43 oxygen\n20:37:41 23 Sep 2014 UTC: INFO: MakeDiveProfiles.py(3714): Finished sensor extensions data processing\n20:37:41 23 Sep 2014 UTC: INFO: MakeDiveProfiles.py(3746): Estimated total flight and drift time: 2356.7s (SM: 109.0s)\n20:37:41 23 Sep 2014 UTC: WARNING: MakeDiveProfiles.py(3762): Significant up/downwelling detected; DAC suspect.\n
    Metadata Language eng
    Metadata Type geospatial
    Old Spatial {"type": "Polygon", "coordinates": [[[-127.01479, 46.99215], [-122.95865, 46.99215], [-122.95865, 48.162422], [-127.01479, 48.162422], [-127.01479, 46.99215]]]}
    Progress
    Spatial Data Service Type ERDDAP tabledap
    Spatial Reference System
    Spatial Harvester True
    Temporal Extent Begin 2010-07-16T19:13:01Z
    Temporal Extent End 2010-10-17T15:08:50Z

    Didn't find what you're looking for? Suggest a dataset here.