BCO-DMO ERDDAP
Accessing BCO-DMO data
log in    
Brought to you by BCO-DMO    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  ADCP data from the Long-Term Observation Program (LTOP) from Mooring site NH10
on the Oregon Shelf from 1997-2004 as part of the U.S. GLOBEC program (NEP
project)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_2458)
Range: longitude = -124.3067 to -124.3067°E, latitude = 44.6467 to 44.6467°N, depth = 8.0 to 72.0m
Information:  Summary ? | License ? | ISO 19115 | Metadata | Background (external link) | Subset | Data Access Form | Files
 
Graph Type:  ?
X Axis: 
Y Axis: 
Color: 
-1+1
 
Constraints ? Optional
Constraint #1 ?
Optional
Constraint #2 ?
       
       
       
       
       
 
Server-side Functions ?
 distinct() ?
? ("Hover here to see a list of options. Click on an option to select it.Hover here to see a list of options. Click on an option to select it.Hover here to see a list of options. Click on an option to select it.Hover here to see a list of options. Click on an option to select it.")
 
Graph Settings
Marker Type:   Size: 
Color: 
Color Bar:   Continuity:   Scale: 
   Minimum:   Maximum:   N Sections: 
Draw land mask: 
Y Axis Minimum:   Maximum:   
 
(Please be patient. It may take a while to get the data.)
 
Optional:
Then set the File Type: (File Type information)
and
or view the URL:
(Documentation / Bypass this form ? )
    Click on the map to specify a new center point. ?
Zoom: 
[The graph you specified. Please be patient.]

 

Things You Can Do With Your Graphs

