Northwest Environmental Moorings ERDDAP
Access To Puget Sound Mooring Data
Brought to you by NOAA WOAC NANOOS IOOS
Northwest Environmental Moorings (NWEM)
Welcome to the ERDDAP server for the Northwest Environmental Moorings (NWEM) Lab group at the Applied Physics Laboratory of the University of Washington.
NWEM maintains a number of buoys throughout the Puget Sound and along the Washington coast. This includes the Oceanic Remote Chemical Analyzer (ORCA) moorings, as well as the Northwest Enhanced Moored Observatory (NEMO).
The Oceanic Remote Chemical Analyzer (ORCA) moorings are autonomous profiling systems that collect near real-time water property and atmospheric data in Puget Sound, Washington State. Data are transmitted from the moorings to a server housed at the University of Washington in Seattle, where they are processed, quality controlled, and disseminated.
Since 2010 the University of Washington has maintained a pair of moorings 13 nautical miles west-northwest of La Push, Washington on the Washington continental shelf and within the Olympic Coast National Marine Sanctuary, collectively referred to as the Northwest Enhanced Moored Observatory (NEMO). The moorings consist of a large surface buoy (Cha'Ba or Quileute for "whale tail") and an adjacent (~400 m away) profiling subsurface mooring referred to as NEMO-subsurface. Both moorings collect oceanographic and atmospheric data, with oceanographic observations throughout much of the 100 m water column. Data are stored both locally and transferred to shore hourly to be displayed on the NANOOS Visualization System (NVS) in near real-time.
To learn more about the ORCA Data Processing, please read the Data Processing Manual, found here.
Start Using ERDDAP:
|Griddap lets you use the OPeNDAP hyperslab protocol to request data subsets, graphs, and maps from gridded datasets (for example, satellite data and climate model data). griddap documentation|
|Tabledap lets you use the OPeNDAP constraint/selection protocol to request data subsets, graphs, and maps from tabular datasets (for example, buoy data). tabledap documentation|
|ERDDAP's "files" system lets you browse a virtual file system and download source data files. WARNING! The dataset's metadata and variable names in these source files may be different than elsewhere in ERDDAP! You might prefer using the dataset's Data Access Form instead. "files" documentation|
|The Web Map Service (WMS) lets you request an image with data plotted on a map. WMS documentation|
In addition to serving data, ERDDAP has some handy converters:
|Acronyms||Convert a Common Oceanic/Atmospheric Acronym to/from a Full Name|
|FIPS County Codes||Convert a FIPS County Code to/from a County Name|
|Interpolate||Interpolate Values From Gridded Dataset Values|
|Keywords||Convert a CF Standard Name to/from a GCMD Science Keyword|
|Time||Convert a String Time to/from a Numeric Time|
|Units||Convert UDUNITS to/from Unified Code for Units of Measure (UCUM)|
|URLs||Convert Out-of-Date URLs into Up-to-Date URLs|
|Variable Names||Convert a Common Oceanic/Atmospheric Variable Name to/from a Full Name|
ERDDAP has an
FGDC Web Accessible Folder (WAF) with FGDC‑STD‑001‑1998 metadata files and an
ISO 19115 Web Accessible Folder (WAF) with ISO 19115‑2/19139 metadata files for all of the geospatial datasets in this ERDDAP.
RESTful Web Services
|Status||The Status web page is a quick way to check the current status/health of this ERDDAP, including a list of datasets which failed to load.|
|Out-Of-Date Datasets||The Out-Of-Date Datasets web page displays a list of near-real-time datasets, ranked by how out-of-date they are.|
|Subscriptions||ERDDAP has an email/URL subscription system so that you can be notified immediately whenever a dataset changes (for example, whenever new data is added to a near-real-time dataset).|
|Slide Sorter||Anyone can use ERDDAP's Slide Sorter to build a personal web page that displays graphs with the latest data (or other images or HTML content), each in its own, draggable slide.|
|Data Provider Form||The Data Provider Form is for people who have data and want it to be served by this ERDDAP. It collects basic information about the dataset and emails it to this ERDDAP's administrator.|