Well, you can do anything you want with your graphs, of course. But some things you might not have considered are:

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  year {
    Int16 _FillValue 32767;
    Int16 actual_range 1997, 2004;
    String bcodmo_name "year";
    String description "Year.";
    String long_name "Year";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/YEARXXXX/";
    String units "dimensionless";
  }
  mooring {
    String bcodmo_name "mooring";
    String description "Mooring ID (NH10 for this dataset).";
    String long_name "Mooring";
    String units "dimensionless";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 _FillValue NaN;
    Float64 actual_range 44.6467, 44.6467;
    String axis "Y";
    String bcodmo_name "latitude";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String description "Latitude in decimal degrees North";
    String ioos_category "Location";
    String long_name "Latitude";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P09/current/LATX/";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 _FillValue NaN;
    Float64 actual_range -124.3067, -124.3067;
    String axis "X";
    String bcodmo_name "longitude";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String description "Longitude in decimal degrees East";
    String ioos_category "Location";
    String long_name "Longitude";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P09/current/LONX/";
    String source_name "long";
    String standard_name "longitude";
    String units "degrees_east";
  }
  depth_w {
    Byte _FillValue 127;
    Byte actual_range 81, 81;
    String bcodmo_name "depth_w";
    Float64 colorBarMaximum 8000.0;
    Float64 colorBarMinimum -8000.0;
    String colorBarPalette "TopographyDepth";
    String description "Water depth in meters";
    String long_name "Depth";
    String standard_name "depth";
    String units "meters";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Float64 _FillValue NaN;
    Float64 actual_range 8.0, 72.0;
    String axis "Z";
    String bcodmo_name "depth";
    Float64 colorBarMaximum 8000.0;
    Float64 colorBarMinimum -8000.0;
    String colorBarPalette "TopographyDepth";
    String description "Depth of velocities in meters";
    String ioos_category "Location";
    String long_name "Depth";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P09/current/DEPH/";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  julian_day {
    Float64 _FillValue NaN;
    Float64 actual_range 2450673.5, 2453371.75;
    String bcodmo_name "unknown";
    String description "Julian day, where JD2440000 is 0000 hrs on 23 May 1968.";
    String long_name "Julian Day";
    String units "dimensionless";
  }
  yrday0_gmt {
    Float32 _FillValue NaN;
    Float32 actual_range 0.0, 365.75;
    String bcodmo_name "yrday0_gmt";
    String description "Day of Year, where 0.5 is 1200 hrs on 1 January.";
    String long_name "Yrday0 Gmt";
    String units "dimensionless";
  }
  month_gmt {
    String bcodmo_name "month_gmt";
    String description "Month in GMT.";
    String long_name "Month Gmt";
    String units "dimensionless";
  }
  day_gmt {
    String bcodmo_name "day_gmt";
    String description "Day of Month in GMT.";
    String long_name "Day Gmt";
    String units "dimensionless";
  }
  time_gmt {
    String bcodmo_name "time_gmt";
    String description "Time of Day in GMT (HHMM).";
    String long_name "Time Gmt";
    String units "dimensionless";
  }
  u {
    Float32 _FillValue NaN;
    Float32 actual_range -46.3, 42.32;
    String bcodmo_name "u";
    String description "Eastward Velocity (cm/s; Positive East)";
    String long_name "U";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/LCEWZZ01/";
    String units "centimeters/sec";
  }
  v {
    Float32 _FillValue NaN;
    Float32 actual_range -74.45, 92.56;
    String bcodmo_name "v";
    String description "Northward Velocity (cm/s; Positive North)";
    String long_name "V";
    String nerc_identifier "https://vocab.nerc.ac.uk/collection/P01/current/LCNSZZ01/";
    String units "centimeters/sec";
  }
 }
  NC_GLOBAL {
    String access_formats ".htmlTable,.csv,.json,.mat,.nc,.tsv,.esriCsv,.geoJson";
    String acquisition_description "\"\"";
    String awards_0_award_nid "54626";
    String awards_0_award_number "unknown GB NOAA";
    String awards_0_funder_name "National Oceanic and Atmospheric Administration";
    String awards_0_funding_acronym "NOAA";
    String awards_0_funding_source_nid "352";
    String awards_1_award_nid "54872";
    String awards_1_award_number "OCE-0000733";
    String awards_1_data_url "http://www.nsf.gov/awardsearch/showAward.do?AwardNumber=0000733";
    String awards_1_funder_name "NSF Division of Ocean Sciences";
    String awards_1_funding_acronym "NSF OCE";
    String awards_1_funding_source_nid "355";
    String awards_1_program_manager "Phillip R. Taylor";
    String awards_1_program_manager_nid "50451";
    String cdm_data_type "Other";
    String comment 
"NH10 Mooring data 
  collected by M. Kosro (kosro@coas.oregonstate.edu) 
 File created with clean_revise_kosro_uv_6hr1.pl 
  created Mon, 13 Mar 2006 by Hal Batchelder";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String creator_email "info@bco-dmo.org";
    String creator_name "BCO-DMO";
    String creator_type "institution";
    String creator_url "https://www.bco-dmo.org/";
    String data_source "extract_data_as_tsv version 2.3  19 Dec 2019";
    String date_created "2009-11-29T11:32:26Z";
    String date_modified "2019-10-31T14:23:59Z";
    String defaultDataQuery "&time<now";
    String doi "10.1575/1912/bco-dmo.2458.1";
    Float64 Easternmost_Easting -124.3067;
    Float64 geospatial_lat_max 44.6467;
    Float64 geospatial_lat_min 44.6467;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -124.3067;
    Float64 geospatial_lon_min -124.3067;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 72.0;
    Float64 geospatial_vertical_min 8.0;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2020-07-06T05:49:27Z (local files)
2020-07-06T05:49:27Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_2458.das";
    String infoUrl "https://www.bco-dmo.org/dataset/2458";
    String institution "BCO-DMO";
    String instruments_0_acronym "ADCP";
    String instruments_0_dataset_instrument_description "Upward looking acoustic Doppler current profilers have been used to measure vertical profiles of water velocity (insert actual sample interval here) at 2 or 4 m vertical intervals depending on instrument. The mooring is serviced in spring and fall. winter deployments generally use a Sontek 250 kHz profiler with 4 m vertical resolution; summer deployments use a Sontek 500 kHz profiler with 2 m resolution.";
    String instruments_0_dataset_instrument_nid "4140";
    String instruments_0_description 
"The ADCP measures water currents with sound, using a principle of sound waves called the Doppler effect. A sound wave has a higher frequency, or pitch, when it moves to you than when it moves away. You hear the Doppler effect in action when a car speeds past with a characteristic building of sound that fades when the car passes.
The ADCP works by transmitting \"pings\" of sound at a constant frequency into the water. (The pings are so highly pitched that humans and even dolphins can't hear them.) As the sound waves travel, they ricochet off particles suspended in the moving water, and reflect back to the instrument. Due to the Doppler effect, sound waves bounced back from a particle moving away from the profiler have a slightly lowered frequency when they return. Particles moving toward the instrument send back higher frequency waves. The difference in frequency between the waves the profiler sends out and the waves it receives is called the Doppler shift. The instrument uses this shift to calculate how fast the particle and the water around it are moving.
Sound waves that hit particles far from the profiler take longer to come back than waves that strike close by. By measuring the time it takes for the waves to bounce back and the Doppler shift, the profiler can measure current speed at many different depths with each series of pings. (More from WHOI instruments listing).";
    String instruments_0_instrument_external_identifier "https://vocab.nerc.ac.uk/collection/L05/current/115/";
    String instruments_0_instrument_name "Acoustic Doppler Current Profiler";
    String instruments_0_instrument_nid "405";
    String instruments_0_supplied_name "Acoustic Doppler Current Profiler";
    String keywords "bco, bco-dmo, biological, chemical, data, dataset, day, day_gmt, depth, depth_w, dmo, erddap, julian, julian_day, latitude, longitude, management, month, month_gmt, mooring, oceanography, office, preliminary, time, time_gmt, u, v, year, yrday0, yrday0_gmt";
    String license "https://www.bco-dmo.org/dataset/2458/license";
    String metadata_source "https://www.bco-dmo.org/api/dataset/2458";
    Float64 Northernmost_Northing 44.6467;
    String param_mapping "{'2458': {'lat': 'flag - latitude', 'depth': 'flag - depth', 'long': 'flag - longitude'}}";
    String parameter_source "https://www.bco-dmo.org/mapserver/dataset/2458/parameters";
    String people_0_affiliation "Oregon State University";
    String people_0_affiliation_acronym "OSU-CEOAS";
    String people_0_person_name "Mike Kosro";
    String people_0_person_nid "50461";
    String people_0_role "Principal Investigator";
    String people_0_role_type "originator";
    String people_1_affiliation "Woods Hole Oceanographic Institution";
    String people_1_affiliation_acronym "WHOI BCO-DMO";
    String people_1_person_name "Ms Dicky Allison";
    String people_1_person_nid "50382";
    String people_1_role "BCO-DMO Data Manager";
    String people_1_role_type "related";
    String project "NEP";
    String projects_0_acronym "NEP";
    String projects_0_description 
"Program in a Nutshell
Goal:  To understand the effects of climate variability and climate change on the distribution, abundance and production of marine animals (including commercially important living marine resources) in the eastern North Pacific. To embody this understanding in diagnostic and prognostic ecosystem models, capable of capturing the ecosystem response to major climatic fluctuations.
Approach: To study the effects of past and present climate variability on the population ecology and population dynamics of marine biota and living marine resources, and to use this information as a proxy for how the ecosystems of the eastern North Pacific may respond to future global climate change. The strong temporal variability in the physical and biological signals of the NEP will be used to examine the biophysical mechanisms through which zooplankton and salmon populations respond to physical forcing and biological interactions in the coastal regions of the two gyres. Annual and interannual variability will be studied directly through long-term observations and detailed process studies; variability at longer time scales will be examined through retrospective analysis of directly measured and proxy data. Coupled biophysical models of the ecosystems of these regions will be developed and tested using the process studies and data collected from the long-term observation programs, then further tested and improved by hindcasting selected retrospective data series.";
    String projects_0_geolocation "Northeast Pacific Ocean, Gulf of Alaska";
    String projects_0_name "U.S. GLOBEC Northeast Pacific";
    String projects_0_project_nid "2038";
    String projects_0_project_website "http://nepglobec.bco-dmo.org";
    String projects_0_start_date "1997-01";
    String publisher_name "Biological and Chemical Oceanographic Data Management Office (BCO-DMO)";
    String publisher_type "institution";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 44.6467;
    String standard_name_vocabulary "CF Standard Name Table v55";
    String subsetVariables "mooring,latitude,longitude,depth_w";
    String summary "ADCP data from the Long-Term Observation Program (LTOP) from Mooring site NH10 on the Oregon Shelf from 1997-2004 as part of the U.S. GLOBEC program.";
    String title "ADCP data from the Long-Term Observation Program (LTOP) from Mooring site NH10 on the Oregon Shelf from 1997-2004 as part of the U.S. GLOBEC program (NEP project)";
    String version "1";
    Float64 Westernmost_Easting -124.3067;
    String xml_source "osprey2erddap.update_xml() v1.3";
  }
}

 

Using tabledap to Request Data and Graphs from Tabular Datasets

tabledap lets you request a data subset, a graph, or a map from a tabular dataset (for example, buoy data), via a specially formed URL. tabledap uses the OPeNDAP (external link) Data Access Protocol (DAP) (external link) and its selection constraints (external link).

The URL specifies what you want: the dataset, a description of the graph or the subset of the data, and the file type for the response.

Tabledap request URLs must be in the form
https://coastwatch.pfeg.noaa.gov/erddap/tabledap/datasetID.fileType{?query}
For example,
https://coastwatch.pfeg.noaa.gov/erddap/tabledap/pmelTaoDySst.htmlTable?longitude,latitude,time,station,wmo_platform_code,T_25&time>=2015-05-23T12:00:00Z&time<=2015-05-31T12:00:00Z
Thus, the query is often a comma-separated list of desired variable names, followed by a collection of constraints (e.g., variable<value), each preceded by '&' (which is interpreted as "AND").

For details, see the tabledap Documentation.


 
ERDDAP, Version 2.02
Disclaimers | Privacy Policy | Contact